# Statement of Compliance

# Parlay X 2.1 Terminal Location

The following chapter describes the standard Oracle Communications Services Gatekeeper communication services and how the interfaces and protocols complies to standards.

- Parlay X 2.1 Terminal Location
- MLP 3.0/3.2 for Parlay X 2.1 Terminal Location

## Parlay X 2.1 Terminal Location

This section describes the standards compliance for the communication services for Parlay X 2.1 Terminal Location:

The Parlay X 2.1 interface complies to ETSI ES 202 391-9 V1.2.1 (2006-12), Open Service Access (OSA); Parlay X Web Services; Part 9: Terminal Location (Parlay X 2).

See http://portal.etsi.org/docbox/TISPAN/Open/OSA/ParlayX21.html for links to the specification.

Table 9-1 Statement of Compliance, Parlay X 2.1 Terminal Location
Method | Compliant (Yes | No) | Comment
--- | --- | ---
Interface: TerminalLocation
GetLocation | Y |
GetTerminalDistance | Y |
GetLocationForGroup | Y |
Interface: TerminalLocationNotificationManager
StartGeographicalNotification | Y |
StartPeriodicNotification | Y |
EndNotification | Y |
Interface: TerminalLocationNotification
LocationNotification | Y |
LocationError | Y |
LocationEnd | Y |

## MLP 3.0/3.2 for Parlay X 2.1 Terminal Location

The MPL 3.0/3.2 plug-in for Parlay X 2.1 Terminal Location acts as an LCS/MLS Client towards a location server using the MLP interface. It is possible to use either version 3.0 or version 3.2 of MLP. When using MLP 3.2, triggered notifications are supported. It is configurable on plug-in instance level wether tit shall operate in Standard Location or Emergency Location Immediate mode.

The plug-in connects to the Location Server using HTTP. The plug-in always acts as one single LCS/MLS Client towards the location server.

### Standards Compliance

Location Inter-operability Forum (LIF) Mobile Location Protocol, LIF TS 101 Specification Version 3.0.0 and Mobile Location Protocol 3.2 Candidate Version 3.2 Open Mobile Alliance, OMA-TS-MLP-V3_2-20051124-C(MLP 3.2.0).

A link to the MLP 3.0 specification is found on http://www.openmobilealliance.org/tech/affiliates/lif/lifindex.html

A link to the MLP 3.2 specification is found on http://www.openmobilealliance.org

Table 9-2 Statement of Compliance, MLP 3.0/3.2 for Parlay X 2.1 Terminal Location
Message | Compliant (Yes | No) | Comment
--- | --- | ---
Standard Location Immediate Service
Standard Location Immediate Request | Y |
Standard Location Immediate Answer | Y |
Emergency Location Immediate Service
Emergency Location Immediate Request | Y |
Emergency Location Immediate Answer | Y |
Triggered Location Reporting Service
Triggered Location Reporting Request | Y | Only when the plug-in operates in MLP 3.2 mode.
Triggered Location Reporting Answer | Y | Only when the plug-in operates in MLP 3.2 mode.
Triggered Location Report | Y | Only when the plug-in operates in MLP 3.2 mode.
Triggered Location Reporting Stop Request | Y | Only when the plug-in operates in MLP 3.2 mode.
Triggered Location Reporting Stop Answer | Y | Only when the plug-in operates in MLP 3.2 mode.

The attribute subclient is populated with the ID of the application instance group that the request originated from.