PLMN Selection:There are two modes for PLMN selection: Automatic mode: This mode utilizes a list of PLMNs in priority order. The highest priority PLMN which is available and allowable is selected. Manual mode: Here the MS indicates to the user which PLMNs are available. Only when the user makes a manual selection does the MS try to obtain normal service on the VPLMN. Forbidden LA(stored in MS & SIM): No Suitable Cells In Location Area.On request of the NAS the AS should perform a search for available PLMNs and report them to NAS. The UE shall scan all RF channels in the UTRA bands according to its capabilities to find available PLMNs. On each carrier, the UE shall search for the strongest cell and read its system information, in order to find out which PLMN the cell belongs to. If the UE can read one or several PLMN identities in the strongest cell, each found PLMN shall be reported to the NAS as a high quality PLMN (but without the RSCP value), provided that the following high quality criterion is fulfilled: For an FDD cell, the measured primary CPICH RSCP value shall be greater than or equal to -95 dBm. For a TDD cell, the measured P-CCPCH RSCP shall be greater than or equal to -84 dBm. Found PLMNs that do not satisfy the high quality criterion, but for which the UE has been able to read the PLMN identities are reported to the NAS together with the CPICH RSCP value for UTRA FDD cells and P-CCPCH RSCP for UTRA TDD cells. The quality measure reported by the UE to NAS shall be the same for each PLMN found in one cell. The search for PLMNs on the rest of the carriers may be stopped on request of the NAS. The UE may optimize this search by using stored information of carrier frequencies and optionally also information on cell parameters, e.g. scrambling codes, from previously received measurement control information elements.

Initial UE Cell Selection:The purpose of the initial cell-selection procedure is to find a cell, not necessarily the best cell, but a usable cell, for the UE to camp on after power-on. In the UTRAN, the number of carrier frequencies is quite small. One operator typically operates only on two or three frequency carriers. In the first phase of UMTS in Europe, the frequency allocation for UMTS-FDD is 2 60 MHz (uplink/downlink), which means that there can be, at most, only 12 carrier frequencies of 5-MHz bandwidth each. These carriers are then divided between up to six operators. Each carrier will only support one operator. In principle the process includes the following: Search for primary synchronization channels (P-SCHs); Once such a channel is found, acquire time-slot synchronization from it; Acquire frame synchronization from the corresponding S-SCH; Acquire the primary scrambling code from the corresponding CPICH; Decode system information from the cell to check whether it is a suitable cell for camping (i.e., it contains the right PLMN code and access to it is allowed). The situation is different if the UE is roaming abroad, and the home PLMN is not found. In that case RRC has to report all available PLMNs to NAS and wait for its selection decision, which can be either automatic or manual (user selection).The initial cell-selection process is repeated as many times as necessary until the first suitable cell is found for camping. Once the UE has managed to camp on a cell, it decodes the system information from it, including the neighbor cell list. This information can be used to help the UE find the best cell to camp onto. Note that the initial cell-selection procedure only found a cell to camp on (the first possible cell). It is possible that this cell will not be the best possible cell.

Radio Frame SynchronisationCpCpCpCs1Cs1Cs2Primary SCHSecondary SCHPrimary CCPCH256 chips2560 - 256 chipsSlot 1Slot 2Slot 15Slot 1The UE completes the three step radio frame synchronisation processStep 1: Primary SCH identification and slot synchronisation (completed during cell search)(each cell in network uses same chip sequence)Step 2: Code group identification and frame synchronisation using the Secondary SCH(collection of 15 sequences, repeated every 10ms)Step 3: Scrambling code identification using the CPICHHaving completed these three steps the UE is able to decode the Primary CCPCH -> BCH -> BCCHUE is powered upRead BCCHCell selectionRegister with core networkOriginating AMR speech callHandoversRelease of AMR speech callRadio frame synchronisationCell searchPrimary CPICH

Relation between S-SCH & Scrambling Code Group

* Nokia Siemens Networks Presentation / Author / DateFor internal use

RACH Process

DownlinkBSL1 ACK / AICHUplinkMSPreamble1Not detectedMessage partPreamble2PRACH_preamble_retrans# PRACH preambles transmitted during one PRACH cycle without receiving AICH responseUEtxPowerMaxPRACH RACH_tx_Max# preamble power ramping cycles that can be done before RACH transmission failure is reportedPowerRampStepPRACHpreamblePowerOffsetLastPreamblePRACHmessageInitial preample power:Ptx = CPICHtransmissionPower-RSCP(CPICH) +RSSI(BS) + PRACHRequiredReceivedCI

UERNCNodeBMGW/CNRRC: RRC Connection Request (RACH)NBAP: Radio Link Setup RequestNBAP: Radio Link Setup ResponseALCAP: ERQ (Establish Request)ALCAP: ECF (Establish Confirm)RRC: RRC Connection Setup (FACH) [RRCconnRepTimer1/2(100ms,1s)]L1 SynchronizationNBAP: Synchronization IndicationRRC: RRC Connection Setup Complete (DCH)RRC: Initial Direct Transfer (MM: CM Service Request)SCCP: CR (Connection Request)RANAP: Initial UE Message (MM: CM Service Request)SCCP: CC (Connection Confirm)RANAP: Direct Transfer (MM: Authentication Request)RRC: Downlink Direct Transfer (MM: Authentication Request)RRC: Uplink Direct Transfer (MM: Authentication Response)RANAP: Direct Transfer (MM: Authentication Response)RANAP: Common IDRANAP: Security Mode CommandRRC: Security Mode CommandFP: Downlink SynchFP: Uplink SynchRRC Connection Establishment CELL DCH StateRNC checks if resources are available: BTS, AC, Transmission.If not it sends RRC Connection RejectT300=2s ; N300=3L1 SynchronizationT312=6s ; N312=4MOC CS Message Flow

UERNCNodeBMGW/CNRRC: Security Mode CompleteRANAP: Security Mode CompleteRRC: Uplink Direct Transfer (CC: Setup)RANAP: Direct Transfer (CC: Setup)RANAP: Direct Transfer (CC: Call Proceeding)RRC: Downlink Direct Transfer (CC: Call Proceeding)RANAP: RAB Assignment RequestNBAP: Radio Link Reconfiguration PrepareNBAP: Radio Link Reconfiguration ReadyALCAP: ERQ (Establish Request)ALCAP: ECF (Establish Confirm)NBAP: Radio Link Reconfiguration Commit)RRC: Radio Bearer SetupRRC: Radio Bearer Setup CompleteRANAP: RAB Assignment ResponseALCAP: ERQ (Establish Request)ALCAP: ECF (Establish Confirm)RAB EstablishmentFP: Downlink SynchFP: Uplink SynchRL modification procedure:SRB+DCH, HW resources checkedPossible failure in AAL2 setup (Iub, Iur and Iu)Soft handover is not allowed during the RAB establishment procedure (The mobile can not add or remove cells in AS) this makes the UE and Node B particularly sensitive to mobility and dominance Timer wf_rb_setup_cpl (6s) is started when the RRC: Radio Bearer Setup message is sent to the UE In case the timer expires Iu Release Request is sent to the CN with release cause (radio_conn_lost)< 1s

Call EstablishedUERNCNodeBRANAP: Direct Transfer (CC: Connect)RRC: Downlink Direct Transfer (CC: Connect)RRC: Uplink Direct Transfer (CC: Connect Acknowledge)RANAP: Direct Transfer (CC: Connect Acknowledge)RRC: Uplink Direct Transfer (CC: Release Complete)RANAP: Direct Transfer (CC: Release Complete)RANAP: Iu Release CommandRRC: Uplink Direct Transfer (CC: Disconnect)RANAP: Direct Transfer (CC: Disconnect)RANAP: Direct Transfer (CC: Release)RRC: Downlink Direct Transfer (CC: Release)RANAP: Iu Release CompleteMGW/CNRANAP: Location ReportRRC: Measurement ControlCall DisconnectRRC: Downlink Direct Transfer (CC: RRC Connection Release)RRC: Uplink Direct Transfer (CC: Release Complete)RRC: Uplink Direct Transfer (CC: Release Complete)NBAP: Radio Link Deletion RequestNBAP: Radio Link Deletion ResponseALCAP: ERQ (Establish Request)ALCAP: ECF (Establish Confirm)RANAP: Direct Transfer (CC: Alerting)RRC: Downlink Direct Transfer (CC: Alerting)

UERNCNodeBMGW/CNRRC: RRC Connection Request (RACH)NBAP: Radio Link Setup RequestNBAP: Radio Link Setup ResponseALCAP: ERQ (Establish Request)ALCAP: ECF (Establish Confirm)RRC: RRC Connection Setup (FACH)L1 SynchronizationNBAP: Synchronization IndicationRRC: RRC Connection Setup Complete (DCH)RRC: Initial Direct Transfer (MM: Paging Response)SCCP: CR (Connection Request)RANAP: Initial UE Message (MM: Paging Response)SCCP: CC (Connection Confirm)RANAP: Direct Transfer (MM: Authentication Request)RRC: Downlink Direct Transfer (MM: Authentication Request)RRC: Uplink Direct Transfer (MM: Authentication Response)RANAP: Direct Transfer (MM: Authentication Response)RANAP: Common IDRANAP: Security Mode CommandRRC: Security Mode CommandFP: Downlink SynchFP: Uplink SynchRRC Connection Establishment CELL DCH StateL1 SynchronizationMTC CS Message FlowRANAP: PagingRRC: Paging Type 1

UERNCNodeBMGW/CNRRC: Security Mode CompleteRANAP: Security Mode CompleteRRC: Uplink Direct Transfer (CC: Setup)RANAP: Direct Transfer (CC: Setup)RANAP: Direct Transfer (CC: Call Confirmed)RRC: Downlink Direct Transfer (CC: Call Confirmed)RANAP: RAB Assignment RequestNBAP: Radio Link Reconfiguration PrepareNBAP: Radio Link Reconfiguration ReadyALCAP: ERQ (Establish Request)ALCAP: ECF (Establish Confirm)NBAP: Radio Link Reconfiguration Commit)RRC: Radio Bearer SetupRRC: Radio Bearer Setup CompleteRANAP: RAB Assignment ResponseALCAP: ERQ (Establish Request)ALCAP: ECF (Establish Confirm)RAB EstablishmentFP: Downlink SynchFP: Uplink SynchRL modification procedure:SRB+DCH, HW resources checkedPossible failure in AAL2 setup (Iub, Iur and Iu)Soft handover is not allowed during the RAB establishment procedure (The mobile can not add or remove cells in AS) this makes the UE and Node B particularly sensitive to mobility and dominance Timer wf_rb_setup_cpl (6s) is started when the RRC: Radio Bearer Setup message is sent to the UE In case the timer expires Iu Release Request is sent to the CN with release cause (radio_conn_lost)

Call EstablishedUERNCNodeBRANAP: Direct Transfer (CC: Connect)RRC: Downlink Direct Transfer (CC: Connect)RRC: Uplink Direct Transfer (CC: Connect Acknowledge)RANAP: Direct Transfer (CC: Connect Acknowledge)MGW/CNRANAP: Location ReportRRC: Measurement ControlRANAP: Direct Transfer (CC: Alerting)RRC: Downlink Direct Transfer (CC: Alerting)

UENodeBRNCSGSNNBAP: Radio Link Setup RequestNBAP: Radio Link Setup ResponseAAL2SIG: ERQAAL2SIG: ECFNBAP: Synchronization IndicationRRC: Initial Direct Transfer (MM: Attach Request)RANAP: Initial UE Message MM: (Attach Request)RANAP: Direct Transfer (MM: GPRS Identity Request)RRC: Downlink Direct Transfer (MM: GPRS Identity Request)RRC: Uplink Direct Transfer (MM: GPRS Identity Response)RANAP: Direct Transfer (MM: GPRS Identity Response)RANAP: Direct Transfer (MM: Authentication & Ciphering Request)RRC: Downlink Direct Transfer (MM: Authentication & Ciphering Request)RRC: Uplink Direct Transfer (MM: Authentication & Ciphering Response)RANAP: Direct Transfer (MM: Authentication & Ciphering Response)RANAP: Security Mode CommandRRC: Security Mode CommandRRC: Security Mode CompleteRANAP: Security Mode CompleteRANAP: Common IDMOC PS Message FlowL1 SynchronizationRRC: RRC Connection Request (RACH)FP: Downlink SynchFP: Uplink SynchRRC: RRC Connection Setup Complete (DCH)RRC Connection Establishment CELL DCH StateRRC: RRC Connection Setup (FACH) [RRCconnRepTimer1/2(100ms,1s)]RNC checks if resources are available: BTS, AC, Transmission.If not it sends RRC Connection RejectL1 Synchronization

RANAP: Direct Transfer (MM: Attach Accept)RRC: Downlink Direct Transfer (MM: Attach Accept)RRC: Uplink Direct Transfer (MM: Attach Complete)RANAP: Direct Transfer (MM: Attach Complete)RRC: Uplink Direct Transfer (SM: Activate PDP Context Request)RANAP: Direct Transfer(SM: Activate PDP Context Request)UENodeBRNCSGSNMOC PS Message FlowNBAP: Radio Link Reconfiguration CommitRRC: Radio Bearer ReconfigurationRRC: Radio Bearer Reconfiguration CompleteNBAP: Radio Link Reconfiguration PrepareNBAP: Radio Link Reconfiguration ReadyRRC: Radio Bearer SetupRRC: Radio Bearer Setup CompleteRANAP: RAB Assignment ResponseRANAP: Direct Transfer(SM: Activate PDP Context Accept)RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept)RANAP: RAB Assignment RequestRRC: Measurement ControlRRC: Measurement Repor (Trafic Volume Reports 4a)AAL2SIG: ERQAAL2SIG: ECFRAB EstablishmentSRB + DCH 0/0RL modification procedure:SRB+DCH, HW resources checkedUplink & Downlink Data TransferIndication to transmit or receive data

RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)RANAP: Direct Transfer (SM: DeactivatePDP Context Request)RANAP: Direct Transfer(SM: Deactivate PDP Context Accept)RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept)NBAP: Radio Link Reconfiguration CommitNBAP: Radio Link Reconfiguration PrepareNBAP: Radio Link Reconfiguration ReadyAAL2SIG: ERQAAL2SIG: ECFRRC: Radio Bearer ReleaseRRC: Uplink Direct Transfer (MM: Detach Request)RANAP: Direct Transfer (MM: Detach Request)RANAP: Direct Transfer (MM: Detach Accept)RRC: Downlink Direct Transfer (MM: Detach Accept)UENodeBRNCSGSNRANAP: Iu Release CommandRANAP: Iu Release CompleteRRC: Radio Bearer Release CompleteRRC: RRC Connection ReleaseRRC: RRC Connection Release CompleteNBAP: Radio Link Deletion RequestNBAP: Radio Link Deletion ResponseAAL2SIG: REL (Release Request)AAL2SIG: RCL (Release Confirm)RRC: RRC Connection Release CompleteRRC: RRC Connection Release CompleteMOC PS Message Flow

User Plane: RLC Protocol is a layer 2 protocol that provides a range of transport services between an RLC entity in the UE and a peer RLC entity in the RNC. Segmentation and reassembly of higher-layer PDUs into/from smaller RLC payload units, Error correction, Protocol error detection and recovery MAC is a Layer 2 protocol and it resides between Physical Layer (L1) and RLC. The internal configuration of MAC is done by the RRC layer (L3). Mapping between logical channels and transport channels, Selection of appropriate Transport Format for each Transport channel

Control Plane: The Radio Resource Control (RRC) protocol belongs to the UMTS WCDMA protocol stack and handles the control plane signalling of Layer 3 between the UEs (User Equipment) and the UTRAN. Functions for connection establishment and release, Broadcast of system information, Outer loop power control, Radio bearer establishment/reconfiguration and release.

Iub Protocol Stack: The Iub protocol stack has three planes-The radio network control plane uses the NBAP protocol and completes tasks such as configuring a radio link at a Node B-The transport network control plane uses ALCAP and is responsible for setting up and tearing down user plane transport bearers-The user plane uses Frame Protocol and is responsible for encapsulating all data to and from the UE

Iu-CS Protocol Stack: The Iu-cs protocol stack has three planes-The radio network control plane uses the RANAP protocol and completes tasks such as configuring a RAB or assigning Iu-cs resources-The transport network control plane is responsible for setting up and tearing down Iu transport bearers-The user plane is responsible for encapsulating all data to and from the UE

Direct Transfer Messages There are three different types of direct transfer message, two in the uplink and one in the downlink. Initial Direct Transfer Message This is the message used to transfer the first signalling initiation message from the NAS. This message tells the RNC about a request for a new connection, which in turn informs the CN that a new signalling connection is being set up. The information contained in this is the NAS message itself, thedomainthe signalling connection is to be established and something known as the intradomain NAS node selector, which contains information about the core network node the message is to be routed to. All this information is utilized by the RNC to cause a successful connection to the requested domain. Uplink Direct Transfer Message After the transmission of the initial direct transfer message, any message sent by the NAS in the uplink for that domain will be sent in the uplink direct transfer message. This message just encapsulates the NAS message and contains the domain for which the message is meant. Downlink Direct Transfer Message The downlink direct transfer message contains the NAS message sent on the downlink. This message also contains the domain from which the message has originated so that the message can be routed to the correct domain in the NAS in the UE.

Transmit power of first preamble = CPICH transmit power (SIB 5)(33dBm) CPICH RSCP (UE measured) + Uplink RSSI (SIB 7) + PRACH C/I requirement (SIB 5)The CPICH Ec/Io can be extracted from the IE using:Ec/Io = -24 + IE / 2DRX cycle length = 2k framesDPCCH power offset = -X dB, (actual value = IE x 2) used for the uplink open loop power control (Initial UE Tx power = -X - CPICH RSCP)Cell Selection: Both Squal and Srxlev must be positive for the UE to camp upon the cell

Squal = Qqualmeas QqualMin (value in SIB 3)

Srxlev = Qrxlevmeas QrxlevMin Pcompensation

where, Pcompensation = Max(UE_TXPWR_MAX_RACH P_MAX, 0)

Default values:QqualMin is 20 dB CPICH Ec/IoQrxlevMin is 115 dBm CPICH RSCPUE_TXPWR_MAX_RACH is 21 dBm

When a UE is switched on, it enters RRC Idle mode and completes PLMN selection prior toselecting a cell and registering with the network. PLMN selection requires the reception of SystemInformation messages to identify the PLMN to which a specific cell belongs, i.e. the PLMN identity isbroadcast within the Master Information Block (MIB). The registration procedure requires signallingand is completed in RRC Connected mode.*