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:
Individual attributes, identified using a path.
A collection of attributes.
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.
Namespaces
The SubscriberProfile interface and service use the namespaces:
The following describes the interfaces and operations that are available in the Extended Web Subscriber Profile Web Service.
Interface: SubscriberProfile
Operations to obtain specific subscriber profile attributes and operations to obtain a set of profile properties grouped together in a profile.
Operation: get
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.
Input message: get
Part name
Part type
Optional
Description
address
xsd:anyURI
N
Identity to get profile attributes for.
pathNames
xsd:string [1..unbounded]
N
Requested subscriber properties.
Expressed as a relative UNIX path.
Example:
serviceName/accessControlId/accessControlId
Output message: getResponse
Part name
Part type
Optional
Description
properties
PropertyTuple [1..unbounded]
N
All retrieved subscription property name and value pairs which are requested by application and allowed by the usage policies as specified in a filter.
Gets a set of profile properties grouped together in a profile identified by a certain profile ID.
Input message: getProfile
Part name
Part type
Optional
Description
subscriberID
xsd:string
N
Identity to get profile attributes for.
profileID
xsd:string
N
Identity of the profile to get.
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.
Output message: getResponse
Part name
Part type
Optional
Description
properties
PropertyTuple [1..unbounded]
N
All retrieved subscription property name and value pairs which are requested by application and allowed by the usage policies as specified in a filter.
