# Communication Service Reference

# EWS Subscriber Profile Communication Service

This chapter describes the Extended Web Services Subscriber Profile communication service in detail:

- An Overview of the Extended Web Services Subscriber Profile Communication Service

- How It Works
- Supported Network Protocols

- Configuration Specifics for the Extended Web Services Subscriber Profile Communication Service

- Charging Data Records
- Event Data Records
- Statistics
- Supported Address Schemes

## An Overview of the Extended Web Services Subscriber Profile Communication Service

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:

- Retrieve the specific value for a particular property belonging to a subscriber profile stored in an LDAP data source.
- Retrieve an entire subscriber profile from an LDAP data source, subject to SLA filtering.

### How It Works

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.

### Supported Network Protocols

Off-the shelf, the Extended Web Services Subscriber Profile communication service can be configured to support the following network protocol:

- LDAPv3

#### LDAPv3

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.

## Configuration Specifics for the Extended Web Services Subscriber Profile Communication Service

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:

- Charging Data Records
- Event Data Records
- Statistics
- Supported Address Schemes

### Charging Data Records

There are two specific CDRs associated with the Extended Web Services Subscriber Profile/LDAP communication service. They occur when the following criteria are met:

- After Oracle Communications Services Gatekeeper has returned a full or partial subscriber profile to an application based on one or more attributes requested by that application.
- After Oracle Communications Services Gatekeeper has returned a subscriber profile to an application based on the ID of the profile.

### Event Data Records

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-1 Event types emitted in the EWS Subscriber Profile/LDAP communication service
EdrId | Method Called
--- | ---
13001 | get
13002 | getProfile

### Statistics

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.

Table 13-2 Transaction types for EWS Subscriber Profile/LDAP communication service
Method | Transaction type
--- | ---
get | TRANSACTION_TYPE_SUBSCRIBER_PROFILE
getProfile | TRANSACTION_TYPE_SUBSCRIBER_PROFILE

### Supported Address Schemes

The EWS Subscriber Profile/LDAP communication service supports the`tel:,` `id:,` `imsi:` and `ipv4:` address schemes.