ETSI 3GPP TS 25 453-2003 See TS 125 453 V5 6 0 (Version 5 6 0 Release 5).pdf

《ETSI 3GPP TS 25 453-2003 See TS 125 453 V5 6 0 (Version 5 6 0 Release 5).pdf》由会员分享，可在线阅读，更多相关《ETSI 3GPP TS 25 453-2003 See TS 125 453 V5 6 0 (Version 5 6 0 Release 5).pdf（85页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 125 453 V5.6.0 (2003-06)Technical Specification Universal Mobile Telecommunications System (UMTS);UTRAN Iupc interface Positioning CalculationApplication Part (PCAP) signalling(3GPP TS 25.453 version 5.6.0 Release 5)ETSI ETSI TS 125 453 V5.6.0 (2003-06) 1 3GPP TS 25.453 version 5.6.0 Releas

2、e 5 Reference RTS/TSGR-0325453v560 Keywords UMTS 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 notic

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

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

5、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: editoretsi.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright a

6、nd the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2003. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being r

7、egistered 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 125 453 V5.6.0 (2003-06) 2 3GPP TS 25.453 version 5.6.0 Release 5 Intellectual Property Rights IPRs essential or potentiall

8、y 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

9、 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 guarant

10、ee 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 been produced by ETSI 3rd Generation Partnership Project

11、(3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be

12、 found under http:/webapp.etsi.org/key/queryform.asp . ETSI ETSI TS 125 453 V5.6.0 (2003-06) 3 3GPP TS 25.453 version 5.6.0 Release 5 Contents Intellectual Property Rights2 Foreword.2 Foreword.6 1 Scope 7 2 References 7 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .8 4 Genera

13、l .9 4.1 Procedure Specification Principles.9 4.2 Forwards and Backwards Compatibility 9 4.3 Specification Notations 9 5 PCAP Services .10 6 Services Expected from Signalling Transport10 7 Functions of PCAP.10 8 PCAP Procedures .10 8.1 Elementary Procedures.10 8.2 Position Calculation .11 8.2.1 Gene

14、ral11 8.2.2 Successful Operation 11 8.2.3 Unsuccessful Operation 12 8.2.4 Abnormal Conditions12 8.3 Information Exchange Initiation.12 8.3.1 General12 8.3.2 Successful Operation 13 8.3.3 Unsuccessful Operation 15 8.3.4 Abnormal Conditions15 8.4 Information Reporting15 8.4.1 General15 8.4.2 Successfu

15、l Operation 16 8.4.3 Abnormal Conditions16 8.5 Information Exchange Termination .16 8.5.1 General16 8.5.2 Successful Operation 16 8.5.3 Abnormal Conditions17 8.6 Information Exchange Failure17 8.6.1 General17 8.6.2 Successful Operation 17 8.7 Error Indication 17 8.7.1 General17 8.7.2 Successful Oper

16、ation 18 8.7.3 Abnormal Conditions18 9 Elements for PCAP Communication18 9.1 Message Functional Definition and Content 18 9.1.1 General18 9.1.2 Message Contents .19 9.1.2.1 Presence 19 9.1.2.2 Criticality 19 9.1.2.3 Range 19 9.1.2.4 Assigned Criticality.19 ETSI ETSI TS 125 453 V5.6.0 (2003-06) 4 3GP

17、P TS 25.453 version 5.6.0 Release 5 9.1.3 Position Calculation Request 19 9.1.4 Position Calculation Response20 9.1.5 POSITION CALCULATION FAILURE .20 9.1.6 Information Exchange Initiation Request .20 9.1.7 Information Exchange Initiation Response.21 9.1.8 Information Exchange Initiation Failure.21

18、9.1.9 Information Report .21 9.1.10 Information Exchange Termination Request 21 9.1.11 Information Exchange Failure Indication .22 9.1.12 Error Indication.22 9.2 Information Element Functional Definitions and Contents22 9.2.1 General22 9.2.2 Radio Network Layer Related IEs 22 9.2.2.1 Almanac and Sat

19、ellite Health SIB.22 9.2.2.2 Altitude and direction23 9.2.2.3 Cause.23 9.2.2.4 Criticality Diagnostics.24 9.2.2.5 DGPS Corrections.26 9.2.2.6 Geographical Area 27 9.2.2.7 Geographical Coordinates.29 9.2.2.8 GPS Acquisition Assistance29 9.2.2.9 GPS Almanac and Satellite Health30 9.2.2.10 GPS Clock an

20、d Ephemeris Parameters .31 9.2.2.11 GPS Ionospheric Model 33 9.2.2.12 GPS Measured Results34 9.2.2.13 GPS Navigation Model .35 9.2.2.14 GPS Real Time Integrity.36 9.2.2.15 GPS Reference Time.36 9.2.2.16 GPS Transmission TOW.37 9.2.2.17 GPS UTC Model.37 9.2.2.18 GPS-UTRAN Time Relationship Uncertaint

21、y 37 9.2.2.19 Information Exchange ID37 9.2.2.20 Information Exchange Object Type 37 9.2.2.21 Information Report Characteristics .38 9.2.2.22 Information Type 39 9.2.2.23 Message Structure .40 9.2.2.24 Message Type .41 9.2.2.25 Method Type.41 9.2.2.26 Requested Data Value .41 9.2.2.27 Requested Data

22、 Value Information .42 9.2.2.28 Transaction ID.42 9.2.2.29 Transmission TOW Indicator42 9.2.2.30 Uncertainty Ellipse43 9.3 Message and Information Element Abstract Syntax (with ASN.1)43 9.3.0 General43 9.3.1 Usage of private message mechanism for non-standard use.43 9.3.2 Elementary Procedure Defini

23、tions44 9.3.3 PDU Definitions .46 9.3.4 Information Element Definitions 52 9.3.5 Common Definitions.63 9.3.6 Constant Definitions .64 9.3.7 Container Definitions65 9.4 Message Transfer Syntax .67 10 Handling of Unknown, Unforeseen and Erroneous Protocol Data 67 10.1 General .67 10.2 Transfer Syntax

24、Error.68 10.3 Abstract Syntax Error.68 10.3.1 General68 10.3.2 Criticality Information 69 10.3.3 Presence Information 69 10.3.4 Not comprehended IE/IE group70 ETSI ETSI TS 125 453 V5.6.0 (2003-06) 5 3GPP TS 25.453 version 5.6.0 Release 5 10.3.4.1 Procedure Code.70 10.3.4.1A Type of Message .70 10.3.

25、4.2 IEs other than the Procedure Code and Type of Message.70 10.3.5 Missing IE or IE group .71 10.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present 72 10.4 Logical Error 72 10.5 Exceptions 73 Annex A (informative): Guidelines for Usage of the Criticalit

26、y Diagnostics IE.74 A.1 EXAMPLE MESSAGE Layout .74 A.2 Example on a Received EXAMPLE MESSAGE.74 A.3 Content of Criticality Diagnostics76 A.3.1 Example 1.76 A.3.2 Example 2.77 A.3.3 Example 3.78 A.3.4 Example 4.79 A.3.5 Example 5.80 A.4 ASN.1 of EXAMPLE MESSAGE .81 Annex B (informative): Change histo

27、ry .83 History 84 ETSI ETSI TS 125 453 V5.6.0 (2003-06) 6 3GPP TS 25.453 version 5.6.0 Release 5 Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change

28、following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presente

29、d to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the

30、 document. ETSI ETSI TS 125 453 V5.6.0 (2003-06) 7 3GPP TS 25.453 version 5.6.0 Release 5 1 Scope The present document specifies the Positioning Calculation Application Part (PCAP) between the Radio Network Controller (RNC) and the Stand-alone A-GPS SMLC (SAS). It fulfills the RNC-SAS communication

31、requirements specified in 6 and thus defines the Iupc interface and its associated signaling procedures. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of

32、 publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly re

33、fers to the latest version of that document in the same Release as the present document. 1 3GPP TS 25.450: “UTRAN Iupc interface general aspects and principles“. 2 3GPP TS 25.451: “UTRAN Iupc interface layer 1“. 3 3GPP TS 25.452: “UTRAN Iupc interface signalling transport“. 4 3GPP TS 25.331: “Radio

34、Resource Control (RRC) Protocol Specification“. 5 3GPP TS 25.401: “UTRAN Overall Description“. 6 3GPP TS 25.305: “Stage 2 functional specification of UE positioning in UTRAN“. 7 ITU-T Recommendation X.680 (12/97): “Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic

35、 notation“. 8 ITU-T Recommendation X.681 (12/97): “Information technology - Abstract Syntax Notation One (ASN.1): Information object specification“. 9 ITU-T Recommendation X.691 (12/97): “Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)“. 10 ICD-GPS-200: (1

36、2 April 2000) “Navstar GPS Space Segment/Navigation User Interface“. 11 3GPP TS 23.032: “Universal Geographical Area Description (GAD)“. 12 3GPP TR 25.921: “Guidelines and principles for protocol description and error handling“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the

37、 present document, the following terms and definitions apply: Standalone A-GPS SMLC (SAS): logical node that interconnects to the RNC over the Iupc interface via the PCAP protocol An SAS performs the following procedures: - provide GPS related data to the RNC; ETSI ETSI TS 125 453 V5.6.0 (2003-06) 8

38、 3GPP TS 25.453 version 5.6.0 Release 5 - performs the position calculation function for UE assisted GPS. Elementary Procedure: PCAP consists of Elementary Procedures (EPs) An Elementary Procedure is a unit of interaction between the RNC and the SAS. An EP consists of an initiating message and possi

39、bly a response message. Two kinds of EPs are used: - Class 1: Elementary Procedures with response (success or failure). - Class 2: Elementary Procedures without response. For Class 1 EPs, the types of responses can be as follows: Successful: - A signalling message explicitly indicates that the eleme

40、ntary procedure successfully completed with the receipt of the response. Unsuccessful: - A signalling message explicitly indicates that the EP failed. Class 2 EPs are considered always successful. Information Exchange Context: Information Exchange Context is created by the first Information Exchange

41、 Initiation Procedure initiated by the RNC and requested from the SAS The Information Exchange Context is deleted by the Information Exchange Termination or the Information Exchange Failure procedure when there is no more Information Exchange to be provided by the RNC to the SAS. The Information Exc

42、hange Context is identified by an SCCP connection as, for Information Exchanges, only the connection oriented mode of the signalling bearer is used. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: A-GPS Assisted GPS ASN.1 Abstract Syntax Notation One CN

43、 Core Network CRNC Controlling RNC DGPS Differential GPS EP Elementary Procedure GPS Global Positioning System MSC Mobile services Switching Center PCAP Positioning Calculation Application Part PRC Pseudorange CorrectionRNC Radio Network Controller RNS Radio Network Subsystem RRC Radio Resource Cont

44、rol SAS Standalone A-GPS SMLC SCCP Signalling Connection Control Part SIB System Information Block SMLC Serving Mobile Location Center SRNC Serving RNC SRNS Serving RNS TOW Time of Week UE User Equipment UTRAN Universal Terrestrial Radio Access Network ETSI ETSI TS 125 453 V5.6.0 (2003-06) 9 3GPP TS

45、 25.453 version 5.6.0 Release 5 4 General 4.1 Procedure Specification Principles The principle for specifying the procedure logic is to specify the functional behaviour of the SAS exactly and completely. The RNC functional behaviour is left unspecified. The following specification principles have be

46、en applied for the procedure text in clause 8: - The procedure text discriminates between: 1) Functionality which “shall“ be executed: - The procedure text indicates that the receiving node “shall“ perform a certain function Y under a certain condition. If the receiving node supports procedure X but

47、 cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value. 2) Functionality which “shall, if supported“ be executed: - The procedure

48、 text indicates that the receiving node “shall, if supported,“ perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting no

49、de about the not supported functionality. - Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. 4.2 Forwards and Backwards Compatibility The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and IEs or groups of related IEs, include Id and criticality fields that are coded in