1、 ATIS-0700003 UTDOA LBIS INTERFACE: REMOTE PDE PROTOCOL (RPP) METHOD TECHNICAL REPORT The Alliance for Telecommunication Industry Solutions (ATIS) is a technical planning and standards development organization that is committed to rapidly developing and promoting technical and operations standards f
2、or the communications and related information technologies industry worldwide using a pragmatic, flexible and open approach. Over 1,100 participants from more than 350 communications companies are active in ATIS 23 industry committees and its Incubator Solutions Program. NOTE - The users attention i
3、s called to the possibility that compliance with this standard may require use of an invention covered by patent rights. By publication of this standard, no position is taken with respect to the validity of this claim or any patent rights in connection therewith. The patent holder has, however, file
4、d a statement of willingness to grant license under these rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain such a license. Details may be obtained from the publisher. ATIS-0700003, UTDOA Lbis Interface: Remote PDE Protocol (RPP) Method Is an ATIS Stand
5、ard developed by the UTDOA Ad Hoc Committee under the ATIS Wireless Technologies and Systems Committee (WTSC). Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2006 by Alliance for Telecommunications Industry Solutions All ri
6、ghts reserved. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. ATIS-0700003 Tec
7、hnical Report on UTDOA LBIS INTERFACE: REMOTE PDE PROTOCOL (RPP) METHOD Secretariat Alliance for Telecommunications Industry Solutions Approved August, 2004 Abstract UTDOA (Uplink Time Difference of Arrival) is one of the location technologies supported by 3GPP GSM standards. The Lbis interface and
8、Remote PDE Protocol (RPP) enable upgrading earlier proprietary implementations of UTDOA to a 3GPP standards-based solution in a manner that minimizes impacts to the network infrastructure. This document is the second of a three-part set that together describe the Lbis interface in detail. This docum
9、ent is a Stage 3 description of Lbis RPP (Remote PDE Protocol) signaling between the SMLC (Serving Mobile Location Center) and the PDE (Positioning Determination Entity). The other two documents cover, separately, the functional architecture and the Stage 3 OAM protocol description. ATIS-0700003 FOR
10、EWORD The Alliance for Telecommunication Industry Solutions (ATIS) serves the public through improved understanding between carriers, customers, and manufacturers. The Wireless Technologies and Systems Committee (WTSC) formerly T1P1 - develops and recommends standards and technical reports related t
11、o wireless and/or mobile services and systems, including service descriptions and wireless technologies. WTSC develops and recommends positions on related subjects under consideration in other North American, regional and international standards bodies. This document is entitled UTDOA Lbis Interface
12、: Remote PDE Protocol (RPP). The method described in this report is intended for use in conjunction with standard 3GPP TS.22.071: Location Services (LCS)-Stage 1, 3GPP TS 23.271: Technical Specification Group Services and System Aspects; Functional stage 2 description of LCS, and 3GPP TS.48.071: Ser
13、ving Mobile Location Centre Base Station System (SMLC-BSS) interface. Footnotes are not officially part of this technical report. Future control of this document will reside with ATIS. This control of additions to the specification, such as protocol evolution, new applications, and operational requi
14、rements, will permit compatibility among U.S. networks. Such additions will be incorporated in an orderly manner with due consideration to the ITU-T layered model principles, conventions, and functional boundaries. Suggestions for improvement of this document are welcome. They should be sent to the
15、Alliance for Telecommunications Industry Solutions, WTSC Secretariat, 1200 G Street NW, Suite 500, Washington, DC 20005. Committee WTSC chartered the UTDOA Ad Hoc Committee to provide technical assistance in reviewing this report. ii ATIS-0700003 TABLE OF CONTENTS FOREWORD . II INTRODUCTION/EXECUTIV
16、E SUMMARY 1 1 SCOPE, PURPOSE, AND APPLICATION 1 1.1 SCOPE 1 1.2 PURPOSE 1 1.3 APPLICATION 1 2. NORMATIVE REFERENCES . 1 3. DEFINITIONS 2 4. ABBREVIATIONS, ACRONYMS, AND SYMBOLS. 2 5. NODE PROCEDURE. 3 5.1 SMLC/PDE FUNCTIONALITY WITH LBIS INTERFACE SUPPORTS 3 5.1.1 Physical Connection and Communicati
17、on Protocol 3 5.1.2 TCP Connection and Application Link Establishment on the Lbis 4 5.1.3 Application Level Handshake 5 5.1.4 RP Link Supervision Procedure 6 5.1.4.1 SMLC Procedure 6 5.1.4.2 PDE Procedure 8 5.1.5 Mapping of SMLCs to BSCs and PDEs. 8 5.1.6 Transaction Coordination Function for Lbis a
18、nd Lb 8 5.1.7 RPP Message Sending Rules. 9 5.1.8 Loss of RP Link Procedure 9 5.1.9 Exceptional Procedure on Lbis Transaction . 10 5.1.10 Transaction Error on the Lbis. 10 5.1.11 Badly Formed Message. 11 5.1.12 Messages Collision Scenarios. 13 5.1.13 RPP Message Synchronization Lost 13 5.1.14 Ending
19、of RPP Transaction. 14 6. INTERFACE DESCRIPTION 14 6.1 LB INTERFACE 14 6.2 LBIS INTERFACE . 14 6.2.1 RPP Positioning Message 15 6.2.1.1 RPP Perform Location Request Message (from SMLC to PDE). 15 6.2.1.2 RPP Perform Location Response Message (From PDE to SMLC) . 17 6.2.1.3 RPP Abort Message (from SM
20、LC to PDE) . 17 6.2.1.4 RPP RESET message (from SMLC to PDE) . 18 6.2.1.5 RPP PROTOCOL ERROR Message (from PDE to SMLC) 18 6.2.1.6 RPP TERMINATION Message (from SMLC to PDE) 18 6.2.2 RPP Control Message. 19 6.2.2.1 RPP APPLICATION CONTEXT Message . 19 6.2.2.2 RPP APPLICATION CONTEXT RESPONSE Message
21、 . 19 6.2.2.3 RPP CHECK ALIVE Message . 19 6.2.2.4 RPP CHECK ALIVE ACK Message. 19 6.2.3 Coding of Messages on RPP . 20 6.2.4 Coding of Information Element on RPP 21 6.2.4.1 Element Identifier. 21 6.2.4.2 Transaction_ID 22 6.2.4.3 Response Time 22 6.2.4.4 Application ID 22 6.2.4.5 Context Status 23
22、6.2.4.6 Transaction Error Cause . 23 iii ATIS-0700003 iv 6.2.4.7 User Information IE . 23 6.2.4.8 Cause IE. 24 6.2.4.9 Termination Cause IE 24 6.2.4.10 Generic Information IE 24 TABLE OF FIGURES FIGURE 1: LBIS APPLICATION LINK SETUP STATE DIAGRAM 5 FIGURE 2: APPLICATION LEVEL MESSAGE . 6 FIGURE 3: H
23、EARTBEAT CHECKS STATE DIAGRAM FOR THE SMLC. 7 FIGURE 4: HEARTBEAT MESSAGE BETWEEN SMLC AND PDE . 7 FIGURE 5: STATE DIAGRAM FOR THE PDE . 8 FIGURE 6: EXAMPLE OF A TRANSACTION COORDINATION FUNCTION IN SMLC 9 FIGURE 7: TRANSACTION ERROR WITH UNKNOWN TRANSACTION ID. 10 FIGURE 8: LBIS TRANSACTION CONFUSI
24、ON 11 FIGURE 9: LBIS TRANSACTION TIMEOUT DUE TO BADLY FORMED MESSAGE . 12 FIGURE 10: MESSAGE REJECTED BY PDE WITH RPP PROTOCOL ERROR MESSAGE 12 FIGURE 11: MESSAGES COLLISION SCENARIOS BETWEEN LB AND LBIS 13 FIGURE 12: ENDING RPP TRANSACTION WITHOUT PDE RETURNING A RESPONSE . 14 FIGURE 13: RPP POSITI
25、ONING MESSAGE . 15 FIGURE 14: RPP CONTROL MESSAGE 15 TABLE OF TABLES TABLE 1: ABBREVIATIONS AND ACRONYMS. 2 TABLE 2: NETWORK LAYERS SUPPORTING AN RP LINK . 4 TABLE 3: RPP PERFORM LOCATION REQUEST MESSAGE . 16 TABLE 4: RPP PERFORM LOCATION RESPONSE MESSAGE (FROM PDE TO SMLC). 17 TABLE 5: RPP ABORT ME
26、SSAGE . 17 TABLE 6: RPP RESET MESSAGE 18 TABLE 7: RPP PROTOCOL ERROR MESSAGE 18 TABLE 8: RPP TERMINATION MESSAGE . 18 TABLE 9: RPP APPLICATION CONTEXT MESSAGES 19 TABLE 10: RPP APPLICATION CONTEXT RESPONSE MESSAGES . 19 TABLE 11: RPP CHECK ALIVE MESSAGE. 19 TABLE 12: RPP CHECK ALIVE ACK MESSAGE . 19
27、 TABLE 13: CODING OF MESSAGES ON RPP 20 TABLE 14: CODING OF INFORMATION ELEMENT ON RPP 21 TABLE 15: TRANSACTION ID . 22 TABLE 16: RESPONSE TIME . 22 TABLE 17: APPLICATION ID 22 TABLE 18: CONTEXT STATUS 23 TABLE 19: TRANSACTION ERROR CAUSE . 23 TABLE 20: USER INFORMATION IE. 23 TABLE 21: CAUSE IE . 2
28、4 TABLE 22: TERMINATION CAUSE IE 24 TABLE 23: GENERIC INFORMATION IE . 24 TECHNICAL REPORT ATIS-0700003 Technical Report on UTDOA Lbis Interface: Remote PDE Protocol (RPP) Method 1 INTRODUCTION/EXECUTIVE SUMMARY The Lbis interface and Remote PDE Protocol (RPP) have been developed as an addition to 3
29、GPP specifications to enable upgrading earlier proprietary implementations of UTDOA to a 3GPP standards-based solution in a manner that minimizes impacts to the network infrastructure. This document is a Stage 3 description of Lbis RPP (Remote PDE Protocol) signaling between the SMLC (serving mobile
30、 location center) and the PDE (Positioning Determination Entity). A Stage 2 description is contained in the companion ATIS-0700003 “GSM UTDOA Lbis Interface: Architecture and Functional Description” document published separately. 1 SCOPE, PURPOSE, AND APPLICATION 1.1 Scope This document defines the
31、protocol requirements for the Lbis interface that supports the UTDOA positioning method for emergency calls. Because the Lbis interface is primarily an extension of the Lb interface to a remote PDE, the relevant Lb interface is also reviewed in detail. The node procedure associated with the transmis
32、sion and reception of UTDOA messages is also defined in this document. This document shall be used in conjunction with the UTDOA Architecture and Functional Description document. 1.2 Purpose This document provides details of the Lbis interface and the RPP protocol sufficient to permit implementation
33、 of the protocol in a GSM system. The document is a Technical Report, and not a Technical Specification, because details of the PDE implementation are not typically addressed as part of the 3GPP specifications. Note that the information specific to the Lb interface is informative only, since the Lb
34、interface parameters needed for UTDOA are now incorporated in 3GPP TS 48.071 v6.3.0. 1.3 Application The application of this open interface is typically to North American GSM networks using UTDOA in support of E911 Phase 2 emergency services. 2 NORMATIVE REFERENCES This technical report is not a sta
35、ndard, and contains no normative references of its own. All standards referred to in the report are subject to revision, and the parties to agreements based on this report are encouraged to investigate the possibility of applying the most recent edition of the standards and reports indicated below.
36、ATIS-0700003 2 ATIS-0700002 August 2004, UTDOA Lbis Interface: Architecture and Functional Description.1IETF RFC793, Transmission Control Protocol.23GPP TS 49.031v6.2.0 or latest: Base Station System Application Part; LCS Extension (BSS-LE).1 3GPP TS 48.071 v.6.4.0 or latest: Serving Mobile Location
37、 Center - Base Station System (SMLC-BSS) interface; Layer 3 specification.13GPP TS 43.059 v6.2.0 or latest: Functional stage 2 description of Location Services (LCS in GERAN).13GPP TS.22.071: Location Services (LCS)-Stage 1.13GPP TS.23.271: Technical Specification Group Services and System Aspects;
38、Functional stage 2 description of LCS.1 3. DEFINITIONS There are no new definitions being introduced as part of this report. 4. ABBREVIATIONS, ACRONYMS, AND SYMBOLS This clause provides project-specific terms and acronyms used in this document. Table 1: Abbreviations and Acronyms 3GPP Third Generati
39、on Partnership Project AMR Adaptive Multi-Rate BSC Base Station Controller BSSLAP BSS LCS Assistance Protocol BSSMAP-LE BSS Management Application Part LCS Extension CR Change Request IE Information Element IEI Information Element Identifier IP Internet Protocol Lb Interface between SMLC and BSC Lbi
40、s Interface between SMLC and PDE LCS Location Services MS Mobile Station PCF Position Calculation Function (The set of software, data, and algorithms that calculate the MS location.) PDE Position Determination Entity (The set of nodes, application software, and links that support location data colle
41、ction and the PCF.) 1This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. 2This document is available from the Internet Engineering Task Force (IETF). ATIS-0700003 3 QoS Quality of Service RP Remote PDE -
42、the low level data connection (physical and link) between an SMLC and a controller in the PDE. RPP Remote PDE Protocol - the high level data protocol (TCP/IP) between an SMLC and a controller in the PDE. SCCP Signaling Connection Control Part SMLC Serving Mobile Location Center T (IE format) Type TC
43、P Transmission Control Protocol TLV (IE format) Type, Length, and Value TS Technical Specification TV (IE format) Type and Value UTDOA Uplink Time Difference Of Arrival V (IE format) Value only 5. NODE PROCEDURE The general call flows, messages, and procedures for the BSC to support the UTDOA positi
44、oning procedure are described in ATIS-0700002. Because of the introduction of the new Lbis interface, the requirements of that interface on the SMLC and the PDE are described in the following subsections. 5.1 SMLC/PDE Functionality with Lbis Interface Supports In the definition of the SMLC under 3GP
45、P TS 43.059 v6.2.0, the implicit architecture has the SMLC performing two different functions. 1. The SMLC supports RAN-oriented, LCS administrative functions (e.g. process and responds to position requests from the Core and Radio Access Networks through the Lb interface). 2. The SMLC supports PDE-o
46、riented functions such as the PCF for certain positioning methods (e.g. returns the XY position Lat/Longfor an MS using Cell ID+Timing Advance). For some positioning technologies, such as UTDOA, the SMLC may not support the second function the PCF. For such technologies it may be necessary to employ
47、 a technology-specific PDE controller. The Lbis interface supports this Remote PDE through an interface between the SMLC and the PDE controller. Specified here for the UTDOA positioning technology, this interface could be applied to other remote PDEs and to other positioning methods. 5.1.1 Physical
48、Connection and Communication Protocol In the link described here, the Lbis interface employs TCP/IP protocol RFC793. Ethernet (IEEE 802.3) connectivity may be used. The Remote PDE Protocol (RPP) is defined as the communication protocol between the SMLC and the Remote PDE. RPP message content cipheri
49、ng is not required. The connection between an SMLC and a ATIS-0700003 4 Remote PDE is called an RP link. It is assumed that RP links are supported on a dedicated, private IP network suitable for production telecommunications traffic. A typical implementation is shown in Table 2, below. Table 2: Network Layers Supporting an RP Link Layer Supported by Application Layer Remote PDE Protocol Message Handler Sockets API Network and Transport Layers TCP/IP Interface Layers IEEE 802.3 (Ethernet) 5.1.2 TCP Connection a
