The Extended Web Services Subscriber Profile Web Service allows an application to get subscriber-specific data from data sources within the network operator’s domain.
Examples of data sources are subscriber databases containing information about terminal types in use, preferred language, and currency types. This information can be used by applications in order to control rendering options for rich media, charging information, and the language to be used in voice and text interaction with the end-user.
The interface is built around a model where the data can be retrieved in two different ways:
The attributes are keyed on a subscriber ID that uniquely identifies the subscriber for whom the attributes are valid or by an address that uniquely identifies the terminal for which the attributes are valid. An attribute is identified by a path name, which corresponds to a specific property. The following is an example of a path name:
serviceName/accessControlId/accessControlId
The syntax for the path is similar to relative file system paths in UNIX.
A collection of attributes is specified in a subscriber profile filter for the application or the service provider. Only allowed attributes, as specified in the filter, are returned.
The returned attributes are returned in the form of name-value pairs, or property tuples, where the name is expressed as a path name with a associated property value.
The interface is based on a proposal for a Parlay X Subscriber Profile Web Service interface.
The SubscriberProfile interface and service use the namespaces:
The data types are defined in the namespace:
In addition, Extended Web Services Subscriber Profile uses definitions common for all Extended Web Services interfaces:
The endpoint for the PushMessage interface is: http://<host>:<port>/ews/subscriber_profile/SubscriberProfile
Where host and port depend on the Oracle Communications Services Gatekeeper deployment.
The following data structures are used in the Extended Web Services Subscriber Profile Web Service.
Defines the response that the Oracle Communications Services Gatekeeper returns from Operation: get and Operation: getProfile.
The following describes the interfaces and operations that are available in the Extended Web Subscriber Profile Web Service.
Operations to obtain specific subscriber profile attributes and operations to obtain a set of profile properties grouped together in a profile.
Gets specific subscriber profile attributes. The requested attributes are identified by the pathNames parameter, and the possible values are restricted by the configured capabilities of the underlying data source. The allowed path name values are also restricted individually per service provider and application in the SLA.
Gets a set of profile properties grouped together in a profile identified by a certain profile ID.
Profile ID is ignored when connecting the to the network using the LDAPv3 network protocol plug-in. The collection of attributes that identifies the profile are provisioned as filters.
The document/literal WSDL representation of the SubscriberProfile interface can be retrieved from the Web Services endpoint, see Endpoint, or:
http://<host>:<port>/ews/subscriber_profile/SubscriberProfile?WSDL
http://<host>:<port>/ews/subscriber_profile/SubscriberProfile?WSDL/ews_subscriber_profile_interface.wsdl
http://<host>:<port>/ews/subscriber_profile/SubscriberProfile?WSDL/ews_common_types.xsd
Where host and port depend on the Oracle Communications Services Gatekeeper deployment.