1. Cloud Native Policy Control Function User's Guide
  2. Configuring Policy Control Function

4 Configuring Policy Control Function

This section provides the information for configuring Oracle Communications Policy Control Function (PCF) for various services.

PCF offers the following interfaces to configure the PCF system:

  • A web-browser based Graphical User Interface
  • A REST API based Machine-to-Machine interface
  • Kubernetes Configuration Maps

The minimum configurations required to bring up a working PCF instance is described in the below sections.

For more detailed and elaborate configuration information, please refer Configuring Policy Control Function Using Cloud Native Core Console.

For REST API information, please refer Oracle Communications Cloud Native Policy Control Function (PCF) REST Specification Document.

Network Repository Function (NRF) Configuration

A Kubernetes Configuration Map is provided to save the NRF address and the NF Profile information. You can edit the Kubernetes Configuration Map to register Policy Control Function (PCF) with the NRF.

To edit the Kubernetes Configuration Map

Open a console to the master node of the Kubernetes deployment and edit the config map named "pcf-name-application-config" where pcf-name is the HELM chart release name used at the time of installation, please refer

  1. Get a list of all the config maps in the PCF deployment namespace by entering this command: 
    kubectl get cm -n pcf-namespace
    where, pcf-namespace is the PCF deployment namespace used by helm command.
  2. Edit the application configuration map by entering this command: 
    kubectl edit cm pcf-name-application-config -n pcf-namespace
    where, pcf-name is the release name used by helm command.

    A standard unix vi editor is opened with the config map contents pre-filled. Use vi commands to edit the application configuration map.

  3. Verify the NRF address (fqdn/IP) and the port number.
  4. Check and add necessary NFs to "nrfClientSubscribeTypes". These NFs will be discovered and subscribed by PCF at the startup time. Leave this field empty if this onetime discovery and subscription for NFs is not required.
  5. Check and edit, as necessary, the PCF Profile to be registered with the NRF. For example, if required enter the IP details of the PCF Services.
  6. Save and exit the editor.

Global Configurations

You can manage and view the Global Configurations from this page.

To edit the Global Configurations:
  1. From the navigation menu, under PCF, click Global Configurations.

    The Global Configurations screen appears.

  2. Click Edit to edit the global configurations.
  3. Enter the following information:
    • Enable Tracing- Specifies whether to enable tracing. The default value is true.
    • Enable Metrics- Specifies whether to enable system metrics. The default value is true.
    • API Gateway Host- The name of the API gateway host.
    • API Gateway Port- The port number of the API gateway. (if a port other than the default is being used) The default value is 80.
    • Enable TLS- Specifies whether to enable TLS. The default value is false.
    • Enable Subscriber Activity Logging- Specifies whether to enable subscriber activity logging. The dafault value is false.
  4. Click Save.

Diameter Configurations

You can manage and view the Diameter Configurations from this page.

Settings

To edit the Settings:
  1. From the navigation menu, under Policy Common Configurations, and then under Diameter Configurations, click Settings.

    The Settings screen appears.

  2. Click Edit to edit the settings.
  3. Enter the following information:
    • Reconnect Delay (sec)- Enter the time frame to delay before attempting to reconnect after a connection failure in seconds. The default is 3 seconds.
    • Response Timeout (sec)- Enter the response timeout interval in seconds. The default is 5 seconds.
    • Connection Timeout (sec)- Enter the connection timeout interval in seconds. The default is 3 seconds.
    • WatchDog Interval (sec)- Enter the watchdog interval in seconds. The default is 6 seconds.
  4. Click Save.

Peer Nodes

To edit the Peer Node Configurations:
  1. From the navigation menu, under Policy Common Configurations, and then under Diameter Configurations, click Peer Node.

    The Peer Node Configurations screen appears.

  2. Click Add to create peer node.

    The Create Peer Node screen appears.

  3. Enter the following information:
    • Name- Unique Name of the peer node.
    • Type- Defines which type of diameter service it should take up. The value can be Application function (af) or diameter routing agent(dra).
    • Initiate Connection- Set it to True to initiate a connection for this peer node.
    • Port- Enter the port number. Enter a number from 0 to 65535.
    • Host- Enter the host name. Enter a FQDN, ipv4 or ipv6 address available for establishing diameter transport connections to the peer node .
    • Realm- Enter the realm name, that is, FQDNs to all of that computers that transact diameter traffic.
    • Identity- Enter a identity to define a node in a realm.
  4. Click Save.

    Note:

    You can import and export the Peer Node configurations by clicking on the Import and Export on the Peer Node Configurations screen.

Service Configurations

You can tailor the PCF services as per network operator's requirements using the Service configuration pages. The configurations include setting up end point addresses, setting up log levels and other debug information like tracing etc. and customizing and/or optimizing NF interactions for example with UDR etc.

Configuring Session Management Service

You can configure the session management service from this page.

To configure the Session Management Service:
  1. From the navigation menu, under PCF, then under Service Configurations, click Session Management Service.

    The Session Management Service screen appears.

  2. Click Edit to edit the session management service configurations.
  3. Check the default configuration for all the fields in all groups and edit as necessary.
  4. Click Save.

Refer Configuring Policy Control Function Using Cloud Native Core Console for the fields details.

Configuring Access and Mobility Service

You can configure the access and mobility service from this page.

To configure the Access and Mobility Service:
  1. From the navigation menu, under PCF, then under Service Configurations, click Access and Mobility Service.

    The Access and Mobility Service screen appears.

  2. Click Edit to edit the access and mobility service configurations.
  3. Check the default configuration for all the fields in all groups and edit as necessary
  4. Click Save.

Refer Configuring Policy Control Function Using Cloud Native Core Console for the fields details.

Configuring User Service

You can configure the user service from this page.

To configure the User Service:
  1. From the navigation menu, under PCF, then under Service Configurations, click User Service.

    The User Service screen appears.

  2. Click Edit to edit the user service configurations.
  3. In the Server Root URL field, enter the callback URI for notifications to be received by the User service (For example, while creating a subscription for the user with the UDR)
  4. Check the default configuration for all the fields in all groups and edit as necessary
  5. Click Save.

Refer Configuring Policy Control Function Using Cloud Native Core Console for the fields details.

Configuring Policy Authorization Service

You can configure the policy authorization service from this page.

To configure the Policy Authorization Service:
  1. From the navigation menu, under PCF, then under Service Configurations, click Policy Authorization Service.

    The Policy Authorization Service screen appears.

  2. Click Edit to edit the policy authorization service configurations.
  3. Check the default configuration for all the fields in all groups and edit as necessary
  4. Click Save.

Refer Configuring Policy Control Function Using Cloud Native Core Console for the fields details.

Configuring UE Policy Service

You can configure the UE policy service from this page.

To configure the UE Policy Service:
  1. From the navigation menu, under PCF, then under Service Configurations, click UE Policy Service.

    The UE Policy Service screen appears.

  2. Click Edit to edit the UE policy service configurations.
  3. In the Notification URI Root field, enter the callback URI for notifications to be received by the UE Policy service (For example, while creating a subscription for the NAS Message Transfer with the AMF)
  4. Check the default configuration for all the fields in all groups and edit as necessary
  5. Click Save.

Refer Configuring Policy Control Function Using Cloud Native Core Console for the fields details.

Note:

  • The NAS Message Maximum Packet Size field is not supported in this release of PCF and will not take effect.
  • The Validate User and Query User fields must always be set to false in this release of PCF.