# Communication Service Reference

# Parlay X 2.1 Terminal Location Communication Services

This chapter describes the Parlay X 2.1 Terminal Location communication services in detail:

- An Overview of the Parlay X 2.1 Terminal Location Communication Service

- Processing Direct Queries/Application-initiated Requests
- Processing Notifications/Network-triggered Requests
- Supported Network Protocols

- Configuration Specifics for the Parlay X 2.1 Terminal Location Communication Services

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

## An Overview of the Parlay X 2.1 Terminal Location Communication Service

The SOAP Service Facade Terminal Location communication services implement the Parlay X 2.1 Terminal Location set of interfaces. For the exact version of the standard these communication services support, see “Appendix A: Standards and Specifications” in Concepts and Architectural Overview, another document in this set.

Note: | The RESTful Service Facade Terminal Location 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 a Terminal Location communication service, an application can:

- Ask for the location of one or many terminals by polling
- Ask for the distance between a given terminal and a given position
- Sign up to be notified when a terminal enters or leaves a specified geographical area
- Receive notifications when the terminal enters or leaves the specified geographical area
- Sign up to be notified periodically about the location of a terminal
- Receive periodic location notifications about the location of a terminal

The application can specify a number of parameters concerning the nature of the notification. These include:

- Requested accuracy
- Accepted accuracy
- Accepted response time
- Maximum age of location data
- Tolerance, which expresses the priority of response time versus accuracy
- Minimum frequency of notifications
- Duration of notifications
- Maximum number of notifications

Ultimately, the nature of the information that is available to the application depends on the network node and network protocol used. Not all networks or protocols support all operations. The accuracy of the location provided, the response times, and the frequency of notification are all also dependent on the specifics of the protocol and network node used.

### Processing Direct Queries/Application-initiated Requests

If an application directly queries Oracle Communications Services Gatekeeper for the location of a terminal or group of terminals, Oracle Communications Services Gatekeeper sends the request to the network node, and the location information is sent back synchronously in the response to the request.

### Processing Notifications/Network-triggered Requests

If an application registers for periodic or geographically-defined notifications, information for the application (which may or may not include the location data for one or more terminals) arrives at Oracle Communications Services Gatekeeper from the network. The notification is passed on to the application. If the application acknowledges the reception of the notification, Oracle Communications Services Gatekeeper acknowledges the reception of the notification to the network. If the application does not acknowledge the reception of the notification, Oracle Communications Services Gatekeeper does not acknowledge the reception of the notification to the network.

### Supported Network Protocols

Off the shelf, the Terminal Location communication service can be configured to support the following network protocols:

- MLP 3.0 and 3.2

#### MLP 3.0 and 3.2

Oracle Communications Services Gatekeeper acts as an LCS/MLS client. It is possible to use either version of MLP. See “Appendix A: Standards and Specifications” in Concepts and Architectural Overview for the exact version of the standard Oracle Communications Services Gatekeeper supports.

Oracle Communications Services Gatekeeper can be configured to act in Standard Location or Emergency Location Immediate mode on the node level.

Oracle Communications Services Gatekeeper connects to the location server using HTTP. It always acts as a single LCS/MLS client towards the location server.

Note: | When using MLP 3.0, triggered notifications are not supported.

## Configuration Specifics for the Parlay X 2.1 Terminal Location Communication Services

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 Terminal Location communication services, including:

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

### Charging Data Records

#### Generation of CDRs

In the Terminal Location/MLP communication services, CDRs are written:

- When the response to a polling request (of whatever type) is successfully delivered to the application
- When a notification is received from the network
- When an error occurs

### Event Data Records

Events for Terminal Location using MLP are documented in Table 11-1. For more information, see Events, Alarms, and Charging..

Table 11-1 Event types emitted in Terminal Location/MLP communication services
EdrId | Description
--- | ---
9001 | getLocation
9002 | getTerminalDistance
9003 | getLocationForGroup
9004 | sendLocationRequest
9011 | LocationEnd
9012 | LocationError
9013 | LocationNotification

### Statistics

Table 11-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 Parlay X 2.1 Terminal Location/MLP communication services:

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 11-2 Transaction types for Parlay X 2.1 Terminal Location/MLP communication services
Method | Transaction type
--- | ---
getLocation | TRANSACTION_TYPE_USER_LOCATION
getLocationForGroup | TRANSACTION_TYPE_USER_LOCATION
getLocationDistance | TRANSACTION_TYPE_USER_LOCATION
locationNotification | TRANSACTION_TYPE_USER_LOCATION

### Supported Address Schemes

The Parlay X 2.1 Terminal Location/MLP communication services support the`tel:` address scheme.