WCDMA UTRAN Interfaces and Protocol Stacks

UTRAUTRA-FDD Radio Communication
By David Soldani
NOKIA
3G Mobile Systems.PPT v.0.0.3/ March 2002 / David Soldani
UTRAN Interfaces and Protocol Stacks
NOKIA
Network Elements and Interfaces

Iub Interface: Transport Plane - ATM Control Plane - Communication Control Ports - Node B Control Ports User Plane - RACH/FACH/DCH Data Ports forming UE Context(s) Procedures - Radio Link (RL) Setup - RL Reconfiguration - RL Addition - RL Deletion - Power Control Information - Handover Signalling - Measurement Reports Iur Interface: Transport Plane - ATM Control Plane - RNSAP (SCCP over CCS7 ) User Plane - Frame Protocols for Dedicated Channels over ATM Procedures - Radio Link (RL) Setup - RL Reconfiguration - RL Addition - RL Deletion - Power Control Information - Handover Signalling - Measurement Reports
Uu Interface: Transport Plane - WCDMA (Wideband Code Division Multiple Access) Control Plane - DPDCH and DPCCH Channels User Plane - Optimized, application related protocols suitable for both packet and circuit switched traffic Procedures - RRC Connection Management - Radio Bearer control - RRC connection mobility - Measurement - General procedures
Node B
RNC
Iu Interface for CN Circuit Domain: Transport Plane - ATM Control Plane - RANAP over CCS7 User Plane - Optimized, application related protocols over ATM AAL2 Procedures - Radio Access Bearer Management - SRNC Relocation - Direct Transfer Procedures (Direct Signalling between UE and the CN Circuit Domain)
Node B
RNC
RNC Functions: Radio Resource Management - Admission Control - Code Allocation (RM) - Load Control - Power Control - Handover Control (HO) - Macro Diversity (Soft HO) Telecommunication Management - Radio Access Bearer (RAB) - RAB - Radio Link Mapping Transmission Management
Node B Functions: - Modulation - Rate Matching - Error Protection in Uu Interface - Uu Interface Channelisation - Macro Diversity (Softer Handover) - RRM: PC, LC, RM
Iu Interface for CN Packet Domain: Transport Plane - ATM Control Plane - RANAP over CCS7 or IP User Plane - GTP (GPRS Tunneling Protocol) over UDP/IP over AAL5 Procedures - Radio Access Bearer Management - SRNC Relocation - Direct Transfer Procedures (Direct Signalling between UE and the CN Packet Domain)
NOKIA
Cell is defined by a cell identification (C-ID), Configuration Generation ID, Timing delay (T_Cell), UTRA Absolute Radio Frequency Channel Number (UARFCN), Maximum transmission power, Closed Loop Timing Adjustment Mode and Primary scrambling code
Protocol Architecture
Set of defined rules or procedures
Protocol = 1...N Procedures Procedure = 1 ...N messages
Plane
Set of different protocols defined for common purpose
Layer N+1
Entity
SAP
Entity
SAP
Entity
Set of N Layer well defined protocols
SAP
Entity
Layer N -1
Entity
Primitive = 1...N interlayer data flows
Reference point between subsystems (domains)
SAP
Data exchange between layers
Entity
ELEMENT X (peer or entity)

4 NOKIA 3G Mobile Systems.PPT v.0.0.3/ March 2002 / David Soldani
ELEMENT Y (peer or entity)
Main reasons behind the layered architecture To handle the architectural complicity in very large communication systems by utilizing layered modelling To facilitate the system implementation and testing To support the system evolution by easing the modifications to the existing systems To support the service vs. system independence To ensure the system forward and backward compatibility Cost-efficiency in a large network environment with many NEs Common reference model (OSI, Open System Interconnection) Protocol A set of defined rules or procedures and conventions used by a specific layer in order to communicate with a similar peer or entity layer in another NE or subsystem Layer A set of well-defined functionalities or protocols in the context of the overall communication subsystem. A protocol layer can be implemented independently Plane A set of different protocols (including different layer) used for common purposes in a communication system (C-plane, U-Plan, transport plane A plane can be Uplane). C implemented independently Service Access Point A reference point between two immediately above and below protocol layers through which the layers can exchange data Interface A well-defined reference point between two subsystems (domains) in which the subsystems exchange information with a fully recognized manner
UTRAN specific protocols
UTRAN Interfaces Protocol Stacks

Radio Network Layer
CP (1) xxAP TNCP (2) ALCAP Transport Transport Transport UP (3) FPs
Transport Network Layer
(1) Control Plane: Interface Application Part (RANAP for Iu, RNSAP for Iur, NBAP for Iub) and signalling bearers (ex: SS7, CTP/IP) (2) Transport Network Control Plane: Signalling protocol (Access Link Control Application Part) + bearer, for the control of the transport channels in the user plane (ex Q.AAL2) (3) User Plane: Frame Protocols (FP) for user data transfer through the interface and the underlying transport protocols
IuUTRAN Iu-CS Interface Stack

Radio Network Layer
MSC
SGSN DRNC
SRNC
NB
Control Plane RANAP
User Plane Iu User Plane Protocol
UE
RAN Application Part is an evolution of BSSMAP. - Multi-bearer capability - New security features
Transport Network User Plane
Transport Network Control Plane Q.2630.1
Codec control information (Codecs in CN)
SCCP MTP3b SSCF-NNI SSCOP
Q.2150.1 MTP3b SSCF-NNI SSCOP AAL5 AAL2
SS7 Stack on SAAL-NNI
AAL5
ATM Physical Layer
One transport connection per Radio Access Bearer
NOKIA
RANAP Functions (UE Radio Access Bearer (UE - CN bearer) handling (combined procedure): RAB Set-up (Including Queuing) RAB Modification Clearing (release) RAB (Including RAN initiated case) Release: Iu Release Releases all Iu resources (Signaling link and U-Plane) related to the specified UE. Also includes RAN initiated case Relocation: Handling both SRNS Relocation (UE already in target RNC with Iur) and Hard Handover (simultaneous switch of Radio and Iu). Includes Loss-less relocation and Inter system Handover Paging: Paging CN to page an UE for a terminating call/connection ID: Common ID UE NAS Id sent to RNC for paging co-ordination Invocation: Trace Invocation CN may request UTRAN to start/stop tracing a specific UE Security Mode Control: Controls Ciphering and Integrity Checking Location Reporting: Requesting (CN) and reporting (RNC) UE location Reporting Data Volume Reporting: Requesting (CN) and reporting (RNC) Unsuccessfully Reporting transmitted DL data Message: Initial UE Message Carries the first Radio interface L3 message to the CN and sets up the Iu signalling connection. Direct Transfer: Carries CN and UE signalling information over Iu (content not Transfer interpreted by UTRAN) Broadcast: CN Information Broadcast This procedure allows the CN to set CN (NAS) related system information to be broadcast to all users Overload: Overload Used for flow control (to reduce flow) over the Iu interface e.g. due to processor overload at CN or UTRAN Reset: It is used to reset the CN or the UTRAN side of Iu interface in error situations (includes also resetting Signalling Connection) Indication: Error Indication Used for protocol errors where no other error applies
IuUTRAN Iu-PS Interface Stack

Radio Network Layer
MSC
SGSN DRNC
SRNC
Control Plane RANAP
User Plane Iu User Plane Protocol
NB UE
Same protocols as the Iu-CS

SCCP
Transport Network Control Plane
Typically no FP header (transparent mode)
Two options for signalling transport
MTP3-B SSCF-NNI SSCOP AAL5
M3UA SCTP IP
No signalled transport connections (no AAL2 connection establishment in TNL)
GTP-U UDP IP AAL5
User plane of the GPRS Tunnelling Protocol is used
ATM Physical Layer
ATM Physical Layer
NOKIA
UTRAN Iur Interface Stack

Composed by 3 modules: 1 Basic mobility 2 Dedicated transport 3 Common transport
Radio Network Layer
MSC
SGSN DRNC
SRNC
Control Plane RNSAP
User Plane
UE
NB
DCH FP
CCH FP

Q.2630.1
SCCP MTP3-B SSCF-NNI M3UA SCTP IP AAL5
Q.2150.1 MTP3-B SSCF-NNI SSCOP AAL5 M3UA SCTP IP AAL2
Dedicated and Common Channel Frame Protocol - Frame transfer - Synchronisation - Power control - ...
Two options (IP and ATM based) for the signalling bearers
SSCOP
Each dedicated channel has a dedicated transport connection
ATM Physical Layer
NOKIA
RNSAP Functions Management: Radio Link Management This function allows the SRNC to manage radio links using dedicated resources in a DRNS Physical Channel Reconfiguration: This function allows the DRNC to reallocate the physical channel resources for a Radio Link Supervision: Radio Link Supervision This function allows the DRNC to report failures and restorations of a Radio Link [FDD FDD]: Compressed Mode Control [FDD]: This function allows the SRNC to control the usage of compressed mode within a DRNS Measurements on Dedicated Resources: This function allows the SRNC to initiate measurements on dedicated resources in the DRNS. The function also allows the DRNC to report the result of the measurements [FDD FDD]: DL Power Drifting Prevention [FDD]: This function allows the SRNC to adjust the DL power level of one or more Radio Links in order to avoid DL power drifting between the Radio Links CCCH Signalling Transfer: This function allows the SRNC and DRNC to pass information between the UE and the SRNC on a CCCH controlled by the DRNS Paging: Paging This function allows the SRNC to page a UE in a URA or a cell in the DRNS Common Transport Channel Resources Management: This function allows the SRNC to utilise Common Transport Channel Resources within the DRNS (excluding DSCH resources for FDD) Relocation Execution: This function allows the SRNC to finalise (commit) a Relocation previously prepared via other interfaces Reporting general error situations: This function allows reporting of general error situations, situations for which function specific error messages have not been defined
UTRAN Iub Interface Stack

Common NBAP to initialise UE context at the set-up of the first RL, and Logical O&M Dedicated NBAP for UE related signalling One signalling connection per traffic termination point in Node B. Simple SAAL-UNI stack
Radio Network Layer
MSC
SGSN DRNC
SRNC
Control Plane NBAP
User Plane DCH FP CCH FP
NB UE

Q.2630.1
Q.2150.2 SSCF-UNI SSCOP AAL5 SSCF-UNI SSCOP AAL5 AAL2
Iub DCH FP is the same as Iur DCH FP (no user plane processing in DRNC, only MDC possible)
ATM Physical Layer
NOKIA
NBAP Functions Cell Configuration Management: This function gives the CRNC the possibility to manage the cell configuration information in a Node B Common Transport Channel Management: This function gives the CRNC the Management possibility to manage the configuration of Common Transport Channels in a Node B System Information Management: This function gives the CRNC the ability to manage the scheduling of System Information to be broadcast in a cell Resource Event Management: This function gives the Node B the ability to inform the Management CRNC about the status of Node B resources Configuration Alignment: This function gives the CRNC and the Node B the possibility to verify that both nodes has the same information on the configuration of the radio resources Measurements on Common Resources: This function allows the CRNC to initiate measurements in the Node B. The function also allows the Node B to report the result of the measurements (e.g. Ptx/rx_Total) Synchronisation Management (TDD): This function allows the CRNC to manage the synchronisation of a TDD cell in a Node B Management: Radio Link Management This function allows the CRNC to manage radio links using dedicated resources in a NodeB Supervision: Radio Link Supervision This function allows the CRNC to report failures and restorations of a Radio Link Measurements on Dedicated Resources: This function allows the CRNC to initiate measurements in the Node B. The function also allows the NodeB to report the result of the measurements (e.g. RL power) DL Power Drifting Correction (FDD): This function allows the CRNC to adjust the DL (FDD) power level of one or more Radio Links in order to avoid DL power drifting between the Radio Links Reporting general error situations: This function allows reporting of general error situations, for which function specific error messages have not been defined
CRNC
Node B
RADIO LINK SETUP REQUEST
Radio Link
Logical Def: Logical association between single E and a single UTRAN access point
Parameter RL Information
RADIO LINK SETUP RESPONSE
BTS id DCHs information DSCH Information DL Channelisation code number DL Scrambling code Min UL/DL Channelisation Code length UL/DL TFCS DL TPC DL Power Step Size UL DPCCH and DL DPCH slot formats Power Offset Information UL SIR Target PDSCH information Limited Power Increase Uplink puncture Limit Max Number of UL DPDCHs Uplink scrambling code
Description RL ID, C-ID, First RLS Indicator, Frame Offset, Chip Offset, Propagation Delay, Diversity Control Field, DL Code Information, Initial DL transmission Power, Maximum DL power, Minimum DL power, SSDT Cell Identity, Transmit Diversity Indicator, Transmission Gap Pattern Sequence Information, Active Pattern Sequence Information Identifier of the base station end of the radio link For each DCH: UL TFS, DL TFS, CRC presence, etc DSCH ID, Transport Format Set, Allocation/Retention Priority, Frame Handling Priority DL Channelization code DL Scrambling code (Shall be cell based) Identifiers of the spreading codes to be used in the uplink/ downlink UL/DL DPCH Transport Format Combination Set DL TPC power step size for inner loop PC Slots format to be used PO1, PO2 and PO3, DL DPCCH offsets (TFCI, TPC, Pilots) with respect to DPDCH symbols UL initial SIR Target in the WCDMA BTS PDSCH RL ID and code mapping Parameters for downlink limited power increase algorithm Limit used by the UE Uplink multicode transmission information Identifier of the long code to be used in uplink transmission. Same code will probably be used for all the radio links of one terminal
10
NOKIA
link: Radio link: A "radio link" is a logical association between single User Equipment and a single UTRAN access point. Its physical realization comprises one or more radio bearer transmissions. An UE can have more than one RL (softer or soft HO). Each RL is comprised of all the channel codes (DPDCH's) that are associated with the same physical layer control channel (DPCCH). Radio Link modification: actions which effect the RL bit rate or bit rates of its RABs, as well as the RAB additions and releases
Access link between UE and CN

GMM) Services and control protocols (CC, MM, SM, GMM)
Non-Access Stratum Non-Access -
Radio Access Bearers
ACCESS LINK
Signalling connection
RRC connection
Iu connection
Access Stratum Access Stratum Access Stratum Access Stratum
Radio Bearer service Radio protocols
Iu bearer service Iu protocols
UE
UTRAN
CN
: SAP
11 NOKIA
Uu
Iu
NonStratum, Non-Access Stratum contains CN related signaling and services. Stratum, The Access Stratum handles all access dependent issues, and offers services to the Non-Access Stratum over Service Access Points (SAP) in the UE and the CN. It provides the Access Link between UE and CN. The Access Link consists of: One or more independent and simultaneous UE-CN Radio Access Bearer connections, connections and A Signaling Connection between the upper layer entities [CM/SM, CS/PS MM] of UE and CN. The Signaling connection is comprised of two parts: RRC connection connection); (signalling connection); and Iu connection (expands the RRC connection the terminates in UTRAN to CN) The protocols over Uu and Iu interfaces are divided into two planes: User plane protocols, that are implementing the actual radio access bearer service, User protocols carrying user data through the access stratum. Control plane protocols that are controlling the radio access bearers and the Control protocols, connection between UE and the network.
Radio Interface Protocols

CC, MM, GMM, SM
C-plane signalling
RABs
U-plane information
sublayers/NAS Higher L3 sublayers/NAS
control RRC control control control control PDCP PDCP
L3 L2/PDCP L2/PDCP
BMC
L2/BMC L2/BMC
Transport CHannel bit rate user bit rate added by the L2 header bit rate
RLC
RLC
RLC
RLC RLC RLC
RLC RLC
L2/RLC L2/RLC CHannels, Logical CHannels, MAC provides logical channels for data transfer services to the layers above MAC L2/MAC CHannels, Transport CHannels, information transfer service, which L1 offers to MAC and higher layers
MAC
PHY
L1
The radio interface protocols are needed to set up, reconfigure and release the Radio Bearer services
The radio interface protocols are needed to set up, reconfigure and release the Radio Bearer services. The radio interface consists of three protocol layers The physical layer (L1); The data link layer (L2); and The network layer (L3). Layer 2 contains the following sub layers Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Broadcast/Multicast Control (BMC). RLC is divided into Control (C) and User (U) planes, whilst PDCP and BMC exist only in the U-plane. Layer 3 consists of one protocol, denoted Radio Resource Control (RRC), which belongs to the C-plane. Each block represents an instance of the corresponding protocol. The dashed lines represent the control interfaces through which the RRC protocol controls and configures the lower layers. The service access points between MAC and physical layer and between RLC and MAC sub layers provide the transport channels (TrCHs) and the logical channels (LoCHs), respectively. The TrCHs are specified for data transport between physical layer and Layer 2 peer entities, whereas logical channels whereas radio interface. define the transfer of a specific type of information over the radio interface
CS side protocol stack (UP)

Uu UE
E.g. Vocoder RLC-U MAC
WCDMA L1
Iub
Transparent mode
Iu
Transcoding function
A IWU
E.g. Vocoder Iu -CS UP AAL2 ATM PHY A/m-law PCM, UDI, etc.
MSC
A/m-law PCM, UDI, etc. Link Layer PHY PHY
RNC Node B
FP
WCDMA L1
RLC-U MAC FP AAL2 ATM PHY Iu -CS UP AAL2 ATM PHY
PSTN/ N-ISDN
AAL2 ATM PHY
Link Layer PHY
SDH/PDH
13
NOKIA
Medium Access Control protocol (MAC) The MAC is responsible for mapping of LoCH(s) onto appropriate TrCH(s). MAC selects the appropriate TF within an assigned TFS for each active TrCH depending on source rate (efficient use of transport channels), given the TFCS assigned by RRC. Priority handling between data flows of one UE (selecting a TFC for which high priority data is mapped onto L1 with a "high bit rate" TF). Priority handling between UEs by means of dynamic scheduling (MAC realizes priority handling on common and shared transport channels). Identification of UEs on common transport channels (need for inband identification, the identification functionality is naturally also placed in MAC). Mux/demux of RLC PDUs into/from TBs delivered to/from the physical layer on CCHs (service (LoCHs) multiplexing for CCHs). Mux/demux of RLC PDUs into/from TBSs delivered to/from the physical layer on DCHs (service (LoCHs) multiplexing for DCHs). Traffic volume monitoring (measurement of traffic volume on logical channels and reporting to RRC, based on the reported traffic volume information, RRC performs transport channel switching decisions). Dynamic TrCH type switching (execution of the switching between common and dedicated transport channels). Ciphering (for transparent RLC mode). Access Service Class (ASC) selection for RACH transmission (i.e. RACH subchannel groups may be divided between different ASCs in order to provide different priorities of RACH usage).
PS side protocol stack (UP)

Segmentation & reassembling (UM/AM)
UE
E.g. IPv4, IPv6
Uu
Iub
Header compression (no payload compression)
Header for packet directing (UP only - RANAP otherwise)
Iu RNC
PDCP RLC-U MAC FP AAL2 ATM PHY GTP-U UDP IP
LLC/SNAP
Gn 3G- SGSN
GTP-U UDP IP
LLC/SNAP
GGSN
E.g. IPv4, IPv6
Gi
PDCP RLC-U MAC

WCDMA L1
TF scheduling and LoCH multiplexing
GTP UDP IP Link Layer PHY
GTP UDP IP Link Layer PHY PHY
Node B
FP
WCDMA L1
AAL2 ATM PHY
AAL5 ATM PHY
AAL5 ATM PHY
UP only
14
NOKIA
(RLC RLC) Radio Link Control protocol (RLC) Provides segmentation (payloads units, PU) and retransmission services for both user (Radio Bearer) and control data (Signalling Radio Bearer) Each RLC instance is configured by RRC to operate in one of the three modes: Tr), Transparent mode (Tr no protocol overhead is added to higher layer data Tr UM), Unacknowledged Mode (UM no retransmission protocol is in use and data delivery is UM not guaranteed AM), ARQ) Acknowledged Mode (AM Automatic Repeat reQuest (ARQ mechanism is used for AM Q ARQ error correction For all RLC modes, the CRC error detection is performed on the physical layer and the results of the CRC is delivered to the RLC together with the actual data (provided that the RLC PDUs are mapped one-to-one onto the Transport Blocks) Flow control Protocol error detection and recovery Ciphering Etc... Packet Data Convergence Protocol (PDCP) Exists only in the user plane and only for services from the PS domain Contain header compression/decompression methods, which are needed to get better spectral efficiency for service requiring IP packets to be transmitted over the radio interface Every PDCP compression entity uses zero, one or several compression algorithms type with a set of configurable parameters Several PDCP entities may use the same algorithm type The algorithm type and their parameters are negotiated during the RRC RAB establishment or reconfiguration procedures and indicated to the PDCP through the PDCP control service AP
Control plane
Uu
GMM / SM / SMS Relay RRC RLC-C MAC FP WCDMA L1 WCDMA L1 AAL2 ATM PHY FP AAL2 ATM PHY RANAP SCCP
Signalling Bearer
I ub
Iu
(PS)
GMM / SM / SMS RANAP SCCP
Signalling Bearer
RRC RLC-C MAC
AAL5 ATM PHY
AAL5 ATM PHY
UE
15 NOKIA
Node B
RNC
3G SGSN
Radio Resource Control protocol (RRC) RRC messages carry all parameters required to set-up, modify and release layer 2 and layer 1 protocol entities. Also, RRC messages carry in their payload all higher layer signalling (MM, CM). The mobility of the user equipment in the connected mode is controlled by RRC signalling (measurements, handover, cell update, etc.). After power on, the UE stays in Idle Mode until it transmits a request to establish an RRC Connection. In Idle Mode the connection of the UE is closed on all layers of the Access Stratum; the UE is identified by NAS identities such as IMSI TMSI and PIMSI, TMSI (Packet- TMSI); UTRAN has no own information about the individual Idle Mode UEs, and it can only address e.g. all UEs in a cell or all UEs monitoring a paging occasion. The UTRAN Connected Mode is entered when the RRC Connection is established. The UE is assigned a Radio Network Temporary Identity (RNTI) to be used as UE (RNTI RNTI) identity on common transport channels. The transition to the UTRAN Connected Mode from the Idle Mode can only be initiated by the UE by transmitting a request for an RRC Connection. The event is triggered either by a paging request from the network or by a request from upper layers in the UE. (UTRAN UE) RRC connection released procedure (UTRAN UE): the purpose of this procedure is to release the RRC connection including the signalling link and all RBs between the UE and the UTRAN. By doing so, all established signalling flows and signalling connections will be released. Frame Protocol The FP protocol layer is an Iub/Iur user plane protocol on top of AAL2 which is used to transfer user data, plus the necessary control information, between the SRNC and BTS; the FP protocol is also used to support some simple procedures e.g. timing adjustment, OLPC, etc... Frame structure: Payload contains the data (typically one or more MAC PDUs); Payload, Header/trailer, Header/trailer contains control information used for example for synchronization, power control, etc
RRC States and State Transitions

UTRA Connected Mode (Allowed transitions)
GSM Connected Mode GSM-UTRA Inter-system Handover
URA_ URA_PCH
12 11
CELL_PCH CELL PCH

10
GPRS Packet Transfer Mode
Only by Paging 2 5 7
Establish RR Connection
Release RR Connection Initiation of temporary block flow
Cell reselection
CELL_DCH CELL_DCH
4 1
CELL_FACH CELL_FACH
8
Release of temporary block flow
Release RRC Connection
Establish RRC Connection
Release RRC Connection
Establish RRC Connection
13
GPRS Packet Idle Mode Camping on a GSM / GPRS cell
Camping on a UTRAN cell
Idle Mode
16
NOKIA
1) Via explicit signalling when all dedicated channels have been released; 2) Via explicit signalling; 3) Via explicit signalling; 4) The RRC Connection mobility is handled by measurement reporting and soft/hard handover procedure; 5) Via explicit signalling when a dedicated physical channel is established; 6) Via explicit signalling when UTRAN orders the UE to move to CELL_PCH state; 7) Via explicit signalling when UTRAN orders the UE to move to URA _PCH state; 8) The UE monitors the broadcast channel and its location is known on cell level; 9) By paging from UTRAN (PAGING TYPE1 message) or through any uplink access; 10) The UE may use Discontinuous Reception (DRX), monitors the broadcast channel and its mobility is performed through cell reselection procedures moving to Cell_FACH state; 11) By paging from UTRAN (PAGING TYPE1 message) or uplink access using RACH; 12) The UE may use Discontinuous Reception (DRX), monitors the broadcast channel and its mobility is performed through URA reselection procedures moving to CELL_FACH state; 13) The connection of the UE is closed on all layers of the AS (the UE is identified by NAS identities such as IMSI, TMSI and P-TMSI)
RRC states Cell_DCH Cell_DCH; in this state the dedicated physical channel (DPCH), plus eventually the physical downlink shared channel (PDSCH), is allocated to the UE. Is entered from the idle mode or by establishing a dedicated transport channel (DCH) from Cell_FACH state. In this state the UE performs measurements according to the RRC: MEASUREMENT CONTROL message. The transition from Cell_DCH to Cell_FACH can occur either through the expiration of an inactivity timer or via explicit signalling. Cell_FACH Cell_FACH; in this state no DPCH is allocated to the UE, the random access transport channel (RACH) and the forward transport channel (FACH) are used instead, for transmitting signalling and small amount of user data. The UE listens to the BCH system information and moves to Cell_PCH sub-state via explicit signalling when the inactivity timer on FACH expires. Cell_PCH Cell_PCH; in this state the UE location is known by the SRNC on a cell level, but it can be reached only via a paging message. This state allows low battery consumption. The UE may use Discontinuous Reception (DRX), reads the BCH to acquire valid system information and moves to Cell_FACH if paged by the network or through any uplink access, e.g. initiated by the terminal for cell reselection (cell update procedure). URA_ URA_PCH; this state is similar to Cell_PCH, except that the UE executes the cell update procedure only if the UTRAN Registration Area (URA) is changed. One cell can belong to one or several URAs in order to avoid ping-pong effects. When the number of cell updates exceeds a certain limit, the UE may be moved to URA_PCH state via explicit signalling. The DCCH cannot be used in this state and any activity can be initiated by the network via a paging request on PCCH or through an uplink access by the terminal using RACH.
States of Bearer Allocations

RRC connection established RRC connection released
Both RACH / FACH and DCH possible

First RT bearer setup
RRC connection (no bearers allocated)
First NRT bearer setup
Last RT bearer released
Last NRT bearer released
Real time bearer(s) allocated

RT bearer setup Last NRT bearer released Last RT bearer released
Non-real time bearer(s) allocated

NRT bearer setup
NRT bearer setup
Real time and non-real time bearers allocated
RT bearer setup
Only DCH allocation possible

RT or NRT bearer setup
(RAB RAB) Radio Access Bearer (RAB): service provided by the Access Stratum to the NonAccess Stratum for transferring user data between UE and CN (a bearer is described by a set of parameters/attributes of particular traffic aspects or Quality of Service (QoS) aspects for an application/service) Radio Bearer (RB): service provided by the access stratum that runs on top of layer 2 (RB) RB between UE and UTRAN
Logical channels (1/2)

Control Channels

Control channels are used for transfer of control plane information only Broadcast Control Channel (BCCH) Paging Control Channel (PCCH) Common Control Channel (CCCH) Dedicated Control Channel (DCCH) Traffic channels are used for transfer of user plane information only Dedicated Traffic Channel (DTCH) Common Traffic Channel (CTCH)
Traffic Channels

18
NOKIA
The data transfer services of the MAC layer are provided on logical channels. The type of information transferred defines each logical channel type. The logical channels are divided into two groups Control Channels and Traffic Channels. The control channels are used for transfer of control plane information and the traffic channels are used for the transfer of user plane information only. Control Channels (BCCH BCCH) Broadcast Control Channel (BCCH), for broadcasting system control information in the downlink. (PCCH PCCH) Paging Control Channel (PCCH), for transferring paging information in the downlink (used when the network does not know the cell location of the UE, or, the UE is in cell-connected state). (CCCH CCCH) Common Control Channel (CCCH), for transmitting control information between the network and UEs in both directions (commonly used by UEs having no RRC connection with the network and by UEs using common transport channels when accessing a new cell after cell reselection). (DCCH DCCH) Dedicated Control Channel (DCCH). Point-to-point bi-directional channel for transmitting dedicated control information between the network and a UE (established through RRC connection set up procedure). Traffic Channels (DTCH DTCH) Dedicated Traffic Channel (DTCH). Point-to-point channel, dedicated to one UE for the transfer of user information (a DTCH can exist in both uplink and downlink directions). Common Traffic Channel (CTCH). Point-to-multipoint unidirectional channel for (CTCH) transfer of dedicated user information for all or a group of specified UEs.
Logical Channels (2/2)

UpLink DownLink BCCH PCCH CCCH CTCH DTCH/ DTCH/DCCH MAC SAPs
Logical Channels
CCCH
DTCH/ DTCH/DCCH
Transport Channels
RACH CPCH DCH

(FDD only)
BCH PCH
FACH
DSCH DCH
BCCH BCH CCCH CCH CPCH CTCH DCCH

19 NOKIA
Broadcast Control Channel Broadcast Channel Common Control Channel Control Channel Common Packet Channel Common Traffic Channel Dedicated Control Channel
DCH DSCH DTCH FACH PCCH PCH RACH
Dedicated Channel Downlink Shared Channel Dedicated Traffic Channel Forward Access Channel Paging Control Channel Paging Channel Random Access Channel
Transport Channels (1/3)

TrCH 1 TrCH 2
Transport Block
Transport Block
TB & Error Indication
TFI
Transport Block
TFI
Transport Block
TFI
TFI
Higher Layers Physical Layer

TFCI Coding & Multiplexing TFCI Decoding De-multiplexing & Decoding De-
Physical Control CHannel
Physical Data CHannels
Physical Control CHannel
Physical Data CHannels
20
NOKIA
In UTRAN the data generated at higher layers is carried over the radio interface using transport channels mapped onto different physical channels. The physical layer has been designed to support variable bit rate transport channels to offer bandwidth-onchannels, demand services, and to be able to multiplex several services within the same RRC connection. The single output data stream from the coding and multiplexing unit is denoted Coded Composite Transport Channel (CCTrCH). A CCTrCH is carried by (CCTrCH) one physical control channel and one or more physical data channels. In general there can be more than one CCTrCH, but only one physical control channel is transmitted on a given connection. In 3GPP all TrCHs are defined as unidirectional, i.e. uplink, downlink, or relay-link. unidirectional Depending on services and state, the UE can have simultaneously one or several TrCHs in the downlink, and one or more TrCHs in the uplink. For each TrCH, at any Transmission Time Interval (TTI) the physical layer receives TTI) (TTI from upper layers a set of Transport Blocks and the corresponding Transport Format (TFI TFI) Indicator (TFI). Then Layer 1 combines the TFI information received from different TrCHs to the (TFCI TFCI) Transport Formant Combination Indicator (TFCI). The TFCI is transmitted in the physical control channel to inform the receiver about what TrCHs are active in the current radio frame. In the downlink, in case of limited TFCSs the TFCI signalling may be omitted and Blind Transport Format Detection (BTFD) can be employed, where the TrCHs (BTFD) BTFD decoding can be done verifying in which position of the output block is matched with the CRC results.

Common channels

Resource divided between all or a group of users in a cell Broadcast Channel (BCH) Forward Access Channel (FACH) Paging Channel (PCH) Random Access Channel (RACH) Uplink Common Packet Channel (CPCH) Downlink Shared Channel (DSCH) Resource reserved for a single user Dedicated Transport Channels (DCH)
Dedicated channel

21
NOKIA
Dedicated transport channels The only dedicated transport channel specified in 3GPP is the Dedicated Channel (DCH), which support DCH) variable bit rate and services multiplexing. It is reserved for a single user. It carriers all user information coming from higher layers, including data for the actual service (speech frames, data, etc.) and control information (measurement control commands, UE measurement reports, etc.). It is mapped on the Dedicated Physical Data Channel (DPDCH). The DPCH is characterized by inner loop PC and fast data rate change on a frame-by-frame basis; it can be transmitted to part of the cell and supports soft/softer handover. Common transport channels The common transport channels are resource divided between all or a group of user in a cell (an in band identifier is needed). They do not support soft/softer HO, but some of them can have fast PC, e.g. Common Packet Channel (CCPCH) and slow PC, e.g. Downlink Shared Channel (DSCH), Forward Access Channel (FACH) (BCH), Broadcast Channel (BCH) it is used to transmit information (e.g. random access codes, cell access slots, cell type transmit diversity methods, etc.) specific to the UTRA network or to a given cell; is mapped onto the Primary Common Control Physical Channel (P-CCPCH), which is a downlink data channel, only. (FACH), Forward Access Channel (FACH) it carries downlink control information to terminals known to be located in the given cell. It is further used to transmit a small amount of downlink packet data. There can be more than one FACH in a cell, even multiplexed onto the same Secondary Common Control Physical Channel (S-CCPCH). The S-CCPCH may use different offsets between the control and data field at different symbol rate and may support slow PC. (PCH), Paging Channel (PCH) it carries data relevant to the paging procedure. The paging message can be transmitted in a single or several cells, according to the system configuration. It is mapped onto the SCCPCH. Random Access Channel (RACH), it carries uplink control information, such as a request to set up an (RACH) RRC connection. It is further used to send small amounts of uplink packet data. It is mapped onto the Physical Random Access Channel (PRACH). Uplink Common Packet Channel (CPCH), it carries uplink packet-based user data. It supports uplink inner (CPCH) loop PC, with the aid of a downlink Dedicated Physical Control Channel (DPCCH). Its transmission may span over several radio frames and it is mapped onto the Physical Common Packet Channel (PCPCH). (DSCH), Downlink Shared Channel (DSCH) it carries dedicated user data and/or control information and it can be shared in time between several users. It is as a pure data channel always associated with a downlink DCH. It supports the use of downlink inner loop PC, based on the associated uplink DPCCH. It is mapped onto the Physical Downlink Shared Channel (PDSCH). The common transport channels needed for the basic cell operation are RACH, FACH and PCH, while the use of the DSCH and CPCH may or may not be used by the operator.

DCH RACH CPCH BCH FACH PCH SCH DSCH PDSCH AICH PICH
DPDCH DPCCH PRACH PCPCH CPICH P-CCPCH S-CCPCH
(Dedicated Physical Data Channel) (Dedicated Physical Control Channel) (Physical Random Access Channel) (Physical Common Packet Channel) (Common Pilot Channel) (Primary Common Control Physical Channel) (Secondary Common Control Physical Channel) (Synchronisation Channel) (Physical Downlink Shared Channel) (Acquisition Indication Channel) (Page Indication Channel)
Mapping of transport channels onto physical channels One UE can transmit only one CCTrCH at once, but multiple CCTrCHs can be simultaneously received in the forward (downlink) direction. In the uplink one TFCI represents the current TFs of all DCHs of the CCTrCH. RACHs are always mapped one-to-one onto physical channels (PRACHs), i.e. there is no physical layer multiplexing of RACHs. Further, only a single CPCH of a CPCH set is mapped onto a PCPCH, which employs a subset of the TFCs derived by the TFS of the CPCH set. A CPCH set is characterized by a set-specific scrambling code for access preamble and collision detection, and it is assigned to the terminal when a service is configured for CPCH transmission. In the downlink the mapping between DCHs and physical channel data streams works in the same way as in the reverse direction. The current configuration of the coding and multiplexing unit is either signalled (TFCI) to the terminal, or optionally blindly (Blind TF Detection - BTFD) detected. Each CCTrCH has only zero or one corresponding TFCI mapped (each 10 ms radio frame) on the same DPCCH used in the connection. When the DSCH is employed in the communication, the DSCH TFI also indicates the channelisation code used for the shared channel. A PCH and one or several FACH can be encoded and multiplexed together forming a CCTrCH, one TFCI indicates the TFs used on each FACH and PCH carried by the same S-CCPCH. The PCH is always associated with the Paging Indicator Channel (PICH), which is used to trigger off the UE reception of S-CCPCH where the PCH is mapped. A FACH or a PCH can also be individually mapped onto a separate physical channel. The BCH is always mapped onto the P-CCPCH, without any multiplexing with other transport channels.
Formats and Configurations (1/2)

Transport Format Combination (TFC) Transport Format Combination Set (TFCS)
TB Transmission Time Interval
TB TTI
TB TTI
DCH1
Transport Block Transport Block TB TTI Transport Block TTI
Transport Block Set (TBS)
TB TB TTI
DCH2
Transport Format Set (TFS)
Transport Format (TF)
Transport Format: One Dynamic Part (Transport Block Size, Transport Block Set Size); and One Semi-Static Part (TTI, type of EP [turbo code, convolutional code or no channel coding], coding rate, static RM parameter, size of CRC) emi23 NOKIA 3G Mobile Systems.PPT v.0.0.3/ March 2002 / David Soldani
(TB), Transport Block (TB) it is the basic unit exchanged between L1 and MAC for L1 processing; a TB typically corresponds to an RLC PDU or corresponding unit; layer 1 adds a CRC to each TB. (TBS), Transport Block Set (TBS) it is defined as a set of TBs, which are exchanged between L1 and MAC at the same time instance using the same transport channel. Transport Block Size, it is defined as the number of bits in a TB; the Transport Block Size Size is always fixed within a given TBS, i.e. all TBs within a TBS are equally sized. Transport Block Set Size, it is defined as the number of bits in a TBS. Size (TTI TTI) Transmission Time Interval (TTI), it is defined as the inter-arrival time of TBSs, and is equal to the periodicity at which a TBS is transferred by the physical layer on the radio interface. It is always a multiple of the minimum interleaving period (i.e. 10 ms, the length of one Radio Frame). MAC delivers one TBS to the physical layer every TTI. (TF TF) Transport Format (TF), it is the format offered by L1 to MAC (and vice versa) for the delivery of a TBS during a TTI on a given TrCH. It consists of one dynamic part (Transport Block Size, Transport Block Set Size); and one semi-static part (TTI, type semiof error protection [turbo code, convolutional code or no channel coding], coding rate, static RM parameter, size of CRC). Transport Format Set (TFS), it is a set of TFs associated to a TrCH. The semi-static (TFS) parts of all TFs are the same within a TFS. TB size, TBS size and TTI define the TrCH bit rate before L1 processing. Depending on the type of service carried by the TrCH, the variable bit rate may be achieved by changing between TTIs either the TBS Size only, or both the TBS and TBS Size. Transport Format Combination (TFC), is an authorised combination of the currently (TFC) valid TFs that can be simultaneously submitted to layer 1 on a CCTrCH of a UE, i.e. containing one TF from each TrCH being a part of the combination.
Formats and configurations (2/2)

Relations of transport format, transport format set and transport format combination
Transport Format Combination x Transport Format Combination x+1 Transport Transport Transport Transport format set format set format set format set
TrCH1 TrCH2
TrCHn
Transport Format
24
NOKIA
Note: 1 RAB can have more than 1 TrCH, e.g. 144 kbps 2x64kbps DCHs The TFCS may be produced as a Cartesian product between TFSs of the TrCHs that are multiplexed onto a CCTrCH, each one of those considered as a vector. In theory every TrCH can have any TF in the TFC, but in practise only a limited number of possible combinations are selected. (TFCS), Transport Format Combination Set (TFCS) it is defined as a set of TFCs on a CCTrCH and a proprietary algorithm in the RNC produces it. The TFCS is what is given to MAC by L3 for control. When mapping data onto L1, MAC chooses between the different TFCs specified in the TFCS. MAC has any and only control over the dynamic-part of the TFC, since the semi-static part corresponds to the service attributes (quality, transfer delay) set by the admission control in the RNC. The selection of TFCs can be seen as the fast part of the radio resource control dedicated to MAC, close to L1. Thereby the bit rate can be changed very fast, without any need of L3 signalling. TFI) Transport Format Indicator (TFI), as pointed out in the introduction, it is a label for a (TFI specific TF within a TFS. It is used in the inter-layer communication between MAC and L1, each time a TBS is exchanged between the two layers on a transport channel. Transport Format Combination Indicator (TFCI), as explained alredy, it is used in (TFCI) order to inform the receiving side of the currently valid TFC, and hence to decode, demultiplex and transfer the received data to MAC on the appropriate TrCHs. MAC indicates the TFI to L1 at each delivery of TBSs on each TrCH. L1 then builds the TFCI from the TFIs of all parallel TrCHs of the UE, processes the TBs and appropriately appends the TFCI to the physical control signalling (DPCCH). Through the detection of the TFCI the receiving side is able to identify the TFC.
Function of the Physical Layer

FEC encoding/decoding of transport channels, measurements and indication to higher layers (e.g. BER, SIR, interference power, transmission power, etc.) Macro diversity distribution/combining and softer handover execution Error detection on transport channels (CRC) Multiplexing of transport channels and de-multiplexing of CCTrCHs, rate matching, mapping of CCTrCHs on physical channels Modulation/demodulation and spreading/despreading of physical channels, frequency and time (chip, bit, slot, frame) synchronisation, closed-loop power control (inner loop PC), power weighting, combining of physical channels RF processing
See references for more information.
MAC and higher layers
Uplink TrCH Multiplexing

Rate matching
Spreading/Scrambling and Modulation
CCTrCH
Physical channel mapping
2nd interleaving /RF
TrCH Multiplexing
Physical channel segmentation
Radio frame equalisation
Radio frame segmentation
TrBk concatenation / Code block segmentation
CRC attachment / TB
PhCH #2 PhCH #1
Channel coding
interleaving / TTI
Rate matching
TrCH #1
No DTX but dynamic rate matching for Variable Rate Handling (SF) after Mux Puncturing or better repetition
26
NOKIA
Data arrives to the coding/multiplexing unit in form of transport block sets once every Transmission Time Interval. The transmission time interval is transport-channel specific from the set {10 ms, 20 ms, 40 ms, 80 ms}. Error detection is provided on transport blocks through a Cyclic Redundancy Check. The CRC length is determined by the admission control in the RNC and can be 24, 16, 12, 8 or 0 bits; the more bits the CRC contains, the lower is the probability of having undetected errors in the receiver. The CRC is carried out based on the CRC parity bits of each transport block. Regardless of the result of the CRC check, all TBs are delivered to L2 along with the associated error indications. This estimation is then used as quality information for uplink macro diversity selection/combining in the RNC. Also, this indication may be directly used as an error indication to L2 for each erroneous TB in TM, UM and AM RLC, provided that RLC PDUs are one-to-one mapped onto TBs. Depending on whether the TB fits in the available code block size (channel coding method), the transport blocks in a TTI are either concatenated or segmented to coding blocks of suitable size. The benefit of the concatenation is better performance in terms of lower overhead due to encoder tail bits and in some cases due to better channel coding performance because of the larger block size. Channel coding and radio frame equalisation is performed on the coding blocks after the concatenation or segmentation operation. The convolutional coding is supposed to be used with relative low data rate, e.g. the BTFD using Viterbi decoder is much faster than turbo coding. Whereas turbo coding is applied for higher data rates and brings performance benefits when large enough block size are achieved for significant interleaving effect. As an example, the AMR speech service (coordinated TrCHs, coordinated TrCHs multiplexed in the FP) uses UEP (Unequal Error Protection): Class A bits, strong protection (1/3 cc and 12 bit CRC); Class B bits, less protected (1/3 cc); and Class C bits, the least protected (1/2 cc). The function of the radio frame equalisation (padding) is to ensure that data arrive after channel coding can be divided into equalised blocks when transmitted over more than a single 10 ms radio frame. The radio frame size equalisation is only performed in the UL, because in the DL the rate matching output block length is already produced in blocks of equal size per frame.
Downlink TrCH Multiplexing

MAC and higher layers Spreading/Scrambling and Modulation
Rate matching
CCTrCH
2nd insertion of DTX indication
2 nd interleaving/RF
TrCH Multiplexing
Radio frame segmentation
TrBk concatenation / Code block segmentation
CRC attachment / TB
1st insertion of DTX indication
1st interleaving/TTI
PhCH #2 PhCH #1
Channel coding
Rate matching
TrCH #1
DTX for Variable Rate Handling after Mux
Puncturing or better repetition Static Rate Matching (Eb/N0 balancing or Es/N0 matching)
27
NOKIA
The 1st interleaving (or radio-frame interleaving) is used when the delay budget allows radiomore than 10 ms of interleaving period. The 1st interleaving period is related to the TTI and can be 20, 40 or 80 ms. When different TrCHs are multiplexed together for a single connection, the positions where the corresponding TTIs start are time aligned. If the 1st interleaving is used, the frame segmentation will distribute the data coming from the 1st interleaving over 2, 4, or 8 consecutive frames in line with the interleaving length. Rate matching is used for matching the number of bits to be transmitted to the number of bits available on a single frame (DPCH). This is achieved either by puncturing or by repetition. The amount of repetition/puncturing for each service depends on the service combination and their QoS requirements. In the uplink direction, repetition is preferred, puncturing is used to avoid multicode transmission or when facing the limitations of the terminal transmitter or base station receiver. The rate matching procedure takes into account the number of bits of all TrCHs active in that frame. The admission control in the RNC provides a semi static parameter, the rate-matching attribute, to control the relative rate matching between different TrCHs. The rate-matching attribute is used to calculate the rate matching value when multiplexing several TrCHs for the same frame. With the aid of the rate matching attribute and TFCI the receiver can calculate backwards the rate matching parameters used and perform the inverse operation. By adjusting the rate-matching attribute, admission control of the RNC fine-tunes the quality of different services in order to reach an equal or near equal symbol power level requirement for all services. The variable rate handling is performed after TrCH multiplexing for matching the total instantaneous rate of the multiplexed TrCHs to the channel bit rate of the DPDCH (when the transport block sets do not contain the maximum number of DPDCH bits). The number of bits on a TrCH can vary between different TTIs. In the downlink the transmission is interrupted if the number of bits is lower than maximum allowed by the DPDCH. In the uplink bits are repeated or punctured to ensure that the total bit rate after TrCHs multiplexing is identical to the total channel bit rate of the allocated DPCHs. The rate matching is performed in a more dynamic way and may vary on a frame-byframe basis.
Channel Coding
Type of TrCH BCH PCH RACH CPCH, DCH, DSCH, FACH Coding scheme Convolutional coding Turbo coding No coding Coding rate 1/2 1/3, 1/2 1/3
Note: only the channel coding schemes reported in the table can be applied to TrCHs, i.e. convolutional coding (CC), turbo coding or no coding (no limitation on the coding block size). Ex. AMR speech service (coordinated TrCHs, multiplexed in the FP) uses UEP (Unequal Error Protection): Class A bits, strong protection (1/3 cc and 12 bit CRC); 1/3 CRC Class B bits, less protected (1/3 cc and Class C bits, the least protected (1/2 cc 1/3 cc); 1/2 cc).
The multicode transmission is employed when the total bit rate to be transmitted on a CCTrCH exceeds the maximum bit rate of the DPCH. The multicode transmission depends on the multicode capabilities of UE and Node B, and consists of several parallel DPDCHs transmitted for one CCTrCH using the same spreading factor. downlink, In the downlink if several CCTrCHs are employed for one UE, each CCTrCH can have a different spreading factor, but only one DPCCH is used for them in the connection. uplink, In the uplink the UE can use only one CCTrCH simultaneously. Multi-code operation is possible if the maximum allowed amount of puncturing has already been applied. For the different codes it is mandatory for the terminal to use the SF 4. Up to 6 4 parallel DPDCHs and only one DPCCH per connection can be transmitted. The second interleaving is also called intra-frame interleaving (10 ms radio frame intrainterleaving). It consists of block inter-column permutations, separately applied for each physical channel (if more than a single code channel is transmitted). The amount of bits output at this stage is exactly the number of bits the spreading factor of that frame can transmit.
Example of DCH Bit Rate Calculation

Assume a TB size of 336 bits (= 320 bit payload + 16 RLC header), a TBS size = 2 TBs, and a TTI = 10 ms DCH bit rate 336*2/10 = 67.2 kbit/s DCH user bit rate which is defined as the DCH bit rate rate, minus the RLC header rate, is given by (336-16) *2/10 = 64 kbit/s. DPDCH bit rate = (TB size + RLC header + CRC_bits + Tail_bits)*TBS size * [(1-Puncturing) or Repetition rate]*Coding_Rate/TTI = DPCH bit rate DPCCH overhead (downlink only)
Note: The DCH user bit rate is used for radio network planning.
Example for 3.4 kbps Data (DCCH) - DL

Transport block
CRC attachment
148
Transport block size Transport block set size CRC Coding TTI
148 bits 148*B bits (B=0, 1) 16 bits CC, coding rate = 1/3 40 ms = 4 R. Frames
CRC
148 16 bits
TrBk concatination
B TrBks (B =0,1)
Tail bit attachment
164*B
Tail Convolutional coding R=1/3 Rate matching Insertion of DTX indication*

164*B 8*B
DCH bit rate DCH bit rate 148/40 3.7 kb/s (with RLC header) ==148/40 ==3.7 kb/s (with RLC header) DCH encoded bit rate DCH encoded bit rate (148+16+8)*1*3*/40 12.9 kbps ==(148+16+8)*1*3*/40 ==12.9 kbps DL DPCH 15 ksps (30 kb/s= SF256 256) 256 DL DPCH 15 ksps (30 kb/s= SF 256) (516 NRM)/4 300 DPCCH HH (30%)= (516 ++NRM)/4 ==300 DPCCH HH (30%)= 129+NRM /4 210 (in Radio Frame) N 129+NRM /4 ==210 (in aaRadio Frame) N 324 Hence, NRM (210-129) Hence, NRM ==(210-129) * *44==324 Repetition 30*0.7 12.9 =1.63 RM Repetition ==30*0.7 / /12.9 =1.63 ==RM
516*B
(516+NRM)*B
1 interleaving Radio frame segmentation #1
st
(516+NRM)*B+NDI
(516+NRM)*B+NDI
#2
#3
#4
[ (516+NRM)*B+NDI]/ [ (516+NRM)*B+NDI]/ [ (516+NRM)*B+NDI]/ [ (516+NRM)*B+NDI]/ 4 4 4 4
To TrCh Multiplexing
30 NOKIA
* Insertion of DTX indication is used only 2002 / David Soldani 3G Mobile Systems.PPT v.0.0.3/ March if the position of the TrCHs in the radio frame is fixed.
Example for 3.4 kbps data NOTE: This example can be applied to DCCH. In this example, it is assumed that maximum data rate of RLC payload is 3.4 kbps, and that MAC and RLC overhead in a transport block is 12 bits.
Example for Stand-Alone Mapping of 3.4 Standkbps Data - DL

3.4 kbps data
#1 2 interleaving Physical channel mapping
nd
#2
129+NRM /4=150
#3
129+NRM /4=150
#4
129+NRM /4=150
129+NRM /4=150
150 1 2 15 1 2
150 15 1 2
150 15 1 2
150 15
15 ksps DPCH
slot
CFN=4N
slot
CFN=4N+1
slot
CFN=4N+2
slot
CFN=4N+3 Pilot symbol TPC
Symbol rate (ksps) 15 (SF = 256)
Npilot (bits/slot) 4
NTFCI (bits/slot) 0
NTPC /slot) (bits /slot 2
Ndata1 (bits /slot) 2
Ndata2 (bits /slot) 12
DPCCH overhead (4+2)/20 30% DPCCH overhead ==(4+2)/20 ==30%
31
NOKIA
Example for Stand-alone mapping of 3.4 kbps data on a 30 kbps (= 15 ksps) NOTE: This example can be applied to Stand-alone mapping of DCCH. The Table shows example of physical channel parameters for stand-alone mapping of 3.4 kbps data.
Example for 64/128/144 kbps packet data

Transport block
CRC attachment
336
The number of TrChs Transport block size
1 336 bits 64 kbps 128 kbps 144 kbps 336*B bits (B = 0, 1, 2, 3, 4) 336*B bits (B = 0, 1, 2, 4, 8) 336*B bits (B = 0, 1, 2, 4, 8, 9) 16 bits Turbo coding, coding rate = 1/3 20 ms
CRC
336 16
Transport block Set size CRC Coding TTI
TrBk concatenation
B TrBks (B=0, 1, 2, 3, 4, 8, 9)
Turbo coding R=1/3
352* B
Tail bit attachment
1056*B
Tail Rate matching

1056*B 12*B/9
1056* B+12*B/9+NRM
1st interleaving Radio frame segmentation

1056* B +12*B/9+NRM
#1
(1056* B +12*B/9+NRM)/2
#2
(1056* B +12*B/9+NRM)/2
To TrCh Multiplexing
Example for 64/128/144 kbps packet data NOTE: In this example, it is assumed that maximum data rate of RLC payload is 64/128/144 kbps, and MAC and RLC overhead in a transport block is 16 bits.
Example for multiplexing of 64/128/144/384 kbps and 3.4 kbps

Packet data #1 TrCH multiplexing #1 Insertion of DTX indication Physical channel segmentation 2nd interleaving #1 Physical channel mapping
1 2
Packet data #2 #1 #2 #1
3.4 kbps data #2 #3 #4
#1
#2
#2
#1
#3
#2
#4
#1
#P #P
15 1
#1 #1
2
#P #P
15 1
#1 #1
2
#P #P
15 1
#1 #1
2
#P #P
15
#1 DPDCH #P slot CFN=4N CFN=4N+1 CFN=4N+2 CFN=4N+3 Pilot symbol

Data rate (kbps) 64 128 144 384 Symbol rate (ksps) 120 240 240 240 480 1 1 1 3 1 No.of physical channel: P Npilot (bits) 8 16 16 16 16 NTFCI (bits) 8 8 8 8 8 NTPC (bits) 4 8 8 8 8 Ndata1 (bits) 28 56 56 56 120 Ndata2 (bits) 112 232 232 232 488
TFCI&TPC
33
NOKIA
Example for multiplexing of 64/128/144/384 kbps packet data and 3.4 kbps data NOTE: This example can be applied to multiplexing 64/128/144/384 kbps packet data and DCCH. The table shows an example of physical channel parameters for multiplexing of 64/128/144/384 kbps packet data and 3.4 kbps data
Examples of Layer 3 Procedures
34
NOKIA
MOC (1/2)
UE PRACH: Preamble AICH (CP-UE) RRC: CONNECTION REQUEST (CCCH/RACH/PRACH/FP/AAL2) (CP) AAL5: C-NBAP: RADIO LINK SETUP (CP) AAL5: C-NBAP: RL SETUP RESPONSE (CP) AAL5 ALCAP: AAL2 Connection Setup (CID1 for DCCH/DCH1) (CP-UE) RRC: CONNECTION SETUP (S-CCPCH/FACH/CCCH/FP/AAL2) L1 synch (CP) AAL5: D-NBAP: SYNCH INDICATION BTS RNC
(CP-UE) RRC:CONNECTION SETUP COMPLETE (DCCH/DCH1/UL DPDCH/FP/AAL2) (CP-UE) RRC:INITIAL DIRECT TRANSFER (DCCH/DCH1/UL DPDCH/FP/AAL2)
UE Information Elements Initial UE identity Activation time New U-RNTI UTRAN DRX cycle length coefficient Re-establishment timer Capability update requirement RB Information Elements Signalling RB information to setup list Signalling RB information to setup TrCH Information Elements Uplink transport channels Added or Reconfigured TrCH information list Added or Reconfigured UL TrCH information Downlink transport channels Added or Reconfigured TrCH information list Added or Reconfigured DL TrCH information PhyCH information elements Frequency info Uplink radio resources Maximum allowed UL TX power Uplink DPCH info PRACH Info (for RACH) Downlink radio resources Downlink information for each radio link
CN
(CP) AAL5: RANAP:INITIAL UE MESSAGE
UE-CN signalling (authentication, ciphering, etc) = RRC connection + Iu connection
35
NOKIA
MOC (2/2)
UE
DCHs to Modify DCH ID DCHs to Add DCH ID Limited Power Increase UL Transport Format Set DL Transport Format Set Frame Handling Priority Payload CRC Presence indicator UL FP Mode QE-Selector ToAWS ToAWE
BTS
RNC (CP) AAL5: RANAP: COMMON ID RANAP: RAB ASSIGNMENT REQUEST Radio Access Bearer service attributes -> AC
CN
D-NBAP:RL RECONFIGURATION PREPARE D-NBAP: RL RECONFIGURATION READY
AAL5 ALCAP: AAL2 Connection Setup (CID2 for DTCH/DCH2)
AAL2 Connection Setup NBAP: RL RECONFIGURATION COMMIT (CP-UE) RRC:RADIO BEARER SETUP (AAL2/FP/DCCH/DCH1/DPCH) (CP-UE) RRC:RADIO BEARER SETUP COMPLETE (DCCH/DCH1/DPDCH/FP/AAL2) Connection established RANAP:RAB ASSIGNMENT RESPONSE
36
NOKIA
UE
BTS
MTC (1/2)
RNC RANAP:PAGING
CN
UE has no RRC connection.
(CP-UE) RRC:PAGING TYPE 1 (FP/AAL2/PCCH/PCH/S-CCPCH) PRACH: Preamble AICH (CP-UE) RRC:RRC CONNECTION REQUEST (RACH/PRACH/FP/AAL2) (CP) AAL5: NBAP:RADIO LINK SETUP (CP) AAL5 NBAP: RL SETUP RESPONSE (CP) AAL5 ALCAP: AAL2 Connection Setup (CID1 for DCCH/DCH1) RRC:RRC CONNECTION SETUP L1 synch (CP) AAL5 NBAP:SYNCH INDICATION RRC:CONNECTION SETUP COMPLETE RRC:INITIAL DIRECT TRANSFER
(CP) AAL5: RANAP:INITIAL UE MESSAGE
UE-CN signalling (authentication, ciphering, etc)- RRC connection + Iu connection

MTC (2/2)
UE BTS RNC (CP) AAL5: RANAP: COMMON ID RANAP: RAB ASSIGNMENT REQUEST CN
NBAP:RL RECONFIGURATION PREPARE NBAP: RL RECONFIGURATION READY
AAL5 ALCAP: AAL2 Connection Setup (CID2 for DTCH/DCH2)
AAL2 Connection Setup NBAP: RL RECONFIGURATION COMMIT RRC:RADIO BEARER SETUP RRC:RADIO BEARER SETUP COMPLETE Connection established RANAP:RAB ASSIGNMENT RESPONSE
38
NOKIA
Paging
UE Node B UE has no RRC connection. (CP) AAL5: RANAP:PAGING RNC CN
(CP-UE) RRC:PAGING TYPE 1 (FP/AAL2/PCCH/PCH/S-CCPCH)
RRC connection establishment
Paging response
39
NOKIA
Cell_FACH Cell_DCH From Cell_FACH to Cell_DCH

UE Uu BTS Iub RNC-NBAP RNC-RRC RNC-L2 RNC-RRM NRT RB establishment for UE UE in CELL_FACH state Traffic volume measurement triggers RNC has data to send in downlink : MAC requests DL capacity from RRM DL_capacity_req
Channel type selection -> DCH
UE has data to send in uplink : RRC of UE requests uplink capacity from RRM
[RACH] RRC: MEASUREMENT REPORT BTS provides periodical cell load info to RRM NBAP: RADIO RESOURCE INDICATION UL_capacity_req
RR_ind UL & DL packet scheduling
Radio link setup (NBAP) and AAL2 transmission setup PS indicates UE about the granted capacity [FACH] RRC: RADIO BEARER RECONFIGURATION L1: SYNC NBAP: SYNCHRONIZATION INDICATION Sync_ind [DCH] RRC: RADIO BEARER RECONFIGURATION COMPLETE UE in CELL_DCH state RLC-PDU transportation on DCH
Capacity_allocation
L2 configuration
From Cell_DCH to Cell_FACH Cell_DCH Cell_FACH

Uu UE BTS Iub RNC-NBAP RNC-RRC RNC-L2 RNC-RRM
UE in CELL_DCH state RLC-PDU transportation on DCH All data is sent and RLC-U buffer is empty Inactivity_ind Inactivity_ind Define inactivity timer Inactivity timer expires [DCH] RRC: RADIO BEARER RECONFIGURATION [RACH] RRC: RADIO BEARER RECONFIGURATION COMPLETE L2 configuration Capacity_release Radio link release (NBAP) and AAL2 transmission release UE in CELL_FACH state
41
NOKIA
Physical Channels and Mapping of Transport Channels
42
NOKIA
Frequency Division Duplex Principle

P (bit-rate)
Static Rate Matcing and DTX for variable rate handling
Downlink
f
Tx Rx f re que n
Dynamic rate matching for variable rate handling

cy s epa ra
t
tion
P (bit-rate)
10 ms frame
of 1 90 M Hz
Uplink
f
4.4-5 MHz High rate multicode user
....
Codes with different spreading, user bit rate 8 384 kbps
t
Variable rate users 10 ms frame
43
NOKIA
Advantagies of WCDMA Wide 3.84 Mcps bandwidth (DS-CDMA) good frequency & interferer diversity low Eb/No Coherent detection in both U/DL directions based on the use of pilot symbols low Eb/No Fast power control (PC) minimizes interference high spectral efficiency Robust RAKE diversity receiver low complexity Dynamic variable rate multiplexing flexibility, BoD(Bandwidth on Demand) Supports the operation of asynchronous WCDMA BTSs
Dedicated PhCH Structure

physical phase /2) A physical channel is defined by specific carrier frequency, code, and on the uplink, relative phase (0 or /2) Superframe (720 ms)
Radio frame (10ms) #0 Slot (0.667 ms) #0

DPDCH
#1
#71
System Frame Number Sent on BCH Range 0 to 4095
#2
Data Pilot TFCI FBI
#14
Mchips/s Chip rate: 3.84 Mchips/s 1 Slot = 2560 chips
UL
DPCCH
TPC
I/Q code multiplexed with complex scrambling DL
Time multiplexed with complex scrambling

Data DPDCH TPC DPCCH TFCI Data DPDCH Pilot DPCCH
UL DPDCH SF 256 (15 ksps), 128, ..., (960 ksps) UL DPDCH SF == 256 (15 ksps), 128, ...,44 (960 ksps) UL DPCCH SF 256 (15 ksps) UL DPCCH SF == 256 (15 ksps)
DL DPCH SF 512 (7.5 ksps), 256 (15 ksps), , 4 (960 ksps) DL DPCH SF == 512 (7.5 ksps), 256 (15 ksps), , 4 (960 ksps)
Note: in UL symbols/s = bits/s
Mchips/s Chip rate: 3.84 Mchips/s 1 Time Slot = 2560 chips Each two bits-pair (symbol) represents an I/Q pair of QPSK modulation SFN Cell System Frame Number is used for paging groups, system information scheduling etc. In FDD SFN = BFN adjusted with T_cell. Range: 0 to 4095 frames Dedicated Uplink PhCH structure Frame structure for one PC period (1 slot) - the DCH is carried by this PhCH DPDCH (Dedicated Physical Data Channel) SF = 256/2k = 256 (15 ksps), 128, ..., 4 (960 ksps) DPCCH (Dedicated Physical Control Channel) SF = 256 (15 ksps) L1 control information TFCI = Transport Format Combination Indicator (UL radio frame CCTrCH parameters information) FBI = Feedback Information between UE and UTRAN (L1: closed loop mode Tx Div and Site Selection Diversity SSDT) TPC = Transmit Power Control symbols (DL inner loop PC commands) Pilot = Pilot symbols (channel estimation + coherent detection/averaging) I/Q multiplexed within each radio frame (no UL discontinuities) with complex scrambling Dedicated Downlink PhCH structure Frame structure for one PC period - the DCH is carried by the DPDCH Within one downlink DPCH, dedicated data generated at Layer 2 and above, i.e. the dedicated transport channel (DCH), is transmitted in time-multiplex with control information generated at Layer 1 (known pilot bits, UL TPC commands, and an optional TFCI) The downlink DPCH can be seen as a time multiplex of a downlink DPDCH and a downlink DPCCH 512 DPCH SF = 512/2k = 512 (7.5 ksps), 256 (15 ksps), , 4 (960 ksps) There are basically two types of downlink DPCHs Those that include TFCI (e.g. for several simultaneous services) And those that do not include TFCI (e.g. for fixed-rate services) In compressed mode a different slot format (A, B) is used compared to normal mode
Multicode Transmission
Ex. in the downlink
DPDCH DPCCH Transmission Power
Data TPC TFCI
DPDCH
Data
DPCCH
Pilot
Physical Channel 1
Transmission Power
Data
Data
Physical Channel 2
Transmission Power
.
Data Data
Physical Channel N
One Slot (2560 chips)
45
NOKIA
Uplink Dedicated PhCHs

DPDCH fields
Slot Format #i 0 1 2 3 4 5 6 Channel Bit Rate (kbps) 15 30 60 120 240 480 960 Channel Symbol Rate (ksps) 15 30 60 120 240 480 960 Services (kbps) SF 256 128 64 32 16 8 4 Bits/ Frame 150 300 600 1200 2400 4800 9600 Bits/ Slot 10 20 40 80 160 320 640 N data 10 20 40 80 160 320 640
12.2+3.4 28.8+3.4 64+3.4 (12.2)+128+3.4 (12.2)+384+3.4
DPCCH fields
Slot Format #i 0 0A 0B 1 2 2A 2B 3 4 5 5A 5B Channel Bit Rate (kbps) 15 15 15 15 15 15 15 15 15 15 15 15 Channel Symbol Rate (ksps) 15 15 15 15 15 15 15 15 15 15 15 15 SF 256 256 256 256 256 256 256 256 256 256 256 256 Bits/ Frame 150 150 150 150 150 150 150 150 150 150 150 150 Bits/ Slot 10 10 10 10 10 10 10 10 10 10 10 10 Npilot 6 5 4 8 5 4 3 7 6 5 4 3 NTPC 2 2 2 2 2 2 2 2 2 1 1 1 NTFCI 2 3 4 0 2 3 4 0 0 2 3 4 NFBI 0 0 0 0 1 1 1 1 2 2 2 2 Transmitted slots per radio frame 15 10-14 8-9 8-15 15 10-14 8-9 8-15 8-15 15 10-14 8-9
46
NOKIA
The channel bit and symbol rates in the table are the rates immediately before spreading The field order and the total n. of bits/slot are fixed, although the n. of bits per field may vary during a connection 3.4 kbps is for mapping the DCCH (signalling)
Downlink Dedicated PhCHs

Slot Format #i 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Channel Bit Rate (kbps) 15 15 30 30 30 30 30 30 60 60 60 60 120 240 480 960 1920 Channel Symbol Rate (ksps) 7.5 7.5 15 15 15 15 15 15 30 30 30 30 60 120 240 480 960 Services (kbps) SF Bits/Slot DPDCH Bits/Slot NData1 NData2 512 512 256 256 256 256 256 256 128 128 128 128 64 32 16 8 4 10 10 20 20 20 20 20 20 40 40 40 40 80 160 320 640 1280 0 0 2 2 2 2 2 2 6 6 6 6 12 28 56 120 248 4 2 14 12 12 10 8 6 28 26 24 22 48 112 232 488 1000 NTPC 2 2 2 2 2 2 2 2 2 2 2 2 4 4 8 8 8 DPCCH Bits/Slot NTFCI 0 2 0 2 0 2 0 2 0 2 0 2 8* 8* 8* 8* 8* NPilot 4 4 2 2 4 4 8 8 4 4 8 8 8 8 16 16 16 Transmitted slots per radio frame NTr 15 15 15 15 15 15 15 15 15 15 15 15 15 15 15 15 15
12.2+3.4
28.8+3.4 (12.2)+64+3.4 (12.2)+128+3.4 (12.2)+384+3.4
* If TFCI bits are not used, then DTX shall be used in TFCI field
47
NOKIA
3.4 kbps is for mapping the DCCH (signalling) Multicode transmission = 1 DPCCH + n parallel DPDCH using different OVSF codes
Variable Rate Handling on DPCHs

Uplink
Higher bit rate Lower bit rate Medium bit rate DPDCH DPCCH 10 ms frame 10 ms frame 10 ms frame
Downlink
Maximum bit rate of that connection Lower bit rate (discontinuous transmission) ... 10 ms frame
DPCCH
DPDCH
48
NOKIA
Uplink DPDCH bit rate can change frame-by-frame (10 ms). Higher bit rate requires more transmission power. Continuous transmission regardless of the bit rate. Reduced audible interference to other equipment (nothing to do with normal interference, does not affect the spectral efficiency). GSM interference frequency ~217 Hz (=1/4.615 ms). Admission control in RNC allocates the TFCS and the minimum SF. The relative power level is such that for higher bit rates the power of DPCCH is higher, thus enabling more accurate channel estimation, and the overhead (DPDCH vs DPCCH power) of the DPCCH is still lower. Downlink DPDCH bit rate can change frame-by-frame (10 ms). Rate matching done to the maximum bit rate of that connection. Lower bit rates obtained with discontinuous transmission (audible interference not a problem in downlink). Admission control allocates those bit rates that can be used on physical layer. No L1 DTX bits transmitted on the radio interface.
Common Uplink PhCH (1/4)

Physical Random Access Channel (PRACH) (PRACH PRACH)
radio frame: 10 ms 5120 chips #0 Access slot #0 Access slot #1 #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14
Slotted ALOHA approach with fast acquisition indication

radio frame: 10 ms
Random Access Transmission Random Access Transmission
Access slot #7 Access slot #8
Random Access Transmission
Random Access Transmission Random Access Transmission
Access slot #14
49
NOKIA
The random-access transmission is based on a Slotted ALOHA approach with fast acquisition indication. The UE can start the random-access transmission at the beginning of a number of well-defined time intervals, denoted access slots. There are 15 access slots per two frames and they are spaced 5120 chips apart. Information on what access slots are available for random-access transmission is given by higher layers.

RACH sub-channels sub
A RACH sub-channel defines a sub-set of the total set of uplink access slots There are a total of 12 RACH sub-channels RACH sub-channel #i (i = 0, , 11) consists of the following uplink access slots
Uplink access slot #i leading by p-a chips the downlink access slot #i contained within the 10 ms interval that is time aligned with P-CCPCH frames for which SFN mod 8 = 0 or SFN mod 8 = 1 Every 12th access slot relative to this access slot
SFN modulo 8 of corresponding P-CCPCH frame

0 1 2 3 4 5 6 7
0
0 12 9 6 3
1
1 13 10 7 4
2
2 14 11 8 5
3
3 0 12 9 6
Sub-channel number 4 5 6 7
4 1 13 10 7 5 2 14 11 8 6 3 0 12 9 7 4 1 13 10
8
8 5 2 14 11
9
9 6 3 0 12
10
10 7 4 1 13
11
11 8 5 2 14
50
NOKIA
Each cell is configured by RNP setting the preamble scrambling code the message code, length in time (either 10 or 20 ms), the AICH Transmission Timing parameter (0 or 1, for setting the preamble-to-Acquisition Indicator distance), the set of available subsignatures and the set of available RACH sub-channels for each Access Service (ASC ASC) Class (ASC). In order to provide different priorities of RACH usage when the RRC connection is set up, PRACH resources (access slots and preamble signatures) can be divided between 8 different ASCs numbered from 0 (highest priority, used in case of Emergency Call or for reasons with equivalent priority) to 7 (lowest priority). If the UE is member of several ACs, then it selects the ASC for the highest AC number. An ASC defines a certain partition by RNP of the PRACH resources and is always associated with a persistence value computed by the terminal as a function of a dynamic persistence level (1-8) and a persistence-scaling factor (7 values, from 0-1 for ASC 2 7) set by RNP.

Structure of the PRACH message part
Data Control Pilot Npilot bits Tslot = 2560 chips, 10*2 bits (k=0..3)
k
SF = 256, 128, 64, or 32
Data Ndata bits TFCI NTFCI bits
15ksps) SF = 256 (15ksps) (15ksps
PRACH ramping and message transmission

AICH Access Slot Acquisition Indicator
RACH max bit rate = 18 kbit/s (including L2 overhead)
Repetitions of a signature (16 signatures 16 available) available

Preamble Power Ramp Step Preamble
RX at UE Pp-m AICH access slots
Message part...
10 ms or 20 ms
TX at UE PRACH access slots
Preamble Retrans Max

note: in UL symbols/s = bits/s
Structure of the PRACH transmission The message part length can be determined by L1 from the used signature and/or access slot, as configured by higher layers. Signatures, message length, and/or access slots (for which message length) assigned by higher layers. PRACH preamble part The preamble consists of 256 repetitions of a signature of length 16 chips (16x256 = 4096). There are a maximum of 16 available signatures based on the Hadamard code set of length signatures, 16. PRACH message part Each slot consists of two parts, a data part to which the RACH transport channel is mapped and a control part that carries Layer 1 control information (data and control parts are transmitted in parallel) A 20 ms message part consists of two consecutive 10 ms message part radio frames Data part SF = 256 (15 ksps), 128 (30 ksps), 64 (60 ksps), and 32 (120 ksps) Control part SF = 256 (15ksps) note: in UL symbols/s = bits/s 15ksps) (15ksps The control part consists of 8 known pilot bits to support channel estimation for coherent detection The TFCI of a radio frame indicates the TF of the RACH transport channel mapped to the simultaneously transmitted message part radio frame (in case of a 20 ms PRACH message part, part the TFCI is repeated in the second radio frame)

Structure of the PCPCH message part
Data Pilot TFCI Ts = 2560 chips FBI TPC
15ksps) SF = 256 (15ksps) (15ksps SF = 256, 128, , or 4
Structure of the CPCH access transmission

AP-AICH CD/CA-ICH
DPCCH (DL)
Ta
APs
p-a1
a1-cdp
cdp-a2
Power Control, Pilot and CPCH
CD/CA
[Example shown is for Tcpch = 0] control commands

0 or 8 slots Power Control Preamble T0
P0
P1
P1
PCPCH (UL)
p-p
52 NOKIA
p-cdp
cdp-pcp
Information and Control Data
The CPCH transmission is based on DSMA-CD approach with fast acquisition indication. The UE can start transmission at the beginning of a number of well-defined time-intervals, relative to the frame boundary of the received BCH of the current cell. The access slot timing and structure is identical to RACH. The PCPCH access transmission consists of one or several Access Preambles [A-P] of length 4096 chips, one Collision Detection Preamble (CD-P) of length 4096 chips, a DPCCH Power Control Preamble (PC-P) which is either 0 slots or 8 slots in length, and a message of variable length Nx10 ms. CPCH access preamble part Similar to RACH preamble part. The RACH preamble signature sequences are used. The number of sequences used could be less than the ones used in the RACH preamble. The scrambling code could either be chosen to be a different code segment of the Gold code used to form the scrambling code of the RACH preambles or could be the same scrambling code in case the signature set is shared. CPCH collision detection preamble part Similar to RACH preamble part. The RACH preamble signature sequences are used. The scrambling code is chosen to be a different code segment of the Gold code used to form the scrambling code for the RACH and CPCH preambles. CPCH power control preamble part The power control preamble segment is called the CPCH Power Control Preamble (PC-P) part. The Power Control Preamble length is a higher layer parameter, Lpc-preamble, which shall take the value 0 or 8 slots. CPCH message part Each message consists of up to N_Max_frames 10 ms frames. N_Max_frames is a higher layer parameter. Each 10 ms frame is split into 15 slots, each of length Tslot = 2560 chips. Each slot consists of two parts, a data part that carries higher layer information and a control part that carries Layer 1 control information. The data and control parts are transmitted in parallel. The spreading factor for the control part of the CPCH message part is 256. The data part consists has SF = 256, 128, 64, 32, 16, 8 or 4.
Common Downlink PhCHs (1/4)

Radio frame (10ms)
#0
Slot (2560 chips)
#1
FACH max. bit rate = 36 kbps (including L2 overhead)
#0
#2
#14
Any CPICH
Pre-defined pilot sequence

20 bits 256 chips
15 ks/s SF =256 Cch,256,0 (P-CPICH)
P-CCPCH
(Tx OFF)
Data only (18 bits)

20 bits
15 ks/s SF =256 Cch,256,1
S-CCPCH
TFCI
Data
20*2k bits (k = 0, ....,6)
Pilots
15-960 ks/s SF =256-4
53
NOKIA
Physical channel, carries a pre-defined bit/symbol sequence at fixed rate (15 ksps, SF= 256) channel (P-CPICH) Primary Common Pilot Channel (P-CPICH) The same channelization code is always used for this channel (Cch,256,0). Cch,256,0 Scrambled by the primary scrambling code. There is one and only one P-CPICH per cell, which is broadcast over the entire cell. The Primary CPICH is a phase reference for the following downlink channels: SCH, Primary CCPCH, AICH, PICH AP-AICH, CD/CA-ICH, CSICH, DL-DPCCH for CPCH and the S-CCPCH. By default, the Primary CPICH is also a phase reference for downlink DPCH and any associated PDSCH. The UE is informed by higher layer signalling if the P-CPICH is not a phase reference for a downlink DPCH and any associated PDSCH. The Primary CPICH is always a phase reference for a DL PhCH using closed loop TX diversity.
(CPICH CPICH) Common Pilot Channel (CPICH)
(S-CPICH) Secondary Common Pilot Channel (S-CPICH)
Is a fixed rate (15 ksps, SF = 256 downlink physical channel used to carry the BCH. 256) 15 Primary CCPCH the channelization code is fixed to Cch,256,1. ch,256,1. No TPC commands, no TFCI and no pilot bits are transmitted. P-CCPCH is broadcast over the entire cell. It is not transmitted during the first 256 chips of each slot, where Primary SCH and Secondary SCH are transmitted. Primary CCPCH (BCH) can only have a fixed predefined transport format combination.
(PPrimary Common Control Physical Channel (P-CCPCH)
An arbitrary channelization code of SF=256 is used for the S-CPICH. A S-CPICH is scrambled by either the primary or a secondary scrambling code. There may be zero, one, or several S-CPICH per cell. SA S-CPICH may be transmitted over the entire cell or only over a part of the cell. A Secondary CPICH may be a phase reference for a downlink DPCH If this is the case, the UE is DPCH. informed about this by higher-layer signalling. The Secondary CPICH can be a phase reference for a downlink physical channel using open loop TX diversity, instead of the Primary CPICH being a phase reference.
(SSecondary Common Control Physical Channel (S-CCPCH)
Is used to carry FACH and PCH they can be mapped to the same S-CCPCH (same frame) or to PCH, separate Secondary CCPCHs. Secondary CCPCH SF = 256/2k = 256, , 4 Channel symbol rate 15, , 960 ksps. It is not inner-loop power controlled (FACH/S-CCPCH slow power control via Frame Protocol). It can support variable rate (multiple transport format combinations) with the help of the TFCI field included. Only transmitted when there is data available. The FACH and PCH can be mapped to the same or to separate Secondary CCPCHs.

Synchronization Channels (SCH)
256 chips
Same code for every cell in the network, for slot synchronisation
Primary SCH Secondary SCH
ac p acsi,0
acp acsi,1
ac p acsi,14
64 possible Code Sequences (i=1,,64), for frame synchronization and scrambling code group detection
Slot #0 2560 chips
Slot #1
Slot #14
SCH radio frame (10 ms)
54
NOKIA
Physical channel used for cell search It consists of two sub-channels transmitted in parallel and modulated by the symbol a , which indicates the presence/absence of STTD encoding on the P-CCPCH. Primary SCH (one code/slot) It consists of a modulated code of length 256 chips (Cp). It is transmitted every slot. It is the same for every cell in the system and allows DL slot synchronisation to the cell. Secondary SCH (one sequence/radio frame) It consists of repeatedly transmitting a (length 15) sequence of modulated codes of length 256 chips, the Secondary Synchronisation Codes (SSC). The SSC is denoted csi,k, where i = 1, 2, , 64 is the number of the scrambling code group, and k = 0, 1, , 14 is the slot number. This sequence on the Secondary SCH allows DL frame synchronisation and indicates which of the code groups the cell downlink scrambling code belongs to (see cell search procedure). Each SSC is chosen from a set of 16 different codes of length 256.

Acquisition Indicator Channel (AICH) (AICH AICH)
AI part = 4096 chips, 32 real-valued symbols
1024 chips No transmission
Reserved for future use by other physical channels
15 ks/s SF =256
AS #0 AS #1 AS #i 20 ms AS #14
Page Indicator Channel (PICH) (PICH PICH)

The PICH is always associated with the SCCPCH to which a PCH transport channel is mapped
Bits not transmitted and reserved for future use
15 ks/s SF =256
288 bits for paging indication One radio frame (10 ms) 12 bits
55
NOKIA
(AICH AICH) Acquisition Indicator Channel (AICH)

The AICH is a fixed rate physical channel (SF = 256) used to indicate in a cell the reception by the base station of PRACH preambles (signatures). Once the base station has received a preamble, the same signature that has been detected on the PRACH preamble is then sent back to the UE using this channel. Higher layers are not involved in this procedure: a response from the RNC would be too slow in order to acknowledge a PRACH preamble. The AICH consists of a repeated sequence of 15 consecutive access slots (AS) of length 5120 chips chips. Each AS includes an Acquisition-Indicator (AI) part of 32 real-valued symbols. The base station as a function of the signature s detected on the PRACH preamble derives the symbols of the AI part. The computation may result in a positive acknowledge, negative acknowledge or no acknowledge at all, if the detected signature is not a member of the set of available signatures for all the ASCs for the corresponding PRACH. There can be up to 16 signatures acknowledged on AICH at the same time. The UE receives the AICH information (channelisation code, STTD indicator ad AICH transmission timing) from the system information broadcast on BCH and accordingly starts receiving the AICH when the allocated PRACH is used. If the AICH or PICH information is not present, the terminal considers the cell barred and proceeds to cell re-selection.
(PICH PICH) Page Indicator Channel (PICH)

The PICH is a fixed rate (SF=256 physical channel used to carry the paging indicators. SF=256) SF=256 The PICH is always associated with an S-CCPCH to which a PCH transport channel is mapped. One PICH radio frame of length 10 ms consists of 300 bits (b0, b1, , b299). 288 bits (b0, b1, , b287) are used to carry paging indicators. The remaining 12 bits are not formally part of the PICH and shall not be transmitted. The part of the frame with no transmission is reserved for possible future use. In each PICH frame are transmitted Np paging indicators, where Np is a cell based parameter, which can be set by RNP equal to 18 (16 bits are repeated), 36 (8 bits are repeated), 72 (4 bits are repeated), or 144 (only 2 bits are repeated). If a paging indicator in a certain frame is set to "1" it is an indication that UEs associated with this PI should read the corresponding frame of the associated S-CCPCH. Once a paging indicator has been detected, the UE decodes the S-CCPCH frame to see whether there was a paging message on PCH intended for it or not. The less often the page indicators appear in the frame the longer the UE battery life is.

Physical Downlink Shared Channel (PDSCH) (PDSCH PDSCH)
PDSCH power offset
Downlink transmission power
Associated PDSCH data

(not time aligned)
PO2 PO1 PO3
DL DPCH
Data 1
TPC
TFCI
Data 2
Pilot
15=25615-960 ks/s SF =256-4

time
Timeslot (0.667 ms)
32-512 kb/s (Turbo 1/3)
56
NOKIA
The Physical Downlink Shared Channel (PDSCH) is used to carry the Downlink Shared Channel (DSCH). A PDSCH corresponds to a channelisation code below or at a PDSCH root channelisation code. A PDSCH is allocated on a radio frame basis to a single UE. Within one radio frame, UTRAN may allocate different PDSCHs under the same PDSCH root channelisation code to different UEs based on code multiplexing. Within the same radio frame, multiple parallel PDSCHs, with the same spreading factor, may be allocated to a single UE. This is a special case of multicode transmission. All the PDSCHs are operated with radio frame synchronisation. PDSCHs allocated to the same UE on different radio frames may have different spreading factors. For each radio frame, each PDSCH is associated with one downlink DPCH. The PDSCH and associated DPCH do not necessarily have the same spreading factors and are not necessarily frame aligned. All relevant Layer 1 control information is transmitted on the DPCCH part of the associated DPCH, i.e. the PDSCH does not carry Layer 1 information. To indicate for UE that there is data to decode on the DSCH, the TFCI field of the associated DPCH is used. The TFCI informs the UE of the instantaneous transport format parameters related to the PDSCH as well as the channelisation code of the PDSCH. For PDSCH the allowed spreading factors may vary from 256 to 4 4. The DSCH is always set up on top of a dedicated channel, which is used as a return channel for upper layer acknowledges The DL OLPC on DSCH is based on the associated DCH, when there is nothing to transmit on that DCH TBs with zero size are used and the UE can measure the BLER and adjust SIR target accordingly BitRateDsch (Cell): 32, 64, 128, 256, 384, 512 kb/s TtiDsch (Cell): 10, 20 ms Channel coding type: Turbo coding (1/3)
Cell Search Procedure

Slot synchronisation to a cell (cell selection using a matched filter) Primary SCH Frame synchronisation and identification of the cell code group (correlation with all possible secondary synchronisation code sequences 64 groups of 8 primary Scrambling Codes) Determination of the exact primary scrambling code used by the found cell (symbol-by-symbol correlation over the CPICH with all codes within the code group identified in the second step)
Secondary SCH
Primary CPICH
P-CCPCH, (SFN modulo 2) = 0
P-CCPCH, (SFN modulo 2) = 1 The Primary CCPCH is detected using the identified P-Scrambling Code System- and cell specific BCH information can be read
10 ms
57
NOKIA
Slot synchronisation During the first step of the cell search procedure the UE uses the SCHs primary synchronisation code to acquire slot synchronisation to a cell. This is typically done with a single matched filter (or any similar device) matched to the primary synchronisation code which is common to all cells. The slot timing of the cell can be obtained by detecting peaks in the matched filter output. codeFrame synchronisation and code-group identification During the second step of the cell search procedure, the UE uses the SCHs secondary synchronisation code to find frame synchronisation and identify the code group of the cell found in the first step. This is done by correlating the received signal with all possible secondary synchronisation code sequences, and identifying the maximum correlation value. Since the cyclic shifts of the sequences are unique the code group as well as the frame synchronisation is determined. ScramblingScrambling-code identification During the third and last step of the cell search procedure, the UE determines the exact primary scrambling code used by the found cell. The primary scrambling code is typically identified through symbol-by-symbol correlation over the CPICH with all codes within the code group identified in the second step. After the primary scrambling code has been identified, the Primary CCPCH can be detected.And the system- and cell specific BCH information can be read.
Compressed Mode
Transmission Gap Pattern Sequence
#1 TG pattern 1 #2 TG pattern 2 #3 TG pattern 1 #4 TG pattern 2 #5 TG pattern 1 #TGPRC TG pattern 2
TG pattern 1
TG pattern 2 Transmission
Transmission gap 1
Transmission gap 2
Transmission gap 1
gap 2
TGSN TGL1 TGD TGPL1

TGSN TGL2 TGL1 TGD TGPL2 TGL2
Compressed Mode State where at least one transmission gap pattern sequence (layer one parameterization unit, which contains one or two transmission gaps within a set of radio frames) is active. The aim of the downlink and uplink compressed mode is to allow the UE to monitor cells on other FDD frequencies and on other modes and radio access technologies that are supported by the UE, i.e. TDD and GSM. Instantaneous transmit power and the SIR target needs to be changed during the compressed frames, comparing to normal mode (for this purpose, the respective Delta SIRs are signaled by the RNC to the UE and to the WCDMA BTS). The methods for generating the compressed mode gaps are: rate matching, reduction of the spreading factor by a factor of two and higher layer scheduling (in the downlink all methods are supported while compressed mode by rate matching is not used in the uplink). The maximum idle length is defined to be 7 slots per one 10 ms frame.
Timing and Synchronisation UTRANin UTRAN-FDD
59
NOKIA
Timing between Physical Channels

Primary SCH Secondary SCH Any CPICH P-CCPCH, (SFN modulo 2) = 0 CCPCH, (SFN
tS-CCPCH,k tPICH
P-CPICH is the phase reference for all downlink physical channels P-CCPCH is the timing reference for all the physical channels, directly for downlink and indirectly for uplink P-CCPCH, (SFN modulo 2) = 1 CCPCH, (SFN
k:th k:th S-CCPCH
k:th PICH for k:th S-CCPCH

#0 AICH access slots #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14
Any PDSCH
tDPCH,n Chip Offset 10 ms
tS-CCPCH,k = Tk 256 chip, Tk {0, 1, , 149}
n:th n:th DPCH
tPICH = 7680 chips tDPCH,n = Tn 256 chip, Tn {0, 1, , 149}
The cell SFN is transmitted on the P-CCPCH, which is used as timing reference for all physical channels, since the transmission timing in the uplink is derived from the timing of the downlink physical channels. The SCH (primary and secondary), CPICH (primary and secondary), P-CCPCH, and PDSCH have identical frame timing. The S-CCPCH timing may be different for different S-CCPCHs, but the offset from the P-CCPCH frame timing is a multiple of 256 chips. The PICH timing is 7680 chips prior to its corresponding S-CCPCH frame timing, i.e. the timing of the S-CCPCH carrying the PCH transport channel with the corresponding paging information. The AICH access slots #0 starts at the same time as P-CCPCH frames with (SFN modulo 2) = 0. The DPCH timing may be different for different DPCHs, but the offset from the P-CCPCH frame timing is always a multiple of 256 chips
Transport Channel Synchronisation

RNC
147 148 149 150 151 152 153
CFN
DL Data Frame [CFN =150]

147 1171 148 1172 148 1684 149 1173 149 1685 150 1174 150 1686
UL Data Frame [CFN =150]
BS -1
151 1175 151 1687
152 1176 152 1688
153 1177 153 1689
CFN Frame Offset SFN-1 CFN Frame Offset SFN-2
BS -2
147 1683
Receiving Window
UL Radio Frame
DL Radio Frame UE DL
147 148 149 150 151 152 153
CFN
Frame arrows represent first chip or first bit in frames, TTI=10 ms, [FDD - Chip Offset = 0]
Frame Offsets of the different radio links are selected by the SRNC in order to have a timed transmission
The Transport Channel synchronisation, also presented as Layer 2 synchronisation, provides a Layer 2 common frame numbering between UTRAN and UE, or better the frame synchronisation between the L2 entities in the UTRAN and in the UE. The common frame reference at Layer 2 is defined as Connection Frame Number (CFN). The CFN is a unique number for each RRC connection, and it is specified as the frame counter used for the transport channel synchronisation between UE and UTRAN. A CFN value is associated to each TBS and it is passed together with the TBS through the MAC-L1 service access point. The duration of a CFN cycle (0-255 frames) is supposed to be longer than the maximum allowed transport delay between MAC and L1 . When used for PCH the range of the CFN is from 0 to 4095 frames. Other important (optionally frequency-locked) counters are the Node B Frame Number (BFN) and the RNC Frame Number (RFN). The BFN and RFN are, respectively the Node B and RNC common frame number counters, which range form 0 up to 4095 frames. The System Frame Number (SFN) is the cell System Frame Number counter, which ranges from 0 up to 4095 frames and it is sent on BCH. The SFN is used for scheduling the information transmitted in the cell. In FDD the SFN equals the BFN adjusted with the timing delay used for defining the start of SCH, CPICH and the downlink Scrambling Code(s) in the cell (T_cell in 3GPP). T_cell has been specified in 3GPP in order to avoid the overlapping of SCHs (collision of SCH bursts) in different cells belonging to the same base station. In other words, the SFN in a cell is supposed to be delayed T_cell chips with respect to the BFN. T_cell has a resolution (step size) of 256 chips and ranges form 0 up to 9. In TDD, the SFN is locked to the BFN (i.e. SFN = BFN). The CFN is not transmitted in the radio interface, but is mapped by Layer 1 to the SFN of the first radio frame used for the transmission of the TBS in question. As already mentioned in this section, the SFN is broadcast at Layer 1 in the BCH and the mapping between the CFN and the SFN is performed as a function of a radio link specific parameter, denoted Frame Offset in 3GPP. The Frame Offset is computed by the SRNC and provided to the base station when the radio link is set up, where the mapping between Layer 2 and Layer 1 is performed as: SFN mod 256 = (CFN + Frame Offset) mod 256 (from L2 to L1); and CFN = (SFN - Frame Offset) mod 256 (from L1 to L2). The transport channel synchronisation mechanism is valid for all downlink transport channels. In case of soft handover, i.e. only for DCHs belonging to radio links of different radio link sets, the Frame Offsets of the different radio links are selected by the SRNC in order to have a timed transmission of the diversity branches on the radio interface. During soft handover the CFN allows the frame selection combining at Layer 2 in the uplink and the frame splitting in the downlink.
Radio Interface Synchronisation

Node B
Source cell
Node B
Target cell
SRNC
UE
DOFF (RRC) At initial RL
DL DPCH DL DPCHnom = TUETx To
Frame Offset + Chip Offset (NBAP)
DL SFN (timing reference)

At HO
OFFtarget+ Tmtarget
(RRC)
DL DPCH
Frame_offset + Chip_offset (NBAP)
For downlink orthogonality Frame Offset + Chip Offset are rounded to closest 256 chip boundary
The Radio Interface Synchronisation assures that the UE gets the correct frames while receiving from several cells. When setting up the first RL the SRNC selects a default-offset value for the dedicated physical channel, denote (DOFF) in the fugure, which is then used to initialise the Frame Offset and Chip Offset in the base station, and to inform the UE when the frames in the downlink are expected. In order to average out the Iub traffic and the Node B processing load all services are scheduled by means of DOFF. In addition, DOFF is used to spread out the location of pilot symbols in the downlink in order to reduce the base station peak power, since pilot symbols are always transmitted at the fixed location within a slot. Before any intra-frequency diversity handover the UE is supposed to measure the timing difference between the uplink DPCH and the target cell SFN and to report it to the SRNC. The SRNC breaks this time difference into two parameters (Frame Offset and Chip Offset) and forwards the computed values to Node B. The Node B rounds the received Chip Offset to the closest 256 chips boundary value in order to maintain the downlink orthogonality in the cell (regardless of the spreading factor in use) and then uses it for the downlink DPCH transmission as offset relative to the P-CCPCH timing. The handover reference is the time instant TUETx -To, which denoted DL DPCHnom in the timing diagram. Where TUETx represents the time when the UE transmits the uplink DPCH, and To is the nominal difference between the first received DPCH finger (DL DPCHnom) and TUETx at UE (constant of 1024 chips). OFF and Tm are estimated by the UE according to the following equation: OFF + Tm = (SFNtarget DL DPCHnom) mod 256 frames [chips], where OFF and Tm are expressed in Frames and chips, respectively.
Spreading, Scrambling and Modulation
63
NOKIA
Spreading
One symbol duration
Symbol
Symbol
BPSK-modulated bit sequence of rate R +1
Spectrum
-1
Data Chip Code (pseudo noise) Data x Code Chip SF = 8 chips / Symbol
+1 -1 +1 -1
Despreading
Code Data
+1 -1 +1 -1
Spreading Factor (SF) = Number of chips per data symbol

The spreading concept is applied to physical channels and it consists of two operations. The first is the channelization operation, which transforms each data symbol into a number of chips; thus increasing the bandwidth of the signal. The number of chips per data symbol is called Spreading Factor (SF) (SF). The second operation is the scrambling operation, where a scrambling code is applied on top of the spread signal.
Detecting own signal. Correlator

+1
Own signal
-1 +1
Code Data after multiplication Data after Integration Other signal Code
Increased on av. By a factor of 8 (Processing Gain)
-1 +1 -1 +8
-8 +1 -1 +1 -1 +1
Data after multiplication Data after Integration

-1 +8
-8
Scrambling and Channelization codes

Channelisation Codes (OVSF) (OVSF) OVSF
Channelisation Code Scrambling Code (Spreading) (Scrambling) Chip Rate (W) Chip Rate
Scrambling Codes
Used for transmission from a single source separation DATA DL: connections within 1 cell UL: dedicated PhCHs from 1 UE Have orthogonality properties reduced interference Have different spreading factors (SF) different symbol rates Are a limited resource (in the downlink) must be "managed"
UL: separate different UEs DL: separate different cells (sectors) Have good interference averaging (correlation) properties On top of spreading codes (transmission BW is not affected no spreading effect)
+1 -1 +1 -1 +1 -1
(OVSF OVSF) Channelization code (OVSF) Scrambling code Combined code
66
NOKIA
Channelisation Codes (1/2)

Orthogonal Variable Spreading Factors (OVSF codes OVSF) OVSF
Cch,4,0 =(1,1,1,1) Cch,2,0 = (1,1) Lowest SF Cch,4,1 = (1,1,-1,-1) Spreading codes in the sub-tree
Cch,1,0 = (1) SF = 1
Cch,4,2 = (1,-1,1,-1) Cch,2,1 = (1,-1) SF = 2 Cch,4,3 = (1,-1,-1,1) SF = 4
67
NOKIA
In the channelization process data symbols on I- and Q-branches are independently multiplied with an Orthogonal Variable Spreading Factor (OVSF) code. In 3GPP the OVSF codes used for different symbol rates are uniquely described as Cch,SF,k, where SF is the spreading factor of the code and k is the code number (0 k SF-1). Each level of the code tree defines the channelization codes of length SF, where SF is the spreading factor of the codes. The channelization codes have orthogonal properties, and are used for separating the information transmitted from a single source, i.e. different connections within one cell in the downlink, where the own interference is also reduced, and dedicated physical data channels from one UE in the reverse direction. In the downlink the OVSF codes in a cell are limited resources and need to be managed by the radio network controller, whereas in the reverse direction such a problem does not exist and each terminal autonomously manages the code tree. The orthogonal property is preserved across different symbol rates, but the selection of one OVSF code will block the sub tree. In other words, another physical channel may use a certain code in the tree if no other physical channel to be transmitted using the same code tree is using a code that is on an underlying branch, i.e. using a higher SF code generated from the intended spreading code to be used. For the same reason, a smaller SF code on the path to the root of the tree cannot be used. During the network operation, the code tree may become fragmented and a code reshuffling is then needed.
Generation method
Channelisation Codes (2/2)

Cch,1,0 = 1
Cch , 2,0 Cch ,1,0 = Cch , 2,1 Cch ,1,0
Cch ,1,0 1 1 = Cch ,1,0 1 1

C ch , 2n , 0 C ch , 2n , 0 C ch , 2n ,1 C ch , 2n ,1 : C ch , 2n , 2n 1 C ch , 2n , 2n 1
Cch,SF,k
SF = spreading factor of the code k = code number, 0 k SF-1
C ch , 2 ( n+1), 0 C ch , 2n , 0 C C ch , 2 ( n +1 ),1 ch , 2n , 0 C ch , 2 ( n+1), 2 C ch , 2n ,1 C ch , 2 ( n+1), 3 = C ch , 2n ,1 : : C ch , 2 ( n+1), 2 ( n+1)2 C ch , 2n , 2n 1 C ( n+1) ( n+1) C n n ch , 2 , 2 1 ch , 2 , 2 1
68
NOKIA
The OVSF codes are only effective when the channels are perfectly synchronized at symbol level. The loss in cross-correlation, e.g. due to multi-path, is compensated by the additional scrambling operation. With the scrambling operation the real (I) and imaginary (Q) parts of the spread signal are further multiplied by a complex-valued scrambling code. As already pointed out, the scrambling codes are used to separate different cells in the downlink and different terminals in the uplink direction. They have good correlation properties (interference averaging) and are always used on top of the spreading codes, thus not producing any effect on the transmission bandwidth.
UL Spreading and Modulation (1/2)

DPCCH/DPDCH DPCCH/
Cd,1 DPDCH1 DPDCH3 DPDCH5 Cd,3 Cd,5 d d d d d
I/Q code multiplexing (dual-channel QPSK modulation) to avoid audible interference if no UL data transmitted Complex-valued scrambling operation to avoid BPSK-type modulation @ high bit-rate (DPDCH and DPCCHs leads to multicode transmission )
S dpch, n
Re{S} Split real & imag. parts Pulseshaping Pulseshaping
cos(t)
DPDCH2 DPDCH4
Cd,2 Cd,4
I+jQ
Im{S}
DPDCH6 DPCCH
Cd,6
69
NOKIA
DPCCH always spread by code C = Cch,256,0 where k = 0 DPCCH always spread by code Cc c Cchch,256,0 where k = 0 = ch,256,0 ,256,0 DPDCH spread by code Cd ,1 = Cch,SF,k where k = SF/4 is the OVSF code number spread by code Cd ,1 = Cchch,SF,k DPDCH1 1 ch,SF,k where k = SF/4 is the OVSF code number ,SF,k Multicode all DPDCHs have spreading factors equal to 4 Multicode, Multicode all DPDCHs have spreading factors equal to 4 Multicode, Cc c Short scrambling codes (assigned by upper layers , 224 codes) Short scrambling codes (assigned by upper layers , 224 codes) Used if in the Node B multi-user detectors or interference cancellation receivers are used Used if in the Node B multi-user detectors or interference cancellation receivers are used Long scrambling codes (assigned by upper layers, 224 codes) Long scrambling codes (assigned by upper layers, 224 codes) 10 ms long (38400 chips with 3.84 Mcps). Used if in the BS a Rake receiver is used 3 10 ms long (38400 chips with 3.84 Mcps). Used if in the BS a Rake receiver is used 3 The DPCCH/DPDCH may be scrambled by either long or short scrambling codes DPCCH/ The DPCCH/ DPDCH may be scrambled by either long or short scrambling codes DPCCH/ 3G Mobile Systems.PPT v.0.0.3/ March 2002 / David Soldani
Q j
-sin(t)
DPCCH/ Uplink DPCCH/DPDCH Spreading Real-valued spread signals are weighted by gain factors c for DPCCH and d for all factors, DPDCHs (at every instant in time, at least one of the values c and d has the amplitude 1.0); the stream of real-valued chips on the I and Q-branches are then summed and treated as a complex-valued stream of chips. This complex-valued signal is then scrambled by the complex-valued scrambling code Sdpch,n complexdpch,n The DPCCH is always spread by code Cc = Cch,256,0 where k = 0. ch,256,0 When only one DPDCH is to be transmitted, DPDCH1 is spread by code Cd,1 = Cch,SF,k ch,SF,k where SF is the spreading factor of DPDCH1 and k= SF/4 is the OVSF code number. When more than one DPDCH is to be transmitted, all DPDCHs have spreading factors equal to 4: DPDCHn is spread by the the code Cd,n = Cch,4,k , where k = 1 if n {1, 2}, k = 3 ch,4,k if n {3, 4}, and k = 2 if n {5, 6}. Uplink spreading The spreading factor on DPDCH may vary on a frame by frame basis. The UE provides the TFCI to allow data detection with a variable SF on the DPDCH. Uplink scrambling codes All uplink physical channels are subjected to scrambling with a complex-valued scrambling code (scrambling sequence). The transmission from different UEs are separated by the scrambling codes. Uplink scrambling codes are assigned by higher layers. In uplink direction there are two alternatives: Short scrambling codes Is 256 chips. chips. Used if in the Node B multi-user detectors or interference cancellation receivers are used. Long scrambling codes 10 ms frame length (38400 chips with 3.84 Mcps). 38400 Used if in the Node B a Rake receiver is used. The DPCCH/DPDCH may be scrambled by either long or short scrambling codes. DPCCH/ There are 224 long and 224 short uplink scrambling codes No uplink code planning need (millions of codes available)
UL Spreading and Modulation (2/2)

PRACH (or PCPCH) message part PCPCH)
Preamble Signature s, 0 s 15 Cc = Cch,256,m where m = 16*s + 15 ch,256,m Cd = Cch,SF,m where SF is the spreading factor used for the data part and m = SF*s/16 ch,SF,m
PRACH message data part PRACH message control part
Cd
Sr-msg, n
(Long SC)
Split S& real Re{S} Pulseshaping Pulseshaping
cos(t)
Cc
I+jQ j
imag. parts
Im{S}
-sin(t)
The Random Access Preamble code Cpre,n is derived from a preamble scrambling code Sr-pre,n, which is also pre,n ,n, pre, constructed from the long scrambling sequences as a function of the downlink primary scrambling code used cell, in the serving cell and a preamble signature Csig,s sig,s
70
NOKIA
PRACH message part and preamble codes The preamble signature s, 0 s 15 points to one of the 16 nodes in the code-tree 15, that corresponds to channelization codes of length 16. The sub-tree below the specified node is used for spreading of the message part. The control part is spread with the channelization code Cc of spreading factor 256 in the lowest branch of the sub-tree, i.e. Cc = Cch,256,m where m = 16*s + 15. ch,256,m The data part is spread by channelization code Cd = Cch,SF,m and SF is the spreading ch,SF,m factor used for the data part and m = SF*s/16. The PRACH message part is scrambled with a long scrambling code. The scrambling code for the PRACH preamble part is also constructed from the long scrambling sequences. The 8192 preamble scrambling codes are divided into 512 groups with 16 codes in each group for a one-to-one correspondence between the preamble scrambling code and the downlink primary scrambling code m used in the serving cell. The random access preamble code Cpre,n, is derived from a preamble scrambling code Sr-pre,n and a preamble signature Csig,s. In one cell may be configured several RACHs/PRACHs and the available pairs of RACH and PRACHs and their respective parameters and codes are indicated in system information. The various PRACHs are distinguished either by employing different preamble scrambling codes, or by using a common scrambling code but distinct (non-overlapping) partitions of available signatures and available subchannels. PCPCH message part and preamble codes The spreading and scrambling of the PCPCH message part is similar to the one illustrated for the PRACH. The same observation is valid for the preamble codes used for PCPCH.
DL Spreading and Modulation (1/2)

All downlink physical channels
Any downlink physical channel except SCH
S P
I Cch,SF,m Q j
S dl,n I+jQ S G1 G2 cos(t) P-SCH G S-SCH P

S Split real & imag. parts Im{S}
Re{S}
Pulseshaping Pulseshaping
P-CPICH always spread by code C = Cch,256,0 P-CPICH always spread by code Cchch Cchch,256,0 = ch,256,0 ,256,0 P-CCPCH always spread by code C = Cch,256,1 P-CCPCH always spread by code Cchch Cchch,256,1 = ch,256,1 ,256,1 Multicode all DPDCHs have the same SF (different SF allowed for different CCTrCHs) Multicode, Multicode all DPDCHs have the same SF (different SF allowed for different CCTrCHs) Multicode, The SF does not vary on a frame-by-frame basis (DTX on DPDCH is used) The SF does not vary on a frame-by-frame basis (DTX on DPDCH is used) Long scrambling codes (assigned by upper layers, 218 1 codes, 8192 in practice) Long scrambling codes (assigned by upper layers, 218 1 codes, 8192 in practice) 10 ms long (38400 chips with 3.84 Mcps) 38400 10 ms long (38400 chips with 3.84 Mcps) 38400 Each cell is allocated 1 primary SC (trivial task, no planning needed) Each cell is allocated 1 primary SC (trivial task, no planning needed)
One code tree per cell is used and the code tree under a single scrambling code is then One code tree perseveralused and the code tree under a single scrambling code is then shared between cell is users shared between several users
-sin(t)
GS
Downlink Spreading and Modulation

A part from SCHs, each pair of two consecutive symbols is first serial-to-parallel converted and mapped onto I and Q branches. The I and Q branches are then spread to the chip rate by the same channelization code Cch,SF,m. The sequences of real-valued chips on the I and Q branch are then scrambled using a complex-valued scrambling code, denoted Sdl,n. The scrambling code is applied aligned with the scrambling code applied to the P-CCPCH, where the first complex chip of the spread P-CCPCH frame is multiplied with chip number zero of the scrambling code. After spreading, each physical downlink channel (except SCHs) is separately weighted by a weight factor, denoted Gi in the figure. The complex-valued P-SCH and S-SCH are separately weighted by weight factors Gp and Gs. All downlink physical channels are combined together using a complex addition and the resulting sequence generated by the spreading and scrambling processes is then QPSK modulated.
Downlink spreading codes

In the downlink the same channelization codes as in the uplink (OVSF codes) are used. Typically only one code tree per cell is used and the code tree under a single scrambling code is then shared between several users. By definition, the channelization code used for P-CPICH and P-CCPCH is Cch,256,0 and Cch,256,1, respectively. Resource manager in the RNC assigns the channelization codes for all the other channels, with some restrictions on the usage of spreading factor 512 in case of diversity handover. In compressed mode there are three methods for generating gaps rate matching, reduction of the spreading factor by a factor of two and higher layer scheduling. When the mechanism for opening the gap is by reducing the SF of 3 dB, the OVSF code used for compressed frames is Cch,SF/2,n/2, if an ordinary scrambling code is used; and Cch,SF/2,n mod SF/2, if an alternative scrambling code is used (see next slide), where Cch,SF,n is the channelization code used for non-compressed frames. In the downlink the SF of the DPCH does not vary on a frame-by-frame basis. The data rate variation on DPCH is managed with either a rate matching operation or with Layer 1 discontinuous transmission (DTX), where the transmission is interrupted during a part of the DPDCH slot. In case of multicode transmission, the parallel code channels have different channelisation codes, but equal spreading factor under the same scrambling code. Different spreading factors may be employed in case of several CCTrCHs received by the same UE. The OVSF code may vary from frame to frame on the PDSCH. The rule is such that the OVSF code(s) below the smallest spreading factor is from the branch of the code tree pointed by the smallest spreading factor used for that connection. If the DSCH is mapped onto multiple parallel PDSCHs, the same rule applies, but all branches identified by the multiple codes, corresponding to the smallest spreading factor, may be used for higher spreading factor allocation.
DL Spreading and Modulation (2/2)

Scrambling code
Primary scrambling code Set1 = i = 0, 1, , 511 (P-CPICH, P-CCPCH, PICH, AICH, and S-CCPCH carrying PCH) Group 1 (of 8 P-Scrambling Codes) {16*( 8*0 +l)} I = 0, , 7
i set of 15 Secondary scrambling codes : {16*i+k} k=1, 2, , 15 (Other PhCH Cell) : Set16i+1 = {S16 * i, dl , S16 * i + 1, dl ,..., S16 * i + k, dl ..., S16 * i + 15, dl }
{S
0, dl
, S1, dl , S 2, dl ,..., S k, dl ..., S15, dl }
th
Group j {16*(8j+l)} l = 0, ...,7 j = 0, ..., 63
: : Set512 = {S8176, dl , S8177 + 1, dl ,..., S8 176 + k, dl ..., S8191 , dl }
Group 64 {16*( 8*63+l)} I = 0, , 7
Note: the primary CCPCH, primary CPICH, PICH, AICH, and S-CCPCH carrying PCH are always transmitted using the primary scrambling code
Downlink scrambling codes In the downlink only long scrambling codes are used. There are 218-1 (= 262143) scrambling codes, numbered from 0 to 262142. The scrambling code sequences, denoted Sdl,n, are constructed as segments of the Gold sequence by combining two real sequences into a complex scrambling code sequence. In order to speed up the cell search procedure only 8192 codes of those are used in practice; and the phase pattern from 0 to 38399 is forcibly repeated, thus resulting in a periodical scrambling code of period 10 ms, which facilitates the UE in finding the correct code phase. Only the scrambling codes with k = 0, 1, , 8191 can be employed. Those codes are divided into 512 sets. Each set consists of a primary scrambling code and 15 secondary scrambling codes, unambiguously associated the ones to the others, i.e. the ith primary scrambling code corresponds to ith set of secondary scrambling codes. The set of primary scrambling codes is further divided into 64 groups of 8 primary scrambling codes. Each primary scrambling code k is unambiguously associated with a left (denoted k + 8192) and a right alternative scrambling code (denoted k + 16384), which can be used for scrambling compressed frames, during the downlink compressed mode. Each cell is allocated one and only one primary scrambling code. The primary CCPCH, primary CPICH, PICH, AICH, and S-CCPCH carrying PCH are always transmitted using the primary scrambling code. The allocation of primary scrambling codes is a trivial task and can be done with the aid of any planning tool. The other downlink physical channels can be transmitted with either the same primary scrambling code or using a secondary scrambling code taken from the set of codes associated with it. For one CCTrCH is allowed the mixture of primary and secondary scrambling codes. However, if the CCTrCH is type DSCH, then all PDSCH channelisation codes received by a single UE must be under a single scrambling code.
Maximum Downlink Capacity (1/2)

Common Channels Soft HO overhead Spreading factor for AMR Chip rate Modulation 10 codes with SF = 128 20% 128 3.84 Mcps QPSK, 2 bits/symbol
Average DPCCH overhead for data 10% Channel coding rate for data 1/3 with 30% puncturing
AMR 12.2 kbps and one SC per cell

Maximum Downlink Capacity (2/2)

Speech full rate (AMR 12.2 kbps) 128 channels *(128-10)/128 /1.25 = 94 channels 3.84 106 *(128-10)/128/1.25 *2 *0.9 /3 /(1-0.3) = 2.4 Mbps 2.4 N. of codes with SF 128 CCH overhead Soft HO overhead Chip rate CCH and Soft HO overhead QPSK modulation DPCCH overhead 1/3 rate channel coding 30% puncturing = 94*12.2*3*0.7/1000
Throughput
AMR 12.2 kbps and one SC per cell

Part of the DL orthogonal codes must be reserved for the common channels and for soft and softer HO overhead. With this assumption the maximum number of speech calls per cell is 94 and the maximum data throughput is 2.4 Mbps.
High Speed Downlink Packet Access HS-DSCH) (HS-DSCH)
75
NOKIA
Achievable HSDPA Peak Data Rates

Modulation SF
16 QPSK 16 16 16QAM 16 16
Turbo code rate

1/4 2/4 3/4 2/4 3/4
Bits/block /code
240 470 711 950 1440
Throughput (10 codes)

1.2 Mbps 2.4 Mbps 3.6 Mbps 4.8 Mbps 7.2 Mbps
Throughput (15 codes)

1.8 Mbps 3.6 Mbps 5.3 Mbps 7.2 Mbps 10.7 Mbps
76
NOKIA
Basic block length is 2 ms corresponding to 3 time slots. Shown code rates are not accurate since transport block size will be semi-static. Hence, rate matching is used to fill out the TTI. 64QAM has been suggested for HSDPA as well. However, due to performance and complexity issues, 64QAM may not be supported. 16QAM with 15 multi-codes supports >10Mbps throughput.
HSHS-DSCH versus DSCH

FEATURE
TTI Size (link adaptation rate) Variable spreading factor (VSF) Fast power control Adaptive modulation and coding (AMC) Multi-code operation H-ARQ with soft combining/incremental redundancy Handover support Support for Tx/Rx diversity or MIMO
DSCH
10 ms Yes Yes No (Yes) No Hard Tx/Rx
HS-DSCH
2 ms No No Yes Yes (10) Yes Hard/(FCS, Rel6?) Tx/Rx, (MIMO Rel 6?)
77
NOKIA
In HSDPA fast power control and variable SF are replaced by AMC and multicodes combined with H-ARQ. Additionally, HSDPA facilitates faster scheduling and link adaptation rate.
HSDPA Protocol Architecture

HS-DSCH FP (frame protocol)
RLC MAC MAC-c/sh MAChs HSDSCH FP L2 HSDSCH FP L2 HSDSCH FP RLC MAC-D HSDSCH FP
L2
L2
PHY
PHY
L1
L1
L1
L1
Uu
Iub
Iur
UE
Node B
SRNC
DRNC
78
NOKIA
SDUs to be transmitted are transferred from MAC-c/sh to the MAC-hs via the Iub interface. Hybrid ARQ, link adaptation & packet scheduling are included in MAC-hs and located in Node-B The possibility to connect directly the HS-DSCH user plane of the SRNC and Node B using the transport network, i.e. by-pass the DRNC for the HS-DSCH user plane, is under consideration
Physical-Layer Structure in Time Domain hysical Channelization codes at a fixed spreading factor SF=16 Multi-code transmission is allowed The same scrambling code sequence is applied to all the channelisation codes that form a single HS-DSCH CCTrCH Furthermore, multiple UEs may be assigned channelisation codes in the same TTI i.e. multiplexing of multiple UEs in code-domain is allowed The length of the HS-DSCH TTI is 3Tslot, where Tslot is equal to 2560 chip (0.67 ms) The TTI for HS-DSCH is a static transport-format parameter
CCTrCH and transport channels There is only one CCTrCH of HS-DSCH type per UE. If there are several HS-DSCH transport channels in an HS-DSCH CCTrCH, the transport format combinations are configured in such a way that for any transport format combination, there is a maximum of one transport channel having a transport format with one or more transport blocks. There is no need to balance the quality between several transport channels. As such, there is no need for static rate matching parameters. As for the DSCH of Release-99, flexible positions are assumed.
Channel Coding and Modulation

Link Adaptation

TF, modulation scheme and code rate, can be selected based on the downlink channel quality The selection of transport format is done by the MAC-HS located in Node B and can be based on e.g.

Channel-quality feedback reported by the UE, or From the transmit power of an associated DPCH Other methods may also be possible
Redundancy-version (RV) parameter Physical Layer Hybrid-ARQ functionality
Code block segmentation
TrBlk concatenation
CRC attachment
Channel Coding
Interleaving
80
NOKIA
Transport block concatenation and code block segmentation The same transport block concatenation and code block segmentation as in Release-99 is used for HS-DSCH. However, Transport block concatenation is performed before CRC attachment since there is only one CRC per TTI. The maximum code block size for turbo coding is 5114. CRC Attachment A CRC of size 24 bits is calculated and added per HS-DSCH TTI. The CRC polynomial is defined in 3G TS 25.212. Channel Coding HS-DSCH channel coding uses the existing rate 1/3 Turbo code and the existing Turbo code internal interleaver, as outlined in 3G TS 25.212. Other code rates are generated from the basic rate 1/3 Turbo code by applying rate matching by means of puncturing or repetition. hysicalHybridPhysical-layer Hybrid-ARQ This functionality is an extension of the release 99 rate matching. The Hybrid-ARQ functionality matches the number of bits at the output of the channel (turbo) coder to the total number of bits of the HS-DSCH physical channels. The Hybrid-ARQ functionality is controlled by the parameter RV (Redundancy Version), i.e. the exact set of bits at the output of the physical-layer Hybrid-ARQ functionality depends on the number of input bits, the number of output bits, and the RV parameter. Channel Coding for Control Channels Defined in previous slides DTX indication bits DTX insertion is not employed. Since only one transport channel per TTI is supported, the rate-matching algorithm is used to fill the available physical resource, instead of using DTX insertion. Interleaving Since the HS-DSCH TTI is static, only one interleaving (corresponding to Release-99 2nd interleaving) is needed. The interleaver has to be adapted to 3 slots. For TDD, interleaving adaptation has to be done to the HS-DSCH TTI length. Physical channel mapping The bits can be mapped to multiple physical channels in the same way as in release'99. Modulation Two types of modulations namely QPSK and 16-QAM may be applied for HS-DSCH. 16-
PhCH#1
PhCH#2
Downlink Physical Channel Structure
Node B
Downlink DPCH Shared Control Channel #1 Shared Control Channel #2
UE
Shared Control Channel #M
81
NOKIA
Choice of Hybrid ARQ combining schemes a) For a retransmission, the transport-block set is the same as for the initial transmission. This means that, for a retransmission, the number of information bits NINFO to be transmitted is the same as for the initial transmission. Furthermore, for a retransmission, the modulation scheme and the channelisation-code set, including the size of the channelisation-code set, and the transmission power, may be different compared to the initial transmission. This means that, for a retransmission, the number of available channel bits Nch may differ compared to the initial transmission. Even if the number of available channel bits Nch is the same, the set of channel bits may be different for the retransmission compared to the initial transmission (Incremental Redundancy). b) Regardless of the number of information bits NINFO, channel coding is done using a Turbo code with rate Rbasic = 1/3. Each retransmission may use a different redundancy version, where each redundancy version is a different subset of the coded bits. Each subset may contain a different number of bits. Chase combining corresponds to defining or using only a single redundancy version. Physical layer aspects of Hybrid ARQ The following signalling is needed to support Hybrid ARQ: Downlink Signaling The HARQ information includes the Hybrid ARQ process identifier in the corresponding HSDSCH TTI. The HARQ information also includes information about the redundancy version of the transmission in the corresponding HS-DSCH TTI. Uplink Signaling For communicating the HARQ acknowledgements, an 1-bit ACK/NACK indication is used in the uplink. hysicalPhysical-channel structure It consists of a downlink DPCH and a number of SCCH-HSs. The number of SCCH-HSs can range from a minimum of one SCCH-HS (M=1) to a maximum of four SCCH-HSs (M=4). Shared Control Channel For each HS-DSCH TTI, each Shared Control Channel (SCCH-HS) carries HS-DSCH-related downlink signalling for one UE. The following information is carried on the SCCH-HS: Transport-format and Resource related Information (TFRI);The exact number of bits for the Hybrid-ARQ-related information is FFS
Downlink DPCH
Example of coding of HS-DSCH Indicator (HI) HS
Pi indicates SCCH-HS #i (i {1, 2, 3, 4}) P0 indicates that no SCCH-HS carries HS-DSCH-related signalling information to the UE
P4 (-1 +1) P1 (+1 +1)
P0 (0 0)
P2 (-1 1)
P3 (+1 1)
82
NOKIA
If a downlink DPCH is present, it carries an HS-DSCH Indicator (HI), in addition to non-HS-DSCH-related physical-layer signalling and DCH transport channels. The HI consists of two information bits that indicate the SCCH-HS that carries the HS-DSCHrelated signalling for the corresponding UE. The HI is transmitted in every third slot. If no SCCH-HS carries HS-DSCH-related signalling to the UE, the HI is not transmitted (DTX). As an example, if the HI is transmitted as one QPSK symbol, the possible signalling points are as in the figure. The QPSK symbol carrying the HI is punctured on the DPDCH. However, the puncturing position is TBD.
Downlink Timing Structure

Tslot (0.67 ms) Downlink DPCH (maximum Downlink DPCH (maximum late) HI HI
HI 3Tslot (2 ms)
HI
Shared Control Channel HS-DSCH TTI (2 ms) HS-DSCH
HS-DSCH-control=(5120+mx256)chips
83
NOKIA
The figure illustrates the timing structure for the HS-DSCH control signalling. The fixed time offset between the SCCH-HS information and the start of the corresponding HS-DSCH TTI equals HS-DSCH-control (2*Tslot+m*256chips=(5120+m*256)chips where ). The time offset between the DL DPCH slot carrying the HI and the start of the SCCH-HS information can vary in the interval [0, Tslot] depending on the timing of the downlink DPCH. It may be noted that the start of the HI overlaps with the first slot of the SCCH-HS Figure 4 illustrates the two extreme cases of the timing of DPCH vs SCCH-HS.
HSHS-DSCH Uplink Signalling

DPCCH-HS with SF=256 that is code multiplexed with the existing dedicated uplink physical channels The HS-DSCH related uplink signalling consists of
H-ARQ acknowledgement and Channel quality indicator
84
NOKIA
In FDD, the HS-DSCH related uplink signalling uses DPCCH-HS with SF=256 that is code multiplexed with the existing dedicated uplink physical channels. The HSDSCH related uplink signalling consists of H-ARQ acknowledgement and channel quality indicator. HSHS-DSCH Associated Uplink Dedicated Control Channel The following information is carried on the HS-DSCH associated uplink dedicated control channel (DPCCH-HS):
H-ARQ acknowledgment, A 1-bit Ack/Nack indication is used for a H-ARQ acknowledgement. The acknowledgement bit is repetition coded to 10 bits and transmitted in one slot. H-ARQ acknowledgement field is DTXed when there is no ACK/NACK information being sent. Measurement feedback information
Measurement feedback information contains channel quality indicator that may be used to select transport format and resource by HS-DSCH serving Node-B. A [5]-bit channel quality indicator is coded and transmitted over two slots. The transmission cycle and timing for channel quality indicator is determined by UTRAN and signalled by higher layer. The channel quality indicator consists of a recommended TFRC provided by the UE to Node-B. The recommended TFRC is chosen by the UE from a TFRC reference list. The ACK/NACK message is transmitted with a power offset PAN relative to the Release '99 uplink DPCCH. The power offset PAN is a higherlayer parameter.
WCDMA Radio Link Performance Indicators
85
NOKIA
UE Measurement Abilities
CPICH Ec/N0

CPICH RSCP
Received energy per chip divided by the power density in the band Ec/N0 = RSCP/RSSI Received Signal Code Power, the received power on one code measured on the Primary CPICH Received Signal Strength Indicator, the wide-band received power within the relevant channel bandwidth Block Error Ratio for each TrCH having CRC Terminal transmission power
UTRA carrier RSSI
TrCH BLER
UE Tx Power
86
NOKIA
Ec/No CPICH Ec/No Received energy per chip divided by the power density in the band Measurement performed on the Primary CPICH The reference point for Ec/N0 is the antenna connector at the UE If Tx diversity is applied on the Primary CPICH the received energy per chip (Ec) from each antenna shall be separately measured and summed together in [Ws] to a total received chip energy per chip on the Primary CPICH, before calculating the Ec/N0 CPICH RSCP Received Signal Code Power The received power on one code measured on the Primary CPICH The reference point for the RSCP is the antenna connector at the UE If Tx diversity is applied on the Primary CPICH the received code power from each antenna shall be separately measured and summed together in [W] to a total received code power on the Primary CPICH UTRA carrier RSSI Received Signal Strength Indicator The wide-band received power within the relevant channel bandwidth Measurement shall be performed on a UTRAN downlink carrier The reference point for the RSSI is the antenna connector at the UE Other measurements PCCPCH RSCP GSM carrier RSSI Transport channel BLER UE transmitted power SFN-CFN observed time difference SFN-SFN observed time difference UE Rx-Tx time difference Observed time difference to GSM cell UE GPS Timing of Cell Frames for LCS
UTRAN Measurement Abilities

Received carrier power
The wide-band received power within the UTRAN uplink carrier channel bandwidth in an UTRAN access point Ratio between the total transmitted power and the maximum transmission power Transmitted power on one channelisation code on one given scrambling code on one given carrier
Transmitted carrier power
Transmitted code power
SIR Signal to Interference Ratio (defined in UL only)

SIRDPCCH = (RSCPDPCCH/ISCP)*SFDPCCH Eb/N0 = SIRDPCCH*[N+(c/d)2]*(RDPDCH/Ruser)*(d/c)2*(SFDPDCH/SFDPCCH) For a single bearer service, N = n. of channelisation codes
87
NOKIA
Received carrier power
Transmitted carrier power
The wide-band received power within the UTRAN uplink carrier channel bandwidth in an UTRAN access point The reference point for the received carrier power measurements shall be the antenna connector Ratio between the total transmitted power and the maximum transmission power Total transmission power is the mean power [W] on one carrier from one UTRAN access point Maximum transmission power is the mean power [W] on one carrier from one UTRAN access point when transmitting at the configured maximum power for the cell (on any carrier transmitted from the UTRAN access point) The reference point for the transmitted carrier power measurement shall be the antenna connector In case of Tx diversity the transmitted carrier power for each branch shall be measured Transmitted power on one channelisation code on one given scrambling code on one given carrier (on any DPCH transmitted from the UTRAN access point and shall reflect the power on the pilot bits of the DPCH) The reference point for the transmitted code power measurement shall be the antenna connector In case of Tx diversity the transmitted code power for each branch shall be measured
Transmitted code power
SIR Signal to Interference Ratio
Other measurements
SIR = (RSCP/ISCP)*SF = Uplink Es/No Where RSCP, Received Signal Code Power, the received power on one code measured on the pilot bits; ISCP, Interference Signal Code Power, the interference on the received signal measured on the pilot bits; SF, Spreading Factor used on DPCCH (256). SIR is measured on DPCCH after RL combination in Node B; The reference point for the SIR is the antenna connector of the UE Eb = (N*RSCPd+RSCPc)/Ru Eb/N0 = RSCPd(N+(c/ d)2)*W/(Ru*ISCP) = SIRc*(Rd/Ru)(N+(c/ d)2)*(d/ c)2*(SFd/SFc). Transport channel BER Physical channel BER Round trip time UTRAN GPS timing of cell frames for LCS PRACH/PCPCH propagation delay Acknowledged PRACH preambles Detected PCPCH access preambles Acknowledged PCPCH access preambles
Layer 1 Processing
88
NOKIA
Maximal Ratio Combining of Symbols

Transmitted symbol in a slot Received symbol + Noise
Modified Combined with symbol channel + estimate Residual noise and relative delay compensation (for combining) Depending on distance, medium and attenuation of path between UE and WCDMA BTS, channel can rotate signal to any phase and to any amplitude QPSK (pilot) symbols carry information in phase Energy splitted to many fingers combining (Pilots for SIR estimation and Data symbols) Maximal ratio combining corrects channel phase rotation (for combining) and weights components with channel amplitude estimate Less bias in the signal power estimate after combining (noise cancel), a further benefit is achieved in averaging the combination upon pilot symbols on each slot Same method used also for antenna combining (BTS, UE) and softer handover (BTS) and soft/softer handover (UE)
finger #1
finger #2
finger #3
The chip duration is 260 ns the WCDMA receiver can separate multipath components and combine them if the difference in path length is at least 78 m
General The delay profile extends from 1-3 s in urban and suburban area; it can be more of 20 s in hilly area The chip duration is 260 ns the WCDMA receiver can separate multipath components and combine them if the difference in path length is at least 78 m The fast fading (signal cancellation) is due to the relative phase shift [difference in path (/2 = 7 cm) and reflection coefficients (boundary conditions)] of the different contributions arriving at the receiver The response of a matched filter identifies the delay positions at which significant energy arrives, and the correlation receivers (RAKE fingers) are allocated to those peaks Within each correlation receiver, the fast changing phase and amplitude values are tracked and removed (pilot symbols are used to sound the channel and provide an estimate of the momentary channel state for a particular finger, then the received symbol is rotated back, so as undo the phase rotation caused by the channel) The demodulated and phase-adjusted (data and pilots) symbols across all active fingers are combined (recovering the energy across all delay positions, Maximal Combining) Ratio Combining and presented to the decoder for further processing Processing at the chip rate (correlator, code generator and matched filter) is done in ASICs, whereas symbol level processing (channel estimator, phase rotator, combiner) is implemented by a DSP Multiple receiver antennas (including the softer HO case) can be accommodated in the same way as multiple paths received from a single antenna (separated busses are used): by just adding additional Rake fingers to the antennas (actually the same n. of CHE fingers are shared to the peaks belonging to different antennas)
RAKE Diversity Receiver

Digitized input samples
(from RF, I/Q branches) Despreading and integration to user data symbols Estimation of the state of the channel form pilot symbols and channel effect removal Compensation of the delay for the difference in the arrival times of the symbols in each finger
Correlator
I Q
Phase rotator Channel estimator
Delay Equalizer
I Q
I Q
Code generators
Finger 1 Finger 2 Finger 3
Combiner
Addition of the channel compensated symbols multipath diversity against fading assignment of the RAKE fingers to the largest peaks Determination and updating of the multipath delay profile of the channel
Timing (finger allocation)
Matched filter
90
NOKIA
Delay Profile Estimation with MF

Multipath propagation causes several peaks in matched filter (MF) output Allocate RAKE fingers to these peaks Later: track and monitor the peaks
Node B
UE
91
NOKIA
Matched Filter
To make a successful despreading, code and data timing must be known The propagation delay profile can be detected e.g. by a matched filter
Predefined (parallel) data (codes only)
When samples of incoming serial data are equal to bits of predefined data, there is a maximum at filter output Incoming serial data
+1 -1
Tap 127 Tap 126
Tap 0
Register 1
Sample 127 Sample 126 Sample 0
Register 2
92
NOKIA
UL Receiver diversity (space diversity)

Amplitude Antenna RAKE combining (MRC) Fading Time
Node B
= Antenna 1 = Antenna 2
SRNC
RNC
DL Receiver diversity (space diversity)

Amplitude = Antenna 1 = Antenna 2
Fading Antenna RAKE combining (MRC)

Node B
Time
SRNC
RNC

WCDMA UTRAN Interfaces and Protocol Stacks

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WCDMA UTRAN Interfaces and Protocol Stacks

Uploaded by

Copyright:

Available Formats

UTRAUTRA-FDD Radio Communication

3G Mobile Systems.PPT v.0.0.3/ March 2002 / David Soldani

UTRAN Interfaces and Protocol Stacks

3G Mobile Systems.PPT v.0.0.3/ March 2002 / David Soldani

Network Elements and Interfaces

3G Mobile Systems.PPT v.0.0.3/ March 2002 / David Soldani

Reference point between subsystems (domains)

Data exchange between layers

ELEMENT X (peer or entity)

ELEMENT Y (peer or entity)

UTRAN specific protocols

UTRAN Interfaces Protocol Stacks

Transport Network Layer

IuUTRAN Iu-CS Interface Stack

Control Plane RANAP

User Plane Iu User Plane Protocol

Transport Network Layer

Transport Network User Plane

Transport Network Control Plane Q.2630.1

Transport Network User Plane

Codec control information (Codecs in CN)

SCCP MTP3b SSCF-NNI SSCOP

Q.2150.1 MTP3b SSCF-NNI SSCOP AAL5 AAL2

SS7 Stack on SAAL-NNI

ATM Physical Layer

One transport connection per Radio Access Bearer

3G Mobile Systems.PPT v.0.0.3/ March 2002 / David Soldani

IuUTRAN Iu-PS Interface Stack

Control Plane RANAP

User Plane Iu User Plane Protocol

Same protocols as the Iu-CS

Transport Network Control Plane

Transport Network User Plane

Typically no FP header (transparent mode)

Two options for signalling transport

MTP3-B SSCF-NNI SSCOP AAL5

No signalled transport connections (no AAL2 connection establishment in TNL)

GTP-U UDP IP AAL5

User plane of the GPRS Tunnelling Protocol is used

ATM Physical Layer

ATM Physical Layer

3G Mobile Systems.PPT v.0.0.3/ March 2002 / David Soldani

UTRAN Iur Interface Stack

Control Plane RNSAP

Transport Network Layer

Transport Network User Plane

Transport Network Control Plane

Transport Network User Plane

SCCP MTP3-B SSCF-NNI M3UA SCTP IP AAL5

Q.2150.1 MTP3-B SSCF-NNI SSCOP AAL5 M3UA SCTP IP AAL2

Each dedicated channel has a dedicated transport connection

ATM Physical Layer

3G Mobile Systems.PPT v.0.0.3/ March 2002 / David Soldani

UTRAN Iub Interface Stack

Control Plane NBAP

User Plane DCH FP CCH FP

Transport Network Layer

Transport Network User Plane

Transport Network Control Plane

Transport Network User Plane

Q.2150.2 SSCF-UNI SSCOP AAL5 SSCF-UNI SSCOP AAL5 AAL2

ATM Physical Layer

3G Mobile Systems.PPT v.0.0.3/ March 2002 / David Soldani

RADIO LINK SETUP RESPONSE