|
|
This chapter describes the Extended Web Services Subscriber Profile communication service in detail:
There is no standard available for this service, although it uses elements from preliminary Parlay X drafts (preliminary as of January 2008) for this functionality.
| Note: | The RESTful Service Facade Subscriber Profile interfaces provide RESTful access to this same functionality. The internal representations are identical, and for the purposes of creating SLAs and reading CDRs, etc., they are the same. |
Using these interfaces an application can:
The Extended Web Services Subscriber Profile communication service can be used by applications that need to retrieve subscriber profile data from an LDAP server attached to the underlying network.
Off-the shelf, the Extended Web Services Subscriber Profile communication service can be configured to support the following network protocol:
When Oracle Communications Services Gatekeeper is configured to use this protocol, it connects to an LDAP server. See “Appendix A: Standards and Specifications” in Concepts and Architectural Overview for the exact version of the standard Oracle Communications Services Gatekeeper supports.
Communication services share many common features, covered in “Introducing Communication Services” in Concepts and Architectural Overview, but each one has a few characteristics that are specific only to that service. This section describes those specific features for the Extended Web Services Subscriber Profile communication service, including:
There are two specific CDRs associated with the Extended Web Services Subscriber Profile/LDAP communication service. They occur when the following criteria are met:
The EDRs produced by the Extended Web Services Subscriber Profile/LDAPv3 communication service are documented in Table 13-1. This does not include EDRs created when exceptions are thrown. For more information on the contents of standard EDRs, see Events, Alarms, and Charging.
Table 13-2 outlines the correlation between the methods being invoked from either the application (in application-initiated requests) or the telecom network (in network-initiated requests) and the transaction type collected by the statistics counters in Oracle Communications Services Gatekeeper for the EWS Subscriber Profile/LDAP communication service:
| Note: | Method names for network-initiated requests are specified by the internal Gatekeeper name, which is not necessarily the same as the message from the network. |
The EWS Subscriber Profile/LDAP communication service supports the tel:, id:, imsi: and ipv4: address schemes.
|