ETSI TS 102 164-2006 Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) Emergency Location Protocols (V1 3 1 OMA-TS-MLP-V3 2-20051124_1.pdf

1、 ETSI TS 102 164 V1.3.1 (2006-09)Technical Specification Telecommunications and Internet converged Services andProtocols for Advanced Networking (TISPAN);Emergency Location ProtocolsOMA-TS-MLP-V3_2-20051124-CETSI ETSI TS 102 164 V1.3.1 (2006-09) 2 Reference RTS/TISPAN-03071-EMTEL Keywords Emergency,

2、 location, mobile, protocol, endorsement ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Indivi

3、dual 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

4、 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 curr

5、ent 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, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduc

6、ed except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2006. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members.

7、 TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 102 164 V1.3.1 (2006-09) 3 Contents Intellectual Property Rig

8、hts4 Foreword.4 1 Scope 6 2 References 6 3 Definitions and abbreviations.6 3.1 Definitions6 3.2 Abbreviations .7 4 Name and address data.7 Endorsement notice 7 Global modifications to OMA TS-MLP-V3-2-20051124-C 7 Annex ZA (informative): Example messages12 ZA.1 Emergency location immediate request12

9、ZA.2 Emergency location immediate answer - valid response12 ZA.3 Emergency location immediate answer - error response13 ZA.4 Example usage Emergency Location Report .14 ZA.5 Example usage of MLP extension14 Annex ZB (informative): Bibliography.16 History 17 ETSI ETSI TS 102 164 V1.3.1 (2006-09) 4 In

10、tellectual 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 R

11、ights (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

12、 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 Technical Specification (TS) has be

13、en produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document: Identifies the clauses of the OMA-TS-MLP-V3_2 1 that are applicable to the emergency location information services. Does not identify how t

14、he mobile network operator determines location. Does not identify how the location information is passed between the emergency operator and the appropriate emergency authority. Does not describe how the emergency call is established. Figure 1 shows diagrammatically the scope of the present document.

15、 Mobile NetworkLocationServerPSTN999 / 112 callPSAPEmergencyControl CentrePSAP ECCScope of the present documentCall pathLocation information pathNote: the PSAP and Emergency Control Centre may be co-locatedFigure 1: Scope of the present document Please see OMA-TS-MLP-V3_2 Specification 1 full OMA ML

16、P specification at http:/www.openmobilealliance.org/release_program/index.html for further details and information. ETSI ETSI TS 102 164 V1.3.1 (2006-09) 5 Note that in this implementation of the OMA MLP protocol: ALL compulsory OMA elements are compulsory. Some optional OMA elements are compulsory.

17、 ETSI ETSI TS 102 164 V1.3.1 (2006-09) 6 1 Scope The present document specifies the protocol that is used by the local emergency operator to obtain the location information that is registered on the operator location server, see figure 1. It endorses and defines a profile of the OMA specification OM

18、A-TS-MLP-V3_2-20051124-C 1 that are applicable to the emergency location information services. NOTE: The LI Forum has been affiliated and its work subsumed into the OMA; the LIF TS 101 Specification has been succeeded by OMA-TS-MLP-V3_2. 2 References The following documents contain provisions which,

19、 through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the l

20、atest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity

21、. 1 OMA TS-MLP-V3-2-20051124-C: “Mobile Location Protocol 3.2“. NOTE: Available at http:/www.openmobilealliance.org/release_program/index.html 2 EPSG Geodesy Parameters: “EPSG Geodetic Parameter Data Set Version 6.3“. NOTE: Available at http:/www.epsg.org/. 3 NICC Specification ND1013:2002/11: “Emer

22、gency Location Information Interface“. NOTE: Available at: http:/www.nicc.org.uk/. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: emergency location immediate service: service used for querying of the location of a

23、 mobile subscriber that has initiated an emergency call NOTE: The response to this service is required immediately (within a set time). emergency location reporting service: service that is used when the wireless network automatically initiates the positioning at an emergency call NOTE: The position

24、 and related data is then sent to the emergency application from the location server. Which application and its address are defined in the location server. local emergency operator: designated emergency operator that can use the a Mobile Location Protocol operated by a location-based application to

25、request MS location information from an operator location server ETSI ETSI TS 102 164 V1.3.1 (2006-09) 7 operator location server: location server with in the PLMN that, in the event of an emergency situation, a designated emergency operator can use the a Mobile Location Protocol (MLP) to request MS

26、 location information from. NOTE: An Operator Location Server may be a GMLC/MPC or other entity in the wireless network. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: EPSG European Petroleum Survey Group FFS For Further Study ISO International Standar

27、ds Organization LCS Location Service LIF Location Interoperability Forum MLP Mobile Location Protocol MS Mobile Station MSISDN Mobile Subscriber ISDN OMA Open Mobile Alliance 4 Name and address data The OMA MLP 1 standard does not include name and address type fields but does include an extension me

28、chanism to allow additional elements to be added. A name and address extension is included in this specification to enable fixed line operators to adopt the same protocol as mobile operators to provide location information to emergency services: Potential data sources to populate these fields includ

29、e: - installation address for fixed lines phones; - addresses “reverse geocoded“ from latitude, longitude position of mobile handset; - location of pico cells within buildings. Note that the referenced extension (and therefore the structure and elements within this extension) could be different for

30、different countries, different operators and different emergency services. EXAMPLE: If required the name and address fields and field formats could be defined differently to suit different countries, different operators or different emergency services. NOTE: Liaison to include name and address data

31、into OMA MLP was sent to OMA by TISPAN Plenary #10. Endorsement notice The present document endorses OMA TS-MLP-V3-2-20051124-C, the contents of which apply together with the addition of the modifications being covered herein. Global modifications to OMA TS-MLP-V3-2-20051124-C The present document i

32、s a profile of MLP and is based on the interface defined by the OMA. The following table identifies clauses within the OMA specification, and clarifies which options are applicable to a emergency location information service. The present document identifies the minimum requirement. Elements not expl

33、icitly mentioned in this clause should be considered to be “Not required“. Additional optional elements may be implemented on a bilateral basis. ETSI ETSI TS 102 164 V1.3.1 (2006-09) 8 NOTE: In the following table, the term: “is required to be supported“ is equivalent to “shall contain“. However, it

34、 is understood that the definition of “is required to be supported“ provides more clarity and detail than the definition of “shall contain“ as the definition is captured from clause 0.7.2 of the NICC Specification ND1013:2002/11. Endorsed Profiles Reference OMA MLP 1 section Remarks MLP structure 5.

35、1.1 MLP extension mechanism 5.1.2 Transport Protocol Layer Definitions 5.2.1 See also HTTP mapping endorsement (5.6). Identity Element Definitions 5.2.2.1 The following elements are required to be supported, and where an element is a construction, which elements are required to be supported within t

36、he construction: msid msids o msid+ One msid element shall be included in an msids element) Location Element Definitions 5.2.2.3 The following elements are required to be supported, and where an element is a construction, which elements are required to be supported within the construction: eme_pos o

37、 msid o pd o poserr pd o time o shape o lev_conf poserr o result o time time lev_conf Shape Element Definitions 5.2.2.5 All shapes defined by 1 shall be supported. Depending from national regulation the type of shapes nationally required can be restricted. Context Element Definitions 5.2.2.8 The fol

38、lowing elements are required to be supported, and where an element is a construction, which elements are required to be supported within the construction: Client o Id o Pwd o Requestmode Id Pwd Requestmode servicetype Header DTD 5.2.3.1 The following elements are required to be supported, and where

39、an element is a construction, which elements are required to be supported within the construction: hdr o client Emergency Location Immediate Service 5.2.3.3 Required Emergency Location Immediate Request DTD 5.2.3.3.1 The “eme_lir“ shall contain the following element: msids Emergency Location Immedia

40、te Answer DTD 5.2.3.3.2 The “eme_lia“ shall contain the following elements: eme_pos+ caller_location (optional) ed: not specified by 1 or result Emergency Location Reporting Service 5.2.3.5 Required Emergency Location Report DTD 5.2.3.5.1 The “emerep“ shall contain the following elements: eme_event

41、eme_pos caller_location (optional) ed: not specified by 1 ETSI ETSI TS 102 164 V1.3.1 (2006-09) 9 Endorsed Profiles Reference OMA MLP 1 section Remarks General Error Message Definition 5.2.3.7 The “gem“ shall contain the following elements: result angle 5.3.5 Required angularUnit 5.3.6 RequireEllipt

42、icalArea 5.3.20 Required eme_event 5.3.21 Requireeme_trigger 5.3.21.1 Required eme_pos 5.3.22 Requireid 5.3.26 Requirelev_conf 5.3.32 Required msid 5.3.42 RequireType 5.3.42.1 Type shall be “MSISDN“ enc 5.3.42.2 Enc shall be “ASC“ pwd 5.3.58 Required result 5.3.65 RequiresemiMajor 5.3.66 Required se

43、miMinor 5.3.67 Requirerequestmode 5.3.69 Required type 5.3.69.1 Type shall be “PASSIVE“ time 5.3.78 Required X 5.3.85 RequireY 5.3.86 Requirever 5.3.88.2 Required Result codes 5.4.1 Required HTTP mapping 5.6 The lif-mlp-s (9211/tcp) port or the lif-mlp (9210/tcp) port shall be used. Location client

44、shall use separate HTTP posts and NOT use pipelining for time critical requests to avoid that one request delays other requests. Location Server shall process and respond to the separate HTTP posts out of order. Service Initiation DTD 5.6.2.1 The “svc_init“ shall contain the following elements: hdr

45、eme_lir Service Result DTD 9.2.2 The “svc“_result shall contain the following elements: eme_lia emerep Result codes This table defines the result codes that indicate the result of the request or individual positioning. The codes are divided in ranges: 0 to 99 Location server specific errors 100 to 1

46、99 Request specific errors 200 to 299 Network specific errors 300 to 499 Reserved for future use 500 to 599 Vendor specific errors 600 to 699 MLS Client specific errors NOTE: For privacy reasons it might be needed to not report certain specific errors. In this case it is up to the implementation or

47、configuration of the location server which errors will be reported. For the detailed codes chapter 5.4 of OMA MLP V3.2 1 is referred. ETSI ETSI TS 102 164 V1.3.1 (2006-09) 10“Add the following clause:“ 5.1.3.1 MLP extension This clause details an optional MLP extension. This provides a simple mechan

48、ism to transport name information, as described in 1. Furthermore it can be used to handle a freeform textual description of location, see 3. Support of this extension is not mandatory. NOTE: Liaison to include name and address data into OMA MLP was sent to OMA by TISPAN Plenary #10. 5.1.3.1.1 Data

49、type definition Elements and attributes Customer_name Description: Specifies the name of the customer associated with the geographic info Format: Char String Defined values: - Default value: - Example: Mr Benn Address_line Description: Specifies a line of text providing a freeform textual description of the associated location information Format: Char String Defined values: - Default value: - Example 1: 52 Festive Road Example 2: Heathrow Terminal 4 Check In Desks NOTE: No formatti