1、 ETSI TS 125 303 V15.0.0 (2018-07) Universal Mobile Telecommunications System (UMTS); Interlayer procedures in Connected Mode (3GPP TS 25.303 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 125 303 V15.0.0 (2018-07)13GPP TS 25.303 version 15.0.0 Release 15Reference RTS/TSGR-0625303vf
2、00 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 notice The present document can be do
3、wnloaded 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 modified without the prior written authorization of ETSI. In case of any exis
4、ting 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. Users of the present document should be aware that the document may be sub
5、ject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/
6、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. The content of the PDF version shall not be modified without t
7、he written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI reg
8、istered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 125 303 V15.0.0 (2018-07)23GPP TS 25.303 version 15.0.0 Release 15Inte
9、llectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables 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: “Intel
10、lectual 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 Policy, no investigation, inclu
11、ding 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. Trademarks The present document may include t
12、rademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present do
13、cument does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or rep
14、orts 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 found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs termino
15、logy In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to 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 E
16、TSI deliverables except when used in direct citation. ETSI ETSI TS 125 303 V15.0.0 (2018-07)33GPP TS 25.303 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Def
17、initions 6g33.2 Abbreviations . 6g34 General Description of Connected Mode . 7g35 Radio Bearer Control - Overview of Procedures . 7g35.1 Configurable parameters 7g35.2 Typical configuration cases 8g35.3 RRC Elementary Procedures 9g35.3.1 Category 1: Radio Bearer Configuration 9g35.3.2 Category 2: Tr
18、ansport Channel Configuration 9g35.3.3 Category 3: Physical Channel Configuration 9g35.3.4 Category 4: Transport Format Combination Restriction. 10g35.3.5 Category 5: Uplink Dedicated Channel Control in CRNC . 10g36 Examples of procedures . 10g36.1 RRC Connection Establishment and Release Procedures
19、 10g36.1.1 RRC connection establishment . 10g36.1.2 UE Initiated Signalling Connection Establishment. 12g36.1.3 Normal RRC Connection Release 12g36.1.3.1 RRC Connection Release from Dedicated Physical Channel . 13g36.1.3.2 RRC Connection Release without Dedicated Physical Channel . 14g36.2 Radio Bea
20、rer Control Procedures . 16g36.2.1 Radio Bearer Configuration 16g36.2.1.1 Radio Bearer Establishment 16g36.2.1.1.1 Radio Bearer Establishment with Dedicated Physical Channel Activation . 16g36.2.1.1.2 Radio Bearer Establishment with Unsynchronised Dedicated Physical Channel Modification 18g36.2.1.1.
21、3 Radio Bearer Establishment with Synchronised Dedicated Physical Channel Modification 19g36.2.1.1.4 Radio Bearer Establishment without Dedicated Physical Channel 21g36.2.1.1.5 Void . 22g36.2.1.2 Radio Bearer Release 22g36.2.1.2.1 Radio Bearer Release with Unsynchronised Dedicated Physical Channel M
22、odification 22g36.2.1.3 Radio Bearer Reconfiguration . 24g36.2.1.3.1 Unsynchronised Radio Bearer Reconfiguration 24g36.2.2 Transport Channel Reconfiguration 26g36.2.2.1 Unsynchronised Transport Format Set Reconfiguration . 26g36.2.3 Physical Channel Reconfiguration 28g36.2.3.1 UE-Originated DCH Acti
23、vation 28g36.2.3.2 UE-terminated synchronised DCH Modify . 30g36.2.3.3 UE-terminated DCH Release 31g36.2.4 Transport Format Combination Control . 33g36.2.4.1 Transport Format Combination Limitation . 33g36.2.5 Dynamic Resource Allocation Control of Uplink DCHs 34g36.2.6 Variable Rate Transmission of
24、 Uplink DCHs . 36g36.3 Data transmission . 38g36.3.1 Void 38g36.3.2 Void 38g36.3.3 Void 38g36.3.4 Data transfer on USCH (TDD only) . 38g3ETSI ETSI TS 125 303 V15.0.0 (2018-07)43GPP TS 25.303 version 15.0.0 Release 156.3.5 Data transfer on DSCH (TDD only) . 39g36.4 RRC Connection mobility procedures
25、40g36.4.1 Handover Measurement Reporting . 40g36.4.2 Cell Update . 41g36.4.3 URA Update . 43g36.4.4 Radio Link Addition (FDD) . 46g36.4.5 Radio Link Removal (FDD) . 47g36.4.6 Combined radio link addition and removal . 48g36.4.7 Hard Handover (FDD and TDD) 49g36.4.8 SRNS Relocation 50g36.4.8.1 Combin
26、ed Cell/URA Update and SRNS relocation (lossless radio bearers) . 50g36.4.8.2 Combined Hard Handover and SRNS relocation (lossless radio bearers) 53g36.4.8.3 Combined Cell/URA Update and SRNS relocation (seamless radio bearers) . 55g36.4.8.4 Combined Hard Handover and SRNS relocation (seamless radio
27、 bearers). 57g36.4.9 RRC Connection re-establishment 59g36.4.10 Inter-system Handover: GSM/BSS to UTRAN 60g36.4.11 Inter-RAT Handover: UTRAN to GSM/BSS, CS domain services 62g36.5 CN originated paging request in connected mode 64g36.5.1 UTRAN coordinated paging using DCCH . 64g36.6 UTRAN originated
28、paging request and paging response . 66g36.7 Other procedures 67g36.7.1 UE Capability Information . 67g36.7.2 Random access transmission sequence (FDD) . 68g36.7.3 Random access transmission sequence (TDD) . 69g36.7.3.1 Random access transmission sequence (3.84 Mcps TDD) 69g36.7.3.2 Random access tr
29、ansmission sequence (1.28 Mcps TDD) 70g36.7.4 Void 71g37 Traffic volume monitoring . 71g3Annex A (informative): Change history . 72g3History 74g3ETSI ETSI TS 125 303 V15.0.0 (2018-07)53GPP TS 25.303 version 15.0.0 Release 15Foreword This Technical Specification has been produced by the 3rdGeneration
30、 Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change 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 a
31、n 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 greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enha
32、ncements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 125 303 V15.0.0 (2018-07)63GPP TS 25.303 version 15.0.0 Release 151 Scope The present document describes all procedures that assign, reconfigure and
33、release radio resources. Included are e.g. procedures for transitions between different states and substates, handovers and measurement reports. The emphasis is on showing the combined usage of both peer-to-peer messages and interlayer primitives to illustrate the functional split between the layers
34、, as well as the combination of elementary procedures for selected examples. The peer-to-peer elementary procedure descriptions and interlayer dependencies are described in the related protocol descriptions /1, 2, 3/ and they are thus not within the scope of the present document. The interlayer proc
35、edures and interlayer dependencies in the present document are informative. 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 publication, edition numbe
36、r, 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 refers to the latest vers
37、ion of that document in the same Release as the present document. 1 3GPP TS 25.321: “Medium Access Control (MAC) protocol specification“. 2 3GPP TS 25.322: “Radio Link Control (RLC) protocol specification“. 3 3GPP TS 25.331: “Radio Resource Control (RRC) protocol specification“. 4 3GPP TS 25.304: “U
38、E Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode“. 5 3GPP TS 25.301: “Radio Interface Protocol Architecture“. 6 3GPP TS 23.060: “General Packet Radio Service (GPRS); Service description; Stage 2“. 7 3GPP TS 25.323: “Packet Data Convergence Protocol (PDCP) specification
39、“. 8 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 8 apply. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ASC Access S
40、ervice Class DC-SAP Dedicated Control SAP DCH Dedicated transport CHannels RNTI Radio Network Temporary Identity ETSI ETSI TS 125 303 V15.0.0 (2018-07)73GPP TS 25.303 version 15.0.0 Release 154 General Description of Connected Mode The connected mode is entered when the RRC connection is established
41、. The UE is assigned a Radio Network Temporary Identity (RNTI) to be used as UE identity on common transport channels. Two types of RNTI exist. The Serving RNC allocates an s-RNTI for all UEs having an RRC connection. The combination of s-RNTI and an RNC-ID is unique within a PLMN. c-RNTI is allocat
42、ed by each Controlling RNC through which UE is able to communicate on DCCH. c-RNTI is always allocated by UTRAN when a new UE context is created to an RNC, but the UE needs its c-RNTI only for communicating on common transport channels. The UE leaves the connected mode and returns to idle mode when
43、the RRC connection is released or at RRC connection failure. Within connected mode the level of UE connection to UTRAN is determined by the quality of service requirements of the active radio bearers and the characteristics of the traffic on those bearers. The UE-UTRAN interface is designed to suppo
44、rt a large number of UEs using packet data services by providing flexible means to utilize statistical multiplexing. Due to limitations, such as air interface capacity, UE power consumption and network h/w availability, the dedicated resources cannot be allocated to all of the packet service users a
45、t all times. Variable rate transmission provides the means that for services of variable rate the data rate is adapted according to the maximum allowable output power. The UE state in the connected mode defines the level of activity associated to the UE. The key parameters of each state are the requ
46、ired activity and resources within the state and the required signalling prior to the data transmission. The state of the UE shall at least be dependent on the application requirement and the period of inactivity. The different levels of UE connection to UTRAN are listed below: - No signalling conne
47、ction exists The UE is in idle mode and has no relation to UTRAN, only to CN. For data transfer, a signalling connection has to be established. - Signalling connection exists When at least one signalling connection exists, the UE is in connected mode and there is normally an RRC connection between U
48、E and UTRAN. The UE position can be known on different levels: - UTRAN Registration Area (URA) level The UE position is known on URA level. The URA is a set of cells - Cell level The UE position is known on cell level. Different transport channel types can be used for data transfer: - Common transpo
49、rt channels (RACH / FACH, DSCH) - Dedicated transport CHannels (DCH) Assuming that there exists an RRC connection, there are two basic families of RRC connection mobility procedures, URA updating and handover. Different families of RRC connection mobility procedures are used in different levels of UE connection (cell level and URA level): - URA updating is a family of procedures that updates the UTRAN registration area of a UE when an RRC connection exists and the position of the UE is known on URA level in the UTRAN; - handover is a family of procedures that
