ETSI TS 129 108-2016 Universal Mobile Telecommunications System (UMTS) LTE Application of the Radio Access Network Application Part (RANAP) on the E-interface (V13 0 0 3GPP TS 29 1.pdf

《ETSI TS 129 108-2016 Universal Mobile Telecommunications System (UMTS) LTE Application of the Radio Access Network Application Part (RANAP) on the E-interface (V13 0 0 3GPP TS 29 1.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 129 108-2016 Universal Mobile Telecommunications System (UMTS) LTE Application of the Radio Access Network Application Part (RANAP) on the E-interface (V13 0 0 3GPP TS 29 1.pdf（15页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 1Universal Mobile TelApplication oApplication Pa(3GPP TS 29.1TECHNICAL SPECIFICATION129 108 V13.0.0 (2016elecommunications System (LTE; of the Radio Access NetworkPart (RANAP) on the E-interfac.108 version 13.0.0 Release 1316-01) (UMTS); rk face 13) ETSI ETSI TS 129 108 V13.0.0 (2016-01)13G

2、PP TS 29.108 version 13.0.0 Release 13Reference RTS/TSGR-0329108vd00 Keywords LTE,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

3、 Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modifie

4、d without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. User

5、s 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, please send your comme

6、nt to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. Th

7、e content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are T

8、rade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 129 108 V13.0.0 (2016

9、-01)23GPP TS 29.108 version 13.0.0 Release 13Intellectual 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 fou

10、nd 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 (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Po

11、licy, 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 Te

12、chnical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (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 E

13、TSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to

14、 be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 129 108 V13.0.0 (2016-01)33GPP TS 29.108 version 13.0.0 Release 13Conten

15、ts Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Abbreviations . 5g34 Principles for the use of RANAP on the E-interface 6g34.1 General . 6g34.2 Transfer of RANAP layer 3 messages on the E-interface 6g34.3 Roles of 3G_MSC-A, 3G_MS

16、C-I and 3G_MSC-T . 6g35 Use of the RANAP on the E-interface . 7g35.1 RAB Assignment 7g35.2 RAB Release Request 7g35.3 Iu Release Request . 8g35.4 Relocation Resource Allocation . 8g35.5 Relocation Cancel. 8g35.6 Relocation Detect and Relocation Complete 8g35.7 CN Trace invocation 9g35.8 Security mod

17、e control 9g35.9 Location Reporting Control 9g35.10 Location Report 9g35.11 Direct Transfer . 9g35.12 Error Indication 10g35.13 CN Deactivate Trace 10g35.14 Common ID 10g35.15 Location Related Data 10g35.16 UE Specific Information 10g35.17 RAB Modification Request 10g36 RANAP messages transferred on

18、 the E-interface 11g37 Exceptions for RANAP message contents and information element coding when transferred on the E-interface 12g37.1 Message Contents . 12g38 RANAP message error handling when transferred on the E-interface . 12g3Annex A (informative): Change history . 13g3History 14g3ETSI ETSI TS

19、 129 108 V13.0.0 (2016-01)43GPP TS 29.108 version 13.0.0 Release 13Foreword 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 following formal TSG approval.

20、 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 presented to TSG for approval; 3 or gr

21、eater 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 document. ETSI ETSI TS 129 10

22、8 V13.0.0 (2016-01)53GPP TS 29.108 version 13.0.0 Release 131 Scope The present document describes the subset of Radio Access Network Application Part (RANAP) messages and procedures, defined in 3GPP TS 25.413 4, which is used on the E-interface. A general description can be found in 3GPP TS 23.002

23、7 and 3GPP TS 23.009 2. For the initiation and execution of relocation of SRNS (relocation for short, throughout the whole document) between MSCs a subset of RANAP procedures are used. For the subsequent control of resources allocated to the User Equipment (UE) RANAP procedures are used. The Direct

24、Transfer Elementary Procedure (EP) of RANAP, is used for the transfer of connection management and mobility management messages between the UE and the controlling 3G_MSC. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the prese

25、nt document. - References are either specific (identified by date of 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 doc

26、ument (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary“. 2 3GPP TS 23.009: “Handover procedures“. 3 Void 4 3GPP TS 25.413: “UTRAN Iu Interface Radio Access Network

27、Application Part (RANAP) signalling“. 5 3GPP TS 29.002: “Mobile Application Part (MAP) specification“. 6 3GPP TS 29.010: “Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling procedures

28、and the Mobile Application Part (MAP)“. 7 3GPP TS 23.002: “Network architecture“. 8 Void 3 Abbreviations For the purposes of the present document, the abbreviations defined in TR 21.905 1 and the following apply: 3G_MSC A third generation Mobile services Switching Centre that supports the Iu interfa

29、ce (and possibly also the A-interface) 3G_MSC-A The controlling 3G_MSC on which the call was originally established 3G_MSC-B The 3G_MSC to which the UE is handed over in a Basic Handover 3G_MSC-B The 3G_MSC to which the UE is handed over in a Subsequent Handover 3G_MSC-I Interworking 3G_MSC 3G_MSC-T

30、 Target 3G_MSC EP Elementary Procedure NNSF NAS Node Selection Function RNC Radio Network Controller ETSI ETSI TS 129 108 V13.0.0 (2016-01)63GPP TS 29.108 version 13.0.0 Release 134 Principles for the use of RANAP on the E-interface 4.1 General The mechanism for the transfer of the RANAP messages on

31、 the E-interface is defined in TS 29.002 5. The operation of the relocation procedures between 3G_MSCs and the use of the RANAP messages for those procedures is described in TS 23.009 2 and TS 29.010 6. RANAP is defined to connect the RNS to both, the cs and ps domain of an UMTS CN. Procedures, mess

32、ages and IEs, only defined for communication between the RNS and the ps domain of an UMTS CN will, of course, never appear on the E-interface. In the same way as a the connection oriented service of SCCP is used for the messages relating to one UE on the 3G_MSC-RNS interface a TCAP dialogue is used

33、on the E-interface for messages relating to one UE. As no correspondence to the connectionless service on the 3G_MSC-RNS interface is used on the E-interface none of the global procedures are applicable. The management of the terrestrial circuits between the 3G_MSCs is outside the scope of the E-int

34、erface (see TS 23.009 2), therefore all procedures, messages and information elements relating to terrestrial circuits are also excluded from the RANAP procedures and messages used on the E-interface. 4.2 Transfer of RANAP layer 3 messages on the E-interface The RANAP data which on the 3G_MSC-RNS in

35、terface is contained in the user data field of the exchanged SCCP frames is on the E-interface transferred as the contents of the access network signalling info in the AN-APDU parameter as described in TS 29.002 5, indicating the access network protocol identification “ts3G-25413“. 4.3 Roles of 3G_M

36、SC-A, 3G_MSC-I and 3G_MSC-T For the description in the present document, the 3G_MSCs functionality related to the relocation between 3G_MSCs has been split into three logical parts, 3G_MSC-A, 3G_MSC-T and 3G_MSC-I. The different roles need not necessarily be performed by different 3G_MSCs. 3G_MSC-A

37、is the call/connection controlling part of the 3G_MSC where the call/connection was originally established and the switching point for relocation between 3G_MSCs. (This corresponds to 3G_MSC-A as defined in TS 23.009 2 and TS 29.002 5). The 3G_MSC that is the 3G_MSC-A will not be changed during the

38、duration of a call/connection. 3G_MSC-T is the part relating to the transitory state during the relocation for the 3G_MSC controlling the RNS the serving RNS functionality is relocated to, when basic relocation or subsequent relocation (see TS 23.009) take place. (This corresponds, depending on the

39、type of relocation to 3G_MSC-A, 3G_MSC-B or 3G_MSC-B in TS 23.009 2 and TS 29.002 5). 3G_MSC-I is the part of a 3G_MSC through which the 3G_MSC-A, via an E-interface (or an internal interface) is in contact with the UE. (This corresponds, depending on the type of relocation to 3G_MSC-A, 3G_MSC-B or

40、3G_MSC-B in TS 23.009 2 and TS 29.002 5). The 3G_MSC that is the 3G_MSC-A can also have the role of either the 3G_MSC-I or the 3G_MSC-T during a period of the call/connection. The following is applicable for the involved 3G_MSCs concerning the exchange of RANAP data on an E-interface before and afte

41、r a successful inter 3G_MSC relocation: 1) At basic relocation, two 3G_MSCs are involved, one 3G_MSC being 3G_MSC-A and one being 3G_MSC-T. When this relocation has been performed, the two 3G_MSCs interworking on the E-interface have the roles of 3G_MSC-A and 3G_MSC-I respectively, i.e. the 3G_MSC t

42、hat is the 3G_MSC-T during the relocation is now the 3G_MSC-I. 2) At subsequent relocation back to 3G_MSC-A, two 3G_MSCs are involved. The 3G_MSC having the role of 3G_MSC-A has also the role of 3G_MSC-T. The other 3G_MSC involved has the role of 3G_MSC-I. When this ETSI ETSI TS 129 108 V13.0.0 (201

43、6-01)73GPP TS 29.108 version 13.0.0 Release 13relocation has been completed, there is no exchange of RANAP data on the E-interface, i.e. the 3G_MSC being the 3G_MSC-I before and during the relocation is now no longer taking part. 3) At subsequent relocation of SRNS to an 3G_MSC not being 3G_MSC-A, t

44、hree 3G_MSCs are involved. The roles of these 3G_MSCs are 3G_MSC-A, 3G_MSC-I, and 3G_MSC-T respectively. When this relocation has been performed, the two 3G_MSCs interworking on an E-interface have the roles of 3G_MSC-A and 3G_MSC-I respectively, i.e. the 3G_MSC that is the 3G_MSC-T during the reloc

45、ation is now the 3G_MSC-I and the 3G_MSC being 3G_MSC-I during the relocation is now no longer taking part. 5 Use of the RANAP on the E-interface The dedicated RANAP procedures used on the E-interface to some extent are: - RAB assignment; - RAB Release Request; - Iu Release Request; - Relocation res

46、ource allocation; - Relocation Detect; - Relocation Complete; - Relocation Cancel; - CN Invoke Trace; - Security mode control; - Location Reporting Control; - Location Report; - Direct Transfer; - Error Indication; - Common ID; - Location Related Data; - UE Specific Information; - RAB Modification R

47、equest. 5.1 RAB Assignment The RAB Assignment procedure (TS 25.413 4 subclause 8.2) is applied on the E-interface with following conditions: - the 3G_MSC-A acts as the 3G_MSC; - the 3G_MSC-I acts as the RNS. The handling of terrestrial resources is not applicable, i.e. the RANAP IEs Transport Layer

48、Address and Iu Transport Association will be assigned by the 3G_MSC-I. 5.2 RAB Release Request For the RAB Release Request procedure (TS 25.413 4 subclauses 8.3) the involved 3G_MSCs shall act according to the following: ETSI ETSI TS 129 108 V13.0.0 (2016-01)83GPP TS 29.108 version 13.0.0 Release 13

49、- the 3G_MSC-I acts as the RNS; - the 3G_MSC-A acts as the 3G_MSC. 5.3 Iu Release Request For the Iu Release Request procedure (TS 25.413 4 subclause 8.4) the involved 3G_MSCs shall act according to the following: - the 3G_MSC-I acts as the RNS; - the 3G_MSC-A acts as the 3G_MSC. Additionally, at basic Inter-3G_MSC relocation and at subsequent Inter-3G_MSC relocation (TS 23.009 2), if the 3G_MSC that is the 3G_MSC-A is not also the 3G_MSC-T, the Iu Release Request procedure (TS 25.413 4 subclause 8.4) is applied on t