Umts Call Flows

Alexander SeifarthCONFIDENTIAL - DRAFTJune 1, 20051

Module 01

UE-UTRAN Signalling Protocols

Version 0.0.1 (07/02/2005)

Author: Alexander Seifarth ([email protected])


1. Network Architecture



1.1. Top Level Network Architecture


1.1. Top Level Network Architecture

UE

UTRAN

(UMTS TerrestrialRadio Access

Network)

UTRAN

(UMTS TerrestrialRadio Access

Network)

CN

(Core Network)

CN

(Core Network)

Uu Iu

Access Protocols Access Protocols

Non Access Protocols

intra-UTRANprotocols

intra-CNprotocols


1.1. Top Level Network ArchitectureUMTS inherits its top level network architecture from second generation mobile communication networks. Any UMTS network can be divided into three major network subsystems:

• UE (User Equipment): The UE is built from Mobile Equipment (ME) providing all required hard- and software to gain access to the network and a UMTS Subscriber Identity Module (USIM). In other words the UE is a 3G enabled cell phone.• UTRAN (UMTS Terrestrial Radio Access Network): The major change of UMTS compared to second generation systems like GSM is the radio access technology. Instead of the classical GSM BSS (Base Station Subsystem) using TDMA/FDMA radio access there is now UTRAN utilizing CDMA (Code Division Multiple Access). UTRAN currently comes in three different flavours – FDD mode, TDD mode and low chip rate TDD mode. (This script focuses on FDD mode).

• CN (Core Network): The core network is the same for GSM and UMTS. It is responsible to provide telecommunication services like mobility handling, circuit switched call services, packet switched data services and messaging service. The CN can be split into domains – the CS domain and the packet switched domain.

Several signalling protocols provide the communication facilities between these subsystems. To establish the basic communication links (access links) between UE-UTRAN and UTRAN-CN there are access signalling protocols between these subsystems. On the other hand for telecom services there are protocols between UE and CN for mobility management, CS call management, PDP context management, SMS, etc. These protocols belong to the so called non-access signalling protocols. These non-access protocols are exchanged between UE and CN directly. UTRAN must transparently pass signalling messages from non-access signalling protocols from UE to CN and vice versa.

Obviously there are also protocols inside UTRAN and inside CN. These are labelled intra-UTRAN or intra-CN protocols respectively.



1.2. Network Elements and Interfaces



Node B

UE

RNC

Node B

Iub

Iub

RNC

Iur

IubNode B

RNS

RNS

BSCBTS

BSS

Uu

MSC/VLRServer#1

SGSN #1

SGSN #L

MSC/VLRServer#N

. . .

. . .

CSMGW #1

CSMGW #K

Iu-CS

Iu-PS

Iu-PS

A

Gb

CS-CN

PS-CN


1.2. Network Elements and InterfacesUTRAN is composed of two different network elements:

• RNC (Radio Network Controller): The RNC is responsible for all radio management tasks inside of UTRAN. This includes channel allocation/modification/removal, handover procedures, security functions, etc.

• Node B: The Node B serves one or more cells. The tasks of the Node B is to terminated the physical layer (WCDMA FDD) and convert it to the transport protocol on the Iub interface towards RNC. In other words the Node B is a relay point. Anything above the radio physical layer must pass transparently through the Node B.

Between RNC and Node B there is the Iub interface. Its task is to transfer data (user data, signalling) between UE and RNC. Furthermore there is an optional interface Iur between two RNC. The Iur interface is related to soft handover procedures. This interface is similar to the Iub interface used for transparent transfer of data between UE and the so called serving RNC.

For the connection between UTRAN and CN there is the Iu interface defined. It comes in two different versions – Iu-CS for the connectivity between RNC and MSC (MSC server, CS Media Gateway MGW) and Iu-PS for RNC-SGSN communication. The Iu interfaces shall transfer user data (CS speech calls, CS data calls, PDP context data), non-access signalling to and from the UE and access signalling between RNC and MSC/SGSN.

Iu, Iub and Iur interfaces are currently based on ATM as transport layer technology, but also IP may be used. The IP based UTRAN is already specified.

In parallel to UTRAN the classical GSM BSS may still be used together with UTRAN. Thus the core network still provides connectivity for A and Gb interface. Note that in future releases also the GSM BSS may be based on Iu interfaces rather than the old second generation protocols.



ServingRNC

DriftRNC

SGSNMSC

ServerCS-MGW

Node B Node B Node B

UE

Drift RNC

• relay between Iurand Iub• splitting/combining function [optional]• local admission control

Serving RNC

• radio management(handover decision, channel de/allocation• NAS message relay• Iu management• backward error correction• splitting/combination function• local and global admission control

Iur

IubIubIub

Iu-PSIu-CS


1.2. Network Elements and InterfacesA UE can be in one of two states:

• IDLE: A UE in IDLE mode has no connectivity to UTRAN, in other words there is no signalling relation with an RNC and of course no radio resources are allocated for the UE.

• CONNECTED: A CONNECTED mode UE has a signalling relation with an RNC which performs all radio management tasks for this UE. This special RNC is called the serving RNC (S-RNC) for the UE. A single UE has in CONNECTED mode exactly one serving RNC, in IDLE mode there is no serving RNC for the UE.

During soft handover procedures it can happen, that a UE is connected with a cell that does not belong to the serving RNC’s area. The RNC managing this cell is called a drift RNC (D-RNC). A D-RNC must have an Iur interface to the serving RNC of the UE.

The drift RNC must not perform radio management procedures for the UE, this is task of the serving RNC. The drift RNC provides functionality to relay data between serving RNC and UE. In other words the drift RNC is a Iub/Iur relay. In some RNC equipment also functionality to combine and split data streams to/from a UE during soft handover can be provided.



1.3. UTRAN/UE Main Functional Protocols Overview


1.3. UTRAN/UE Main Functional Protocols

UE

Node B

RNC

RNC

MSC/VLRServer

SGSN

Iu-CS

Iu-PS

Uu Iub

IubUu

Iur

RRCRRC

RNSAPRNSAP

RANAPRANAP

RANAPRANAP

Iu-CSALCAPALCAP

NBAPNBAP ALCAPALCAP

ALCAPALCAP

WCDMAWCDMA

CS-MGW


1.3. UTRAN/UE Main Functional ProtocolsThere are some main functional protocols within UTRAN that implement the UMTS specific operations. These protocols are:

• RRC (Radio Resource Control): The RRC protocol is exchanged between UE and serving RNC. It provides functions for radio channel management, handover, security functions, measurements, etc.

• RANAP (Radio Access Network Application Part): RANAP is the main protocol on the Iu interfaces. MSC server and SGSN use RANAP signalling messages to allocated radio access bearers and to handle relocation of the serving RNC.

• NBAP (Node B Application Part): NBAP is the control protocol on the Iub interface. It allows the RNC to command the Node B to allocate or delete channels on the air interface, to transport Node B measurements to the RNC. Although there is a detailed specification of NBAP, most of all available UTRAN equipment implements a propriety version of NBAP.

• RNSAP (Radio Access Network Application Part): RNSAP is used on Iur interface, thus it is an open protocol. The RNSAP protocol extends the NBAP protocol, so that a serving RNC can allocate radio resources on cells owned by a drift RNC. Some other functions of RNSAP concern the relocation of the serving RNC function and packet data forwarding from old to new RNC over Iur.

The mentioned protocols RRC, NBAP, RANAP, RNSAP are UTRAN specific protocols. On Iub, Iur and Iu-CS interfaces real-time data streams will be transported. Thus before such a real-time data stream can be transferred, an appropriate transmission bearer must be allocated on the transport network, this requires another protocol:

• ALCAP (Access Link Control Application Part): The term ALCAP is a generic “placeholder” for a transport network specific control protocol to allocate transport bearers for delay sensitive data. In case of ATM-AAL2 transport network the ACLAP is the ITU-T protocol Q.2630 (AAL type 2 signalling protocol). If IP/UDP is used instead, the ALCAP is not defined, because in IP/UDP there is no resource allocation defined.


RNC

RNS

1.3. UTRAN/UE Main Functional Protocols

UE

MSC/VLRServer

SGSN

MMMM CCCC SSSS SMSSMS

GMMGMM SMSM SMSSMS PS dataPS data

CS dataCS dataCS-MGW

NAS Signalling Relay


1.3. UTRAN/UE Main Functional ProtocolsThe non-access signalling protocols between UE and MSC server/SGSN are the direct transfer application part (DTAP) protocols known from GSM/GPRS.

For the CS services there are:

• MM (Mobility Management): This protocols provides location area update, authentication, IMSI detach procedures and some others (e.g. identity request, MM information).

• CC (Call Control): Here we find mobile originated and mobile terminated call setup, local and remote call release, as well as call related supplementary services, mid-call modification and DTMF interaction.

• SS (Supplementary Services): This protocol allows to trigger non-call related supplementary services like USSD, management of call forwarding and call barring, etc.

For PS core network the following protocols are used:

• GMM (GPRS Mobility Management): This protocol defines GPRS attach, GPRS detach, routing area update, authentication, service request and some other procedures (e.g. identity request, GMM information).

• SM (Session Management): The SM protocol provides the functionality for PDP context activation, PDP context deactivation and PDP context modification.

For PS and CS core network domain the short messaging service is possible. The protocols for SMS are identical for both domains:

• SMS (Short Message Service): The SMS protocol suite consists of SM-CP (Short Message Control Protocol), SM-RP (Short Message Relay Protocol), SM-TL (Short Message Transfer Layer) and SM-AL (Short Message Application Layer).



1.4. UTRAN Protocol Stacks on Iux Interfaces


1.4. Protocol Stacks on Iux Interfaces – Iu-CSServing

RNCMSC/VLR Server

CS-MGWIu-CS (control plane)

Iu-CS (user + transport network control plane)

RANAPRANAP

ALCAPALCAPSCCPSCCP

MTP3BMTP3B

SAALSAAL SAALSAAL SAALSAAL

ATMATM

AAL2AAL2AAL2AAL2. . . . . .

PVC PVC PVC PVC PVC

MMMM CCCC SSSS SMSSMS

IuUPIuUP

IuUPIuUP

. . .IuUPIuUP

IuUPIuUP

. . .

CS call data

User PlaneTransportNetworkControlPlane

Control Plane


1.4. Protocol Stacks on Iux Interfaces – Iu-CSOn the Iu-CS interface the main functionality is to transfer CS call (speech, video, data) between RNC and CS media gateway (CS-MGW). CS user data is carried over the Iu UP (Iu User Plane) protocol from RNC to CS-MGW and vice versa. The Iu UP protocol supports codecs with multiple data rate modes like the AMR codec. Each application has its own Iu UP instance which is carried as AAL2 call inside a AAL2 virtual channel.

To allocate AAL2 calls inside a AAL2 virtual channel the establishment procedure of the ALCAP protocol (Q.2630) must be used. In the same way when the application terminates, the associated AAL2 call must be released by ALCAP’s release procedure. Thus the ALCAP protocol is required between RNC and CS-MGW.

The UMTS specific higher layer control of radio access bearers the AAL2 call belongs to the RANAP protocol is used. RANAP uses the SCCP (Signalling Connection Control Part) for virtual signalling connection between RNC and MSC server to identify a single UE.

For signalling message transfer MTP3B (Message Transfer Part level 3 Broadband) is used. This is commonly known as broadband or high speed SS7. MTP3B provides routing facilities between RNC, MSC server and CS-MGW. The transmission is done on one or more high speed SS7 signalling links. Such high speed links are provided via SAAL (Signalling ATM Adaptation Layer) protocol instances. Each SAAL represents one ATM virtual channels together with retransmission functionality to increase transmission reliability.

The non-access signalling protocol for the circuit switched side (MM, CC, SS, SMS) are carried over RANAP.


1.4. Protocol Stacks on Iux Interfaces – Iu-PSServing

RNCSGSNIu-PS (control plane, user plane)

RANAPRANAP

SCCPSCCP

MTP3BMTP3B

SAALSAAL SAALSAAL SAALSAAL

ATMATM

AAL5AAL5AAL5AAL5. . . . . .

PVC PVC PVC PVC PVC

GMMGMM SMSM SMSSMS PS call data (PDP Contexts)

User PlaneControl Plane

IPIP

UDPUDP

GTP-UGTP-U

. . .


1.4. Protocol Stacks on Iux Interfaces – Iu-PSOn Iu-PS user data consists of PDP context packets. PDP context data is transferred over the GTP-U (GPRS Tunnelling Protocol – User plane). GTP-U provides so called GTP-U tunnels which are used to identify subscriber and PDP context and to route PDP context data correspondingly. The GTP-U protocol uses IP/UDP as transport layer. The IP layer routes between RNC and SGSN. In an ATM environment IP is transmitted over one or more AAL5 virtual channels.

The control stack is similar to Iu-CS. The RANAP protocol is used between SGSN and RNC to allocate radio access bearer services for PDP contexts. There is no ALCAP on Iu-PS because AAL2 is not used here.

Obviously the non-access signalling protocols on Iu-PS are different to Iu-CS. Between RNC and SGSN we can find GMM, SM and SMS on RANAP.


1.4. Protocol Stacks on Iux Interfaces – IubRNCNode BUE Uu Iub

NBAPNBAP

ALCAPALCAP

TrCHFPTrCH

FPTrCH

FPTrCH

FPTrCH

FPTrCH

FP

SAALSAAL

ATMATM

PVC

SAALSAAL

PVC...

ALCAPALCAP...

SAALSAAL

PVC

SAALSAAL

PVC...

AAL2AAL2

PVC

AAL2AAL2

PVC...

... ...

Control Plane Transport NetworkControl Plane

User Plane

Transport Channel Data


1.4. Protocol Stacks on Iux Interfaces – IubOn the Iub interface data (user data and signalling) to and from the UE must be transported transparently. This UE-RNC is data is transferred in form of so called transport channels TrCH. Each transport channel is carried over Iub in a Frame Protocol (FP). Each such frame protocol FP uses a single AAL2 call inside a AAL2 virtual channel as transport resource.

To allocate a AAL2 call for a frame protocol instance, again the ALCAP protocol is required. The ALCAP is carried over a single SAAL ATM virtual channel. Dependent on the RNC/Node B vendor also one or several ALCAP instances might be used on Iub.

The main protocol on Iub, the NBAP protocol, may also be split into several parts. Again this depends on the equipment vendor. Thus one or more SAAL ATM virtual channels are required to transfer NBAP messages over the Iub interface.


1.4. Protocol Stacks on Iux Interfaces – IurDrift RNCNode BUE Uu Iub

RNSAPRNSAP TrCHFPTrCH

FPTrCH

FPTrCH

FPTrCH

FPTrCH

FP

SAALSAAL

ATMATM

PVC

SAALSAAL

PVC

ALCAPALCAP

SAALSAAL

PVC...

AAL2AAL2

PVC

AAL2AAL2

PVC...

... ...

Control Plane TransportNetwork

Control Plane

User Plane

Transport Channel Data

Serving RNCIur

SCCPSCCP

MTP3BMTP3B


1.4. Protocol Stacks on Iux Interfaces – IurThe Iur interface is comparable to Iub with two differences. First instead of NBAP the RNSAP protocol is used. The second difference is that RNSAP and ALCAP use broadband SS7 for transfer and routing of signalling messages between serving RNC and drift RNC.


2. Radio Protocol Architecture and Channels



2.1. Radio Protocol Architecture


2.1. Radio Protocol Architecture

WCDMA Physical Layer (FDD)WCDMA Physical Layer (FDD)#1 #2 #n

Medium Access Control (MAC)Medium Access Control (MAC)

Transport Channels (TrCH)

Physical Channels (PhCH)#1 #k

RF

#1 #x #y #z

RLCRLC RLCRLC... RLCRLC RLCRLC...

#y2

RLCRLC

BMCBMCPDCPPDCP

#1 #x #y #z#y2

RRCRRC...

MMMM GMMGMM SMSM CCCC SSSS SMSSMS

NAS Protocols CSApp

CSApp

PSPDP Ctx.

PSPDP Ctx.

CBSMSApp

CBSMSApp

#y1

RLCRLC

#y1

Logical Channels (LogCH)

Radio Bearer (RB)

...

...

RAB RAB


2.1. Radio Protocol ArchitectureThe UMTS radio protocol architecture as it is implemented in the UE has the following protocols:

• WCDMA Physical Layer: The physical layer offers bit transport services in form of so called transport channel TrCH. To transmit TrCH data over the air the physical layer has access to physical channels PhCH. A PhCH represents the physical resource and is identified by frequency, scrambling code and channelization code (plus some additional parameters for certain channels).

• Medium Access Control (MAC): MAC protocol has the task to include or check UE identifiers on transport channels that are shared between several UE (common transport channels). The transport services are offered to higher layers in form of logical channels LogCH. Thus the MAC also has to multiplex and demultiplex logical channels onto or from transport channels.

• Radio Link Control (RLC): To each logical channel there is one RLC instance. The RLC belongs to a single radio bearer (RB) which represents the transmission resource for a layer 3 application (codec, RRC protocol, PDP context). The RLC protocol offers reliability in form of sequence numbering and backward error correction. Typically one RLC belongs to one logical channel, but for acknowledged mode one RLC instance can also utilize two logical channels.

• Packet Data Convergence Protocol (PDPC): This protocol is applicable for radio bearers belonging to PDP contexts only. The protocol performs IP header compression and optionally also IP datagram numbering.

• Broadcast Multicast Control (BMC): This protocol exists only for cell broadcast SMS radio bearer. This protocol contains the scheduling messages and the basic CB SMS frames.

• Radio Resource Control (RRC): The main signalling protocol for radio resource management.

For a single application one or more radio bearers have to be allocated. For user applications all radio bearers of a single application are combined in a radio access bearer (RAB).



2.2. Logical Channel Types and their Usage



UE Identification in UTRAN

ServingRNC

Node BUE Uu Iub

No UE IdentificationNo UE Identification

Layer 1 IdentificationLayer 1 Identification



Case UE Identification in RNC

Some information (System Information, CB SMS) does not require a UE identification.

UE must have a dedicated physical resource. This resource uniquely identifies the UE for the time the resource is assigned to it.

UE uses common resources and identifies itself with a special MAC header identifier (c-RNTI, u-RNTI, dsch-RNTI) on that resource.

UE has no dedicated resource and no assigned MAC header identifier, but uses common resources (RRC signalling only). The RRC message must contain a UE identifier as layer 3 parameter.



BCCHBCCH

PCCHPCCH

CCCHCCCH

DCCHDCCH

DTCHDTCH

CTCHCTCH

Logical Channel Types

Control Channels

Traffic Channels

Broadcast Control Channel[dl, ptm]

System Information broadcast; downlink channel;no UE specific information

Paging Control Channel[dl, ptm]

Point-to-multipoint paging procedure (Paging Type 1) UE identification by RRC message itself

Common Control Channel[ul+dl, ptp]

Point-to-point RRC signalling on common resource when no MAC identifier available

Dedicated Control Channel[ul+dl, ptp]

Point-to-point RRC signalling on common or dedic. resource with MAC identifier available (on common resource)

Dedicated Traffic Channel[ul|dl|ul+dl, ptp]

Point-to-point data (CS data, CS speech, PS data) on common or dedicated resource (requires MAC-ID on common resource).

Common Traffic Channel[dl (currently), ptm] Used for cell broadcast SMS. Thus no UE-ID.

ptm: point-to-multipointptp: point-to-pointdl: downlinkul: uplink


2.2. Logical Channel Types and their UsageFor FDD mode the following logical channel types are defined:

• BCCH (Broadcast Control Channel): The BCCH carries the cell’s system information, which are RRC messages (System Information Blocks, Master Information Block). The BCCH is not associated with a radio bearer.

• PCCH (Paging Control Channel): The PCCH carries RRC messages ‘Paging Type 1’. This message type is used to page a UE or to indicate system information changes. Like the BCCH there is no radio bearer associated with the PCCH.

• CCCH (Common Control Channel): The CCCH is a bi-directional RRC signalling channel where layer 3 identification is required. The UE uses CCCH signalling at the beginning of communication when no DCCH is available. Only radio bearer RB 0 is attached to CCCH. RB 0 is configured via system information, because it works as a start up point.

• DCCH (Dedicated Control Channel): The normal bi-directional RRC signalling and also rate control signalling is exchanged on a DCCH. Every DCCH is associated with its own radio bearer which must be configured via explicit RRC signalling from RNC to UE. On DCCH only layer 1 or layer 2 identification is allowed.

• DTCH (Dedicated Traffic Channel): CS call data (speech, video, data) as well as PDP context data is carried over DTCH. Like for DCCH also on DTCH layer 1 or layer 2 identification is required, layer 3 identification is not possible.

• CTCH (Common Traffic Channel): This channel type is currently used for cell broadcast SMS (CB SMS) only.

It should be obvious that any DTCH or CTCH requires an associated radio bearer. Such radio bearers are granted via RRC procedure from the RNC to the UE.



2.3. Transport Channel Types and their Usage


2.3. Transport Channel Types and their UsageNode B

UE

UE

WCDMA FDD cell

dedicatedphysical

channels

commonphysicalchannel

Dedicated TrCHDedicated TrCH

UE



Common TrCHCommon TrCH

Common TrCHCommon TrCH

Common TrCH

• mapped onto shared physical resources• multiple UE can be assigned to same physical resource• requires Layer 2 identification for DCCH, DTCH• requires Layer 3 identification for CCCH, PCCH [opt]

Dedicated TrCH

• mapped onto dedicated physical resources• only one UE can use the physical resource• automatically provides Layer 1 identification for the UE assigned to the channel• used with DCCH and DTCH


2.3. Transport Channel Types and their Usage 1

BCHBCH

PCHPCH

RACHRACH

FACHFACH

Transport Channel Types

Common Channels

Broadcast Channel[dl, 1/cell]

Carries BCCH.

Paging Channel[dl, ≦16/cell] Carries PCCH.

Random Access Channel[ul, ≦16/cell]

Can carry CCCH, DCCH and DTCH. Minimum SF is 32 and maximum transmission time is 10|20 ms.

Forward Access Channel[dl, ≦16/cell] Can carry CCCH, DCCH, DTCH, BCCH and CTCH.

Minimum SF is 4.

dl: downlinkul: uplink

DSCHDSCH

CPCHCPCH

HS-DSCHHS-DSCH

Downlink Shared Channel[dl, ≦?/cell]

Common Packet Channel[ul, ≦64/cell]

High Speed DSCH[dl, ≦16/cell]

Carries DCCH and DTCH. A DSCH is always used together with one or more DCH.

Carries DCCH and DTCH. Minimum SF is 4 and maximum transmission time is 80 ms.

Carries DCCH and DTCH. Can switch between QPSK and 16QAM on physical channel.


2.3. Transport Channel Types and their Usage 2

DCHDCH

Transport Channel Types

Dedicated Channels

Dedicated Channel[ul|dl]

One DCH can carry one or more DCCH or one DCH can carry one or more DTCH.


2.3. Transport Channel Types and their UsageA single transport channel has a certain characteristics that describes how bits are transmitted over the air interfaces. This concerns bit rate, delay and reliability. A special characteristics is whether the associated physical channel used for transport channel data transmission is dedicated to a single UE or must be shared between several UE. This means that we have two groups of transport channels – dedicated TrCH and common TrCH.

Common transport channels are created during cell setup or O&M triggered cell reconfiguration. In UMTS FDD mode we have the following common transport channels:

• BCH (Broadcast Channel): There is exactly one BCH per cell and it is used to carry BCCH. The format of a BCH is fixed by specification so that any UE camping on a cell can read the BCH.

• PCH (Paging Channel): A PCH carries PCCH. A cell may have up to 16 PCH by specification. A UE selects a PCH depending on subscriber identity.

• RACH (Random Access Channel): The random access channel is used to carry CCCH, DCCH, DTCH in the uplink. In case of CCCH any UE in the cell can freely access the RACH, for DCCH/DTCH a UE has to get permission from the RNC to do so. Especially it is so that for DCCH/DTCH on RACH the UE needs a temporary identifier (C-RNTI) for layer 2 identification.

• FACH (Forward Access Channel): The FACH is the downlink response channel to the RACH. It is used to carry CCCH, DCCH, DTCH, CTCH and BCCH. For DCCH/DTCH on FACH the already mentioned C-RNTI is required. Note that there is no fixed timing relationship between transmission on RACH and reception on FACH. Rather a UE that uses RACH/FACH the FACH must be monitored permanently.

• CPCH (Common Packet Channel): The CPCH is working like the RACH, but is used for DCCH and DTCH only. Compared to the RACH the CPCH allows higher bit rates and longer transmission periods – thus a higher throughput can be achieved on CPCH.


2.3. Transport Channel Types and their Usage• DSCH (Downlink Shared Channel): The downlink shared channel shall be used for packet data in the downlink. The channel allows multiplexing of DCCH/DTCH of several UE using time and code multiplexing mechanisms. This shall increase resource usage efficiency.

• HS-DSCH (High Speed Downlink Shared Channel): This channel is one of the new features in UMTS Release 5. TheHS-DSCH has the same function like the normal DSCH. DCCH/DTCH of several UE shall be multiplexed – again time and code multiplexing is used. The special thing is, that the physical resource allocation and the multiplexing is handled at the Node B, not at the RNC. Furthermore the associated physical channel allows switch between QPSK and 16QAM.

In contrast to this the dedicated transport channels which are assigned to a single UE will be created and deleted during normal operation using NBAP/RNSAP- and RRC-procedures. There is only one dedicated transport channel type defined:

• DCH (Dedicated Channel): The dedicated channel carries either several (or one) DCCH or several (or one) DTCH. Obviously several logical channels on a DCH belong to the same UE. Thus the DCH is the only case where layer 1 identification is in use. A UE can have several DCH simultaneously. A single DCH is either uplink or downlink.



2.4. Physical Channels and their Usage


2.4. Physical Channels and their Usage 1

P-SCHP-SCH

S-SCHS-SCH

P-CPICHP-CPICH

Physical Channel Types

Synchronisation Channels

Primary Synchr. Channel[dl, 1/cell]

Transmits Primary Synchr. Code (PSC) to detect cell.

Secondary Synchr. Channel[dl, 1/cell]

Transmits a Secondary Synchr. Code sequence to identify scrambling code group and radio frame start.

Primary Common Pilot CH[dl, 1/cell] Transmits a pre-defined symbol sequence (all –1)

with the primary dl scrambling code of the cell.


S-CPICHS-CPICH

P-CCPCHP-CCPCH

Secondary CPICH[dl, 0...15/cell]

Primary Common ControlPhysical Channel[dl, 1/cell]

Transmits a pre-defined symbol sequence with one the 15 possible secondary scrambling codes of cell.

Carries BCH with BCCH. Always scrambled by primarydl scrambling code of the cell.

Measurement Reference Channels

System Information Broadcast



S-CCPCHS-CCPCH

PICHPICH

PRACHPRACH


PhCH for FACH and PCH

Secondary CommonControl Physical Channel[dl, ≦ 16/cell]

Carries either 1) FACH only, 2) PCH only or 3) FACH + PCH multiplexed.

Paging Indicator Channel[dl, ≦ 16/cell]

Contains paging indicators for discontinuous reception (DRX) in association with a PCH.

Physical Random AccessChannel[ul, ≦ 16/cell]

Consists of a preamble part to perform open looppower control and a data part transferring RACH data.


AICHAICHAcquisition IndicatorChannel[dl, ≦ 16/cell]

Associated with a single PRACH. Carries the preamble responses (acquisition indications).

PhCH for RACH



DPCHDPCH

DPCCHDPCCH

PDSCHPDSCH


PhCH for DCH

Dedicated Physical Channel[dl, dynamical allocation]

Carries one or several DCH of a single UE and physical layer information (TPC, pilot bits, TFCI).Data rate ≦1860 kpbs (SF=4). [Physical channel bit rate]

Dedicated Physical Ctrl CH[ul, dynamical allocation][ 1/UE]

Carries physical layer information from a single UE to Node B (TPC, pilot bits, TFCI, FBI). SF=256 fix.

Physical Downlink SharedChannel[dl, dynamical allocationof codes]

Carries a DSCH with DCCH/DTCH of several UE multiplexed by time and channelization codes. Data rate ≦ 1920 kbps (SF=4).[Physical channel bit rate]


DPCHDPCHDedicated Physical Channel[dl, dynamical allocation]

A PSDCH must be used by together with DPCH by a UE. The DPCH contains physical layer control bits.

PhCH for DSCH

DPDCHDPDCHDedicated Physical Data CH[ul, dynamical allocation][≦6/UE]

Carries one or several DCH of a single UE to Node B.Data rate ≦ 960 kpbs (SF=4). [Physical channel bit rate]



PCPCHPCPCH

AP-AICHAP-AICH

CSICHCSICH


PhCH for CPCH

Physical Common PacketChannel[ul]

Carries CPCH with DCCH/DTCH of several UE multiplexed by time (asynchronous) and CPCH access preambles, collision detection preambles and power control preambles. Data rate ≦960 kpbs (SF=4) for max. 80 ms.

Access PreambleAcquisition Indicator CH[dl]

Gives positive or negative acquisition indications to CPCH access preambles for CPCH access preambles.

CPCH Status Indicator CH[dl]

Gives status indications about availability/non-availability of CPCH resources.


CD/CA-ICHCD/CA-ICHCollision Detection/Channel AssignmentIndicator Channel[dl]

Gives collision indications or channel assignment indications (code alloc.) for CPCH collision preambles.

DPCHDPCH Dedicated Physical CH[dl]

Carries physical layer control bits (TPC) used for closed loop power control of PCPCH.



HS-PDSCHHS-PDSCH

HS-SCCHHS-SCCH


PhCH for HS-DSCH

High Speed PhysicalDownlink Shared Channel[dl, ≦ 15/cell]

Carries a HS-DSCH with DCCH/DTCH of several UE. Fixed spreading factor 16. Up to 15 HS-PDSCH may be used in parallel. Can switch between QPSK and 16QAM.Single HS-PDSCHData rate =960 kpbs (16QAM) and =480 kbps (QPSK).

HS-DSCH relatedShared Control Channel[dl, ≦4 per HS-DSCH]

On this channel the physical layer assigns a UE theHS-PDSCH for the next transmission period.


HS-DPCCHHS-DPCCH Dedicated Physical CH[ul, 1 per UE on HS-DSCH]

Transmits quality indicator (C/I) and acknowledgements for received data on HS-PDSCH from UE to Node B.



2.5. Radio Bearers (RB) and Radio Access Bearers (RAB)


2.5. RB and RAB - Architecture

RB 1 RRC

RB 2

RB 3RB 4

RRC

AMR

RB 5

RB 6RB 7RB 8

Ratecontrol

Iu UP

UE ServingRNC

RAB subflow 1RAB subflow 2RAB subflow 3

MSCServer

CS-MGW

Iu UP

AMR

ABC

A B C

SGSN

PDPCtx.

1RB 9

PDPContext 1

RAB (CS)

RAB (PS)

RAB (PS)

PDPCtx.

2

PDPContext 2


2.5. RB and RAB - ArchitectureTransmission resources for telecommunication services in UMTS are handled on several levels – each network subsystem is responsible for its own resources. This allows to handle transmission resources on different time scales.

As shown in the section about the radio protocol architecture within UTRAN each application uses one or more so called Radio Bearers (RB). Radio bearers are used for signalling (RRC protocol messages, rate control signalling) as well as for user data applications (CS calls, PDP contexts). But user data applications have to be terminated by the core network. Thus for each active application the core network establishes one so called Radio Access Bearer (RAB). A RAB can be considered as a virtual transmission resource between UE and CN.

Depending on the application a single RAB can utilize one or more radio bearers. For PDP contexts it is even possible to have a RAB without radio bearer. Note that a PDP context can be active with and also without radio access bearer. The SGSN removes or reallocates the RAB by timer supervision. Whereas the radio bearers are removed and reallocated by the RNC also by timer supervision.


2.5. RB and RAB – RRC Radio Bearer Usage

RRCRRC

MACMAC

PHYPHY

MMMM GMMGMM SMSM CCCC SSSS SMSSMS

NAS Protocols

high prioritysignalling transfer

low prioritysignalling transfer

RB 0

RLC(UL:TM; DL:UM)

CCCH

RB 1

RLC(UL/DL:UM)

DCCH 1

RB 2

RLC(UL/DL:AM)

DCCH 2

RB 3

RLC(UL/DL:AM)

DCCH 3

RB 4

RLC(UL/DL:AM)

DCCH 4

UL-TrCHDL-TrCH


2.5. RB and RAB – RRC Radio Bearer UsageThe RRC protocol has to use radio bearers for the transmission of its signalling messages.

The very first radio bearer RB 0 is special, because it is configured via system information (BCCH) and acts as a start up item for signalling. RB 0 is always mapped to CCCH and is thus found on RACH and FACH.

For normal signalling (DCCH) there are RB 1, RB 2, RB 3 and RB 4. RB 1 and RB 2 are used for radio management procedures only, whereas RB 3 and RB 4 are to be used for non-access signalling (CN procedures). The difference between RB 1 and RB 2 is the mode of the associated RLC protocol instance. RB 1 is always running with unacknowledged mode, RB 2 always uses acknowledged mode.

RB 3 and RB 4 have to use acknowledged mode, their difference is the priority. RB 3 is for high priority CN signalling (MM, GMM, SM, CC, SS). In contrast to that RB 4 is for low priority signalling (SMS).



2.6. Channel Configuration Scenario


DL

2.6. Channel Configuration Scenario

RB 1

UM

DCCH 1

RB 2

AM

DCCH 2

RB 3

AM

DCCH 3

RB 4

AM

DCCH 4

RB 5

TM

DTCH 1

RB 6

TM

DTCH 2

RB 7

TM

DTCH 3

RB 8

TM

DCCH 5

RB 9

UM|AM

DTCH 5

PDCP

RLC

RRCRRC

MM, GMM, CC, SS, SM, SMSMM, GMM, CC, SS, SM, SMSAMR codecAMR codec PDP Ctx.PDP Ctx.

MAC

DCH #31DCH#0

DCH#1

DCH#2

DCH#3

DCH#4

A B C frameheader

PHY

UE with one variable rate AMR CS call, 1 PDP context (active data transfer)

DPCH DPCCH DPDCH UL


2.6. Channel Configuration ScenarioThe scenario shown here presents the configuration of a UE in UTRA connected mode with two services running:• one AMR speech call with variable bit rate,• one PDP context with active data transfer.

The UE uses several radio bearers RB1, …, RB4 for RRC signalling. Obviously these radio bearers are DCCH. For the AMR codec also four radio bearers are required. RB 5, …, RB 7 carry the encoded speech data in form of the codec’s A, B and C bits. Every 20 ms the codec produces one set of A, B and C bits. Together with the codec frame header which are mapped to RB 8 they form the AMR codec frame. The frame header is essential for rate control of AMR codecs. For the PDP context there is at most one radio bearer RB 9 required. RB 5, 6, 7 and 9 are mapped to DTCH, whereas the radio bearer RB 8 for the AMR codec frame header is DCCH.

All RRC signalling radio bearers RB 1, …, RB 4 are multiplexed onto the same DCH (UL-DCH + DL-DCH). RB 5, 6, 7 and 8 belong to the codec but require different reliability settings. Thus they are mapped each to their own DCH (UL/DL). The same is true for the PDP context’s radio bearer RB 9, it also gets its own DCH.

On the physical layer all DCH can be multiplexed to a single DPDCH in the uplink and a DPCH in the downlink. If the data rate exceeds the capacity of single DPDCH or DPCH, several physical channels might be used in parallel.


Module 02

Radio Layer 2 Protocols MAC, RLC, PDCP

Version 0.0.1 (10/02/2005)



1. Transport Channel Configuration



1.1. Transport Formats (TF) and Transport Format Sets (TFS)


1.1. TF and TFS – Transport Blocks and Format

MACMAC PHYPHYTrCH x

Transport Block TB #0

Transport Block TB #1

Transport Block TB #N-1

. . .

Transport Block Set TBS

Transport BlockSet TBS



time

Transmit TimeInterval TTI

Transmit TimeInterval TTI

Transport Format (TF)channel coding algorithm

CRC size

rate matching attribute

TTI

TB size (no. of bits)

TBS size (no. of TB in TBS)


1.1. TF and TFS – Transport Format Sets

channel coding algorithm

CRC size

rate matching attribute

TTI TFI 0

TB size #0

TBS size #0

TFI 1

TB size #1

TBS size #1

TFI K-1

TB size #K-1

TBS size #K-1. . .

Transport Format Set (TFS)

| 1.1.1.1.9 ul-AddReconfTransChInfoList || 1.1.1.1.9.1 uL-AddReconfTransChInformation ||-----0-- |1.1.1.1.9.1.1 ul-TransportChannelType |dch ||***b5*** |1.1.1.1.9.1.2 transportChannelIdentity |32 || 1.1.1.1.9.1.3 transportFormatSet || 1.1.1.1.9.1.3.1 dedicatedTransChTFS || 1.1.1.1.9.1.3.1.1 tti || 1.1.1.1.9.1.3.1.1.1 tti40 || 1.1.1.1.9.1.3.1.1.1.1 dedicatedDynamicTF-Info || 1.1.1.1.9.1.3.1.1.1.1.1 rlc-Size || 1.1.1.1.9.1.3.1.1.1.1.1.1 octetModeType1 ||***b5*** |1.1.1.1.9.1.3.1.1.1.1.1.1.1 sizeType1 |16 || 1.1.1.1.9.1.3.1.1.1.1.2 numberOfTbSizeList || 1.1.1.1.9.1.3.1.1.1.1.2.1 numberOfTransportBlocks || |1.1.1.1.9.1.3.1.1.1.1.2.1.1 zero |0 || 1.1.1.1.9.1.3.1.1.1.1.3 logicalChannelList || |1.1.1.1.9.1.3.1.1.1.1.3.1 allSizes |0 |


1.1. TF and TFS – Transport Format Sets

| 1.1.1.1.9.1.3.1.1.1.2 dedicatedDynamicTF-Info || 1.1.1.1.9.1.3.1.1.1.2.1 rlc-Size || 1.1.1.1.9.1.3.1.1.1.2.1.1 octetModeType1 ||10000--- |1.1.1.1.9.1.3.1.1.1.2.1.1.1 sizeType1 |16 || 1.1.1.1.9.1.3.1.1.1.2.2 numberOfTbSizeList || 1.1.1.1.9.1.3.1.1.1.2.2.1 numberOfTransportBlocks || |1.1.1.1.9.1.3.1.1.1.2.2.1.1 one |0 || 1.1.1.1.9.1.3.1.1.1.2.3 logicalChannelList || |1.1.1.1.9.1.3.1.1.1.2.3.1 allSizes |0 || 1.1.1.1.9.1.3.1.2 semistaticTF-Information || 1.1.1.1.9.1.3.1.2.1 channelCodingType ||1------- |1.1.1.1.9.1.3.1.2.1.1 convolutional |third ||***b8*** |1.1.1.1.9.1.3.1.2.2 rateMatchingAttribute |185 ||-011---- |1.1.1.1.9.1.3.1.2.3 crc-Size |crc16 |


1.1. TF and TFS – Transport Format SetsEach transport channel has to be configured with a set of transport characteristics that control the data transmission within the channel.

Data transmission within a transport channel is organized in so called transport blocks (TB). A single transport block TB contains data from one logical channel. Zero, one or more of these transport blocks (also from different logical channels) are assembled in a single transport block set (TBS). One TBS has to be transmitted every transmission time interval (TTI), which can be 10 ms, 20 ms, 40 ms or 80 ms.

The configuration of a single transport channel has to configure the TTI, TB size (bits or octets) and TBS size (in number of transport blocks). Every transport block TB gets in the physical layer its own cyclic redundancy check (CRC). The size of the CRC (CRC Size) which can be 0 bits, 8 bits, 12 bits, 16 bits or 24 bits, is a transport channel configuration parameter too. The transport blocks together with their CRC are channel coded with either a ½ convolutional coding, 1/3 convolutional coding or a 1/3 turbo coding. The type of channel coding is also part of the TrCH configuration parameter.

A problem of code division multiple access using OVSF channelization code tree is that the number of bits after channel coding must be adapted to the physical layer frame size. This task is performed by the rate matching function. When too many bits are coming from the channel encoder a puncturing algorithm will be used to reduce the number of bits, when too less bits are available some bits will be repeated. The rate matching algorithm is configured with a single rate matching attribute.

These parameters: TB size, TBS size, TTI, CRC size, Channel Coding and Rate Matching Attribute form a so called transport format (TF). A single TBS is transmitted with exactly one TF. Several transport formats TF can be configured in parallel for a single transport channel. All TF of a TrCH are called transport format set (TFS). The physical layer’s architecture requires that all TF of a TFS have the same settings for TTI, CRC size, Channel Coding and Rate Matching Attribute.

Whenever a new TrCH shall be created it is the RNC that allocates a TFS for it. The TFS is sent to Node B via NBAP signalling. The UE gets the TFS either via System Information (BCCH) or via explicit RRC signalling on a CCCH or DCCH.



1.2. Transport Format Combinations TFC


TFS (TrCH 1)

1.2. Transport Format Combinations TFC

MACMAC

PHYPHY

TrCH 1 TrCH 2TFI 0

TFI 1

TFI 2

TFI 0

TFI 1

TFS (TrCH 2)

0 kbps

8 kbps

0 kbps

16 kbps

32 kbps

TrCH 1 TrCH 2TFCI Total TrCH Bit Rate

TFI 0 TFI 1

TFI 0 TFI 2

TFI 0TFI 0

TFI 1 TFI 0

TFI 1 TFI 2

TFI 1TFI 1

0

1

2

3

blocked

blocked

16 kbps

32 kbps

0 kbps

8 kbps

40 kbps

24 kbps


1.2. Transport Format Combinations TFCA UE can use several transport channels simultaneously. Each transport channel has its own set of transport formats assigned. This means at every time instant every transport channel transmits a TBS using a certain transport format.

A set of one transport format for every configured transport channel is a transport format configuration (TFC). Which transport format combinations TFC are permitted is indicated by the RNC to the UE. One major function that uses TFC restrictions is the admission control, because in the end effect each TFC is associated with a certain required transmission power.


2. Medium Access Control MAC



2.1. MAC Entities


2.1. MAC Entities

MAC-b

NBAP

MAC-c/sh

MAC-d

MAC-b

MAC-c/sh

MAC-d

NBAP

MAC-d

MAC-hs MAC-hsHS-DSCH

DCH

RACH, FACH,DSCH, CPCH,PCH

BCH

UE RNCNode B


2.1. MAC EntitiesThe MAC protocol is split into several entities:

• MAC-b: This entity is responsible for broadcasting the system information downlink. The system information is assembled by the RNC at sent via NBAP messages to the Node B. From here the MAC-b sends this information periodically in the cell.

• MAC-c/sh: MAC-c/sh has to manage all common transport and shared logical channels. For DCCH/DTCH on common transport channels this includes identification of the UE with help of special UE identifiers contained in the MAC header.

• MAC-d: For DCH as well as DCCH/DTCH the MAC-d entities are responsible.

MAC-b and MAC-c/sh are created once per cell, whereas MAC-d is available inside the UE and the serving RNC for each UE. For high speed downlink packet access a new MAC entity is introduced:

• MAC-hs: This entity manages the high speed downlink shared channel HS-DSCH. It is implemented in the Node B and gets its data input from MAC-d (serving RNC) directly or indirectly via MAC-c/sh (drift RNC). MAC-hs is especially responsible to perform the scheduling of downlink packet data.



2.2. MAC – PDU, LogCH Identification, UE Identificationon Layer 2


2.2. MAC-PDU, UE/LogCH Identification

MAC-dMAC-d

DCH #N

PHYPHY

DCH case:

DxCH#0

DxCH#1

DxCH#K-1

. . .TB #0 (MAC-PDU #0)

TB #1 (MAC-PDU #1)

TB #L-1 (MAC-PDU #L-1)

. . .


MACHeader

MAC-SDU = LogCH Data(RLC PDU)

MAC - PDU

DxCH – number (if K>1)

x = T(raffic) | C(ontrol)



MAC-c/shMAC-c/sh

RACH |FACH |DSCH |CPCH

PHYPHY

Common TrCH (RACH, FACH, DSCH, CPCH) case:

CCCH BCCH|CTCH

DxCH#K-1

. . .TB #0 (MAC-PDU #0)

TB #1 (MAC-PDU #1)

TB #L-1 (MAC-PDU #L-1)

. . .


MACHeader


MAC - PDU

DxCH – number (if K>1)

x = T(raffic) | C(ontrol)

DxCH#0

UE-identifier (for DxCH only)

LogCH Type

from MAC-d



Common TrCH (HS-DSCH) case:

MAC-dMAC-d

HS-DSCH

PHYPHY

DxCH#0

DxCH#1

DxCH#K-1

. . .

MAC-hsMAC-hs

MAC-d Flow

DxCH – number (if K>1)LogCH Type

MACHeader


MAC-d - PDU

MAC-dPDU #0

MAC-dPDU #M-1

. . .MAC-hsHeader

MAC-hs PDU


2.2. MAC-PDU, UE/LogCH IdentificationTwo major functions are provided by MAC protocol: • explicit UE identification on common transport channels,• multiplexing of logical channels onto/from transport channels.

On a DCH the MAC frame provides in its header the DCCH or DTCH logical channel number if more than one logical channel is multiplexed onto the DCH.

On common transport channels like RACH, FACH, DSCH, FACH or CPCH the MAC header indicates the type of logical channel that the transport block carries, the UE identity if the logical channel is DCCH or DTCH and if more than one logical channel of the same UE and of the same type is contained the logical channel number.

For high speed downlink packet access a single UE can get one or more so called MAC-d flows on Iub interface. Each MAC-d flow corresponds to a so called re-ordering queue. The MAC-d PDU indicates to which logical channel (DTCH) the data belongs to. On the air interface the MAC-hs entity assembles several MAC-d PDU of the same user and bundles them in a MAC-hs PDU. In the MAC-hs PDU the re-ordering queue identity and a sequence number (for retransmission purposes) is contained. Furthermore size indicators for the contained MAC-d PDU are implemented into the MAC-hs PDU.


2.2. MAC-PDU, UE/LogCH Identification• MAC-PDU (non HS-DSCH)

TCTF UE-IDType UE-ID C/T

MAC Header

RLC PDU (LogCH Data)

• MAC-d PDU (for HS-DSCH)

C/T

MAC Header

RLC PDU (LogCH Data)

MAC SDU

MAC SDU

• MAC PDU (HS-DSCH)

MAC-hs Header

MAC Header MAC-hs SDUs

MAC-d PDU#0

MAC-d PDU#1

MAC-d PDU#N-1

. . .

VersionFlag

QueueID

Seq.No.TSN

Size IndexId. #0

No. MAC-dPDUs #0 Flag #0 Size Index

Id. #YNo. MAC-dPDUs #Y Flag #Y. . .



UE

U-RNTI (32 bit)U-RNTI (32 bit)

MAC header UE identifier

C-RNTI (16 bit)C-RNTI (16 bit)

DSCH-RNTI (16 bit)DSCH-RNTI (16 bit)

RNC

MAC PDU

-- (no MAC UE ID)-- (no MAC UE ID) • UE uses CCCH/PCCH/BCCH/CTCH orDCH/HS-DSCH

• UE uses DCCH/DTCH on RACH/FACH in a new cell

• UE uses DCCH/DTCH on RACH/FACH/ CPCH (not after cell change)

• UE uses DCCH/DTCH on DSCH

= S-RNC-ID + S-RNTI


2.2. MAC-PDU, UE/LogCH Identification• TCTF (Target Channel Type Field): Indicates logical channel type that is carried in the MAC header.

• UE-ID/UE-ID type: Identifies a UE on common transport channels for DCCH or DTCH. The UE-ID can be u-rnti (umts –radio network temporary identifier), c-rnti (cell-rnti) or dsch-rnti. These identifiers must be allocated for a UE via RRC signalling before their use.

• C/T (Channel of Type): If several logical channels of the same type are multiplexed onto the same transport channel, this field is used to distinguish and therefore demultiplex them.

The following information elements are used in HS-DSCH frames only:• Version Flag: Currently always set to zero. May be used to allow MAC-hs extensions in future.

• Queue ID: Indicates which re-ordering queue inside the UE the data belongs to. This enables independent buffer management for data of different applications.

• TSN (Transmission Sequence Number): Sequence number for re-ordering purposes in case of disordering or re-transmission.

• SID (Size Index Identifier): Identifies the size of a number of consecutive MAC-d PDU (see next field). The SID is dynamically configured via higher layer signalling and is independent for each re-ordering queue.

• Number of MAC-d PDU: Indicates the number of consecutive MAC-d PDU with the same SID.

• Flag: If 0 then another SID fields follows, if 1 then the MAC-d PDU part starts after the flag.



| 2.2 FP: Transport Block ||0011---- |2.2.1 MAC: C/T Field |Logical Channel 4 || |2.2.2 MAC: Target Channel Type |DCCH (Dedicated Control Channel) || |2.2.3 MAC: RLC Mode |Acknowledge Mode ||----0--- |2.2.4 RLC: Data/Control |Control PDU ||-----000 |2.2.5 RLC: PDU Type |STATUS || |2.2.6 RLC: Acknowledgement Super Field ||0010---- |2.2.6.1 RLC: SUFI Type |Acknowledgement ||**b12*** |2.2.6.2 RLC: Last Sequence Number |2 || |2.2.7 RLC: Padding ||**b124** |2.2.7.1 RLC: Padding |'000000000000000000000000000000000'B || | |'000000000000000000000000000000000'B || | |'000000000000000000000000000000000'B || | |'0000000000000000000000000'B |

• Example: MAC-PDU (Transport Block) DCCH on DCH



| 2 FP: Transport Block ||01------ | 2.1 MAC: Target Channel Type Field |DTCH/DCCH (Dedicated Traffic/Cont... ||--01---- | 2.2 MAC: UE-ID Type |C-RNTI (Cell Radio Network Tempor... ||**b16*** | 2.3 MAC: UE-ID |0 ||----0010 | 2.4 MAC: C/T Field |Logical Channel 3 || | 2.5 MAC: RLC Mode |Acknowledge Mode ||1------- | 2.6 RLC: Data/Control |Acknowledged mode data PDU ||**b12*** | 2.7 RLC: Sequence Number |1 ||-----1-- | 2.8 RLC: Polling Bit |Request a status report ||------01 | 2.9 RLC: Header extension type |Octet contains LI and E bit ||0001010- | 2.10 RLC: Length Indicator |10 ||-------1 | 2.11 RLC: Extension Bit |The next field is LI and E bit ||1111111- | 2.12 RLC: Length Indicator |Rest is padding ||-------0 | 2.13 RLC: Extension Bit |The next field is data ||**B10*** | 2.14 RLC: Last Data Segment |94 02 08 00 18 00 11 88 10 00 ||***B4*** | 2.15 RLC: Padding |00 00 00 00 |

• Example: MAC-PDU (Transport Block) DCCH on FACH


2.2. MAC-PDU, UE/LogCH IdentificationThe two examples show a trace made on Iub interface. They contain MAC PDU on non-high speed channels.

The first example shows a transport block on DCH. There is no UE-ID because a DCH is already identifying a UE uniquely. Also there is no TCTF, because on a DCH there can be either DCCH or DTCH but not mixed.

The second example shows a transport block on FACH. The TCTF indicates that DCCH is transported, thus a UE-ID is required to assign the dedicated data to a UE. In this case the c-rnti is used.



2.3. RACH Access Control


2.3. RACH Access Control – Basic Procedure 1(3)

UE RNCNode B

Uu Iub

MAC PHY PHY MAC

Acess.Request[PHY]

R=random (0≤R<1)IF (R ≤ P)

TRUE

Wait 10 ms

FALSE

START P = Persistence Value (SIB 7)M = Preamble Cycle Counter (UE counter)

AccessPreamblePHY:PRACH



. . .

1st Preamble Cycle

Case: No acquisition indication1) maximum no. of preambles2) maximum power on PRACH

NoAck.Indication[PHY]

M= 1



UE RNCNode B

Uu Iub

MAC PHY PHY MAC

Acess.Request[PHY] AccessPreamblePHY:PRACH


AI = -1PHY:AICH

2nd Preamble Cycle

Case: Negative acquisition indication

NAck.Indication[PHY]


TRUE

Wait 10 ms

FALSE

M:=M+1

Wait 10 ms



UE RNCNode B

Uu Iub

MAC PHY PHY MAC

Acess.Request[PHY] AccessPreamblePHY:PRACH

AI = +1PHY:AICH

3rd Preamble Cycle

Case: Positive acquisition indication

Ack.Indication[PHY]


TRUE

Wait 10 ms

FALSE

M:=M+1

NBO1=random{0 ≤ NBO1min ≤ NBO1 ≤ NBO1max}Wait TBO1 (= NBO1 x 10 ms)

Wait 10 msNBO1min = minimum value for backoff timer 1 (SIB)NBO1max = maximum value for backoff timer 1 (SIB)

Data.Request[PHY] RACH DataPHY:PRACH RACH DATARACH-FP


2.3. RACH Access Control – Basic ProcedureThe MAC layer is in control of the PRACH preamble cycles. This means the MAC layer has to trigger PRACH preamble cycles and to handle negative outcomes of this procedure.

Whenever a data transmission on RACH shall be done the MAC layer will first of all generate a random number R and compare it against a so called persistence value P. The persistence value P is coming from system information SIB 7, a block generated by the Node B itself. If the number R is bigger than P (R>P) then the MAC layer will wait 10 ms and generate a new random number. If R is less or equal to P then the physical layer can start a random number. By decreasing P the Node B can reduce the number of UE that will simultaneously access the RACH.

When a preamble cycle ends without an indication from the Node B, then the MAC layer will wait another 10 ms and restart the preamble cycle (of course with random number and persistence check first) again.

When a preamble cycle ends with a negative indication from the Node B, then again the MAC layer has to wait 10 ms. But afterwards the backoff 1 timer (T_BO1) is started with a time N_BO1 x 10 ms. N_BO1 is a random number that lies within the range N_BO1min and N_BO1max. These limits are BCCH parameters. When T_BO1 has its time out, then another preamble cycle including persistence check is done.

Both negative cases (no indication, negative indication) will be aborted when the maximum number of preambles (BCCH parameter) is exceeded.

In case the preamble cycle is positive, then the RACH data will be transmitted.


3. Radio Link Control (RLC) Protocol



3.1. RLC Modes of Operation



Transparent ModeTM

Transparent ModeTM

Unacknowledged ModeUM

Unacknowledged ModeUM

Acknowledged ModeAM

Acknowledged ModeAM

RLC ModesRLC Modes

• no sequence numbercheck• no acknowledgements• no retransmission

• segmentation/reassembly may be used or not used

• no RLC overhead

• sequence number check• no acknowledgements• no retransmission

• segmentation/reassembly is done in RLC

• sequence number and length indicators included in RLC frame

• sequence number check• acknowledgements• retransmission

• segmentation/reassembly is done in RLC

• sequence number and length indicators included in RLC frame + RLC control messages required

MAC Header

RLC SDU(Data)

cipherunit

MAC Header

RLC SDU(Data)

cipherunit

RLC Seq. No.

Length Indicators

MAC Header

RLC SDU(Data or Ctrl)

cipherunit

RLC Seq. No.

Length Indicators


3.1. RLC Modes of OperationThe RLC protocol is used to enhance the reliability of a single radio bearer. Thus there is one instance of RLC protocol per radio bearer available. Each RLC instance can be set in one of three modes independent of each other:

• Transparent Mode (TM): In transparent mode there is no additional reliability provided by the RLC protocol instance. Only segmentation and reassembly functions might be used. There is no RLC overhead included in this mode. Ciphering is done over the whole RLC SDU.

• Unacknowledged Mode (UM): In unacknowledged mode there is at least a sequence number check provided by RLC. This is used to ensure correct reassembly. Thus there are sequence numbers and length indicators for reassembly control n the RLC frame. Ciphering is done over the whole RLC PDU except the sequence number.

• Acknowledged Mode (AM): In acknowledged mode the RLC protocol instance provides acknowledgements and retransmission functionality. The RLC PDU contains now sequence number, length indicators for reassembly control and RLC status messages for retransmission control. Ciphering is done over the whole RLC PDU except the sequence number.

Which mode is used is configured by the RNC during radio bearer setup procedure. Thus the UE is told via RRC signalling which RLC mode to use on a radio bearer.

It is possible to combine TM and UM on the same radio bearer. This can be done by assigning uplink and downlink different modes. It is not possible to combine AM with another mode, because for acknowledgements always uplink and downlink direction must be used simultaneously in AM.



PCCH

BCCH

CCCH-UL

DCCH

DTCH

CTCH

TM

TM

TM

CCCH-DL UM

TM UM AM

TM UM AM

UM

RLC ModesLogCH Type



3.2. Segmentation/Reassembly Function


3.2. Segmentation/Reassembly Function

MACMAC

RLCRLC

Layer 3 (RRC, applic.)Layer 3 (RRC, applic.)

PHYPHY

RLC SDU #0 RLC SDU #1

#0.0 #0.1 #1.0 #1.1 paddingRLCheader

RLCheader

RLCheader

RLC PDU #0 RLC PDU #1 RLC PDU #2

MACheader #0.0RLC

header

Transport Block Set

MACheader #0.1RLC

header #1.0

MACheader #1.1RLC

header padding


3.2. Segmentation/Reassembly FunctionNext to the enhanced reliability functions provided by RLC there is another task done by this protocol – segmentation and reassembly. The RLC protocol instances have to segment higher layer data so that a transport block of an appropriate size corresponding to the available transport formats can be formatted.

The RLC protocol can perform segmentation together with concatenation (several RLC SDU or segments of an RLC SDU in one RLC PDU) and padding. The RLC protocol has been designed for maximum resource efficiency.

In unacknowledged and acknowledged mode the RLC protocol includes length indicators in its PDU to indicate the end of an higher layer frame (RLC SDU). Sometimes the length indicators can also carry special control meaning.

In transparent mode such length indicators are not used. Rather the RLC protocol reassembles everything that comes in the same transport blocks. This might not be exactly the inverse of the segmentation process in transparent mode. Therefore segmentation and reassembly is usually switched off when transparent mode is used. The higher layers have then to send frame of correct size to match the transport block sizes.



3.3. RLC Transparent Mode Procedures


3.3. RLC Transparent Mode Procedures

UE RNC

TMD PDURLCRLC SDU segments


.

.

.

IF all segments of a SDUreceived

reassembly



.

.

.


reassembly


3.3. RLC Transparent Mode Procedures| 2 FP: Transport Block ||00------ |2.1 MAC: Target Channel Type Field |CCCH (Common Control Channel) || |2.2 MAC: RLC Mode |Transparent Mode ||**b166** |2.3 RLC: Whole Data |'001000010000011101000000001000011'B || | |'010000000100110001000000001000000'B || | |'111110100110110000000000000000000'B || | |'000000000000000000000000000000000'B || | |'000000000000000000000000000000000'B || | |'0'B |

segmentedSDU data

RLC Transparent Mode DATA


3.3. RLC Transparent Mode ProceduresIn transparent mode there is only the data transfer procedure defined. It is implemented via the TMD PDU (Transparent Mode Data). The TMD PDU contains nothing else data from higher layers, no RLC control information is to be found.



3.4. Unacknowledged Mode Procedures



UE RNC

UMD PDURLCSequence No. = 2, Length Indicators, RLC SDU segments


.

.

.


reassembly



.

.

.


reassembly


3.4. Unacknowledged Mode Procedures| 2 FP: Transport Block ||01000000 |2.1 MAC: Target Channel Type Field |CCCH (Common Control Channel) || |2.2 MAC: RLC Mode |Unacknowledge Mode ||0101010- |2.3 RLC: Sequence Number |42 ||-------1 |2.4 RLC: Extension Bit |The next field is LI and E bit ||1111100- |2.5 RLC: Length Indicator |Start with new SDU ||-------0 |2.6 RLC: Extension Bit |The next field is data ||**B18*** |2.7 RLC: First Data Segment |30 f7 36 c0 00 04 24 c4 02 00 18... || 3 FP: Transport Block ||01000000 |3.1 MAC: Target Channel Type Field |CCCH (Common Control Channel) || |3.2 MAC: RLC Mode |Unacknowledge Mode ||0101011- |3.3 RLC: Sequence Number |43 ||-------0 |3.4 RLC: Extension Bit |The next field is data ||**B19*** |3.5 RLC: Data Segment |49 d3 e2 84 f8 ea 30 00 14 61 67... |

| 2 FP: Transport Block ||01000000 |2.1 MAC: Target Channel Type Field |CCCH (Common Control Channel) || |2.2 MAC: RLC Mode |Unacknowledge Mode ||0101100- |2.3 RLC: Sequence Number |44 ||-------0 |2.4 RLC: Extension Bit |The next field is data ||**B19*** |2.5 RLC: Data Segment |92 13 e5 a9 40 00 52 8a 13 a7 cd... || 3 FP: Transport Block ||01000000 |3.1 MAC: Target Channel Type Field |CCCH (Common Control Channel) || |3.2 MAC: RLC Mode |Unacknowledge Mode ||0101101- |3.3 RLC: Sequence Number |45 ||-------0 |3.4 RLC: Extension Bit |The next field is data ||**B19*** |3.5 RLC: Data Segment |d3 e8 84 fa 6a 90 00 15 08 00 06... |


3.4. Unacknowledged Mode Procedures| 2 FP: Transport Block ||01000000 |2.1 MAC: Target Channel Type Field |CCCH (Common Control Channel) || |2.2 MAC: RLC Mode |Unacknowledge Mode ||0101110- |2.3 RLC: Sequence Number |46 ||-------0 |2.4 RLC: Extension Bit |The next field is data ||**B19*** |2.5 RLC: Data Segment |04 80 11 dc 32 00 01 04 13 f7 eb... || 3 FP: Transport Block ||01000000 |3.1 MAC: Target Channel Type Field |CCCH (Common Control Channel) || |3.2 MAC: RLC Mode |Unacknowledge Mode ||0101111- |3.3 RLC: Sequence Number |47 ||-------1 |3.4 RLC: Extension Bit |The next field is LI and E bit ||0001110- |3.5 RLC: Length Indicator |14 ||-------1 |3.6 RLC: Extension Bit |The next field is LI and E bit ||1111111- |3.7 RLC: Length Indicator |Rest is padding ||-------0 |3.8 RLC: Extension Bit |The next field is data ||**B14*** |3.9 RLC: Last Data Segment |ba dd fc 80 64 53 ca 08 00 40 8c... ||***B3*** |3.10 RLC: Padding |00 00 00 |



Sequence Number E

• UMD PDU (7-bit Length Indicators)

LI0 E

LIN-1 E=0

. . .

segmentedRLC SDU

padding

Sequence Number E

• UMD PDU (15-bit Length Indicators)

LI0 (low part) E

LIN-1 E=0

. . .

segmentedRLC SDU

padding

LI0 (high part)

LIN-1 (high part)


3.4. Unacknowledged Mode ProceduresIn unacknowledged mode there is also only one frame defined, the UMD PDU (Unacknowledged Mode Data PDU). It is used to carry RLC SDU or segments of RLC SDU between UE and RNC.

To enable faithful segmentation and reassembly, length indicators are used to point to the end of the last segment of a RLC SDU. This means a length indicator is to be found whenever a UMD PDU contains the last (or the only one) segment of a RLC SDU. In some situations special length indicators will be included that have control meaning (e.g. reset of reassembly etc.).

Length indicators can be either 7 bit long or 15 bit long. It depends on the largest UMD PDU (transport block size – MAC header size) in the associated transport channel. If the maximum UMD PDU size is less or equal 125 bytes, then 7 bit length indicators shall be used, otherwise 15 bit length indicators have to be included in the UMD PDU.

For detection of lost RLC PDU there is a 7 bit long sequence number included in every UMD PDU. If an UMD PDU is lost, then all RLC SDU with segments in this UMD PDU are discarded by the receiver.



3.5. Acknowledged Mode Procedures



UE RNC

RESET PDURLCReset Sequence Number, Hyper Frame Number uplink (HFNI)

RESET ACK PDURLC

Reset

Reset Sequence Number, Hyper Frame Number downlink (HFNI)

RESET PDURLCReset Sequence Number, Hyper Frame Number downlink (HFNI)

RESET ACK PDURLCReset Sequence Number, Hyper Frame Number uplink (HFNI)



UE RNC

AMD PDURLCSequence No. = 12, Poll Bit P, Length Indicators, RLC SDU segments

AMD PDURLC

.

.

.

Data Transfer with Solitary STATUS PDU

Sequence No. = 18, Poll Bit P, Length Indicators, RLC SDU segments

STATUS PDURLCAcknowledgement super fields (SUFI): ACK, BITMAP, LIST, RLIST


AMD PDURLC

.

.

.Sequence No. = 18, Poll Bit P, Length Indicators, RLC SDU segments

STATUS PDURLCAcknowledgement super fields (SUFI): ACK, BITMAP, LIST, RLIST



UE RNC


AMD PDURLC

.

.

.

Data Transfer with Piggybacked STATUS PDU

Sequence No. = 18, Poll Bit P, Length Indicators, RLC SDU segments

AMD PDURLCSequence No. = 34, Poll Bit P, Length Indicators, RLC SDU Segments,Piggybacked STATUS PDU = {Acknowledgement super fields (SUFI): ACK, BITMAP, LIST, RLIST}


AMD PDURLC

.

.

.Sequence No. = 28, Poll Bit P, Length Indicators, RLC SDU segments

AMD PDURLCSequence No. = 39, Poll Bit P, Length Indicators, RLC SDU Segments,Piggybacked STATUS PDU = {Acknowledgement super fields (SUFI): ACK, BITMAP, LIST, RLIST}


3.5. Acknowledged Mode ProceduresMove Receiving Window ProcedureUE RNC

STATUS PDURLCMove Receiving Window (MRW) super field: SN1,...SNK

STATUS PDURLCMove Receiving Window Ack (MRWACK) super field

STATUS PDURLCMove Receiving Window (MRW) super field: SN1,...SNK

STATUS PDURLCMove Receiving Window Ack (MRWACK) super field


3.5. Acknowledged Mode ProceduresWindowsize ConfigurationUE RNC

STATUS PDURLCWindow (WINDOW) super field: window size

STATUS PDURLCWindow (WINDOW) super field: window size


3.5. Acknowledged Mode ProceduresIn acknowledged mode there some more procedures defined. In detail we have

• Reset: The Reset procedure is used to recover after errors in acknowledged mode. A new HFNI (Hyper Frame Number Indicator) for ciphering can be allocated at Reset procedure. The RESET PDU and RESET ACK PDU are defined for this procedure.

• Data Transfer with solitary STATUS PDU: For data transfer the AMD (Acknowledged Mode Data) PDU is defined. It carries a 12 bit long sequence number. A single AMD or a series of AMD PDU can be acknowledged by a stand-alone acknowledgement in form of a STATUS PDU.

• Data Transfer with piggybacked STATUS PDU: Very often AMD PDU are exchanged in both directions. In this case it is possible to include STATUS PDU in AMD PDU for acknowledgements. This simply is more efficient with respect to bandwidth usage.

• Move Receiving Window: In some situations an AMD PDU is transmitted and retransmitted correctly. This situation can be determined by thresholds (maximum number of retransmissions) or timers (maximum time for data transmission). Either an error is the result or both sides agree to skip the problematic AMD PDU. For skipping (discarding) the Move Receiving Window procedure is used. In a STATUS PDU the command to move the receiving window with the sequence numbers of the AMD PDU to be discarded are indicated. An acknowledgement completes the procedure.

• Window Size: The RLC protocol uses acknowledgements that acknowledges several AMD PDU with one message. The maximum number of AMD PDU that can be sent without acknowledgement is indicated in the window size procedure. A STATUS PDU contains a window size field in which the limit is indicated.


3.5. Acknowledged Mode Procedures| 2.2 FP: Transport Block ||0010---- |2.2.1 MAC: C/T Field |Logical Channel 3 || |2.2.2 MAC: Target Channel Type |DCCH (Dedicated Control Channel) || |2.2.3 MAC: RLC Mode |Acknowledge Mode ||----1--- |2.2.4 RLC: Data/Control |Acknowledged mode data PDU ||**b12*** |2.2.5 RLC: Sequence Number |2 ||-1------ |2.2.6 RLC: Polling Bit |Request a status report ||--01---- |2.2.7 RLC: Header extension type |Octet contains LI and E bit ||***b7*** |2.2.8 RLC: Length Indicator |9 ||---1---- |2.2.9 RLC: Extension Bit |The next field is LI and E bit ||***b7*** |2.2.10 RLC: Length Indicator |Rest is padding ||---0---- |2.2.11 RLC: Extension Bit |The next field is data ||**b72*** |2.2.12 RLC: Last Data Segment |df d9 4c ed 0d 21 31 f1 10 ||**b40*** |2.2.13 RLC: Padding |00 00 00 00 00 |

| 2.2 FP: Transport Block ||0010---- |2.2.1 MAC: C/T Field |Logical Channel 3 || |2.2.2 MAC: Target Channel Type |DCCH (Dedicated Control Channel) || |2.2.3 MAC: RLC Mode |Acknowledge Mode ||----0--- |2.2.4 RLC: Data/Control |Control PDU ||-----000 |2.2.5 RLC: PDU Type |STATUS || |2.2.6 RLC: Acknowledgement Super Field ||0010---- |2.2.6.1 RLC: SUFI Type |Acknowledgement ||**b12*** |2.2.6.2 RLC: Last Sequence Number |3 || |2.2.7 RLC: Padding ||**b124** |2.2.7.1 RLC: Padding |'000000000000000000000000000000000'B || | |'000000000000000000000000000000000'B || | |'000000000000000000000000000000000'B || | |'0000000000000000000000000'B |



Sequence Number (high part)D/C(1)

• AMD PDU (7-bit Length Indicators)

LI0 E

LIN-1 E=0

. . .

segmentedRLC SDU

Padding| piggybacked STATUS PDU

• AMD PDU (15-bit Length Indicators)

LI0 (low part) E

LIN-1 E=0

. . .

segmentedRLC SDU

padding

LI0 (high part)

LIN-1 (high part)

HEPSeq.Number (low part)

Sequence Number (high part)D/C(1)

HEPSeq.Number (low part)



D/C(0)

• RESET/RESET ACK PDU

HFNI

HFNI

padding

padding

PDU TYPE0 0 1 / 0 1 0 RSN reserved

HFNI

D/C(0)

• STATUS PDU

PDU TYPE0 0 0 SUFI #1

SUFI #1. . .

SUFI #N

padding

Note: In case of a piggybacked STATUS PDUthe D/C bit is reserved.


3.5. Acknowledged Mode ProceduresSuper Fields (SUFI)

0 0 0 0NO_MORE

0 0 1 0ACK

LSN high

LSN low

0 0 0 1WINDOW

WSN high

WSN low

0 0 1 1LIST

LENGTH

SN1 high

SN1 low L1. . .

SNLENGTH high

SNLENGTH low LLENGTH

0 1 0 0BITMAP

LENGTH

FSN high

FSN low BITMAP. . .

BITMAP Padding

0 1 0 1RLIST

LENGTH

FSN high

FSN low CW1

. . .CWLENGTH padding

0 1 1 0MRW

LENGTH

SN1 high

SN1 low

. . .SNLENGTH high

SNLENGTH low NLENGTH

SN2 high

SN2 high

0 1 1 1MRW_ACK

SNACK low

NLENGTH

SNACK high

Padding


3.5. Acknowledged Mode ProceduresAMD PDU have a similar format like UMD PDU. The sequence of length indicators is used to control reassembly. Each length indicator points to the end of the last segment of a RLC SDU. Furthermore some special length indicator values are reserved (e.g. whether a STATUS PDU is carried within the AMD PDU or not, etc.). Again there are 7 bit long length indicators and 15 bit long length indicators. If the maximum AMD PDU size is less or equal to 126 octets then 7 bit long length indicators shall be used, otherwise 15 bit length indicators are chosen.

The sequence number of AMD PDU is 12 bit long to enable bigger window size for acknowledgements. The poll bit P is used to request immediate acknowledgement for a AMD PDU.

STATUS PDU contain one or more so called super fields SUFI. Each SUFI carries special acknowledged mode control meaning for acknowledgements, window size negotiation, moving receiving window. The following SUFI types are known:

• No More: Indicates end of the STATUS PDU.

• ACK: A simple acknowledgement. Indicates the next expected AMD PDU sequence number (LSN: last sequence number).

• LIST: Indicates gaps of the reception of AMD PDU. Each gap is indicated by its start sequence number (SN: start number) and its length (L:length). Up to 15 gaps can be indicated in a single LIST super field.

• BITMAP: Indicates positive or negative acknowledgement for a series of consecutive AMD PDU with a bitmap. The first bit of the bitmap stands for AMD PDU with sequence number FSN (FSN: first sequence number). The second bit of the bitmap is for FSN+1, and so on. When the bit is ‘0’ the associated AMD PDU is negatively acknowledged.

• MRW/MRW_ACK: Used to move the receiving window. Inside the MRW field each AMD PDU to be discarded is indicated by its sequence number SN.

• RLIST: A relative list used to indicate gaps in the reception. The method to specify the gap is different to LIST super field. In a RLIST special code words CW are used to calculate gap start and length.


Module 03

Radio Resource Control Signalling(RRC)

Version 0.0.1 (21/03/2005)



1. System Information



1.1. System Information Blocks and Segmentation


1.1. System Information Blocks and Segments

UE RNC

SystemInformation (SI)[BCH:BCCH] RRCSFNPrime (INTEGER 0…4094 step 2), Segment Combination = CHOICE { Combination 1: no data |Combination 2: first segment |Combination 3: subsequence segment |Combination 4: last segment |Combination 5: last segment, first segment |Combination 6: last segment, complete list = {complete block#0, …, complete block#N} |Combination 7: last segment, complete list = {complete block#0, …, complete block#N}, first segment |Combination 8: complete list = {complete block#0, …, complete block#N} |Combination 9: complete list = {complete block#0, …, complete block#N}, first segment |Combination10: complete SIB of size 215…226 |Combination11: last segment of size 215…226 }

firstsegment

subsequentsegment

subsequentsegment

lastsegmentSystem Information Block (SIB): . . .


1.1. System Information Blocks and SegmentsSignalling on the BCCH is done by means of the RRC System Information. On the BCH that carries the BCCH there is only RLC transparent mode used. Thus the RRC protocol must provide its own sequence numbering and segmentation functionality.

For segmentation of System Information Blocks (SIB) the RRC protocol defines the System Information (SI) message. In each SI message one or more segments of a SIB or several SIB can be contained. Several combinations allow to indicate first, last and subsequent segments, or to bundle several complete blocks in one SI message.

Additionally to the SIB segments the SI message also indicates the cell time via the System Frame Number (0..4095). The SFN is translated into the SFN prime via th following rule. In each frame with even SFN (SFN mod 2 = 0) it holds SFN prime = SFN. In radio frames with odd SFN (SFN mod 2 = 1) we have SFN prime = SFN-1. In other words the SFN prime is increased with every second radio frame by 2.



1.2. Master and Scheduling Information Blocks



UE RNC

MasterInformationBlock (MIB)[BCH:BCCH] RRCMIB value tag, supported PLMN types = GSM-MAP|ANSI-41|GSM-MAP+ANSI-41,PLMN identity = MCC + MNC, ANSI-41-CN information,references to other system information blocks = { SIB Type, value tag, scheduling }

MasterInformationBlock (MIB)[BCH:BCCH] RRC

80 ms

MIB value tag, supported PLMN types = GSM-MAP|ANSI-41|GSM-MAP+ANSI-41,PLMN identity = MCC + MNC, ANSI-41-CN information,references to other system information blocks = { SIB Type, value tag, scheduling }

MasterInformationBlock (MIB)[BCH:BCCH] RRC

80 ms

MIB value tag, supported PLMN types = GSM-MAP|ANSI-41|GSM-MAP+ANSI-41,PLMN identity = MCC + MNC, ANSI-41-CN information,references to other system information blocks = { SIB Type, value tag, scheduling }

Master Information Block (MIB)

Alexander Seifarth

Durchstreichen

Alexander Seifarth

Eingefügter Text

2



UE RNC

SchedulingInformationBlock1/2[BCH:BCCH] RRCreferences to other system information blocks = { SIB Type, value tag, scheduling }

[BCH:BCCH] RRC

repetitionrate given

in MIB

references to other system information blocks = { SIB Type, value tag, scheduling }

[BCH:BCCH] RRC

Scheduling Information Block (SchIB1/2)

SchedulingInformationBlock1/2


in MIB

references to other system information blocks = { SIB Type, value tag, scheduling }SchedulingInformationBlock1/2

Alexander Seifarth

Durchstreichen

Alexander Seifarth

Eingefügter Text

2


1.1. Master and Scheduling Information Blocks| |masterInfoBlock (= masterInfoBlock) || |sib_description || |1 sib_choice || |1.1 masterInfoBlock ||-001---- |1.1.1 mib-ValueTag |2 || |1.1.2 plmn-Type || |1.1.2.1 gsm-MAP || |1.1.2.1.1 plmn-Identity || |1.1.2.1.1.1 mcc ||***b4*** |1.1.2.1.1.1.1 digit |2 ||--0110-- |1.1.2.1.1.1.2 digit |6 ||***b4*** |1.1.2.1.1.1.3 digit |2 || |1.1.2.1.1.2 mnc ||---0000- |1.1.2.1.1.2.1 digit |0 ||***b4*** |1.1.2.1.1.2.2 digit |9 || |1.1.3 sibSb-ReferenceList || |1.1.3.1 schedulingInformationSIBSb || |1.1.3.1.1 sibSb-Type ||***b8*** |1.1.3.1.1.1 sysInfoType1 |44 || |1.1.3.1.2 scheduling || |1.1.3.1.2.1 scheduling || |1.1.3.1.2.1.1 segCount |1 || |1.1.3.1.2.1.2 sib-Pos ||***b6*** |1.1.3.1.2.1.2.1 rep128 |6 || |1.1.3.2 schedulingInformationSIBSb || |1.1.3.2.1 sibSb-Type ||------01 |1.1.3.2.1.1 sysInfoType2 |2 |...

Master Information Block MIB

Alexander Seifarth

Durchstreichen

Alexander Seifarth

Eingefügter Text

2


1.1. Master and Scheduling Information BlocksThe individual system information blocks in the RRC protocol divide the information into groups. Two blocks have special meaning: the master information block and the scheduling information blocks.

In the master information block MIB the PLMN type (GSM-MAP or ANSI-41) is indicated. For GSM-MAP the PLMN identity (MCC + MNC) is broadcasted also in the MIB. Then for every further system information block the MIB indicates scheduling information and a value tag (except SIB 7). The value tag indicates changes of the associated SIB by incremented value.

The master information block always starts at radio frames with SFN mod 8 = 0.

Alexander Seifarth

Durchstreichen

Alexander Seifarth

Eingefügter Text

2



1.3. System Information Blocks (SIB)



UE RNC

SIBx[BCH:BCCH] RRCSIBx data

[BCH:BCCH] RRC


in MIB

SIBx data

[BCH:BCCH] RRC

SIBx


in MIB

SIBx dataSIBx

General System Information Transmission



UE RNC

SIB1[BCH:BCCH] RRCCN common GSM-MAP NAS info = LAC, CS domain system info = {periodic LAU timer T3212, ATT flag},PS domain system info = {RAC, Network Mode of Operation NMO},UE timers and constants in idle mode, UE timers and constants in connected mode

SIB2[BCH:BCCH] RRCURA-ID list = URA#1,.., URA#<maxURA>

SIB3[BCH:BCCH] RRCSIB4 indicator = true|false, cell identity, cell selection and re-selection info, cell access restriction

SIB4[BCH:BCCH] RRCcell identity, cell selection and re-selection info, cell access restriction



UE RNC

SIB5[BCH:BCCH] RRCSIB6 indicator = true|false, PICH power offset, AICH power offset, secondary CCPCH system info,primary CCPCH info = Tx diversity indicator, PRACH system information list, CBS DRX level 1 information

SIB6[BCH:BCCH] RRCPICH power offset, AICH power offset, secondary CCPCH system info, CBS DRX level 1 information,primary CCPCH info = Tx diversity indicator, PRACH system information list

SIB7[BCH:BCCH] RRCUL interference, dynamic persistence level for PRACH in SIB5/6, expiration time factor

SIB8[BCH:BCCH] RRCCPCH parameters (UE access parameters), CSICH power offset, CPCH set info (code and resource info)

SIB9[BCH:BCCH] RRCCPCH persistence levels



UE RNC

SIB10[BCH:BCCH] RRCDRAC (dynamic resource allocation) system information

SIB11[BCH:BCCH] RRCSIB12 indicator = true|false, FACH measurement occasion info = {measurement cycle length info, IF/IRAT measurement indicators}measurement control system information = {HCS indicator, cell selection/re-selection quantity,neighbour cell list SF/IF/IRAT, traffic volume measurements}

SIB12[BCH:BCCH] RRCFACH measurement occasion info = {measurement cycle length info, IF/IRAT measurement indicators}measurement control system information = {HCS indicator, cell selection/re-selection quantity,neighbour cell list SF/IF/IRAT, traffic volume measurements}

SIB13|SIB13.1|SIB13.2|SIB13.3|SIB13.4[BCH:BCCH] RRCANSI-41 CN information



UE RNC

SIB14[BCH:BCCH] RRC3.84 Mcps TDD mode system information

SIB15|SIB15.1|SIB15.2|SIB15.3|SIB15.4|SIB15.5[BCH:BCCH] RRCsystem information for UE positioning

SIB16[BCH:BCCH] RRCpre-defined RB/TrCH/PhCH configuration for inter-system handover to UTRAN

SIB17[BCH:BCCH] RRC3.84 Mcps TDD|1.28 Mcps TDD mode system information

SIB18[BCH:BCCH] RRCPLMN identities for neighbour cells for idle|connected mode UE



| |sibType1 (= sibType1) || |sib_description || |1 sib_choice || |1.1 sibType1 ||**b16*** |1.1.1 cn-CommonGSM-MAP-NAS-SysInfo |00 18 || |1.1.2 cn-DomainSysInfoList || |1.1.2.1 cN-DomainSysInfo ||0------- |1.1.2.1.1 cn-DomainIdentity |cs-domain || |1.1.2.1.2 cn-Type ||**b16*** |1.1.2.1.2.1 gsm-MAP |01 01 ||-----01- |1.1.2.1.3 cn-DRX-CycleLengthCoeff |7 || |1.1.2.2 cN-DomainSysInfo ||-------1 |1.1.2.2.1 cn-DomainIdentity |ps-domain || |1.1.2.2.2 cn-Type ||**b16*** |1.1.2.2.2.1 gsm-MAP |08 01 ||----01-- |1.1.2.2.3 cn-DRX-CycleLengthCoeff |7 || |1.1.3 ue-ConnTimersAndConstants ||----1010 |1.1.3.1 t-301 |ms2000 ||010----- |1.1.3.2 n-301 |2 ||---1100- |1.1.3.3 t-302 |ms4000 |...|--001--- |1.1.3.22 t-317 |s10 || |1.1.4 ue-IdleTimersAndConstants ||***b4*** |1.1.4.1 t-300 |ms1000 ||-011---- |1.1.4.2 n-300 |3 ||----1010 |1.1.4.3 t-312 |10 ||000----- |1.1.4.4 n-312 |s1 |

System Information Block SIB1


2. RRC Connection Handling

2.1. RRC States


2.1. RRC States

CELL_DCHCELL_DCH CELL_FACHCELL_FACH

URA_PCHURA_PCH CELL_PCHCELL_PCH

UTRA IDLEUTRA IDLE


2.1. RRC StatesTo manage radio resources of a UE in UMTS a state system with respect to the RRC protocol is introduced. In general a UE has two main states – UTRA Idle and UTRA Connected. The difference between idle and connected is that in connected mode there is a serving RNC for the UE, whereas in idle mode there is no serving RNC. Note that a connected mode UE can have radio resources allocated or not. In idle mode a UE cannot have radio resources.

To make a more detailed specification of a connected mode UE there are four sub-states defined for connected mode:

• CELL_DCH: In this state the UE uses DCH for signalling and might use additional DCH or DSCH for applications. The UE is subject to soft and hard handover procedures in this state.

• CELL_FACH: In this state the UE listens to FACH for RRC signalling and uses RACH on the uplink side. Also CPCH might be in use. Mobility is handled in this state via cell reselection, handover procedures like in CELL_DCH state are not used.

• CELL_PCH: Here the UE has currently no radio resources allocated. Thus the UE waits for incoming paging messages on the PCH. The UE executes cell reselection, the RNC knows the current serving cell of the UE.

• URA_PCH: This state is similar to CELL_PCH, only this time the RNC knows the current URA (UTRAN Registration Area) of the UE and not the cell.

In CELL_FACH, CELL_PCH and URA_PCH the UE performs automatic cell reselection. Thus the RNC has to be updated whenever the area of interest (cell for CELL_FACH and CELL_PCH, URA for URA_PCH) changes.


2.1. RRC States – Cell Reselection in CELL_FACHUE RNC

TMD Cell Update[RACH:CCCH] RLC/RRCU-RNTI, STARTCS, STARTPS, cell update cause = cell re-selection , measured results on RACH, …

CELL_FACH

automaticcell reselection

UMD Cell Update Confirm[FACH:CCCH] RLC/RRCU-RNTI, new U-RNTI, new C-RNTI, new DSCH-RNTI, new H-RNTI, RRC state indicator = state_X, CN info, RB to reconfigure or delete, TrCH-UL to add/reconfigure/delete, TrCH-DL to add/reconfigure/delete, uplink/downlink physical resources

State_X

. . .


2.1. RRC States – Cell Reselection in CELL_PCHUE RNC

TMD Cell Update[RACH:CCCH] RLC/RRCU-RNTI, STARTCS, STARTPS, cell update cause = cell re-selection , measured results on RACH, …

CELL_PCH


UMD Cell Update Confirm[FACH:CCCH] RLC/RRCU-RNTI, new U-RNTI, new C-RNTI, new DSCH-RNTI, new H-RNTI, RRC state indicator = state_X, CN info, RB to reconfigure or delete, TrCH-UL to add/reconfigure/delete, TrCH-DL to add/reconfigure/delete, uplink/downlink physical resources

State_X

. . .

CELL_FACH


2.1. RRC States –URA Reselection in URA_PCHUE RNC

TMD URA Update[RACH:CCCH] RLC/RRCU-RNTI, STARTCS, STARTPS, URA update cause = URA re-selection

URA_PCH


UMD URA Update Confirm[FACH:CCCH] RLC/RRCU-RNTI, new U-RNTI, new C-RNTI, new DSCH-RNTI, new H-RNTI, RRC state indicator = state_X, CN info, RB to reconfigure or delete, TrCH-UL to add/reconfigure/delete, TrCH-DL to add/reconfigure/delete, uplink/downlink physical resources

State_X. . .

CELL_FACH

(new cell is not part of old URA) falseURA_PCH

true


2.1. Mobility Handling in CELL_FACH, CELL_PCH and URA_PCHWhen a UE reselects a cell in CELL_FACH state, it has to perform a CELL UPDATE procedure afterwards in the new cell. The CELL UPDATE message contains the current UE identifier (U-RNTI), so that the RNC can identify the UE. The message is sent on RACH via CCCH. Thus the associated response CELL UPDATE CONFIRM is returned to the UE on the FACH, also CCCH. In this message the UE is assigned a new state or again CELL_FACH.

A similar procedure is done when a UE reselects a cell in CELL_PCH state. The only difference to the update procedure in CELL_FACH is, that after the cell reselection the UE enters automatically CELL_FACH state and then sends CELL UPDATE to the RNC. With the CELL UPDATE CONFIRM the UE is sent to a new state or back to CELL_PCH.

In case the UE reselects a cell in URA_PCH state then another procedure is done. First of all the UE checks whether the new cell still belongs to the old URA. If this is true no update procedure will be performed. Otherwise the UE enters CELL_FACH state and sends URA UPDATE on RACH. The response CELL UPDATE CONFIRM on the FACH contains again a new state for the UE. If this state is set to URA_PCH, then the UE goes back to URA_PCH state and enters the master URA (URA #0 in SIB2) of the new cell.



2.2. RRC Connection Establishment


2.2. RRC Connection Estab. - CELL_FACHUE RNC

TMD RRC Connection Request[RACH:CCCH] RLC/RRCpre-defined configuration status indicator = true|false, Initial UE ID, establishment cause,measured result on RACH

UTRA IDLE

NAS Trigger

UMD RRC Connection Setup[FACH:CCCH] RLC/RRCInitial UE ID, new U-RNTI, new C-RNTI, RRC state indicator = CELL_FACH, capability updaterequirement, signalling radio bearer to setup, TrCH to add/reconfigure

CELL_FACH

UTRA IDLE CELL_FACH

• TMSI + LAI• PTMSI + RAI• IMSI• IMEI

• orig./term. conversational call• orig./term. streaming call• orig./term. interactive call• orig./term. background call• originating subscribed traffic call• emergency call

• inter-RAT cell re-selection• inter-RAT cell change order• registration• detach• orig./term. high/low priority signalling• call re-establishment• terminating – cause unknown

AMD RRC Connection Setup Complete[RACH:DCCH] RLC/RRCSTARTCS, STARTPS, UE radio access capability, inter-RAT UE radio access capability

STATUS[RACH:DCCH] RLC/-Acknowledgement


2.2. RRC Connection Est. – CELL_FACH

+--------+--------------------+------------+------------+------------+-------------------------------------+|No |Long Time |2. Prot |2. MSG |3. Prot |3. MSG |+--------+--------------------+------------+------------+------------+-------------------------------------+|68 |17:25:34,045,725 |RLC/MAC |FP DATA RACH| | ||69 |17:25:34,045,725 |RLC reasm. |TM DATA RACH|RRC_CCCH_UL |rrcConnectionRequest ||70 |17:25:34,130,812 |RLC/MAC |FP DATA FACH| | ||71 |17:25:34,140,807 |RLC/MAC |FP DATA FACH| | ||72 |17:25:34,150,775 |RLC/MAC |FP DATA FACH| | ||73 |17:25:34,150,775 |RLC reasm. |UM DATA FACH|RRC_CCCH_DL |rrcConnectionSetup ||74 |17:25:34,414,754 |RLC/MAC |FP DATA RACH| | ||75 |17:25:34,513,729 |RLC/MAC |FP DATA RACH| | ||76 |17:25:34,513,729 |RLC reasm. |AM DATA RACH|RRC_DCCH_UL |rrcConnectionSetupComplete |

RRC Connection Establishment CELL_FACH (short trace)



|TS 25.331 CCCH-UL (2002-09) (RRC_CCCH_UL) rrcConnectionRequest (= rrcConnectionRequest) || |uL-CCCH-Message || |1 message || |1.1 rrcConnectionRequest || |1.1.1 initialUE-Identity || |1.1.1.1 tmsi-and-LAI ||***B4*** |1.1.1.1.1 tmsi |'00000111010000000010000110011110'B || |1.1.1.1.2 lai || |1.1.1.1.2.1 plmn-Identity || |1.1.1.1.2.1.1 mcc ||0010---- |1.1.1.1.2.1.1.1 digit |2 ||----0110 |1.1.1.1.2.1.1.2 digit |6 ||0010---- |1.1.1.1.2.1.1.3 digit |2 || |1.1.1.1.2.1.2 mnc ||***b4*** |1.1.1.1.2.1.2.1 digit |0 ||-0010--- |1.1.1.1.2.1.2.2 digit |2 ||**b16*** |1.1.1.1.2.2 lac |'0000011111010010'B ||***b5*** |1.1.2 establishmentCause |registration ||--0----- |1.1.3 protocolErrorIndicator |noError |

RRC Connection Request



|TS 25.331 CCCH-DL (2002-09) (RRC_CCCH_DL) rrcConnectionSetup (= rrcConnectionSetup) || |dL-CCCH-Message || |1 message || |1.1 rrcConnectionSetup || |1.1.1 r3 || |1.1.1.1 rrcConnectionSetup-r3 || |1.1.1.1.1 initialUE-Identity || |1.1.1.1.1.1 tmsi-and-LAI ||**b32*** |1.1.1.1.1.1.1 tmsi |'00000111010000000010000110011110'B || |1.1.1.1.1.1.2 lai || |1.1.1.1.1.1.2.1 plmn-Identity || |1.1.1.1.1.1.2.1.1 mcc ||---0010- |1.1.1.1.1.1.2.1.1.1 digit |2 ||***b4*** |1.1.1.1.1.1.2.1.1.2 digit |6 ||---0010- |1.1.1.1.1.1.2.1.1.3 digit |2 || |1.1.1.1.1.1.2.1.2 mnc ||0000---- |1.1.1.1.1.1.2.1.2.1 digit |0 ||----0010 |1.1.1.1.1.1.2.1.2.2 digit |2 ||***B2*** |1.1.1.1.1.1.2.2 lac |'0000011111010010'B ||00------ |1.1.1.1.2 rrc-TransactionIdentifier |0 || |1.1.1.1.3 new-U-RNTI ||**b12*** |1.1.1.1.3.1 srnc-Identity |'010111110000'B ||**b20*** |1.1.1.1.3.2 s-RNTI |'00001011101011110111'B ||**b16*** |1.1.1.1.4 new-c-RNTI |'0000000000000000'B ||--01---- |1.1.1.1.5 rrc-StateIndicator |cell-FACH ||----000- |1.1.1.1.6 utran-DRX-CycleLengthCoeff |3 |

RRC Connection Setup 1( )



| |1.1.1.1.7 capabilityUpdateRequirement ||1------- |1.1.1.1.7.1 ue-RadioCapabilityFDDUpdateRequ.. |1 ||-0------ |1.1.1.1.7.2 ue-RadioCapabilityTDDUpdateRequ.. |0 || |1.1.1.1.7.3 systemSpecificCapUpdateReqList || |1.1.1.1.7.3.1 systemSpecificCapUpdateReq |gsm || |1.1.1.1.8 srb-InformationSetupList || |1.1.1.1.8.1 sRB-InformationSetup ||00000--- |1.1.1.1.8.1.1 rb-Identity |1 |...| |1.1.1.1.8.1.3.2 rB-MappingOption |...| |1.1.1.1.8.1.3.2.1.1.1 ul-TransportChannelType || |1.1.1.1.8.1.3.2.1.1.1.1 rach |0 ||***b4*** |1.1.1.1.8.1.3.2.1.1.2 logicalChannelIdentity |2 |...| |1.1.1.1.8.1.3.2.2.1.1 dl-TransportChannelType || |1.1.1.1.8.1.3.2.2.1.1.1 fach |0 ||***b4*** |1.1.1.1.8.1.3.2.2.1.2 logicalChannelIdentity |2 |

RRC Connection Setup 2( )


2.2. RRC Connection Est. – CELL_FACHRRC Connection Setup 3( )

...| |1.1.1.1.8.2.3.2 rB-MappingOption || |1.1.1.1.8.2.3.2.1.1.1 ul-TransportChannelType || |1.1.1.1.8.2.3.2.1.1.1.1 rach |0 ||***b4*** |1.1.1.1.8.2.3.2.1.1.2 logicalChannelIdentity |3 |...| |1.1.1.1.8.2.3.2.2.1.1 dl-TransportChannelType || |1.1.1.1.8.2.3.2.2.1.1.1 fach |0 ||----0010 |1.1.1.1.8.2.3.2.2.1.2 logicalChannelIdentity |3 || |1.1.1.1.8.3 sRB-InformationSetup ||-00010-- |1.1.1.1.8.3.1 rb-Identity |3 || |1.1.1.1.8.3.2 rlc-InfoChoice ||***b5*** |1.1.1.1.8.3.2.1 same-as-RB |2 ...| |1.1.1.1.8.4 sRB-InformationSetup ||--00011- |1.1.1.1.8.4.1 rb-Identity |4 || |1.1.1.1.8.4.2 rlc-InfoChoice ||00001--- |1.1.1.1.8.4.2.1 same-as-RB |2 |...


2.2. RRC Connection Est. – CELL_FACH|TS 25.331 DCCH-UL (2002-09) (RRC_DCCH_UL) rrcConnectionSetupComplete (= rrcConnectionSetupComplete) || |uL-DCCH-Message || |1 message || |1.1 rrcConnectionSetupComplete ||-00----- |1.1.1 rrc-TransactionIdentifier |0 || |1.1.2 startList || |1.1.2.1 sTARTSingle ||-----0-- |1.1.2.1.1 cn-DomainIdentity |cs-domain ||**b20*** |1.1.2.1.2 start-Value |'00000000000000000100'B || |1.1.2.2 sTARTSingle ||--1----- |1.1.2.2.1 cn-DomainIdentity |ps-domain ||**b20*** |1.1.2.2.2 start-Value |'00000000000000001010'B || |1.1.3 ue-RadioAccessCapability || |1.1.3.1 accessStratumReleaseIndicator |r99 || |1.1.3.2 pdcp-Capability ||0------- |1.1.3.2.1 losslessSRNS-RelocationSupport |0 || |1.1.3.2.2 supportForRfc2507 || |1.1.3.2.2.1 notSupported |0 || |1.1.3.3 rlc-Capability ||--010--- |1.1.3.3.1 totalRLC-AM-BufferSize |kb50 ||-----0-- |1.1.3.3.2 maximumRLC-WindowSize |mws2047 ||***b3*** |1.1.3.3.3 maximumAM-EntityNumber |am6 || |1.1.3.4 transportChannelCapability || |1.1.3.4.1 dl-TransChCapability ||-0101--- |1.1.3.4.1.1 maxNoBitsReceived |b6400 ||***b4*** |1.1.3.4.1.2 maxConvCodeBitsReceived |b640 |...

RRC Connection Setup Complete


2.2. RRC Connection Est. – CELL_FACHWhen a UE wants to leave idle mode and enter connected mode it has to start the RRC Connection Establishment

procedure. During this procedure the UE is sent either to CELL_FACH state or CELL_DCH state. The decision which of the two states is chosen is done by the RNC.

The first flow shows the transition to state CELL_FACH. The procedure is done in the following way:

1. The UE sends RRC CONNECTION REQUEST on the RACH (CCCH) to the RNC. Inside the message the UE indicates its identity in the parameter ‚Initial UE ID‘. Furthermore a cause for the request is indicated via the ‚Establishment Cause‘ information element.

2. When the RNC has made the decision about the state (here CELL_FACH) then it sends RRC CONNECTION SETUP to the UE on FACH (CCCH). As reference to the RRC CONNECTION REQUEST the ‚Initial UE ID‘ is repeated in this message. The ‚RRC State Indicator‘ tells the UE to enter CELL_FACH state. To use DCCH/DTCH on RACH and FACH the UE needs a c-rnti, which is also indicated in this message. As sign for the connected mode the UE also gets a u-rnti.

3. To confirm the connected mode the UE returns now RRC CONNECTION SETUP COMPLETE. This message is sent on RACH because the UE is in state CELL_FACH now. The logical channel is DCCH, thus the MAC header for the transport blocks of this message contains the c-rnti for identification of the UE.


2.2. RRC Connection EstablishmentUE RNC

TMD RRC Connection Request[RACH:CCCH] RLC/RRCpre-defined configuration status indicator = true|false, Initial UE ID, establishment cause,measured result on RACH

UTRA IDLE

NAS Trigger

UMD RRC Connection Setup[FACH:CCCH] RLC/RRCInitial UE ID, new U-RNTI, RRC state indicator = CELL_DCH, capability update requirement,signalling radio bearer to setup, TrCH to add/reconfigure (signalling DCH), uplink and downlink physical resources

CELL_DCH

UTRA IDLE CELL_DCH

AMD RRC Connection Setup Complete[DCH:DCCH] RLC/RRCSTARTCS, STARTPS, UE radio access capability, inter-RAT UE radio access capability

STATUS[DCH:DCCH] RLC/-Acknowledgement

DPCH and DPDCH/DPCCHsynchronisation


2.2. RRC Connection EstablishmentWhen the UE enters CELL_DCH instead of CELL_FACH the basic flow of messages is the same. The first difference is to be seen in the RRC CONNECTION SETUP message. The ‚RRC State Indicator‘ is now set to CELL_DCH and thus there is no c-rnti to be allocated for the UE. Rather the physical layer will identify the UE in CELL_DCH state, the MAC layer will not perform layer 2 identification.

Of course the RRC CONNECTION SETUP COMPLETE message will now be sent on DCH (DCCH) instead of RACH.



2.3. RRC Connection Release


2.3. RRC Connection ReleaseUE RNC

UMD RRC Connection Release Complete[DCH:DCCH] RLC/RRC

CELL_DCHUMD RRC Connection Release[DCH:DCCH] RLC/RRC

N308, release cause

CELL_DCH UTRA IDLE

UMD RRC Connection Release Complete[DCH:DCCH] RLC/RRC

. . .N308

UTRA IDLE

• normal event• unspecified• pre-emptive release• congestion• re-establishment reject• user inactivity• directed signalling connection re-establishment



AMD RRC Connection Release Complete[RACH:DCCH] RLC/RRC

CELL_FACHUMD RRC Connection Release[FACH:DCCH] RLC/RRC

release cause

CELL_FACH with DCCH UTRA IDLE

UTRA IDLE

UE RNC

CELL_FACHUMD RRC Connection Release[FACH:CCCH] RLC/RRC

U-RNTI, release cause

CELL_FACH without DCCH UTRA IDLE

UTRA IDLE

STATUS[FACH:DCCH] RLC/-Acknowledgement



CELL_PCHor

URA_PCH

TMD Paging Type 1[PCH:PCCH] RLC/RRCU-RNTI, release indicator = release

URA_PCH/CELL_PCH UTRA IDLE

UTRA IDLE


2.3. RRC Connection ReleaseTo release a UE from connected mode and send it to idle the RRC Connection Release procedure is defined. Depending on the configuration of the UE the procedure has a different appearance.

When the UE is in state CELL_DCH then the RNC has to send the RRC CONNECTION RELEASE procedure to the UE via the signalling DCH. Inside the message a cause value indicates the reason for the release. A counter value N308 tells the UE how often to repeat the RRC CONNECTION RELEASE COMPLETE message on the uplink DCH to confirm the procedure. After this the UE is in idle mode and the RNC can release all dedicated resources allocated to this UE.

When the UE is in state CELL_FACH with allocated DCCH then the RNC also sends RRC CONNECTION RELEASE to release the UE. This time there is no counter value N308. Thus the UE sends exactly one RRC CONNECTION RELEASE COMPLETE message on RACH, then it enters idle mode.

If the UE is in state CELL_FACH but has currently no DCCH (happens after paging in state CELL_PCH or URA_PCH or after cell reselection) then only the RRC CONNECTION RELEASE message is sent. No completion message follows afterwards, instead the UE enters directly idle mode (see paging procedures for more information about this).

In UMTS Release 5 a new procedure is introduced. When a UE is in state CELL_PCH or URA_PCH it is possible to page it with a PAGING TYPE 1 message that contains a release indicator. If this indicator is set to release, then the UE enters directly idle mode without any further action (NOTE: There is a small inconsistency with the RRC state diagram.)


3. Iu Signalling Connection Handling



3.1. Iu Signalling Connections - General



SGSN

MSC Server

CS-MGWUE

ServingRNC

RRCConnection

Iu Signalling Connection CS

Iu Signalling Connection PS

radio mgt.data

radio mgt.data

S-RNTIS-RNTI CS-Iu Sign.ConnectionCS-Iu Sign.ConnectionPS-Iu Sign.ConnectionPS-Iu Sign.Connection



CMM_DetachedCMM_Detached

CMM_ConnectedCMM_ConnectedCMM_IdleCMM_Idle

CS Mobility Management States

PMM_DetachedPMM_Detached

PMM_ConnectedPMM_ConnectedPMM_IdlePMM_Idle

PS Mobility Management States


3.1. Iu Signalling Connections - GeneralThe RRC Connection provides signalling facilities between UE and RNC for radio management tasks. Of course the main reason to start signalling is to get services from the core network. In other words the UE also needs signalling transfer capabilities to and from the core network.

In UMTS (like in GSM) the UE has no direct link to the CN, thus the UTRAN has to manage signalling connection towards the CN for the UE. These connections are called Iu signalling connections. They are implemented by the SCCP protocol on Iu interface. The RANAP protocol is running in Iu signalling connections.

A connected mode UE can have none, one or two Iu signalling connections. At most one Iu signalling connection can be set up for a UE to the MSC server and at most one Iu signalling connection can be established to SGSN for a UE. An idle mode UE cannot have any Iu signalling connection. The reason for the last fact is that it is the serving RNC that has to manage Iu signalling connections.

Within the core network entities MSC server and SGSN a mobility management state (PMM = Packet Mobility Management, CMM = Circuit Mobility Management) is maintained for each UE. PMM and CMM states are relatively equal defined. Both consist of three possible states:

• P/CMM_DETACHED: A UE in state P/CMM_DETACHED is currently not registered for services in the core network entity.

• P/CMM_CONNECTED: In this state the UE is registered for services in the CN entity and an Iu signalling connection for this UE exists in the moment. Thus the CN can immediately start signalling towards UE by sending a message within the appropriate Iu signalling connection. This means that CN triggered paging is not required in this state.

• P/CMM_IDLE: In this state the UE is registered for services in the CN entity, but there is currently no Iu signalling connection for this UE. Thus before a signalling procedure can be started with the UE the CN must page the UE. This paging is for the UE the trigger to establish an Iu signalling connection (P/CMM_CONNECTED) state.



3.2. Establishment and Signalling Transfer



UE RNC

CELL_DCHCELL_FACH

AMD Initial Direct Transfer[DCCH] RLC/RRCCN domain ID, intra domain NAS node selector, establishment cause,NAS message, START, measured results on RACH

Iu Signalling Connection Establishment

SGSN

MSC Server

Initial UE MessageRANAP

STATUS[DCCH] RLC/--acknowledgement

CN domain ID, NAS message, LAI, RAC, …



UE RNC

CELL_DCHCELL_FACH

AMD Uplink Direct Transfer[DCCH] RLC/RRCCN domain ID, NAS message, measured results on RACH

Uplink NAS Signalling TransferSGSN

MSC Server

Direct TransferRANAPCN domain ID, NAS message, LAI, RAC

UE RNC

CELL_DCHCELL_FACH

AMD Downlink Direct Transfer[DCCH] RLC/RRCCN domain ID, NAS message

Downlink NAS Signalling TransferSGSN

MSC Server

Direct TransferRANAP

CN domain ID, NAS message, SAPI


3.2. Establishment and Signalling TransferThe establishment of Iu signalling connection is triggered by the UE via the INITIAL DIRECT TRANSFER message. This message indicates which core network domain the connection shall be set up to and a message for this core network is contained. On the Iu interface the serving RNC issues the RANAP message INITIAL UE MESSAGE is sent to the indicated core network domain.

Once the Iu signalling connection exists, the UE and the core network can freely exchange NAS signalling with each other. The serving RNC acts as relay point for the NAS signalling messages.

In case of uplink NAS signalling the UE packs the NAS message in a UPLINK DIRECT TRANSFER message, the RNC relays the message via RANAP DIRECT TRANSFER to the core network.

For downlink NAS messages the CN has to encapsulate the NAS PDU in a RANAP DIRECT TRANSFER message. The RNC translates this into the DOWNLINK DIRECT TRANSFER message. The ‚SAPI‘ parameter in the DIRECT TRANSFER message gives the priority of the NAS message.



3.3. Iu Signalling Connection Release



UE RNCSGSN

MSC Server

Iu Release CommandRANAPrelease cause

RRC Connection Release ProcedureIF (last Iu signalling connection to be released)

ELSE IF (no radio bearer for releasing CN allocated)

Iu Release CompleteRANAP…

AMD Signalling Connection Release[DCCH] RLC/RRCCN domain ID

ELSE IF (radio bearer for releasing CN allocated)

AMD Radio Bearer Release[DCCH] RLC/RRC…, signalling connection release indication = CN domain ID, …

AMD Radio Bearer Release Complete[DCCH] RLC/RRC…



UE RNCSGSN

MSC Server

Iu Release CommandRANAPrelease cause = UTRAN generated reason

Iu Release CompleteRANAP

Handling like in normal Iu signalling connectionrelease case

AMD Signalling Conn. Release Indic.[DCCH] RLC/RRCCN domain ID

Iu Release RequestRANAP


3.3. Iu Signalling Connection ReleaseThe release of Iu signalling connections is managed by the core network via the RANAP Iu Release procedure.

The core network releases an Iu signalling connection via RANAP message IU RELEASE COMMAND. The serving RNC will respond with IU RELEASE COMPLETE.

Depending on the current UE configuration there are three basic procedures possible on the radio interface:

• RRC Connection Release procedure is triggered (UE is sent to IDLE state),

• UE is informed about Iu signalling connection release via SIGNALLING CONNECTION RELEASE procedure,

• radio bearers are released via RADIO BEARER RELEASE procedure.

Of course none of these procedures is triggered when the UE is no longer in this RNC area.

In some situations the RNC can request the release of the Iu signalling connection from the CN via the RANAP procedure IU RELEASE REQUEST. The reason for this message might be an RNC internal trigger or the UE has requested the release by SIGNALLING CONNECTION RELEASE MESSAGE.


4. Security Mode Control



4.1. Ciphering and Integrity Protection


RRC HFN (28 bit)

4.1. Ciphering and Integrity ProtectionIntegrity Protection

f9 (UIA)f9 (UIA)

IK

COUNT-IDIRECTION

FRESH

RRC Message MAC-I

f9 (UIA)f9 (UIA)

IK

COUNT-IDIRECTION

FRESH

RRC Message MAC-I

XMAC-I

Transmitter Receiver

COUNT-I

RRC HFN (28 bit) RRC SN (4)


4.1. Ciphering and Integrity ProtectionDCCH RRC messages can be protected against change of information or message injection by an integrity protection mechanism. Therefore an algorithm f9 (UIA: UMTS Integrity Algorithm) must be available in UE and RNC. For each DCCH RRC message this algorithm calculates a message authentication code (MAC-I: Message Authentication Code – Integrity). This MAC-I is included in the message itself.

At the receiver side the MAC-I is calculated again and cross-checked with the transmitted one.

The algorithm UIA (f9) takes several additional values as input:

• IK (Integrity Key): A UE specific key that is derived from authentication (automatic key agreement).

• DIRECTION: Discriminates between uplink and downlink direction.

• FRESH: An offset value that is allocated for uplink by UE and for downlink by RNC. The UL/DL-FRESH values are exchanged at set up of signalling radio bearers (RRC CONNECTION SETUP and RRC CONNECTION SETUP COMPLETE).

• COUNT-I: This value is increased with every message that is transmitted. For initialisation of COUNT-I a START value is negotiated at radio bearer set up time.


4.1. Ciphering and Integrity Protection

RRC HFN (28 bit)

Ciphering

f8 (UEA)f8 (UEA)

BEARER

COUNT-CDIRECTION

LENGTH

PlaintextBlock

f8 (UIA)f8 (UIA)

Transmitter Receiver

COUNT-C for RLC TM on DCH MAC-d HFN (24 bit) CFN (4 bit)

CK

BEARER

COUNT-CDIRECTION

LENGTH

CK

KeystreamBlock

XOR

CiphertextBlock

KeystreamBlock

XOR

PlaintextBlock

RRC HFN (28 bit)COUNT-C for RLC UM RLC HFN (25 bit) RLC SN (7 bit)

COUNT-C for RLC AM RLC HFN (20 bit) RLC SN (12 bit)


4.1. Ciphering and Integrity ProtectionLike in GSM also UMTS allows an encryption with a classical stream cipher algorithm.

The algorithm for production of the stream cipher sequence is called UEA (UMTS Encryption Algorithm) or f8. This algorithm uses several values as input:

• CK (Cipher Key): A UE specific key that is coming from authentication (automatic key agreement).

• BEARER: The radio bearer identity.

• DIRECTION: Distinguishes between uplink and downlink direction.

• LENGTH: Length of the cipher sequence to be produced.

• COUNT-C: Strictly increasing value for each radio frame (RLC transparent mode) or RLC frame (RLC unacknowledged or acknowledged mode). COUNT-C is initialised with the START values that are exchanged at radio bearer set up time.



4.2. Security Mode Activation


4.2. Security Mode Activation

UE RNCSGSN

MSC Server

Security Mode CommandRANAPintegrity protection info, ciphering info, …

Security Mode CompleteRANAP

AMD Security Mode Command.[DCCH] RLC/RRCCN domain ID, security capability, inter-RAT security capability, ciphering mode info = {start/modify, selected UEA-no., RB activation

time, DPCH activation time}integrity mode info = {start/modify, selected UIA-no., DL-FRESH, …}


AMD Security Mode Complete[DCCH] RLC/RRCintegrity check info = {MAC-I, RRC SN for RB2}, uplink integrity protection activation info ={RRC SN for RB1-RB4},RB ciphering activation time info = {RB-ID, RLC SN}


…


4.2. Security Mode Activation|TS 25.331 DCCH-DL (2002-09) (RRC_DCCH_DL) securityModeCommand (= securityModeCommand) || |1 integrityCheckInfo ||**b32*** |1.1 messageAuthenticationCode |'10110100100001111011101010000100'B ||-0001--- |1.2 rrc-MessageSequenceNumber |1 || |2 message || |2.1 securityModeCommand || |2.1.1 r3 || |2.1.1.1 securityModeCommand-r3 ||***b2*** |2.1.1.1.1 rrc-TransactionIdentifier |0 || |2.1.1.1.2 securityCapability ||**b16*** |2.1.1.1.2.1 cipheringAlgorithmCap |uea1 || | |uea0 ||**b16*** |2.1.1.1.2.2 integrityProtectionAlgorithmCap |uia1 || |2.1.1.1.3 integrityProtectionModeInfo || |2.1.1.1.3.1 integrityProtectionModeCommand || |2.1.1.1.3.1.1 startIntegrityProtection ||**b32*** |2.1.1.1.3.1.1.1 integrityProtInitNumber |'01000000110110110000111010010001'B || |2.1.1.1.3.2 integrityProtectionAlgorithm |uia1 ||---0---- |2.1.1.1.4 cn-DomainIdentity |cs-domain |

|TS 25.331 DCCH-UL (2002-09) (RRC_DCCH_UL) securityModeComplete (= securityModeComplete) || |1 integrityCheckInfo ||**b32*** |1.1 messageAuthenticationCode |'11101010011001010000010001001011'B ||-0001--- |1.2 rrc-MessageSequenceNumber |1 || |2 message || |2.1 securityModeComplete ||-----00- |2.1.1 rrc-TransactionIdentifier |0 || |2.1.2 ul-IntegProtActivationInfo || |2.1.2.1 rrc-MessageSequenceNumberList ||0000---- |2.1.2.1.1 rRC-MessageSequenceNumber |0 ||----0000 |2.1.2.1.2 rRC-MessageSequenceNumber |0 ||0000---- |2.1.2.1.3 rRC-MessageSequenceNumber |0 ||----0000 |2.1.2.1.4 rRC-MessageSequenceNumber |0 ||0000---- |2.1.2.1.5 rRC-MessageSequenceNumber |0 |


4.2. Security Mode ActivationSecurity functions are activated by the core network via the RANAP procedure Security Mode Control. This procedure is triggered with the message SECURITY MODE COMMAND. In this message the CN provides IK and CK to the RNC as well as a list of permitted UIA and UEA.

The serving RNC has to select an UIA and an UEA that is supported by UE and RNC and is permitted by the CN. Then the security functions are activated by the RRC message SECURITY MODE COMMAND. In it one can find the selected algorithms.

When the UE is able to activate the requested algorithms it returns SECURITY MODE COMPLETE. The same message but from RANAP protocol is also returned to the core network.


5. Paging


5. Paging

5.1. UTRAN Paging Types


5.1. UTRAN Paging Types

CN originatedCN originated

UTRAN originatedUTRAN originated

UTRAN Paging

Paging Originator

Request for Iu signalling connection

Request for UE to enter CELL_FACH and perform Cell Update procedure

Paging Type 1Paging Type 1

Paging Type 2Paging Type 2

Paging Type

PCCH on PCH; may be used to page up to 8 UE

DCCH on DCH or FACH


5.1. UTRAN Paging TypesPaging in UMTS can come from two different types of source – the paging originator:

• CN originated paging: The CN triggers paging whenever a downlink signalling message shall be sent, but currently there is no Iu signalling connection for this UE at the CN domain of interest available (P/CMM_DETACHED state). Thus CN originated paging is a request for an Iu signalling connection.

• UTRAN originated paging: The serving RNC has to trigger a paging whenever the UE is in state CELL_PCH or URA_PCH and a downlink message shall be sent to the UE. This paging shall force the UE to enter state CELL_FACH and perform a Cell Update procedure.

A problem for UTRAN is the question on which channel to send the paging message. The RRC protocol provides two options:

• Paging Type 1: The RRC message PAGING TYPE 1 is always sent on the PCH. Thus it can be used for UE in state Idle, CELL_PCH or URA_PCH. The PAGING TYPE 1 message can be used to page up to 8 UE in one single message. Furthermore the PAGING TYPE 1 message can also be used to indicate change of BCCH (BCCH Modification) or to release a UE from state CELL_PCH or URA_PCH to idle.

• Paging Type 2: The message PAGING TYPE 2 is sent on either DCH or FACH. Thus it is the choice for UE in state CELL_DCH or CELL_FACH. Note that PAGING TYPE 2 is a dedicated control channel (DCCH) message, thus only one UE can be paged with such a message.


5. Paging

5.2. CN originated paging



UE RNCSGSN

MSC Server

PagingRANAPCN domain ID, UE identifier, paging area,paging cause

Initial UE MessageRANAP

TMD/AMD Paging Type 1|2[P/DCCH] RLC/RRCType 1: Paging Record ={…, CN UE ID or U-RNTI + CN domain ID}Type 2: CN domain ID

TMD RRC Connection Request[CCCH] RLC/RRC

UMD RRC Connection Setup[CCCH] RLC/RRC

AMD RRC Connection Setup Complete[DCCH] RLC/RRC

IF (UE idle)

AMD Initial Direct Transfer[DCCH] RLC/RRC

. . .

STATUS[DCCH] RLC/--

CN domain ID, …, NAS-Message = RR:Paging Response|GMM:Service Request NAS-Message



|TS 25.331 PCCH (2002-03) (RRC_PCCH) pagingType1 (= pagingType1) || |pCCH-Message || |1 message || |1.1 pagingType1 || |1.1.1 pagingRecordList || |1.1.1.1 pagingRecord || |1.1.1.1.1 cn-Identity ||110----- |1.1.1.1.1.1 pagingCause |terminatingCauseUnknown ||---0---- |1.1.1.1.1.2 cn-DomainIdentity |cs-domain || |1.1.1.1.1.3 cn-pagedUE-Identity ||**b32*** |1.1.1.1.1.3.1 tmsi-GSM-MAP |'10110110000000000000000000100001'B |

|TS 25.331 PCCH (2002-03) (RRC_PCCH) pagingType1 (= pagingType1) || |pCCH-Message || |1 message || |1.1 pagingType1 || |1.1.1 bcch-ModificationInfo ||-----010 |1.1.1.1 mib-ValueTag |3 ||***b9*** |1.1.1.2 bcch-ModificationTime |237 |

CN Triggered Paging

BCCH Modification Indication


5.2. CN originated pagingCN originated paging is obviously triggered by the core network.

MSC server or SGSN send the RANAP message PAGING to the RNC (or to several RNC). Inside the message the UE is identified (IMSI, TMSI/PTMSI) and the paging area (LAI/RAI) is indicated.

The RNC determines the state of the UE by checking the IMSI. Then either PAGING TYPE 1 or PAGING TYPE 2 is sent on an appropriate downlink signalling transport channel.

If the UE is in idle state, then it first of all performs a RRC connection setup procedure. If the UE is already in connected mode, it can skip this part.

Then the UE has to trigger the Iu signalling connection to the requesting core network using the INITIAL DIRECT TRANSFER message.


5. Paging

5.3. UTRAN originated paging


5.3. UTRAN originated pagingUE

RNC

TMD Paging Type 1[PCCH] RLC/RRCType 1: Paging Record ={…, U-RNTI, RRC connection release indication=No Release|Release Cause}

TMD Cell Update[CCCH] RLC/RRCIF (RRC connection release indication = NoRelease)

U-RNTI, cell update cause = paging response, …

UMD Cell Update Confirm[CCCH] RLC/RRCU-RNTI, new U-RNTI, new C-RNTI, RRC state indicator, RB info, TrCH info, PhCH info, …

CELL_PCHURA_PCH

ORUMD RRC Connection Release[CCCH] RLC/RRC

U-RNTI, new U-RNTI, new C-RNTI, RRC state indicator, RB info, TrCH info, PhCH info, …

IF (RRC connection release indication = ReleaseCause

UE enters UTRA IDLE mode


5.3. UTRAN originated pagingIn case the paging is originated by the serving RNC there is no ‚CN Domain‘ information element inside the PAGING TYPE 1 message.

The UE will enter state CELL_FACH on reception of an UTRAN originated paging. Then the UE will send a CELL UPDATE message on RACH (CCCH). Inside it will identify itself with the u-rnti and the parameter ‚cell update cause‘ is set to „paging response“.

The RNC has now two options. Either it sends the CELL UPDATE CONFIRM message on FACH to the UE and indicates with this a new state and radio configuration to the UE. Or the RNC sends RRC CONNECTION RELEASE, so that the UE immediately enters idle mode.

Since UMTS Release 5 the PAGING TYPE 1 message can contain a release indicator. If this is set to „release“, the UE will not perform the CELL UPDATE, instead it silently enters idle mode without any further interaction with the RNC.


6. Radio Resource Management



6.1. Radio Bearer and Radio Access Bearer Setup


6.1 RB and RAB Setup

UE RNCSGSN

MSC Server

RAB Assignment RequestRANAPRAB to setup or Modify, RAB to release

RAB Assignment ResponseRANAP

UMD/AMD Radio Bearer Setup[DCCH] RLC/RRC…, RRC state indicator, signalling radio bearer,radio access bearers radio bearers (user data)transport channel to add/delete, physical channel configuration

AMD Radio Bearer Setup Complete[DCCH] RLC/RRC…

successful RAB setup, failed RAB setup


6.1 RB and RAB Setup

+--------+----------------+--------------------+------------+------------+------------+--------------------------+|No |Long Time |From |2. Prot |2. MSG |3. Prot |3. MSG |+--------+----------------+--------------------+------------+------------+------------+--------------------------+|97 |12:01:15,470,365|NB #2 (DCH #1 DL) |RLC/MAC |FP DATA DCH | | ||98 |12:01:15,510,323|NB #2 (DCH #1 DL) |RLC/MAC |FP DATA DCH | | ||99 |12:01:15,550,476|NB #2 (DCH #1 DL) |RLC/MAC |FP DATA DCH | | ||100 |12:01:15,590,240|NB #2 (DCH #1 DL) |RLC/MAC |FP DATA DCH | | ||101 |12:01:15,630,489|NB #2 (DCH #1 DL) |RLC/MAC |FP DATA DCH | | ||102 |12:01:15,670,155|NB #2 (DCH #1 DL) |RLC/MAC |FP DATA DCH | | ||103 |12:01:15,710,405|NB #2 (DCH #1 DL) |RLC/MAC |FP DATA DCH | | ||104 |12:01:15,750,364|NB #2 (DCH #1 DL) |RLC/MAC |FP DATA DCH | | ||105 |12:01:15,750,364|NB #2 (DCH #1 DL) |RLC reasm. |AM DATA DCH |RRC_DCCH_DL |radioBearerSetup ||106 |12:01:15,967,569|NB #2 (DCH #1 UL) |RLC/MAC |FP DATA DCH | | ||109 |12:01:17,327,602|NB #2 (DCH #1 UL) |RLC/MAC |FP DATA DCH | | ||110 |12:01:17,327,602|NB #2 (DCH #1 UL) |RLC reasm. |AM DATA DCH |RRC_DCCH_UL |radioBearerSetupComplete |


6.1 RB and RAB SetupThe radio bearers for RRC signalling are usually set up via RRC CONNECTION SETUP. Radio bearers for user data (especially DTCH/CTCH, but not exclusively) cannot be created with this operation.

The general radio bearer establishment is provided by the RADIO BEARER SETUP procedure implemented by RRC protocol. This operation can be used to create any kind of radio bearer.

When radio bearers for applications like calls or PDP context shall be created, then the RADIO BEARER SETUP is part of the radio access bearer establishment triggered by core network. This is done via the RANAP message RAB ASSIGNMENT REQUEST. This message is used for set up, modification and release of radio access bearers. When a RAB is created or modified, then the serving RNC calculates how many radio bearers with which settings are required and creates these radio bearers with the RADIO BEARER SETUP procedure. In it the UE also gets an indication about the radio access bearers created.

When the new radio bearers are allocated by the UE it will respond with RADIO BEARER SETUP COMPLETE, this will in the end effect also trigger the RAB ASSIGNMENT RESPONSE message of RANAP back to the core network. This RANAP message contains parameters that indicate success or failure of the procedure.



6.2. Radio Bearer and Radio Access Bearer Release


6.2. RB and RAB Release

UE RNCSGSN

MSC Server

RAB Assignment RequestRANAPRAB to setup or Modify, RAB to release

RAB Assignment ResponseRANAP

UMD/AMD Radio Bearer Release[DCCH] RLC/RRC…, RRC state indicator, radio access bearers to reconfigure listtransport channel to add/delete, physical channel configuration


successful RAB setup, failed RAB setup

Iu Release CommandRANAP


UMD/AMD Radio Bearer Release[DCCH] RLC/RRC…, RRC state indicator, signalling connection release indication = ps|csradio access bearers to reconfigure listtransport channel to add/delete, physical channel configuration


RAB released


6.2. RB and RAB ReleaseTo release radio bearers the RADIO BEARER RELEASE procedure is provided by RRC protocol. It can be used to release individual radio bearers or complete radio access bearers with all associated radio bearers and the procedure can also trigger RRC state changes.

The RNC can in principle release a radio bearer at any time without involution of the core network. If this is really done, depends on the traffic class of the radio access bearer. Because of delay problems when a radio bearer is to be re-established, such a Radio Access Bearer independent Radio Bearer management is not done for conversational or streaming traffic classes. Only background and interactive traffic class radio access bearers allow such a radio bearer management without involution of CN.

Of course radio bearers have to be released whenever the radio access bearer of the service is terminated. A radio access bearer can be released in two ways. Either the CN uses again the RANAP procedure RAB ASSIGNMENT REQUEST with a RAB release indication or the CN releases the Iu signalling connection with IU RELEASE COMMAND. In the latter case all RAB for this UE of to the releasing core network have to be terminated.

The RNC can upon one of these two procedures release the associated radio bearers with RADIO BEARER RELEASE, the UE has to respond with RADIO BEARER RELEASE COMPLETE.

Of course there is another final way to release all radio bearers. When the UE is sent to idle state by the RRC message RRC CONNECTION RELEASE automatically all radio bearers will be terminated. This option is used after the IU RELEASE COMMAND when no Iu signalling connection is left at the end of the procedure.



6.3. Reconfiguration Operations


6.3. Reconfiguration OperationsUE

RNC

UMD/AMD Radio Bearer Reconfiguration[DCCH] RLC/RRCNew U-RNTI, new C-RNTI, new DSCH-RNTI, new H-RNTI, RRC state indicator, RB to reconfigure,transport channels to add/delete/modify, physical channel configuration

AMD Radio Bearer Reconfiguration Complete[DCCH] RLC/RRC…

UMD/AMD Transport Channel Reconfiguration[DCCH] RLC/RRCNew U-RNTI, new C-RNTI, new DSCH-RNTI, new H-RNTI, RRC state indicator,transport channels to add/delete/modify, physical channel configuration

AMD Transport Channel Reconfiguration Complete[DCCH] RLC/RRC…

UMD/AMD Physical Channel Reconfiguration[DCCH] RLC/RRCNew U-RNTI, new C-RNTI, new DSCH-RNTI, new H-RNTI, RRC state indicator, physical channel configuration

AMD Physical Channel Reconfiguration Complete[DCCH] RLC/RRC…


6.3. Reconfiguration OperationsThree main operations are provided in the RRC protocol to modify the current radio configuration of a UE. There are

• RADIO BEARER RECONFIGURATION: This allows to modify physical channels (frequency, channelization codes, scrambling codes), transport channels (transport format sets, transport format combination sets, type of transport channels) and radio bearers itself.

• TRANSPORT CHANNEL RECONFIGURATION: This procedure allows to modify transport channels and physical channels. Radio bearers are not affected by this procedure.

• PHYSICAL CHANNEL RECONFIGURATION: This allows to modify physical channels only.

Depending on what shall be modified the serving RNC has to select one of these procedures. If only transport format combinations shall be allowed or blocked there is another procedure – the TRANSPORT FORMAT COMBINATION CONTROL operation. This is not really a reconfiguration, because the channels and radio bearers are not modified by it.

The reconfiguration operations can be used to implement hard handover procedures on the same frequency or to other frequency (inter-frequency handover). They cannot be used for soft handover (see active set update procedure) or to perform inter-system (inter-RAT) handover (see HANDOVER FROM UTRAN COMMAND).



6.4. Inter-System Change Operations


6.4. Inter-System Change OperationsHandover From UTRAN

UESource

RNC

AMD Handover From UTRAN Command[DCCH] RLC/RRCRAB to handover list, other RAT system information other system’s handover message, …

STATUS[DCCH] RLC/--SUFI: Acknowledgement

other RAT(e.g. GSM BSS)

CoreNetwork

other system’s handover message

other system’s handover completion

AMD/UMD UE Capability Enquiry[DCCH] RLC/RRCcapability update requirement

AMD UE Capability Information[DCCH] RLC/RRCUE radio access capability, other RAT capabilities

AMD/UMD UE Capability Information Confirm[DCCH] RLC/RRC…


6.4. Inter-System Change OperationsTo change from UMTS WCDMA FDD mode to another radio access technology (RAT) there are inter-system (inter-RAT) procedures defined.

Before a UE can go to another RAT it might be necessary to retrieve the UE’s capabilities with respect to this RAT. If these RAT capabilities are not available yet at the serving RNC a capability enquiry procedure has to be performed. During this procedure the RNC request the updated capabilities with UE CAPABILITY ENQUIRY from the UE, which will respond with a UE CAPABILITY INFO message back to the RNC. This message contains the UE capabilities as requested before by the UE CAPABILITY ENQUIRY message. The RNC confirms reception of the parameters by sending UE CAPABILITY INFO CONFIRM.

When the handover to the other RAT shall be started typically a so called S-RNS Relocation procedure (not shown here) is started. During this relocation the new RAT radio network controller (whatever this might be) sends an appropriate handover command over the core network to the serving RNC. This will take it and pack it into a HANDOVER FROM UTRAN COMMAND, which is sent to the UE.

The UE now changes the radio access system and completes the handover procedure in the new radio subsystem.


6.4. Inter-System Change OperationsHandover To UTRAN

UETarget

RNC

AMD Handover To UTRAN Complete[DCCH] RLC/RRC…



CoreNetwork

Signalling transfer “Handover To UTRAN Command”Handover To UTRAN CommandRRCnew U-RNTI, ciphering algorithm,signalling radio bearer to setup,RAB and radio bearer to setup,transport channels to add, physical channelconfiguration

Signalling transfer “Inter-RAT Handover Info”Inter-RAT Handover InfoRRCUE radio access capabilities, pre-definedconfiguration status information


6.4. Inter-System Change OperationsA handover to UTRAN is of course triggered by the other RAT that is used by the UE in the moment.

Before a handover to UTRAN is started usually the new RNC (target RNC) has to get the UE capabilities with respect to WCDMA FDD mode. Therefore the other RAT requests the UE WCDMA capabilities and forwards it over the CN to the target RNC. This is embedded in a S-RNC relocation procedure, but this time the RNC is the destination of the procedure, not the source.

When the target RNC has the UE capabilities it will prepare all resources for it and then create a HANDOVER TO UTRAN COMMAND. This command is sent over the core network to the radio controller of the other RAT. From here the message finds its way to the UE. How this is done depends on the other RAT.

Now the UE switches to the WCDMA FDD cell and completes the handover with the message HANDOVER TO UTRAN COMPLETE.


6.4. Inter-System Change OperationsNetwork Ordered Cell Change To Other RAT

UESource

RNCAMD Cell Change Order From UTRAN[DCCH] RLC/RRC

target cell description, …



update procedures corresponding to new system


6.4. Inter-System Change OperationsThere is a second possibility to change from UTRAN to another radio access technology. This option is especially designed for UMTS (CELL_FACH) to GSM (Packet Transfer Mode).

Here we use a network ordered cell change to switch away from UMTS to another RAT. The RNC give the CELL CHANGE ORDER FROM UTRAN command to the UE. In this message the new cell of the other RAT is indicated. The UE now performs a forced cell reselection to the new cell. All cell reselection criteria for automatic cell reselection are ignored at the UE.

The remaining part of the procedure consists possibly of an update procedure in the new RAT. This is out of scope of UTRAN.



6.5. Active Set Management (Soft Handover)


6.5. Active Set Management (Soft Handover)UE

RNC

AMD/UMD Active Set Update[DCCH] RLC/RRCRadio link addition info {primary CPICH info = primary DL scrambling code,

cell identity, downlink DPCH info, …}Radio link removal info {primary CPICH info = primary DL scrambling code}

AMD Active Set Update Complete[DCCH] RLC/RRC


6.5. Active Set Management (Soft Handover)Soft handover consists of operations to add, delete and replace cells from the so called active set. The procedure that provides this functionality is the ACTIVE SET UPDATE.

In an ACTIVE SET UPDATE message the serving RNC indicates the cells that are to be added to the active set and the cells that must be removed from it. Whenever the UE receives such an ACTIVE SET UPDATE it immediately performs the requested operations and returns the ACTIVE SET UPDATE COMPLETE message.


7. UE Measurements


7. Measurements

7.1. Measurement Types and Reporting


7.1. Measurement Types and Reporting

1) Intra Frequency Measurements

2) Inter Frequency Measurements

3) Inter RAT Measurements

4) Traffic Volume Measurements

5) Quality Measurements

6) UE Internal Measurements

7) Positioning Measurements

RLC/MAC

TrCH#N

WCDMA physical layer

TrCH#0

. . .

RRC

. . .

PeriodicalMeasurements - Filtering

- Reporting criteria evaluation

RNCMeasurement Control | SIB 3/4+11/12RRC

Measurement ReportRRC


7.1. Measurement Types and ReportingUE Measurements in UTRAN are divided into seven categories as shown on the slide. Every measurement in a UE has to be created before it starts. Therefore a MEASUREMENT CONTROL message is provided. Additionally SIB 3/4 and SIB 11/12 can create measurements.

Reporting of measurements can be done either periodically or by event trigger. Which reporting mode for a created measurement is to chosen is indicated in the associated MEASUREMENT CONTROL message. When a trigger for a report is fulfilled then the UE sends MEASUREMENT REPORT uplink to the RNC which contains the measured results (filtered by UE) and the indication of the event that triggered the report (only for even triggered reporting).


7. Measurements

7.2. Measurement Control and Report Procedure


7.2. Measurement Control and Report ProcedureUE

RNC

AMD Measurement Control[DCCH] RLC/RRCmeasurement identity, measurement control command = setup, release, modify, measurement type,measurement reporting mode {RLC mode = AMD|UMD, trigger = periodical|event}, …

STATUS[DCCH] RLC/--

AMD/UMD Measurement Report[DCCH] RLC/RRCmeasurement identity, measurement control command = setup, release, modify, measurement type,measurement reporting mode {RLC mode = AMD|UMD, trigger = periodical|event}, …

STATUS[DCCH] RLC/--


|TS 25.331 DCCH-DL (2002-03) (RRC_DCCH_DL) measurementControl (= measurementControl) |

|dL-DCCH-Message || |1 integrityCheckInfo ||**b32*** |1.1 messageAuthenticationCode |'11101001001100000100101100101000'B ||-0011--- |1.2 rrc-MessageSequenceNumber |3 || |2 message || |2.1 measurementControl || |2.1.1 r3 || |2.1.1.1 measurementControl-r3 ||***b2*** |2.1.1.1.1 rrc-TransactionIdentifier |2 ||-1000--- |2.1.1.1.2 measurementIdentity |9 || |2.1.1.1.3 measurementCommand || |2.1.1.1.3.1 setup || |2.1.1.1.3.1.1 intraFrequencyMeasurement || |2.1.1.1.3.1.1.1 intraFreqCellInfoList || |2.1.1.1.3.1.1.1.1 removedIntraFreqCellList || |2.1.1.1.3.1.1.1.1.1 removeAllIntraFreqCells |0 || |2.1.1.1.3.1.1.1.2 newIntraFreqCellList || |2.1.1.1.3.1.1.1.2.1 newIntraFreqCell ||--00000- |2.1.1.1.3.1.1.1.2.1.1 intraFreqCellID |0 || |2.1.1.1.3.1.1.1.2.1.2 cellInfo ||-000000- |2.1.1.1.3.1.1.1.2.1.2.1 cellIndividualOffset |-20 || |2.1.1.1.3.1.1.1.2.1.2.2 modeSpecificInfo || |2.1.1.1.3.1.1.1.2.1.2.2.1 fdd || |2.1.1.1.3.1.1.1.2.1.2.2.1.1 primaryCPICH-Info ||***b9*** |2.1.1.1.3.1.1.1.2.1.2.2.1.1.1 primaryScramb.. |3 ||***b6*** |2.1.1.1.3.1.1.1.2.1.2.2.1.2 primaryCPICH-TX.. |30 ||-1------ |2.1.1.1.3.1.1.1.2.1.2.2.1.3 readSFN-Indicator |1 ||--0----- |2.1.1.1.3.1.1.1.2.1.2.2.1.4 tx-DiversityInd.. |0 |

7.2. Measurement Control and Report ProcedureMeasurement Control 1(4)



| |2.1.1.1.3.1.1.1.2.2 newIntraFreqCell ||***b5*** |2.1.1.1.3.1.1.1.2.2.1 intraFreqCellID |1 || |2.1.1.1.3.1.1.1.2.2.2 cellInfo ||***b6*** |2.1.1.1.3.1.1.1.2.2.2.1 cellIndividualOffset |-20 || |2.1.1.1.3.1.1.1.2.2.2.2 modeSpecificInfo || |2.1.1.1.3.1.1.1.2.2.2.2.1 fdd || |2.1.1.1.3.1.1.1.2.2.2.2.1.1 primaryCPICH-Info ||***b9*** |2.1.1.1.3.1.1.1.2.2.2.2.1.1.1 primaryScramb.. |5 ||***b6*** |2.1.1.1.3.1.1.1.2.2.2.2.1.2 primaryCPICH-TX.. |30 ||---1---- |2.1.1.1.3.1.1.1.2.2.2.2.1.3 readSFN-Indicator |1 ||----0--- |2.1.1.1.3.1.1.1.2.2.2.2.1.4 tx-DiversityInd.. |0 || |2.1.1.1.3.1.1.1.2.3 newIntraFreqCell ||***b5*** |2.1.1.1.3.1.1.1.2.3.1 intraFreqCellID |2 || |2.1.1.1.3.1.1.1.2.3.2 cellInfo ||***b6*** |2.1.1.1.3.1.1.1.2.3.2.1 cellIndividualOffset |-18 || |2.1.1.1.3.1.1.1.2.3.2.2 modeSpecificInfo || |2.1.1.1.3.1.1.1.2.3.2.2.1 fdd || |2.1.1.1.3.1.1.1.2.3.2.2.1.1 primaryCPICH-Info ||***b9*** |2.1.1.1.3.1.1.1.2.3.2.2.1.1.1 primaryScramb.. |1 ||***b6*** |2.1.1.1.3.1.1.1.2.3.2.2.1.2 primaryCPICH-TX.. |30 ||-----1-- |2.1.1.1.3.1.1.1.2.3.2.2.1.3 readSFN-Indicator |1 ||------0- |2.1.1.1.3.1.1.1.2.3.2.2.1.4 tx-DiversityInd.. |0 || |2.1.1.1.3.1.1.2 intraFreqMeasQuantity || |2.1.1.1.3.1.1.2.1 filterCoefficient |fc0 || |2.1.1.1.3.1.1.2.2 modeSpecificInfo || |2.1.1.1.3.1.1.2.2.1 fdd ||-00----- |2.1.1.1.3.1.1.2.2.1.1 intraFreqMeasQuantity.. |cpich-Ec-N0 || |2.1.1.1.3.1.1.3 intraFreqReportingQuantity || |2.1.1.1.3.1.1.3.1 activeSetReportingQuantities ||----00-- |2.1.1.1.3.1.1.3.1.1 sfn-SFN-OTD-Type |noReport ||------0- |2.1.1.1.3.1.1.3.1.2 cellIdentity-reportingI.. |0 ||-------1 |2.1.1.1.3.1.1.3.1.3 cellSynchronisationInfo.. |1 |

Measurement Control 2(4)


| |2.1.1.1.3.1.1.3.1.4 modeSpecificInfo || |2.1.1.1.3.1.1.3.1.4.1 fdd ||-1------ |2.1.1.1.3.1.1.3.1.4.1.1 cpich-Ec-N0-reporti.. |1 ||--0----- |2.1.1.1.3.1.1.3.1.4.1.2 cpich-RSCP-reportin.. |0 ||---0---- |2.1.1.1.3.1.1.3.1.4.1.3 pathloss-reportingI.. |0 || |2.1.1.1.3.1.1.3.2 monitoredSetReportingQuantities ||----00-- |2.1.1.1.3.1.1.3.2.1 sfn-SFN-OTD-Type |noReport ||------0- |2.1.1.1.3.1.1.3.2.2 cellIdentity-reportingI.. |0 ||-------1 |2.1.1.1.3.1.1.3.2.3 cellSynchronisationInfo.. |1 || |2.1.1.1.3.1.1.3.2.4 modeSpecificInfo || |2.1.1.1.3.1.1.3.2.4.1 fdd ||-1------ |2.1.1.1.3.1.1.3.2.4.1.1 cpich-Ec-N0-reporti.. |1 ||--0----- |2.1.1.1.3.1.1.3.2.4.1.2 cpich-RSCP-reportin.. |0 ||---0---- |2.1.1.1.3.1.1.3.2.4.1.3 pathloss-reportingI.. |0 || |2.1.1.1.3.1.1.4 reportCriteria || |2.1.1.1.3.1.1.4.1 intraFreqReportingCriteria || |2.1.1.1.3.1.1.4.1.1 eventCriteriaList || |2.1.1.1.3.1.1.4.1.1.1 intraFreqEventCriteria || |2.1.1.1.3.1.1.4.1.1.1.1 event || |2.1.1.1.3.1.1.4.1.1.1.1.1 e1a ||001----- |2.1.1.1.3.1.1.4.1.1.1.1.1.1 triggeringCondi.. |monitoredSetCellsOnly ||---00011 |2.1.1.1.3.1.1.4.1.1.1.1.1.2 reportingRange |3 ||00000--- |2.1.1.1.3.1.1.4.1.1.1.1.1.3 w |0 ||-----010 |2.1.1.1.3.1.1.4.1.1.1.1.1.4 reportDeactivat.. |t2 ||111----- |2.1.1.1.3.1.1.4.1.1.1.1.1.5 reportingAmount |ra-Infinity ||---011-- |2.1.1.1.3.1.1.4.1.1.1.1.1.6 reportingInterval |ri1 ||***b4*** |2.1.1.1.3.1.1.4.1.1.1.2 hysteresis |0 ||--0000-- |2.1.1.1.3.1.1.4.1.1.1.3 timeToTrigger |ttt0 || |2.1.1.1.3.1.1.4.1.1.1.4 reportingCellStatus ||--100--- |2.1.1.1.3.1.1.4.1.1.1.4.1 allActiveplusMoni.. |viactCellsPlus5 |



| |2.1.1.1.3.1.1.4.1.1.2 intraFreqEventCriteria || |2.1.1.1.3.1.1.4.1.1.2.1 event || |2.1.1.1.3.1.1.4.1.1.2.1.1 e1b ||---00--- |2.1.1.1.3.1.1.4.1.1.2.1.1.1 triggeringCondi.. |activeSetCellsOnly ||***b5*** |2.1.1.1.3.1.1.4.1.1.2.1.1.2 reportingRange |3 ||--00000- |2.1.1.1.3.1.1.4.1.1.2.1.1.3 w |0 ||***b4*** |2.1.1.1.3.1.1.4.1.1.2.2 hysteresis |0 ||---0000- |2.1.1.1.3.1.1.4.1.1.2.3 timeToTrigger |ttt0 || |2.1.1.1.3.1.1.4.1.1.2.4 reportingCellStatus ||---010-- |2.1.1.1.3.1.1.4.1.1.2.4.1 withinActiveSet |e3 || |2.1.1.1.3.1.1.4.1.1.3 intraFreqEventCriteria || |2.1.1.1.3.1.1.4.1.1.3.1 event || |2.1.1.1.3.1.1.4.1.1.3.1.1 e1c ||---011-- |2.1.1.1.3.1.1.4.1.1.3.1.1.1 replacementActi.. |t3 ||***b3*** |2.1.1.1.3.1.1.4.1.1.3.1.1.2 reportingAmount |ra1 ||-000---- |2.1.1.1.3.1.1.4.1.1.3.1.1.3 reportingInterval |noPeriodicalreporting ||----0000 |2.1.1.1.3.1.1.4.1.1.3.2 hysteresis |0 ||0000---- |2.1.1.1.3.1.1.4.1.1.3.3 timeToTrigger |ttt0 || |2.1.1.1.3.1.1.4.1.1.3.4 reportingCellStatus ||100----- |2.1.1.1.3.1.1.4.1.1.3.4.1 allActiveplusMoni.. |viactCellsPlus5 || |2.1.1.1.4 measurementReportingMode ||---0---- |2.1.1.1.4.1 measurementReportTransferMode |acknowledgedModeRLC ||----1--- |2.1.1.1.4.2 periodicalOrEventTrigger |eventTrigger |



|TS 25.331 DCCH-UL (2002-03) (RRC_DCCH_UL) measurementReport (= measurementReport) ||uL-DCCH-Message || |1 integrityCheckInfo ||**b32*** |1.1 messageAuthenticationCode |'11111000011011110101100100001111'B||-0100--- |1.2 rrc-MessageSequenceNumber |4 || |2 message || |2.1 measurementReport ||***b4*** |2.1.1 measurementIdentity |14 || |2.1.2 measuredResults || |2.1.2.1 intraFreqMeasuredResultsList || |2.1.2.1.1 cellMeasuredResults || |2.1.2.1.1.1 cellSynchronisationInfo || |2.1.2.1.1.1.1 modeSpecificInfo || |2.1.2.1.1.1.1.1 fdd || |2.1.2.1.1.1.1.1.1 countC-SFN-Frame-difference ||0000---- |2.1.2.1.1.1.1.1.1.1 countC-SFN-High |0 ||***b8*** |2.1.2.1.1.1.1.1.1.2 off |6 ||**b16*** |2.1.2.1.1.1.1.1.2 tm |16896 || |2.1.2.1.1.2 modeSpecificInfo || |2.1.2.1.1.2.1 fdd || |2.1.2.1.1.2.1.1 primaryCPICH-Info ||***b9*** |2.1.2.1.1.2.1.1.1 primaryScramblingCode |3 ||-100101- |2.1.2.1.1.2.1.2 cpich-Ec-N0 |37 |

7.2. Measurement Control and Report ProcedureMeasurement Report 1(2)



| |2.1.2.1.2 cellMeasuredResults || |2.1.2.1.2.1 cellSynchronisationInfo || |2.1.2.1.2.1.1 modeSpecificInfo || |2.1.2.1.2.1.1.1 fdd || |2.1.2.1.2.1.1.1.1 countC-SFN-Frame-difference ||----0000 |2.1.2.1.2.1.1.1.1.1 countC-SFN-High |0 ||00000110 |2.1.2.1.2.1.1.1.1.2 off |6 ||***B2*** |2.1.2.1.2.1.1.1.2 tm |17372 || |2.1.2.1.2.2 modeSpecificInfo || |2.1.2.1.2.2.1 fdd || |2.1.2.1.2.2.1.1 primaryCPICH-Info ||***b9*** |2.1.2.1.2.2.1.1.1 primaryScramblingCode |1 ||***b6*** |2.1.2.1.2.2.1.2 cpich-Ec-N0 |15 || |2.1.3 eventResults || |2.1.3.1 intraFreqEventResults ||***b4*** |2.1.3.1.1 eventID |e1a || |2.1.3.1.2 cellMeasurementEventResults || |2.1.3.1.2.1 fdd || |2.1.3.1.2.1.1 primaryCPICH-Info ||***b9*** |2.1.3.1.2.1.1.1 primaryScramblingCode |3 |

Measurement Report 2(2)

Alexander SeifarthJune 1, 2005 CONFIDENTIAL - DRAFT1

Module 04

Complete Sequences – Use Cases(Layer 3 signalling)

Version 0.0.1 (02/05/2005)



1. CS Mobility Management



1.1. Location Area Update

• UE is UTRA idle;• UE is PS detached;• performs cell reselection• no services follow after update


1.1. Location Area Update (1)UE RNC

UTRA_Idle

RRC Connection Request[CCCH] RRCInitial UE ID = IMSI|TMSI+LAI, Est.Cause = registration

MSC Server

Initial UE MessageRANAPCN domain = cs, LAI, SAI, RNC-ID,NAS-PDU = Location Updating Request

cell reselection

New LAI ?false

true

RRC Connection Setup[CCCH] RRCU-RNTI, C-RNTI, signalling radio bearer RB1..RB4, TrCH configuration,PhCH configuration, radio access capability update requirement

RRC Connection Setup Complete[DCCH] RRCUE radio access capabilities

Initial Direct Transfer[DCCH] RRCCN domain = cs, NAS-PDU = MM-message: Location Updating Request

CELL_DCH|CELL_FACH


1.1. Location Area Update (2)UE RNC MSC

Server

Direct TransferRANAPSAPI=0, NAS-PDU = Authentication Req.

Downlink Direct Transfer[DCCH] RRCCN domain = cs, NAS-PDU = MM-message: Authentication Request

Direct TransferRANAPLAI, SAI, NAS-PDU = Authentication Resp.

Uplink Direct Transfer[DCCH] RRCCN domain = cs, NAS-PDU = MM-message: Authentication Response

Security Mode CommandRANAPpermitted UIA, IK, permitted UEA, CK, …

Security Mode Command[DCCH] RRCselected UIA, selected UEA, ciphering activation time, …

Security Mode CommandRANAPselected UIA, selected UEA

Security Mode Complete[DCCH] RRC…

Direct TransferRANAPSAPI=0, NAS-PDU = Location Updating

Accept

Downlink Direct Transfer[DCCH] RRCCN domain = cs, NAS-PDU = MM-message: Location Updating Accept

Direct TransferRANAPLAI, SAI, NAS-PDU = TMSI Realloc. Compl.

Uplink Direct Transfer[DCCH] RRCCN domain = cs, NAS-PDU = MM-message: TMSI Reallocation Compl.


1.1. Location Area Update (3)UE RNC MSC

Server

Iu Release CommandRANAPcause = normal event

RRC Connection Release[DCCH] RRCcause = normal event, N308 (only for CELL_DCH)


RRC Connection Release Complete[DCCH] RRC

UTRA_Idle



1.2. IMSI Detach (UE Power Off)

• UE is UTRA idle;• UE is PS detached;• user switches UE off


1.2. IMSI Detach (UE Power Off) (1)UE RNC

UTRA_Idle

RRC Connection Request[CCCH] RRCInitial UE ID = IMSI|TMSI+LAI, Est.Cause = detach

MSC Server

Initial UE MessageRANAPCN domain = cs, LAI, SAI, RNC-ID,NAS-PDU = IMSI Detach Indication

Power Off (User)

ATT=truefalse

true



Initial Direct Transfer[DCCH] RRCCN domain = cs, NAS-PDU = MM-message: IMSI Detach Indication

CELL_DCH|CELL_FACH

Power Off

SIB 1[BCCH] RRC…, ATT, …


1.2. IMSI Detach (UE Power Off) (2)UE RNC MSC

Server

Connection RefusedSCCPRRC Connection Release[DCCH] RRC

Cause = normal event | unspecified, N308 (only CELL_DCH)


Power Off

UTRA_Idle


2. CS Call Services


2. CS Call Services

2.1. Mobile Originating Call (MOC)

• UE is UTRA idle;• no PS services running, no other CS services except the MOC• no handovers during call• call release by remote party


2.1. Mobile Originating Call (MOC) (1)UE RNC

UTRA_Idle

RRC Connection Request[CCCH] RRCInitial UE ID = IMSI|TMSI+LAI, Est.Cause = originating conversational call

MSC Server

Initial UE MessageRANAPCN domain = cs, LAI, SAI, RNC-ID,NAS-PDU = CM Service Request

call request (User)



Initial Direct Transfer[DCCH] RRCCN domain = cs, NAS-PDU = MM-message: CM Service Request

CELL_DCH|CELL_FACH


2.1. Mobile Originating Call (MOC) (2)UE RNC MSC

Server









Direct TransferRANAPSAPI=0, NAS-PDU = Call Proceeding

Downlink Direct Transfer[DCCH] RRCCN domain = cs, NAS-PDU = CC-message: Call Proceeding

Direct TransferRANAPLAI, SAI, NAS-PDU = Setup

Uplink Direct Transfer[DCCH] RRCCN domain = cs, NAS-PDU = CC-message: Setup



Server

RAB Assignment RequestRANAPRABSetupOrModifyItem RAB Parameter

Radio Bearer Setup[DCCH] RRCRRC state = CELL_DCH, RAB to setup radio bearer to setup, signalling radio bearer, transport channels to add, physical channel

RAB Assignment ResponseRANAPsuccessful setup

Radio Bearer Setup Complete[DCCH] RRC

Direct TransferRANAPDownlink Direct Transfer[DCCH] RRC

Direct TransferRANAPLAI, SAI, NAS-PDU = Connect Ackn.

Uplink Direct Transfer[DCCH] RRCCN domain = cs, NAS-PDU = CC-message: Connect Ackn.

SAPI=0, NAS-PDU = AlertingCN domain = cs, NAS-PDU = CC-message: Alerting

Direct TransferRANAPDownlink Direct Transfer[DCCH] RRCSAPI=0, NAS-PDU = Connect

CN domain = cs, NAS-PDU = CC-message: Connect

call active

CELL_DCH



Server

Iu Release CommandRANAPcause = normal eventRRC Connection Release[DCCH] RRC

cause = normal eventIu Release CompleteRANAP

released RABRRC Connection Release Complete[DCCH] RRC

Direct TransferRANAPDownlink Direct Transfer[DCCH] RRC

Direct TransferRANAPLAI, SAI, NAS-PDU = Release

Uplink Direct Transfer[DCCH] RRCCN domain = cs, NAS-PDU = CC-message: Release

SAPI=0, NAS-PDU = Disconnect CN domain = cs, NAS-PDU = CC-message: Disconnect

Direct TransferRANAPDownlink Direct Transfer[DCCH] RRCSAPI=0, NAS-PDU = Release Complete

CN domain = cs, NAS-PDU = CC-message: Release Complete

UTRA_Idle


2. CS Call Services

2.2. Mobile Terminating Call (MTC)

• UE is UTRA idle;• no other services running;• call release by local party


2.2. Mobile Terminating Call (MTC) (1)UE RNC

UTRA_Idle

RRC Connection Request[CCCH] RRCInitial UE ID = IMSI|TMSI+LAI, Est.Cause = terminating conversational call|terminating cause unknown

MSC Server

Initial UE MessageRANAPCN domain = cs, LAI, SAI, RNC-ID,NAS-PDU = Paging Response



Initial Direct Transfer[DCCH] RRCCN domain = cs, NAS-PDU = MM-message: Paging Response

CELL_DCH|CELL_FACH

Paging Type 1[PCCH] RRCUE-ID = TMSI|IMSI, cause = terminating conversation call|terminating cause unknown

PagingRANAPCN domain = cs, LAI, IMSI, TMSI, cause


2.2. Mobile Terminating Call (MTC) (2)UE RNC MSC

Server









Direct TransferRANAPLAI, SAI, NAS-PDU = Call Confirmed

Uplink Direct Transfer[DCCH] RRCCN domain = cs, NAS-PDU = CC-message: Call Confirmed

Direct TransferRANAPSAPI=0, NAS-PDU = Setup

Downlink Direct Transfer[DCCH] RRCCN domain = cs, NAS-PDU = CC-message: Setup



Server


Radio Bearer Setup[DCCH] RRCRRC state = CELL_DCH, RAB to setup radio bearer to setup, signalling radio bearer, transport channels to add, physical channel



Direct TransferRANAPUplink Direct Transfer[DCCH] RRC

Direct TransferRANAPSAPI=0, NAS-PDU = Connect Ackn.

Downlink Direct Transfer[DCCH] RRCCN domain = cs, NAS-PDU = CC-message: Connect Ackn.

LAI, SAI, NAS-PDU = AlertingCN domain = cs, NAS-PDU = CC-message: Alerting


LAI, SAI, NAS-PDU = ConnectCN domain = cs, NAS-PDU = CC-message: Connect

call active

CELL_DCH



Server



released RABRRC Connection Release Complete[DCCH] RRC


Direct TransferRANAPSAPI=0, NAS-PDU = Release

Downlink Direct Transfer[DCCH] RRCCN domain = cs, NAS-PDU = CC-message: Release

LAI, SAI, NAS-PDU = Disconnect CN domain = cs, NAS-PDU = CC-message: Disconnect


LAI, SAI, NAS-PDU = Release CompleteCN domain = cs, NAS-PDU = CC-message: Release Complete

UTRA_Idle


3. PS Mobility Management



3.1. PS (GPRS) Attach

• UE is UTRA idle;• UE is PS detached;• no CS services running


3.1. PS (GPRS) Attach (1)UE

RNC

UTRA_Idle

RRC Connection Request[CCCH] RRCInitial UE ID = IMSI|TMSI+LAI, Est.Cause = registration

Initial UE MessageRANAPCN domain = ps, RAI, SAI, RNC-ID,NAS-PDU = Attach Request

GPRS activation (User)



Initial Direct Transfer[DCCH] RRCCN domain = ps, NAS-PDU = GMM-message: Attach Request

CELL_DCH|CELL_FACH

SGSN



RNC

Direct TransferRANAPSAPI=0, NAS-PDU = Authentication And

Ciphering Request

Downlink Direct Transfer[DCCH] RRCCN domain = ps, NAS-PDU = GMM-message: Authentication And Ciphering Request

Direct TransferRANAP[DCCH] RRC

RAI, SAI, NAS-PDU = Authentication AndCiphering Response

CN domain = ps, NAS-PDU = GMM-message: Authentication And Ciphering Response

Uplink Direct Transfer





Direct TransferRANAPSAPI=0, NAS-PDU = Attach Accept

Downlink Direct Transfer[DCCH] RRCCN domain = ps, NAS-PDU = GMM-message: Attach Accept

SGSN



RNC


RAI, SAI, NAS-PDU = Attach CompleteCN domain = ps, NAS-PDU = GMM-message: Attach Complete





UTRA_Idle

SGSN



3.2. Routing Area Update (IDLE mode update)

• UE is UTRA idle;• UE is PS attached;• performs cell reselection


3.2. Routing Area Update (IDLE) (1)UE RNC

UTRA_Idle

RRC Connection Request[CCCH] RRCInitial UE ID = IMSI|PTMSI+RAI|TMSI+LAI, Est.Cause = registration

Initial UE MessageRANAPCN domain = ps, RAI, SAI, RNC-ID,NAS-PDU = Routing Area Update Request

cell reselection

New RAI ?false

true



Initial Direct Transfer[DCCH] RRCCN domain = ps, NAS-PDU = GMM-message: Routing Area Update

Request

CELL_FACH|CELL_DCH

SGSN


3.2. Routing Area Update (IDLE) (2)UE

RNC


Ciphering Request










Direct TransferRANAPSAPI=0, NAS-PDU = Routing Area Update

Accept

Downlink Direct Transfer[DCCH] RRCCN domain = ps, NAS-PDU = GMM-message: Routing Area Update

Accept

SGSN


3.2. Routing Area Update (IDLE) (3)UE

RNC


RAI, SAI, NAS-PDU = Routing Area UpdateComplete

CN domain = ps, NAS-PDU = GMM-message: Routing Area UpdateComplete


Iu Release CommandRANAP

cause = normal eventRRC Connection Release[DCCH] RRCcause = normal event

Iu Release CompleteRANAPRRC Connection Release Complete[DCCH] RRC

UTRA_Idle

SGSN



3.3. Routing Area Update (Connected mode update)

• UE is UTRA connected for CS services;• UE is PS attached without Iu signalling connection, (PMM_IDLE);• UE performs cell reselection


3.3. Routing Area Update (Connected) (1)UE RNC

UTRA_Connected

Initial UE MessageRANAPCN domain = ps, RAI, SAI, RNC-ID,NAS-PDU = Routing Area Update Request

UTRAN Mobility Information[DCCH] RRC…, new RAI, …

UTRAN Mobility Information Confirm[DCCH] RRC…

Initial Direct Transfer[DCCH] RRCCN domain = ps, NAS-PDU = GMM-message: Routing Area Update

Request

CELL_FACH|CELL_DCH

SGSN


Ciphering Request







3.3. Routing Area Update (Connected) (2)UE

RNC





Direct TransferRANAPSAPI=0, NAS-PDU = Routing Area Update

Accept

Downlink Direct Transfer[DCCH] RRCCN domain = ps, NAS-PDU = GMM-message: Routing Area Update

Accept

SGSN


RAI, SAI, NAS-PDU = Routing Area UpdateComplete

CN domain = ps, NAS-PDU = GMM-message: Routing Area UpdateComplete


UTRA_Connected



3.4. PS (GPRS) Detach (no UE power off)

• UE is UTRA Idle• UE is PMM_Idle• GPRS is to be deactivated by user


3.4. PS (GPRS) Detach (no UE power off) (1)UE

RNC

UTRA_Idle

RRC Connection Request[CCCH] RRCInitial UE ID = IMSI|TMSI+LAI, Est.Cause = detach

Initial UE MessageRANAPCN domain = ps, RAI, SAI, RNC-ID,NAS-PDU = Detach Request

GPRS deactivation (User)



Initial Direct Transfer[DCCH] RRCCN domain = ps, NAS-PDU = GMM-message: Detach Request

CELL_DCH|CELL_FACH

SGSN



RNC


Ciphering Request










Direct TransferRANAPSAPI=0, NAS-PDU = Detach Accept

Downlink Direct Transfer[DCCH] RRCCN domain = ps, NAS-PDU = GMM-message: Detach Accept

SGSN



RNC




UTRA_Idle

SGSN


4. PDP Context Management



4.1. PDP Context Activation

• UE is UTRA idle,• UE is PMM_Idle (already registered for GPRS)• user or application activate PDP context


4.1. PDP Context Activation (1)UE

RNC

UTRA_Idle

RRC Connection Request[CCCH] RRCInitial UE ID = IMSI|TMSI+LAI, Est.Cause = originating <xxx> call

Initial UE MessageRANAPCN domain = ps, RAI, SAI, RNC-ID,NAS-PDU = Service Request

PDP Context request (User)



Initial Direct Transfer[DCCH] RRCCN domain = ps, NAS-PDU = GMM-message: Service Request

(service type = signalling)

CELL_DCH|CELL_FACH

SGSN


4.1. PDP Context Activation (2)UE

RNC


Ciphering Request










SGSN


RAI, SAI, NAS-PDU = Activate PDP ContextRequest

CN domain = ps, NAS-PDU = SM-message: Activate PDP Context Request



4.1. PDP Context Activation (3)UE RNC


Radio Bearer Setup[DCCH] RRCRRC state = CELL_DCH/FACH, RAB to setup radio bearer to setup, signalling radio bearer, transport channels to add, physical channel



SGSN

CELL_DCH|CELL_FACH

Direct TransferRANAPSAPI=0, NAS-PDU = Activate PDP Context

Accept

Downlink Direct Transfer[DCCH] RRCCN domain = ps, NAS-PDU = SM-message: Activate PDP Context Accept

Packet PDU Transmission



4.2. Service Data for uplink traffic

• UE is UTRA idle and PMM_Idle,• PDP context is active• uplink packet data shall be sent


4.2. Service Data for uplink traffic (1)UE

RNC

UTRA_Idle

RRC Connection Request[CCCH] RRCInitial UE ID = IMSI|TMSI+LAI, Est.Cause = high priority signalling


uplink PDP PDU




(service type = data)

CELL_DCH|CELL_FACH

SGSN


4.2. Service Data for uplink traffic (2)UE

RNC





SGSN





CELL_DCH|CELL_FACH




4.3. Service Data for downlink traffic

• UE is UTRA idle and PMM_Idle,• PDP context is active• downlink packet data shall be sent


4.3. Service Data for downlink traffic (1)UE

RNC

UTRA_Idle

RRC Connection Request[CCCH] RRCInitial UE ID = IMSI|TMSI+LAI, Est.Cause = terminating cause unkn.





(service type = paging response)

CELL_DCH|CELL_FACH

SGSN

Paging Type 1[PCCH] RRCUE-ID = TMSI|IMSI, cause = terminating cause unknown

PagingRANAPCN domain = ps, RAI, IMSI, PTMSI, cause


4.3. Service Data for downlink traffic (2)UE

RNC





SGSN





CELL_DCH|CELL_FACH




4.4. PDP Context Deactivation by UE

• UE is UTRA connected and PMM_Connected,• PDP context is active and will be deactivated,• ohter PS services are still active


4.4. PDP Context Deactivation (1)UE

RNC

UTRA_Connected

SGSN

PMM_Connected

Direct TransferRANAPSAPI=0, NAS-PDU = Deact.PDP Context

Accept

Downlink Direct Transfer[DCCH] RRCCN domain = ps, NAS-PDU = SM-message: Deactivate PDP Context Accept


RAI, SAI, NAS-PDU = Deact. PDP ContextRequest

CN domain = ps, NAS-PDU = SM-message: Deactivate PDP Context Request


RAB Assignment RequestRANAPRABReleaseItem RAB ID

Radio Bearer Release[DCCH] RRCRRC state = XXX, RAB to reconfigure, RB to release, TrCH to reconf.

RAB Assignment ResponseRANAPRAB data volume

Radio Bearer Release Complete[DCCH] RRC

UTRA_XXX


5. Radio Management Procedures



5.1. Soft Handover

• UE is UTRA connected in state CELL_DCH,• soft handover including cell 1, cell 2, cell 3


5.1. Soft Handover (1 – add radio link)UE

RNC

CELL_DCH

Measurement Report[DCCH] RRC

trigger event = 1A for cell 2, measured results

Measurement Control[DCCH] RRCintra-frequency cell list for cell 1, reporting criteria events 1A, 1B, 1C

cell 1

Active Set

Active Set Update[DCCH] RRCcell addition info downlink code information for cell 2

Active Set Update Complete[DCCH] RRC

Measurement Control[DCCH] RRCintra-frequency cell list for cell 1/2, reporting criteria events 1A, 1B, 1C

CELL_DCH cell 1, cell 2

Active Set


5.1. Soft Handover (2 – replacement)UE

RNC


trigger event = 1C for cell 3/1, measured results

Active Set Update[DCCH] RRCcell addition info downlink code information for cell 3cell removal info radio link id cell 1


Measurement Control[DCCH] RRCintra-frequency cell list for cell 3/2, removal of cell 1’s neighbour cell list,reporting criteria events 1A, 1B, 1C

CELL_DCH cell 3, cell 2

Active Set


5.1. Soft Handover (3 – radio link deletion)UE

RNC


trigger event = 1B for cell 2, measured results

Active Set Update[DCCH] RRCcell removal info radio link id cell 2


Measurement Control[DCCH] RRCremoval of cell 2’s neighbour cell list, reporting criteria events 1A, 1B, 1C

CELL_DCH cell 3

Active Set



5.2. Packet Radio Bearer Management

• UE is UTRA connected and PMM_Connected,• PDP context is active and RAB exists for it


5.2. Packet Radio Bearer Management (1)UE

RNC SGSN

Radio Bearer Release[DCCH] RRCRRC state = CELL_PCH/URA_PCH, radio bearer identitiy to release


Packet PDU TransmissionCELL_DCH|CELL_FACH

RB Inactivity Timer

CELL_PCH|URA_PCH

Expiry of all Inactivity Timers

uplink PDP PDU

Cell Update[CCCH] RRCU-RNTI, cause = uplink data transmission

Cell Update Confirm[CCCH] RRCU-RNTI, RRC state = CELL_DCH/FACG, radio bearer to set up



RNC SGSN


CELL_DCH|CELL_FACH

Radio Bearer Release[DCCH] RRCRRC state = CELL_PCH/URA_PCH, radio bearer identitiy to release



RB Inactivity Timer

CELL_PCH|URA_PCH

Expiry of all Inactivity Timers



RNC SGSN

Paging Type 1[PCCH] RRCU-RNTI


Cell Update[CCCH] RRCU-RNTI, cause = paging response

Cell Update Confirm[CCCH] RRCU-RNTI, RRC state = CELL_DCH/FACG, radio bearer to set up


CELL_DCH|CELL_FACH



RB Inactivity Timer

Umts Call Flows

Documents

medium access

forward access

dedicated

dedicated

transport

transport

common traffic

rate control