《3GPP TS 25.301 V8.7.0 (06).doc》由会员分享，可在线阅读，更多相关《3GPP TS 25.301 V8.7.0 (06).doc（53页珍藏版）》请在三一文库上搜索。
1、3GPP TS 25.301 V8.7.0 (2010-06)Technical Specification3rd Generation Partnership Project;Technical Specification Group Radio Access Network;Radio Interface Protocol Architecture(Release 8)The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be furth
2、er elaborated for the purposes of 3GPP.The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for a
3、ny use of this Specification.Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners Publications Offices.KeywordsUMTS, radio, architecture3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonn
4、e - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16Internethttp:/www.3gpp.orgCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media. 2010, 3GPP Organizational Partners (ARIB, ATIS
5、, CCSA, ETSI, TTA, TTC).All rights reserved.UMTS is a Trade Mark of ETSI registered for the benefit of its members3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersLTE is a Trade Mark of ETSI currently being registered for the benefit of it
6、s Members and of the 3GPP Organizational PartnersGSM and the GSM logo are registered and owned by the GSM AssociationContentsForeword51Scope62References63Definitions and abbreviations73.1Definitions73.2Abbreviations74Assumed UMTS Architecture85Radio interface protocol architecture95.1Overall protoco
7、l structure95.1.1Service access points and service primitives115.2Layer 1 Services and Functions125.2.1L1 Services125.2.1.1Transport channels125.2.2L1 Functions145.3Layer 2 Services and Functions145.3.1MAC Services and Functions145.3.1.1MAC Services to upper layers145.3.1.1.1Logical channels145.3.1.
8、1.2Mapping between logical channels and transport channels165.3.1.1.2.1Mapping in Uplink165.3.1.1.2.2Mapping in Downlink165.3.1.2MAC functions185.3.2RLC Services and Functions205.3.2.1Services provided to the upper layer205.3.2.2RLC Functions215.3.3PDCP Services and Function215.3.3.1PDCP Services pr
9、ovided to upper layers215.3.3.2PDCP Functions215.3.4Broadcast/Multicast Control - Services and functions225.3.4.1BMC Services225.3.4.2BMC Functions225.3.5Data flows through Layer 2225.3.5.1Data flow for BCCH mapped to BCH275.3.5.2Data flow for BCCH mapped to FACH285.3.5.3Data flow for PCCH mapped to
10、 PCH285.3.5.4Data flow for CCCH mapped to FACH/RACH285.3.5.5Data flow for SHCCH mapped to USCH285.3.5.6Data flow for SHCCH mapped to FACH/RACH285.3.5.7Data flow for DCCH mapped to FACH/RACH285.3.5.8Data flow for DCCH mapped to DSCH285.3.5.9Data flow for DCCH mapped to USCH285.3.5.10Void285.3.5.11Dat
11、a flow for DTCH (non-transparent RLC) mapped to FACH/RACH285.3.5.12Data flow for DTCH (non-transparent RLC) mapped to DSCH295.3.5.13Data flow for DTCH (non-transparent RLC) mapped to USCH295.3.5.14Data flow for DTCH (transparent RLC) mapped to DCH295.3.5.15Data flow for DTCH (non-transparent RLC) ma
12、pped to DCH295.3.5.16Void295.3.5.17Data flow for DCCH mapped to DCH295.3.5.18Data flow for CTCH mapped to FACH295.3.5.19Data flow for DCCH mapped to HS-DSCH295.3.5.20Data flow for DTCH (non-transparent RLC) mapped to HS-DSCH295.3.5.21Data flow for DCCH mapped to E-DCH295.3.5.22Data flow for DTCH (no
13、n-transparent RLC) mapped to E-DCH305.3.5.23Data flow for MCCH (non-transparent RLC) mapped to FACH305.3.5.24Data flow for MSCH (non-transparent RLC) mapped to FACH305.3.5.25Data flow for MTCH (non-transparent RLC) mapped to FACH305.3.5.26Data flow for CCCH mapped to HS-DSCH/RACH (FDD only)305.3.5.2
14、7Data flow for PCCH mapped to HS-DSCH305.3.5.28Data flow for BCCH mapped to HS-DSCH (FDD and 1.28 Mcps TDD only)305.3.5.29Data flow for CCCH mapped to HS-DSCH/E-DCH (FDD and 1.28 Mcps TDD only)305.3.6Transport Channel, Logical Channel and MAC-d flow Numbering305.4Layer 3 - Uu Stratum Services and Fu
15、nctions325.4.1Uu Stratum services325.4.1.1General Control325.4.1.2Notification335.4.1.3Dedicated Control335.4.2RRC functions335.5Interactions between RRC and lower layers in the C plane355.6Protocol termination365.6.1Protocol termination for DCH365.6.2Protocol termination for RACH/FACH365.6.3Void395
16、.6.4Void395.6.5Protocol termination for DSCH395.6.5.1DSCH definition395.6.5.2Resource allocation and UE identification on DSCH405.6.5.2.1Void405.6.5.2.2UE requires a downlink SHCCH405.6.5.3Model of DSCH in UTRAN405.6.5.4Protocol termination415.6.6Protocol termination for transport channel of type US
17、CH425.6.6.1USCH definition425.6.6.2Resource allocation and UE identification on USCH425.6.6.3Model of USCH in UTRAN425.6.6.4Protocol termination435.6.7Protocol termination for transport channel of type BCH445.6.8Protocol termination for transport channel of type PCH445.6.9Protocol termination for HS
18、-DSCH455.6.9.1HS-DSCH definition455.6.9.2Resource allocation and UE identification on HS-DSCH455.6.9.3Protocol termination455.6.10Protocol termination for E-DCH465.6.10.1E-DCH definition465.6.10.2Resource allocation and UE identification related to E-DCH465.6.10.3Protocol termination465.6.11Protocol
19、 termination for MBMS475.6.11.1MBMS definition475.6.11.2Resource allocation related to MBMS485.6.11.3Protocol termination486User Identification and RRC Connection Mobility496.1UE identification on the radio interface496.2UE connection to UTRAN507UE modes51Annex A (informative):Change history52Forewo
20、rdThis Technical Specification (TS) has been produced by the 3rd Generation 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
21、be re-released by the TSG with an identifying change of release date and an increase in version number as follows:Version x.y.zwhere:xthe first digit:1presented to TSG for information;2presented to TSG for approval;3or greater indicates TSG approved document under change control.ythe second digit is
22、 incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.zthe third digit is incremented when editorial only changes have been incorporated in the document.1ScopeThe present document shall provide an overview and overall description of the UE-UTRAN radio inte
23、rface protocol architecture as agreed within the 3GPP TSG RAN working group 2. Details of the radio protocols will be specified in companion documents.2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the present document. Reference
24、s are either specific (identified by date of publication, edition number, version number, etc.) or nonspecific. 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 docume
25、nt), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.13GPP TS23.110: UMTS Access Stratum; Services and Functions.23GPP TS25.401: RAN Overall Description.33GPP TR21.905: Vocabulary for 3GPP Specifications.43GPP TS25.302: Se
26、rvices provided by the Physical Layer.53GPP TS25.303: Interlayer Procedures in Connected Mode.63GPP TS25.304: UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode.73GPP TS25.321: MAC Protocol Specification.83GPP TS25.322: RLC Protocol Specification.93GPP TS25.323: PDCP Pr
27、otocol Specification.103GPP TS25.324: BMC Protocol Specification.113GPP TS25.331: RRC Protocol Specification.123GPP TS25.224: Physical Layer Procedures (TDD).133GPP TS24.007: Mobile radio interface signalling layer 3; General aspects.143GPP TS33.105: Cryptographic Algorithm Requirements.153GPP TS33.
28、102: Security Architecture.163GPP TS44.005: Data Link (DL) layer; General aspects.173GPP TS 25.308: UTRA High Speed Downlink Packet Access (HSDPA); Overall description.183GPP TS 25.309: FDD Enhanced Uplink; Overall description. 193GPP TS 25.346: Introduction of the Multimedia Broadcast Multicast Ser
29、vice (MBMS) in the Radio Access Network (RAN) (Stage-2).203GPP TS 25.423: UTRAN Iur interface RNSAP signalling.3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the terms and definitions given in 3 apply.3.2AbbreviationsFor the purposes of the present document, th
30、e following abbreviations apply:ARQAutomatic Repeat RequestASAccess StratumASCAccess Service ClassBCCHBroadcast Control ChannelBCHBroadcast ChannelBMCBroadcast/Multicast ControlC-Control-CCCall ControlCCCHCommon Control ChannelCCHControl ChannelCCTrCHCoded Composite Transport ChannelCNCore NetworkCR
31、CCyclic Redundancy CheckCTCHCommon Traffic ChannelDCDedicated Control (SAP)DCADynamic Channel AllocationDCCHDedicated Control ChannelDCHDedicated ChannelDLDownlinkDRNCDrift Radio Network ControllerDSCHDownlink Shared ChannelDTCHDedicated Traffic ChannelE-DCHEnhanced Dedicated ChannelFACHForward Link
32、 Access ChannelFCSFrame Check SequenceFDDFrequency Division DuplexGCGeneral Control (SAP)HARQHybrid Automatic Repeat RequestHOHandoverHS-DSCHHigh Speed Downlink Shared ChannelHS-PDSCHHigh Speed Physical Downlink Shared Channel JBMJitter Buffer ManagementITUInternational Telecommunication Unionkbpski
33、lobits per secondL1Layer 1 (physical layer)L2Layer 2 (data link layer)L3Layer 3 (network layer)LACLink Access ControlLAILocation Area IdentityMACMedium Access Control MBMSMultimedia Broadcast Multicast ServiceMCCHMBMS point-to-multipoint Control ChannelMMMobility ManagementMRNCMBMS Master RNCMSCHMBM
34、S point-to-multipoint Scheduling ChannelMTCHMBMS point-to-multipoint Traffic ChannelNASNon-Access StratumNtNotification (SAP)PCCHPaging Control ChannelPCHPaging ChannelPDCPPacket Data Convergence ProtocolPDUProtocol Data UnitPHYPhysical layerPhyCHPhysical ChannelsRABRadio Access BearerRACHRandom Acc
35、ess ChannelRBRadio BearerRLCRadio Link ControlRNCRadio Network ControllerRNSRadio Network SubsystemRNTIRadio Network Temporary IdentityRRCRadio Resource ControlSAPService Access PointSDUService Data UnitSHCCHShared Channel Control ChannelSRNCServing Radio Network ControllerSRNSServing Radio Network
36、SubsystemSYNCSynchronization User Plane ProtocolTCHTraffic ChannelTDDTime Division DuplexTFCITransport Format Combination IndicatorTFITransport Format IndicatorTFRITransport Format and Resource IndicatorTMSITemporary Mobile Subscriber IdentityTPCTransmit Power ControlTSNTransmit Sequence NumberU-Use
37、r-UEUser EquipmentULUplinkUMTSUniversal Mobile Telecommunications SystemURAUTRAN Registration AreaUSCHUplink Shared ChannelUTRAUMTS Terrestrial Radio AccessUTRANUMTS Terrestrial Radio Access NetworkUuSUu (Radio Interface) Stratum4Assumed UMTS ArchitectureFigure 1 shows the assumed UMTS architecture
38、as outlined in 1. The figure shows the UMTS architecture in terms of its entities User Equipment (UE), UTRAN and Core Network. The respective reference points Uu (Radio Interface) and Iu (CN-UTRAN interface) are shown. The figure illustrates furthermore the high-level functional grouping into the Ac
39、cess Stratum and the Non-Access Stratum.The Access Stratum offers services through the following Service Access Points (SAP) to the Non-Access Stratum:-General Control (GC) SAPs;-Notification (Nt) SAPs; and-Dedicated Control (DC) SAPs.The SAPs are marked with circles in Figure 1.Figure 1: Assumed UM
40、TS ArchitectureThe model in Figure 1 distinguishes the end AS entities 1, which provide the services to higher layers, from the local entities, which provide services over respectively the Uu and the Iu reference points.The Uu Stratum (UuS) block includes the radio interface protocol stack described
41、 in subclause 5.1.5Radio interface protocol architecture5.1Overall protocol structureThe radio interface is layered into three protocol layers:-the physical layer (L1);-the data link layer (L2);-network layer (L3).Layer 2 is split into following sublayers: Medium Access Control (MAC), Radio Link Con
42、trol (RLC), Packet Data Convergence Protocol (PDCP) and Broadcast/Multicast Control (BMC).Layer 3 and RLC are divided into Control (C-) and User (U-) planes. PDCP and BMC exist in the U-plane only.In the C-plane, Layer 3 is partitioned into sublayers where the lowest sublayer, denoted as Radio Resou
43、rce Control (RRC), interfaces with layer 2 and terminates in the UTRAN. The next sublayer provides Duplication avoidance functionality as specified in 13. It terminates in the CN but is part of the Access Stratum; it provides the Access Stratum Services to higher layers. The higher layer signalling
44、such as Mobility Management (MM) and Call Control (CC) is assumed to belong to the non-access stratum, and therefore not in the scope of 3GPP TSG RAN. On the general level, the protocol architecture is similar to the current ITU-R protocol architecture, ITU-R M.1035.Figure 2 shows the radio interfac
45、e protocol architecture. Each block in Figure 2 represents an instance of the respective protocol. Service Access Points (SAP) for peer-to-peer communication are marked with circles at the interface between sublayers. The SAP between MAC and the physical layer provides the transport channels (cf. su
46、bclause 5.2.1.1). The SAPs between RLC and the MAC sublayer provide the logical channels (cf. subclause 5.3.1.1.1). The RLC layer provides three types of SAPs, one for each RLC operation mode (UM, AM, and TM, see 8). PDCP and BMC are accessed by PDCP and BMC SAPs, respectively. The service provided by layer 2 is referred to as the radio bearer. The C-plane radio bearers, which are provided by RLC to RRC, are denoted as signalling radio bearers. In