29.198-133GPPOpen Service Access (OSA) Application Programming Interface (API)Part 13: Policy management Service Capability Feature (SCF)Release 9TS
It is expected that more and more OSA services will use policies to express operational criteria. It is also expected that network providers will host policy-enabled services that have been written by 3rd party application service providers. In order to manage policy information, control access to it and to request evaluation of policies a policy management service is needed. Consistent with this, a policy management provisioning manager, IpPolicyManager, and a policy evaluation manager, IpPolicyEvalManager have been defined.
APIs have been defined to offer provisioning services. These include APIs to create, update or view policy information for any policy enabled service. Similarly APIs have been defined to facilitate interactions between clients (e.g. a 3rd party application) and the policies of any policy enabled service. These include APIs to subscribe to policy events, to request evaluation of policies and to request the generation of policy events . All APIs conform to an underlying policy information model that is a derived from the policy core information model defined by the IETF in RFC 3460.
Clients that perform administrative tasks of behalf of a policy enabled service, e.g. create, update or delete policy information must obtain access to IpPolicyManager via the Framework. Administrative tasks may then be performed through methods supported by IpPolicyManager. Similarly, clients that need to invoke evaluation of policies of a specific policy enabled service may do so by obtaining access to IpPolicyEvalManager via the Framework.
Consistent with the above the Policy Management Service supports two classes of service interfaces for policy provisioning and policy evaluation. These are the PM Provisioning SCF and the PM Policy Evaluation SCF respectively.
Examples of policy enabled services include: A load balancing service that uses policies to manage application loads on the network, a charging service that determines charging criteria based on policies, a call management service that uses policies to direct end-user calls to appropriate call agents, etc.
Information in the present document is organized as follows:
- The Sequence diagrams give the reader a practical idea of how PM provisioning and PM evaluation SCFs are used by clients.
- The Class relationships clause shows relationships between the various interfaces supported by the PM provisioning and PM evaluation SCFs respectively.
- The Interface specification clauses describe in detail each of the interfaces shown within the Class diagram clause.
- The Data Definitions clause shows a detailed expansion of each of the data types associated with the methods within the classes. Note that some data types are used in other methods and classes and are therefore defined within the Common Data types part of this specification.
An implementation of this API which supports or implements a method described in the present document, shall support or implement the functionality described for that method, for at least one valid set of values for the parameters of that method. Where a method is not supported by an implementation of a Service interface, the exception P_METHOD_NOT_SUPPORTED shall be returned to any call of that method.