Transcription

Oracle CommunicationsCloud Native Policy and Charging RulesFunction User's GuideRelease 1.6.0F31348-01May 2020

Oracle Communications Cloud Native Policy and Charging Rules Function User's Guide, Release 1.6.0F31348-01Copyright 2019, 2020, Oracle and/or its affiliates.This software and related documentation are provided under a license agreement containing restrictions onuse and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify,license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law forinteroperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free. Ifyou find any errors, please report them to us in writing.If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it onbehalf of the U.S. Government, then the following notice is applicable:U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,any programs embedded, installed or activated on delivered hardware, and modifications of such programs)and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government endusers are "commercial computer software" or “commercial computer software documentation” pursuant to theapplicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use,reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/oradaptation of i) Oracle programs (including any operating system, integrated software, any programsembedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oraclecomputer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in thelicense contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloudservices are defined by the applicable contract for such services. No other rights are granted to the U.S.Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications thatmay create a risk of personal injury. If you use this software or hardware in dangerous applications, then youshall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure itssafe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of thissoftware or hardware in dangerous applications.Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks oftheir respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks areused under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc,and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registeredtrademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products,and services from third parties. Oracle Corporation and its affiliates are not responsible for and expresslydisclaim all warranties of any kind with respect to third-party content, products, and services unless otherwiseset forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not beresponsible for any loss, costs, or damages incurred due to your access to or use of third-party content,products, or services, except as set forth in an applicable agreement between you and Oracle.

nces1-2About Cloud Native Policy and Charging Rule Function ServicesHow the Services Talk to Each Other3Cloud Native Policy and Charging Rules Function ArchitectureAbout Policy Design Experience42-13-1Configuring Cloud Native Policy and Charging Rules FunctionUsing Cloud Native Core ConsoleConfiguring Services and Manageable Objects4-1Managing a Charging Server4-2Managing Custom AVPs4-3About Custom AVPs4-3Creating a Custom AVP4-4Modifying an AVP4-8Deleting an AVP4-8Managing Custom Vendors4-9About Custom Vendors4-9Creating a Custom Vendor4-9Modifying a Custom Vendor4-9Deleting a Custom Vendor4-10Creating a Media Profile4-10Session Viewer4-12Configuring Core Service4-12Managing Policy4-12Settings4-13iii

Creating a Policy Project4-13Managing State Variables4-14Data Model4-15Configuring Policy Common Configurations54-17Connecting to LDAP Data Source4-17Managing Match Lists4-20Importing Configurable Objects4-22Exporting Configurable Objects4-22Writing Policy ConditionsPolicy Condition Categories5-1Mobility Conditions5-1where the mobile session supports sponsored connectivity5-1where the Cell Identifier matches one of specified CI value(s)5-2where the IP address of the Serving Gateway matches one of specified value(s)(es)5-3where the IP-CAN type specified5-3where network initiated requests are supported5-4where the E-UTRAN Cell Identifier matches one of specified ECI value(s)5-4where the subscribed PRA area matches one of PRA area(s)5-5where the UE is inside/outside/inactive for any one of PRA Area5-6where the APN matches one of specified APN value(s)5-7Network Device Conditions5-8where the device type is specified type5-8where the User Equipment IMEISV matches one of specified IMEISV value(s)5-9Policy SDP Properties Conditionswhere the local codec data is an offer5-95-9where the local specified SDP property exists5-10where the local specified SDP property is numerically equal to value5-12where the local specified SDP property matches one of value(s)5-14Request Conditions5-16where the requested QCI is specified QCI5-16where the request supports feature name5-17where the session is an enforcement session5-18where the request AVP name exists5-18where the request AVP namevalue matches one of value(s)5-19where the request AVP name value is numerically equal to value5-20where the request AVP name value is contained in Match Lists select lists5-21where the request AVP name value contains one of value(s)5-22where the request AVP Media-Component-Description exists5-23where at least one flow has media type that matches specified type(s)5-23iv

where the AF-Application-ID matches one of specified value(s)5-24where the corresponding enforcement session supports feature name5-24where the flow media type is one of specified type(s)5-25where the flow usage is one of specified usage(s)5-26where the request is creating a new flow5-26where the Service-URN is one of specified value(s)5-27where the specific action is one of specified action(s)5-27where the rule report contains one of specified rule name(s) and the rule statusis active5-28where the request MPS Identifier matches one of value(s)5-28where the requested media component description reservation priority is one ofspecified5-29where the requested session reservation priority is one of specified5-30where the flow media type matches one of user defined media type(s)5-31where the Sponsor-Identity matches one of specified Sponsor Identity(s)5-31where the AF-Application-ID is available5-32where the requested APN aggregate maximum bitrate upstream is greater than# bps5-32Time of Day Conditions675-33where the current time is between start time and end time using configured localtime5-33where the current time is within the specified time period(s)5-34where today is a week day using configured local time5-35where today is a weekend day using configured local time5-35where today is day using configured local time5-36where today is the specified number(s) th day(s) of Any Month in natural orderusing configured local time5-37Actions for Writing Policy Rulesadd custom grouped AVP name and send always6-1set value to Existing or New custom AVP name and send always6-2set custom AVP name value to the policy context property name6-2remove custom AVP name from reply always6-3mark request AVP name as failed if exists and send always6-3set the user property name to Existing or New custom AVP name and send always6-4Cloud Native Policy and Charging Rule Function AlertsPCRF Alert Configuration7-3v

What's New in This GuideThis section introduces the new features for Release 1.6.0 in Oracle CommunicationsCloud Native Policy and Charging Rules Function (CNPCRF) User's Guide.New Features for Release 1.6.0For CNPCRF Release 1.6.0, this guide has been updated to include the following newdevelopment features: Added Session Viewer support Added Custom AVP support Added Custom Vendor support Added State Variables support Updated the Connecting to LDAP Data Source feature documentation to align withthe new GUI Added the supported conditions and actions for Custom AVP in the PolicyConditions and Actions chapter6

My Oracle SupportMy Oracle Support (https://support.oracle.com) is your initial point of contact for allproduct support and training needs. A representative at Customer Access Support canassist you with My Oracle Support registration.Call the Customer Access Support main number at 1-800-223-1711 (toll-free in theUS), or call the Oracle Support hotline for your local country from the list at l. When calling, make the selections inthe sequence shown below on the Support telephone menu: For Technical issues such as creating a new Service Request (SR), select 1. For Non-technical issues such as registration or assistance with My OracleSupport, select 2. For Hardware, Networking and Solaris Operating System Support, select 3.You are connected to a live agent who can assist you with My Oracle Supportregistration and opening a support ticket.My Oracle Support is available 24 hours a day, 7 days a week, 365 days a year.7

1IntroductionThis document provides information on how to use the Cloud Native Policy andCharging Rule Function (CNPCRF) and configure the services.OverviewThe Oracle Communications Cloud Native Core Policy and Charging Rules Function(cnPCRF) is a micro-services based solution for managing policy and chargingfunctionality in a 3G and 4G network. Oracle cnPCRF’s offers operators a highlyscalable PCRF that is cloud ready. It helps service providers to create and managecomplex network policies in a telecom network.Oracle Communications cnPCRF has the Oracle’s PCRF functionalities with productarchitecture designed for the cloud. The cnPCRF provides a new policy designer/configuration & troubleshooting GUI, besides a set of new functionalities andarchitectural changes, the prominent features are listed below: 3-Tier Architecture with N M Geo-Redundancy model Compliant with 3GPP Release 15 Leverages a common Oracle Communications Cloud Native Environment (CNE) Packaged to support both VM-based and container-based cloud infrastructure Policy solution handling 4G Policy and Charging Control (PCC) use cases withsupport to legacy diameter based interfaces Supports CI/CD Integrated with Kubernetes and 5G/CNE common services Integrated with DevOps workflows Supports all legacy diameter interfacesAcronymsThe following table provides information about the acronyms used in the document.Table 1-1AcronymsAcronymDefinitionCNPCRFCloud Native Policy Charging and Rules FunctionDNAIDN Access IdentifierFQDNFully Qualified Domain NameMDBVMaximum Data Burst VolumeMFBRMaximum Flow Bit RateNAINetwork Access Identifier1-1

Chapter 1ReferencesTable 1-1(Cont.) AcronymsAcronymDefinitionPSAPDU Session AnchorPDSPolicy Data SourceQFIQoS Flow IdentifierQoEQuality of ExperienceRQAReflective QoS AttributeRQIReflective QoS IndicationS-NSSAISingle Network Slice Selection Assistance InformationSUPISubscription Permanent IdentifierReferencesRefer to the following documents for more information. Oracle Communications Cloud Native Policy and Charging Rule Function(CNPCRF) Installation and Upgrade Guide.1-2

2About Cloud Native Policy and ChargingRule Function ServicesThis section provides information about the CNPCRF services which includes: PCRF Core ServicePCRF Core ServicePCRF core service includes all the features of 4G PCRF except those provided byMRA, including: Protocol implementation including the support of various call flows, validity check,etc. Session correlation Retrieval and storage of user information Invoker of policy service and process of policy actionsHow the Services Talk to Each OtherIn general, most services under Cloud Native Policy and Charging Rules Function(CNPCRF) would use ClusterIP as deployment type under Kubernetes clusterenvironment. However, the following two services need LoadBalancer deploymenttype which require external access: diam-gateway service cm serviceGiven above deployment structure, a public IP would allocate to the above twoservices which accept external request, the inner communication rely on cluster IP tofind each other.2-1

3Cloud Native Policy and Charging RulesFunction ArchitectureThe Oracle Communications Cloud Native Policy and Charging Rule Function(CNPCRF) is built as a cloud-native application composed of a collection ofmicroservices running in a cloud-native environment. It separates processing/businesslogic and state concerns following the corresponding logical grouping of microservices/components:Figure 3-1PCRF ArchitectureAbout Policy Design ExperiencePolicy design experience allows you to craft and deploy, from scratch, operatorpolicies in production in very less time. 5G brings the policy design experience to thenext level by providing flexibility, extensibility, modularization, and assurance to theoperator to rapidly, yet confidently deploy new operator policies and enable use casesmore faster.The Cloud Native Policy and Charging Rules Function (CNPCRF) packages its microservices into containers and leverages Kubernetes' constructs and abstractions suchas Pods, ReplicaSets, and services so it can enable Kubernetes to manage andorchestrate the CNPCRF. It also leverages Istio as a service mesh (including Envoyproxies as sidecars) for the internal communication amongst the various microservices. The Oracle Communications CNPCRF integrates with a variety of commonservices for data collection, analysis, and visualization services for operational aspectslike logs, metrics, and traces. The Oracle Communications CNPCRF comprises3-1

Chapter 3About Policy Design Experienceartifacts like Helm charts that encapsulate lifecycle instructions and resourcedependencies for all member components.The Oracle Communications CNPCRF is flexible to run in various cloud-nativeenvironments. The CNPCRF can be configured to leverage common services providedby the cloud-native environment and/or provide its own set if certain common servicesaren't provided by the underlying environment.The following figure highlights the various components used by the policy design andrun-time:Figure 3-2Policy Design ExperienceDesign Modular and flexible domain driven policy design Modules encompasses data model, triggers, conditions and actions Modules can be designed via a GUI (very intuitive, can be used by anyone) andallows any language supported by JVM for advances cases if needed (e.g. Java,Groovy, etc) Pre-packaged modules provided by Oracle Modules can be extended or built by operatorsRun-time Run-time engine service to expose APIs Run-time engine service to be stateless and independently scalable Newly designed policies or policy updates can be rolled out in an incrementalfashion (e.g. to a specific set of policy run-time engines) to enable canary releasesand ensure updates are working as expected before being rolled out globally3-2

Chapter 3About Policy Design ExperienceDebugging and testing Debugging policy logic capability as a complementary tool to the designexperience Automated testing framework to enable regression and validation of policy logicand modules before deployment3-3

4Configuring Cloud Native Policy andCharging Rules Function Using CloudNative Core ConsoleThis chapter describes how to configure different services in Oracle CommunicationsCloud Native Policy and Charging Rules Function (CNPCRF) and how to createpolicies and manageable objects in CNPCRF using Oracle Communications CloudNative Core Console.Cloud Native Core Console InterfaceThis section provides an overview of the Oracle Communications Cloud Native Core(CNC) Console, which includes a interface to aid in creating policies and manageableobjects in CNPCRF.To Log in:1.Open a web browser and enter the IP address of the CNC Console system.The login page opens.2.Enter your Username.3.Enter your Password.4.Click Login.Tha main page opens.Figure 4-1CNC Console InterfaceYou are logged in. All the PCF related configurations are available in the leftnavigation menu under PCRF.Configuring Services and Manageable ObjectsThis section describes how to create and manage the services and manageableobjects that are available to be used in policies.4-1

Chapter 4Configuring Services and Manageable ObjectsManaging a Charging ServerThis chapter describes how to define and manage charging servers within theCNPCRF GUI. A charging server is an application that calculates billing charges.To define a charging server:1.From the navigation pane, under PCRF, then under Configurations, selectCharging Servers.The Charging Server Management screen appears.2.Click Add.The Create Charging Server page opens.3.(Required) Enter the Name for the charging server.The name can only contain the characters A through Z, a through z, 0 through 9,period (.), hyphen (-), and underline ( ).4.Enter the Description/Location.Free-form text that identifies the charging server within the network. Enter up to250 characters.5.(Required) Enter the Host Name.The FQDN (fully qualified domain name assigned) to the charging server.6.Enter the Port number on which the charging server is listening for messages.If left blank, port 3868 is used.7.Select the Transport protocol used to communicate with the charging server:Available options include: tcpTransmission Control Protocol (used with TACACS ) udpUser Datagram Protocol (used with RADIUS)Note:If you configure the Transport protocol as udp, you cannot configurethe AAA Protocol as diameter. 8.sctpStream Control Transmission ProtocolSelect the Authentication, Authorization, and Accounting (AAA) Protocol used tocommunicate with the charging server.Available options include: diameter radius tacacs 4-2

Chapter 4Configuring Services and Manageable ObjectsNote:If you configure the Transport protocol as udp, you cannot configure theAAA Protocol as diameter.9.Select if transport Security is used to communicate with the charging server.10. Click Save.The charging server is displayed on the Charging Server Management page.Note:Use pencil icon or trash bin icon available in the next column to edit orupdate the created charging server.Managing Custom AVPsThis chapter describes how to create, modify, and delete custom third-party attributevalue pairs (AVPs) in the CNPCRF User Interface (UI).In a wireless network, custom AVPs are used to encapsulate protocol-specific data forrouting, authentication, authorization, and accounting information.About Custom AVPsAn attribute-value pair (AVP) is used to encapsulate protocol-specific information withusage monitoring supported by the MPE device. Diameter messages such as RAA,CCA, CCR, and RAR are supported by third-party AVP policy conditions. Thesupported outgoing Diameter messages set or remove third-party AVPs.Note:The Diameter messages listed are examples only. There are manymessages associated with Diameter.You can create policy conditions to evaluate the presence of both standard (base) andthird-party AVPs in Diameter messages or group AVPs during policy execution. Apolicy condition can check for the presence of both standard and third-party AVPs inincoming Diameter messages and evaluate their values. A policy action can usestandard and third-party AVPs for routing, authentication, authorization, andaccounting.Standard AVPs can be included in third-party AVP conditions and actions. To includea standard (base) AVP in a nonstandard application message, or to use a prestandard AVP as a standard AVP, define it as a custom AVP.When defined, custom AVPs are located at the end of a parent Diameter message orgroup AVP. If the parent AVP is null, the custom AVP is inserted at the root level of the4-3

Chapter 4Configuring Services and Manageable Objectsmessage. For example, a custom AVP definition appears at the end of this ChargingRule-Install message:Charging-Rule-Install :: AVP Header: 1001 *[ Charging-Rule-Definition ]*[ Charging-Rule-Name ]*[ Charging-Rule-Base-Name ][ Bearer-Identifier ][ Rule-Activation-Time ][ Rule-Deactivation-Time ][ Resource-Allocation-Notification ][ Charging-Correlation-Indicator ]*[ customAVP ]A Set or Get SPR user attribute value can be set to the defined third-party AVP inDiameter messages. You can also set or remove defined third-party AVPs during theexecution point.A third-party AVP is identified by a unique identifier in the following format:name:vendorIdFor example:Conditionwhere the request AVP NEW AVP3:555 value is numerically equal to 2012ParametersThe AVP name and vendor ID. In the example, the vendor ID is 555.DescriptionA well-defined AVP custom name is referred to if the vendor ID is not specified.When entering and sending a new third-party AVP definition to an MPE or MRAdevice, the definition must include the AVP name, code, vendor ID, data type, and anoptional AVP flag.Validation of the AVP code, Name, and vendor ID prohibits a user from overwriting theexisting base AVPs.These AVP actions include the ability to perform the following: Routing Authentication Authorization AccountingCreating a Custom AVPTo create a Custom AVP:1.From the PCRF section of the navigation pane, select Custom AVP underConfigurations .The Custom AVP Management screen appears.4-4

Chapter 4Configuring Services and Manageable Objects2.Click Add.The Create Custom AVP page opens.3.Enter information as appropriate:a.AVP Name (required) — The name you assign to the AVP.The name can only contain the characters A–Z, a–z, 0–9, period (.), hyphen(-), and underline ( ). The maximum length is 255 characters.b.Description — Free-form text that identifies the AVP.Enter up to 250 characters.c.AVP Code (required) — A unique numeric value assigned to the new AVP.d.Vendor — Select a vendor from the vendor list.To add a vendor to the list, see Managing Custom Vendors .e.Mandatory Flag (optional) —f.Protect Flag (optional) — When checked, specifies the protected AVP values.g.May Encrypt Flag — The AVP is encrypted if the checkbox is specified.h.Vendor Specific Flag — The AVP is vendor specific if the checkbox isspecified.Note:This box is checked automatically if the value of the vendor ID is not0.i.AVP Type (required) — Select the data type from the list: address enumerated float32 float64 grouped id int32 int64 ipFilterRule octetString time uint32 uint64 uri utf8String4-5

Chapter 4Configuring Services and Manageable Objectsj.Parent AVP — If the AVP is a member of a grouped AVP, then the parentAVP must be specified. Select one of the following from the list: ADC-Rule-Definition:10415 ADC-Rule-Install:10415 ADC-Rule-Remove:10415 ADC-Rule-Report:10415 AF-Correlation-Information:10415 Acceptable-Service-Info:10415 Access-Network-Charging-Identifier-Gx:10415 Access-Network-Charging-Identifier:10415 Access-Network-Physical-Access-ID:10415 Allocation-Retention-Priority:10415 Application-Detection-Information:10415 CC-Money Charging-Information:10415 Charging-Rule-Definition-3GPP2:5535 Charging-Rule-Definition:10415 Charging-Rule-Event-Cisco:9 Charging-Rule-Event-Trigger-Cisco:9 Charging-Rule-Install-3GPP2:5535 Charging-Rule-Install:10415 Charging-Rule-Remove:10415 Charging-Rule-Report-3GPP2:5535 Charging-Rule-Report:10415 Codec-Data-Tmp:10415 Codec-Data:10415 Cost-Information Default-EPS-Bearer-Qos:10415 E2E-Sequence Envelope:10415 Event-Report-Indication:10415 Explicit-Route-Record:21274 Explicit-Route:21274 Failed-AVP Final-Unit-Indication Flow-Description-Info:5535 Flow-Description:104154-6

Chapter 4Configuring Services and Manageable Objects Flow-Grouping:10415 Flow-Info:5535 Flow-Information:10415 Flow:10415 G-S-U-Pool-Reference Granted-Qos:5535 Granted-Service-Unit Juniper-Discovery-Descriptor:2636 Juniper-Provisioning-Descriptor:2636 LI-Indicator-Gx:12951 LI-TargetMFAddr:12951 Media-Component-Description:10415 Media-Sub-Component:10415 Multiple-Services-Credit-Control Offline-Charging:10415 PCEF-Forwarding-Info:971 PCEF-Info:971 PS-Furnish-Charging-Information:10415 PS-information:10415 Packet-Filter-Information:10415 Qos-Information-3GPP2:5535 Qos-Information:10415 Qos-Rule-Install:10415 Qos-Rule-Definition:10415 Qos-Rule-Remove:10415 Qos-Rule-Report:10415 Reachable-Peer:21274 Redirect-Information:10415 Redirect-Server Requested-Qos:5535 Requested-Service-Unit Service-Information:10415 Service-Parameter-Info Siemens-DL-SDP-Data:4329 Siemens-UL-SDP-Data:4329 Subscription Id Subscription-Id-3GPP:104154-7

Chapter 4Configuring Services and Manageable Objects Supported-Features:10415 TDF-Information:10415 TFT-Packet-Filter-Information:10415 TMO-Redirect-Server-29168 Time-Quota-Mechanism:10415 Trigger:10415 Tunnel-Header-Filter:10415 Unit-Value Usage-Monitoring-Control:21274 Usage-Monitoring-Information:10415 Used-Service-Unit User-CSG-Information:10415 User-Equipment-Info User-Location-Info-3GPP:10415 VZW-Access-Network-Physical-Access-ID:12951 Vendor-Specific-Application-Id Vzw-Trigger:129514.Click Save.5.If the AVP name matches the name of a standard AVP, a confirmation messagedisplays. Click OK to overwrite the existing AVP.The AVP is created.Modifying an AVPTo modify an AVP:1.From the PCRF section of the navigation pane, select Custom AVP underConfigurations .The Custom AVP Management page opens in the work area, listing the definedAVPs.2.From the work area, click(pencil icon), located to the right of the AVP.The Edit Custom AVP page opens.3.Modify AVP information as required.For a description of the fields contained on this page, see Creating a Custom AVP.4.Click Save.The AVP is modified.Deleting an AVPTo delete an AVP:4-8

Chapter 4Configuring Services and Manageable Objects1.From the PCRF section of the navigation pane, select Custom AVP underConfigurations .The Custom AVP Management page opens in the work area, listing the definedAVPs.2.From the work area, click(trash can icon), located to the right of the AVP.A confirmation message displays.3.Click OK.The AVP is deleted.Managing Custom VendorsThis chapter describes how to create, modify, and delete custom vendor definitions inthe CNPCRF User Interface (UI).Custom vendors are used in RADIUS Change of Authorization (CoA) messages.About Custom VendorsA custom vendor is used to define a vendor in the CNPCRF system. This dictionaryincludes vendor IDs and text descriptions. You can define custom vendors and addthem to the dictionary.Creating a Custom VendorTo create a custom vendor:1.From the PCRF section of the navigation pane, select Custom Vendor underConfigurations .The Custom Vendor Management screen appears.2.Click Add.The Create Custom Vendor page opens.3.Enter information as appropriate:a.Name (required) — The name you assign to the vendor.The name can only contain the characters A–Z, a–z, 0–9, period (.), hyphen(-), and underline ( ).b.Description — Free-form text that identifies the vendor.Enter up to 250 characters.c.Vendor Id — Enter the vendor ID.Enter a positive integer.4.Click Save.The vendor is created.Modifying a Custom VendorTo modify a custom vendor definition:4-9

Chapter 4Configuring Services and Manageable Objects1.From the PCRF section of the navigation pane, select Custom Vendor underConfigurations .The Custom Vendor Management page opens in the work area, listing thedefined vendors.2.From the work area, click(pencil icon), located to the right of the vendor.The Edit Custom Vendor page opens.3.Modify Vendor information as required.For a description of the fields contained on this page, see Creating a CustomVendor .4.Click Save.The Vendor is modified.Deleting a Custom VendorYou cannot delete a custom vendor definition that is used in a CoA template.To delete a custom vendor definition:1.From the PCRF section of the navigation pane, select Custom Vendor underConfigurations .The Custom Vendor Management page opens in the work area, listing thedefined vendors.2.From the work area, click(trash can icon), located to the right of the vendor.A confirmation message displays.3.Click OK.The custom vendor definition is deleted.Creating a Media ProfileThis section defines how to manage media profiles in the CNPCRF GUI. In a cablenetwork, a media profile describes a CODEC supported for Rx-to-PCMM translation.Note:Media Profiles is a function that is applicable to Cable mode only.To create a media profile:1.From the navigation pane, under PCRF, then under Configurations, select MediaProfiles.The Media Profile Management screen appears.2.Click Add.The Create Media Profile page opens.4-10

Chapter 4Configuring Services and Manageable Objects3.Enter the following information:a.ID — Unique ID assigned to the media profile.b.Name — Unique name assigned to the media profile.c.Description — specifies the description of the media profile.d.Codec Name — Unique media subtype assigned to the media profile.This is defined in the IANA MIME registration for the CODEC. Enter a string ofup to 255 characters.e.f.Transport Type — Select

3 Cloud Native Policy and Charging Rules Function Architecture . Creating a Media Profile 4-10 Session Viewer 4-12 Configuring Core Service 4-12 Managing Policy 4-12 . where the Cell Identifier matches one of specified CI value(s) 5-2 where the IP address