throbber
3GPP TS 25.301 V7.1.0 (2007-03)
`
`Technical Specification
`
`3rd Generation Partnership Project;
`Technical Specification Group Radio Access Network;
`Radio Interface Protocol Architecture
`(Release 7)
`
`The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further 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 any use of this Specification.
`Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.
`
`CR page 1
`
`1
`
`APPLE 1009
`
`

`

`
`Release 7
`
`2
`
`3GPP TS 25.301 V7.1.0 (2007-03)
`
`
`
`
`
`
`
`
`
`Keywords
`UMTS, radio, architecture
`
`3GPP
`
`Postal address
`
`
`3GPP support office address
`650 Route des Lucioles - Sophia Antipolis
`Valbonne - FRANCE
`Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
`
`Internet
`http://www.3gpp.org
`
`Copyright Notification
`
`No part may be reproduced except as authorized by written permission.
`The copyright and the foregoing restriction extend to reproduction in all media.
`
`© 2007, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
`All rights reserved.
`
`
`3GPP
`
`2
`
`

`

`
`Release 7
`
`3
`
`3GPP TS 25.301 V7.1.0 (2007-03)
`
`Contents
`Foreword ............................................................................................................................................................ 5
`1
`Scope ........................................................................................................................................................ 6
`2
`References ................................................................................................................................................ 6
`3
`Definitions and abbreviations ................................................................................................................... 7
`3.1
`Definitions ............................................................................................................................................................. 7
`3.2
`Abbreviations ........................................................................................................................................................ 7
`4
`Assumed UMTS Architecture .................................................................................................................. 8
`5
`Radio interface protocol architecture ....................................................................................................... 9
`5.1
`Overall protocol structure ..................................................................................................................................... 9
`5.1.1
`Service access points and service primitives ................................................................................................ 11
`5.2
`Layer 1 Services and Functions .......................................................................................................................... 12
`5.2.1
`L1 Services .................................................................................................................................................... 12
`5.2.1.1
`Transport channels ................................................................................................................................... 12
`5.2.2
`L1 Functions .................................................................................................................................................. 13
`5.3
`Layer 2 Services and Functions .......................................................................................................................... 14
`5.3.1
`MAC Services and Functions ....................................................................................................................... 14
`5.3.1.1
`MAC Services to upper layers ................................................................................................................ 14
`5.3.1.1.1
`Logical channels ................................................................................................................................ 14
`5.3.1.1.2
`Mapping between logical channels and transport channels .............................................................. 16
`5.3.1.1.2.1
`Mapping in Uplink ....................................................................................................................... 16
`5.3.1.1.2.2
`Mapping in Downlink .................................................................................................................. 16
`5.3.1.2
`MAC functions ........................................................................................................................................ 18
`5.3.2
`RLC Services and Functions ......................................................................................................................... 19
`5.3.2.1
`Services provided to the upper layer ....................................................................................................... 19
`5.3.2.2
`RLC Functions ......................................................................................................................................... 20
`5.3.3
`PDCP Services and Function ........................................................................................................................ 21
`5.3.3.1
`PDCP Services provided to upper layers ................................................................................................ 21
`5.3.3.2
`PDCP Functions ...................................................................................................................................... 21
`5.3.4
`Broadcast/Multicast Control - Services and functions ................................................................................. 21
`5.3.4.1
`BMC Services .......................................................................................................................................... 21
`5.3.4.2
`BMC Functions ........................................................................................................................................ 21
`5.3.5
`Data flows through Layer 2........................................................................................................................... 21
`5.3.5.1
`Data flow for BCCH mapped to BCH .................................................................................................... 25
`5.3.5.2
`Data flow for BCCH mapped to FACH .................................................................................................. 25
`5.3.5.3
`Data flow for PCCH mapped to PCH ..................................................................................................... 25
`5.3.5.4
`Data flow for CCCH mapped to FACH/RACH ..................................................................................... 25
`5.3.5.5
`Data flow for SHCCH mapped to USCH ............................................................................................... 25
`5.3.5.6
`Data flow for SHCCH mapped to FACH/RACH ................................................................................... 26
`5.3.5.7
`Data flow for DCCH mapped to FACH/RACH ..................................................................................... 26
`5.3.5.8
`Data flow for DCCH mapped to DSCH .................................................................................................. 26
`5.3.5.9
`Data flow for DCCH mapped to USCH .................................................................................................. 26
`5.3.5.10
`Void .......................................................................................................................................................... 26
`5.3.5.11
`Data flow for DTCH (non-transparent RLC) mapped to FACH/RACH ............................................... 26
`5.3.5.12
`Data flow for DTCH (non-transparent RLC) mapped to DSCH ............................................................ 26
`5.3.5.13
`Data flow for DTCH (non-transparent RLC) mapped to USCH ............................................................ 26
`5.3.5.14
`Data flow for DTCH (transparent RLC) mapped to DCH ..................................................................... 26
`5.3.5.15
`Data flow for DTCH (non-transparent RLC) mapped to DCH .............................................................. 26
`5.3.5.16
`Void .......................................................................................................................................................... 27
`5.3.5.17
`Data flow for DCCH mapped to DCH .................................................................................................... 27
`5.3.5.18
`Data flow for CTCH mapped to FACH .................................................................................................. 27
`5.3.5.19
`Data flow for DCCH mapped to HS-DSCH ........................................................................................... 27
`5.3.5.20
`Data flow for DTCH (non-transparent RLC) mapped to HS-DSCH ..................................................... 27
`5.3.5.21
`Data flow for DCCH mapped to E-DCH ................................................................................................ 27
`5.3.5.22
`Data flow for DTCH (non-transparent RLC) mapped to E-DCH .......................................................... 27
`
`3GPP
`
`3
`
`

`

`
`Release 7
`
`4
`
`3GPP TS 25.301 V7.1.0 (2007-03)
`
`Data flow for MCCH (non-transparent RLC) mapped to FACH ........................................................... 27
`5.3.5.23
`Data flow for MSCH (non-transparent RLC) mapped to FACH ........................................................... 27
`5.3.5.24
`Data flow for MTCH (non-transparent RLC) mapped to FACH ........................................................... 27
`5.3.5.25
`Transport Channel, Logical Channel and MAC-d flow Numbering ............................................................ 27
`5.3.6
`Layer 3 - Uu Stratum Services and Functions .................................................................................................... 29
`5.4
`Uu Stratum services ...................................................................................................................................... 29
`5.4.1
`General Control ....................................................................................................................................... 29
`5.4.1.1
`Notification .............................................................................................................................................. 29
`5.4.1.2
`Dedicated Control .................................................................................................................................... 29
`5.4.1.3
`RRC functions ............................................................................................................................................... 30
`5.4.2
`Interactions between RRC and lower layers in the C plane ............................................................................... 32
`5.5
`Protocol termination ............................................................................................................................................ 32
`5.6
`Protocol termination for DCH ....................................................................................................................... 32
`5.6.1
`Protocol termination for RACH/FACH ........................................................................................................ 33
`5.6.2
`Void ............................................................................................................................................................... 35
`5.6.3
`Void ............................................................................................................................................................... 35
`5.6.4
`Protocol termination for DSCH .................................................................................................................... 35
`5.6.5
`DSCH definition ...................................................................................................................................... 35
`5.6.5.1
`Resource allocation and UE identification on DSCH ............................................................................. 36
`5.6.5.2
`Void .................................................................................................................................................... 36
`5.6.5.2.1
`UE requires a downlink SHCCH ....................................................................................................... 36
`5.6.5.2.2
`Model of DSCH in UTRAN .................................................................................................................... 36
`5.6.5.3
`Protocol termination ................................................................................................................................ 37
`5.6.5.4
`Protocol termination for transport channel of type USCH ........................................................................... 38
`5.6.6
`USCH definition ...................................................................................................................................... 38
`5.6.6.1
`Resource allocation and UE identification on USCH ............................................................................. 38
`5.6.6.2
`Model of USCH in UTRAN .................................................................................................................... 38
`5.6.6.3
`Protocol termination ................................................................................................................................ 39
`5.6.6.4
`Protocol termination for transport channel of type BCH ............................................................................. 40
`5.6.7
`Protocol termination for transport channel of type PCH .............................................................................. 40
`5.6.8
`Protocol termination for HS-DSCH .............................................................................................................. 41
`5.6.9
`HS-DSCH definition ............................................................................................................................... 41
`5.6.9.1
`Resource allocation and UE identification on HS-DSCH ...................................................................... 41
`5.6.9.2
`Protocol termination ................................................................................................................................ 41
`5.6.9.3
`Protocol termination for E-DCH ................................................................................................................... 42
`5.6.10
`E-DCH definition .................................................................................................................................... 42
`5.6.10.1
`Resource allocation and UE identification related to E-DCH ................................................................ 42
`5.6.10.2
`Protocol termination ................................................................................................................................ 42
`5.6.10.3
`Protocol termination for MBMS ................................................................................................................... 43
`5.6.11
`MBMS definition ..................................................................................................................................... 43
`5.6.11.1
`Resource allocation related to MBMS .................................................................................................... 43
`5.6.11.2
`Protocol termination ................................................................................................................................ 43
`5.6.11.3
`6
`User Identification and RRC Connection Mobility ................................................................................ 44
`6.1
`UE identification on the radio interface ............................................................................................................. 44
`6.2
`UE connection to UTRAN .................................................................................................................................. 45
`7
`UE modes ............................................................................................................................................... 45
`Annex A (informative): Change history ....................................................................................................... 47
`
`
`3GPP
`
`4
`
`

`

`
`Release 7
`
`5
`
`3GPP TS 25.301 V7.1.0 (2007-03)
`
`Foreword
`This 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 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 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.
`
`3GPP
`
`5
`
`

`

`
`Release 7
`
`6
`
`3GPP TS 25.301 V7.1.0 (2007-03)
`
`Scope
`1
`The present document shall provide an overview and overall description of the UE-UTRAN radio interface protocol
`architecture as agreed within the 3GPP TSG RAN working group 2. Details of the radio protocols will be specified in
`companion documents.
`
`References
`2
`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 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 reference implicitly refers to the latest version of that document in the same
`Release as the present document.
`
`[1]
`
`[2]
`
`[3]
`
`[4]
`
`[5]
`
`[6]
`
`[7]
`
`[8]
`
`[9]
`[10]
`
`[11]
`
`[12]
`
`[13]
`
`[14]
`[15]
`
`[16]
`
`[17]
`
`[18]
`
`[19]
`
`3GPP TS 23.110: "UMTS Access Stratum; Services and Functions".
`
`3GPP TS 25.401: "RAN Overall Description".
`
`3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
`
`3GPP TS 25.302: "Services provided by the Physical Layer".
`
`3GPP TS 25.303: "Interlayer Procedures in Connected Mode".
`
`3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected
`Mode".
`
`3GPP TS 25.321: "MAC Protocol Specification".
`
`3GPP TS 25.322: "RLC Protocol Specification".
`
`3GPP TS 25.323: "PDCP Protocol Specification".
`3GPP TS 25.324: "BMC Protocol Specification".
`
`3GPP TS 25.331: "RRC Protocol Specification".
`
`3GPP TS 25.224: "Physical Layer Procedures (TDD)".
`
`3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
`
`3GPP TS 33.105: "Cryptographic Algorithm Requirements".
`3GPP TS 33.102: "Security Architecture".
`
`3GPP TS 44.005: "Data Link (DL) layer; General aspects".
`
`3GPP TS 25.308: "UTRA High Speed Downlink Packet Access (HSDPA); Overall description".
`
`3GPP TS 25.309: " FDD Enhanced Uplink; Overall description".
`
`3GPP TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the
`Radio Access Network (RAN) (Stage-2)".
`
`3GPP
`
`6
`
`

`

`
`Release 7
`
`7
`
`3GPP TS 25.301 V7.1.0 (2007-03)
`
`3
`
`Definitions and abbreviations
`
`Definitions
`3.1
`For the purposes of the present document, the terms and definitions given in [3] apply.
`
`Abbreviations
`3.2
`For the purposes of the present document, the following abbreviations apply:
`
`ARQ
`AS
`ASC
`BCCH
`BCH
`BMC
`C-
`CC
`CCCH
`CCH
`CCTrCH
`CN
`CRC
`CTCH
`DC
`DCA
`DCCH
`DCH
`DL
`DRNC
`DSCH
`DTCH
`E-DCH
`FACH
`FCS
`FDD
`GC
`HARQ
`HO
`HS-DSCH
`HS-PDSCH
`ITU
`kbps
`L1
`L2
`L3
`LAC
`LAI
`MAC
`MBMS
`MCCH
`MM
`MSCH
`MTCH
`NAS
`Nt
`PCCH
`PCH
`PDCP
`
`Automatic Repeat Request
`Access Stratum
`Access Service Class
`Broadcast Control Channel
`Broadcast Channel
`Broadcast/Multicast Control
`Control-
`Call Control
`Common Control Channel
`Control Channel
`Coded Composite Transport Channel
`Core Network
`Cyclic Redundancy Check
`Common Traffic Channel
`Dedicated Control (SAP)
`Dynamic Channel Allocation
`Dedicated Control Channel
`Dedicated Channel
`Downlink
`Drift Radio Network Controller
`Downlink Shared Channel
`Dedicated Traffic Channel
`Enhanced Dedicated Channel
`Forward Link Access Channel
`Frame Check Sequence
`Frequency Division Duplex
`General Control (SAP)
`Hybrid Automatic Repeat Request
`Handover
`High Speed Downlink Shared Channel
`High Speed Physical Downlink Shared Channel
`International Telecommunication Union
`kilobits per second
`Layer 1 (physical layer)
`Layer 2 (data link layer)
`Layer 3 (network layer)
`Link Access Control
`Location Area Identity
`Medium Access Control
`Multimedia Broadcast Multicast Service
`MBMS point-to-multipoint Control Channel
`Mobility Management
`MBMS point-to-multipoint Scheduling Channel
`MBMS point-to-multipoint Traffic Channel
`Non-Access Stratum
`Notification (SAP)
`Paging Control Channel
`Paging Channel
`Packet Data Convergence Protocol
`
`3GPP
`
`7
`
`

`

`
`Release 7
`
`8
`
`3GPP TS 25.301 V7.1.0 (2007-03)
`
`PDU
`PHY
`PhyCH
`RAB
`RACH
`RB
`RLC
`RNC
`RNS
`RNTI
`RRC
`SAP
`SDU
`SHCCH
`SRNC
`SRNS
`TCH
`TDD
`TFCI
`TFI
`TFRI
`TMSI
`TPC
`TSN
`U-
`UE
`UL
`UMTS
`URA
`USCH
`UTRA
`UTRAN
`UuS
`
`Protocol Data Unit
`Physical layer
`Physical Channels
`Radio Access Bearer
`Random Access Channel
`Radio Bearer
`Radio Link Control
`Radio Network Controller
`Radio Network Subsystem
`Radio Network Temporary Identity
`Radio Resource Control
`Service Access Point
`Service Data Unit
`Shared Channel Control Channel
`Serving Radio Network Controller
`Serving Radio Network Subsystem
`Traffic Channel
`Time Division Duplex
`Transport Format Combination Indicator
`Transport Format Indicator
`Transport Format and Resource Indicator
`Temporary Mobile Subscriber Identity
`Transmit Power Control
`Transmit Sequence Number
`User-
`User Equipment
`Uplink
`Universal Mobile Telecommunications System
`UTRAN Registration Area
`Uplink Shared Channel
`UMTS Terrestrial Radio Access
`UMTS Terrestrial Radio Access Network
`Uu (Radio Interface) Stratum
`
`Assumed UMTS Architecture
`4
`Figure 1 shows the assumed UMTS architecture 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
`Access 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.
`
`3GPP
`
`8
`
`

`

`
`Release 7
`
`9
`
`3GPP TS 25.301 V7.1.0 (2007-03)
`
`GC
`
`Nt
`
`DC
`
`end AS entity
`
`Non-Access Stratum (NAS)
`
`Access Stratum (AS)
`
`Relay
`
`GC
`
`Nt
`
`DC
`
`end AS entity
`
`GC
`
`Nt
`
`DC
`
`GC
`
`Nt
`
`DC
`
`GC
`
`Nt
`
`DC
`
`GC
`
`Nt
`
`DC
`
`Uu
`Stratum
`(UuS)
`
`RRC
`
`L2/L1
`
`RRC
`
`L2/L1
`
`Iu
`Stratum
`
`UE
`
`UTRAN
`
`Core Network
`
`Radio
`Iu
`(Uu)
`Figure 1: Assumed UMTS Architecture
`The 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 in subclause 5.1.
`
`5
`
`Radio interface protocol architecture
`
`Overall protocol structure
`5.1
`The 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 Control (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 Resource 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 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 interface 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. subclause 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
`
`3GPP
`
`9
`
`

`

`
`Release 7
`
`10
`
`3GPP TS 25.301 V7.1.0 (2007-03)
`
`C-plane radio bearers, which are provided by RLC to RRC, are denoted as signalling radio bearers. In the C-plane, the
`interface between 'Duplication avoidance' and higher L3 sublayers (CC, MM) is defined by the General Control (GC),
`Notification (Nt) and Dedicated Control (DC) SAPs.
`
`NOTE: The SAPs shown in Figure 2 are examples. For details on the definition of SAPs refer to the respective
`radio interface protocol specification.
`
`Also shown in the figure are connections between RRC and MAC as well as RRC and L1 providing local inter-layer
`control services. An equivalent control interface exists between RRC and the RLC sublayer, between RRC and the
`PDCP sublayer and between RRC and BMC sublayer. These interfaces allow the RRC to control the configuration of
`the lower layers. For this purpose separate Control SAPs are defined between RRC and each lower layer (PDCP, RLC,
`MAC, and L1).
`
`The RLC sublayer provides ARQ functionality closely coupled with the radio transmission technique used. There is no
`difference between RLC instances in C and U planes.
`
`The MAC sublayer is made up of several different MAC entities, MAC-d, MAC-c/sh/m, MAC-hs, MAC-es/MAC-e and
`MAC-m.
`
`The MAC-hs entity provides Hybrid ARQ functionality, and is only used on the HS-DSCH.
`
`The MAC-es/MAC-e entities provide Hybrid ARQ functionality, and are only used with E-DCH.
`
`The MAC-m entity provides selection combining functionality for MTCH from different cells. MAC-m is only used for
`FACH carrying MTCH and MSCH.
`
`The UTRAN can be requested by the CN to prevent all loss of data (i.e. independently of the handovers on the radio
`interface), as long as the Iu connection point is not modified. This is a basic requirement to be fulfilled by the UTRAN
`retransmission functionality as provided by the RLC sublayer.
`
`However, in case of the Iu connection point is changed (e.g. SRNS relocation, streamlining), the prevention of the loss
`of data may not be guaranteed autonomously by the UTRAN but relies on 'Duplication avoidance' functions in the CN.
`
`There are primarily two kinds of signalling messages transported over the radio interface - RRC generated signalling
`messages and NAS messages generated in the higher layers. On establishment of the signalling connection between the
`peer RRC entities three or four UM/AM signalling radio bearers may be set up. Two of these bearers are set up for
`transport of RRC generated signalling messages - one for transferring messages through an unacknowledged mode RLC
`entity (see subclause 5.3.2. for details on RLC modes) and the other for transferring messages through an acknowledged
`mode RLC entity. One signalling radio bearer is set up for transferring NAS messages set to "high priority" by the
`higher layers. An optional signalling radio bearer may be set up for transferring NAS messages set to "low priority" by
`the higher layers. Subsequent to the establishment of the signalling connection zero to several TM signalling radio
`bearers may be set up for transferring RRC signalling messages using transparent mode RLC.
`
`3GPP
`
`10
`
`

`

`
`Release 7
`
`11
`
`3GPP TS 25.301 V7.1.0 (2007-03)
`
`UuS boundary
`
`L3
`
`Radio
`Bearers
`
`L2/PDCP
`
`L2/BMC
`
`GC
`
`Nt
`
`DC
`
`Duplication avoidance
`
`GC
`
`Nt
`
`DC
`
`C-plane signalling
`
`U-plane information
`
`RRC
`
`control
`
`PDCP
`
`PDCP
`
`BMC
`
`control
`control
`
`control
`
`control
`
`RLC
`
`RLC
`
`RLC
`
`RLC
`
`RLC
`
`RLC
`
`RLC
`
`RLC
`
`L2/RLC
`
` MAC
`
`PHY
`
`Logical
`Channels
`
`L2/MAC
`Transport
`Channels
`L1
`
`
`
`Figure 2: Radio Interface protocol architecture (Service Access Points marked by circles)
`
`Service access points and service primitives
`5.1.1
`Each layer provides services at Service Access Points (SAPs). A service is defined by a set of service primitives
`(operations) that a layer provides to upper layer(s).
`
`Control services, allowing the RRC layer to control lower layers locally (i.e. not requiring peer-to-peer communication)
`are provided at Control SAPs (C-SAP). Note that C-SAP primitives can bypass one or more sublayers, see Figure 2.
`
`In the radio interface protocol specifications, the following naming conventions for primitives shall be applicable:
`
`- Primitives provided by SAPs between adjacent layers shall be prefixed with the name of the service-providing
`layer, i.e. PHY, MAC, RLC, PDCP, BMC or UUS.
`
`- Primitives provided by SAPs to an application shall be prefixed with the name of the service-providing layer, i.e.
`RRC.
`
`- Primitives provided by Control SAPs, in addition to the name of the service-providing layer, shall be prefixed
`with a "C", i.e. CPHY, CMAC, CRLC, CPDCP or CBMC.
`
`This principle leads to the following notations, where <Type> corresponds to request, indication, response or confirm
`type of primitives:
`
`3GPP
`
`11
`
`

`

`
`Release 7
`
`12
`
`3GPP TS 25.301 V7.1.0 (2007-03)
`
`Primitives between PHY and MAC:
`PHY- <Generic name> - <Type>
`Primitives between PHY and RRC (over C-SAP):
`CPHY- <Generic name> - <Type>
`Primitives between MAC and RLC:
`MAC- <Generic name> - <Type>
`Primitives between MAC and RRC (over C-SAP):
`CMAC- <Generic name> - <Type>
`Primitives between RLC and upper layers, between RLC and RRC for data transfer and between RLC and PDCP:
`RLC- <Generic name> - <Type>
`Primitives between RLC and RRC for control of RLC (over C-SAP):
`CRLC- <Generic name> - <Type>
`Primitives above Uu Stratum:
`UUS- <Generic name> - <Type>
`Primitives between PDCP and non-access stratum:
`PDCP- <Generic name> - <Type>
`Primitives between PDCP and RRC (over C-SAP):
`CPDCP- <Generic name> - <Type>
`Primitives between BMC and upper layer:
`BMC- <Generic name> - <Type>
`Primitives between BMC and RRC for control of BMC (over C-SAP):
`CBMC- <Generic name> - <Type>
`In this model, some UUS primitives map directly to RLC primitives without intervening function.
`
`Layer 1 Services and Functions
`5.2
`This subclause shall provide an overview on services and functions provided by the physical layer. A detailed
`description of Layer 1 general requirements can be found in [4].
`
`L1 Services
`5.2.1
`The physical layer offers information transfer services to MAC and higher layers. The physical layer transport services
`are described by how and with what characteristics data are transferred over the radio interface. An adequate term for
`this is 'Transport Ch

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket