29.198-133GPPOpen Service Access (OSA) Application Programming Interface (API)Part 13: Policy management Service Capability Feature (SCF)Release 9TS
The following sequence diagram shows how a policy signature interface is created within a given (service) domain. A signature is used to establish the context of a policy evaluation request made by a client. A signature definition includes the names of input variables that may be used in the evaluation request. It also includes the name of all output, relevant policy roles and group names. The latter are used to select exactly those groups and rules that are relevant for the evaluation request.
1: All changes are performed in a transaction bracket.
2: This method is used by the client to navigate to the relevant domain.
4: A new Signature is created within the chosen domain.
6: Names of all input variables associated with this signature are specified.
7: Names of all output variables associated with the signature are specified.
8: Name of the rule Group(s) relevant to the request is specified. This could be a NULL collection but it is advisable to specify a name(s) for performance reasons.
9: Name of policy roles that are used to select rules relevant to the request. This could be a NULL collection but it is advisable to specify policy role name(s).
10: Transaction is committed. At this stage a new signature has been created under the selected domain.