tech-invite   World Map
3GPP     Specs     Glossaries     UICC       IETF     RFCs     Groups     SIP     ABNFs       T+       Search     Home
Top        in Index        Prev        Next

TS 29.198-06 (CT)
Open Service Access (OSA) API
Part 6: Mobility Service Capability Feature

|   ToC   |   3GPP‑Page   |   ETSI‑search   |   Help   |

(P) V9.0.0    2009/12    87 p.
(P) V8.0.0    2008/06    87 p.
(P) V7.0.0    2007/03    78 p.
(P) V6.6.1    2006/07    77 p.
(P) V5.8.0    2005/12    63 p.
(P) V4.6.0    2005/12    67 p.


Rapporteur:  Mr. Unmehopa, Musa
See also:  TS 29.198    


The User Location service (UL) provides a general geographic location service. UL has functionality to allow applications to obtain the geographical location and the status of fixed, mobile and IP based telephony users.

UL is supplemented by User Location Camel service (ULC) to provide information about network related information. There is also some specialised functionality to handle emergency calls in the User Location Emergency service (ULE).

The UL service provides the IpUserLocation and IpTriggeredUserLocation interfaces. Most methods are asynchronous, in that they do not lock a thread into waiting whilst a transaction performs. In this way, the client machine can handle many more calls, than one that uses synchronous message calls. To handle responses and reports, the developer must implement IpAppUserLocation and IpAppTriggeredUserLocation interfaces to provide the callback mechanism.

When periodic or triggered location reporting is used, errors may be reported either when the recurrent reporting is requested, as an error per user in reports or in the corresponding err-method when the error concerns all subscribers in an assignment.

The ULC provides location information, based on network-related information, rather than the geographical coordinates that can be retrieved via the general User Location Service. Using the ULC functions, an application programmer can request the VLR Number, the location Area Identification and the Cell Global Identification and other mobile-telephony-specific location information.

The ULC provides the IpUserLocationCamel interface. Most methods are asynchronous, in that they do not lock a thread into waiting whilst a transaction performs. In this way, the client machine can handle many more calls, than one that uses synchronous message calls. To handle responses and reports, the developer must implement IpAppUserLocationCamel interface to provide the callback mechanism.

In the case of an emergency call, the network may locate the caller automatically. The resulting location is sent directly to an application that is dedicated to handle emergency user location. If the dedicated emergency call application is using the API, the location is sent to the application using a callback method in the IpAppUserLocationEmergency interface.

However, the network does not always send the location immediately (probably when the location procedure is not finished when the call is set up). In this case the network will send an identifier of the caller that can be used to locate the caller using the interface IpUserLocationEmergency.


 

Here        Top        None        None        Next
part:    1     2     3

 

 

1   Scope   PDF-p. 10
2   References
3   Definitions and abbreviations   PDF-p. 11
4   Mobility SCF
5   Sequence Diagrams
6   Class Diagrams   PDF-p. 22
7   The Service Interface Specifications   PDF-p. 27

Up        Top        ToC