1、 ETSI TS 1Universal Mobile TelInterlayer pro(3GPP TS 25.3TECHNICAL SPECIFICATION125 303 V13.0.0 (2016elecommunications System (rocedures in Connected Mode.303 version 13.0.0 Release 1316-01) (UMTS); 13) ETSI ETSI TS 125 303 V13.0.0 (2016-01)13GPP TS 25.303 version 13.0.0 Release 13Reference RTS/TSGR
2、-0225303vd00 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
3、 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 modified without the prior written authorization of ETSI. In case o
4、f 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. Users of the present document should be aware that the document
5、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 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. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members
8、. 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 125 303 V13.0.0 (2016-01)23GPP TS 25.303 version 13.0.0 Release 13Intellectual Pr
9、operty 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 Rights (IPRs);
10、 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, including IPR searches, has been car
11、ried 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 been produced by ETSI 3rd Gen
12、eration 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 ETSI deliverables. The cross reference between GSM, UMTS, 3GP
13、P 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 be interpreted as described in clause 3.2 of the ETSI Draft
14、ing 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 125 303 V13.0.0 (2016-01)33GPP TS 25.303 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs
15、 terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 General Description of Connected Mode . 7g35 Radio Bearer Control - Overview of Procedures . 8g35.1 Configurable parameters 8g35.2 Typical configuration cases 8g3
16、5.3 RRC Elementary Procedures 9g35.3.1 Category 1: Radio Bearer Configuration 9g35.3.2 Category 2: Transport Channel Configuration 9g35.3.3 Category 3: Physical Channel Configuration 10g35.3.4 Category 4: Transport Format Combination Restriction. 10g35.3.5 Category 5: Uplink Dedicated Channel Contro
17、l in CRNC . 10g36 Examples of procedures . 10g36.1 RRC Connection Establishment and Release Procedures 11g36.1.1 RRC connection establishment . 11g36.1.2 UE Initiated Signalling Connection Establishment. 13g36.1.3 Normal RRC Connection Release 13g36.1.3.1 RRC Connection Release from Dedicated Physic
18、al Channel . 14g36.1.3.2 RRC Connection Release without Dedicated Physical Channel . 15g36.2 Radio Bearer Control Procedures . 17g36.2.1 Radio Bearer Configuration 17g36.2.1.1 Radio Bearer Establishment 17g36.2.1.1.1 Radio Bearer Establishment with Dedicated Physical Channel Activation . 17g36.2.1.1
19、.2 Radio Bearer Establishment with Unsynchronised Dedicated Physical Channel Modification 19g36.2.1.1.3 Radio Bearer Establishment with Synchronised Dedicated Physical Channel Modification 20g36.2.1.1.4 Radio Bearer Establishment without Dedicated Physical Channel 22g36.2.1.1.5 Void . 23g36.2.1.2 Ra
20、dio Bearer Release 23g36.2.1.2.1 Radio Bearer Release with Unsynchronised Dedicated Physical Channel Modification 23g36.2.1.3 Radio Bearer Reconfiguration . 25g36.2.1.3.1 Unsynchronised Radio Bearer Reconfiguration 25g36.2.2 Transport Channel Reconfiguration 27g36.2.2.1 Unsynchronised Transport Form
21、at Set Reconfiguration . 27g36.2.3 Physical Channel Reconfiguration 29g36.2.3.1 UE-Originated DCH Activation 29g36.2.3.2 UE-terminated synchronised DCH Modify . 31g36.2.3.3 UE-terminated DCH Release 32g36.2.4 Transport Format Combination Control . 34g36.2.4.1 Transport Format Combination Limitation
22、. 34g36.2.5 Dynamic Resource Allocation Control of Uplink DCHs 35g36.2.6 Variable Rate Transmission of Uplink DCHs . 37g36.3 Data transmission . 39g36.3.1 Void 39g36.3.2 Void 39g3ETSI ETSI TS 125 303 V13.0.0 (2016-01)43GPP TS 25.303 version 13.0.0 Release 136.3.3 Void 39g36.3.4 Data transfer on USCH
23、 (TDD only) . 39g36.3.5 Data transfer on DSCH (TDD only) . 40g36.4 RRC Connection mobility procedures 41g36.4.1 Handover Measurement Reporting . 41g36.4.2 Cell Update . 42g36.4.3 URA Update . 44g36.4.4 Radio Link Addition (FDD) . 47g36.4.5 Radio Link Removal (FDD) . 48g36.4.6 Combined radio link add
24、ition and removal . 49g36.4.7 Hard Handover (FDD and TDD) 50g36.4.8 SRNS Relocation 51g36.4.8.1 Combined Cell/URA Update and SRNS relocation (lossless radio bearers) . 51g36.4.8.2 Combined Hard Handover and SRNS relocation (lossless radio bearers) 54g36.4.8.3 Combined Cell/URA Update and SRNS reloca
25、tion (seamless radio bearers) . 56g36.4.8.4 Combined Hard Handover and SRNS relocation (seamless radio bearers). 58g36.4.9 RRC Connection re-establishment 60g36.4.10 Inter-system Handover: GSM/BSS to UTRAN 61g36.4.11 Inter-RAT Handover: UTRAN to GSM/BSS, CS domain services 63g36.5 CN originated pagi
26、ng request in connected mode 65g36.5.1 UTRAN coordinated paging using DCCH . 65g36.6 UTRAN originated paging request and paging response . 67g36.7 Other procedures 68g36.7.1 UE Capability Information . 68g36.7.2 Random access transmission sequence (FDD) . 69g36.7.3 Random access transmission sequenc
27、e (TDD) . 70g36.7.3.1 Random access transmission sequence (3.84 Mcps TDD) 70g36.7.3.2 Random access transmission sequence (1.28 Mcps TDD) 71g36.7.4 Void 72g37 Traffic volume monitoring . 73g3Annex A (informative): Change history . 74g3History 76g3ETSI ETSI TS 125 303 V13.0.0 (2016-01)53GPP TS 25.303
28、 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. Should the TSG modify the contents of th
29、e 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 greater indicates TSG approved document und
30、er 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 125 303 V13.0.0 (2016-01)63GPP TS 25.303 versio
31、n 13.0.0 Release 131 Scope The present document describes all procedures that assign, reconfigure and 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
32、 peer-to-peer messages and interlayer primitives to illustrate the functional split between the layers, 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 desc
33、riptions /1, 2, 3/ and they are thus not within the scope of the present document. The interlayer procedures 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 th
34、e present 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 do
35、cument (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 TS 25.321: “Medium Access Control (MAC) protocol specification“. 2 3GPP TS 25.322: “Radio Link Control (RLC) protocol specification
36、“. 3 3GPP TS 25.331: “Radio Resource Control (RRC) protocol specification“. 4 3GPP TS 25.304: “UE 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
37、 description; Stage 2“. 7 3GPP TS 25.323: “Packet Data Convergence Protocol (PDCP) specification“. 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 Abbrevi
38、ations For the purposes of the present document, the following abbreviations apply: ASC Access Service Class DC-SAP Dedicated Control SAP DCH Dedicated transport CHannels RNTI Radio Network Temporary Identity ETSI ETSI TS 125 303 V13.0.0 (2016-01)73GPP TS 25.303 version 13.0.0 Release 134 General De
39、scription of Connected Mode The connected mode is entered when the RRC connection is established. 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 RR
40、C connection. The combination of s-RNTI and an RNC-ID is unique within a PLMN. c-RNTI is allocated 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 communicati
41、ng on common transport channels. The UE leaves the connected mode and returns to idle mode when 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
42、the characteristics of the traffic on those bearers. The UE-UTRAN interface is designed to support 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/
43、w availability, the dedicated resources cannot be allocated to all of the packet service users at 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 d
44、efines the level of activity associated to the UE. The key parameters of each state are the required 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 in
45、activity. The different levels of UE connection to UTRAN are listed below: - No signalling connection 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
46、connection exists, the UE is in connected mode and there is normally an RRC connection between UE 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
47、on cell level. Different transport channel types can be used for data transfer: - Common transport 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 hand
48、over. 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
49、level in the UTRAN; - handover is a family of procedures that adds or removes one or several radio links between one UE and UTRAN when an RRC connection exists and the position of the UE is known on cell level in the UTRAN. ETSI ETSI TS 125 303 V13.0.0 (2016-01)83GPP TS 25.303 version 13.0.0 Release 135 Radio Bearer Control - Overview of Procedures 5.1 Configurable parameters The following layer 1, MAC and RLC parameters should be configurable by RRC. The list is not complete. - Radio bearer parameters, e.g.: - RLC parameters per RLC link (radio bearer
