1、 ETSI TS 1Universal Mobile TelUTRAN(3GPP TS 25.4TECHNICAL SPECIFICATION125 401 V13.0.0 (2016elecommunications System (A overall description .401 version 13.0.0 Release 1316-01) (UMTS); 13) ETSI ETSI TS 125 401 V13.0.0 (2016-01)13GPP TS 25.401 version 13.0.0 Release 13Reference RTS/TSGR-0325401vd00 K
2、eywords LTE 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 downloa
3、ded 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 existing
4、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 subject
5、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/People/Commitee
6、SupportStaff.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 the written auth
7、orization 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. 3GPPTM and LT
8、E 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 401 V13.0.0 (2016-01)23GPP TS 25.401 version 13.0.0 Release 13Intellectual Property Rights I
9、PRs 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); Essential, or
10、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 carried out by ETS
11、I. 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 Generation Partner
12、ship 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, 3GPP and ETSI iden
13、tities 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 Drafting Rules (Verb
14、al 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 401 V13.0.0 (2016-01)33GPP TS 25.401 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g
15、3Foreword . 6g31 Scope 7g32 References 7g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 10g33.3 Notation 12g34 General principles 13g35 UMTS General architecture . 13g35.1 Overview 13g35.2 General protocols architecture 14g35.2.1 User plane . 14g35.2.2 Control plane 15g
16、36 UTRAN Architecture . 15g36.1 UTRAN Identifiers . 20g36.1.1 PLMN Identity 20g36.1.2 CN Domain Identifier . 20g36.1.3 RNC Identifier 20g36.1.4 Service Area Identifier 20g36.1.5 Cell Identifier 20g36.1.6 Local Cell Identifier 20g36.1.7 UE Identifiers 20g36.1.7.1 Usage of RNTI 22g36.1.7a UE Identifie
17、rs in GERAN A/Gb mode (1.28Mcps TDD) . 22g36.1.8 Identifiers for dedicated resources within UTRAN 22g36.1.8.1 Radio Network Control Plane identifiers 22g36.1.8.2 Transport Network Identifiers . 23g36.1.8.3 Binding identifier 24g36.1.9 URA Identity 25g36.1.10 Service Identifiers for MBMS 25g36.1.10.1
18、 IP Multicast Address and APN . 25g36.1.10.2 TMGI 26g36.1.10.3 Session Identifier . 26g36.1.10.4 MBMS Service Area . 26g36.1.10.5 MBMS Cell Group Identifier 26g36.1.10.6 MBMS UTRAN Cell Group Identifier . 26g36.1.11 Transport Network Identifiers for MBMS 26g36.1.12 Binding Identifiers for MBMS 26g36
19、.1.13 Use of Extended Identifiers 26g36.2 Transport Addresses . 26g36.3 Function Distribution Principles . 27g37 UTRAN Functions description . 27g37.1 List of functions . 27g37.2 Functions description . 29g37.2.0 Transfer of user data . 29g37.2.1 Functions related to overall system access control .
20、29g37.2.1.1 Admission Control 29g37.2.1.2 Congestion Control . 29g3ETSI ETSI TS 125 401 V13.0.0 (2016-01)43GPP TS 25.401 version 13.0.0 Release 137.2.1.3 System information broadcasting 29g37.2.1.4 MOCN and GWCN configuration support . 29g37.2.2 Radio channel ciphering and deciphering . 30g37.2.3 Fu
21、nctions related to Mobility 30g37.2.3.1 Handover . 30g37.2.3.2 SRNS Relocation 30g37.2.3.3 Paging support . 30g37.2.3.4 Positioning 30g37.2.3.5 NAS Node Selection Function 31g37.2.3.6 Shared Networks Access Control 31g37.2.3.7 GERAN System Information Retrieval . 31g37.2.3.8 Enhanced SRNS Relocation
22、 31g37.2.3.9 Subscriber Profile ID for RAT/Frequency Priority . 31g37.2.4 Functions related to radio resource management and control . 32g37.2.4.1 Radio resource configuration and operation . 32g37.2.4.2 Radio environment survey 32g37.2.4.3 Combining/splitting control 32g37.2.4.4 Connection set-up a
23、nd release . 32g37.2.4.5 Allocation and deallocation of Radio Bearers . 33g37.2.4.6 TDD - Dynamic Channel Allocation (DCA) 33g37.2.4.7 Radio protocols function . 33g37.2.4.8 RF power control 33g37.2.4.8.1 UL Outer Loop Power Control 33g37.2.4.8.2 DL Outer Loop Power Control 33g37.2.4.8.3 UL Inner Lo
24、op Power Control . 34g37.2.4.8.4 DL Inner Loop Power Control . 34g37.2.4.8.5 UL Open Loop Power Control 34g37.2.4.8.6 DL Open Loop Power Control 34g37.2.4.9 Radio channel coding 34g37.2.4.10 Radio channel decoding 34g37.2.4.11 Channel coding control . 35g37.2.4.12 Initial (random) access detection a
25、nd handling . 35g37.2.4.13 CN Distribution function for Non Access Stratum messages . 35g37.2.4.14 3.84 Mcps and 7.68 Mcps TDD - Timing Advance . 35g37.2.4.15 Service specific function for Non Access Stratum messages 35g37.2.4.16 1.28 Mcps TDD Uplink Synchronisation 35g37.2.5 Functions related to br
26、oadcast and multicast services (broadcast/multicast interworking function BM-IWF) 35g37.2.5.1 Broadcast/Multicast Information Distribution 36g37.2.5.2 Broadcast/Multicast Flow Control 36g37.2.5.3 CBS Status Reporting . 36g37.2.6 Tracing 36g37.2.7 Volume Reporting 36g37.2.8 RAN Information Management
27、 36g37.2.9 Functions related to MBMS 36g37.2.9.1 MBMS provision . 36g37.2.9.2 MBMS Notification Coordination 36g37.2.10 SIPTO at Iu-PS . 36g37.2.11 Explicit Congestion Notification 37g37.2.12 MDT . 37g37.2.13 SIPTO at the Local Network with Standalone GW 37g37.2.14 Traffic Volume for RAN Sharing . 3
28、7g38 Mobility Management 37g38.1 Signalling connection . 37g38.2 Consequences for Mobility Handling . 38g39 Synchronisation 38g39.1 SYNCHRONISATION MODEL . 38g310 UTRAN O 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is increme
29、nted 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 401 V13.0.0 (2016-01)73GPP TS 25.401 version 13.0.0 Release 131 Scope The present document
30、describes the overall architecture of the UTRAN, including internal interfaces and assumptions on the radio and Iu interfaces. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific
31、(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 document (including a GSM document), a non-specific r
32、eference implicitly refers to the latest version of that document in the same Release as the present document. 1 Void 2 3GPP TS 23.110: “UMTS Access Stratum Services and Functions“. 3 Void 4 3GPP TS 25.442: “UTRAN Implementation Specific O Protocol specification“. 8 3GPP TS 23.101: “General UMTS Arc
33、hitecture“. 9 3GPP TS 25.414: “ UTRAN Iu Interface Data Transport Stage 2“. 22 3GPP TR 44.901: “External Network Assisted Cell Change“. 23 3GPP TS 48.018: “General Packet Radio Service (GPRS); BSS GPRS Protocol (BSSGP)“. 24 3GPP TS 25.460: “UTRAN Iuant Interface: General Aspects and Principles“. 25
34、3GPP TS 25.461: “UTRAN Iuant Interface: Layer 1“. 26 3GPP TS 25.462: “UTRAN Iuant Interface: Signalling Transport“. 27 Void 28 3GPP TS 23.251: “Network sharing - Architecture and functional description“. 29 3GPP TS 25.410: UTRAN Iu Interface: general aspects and principles. 30 3GPP TS 25.346: Introd
35、uction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2. 31 3GPP TS 25.413: “UTRAN Iu Interface RANAP Signalling“. 32 3GPP TS 25.466: “UTRAN Iuant Interface: Application part“. 33 3GPP TS 25.305: “Stage 2 functional specification of UE positioning in UT
36、RAN“. 34 IETF RFC 4548 (2006-05): “Internet Code Point (ICP) Assignments for NSAP Addresses“ 35 3GPP TS 36.300: “Evolved Universal Terrestrial Radio Access (E-UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; stage 2“. 36 3GPP TS 23.060: “General Packet Radio
37、Service (GPRS); Service description; Stage 2“. 37 IETF RFC 3168 (2001-09): “The Addition of Explicit Congestion Notification (ECN) to IP“. 38 3GPP TS 37.320: “Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimizat
38、ion of Drive Tests (MDT); Overall description; Stage 2“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: 1.28Mcps TDD - Multi-frequency Cell: If multiple frequencies are configured in one cell, the cell is defined a
39、s the multi-frequency cell. 1.28Mcps TDD - Primary frequency: In a multi-frequency cell, the frequency on which the P-CCPCH is transmitted is defined as primary frequency. 1.28Mcps TDD - Secondary frequency: In a multi-frequency cell, any frequency other than the primary frequency is defined as seco
40、ndary frequency. ALCAP: generic name for the transport signalling protocols used to set-up and tear-down transport bearers Cell: Radio Network object that can be uniquely identified by a User Equipment from a (cell) identification that is broadcasted over a geographical area from one UTRAN Access Po
41、int A Cell is either FDD or TDD mode. ETSI ETSI TS 125 401 V13.0.0 (2016-01)93GPP TS 25.401 version 13.0.0 Release 13Iu: interface between an RNC and an MSC, SGSN or CBC, providing an interconnection point between the RNS and the Core Network. It is also considered as a reference point Iub: interfac
42、e between the RNC and the Node B Iur: logical interface between two RNCs Whilst logically representing a point to point link between RNCs, the physical realisation need not be a point to point link. Iur-g: logical interface between RNC/BSS and BSS Whilst logically representing a point to point link
43、between RNC/BSS and BSS, the physical realisation need not be a point to point link. Logical Model: Logical Model defines an abstract view of a network or network element by means of information objects representing network element, aggregations of network elements, the topological relationship betw
44、een the elements, endpoints of connections (termination points), and transport entities (such as connections) that transport information between two or more termination points The information objects defined in the Logical Model are used, among others, by connection management functions. In this way
45、, a physical implementation independent management is achieved. Network sharing supporting UE: as defined in TS 23.251 28. Network sharing non-supporting UE: as defined in TS 23.251 28. Node B: logical node in the RNS responsible for radio transmission / reception in one or more cells to/from the UE
46、 The logical node terminates the Iub interface towards the RNC. Radio Resources: resources that constitute the radio interface in UTRAN, e.g. frequencies, scrambling codes, spreading factors, power for common and dedicated channels Node B Application Part: Radio Network Signalling over the Iub Radio
47、 Network Controller: logical node in the RNS in charge of controlling the use and the integrity of the radio resources Controlling RNC: role an RNC can take with respect to a specific set of Node Bs There is only one Controlling RNC for any Node B. The Controlling RNC has the overall control of the
48、logical resources of its node Bs. MBMS Master RNC: role an RNC can take with respect to one or more specific MBSFN cluster(s) MRNC may be used for Inter-RNC MBSFN operation whenever dynamic synchronization of radio resources used for MBMS services is centrally controlled. There is only one MBMS Mast
49、er RNC for any MBSFN cluster, which may control one or more MBSFN cluster(s). The MRNC has the overall control of the logical resources of the RNSs that are used for MBSFN operation within the MBSFN cluster(s). Radio Network Subsystem: RNS can be either a full UTRAN or only a part of a UTRAN An RNS offers the allocation and release of specific radio resources to establish means of connection in between an UE and the UTRAN. A Radio Network Subsystem contains one RNC and is responsible for the resources
