SIST ES 202 391-9 V1.3.1:2008

SLOVENSKI STANDARD
SIST ES 202 391-9 V1.3.1:2008
01-september-2008
Odprti dostop do storitve (OSA) - Spletne storitve Parlay X - 9. del: Lokacija
terminala (Parlay X 2)

Open Service Access (OSA) - Parlay X Web Services - Part 9: Terminal Location (Parlay

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

The present document may be made available in more than one electronic version or in print. In any case of existing or

perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).

In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive

Users of the present document should be aware that the document may be subject to revision or change of status.

Information on the current status of this and other ETSI documents is available at

If you find errors in the present document, please send your comment to one of the following services:

DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered

3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.

Intellectual Property Rights................................................................................................................................5

Foreword.............................................................................................................................................................5

1 Scope........................................................................................................................................................6

2 References................................................................................................................................................6

2.1 Normative references.........................................................................................................................................6

3 Definitions and abbreviations...................................................................................................................7

3.1 Definitions..........................................................................................................................................................7

3.2 Abbreviations.....................................................................................................................................................7

4 Detailed service description .....................................................................................................................7

5 Namespaces..............................................................................................................................................7

6 Sequence diagrams...................................................................................................................................8

6.1 Terminal location query .....................................................................................................................................8

6.2 Terminal location group query ...........................................................................................................................9

6.3 Terminal location notification ..........................................................................................................................10

6.4 Terminal location notification with check immediate ......................................................................................11

6.5 Terminal location periodic notification ............................................................................................................12

7 XML Schema data type definition .........................................................................................................13

7.1 Latitude and Longitude values .........................................................................................................................13

7.2 Accuracy values...............................................................................................................................................13

7.3 EnteringLeavingCriteria enumeration..............................................................................................................14

7.4 LocationInfo structure......................................................................................................................................14

7.5 RetrievalStatus enumeration.............................................................................................................................14

7.6 LocationData structure.....................................................................................................................................14

7.7 DelayTolerance enumeration............................................................................................................................15

8 Web Service interface definition............................................................................................................15

8.1 Interface: TerminalLocation.............................................................................................................................15

8.1.1 Operation: getLocation...............................................................................................................................15

8.1.1.1 Input message: getLocationRequest......................................................................................................15

8.1.1.2 Output message: getLocationResponse.................................................................................................15

8.1.1.3 Referenced faults...................................................................................................................................16

8.1.2 Operation: getTerminalDistance.................................................................................................................16

8.1.2.1 Input message: getTerminalDistanceRequest .......................................................................................16

8.1.2.2 Output message: getTerminalDistanceResponse..................................................................................16

8.1.2.3 Referenced faults...................................................................................................................................16

8.1.3 Operation: getLocationForGroup................................................................................................................17

8.1.3.1 Input message: getLocationForGroupRequest ......................................................................................17

8.1.3.2 Output message: getLocationForGroupResponse.................................................................................17

8.1.3.3 Referenced faults...................................................................................................................................17

8.2 Interface: TerminalLocationNotificationManager............................................................................................17

8.2.1 Operation: startGeographicalNotification...................................................................................................18

8.2.1.1 Input message: startGeographicalNotificationRequest .........................................................................18

8.2.1.2 Output message: startGeographicalNotificationResponse....................................................................18

8.2.1.3 Referenced faults...................................................................................................................................19

8.2.2 Operation: startPeriodicNotification...........................................................................................................19

8.2.2.1 Input message: startPeriodicNotificationRequest..................................................................................19

8.2.2.2 Output message: startPeriodicNotificationResponse ............................................................................19

8.2.2.3 Referenced faults...................................................................................................................................20

8.2.3 Operation: endNotification.........................................................................................................................20

8.2.3.1 Input message: endNotificationRequest................................................................................................20

8.2.3.2 Output message: endNotificationResponse...........................................................................................20

8.2.3.3 Referenced faults...................................................................................................................................20

8.3 Interface: TerminalLocationNotification..........................................................................................................21

8.3.1 Operation: locationNotification..................................................................................................................21

8.3.1.1 Input message: locationNotificationRequest.........................................................................................21

8.3.1.2 Output message: locationNotificationResponse....................................................................................21

8.3.1.3 Referenced faults...................................................................................................................................21

8.3.2 Operation: locationError.............................................................................................................................21

8.3.2.1 Input message: locationErrorRequest....................................................................................................21

8.3.2.2 Output message: locationErrorResponse...............................................................................................21

8.3.2.3 Referenced faults...................................................................................................................................21

8.3.3 Operation: locationEnd...............................................................................................................................21

8.3.3.1 Input message: locationEndRequest......................................................................................................22

8.3.3.2 Output message: locationEndResponse.................................................................................................22

8.3.3.3 Referenced faults...................................................................................................................................22

9 Fault definitions......................................................................................................................................22

9.1 ServiceException..............................................................................................................................................22

9.1.1 SVC0200: Accuracy out of limit ................................................................................................................22

9.2 PolicyException...............................................................................................................................................22

9.2.1 POL0230: Requested accuracy not supported ............................................................................................22

9.2.2 POL0231: Geographic notification not available .......................................................................................22

9.2.3 POL0232: Periodic notification not available.............................................................................................22

10 Service policies ......................................................................................................................................23

Annex A (normative): WSDL for Terminal Location ......................................................................24

Annex B (informative): Bibliography...................................................................................................25

History ..............................................................................................................................................................26

IPRs essential or potentially essential to the present document may have been declared to ETSI. The information

pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found

in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in

respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee

can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web

This ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet

The present document is part 9 of a multi-part deliverable covering Open Service Access (OSA); Parlay X

The present document has been defined jointly between ETSI, The Parlay Group (http://www.parlay.org) and the 3GPP.

The present document is part 9 of the Stage 3 Parlay X 2 Web Services specification for Open Service Access (OSA).

The OSA specifications define an architecture that enables application developers to make use of network functionality

The present document specifies the Common aspects of the Parlay X 2 Web Services. The following are defined here:

References are either specific (identified by date of publication and/or edition number or version number) or

• Non-specific reference may be made only to a complete document or a part thereof and only in the following

- if it is accepted that it will be possible to use all future changes of the referenced document for the

Referenced documents which are not found to be publicly available in the expected location might be found at

For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,

the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the

reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the

method of access to the referenced document and the full network address, with the same punctuation and use of upper

NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee

The following referenced documents are indispensable for the application of the present document. For dated

references, only the edition cited applies. For non-specific references, the latest edition of the referenced document

[2] ETSI ES 202 391-1: "Open Service Access (OSA); Parlay X Web Services; Part 1: Common

[3] ISO 6709: "Standard representation of latitude, longitude and altitude for geographic point

For the purposes of the present document, the terms and definitions given in ES 202 391-1 [2] apply.

For the purposes of the present document, the abbreviations given in ES 202 391-1 [2] apply.

When a request for a group of terminals is made, the response may contain a full or partial set of results. This allows the

service to provide results based on a number of criteria including number of terminals for which the request is made and

amount of time required to retrieve the information. This allows the requester to initiate additional requests for those

The "xsd" namespace is used in the present document to refer to the XML Schema data types defined in

For an application to determine the location of a terminal device, it provides a terminal device address and desired

When an application requires the locations of a set of terminal devices, it may provide an array of terminal device

addresses, including network managed group addresses, and receive the location data for the set of devices requested.

An application can be notified of a terminal device entering or leaving a geographical area. When a matching event

In some applications, the terminal location notification will be used to watch for a specific location change. An example

is a "call when present" service, where the terminal location is checked and determined to be outside the target area, and

a notification is set up to notify the application when the terminal enters the target area. Between the time of the original

location determination and the time the notification is set up, the terminal could move into the target area, thus the

Using the check immediate flag, after the notification is established, the terminal location will be determined, and if the

terminal is in the target area, then a notification will be sent immediately. The following sequence diagram shows this

: Application : Terminal Location : Terminal Location : Notification : Notification

• The Enterprise Application checks the location of a terminal, and receives its location (in this scenario

• The Enterprise Application generates a correlator, and starts a notification with criteria defined to notify the

Enterprise Web Service when the terminal enters the target area and the check immediate flag set to true.

• Check the current location of the terminal, and determine if the terminal lies inside the target area.

• In this case, the terminal is in the target area, and a notification is delivered to the Enterprise Web Service.

• The count of notifications is incremented and compared to the notification count limit.

• In this case, a single notification was requested, and the end notification message is sent.

This scenario includes the full set of interactions in one sequence, which also shows that the notifications can be

An application can be notified of a terminal device location on a periodic basis. At each interval, a notification message

Latitude and longitude values used in the present document follow the conventions of the ISO 6709 [3] specification, as

Latitude values are expressed as floating point numbers in the range -90,0000 to +90,0000, using decimal degrees (as

opposed to minutes and seconds). Positive values indicate locations north of and on the equator. Negative values

Longitude values are expressed as floating point numbers in the range -180,0000 to +180,0000, using decimal degrees

(as opposed to minutes and seconds). Positive values indicate locations east of and on the prime meridian (Greenwich).

Negative values indicate locations west of the prime meridian up to the 180 meridian.

Two accuracy values are used in some of the operations. These values express the desire of the application for the

location information to be provided by the Web Service. The choice of values may influence the price that the Service

• The "requested accuracy" expresses the range in which the application wishes to receive location information.

This may influence the choice of location technology to use (for instance, cell sector location may be suitable

for requests specifying 1 000 meters, but GPS technology may be required for requests below 100 meters).

• The "acceptable accuracy" expresses the range that the application considers useful, if the location cannot be

determined within this range, then the application would prefer not to receive the information. For instance, a

taxi tracking service to determine the closest taxi to a person may not be useful if the accuracy cannot be

provided within 1 000 meters to provide prompt service. This will also reduce customer satisfaction issues,

since results that are not useful can be handled appropriately for billing (e.g. Service Provider may choose not

The "maximum_age" expresses the maximum age of location information that the application considers useful. This can

be used by the service provider to supply cached location information rather than always to do a direct network location

The "response time" expresses the expected response time from an application point of view. If the network is unable to

respond within the desired time frame, the application would prefer not to have the information as it may no longer be

The "tolerance" expresses the priority of response time versus accuracy. If the application is delay tolerant the network

is expected to return a location with the requested accuracy even if this means not complying with the requested

response time. The application can also indicate that it is more important that the location information is returned within

the requested time even if this implies that the requested accuracy can not be fulfilled. An indication of "no delay"

implies that the application expects the service provider to return any current location estimate immediately.

In triggered notifications, a tracking accuracy is defined. This accuracy refers not to the accuracy for the area being

checked against, but rather for the accuracy of the technology used to track the terminal. For instance, a fine grained

tracking accuracy would be suitable for tracking the terminal entering a specific location, like a person arriving at a

destination building. A coarse grained tracking accuracy would be appropriate for determining when a person has

arrived at a city after a plane trip or a truck is in the vicinity of a warehouse.