SIST ES 202 915-6 V1.2.1:2005

• Abstract:

  Edition PARLAY 4.0.

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.040.01 - Telecommunication systems in general
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Ref Project: ETSI ES 202 915-6 V1.2.1 (2003-08) - Open Service Access (OSA); Application Programming Interface (API); Part 6: Mobility SCF (Parlay 4)

SIST ES 202 915-6 V1.2.1:2005 is the Slovenian version of ETSI ES 202 915-6 V1.2.1. It specifies the Open Service Access (OSA) Application Programming Interface (API) for the Mobility Service Capability Feature (SCF) in Parlay 4, so application developers can use standardized network interfaces for user location and user status services.

What does SIST ES 202 915-6 V1.2.1:2005 specify?

SIST ES 202 915-6 V1.2.1:2005 specifies the Mobility SCF part of the OSA API Stage 3 specification. It defines how applications interact with network functions for location and status reporting, including the service interfaces, callback interfaces, data types, and the model used to describe behavior.

The document is organized from general API rules to specific mobility services. Clause 1 gives the scope, clause 2 lists references, clause 3 gives definitions and abbreviations, clause 4 explains the Mobility SCF structure, and clauses 5 to 12 cover sequence diagrams, class diagrams, interface specifications, state transitions, service properties, data definitions, and exception classes.

Annex	What it covers
Annex A	OMG IDL Description of Mobility SCF
Annex B	W3C WSDL Description of Mobility SCF
Annex C	Java API Description of the Mobility SCFs
Annex D	Contents of 3GPP OSA R5 Mobility
Annex E	Record of changes

What are the key requirements of SIST ES 202 915-6 V1.2.1:2005?

The central requirement is that an implementation that supports a method shall implement the behavior described for that method for at least one valid parameter set. In practice, this means a service cannot claim support for a method without actually providing a usable function path for real requests.

Service and callback behavior

SIST ES 202 915-6 V1.2.1:2005 uses a service interface on the network side and an application interface for callbacks. Clause 7 explains that asynchronous methods use Req, Res, and Err naming, and the application developer must implement the matching IpApp<name> interface to receive results, reports, and error callbacks. That matters because the service often returns later, not in the original call.

Clause 7 also defines the generic IpService interface. setCallback() binds the application callback interface, while setCallbackWithSessionID() does the same for a specific session. This is important for implementations that track a call or call leg through a session identifier.

User Location service

Clause 8.1 states that the User Location service (UL) supports geographical location and status of fixed, mobile, and IP based telephony users. A User Location SCF shall implement either IpUserLocation or IpTriggeredUserLocation as a minimum, and it shall provide one of the basic request paths such as interactive location, extended location, or periodic reporting.

IpUserLocation supports interactive and periodic location retrieval. IpAppUserLocation receives the location results or errors. In practice, this lets an application ask for a one-time location or subscribe to repeated reports.

IpTriggeredUserLocation adds location-change reporting based on trigger conditions. IpAppTriggeredUserLocation receives the triggered reports. That is useful when the application wants updates only when a user enters or leaves a defined area.

User Location Camel service

Clause 8.2 defines User Location Camel (ULC) for network-related location information rather than geographic coordinates. The service can return items such as VLR Number, Location Area Identification (LAI), and Cell Global Identification (CGI). A ULC implementation shall support IpUserLocationCamel, and it shall provide at least one of interactive, periodic, or triggered reporting.

This matters when the application needs mobile-network context, not only coordinates. The callback side uses IpAppUserLocationCamel to receive the reported network location data.

Emergency location handling

Clause 8.3 defines User Location Emergency (ULE) for emergency calls. A Mobility SCF shall implement IpUserLocationEmergency, with either direct emergency location requests or subscription to network-initiated emergency reports. The application receives the information through IpAppUserLocationEmergency.

This section is designed for cases where the network may identify the caller immediately or may first provide identifiers that can later be used to obtain the location. That is important for emergency service applications that must handle incomplete or delayed location information.

User Status service

Clause 8.4 defines the User Status service (US) for fixed, mobile, and IP-based telephony users. A User Status SCF shall implement IpUserStatus, with either interactive status requests or triggered status reporting. The callback interface IpAppUserStatus receives the results.

In practice, this supports applications that need to know whether a user is reachable, busy, or not reachable, and to subscribe to status changes over time.

Service properties and parameter limits

Clause 10 defines service properties that a specific service instance shall set, including permitted application types and subtypes, whether altitude can be obtained, supported location methods, supported priorities, and limits such as maximum interactive requests, maximum triggered users, maximum periodic users, and minimum periodic interval duration. This is the part an operator or integrator checks when deciding whether a deployment can support a given application workload.

Clause 11 defines the data structures that carry location, status, triggers, and emergency identifiers. These definitions matter because they fix how an implementation should package a request or response, including uncertainty shapes, trigger criteria, and whether fields such as altitude or timestamp are present.

What terms does SIST ES 202 915-6 V1.2.1:2005 define?

• Open Service Access (OSA) - An architecture that lets application developers use network functionality through standardized APIs.
• Service Capability Feature (SCF) - A service capability exposed through the API, such as Mobility, User Location, or User Status.
• User Location (UL) - The general service for obtaining geographical location and related status for users.
• User Location Camel (ULC) - The mobility service that returns network-related location information for mobile telephony users.
• User Location Emergency (ULE) - The specialized service for emergency-call location handling.
• User Status (US) - The service that reports whether a user is reachable, busy, or not reachable.
• Unified Modelling Language (UML) - The modeling notation used for the sequence diagrams, class diagrams, and state transition diagrams.
• Interface Definition Language (IDL) - The interface description format given in Annex A.

Who uses SIST ES 202 915-6 V1.2.1:2005?

Telecom application developers use this standard to build applications that request location or status data through OSA interfaces. Network platform and service developers use it to implement the service and callback interfaces, the data types, and the state behavior.

Operators and integrators use it when exposing mobility services to third-party or internal applications, especially for emergency handling, mobile-network location, and user status reporting. Test and quality teams use it to verify supported methods, callback behavior, parameter validation, and service properties.

What changed in SIST ES 202 915-6 V1.2.1:2005 from the previous edition?

Annex E records a large set of changes across the Parlay 4.0 and 4.1 versions. The most visible changes are the conversion of many request and callback return types from TpSessionID to TpAssignmentID, plus a change in TpMobilityStopAssignmentData so that the assignment identifier uses TpAssignmentID.

The change record also shows method-level updates such as removed exceptions for some User Location requests and revised exception handling for User Location Camel periodic reporting. It lists added, deprecated, modified, and removed items for interfaces, methods, data definitions, service properties, and exceptions.

Which standards are used with SIST ES 202 915-6 V1.2.1:2005?

SIST ES 202 915-6 V1.2.1:2005 uses ES 202 915-1 for the overview, definitions, and abbreviations, and ES 202 915-2 for the common data definitions shared across the OSA API family. Those two parts provide the foundation that this Mobility SCF part builds on.

The foreword also states that a subset of this document is in 3GPP TS 29.198-6 V5.2.0 (Release 5). Clause 10 and clause 11 additionally refer to TS 123 271 and TS 129 002 for specific location and identifier coding details used by some data items and service properties.

What does the SIST ES 202 915-6 V1.2.1:2005 document contain?

The body of the document contains sequence diagrams for interactive, periodic, and triggered location and status reporting, including emergency scenarios. It also contains class diagrams that show how service interfaces and application callback interfaces relate to each other.

Clause 7 and clause 8 give the interface signatures, method descriptions, callback patterns, and minimum implementation rules for UL, ULC, ULE, and US. Clause 9 provides state transition diagrams for User Location Camel and User Status, showing the active service states and the method calls that drive transitions.

Clause 10 defines service properties and includes an example property table for User Location services. Clause 11 gives the data structures for geographical position, trigger criteria, mobile identifiers, emergency requests, and user status, while clause 12 lists the exception classes used by the API.

Annex A gives the OMG IDL form, Annex B gives the WSDL form, and Annex C points to the Java API description. Annex E is a change record that helps implementers track how the interfaces and data definitions evolved between versions.

SLOVENSKI STANDARD
01-januar-2005
Odprti dostop do storitve (OSA) – Vmesnik za aplikacijsko programiranje (API) – 6.
del: Mobilnost SCF
Open Service Access (OSA); Application Programming Interface (API); Part 6: Mobility
SCF (Parlay 4)
Ta slovenski standard je istoveten z: ES 202 915-6 Version 1.2.1
ICS:
33.040.01 Telekomunikacijski sistemi Telecommunication systems
na splošno in general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI Standard
Open Service Access (OSA);
Application Programming Interface (API);
Part 6: Mobility SCF
(Parlay 4)
�
2 ETSI ES 202 915-6 V1.2.1 (2003-08)

Reference
RES/SPAN-120096-6
Keywords
API, IDL, OSA, UML
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
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
within ETSI Secretariat.
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
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
[e-mail]
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2003.
© The Parlay Group 2003.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI ES 202 915-6 V1.2.1 (2003-08)
Contents
Intellectual Property Rights.7
Foreword.7
1 Scope.8
2 References.8
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.8
4 Mobility SCF.9
4.1 General requirements on support of methods.9
5 Sequence Diagrams.10
5.1 User Location Sequence Diagrams.10
5.1.1 User Location Interrogation - Triggered Request .10
5.1.2 User Location Interrogation - Periodic Request.11
5.1.3 User Location Interrogation - Interactive Request.12
5.2 User Location Camel Sequence Diagrams .12
5.2.1 User Location Camel Interrogation - Triggered Request.12
5.2.2 User Location Camel Interrogation - Periodic Request .13
5.2.3 User Location Camel Interrogation - Interactive Request .14
5.3 User Location Emergency Sequence Diagrams .15
5.3.1 Subscription and Network Induced Location Reports .15
5.3.2 Network Induced Location Reports .16
5.3.3 Interactive Location Request .16
5.4 User Status Sequence Diagrams.16
5.4.1 Triggered Reporting.16
5.4.2 Interactive Request.17
6 Class Diagrams.18
6.1 User Location Class Diagrams .18
6.2 User Location Camel Class Diagrams.19
6.3 User Location Emergency Class Diagrams .19
6.4 User Status Class Diagrams.20
7 The Service Interface Specifications.20
7.1 Interface Specification Format .20
7.1.1 Interface Class.20
7.1.2 Method descriptions.20
7.1.3 Parameter descriptions.21
7.1.4 State Model.21
7.2 Base Interface.21
7.2.1 Interface Class IpInterface .21
7.3 Service Interfaces.21
7.3.1 Overview.21
7.4 Generic Service Interface .21
7.4.1 Interface Class IpService .21
7.4.1.1 Method setCallback().22
7.4.1.2 Method setCallbackWithSessionID().22
8 Mobility Interface Classes.22
8.1 User Location Interface Classes .22
8.1.1 Interface Class IpUserLocation.23
8.1.1.1 Method locationReportReq().23
8.1.1.2 Method extendedLocationReportReq().24
8.1.1.3 Method periodicLocationReportingStartReq().24
8.1.1.4 Method periodicLocationReportingStop().25
ETSI
4 ETSI ES 202 915-6 V1.2.1 (2003-08)
8.1.2 Interface Class IpAppUserLocation.25
8.1.2.1 Method locationReportRes().26
8.1.2.2 Method locationReportErr().26
8.1.2.3 Method extendedLocationReportRes().26
8.1.2.4 Method extendedLocationReportErr().26
8.1.2.5 Method periodicLocationReport().27
8.1.2.6 Method periodicLocationReportErr().27
8.1.3 Interface Class IpTriggeredUserLocation.27
8.1.3.1 Method triggeredLocationReportingStartReq().28
8.1.3.2 Method triggeredLocationReportingStop().28
8.1.4 Interface Class IpAppTriggeredUserLocation .29
8.1.4.1 Method triggeredLocationReport().29
8.1.4.2 Method triggeredLocationReportErr().29
8.2 User Location Camel Interface Classes.30
8.2.1 Interface Class IpUserLocationCamel .30
8.2.1.1 Method locationReportReq().30
8.2.1.2 Method periodicLocationReportingStartReq().31
8.2.1.3 Method periodicLocationReportingStop().31
8.2.1.4 Method triggeredLocationReportingStartReq().32
8.2.1.5 Method triggeredLocationReportingStop().32
8.2.2 Interface Class IpAppUserLocationCamel .32
8.2.2.1 Method locationReportRes().33
8.2.2.2 Method locationReportErr().33
8.2.2.3 Method periodicLocationReport().34
8.2.2.4 Method periodicLocationReportErr().34
8.2.2.5 Method triggeredLocationReport().34
8.2.2.6 Method triggeredLocationReportErr().34
8.3 User Location Emergency Interface Classes .35
8.3.1 Interface Class IpUserLocationEmergency .35
8.3.1.1 Method emergencyLocationReportReq().35
8.3.1.2 Method subscribeEmergencyLocationReports().36
8.3.1.3 Method unSubscribeEmergencyLocationReports().36
8.3.2 Interface Class IpAppUserLocationEmergency.37
8.3.2.1 Method emergencyLocationReport().37
8.3.2.2 Method emergencyLocationReportErr().37
8.4 User Status Interface Classes.38
8.4.1 Interface Class IpAppUserStatus .38
8.4.1.1 Method statusReportRes().38
8.4.1.2 Method statusReportErr().38
8.4.1.3 Method triggeredStatusReport().39
8.4.1.4 Method triggeredStatusReportErr().39
8.4.2 Interface Class IpUserStatus.39
8.4.2.1 Method statusReportReq().40
8.4.2.2 Method triggeredStatusReportingStartReq().40
8.4.2.3 Method triggeredStatusReportingStop().41
9 State Transition Diagrams.41
9.1 User Location.41
9.2 User Location Camel.41
9.2.1 State Transition Diagrams for IpUserLocationCamel.41
9.2.1.1 Active State.42
9.3 User Location Emergency .42
9.4 User Status.42
9.4.1 State Transition Diagrams for IpUserStatus .42
9.4.1.1 Active State.42
10 Service Properties.43
10.1 Mobility Properties.43
10.1.1 Emergency Application Subtypes.43
10.1.2 Value Added Application Subtypes.43
10.1.3 PLMN Operator Application Subtypes.43
10.1.4 Lawful Intercept Application Subtypes .44
ETSI
5 ETSI ES 202 915-6 V1.2.1 (2003-08)
10.1.5 Altitude Obtainable.44
10.1.6 Location Methods.44
10.1.7 Priorities.44
10.1.8 Max Interactive Requests.44
10.1.9 Max Triggered Users .44
10.1.10 Max Periodic Users.44
10.1.11 Min Periodic Interval Duration.45
10.2 User Location Service Properties .45
10.3 User Location Camel Service Properties.46
10.4 User Location Emergency Service Properties .46
10.5 User Status Service Properties.46
11 Data Definitions.46
11.1 Common Mobility Data Definitions.46
11.1.1 TpGeographicalPosition.46
11.1.2 TpLocationPriority.48
11.1.3 TpLocationRequest.48
11.1.4 TpLocationResponseIndicator.48
11.1.5 TpLocationResponseTime.49
11.1.6 TpLocationType.49
11.1.7 TpLocationUncertaintyShape.49
11.1.8 TpMobilityDiagnostic.50
11.1.9 TpMobilityError.50
11.1.10 TpMobilityStopAssignmentData.50
11.1.11 TpMobilityStopScope.51
11.1.12 TpTerminalType.51
11.2 User Location Data Definitions.51
11.2.1 IpUserLocation.51
11.2.2 IpUserLocationRef.51
11.2.3 IpAppUserLocation.51
11.2.4 IpAppUserLocationRef.51
11.2.5 IpTriggeredUserLocation.51
11.2.6 IpTriggeredUserLocationRef.51
11.2.7 IpAppTriggeredUserLocation.51
11.2.8 IpAppTriggeredUserLocationRef.52
11.2.9 TpUlExtendedData.52
11.2.10 TpUlExtendedDataSet.52
11.2.11 TpUserLocationExtended.52
11.2.12 TpUserLocationExtendedSet.52
11.2.13 TpLocationTrigger.52
11.2.14 TpLocationTriggerSet.53
11.2.15 TpLocationTriggerCriteria.53
11.2.16 TpUserLocation.53
11.2.17 TpUserLocationSet.53
11.3 User Location Camel Data Definitions .53
11.3.1 IpUserLocationCamel.53
11.3.2 IpUserLocationCamelRef.53
11.3.3 IpAppUserLocationCamel.53
11.3.4 IpAppUserLocationCamelRef.53
11.3.5 TpLocationCellIDOrLAI.53
11.3.6 TpLocationTriggerCamel.54
11.3.7 TpUserLocationCamel.54
11.3.8 TpUserLocationCamelSet.54
11.4 User Location Emergency Data Definitions.55
11.4.1 IpUserLocationEmergency.55
11.4.2 IpUserLocationEmergencyRef.55
11.4.3 IpAppUserLocationEmergency.55
11.4.4 IpAppUserLocationEmergencyRef.55
11.4.5 TpIMEI.55
11.4.6 TpNaESRD.55
11.4.7 TpNaESRK.55
11.4.8 TpUserLocationEmergencyRequest.55
ETSI
6 ETSI ES 202 915-6 V1.2.1 (2003-08)
11.4.9 TpUserLocationEmergency.56
11.4.10 TpUserLocationEmergencyTrigger.56
11.5 User Status Data Definitions .56
11.5.1 IpUserStatus.56
11.5.2 IpUserStatusRef.56
11.5.3 IpAppUserStatus.56
11.5.4 IpAppUserStatusRef.56
11.5.5 TpUserStatus.57
11.5.6 TpUserStatusSet.57
11.5.7 TpUserStatusIndicator.57
11.6 Units and Validations of Parameters .57
12 Exception Classes.58
Annex A (normative): OMG IDL Description of Mobility SCF .59
Annex B (informative): W3C WSDL Description of Mobility SCF.60
Annex C (informative): Java API Description of the Mobility SCFs .61
Annex D (informative): Contents of 3GPP OSA R5 Mobility .62
Annex E (informative): Record of changes .63
E.1 Interfaces.63
E.1.1 New.63
E.1.2 Deprecated.63
E.1.3 Removed.63
E.2 Methods.63
E.2.1 New.63
E.2.2 Deprecated.64
E.2.3 Modified.64
E.2.4 Removed.65
E.3 Data Definitions.65
E.3.1 New.65
E.3.2 Modified.65
E.3.3 Removed.65
E.4 Service Properties.66
E.4.1 New.66
E.4.2 Deprecated.66
E.4.3 Modified.66
E.4.4 Removed.66
E.5 Exceptions.66
E.5.1 New.66
E.5.2 Modified.67
E.5.3 Removed.67
E.6 Others.67
History .68

ETSI
7 ETSI ES 202 915-6 V1.2.1 (2003-08)
Intellectual Property Rights
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
server (http://webapp.etsi.org/IPR/home.asp).
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
server) which are, or may be, or may become, essential to the present document.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Services and Protocols for Advanced
Networks (SPAN).
The present document is part 6 of a multi-part deliverable covering Open Service Access (OSA); Application
Programming Interface (API), as identified below. The API specification (ES 202 915) is structured in the following
parts:
Part 1: "Overview";
Part 2: "Common Data Definitions";
Part 3: "Framework";
Part 4: "Call Control";
Part 5: "User Interaction SCF";
Part 6: "Mobility SCF";
Part 7: "Terminal Capabilities SCF";
Part 8: "Data Session Control SCF";
Part 9: "Generic Messaging SCF";
Part 10: "Connectivity Manager SCF";
Part 11: "Account Management SCF";
Part 12: "Charging SCF";
Part 13: "Policy management SCF";
Part 14: "Presence and Availability Management SCF".
The present document has been defined jointly between ETSI, The Parlay Group (http://www.parlay.org) and the 3GPP,
in co-operation with a number of JAIN™ Community (http://www.java.sun.com/products/jain) member companies.
The present document forms part of the Parlay 4.1 set of specifications.
A subset of the present document is in 3GPP TS 29.198-6 V5.2.0 (Release 5).
ETSI
8 ETSI ES 202 915-6 V1.2.1 (2003-08)
1 Scope
The present document is part 6 of the Stage 3 specification for an Application Programming Interface (API) for Open
Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality
through an open standardised interface, i.e. the OSA APIs.
The present document specifies the Mobility Service Capability Feature (SCF) aspects of the interface. All aspects of
the Mobility SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data Definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the
Unified Modelling Language (UML).
2 References
The references listed in clause 2 of ES 202 915-1 contain provisions which, through reference in this text, constitute
provisions of the present document.
ETSI ES 202 915-1: "Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview
(Parlay 4)".
ETSI ES 202 915-2: "Open Service Access (OSA); Application Programming Interface (API); Part 2: Common Data
Definitions (Parlay 4)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 202 915-1 apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations defined in ES 202 915-1 apply.
ETSI
9 ETSI ES 202 915-6 V1.2.1 (2003-08)
4 Mobility SCF
The following clauses describe each aspect of the Mobility Service Capability Feature (SCF).
The order is as follows:
• The Sequence diagrams give the reader a practical idea of how each of the SCFs is implemented.
• The Class relationships clause show how each of the interfaces applicable to the SCF, relate to one another.
• The Interface specification clause describes in detail each of the interfaces shown within the Class diagram
part.
• The State Transition Diagrams (STD) show the transition between states in the SCF. The states and transitions
are well-defined; either methods specified in the Interface specification or events occurring in the underlying
networks cause state transitions.
• The Data Definitions clause show a detailed expansion of each of the data types associated with the methods
within the classes. Note that some data types are used in other methods and classes and are therefore defined
within the Common Data types part ES 202 915-2.
4.1 General requirements on support of methods
An implementation of this API which supports or implements a method described in the present document, shall
support or implement the functionality described for that method, for at least one valid set of values for the parameters
of that method.
Where a method is not supported by an implementation of a Service interface, the exception
P_METHOD_NOT_SUPPORTED shall be returned to any call of that method.
Where a method is not supported by an implementation of an Application interface, a call to that method shall be
possible, and no exception shall be returned.
ETSI
10 ETSI ES 202 915-6 V1.2.1 (2003-08)
5 Sequence Diagrams
5.1 User Location Sequence Diagrams
5.1.1 User Location Interrogation - Triggered Request
The following sequence diagram shows how an application requests triggered location reports from the User Location
service. When users location changes, the service reports this to the application.
: IpAppTriggeredUserLocation : IpTriggeredUserLocation
1: triggeredLocationReportingStartReq(  )
2: triggeredLocationReport(  )
3: triggeredLocationReport(  )
New reports are sent until the
triggered reporting is stopped
4: triggeredLocationReportingStop( )

1: This message is used to start triggered location reporting for one or several users.
2: When the trigger condition is fulfilled then this message passes the location of the affected user to its callback
object.
3: This is repeated until the application stops triggered location reporting (see next message).
4: This message is used to stop triggered location reporting.
ETSI
11 ETSI ES 202 915-6 V1.2.1 (2003-08)
5.1.2 User Location Interrogation - Periodic Request
The following sequence diagram shows how an application requests periodic location reports from the User Location
service.
: IpAppUserLocation : IpUserLocation
1: periodicLocationReportingStartReq(  )
2: periodicLocationReport( )
3: periodicLocationReport( )
New reports are s ent until the
periodic reporting is stopped
4: periodicLocationReportingStop( )

1: This message is used to start periodic location reporting for one or several users.
2: This message passes the location of one or several users to its callback object.
3: This message passes the location of one or several users to its callback object.
This is repeated at regular intervals until the application stops periodic location reporting (see next message).
4: This message is used to stop periodic location reporting.
ETSI
12 ETSI ES 202 915-6 V1.2.1 (2003-08)
5.1.3 User Location Interrogation - Interactive Request
The following sequence diagram shows how an application requests a location report from the User Location service.
: IpAppUserLocation : IpUserLocation
1: locationReportReq( )
2: locationReportRes( )
1: This message is used to request the location of one or several users.
2: This message passes the result of the location request for one or several users to its callback object.
5.2 User Location Camel Sequence Diagrams
5.2.1 User Location Camel Interrogation - Triggered Request
The following sequence diagram shows how an application requests trigg
...