Developed By: Aumpika Viun (Ice) Contact:
[email protected]
W-RNO AnalysisMate Ver1.0 0. UTRAN Network Architecture and Protocols 1.1 UMTS Network Architecture 1.2 UTRAN Protocols
Convention Underline Text MML Command Click to return to main page
1. RRC,RB and UE Measurement Procedures
Value= Comments
1.1 Mapping of UE state to 3GPP Specifications 1.2 RRC Tasks and Functions 1.3 RRC Modes and State Transitions including GSM 1.3 RRC Mode Description
Tool Version Ver1.0
1.4 RRC Connection Mobility Management and RRC Modes 1.5 RRC Procedures 1.6 RB Procedures 1.7 UE Measurement Procedures
2. Paging Messages 2.1 Paging Message Type 1 2.2 Paging Message Type 2
3. System Information Block (SIB) 4. Location Update Procedure & L3-messages 5. Call Procedure & L3-messages 5.1 AMR Voice (MOC) 5.1 AMR Voice (MTC) 5.2 CS64/ Video Call 5.3 PS-R99 5.4 PS-HSDPA 5.5 PS-HSUPA
6. HO Procedure & L3-messages (Intra-Freq HO)
Tool Version
6.1 Intra-Frequency Soft Handover within a NodeB(Softer-HO) 6.2 Intra-Frequency Soft Handover between NodeBs in an RNC 6.3 Intra-Frequency Soft Handover between RNCs 6.4 Intra-Frequency Hard Handover Between NodeBs in an RNC 6.5 Intra-Frequency Hard Handover Between RNCs
7.HO Procedure & L3-messages (Inter-Freq HO) 7.1 Inter-Frequency Hard Handover Between NodeBs in an RNC 7.2 Inter-Frequency Hard Handover Between RNCs
8. HO Procedure & L3-messages (Inter-RAT HO) 8.1 Inter-RAT C S Handover from WCDMA to GSM (Coveraged Based) 8.2 Inter-RAT CS Handover from GSM to WCDMA(Coveraged Based) 8.3 Inter-RAT PS Handover from WCDMA to GSM(Coveraged Based) 8.4 Inter-RAT PS Handover from GSM to WCDMA(Coveraged Based) 8.5 Inter-RAT CS&PS Handover from WCDMA to GSM (Intra-SGSN) 8.6 Inter-RAT CS&PS Handover from WCDMA to GSM (Inter-SGSN)
9.SRNS Relocation Procedure & L3-messages 9.1 Static Relocation(UE not-involved relocation) 9.2 Relocation with Cell/URA Update (UE not-involved relocation) 9.3 Relocation with Hard Handover (UE involved relocation)
Convention Underline Text MML Command
lick to return to main page Value=
Description All texts with an Underline has a hyperlink function which link to other related information e.g. signalling procedure, signalling measages,parameter description, features algorithm etc. All bold texts with highlighted in "Orange" are MML command Click here to return to root topic Give an acutal value includes the conversion schemes
Comments
Extra comments for some topics
Release Date
Genex Probe Version
25-Jun-09
V100R005C01B040 (V1.51 20090210 )
Change Type
Genex Assistant Version
V100R005C01B040 (V1.52 20090210 )
Change History
RAN Version 10.0
Change Date
;
nk to other related information e.g. ion, features algorithm etc.
nd
RNC Version V200R010C01B061
Remark
Change Type Correction Addition Remove
Click to return to main page
UMTS Network Architecture (Rel'99)
The UMTS PLMN is logically divided into a Core Network (CN), a Radio Access Network (RAN) and the User Equipment UE.
The Core Network(CN) consists of an enhanced GSM Phase2+ with a Circuit Switched CS and Packet Switched PS (i.e. GPRS) do The most important network elements of these GSM Phase 2+ CN are: - Mobile Service Switching Center(MSC) - Gateway Mobile Service Switching Center (GMSC) - Visitor Location Register (VLR) - Home Location Register (HLR) - Authentication Center (AuC) - Equipment Identity Register (EIR) - Serving GPRS Support Node (SGSN) - Gateway GPRS Support Node (GGSN) The RAN of UMTS is the UMTS Terrestrial Radio Access Network (UTRAN) consists of, - Radio Network Controller (RNC), which is controlling a Radio Network Subsystem (RNS) - Node B, which is the physical entity to serve on or several cells
The User Equipment(UE) consists of, - Mobile Equipment (ME), The Mobile Equipment represents the partner of the NodeB and of the RNC. It is responsible for serving the ra encoding,Modulation and demodulation on the carrier,Power control,Quality and field strenght measurements,Ciphering and authorization
- UMTS Subscriber Identity Module (USIM), The USIM functions to save data and procedures in ther terminal equipment. It supports cal entries, etc. The installed USIM is made available to the customer by the network operator and can be updated e.g. via SMS or cell broad Examples of USIM data and procedures, 1.Data: International Mobile Subscriber Identity,Packet Switched Location Information,Security Information for authentication and chipheri period,Call meters,Display Languages,Telephone directory,Forbidden PLMNs,Emergency Call Codes etc. 2.Procedures: Application related procedures,Security related procedures,Subscription related procedures etc.
With UTRAN, four new interfaces were specified: - Iu, Iu connects UTRAN with the CN. A distinguishing is drawn between the Iu connection to the ps domain, which is labelled Iu-PS, and network solution. Please note, that there are differences in the protocol stacks on the Iu-CS and Iu-PS interfac e. - Iub, this interface is used between the Node B and its controlling RNC. - Iur, this is an inter-RNS interface, connecting two neighbouring RNC. It is used among others in soft handover situations, where a UE„s a the UE; it is called S-RNC. The remaining RNCs are called D-RNC. - Uu, Uu is the acronym for the WCDMA radio interface. On the interfaces Iu, Iur, and Iub, ATM is used for the transport of user data and higher layer signalling information.
Radio Network Controller(RNC) Functionality
The RNC has many different tasks in the UTRAN. It is responsible for e.g. Radio Resource Management (RRM) and the control of itself an and to the PS domain via Iu(PS) interface. Signalling and data transfer to other RNCs are possible via Iur interface and to the connected N The following are examples of RNC functions: - Power Control - Handover - Ciphering/Deciphering - Protocol conversion - Admission Control/Load Control - Macro Diversity - Geographical Coordinates Logically,the RNC can be divided into different types, according to its current functionality as follows, 1. Controlling RNC (C-RNC) : Every cell has only one C-RNC. The C-RNC of a cell is exactly the RNC that is connected with the NodeB - Admission Control based on UL interference and DL transmission power level - System Information Broadcasting - allocation/de-allocation of radio bearers - data transmission and reception - Congestion control in its own cell - Power control - Resource allocation and admission control for new radio links to be established in those cells
Summary: The C-RNC is the RNC controlling a Node B ( i.e. terminating the Iub interface towards the NodeB).This means the C-R 2. Serving RNC (S-RNC) : An UE that is attached to an UTRAN is served by only one RNC. This RNC is called the serving RNC (S-RNC).The existence of a serving higher layer functions related to radio access and information transport through UTRAN. The S-RNC performs the following functions: - the S-RNC handles the Iu interface towards the CN for this UE - the S-RNC handles the completed Radio Resoruce Control (RRC) for this UE - Location/Mobility handling - Ciphering - Backward Error Correction (BEC, layer 2 functionality) - Radio bearer control - Handover decision - Power Control
The S-RNC is responsible for the handling of all decisions for the connection with the UE e.g. for the allocation/modification or release of r In the case of Soft Handover,S-RNC performs data splitting toward the different NodeBs and combining toward the CN. It decides to add o the C-RNC of some NodeBs used for the connection toward an UE. The S-RNC is no anchor functionality. It can be re-allocated to anothe
Summary: The S-RNC for one UE is the RNC that terminates both Iu link for transport of user data and corresponding RANAP sig (signalling protocol between UE and UTRAN)
3. Drift RNC (D-RNC): In UMTS it is possible that one UE is connected to more than one cell, or connected to a cell, that does not belong to the S-RNC.This foreign RNC is called drift RNC ,D-RNC. In principle the D-RNC is the C-RNC of a cell the UE is connected to, but its n controlled by S-RNC.
The S-RNC is responsible for the handling of all decisions for the connection with the UE e.g. for the allocation/modification or release of r In the case of Soft Handover,S-RNC performs data splitting toward the different NodeBs and combining toward the CN. It decides to add o the C-RNC of some NodeBs used for the connection toward an UE. The S-RNC is no anchor functionality. It can be re-allocated to anothe
Summary: The S-RNC for one UE is the RNC that terminates both Iu link for transport of user data and corresponding RANAP sig (signalling protocol between UE and UTRAN)
3. Drift RNC (D-RNC): In UMTS it is possible that one UE is connected to more than one cell, or connected to a cell, that does not belong to the S-RNC.This foreign RNC is called drift RNC ,D-RNC. In principle the D-RNC is the C-RNC of a cell the UE is connected to, but its n controlled by S-RNC.
When a D-RNC is involved for a UE, then the data streams between UE-UTRAN and UE-CN always pass the S-RNC. In the downlink the The UE receives all the data streams from the cells,it is connected to and adds them together (RAKE Receiver, Maximum Ratio Combinin the S-RNC takes only the data frame with the smallest bit error rate, all other data frames will be discarded (Selective combining). The usa Because the implementation of Iur interface is optional,i's matter of network planning, whether the usage of D-RNCs is allowed or not.
Summary: D-RNC is any RNC, other than SRNC that controls cells used by the UE. The D-RNC performs macro-diversity combini ,but routes the data transparently between the Iub and Iur interfaces.The UE can be connected to 0 ,one or more DRNCs. ( Macro more UTRAN access points.
Node B Functionality
A nodeB is a physical unit for implementing a UMTS radio serviced by a Node B. Generally,up to six cells are serviced
A Node B can be used for Frequency Division Duplex (U in different timeslots) or dual mode operation. A Node B c the opposite direction. Node Bs are involved in power contr predefined one and instructs the UE to control its transmiss Error Rate (FER). The following are examples of NodeB
- Radio Channel functions: Transport to physical channe - Air Interface management. Controlling Uplink and Down Intra NodeB SofterHO,Power Control,Quality and signal str - O&M Processing,Interfacing with M2000 and RNC for al - Cellular Transmission management. Managing ATM sw of the physical transmission interfaces – E1, PDH, SDH or
Geographical and UTRAN Entity Identifiers
1.International UMTS/GSM Service Area International UMTS/GSM Service Area, i.e. the world-wide area where access to GSM and UMTS network is possible,is sub-divided into N 2.National Service Area National Service Area is the area of on country or region. It is identified by the Mobile Country Code (MCC) and Country Code (CC). The N 3. PLMN Service Area PLMN Service Area is the service area of a single PLMN. It identified by the Mobile Country Code(MCC) and Country Code (CC). The Nat 4. MSC/SGSN Service Area
1.International UMTS/GSM Service Area International UMTS/GSM Service Area, i.e. the world-wide area where access to GSM and UMTS network is possible,is sub-divided into N 2.National Service Area National Service Area is the area of on country or region. It is identified by the Mobile Country Code (MCC) and Country Code (CC). The N 3. PLMN Service Area PLMN Service Area is the service area of a single PLMN. It identified by the Mobile Country Code(MCC) and Country Code (CC). The Nat 4. MSC/SGSN Service Area An MSC or SGSN Service Area is the area, which is served by a single MSC (CS-domain) or by a single SGSN (PS-domain). MSC and SG SGSNs have their own identifiers/addresses for singalling and user data transfer. 5. Location Area (LA) A Location Area (LA) is the most precise UE location information,which is stored in the CS-domain (in the VLR) of UMTS. A Location Area 6. Routing Area (RA) The SGSN Service Area is sub-divided into one or more Routing Areas. A Routing Area (RA) is a subset of a Location Area i.e. one LA ma stored in the PS-domain (in the SGSN) of UMTS. It is world-wide uniquely identified by the Routing Area Identity. The RA is sub-divided in 7. Cell Area The Cell is the area, where the UE is located. It is the most precise information which might be stored in the PLMN (in the RNC). The cell i
It is also essential to address different physical,geographical or logical entities within UMTS. The geographical and physical enti
1. PLMN Id = MCC +MNC The PLMN-ID is used to address a PLMN in a world-wide unique manner. As in GSM the PLMN-ID consist of a MCC(mobile country code) E212. 2. CN-Domain Id: CS- and PS core network introduce their own regional area concept. This is the concept of Location Area for CS and the concept of Routin LAI= PLMN-ID + LAC (Location Area Identity Code) RAI= PLMN-ID + LAC +RAC ( Rotuing Area Identity Code) 3. Cell Global Identity (CGI) The Cell Global Identity (CGI) is composed by the CGI=LAI+CellID. 4. RNC Id: Every RNC node has to be uniquely identified within UTRAN. Therefore every RNC gets a RNC-ID. Together with the PLMN-ID the RNC-I interface. The RNC identifier is allocated by O&M. Global RNC-ID= PLMN-ID + RNC-ID 5. Cell Id and UTRAN Cell Id: The cell-ID is used to address a cell within a RNS. The cell-ID is set by O&M in the C-RNC. Together with the RNC-ID the Cell-ID forms th UTRAN Cell-ID= RNC-ID + Cell-ID 6. Local Cell Identifier The local cell identifier is used in the Node B to identify resources. There is a unique relation UTRAN Cell-ID to local cell identifier 7. Service Area Id: Serveral cells of one location area can be defined to form a service area. Such a service area is identified with a SAI(service area id): SAI= PLMN-ID+LAC+SAC 8. URA ID: The UTRAN introduces its own area concept next to LA and RA. This is the UTRAN Registration Area (URA)
UTRAN Identifiers for UE
The UE and the Subscriber can have several identifiers for the PLMN. Typically we can distinguish two types of identifiers accord
1. Core Network Identities or NAS (Non Access Stratum) Identifiers: These identifiers are allocated by the core network. In detail there 2. UTRAN identifiers : UTRAN identifiers are always temporary (Radio Network Temporary Identifiers ,RNTIs). This means they are alloc
- International Mobile Subscriber Identity (IMSI) The IMSI is the quasi-permanent subscriber identity in GSM/UMTS. The IMSI is composed by the Mobile Country Code,MCC (3 digits) + M the IMSI is less than 15 digits - Temporary Mobile Subscriber Identity (TMSI) The TMSI is used as temporary user identity instead of the IMSI to support subscriber identity confidentiality. This TMSI is allocated to an The TMSI consists of 4 bytes, which are operator-dependent. - Packet Temporary Mobile Subscriber Identity (P-TMSI) The P-TMSI is used as temporary packet user identity. It is allocated to an UE b y an SGSN and stored in the U-SIM. The P-TMSI consists - International Mobile Equipment Identity (IMEI) The IMEI is used as Mobile Equipment Identity. The IMEI can be checked at the start of a connection by the EIR. The IMEI(15 digits) cons identifiers the place of manufacture or final assemblym,the Serial Number (6 digits) and a Spare digit. - Radio Network Temporary Identifiers (RNTI) The RNTIs are temporary UE identifier within UTRAN and between UE and UTRAN. They are generated by the RNCs. Fours RNTI types
1. Serving RNC RNTI (S-RNTI) : The S-RNTI is allocated by the S-RNC,after every S-RNC Reallocation it has to be reallocation,too.The S S-RNC and by the UE to identify itself ot the S-RNC 2. UTRAN RNTI (U-RNTI): The U-RNTI is composed by the S-RNTI and the S-RNC-id. It is used as UE Id for the first cell access (at cell c associated response messages. 3. Cell RNTI (C-RNTI): The C-RNTI is allocated by the C-RNC,when the UE accesses a new cell. It is used as an in-band UE identifier in (see U-RNTI) 4. Drift RNC RNTI (D-RNTI): The D-RNTI is allocated by the D-RNC. It is used by the S-RNC to identify the UE to the D-RNC. It is never u
UTRAN Protocols
The communication between the different d between UE and UTRAN and transport of s signalling between UE,UTRAN and CN as
1. Access Stratum(AS) : The Access Stra messages occur between UE and UTRAN UTRAN and UTRAN-CN is ,that the UTRAN enables the CN to support several different
2. Transport Stratum: The Transport Stra and user data. Because UTRAN has the ta messages between UE and UTRAN and be
3. Non-Access Stratum (NAS) : The Nonaccess or transport tasks.This cover pure a ,handling of subscription data and subscrib
UTRAN Protocol Architecture
The UMTS network is split into the CN,UTRAN and the UE (radio access bearer services) and control information (incl between the CN and the UEs using the Radio protocols an
The higher layer protocols of the Non-Access Stratum(NAS Session Manangement (SM) tasks. The NAS procedures (o procedures. The radio and Iu protocols contain mechanism used in the Iu and radio protocols for these these transpare
UTRAN Interface Protocol Structure Horizontal Layer
The protocol structures of the UTRAN interfaces are design planes as logically independent of each other. The modula parts remain intact.
The transport system used within UTRAN is ATM. There is different types of bearer service labelled AAL type 1,AAL ty type2 can be set up with explicit signalling. This means bef switches. This behavior results in a new protocol model, wh
Horizontal Layer: The general protocol model consists of two main horizonta are visible in the Radio Network Layer only.The Transport N specific requirements. - Transport Network Layer : The Transport Network Laye layer and its transport frame layer,also the bearer service p - Radio Network Layer : The Radio Network Layer contain streams, to be transported through UTRAN, belong to this
Vertical Layer
Vertical Plane: There is also a vertical structure, the elements of this vertic next to eachother. The general protocol model consists of t Plane. -User Plane: The user plane supports the data streams for protocols will be transmitted via data bearers. In contrast to explicit signalling.
streams, to be transported through UTRAN, belong to this
Vertical Plane: There is also a vertical structure, the elements of this vertic next to eachother. The general protocol model consists of t Plane. -User Plane: The user plane supports the data streams for protocols will be transmitted via data bearers. In contrast to explicit signalling. -Control Plane: The control plane consists of all applicatio application protocol,one or several signaling bearers,provid signaling,which is UMTS-specific. It includes the Applicatio Application Protocol messages. -Transport Network Control Plane: The transport network protocols are used to set up and release the data bearers o not necessary to use the ALCAP for all data bearers. Expe are used. The Transport Network Control Plane is used for information.
The Transport Network Control Plane acts as plane betwee to be total independent of the technology selected for data
UTRAN Interface Protocol Overview
The protocols can be divided into the following part according to the functions:
1. User Plane : User Plane protocol stacks for transport of the user information on the different interfaces. - Iu Interface : IuCS for Voice and Data and IuPS for Data - Iub Interface: Frame Protocols (DCH and CCH) - Radio Interface Uu: User Data Streams and Application 2. Control Plane : Control can be subdivided into: -Control Plane for interface signaling (used for NE configuration) -Control Plane for radio signaling 3. Transport Plane : Between user plance and control plane exist the transport plane. The task of transport plane is the setup of a data b
UMTS Protocol Stacks -> UE-UTRAN-CN for CS domain
Control Plane - CS
The CS control plane is used for the exchange of control information which are related to CS services. In addition ,the CS control plane i contains of following important protocol layer as follows; -Physical Layer (PHY) : The physical layer (Layer1) on the air interface provides access to the WCDMA radio interface. Therefore it perfo -Medium Access Control (MAC) : The MAC protocol belongs to Layer 2. The tasks of MAC are the control of random access and the mu -Radio Link Control (RLC) : As MAC also the RLC protocol is a Layer 2 protocol. RLC provides three reliabilty modes for every radio bea -Radio Resource Control (RRC) : The RRC protocol is the first protocol of Layer 3. The RRC protocol performs all higher layer tasks rela -NAS Protocols : On top of RRC there are the control protocols for the non-access stratum (NAS). For the CS service these are: MM (Mo Message Service), if it is not provided by the Packet Switched Protocol Stack. -Radio Access Network Application Part (RANAP) : RANAP is between UTRAN and CN. It performs all tasks related to transport stratu counterpart to RRC -Signaling Connection Control Part (SCCP): The SCCP has mainlu transport tasks. It is used to establish a singling connection for a UE identifier. -MTP 3B,SAAL,AAL5, ATM : These protocols belong to transport network (ATM). They provide a signaling bearer to transport SCCP and User Plane- CS
UMTS transports the control signaling and the user data over the same transport network. So,there are some protocols supporting the use protocols involved into the user data transport, -PHY,MAC,RLC : The air interface transport system is built out of PHY,MAC and RLC as for the control plane. The same basic stack is us -User data stream : The user data streams are generated by the applications using the CS core network services (switched channels). Th -ATM : The transport system for the Iu interface between UTRAN and CN is ATM -AAL 2 : To provide a circuit switched like transport bearer on Iu, The AAL 2 protocol is used. This adaptation layer provides a bearer chan includes time stamps in the transport frames. This allows synchronization and timing control between sender and receiver. -Iu User Plane protocol (Iu UP) : The Iu user Plane protocl is on top of AAL2. This protocal can provide different stages of user data stre
Please note that AAL 5 is used for all control functions on the Iu-CS interface ( <> RANAP) and the Iub interface (<>NBAP). On th
UMTS transports the control signaling and the user data over the same transport network. So,there are some protocols supporting the use protocols involved into the user data transport, -PHY,MAC,RLC : The air interface transport system is built out of PHY,MAC and RLC as for the control plane. The same basic stack is us -User data stream : The user data streams are generated by the applications using the CS core network services (switched channels). Th -ATM : The transport system for the Iu interface between UTRAN and CN is ATM -AAL 2 : To provide a circuit switched like transport bearer on Iu, The AAL 2 protocol is used. This adaptation layer provides a bearer chan includes time stamps in the transport frames. This allows synchronization and timing control between sender and receiver. -Iu User Plane protocol (Iu UP) : The Iu user Plane protocl is on top of AAL2. This protocal can provide different stages of user data stre
Please note that AAL 5 is used for all control functions on the Iu-CS interface ( <> RANAP) and the Iub interface (<>NBAP). On th messages (<> Iub-FP) between NodeB and RNC and for user data on Iu-CS interface between RNC and MSC.
UMTS Protocol Stacks -> UE-UTRAN-CN for PS domain Control Plane - PS
For Packet Switched (PS) service,there are different procedures. So there is a need for special proctocols for PS services. In fact these s services. The Packet Switched control plane consists of: - PHY,MAC,RLC,RRC : The transport and access stratum protocols on the air interface are the same for PS and CS. UMTS has been des - ATM,AAL 5, SAAL,MTP 3B : Also the transport and access stratum on the Iu-PS interface is similar to the Iu interface towards the MSC - SCCP,RANAP : SCCP and RANAP are the same as for CS. The SCCP is mainlu used to setup a signaling conenction to the SGSN in th - NAS protocols : The only special protocols for the packet switched service are the non-access stratum protocols. Because there are es network has its own mobility managment GMM ( GPRS Mobility Management). To set up a data session the SM (Session Management) p
In contrast to the control planes, that look very similar for PS and CS, the user plane has important differences. The Packet Switched User Plane consists of: - User data : The user data for PS services is usually dedicated to external packet data networks (e.g. internet). These external data netw network have their own special network protocols (e.g .TCP/IP). When a UMTS user wants want to be connected with such an external ne network this only data. But because of its special role, the network protocol of the external network is called Packet Data Protocol (PDP). transport of the PDP packets. -Packet Data Convergence Protocol (PDCP) : This protocol performs header compression of the PDP packet header. This shall increas -RLC,MAC,PHY : The transport layers are the same as for control plane -GPRS Tunneling Protocol User Plane (GTP-U): The PDP packets are transported in a GTP-U frame on Iu. GTP-U organizes addressin -UDP/IP : To route from RNC to SGSN the standard UDP/IP protocol stack is used. This is a connection less unreliable transport service. -AAL5 /ATM : The UDP/IP datagrams (packets) are transmitted on ATM using the adaptaiton layer 5.
UTRAN Interface Protocol -Uu (UE-UTRAN)
Uu interface is the interface between Us important interface in the UMTS system
The radio interface (Uu) is layered into t -the physical layer (L1) -the data link layer (L2) -the network layer (L3).
The layer 1 supports all functions required consisting in indicating to higher layers, for … It is basically composed of a “layer 1 ma “physical channel” entity.
The layer 2 protocol is responsible for pro sublayers: MAC (Medium Access Control), Control).
The layer 3 is split into 2 parts: the access Resource Control)” entity and “duplication a L3 are implemented by RNC, and the MM
The protocol layers are located in the UE
Physical Layer (L1) Functions Transport Channel Processing for FDD Uplink
Transport Format Combinations
L1 Functions The functions of L1 (physical layer) mainly includes:
A) Transport Channel Processing: The processing of the transport channels that come from the MAC layer has the following steps,that 1. CRC attachement (error detection) : Every transport block of a transport block set get its own CRC,used for error detection 2. Transport Block concatenation & code block segmentation : The transport blocks are concatenated after the CRC is appended. if t afterwards 3. Channel Coding : Channel coding can enhance symbol correlation to recover signals in the case of interference.UTRAN FDD and TDD are : no coding,Convolutional coder 1:2,Convolutionalcoder 1:3,Turbo coder 1:3. 4. Rate matching (pucturing) : The physical layer can perform a puncturing of bits to reduce the data rate. the physical layer gets matchi 5. Radio Frame Equalization : If the data block after rate matching is too short for one radio frame,some padding bits are appended 6. Interleaving : Interleaving is used to damage symbol correlation and reduce the impact caused by fast fading and interference of the ch 7. TrCH Multiplexing : This function multiplexes several transport channels to one CCTrCH (Code Composite Transport Channels) 8. Physical Channel Segmentation : The CCTrCH are split to several physical channels,it there are any 9. DTX bit insertion : If no information is to be transmitted by the network, so called DTX (Discontinuous transmission) bits are inserted. T 10. Radio Frame segmentation : When a data block is too long for one radio frame(10ms), it is segmented to several radio frames 11. Physial Channel Mapping : The data has to be mapped to the slot format of a physical channel or to several physical channels if nec Transport Format Combinations
4. Rate matching (pucturing) : The physical layer can perform a puncturing of bits to reduce the data rate. the physical layer gets matchi 5. Radio Frame Equalization : If the data block after rate matching is too short for one radio frame,some padding bits are appended 6. Interleaving : Interleaving is used to damage symbol correlation and reduce the impact caused by fast fading and interference of the ch 7. TrCH Multiplexing : This function multiplexes several transport channels to one CCTrCH (Code Composite Transport Channels) 8. Physical Channel Segmentation : The CCTrCH are split to several physical channels,it there are any 9. DTX bit insertion : If no information is to be transmitted by the network, so called DTX (Discontinuous transmission) bits are inserted. T 10. Radio Frame segmentation : When a data block is too long for one radio frame(10ms), it is segmented to several radio frames 11. Physial Channel Mapping : The data has to be mapped to the slot format of a physical channel or to several physical channels if nec
Transport Format Combinations When multiple transport channels are multiplexed to CCTrCH (Coded Composite Transport Channel) and transmitted in physical chann channel. Therefore the so called "Transport Format Combination Identifier (TFCI)" is used. In UE and NodeB the value of the TFCI can - the number of transport channels - the transport format for every transport block of every transport channel in the combination This allows the de-multiplexing of CCTrCHs. the TFCI values and the assignment of transport format combination is signaled by RRC duri The definition of TFCIs runs in the following way. 1. During radio bearer setup or reconfiguration the transport channels to be multiplexed are defined 2. Now each transport channel has its transport format set. One transport format from each transport channel's transport format set build a care,taking UE radio capabilities into account. 3. Several transport format combinations from a so called "transport format combination set" .Every transport format combination in the combination identifier TFCI. B) Radio Tasks: 1. Provision for higher layers with measurements and indications (such as FER, SIR, interference power, and transmission power) 2. Macro-diversity distribution/combination and soft handover execution 3. Frequency and time (chip, bit, slot, frame) synchronization 4. Closed-loop power control 5. Power weighting and multiplexing of physical channels 6. Modulation,spreading,scrambling 7. Scrambling and modualtion
Physical Layer Procedures The physical layer defines several procedures to control the radio interface on the lowest level. Most of these procedures are triggered an the following categories: 1. Synchonization procedures : These types of procedures are used for cell search,radio frame/slot and chip synchronization to physica the UE to the cell timing. 2. Power Control Procedures : One of the most critical issues for CDMA systems is the near-far problem. The solution for this is a very f 3. Random Access Procedures : Like all known mobile radio access technologies also WCDMA has to use random access mechanism shared resources between several UEs an access mechanism with collision risk is used. 4. Radio Measurment : For the mobility handling within the radio network the UE and the Node B have to perform measurements of radio ratio,interference power,signal power). These measurment are used as criteria for the cell reselection or handover procedures. For the me frames. In such radio frames some slots are not used for transmission/reception,rather the measuement are then performed. L2 Functions L2 includes four sublayers, Medium Access Control (MAC), Radio Link Control (RLC), Broadcast/Multicast Control (BMC) and Packet Data Convergence Protocol (PDCP). I. MAC, The functions of MAC include: 1.Mapping between logical channels and transport channels 2.Selection of appropriate transport format for each transport channel 3.Priority handling between data flows of one UE 4.Priority handling between UEs by means of dynamic scheduling 5.Priority handling between data flows of several UEs on FACH 6.Identification of UEs on common transport channels 7.Multiplexing/demultiplexing of upper layer PDUs into/from transport blocks delivered to/from the physical layer on common transport channels 8. Switching of the transport channel type for a radio berarer(controlled by RRC),means several transport channel types can be assigned to one radio bearer 9.Traffic volume measurement 10.Ciphering/de-chipering for transparent mode RLC 11. Control of random access and CPCH access (e.g. priority classes)
9.Traffic volume measurement 10.Ciphering/de-chipering for transparent mode RLC 11. Control of random access and CPCH access (e.g. priority classes)
L3 Functions The RRC performs the functions listed below: 1.Broadcast of information related to the non-access stratum (NAS:Core Network) 2.Broadcast of information related to the access stratum (AS) 3.Establishment, maintenance and release of an RRC connection between the UE and UTRAN 4.Establishment, reconfiguration and release of Radio Bearers 5.Assignment, reconfiguration and release of radio resources for the RRC connection 6.RRC connection mobility functions 7.Route selection for the Protocol Data Unit (PDU) of upper layers 6.Control of requested QoS 7.UE measurement reporting and control of the reporting 8.Outer loop power control 9. Security Control 10. Paging 11. Initial cell selection and cell re-selection 12. Arbitration of radio resources on uplink DCH 13. RRC message integrity protection 14. CBS control
UTRAN Interface Protocol - Iub ( RNC-NodeB)
The control plane of the Iub interface contains the follo
-NBAP (NodeB Application Part) : The NBAP protocol is (e.g. code allocation,transceiver configuration). -SAAL,AAL 5, ATM : These protocols constitute the signal
The user plane of the Iub interface has to transfer the d way as on the Iur interface. The user plane consists of:
-Frame Protocols : The Frame Protocols encapsulate the -AAL 2 ,ATM : The frame protocol,that encapsulate the UE first -AAL type 2 signaling protocol : The AAL type 2 SP prov -STC, SAAL,AAL 5,ATM : The STC (Signaling Transport C
The physical layer is not standardized. it is up to the op
UTRAN Interface Protocol - Iur ( RNC-RNC)
The control plane of the Iur interface contains the follo
-RNSAP (Radio Network Subsystem Application Part) : covers resource allocation for a UE in a cell of the D-RNC, (SRNS relocation) - SCCP (Signaling Connection Control Part) : The SCCP the S-RNC sets up one SCCP signaling connection for eve signaling messages -MTP 3B,SAAL,AAL5,ATM : These protocols form the sig
The user plane of the Iur interface has the tasks to tran protocols
-Frame Protocols : The data to and from the UE will be en protocols allow traffic management with in-band signaling -AAL 2 ,ATM : The frame protocol packets are transmitted -AAL type 2 signaling protocol : The AAL type 2 SP prov -STC,MTP3B, SAAL,AAL 5,ATM : These protocols provide Converter) provides functionality for congestion handling a signaling bearer of RNSAP of Control Plane
UTRAN Interface Protocol - Iu ( UTRAN-CN)
The following protocol model is applied to the UTRAN inter PS-core network domain. Iu-CS Protocol Stack
1. Iu-CS protocol stack The control plane for Iu-CS is formed out of the following -RANAP ( Radio Access Network Application Part) : The protocol of the Iu-CS interface -SCCP (Signaling Connection Control Part) : The SCCP connection UTRAN-MSC for every IE using CS service. -MTP 3B,SAAL,AAL5,ATM : Theses protocols provide the
The user plane on Iu-CS has to support the transfer of re -Iu UP (User Plane) protocol : The Iu UP protocol is used control,data rate control,backward error conrrection. -AAL2,ATM : For the data bearer to transport the data stre
The transport network control plane is necessary ,becau network control plane consisting of: - AAL type 2 signaling protocol : used to setup ,modify a - STC,MTP 3B,SAAL,AAL5,ATM : These protocols provid
Iu-PS Protocol Stack
2. Iu-PS protocol stack The Iu-PS interface is the interface between RNC and SGS Iu-PS control plane -RANAP : The application protocol for Iu-CS and Iu-PS -SCCP : Provides signaling connection on Iu-PS. There wil service. SCCP connections on Iu-PS and Iu-CS do not affe -MTP 3B,SAAL,AAL5,ATM : The signaling bearer for SCC
The user plane on Iu-PS is competely different to the user necessary. The UTRAN provides the following protocols on -Iu UP protocol : As for Iu-CS the Iu UP protocol can prov -GTP-U (GPRS Tunneling Protocol-User Plane): GTP-U the PDP context and sequence numbers for the data are co -UDP/IP : The UDP/IP protocol suite is used as network lay vice versa. -AAL 5,ATM : The ATM adaptation layer of type 5 is used a The AAL 5 virtual channels do not need to be set up in a dy for the packet transfer. Therefore on Iu-PS there is no nee
UMTS Protocol Stacks -> Application Part
UMTS system has different application parts depending on interface being used and each application part controls signaling information fo signaling format, consisting each message of mandatory fixed part,variable fixed part and optional part. Between nodes, there are three application parts (NBAP,RANAP and RNSAP) to convert and transmit signaling for the control plane and
1. RANAP (Radio Access Network Applciation Part) : This application part is the Iu interface signaling protocol that contains all the con implemented by various Elementatry Procedures (EP). Each RANAP function requires the execution of one or more EP. The following RANAP functions are defined: -Relocation & Handover Control : Handles the relocation of RNC for soft handover and hard handover -RAB Management: Handles the RAB setup,modification characteristic of an existing RAB and clearing a connected RAB -Iu Release Control : Connected signaling link and the U-Plane resources will be released. -Paging : Sends paging messages from CN to an idle UE -UE-CN signaling Transfer : Provides transparent transfer of UE-CN signaling messages that are not interpreted by UTRAN, such as bro -Security Mode Control : Sets the ciphering on or off by encrypting signaling and user data connection in the radio interface
2. NBAP (NodeB Application Part): This application part is the Iub interface signaling protocol. It is divided into two procedures : -Common NBAP : Defines the signaling sequence across the common signaling link. Common NBAP defines all the procedures for the lo management -Dedicated NBAP : Sequence related to a specific UE signaling in the NodeB. Upon radio link setup procedure,the NodeB assigns a traff this mobile is exchanged by Dedicated NBAP function by the dedicated control channel. The following NBAP functions are defined: 1.Cell Configuration Management ,this function gives the controlling RNC (CRNC) the possibility to manage the cell configuration inform 2.Common Transport Channel Management,this function gives the CRNC the possibility to manage the configuration of common transp 3.System Information Management, this function gives the CRNC the ability to manage the scheduling of System Information to be broa 4.Resource Event Management, this function gives the NodeB the ability to inform the CRNC about the status of NodeB resources.
2. NBAP (NodeB Application Part): This application part is the Iub interface signaling protocol. It is divided into two procedures : -Common NBAP : Defines the signaling sequence across the common signaling link. Common NBAP defines all the procedures for the lo management -Dedicated NBAP : Sequence related to a specific UE signaling in the NodeB. Upon radio link setup procedure,the NodeB assigns a traff this mobile is exchanged by Dedicated NBAP function by the dedicated control channel. The following NBAP functions are defined: 1.Cell Configuration Management ,this function gives the controlling RNC (CRNC) the possibility to manage the cell configuration inform 2.Common Transport Channel Management,this function gives the CRNC the possibility to manage the configuration of common transp 3.System Information Management, this function gives the CRNC the ability to manage the scheduling of System Information to be broa 4.Resource Event Management, this function gives the NodeB the ability to inform the CRNC about the status of NodeB resources. 5.Configuration Alignment ,this function gives the CRNC and the NodeB the possibility to verify and enforce that both nodes have the sa 6.Measurements on Common Resources,this function allows the NodeB to initiate measurements in the NodeB. The function also allow 7.Radio Link Management, this function allows the CRNC to manage radio links using dedicated resources in a NodeB. 8.Radio Link Supervision ,this function allows the CRNC to report failures and restorations of a radio link. 9.Compressed Mode Control,this function allows the CRNC to control the usage of compressed mode in a NodeB. 10.Measurements on Dedicated Resources,this function allows the CRNC to initiate measurements in the NodeB. The function also allo 11.DL Power Drifting Correction, this function allows the CRNC to adjust the DL power level of one or more radio links in order to avoid 12.Reporting of General Error Situations, this function allows reporting of general error situations.
3. RNSAP (Radio Network Subsystem Application Part) : This application part is the Iur interface signaling protocol that controls signal handover. The RNSAP protocol has the following functions: -Radio Link Management : Allows the SRNC to manage radio links using dedicated resoruces in a DRNC. -Physical Channel Reconfiguration : DRNC reallocates the physical channel resources for a radio link -Radio Link Supervision: Allows DRNC to report failures and restoration of a radio link -DL Power Drifting Correction : Allows SRNC to adjust the DL power level of one or more radio links in order to avoid DL power drifting b -CCCH Signaling Transfer : Allows the SRNC and DRNC to pass information between UE and SRNC on a CCCH controlled by the DRN -Paging : Allows the SRNC to page a UE in a URA -Relocation Execution: Allows the SRNC to finalize a relocation previously prepared via other interfaces.
4. ALCAP (Access Link Control Application Part) : This application part is the signaling protocol that provides the signaling capability to words, ALCAP setup transport bearer such as AAL2 path between different nodes interfaces (Iu,Iur,Iub) in the UTRAN. The transport bear Control Plane (NBAP,RANAP,RNSAP). And then,data bearer is setup by the ALCAP protocol.The use of the ALCAP is dependent on the there is no dynamical setup and release for signaling bearers.
Data bearers have to be setup and released with ALCAP, when they are not pre-configured. In this case the setup runs in the following ma The setup or release of a bearer is always controlled by an application protocol. But to avoid the restriction to a single transport system, th the application protocol can control the bearer via abstract parameters (QOS parameters) only. This principle is the same as for BICC (Be protocol starts a procedure to the destination node.
After the application protocol triggered the procedure,the ALCAP, that is specific to the bearer to be setup ,performs all necessary procedu successful bearer setup, the application protocol procedure can be finished, and the application can be informed to start the data stream t
N) and the User Equipment UE.
and Packet Switched PS (i.e. GPRS) domain
e RNC. It is responsible for serving the radio interface. Some of the tasks of the Mobile Equipment ares CDMA coding and easurements,Ciphering and authorization,Mobility management and equipment identification.
n ther terminal equipment. It supports call handling,contains security parameters,user-specific data e.g. telephone directory an be updated e.g. via SMS or cell broadcasting.
ormation for authentication and chiphering for circuit and packet switched applications,PLMN selector and HPLMN search odes etc. rocedures etc.
ps domain, which is labelled Iu-PS, and to the cs domain, which is called Iu-CS. In both cases, ATM is used as transmission u-PS interfac e. soft handover situations, where a UE„s active cells are under the control of more than one RNC. One RNC is responsible for
er signalling information.
gement (RRM) and the control of itself and the connected NodeB (O&M functionality). It is connected to the CN , CS domain via Iu(CS) interface e via Iur interface and to the connected Node Bs via Iub interface.
as follows, e RNC that is connected with the NodeB serving the cell. The tasks of the C-RNC covers the following areas:
wards the NodeB).This means the C-RNC of a cell is responsible for all lower layer funcions related to the radio technology
RNC (S-RNC).The existence of a serving RNC does not imply that the UE is camped on a cell belonging to the S-RNC.The serving RNC handles all NC performs the following functions:
he allocation/modification or release of radio resources,for Outer Loop Power Control and for Handover decisions/initiation. bining toward the CN. It decides to add or remove cells in the Soft Handover. The S-RNC is in most cases (but not always) tionality. It can be re-allocated to another RNC with the S-RNS reallocation procedure.
er data and corresponding RANAP signalling to/from the core network per UE. The S-RNC terminates the RRC signalling
connected to a cell, that does not belong to the S-RNC. This means the UE is connected with a cell controlled by a RNC different of a cell the UE is connected to, but its not the S-RNC.Therefore D-RNC performs the C-RNC functions for the cells not
he allocation/modification or release of radio resources,for Outer Loop Power Control and for Handover decisions/initiation. bining toward the CN. It decides to add or remove cells in the Soft Handover. The S-RNC is in most cases (but not always) tionality. It can be re-allocated to another RNC with the S-RNS reallocation procedure.
er data and corresponding RANAP signalling to/from the core network per UE. The S-RNC terminates the RRC signalling
connected to a cell, that does not belong to the S-RNC. This means the UE is connected with a cell controlled by a RNC different of a cell the UE is connected to, but its not the S-RNC.Therefore D-RNC performs the C-RNC functions for the cells not
ays pass the S-RNC. In the downlink the S-RNC sends the data to own cells and to the D-RNC(soft HO),this is called splitting. AKE Receiver, Maximum Ratio Combining). In the Uplink,the S-RNC receives data from the own cells and from the D-RNC , discarded (Selective combining). The usage of a D-RNC requires a Iur interface between D-RNC and S-RNC. usage of D-RNCs is allowed or not.
NC performs macro-diversity combining and splitting,if necessary. The D-RNC does not perform user plane data L2 processing cted to 0 ,one or more DRNCs. ( Macro Diversity is an operation state in which a UE simultaneously has radio links with two or
ical unit for implementing a UMTS radio transmission. Depending on the sectoring of the cells ,one (omni) cell or multiple (sector) cells can be e B. Generally,up to six cells are serviced by a Node B in UMTS.
used for Frequency Division Duplex (Uplink and Downlink separated by different frequency bands),Time division Duplex (Uplink and Downlink ts) or dual mode operation. A Node B converts user and signalling information received from the RNC for transport via the radio interface,and in ion. Node Bs are involved in power control,NodeB measures the signal to noise ratio (SIR) of the User Equipment ,compares the value with a d instructs the UE to control its transmission power. The NodeB also measures the quality and strength of the links and determines the Frame The following are examples of NodeB functions:
unctions: Transport to physical channel mappings. Encoding/Decoding – Spreading/De-spreading user traffic and signalling. nagement. Controlling Uplink and Downlink radio paths on the Uu Air Interface,Baseband to RF conversion,Antenna multi-coupling, rHO,Power Control,Quality and signal strength measurements g,Interfacing with M2000 and RNC for alarm and control (Operations and Maintenance) functions. ission management. Managing ATM switching and multiplexing over the Iub interface. Control of AAL2/AAL5 connections. Control nsmission interfaces – E1, PDH, SDH or microwave.
network is possible,is sub-divided into National Service Areas.
de (MCC) and Country Code (CC). The National Service Area is sub-divided into one or more PLMN Service Areas.
(MCC) and Country Code (CC). The National Service Area is sub-divided into one or more MSC and SGSN Service Areas.
network is possible,is sub-divided into National Service Areas.
de (MCC) and Country Code (CC). The National Service Area is sub-divided into one or more PLMN Service Areas.
(MCC) and Country Code (CC). The National Service Area is sub-divided into one or more MSC and SGSN Service Areas. single SGSN (PS-domain). MSC and SGSN Service Area may differ, but they are on the same hierachical level. The MSCs and
n (in the VLR) of UMTS. A Location Area is world-wide uniquely identified by its Location Area Identity LAI
subset of a Location Area i.e. one LA may contain one or more RAs. The RA is the most precise UE information, which is g Area Identity. The RA is sub-divided into the Cell-Areas.
ored in the PLMN (in the RNC). The cell is world-wide uniquely identified by the Cell Global Identity (CGI)
S. The geographical and physical entities of UTRAN are described as follow,
D consist of a MCC(mobile country code) and a MNC(mobile network code). MCC and MNC are allocated by ITU-T and are specified within ITU-T
on Area for CS and the concept of Routing Area for PS.
D. Together with the PLMN-ID the RNC-ID is unique world wide. The RNC-ID will be used to address a RNC via Iu,Iur and Iub
her with the RNC-ID the Cell-ID forms the UTRAN cell ID
RAN Cell-ID to local cell identifier
dentified with a SAI(service area id):
Area (URA)
inguish two types of identifiers according to the point of generation of the identifier:
ocated by the core network. In detail there are IMSI,TMSI and P-TMSI (and IMEI) ifiers ,RNTIs). This means they are allocated to the UE for the time of the need. After the last procedure the identifiers are released.
Mobile Country Code,MCC (3 digits) + Mobile Network Code,MNC (2-3 digits)+Mobile Subscriber Identification Number,MSIN. The total length of
fidentiality. This TMSI is allocated to an UE by VLR and stored in the U-SIM. It has only local significance i.e. within the area controlled by a VLR.
stored in the U-SIM. The P-TMSI consists of 3 bytes,which are operator-dependent.
tion by the EIR. The IMEI(15 digits) consists of a Type Approval Code TAC (6 digits),the Final Assembly Code FAC(2 digits)which digit.
nerated by the RNCs. Fours RNTI types exists:
ocation it has to be reallocation,too.The S-RNTI is used by the S-RNC to address the UE, by the D-RNC to identify the UE to the
as UE Id for the first cell access (at cell change) at existing RRC connection and for UTRAN originating Paging including It is used as an in-band UE identifier in all DCCH/DTCH common channel messages on Uu despite the first access
dentify the UE to the D-RNC. It is never used on Uu.
e communication between the different domains can be divided according to their functions. The UTRAN has the functions to provide access links tween UE and UTRAN and transport of signalling messages and user data between UE and CN. Therefore we can distiguish three types of gnalling between UE,UTRAN and CN as follows,
Access Stratum(AS) : The Access Stratum covers all signalling exchange used to control the access of an UE to the network. Access Stratum essages occur between UE and UTRAN and between UTRAN and CN. The difference between the access stratum UETRAN and UTRAN-CN is ,that the UTRAN-CN access stratum shall be independent of the radio technology used in UTRAN. This ables the CN to support several different radio access technologies.
Transport Stratum: The Transport Stratum protocols and messages have the task to transport higher layer PDUs (Protocol Data Unit) d user data. Because UTRAN has the task to transparently transport data between UE and CN,there will be transport stratum essages between UE and UTRAN and between UTRAN and CN.
Non-Access Stratum (NAS) : The Non-Access-Stratum covers all messages of higher layers and user data, that do not deal with cess or transport tasks.This cover pure application control (application stratum), service request and control (serving stratum) andling of subscription data and subscriber specific services (home stratum).
k is split into the CN,UTRAN and the UE. CN and UTRAN are connected via Iu interface,UTRAN and the UE via Uu(radio) interface. User data er services) and control information (including requesting the service,controlling different transmission resources,handover etc) are exchanged nd the UEs using the Radio protocols and the Iu protocols of the Access Stratum (AS).
rotocols of the Non-Access Stratum(NAS) handle control aspects e.g. (GPRS)Mobility Management (G)MM,Connection Management (CM) or ment (SM) tasks. The NAS procedures (of Rel. '99) are in most cases unchanged compared to the GSM Phase 2+ adio and Iu protocols contain mechanism for transparent NAS message transfer. So-called Direct Transfer (DT) procedures are radio protocols for these these transparent NAS message transfer.
tures of the UTRAN interfaces are designed in horizontal layers and vertical planes. The general protocol model describes these layers and independent of each other. The modularity of this model allows changing parts of the protocol structure in the future,if neccessary,while other .
em used within UTRAN is ATM. There is difference between the usage of ATM and the use PCM lines in a GSM-BSS. ATM supports earer service labelled AAL type 1,AAL type 2, AAL type 3/4 and AAL type 5. In UTRAN only AAL type 2 and AAL Type 5 are used. Bearers of AAL p with explicit signalling. This means before a AAL type 2 virtual channel can be used,there might be signalling between the corresponding ATM avior results in a new protocol model, where protocols for user bearer set up and release occur.
col model consists of two main horizontal layers- the Radio Network Layer and Transport Network Layer. All UTRAN related issues adio Network Layer only.The Transport Network Layer is used for UTRAN,offering transport technologies.It is without any UTRAN nts. ork Layer : The Transport Network Layer consists of all protocols used for the transport network solution. This includes the physical port frame layer,also the bearer service protocols are included. Layer : The Radio Network Layer contains all protocols,that are specific to the radio access and transport stratum. Also all other data nsported through UTRAN, belong to this layer.
tical structure, the elements of this vertical structure are planes. A plane principle is protocol stack,more than one plane can coexist The general protocol model consists of three vertical planes- the Control Plane,the User Plane and the Transport Network Control
user plane supports the data streams for user data. Therefore the data streams are packed into frame protocols. These frame ansmitted via data bearers. In contrast to the signalling bearers of the control plane,the data bearer can require to be set up with
nsported through UTRAN, belong to this layer.
tical structure, the elements of this vertical structure are planes. A plane principle is protocol stack,more than one plane can coexist The general protocol model consists of three vertical planes- the Control Plane,the User Plane and the Transport Network Control
user plane supports the data streams for user data. Therefore the data streams are packed into frame protocols. These frame ansmitted via data bearers. In contrast to the signalling bearers of the control plane,the data bearer can require to be set up with
he control plane consists of all application protocols that are used for radio network controlling. To transport the messages of an ol,one or several signaling bearers,provided by the transport network are neccesary. The Control Plane is used for all control UMTS-specific. It includes the Application Protocols (i.e. RANAP,RNSAP and NBAP) and the signaling bearer for transport the ol messages. ork Control Plane: The transport network control plane contains the ALCAP (Access Link Control Application Part). The ALCAP to set up and release the data bearers of the user plane. Also ALCAP messages require a signaling bearer for transmission. It is se the ALCAP for all data bearers. Expecially the transport network control plane is not necessary when pre-configured bearers only nsport Network Control Plane is used for all control signaling within the Transport Layer. It contains no Radio Network Layer
work Control Plane acts as plane between the Control Plane and User Plane, it enables the Application Protocol in the Control Plane dent of the technology selected for data bearer in the User Plane.
Control Plane
terfaces.
f transport plane is the setup of a data bearer for the user plane
rvices. In addition ,the CS control plane is used for controlling supplementary services and it can be used for the exchange of short messages. It
WCDMA radio interface. Therefore it performs spreading,scrambling.modulation,channel conding,rate matching etc. he control of random access and the multiplexing/de-multiplexing of different UEs onto shared radio resources. hree reliabilty modes for every radio bearer. These modes are : Acknowledge (AM),Unacknowledge(UM) and Transparent (TM). otocol performs all higher layer tasks related to the access stratum on the air interface (e.g. radio bearer setup) ). For the CS service these are: MM (Mobility Management),CC (Call Control),SS(Supplementary Services) and SMS (Short
forms all tasks related to transport stratum for control signaling and access stratum between UTRAN and CN. It is the
o establish a singling connection for a UE. So the UE can then be identified by the signaling connection and not by an explicit signaling bearer to transport SCCP and RANAP.
re are some protocols supporting the user data transfer. In the lowest layers there are the same protocols as for the control plane. The following
ontrol plane. The same basic stack is used for the user plane. network services (switched channels). These data streams are directly input to the RLC
s adaptation layer provides a bearer channel (virtual channel of AAL type 2) with certain QOS gurantees. Additonally the AAL 2 cirtual channel een sender and receiver. provide different stages of user data stream support.
and the Iub interface (<>NBAP). On the other hand, the real time AAL 2 is used for relaying UE- data and UE-signaling
re are some protocols supporting the user data transfer. In the lowest layers there are the same protocols as for the control plane. The following
ontrol plane. The same basic stack is used for the user plane. network services (switched channels). These data streams are directly input to the RLC
s adaptation layer provides a bearer channel (virtual channel of AAL type 2) with certain QOS gurantees. Additonally the AAL 2 cirtual channel een sender and receiver. provide different stages of user data stream support.
and the Iub interface (<>NBAP). On the other hand, the real time AAL 2 is used for relaying UE- data and UE-signaling een RNC and MSC.
User Plane -PS
roctocols for PS services. In fact these special protocols are on the higher layers,so that the lower layer will prove to be the same as for the CS
ame for PS and CS. UMTS has been designed to support both types of services, so that there are no special protocols. milar to the Iu interface towards the MSC. a signaling conenction to the SGSN in the core network. RANAP handles all signaling transport and access related tasks. stratum protocols. Because there are essential differences how to handle a packet switched service request, the PS core ession the SM (Session Management) protocol is used. The SMS is in fact the same as for CS.
mportant differences.
(e.g. internet). These external data network have their own special network protocols ( e.g. internet) . These external data o be connected with such an external network, the UE has to send packets of this special network protocol, for the UMTS k is called Packet Data Protocol (PDP). It is the task of the UMTS network to provide a tunnel (PDP context) for transparent
e PDP packet header. This shall increase the efficiency of the air interface usage.
frame on Iu. GTP-U organizes addressing and identification of the originator and destination of the data between RNC and SGSN. nection less unreliable transport service. In principle only routing is performed with UDP/IP er 5.
u interface is the interface between User Equipment (UE) and UMTS Terrestrial Radio Access Network (UTRAN) and it is the most portant interface in the UMTS system.
he radio interface (Uu) is layered into three protocol layers: e physical layer (L1) e data link layer (L2) e network layer (L3).
he layer 1 supports all functions required for the transmission of bit streams on the physical medium. It is also in charge of measurements function nsisting in indicating to higher layers, for example, Frame Error Rate (FER), Signal to Interference Ratio (SIR),interference power, transmit power, It is basically composed of a “layer 1 management” entity, a “transport channel” entity, and a hysical channel” entity.
he layer 2 protocol is responsible for providing functions such as mapping, ciphering, retransmission and segmentation. It is made of four blayers: MAC (Medium Access Control), RLC (Radio Link Control), PDCP (Packet Data Convergence Protocol) and BMC (Broadcast/Multicast ontrol).
he layer 3 is split into 2 parts: the access stratum and the non access stratum. The access stratum part is made of “RRC (Radio esource Control)” entity and “duplication avoidance” entity. The non access stratum part is made of CC, MM parts.The RRC functions of 3 are implemented by RNC, and the MM and CC functions of L3 are implemented by CN.
he protocol layers are located in the UE and the peer entities are in the node B or the RNC.
ransport Format Combinations
e MAC layer has the following steps,that can be identified with the presented functional blocks: CRC,used for error detection catenated after the CRC is appended. if the resulting data block is too long (e.g does not fit into one radio frame) a segmentation is performed
ase of interference.UTRAN FDD and TDD offer four different channel coding schemes as FEC(Forward Error Correction). These
data rate. the physical layer gets matching parameters from RRC layer me,some padding bits are appended d by fast fading and interference of the channel de Composite Transport Channels) are any tinuous transmission) bits are inserted. This is only for downlink segmented to several radio frames nel or to several physical channels if neccesary
data rate. the physical layer gets matching parameters from RRC layer me,some padding bits are appended d by fast fading and interference of the channel de Composite Transport Channels) are any tinuous transmission) bits are inserted. This is only for downlink segmented to several radio frames nel or to several physical channels if neccesary
annel) and transmitted in physical channels,there has to be an indication which transport formats are used for every transport UE and NodeB the value of the TFCI can be translated into:
mat combination is signaled by RRC during radio bearer establishment.
ed port channel's transport format set build a "transport format comnination". Such a combination has to be chosen with
Every transport format combination in the transport format combination set is uniquely identified with a transport format
power, and transmission power)
ost of these procedures are triggered and mastered by higher layers like MAC and RRC. The procedures can be devided into
/slot and chip synchronization to physical channels. In the TDD mode also timing advance procedures are used to synchronize
problem. The solution for this is a very fast power control mechanism,using a closed control loop ( UE<>NodeB<>UE) A has to use random access mechanism to establish a radio connection between an UE and the Network. BNut also for
B have to perform measurements of radio signal quality (bit error rate) and radio signal strength (signal interference tion or handover procedures. For the measurments the UE physical layer has uses so called compressed mode mode radio uement are then performed.
dcast/Multicast Control
physical layer on common
II. RLC, The functions of RLC include: 1. Segmentation, reassembly, concatenation, padding and transfer of user data 2. Flow control Error correction, in-sequence delivery of upper layer PDUs and duplicate detection 3. Sequence numbers check 4. Protocol error detection and recovery 5. Ciphering 6. Suspend/resume function III. PDCP, The functions of PDCP include: 1.Header compression and decompression of IP data streams at the transmit and receive entities respectively 2.Transfer of packet oriented user data using RLC transparent,unackowledge or acknowledged mode 3.Forwarding of PDCP-SDUs from NAS to RLC, and multiplexing of different RBs to the same RLC entity
ansport channel types can IV. BMC ,The functions of BMC include: 1.Storage of cell broadcast messages 2.Traffic volume monitoring and radio resource request for CBS 3.Scheduling of BMC messages 4.Transmission of BMC messages to UE 5. Delivery of cell broadcast messages to upper layer (NAS)
1.Storage of cell broadcast messages 2.Traffic volume monitoring and radio resource request for CBS 3.Scheduling of BMC messages 4.Transmission of BMC messages to UE 5. Delivery of cell broadcast messages to upper layer (NAS)
e of the Iub interface contains the following protocols:
pplication Part) : The NBAP protocol is the application protocol of the Iub interface. It organizes all controlling tasks between RNC and NodeB on,transceiver configuration). M : These protocols constitute the signalling bearer for the NBAP messages.
f the Iub interface has to transfer the downlink and uplink data to and from the UE. Therefore different frames are defined in the same interface. The user plane consists of:
: The Frame Protocols encapsulate the UE data (UL&DL) on the Iub interface e frame protocol,that encapsulate the UE data,are transported over AAL 2 virtual channels of ATM. These AAL 2 virtual channels have to be set up
aling protocol : The AAL type 2 SP provides the messages and functions to setup, release and modify AAL 2 virtual channels. 5,ATM : The STC (Signaling Transport Converter),SAAL,AAL 5 and ATM provide the signaling bearer for AAL type 2 signaling protocol.
r is not standardized. it is up to the operator and verndor to choose an appropiate physical transmission system.
e of the Iur interface contains the following protocols:
etwork Subsystem Application Part) : The RNSAP protocol is responsible for the communication between S-RNC and D-RNC. This location for a UE in a cell of the D-RNC,soft handover procedures and procedures to transfer the S-RNC functionality to a D-RNC
g Connection Control Part) : The SCCP is used to set up a signaling connection between S-RNC and D-RNC for the UE. This means p one SCCP signaling connection for every D-RNC and UE. The signaling connection will be used for fast identification of the UE in es AL5,ATM : These protocols form the signaling bearer used for the RNSAP protocol messages.
f the Iur interface has the tasks to transport uplink and downlink data for the UE connected to a D-RNC. This tasks requires the following
: The data to and from the UE will be encapsulated into frame. These frames are defined by so called frame protocols. These frame ffic management with in-band signaling e frame protocol packets are transmitted via Iub using AAL 2 virtual channels. So AAL 2 ,ATM form the data bearer on the Iub interface. aling protocol : The AAL type 2 SP provides the messages and functions to setup, release and modify AAL 2 virtual channels. AL,AAL 5,ATM : These protocols provide the signaling bearer for the AAL type2 signaling protocol. The STC(Signaling Transport es functionality for congestion handling and load control. The protocol suite MTP3B,SAAL,AAL5 and ATM can be shared with the RNSAP of Control Plane
ocol model is applied to the UTRAN interfaces Iu, there are differences between Iu-CS toward the CS-core network domain and Iu-PS towards the omain.
stack e for Iu-CS is formed out of the following protocols: Access Network Application Part) : The RANAP protocol is responsible for all access and signaling transport related tasks. It is the application CS interface Connection Control Part) : The SCCP is used to setup signaling connection between RNC and MSC. There will be one and only one SCCP N-MSC for every IE using CS service. AL5,ATM : Theses protocols provide the signaling bearer for RANAP/SCCP messages
n Iu-CS has to support the transfer of real time CS data streams. Therefore the Iu-CS plane has the following protocols: e) protocol : The Iu UP protocol is used to provide additional support functions for CS data streams on Iu. These functions can be : timing ontrol,backward error conrrection. the data bearer to transport the data streams the AAL 2 virtual channels are used.
work control plane is necessary ,because AAL2 virtual channels need to be setup and released. The protocol suite on the transport ane consisting of: aling protocol : used to setup ,modify and release AAL 2 virtual channels. AL,AAL5,ATM : These protocols provide the signaling bearer for the AAL type 2 signalling protocol messages.
stack e is the interface between RNC and SGSN. The control plane of Iu-PS is similar to the Iu-CS plane. It consists of: ne plication protocol for Iu-CS and Iu-PS signaling connection on Iu-PS. There will be one and only one SCCP connection between RNC and SGSN for every UE using PS nnections on Iu-PS and Iu-CS do not affect each other. AL5,ATM : The signaling bearer for SCCP/RANAP
n Iu-PS is competely different to the user plane of Iu-CS. This is because the traffic to and from SGSN is PS, so routing layer are TRAN provides the following protocols on the Iu-PS user plane: As for Iu-CS the Iu UP protocol can provide additional support functions for the data stream. unneling Protocol-User Plane): GTP-U provides a frame for the user data to be transported. In a GTP-U frame a reference number for nd sequence numbers for the data are contained. P/IP protocol suite is used as network layer between RNC and SGSN. The task of these protocols is to route from RNC to SGSN and
ATM adaptation layer of type 5 is used as bearer for the packets of IP/UDP/GTP-U. channels do not need to be set up in a dynamic manner. Rather the operator is expected to pre-configure the AAL 5 bearer to be used nsfer. Therefore on Iu-PS there is no need for a transport network control plane. no bearer set up with explicit signalling is necessary.
RANAP
NBAP
tion part controls signaling information for the call setup between nodes. Basically these applications message structure is similar to the SS7 l part. nsmit signaling for the control plane and one application part (ALCAP) to set up the transport bearer for the user plane.
gnaling protocol that contains all the control information specified for the Radio Network Layer. The fucntions of RANAP are ion of one or more EP.
ndover earing a connected RAB
e not interpreted by UTRAN, such as broadcast information,direct transfer etc. ection in the radio interface
t is divided into two procedures : NBAP defines all the procedures for the logical operation and maintenance of the Node-B, such as configuration and fault
tup procedure,the NodeB assigns a traffic termination point to control UE signaling. All of the subsequent signaling related to
y to manage the cell configuration information in a NodeB. nage the configuration of common transport channels in a NodeB. eduling of System Information to be broadcast in a cell. bout the status of NodeB resources.
t is divided into two procedures : NBAP defines all the procedures for the logical operation and maintenance of the Node-B, such as configuration and fault
tup procedure,the NodeB assigns a traffic termination point to control UE signaling. All of the subsequent signaling related to
y to manage the cell configuration information in a NodeB. nage the configuration of common transport channels in a NodeB. eduling of System Information to be broadcast in a cell. bout the status of NodeB resources. and enforce that both nodes have the same information on the configuration of the radio resources. nts in the NodeB. The function also allows the NodeB to report the result of the measurements. d resources in a NodeB. radio link. mode in a NodeB. ents in the NodeB. The function also allows the NodeB to report the result of the measurements. one or more radio links in order to avoid DL power drifting between radio links. ons.
ce signaling protocol that controls signaling transfer between two RNC (SRNC and DRNC) in order to support the inter RNC soft
n a DRNC. dio link
links in order to avoid DL power drifting between radio links SRNC on a CCCH controlled by the DRNS
terfaces.
ol that provides the signaling capability to establish,release and maintain AAL2 connections by a series of ATM VCCs. In other ur,Iub) in the UTRAN. The transport bearer in the User Plane are setup first sending signals by the Application Protocol in the e use of the ALCAP is dependent on the type of bearer to be used. The signaling bearers are usually pre-configured. This means
s case the setup runs in the following manner: estriction to a single transport system, the application protocols shall not be specific to a certain transport solution. Therefore his principle is the same as for BICC (Bearer Independent Call Control). to trigger the set up of a bearer first the application
be setup ,performs all necessary procedures to configure the bearer. When the application part receives the notification of a an be informed to start the data stream transmission.
coding and
one directory
LMN search
s transmission
responsible for
N , CS domain via Iu(CS) interface
the radio technology
S-RNC.The serving RNC handles all
ons/initiation. t not always)
he RRC signalling
by a RNC different e cells not
ons/initiation. t not always)
he RRC signalling
by a RNC different e cells not
called splitting. the D-RNC ,
plane data L2 processing radio links with two or
or multiple (sector) cells can be
sion Duplex (Uplink and Downlink nsport via the radio interface,and in ment ,compares the value with a links and determines the Frame
c and signalling. ntenna multi-coupling,
connections. Control
reas.
ervice Areas.
reas.
ervice Areas.
el. The MSCs and
on, which is
TU-T and are specified within ITU-T
a Iu,Iur and Iub
entifiers are released.
n Number,MSIN. The total length of
within the area controlled by a VLR.
FAC(2 digits)which
entify the UE to the
g including
ccess
the functions to provide access links e can distiguish three types of
E to the network. Access Stratum atum UEed in UTRAN. This
DUs (Protocol Data Unit) ansport stratum
hat do not deal with erving stratum)
ia Uu(radio) interface. User data ces,handover etc) are exchanged
onnection Management (CM) or e 2+ ) procedures are
odel describes these layers and future,if neccessary,while other
M-BSS. ATM supports AL Type 5 are used. Bearers of AAL g between the corresponding ATM
TRAN related issues without any UTRAN includes the physical
um. Also all other data
one plane can coexist port Network Control
ls. These frame e to be set up with
one plane can coexist port Network Control
ls. These frame e to be set up with
e messages of an d for all control for transport the
Part). The ALCAP or transmission. It is onfigured bearers only Network Layer
col in the Control Plane
he exchange of short messages. It
etc. s. Transparent (TM). ) nd SMS (Short
It is the
ot by an explicit
or the control plane. The following
onally the AAL 2 cirtual channel
d UE-signaling
or the control plane. The following
onally the AAL 2 cirtual channel
d UE-signaling
ove to be the same as for the CS
rotocols.
lated tasks. he PS core
xternal data r the UMTS for transparent
en RNC and SGSN.
UTRAN) and it is the most
in charge of measurements function interference power, transmit power,
mentation. It is made of four l) and BMC (Broadcast/Multicast
de of “RRC (Radio rts.The RRC functions of
e) a segmentation is performed
Correction). These
every transport
osen with
rt format
be devided into
d to synchronize
eB<>UE) t also for
ence de mode radio
duplicate detection
d receive entities respectively acknowledged mode s to the same RLC entity
tasks between RNC and NodeB
rames are defined in the same
L 2 virtual channels have to be set up
virtual channels. type 2 signaling protocol.
on system.
S-RNC and D-RNC. This ionality to a D-RNC
C for the UE. This means ntification of the UE in
. This tasks requires the following
protocols. These frame
earer on the Iub interface. virtual channels. Signaling Transport be shared with the
work domain and Iu-PS towards the
t related tasks. It is the application will be one and only one SCCP
protocols: ese functions can be : timing
ol suite on the transport
s.
of:
every UE using PS
o routing layer are
e a reference number for
om RNC to SGSN and
AAL 5 bearer to be used signalling is necessary.
e structure is similar to the SS7
er plane.
of RANAP are
n and fault
aling related to
n and fault
aling related to
the inter RNC soft
M VCCs. In other Protocol in the gured. This means
ution. Therefore e application
otification of a
Mapping of UE state to 3GPP Specifications After UE switch on, there are two basic operational modes of a UE, idle mode and connected mode.The connected mode can be further divided into 4 service states,which define what kind of physical channels a UE is using. The mapping of UE state to 3GPP speciafication is shown below:
UE Switch on
UE Idle
UE Connected
3GPP TS 25.304
3GPP TS 25.331
GSM Idle GSM TS 05.08
UE Idle 3GPP TS 25.304 3GPP TS 25.331
GSM Connected
GSM Packet Transfer
GSM TS 04.18
GSM TS 04.50
Cell_DCH 3GPP TS 25.331
Cell_FACH 3GPP TS 25.304 3GPP TS 25.331
Cell_PCH 3GPP TS 25.304 3GPP TS 25.331
URA_PCH 3GPP TS 25.304 3GPP TS 25.331
RRC Tasks and Functions
The RRC protocol is the application part for the UMTS radio access technology. This means all controlling radio tasks are in the responsib -broadcasting of system information for NAS stratum -establishment,maintenance and release of RRC signaling between UE and UTRAN connections -establishment,reconfiguration and release of radio bearers -RRC connection mobility functions -Quality of Service (QOS) control -UE measurement reports -outer loop power control -security control -paging -Initial cell selection and reselection -transport of NAS stratum control messages With all these tasks the RRC protocol belongs to the access stratum when the radio oriented control tasks are performed and it higher layer control plane protocol messages.
Usage of Radio Bearer by the RRC protocol The RRC protocol uses the radio bearer service provided by the layer 1 and layer 2 of the UMTS radio interface. The radio be The radio bearers 0,1,2,3,4 are pre-assigned for exclusive RRC usage. The following is speified: -RB0 : The radio bearer 0 shall be used for all CCCHs. The CCH in the uplink is mapped to the RACH with RLC transparent FACH with RLC unacknowledged mode. -RB1 : The radio bearer 1 is for all DCCH messages with RLC unacknowledged mode -RB2 : The radio bearer 2 is used for all DCCH messages in RLC acknowledged mode, but not for RRC messages that trans -RB3 and optional RB4 : These two radio bearers shall be used for RRC messages carrying NAS messages on DCCH in R
The radio bearers 5,...,31 can be used with explicit radio bearer set up for all purposes, e.g. traffic channels or control channe For RRC messages the protocol specified which RLC mode and with this which radio bearer can be chosen for transport of th
RRC Modes and State Transitions including GSM UTRA RRC Connected Mode GSM URA_PCH
CELL_PCH UTRA: Inter-RAT Handover
CELL_DCH
Release RRC Connection
CELL_FACH
Cell Reselection
Release of a TBF
Release RRC Connection Establish RRC Connection
GPRS Packet Transfer
Establish RRC Connection
(MS in GPRS Packet
(UE camps on UTRAN cell) Idle Mode
(MS camps on a
The RRC protocol is an application part (Radio Resource Management) and transport protocol (NAS message transport). Therefore the R states. The RRC state definiton describes the RRC protocol behavior as a nested set of stated. Two main states are defined: 1. UTRA Idle Mode : In UTRA idle mode, the UE has no signaling relationship with the UTRAN. In this case the idle mode procedures ha UE is switched on, it searches for PLMNs and cells and listen to the broadcasted system information of selected cells
2. UTRA RRC Connected Mode : In the connected mode the UE has a signaling connection with the UTRAN. The setup of this signaling connection set up). This procedure is the transistion from idle to connected mode. When the RRC connection is released, the connected
For multi-mode mobile phones (e.g. UMTS,GSM/GPRS) the RRC states can be combined with the radio resource management st
The RRC protocol is an application part (Radio Resource Management) and transport protocol (NAS message transport). Therefore the R states. The RRC state definiton describes the RRC protocol behavior as a nested set of stated. Two main states are defined: 1. UTRA Idle Mode : In UTRA idle mode, the UE has no signaling relationship with the UTRAN. In this case the idle mode procedures ha UE is switched on, it searches for PLMNs and cells and listen to the broadcasted system information of selected cells
2. UTRA RRC Connected Mode : In the connected mode the UE has a signaling connection with the UTRAN. The setup of this signaling connection set up). This procedure is the transistion from idle to connected mode. When the RRC connection is released, the connected
For multi-mode mobile phones (e.g. UMTS,GSM/GPRS) the RRC states can be combined with the radio resource management st phone can be: 1. Idle Mode : The idle mode of GSM/GPRS has the same meaning as the idle mode of UMTS. The only difference is, that the UE is cam 2. GSM conected mode : In GSM the RR (Radio Resource Layer) performs the radio management. This protocol can setup a RR connec When such a connection exist,the UE is in GSM connected mode. A GSM-DCCH is allocated for the UE in this case. 3. GPRS packet transfer mode : In GPRS the radio resources are allocated for a mobile temporary only. Such a temporary resource is c mobile is granted a temporary block flow ,the mobile is in GPRS packet transfer mode (GPRS-RLC state)
With a multi-mode UE it shall be possible to perform in-service-transitions between the different Radio Access Technology (RAT).Therefo handover from UTRA connected mode to GSM connected mode and vice versa. A transistion from UTRA connected mode to GPRS pack packet transfer in UMTS, making a cell reselection to a GPRS cell and getting a GPRS temporary block flow.
RRC Mode Description RRC Idle Mode
When a UE is switched on, it enters the RRC idle mode. In the RRC idle mode, there is no connection on the access stratum level betwee in the RRC idle mode. If UTRAN wants to address the UE, it must use non-access stratum identifiers, such as IMSI or TMSI and LAI. In the RRC idle mode, the UE monitors the BCCH, and when it is registered to the CN, it also listens to paging occasions on its PICH.
The transition from the RRC idle mode to the RRC connected mode can only be initiated by the UE by sending the "RRC Connection Req used to exchange messages and data between the UE and UTRAN, the UE is identified by a Radio Network Temporary Identity (RNTI). A figure above, the UE can be in one of four sub-states, when it is in the RRC connected mode. The sub-states depend on the connectivity channels depend also on the sub-states. For instance, the DCHs are not available in the sub-states CELL_PCH and CELL_URA. The UE mode when sending the RRC Connection Request message to UTRAN. When UTRAN accepts the UE„s request, the UE enters either the
RRC Connected Mode The RRC connected Mode can be further decomposed into four different states. These four sub-states describe, on which level the UE is UE. UTRAN can know any UE either on cell level (cell state) or on URA level (URA state). On the other hand any UE can have a DCH or exchange. Therefore the four connected states are introduced:
CELL_DCH In this sub-state, dedicated physical channels are allocated to the UE. DCCH and – if configured – DTCH information can be transmitted. because the physical channels are exclusively allocated to this UE. UTRAN knows the active set cells for the radio links and thus the loca allocated to the UE. In this state, the UE is capable to receive RRC messages on the DCCH (and BCCH, if it owns specific capabilities). T UE reads the cell system information and acts accordingly. For instance, it determines the measurement quality and the reporting events entered from Cell_FACH by setting up a DCH. When the last DCH is released the UE enters Cell_FACH,Cell_PCH,URA_PCH or idle mod In the CELL_DCH state the UE shall perform the following actions: if DCCH and DTCH are available: - read system information broadcast on FACH (applicable only to UEs with certain capabilities and camping on FDD cells); - perform measurements process according to measurement control information
CELL_FACH This state was introduced for traffic situations, where only small amounts of data have to be transmitted. This is the case when only highe of user data (e.g. SMS messages) have to be transmitted. In this case, an exclusive allocation of one physical channel to the UE would re FACH can be used by the UE to transmit higher layer data, which it has to share with other UEs. Each UE must be explicitly addressed, f permanently in the downlink, not to miss user data for it. The UE„s FACH is mapped on one S-CCPCH.
In the uplink, it uses the shared transport channels for user data transfer, such as the RACH. The UE is only connected to one cell, and t handover takes place in this sub-state. The UE is responsible for cell re-selection. By listening to the cell system information from the BCC values, neighbourhood lists to perform the cell re-selection process. Other relevant information is also learned from the BCCH. The UE re RRC messages on the BCCH, CCCH and DCCH channels. Due to the discontinuous type of traffic, UTRAN can command the UE to per In the CELL_FACH state the UE shall perform the following actions: if the UE is "in service area": - DCCH and DTCH are available - perform cell reselection process - perform measurements process according to measurement control information - run timer T305 (periodical cell update)
In the uplink, it uses the shared transport channels for user data transfer, such as the RACH. The UE is only connected to one cell, and t handover takes place in this sub-state. The UE is responsible for cell re-selection. By listening to the cell system information from the BCC values, neighbourhood lists to perform the cell re-selection process. Other relevant information is also learned from the BCCH. The UE re RRC messages on the BCCH, CCCH and DCCH channels. Due to the discontinuous type of traffic, UTRAN can command the UE to per In the CELL_FACH state the UE shall perform the following actions: if the UE is "in service area": - DCCH and DTCH are available - perform cell reselection process - perform measurements process according to measurement control information - run timer T305 (periodical cell update) - listen to all FACH transport channels mapped on S-CCPCH assigned to this UE if the UE is "out of service area": - perform cell reselection process - run timers T305 (periodical cell update), and T317 (cell update when re-entering "in service") or T307 (transition to Idle mode)
CELL_PCH and URA_PCH The remaining two sub-states – CELL_PCH and URA_PCH – were introduced to cope with inactive data users. Just think about users, wh with the data, and for a longer time, no transmission takes place. If this is the case, access stratum resources can be released when mov DTCH is allocated to the UE. No exchange of data is possible between the UE and UTRAN. If the UE wants to transmit something, it mus
The UE listens to the cell system information, broadcasted on the BCCH. It performs measurements accordingly, and is responsible for ce PLMN with a higher priority. When UTRAN wants to transmit data to the UE, it must be paged first. Therefore, the UE has to monitor pag on the BCCH and the PCCH.
CELL_PCH In this sub-state, the UE„s current cell is known to the RNC. If the RNC wants to exchange data with the UE, it only needs to p must perform a cell update. Also periodical cell updates can be requested by UTRAN. To perform updates, the UE must change to the CE uplink transmission is allowed in CELL_PCH/URA_PCH.)
URA_PCH URA stands for UTRAN Registration Area. This state is comparable to the Cell_PCH,only that the UTRAN knows the UE on If the UE is in the CELL_PCH and moving fast, a lot of cell updates have to be performed. URAs are a combination of one or several cells cell may belong to several URAs. If UTRAN wants to transmit something to the UE, it must page the UE within the URA. The UE is respon URA – and periodic URA updates – when required by UTRAN. In the URA_PCH or CELL_PCH state the UE shall perform the following actions: if the UE is "in service area": - maintain up-to-date system information as broadcast by the serving cell - perform cell reselection process - perform a periodic search for higher priority PLMNs - monitor the paging occasions according to the DRX cycle and receive paging information on the PCH - perform measurements process according to measurement control information - maintain up-to-date BMC data if it supports Cell Broadcast Service (CBS) - run timer T305 for periodical URA update if the UE is in URA_PCH or for periodical cell update if the UE is in CELL_PCH if the UE is "out of service area": - perform cell reselection process - run timer T316; - run timer T305
RRC Connection Mobility Management and RRC Modes
If the UE is in the RRC connected mode, but not in the CELL_DCH sub-state, it is responsible to inform UTRAN about a detected change state and send the RRC message Cell Update or URA Update.
Depending on the UE„s RRC message, UTRAN returns the RRC message Cell Update Confirm or URA Update Confirm – if it accepts the Connection Release message.
The cell or URA update are conducted for several reasons: 1. The UE is in the CELL_PCH or URA_PCH sub-state and re-entering the UMTS service area. Then the UE moves to the CELL_FACH s 2. Periodical updates can be enforced by the operator for UEs in the sub-states CELL_FACH, CELL_PCH and URA_PCH. 3. There is an unrecoverable error at the UE„s RLC-entity, used for acknowledge mode of operation. 4. A cell update is additionally triggered for several reasons: - The UE has performed cell-reselection. It is camping on a new cell, and UTRAN must be notified about it. - The UE was paged in the sub-states URA_PCH or CELL_PCH. - The UE informs UTRAN about its transition to the CELL_FACH state. Another reason for a CELL_FACH transition is an indication by the transmitted uplink. - The UE is in the CELL_DCH and a radio link failed. - The UE was not capable to transmit the RRC message UE Capability Information.
If a cell update takes place, the UE may be requested to modify its RB configuration, TrCH configuration, etc. This must be confirmed by t establishments of RLC-entities in the acknowledged mode as figures below.
4. A cell update is additionally triggered for several reasons: - The UE has performed cell-reselection. It is camping on a new cell, and UTRAN must be notified about it. - The UE was paged in the sub-states URA_PCH or CELL_PCH. - The UE informs UTRAN about its transition to the CELL_FACH state. Another reason for a CELL_FACH transition is an indication by the transmitted uplink. - The UE is in the CELL_DCH and a radio link failed. - The UE was not capable to transmit the RRC message UE Capability Information.
If a cell update takes place, the UE may be requested to modify its RB configuration, TrCH configuration, etc. This must be confirmed by t establishments of RLC-entities in the acknowledged mode as figures below.
URA Update is conducted – next to re-entering the UMTS service area, due to an RRC acknowledged mode unrecoverable error and bec UE performs cell re-selection, and the „new“ cell does not belong the the UE„s URA. An URA Update is then triggered by the UE to get a n
When a UE transmits a Cell Update or URA Update message, it starts the timer T302. It waits for the T302 period to get the Cell Update C If no confirmation message arrived within this time period, the UE retransmits the original message. The number of Cell Update or URA U send, it hereby limited to N302. The retransmission is of course only possible, when the UE is in the service area; if not, it must continue t
Cell and URA updates performed according to the causes in the figure below. As you can see, a periodic update can be done not only, wh also, when the UE is in the CELL_FACH sub-state. A periodic update is a supervision mechanism, which can be used by the mobile oper performed, a UE in the CELL_FACH sub-state may transit to the sub-states CELL_DCH, CELL_PCH or URA_PCH, or in the RRC mode i
UE Tasks in the CELL_FACH Sub-state In the CELL_FACH, but also in the CELL_PCH and URA_PCH, the timer T305 is used for periodical cell or URA updates. It is still active, when the UE is out of the service area. What happens, if this timer expires? The timer T307 is activated, and the UE starts moves into the idle mode and releases all resources. The timers can be broadcasted with the System Information Block 1 (or as part of the UTRAN Mobility Information message):
Out-of-Service Area Timing If the UE is out of service area, it runs the cell selection process. It keeps the timers T305 running and starts timer T316. The UE attempts and the UE is in the service area again, the UE stops timer T316. It also stops timer T307, in case this timer is active. Being back in the s by the same cell or URA, and no update is required. If the UE is in the service area, but the cell or URA has changed, the cell or URA upd happens, if the timer T316 expires? If the UE is still out of service area, it moves to the sub-state CELL_FACH and starts timer T317. If th the Cell Update with cause „re-entering service area . In the CELL_FACH state, the UE acts like this: If the UE is in the service area and the timer T305 has expired, it performs a periodical cell update.
If the UE is out of service area, it performs the cell selection process. The timers T305 is still active, and the UE starts timer T317, if it was timer T317 is stopped. Also timer T307 is stopped, when it was active. The UE has to transmit the RRC Cell Update message to UTRAN, cell update: re-entering service area. If the timer T317 expires, the UE moves to the idle mode. It releases all dedicated resources.
Click to return to main page
nnected mode can be g of UE state to 3GPP
GSM Packet Transfer 04.50
radio tasks are in the responsibility of RRC. The RRC has following functions:
ol tasks are performed and it belongs to the transport stratum,because it carriers the
radio interface. The radio bearers in an UE will be numbered from 0 to 31.
RACH with RLC transparent mode, the downlink CCCH is mapped to the
or RRC messages that transport NAS messages inside. S messages on DCCH in RLC acknowledged mode.
c channels or control channels. be chosen for transport of this message.
GSM-UMTS Handover GSM Connected Mode
RAT Handover Release RR Connection GPRS Packet Transfer Mode Release of a TBF Initiation of a TBF
Establish RR Connection
(MS in GPRS Packet Idle Mode)
(MS camps on a GSM/GPRS cell)
age transport). Therefore the RRC protocol requires state definition with transitions between
tates are defined: e the idle mode procedures have to be applied. This means as soon as the ected cells
AN. The setup of this signaling conenction is done by a RRC procedure (RRC on is released, the connected mode is left and the idle more is entered.
dio resource management states of GSM/GPRS. In GSM/GPRS the states of a mobile
age transport). Therefore the RRC protocol requires state definition with transitions between
tates are defined: e the idle mode procedures have to be applied. This means as soon as the ected cells
AN. The setup of this signaling conenction is done by a RRC procedure (RRC on is released, the connected mode is left and the idle more is entered.
dio resource management states of GSM/GPRS. In GSM/GPRS the states of a mobile
ifference is, that the UE is camped on a GSM/GPRS cell rotocol can setup a RR connection between network and mobile equipment. this case. Such a temporary resource is called a temporary block flow (TBF). When a
ess Technology (RAT).Therefore it is possible to make a inter-system onnected mode to GPRS packet transfer mode is simply done by stoppint the w.
he access stratum level between the UE and UTRAN. UTRAN has no information about UEs as IMSI or TMSI and LAI.
ing occasions on its PICH.
ding the "RRC Connection Request" message to UTRAN. If common transport channels k Temporary Identity (RNTI). As can be seen in the es depend on the connectivity level between the UE and UTRAN. The set of usable transport PCH and CELL_URA. The UE leaves the RRC idle equest, the UE enters either the sub-state CELL_DCH or CELL_FACH.
cribe, on which level the UE is known by UTRAN and which resources are allocated by the nd any UE can have a DCH or a FACH or no transport channel for control message
nformation can be transmitted. There no need to identify the UE on a dedicated channel, he radio links and thus the location of the the UE. Also downlink shared channels can be f it owns specific capabilities). The cell system information is broadcasted on the FACH. The uality and the reporting events from the cell system information. This state can only be ell_PCH,URA_PCH or idle mode
g on FDD cells);
his is the case when only higher layer signalling information (NAS signalling) or small amount cal channel to the UE would result in a waste of resources. Only common transport channel must be explicitly addressed, for instance by the RNTI. It has to monitor the FACH
nly connected to one cell, and this is the location information, known within UTRAN. No soft ystem information from the BCCH, it gains all relevant measurement qualities, threshold ned from the BCCH. The UE receives N can command the UE to perform periodic cell updates.
nly connected to one cell, and this is the location information, known within UTRAN. No soft ystem information from the BCCH, it gains all relevant measurement qualities, threshold ned from the BCCH. The UE receives N can command the UE to perform periodic cell updates.
nsition to Idle mode)
sers. Just think about users, who surf in the Internet. After downloading some files, they work es can be released when moving in one of the two states. In both states, no DCCH nor s to transmit something, it must move first internally to the sub-state CELL_FACH.
dingly, and is responsible for cell-reselection. In addition to that, it periodically looks for a ore, the UE has to monitor paging occasions on its PICH, i.e. it receives RRC messages both
a with the UE, it only needs to page the UE there. If the UE changes the cell, it the UE must change to the CELL_FACH sub-state. (Please note, that no
the UTRAN knows the UE on URA level. bination of one or several cells under one S-RNC. URAs may overlap, i.e. a hin the URA. The UE is responsible for URA updates – when it changes the
s in CELL_PCH
RAN about a detected change of location. The UE then moves (or is) in the CELL_FACH
date Confirm – if it accepts the UE„s update request. Otherwise, it return the RRC
E moves to the CELL_FACH state and notifies UTRAN. and URA_PCH.
ransition is an indication by the UE„s higher layers, that data has to be
tc. This must be confirmed by the UE. It may also include a re-
ransition is an indication by the UE„s higher layers, that data has to be
tc. This must be confirmed by the UE. It may also include a re-
e unrecoverable error and because of an periodic URA update – when the n triggered by the UE to get a new URA assigned.
period to get the Cell Update Confirm resp. URA Update confirm message mber of Cell Update or URA Update messages, the UE is allowed to e area; if not, it must continue to search a service area.
pdate can be done not only, when the UE is in the CELL_PCH or URA_PCH sub-state, but an be used by the mobile operator to keep track of the UE. If a cell or URA update was RA_PCH, or in the RRC mode idle.
URA updates. is activated, and the UE starts the cell selection process. If the timer T307 expires, the UE
mation message):
s timer T316. The UE attempts to find a serving cell again. If it is successful, r is active. Being back in the service area can mean, that the UE is served s changed, the cell or URA update has to be initiated by the UE. But what CH and starts timer T317. If the UE is back in the service area, it performs
e UE starts timer T317, if it was not yet active. If the UE enters the service area again, the l Update message to UTRAN, indicating the cause of the all dedicated resources.
Click to return to main page
Click to return to main page >>State Transistions Parameters Description (Module II)
Click to return to main page
Click to return to main page
Click to return to main page >>UE&NodeB Timer and constant Parameters Description (Module II)
Click to return to main page
RRC Procedures
Between the UE and the RNC, the Radio Resource Control (RRC) protocol is used to exchange signalling and control data to establish, m transport channel configurations, and the physical layer settings. With that, the UE knows how to receive and transmit data via the WCDM about the radio interface configuration.
Following RRC procedures can be identified in accordance to the ETSI specification TS 25.331 V3.12.0: -RRC Connection Management Procedures :These procedures include the broadcasting of system information, paging, RRC connectio information transfer, etc. -Radio Bearer Control Procedures :These procedures for radio bearer establishment, transport channel and physical channel reconfigu -RRC Connection Mobility Procedures :These procedures such as cell and URA updates, UTRAN mobility information, active set updat -Measurement Procedures Measurement control and report, etc. is managed here.
Radio Resource Control message contains of following groups of information elements : -CN information elements : NAS specific information is transmitted, such as the CN type and CN domain identity. -UTRAN mobility management information elements : Cell access restrictions, cell and URA identities are examples of data, associate -UE information elements: UE related information is exchanged here, including capability update requirements, PDCP and FDD RF capa -Radio Bearer information elements: These information elements mostly describe the characteristics of a radio bearer, such as RB infor -Transport Channel information elements: Here, mainly the transport channel characteristics are described, such as the description of -Physical Channel information elements: Here, everything relevant for the PHY-layer is covered, such as the description of CCTrCHs o -Measurement information elements: Cell measured results, event results, filter coefficients etc. are exchanged here. -Other information elements
RRC Connection Establishment The purpose of the RRC Connection Establishment procedure is to create a RRC connection between the UE and UTRAN.
To do so, the UE sends the RRC Connection Request message to the RNC. The UE was in the RRC idle mode, and higher layer protocol establishment is always initiated by the UE. It is transmitted via the logical channel CCCH.
UTRAN returns a response. If UTRAN accepts the UE„s RRC Connection Request, it returns the message RRC Connection Setup messa physical channels.
From the RNC point of view, it is not just sufficient to inform the UE about the signalling resources. The Node B must also get all relevant p interface and Uu-interface. Before the RNC returns the RRC Connection Setup message to the UE, it uses the UTRAN specific signalling If UTRAN denies access to the UE, it returns the message RRC Connection Reject. Both messages are returned to the UE via a FACH. If the UE has received the message RRC Connection Setup, it returns the RRC Connection Setup Complete message to the RNC, using
RRC Connection Request Message
1. RRC Connection Request message It is initiated by the UE and transmitted via the uplink CCCH. Two types of information element groups can be found in this message: -UE information elements and -Measurement information elements. Following data about the UE is sent in this message: -Initial UE identity: The UE identities contains of 4 options- IMSI,IMEI,P-TMSI&RAI or TMSI&LAI. The operator can choice one of the UE identity to use -Establishment cause : There is a huge list of causes for a connection request -Protocol error indicator : This message can also indicate, whether a protocol error occurred. If so, this value is set to TRUE. The default value is FALSE.
The UE also delivers measurement results; the corresponding IE is called Measured Results on the RACH, because the measurement operator, but it is an option. If set by the operator, it is broadcasted as cell system information. The cells, listed in the measurement result with the best one in the beginning of the list.
RRC Connection Setup Message
2.RRC Connection Setup mess If the S-RNC accepts the UE„s R connection over the interface Iub configuration parameters for uplin prepared to serve as intermediat parameters with the RRC Conne establish signalling radio bearers
The RRC Connection Setup mes characteristics both in the UL and the RRC layer in the UE. The UE -If only the physical layer chara modification may affect scramblin has no impact to the higher layer change measurement quantities -If the transport channels are m PHY layer. The MAC layer is resp resources, ciphering and de-ciph -If a radio bearer is established (RLC) layer – for each radio bear Broadcast/Multicast Control (BMC the RRC Connection Setup mess PDCP layer and BMC layer relev
PHY layer. The MAC layer is resp resources, ciphering and de-ciph -If a radio bearer is established (RLC) layer – for each radio bear Broadcast/Multicast Control (BMC the RRC Connection Setup mess PDCP layer and BMC layer relev
The message itself holds 4 information elements groups: 1. UE information elements to identify the UE (UE IEs) 2. Radio bearer information elements (RB IEs), which specify the properties of the signalling bearers, which are established with this RR 3. Transport channel information elements(TrCH IEs: UL/DL) to define the transport channel characteristics, in other words the TFCS 4. Physical Channel information elements(PhyCH IEs: UL/DL), which specify parameters relevant for the PHY layer to make the physic
3. RRC Connection Setup message: TrCH IEs (UL/DL): Each RB set between a UE and UTRAN has a unique number. Each of them can be mapped on one or two logical channels. This was par mapped on transport channels. But on which transport channels can the higher layer information be transmitted? How can higher layer inf TrCH UL/DL. This information is used by the RRC to configure the RLC-, MAC, and PHY layer.
A very important IE is the Transport Format Set (TFC). The Transport Format Set information element describes the the allowed TFs, wh which logical channels are mapped on this TrCH.
The MAC layer is responsible to take the RLC PDUs (which hold the TBs), and to send them to their peer entity. RLC PDUs from several holds relevant information to identify the receiver of the RLC PDU. For instance, if two DTCHs are multiplexed on one DCH, then field C/T the RLC PDU has to be delivered to. Please note, that three different MAC entities exist: -MAC-b: This entity controls the BCH. It is located in the Node B. -MAC-c/sh : This MAC-entity controls the access to the common control channels PCH, FACH, RACH, CPCH, DSCH. -MAC-d: This MAC-entity control the access to the dedicated transport
4.RRC Connection Setup message: PhyCH IEs (UL/DL):
The Physical Channel information elements deliver relevant information for the PHY layer to configure the physical channels. One of the P established. As can be seen, a UE can be immediately re-directed to another frequency band for the signalling bearer setup. Also the ava The Uplink DPCH info is an optional information element in the RRC Connection Setup message.
The UE can be informed about the downlink radio resources, when receiving the RRC Connection Setup message. When we have a close following FDD-mode specific information elements: 1. DPCH compressed mode If a UE has only one receiver, it can„t make inter-frequency or inter-RAT measurements on neighbouring c the downlink transmission must be interrupted to give the UE time to make its measurements. Therefore, this mode is often called Slotted puncturing is done – if the required link quality can be kept up – or the spreading factor is halved for a short while. 2. Site Selection Diversity Transmit (SSDT) ,The UE is served by several active set cells. But while all active set cells receive the UE„s s cells, which one shall serve it in the downlink. 3.Transmit Diversity Two-transmitter diversity is applied. The UE sends a feedback (FBI) to the Node B, so that this device can decide called „closed loop modes“: - closed loop mode 1: A phase adjustment is done with one antenna. Hereby, the feedback command ra are sent on four timeslots to the Node B.
RRC Connection Setup Complete message
RRC Connection Establishment Timing
After the UE transmits RRC CONNECTION REQUEST message, the T300 timer will be started, and the timer will be stopped after the UE REQUEST message is retransmitted less than the number of times specified by the constant N300, the UE repeats RRC CONNECTION R procedures in details are as follows:
if the UE has not yet received an RRC CONNECTION SETUP message with the value of the IE "Initial UE identity" equal to the value of th the UE shall: - check the value of V300; and if V300 is equal to or smaller than N300: - if cell re-selection occurred: set CFN in relation to SFN of current cell - set the IEs in the RRC CONNECTION REQUEST message - perform the mapping of the Access Class to an Access Service Class and - apply the given Access Service Class when accessing the RACH; - submit a new RRC CONNECTION REQUEST message to lower layers for transmission on the uplink CCCH; - increment counter V300; - restart timer T300 when the MAC layer indicates success or failure to transmit the message; if V300 is greater than N300: - enter idle mode. - consider the procedure to be unsuccessful; - Other actions the UE shall perform when entering idle mode from connected mode - The procedure ends.
L1 Synchonization on DPCCH and DPDCH (UL and DL)
Downlink synchronisation primitives
For the dedicated channels, synchronisation primitives are used to indicate the synchronisation status of radio links, both in upl A UE Layer1 shall check the synchronisation status of every radio frame of downlink and uplink dedicated channels in order to detect a los a radio link is determined based on the physical channel BER of the DPCCH (The physical channel BER is the relation of the incorrectly d Qout and Qin specify at what DPCCH quality levels the UE shall shut its power off and when it shall turn its power on respectively. The sy
The criteria for reporting synchronisation status are defined in two different phases. Phase 1: -Starts when higher layers initiate physical dedicated channel establishment and lasts until 160 ms after the downlink dedicated channel is -During this time the Out-of-sync status shall not exist -During this time the In-sync status shall be reported using the CPHY-Sync-IND primitive if the following criterion is fulfilled: The UE estimates the DPCCH quality over the previous 40 ms period to be better than a threshold Qin. This criterion shall be assumed no collected. Qin is defined implicitly by the relevant tests. (def. 20% BER) . (The mapping of the Q_IN values to the actual physical channel
Phase 2: -Starts 160 ms after the downlink dedicated channel is considered established by higher layers with In-sync status -During this phase the criteria for the Out-of-sync and In-sync status are as follows Out-of-sync shall be reported using the CPHY-Out-of-Sync-IND primitive if either of the following criteria are fulfilled: - The UE estimates the DPCCH quality over the previous 160 ms period to be worse than a threshold Qout. Qout is defined implicitly by th - The 20 most recently received transport blocks with a CRC attached, as observed on all TrCHs using CRC, have been received with inco attached have been received with incorrect CRC. In case of no TFCI is used this criterion shall be considered only for TrCHs using CRC in
In-sync shall be reported using the CPHY-Sync-IND primitive if both of the following criteria are fulfilled: - The UE estimates the DPCCH quality over the previous 160 ms period to be better than a threshold Qin. Qin is defined implicitly by the r - At least one transport block with a CRC attached, as observed on all TrCHs using CRC, is received in a TTI ending in the current frame w CRC attached, this criterion shall be assumed to be fulfilled. In case of no TFCI is used this criterion shall be considered only for TrCHs us At least one TB in the last radio frame with correct CRC transmitted UE Sycnchronization Status
20 last TBs transmitted with incorrect CRC transmitted
Uplink synchronisation primitives
Layer 1 in the Node B shall every radio frame check synchronisation status of all radio link sets. Synchronisation status is indicated to the CPHY-Out-of Sync IND primitive. Hence, only one synchronisation status indication shall be given per radio link set.The exact criteria for i DPCCH quality or CRC checks. One example would be to have the same criteria as for the downlink synchronisation status primitives.
The establishment of a radio link can be divided into two cases: - when there is no existing radio link, i.e. when at least one downlink dedicated physical channel and one uplink dedicated physical cha - or when one or several radio links already exist, i.e. when at least one downlink dedicated physical channel is to be set up and an up
In Node B, each radio link set can be in three different states: initial state , out-of-sync state and in-sync state . Transitions between th explain more details below. 1. No existing radio link When one or several radio links are to be established and there is no existing radio link for the UE already, a dedicated physical channel i in downlink. This corresponds to the case when a dedicated physical channel is initially set up on a frequency. The radio link establishment is as follows: a) Node B considers the radio link sets which are to be set up to be in the initial state. UTRAN shall start the transmission of the downlink
The establishment of a radio link can be divided into two cases: - when there is no existing radio link, i.e. when at least one downlink dedicated physical channel and one uplink dedicated physical cha - or when one or several radio links already exist, i.e. when at least one downlink dedicated physical channel is to be set up and an up
In Node B, each radio link set can be in three different states: initial state , out-of-sync state and in-sync state . Transitions between th explain more details below. 1. No existing radio link When one or several radio links are to be established and there is no existing radio link for the UE already, a dedicated physical channel i in downlink. This corresponds to the case when a dedicated physical channel is initially set up on a frequency. The radio link establishment is as follows: a) Node B considers the radio link sets which are to be set up to be in the initial state. UTRAN shall start the transmission of the downlink transmitted.The initial downlink DPCCH transmit power is set by higher layers.Downlink TPC commands are generated. b) The UE establishes downlink chip and frame synchronisation of DPCCH, using the P-CCPCH timing and timing offset information notifi synchronisation word. Downlink synchronisation status is reported to higher layers every radio frame. c) If no activation time for uplink DPCCH has been signalled to the UE, uplink DPCCH transmission shall start when higher layers conside uplink DPCCH transmission shall not start before the downlink physical channel has been established and the activation time has been re d) UTRAN establishes uplink chip and frame synchronisation. Frame synchronisation can be confirmed using the frame synchronisation w in-sync indications are received from layer 1, when Node B shall trigger the RL Restore procedure indicating which radio link set has obtai shall be considered to be in the in-sync state.The RL Restore procedure may be triggered several times, indicating when synchronisation
2. One or several existing radio links When one or several radio links are to be established and one or several radio links already exist, there is an existing DPCCH/DPDCH in set up in the downlink. This corresponds to the case when new radio links are added to the active set and downlink transmission starts for
a) Node B considers new radio link sets to be set up to be in initial state. If a radio link is to be added to an existing radio link set this radio addition of the radio link, i.e. if the radio link set was in the in-sync state before the addition of the radio link it shall remain in that state. b) UTRAN starts the transmission of the downlink DPCCH/DPDCH at a frame timing such that the frame timing received at the UE will be the UE. Simultaneously, UTRAN establishes uplink chip and frame synchronisation of the new radio link. Frame synchronisation can be co in the initial state shall remain in the initial state until N_INSYNC_IND successive in-sync indications are received from layer 1, when Nod obtained synchronisation. When RL Restore is triggered the radio link set shall be considered to be in the in-sync state.The RL Restore pr obtained for different radio link sets. c) The UE establishes chip and frame synchronisation of the new radio link. Frame synchronisation can be confirmed using the frame syn layers every radio frame.
Radio Link Monitoring
Downlink Direction Uplink Direction
Downlink radio link failure/restore
The downlink radio links shall be monitored by the UE, to trigger radio link failure procedures. Radio link failure detection in DL is based on receiving N313 consecutive "out of sync" indications from layer 1 for the established DPCCH physical channel in FDD the UE ->start timer T313 ->upon receiving N315 successive "in sync" indications from layer 1 and upon change of UE state: ->stop and reset timer T313
In case of the expiry of T313 which means Radio Link Failure, how much time UE can re-establish a bearer. A bearer can be associated cell or URA update. T314 is controlling transparent and unacknowledged mode(UM) bearers. T315 is controlling acknowledged(AM) mode ->Timer T314 is started if radio bearer(s) that are associated with T314 exist or if only RRC connection exists, and stopped when the Cell ->Timer T315 is started only if radio bearer(s) that are associated with T315 exist, and stopped when the Cell Update procedure has been
If T314 expires and T305 is not running, then all radio bearers associated with radio bearers with T314 value are locally released. If additio
->start timer T313 ->upon receiving N315 successive "in sync" indications from layer 1 and upon change of UE state: ->stop and reset timer T313
In case of the expiry of T313 which means Radio Link Failure, how much time UE can re-establish a bearer. A bearer can be associated cell or URA update. T314 is controlling transparent and unacknowledged mode(UM) bearers. T315 is controlling acknowledged(AM) mode ->Timer T314 is started if radio bearer(s) that are associated with T314 exist or if only RRC connection exists, and stopped when the Cell ->Timer T315 is started only if radio bearer(s) that are associated with T315 exist, and stopped when the Cell Update procedure has been
If T314 expires and T305 is not running, then all radio bearers associated with radio bearers with T314 value are locally released. If additio
If T315 expires and T305 is not running, then all radio bearers associated with radio bearers with T315 value are locally released. If additio In case of the expiry of T314 (T315), the corresponding service Radio Bearers will be removed.
For UE in CELL_DCH state, In case of Radio link failure, if the Radio link cannot be successfully reconfigured by CELL UPDATE CONFIR resent for Radio link reconfiguration (this operation relates to T302 and N302). T314(T315) should be set greater than T302*N302
The timer T302 is started when UE transmits CELL UPDATE/URA UPDATE, and stopped when UE receives a CELL UPDATE CONFIRM/ UPDATE/URA UPDATE if the counter V302 is no bigger than the Maximum number of retransmissions of the CELL UPDATE / URA UPDA
Uplink radio link failure/restore
The uplink radio link sets are monitored by the Node B, to trigger radio link failure/restore procedures. Once the radio link sets have been those two states are described below. -The uplink radio link failure/restore criteria is based on the synchronisation status primitives CPHY-Sync-IND and CPHY-Out-of-Sync-IND synchronisation status indication shall be given per radio link set. -When the BTS L1 has detected N_INSYNC_IND consecutive indications with In-sync status, the radio link is moved from the initial state BTS L3 sends the NBAP:SYNCHRONIZATION INDICATION message to the RNC
-When the radio link set is in the in-sync state, Node B shall start timer T_RLFAILURE after receiving N_OUTSYNC_IND consecutive out receiving successive N_INSYNC_IND in-sync indications. If T_RLFAILURE expires, Node B shall trigger the RL Failure procedure and ind triggered, the state of the radio link set change to the out-of-sync state. During the Out-of-sync state, L1 keeps on searching the synchron released by the RNC with the NBAP:RADIO LINK DELETION message
-When the radio link set is in the out-of-sync state, after receiving N_INSYNC_IND successive in-sync indications Node B shall trigger the synchronisation. When the RL Restore procedure is triggered, the state of the radio link set change to the in-sync state. BTS L3 sends the
After the BTS has established the frame synchronization to the uplink DPCH, the transmission power of the downlink DPCH is controlled b downlink dedicated physical channel are based on the SIR measurements from the uplink DPCH. (The parameters Qin and Qout and N_I in the NBAP: CONFIGURATION DATA message)
Example of 3 common cases of L1 Synchonization
When the UE starts to set up the dedicated channel, it starts the T312 timer, and after the UE detects N312 synchronization indications fro has failed.
->When a physical dedicated channel establishment is initiated by the UE, the UE starts a timer T312 and wait for layer 1 to indicate N312 ->On receiving N312 "in sync" indications, the physical channel is considered established and the timer T312 is stopped and reset ->On the BTS side after receiving N_INSYNC_IND synchronization indicators the BTS sends NBAP: SYNCHRONIZATION INDICATION –
->When a physical dedicated channel establishment is initiated by the UE, the UE starts a timer T312 and wait for layer 1 to indicate N312 ->On receiving N312 "in sync" indications, the physical channel is considered established and the timer T312 is stopped and reset ->On the BTS side after receiving N_INSYNC_IND synchronization indicators the BTS sends NBAP: SYNCHRONIZATION INDICATION –
->In case UE is not able to establish synchronization within timer T312 it stops TX on the DCH ->In case BTS is not able to establish synchronization it does not send NBAP:Synchronization Indication –message to RNC The BTS tries to establish synchronization until timer in RNC expires and RNC sends NBAP:Radio Link Deletion -message
->In case BTS is able to establish synchronization it sends NBAP:Synchronization Indication –message to RNC ->In case UE is not able to establish synchronization within timer T312 it stops TX on the DCH ->As the UE TX is off the BTS looses the L1 synchronization and sends NPAB: Radio Link Failure –message to RNC After Timer expires in RNC the RNC sends NPAB: Radio Link Deletion to BTS which then stops searching for the synchronization
ng and control data to establish, maintain, and release connections. The UE gets informed about the radio bearer characteristics, the e and transmit data via the WCDMA radio interface. The RNC uses the NodeB Application Part (NBAP) protocol to inform the Node B
3.12.0: nformation, paging, RRC connection establishment and release, UE capability inquiry, security mode control, Inter-RAT handover
el and physical channel reconfiguration, physical channel failure, etc. can be found here. bility information, active set update, and various handover procedures are covered here.
ain identity. s are examples of data, associated with these IEs. rements, PDCP and FDD RF capabilities, radio access capabilities, cell update causes,etc. of a radio bearer, such as RB information to setup. cribed, such as the description of TFCs and TFCSs. h as the description of CCTrCHs or compressed mode information. xchanged here.
he UE and UTRAN.
e mode, and higher layer protocols in the UE request a signalling connection to UTRAN. Please note, that an RRC connection
ge RRC Connection Setup message. The UE gets all relevant parameters regarding the signalling bearers, transport channels, and
Node B must also get all relevant parameters to serve the UE on the radio interface adequately, and to relay data between the Iubes the UTRAN specific signalling protocol NBAP to send these parameters to the Node B.
e returned to the UE via a FACH.
plete message to the RNC, using the transport channel DCH. Beforehand it performed a L1 Synchronization.
an be found in this message:
one of the UE identity to use
RACH, because the measurement results are transmitted via the transport channel RACH. The measured quantity can be set by the , listed in the measurement result list, are ordered in accordance to the measurement results,
2.RRC Connection Setup message If the S-RNC accepts the UE„s RRC Connection Establishment request. It starts an interaction with the Node B to establish a radio link connection over the interface Iub. This interaction is also used to inform the Node B about the radio link configuration parameters for uplink and downlink transmission via the interface Uu. In other words, the Node B is fully prepared to serve as intermediate mode between the mobile phone and the RNC. The UE gets the radio link configuration parameters with the RRC Connection Setup message, which is transmitted in the transport channel FACH. This message is used to establish signalling radio bearers between the UE and the RNC. The RRC Connection Setup message is used to specify the (signalling) radio bearer, the transport channel and the physical channel characteristics both in the UL and downlink directions. The RRC Connection Setup message is sent from the RRC layer in the RNC to the RRC layer in the UE. The UE„s RRC uses management interfaces to the configure the „lower“ layers accordingly. -If only the physical layer characteristics are modified, then the RRC layer only has to interact with the PHY layer. A modification may affect scrambling and modulation. A new channelisation code may be deployed for the connection, which has no impact to the higher layers. The PHY layer is for instance responsible for radio measurements, and the RNC can change measurement quantities or threshold values. Again, this has no impact on the higher layers. -If the transport channels are modified, then this has an effect both on the MAC (Medium Access Control) layer and the PHY layer. The MAC layer is responsible for Transport Format selection, identification of UEs on the common and shared resources, ciphering and de-ciphering, random access control, etc. -If a radio bearer is established, or modified, then following layer instances may receive parameters: - Radio Link Control (RLC) layer – for each radio bearer, an RLC instance is established - , - Packet Data Convergence Protocol (PDCP) layer, Broadcast/Multicast Control (BMC) layer instances, - Medium Access Control (MAC) layer instances, and - PHY layer. With the RRC Connection Setup message, we establish several signalling radio bearers for the UE, so that we won„t see the PDCP layer and BMC layer relevant parameters.
PHY layer. The MAC layer is responsible for Transport Format selection, identification of UEs on the common and shared resources, ciphering and de-ciphering, random access control, etc. -If a radio bearer is established, or modified, then following layer instances may receive parameters: - Radio Link Control (RLC) layer – for each radio bearer, an RLC instance is established - , - Packet Data Convergence Protocol (PDCP) layer, Broadcast/Multicast Control (BMC) layer instances, - Medium Access Control (MAC) layer instances, and - PHY layer. With the RRC Connection Setup message, we establish several signalling radio bearers for the UE, so that we won„t see the PDCP layer and BMC layer relevant parameters.
which are established with this RRC message. teristics, in other words the TFCS. r the PHY layer to make the physical channels available. 1. RRC Connection Setup message: UE IEs: 1. Initial UE ID: The common transport channel FACH is used to send the RRC Connection Setup message from the RNC to the UE. All UEs listening to the same FACH bearing S-CCPCH must be capable to detect, whether the RRC message is for them. For UE identification, the IMSI or TMSI and LAI can be used. RRC Transaction ID: Several RRC transactions can run in parallel. This number associates the message to one transaction. 2. Activation Time: The transmission of transport channel frames has to be synchronised between the UE and the S-RNC. This is also called L2 synchronisation. The Connection Frame Number (CFN) is an element of the L2 synchronisation. The network has to make sure, that the UE gets a radio frame with a specific CFN (approximately) To = 1024 chips before is starts to send a radio frame with the same CFN. The Activation Time indicates, when the UE can expect the transmission to start. 3. New U-RNTI and New C-RNTI: Common transport channels are shared resources, which can be used by several UEs. The MAC-layer will add the required addressing information U-RNTI and C-RNTI. UE, S-RNC, CRNC and Node B identify each other by called Radio Network Temporary Identifiers (RNTI). The S-RNC allocates a S-RNTI to the UE to address the UE. When the UE accesses a new cell, the C-RNC allocates aC-RNTI to the UE, with which it addresses the UE. The U-RNTI is a concatenation of the S-RNTI and the S-RNC„s RNC-ID. The U-RNTI is unique worldwide, and is used by the S-RNC to address the UE on common radio channels, during paging, etc. 4. RRC State Indicator: This indicator tells the UE, in which internal RRC connected sub-state is has to move to. 5. Capability Update Requirement: 2.RRC Connection Setup message: RB IEs: Radio Bearer (RB) services are offered to the higher layers. Higher layers are: -RRC layer, which uses signalling radio bearers to exchange radio link management messages between the UE and the RNC. The RRC layer also takes NAS-signalling information to guarantee its transport in signalling radio bearers. -NAS layers for user SDU transfer. When the RRC Connection Setup message is sent from the RNC to the UE, then the RB IEs describe, how the Radio Link Control layer(RLC) has to make the radio bearer service available to the RRC layer. RLC sub-layer's tasks: For each RB, and RLC instance is established. Three different types are distinguished: 1.Transparent Mode (TrM) RLC entities In this mode, data is buffered, when it arrives in the RLC entity. Segmentation at the transmitting RLC entity and re-assembly at the receiving RLC entity may occur, if being configured by higher layers and the RLC SDU is larger than required by the lower layers, given the TTI. No other service is offered. 2. Unacknowledged Mode (UM) RLC entities Data transfer, segmentation and reassembly is done like in the TrM. But higher layer data is transmitted without guaranteeing its delivery. Sequence control and ciphering are. 3.Acknowledged Mode (AM) RLC entities A reliable bearer is offered in this mode. Its features can be seen in the figure on the right hand side.
Signalling radio bearers have to be set up. Three signalling radio bearers must be set up, the 4th one is optional. This is indicated with the IE Signalling RB to Setup List. Given the number, either 3 or 4 descriptions of radio bearers follow. They contain information, which must be made available for the RLC sub-layer. -RB identity: Each RB has a unique identity. The identities for signalling radio bearers are ranging from 1 to 4. The total number of RBs, the UE can establish on command of the RNC, is 32. RB0 parameters are not transmitted,because there are fixed rules how to determine its RLC parameters. -Choice RLC info type: a RB is described: This is the case with the IE RLC info. Or its parameters are copied from an existing one, where only the RB identity has to be delivered to the UE. -RB mapping info Uplink, following transport channel types can be identified: DCH, RACH, and CPCH The mapping information describes, on which Transport Channels the given RB can be mapped to. UL DCH are get an identity (number). This number is used to describe, to which UL DCHs the RB can be mapped. Downlink, we can identify following transport channel types: DCH, FACH, DSCH and DCH + DSCH. DSCH and DCH receive an identity. There can be one or two logical channels per radio bearer or RLC entity. Therefore, there are also logical channel identities.
two logical channels. This was part of the RB setup information. The information carried on radio bearers must be smitted? How can higher layer information be segmented? This is described with the information elements for
describes the the allowed TFs, which can be transmitted via this TrCH.This information element also describes,
er entity. RLC PDUs from several RBs (RLC layers) can be multiplexed on one transport channel. The MAC header of a MAC PDU plexed on one DCH, then field C/T is added in the MAC header to identify the logical channel, to which
CPCH, DSCH.
he physical channels. One of the PhyCH IEs is the carrier frequency band, where the signalling connection is nalling bearer setup. Also the available UL and DL radio resources have to be described.
p message. When we have a closer look to the IE „Downlink information common for all radio links“, we detect
measurements on neighbouring cells and at the same time receive data from the active set cells. If this is the case, e, this mode is often called Slotted Mode. In order to transmit still the user data with a given data rate, more hort while. active set cells receive the UE„s signals, only one is making a transmission downlink. The UE tells the active set
e B, so that this device can decide, how to set the weighting to the individual antennas. There are two different soereby, the feedback command rate is 1 bit per timeslot. - closed loop mode 2: Phase and amplitude adjustments
3. RRC Connection Setup Complete message The UE has received the RRC Connection Setup message and returns the RRC Connection Setup Complete message to the S-RNC. This message is transmitted via the logical channel DCCH on the radio signalling bearer, which offers acknowledged mode of operation (RB2). The information elements in the RRC Connection Setup Complete message can be grouped into -UE information elements and -Other information elements. The UE can return its capabilities to the S-RNC with the IE Radio Access Capability, which contains -Transport channel capability: is distributed to the resource manager and to the admission control entity -RF capability: the RF capability is distributed to the resource manager, the power control entity and to the handover control entity -Physical channel entity: is distributed to resource manager -UE multi-mode/multi-RAT capability -Security capability -LCS capability -Measurement capability: is distributed to the handover control entity. Presence is mandatory if IE Multi-mode capability has the value "FDD" or "FDD/TDD" and a FDD capability update has been requested in a previous message. Otherwise this field is not needed in the message. Among the optional other information elements, we find the Inter_RAT UE access capability. The RNC shall extract the inter-system message from the UE CAPABILITY INFORMATION message and transfer it to the handover control entity.
has the value "FDD" or "FDD/TDD" and a FDD capability update has been requested in a previous message. Otherwise this field is not needed in the message. Among the optional other information elements, we find the Inter_RAT UE access capability. The RNC shall extract the inter-system message from the UE CAPABILITY INFORMATION message and transfer it to the handover control entity.
timer will be stopped after the UE receives RRC CONNECTION SETUP message. Once the timer times out, if RRC CONNECTION UE repeats RRC CONNECTION REQUEST; otherwise it will be in the idle mode,consider the procedure to be unsuccessful. The
UE identity" equal to the value of the variable INITIAL_UE_IDENTITY; and if cell re-selection or expiry of timer T300 occurs;
CCCH;
status of radio links, both in uplink and downlink. ed channels in order to detect a loss of the signal on Layer 1, as specified in TS 25.214. The synchronization state of R is the relation of the incorrectly detected pilot bits to the total number of pilot bits in a radio frame),the thresholds n its power on respectively. The synchronisation status is reported to the higher layer.
the downlink dedicated channel is considered established by higher layers
llowing criterion is fulfilled: This criterion shall be assumed not to be fulfilled before 40 ms of DPCCH quality measurements have been es to the actual physical channel BER is given in 3GPP TS 25.133)
ync status
criteria are fulfilled: out. Qout is defined implicitly by the relevant tests(def. 15% BER) CRC, have been received with incorrect CRC. In addition, over the previous 160 ms, all transport blocks with a CRC dered only for TrCHs using CRC in all transport formats.
ulfilled: n. Qin is defined implicitly by the relevant tests(def.20% BER) a TTI ending in the current frame with correct CRC. If no transport blocks are received, or no transport block has a all be considered only for TrCHs using CRC in all transport formats.
last TBs transmitted with incorrect CRC transmitted
Initial state RL Restore RL Failure In-sync state
Out-of-sync state RL Restore
NodeB Radio Link Set States and Transistions
onisation status is indicated to the RL Failure/Restored triggering function using either the CPHY-Sync-IND or adio link set.The exact criteria for indicating in-sync/out-of-sync is not subject to specification, but could e.g. be based on received nchronisation status primitives.
one uplink dedicated physical channel are to be set up; channel is to be set up and an uplink dedicated physical channel already exists.
ync state . Transitions between the different states is shown in figure above. The establishment of a radio link is
dy, a dedicated physical channel is to be set up in uplink and at least one dedicated physical channel is to be set up uency. the transmission of the downlink DPCCH and may start the transmission of DPDCH if any data is to be
one uplink dedicated physical channel are to be set up; channel is to be set up and an uplink dedicated physical channel already exists.
ync state . Transitions between the different states is shown in figure above. The establishment of a radio link is
dy, a dedicated physical channel is to be set up in uplink and at least one dedicated physical channel is to be set up uency.
the transmission of the downlink DPCCH and may start the transmission of DPDCH if any data is to be are generated. and timing offset information notified from UTRAN. Frame synchronisation can be confirmed using the frame
l start when higher layers consider the downlink physical channel established. If an activation time has been given, nd the activation time has been reached. The initial uplink DPCCH transmit power is set by higher layers. using the frame synchronisation word. Radio link sets remain in the initial state until N_INSYNC_IND successive ating which radio link set has obtained synchronisation. When RL Restore has been triggered the radio link set , indicating when synchronisation is obtained for different radio link sets.
is an existing DPCCH/DPDCH in the uplink, and at least one corresponding dedicated physical channel shall be nd downlink transmission starts for those radio links.The radio link establishment is as follows:
an existing radio link set this radio link set shall be considered to be in the state the radio link set was prior to the ink it shall remain in that state. e timing received at the UE will be within T0 +/- 148 chips prior to the frame timing of the uplink DPCCH/DPDCH at . Frame synchronisation can be confirmed using the frame synchronization word. Radio link sets considered to be e received from layer 1, when Node B shall trigger the RL Restore procedure indicating which radio link set has he in-sync state.The RL Restore procedure may be triggered several times, indicating when synchronisation is
be confirmed using the frame synchronization word. Downlink synchronisation status shall be reported to higher
Downlink Direction Uplink Direction
failure detection in DL is based on counter N313 (counting “out of sync” indicator) and timer T313 in UE. In CELL_DCH State, after hannel in FDD the UE
earer. A bearer can be associated with a bearer re-establishment timer (T314 and T315), which defines the time to re-establish it after a ntrolling acknowledged(AM) mode bearers exists, and stopped when the Cell Update procedure has been completed. e Cell Update procedure has been completed.
alue are locally released. If additionally T315 is not running, the UE is moved to the RRC idle mode.
earer. A bearer can be associated with a bearer re-establishment timer (T314 and T315), which defines the time to re-establish it after a ntrolling acknowledged(AM) mode bearers exists, and stopped when the Cell Update procedure has been completed. e Cell Update procedure has been completed.
alue are locally released. If additionally T315 is not running, the UE is moved to the RRC idle mode.
alue are locally released. If additionally T314 is not running, the UE is moved to the RRC idle mode.
gured by CELL UPDATE CONFIRM before the expiry of the corresponding T314 (or T315), CELL UPDATE will be et greater than T302*N302
eives a CELL UPDATE CONFIRM/URA UPDATE CONFIRM. When it expires, UE should retransmit CELL of the CELL UPDATE / URA UPDATE message N302, else, goes to idle mode
nce the radio link sets have been established, they will be in the in-sync or out-of-sync states. Transitions between
c-IND and CPHY-Out-of-Sync-IND, indicating in-sync and out-of-sync respectively. Note that only one
ink is moved from the initial state to an In-sync state. L1 informs BTS L3 about the established synchronization and
_OUTSYNC_IND consecutive out-of-sync indications. Node B shall stop and reset timer T_RLFAILURE upon r the RL Failure procedure and indicate which radio link set is out-of-sync. When the RL Failure procedure is keeps on searching the synchronization as long as the synchronization has been re-established or the radio link is
ndications Node B shall trigger the RL Restore procedure and indicate which radio link set has re-established he in-sync state. BTS L3 sends the NBAP:SYNCHRONIZATION INDICATION message to the RNC
the downlink DPCH is controlled based on the TPC bits transmitted by the UE. Also, the TPC bits transmitted in the parameters Qin and Qout and N_INSYNC_IND, N_OUTSYNC_IND, T_RLFAILURE are given by the RNC to the BTS
312 synchronization indications from L1, it will stop the T312 timer. Once the timer times out, it means that the physical channel setup
Successful Synchronization on UL and DL Downlink Direction Uplink Direction
nd wait for layer 1 to indicate N312 "in sync" indications T312 is stopped and reset NCHRONIZATION INDICATION –message to RNC after which the closed loop and outer loop PC start to control the powers
nd wait for layer 1 to indicate N312 "in sync" indications T312 is stopped and reset NCHRONIZATION INDICATION –message to RNC after which the closed loop and outer loop PC start to control the powers
Failed Synchronization on UL and DL Downlink Direction Uplink Direction
n –message to RNC Deletion -message
to RNC
sage to RNC ng for the synchronization
ULSynchronization failed because of no DL synchronization
Downlink Direction Uplink Direction
Click to return to main page
>>See More details of 1,2,3
>>Synchronization Parameters Description (Module II)
Click to return to main page
Radio Bearer(RB) Procedures The RB control procedures are used to establish additional radio bearers, modify them, or release them. Radio Bearer is established, modified, and released with following RRC messages: 1.Radio Bearer Setup, 2.Radio Bearer Reconfiguration, and 3.Radio Bearer Release. If a radio bearer is setup or reconfigured, not only the RB parameters, but also the transport channel and physical channel parameters have to be set or modified. It is possible to modify the transport channel configuration. If this is done, the accessory RB parameters are not affected. But a transport channel modification always has an impact on the physical channel setting. A transport channel reconfiguration is triggered with the RRC message. 4. Transport Channel Reconfiguration It is also possible to modify the physical channel characteristics of a radio bearer only. One example is a channelisation code re-allocation. This is done with the RRC message 5. Physical Channel Reconfiguration. Every RRC request, which is mentioned above, can be conducted successfully or fail.
Physical Channel Reconfiguration-on existing RBs
RB Setup, Reconfiguration, and Release
Transport Channel Reconfiguration-on existing RBs
Click to return to main page
Measurement procedures
The UE measurements are grouped into 7 different categories, according to what the UE should measure. (TS 25.331-360) The different types of measurements are: - Intra-frequency measurements: measurements on downlink physical channels at the same frequency as the active set. - Inter-frequency measurements: measurements on downlink physical channels at frequencies that differ from the frequency of the ac - Inter-RAT measurements: measurements on downlink physical channels belonging to another radio access technology than UTRAN, - Traffic volume measurements: measurements on uplink traffic volume. - Quality measurements: Measurements of quality parameters, e.g. downlink transport block error rate. - UE-internal measurements: Measurements of UE transmission power and UE received signal level. - UE positioning measurements: Measurements of UE position.
The UE shall support a number of measurements running in parallel. The UE shall also support that each measurement is controlled an
Cells that the UE is monitoring (e.g. for handover measurements) are grouped in the UE into three different categories: 1. Cells, which belong to the active set: User information is sent from all these cells. In FDD, the cells in the active set are involved in 2. Cells, which are not included in the active set, but are monitored according to a neighbour list assigned by the UTRAN belong 3. Cells detected by the UE, which are neither included in the active set nor in the monitored set belong to the detected set. Repo measurements made by UEs in CELL_DCH state.
Measurement Control and Measurement Report
UTRAN controls the measurements in the UE, either by : -broadcasting system information on the BCCH, and/or by -transmitting a Measurement Control message on the DCCH. If the UE is in the RRC idle mode, it receives relevant measurement information from the BCCH. The SIB type 3 contains parameters control information to the UE for the serving cell. SIB 3 and SIB 11are read and valid in the RRC idle state.
If the UE is in the RRC sub-states CELL_FACH, CELL_PCH and URA_PCH, it is connected to one cell only and responsible for cell s type 4. The measurement control information is broadcasted with SIB type 12. SIB 4 and SIB 12 are read and valid, when the UE is in th not broadcasted, then SIB 3 resp. SIB 11 parameters are used instead. In the sub-state CELL_DCH, the UE is not reading the SIB type be still valid in this state.
If the UE is in the RRC sub state CELL_DCH ,the RRC message Measurement Control can be transmitted to the UE. This message measurement command links a measurement with a measurement identity, quantity, objects, reporting quantities, reporting criteria, type
How does a UE perform measurements after a transition in the CELL_DCH state. Two cases have to be distinguished: 1. Transition from the RRC idle state to the CELL_DCH sub-state In the RRC idle state, the UE retrieved the measurement control parameters from the SIB type 11. Information Elements, which contain system information, may be included in the SIB 11. If they are included, the UE can send a measurement report, when a measurement r Control message including one of the above mentioned measurement types, it replaces its internal stored data based on the SIB11 by t
2.Transition from the CELL_FACH to the CELL_DCH sub-state. In the CELL_FACH sub-state, the SIB 12 (or SIB 11, if there is no SIB 12) is valid including all relevant measurement control parameters valid, as long as there was no Measurement Control message, which replaces the parameters. But what happens, if the UE was in the it then transits to the CELL_FACH sub-state. In the CELL_FACH sub-state, the UE reads SIB 12 (SIB 11), and its measurement control CELL_DCH sub-state, the UE resumes with the measurements and associated reporting, as they they were stored before the transition
1. Transition from the RRC idle state to the CELL_DCH sub-state In the RRC idle state, the UE retrieved the measurement control parameters from the SIB type 11. Information Elements, which contain system information, may be included in the SIB 11. If they are included, the UE can send a measurement report, when a measurement r Control message including one of the above mentioned measurement types, it replaces its internal stored data based on the SIB11 by t
2.Transition from the CELL_FACH to the CELL_DCH sub-state. In the CELL_FACH sub-state, the SIB 12 (or SIB 11, if there is no SIB 12) is valid including all relevant measurement control parameters valid, as long as there was no Measurement Control message, which replaces the parameters. But what happens, if the UE was in the it then transits to the CELL_FACH sub-state. In the CELL_FACH sub-state, the UE reads SIB 12 (SIB 11), and its measurement control CELL_DCH sub-state, the UE resumes with the measurements and associated reporting, as they they were stored before the transition
Measurement Control Contents
UTRAN may control a measurement in the UE either by broadcast system information and/or by transmitting a MEASUREMENT information:
1. Measurement identity: A reference number that should be used by the UTRAN when setting up, modifying or releasing the measure 2. Measurement command: One out of three different measurement commands. - Setup: Setup a new measurement. - Modify: Modify a previously defined measurement, e.g. to change the reporting criteria. - Release: Stop a measurement and clear all information in the UE that are related to that measurement. 3. Measurement type: One of the types listed above describing what the UE shall measure.Presence or absence of the following contro 4. Measurement objects: The objects the UE shall measure, and corresponding object information. 5. Measurement quantity: The quantity the UE shall measure. This also includes the filtering of the measurements. 6. Reporting quantities: The quantities the UE shall include in the report in addition to the quantities that are mandatory to report for th 7. Measurement reporting criteria: The triggering of the measurement report, e.g. periodical or event-triggered reporting. 8. Measurement Validity: Defines in which UE states the measurement is valid.
2. Measurement command: One out of three different measurement commands. - Setup: Setup a new measurement. - Modify: Modify a previously defined measurement, e.g. to change the reporting criteria. - Release: Stop a measurement and clear all information in the UE that are related to that measurement. 3. Measurement type: One of the types listed above describing what the UE shall measure.Presence or absence of the following contro 4. Measurement objects: The objects the UE shall measure, and corresponding object information. 5. Measurement quantity: The quantity the UE shall measure. This also includes the filtering of the measurements. 6. Reporting quantities: The quantities the UE shall include in the report in addition to the quantities that are mandatory to report for th 7. Measurement reporting criteria: The triggering of the measurement report, e.g. periodical or event-triggered reporting. 8. Measurement Validity: Defines in which UE states the measurement is valid. 9. Measurement reporting mode: This specifies whether the UE shall transmit the measurement report using AM or UM RLC. 10. Additional measurement identities: A list of references to other measurements. When this measurement triggers a measurement referenced by the additional measurement identities.
Reception of Measurement Control by the UE
The UTRAN may request a measurement by the UE to be setup, modified or released with a MEASUREMENT CONTROL message, wh capabilities into account when a measurement is assigned to the UE.
When a new measurement is initiated, UTRAN should set the IE "Measurement identity" to a value, which is not used for other measure of setting several "Measurement identity" within a same "Measurement type", "Measurement object" can be set differently for each meas When a current measurement is modified or released, UTRAN should set the IE "Measurement identity" to the value, which is used for t identity", it is not needed for UTRAN to indicate the IEs other than modifying IEs, and the UE continues to use the current values of the I
Upon reception of a MEASUREMENT CONTROL message the UE shall perform following actions : The UE shall: - read the IE "Measurement command"; if the IE "measurement command" has the value "setup": - store this measurement in the variable MEASUREMENT_IDENTITY according to the IE "measurement identity"; - for measurement types "inter-RAT measurement" or "inter-frequency measurement": -->if, according to its measurement capabilities, the UE requires compressed mode to perform the measurements and a compressed mo simultaneously activated by the IE "DPCH compressed mode status info"; or -->if, according to its measurement capabilities, the UE does not require compressed mode to perform the measurements: begin measu identity; - for any other measurement type: begin measurements according to the stored control information for this measurement identity. if the IE "Measurement command" has the value "modify": - for all measurement control present in the MEASUREMENT CONTROL message: --> replace the corresponding information stored in variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "m --> resume the measurements according to the new stored measurement control information. if the IE "measurement command" has the value "release": - terminate the measurement associated with the identity given in the IE "measurement identity"; - clear all stored measurement control information related associated to this measurement identity in variable MEASUREMENT_IDENTI if the IE "DPCH Compressed Mode Status Info" is present, the UE shall: - if pattern sequence corresponding to IE "TGPSI" is already active (according to "TGPS Status Flag"): deactivate this pattern sequence received in the message; - after the time indicated by IE "TGPS reconfiguration CFN" has elapsed: -->activate the pattern sequence stored in the variable TGPS_IDENTITY corresponding to each IE "TGPSI" for which the "TGPS status -->begin the inter-frequency and/or inter-RAT measurements corresponding to the pattern sequence measurement purpose of each acti -->if the values of IE "TGPS reconfiguration CFN" and IE "TGCFN" are equal:start the concerned pattern sequence immediately at that C - not alter pattern sequences stored in variable TGPS_IDENTITY, but not identitifed in IE "TGPSI" - clear the entry for the MEASUREMENT CONTROL message in the table "Accepted transactions" in the variable TRANSACTIONS; - And the procedure ends.
Measurement Report Procedures The purpose of the measurement reporting procedure is to transfer measurement results from the UE to UTRAN. Initiation: In CELL_DCH state, the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH when the reporting measurements that are being performed in the UE.
In CELL_FACH state, the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH when the reporting traffic volume measurement that is being performed in the UE.
In CELL_PCH or URA_PCH state, the UE shall first perform the cell update procedure, using the cause "uplink data transm MEASUREMENT REPORT message on the uplink DCCH when the reporting criteria stored in variable MEASUREMENT_ID performed in the UE.
measurements that are being performed in the UE.
In CELL_FACH state, the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH when the reporting traffic volume measurement that is being performed in the UE.
In CELL_PCH or URA_PCH state, the UE shall first perform the cell update procedure, using the cause "uplink data transm MEASUREMENT REPORT message on the uplink DCCH when the reporting criteria stored in variable MEASUREMENT_ID performed in the UE.
The reporting criteria are fulfilled if either: - the first measurement has been completed for a newly initiated measurement with periodic reporting; or - the time period indicated in the stored IE "Periodical reporting" has elapsed since the last measurement report was transm - an event in stored IE "Measurement reporting criteria" was triggered. Events and triggering of reports for different measure For the measurement, which triggered the MEASUREMENT REPORT message, the UE shall: - set the IE "measurement identity" to the measurement identity, which is associated with that measurement in variable MEA - set the IE "measured results" to include measurements according to the IE "reporting quantity" of that measurement stored --> if all the reporting quantities are set to "false": not set the IE "measured results"; - set the IE "Measured results" in the IE "Additional measured results" according to the IE "reporting quantity" for all measur "additional measurements" stored in variable MEASUREMENT_IDENTITY of the measurement that triggered the measurem --> if more than one additional measured results are to be included:sort them in ascending order according to their IE "meas - if the MEASUREMENT REPORT message was triggered by an event (i.e. not a periodical report):set the IE "Event results The UE shall: - transmit the MEASUREMENT REPORT message on the uplink DCCH using either AM or UM RLC according to the stored that triggered the report. When the MEASUREMENT REPORT message has been submitted to lower layers for transmission: -The procedure ends.
hould measure. (TS 25.331-360)
equency as the active set. that differ from the frequency of the active set. radio access technology than UTRAN, e.g. PDC or GSM.
or rate. level.
hat each measurement is controlled and reported independently of every other measurement.
to three different categories: he cells in the active set are involved in soft handover. our list assigned by the UTRAN belong to the monitored set. ed set belong to the detected set. Reporting of measurements of the detected set is only required for intra-frequency
H. The SIB type 3 contains parameters for cell selection and re-selection. In parallel, the SIB type 11 is used to deliver measurement idle state.
o one cell only and responsible for cell selection and re-selection. It retrieves the parameters for cell selection from SIB are read and valid, when the UE is in the CELL_FACH, CELL_PCH and URA_PCH sub-state. If SIB 4 resp. SIB 12 is DCH, the UE is not reading the SIB type 3/4 and 11/12. The parameters of SIB 12 (SIB 11, if SIB is not available) can
e transmitted to the UE. This message informs the UE about the type of measurement, which has to be conducted. Each orting quantities, reporting criteria, type, etc.
es have to be distinguished:
1. Information Elements, which contain intra-frequency, inter-frequency, inter-RAT and traffic volume measurement urement report, when a measurement reporting criteria is fulfilled. As soon as the UE receives a Measurement nal stored data based on the SIB11 by the parameters delivered with the Measurement Control message.
evant measurement control parameters. If the UE transits to the CELL_DCH sub-state, the system information stays But what happens, if the UE was in the CELL_DCH sub-state, it has received Measurement Control messages, and (SIB 11), and its measurement control parameters become valid. But when the UE then transits back to the y they were stored before the transition to the CELL_FACH (or any other RRC connected) sub-state.
1. Information Elements, which contain intra-frequency, inter-frequency, inter-RAT and traffic volume measurement urement report, when a measurement reporting criteria is fulfilled. As soon as the UE receives a Measurement nal stored data based on the SIB11 by the parameters delivered with the Measurement Control message.
evant measurement control parameters. If the UE transits to the CELL_DCH sub-state, the system information stays But what happens, if the UE was in the CELL_DCH sub-state, it has received Measurement Control messages, and (SIB 11), and its measurement control parameters become valid. But when the UE then transits back to the y they were stored before the transition to the CELL_FACH (or any other RRC connected) sub-state.
The Measurement Control is used to setup, to modify, and to release a measurement in the UE. The UE gets all relevant information, how to perform a specific type of measurements. A measurement is either conducted periodically or driven by an event. Then, the UE returns a measurement report. The Measurement Control message is transmitted on a DCCH via an RLC entity in the acknowledged mode. I.e. the UE is either in the RRC connected sub-state CELL_DCH or CELL_FACH. If the setup of a measurement fails, the UE returns the RRC message Measurement Control Failure. It is transmitted on an UL DCCH via an RLC entity in the acknowledged mode. The RRC message Measurement Report was specified to deliver measurement results from the UE to UTRAN (RNC). This message is transmitted on a DCCH. The RLC entity can be in the acknowledged or unacknowledged mode. The RLC entity mode is set by the RRC message Measurement Control. Measurement results can be only transmitted in the CELL_DCH or CELL_FACH sub-state. - CELL_DCH: If a reporting criterion is met, the UE transmits a Measurement Report. A measurement identity identifies the measurement as specified by UTRAN. It includes measurement quantities and identifies the measurement event. -CELL_FACH: In this sub-state, traffic volume measurements and positioning measurements are reported by the UE. Intra-frequency measurements are reported via the RACH, whereby the UE learns from the BCCH (SIB11 or SIB12) the maximum numbers of cells, it can report. -CELL_PCH or URA_PCH: UE must perform a cell update. Cell update cause is „uplink data transmission“. Then they are in the CELL_FACH state, where the Measurement Report can be sent. The measurement report either holds traffic volume measurements or positioning measurements.
There is a set of different types of measurements, which can be conducted: -Intra-Frequency Measurements -Inter-Frequency Measurements -Inter-RAT Measurements -UE-Internal Measurements -Traffic Volume Measurements -Quality Measurements -UE Positioning Methods As a consequence, a UE may be forced to conduct several different types of measurements simultaneously. Each type of measurement is identified by an allocated „Measurement Identity“. Some measurements are not conducted continuously. UTRAN tells the UE once, how to perform a type of measurements. Whenever necessary, it just informs the UE to conduct the measurements of a measurement type by just telling it the associated measurement identity. In the RRC message Measurement Control, the is an PhyCH information elements, where the UE can gain DPCH compressed mode status information
or by transmitting a MEASUREMENT CONTROL message. The latter message includes the following measurement control
up, modifying or releasing the measurement and by the UE in the measurement report.
rement. ence or absence of the following control information depends on the measurement type ion. the measurements. tities that are mandatory to report for the specific event. event-triggered reporting.
rement. ence or absence of the following control information depends on the measurement type ion. the measurements. tities that are mandatory to report for the specific event. event-triggered reporting.
nt report using AM or UM RLC. measurement triggers a measurement report, the UE shall also include the reporting quantities for the measurements In i ti al s ta te RL
Restore RL
Fai l ure
In s y nc s ta te
O RL
ut of s y nc s ta te
Restore
ASUREMENT CONTROL message, which is transmitted on the downlink DCCH using AM RLC.The UTRAN should take the UE
ue, which is not used for other measurements. UTRAN may use several "Measurement identity" for the same "Measurement type". In case ect" can be set differently for each measurement with different "Measurement identity ". dentity" to the value, which is used for the measurement being modified or released. In case of modifying IEs within a "Measurement tinues to use the current values of the IEs that are not modified.
ctions :
urement identity";
e measurements and a compressed mode pattern sequence with an appropriate measurement purpose is
rform the measurements: begin measurements according to the stored control information for this measurement
on for this measurement identity.
ated to the identity indicated by the IE "measurement identity";
y in variable MEASUREMENT_IDENTITY.
Flag"): deactivate this pattern sequence at the beginning of the frame indicated by IE "TGPS reconfiguration CFN"
E "TGPSI" for which the "TGPS status flag" is set to "active" at the time indicated by IE "TGCFN"; and nce measurement purpose of each activated pattern sequence; pattern sequence immediately at that CFN;
" s" in the variable TRANSACTIONS;
results from the UE to UTRAN.
he uplink DCCH when the reporting criteria stored in variable MEASUREMENT_IDENTITY are met for any ongoing
the uplink DCCH when the reporting criteria stored in variable MEASUREMENT_IDENTITY are met for any ongoing
using the cause "uplink data transmission", in order to transit to CELL_FACH state and then transmit a ored in variable MEASUREMENT_IDENTITY are fulfilled for any ongoing traffic volume measurement which is being
the uplink DCCH when the reporting criteria stored in variable MEASUREMENT_IDENTITY are met for any ongoing
using the cause "uplink data transmission", in order to transit to CELL_FACH state and then transmit a ored in variable MEASUREMENT_IDENTITY are fulfilled for any ongoing traffic volume measurement which is being
odic reporting; or ast measurement report was transmitted for a given measurement; or ering of reports for different measurement types e UE shall: h that measurement in variable MEASUREMENT_IDENTITY; quantity" of that measurement stored in variable MEASUREMENT_IDENTITY; and
E "reporting quantity" for all measurements associated with the measurement identities included in the IE urement that triggered the measurement report; and ng order according to their IE "measurement identity" in the MEASUREMENT REPORT message; ical report):set the IE "Event results" according to the event that triggered the report.
M or UM RLC according to the stored IE "measurement reporting mode" associated with the measurement identity
for transmission:
of s y nc ta te
Click to return to main page
Paging
Paging includes CN orignated paging
The CN originated paging precedure: and non co-ordination paging. The CN perform the UTRAN co-ordination pagin -Co-ordination paging, the RNC shall besides the paging domain connection. message shall be transmitted on the alr URA_PCH state,the paging message sh shall be transmitted on the PCCH. -Non-co-ordinating paging, the RNC n besides the paging domain connection specified paging area.
The UTRAN orignated paing : The UT a cell update procedure to enable the tr a UE to trigger reading of updated syste
For a UE in idle mode or in CELL_PCH a PAGING TYPE 1 message on the PC paging procedure by transmitting a PAG
In UTRAN, we distinguish two different types of paging, depending on the existence of a RL connection between UE and UTRAN
Paging Type 1 -The RRC message Paging Type 1 is used, when a paging message has to be transmitted to a UE, which is either in the CELL_PCH or URA_PCH. There are several reasons, why this paging message type is initiated.
-Upper layers request the setup of an RRC signalling connection. This may be the cause, when a paging message from the CN has to be Cause to the the paging message. Higher layers may also initiate paging, when user data has to be transmitted on an existing ps connec UEs in the CELL_PCH and URA_PCH sub-states to establish a connection before forwarding the user data.
-UTRAN wants to trigger a cell update for UEs in the CELL_PCH or URA_PCH sub-state. -UTRAN wants to notify UEs in the RRC idle mode and in the RRC connected mode CELL_PCH and URA_PCH about system informatio
The UE monitors the paging channels (S-CCPCHs carrying PCCH) on all paging occasions. If the UE receives a paging message, it read message. If so, it returns a paging response. The UTRAN may repeat the transmission of a PAGING TYPE 1 message to a UE on sever occasion on the to increase the probability of proper reception of a page
Paging Type 2- This RRC message is used, when the UE is in the CELL_DCH or CELL_FACH state, i.e., when at least dedicated cont One example: The user is serving in the Internet, and due to the high download, the RNC has allocated one DDCH and one DCCH to the SGSN exists, and between the two network elements, dedicated transmission resources are available for the user. While the subscriber message to all RNCs, which participate in the LA where the UE is registered. This paging message is received by a RNC, which is curren paging request to the UE. Therefore, Paging Type 2 is often called dedicated paging.
Paging Message Type 1
Click to return to main page
"Or"
Paging Message Type 2
Click to return to main page
>>Paging Procedure and Param
aging includes CN orignated paging and UTRAN originated paging
he CN originated paging precedure: is used to establish a signaling connection. It is divided into co-ordination paging nd non co-ordination paging. The CN indicates in the RANAP paging message whether the RNC shall erform the UTRAN co-ordination paging Co-ordination paging, the RNC shall check whether the UE has other CN domain signaling connections esides the paging domain connection. If so and the UE is in Cell_DCH or Cell_FACH state, the paging essage shall be transmitted on the already connected DCCH on the radio interface. if so and the UE is in Cell_PCH or RA_PCH state,the paging message shall be transmitted on the PCCH on the radio interface. If no, the paging message hall be transmitted on the PCCH. Non-co-ordinating paging, the RNC need not check whether the UE has other CN domain signaling connections esides the paging domain connection but directly transmit the paging message on the PCCH in the CN pecified paging area.
he UTRAN orignated paing : The UTRAN may initiate paging for a UE in Cell_PCH or URA_PCH state to trgiger cell update procedure to enable the transition to Cell_FACH state. In additon,the UTRAN may initiate paging for UE to trigger reading of updated system information.
or a UE in idle mode or in CELL_PCH or URA_PCH state, the RNC initiates the paging procedure by transmitting PAGING TYPE 1 message on the PCCH. For a UE in CELL_FACH or CELL_DCH state, the RNC initiates the aging procedure by transmitting a PAGING TYPE 2 message on the DCCH
connection between UE and UTRAN.
nsmitted to a UE, which is either in the RRC idle mode, or in the RRC connected mode sub-states
paging message from the CN has to be forwarded to the UE. . In this case, the UE adds the IE Paging e transmitted on an existing ps connection (PMM-IDLE or PMM-CONNECTED). UTRAN has to page the user data.
nd URA_PCH about system information changes.
UE receives a paging message, it reads the UE identity to check, whether it is the receiver of the G TYPE 1 message to a UE on several paging occasions message on an appropriate paging
tate, i.e., when at least dedicated control channel resources were allocated to the UE. ated one DDCH and one DCCH to the user. Consequently, a connection between the UE and the 3Gble for the user. While the subscriber is serving, he receives a call. The 3G-MSC is sending a paging e is received by a RNC, which is currently serving the UE. It then uses the existing DCCH to forward the
ick to return to main page
ick to return to main page
Paging Procedure and Parameters Description (Module II)
Click to return to main page
System Information (3GPP-25.331) 1 Master Information Block (MIB) 2 Scheduling Block (SB) 1. System Scheduling Block 1 (SB1) 2. System Scheduling Block 2 (SB2)
3 System Information Block (SIB) 1. System Information Block 1 (SIB1) 2. System Information Block 2 (SIB2) 3. System Information Block 3 (SIB3) 4. System Information Block 5 (SIB5) 5. System Information Block 7 (SIB7) 6. System Information Block 11 (SIB11) According to 3GPP,there are total 18 SIBs , however in Huawei RAN 10, the SIBs 1, 3, 5, 6, 7, 11 are support. The optional SIBs-2,4,12 and 18 can be added by cell parameter "SIB switch". Below show example of MML commaned, CELLSIBSWITCH:CELLID=X, SIBCFGBITMAP=SIB2-1&SIB4-1&SIB121&SIB18-1; (The SIB switch is only valid for SIB2,SIB4,SIB12 and SIB18)
System Information Structure
The system information is organised as a tree. A Master Information Block(MIB) gives references and scheduling information to a number of system information blocks in a cell. The System Information Blocks (SIBs) contain the actual system information. The master information block may optionally also contain reference and scheduling information to one or two scheduling blocks(SBs), which give references and scheduling information for additional system information blocks. Scheduling information for a system information block may only be included in either the master information block or one of the scheduling blocks.
Information Block(MIB) gives references and scheduling information to a number of system information blocks in a cell. The System Information Blocks (SIBs) contain the actual system information. The master information block may optionally also contain reference and scheduling information to one or two scheduling blocks(SBs), which give references and scheduling information for additional system information blocks. Scheduling information for a system information block may only be included in either the master information block or one of the scheduling blocks.
System Information Monitor Mechanism 1. For a SIB containing dynamic parameters (SIB7, SIB8, SIB9, SIB14, and SIB17), the scheduling occasion information is described in the scheduling information included in MIB or SB. The UE regularly reads the SIB on each occasion based on Timer 2. For a SIB containing static parameters (SIB1–SIB6, SIB10–SIB13, SIB15, SIB16, and SIB18) is identified by a value tag. A value tag is included in MIB or SB as a part of the scheduling information. The UE checks whether the value tag for a SIB is different from that for the SIB the UE last reads.If so, the UE shall reread the SIB. Therefore, the UE can know by monitoring the MIB whether a SIB containing static parameters is updated
System Information Broadcast UTRAN
System Information ( )
NBAP: BCCH
RNC
Node B
UE UTRAN sends a SYSTEM INFORMATION message to UE . The message contain the scheduling information, area scope, system information content and so on. The RRC layer in UTRAN performs segmentation and concatenation of encoded system information blocks. If the encoded system information blocks is larger than the size of a SYSTEM INFORMATION message, it will be segmented and transmitted in several messages. If the encoded system information blocks is smaller than the size of a SYSTEM INFORMATION message, UTRAN may concatenate several system information blocks, or the first segment or the last segment into the same message The UE shall read SYSTEM INFORMATION messages broadcast on a BCH transport channel in idle mode and in the connected mode in states CELL_FACH, CELL_PCH, URA_PCH and CELL_DCH (TDD only). In addition, UEs which support simultaneous reception of one SCCPCH and one DPCH shall read system information on a FACH transport channel when in CELL_DCH state . In Idle mode and connected mode different combinations of SIBs are valid. The UE may store SIBs for different cells and different PLMNs for later use when the UE returns to these cells or PLMNs
System Information Update
Each step is explained as follows: 1) The RNC sends a NBAP: SYSTEM INFORMATION UPDATE REQUEST message to the associated NodeB, requesting for system information broadcst. 2) The NodeB returns a NBAP:SYSTEM INFORMATION UPDATE RESPONSE message to the RNC,confirming the system information broadcast 3) 4) 5) The NodeB sends SYSTEM INFORMATION messages on the air interface
System information block Master information block
Area scope Cell
Scheduling block 1 Cell Scheduling block 2 System information block type 1
PLMN
System information block type 2
Cell
System information block type 3
Cell
System information block type 4
Cell
System information block type 5
Cell
System information block type 6
Cell
System information block type 7
Cell
System information block type 8
Cell
System information block type 9
Cell
System information block type 10
Cell
System information block type 11
Cell
System information block type 12
Cell
System information block type 13
Cell
System information block type 13.1
Cell
System information block type 13.2
Cell
System information block type 13.3
Cell
System information block type 13.4
Cell
System information block type 14
Cell
System information block type 15
Cell
System information block type 15.1
Cell
System information block type 15.2
Cell
System information block type 15.3
PLMN
System information block type 15.4
Cell
System information block type 16
PLMN
System information block type 17
Cell
System Information Block type 18
Cell
System Information Modification Notification
There is a huge amount of SIBs, which have to be read by the UE. This requires a lot of battery power. Therefore, a Master Information Block references and scheduling information about the SIBs. The MIB is transmitted in every 8th radio frame on the P-CCPCH (on position SFN mo For most of the SIBs used within the system, the MIB may carry a value tag. The only exceptions are SIB 15.2, SIB 15.3 and SIB 16. If a valu corresponding system information has not been modified. Thus, there is no need for the UE to read the SIB. For the SIBs which have no valu each occurrence (based on Timer). Scheduling information is used to inform the UE, where and when a specific system information is transm There are two ways of notifying a UE of system information modification: by a value tag and by a timer
1) Notification by a Value Tag For SIBs using value tags, UTRAN should notify the new value tag for the MIB to the UE. - To notify a UE in idle mode, CELL_PCH state or URA_PCH state, UTRAN send a PAGING TYPE 1 message on the PCCH on all paging transmit the new MIB value tag. - To notify a UE in CELL_FACH state, UTRAN sends a SYSTEM INFORMATION CHANGE INDICATION message on the BCCH to transm Upon reception of the PAGING TYPE 1 message or SYSTEM INFORMATCHANGE INDICATION message from UTRAN, the UE shall r according to the new MIB value tag.
2) Notification by a Timer
Other types of SIBs have timers respectively. When the timer expires, the UE shall consider the stored system information content invalid,sta new SIB information. Notification by a Timer consider the stored system information content invalid, start the timer, and re-acquire new SIB in postpone reading the SIB until the content is needed Please note, that UEs in the CELL_DCH sub-state are addressed directly by the RNC via the Measurement Control message
Additonal Information Actions upon reception of the Master Information Block and Scheduling Block(s):
When selecting a new cell, the UE shall read the master information block. The UE may use the pre-defined scheduling information to locate block in the cell. Action upon reception of the master information block, the UE shall:
1. if the "PLMN type" in the variable SELECTED_PLMN has the value "GSM-MAP" and the IE "PLMN Type" has the value "GSM-MAP" or "G - check the IE "PLMN identity" in the master information block and verify that it is the selected PLMN, stored as "PLMN identity" in the variab - if the "PLMN type" in the variable SELECTED_PLMN has the value "ANSI-41 "and the IE "PLMN Type" has the value "ANSI-41" or "GSM-M - store the ANSI-41 Information 2.compare the value tag in the master information block with the value tag stored for this cell and this PLMN in the variable VALUE_TAG. 3.if the value tags differ, or if no IEs for the master information block are stored: store the value tag into the variable VALUE_TAG for the mas and store scheduling information included in the master information block; 4. if the value tags are the same the UE may use stored system information blocks and scheduling blocks using value tag that were stored in valid system information. For all system information blocks or scheduling blocks that are supported by the UE referenced in the master information block or shall perform the following actions: 1.for all system information blocks with area scope PLMN that use value tags:
2.compare the value tag in the master information block with the value tag stored for this cell and this PLMN in the variable VALUE_TAG. 3.if the value tags differ, or if no IEs for the master information block are stored: store the value tag into the variable VALUE_TAG for the mas and store scheduling information included in the master information block; 4. if the value tags are the same the UE may use stored system information blocks and scheduling blocks using value tag that were stored in valid system information. For all system information blocks or scheduling blocks that are supported by the UE referenced in the master information block or shall perform the following actions:
1.for all system information blocks with area scope PLMN that use value tags: ->compare the value tag read in scheduling information for that system information block with the value stored within the variable VALUE_TA information block; - if the value tags differ, or if no IEs for the corresponding system information block are stored,:store the value tag read in scheduling inform information block into the variable VALUE_TAG; read and store the IEs of that system information block. - if the value tags are the same ,the UE may use stored system information blocks using value tag that were stored in this PLMN as valid s 2 for all system information blocks or scheduling blocks with area scope cell that use value tags: -> compare the value tag read in scheduling information for that system information block or scheduling block with the value stored within the that system information block or scheduling block; - if the value tags differ, or if no IEs for the corresponding system information block or scheduling block are stored,store the value tag read that system information block or scheduling block into the variable VALUE_TAG; read and store the IEs of that system information block or s - if the value tags are the same, the UE may use stored system information blocks using value tags that were stored in this cell and this PL information.
For system information blocks, not supported by the UE, but referenced either in the master information block or in the scheduling blocks, t - skip reading this system information block; - skip monitoring changes to this system information block Actions upon reception of system information blocks:
The UE may use the scheduling information included within the master information block and the scheduling blocks to locate each system in acquired. The UE should only expect one occurrence of the scheduling information for a system information block in the master information block and However, to enable future introduction of new system information blocks, the UE shall also be able to receive system information blocks othe within the scheduling information. The UE may ignore contents of such system information block. If the UE - receives a system information block in a position according to the scheduling information for the system information block; and - this system information block uses a value tag according to the system information block type the UE shall: - store the content of the system information block together with the value of its value tag in the scheduling information for the system inform - consider the content of the system information block valid until, if used, the value tag in the scheduling information for the system informatio most for 6 hours after reception. If the UE - receives a system information block in a position according to the scheduling information for the system information block; and - this system information block does not use a value tag according to the system information block type the UE shall: - store the content of the system information block; and - start an expiration timer for that system information block type; and - consider the content of the system information block valid until, the expiration timer expires. If the UE - receives a system information block at a position different from its position according to the scheduling information for the system informatio - receives a system information block for which scheduling information has not been received; and - this system information block uses a value tag according to the system information block type the UE may: - store the content of the system information block with a value tag set to the value NULL; and - consider the content of the system information block as valid until it receives the same type of system information block in a position accord information or at most for 6 hours after reception.
If the UE does not find a scheduling block in a position where it should be according to its scheduling information, but a transport block w at that position, the UE shall read the scheduling information for this scheduling block.
If the UE does not find the master information block in a position fulfilling (SFN mod (MIB_REP*4) = 0),(but a transport block with correct the UE shall, - consider the master information block as not found. - consider the cell to be barred according to [4] and - consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE
If the UE does not find the master information block in a position fulfilling (SFN mod (MIB_REP*4) = 0),(but a transport block with correct the UE shall, - consider the master information block as not found. - consider the cell to be barred according to [4] and - consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE
Main Functions The MIB informs the UE about the supported PLMN types and the PLMN identity. The UE finds in the MIB also references to up to maxSIB (=32) SIBs, including their scheduling information and type. A MIB is valid in one cell. If a UE changes the cell, is must read the new cell„s MIB. A change of the MIB information is indicated by a value tag. The master information block may optionally also contain reference and scheduling information to one or two scheduling blocks (SBs), which give references and scheduling information for additional system information blocks. (The SBs are applied when the scheduling resources of MIB are insufficient) Scheduling information for a system information block may only be included in either the master information block or one of the scheduling blocks This SIB is used to inform the UE about NAS system information. The NAS system information characterises the NAS domains. SIB 1 also delivers UE timers and counters, which have to be used by the UE in the RRC idle and RRC connected mode includes URA information. includes relevant parameters for cell selection and re-selection. It also holds the cell identity and cell restriction data, such as „cell barred“ IEs. SIB 3 valid in the RRC connected , if SIB 4 is not broadcasted. This SIB holds mostly the same data fields as SIB 3, but it is read and valid only, when the UE is in the RRC connected mode includes the configuration of physical channels. The parameters cover the PICH power offset, the AICH power offset, P-CCPCH, S-CCPCH and PRACH system information lists. It is read and valid in the RRC connected mode , if SIB 6 is not available. This SIB holds mostly the same data fields as SIB 5, but it is read and valid only, when the UE is in the RRC connected mode includes rapidly changed parameters (UL interference and dynamic persistence level. This SIB holds fast changing parameters. Therefore no value tag is used for it. The UE has to read its parameters periodically includes static CPCH information of cell. Only in used FDD includes CPCH information of cell. Only used in FDD includes UE DCH information controlled by DRAC process. Only used in FDD includes measurement control information of cell. The UE gets here the relevant date for traffic measurement, intra-frequency measurements, etc. It is also valid in the RRC sub-state CELL_DCH, as long as the UE did not get a Measurement Control message from UTRAN and SIB 12 is not broadcasted
This SIB holds mostly the same data fields as SIB 11, but it is read and valid only, when the UE is in the RRC connected mode
includes ANSI-41 relevant information
includes UL outer loop control parameters of common and dedicated physical channels. Only used in TDD
includes information on UE-based or UE-assisted positioning method
includes parameters of radio bearer, transport channel and physical channel. These parameters are stored in UE (either in idle mode or connected mode). It used when UE is switched to UTRAN. RB, The parameters are used during a handover to UTRAN. Consequently, these parameters stay valid, when the UE is connected to GSM and GPRS. includes the rapid changed parameters used to configure the shared physical channel in connected mode. Only used in TDD.
includes PLMN identity of neighbor cell
dification Notification
ch have to be read by the UE. This requires a lot of battery power. Therefore, a Master Information Block (MIB) was introduced, which gives on about the SIBs. The MIB is transmitted in every 8th radio frame on the P-CCPCH (on position SFN mod 8 = 0, and with a TTI of 20 ms). system, the MIB may carry a value tag. The only exceptions are SIB 15.2, SIB 15.3 and SIB 16. If a value tag is unchanged, the as not been modified. Thus, there is no need for the UE to read the SIB. For the SIBs which have no value tag e.g. SIB7, It changes with Scheduling information is used to inform the UE, where and when a specific system information is transmitted.
UE of system information modification: by a value tag and by a timer
hould notify the new value tag for the MIB to the UE. L_PCH state or URA_PCH state, UTRAN send a PAGING TYPE 1 message on the PCCH on all paging occasions in the cell to
te, UTRAN sends a SYSTEM INFORMATION CHANGE INDICATION message on the BCCH to transmit the new MIB value tag. PE 1 message or SYSTEM INFORMATCHANGE INDICATION message from UTRAN, the UE shall read the changed information g.
ectively. When the timer expires, the UE shall consider the stored system information content invalid,start the timer, and re-acquire a Timer consider the stored system information content invalid, start the timer, and re-acquire new SIB information. The UE may ontent is needed
_DCH sub-state are addressed directly by the RNC via the Measurement Control message
ter Information Block and Scheduling Block(s):
hall read the master information block. The UE may use the pre-defined scheduling information to locate the master information
er information block, the UE shall:
SELECTED_PLMN has the value "GSM-MAP" and the IE "PLMN Type" has the value "GSM-MAP" or "GSM-MAP and ANSI-41",: master information block and verify that it is the selected PLMN, stored as "PLMN identity" in the variable SELECTED_PLMN. ELECTED_PLMN has the value "ANSI-41 "and the IE "PLMN Type" has the value "ANSI-41" or "GSM-MAP and ANSI-41",:
er information block with the value tag stored for this cell and this PLMN in the variable VALUE_TAG. or the master information block are stored: store the value tag into the variable VALUE_TAG for the master information block; read uded in the master information block; UE may use stored system information blocks and scheduling blocks using value tag that were stored in this cell and this PLMN as
or scheduling blocks that are supported by the UE referenced in the master information block or the scheduling blocks, the UE s:
s with area scope PLMN that use value tags:
er information block with the value tag stored for this cell and this PLMN in the variable VALUE_TAG. or the master information block are stored: store the value tag into the variable VALUE_TAG for the master information block; read uded in the master information block; UE may use stored system information blocks and scheduling blocks using value tag that were stored in this cell and this PLMN as
or scheduling blocks that are supported by the UE referenced in the master information block or the scheduling blocks, the UE s:
s with area scope PLMN that use value tags: eduling information for that system information block with the value stored within the variable VALUE_TAG for that system
for the corresponding system information block are stored,:store the value tag read in scheduling information for that system ALUE_TAG; read and store the IEs of that system information block. e UE may use stored system information blocks using value tag that were stored in this PLMN as valid system information. s or scheduling blocks with area scope cell that use value tags: eduling information for that system information block or scheduling block with the value stored within the variable VALUE_TAG for eduling block; for the corresponding system information block or scheduling block are stored,store the value tag read in scheduling information for eduling block into the variable VALUE_TAG; read and store the IEs of that system information block or scheduling block; e UE may use stored system information blocks using value tags that were stored in this cell and this PLMN as valid system
upported by the UE, but referenced either in the master information block or in the scheduling blocks, the UE may n block; tem information block
information blocks:
rmation included within the master information block and the scheduling blocks to locate each system information block to be
rrence of the scheduling information for a system information block in the master information block and any of the scheduling blocks. n of new system information blocks, the UE shall also be able to receive system information blocks other than the ones indicated e UE may ignore contents of such system information block.
k in a position according to the scheduling information for the system information block; and a value tag according to the system information block type
rmation block together with the value of its value tag in the scheduling information for the system information block; and nformation block valid until, if used, the value tag in the scheduling information for the system information block is changed or at
k in a position according to the scheduling information for the system information block; and not use a value tag according to the system information block type
rmation block; and stem information block type; and nformation block valid until, the expiration timer expires.
k at a position different from its position according to the scheduling information for the system information block; or k for which scheduling information has not been received; and a value tag according to the system information block type
rmation block with a value tag set to the value NULL; and nformation block as valid until it receives the same type of system information block in a position according to its scheduling er reception.
ng block in a position where it should be according to its scheduling information, but a transport block with correct CRC was found e scheduling information for this scheduling block.
information block in a position fulfilling (SFN mod (MIB_REP*4) = 0),(but a transport block with correct CRC was found at that position),
ck as not found. ding to [4] and e value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "Tbarred".
information block in a position fulfilling (SFN mod (MIB_REP*4) = 0),(but a transport block with correct CRC was found at that position),
ck as not found. ding to [4] and e value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "Tbarred".
UE mode/state when block is valid
UE mode/state when block is read
Idle mode,CELL_FACH,CELL_PCH, URA_PCH
Idle mode,CELL_FACH,CELL_PCH, URA_PCH
Idle mode,CELL_FACH,CELL_PCH, URA_PCH
Idle mode,CELL_FACH,CELL_PCH, URA_PCH
Idle mode,CELL_FACH,CELL_PCH, URA_PCH
Idle mode,CELL_FACH,CELL_PCH, URA_PCH
Idle mode,CELL_FACH,CELL_PCH, URA_PCH,CELL_DCH
Idle
URA_PCH
URA_PCH
Idle mode, (CELL_FACH, CELL_PCH, URA_PCH)
Idle mode, (CELL_FACH, CELL_PCH, URA_PCH)
CELL_FACH, CELL_PCH, URA_PCH
CELL_FACH, CELL_PCH, URA_PCH
Idle mode, (CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only)) CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only) Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only)
Idle mode, (CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only)) CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only) Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only)
CELL_FACH, CELL_PCH, URA_PCH
CELL_FACH, CELL_PCH, URA_PCH
CELL_FACH, CELL_PCH, URA_PCH
CELL_FACH, CELL_PCH, URA_PCH
CELL_DCH
CELL_DCH
Idle mode (CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH)
Idle mode (CELL_FACH, CELL_PCH, URA_PCH)
CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH
CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH
CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH
Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH
Click to return to main page
Idle mode, CELL_FACH, CELL_PCH, URA_PCH
Scheduling information
Modification of system information
SIB_POS = 0,SIB_REP = 8 (FDD),SIB_REP = 8, 16, 32 (TDD),SIB_OFF=2
Value tag
Specified by the IE "Scheduling information" in MIB
Value tag
Specified by the IE "Scheduling information" in MIB
Value tag
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Value tag Expiration timer = MAX([320 ms],SIB_REP * ExpirationTimeFactor)
Specified by the IE "Scheduling information" Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Expiration timer = SIB_REP
Specified by the IE "Scheduling information"
Expiration timer = SIB_REP
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Expiration timer = MAX([320 ms], SIB_REP * ExpirationTimeFactor) Value tag
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Value tag
Specified by the IE "Scheduling information"
Expiration timer = SIB_REP
Specified by the IE "Scheduling information"
Specified by the IE "Scheduling information"
Value tag
Additional comment
If System information block type 4 is not broadcast in a cell, the connected mode UE shall read System information block type 3
If system information block type 6 is not broadcast in a cell, the connected mode UE shall read System information block type 5. In TDD mode system information block type 7 shall only be read in CELL_DCH if shared transport channels are assigned to the UE.
If some of the optional IEs are not included in System information block type 12, the UE shall read the corresponding IEs in System information block type 11.
This system information block is used in TDD mode only.
For this system information block there may be multiple occurrences For this system information block there may be multiple occurrences
For this system information block there may be multiple occurrences
This system information block is used in TDD mode only.
Master Information Block (MIB)
value=hex2dec(0)=0 , hex2d
System Scheduling Block 1 (SB1)
System Information Block 1 (SIB1)
System Information Block 2 (SIB 2)
System Information Block 3 (SIB 3)
value= 000000001011 011101
value=2dB(step of 2 dB)
value=10dB(step of 2 dB) value=8dB(step of 2 dB)
value=4dB(step of 2 dB)
value=-18dBm
value= ((-58*2)+1)= –115 dBm value=4dB(step of 2 dB) value=1s(step of 1s) value=24dBm
System Information Block 5 (SIB 5)
value=33dBm value=-20dBm value=2dB(step of 1 dB) value=20attempts value=8attempts
value=
System Information Block 7 (SIB 7)
System Information Block 11(SIB 11)
Value= IntraFreqMeasureme
value=hex2dec(3b)=59 (Serv
value=hex2dec(43)=67(Neigh
Value= InterRATMeasureme
value=0dB
value= ((-50*2)+1)= –99 dBm
value=BSIC=32 value=GSM1800 value=BCCH=516
Click to return to main page
value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520
value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
Click to return to main page
Click to return to main page
>>Paging Procedure and Parameters Description (Module II)
value=3000ms value=3 value=40ms value=40ms value=0 value=250ms value=6s value=50 value=20s value=30s value=infinity value=2000ms value=3 value=6s value=1 Click to return to main page
value=hex2dec(0065)=101
Click to return to main page
Cell Identity=RNCid(12bits)+Cellid(16bits) value= 000000001011 0111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610
>>>Cell Selection and Reselection Algorithm and parameters description (Module II)
value=2dB(step of 2 dB)
value=10dB(step of 2 dB) value=8dB(step of 2 dB)
value=4dB(step of 2 dB)
value=-18dBm value= ((-58*2)+1)= –115 dBm e.g. –57 means –113 dBm; …; –13 means -25 dBm value=4dB(step of 2 dB) value=1s(step of 1s) value=24dBm >>>Cell Access Restriction parameters description (Module II)
Click to return to main page
>>>Cell Channel Power Configuration Parameters (Module II)
value=-7dB (relative to the PCPICH)
value=-6dB (relative to the PCPICH)
>>>Access Precedures and parameters description (Module II)
>>>Open Loop Power Control Algorithm and parameters description (Module II)
value=33dBm value=-20dBm value=2dB(step of 1 dB) value=20attempts value=8attempts
value=
Click to return to main page
value=-105dBm
>>>see "Parameters description"
Click to return to main page
Value= InterFreqMeasurement is unavailable
Value= IntraFreqMeasurement is based on CPICH Ec/No >>> IntrafreqMeasurement description (Module II)
value=hex2dec(3b)=59 (Serving Cell's Primary Scrambling Code)
value=hex2dec(43)=67(Neighbour Cell's Primary Scrambling Code)
Value= InterRATMeasurement
value=0dB
value= ((-50*2)+1)= –99 dBm e.g. –57 means –113 dBm; …; –13 means -25 dBm
value=BSIC=32 value=GSM1800 value=BCCH=516
dec(0111011110010010)=30610
Click to return to main page
L3 Messages - Location Update Proc UE
NodeB
S-RNC
1.RRC: RRC Connection Request (RACH) 2.NBAP:Radio Link Setup Req Start Rx 3.NBAP:Radio Link Setup Resp. 4.NBAP:Radio Link Setup Req 5.ALCAP: Iub User Plane Setup RRC Connection Establishment Timing Start Tx
6.RRC: RRC Connection Setup (FACH) L1 Synchonization NBAP:Synchonization Indicator 7.RRC: RRC Connection Setup Completed (DCH)
1.RRC: Initial Direct Transfer (MM: Location Update Request)
Optional : Authentication and Securitty Mode Control may exist depends on Operator's se
4.RRC: Downlink Direct Transfer (MM: Location Update Accept) 5.RRC: Uplink Direct Transfer
1.RRC: RRC Connection Release 2.RRC: RRC Connection Release Complete
2.RRC: RRC Connection Release Complete 3.NBAP: Radio Link Deletion Request 4.NBAP: Radio Link Deletion Response ALCAP: Iub User Plane Release
Note the following information about the procedure : 1.The RRC connection can be set up on a DCH or a CCH. This procedure takes the RRC connection set up on the DCH as an example. 2 If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface after radio links are set up or deleted.
ion Update Procedure S-RNC
CN
RRC Connection Setup
>>RRC Procedure description
2.RANAP: Initial UE Message (MM: Location Update Request)
depends on Operator's setting (refer to signaling in AMR call precedures)
Location Update 3.RANAP: Direct Transfer (MM: Location Update Accept)
6.RANAP: Direct Transfer
1.RANAP: Iu Release Command ALCAP: Iu User Plane Release 2..RANAP: Iu Release Complete
Iu release
RRC connection Release
RRC connection setup procedure is performed for the UE to set up a signaling connection
Triggering Conditions : The UE in idle mode intitiates the RRC connection setup procedure w
When the SRNC receives an RRC CONNECTION REQUEST message from the UE, the Radio R If accepting the request, the RRM module further determines whether to set up the RRC connect the DCH.
RRC Connection Setup
>>RRC Procedure description
The procedure shown is described as follows: 1.The UE sends an RRC CONNECTION REQUEST message to the SRNC through the uplink C 2.Based on the cause in the RRC connection request and the system resource status, the SRNC resources, and L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST m resources required for an RRC connection. 3.The NodeB responds with a RADIO LINK SETUP RESPONSE message to the SRNC after suc 4.The SRNC uses the ALCAP protocol to set up the Iub user plane transport bearer and perform for the ATM-based Iub interface only. 5.The SRNC sends an RRC CONNECTION SETUP message to the UE through the downlink CC 6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Synchonization Indicator mess 7. The UE sends an RRC CONNECTION SETUP COMPLETE message to the SRNC through th RRC connection setup procedure ends. If the RNC judges that the RRC connection request cannot be set up (for instance, due to insuffic indicates the reject reason in the message
The location update procedure is performed to update the location of a UE.
Triggering Conditions : An RRC connection is set up between the UE and the Serving RNC (SR Location Update
release
The procedure is described as follows: 1.The UE sends an INITIAL DIRECT TRANSFER message to the SRNC through the RRC conne 2.The SRNC sends an INITIAL UE MESSAGE to the CS service domain of the CN through the Iu Mobile Subscriber Identity (TMSI),International Mobile Subscriber Identity (IMSI), and Location Ar routing area update. The message indicates ATTACH REQUEST and contains the Routing Area 3.The CN updates the location area information of the UE and saves the new LAI. The CN might indicates LOCATION UPDATE ACCEPT and contains the TMSI that is assigned to the UE.For ro authentication and ciphering. Then, the CN sendsa DIRECT TRANSFER message to the SRNC.
4.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE th 5.The UE receives the LOCATION UPDATE ACCEPT information and sends an UPLINK DIREC area update, it is the ATTACH ACCEPT information that the UE receives. 6.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto th
For routing area update, it is ATTACH COMPLETE that the DIRECT TRANSFER message in
The Iu release procedure is performed for the CN to release an Iu connection and all the UT
Triggering Conditions: The Iu release procedure can be triggered in one of the following condit example,sending an IU RELEASE REQUEST message,The Serving Radio Network Subsystem
The procedure shown is described as follows: 1.The CN sends an IU RELEASE COMMAND message to the SRNC to initiate the Iu release pro
The Iu release procedure is performed for the CN to release an Iu connection and all the UT
Triggering Conditions: The Iu release procedure can be triggered in one of the following condit example,sending an IU RELEASE REQUEST message,The Serving Radio Network Subsystem RRC connection Release
The procedure shown is described as follows: 1.The CN sends an IU RELEASE COMMAND message to the SRNC to initiate the Iu release pro NOTE After sending the IU RELEASE COMMAND message, the CN will not send further RANAP 2.The SRNC releases the related UTRAN resources and then sends an IU RELEASE COMPLET
The RRC Connection Release procedure is performed to release the signaling connection and
Triggering Conditions: After a n RAB is released,the SRNC judges whether the RRC connectio release procedure.
The procedure shown is described as follows: based on the resouce occupied by the RRC co connection from DCH and release of an RRC connection from CCH (If an RRC connection needs connection on the CCH is released)
1.The SRNC sends an RRC CONNECTION RELEASE message to the UE through the DCCH. (NOTE: The SRNC may send the RRC CONNECTION RELEASE message several times to incr and the transmission intervals are determined by the SRNC. If the SRNC does not receive an RR COMPLETE message from the UE after sending the RRC CONNECTION RELEASE message fo 2.The UE sends an RRC CONNECTION RELEASE COMPLETE message to the SRNC. 3.The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB,requesting the 4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESPONSE messa 5.(Optional; required for the ATM-based Iub interface only) The SRNC uses the ALCAP protocol ends.
the UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a maximum of one
es the RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling connection
UEST message from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or reject theRRC c mines whether to set up the RRC connection on a Dedicated Channel (DCH)or on a Common Channel (CCH), based on a specific RRM algo
ssage to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection. d the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio NetworkTemporary Id ends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the specific radio link
SPONSE message to the SRNC after successfully preparing the resources. user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. It is required
ssage to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocated by the SRNC. nds NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state PLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message indicates that the
not be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to the UE, and
date the location of a UE.
between the UE and the Serving RNC (SRNC)
age to the SRNC through the RRC connection. The message contains the Non Access Stratum (NAS) information to be sent to the CN by th S service domain of the CN through the Iu interface. The message indicates LOCATION UPDATE REQUEST and containsthe UE informatio ubscriber Identity (IMSI), and Location Area Identity (LAI).The SRNC sends an INITIAL UE MESSAGE to the PS service domain of the CN th EQUEST and contains the Routing Area Identity (RAI) E and saves the new LAI. The CN might also perform authentication and ciphering. Then, the CN sends a DIRECT TRANSFER message to he TMSI that is assigned to the UE.For routing area update, the CN updates the routing area information of the UE and savesthe new RAI. T ECT TRANSFER message to the SRNC. The message indicates ATTACH ACCEPTand contains the TMSI that is assigned to the UE
RECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. nformation and sends an UPLINK DIRECT TRANSFER message to the SRNC. The message contains the information suchas the NAS infor the UE receives. LINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message. The DIRECT TRANSFER messageindicates TMS
at the DIRECT TRANSFER message indicates.
o release an Iu connection and all the UTRAN resources related only to that Iu connection.
be triggered in one of the following conditions: The transaction between the UE and the CN is complete,The UTRAN requests the CN to relea The Serving Radio Network Subsystem (SRNS) is relocated.4.The SRNS relocation is canceled after a relocation resource allocation proced
to the SRNC to initiate the Iu release procedure. The message indicates the cause for the release of the signaling connection.
o release an Iu connection and all the UTRAN resources related only to that Iu connection.
be triggered in one of the following conditions: The transaction between the UE and the CN is complete,The UTRAN requests the CN to relea The Serving Radio Network Subsystem (SRNS) is relocated.4.The SRNS relocation is canceled after a relocation resource allocation proced
to the SRNC to initiate the Iu release procedure. The message indicates the cause for the release of the signaling connection. sage, the CN will not send further RANAP connection-oriented messages on this particular connection. d then sends an IU RELEASE COMPLETE message to the CN.
d to release the signaling connection and all radio bearers between UE and the UTRAN
RNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry other RAB of
d on the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: release of an RRC n from CCH (If an RRC connection needs to be released after a successful outgoing call,, the RRC connection on the DCH is released and if
message to the UE through the DCCH. RELEASE message several times to increase the probability of proper reception of the message by the UE. The RRC SNs of these message NC. If the SRNC does not receive an RRC CONNECTION RELEASE C CONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC connection.) MPLETE message to the SRNC. ST message to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB. DIO LINK DELETION RESPONSE message to the SRNC. ly) The SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC connection release
One UE has a maximum of one RRC connection at a time.
onnection
her to accept or reject theRRC connection request, based on a specific algorithm. ), based on a specific RRM algorithm. Typically, an RRC connection is set up on
the Radio NetworkTemporary Identity(RNTI),radio c radio link
edure is optional. It is required
H allocated by the SRNC. message indicates that the
message to the UE, and
mation to be sent to the CN by the UE. T and containsthe UE information, such as the Temporary e PS service domain of the CN throughthe Iu interface for
IRECT TRANSFER message to the SRNC. The message he UE and savesthe new RAI. The CN might also perform hat is assigned to the UE
nformation suchas the NAS information and the CN ID.For routing
NSFER messageindicates TMSI REALLOCATION COMPLETE.
UTRAN requests the CN to release the resources on the Iu interface by, for cation resource allocation procedure iscomplete.
naling connection.
UTRAN requests the CN to release the resources on the Iu interface by, for cation resource allocation procedure iscomplete.
naling connection.
on does not carry other RAB of the UE,the SRNC initiates an RRC connection
e: release of an RRC on on the DCH is released and if a radio bearers fails to be setup ,the RRC
The RRC SNs of these messages are the same. The number of retransmissions
onnection.)
en, the RRC connection release procedure
Click to return to main page RRC:RRC Connection Request (RACH)
>>"RRC Connection Request D
>>"Geographical and UTRAN E
value=hex2dec(4)=4 , hex2d
value=hex2dec(0)=0 , hex2d
value=hex2dec(75 AA)= 301
value= registration(Location
value=(-24+ (36/2))= -6 dB (S
value=hex2dec(91)=145 (Ne
value=CPICH Ec/Io invalid
RRC:RRC Connection Setup (FACH)
>>"RRC Connection Setup Des
>>"Geographical and UTRAN E
value=hex2dec(4)=4 , hex2d
value=hex2dec(0)=0 , hex2d
value=hex2dec(75 AA)= 301
value=UE capable to suppo
value=UE capable to suppo
value=Signaling Radio Bear
value=Radio Bearer Mappin
value=Signaling Radio Bear
value=Signaling Radio Bear
value=Signaling Radio Bear
value=BLER Target= -20 dB
value=MaxAllowedULTxPow
value=(-37*2)= -74 dBm (ste
value= use Closed Loop Po
value= use long SC on Uplin
value=Spreading Factor 64
value=Spreading Factor 128
value=Primary Scrambling c
value=Spreading Factor 128
Cell Identity=RNCid(12bits)+
value= 000000000001 01011
RRC:RRC Connection Setup Complete (DCCH)
>>"RRC Connection Setup Com
value= UE (Powerclass3) m
value= support GSM (Dual M
value= Chipering Algorithm
value= support Compressed
RANAP: Initial UE Message (MM: Location Update Request)
RRC: Initial Direct Transfer (MM: Location Update Request)
RANAP: Direct Transfer (MM: Location Update Accept)
RRC: Downlink Direct Transfer (MM: Location Update Accept)
RRC: RRC Connection Release
.RRC: RRC Connection Release Complete
>>"RRC Connection Request Description"
>>"Geographical and UTRAN Entity Identifiers"
value=hex2dec(4)=4 , hex2dec(5)=5 ,hex2dec(6)=6 --> MCC=456
value=hex2dec(0)=0 , hex2dec(2)=2 --> MNC=02
value=hex2dec(75 AA)= 30122
value= registration(Location update)
value=(-24+ (36/2))= -6 dB (Serving cell's CPICH Ec/No)
value=hex2dec(91)=145 (Neighbour's Primary Scrambling Code)
value=CPICH Ec/Io invalid
>>"RRC Connection Setup Description"
>>"Geographical and UTRAN Entity Identifiers"
value=hex2dec(4)=4 , hex2dec(5)=5 ,hex2dec(6)=6 --> MCC=456
value=hex2dec(0)=0 , hex2dec(2)=2 --> MNC=02
value=hex2dec(75 AA)= 30122
value=UE capable to support FDD , not TDD
value=UE capable to support GSM
value=Signaling Radio Bearer Information Setup ,RB-1
value=Radio Bearer Mapping
value=Signaling Radio Bearer Information Setup ,RB-2
value=Signaling Radio Bearer Information Setup ,RB-3
value=Signaling Radio Bearer Information Setup ,RB-4
value=BLER Target= -20 dB value=MaxAllowedULTxPower=24 dBm
value=(-37*2)= -74 dBm (step of 2 dB)
Default Constant
DPCCH_Power_offset
CPICH_RSCP
-22
-74
-80
-22
-74
-70
Note :DPCCH_Power_offset is configured by RNC and delivered to UE in RRC Connection S value= use Closed Loop Power Control Algorithm1
value= use long SC on Uplink
value=Spreading Factor 64 (Uplink)
value=Spreading Factor 128 (Downlink)
value=Primary Scrambling code=385
value=Spreading Factor 128 (Downlink)
Cell Identity=RNCid(12bits)+Cellid(16bits)
value= 000000000001 0101101011001010 => RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(0111011110010010)=23242 >>"RRC Connection Setup Complete Description"
value= UE (Powerclass3) maximum transmitted power =24 dBm
value= support GSM (Dual Mode UMTS<>GSM)
value= Chipering Algorithm A5/3
value= support Compressed Mode (CM) uplink and downlink
value= MCC=456
value= MNC=02 value=hex2dec(75AA)=30122
PCPICH Power
UL Interference
UL DPCCH Initial Power
33
-85
6
33
-85
-4
delivered to UE in RRC Connection Setup.
11011110010010)=23242
Click to return to main page
L3 Messages - AMR Voice (MOC) Call Pro UE
NodeB
S-RNC
1.RRC: RRC Connection Request (RACH) 2.NBAP:Radio Link Setup Req Start Rx 3.NBAP:Radio Link Setup Resp. 4.ALCAP: Iub User Plane Setup RRC Connection Establishment Timing
Start Tx
5.RRC: RRC Connection Setup (FACH) L1 Synchonization NBAP:Synchonization Indicator 6.RRC: RRC Connection Setup Completed (DCH)
1.RRC: Initial Direct Transfer (MM: CM Service Request)
2.RRC: Downlink Direct Transfer (MM: Authentication Request) 3.RRC: Uplink Direct Transfer (MM: Authentication Response)
6.RRC: Security Mode Command 7.RRC: Security Mode Completed 1.RRC: Uplink Direct Transfer (CC: Setup)
4.RRC: Downlink Direct Transfer (CC: Call Proceeding)
3.NBAP: Radio Link Reconfiguration Prepare 4.NBAP: Radio Link Reconfiguration Ready 5.ALCAP: Iub User Plane Setup 6.RRC: Radio Bearer Setup 7.NBAP: Radio Link Reconfiguration Commit Apply new transport format set 8.RRC: Radio Bearer Setup Complete
7.RRC: Downlink Direct Transfer (CC: Alerting) 9.RRC: Downlink Direct Transfer (CC: Connect) 10.RRC: Uplink Direct Transfer (CC: Connect Acknowledge)
Call Established RRC:Measurement Control RRC:Measurement Report Intra-Frequency Soft Handover
Inter-Frequency Hard Handover Inter-RAT Hard Handover
1.RRC: Uplink Direct Transfer (CC: Disconnect)
4.RRC: Downlink Direct Transfer (CC: Release) 5.RRC: Uplink Direct Transfer (CC: Release Complete)
1.RRC: RRC Connection Release 2.RRC: RRC Connection Release Complete 2.RRC:RRC Connection Release Complete 3.NBAP: Radio Link Deletion Request 4.NBAP: Radio Link Deletion Response 5,.ALCAP: Iub User Plane Release
Note the following information about the procedure , 1.The RRC connection can be set up on a DCH or a CCH. This procedure takes the RRC connection set up on the DCH as an example. 2. If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iubinterface after radio links are set up, reconfigured, or deleted. 3. If IP transport is applied to the Iu-CS interface, no ALCAP procedure is performed on the Iu-CS interface after an RAB is set up or a call is released
ce (MOC) Call Procedure S-RNC
CN
>>RRC Procedure Description 1.RRC Connection Setup
SCCP: CR (Connection Request)
2.Signalling Connection Setup 2.RANAP: Initial UE Message (MM: CM Service Request) 3.SCCP: CC (Connection Confirm) 1.RANAP: Direct Transfer (MM: Authentication Request)
4.RANAP: Direct Transfer (MM: Authentication Response) RANAP: Common ID (IMSI) 5.RANAP: Security Mode Command
8.RANAP: Security Mode Complete 2.RANAP: Direct Transfer (CC: Setup)
3.Authentication & Security Mode Control
3.RANAP: Direct Transfer (CC: Call Proceeding) 1.RANAP: RAB Assignment Request 2.ALCAP : Iu User Plane Setup
5. Radio Bearer Setup 4.Call Setup
9.RANAP: RAB Assignment Response 6.RANAP: Direct Transfer (CC: Alerting) 8.RANAP: Direct Transfer (CC: Connect)
11.RANAP: Direct Transfer (CC: Connect Acknowledge)
blished
6.Conversation
2.RANAP: Direct Transfer (CC: Disconnect) 3.RANAP: Direct Transfer (CC: Release)
7.Call Release 6.RANAP: Direct Transfer (CC: Release Complete) 7.RANAP: Iu Release Command 8.ALCAP: Iu User Plane Release 9.RANAP: Iu Release Complete
8.RRC Connection Release
RRC connection setup procedure is performed for the UE to set up a signaling connectio connection at a time.
Triggering Conditions : The UE in idle mode intitiates the RRC connection setup procedur
REQUEST message from the UE, the Radio Resource Management (RRM) module of the RN algorithm. If accepting the request, the RRM module further determines whether to set up the R algorithm. Typically, an RRC connection is set up on the DCH.
>>RRC Procedure Description .RRC Connection Setup
The procedure shown is described as follows: 1.The UE sends an RRC CONNECTION REQUEST message to the SRNC through the uplink 2.Based on the cause in the RRC connection request and the system resource status, the SRN Identity(RNTI),radio resources, and L1 and L2 resources. Then the SRNC sends a RADIO LIN required for an RRC connection. 3.The NodeB responds with a RADIO LINK SETUP RESPONSE message to the SRNC after s 4.The SRNC uses the ALCAP protocol to set up the Iub user plane transport bearer and perfor for the ATM-based Iub interface only. 5.The SRNC sends an RRC CONNECTION SETUP message to the UE through the downlink 6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Synchonization Indicator me 7. The UE sends an RRC CONNECTION SETUP COMPLETE message to the SRNC through RRC connection setup procedure ends. If the RNC judges that the RRC connection request cannot be set up (for instance, due to insu reason in the message
The signaling connection setup procedure is performed to exchange the NAS (Non Ac .Signalling Connection Setup
Triggering Conditons: The UE sends a direct transfer message to initiate the signaling conne
The procedure shown is described as follows: 1.The UE sends an INITIAL DIRECT TRANSFER message to the SRNC through the RRC co 2.The SRNC receives the INITIAL DIRECT TRANSFER message from the UE and sends an I to be sent to the CN by the UE. The content of the NAS information is CM SERVICE REQUES 3.The CN sends a response message to the SRNC. -If accepting the request, the CN sends a CONNECTION CONFIRM (CC) message to the S confirms that the signaling connection is set up. -If rejecting the request, the CN sends a CONNECTION REJECT (CJ) message to the SRN confirms that the signaling connection fails to be setup and then initiates the RRC release pro .Authentication & Security Mode Control
The authentication and security mode control procedure is performed for the UE an
algorithm and ciphering algorithm. This procedure ensures integrity and correctness of signalin
Triggerring Conditions: The UE and the CN exchange signaling. The network initiates the au
The procedure shown is described as follows: 1.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates AUTH 2.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE 3.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 4.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto Subscriber Identity Module (USIM) judges that the authentication is successful, the UE returns 5.The CN sends a SECURITY MODE COMMAND message to the SRNC to initiate the securit protection algorithms. 6.The SRNC sends a SECURITY MODE COMMAND message to the UE to inform the UE of t
The procedure shown is described as follows: 1.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates AUTH 2.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE 3.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 4.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto Subscriber Identity Module (USIM) judges that the authentication is successful, the UE returns 5.The CN sends a SECURITY MODE COMMAND message to the SRNC to initiate the securit protection algorithms. 6.The SRNC sends a SECURITY MODE COMMAND message to the UE to inform the UE of t 7.The UE sends a response message to the SRNC. -If the integrity protection and ciphering algorithms are configured successfully, the UE MODE COMMAND COMPLETE message to the CN.The message contains the information ab -If the UE does not support the integrity protection and ciphering algorithms, the UE se information and the reason for the failure. The SRNC then sends a SECURITY MODE COMM The RANAP:Common ID message is used to transport the permanent UE Identity(IMSI) t
The call setup procedure is performed to set up a call. . Radio Bearer Setup .Call Setup
.Conversation
Triggering Conditions: The UE initiates a call
The procedure shown is described as follows: 1.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. The message conta 2.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto 3.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates CALL 4.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE 5. A Radio Access Bearer (RAB) is set up. (see more details in RAB Setup Procedure below) 6. When the called terminal rings, the CN sends a DIRECT TRANSFER message to the SRNC 7.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE 8.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates CONN 9.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE 10.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 11.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message
The Radio Bearer Setup procedure shown is described as follows: 1.The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the RAB 2.(Optional; applicable to the ATM-based Iu-CS interface only) The SRNC maps the Quality of characteristic parameters. Based on the AAL2 link characteristic parameters,the ALCAP on the 3.The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the NodeB, 4.The NodeB allocates the associated resources and then sends a RADIO LINKRECONFIGUR 5.(Optional; required for the ATM-based Iub interface only) The Iub ALCAP at the SRNC initiat by exchanging uplink and downlink synchronization frames in the DCH frame protocol. 6.The SRNC sends a RADIO BEARER SETUP message to the UE. 7.The SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to theNodeB. 8.After performing the radio bearer setup, the UE sends a RADIO BEARER SETUP COMPLET 9.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The RAB isset u The procedure when RAB Setup Failure shown is described as follows: 1.The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the RAB 2.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The message in
The call release procedure is performed to release services and resources after a call end Triggering Conditions : A call ends and the calling party hangs up
The procedure shown is described as follows: 1.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 2.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto 3.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates RELE 4.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE 5.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 6.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto
Triggering Conditions : A call ends and the calling party hangs up
The procedure shown is described as follows: 1.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 2.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto 3.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates RELE 4.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE 5.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 6.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto 7.The CN sends an IU RELEASE COMMAND message to the SRNC to request call release o 8.(Optional; applicable to the ATM-based Iu-CS interface only) The ALCAP protocol on the Iu i 9.The SRNC sends an IU RELEASE COMPLETE message to the CN. Release
The RRC Connection Release procedure is performed to release the signaling connection a
Triggering Conditions: After a n RAB is released,the SRNC judges whether the RRC connec RRC connection release procedure.
The procedure shown is described as follows: based on the resouce occupied by the RRC RRC connection from CCH (If an RRC connection needs to be released after a successful out fails to be setup ,the RRC connection on the CCH is released)
.RRC Connection Release
1.The SRNC sends an RRC CONNECTION RELEASE message to the UE through the DCCH (NOTE: The SRNC may send the RRC CONNECTION RELEASE message several times to in the same. The number of retransmissions and the transmission intervals are determined by th UE after sending the RRC CONNECTION RELEASE message for four times, the SRNC judg
2.The UE sends an RRC CONNECTION RELEASE COMPLETE message to the SRNC. 3.The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB,requesting 4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESPONSE mes 5.(Optional; required for the ATM-based Iub interface only) The SRNC uses the ALCAP protoc procedure ends.
to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a maximum of one RRC
RC connection setup procedure when the NAS of the UE requests the establishment of a signaling connection When the SRNC receives an ment (RRM) module of the RNC determines whether to accept or reject theRRC connection request, based on a specific ermines whether to set up the RRC connection on a Dedicated Channel (DCH)or on a Common Channel (CCH),based on a specific RRM
o the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection. ystem resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio NetworkTemporary the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the specific radio link resource
E message to the SRNC after successfully preparing the resources. ane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. It is required
o the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocated by the SRNC. AP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message indicates that the
et up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to the UE, and indicates the re
to exchange the NAS (Non Access Stratum) information between the UE and the CN.
e to initiate the signaling connection setup procedure.
he SRNC through the RRC connection. The message contains the initial NAS information to be sent to the CN by the UE. ge from the UE and sends an INITIAL UE MESSAGE to the CN over the Iu interface. The INITIAL UE MESSAGE contains the NAS informat ation is CM SERVICE REQUEST.
NFIRM (CC) message to the SRNC. The message indicates that the SCCP connection is set up. After receivingthe message, the SRNC
ECT (CJ) message to the SRNC. The message indicates that the SCCP connection fails to be set up. After receiving the message, the SRN n initiates the RRC release procedure.
ure is performed for the UE and the network to implement bi-directional authentication and to negotiate and configure the integrity protection grity and correctness of signaling
ng. The network initiates the authentication and securitymode control procedure
. The message indicates AUTHENTICATION REQUEST. RANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. he SRNC. IRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION RESPONSE. If the UMTS n is successful, the UE returns a message with an XRES IE. he SRNC to initiate the security mode control procedure. The message contains the information about the supported ciphering and integrity
to the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.
. The message indicates AUTHENTICATION REQUEST. RANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. he SRNC. IRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION RESPONSE. If the UMTS n is successful, the UE returns a message with an XRES IE. he SRNC to initiate the security mode control procedure. The message contains the information about the supported ciphering and integrity
to the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.
figured successfully, the UE sends a SECURITY MODE COMMAND COMPLETE message to the SRNC. The SRNC then sends a SECU age contains the information about the integrity protection and ciphering algorithms that the UE uses. hering algorithms, the UE sends a SECURITY MODE COMMAND FAILURE message to the SRNC. The message contains the error s a SECURITY MODE COMMAND REJECT message to the CN permanent UE Identity(IMSI) to SRNC
he SRNC. The message contains the number of the called party and the information about the bearer capability of the call. IRECT TRANSFER messageto the CN through a DIRECT TRANSFER message. . The message indicates CALL PROCEEDING and contains the information about the negotiated bearer capability of the call. RANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. RAB Setup Procedure below) ANSFER message to the SRNC. The message indicates ALERTING. RANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. . The message indicates CONNECT, which means that the called party has answered the call. RANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. the SRNC. DIRECT TRANSFER message to the CN through a DIRECT TRANSFER message, indicating CONNECT ACKNOWLEDGE.
ollows: o the SRNC to initiate the RAB setup procedure. The SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and radio resource c parameters,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup procedure. PARE message to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio links for carrying the RAB s a RADIO LINKRECONFIGURATION READY message to the SRNC. Iub ALCAP at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SRNC perform synchronization e DCH frame protocol. UE. MIT message to theNodeB. O BEARER SETUP COMPLETE message to the SRNC. age to the CN. The RAB isset up. d as follows: o the SRNC to initiate the RAB setup procedure. age to the CN. The message indicates the ID of the RAB that fails to be set up and the reason for the failure.
s and resources after a call ends.
s up
he SRNC. IRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating DISCONNECT. This content informs the CN tha . The message indicates RELEASE to request release of the call. RANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. he SRNC. IRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating RELEASE COMPLETE.
s up
he SRNC. IRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating DISCONNECT. This content informs the CN tha . The message indicates RELEASE to request release of the call. RANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. he SRNC. IRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating RELEASE COMPLETE. SRNC to request call release on the Iu interface. The message indicates the reason for the Iu release The ALCAP protocol on the Iu interface initiates an Iu data transport bearer release procedure. he CN.
ase the signaling connection and all radio bearers between UE and the UTRAN
dges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry other RAB of the UE,
resouce occupied by the RRC connection,there are two types of RRC connection release procedure: release of an RRC connection from D eleased after a successful outgoing call,, the RRC connection on the DCH is released and if a radio bearers
e to the UE through the DCCH. SE message several times to increase the probability of proper reception of the message by the UE. The RRC SNs of these messages are n intervals are determined by the SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE COMPLETE message from the for four times, the SRNC judges that the UE has released the RRC connection.)
E message to the SRNC. sage to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB. K DELETION RESPONSE message to the SRNC. SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC connection release
UE has a maximum of one RRC
tion When the SRNC receives an RRC CONNECTION d on a specific CCH),based on a specific RRM
adio NetworkTemporary ate the specific radio link resources
is optional. It is required
ated by the SRNC.
age indicates that the
ge to the UE, and indicates the reject
CN by the UE. SAGE contains the NAS information
eivingthe message, the SRNC receiving the message, the SRNC
d configure the integrity protection
ATION RESPONSE. If the UMTS
supported ciphering and integrity
ATION RESPONSE. If the UMTS
supported ciphering and integrity
C. The SRNC then sends a SECURITY message contains the error
ability of the call.
apability of the call.
ACKNOWLEDGE.
meters and radio resource
g radio links for carrying the RAB.
SRNC perform synchronization
e.
T. This content informs the CN that the UE has hanged up.
MPLETE.
T. This content informs the CN that the UE has hanged up.
MPLETE.
es not carry other RAB of the UE,the SRNC initiates an
ase of an RRC connection from DCH and release of an rs
RC SNs of these messages are COMPLETE message from the
RRC connection release
Click to return to main page RRC:RRC Connection Request (RACH)
>>"RRC Connection Request D
>>"Geographical and UTRAN E
value=hex2dec(5)=5 , hex2d
value=hex2dec(0)=0 , hex2d
value=hex2dec(2908)= 1050
value= OriginatingConversa
value=(-24+ (43/2))=-2.5 dB
value=hex2dec(60)=96(Neig
value=CPICH Ec/Io invalid
RRC:RRC Connection Setup (FACH)
>>"RRC Connection Setup Des
>>"Geographical and UTRAN E
value=hex2dec(5)=5 , hex2d
value=hex2dec(0)=0 , hex2d
value=hex2dec(2908)= 1050
value=UE capable to suppo
value=UE capable to suppo
value=Signaling Radio Bear
value=Radio Bearer Mappin
value=Signaling Radio Bear
value=Signaling Radio Bear
value=Signaling Radio Bear
value=BLER Target= -20 dB
value=MaxAllowedULTxPow
value=(-47*2)= -94 dBm (ste
value= use Closed Loop Po
value= use long SC on Uplin
value=Spreading Factor 64
value=Spreading Factor 128
value=Primary Scrambling c
value=Spreading Factor 128
Cell Identity=RNCid(12bits)+ value= 000000001011 011101
RRC:RRC Connection Setup Complete (DCCH)
>>"RRC Connection Setup Com
value= not support GSM (Lo
value= Chipering Algorithm
value= UE support Band fdd
value= UE (Powerclass3) ma
value= support Compressed
value= UE support Band fdd
RRC: Initial Direct Transfer (MM: CM Service Request)
RANAP:Initial UE Message (MM: CM Service Request)
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)
RRC: Security Mode Command
RRC: Security Mode Complete
RANAP: Direct Transfer (CC: Setup)
RRC: Uplink Direct Transfer (CC: Setup)
RRC: Downlink Direct Transfer (CC: Call Proceeding)
RANAP: Direct Transfer (CC: Call Proceeding)
RRC: Radio Bearer Setup
RRC: Radio Bearer Setup Complete
RANAP: Direct Transfer (CC: Alerting)
RRC: Downlink Direct Transfer (CC: Alerting)
RANAP: Direct Transfer (CC: Connect)
RRC: Downlink Direct Transfer (CC: Connect)
RANAP: Direct Transfer (CC: Connect Acknowledge)
RRC: Uplink Direct Transfer (CC: Connect Acknowledge)
RANAP: Direct Transfer (CC: Disconnect)
RRC: Uplink Direct Transfer (CC: Disconnect)
RANAP: Direct Transfer (CC: Release)
RRC: Downlink Direct Transfer (CC: Release)
RANAP: Direct Transfer (CC: Release Complete)
RRC: Uplink Direct Transfer (CC: Release Complete)
RRC: Downlink Direct Transfer (CC: RRC Connection Release)
RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)
>>"RRC Connection Request Description"
>>"Geographical and UTRAN Entity Identifiers"
value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520
value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
value=hex2dec(2908)= 10504 value= OriginatingConversationalcall (CS MOC)
value=(-24+ (43/2))=-2.5 dB
value=hex2dec(60)=96(Neighbour's Primary Scrambling Code)
value=CPICH Ec/Io invalid
>>"RRC Connection Setup Description"
>>"Geographical and UTRAN Entity Identifiers"
value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520
value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
value=hex2dec(2908)= 10504
value=UE capable to support FDD , not TDD
value=UE capable to support GSM
value=Signaling Radio Bearer Information Setup ,RB-1
value=Radio Bearer Mapping
value=Signaling Radio Bearer Information Setup ,RB-2
value=Signaling Radio Bearer Information Setup ,RB-3
value=Signaling Radio Bearer Information Setup ,RB-4
value=BLER Target= -20 dB value=MaxAllowedULTxPower=24 dBm
value=(-47*2)= -94 dBm (step of 2 dB)
Default Constant
DPCCH_Power_offset
CPICH_RSCP
-22
-94
-80
-22
-94
-70
Note :DPCCH_Power_offset is configured by RNC and delivered to UE in RRC Connec value= use Closed Loop Power Control Algorithm1
value= use long SC on Uplink
value=Spreading Factor 64 (Uplink)
value=Spreading Factor 128 (Downlink)
value=Primary Scrambling code=97
value=Spreading Factor 128 (Downlink)
Cell Identity=RNCid(12bits)+Cellid(16bits) value= 000000001011 0111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610
>>"RRC Connection Setup Complete Description"
value= not support GSM (Locked UMTS Mode)
value= Chipering Algorithm A5/3
value= UE support Band fdd2100 MHz value= UE (Powerclass3) maximum transmitted power =24 dBm
value= support Compressed Mode (CM) uplink and downlink
value= UE support Band fdd1800 MHz
value= Call B-Party number = 0812713339
>>"Radio Bearer Description"
value= SF64(uplink)-> AMR 12.2
value=Primary Scrambling code=97
value= SF128(downlink)-> AMR 12.2
Cell Identity=RNCid(12bits)+Cellid(16bits) value= 000000001011 0111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010
PCPICH Power
UL Interference
UL DPCCH Initial Power
33
-105
-14
33
-105
-24
nd delivered to UE in RRC Connection Setup.
1011110010010)=30610
ellid=bin2dec(0111011110010010)=30610
Click to return to main page
L3 Messages -AMR Voice Call (MTC) Call Pr UE
NodeB
S-RNC
*** The different messages between MOC & MTC are highlighted in "Red" color 2. RRC: Paging Type 1 1. RRC: RRC Connection Request (RACH) 2.NBAP:Radio Link Setup Req Start Rx 3.NBAP:Radio Link Setup Resp. 4. ALCAP: Iub User Plane Setup RRC Connection Establishment Timing
Start Tx
5. RRC: RRC Connection Setup (FACH)
L1 Synchonization NBAP:Synchonization Indicator 6. RRC: RRC Connection Setup Completed (DCH) 1.RRC: Initial Direct Transfer (MM: Paging Response)
2.RRC: Downlink Direct Transfer (MM: Authentication Request) 3.RRC: Uplink Direct Transfer (MM: Authentication Response)
6.RRC: Security Mode Command 7.RRC: Security Mode Completed
2. RRC: Downlink Direct Transfer (CC: Setup) 3. RRC: Uplink Direct Transfer (CC: Call Confirmed)
3. NBAP: Radio Link Reconfiguration Prepare 4. NBAP: Radio Link Reconfiguration Ready 5. ALCAP: Iub User Plane Setup 6. RRC: Radio Bearer Setup 7. NBAP: Radio Link Reconfiguration Commit Apply new transport format set 8. RRC: Radio Bearer Setup Complete 6. RRC: Uplink Direct Transfer (CC: Alerting)
8.RRC: Uplink Direct Transfer (CC: Connect)
11. RRC: Downlink Direct Transfer (CC: Connect Acknowledge)
Call Established RRC:Measurement Control RRC:Measurement Report
RRC: Downlink Direct Transfer (CC: Disconnect) RRC: Uplink Direct Transfer (CC: Release)
RRC: Downlink Direct Transfer (CC: Release Complete)
RRC: Downlink Direct Transfer (CC: RRC Connection Release) RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete) RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete) NBAP: Radio Link Deletion Request NBAP: Radio Link Deletion Response ALCAP: Iub User Plane Release
Note the following information about the procedure , 1.The RRC connection can be set up on a DCH or a CCH. This procedure takes the RRC connection set up on the DCH as an example. 2. If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iubinterface after radio links are set up, reconfigured, or deleted. 3. If IP transport is applied to the Iu-CS interface, no ALCAP procedure is performed on theIu-CS interface after an RAB is set up or a call is released
e Call (MTC) Call Procedure S-RNC
CN 1. RANAP: Paging
1.Paging
Setup
2.RRC ConnectionSetup >>RRC Procedure Description
2.SCCP: CR (Connection Request) 2. RANAP: Initial UE Message (MM: Paging Response)
3.Signalling Connection S
3.SCCP: CC (Connection Confirm) 1.RANAP: Direct Transfer (MM: Authentication Request)
4.RANAP: Direct Transfer (MM: Authentication Response) RANAP: Common ID (IMSI) 5.RANAP: Security Mode Command
7.RANAP: Security Mode Complete
4.Authentication & Securi Mode Control
1. RANAP: Direct Transfer (CC: Setup)
4. RANAP: Direct Transfer (CC: Call Confirmed) 1. RANAP: RAB Assignment Request 2. ALCAP: Iur User Plane Setup
5.Radio Bearer Setup
Setup
4.Call Setup
set
9.RANAP: RAB Assignment Response 7. RANAP: Direct Transfer (CC: Alerting)
9. RANAP: Direct Transfer (CC: Connect) 10. RANAP: Direct Transfer (CC: Connect Acknowledge)
ablished 6.Conversation
RANAP: Direct Transfer (CC: Disconnect)
RANAP: Direct Transfer (CC: Release)
ease
RANAP: Direct Transfer (CC: Release Complete)
7.Call Release
RANAP: Iu Release Command ALCAP: Iur User Plane Release RANAP: Iu Release Complete
8.RRC Connection Releas
Paging Procedure The paging procedure is performed when the CN calls a UE. Triggering Conditions: A Terminal calls the UE .Paging
The Paging Procedure in Idle, Cell_PCH and URA-PCH modes is described as 1.The CN sends a PAGING message to the SRNC. 2.The SRNC initiates the paging procedure by sending a PAGING TYPE 1 messag paging occasion is related to the International Mobile Subscriber Identity (IMSI) of th proper receptionof the paging message by the UE.) 3.The UE in idle mode or in PCH state monitors the paging and receives the paging
.RRC ConnectionSetup
The Paging Procedure in Cell_DCH and Cell_FACH mode is described as follo 1.The CN sends a PAGING message to the SRNC. 2.The SRNC initiates the paging procedure by sending a PAGING TYPE 2 messag 3.The UE receives the PAGNG TPYE 2 message, reads it, and then reports to the N procedure ends
>>RRC Procedure Description
RRC connection setup procedure is performed for the UE to set up a signalin maximum of one RRC connection at a time.
Triggering Conditions: The UE in idle mode intitiates the RRC connection setu
When the SRNC receives an RRC CONNECTION REQUEST message from the U reject theRRC connection request, based on a specific algorithm. If accepting the re Channel (DCH)or on a Common Channel (CCH), based on a specific RRM algorith
.Signalling Connection Setup
.Authentication & Security Mode Control
The procedure shown is described as follows: 1.The UE sends an RRC CONNECTION REQUEST message to the SRNC through 2.Based on the cause in the RRC connection request and the system resource stat NetworkTemporary Identity (RNTI), radio resources, and L1 and L2 resources. The NodeB to allocate the specific radio link resources required for an RRC connection. 3.The NodeB responds with a RADIO LINK SETUP RESPONSE message to the S 4.The SRNC uses the ALCAP protocol to set up the Iub user plane transport bearer It is required for the ATM-based Iub interface only. 5.The SRNC sends an RRC CONNECTION SETUP message to the UE through th SRNC. 6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Synchonization I 7. The UE sends an RRC CONNECTION SETUP COMPLETE message to the SRN indicates that the RRC connection setup procedure ends. If the RNC judges that the RRC connection request cannot be set up (for instance, UE, and indicates the reject reason in the message
The signaling connection setup procedure is performed to exchange the N
Triggering Conditions: The UE sends a direct transfer message to initiate The procedure shown is described as follows:
1.The UE sends an INITIAL DIRECT TRANSFER message to the SRNC through th UE. 2.The SRNC receives the INITIAL DIRECT TRANSFER message from the UE and contains the NAS information to be sent to the CN by the UE. The content ofthe NA
Triggering Conditions: The UE sends a direct transfer message to initiate The procedure shown is described as follows:
1.The UE sends an INITIAL DIRECT TRANSFER message to the SRNC through th UE. 2.The SRNC receives the INITIAL DIRECT TRANSFER message from the UE and contains the NAS information to be sent to the CN by the UE. The content ofthe NA 3.The CN sends a response message to the SRNC. -If accepting the request, the CN sends a CONNECTION CONFIRM (CC) messa message, the SRNC confirms that the signaling connection is set up. -lf rejecting the request, the CN sends a CONNECTION REJECT (CJ) message t message, the SRNC confirms that the signaling connection fails to be setup and th
The authentication and security mode control procedure is performed fo
protection algorithm and ciphering algorithm. This procedure ensures integrity and c
Triggerring Conditions: The UE and the CN exchange signaling. The network init
.Radio Bearer Setup .Call Setup
The procedure shown is described as follows: 1.The CN sends a DIRECT TRANSFER message to the SRNC. The message indic 2.The SRNC transparently sends the contents of the DIRECT TRANSFER messag 3.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 4.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER RESPONSE. If the UMTS Subscriber Identity Module (USIM) judges that the authen 5.The CN sends a SECURITY MODE COMMAND message to the SRNC to initiate ciphering and integrity protection algorithms. 6.The SRNC sends a SECURITY MODE COMMAND message to the UE to inform 7.The UE sends a response message to the SRNC. -If the integrity protection and ciphering algorithms are configured successfu then sends a SECURITY MODE COMMAND COMPLETE message to the CN.The UE uses. -If the UE does not support the integrity protection and ciphering algorithms, contains the error information and the reason for the failure. The SRNC then sends
The RANAP:Common ID message is used to transport the permanent UE Iden
Call Setup Procedure(Incoming Call) is performed to setup a call. Triggering Conditions : A UE receiveds a call from the CN The procedure shown is described as follows: .Conversation
1.The CN sends a DIRECT TRANSFER message to the SRNC. The message indic 2.The SRNC transparently sends the contents of the DIRECT TRANSFER messag 3.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 4.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageindicates CALL CONFIRM and contains the information about the negotiat 5. A Radio Access Bearer (RAB) is set up. (see more details in RAB Setup Procedu 6. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 7.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER called terminal to ring. 8.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 9.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER meansthat the called party has answered the call. 10.The CN sends a DIRECT TRANSFER message to the SRNC. The message ind 11.The SRNC transparently sends the contents of the DIRECT TRANSFER messa
The Radio Bearer Setup procedure shown is described as follows: 1.The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initia 2.(Optional; applicable to the ATM-based Iu-CS interface only) The SRNC maps the
called terminal to ring. 8.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 9.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER meansthat the called party has answered the call. 10.The CN sends a DIRECT TRANSFER message to the SRNC. The message ind 11.The SRNC transparently sends the contents of the DIRECT TRANSFER messa
Release
The Radio Bearer Setup procedure shown is described as follows: 1.The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initia 2.(Optional; applicable to the ATM-based Iu-CS interface only) The SRNC maps the radio resource characteristic parameters. Based on the AAL2 link characteristic par 3.The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to t links for carrying the RAB. 4.The NodeB allocates the associated resources and then sends a RADIO LINKRE 5.(Optional; required for the ATM-based Iub interface only) The Iub ALCAP at the S perform synchronization by exchanging uplink and downlink synchronization frames 6.The SRNC sends a RADIO BEARER SETUP message to the UE. 7.The SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to th 8.After performing the radio bearer setup, the UE sends a RADIO BEARER SETUP 9.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The
.RRC Connection Release
The procedure when RAB Setup Failure shown is described as follows: 1.The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initia 2.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The m
The Call Release procedure is performed to release services and resourc Triggering Conditions: A call ends and the calling party hangs up. The procedure shown is described as follows:
1.The CN sends a DIRECT TRANSFER message to the SRNC. The message indic 2.The SRNC transparently sends the contents of the DIRECT TRANSFER messag 3.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 4.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER RELEASE which requests release of the call. 5.The CN sends a DIRECT TRANSFER message to the SRNC. The message indic 6.The SRNC transparently sends the contents of the DIRECT TRANSFER messag 7.The CN sends an IU RELEASE COMMAND message to the SRNC to request ca 8.(Optional; applicable to the ATM-based Iu-CS interface only) The ALCAP protoco 9.The SRNC sends an IU RELEASE COMPLETE message to the CN.
The RRC Connection Release procedure is performed to release the signaling co
Triggering Conditions: After a n RAB is released,the SRNC judges whether the R other RAB of the UE,the SRNC initiates an RRC connection release procedure.
The procedure shown is described as follows: based on the resouce occupied from DCH and release of an RRC connection from CCH (If an RRC connection nee bearers fails to be setup ,the RRC connection on the CCH is released)
1.The SRNC sends an RRC CONNECTION RELEASE message to the UE through (NOTE: The SRNC may send the RRC CONNECTION RELEASE message severa these messages are the same. The number of retransmissions and the transmissio RELEASE COMPLETE message from the UE after sending the RRC CONNECTIO connection.)
2.The UE sends an RRC CONNECTION RELEASE COMPLETE message to the S 3.The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB,r 4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESP
1.The SRNC sends an RRC CONNECTION RELEASE message to the UE through (NOTE: The SRNC may send the RRC CONNECTION RELEASE message severa these messages are the same. The number of retransmissions and the transmissio RELEASE COMPLETE message from the UE after sending the RRC CONNECTIO connection.)
2.The UE sends an RRC CONNECTION RELEASE COMPLETE message to the S 3.The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB,r 4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESP 5.(Optional; required for the ATM-based Iub interface only) The SRNC uses the ALC connection release procedure ends.
med when the CN calls a UE.
PCH modes is described as follows;
a PAGING TYPE 1 message to the UE through the Paging Control Channel (PCCH) on an appropriate occasion.(NOTE The ubscriber Identity (IMSI) of the UE. The UTRAN may page the same UE on several occasions to increase the probability of
ging and receives the paging message from the network layer.The paging procedure ends. mode is described as follows;
a PAGING TYPE 2 message to the UE through the DCCH. ds it, and then reports to the NAS the information such as the paging cause and the paging record type identifier.The paging
or the UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a
es the RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling connection
QUEST message from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or algorithm. If accepting the request, the RRM module further determines whether to set up the RRC connection on a Dedicated d on a specific RRM algorithm. Typically, an RRC connection is set up on the DCH.
message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection. and the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio nd L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the uired for an RRC connection. ESPONSE message to the SRNC after successfully preparing the resources. b user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. essage to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocated by the
ends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state MPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message ds. nnot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to the
erformed to exchange the NAS (Non Access Stratum) information between the UE and the CN.
ransfer message to initiate the signaling connection setup procedure.
:
sage to the SRNC through the RRC connection. The message contains the initial NAS information to be sent to the CN by the
R message from the UE and sendsan INITIAL UE MESSAGE to the CN through the Iu interface. The INITIAL UEMESSAGE he UE. The content ofthe NAS information is PAGING RESPONSE .
ransfer message to initiate the signaling connection setup procedure.
:
sage to the SRNC through the RRC connection. The message contains the initial NAS information to be sent to the CN by the
R message from the UE and sendsan INITIAL UE MESSAGE to the CN through the Iu interface. The INITIAL UEMESSAGE he UE. The content ofthe NAS information is PAGING RESPONSE .
TION CONFIRM (CC) message tothe SRNC. The message indicates that the SCCP connection is set up. After receiving the ction is set up. ON REJECT (CJ) message to the SRNC. The message indicates that the SCCP connection fails to be set up. After receiving the ection fails to be setup and then initiates the RRC release procedure.
procedure is performed for the UE and the network to implement bi-directional authentication and to negotiate and configure the integrity edure ensures integrity and correctness of signaling.
ge signaling. The network initiates the authentication and securitymode control procedure
he SRNC. The message indicates AUTHENTICATION REQUEST. IRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. ssage to the SRNC. PLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION USIM) judges that the authentication is successful, the UE returns a message with an XRES IE. ssage to the SRNC to initiate the security mode control procedure. The message contains the information about the supported
message to the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.
s are configured successfully, the UE sends a SECURITY MODE COMMAND COMPLETE message to the SRNC. The SRNC ETE message to the CN.The message contains the information about the integrity protection and ciphering algorithms that the
and ciphering algorithms, the UE sends a SECURITY MODE COMMAND FAILURE message to the SRNC. The message ilure. The SRNC then sends a SECURITY MODE COMMAND REJECT message to the CN
port the permanent UE Identity(IMSI) to SRNC
ed to setup a call.
om the CN
:
he SRNC. The message indicates SETUP and contains the number of the calling party and the bearer capability of the call. IRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. ssage to the SRNC. PLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message. The DIRECT TRANSFER nformation about the negotiated bearer capability of the call. details in RAB Setup Procedure below) ssage to the SRNC. PLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating ALERTING to request the
ssage to the SRNC. PLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating CONNECT. This
the SRNC. The message indicatesCONNECT ACKNOWLEDGE. DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
ibed as follows: message to the SRNC to initiate the RAB setup procedure. ce only) The SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and
ssage to the SRNC. PLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating CONNECT. This
the SRNC. The message indicatesCONNECT ACKNOWLEDGE. DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
ibed as follows: message to the SRNC to initiate the RAB setup procedure. ce only) The SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and e AAL2 link characteristic parameters,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup procedure. ON PREPARE message to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio
hen sends a RADIO LINKRECONFIGURATION READY message to the SRNC. only) The Iub ALCAP at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SRNC wnlink synchronization frames in the DCH frame protocol. ge to the UE. ON COMMIT message to the NodeB. s a RADIO BEARER SETUP COMPLETE message to the SRNC. SE message to the CN. The RAB isset up.
described as follows: essage to the SRNC to initiate the RAB setup procedure. SE message to the CN. The message indicates the ID of the RAB that fails to be set up and the reason for the failure.
ease services and resources after a call ends.
ng party hangs up.
:
he SRNC. The message indicates DISCONNECT to inform the UE that the calling party has hanged up. IRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. ssage to the SRNC. PLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message. The DIRECT TRANSFER messageindicates
he SRNC. The message indicatesRELEASE COMPLETE. IRECT TRANSFER message to theUE through a DOWNLINK DIRECT TRANSFER message. e to the SRNC to request call releaseon the Iu interface. The message indicates the reason for the Iu release. ce only) The ALCAP protocol on theIu interface initiates an Iu data transport bearer release procedure. sage to the CN.
ed to release the signaling connection and all radio bearers between UE and the UTRAN
SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry ection release procedure.
ed on the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: release of an RRC connectio H (If an RRC connection needs to be released after a successful outgoing call,, the RRC connection on the DCH is released and if a radio CH is released)
E message to the UE through the DCCH. N RELEASE message several times to increase the probability of proper reception of the message by the UE. The RRC SNs of missions and the transmission intervals are determined by the SRNC. If the SRNC does not receive an RRC CONNECTION nding the RRC CONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC
OMPLETE message to the SRNC. EST message to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB. ADIO LINK DELETION RESPONSE message to the SRNC.
E message to the UE through the DCCH. N RELEASE message several times to increase the probability of proper reception of the message by the UE. The RRC SNs of missions and the transmission intervals are determined by the SRNC. If the SRNC does not receive an RRC CONNECTION nding the RRC CONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC
OMPLETE message to the SRNC. EST message to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB. ADIO LINK DELETION RESPONSE message to the SRNC. only) The SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC
casion.(NOTE The he probability of
tifier.The paging
E. One UE has a
connection
hether to accept or ction on a Dedicated
n. es the Radio requesting the
ocedure is optional.
CH allocated by the
he message
T message to the
nt to the CN by the
AL UEMESSAGE
nt to the CN by the
AL UEMESSAGE
ter receiving the
up. After receiving the
otiate and configure the integrity
HENTICATION
bout the supported
ects.
he SRNC. The SRNC algorithms that the
NC. The message
bility of the call.
RANSFER
TING to request the
NECT. This
tic parameters and
NECT. This
tic parameters and er setup procedure. he existing radio
and the SRNC
he failure.
RANSFER messageindicates
se.
ection does not carry
ure: release of an RRC connection DCH is released and if a radio
E. The RRC SNs of C CONNECTION ed the RRC
E. The RRC SNs of C CONNECTION ed the RRC
Then, the RRC
Click to return to main page RRC: Paging Type 1
RRC: RRC Connection Request (RACH)
RRC: RRC Connection Setup (FACH)
value=hex2dec(5)=5 , he
value=hex2dec(0)=0 , he
value=hex2dec(2908)= 10
value=UE capable to sup
value=UE capable to sup
value=Signaling Radio B
value=Radio Bearer Map
value=Signaling Radio B
value=Signaling Radio B
value=Signaling Radio B
value=BLER Target= -20
value=MaxAllowedULTxP
value=(-48*2)= -96 dBm
value= use Closed Loop
value= use long SC on U
value=Spreading Factor
value=Spreading Factor
value=Primary Scramblin
value=Spreading Factor
Cell Identity=RNCid(12bi
value= 000000001011 011
RRC:RRC Connection Setup Complete (DCCH)
value= not support GSM
value= Chipering Algorit
value= UE support Band
value= UE (Powerclass3)
value= support Compres
RANAP: Initial UE Message (MM: Paging Response)
RRC: Initial Direct Transfer (MM: Paging Response)
RRC: Security Mode Command
RRC: Security Mode Complete
RRC: Downlink Direct Transfer (CC: Setup)
RANAP: Direct Transfer (CC: Setup)
RANAP: Direct Transfer (CC: Call Confirmed)
RRC: Uplink Direct Transfer (CC: Call Confirmed)
RRC: Radio Bearer Setup
value= SF64(uplink)-> AM
value=Primary Scramblin
RRC: Radio Bearer Setup Complete
RANAP: Direct Transfer (CC: Alerting)
RRC: Uplink Direct Transfer (CC: Alerting)
RANAP: Direct Transfer (CC: Connect)
RRC: Uplink Direct Transfer (CC: Connect)
RANAP: Direct Transfer (CC: Connect Acknowledge)
RRC:Downlink Direct Transfer (CC: Connect Acknowledge)
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: Direct Transfer (CC: Disconnect)
RRC: Downlink Direct Transfer (CC: Disconnect)
RRC: Uplink Direct Transfer (CC: Release)
RANAP: Direct Transfer (CC: Release)
RANAP: Direct Transfer (CC: Release Complete)
RRC: Uplink Direct Transfer (CC: Release Complete)
RRC: Downlink Direct Transfer (CC: RRC Connection Release)
RRC: Uplink Direct Transfer (CC: RRC Connection Release)
>>"RRC Connection Request Description"
>>"Geographical and UTRAN Entity Identifiers"
value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520
value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
value=hex2dec(2908)= 10504 value= terminatingConversationalcall (CS MTC)
value=(-24+ (44/2))=-2.0 dB
value=hex2dec(6d)=109(Neighbour's Primary Scrambling Code)
value=CPICH Ec/Io invalid
>>"RRC Connection Setup Description"
>>"Geographical and UTRAN Entity Identifiers"
value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520
value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
value=hex2dec(2908)= 10504
value=UE capable to support FDD , not TDD
value=UE capable to support GSM
value=Signaling Radio Bearer Information Setup ,RB-1
value=Radio Bearer Mapping
value=Signaling Radio Bearer Information Setup ,RB-2
value=Signaling Radio Bearer Information Setup ,RB-3
value=Signaling Radio Bearer Information Setup ,RB-4
value=BLER Target= -20 dB value=MaxAllowedULTxPower=24 dBm
value=(-48*2)= -96 dBm (step of 2 dB)
value= use Closed Loop Power Control Algorithm1
value= use long SC on Uplink
value=Spreading Factor 64 (Uplink)
Default Constant
DPCCH_Power_offset
CPICH_RSCP
-22
-96
-80
-22
-96
-70
Note :DPCCH_Power_offset is configured by RNC and deliver
value=Spreading Factor 128 (Downlink)
value=Primary Scrambling code=97
value=Spreading Factor 128 (Downlink)
Cell Identity=RNCid(12bits)+Cellid(16bits) value= 000000001011 0111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610
>>"RRC Connection Setup Complete Description"
value= not support GSM (Locked UMTS Mode)
value= Chipering Algorithm A5/3
value= UE support Band fdd2100 MHz value= UE (Powerclass3) maximum transmitted power =24 dBm
value= support Compressed Mode (CM) uplink and downlink
value= Call B-Party number = 0813713339
>>"Radio Bearer Description"
value= SF64(uplink)-> AMR 12.2
value=Primary Scrambling code=97
value= SF128(downlink)-> AMR 12.2
Cell Identity=RNCid(12bits)+Cellid(16bits) value= 000000001011 0111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610
PCPICH Power
UL Interference UL DPCCH Initial Power
33
-107
-16
33
-107
-26
igured by RNC and delivered to UE in RRC Connection Setup.
1011110010010)=30610
1011110010010)=30610
Click to return to main page
L3 Messages - Video Call (CS64) Call Pro UE
NodeB
S-RNC
1.RRC: RRC Connection Request (RACH) 2.NBAP:Radio Link Setup Req Start Rx 3.NBAP:Radio Link Setup Resp. 4.ALCAP: Iub User Plane Setup RRC Connection Establishment Timing
Start Tx
5.RRC: RRC Connection Setup (FACH) L1 Synchonization NBAP:Synchonization Indicator 6.RRC: RRC Connection Setup Completed (DCH)
1.RRC: Initial Direct Transfer (MM: CM Service Request)
2.RRC: Downlink Direct Transfer (MM: Authentication Request) 3.RRC: Uplink Direct Transfer (MM: Authentication Response)
6.RRC: Security Mode Command 7.RRC: Security Mode Completed 1.RRC: Uplink Direct Transfer (CC: Setup)
4.RRC: Downlink Direct Transfer (CC: Call Proceeding)
3.NBAP: Radio Link Reconfiguration Prepare 4.NBAP: Radio Link Reconfiguration Ready 5.ALCAP: Iub User Plane Setup 6.RRC: Radio Bearer Setup 7.NBAP: Radio Link Reconfiguration Commit Apply new transport format set 8.RRC: Radio Bearer Setup Complete
7.RRC: Downlink Direct Transfer (CC: Alerting) 9.RRC: Downlink Direct Transfer (CC: Connect) 10.RRC: Uplink Direct Transfer (CC: Connect Acknowledge)
Call Established RRC:Measurement Control RRC:Measurement Report
1.RRC: Uplink Direct Transfer (CC: Disconnect)
4.RRC: Downlink Direct Transfer (CC: Release) 5.RRC: Uplink Direct Transfer (CC: Release Complete)
1.RRC: RRC Connection Release 2.RRC: RRC Connection Release Complete 2.RRC:RRC Connection Release Complete 3.NBAP: Radio Link Deletion Request 4.NBAP: Radio Link Deletion Response 5,.ALCAP: Iub User Plane Release
Note the following information about the procedure , 1.The RRC connection can be set up on a DCH or a CCH. This procedure takes the RRC connection set up on the DCH as an example. 2. If IP transport is applied to the Iub interface, no ALCAP procedure is
ll (CS64) Call Procedure S-RNC
CN
>>RRC Procedure Description 1.RRC Connection Setup
SCCP: CR (Connection Request)
2.Signalling Connection Setup 2.RANAP: Initial UE Message (MM: CM Service Request) 3.SCCP: CC (Connection Confirm) 1.RANAP: Direct Transfer (MM: Authentication Request)
4.RANAP: Direct Transfer (MM: Authentication Response) RANAP: Common ID (IMSI) 5.RANAP: Security Mode Command
8.RANAP: Security Mode Complete 2.RANAP: Direct Transfer (CC: Setup)
3.Authentication & Security Mode Control
3.RANAP: Direct Transfer (CC: Call Proceeding) 1.RANAP: RAB Assignment Request 2.ALCAP : Iu User Plane Setup
5. Radio Bearer Setup 4.Call Setup
9.RANAP: RAB Assignment Response 6.RANAP: Direct Transfer (CC: Alerting) 8.RANAP: Direct Transfer (CC: Connect)
11.RANAP: Direct Transfer (CC: Connect Acknowledge)
blished
6.Conversation
2.RANAP: Direct Transfer (CC: Disconnect) 3.RANAP: Direct Transfer (CC: Release)
7.Call Release 6.RANAP: Direct Transfer (CC: Release Complete) 7.RANAP: Iu Release Command 8.ALCAP: Iu User Plane Release 9.RANAP: Iu Release Complete
8.RRC Connection Release
RRC connection setup procedure is performed for the UE to set up a signaling connectio maximum of one RRC connection at a time.
Triggering Conditions : The UE in idle mode intitiates the RRC connection setup procedur
receives an RRC CONNECTION REQUEST message from the UE, the Radio Resource Mana request, based on a specific algorithm. If accepting the request, the RRM module further dete Dedicated Channel (DCH)or on a Common Channel (CCH),based on a specific RRM algorithm
>>RRC Procedure Description .RRC Connection Setup
The procedure shown is described as follows: 1.The UE sends an RRC CONNECTION REQUEST message to the SRNC through the uplink 2.Based on the cause in the RRC connection request and the system resource status, the SRN resources, and L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUES 3.The NodeB responds with a RADIO LINK SETUP RESPONSE message to the SRNC after s 4.The SRNC uses the ALCAP protocol to set up the Iub user plane transport bearer and perfor for the ATM-based Iub interface only. 5.The SRNC sends an RRC CONNECTION SETUP message to the UE through the downlink 6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Synchonization Indicator me 7. The UE sends an RRC CONNECTION SETUP COMPLETE message to the SRNC through indicates that the RRC connection setup procedure ends. If the RNC judges that the RRC connection request cannot be set up (for instance, due to insu theUE, and indicates the reject reason in the message
The signaling connection setup procedure is performed to exchange the NAS (Non Ac .Signalling Connection Setup
Triggering Conditons: The UE sends a direct transfer message to initiate the signaling conne
The procedure shown is described as follows: 1.The UE sends an INITIAL DIRECT TRANSFER message to the SRNC through the RRC co 2.The SRNC receives the INITIAL DIRECT TRANSFER message from the UE and sends an I CN by the UE. The content of the NAS information is CM SERVICE REQUEST. 3.The CN sends a response message to the SRNC. -If accepting the request, the CN sends a CONNECTION CONFIRM (CC) message to the S SRNC confirms that the signaling connection is set up. -If rejecting the request, the CN sends a CONNECTION REJECT (CJ) message to the SRN the SRNC confirms that the signaling connection fails to be setup and then initiates the RRC r .Authentication & Security Mode Control
The authentication and security mode control procedure is performed for the UE an
the integrity protection algorithm and ciphering algorithm. This procedure ensures integrity and
Triggerring Conditions: The UE and the CN exchange signaling. The network initiates the au
The procedure shown is described as follows: 1.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates AUTH 2.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE 3.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 4.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto Module (USIM) judges that the authentication is successful, the UE returns a message with an 5.The CN sends a SECURITY MODE COMMAND message to the SRNC to initiate the securit algorithms. 6.The SRNC sends a SECURITY MODE COMMAND message to the UE to inform the UE of t
The procedure shown is described as follows: 1.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates AUTH 2.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE 3.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 4.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto Module (USIM) judges that the authentication is successful, the UE returns a message with an 5.The CN sends a SECURITY MODE COMMAND message to the SRNC to initiate the securit algorithms. 6.The SRNC sends a SECURITY MODE COMMAND message to the UE to inform the UE of t 7.The UE sends a response message to the SRNC. -If the integrity protection and ciphering algorithms are configured successfully, the UE then sends a SECURITY MODE COMMAND COMPLETE message to the CN.The message -If the UE does not support the integrity protection and ciphering algorithms, the UE se contains the error information and the reason for the failure. The SRNC then sends a SECUR The RANAP:Common ID message is used to transport the permanent UE Identity(IMSI) t
The call setup procedure is performed to set up a call. . Radio Bearer Setup .Call Setup
.Conversation
Triggering Conditions: The UE initiates a call
The procedure shown is described as follows: 1.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. The message conta 2.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto 3.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates CALL 4.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE 5. A Radio Access Bearer (RAB) is set up. (see more details in RAB Setup Procedure below) 6. When the called terminal rings, the CN sends a DIRECT TRANSFER message to the SRNC 7.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE 8.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates CONN 9.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE 10.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 11.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message
The Radio Bearer Setup procedure shown is described as follows: 1.The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the RAB 2.(Optional; applicable to the ATM-based Iu-CS interface only) The SRNC maps the Quality of parameters. Based on the AAL2 link characteristic parameters,the ALCAP on the Iu interface i 3.The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the NodeB, 4.The NodeB allocates the associated resources and then sends a RADIO LINKRECONFIGUR 5.(Optional; required for the ATM-based Iub interface only) The Iub ALCAP at the SRNC initiat uplink and downlink synchronization frames in the DCH frame protocol. 6.The SRNC sends a RADIO BEARER SETUP message to the UE. 7.The SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to theNodeB. 8.After performing the radio bearer setup, the UE sends a RADIO BEARER SETUP COMPLET 9.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The RAB isset u The procedure when RAB Setup Failure shown is described as follows: 1.The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the RAB 2.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The message in
The call release procedure is performed to release services and resources after a call end Triggering Conditions : A call ends and the calling party hangs up
The procedure shown is described as follows: 1.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 2.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto hanged up. 3.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates RELE 4.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE 5.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC.
Release
The procedure shown is described as follows: 1.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 2.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto hanged up. 3.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates RELE 4.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE 5.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 6.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto 7.The CN sends an IU RELEASE COMMAND message to the SRNC to request call release o 8.(Optional; applicable to the ATM-based Iu-CS interface only) The ALCAP protocol on the Iu i 9.The SRNC sends an IU RELEASE COMPLETE message to the CN.
The RRC Connection Release procedure is performed to release the signaling connection a
Triggering Conditions: After a n RAB is released,the SRNC judges whether the RRC connec UE,the SRNC initiates an RRC connection release procedure.
The procedure shown is described as follows: based on the resouce occupied by the RRC an RRC connection from CCH (If an RRC connection needs to be released after a successful bearers fails to be setup ,the RRC connection on the CCH is released)
.RRC Connection Release
1.The SRNC sends an RRC CONNECTION RELEASE message to the UE through the DCCH (NOTE: The SRNC may send the RRC CONNECTION RELEASE message several times to in number of retransmissions and the transmission intervals are determined by the SRNC. If the COMPLETE message from the UE after sending the RRC CONNECTION RELEASE message
2.The UE sends an RRC CONNECTION RELEASE COMPLETE message to the SRNC. 3.The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB,requesting 4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESPONSE mes 5.(Optional; required for the ATM-based Iub interface only) The SRNC uses the ALCAP protoc
to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a
RC connection setup procedure when the NAS of the UE requests the establishment of a signaling connection When the SRNC UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or reject theRRC connection , the RRM module further determines whether to set up the RRC connection on a ed on a specific RRM algorithm. Typically, an RRC connection is set up on the DCH.
o the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection. ystem resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio NetworkTemporary Identity(R RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the specific radio link resources required for an RR E message to the SRNC after successfully preparing the resources. ane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. It is required
o the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocated by the SRNC. AP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message
et up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to
to exchange the NAS (Non Access Stratum) information between the UE and the CN.
e to initiate the signaling connection setup procedure.
he SRNC through the RRC connection. The message contains the initial NAS information to be sent to the CN by the UE. ge from the UE and sends an INITIAL UE MESSAGE to the CN over the Iu interface. The INITIAL UE MESSAGE contains the NAS informat ICE REQUEST.
NFIRM (CC) message to the SRNC. The message indicates that the SCCP connection is set up. After receivingthe message, the
ECT (CJ) message to the SRNC. The message indicates that the SCCP connection fails to be set up. After receiving the message, up and then initiates the RRC release procedure.
ure is performed for the UE and the network to implement bi-directional authentication and to negotiate and configure procedure ensures integrity and correctness of signaling
ng. The network initiates the authentication and securitymode control procedure
. The message indicates AUTHENTICATION REQUEST. RANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. he SRNC. IRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION RESPONSE. If the UMTS S UE returns a message with an XRES IE. he SRNC to initiate the security mode control procedure. The message contains the information about the supported ciphering and integrity
to the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.
. The message indicates AUTHENTICATION REQUEST. RANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. he SRNC. IRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION RESPONSE. If the UMTS S UE returns a message with an XRES IE. he SRNC to initiate the security mode control procedure. The message contains the information about the supported ciphering and integrity
to the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.
figured successfully, the UE sends a SECURITY MODE COMMAND COMPLETE message to the SRNC. The SRNC sage to the CN.The message contains the information about the integrity protection and ciphering algorithms that the UE uses. hering algorithms, the UE sends a SECURITY MODE COMMAND FAILURE message to the SRNC. The message e SRNC then sends a SECURITY MODE COMMAND REJECT message to the CN permanent UE Identity(IMSI) to SRNC
he SRNC. The message contains the number of the called party and the information about the bearer capability of the call. IRECT TRANSFER messageto the CN through a DIRECT TRANSFER message. . The message indicates CALL PROCEEDING and contains the information about the negotiated bearer capability of the call. RANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. RAB Setup Procedure below) ANSFER message to the SRNC. The message indicates ALERTING. RANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. . The message indicates CONNECT, which means that the called party has answered the call. RANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. the SRNC. DIRECT TRANSFER message to the CN through a DIRECT TRANSFER message, indicating CONNECT ACKNOWLEDGE.
ollows: o the SRNC to initiate the RAB setup procedure. The SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and radio resource charact he ALCAP on the Iu interface initiates an Iu user plane transport bearer setup procedure. PARE message to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio links for carrying the RAB s a RADIO LINKRECONFIGURATION READY message to the SRNC. Iub ALCAP at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SRNC perform synchronization by rotocol. UE. MIT message to theNodeB. O BEARER SETUP COMPLETE message to the SRNC. age to the CN. The RAB isset up. d as follows: o the SRNC to initiate the RAB setup procedure. age to the CN. The message indicates the ID of the RAB that fails to be set up and the reason for the failure.
s and resources after a call ends.
s up
he SRNC. IRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating DISCONNECT. This content informs the CN tha
. The message indicates RELEASE to request release of the call. RANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. he SRNC.
he SRNC. IRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating DISCONNECT. This content informs the CN tha
. The message indicates RELEASE to request release of the call. RANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. he SRNC. IRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating RELEASE COMPLETE. SRNC to request call release on the Iu interface. The message indicates the reason for the Iu release The ALCAP protocol on the Iu interface initiates an Iu data transport bearer release procedure. he CN.
ase the signaling connection and all radio bearers between UE and the UTRAN
dges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry other RAB of the
resouce occupied by the RRC connection,there are two types of RRC connection release procedure: release of an RRC connection from D be released after a successful outgoing call,, the RRC connection on the DCH is released and if a radio leased)
e to the UE through the DCCH. SE message several times to increase the probability of proper reception of the message by the UE. The RRC SNs of these messages are th etermined by the SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE NECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC connection.)
E message to the SRNC. sage to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB. K DELETION RESPONSE message to the SRNC. SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC connection release procedu
UE has a
tion When the SRNC heRRC connection
adio NetworkTemporary Identity(RNTI),radio o link resources required for an RRC connection.
is optional. It is required
ated by the SRNC.
age
ge to
CN by the UE. SAGE contains the NAS information to be sent to the
eivingthe message, the receiving the message,
d configure
ATION RESPONSE. If the UMTS Subscriber Identity
supported ciphering and integrity protection
ATION RESPONSE. If the UMTS Subscriber Identity
supported ciphering and integrity protection
C. The SRNC ms that the UE uses. message
ability of the call.
apability of the call.
ACKNOWLEDGE.
meters and radio resource characteristic
g radio links for carrying the RAB.
SRNC perform synchronization by exchanging
e.
T. This content informs the CN that the UE has
T. This content informs the CN that the UE has
MPLETE.
es not carry other RAB of the
ase of an RRC connection from DCH and release of
RC SNs of these messages are the same. The
tion.)
RRC connection release procedure ends.
Click to return to main page RRC:RRC Connection Request (RACH)
>>"RRC Connection Request D
>>"Geographical and UTRAN E
value=hex2dec(5)=5 , hex2d
value=hex2dec(0)=0 , hex2d
value=hex2dec(2908)= 1050
value= OriginatingConversa
value=(-24+ (44/2))=-2.0 dB
RRC:RRC Connection Setup (FACH)
>>"RRC Connection Setup Des
>>"Geographical and UTRAN E
value=hex2dec(5)=5 , hex2d
value=hex2dec(0)=0 , hex2d
value=hex2dec(2908)= 1050
value=UE capable to suppo
value=UE capable to suppo
value=Signaling Radio Bear
value=Radio Bearer Mappin
value=Signaling Radio Bear
value=Signaling Radio Bear
value=Signaling Radio Bear
value=BLER Target= -20 dB
value=MaxAllowedULTxPow
value=(-48*2)= -96 dBm (ste
value= use Closed Loop Po
value= use long SC on Uplin
value=Spreading Factor 64
value=Spreading Factor 128
value=Primary Scrambling c
value=Spreading Factor 128
Cell Identity=RNCid(12bits)+ value= 000000001011 011101
RRC:RRC Connection Setup Complete (DCCH)
>>"RRC Connection Setup Com
value= not support GSM (Lo
value= Chipering Algorithm
value= UE support Band fdd
value= UE (Powerclass3) ma
value= support Compressed
value= UE support Band fdd
RRC: Initial Direct Transfer (MM: CM Service Request)
RANAP:Initial UE Message (MM: CM Service Request)
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)
RRC: Security Mode Command
RRC: Security Mode Complete
RANAP: Direct Transfer (CC: Setup)
value= Call B-Party n
RRC: Uplink Direct Transfer (CC: Setup)
RRC: Downlink Direct Transfer (CC: Call Proceeding)
RANAP: Direct Transfer (CC: Call Proceeding)
RRC: Radio Bearer Setup
RRC: Radio Bearer Setup Complete
RANAP: Direct Transfer (CC: Alerting)
RRC: Downlink Direct Transfer (CC: Alerting)
RANAP: Direct Transfer (CC: Connect)
RRC: Downlink Direct Transfer (CC: Connect)
RANAP: Direct Transfer (CC: Connect Acknowledge)
RRC: Uplink Direct Transfer (CC: Connect Acknowledge)
RANAP: Direct Transfer (CC: Disconnect)
RRC: Uplink Direct Transfer (CC: Disconnect)
RANAP: Direct Transfer (CC: Release)
RRC: Downlink Direct Transfer (CC: Release)
RANAP: Direct Transfer (CC: Release Complete)
RRC: Uplink Direct Transfer (CC: Release Complete)
RRC: Downlink Direct Transfer (CC: RRC Connection Release)
RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)
>>"RRC Connection Request Description"
>>"Geographical and UTRAN Entity Identifiers"
value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520
value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
value=hex2dec(2908)= 10504 value= OriginatingConversationalcall (CS MOC)
value=(-24+ (44/2))=-2.0 dB
>>"RRC Connection Setup Description"
>>"Geographical and UTRAN Entity Identifiers"
value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520
value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
value=hex2dec(2908)= 10504
value=UE capable to support FDD , not TDD
value=UE capable to support GSM
value=Signaling Radio Bearer Information Setup ,RB-1
value=Radio Bearer Mapping
value=Signaling Radio Bearer Information Setup ,RB-2
value=Signaling Radio Bearer Information Setup ,RB-3
value=Signaling Radio Bearer Information Setup ,RB-4
value=BLER Target= -20 dB value=MaxAllowedULTxPower=24 dBm
value=(-48*2)= -96 dBm (step of 2 dB)
Default Constant
DPCCH_Power_offset
CPICH_RSCP
-22
-96
-80
-22
-96
-70
Note :DPCCH_Power_offset is configured by RNC and delivered to UE in RRC Connec value= use Closed Loop Power Control Algorithm1
value= use long SC on Uplink
value=Spreading Factor 64 (Uplink)
value=Spreading Factor 128 (Downlink)
value=Primary Scrambling code=97
value=Spreading Factor 128 (Downlink)
Cell Identity=RNCid(12bits)+Cellid(16bits) value= 000000001011 0111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610
>>"RRC Connection Setup Complete Description"
value= not support GSM (Locked UMTS Mode)
value= Chipering Algorithm A5/3
value= UE support Band fdd2100 MHz
value= UE (Powerclass3) maximum transmitted power =24 dBm
value= support Compressed Mode (CM) uplink and downlink
value= UE support Band fdd1800 MHz
value= Call B-Party number = 0812713339
>>"Radio Bearer Description"
value= SF16(uplink)-> CS64 (VP)
value=Primary Scrambling code=97
value= SF32(downlink)-> CS64 (VP)
Cell Identity=RNCid(12bits)+Cellid(16bits) value= 000000001011 0111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010
PCPICH Power
UL Interference
UL DPCCH Initial Power
33
-107
-16
33
-107
-26
nd delivered to UE in RRC Connection Setup.
1011110010010)=30610
ellid=bin2dec(0111011110010010)=30610
Click to return to main page
L3 Messages - PS(R99 UE
NodeB 1.RRC: RRC Connection Request (RACH)
Start Rx
4.ALCAP: Iub User Plane Setup RRC Connection Establishment Timing
Start Tx
5.RRC: RRC Connection Setup (FACH) L1 Synchonization
8.RRC: RRC Connection Setup Completed (DCH)
If UE already attached to GPRS CN, the UE will only send "GMM:Service Request" message to N/W
RRC: Initial Direct Transfer (GMM: Attach Request)
RRC: Downlink Direct Transfer (GMM: GPRS Identity Request) RRC: Uplink Direct Transfer (GMM: GPRS Identity Response)
RRC: Downlink Direct Transfer (MM: Authentication & Ciphering Request) RRC: Uplink Direct Transfer (MM: Authentication & Ciphering Response)
RRC: Security Mode Command RRC: Security Mode Completed
RRC: Downlink Direct Transfer (MM: Attach Accept) RRC: Uplink Direct Transfer (MM: Attach Completed) RRC: Uplink Direct Transfer (SM: Activate PDP Context Request)
ALCAP: Iub User Plane Setup RRC: Radio Bearer Setup
Apply new transport format set RRC: Radio Bearer Setup Complete RRC:Measurement Control RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept)
PS Session Esta RRC:Measurement Report
ALCAP: Iub User Plane Setup
RRC: Radio Bearer Reconfiguration RRC: Radio Bearer Reconfiguration Complete RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)
RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept)
ALCAP: Iub User Plane Setup
RRC: Uplink Direct Transfer (MM: Detach Request) RRC: Radio Bearer Release RRC: Downlink Direct Transfer (MM: Detach Accept)
RRC: Radio Bearer Release Completed RRC: Downlink Direct Transfer (CC: RRC Connection Release) RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete) RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)
ALCAP: Iub User Plane Release
L3 Messages - PS(R99) Call Procedure S-RNC
tion Request (RACH) 2.NBAP:Radio Link Setup Req 3.NBAP:Radio Link Setup Resp. 4.ALCAP: Iub User Plane Setup
ction Setup (FACH)
7.NBAP:Synchonization Indicator Setup Completed (DCH)
er (GMM: Attach Request)
(GMM: GPRS Identity Request)
MM: GPRS Identity Response)
Authentication & Ciphering Request)
uthentication & Ciphering Response)
Mode Command
Mode Completed
nsfer (MM: Attach Accept)
er (MM: Attach Completed)
: Activate PDP Context Request)
NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready ALCAP: Iub User Plane Setup
Bearer Setup NBAP: Radio Link Reconfiguration Commit Apply new transport format set
er Setup Complete
ement Control
SM: Activate PDP Context Accept)
PS Session Established
ement Report NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready ALCAP: Iub User Plane Setup NBAP: Radio Link Reconfiguration Commit
r Reconfiguration
configuration Complete
Deactivate PDP Context Request)
M: Deactivate PDP Context Accept) NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready ALCAP: Iub User Plane Setup NBAP: Radio Link Reconfiguration Commit
fer (MM: Detach Request)
earer Release
nsfer (MM: Detach Accept)
ALCAP: Iu User Plane Release
Release Completed
(CC: RRC Connection Release)
RC Connection Release Complete)
RC Connection Release Complete) NBAP: Radio Link Deletion Request NBAP: Radio Link Deletion Response ALCAP: Iub User Plane Release
) Call Procedure CN
>>RRC Procedure Description
1.RRC Connection Establishme
RANAP: Initial UE Message GMM: (Attach Request) RANAP: GMM: GPRS Identity Request
2.GPRS Attach Procedure
RANAP: GMM: GPRS Identity Response RANAP: MM: Authentication & Ciphering Request
RANAP:MM: Authentication&Ciphering Response RANAP: Security Mode Command
RANAP: Security Mode Complete RANAP: Common ID(IMSI)
3.Authentication & Security Mod
RANAP: MM: Attach Accept
RANAP: MM: Attach Completed RANAP: SM: Activate PDP Context Request RANAP: RAB Assignment Request ALCAP : Iu User Plane Setup
4.PS Session Setup
5. Radio Bearer Setup
RANAP: RAB Assignment Response RANAP: SM: Activate PDP Context Accept
ablished
6.Downlink and Uplink Data Tra
Radio Bearer Reconfiguration to Upgrade/Downgrade Bit Rate
RANAP: SM: Deactivate PDP Context Request RANAP: SM: Deactivate PDP Context Accept
7.PS Session Release
RANAP: MM: Detach Request RANAP: MM: Detach Accept RANAP: Iu Release Command ALCAP: Iu User Plane Release RANAP: Iu Release Complete
8.RRC Connection Release
cedure Description
onnection Establishment
RRC connection setup procedure is performed for the UE to set up a signaling connectio maximum of one RRC connection at a time.
Triggering Conditions : The UE in idle mode intitiates the RRC connection setup procedur
SRNC receives an RRC CONNECTION REQUEST message from the UE, the Radio Resource connection request, based on a specific algorithm. If accepting the request, the RRM module f (DCH)or on a Common Channel (CCH),based on a specific RRM algorithm. Typically, an RRC
The procedure shown is described as follows: 1.The UE sends an RRC CONNECTION REQUEST message to the SRNC through the uplink 2.Based on the cause in the RRC connection request and the system resource status, the SRN NetworkTemporary Identity(RNTI),radio resources, and L1 and L2 resources. Then the SRNC allocate the specific radio link resources required for an RRC connection. 3.The NodeB responds with a RADIO LINK SETUP RESPONSE message to the SRNC after s 4.The SRNC uses the ALCAP protocol to set up the Iub user plane transport bearer and perfor is required for the ATM-based Iub interface only. 5.The SRNC sends an RRC CONNECTION SETUP message to the UE through the downlink C 6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Synchonization Indicator me 7. The UE sends an RRC CONNECTION SETUP COMPLETE message to the SRNC through indicates that the RRC connection setup procedure ends. If the RNC judges that the RRC connection request cannot be set up (for instance, due to insuf theUE, and indicates the reject reason in the message
The GPRS Attach procedure is performed in order to make UE presence known to the net
data paging via the SGSN, and notification of incoming PS Data.In the attach procedure, the UE PS attach and combined PS / CS attach.The identity provided to the network shall be the UE's
Triggering Conditons: The UE sends a GPRS Attach Request message to initiate the signalin
Attach Procedure
The procedure shown is described as follows: 1.UE initiates the attach procedure by the transmission of an Attach Request message to the R available. RNC opens an SCCP (Signalling Connection Control Part) connection and sends the 2.If the UE identifies itself with P-TMSI and the SGSN has changed since detach, the new SGS request the IMSI. The old SGSN responds with Identification Response (IMSI, Authentication v 3.If the UE is unknown in both the old and new SGSN, the SGSN sends an Identity Request (Id 4. The new SGSN asks the HLR to authenticate the UE. HLR sends back to SGSN the Authen subscriber information The SGSN sends the Authentication and Ciphering Request to the UE. A and AUTN (Authentication Token) to the UE. At reception of this message, the UE (USIM, WCD Authentication and Ciphering response (RES) message to the SGSN. During generation of aut Integrity Key, IK. These keys are stored together with the CKSN (Ciphering key sequence num transmission security. A known bit stream is encrypted and decrypted in SGSN and UE. 5. If the SGSN number has changed since the GPRS detach, or if it is the very first attach, then
tication & Security Mode Control
-The SGSN sends an Update Location (SGSN Number, SGSN Address, IMSI) to the HLR. -The HLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with Cancellation -The old SGSN acknowledges with Cancel Location Ack (IMSI). If there are any ongoing proce the MM (Mobility Management) and PDP contexts -The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN. -The new SGSN validates the UE's presence in the (new) RA (Routing Area). If all checks are s Subscriber Data Ack (IMSI) message to the HLR. -The HLR acknowledges the Update Location message by sending an Update Location Ack to If the Update Location is rejected by the HLR, the SGSN rejects the Attach Request from the U 6. If Attach Type in step 1 indicated PS Attach while already CS attached, or combined PS/CS SGSN starts the location update procedure towards the new MSC/VLR upon receipt of the first the VLR.
-The old SGSN acknowledges with Cancel Location Ack (IMSI). If there are any ongoing proce the MM (Mobility Management) and PDP contexts -The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN. -The new SGSN validates the UE's presence in the (new) RA (Routing Area). If all checks are s Subscriber Data Ack (IMSI) message to the HLR. -The HLR acknowledges the Update Location message by sending an Update Location Ack to If the Update Location is rejected by the HLR, the SGSN rejects the Attach Request from the U 6. If Attach Type in step 1 indicated PS Attach while already CS attached, or combined PS/CS SGSN starts the location update procedure towards the new MSC/VLR upon receipt of the first the VLR.
a. The SGSN sends a Location Update Request (new LAI, IMSI, SGSN Number, Location Upd indicated combined PS / CS attach. Otherwise, Location Update Type shall indicate normal loc b. If the LA update is inter-MSC, the new VLR sends Update Location (IMSI, new VLR) to the H c. If the LA update is inter-MSC, the HLR sends a Cancel Location (IMSI) to the old VLR. d. The old VLR acknowledges with Cancel Location Ack (IMSI). If there are any ongoing proced removing the MM and PDP contexts. e. If the LA update is inter-MSC, the HLR sends Insert Subscriber Data (IMSI, GSM subscriber f. The VLR acknowledges with Insert Subscriber Data Ack (IMSI). g. After finishing the inter-MSC location update procedures, the HLR responds with Update Loc h. The VLR responds with Location Update Accept (VLR TMSI) to the SGSN. 7. The SGSN sends an Attach Accept (P-TMSI, VLR TMSI, P-TMSI Signature, Radio Priority S Request cannot be accepted, the SGSN returns an Attach Reject (IMSI, Cause) message to th
sion Setup
8. If P-TMSI or VLR TMSI was changed, the UE acknowledges the received TMSI(s) with Attac
9. If VLR TMSI was changed, the SGSN confirms the VLR TMSI re-allocation by sending TMSI
earer Setup
The authentication and security mode control procedure is performed for the UE an
the integrity protection algorithm and ciphering algorithm. This procedure ensures integrity and
Triggerring Conditions: The UE and the CN exchange signaling. The network initiates the au The procedure shown is described as follows: 1.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates AUTH 2.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE 3.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. 4.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto UMTS Subscriber Identity Module (USIM) judges that the authentication is successful, the UE 5.The CN sends a SECURITY MODE COMMAND message to the SRNC to initiate the security and integrity protection algorithms. 6.The SRNC sends a SECURITY MODE COMMAND message to the UE to inform the UE of th 7.The UE sends a response message to the SRNC. -If the integrity protection and ciphering algorithms are configured successfully, the UE then sends a SECURITY MODE COMMAND COMPLETE message to the CN.The message c -If the UE does not support the integrity protection and ciphering algorithms, the UE sen contains the error information and the reason for the failure. The SRNC then sends a SECURI The RANAP:Common ID message is used to transport the permanent UE Identity(IMSI) t
The PS Session Setup procedure is performed to set up a PS session and Uplink Data Transfer
Triggering Conditions: The UE send Activate PDP context request message to RNC. PDP C Mobility Management Connected that enables the user to transmitt and receive data while mov virtual data channel between a terminal connected to a UE and a GGSN. PDP contexts deal wi bearer establishes on request of the SGSN in order to realize the air interface connection. At th (Temporary Logical Link Identity) associated to IMSI.
IP addresses can be allocated dynamically or statistically. If allocated dynamically, this significa enables subscribers to provide their own IP addresses. This can be useful when accesing secu QoS enables the operator to differentiate GPRS services.
arer Reconfiguration to Downgrade Bit Rate
ssion Release
Connection Release
Mobility Management Connected that enables the user to transmitt and receive data while mov virtual data channel between a terminal connected to a UE and a GGSN. PDP contexts deal wi bearer establishes on request of the SGSN in order to realize the air interface connection. At th (Temporary Logical Link Identity) associated to IMSI.
IP addresses can be allocated dynamically or statistically. If allocated dynamically, this significa enables subscribers to provide their own IP addresses. This can be useful when accesing secu QoS enables the operator to differentiate GPRS services.
When dynamic addressing from the home PLMN or the Visitor PLMN is used, it is the responsi
The procedure shown is described as follows: 1.The UE sends an Activate PDP Context Request (NSAPI, TI(Teardown Indication), PDP Typ Options) message to the SGSN The UE shall use PDP Address to indicate whether it requires 2. The SGSN sends a RAB Assignment Request message to the RNC to establish a RABs 3.The RNC establishes the appropriate radio bearer In WCDMA, RAB setup is done by the RA 4.The RNC returns a RAB Assignment Response message to the SGSN 5. The SGSN validates the active PDP Context Request using PDP Type (optional), PDP Addre records.The SGSN sends a Create PDP Context Request message to the affected GGSN. Acc Name to find an external network and optionally to activate a service for this APN 6. The GGSN creates a new entry in its PDP context table and generates a Charging Id. The n the SGSN and the external PDP network, and to start charging 7.The SGSN inserts the Network layer Service Access Point Identifier, NSAPI along with the G SGSN selects Radio Priority and Packet flow Id based on QoS Negotiated, and returns an Activ theGGSN and the UE and to start charging
The Radio Bearer Setup procedure shown is described as follows: 1.The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the RAB 2.(Optional; applicable to the ATM-based Iu-CS interface only) The SRNC maps the Quality of characteristic parameters. Based on the AAL2 link characteristic parameters,the ALCAP on the 3.The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the NodeB, r RAB. 4.The NodeB allocates the associated resources and then sends a RADIO LINKRECONFIGUR 5.(Optional; required for the ATM-based Iub interface only) The Iub ALCAP at the SRNC initiate synchronization by exchanging uplink and downlink synchronization frames in the DCH frame p 6.The SRNC sends a RADIO BEARER SETUP message to the UE. 7.The SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to theNodeB. 8.After performing the radio bearer setup, the UE sends a RADIO BEARER SETUP COMPLET 9.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The RAB isset u The procedure when RAB Setup Failure shown is described as follows: 1.The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the RAB 2.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The message ind
The PS session release procedure is performed to release services and resources after
Triggering Conditions : The UE send Deactivate PDP context request message to RNC. A P deactivation,the UE has the state Active. After the PDP Context deactivation procedure the stat PDP contexts activated.PDP Deactivation may be initiated by a:UE procedure,SGSN procedure
The procedure shown is described as follows: 1.The UE sends a Deactivate PDP Context Request (TI, Teardown Indication) message to the 2.The SGSN sends a Delete PDP Context Request (TEID, NSAPI, Teardown Indication) mess message, then the SGSN deactivates all PDP contexts associated with this PDP address by in 3.The GGSN removes the PDP context(s) and returns a delete PDP Context Response (TEID) 4.The SGSN returns a Deactivate PDP Context Accept (TI) message to the UE via the RNC 5. In Iu mode, radio access bearer release is done by the RAB Assignment procedure 6. The SCCP connection between RNC and SGSN is released. At GPRS detach, all PDP conte
3.The GGSN removes the PDP context(s) and returns a delete PDP Context Response (TEID) 4.The SGSN returns a Deactivate PDP Context Accept (TI) message to the UE via the RNC 5. In Iu mode, radio access bearer release is done by the RAB Assignment procedure 6. The SCCP connection between RNC and SGSN is released. At GPRS detach, all PDP conte
The RRC Connection Release procedure is performed to release the signaling connection an
Triggering Conditions: After a n RAB is released,the SRNC judges whether the RRC connec of the UE,the SRNC initiates an RRC connection release procedure.
The procedure shown is described as follows: based on the resouce occupied by the RRC DCH and release of an RRC connection from CCH (If an RRC connection needs to be released a radio bearers fails to be setup ,the RRC connection on the CCH is released)
1.The SRNC sends an RRC CONNECTION RELEASE message to the UE through the DCCH. (NOTE: The SRNC may send the RRC CONNECTION RELEASE message several times to in the same. The number of retransmissions and the transmission intervals are determined by the COMPLETE message from the UE after sending the RRC CONNECTION RELEASE message
2.The UE sends an RRC CONNECTION RELEASE COMPLETE message to the SRNC. 3.The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB,requesting t 4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESPONSE mes 5.(Optional; required for the ATM-based Iub interface only) The SRNC uses the ALCAP protoco procedure ends.
e UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a
he RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling connection When the ge from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or reject the RRC ting the request, the RRM module further determines whether to set up the RRC connection on a Dedicated Channel RRM algorithm. Typically, an RRC connection is set up on the DCH.
ge to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection. he system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to C connection. NSE message to the SRNC after successfully preparing the resources. r plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. It
ge to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocated by the SRNC. NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state TE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message
be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to
make UE presence known to the network by performing a Packet Service Attach (GPRS attach). This makes the UE available for SMS over P Data.In the attach procedure, the UE shall provide its identity and an indication of which type of attach that is to be executed. ed to the network shall be the UE's Packet TMSI (P-TMSI) or IMSI
uest message to initiate the signaling connection setup procedure.
n Attach Request message to the RNC. IMSI shall be included if the UE does not have a valid P-TMSI (Packet Temporary IMSI) trol Part) connection and sends the Attach request to SGSN hanged since detach, the new SGSN sends an Identification Request (P-TMSI, old RAI, old P-TMSI Signature) to the old SGSN to n Response (IMSI, Authentication vector). The old SGSN also validates the old P-TMSI SGSN sends an Identity Request (Identity Type = IMSI) to the UE. The UE responds with Identity Response (IMSI). R sends back to SGSN the Authentication data received from AUC (Authentication Center). The HLR contains GSM and WCDMA and Ciphering Request to the UE. At authentication of a WCDMA subscriber, the SGSN transmitts the RAND (Random Number) this message, the UE (USIM, WCDMA Subscriber Identity module in the UE) verifies AUTN and if accepted the UE returns an he SGSN. During generation of authentication vectors, the USIM in the UE also computes a new Ciphering Key. CK, and a new KSN (Ciphering key sequence number of Kc) until CKSN is updated at the next authentication. The SGSN verifies the decrypted in SGSN and UE. h, or if it is the very first attach, then the SGSN informs the HLR:
SN Address, IMSI) to the HLR. to the old SGSN with Cancellation Type set to Update Procedure. MSI). If there are any ongoing procedures for that UE, the old SGSN shall wait until these procedures are finished before removing
ription data) to the new SGSN. A (Routing Area). If all checks are successful then the SGSN constructs an MM context for the UE and returns an Insert
sending an Update Location Ack to the SGSN after the canceling of old MM context and insertion of new MM context are finished. ects the Attach Request from the UE with an appropriate cause code CS attached, or combined PS/CS attach, then the VLR shall be updated. The VLR number is received from the RA information. The w MSC/VLR upon receipt of the first Insert Subscriber Data message from the HLR. This operation marks the UE as GPRS-attached in
MSI). If there are any ongoing procedures for that UE, the old SGSN shall wait until these procedures are finished before removing
ription data) to the new SGSN. A (Routing Area). If all checks are successful then the SGSN constructs an MM context for the UE and returns an Insert
sending an Update Location Ack to the SGSN after the canceling of old MM context and insertion of new MM context are finished. ects the Attach Request from the UE with an appropriate cause code CS attached, or combined PS/CS attach, then the VLR shall be updated. The VLR number is received from the RA information. The w MSC/VLR upon receipt of the first Insert Subscriber Data message from the HLR. This operation marks the UE as GPRS-attached in
MSI, SGSN Number, Location Update Type) message to the VLR. Location Update Type shall indicate CS attach if Attach Type date Type shall indicate normal location update. The VLR creates an association with the SGSN by storing SGSN Number. e Location (IMSI, new VLR) to the HLR. ocation (IMSI) to the old VLR. SI). If there are any ongoing procedures for that MS, the old SGSN shall wait until these procedures are finished before
criber Data (IMSI, GSM subscriber data) to the new VLR. IMSI). the HLR responds with Update Location Ack (IMSI) to the new VLR. MSI) to the SGSN. P-TMSI Signature, Radio Priority SMS) message to the UE. P-TMSI is included if the SGSN allocates a new P-TMSI. If the Attach Reject (IMSI, Cause) message to the UE
ges the received TMSI(s) with Attach Complete (P-TMSI, VLR TMSI).
TMSI re-allocation by sending TMSI Reallocation Complete (VLR TMSI) to the VLR.
cedure is performed for the UE and the network to implement bi-directional authentication and to negotiate and configure
his procedure ensures integrity and correctness of signaling
naling. The network initiates the authentication and securitymode control procedure
RNC. The message indicates AUTHENTICATION REQUEST. CT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message. to the SRNC. K DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION RESPONSE. If the uthentication is successful, the UE returns a message with an XRES IE. e to the SRNC to initiate the security mode control procedure. The message contains the information about the supported ciphering
age to the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.
configured successfully, the UE sends a SECURITY MODE COMMAND COMPLETE message to the SRNC. The SRNC message to the CN.The message contains the information about the integrity protection and ciphering algorithms that the UE uses. ciphering algorithms, the UE sends a SECURITY MODE COMMAND FAILURE message to the SRNC. The message . The SRNC then sends a SECURITY MODE COMMAND REJECT message to the CN he permanent UE Identity(IMSI) to SRNC
up a PS session
t request message to RNC. PDP Context Activation is performed when the UE initiates a packet call setup. The UE has the state Packet ansmitt and receive data while moving within a PLMN. and starts the PDP context activation procedure used to set up and remove a and a GGSN. PDP contexts deal with allocation of IP addresses to the UE and Quality of Service, QoS, parameters. A Radio Access e the air interface connection. At the end the UE has an IP address NSAPI (Network layer Service Access Point Identifier) and a TLLI
allocated dynamically, this significantly reduces the total number of IP addresses required per PLMN. Support of static IP address allocation can be useful when accesing secure networks that use the calling IP address as a form of security check. The support of
ansmitt and receive data while moving within a PLMN. and starts the PDP context activation procedure used to set up and remove a and a GGSN. PDP contexts deal with allocation of IP addresses to the UE and Quality of Service, QoS, parameters. A Radio Access e the air interface connection. At the end the UE has an IP address NSAPI (Network layer Service Access Point Identifier) and a TLLI
allocated dynamically, this significantly reduces the total number of IP addresses required per PLMN. Support of static IP address allocation can be useful when accesing secure networks that use the calling IP address as a form of security check. The support of
tor PLMN is used, it is the responsibility of the GGSN to allocate and release the dynamic PDP address.
TI(Teardown Indication), PDP Type, Address, APN (Access Point Name), QoS (Quality of Service) Requested, PDP Configuration ress to indicate whether it requires the use of a static PDP address or whether it requires the use of a dynamic PDP address. o the RNC to establish a RABs DMA, RAB setup is done by the RAB Assignment procedure to the SGSN ng PDP Type (optional), PDP Address, APN (Access Point Name (optional) provided by the UE and the PDP context subscription message to the affected GGSN. Access Point Name shall be the APN Network Identifier of the APN. The GGSN may use Access Point a service for this APN nd generates a Charging Id. The new entry allows the GGSN to route PDP PDUs (Policy Decision Point Protocol Data Units) between ing t Identifier, NSAPI along with the GGSN address in its PDP context and informs the UE via RNC that the PDP Context is Accepted. The oS Negotiated, and returns an Activate PDP Context Accept message to the UE. The SGSN is now able to route PDP PDUs between
as follows: ge to the SRNC to initiate the RAB setup procedure. ly) The SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and radio resource ristic parameters,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup procedure. REPARE message to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio links for carrying the
ends a RADIO LINKRECONFIGURATION READY message to the SRNC. The Iub ALCAP at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SRNC perform nization frames in the DCH frame protocol. the UE. OMMIT message to theNodeB. ADIO BEARER SETUP COMPLETE message to the SRNC. essage to the CN. The RAB isset up. ibed as follows: ge to the SRNC to initiate the RAB setup procedure. essage to the CN. The message indicates the ID of the RAB that fails to be set up and the reason for the failure.
ease services and resources after a session ends.
ntext request message to RNC. A PDP Context Deactivation is performed when the UE terminates a packet call. Before the text deactivation procedure the state becomes Packet Mobility Management Connected.The RAB will be released if there are no other y a:UE procedure,SGSN procedure,GGSN procedure
ardown Indication) message to the SGSN via the RNC NSAPI, Teardown Indication) message to the GGSN. If Teardown Indication was included by the UE in the Deactivate PDP Context Request ociated with this PDP address by including Teardown Indication in the Delete PDP Context Request message ete PDP Context Response (TEID) message to the SGSN. The Delete PDP Context messages are sent over the backbone network message to the UE via the RNC AB Assignment procedure sed. At GPRS detach, all PDP contexts for the UE are implicitly deactivated
ete PDP Context Response (TEID) message to the SGSN. The Delete PDP Context messages are sent over the backbone network message to the UE via the RNC AB Assignment procedure sed. At GPRS detach, all PDP contexts for the UE are implicitly deactivated
release the signaling connection and all radio bearers between UE and the UTRAN
C judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry other RAB ocedure.
n the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: release of an RRC connection from RC connection needs to be released after a successful outgoing call,, the RRC connection on the DCH is released and if e CCH is released)
ssage to the UE through the DCCH. LEASE message several times to increase the probability of proper reception of the message by the UE. The RRC SNs of these messages a sion intervals are determined by the SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE CONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC connection.)
LETE message to the SRNC. message to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB. LINK DELETION RESPONSE message to the SRNC. The SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC connection release
UE has a
ection When the or reject the RRC Channel
Radio ng the NodeB to
e is optional. It
ocated by the SRNC.
ssage
sage to
he UE available for SMS over PS o be executed.
et Temporary IMSI)
e) to the old SGSN to
MSI). s GSM and WCDMA D (Random Number) the UE returns an ey. CK, and a new rifies the
hed before removing
ns an Insert
context are finished.
the RA information. The UE as GPRS-attached in
hed before removing
ns an Insert
context are finished.
the RA information. The UE as GPRS-attached in
tach if Attach Type GSN Number.
hed before
P-TMSI. If the Attach
and configure
CATION RESPONSE. If the
e supported ciphering
NC. The SRNC hms that the UE uses. he message
he UE has the state Packet to set up and remove a meters. A Radio Access oint Identifier) and a TLLI
rt of static IP address allocation he support of
to set up and remove a meters. A Radio Access oint Identifier) and a TLLI
rt of static IP address allocation he support of
ed, PDP Configuration c PDP address.
context subscription SN may use Access Point
ocol Data Units) between
P Context is Accepted. The oute PDP PDUs between
ameters and radio resource
ting radio links for carrying the
e SRNC perform
ure.
call. Before the ased if there are no other
eactivate PDP Context Request
r the backbone network
r the backbone network
does not carry other RAB
ease of an RRC connection from ased and if
RRC SNs of these messages are
ection.)
he RRC connection release
Click to return to main page RRC:RRC Connection Request (RACH)
>>"RRC Connection Request Desc
>>"Geographical and UTRAN Entit
value=hex2dec(5)=5 , hex2dec
value=hex2dec(0)=0 , hex2dec
value=hex2dec(2908)= 10504
value= OriginatingBackground
value=(-24+ (33/2))=-7.5 dB
RRC:RRC Connection Setup (FACH)
>>"RRC Connection Setup Descrip
>>"Geographical and UTRAN Entit
value=hex2dec(5)=5 , hex2dec
value=hex2dec(0)=0 , hex2dec
value=hex2dec(2908)= 10504
value=UE capable to support F
value=UE capable to support G
value=Signaling Radio Bearer
value=Radio Bearer Mapping
value=Signaling Radio Bearer
value=Signaling Radio Bearer
value=Signaling Radio Bearer
value=BLER Target= -20 dB
value=MaxAllowedULTxPower
value=(-48*2)= -96 dBm (step o
value= use Closed Loop Powe
value= use long SC on Uplink
value=Spreading Factor 64 (Up
value=Spreading Factor 128 (D
value=Primary Scrambling cod
value=Spreading Factor 128 (D
Cell Identity=RNCid(12bits)+Ce value= 000000001011 01110111
RRC:RRC Connection Setup Complete (DCCH)
>>"RRC Connection Setup Comple
value= not support GSM (Lock
value= Chipering Algorithm A5
value= UE support Band fdd21
value= UE (Powerclass3) maxi
value= support Compressed M
value= UE support Band fdd18
value= not support HSDPA
RANAP: Initial UE Message GMM: (Attach Request)
RRC: Initial Direct Transfer (GMM: Attach Request)
RANAP: MM: Authentication & Ciphering Request
RRC: Downlink Direct Transfer (MM: Authentication & Ciphering Request)
RRC: Uplink Direct Transfer (MM: Authentication & Ciphering Response)
RANAP:MM: Authentication&Ciphering Response
RRC: Security Mode Command
RRC: Security Mode Complete
RANAP: MM: Attach Accept
RRC: Downlink Direct Transfer (MM: Attach Accept)
RRC: Uplink Direct Transfer (MM: Attach Completed)
RANAP: MM: Attach Completed
RRC: Uplink Direct Transfer (SM: Activate PDP Context Request)
RANAP: SM: Activate PDP Context Request
RRC: Radio Bearer Setup
RRC: Radio Bearer Setup Complete
RANAP: SM: Activate PDP Context Accept
RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept)
RRC: Radio Bearer Reconfiguration
RRC: Radio Bearer Reconfiguration Complete
RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)
RANAP: SM: Deactivate PDP Context Request
RANAP: SM: Deactivate PDP Context Accept
RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept)
RRC: Radio Bearer Release
RRC: Radio Bearer Release Completed
RRC: Downlink Direct Transfer (CC: RRC Connection Release)
RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)
RRC: Uplink Direct Transfer (MM: Detach Request)
RANAP: MM: Detach Request
RANAP: MM: Detach Accept
RRC: Downlink Direct Transfer (MM: Detach Accept)
"RRC Connection Request Description"
"Geographical and UTRAN Entity Identifiers"
lue=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520
lue=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
lue=hex2dec(2908)= 10504
lue= OriginatingBackgroundCall (PS MOC)
lue=(-24+ (33/2))=-7.5 dB
"RRC Connection Setup Description"
"Geographical and UTRAN Entity Identifiers"
lue=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520
lue=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
lue=hex2dec(2908)= 10504
lue=UE capable to support FDD , not TDD
lue=UE capable to support GSM
lue=Signaling Radio Bearer Information Setup ,RB-1
lue=Radio Bearer Mapping
lue=Signaling Radio Bearer Information Setup ,RB-2
lue=Signaling Radio Bearer Information Setup ,RB-3
lue=Signaling Radio Bearer Information Setup ,RB-4
lue=BLER Target= -20 dB
lue=MaxAllowedULTxPower=24 dBm
lue=(-48*2)= -96 dBm (step of 2 dB)
lue= use Closed Loop Power Control Algorithm1
lue= use long SC on Uplink
Default Constant
DPCCH_Power_offset
CPICH_RSCP
-22
-96
-80
-22
-96
-70
Note :DPCCH_Power_offset is configured by RNC and delivered to UE in RRC Connection Setu
lue=Spreading Factor 64 (Uplink)
lue=Spreading Factor 128 (Downlink)
lue=Primary Scrambling code=97
lue=Spreading Factor 128 (Downlink)
ell Identity=RNCid(12bits)+Cellid(16bits) lue= 000000001011 0111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610
"RRC Connection Setup Complete Description"
lue= not support GSM (Locked UMTS Mode)
lue= Chipering Algorithm A5/3
lue= UE support Band fdd2100 MHz
lue= UE (Powerclass3) maximum transmitted power =24 dBm
lue= support Compressed Mode (CM) uplink and downlink
lue= UE support Band fdd1800 MHz
lue= not support HSDPA
>>"Radio Bearer Description"
value= SF16(uplink)-> PS64
value=Primary Scrambling code=97
value= SF32(downlink)-> PS64
Cell Identity=RNCid(12bits)+Cellid(16bits) value= 000000001011 0111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610
value= SF16(uplink)-> PS64
value= SF16(downlink)-> PS128
PCPICH Power
UL Interference
UL DPCCH Initial Power
33
-107
-16
33
-107
-26
nd delivered to UE in RRC Connection Setup.
1011110010010)=30610
d=bin2dec(0111011110010010)=30610
Click to return to main page
L3 Messages - PS(HSDPA) Call Proc UE
NodeB
S-RNC
1.RRC: RRC Connection Request (RACH) 2.NBAP:Radio Link Setup Req Start Rx 3.NBAP:Radio Link Setup Resp. 4.ALCAP: Iub User Plane Setup RRC Connection Establishment Timing
Start Tx
5.RRC: RRC Connection Setup (FACH) L1 Synchonization 7.NBAP:Synchonization Indicator 8.RRC: RRC Connection Setup Completed (DCH)
RRC: Initial Direct Transfer (GMM: Service Request)
RRC: Security Mode Command RRC: Security Mode Completed
RRC: Uplink Direct Transfer (SM: Activate PDP Context Request)
NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready
ALCAP: Iub User Plane Setup RRC: Radio Bearer Setup NBAP: Radio Link Reconfiguration Commit Apply new transport format set RRC: Radio Bearer Setup Complete RRC:Measurement Control RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept)
PS Session Established RRC:Measurement Report (e1d) NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready ALCAP: Iub User Plane Setup NBAP: Radio Link Reconfiguration Commit
RRC: Physical Channel Reconfiguration (DCCH) RRC:Physical Channel Reconfiguration Complete (DCCH)
RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)
RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept) NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready
ALCAP: Iub User Plane Setup NBAP: Radio Link Reconfiguration Commit RRC: Radio Bearer Release
RRC: Radio Bearer Release Completed RRC: Downlink Direct Transfer (CC: RRC Connection Release) RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete) RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete) NBAP: Radio Link Deletion Request NBAP: Radio Link Deletion Response ALCAP: Iub User Plane Release
SDPA) Call Procedure S-RNC
CN
etup
>>RRC Procedure Description
1.RRC Connection Establi
RANAP: GMM:Service Request
RANAP: Security Mode Command
RANAP: Security Mode Complete RANAP: Common ID(IMSI)
RANAP: SM: Activate PDP Context Request RANAP: RAB Assignment Request ALCAP : Iu User Plane Setup
2.PS Session Setup
etup
3. Radio Bearer Setup
set
RANAP: RAB Assignment Response RANAP: SM: Activate PDP Context Accept
n Established
4. Downlink and Uplink Da
etup
HSDPA's Serving Cell Chan
RANAP: SM: Deactivate PDP Context Request RANAP: SM: Deactivate PDP Context Accept
5.PS Session Release
etup
ease
RANAP: Iu Release Command ALCAP: Iu User Plane Release RANAP: Iu Release Complete
6.RRC Connection Relea
RRC connection setup procedure is performed for the UE to set up a signalin maximum of one RRC connection at a time.
Triggering Conditions : The UE in idle mode intitiates the RRC connection setu
SRNC receives an RRC CONNECTION REQUEST message from the UE, the Rad connection request, based on a specific algorithm. If accepting the request, the RR (DCH)or on a Common Channel (CCH),based on a specific RRM algorithm. Typica
>>RRC Procedure Description .RRC Connection Establishment
The procedure shown is described as follows: 1.The UE sends an RRC CONNECTION REQUEST message to the SRNC throug 2.Based on the cause in the RRC connection request and the system resource stat NetworkTemporary Identity(RNTI),radio resources, and L1 and L2 resources. Then allocate the specific radio link resources required for an RRC connection. 3.The NodeB responds with a RADIO LINK SETUP RESPONSE message to the S 4.The SRNC uses the ALCAP protocol to set up the Iub user plane transport beare is required for the ATM-based Iub interface only. 5.The SRNC sends an RRC CONNECTION SETUP message to the UE through th 6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Synchonization I 7. The UE sends an RRC CONNECTION SETUP COMPLETE message to the SR indicates that the RRC connection setup procedure ends. If the RNC judges that the RRC connection request cannot be set up (for instance, theUE, and indicates the reject reason in the message
The PS Session Setup procedure is performed to set up a PS session
Triggering Conditions: The UE send Activate PDP context request message to R Mobility Management Connected that enables the user to transmitt and receive dat virtual data channel between a terminal connected to a UE and a GGSN. PDP cont bearer establishes on request of the SGSN in order to realize the air interface conn (Temporary Logical Link Identity) associated to IMSI.
IP addresses can be allocated dynamically or statistically. If allocated dynamically, t enables subscribers to provide their own IP addresses. This can be useful when ac QoS enables the operator to differentiate GPRS services.
.PS Session Setup
When dynamic addressing from the home PLMN or the Visitor PLMN is used, it is t The procedure shown is described as follows: 1. The UE initiates the PS Session by using the Service Request (Service Type=Da sets-up an SCCP connection with the SGSN and transfers the initial service reque 2 .The UE sends an Activate PDP Context Request (NSAPI, TI(Teardown Indication Options) message to the SGSN The UE shall use PDP Address to indicate whethe 3. The SGSN sends a RAB Assignment Request message to the RNC to establish 4.The RNC establishes the appropriate radio bearer In WCDMA, RAB setup is don 5.The RNC returns a RAB Assignment Response message to the SGSN 6. The SGSN validates the active PDP Context Request using PDP Type (optional) records.The SGSN sends a Create PDP Context Request message to the affected Name to find an external network and optionally to activate a service for this APN 7. The GGSN creates a new entry in its PDP context table and generates a Chargin the SGSN and the external PDP network, and to start charging 8.The SGSN inserts the Network layer Service Access Point Identifier, NSAPI along SGSN selects Radio Priority and Packet flow Id based on QoS Negotiated, and retu theGGSN and the UE and to start charging The Radio Bearer Setup procedure shown is described as follows:
records.The SGSN sends a Create PDP Context Request message to the affected Name to find an external network and optionally to activate a service for this APN 7. The GGSN creates a new entry in its PDP context table and generates a Chargin the SGSN and the external PDP network, and to start charging 8.The SGSN inserts the Network layer Service Access Point Identifier, NSAPI along SGSN selects Radio Priority and Packet flow Id based on QoS Negotiated, and retu theGGSN and the UE and to start charging
. Radio Bearer Setup
The Radio Bearer Setup procedure shown is described as follows: 1.The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initia 2.(Optional; applicable to the ATM-based Iu-CS interface only) The SRNC maps the characteristic parameters. Based on the AAL2 link characteristic parameters,the AL 3.The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to t RAB. 4.The NodeB allocates the associated resources and then sends a RADIO LINKRE 5.(Optional; required for the ATM-based Iub interface only) The Iub ALCAP at the S synchronization by exchanging uplink and downlink synchronization frames in the D 6.The SRNC sends a RADIO BEARER SETUP message to the UE. 7.The SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to the 8.After performing the radio bearer setup, the UE sends a RADIO BEARER SETUP 9.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The R The procedure when RAB Setup Failure shown is described as follows: 1.The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initia 2.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The m
The PS session release procedure is performed to release services and reso
Triggering Conditions : The UE send Deactivate PDP context request message deactivation,the UE has the state Active. After the PDP Context deactivation proced PDP contexts activated.PDP Deactivation may be initiated by a:UE procedure,SGS
. Downlink and Uplink Data Transfer
The procedure shown is described as follows: 1.The UE sends a Deactivate PDP Context Request (TI, Teardown Indication) mes 2.The SGSN sends a Delete PDP Context Request (TEID, NSAPI, Teardown Indic message, then the SGSN deactivates all PDP contexts associated with this PDP ad 3.The GGSN removes the PDP context(s) and returns a delete PDP Context Respo 4.The SGSN returns a Deactivate PDP Context Accept (TI) message to the UE via 5. In Iu mode, radio access bearer release is done by the RAB Assignment procedu 6. The SCCP connection between RNC and SGSN is released. At GPRS detach, a
HSDPA's Serving Cell Change
The RRC Connection Release procedure is performed to release the signaling co
Triggering Conditions: After a n RAB is released,the SRNC judges whether the R of the UE,the SRNC initiates an RRC connection release procedure.
The procedure shown is described as follows: based on the resouce occupied DCH and release of an RRC connection from CCH (If an RRC connection needs to a radio bearers fails to be setup ,the RRC connection on the CCH is released)
1.The SRNC sends an RRC CONNECTION RELEASE message to the UE through (NOTE: The SRNC may send the RRC CONNECTION RELEASE message severa the same. The number of retransmissions and the transmission intervals are determ COMPLETE message from the UE after sending the RRC CONNECTION RELEAS
2.The UE sends an RRC CONNECTION RELEASE COMPLETE message to the S 3.The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB, 4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESP 5.(Optional; required for the ATM-based Iub interface only) The SRNC uses the AL procedure ends.
(NOTE: The SRNC may send the RRC CONNECTION RELEASE message severa the same. The number of retransmissions and the transmission intervals are determ COMPLETE message from the UE after sending the RRC CONNECTION RELEAS
.PS Session Release
.RRC Connection Release
2.The UE sends an RRC CONNECTION RELEASE COMPLETE message to the S 3.The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB, 4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESP 5.(Optional; required for the ATM-based Iub interface only) The SRNC uses the AL procedure ends.
rmed for the UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a
e intitiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling connection When the EST message from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or reject the RRC hm. If accepting the request, the RRM module further determines whether to set up the RRC connection on a Dedicated Channel n a specific RRM algorithm. Typically, an RRC connection is set up on the DCH.
s: EST message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection. quest and the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio es, and L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to d for an RRC connection. UP RESPONSE message to the SRNC after successfully preparing the resources. the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. It . TUP message to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocated by the SRNC odeB sends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state P COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message ure ends. est cannot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to essage
rmed to set up a PS session
PDP context request message to RNC. PDP Context Activation is performed when the UE initiates a packet call setup. The UE has the state he user to transmitt and receive data while moving within a PLMN. and starts the PDP context activation procedure used to set up and remov ed to a UE and a GGSN. PDP contexts deal with allocation of IP addresses to the UE and Quality of Service, QoS, parameters. A Radio Acc der to realize the air interface connection. At the end the UE has an IP address NSAPI (Network layer Service Access Point Identifier) and a MSI.
atistically. If allocated dynamically, this significantly reduces the total number of IP addresses required per PLMN. Support of static IP addres resses. This can be useful when accesing secure networks that use the calling IP address as a form of security check. The support of services.
N or the Visitor PLMN is used, it is the responsibility of the GGSN to allocate and release the dynamic PDP address. s: Service Request (Service Type=Data) message. After the RR setup completion the UE asks for initial direct transfer to the serving node. The d transfers the initial service request (Authentication and ciphering may performed depends on operator's setting) est (NSAPI, TI(Teardown Indication), PDP Type, Address, APN (Access Point Name), QoS (Quality of Service) Requested, PDP Configurat se PDP Address to indicate whether it requires the use of a static PDP address or whether it requires the use of a dynamic PDP address. t message to the RNC to establish a RABs arer In WCDMA, RAB setup is done by the RAB Assignment procedure e message to the SGSN Request using PDP Type (optional), PDP Address, APN (Access Point Name (optional) provided by the UE and the PDP context subscriptio t Request message to the affected GGSN. Access Point Name shall be the APN Network Identifier of the APN. The GGSN may use Access to activate a service for this APN ntext table and generates a Charging Id. The new entry allows the GGSN to route PDP PDUs (Policy Decision Point Protocol Data Units) bet o start charging Access Point Identifier, NSAPI along with the GGSN address in its PDP context and informs the UE via RNC that the PDP Context is Accepte based on QoS Negotiated, and returns an Activate PDP Context Accept message to the UE. The SGSN is now able to route PDP PDUs bet
described as follows:
t Request message to the affected GGSN. Access Point Name shall be the APN Network Identifier of the APN. The GGSN may use Access to activate a service for this APN ntext table and generates a Charging Id. The new entry allows the GGSN to route PDP PDUs (Policy Decision Point Protocol Data Units) bet o start charging Access Point Identifier, NSAPI along with the GGSN address in its PDP context and informs the UE via RNC that the PDP Context is Accepte based on QoS Negotiated, and returns an Activate PDP Context Accept message to the UE. The SGSN is now able to route PDP PDUs bet
described as follows: EST message to the SRNC to initiate the RAB setup procedure. interface only) The SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and radio re nk characteristic parameters,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup procedure. URATION PREPARE message to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio links for c
s and then sends a RADIO LINKRECONFIGURATION READY message to the SRNC. rface only) The Iub ALCAP at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SRNC perform ink synchronization frames in the DCH frame protocol. message to the UE. URATION COMMIT message to theNodeB. E sends a RADIO BEARER SETUP COMPLETE message to the SRNC. SPONSE message to the CN. The RAB isset up. wn is described as follows: EST message to the SRNC to initiate the RAB setup procedure. SPONSE message to the CN. The message indicates the ID of the RAB that fails to be set up and the reason for the failure.
ormed to release services and resources after a session ends.
ate PDP context request message to RNC. A PDP Context Deactivation is performed when the UE terminates a packet call. Before the he PDP Context deactivation procedure the state becomes Packet Mobility Management Connected.The RAB will be released if there are no be initiated by a:UE procedure,SGSN procedure,GGSN procedure
s: uest (TI, Teardown Indication) message to the SGSN via the RNC est (TEID, NSAPI, Teardown Indication) message to the GGSN. If Teardown Indication was included by the UE in the Deactivate PDP Cont ontexts associated with this PDP address by including Teardown Indication in the Delete PDP Context Request message eturns a delete PDP Context Response (TEID) message to the SGSN. The Delete PDP Context messages are sent over the backbone netw Accept (TI) message to the UE via the RNC ne by the RAB Assignment procedure SN is released. At GPRS detach, all PDP contexts for the UE are implicitly deactivated
erformed to release the signaling connection and all radio bearers between UE and the UTRAN
ed,the SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry other n release procedure.
s: based on the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: release of an RRC con CH (If an RRC connection needs to be released after a successful outgoing call,, the RRC connection on the DCH is released and if ection on the CCH is released)
LEASE message to the UE through the DCCH. CTION RELEASE message several times to increase the probability of proper reception of the message by the UE. The RRC SNs of these he transmission intervals are determined by the SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE g the RRC CONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC connection.)
ASE COMPLETE message to the SRNC. REQUEST message to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB. s a RADIO LINK DELETION RESPONSE message to the SRNC. rface only) The SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC connection
CTION RELEASE message several times to increase the probability of proper reception of the message by the UE. The RRC SNs of these he transmission intervals are determined by the SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE g the RRC CONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC connection.)
ASE COMPLETE message to the SRNC. REQUEST message to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB. s a RADIO LINK DELETION RESPONSE message to the SRNC. rface only) The SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC connection
ed by the UE. One UE has a
f a signaling connection When the whether to accept or reject the RRC n on a Dedicated Channel
C connection. and allocates the Radio e NodeB, requesting the NodeB to
eB. This procedure is optional. It
about the DCH allocated by the SRNC.
st set up. The message
ON REJECT message to
acket call setup. The UE has the state Packet n procedure used to set up and remove a ervice, QoS, parameters. A Radio Access Service Access Point Identifier) and a TLLI
per PLMN. Support of static IP address allocation security check. The support of
PDP address.
direct transfer to the serving node. The RNC or's setting) Service) Requested, PDP Configuration he use of a dynamic PDP address.
e UE and the PDP context subscription he APN. The GGSN may use Access Point
ecision Point Protocol Data Units) between
RNC that the PDP Context is Accepted. The N is now able to route PDP PDUs between
he APN. The GGSN may use Access Point
ecision Point Protocol Data Units) between
RNC that the PDP Context is Accepted. The N is now able to route PDP PDUs between
characteristic parameters and radio resource etup procedure. DCHs to the existing radio links for carrying the
The NodeB and the SRNC perform
eason for the failure.
minates a packet call. Before the e RAB will be released if there are no other
by the UE in the Deactivate PDP Context Request Request message ages are sent over the backbone network
RRC connection does not carry other RAB
ase procedure: release of an RRC connection from on the DCH is released and if
ge by the UE. The RRC SNs of these messages are CTION RELEASE sed the RRC connection.)
B.
rocedure. Then, the RRC connection release
ge by the UE. The RRC SNs of these messages are CTION RELEASE sed the RRC connection.)
B.
rocedure. Then, the RRC connection release
Click to return to main page RRC:RRC Connection Request (RACH)
>>"RRC Connection Request Desc
>>"Geographical and UTRAN Entit
value=hex2dec(4)=4 , hex2dec
value=hex2dec(0)=0 , hex2dec
value=hex2dec(7594)= 30100
value= OriginatingBackground
value=(-24+ (37/2))=-5.5 dB
value= HSDPA Release5
RRC:RRC Connection Setup (FACH)
>>"RRC Connection Setup Descrip
>>"Geographical and UTRAN Entit
value=hex2dec(4)=4 , hex2dec
value=hex2dec(0)=0 , hex2dec
value=hex2dec(7594)= 30100
value=UE capable to support F
value=UE capable to support G
value=Signaling Radio Bearer
value=Radio Bearer Mapping
value=Signaling Radio Bearer
value=Signaling Radio Bearer
value=Signaling Radio Bearer
value=BLER Target= -20 dB
value=MaxAllowedULTxPower
value=(-48*2)= -96 dBm (step o
value= use Closed Loop Powe
value= use long SC on Uplink
value=Spreading Factor 64 (Up
value=Spreading Factor 128 (D
value=Primary Scrambling cod
value=Spreading Factor 128 (D
Cell Identity=RNCid(12bits)+Ce value= 000000000001 00010101
RRC:RRC Connection Setup Complete (DCCH)
>>"RRC Connection Setup Comple
value=support GSM (Dual Mod
value= Chipering Algorithm A5
value= support Compressed M
value= support HSDPA, UE Ca
RRC: Initial Direct Transfer (GMM: Service Request)
RANAP: GMM:Service Request
RRC: Security Mode Command
RRC: Security Mode Complete
RRC: Uplink Direct Transfer (SM: Activate PDP Context Request)
RANAP: SM: Activate PDP Context Request
RRC: Radio Bearer Setup
RRC: Radio Bearer Setup Complete
RANAP: SM: Activate PDP Context Accept
RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept)
RRC: Physical Channel Reconfiguration (DCCH)
RRC:Physical Channel Reconfiguration Complete (DCCH)
RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)
RANAP: SM: Deactivate PDP Context Request
RANAP: SM: Deactivate PDP Context Accept
RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept)
RRC: Radio Bearer Release
RRC: Radio Bearer Release Completed
RRC: Downlink Direct Transfer (CC: RRC Connection Release)
RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)
>>"RRC Connection Request Description"
>>"Geographical and UTRAN Entity Identifiers"
value=hex2dec(4)=4 , hex2dec(1)=1 ,hex2dec(3)=3 --> MCC=413
value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
value=hex2dec(7594)= 30100 value= OriginatingBackgroundCall (PS MOC)
value=(-24+ (37/2))=-5.5 dB
value= HSDPA Release5
>>"RRC Connection Setup Description"
>>"Geographical and UTRAN Entity Identifiers"
value=hex2dec(4)=4 , hex2dec(1)=1 ,hex2dec(3)=3 --> MCC=413
value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
value=hex2dec(7594)= 30100
value=UE capable to support FDD , not TDD
value=UE capable to support GSM
value=Signaling Radio Bearer Information Setup ,RB-1
value=Radio Bearer Mapping
value=Signaling Radio Bearer Information Setup ,RB-2
value=Signaling Radio Bearer Information Setup ,RB-3
value=Signaling Radio Bearer Information Setup ,RB-4
value=BLER Target= -20 dB value=MaxAllowedULTxPower=24 dBm
value=(-48*2)= -96 dBm (step of 2 dB) Default Constant
DPCCH_Power_offset
CPICH_RSCP
-22
-96
-80
-22
-96
-70
Note :DPCCH_Power_offset is configured by RNC and delivered to UE in RRC Connec value= use Closed Loop Power Control Algorithm1
value= use long SC on Uplink
value=Spreading Factor 64 (Uplink)
value=Spreading Factor 128 (Downlink)
value=Primary Scrambling code=30
value=Spreading Factor 128 (Downlink)
Cell Identity=RNCid(12bits)+Cellid(16bits) value= 000000000001 0001010100101111 => RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(0001010100101111)=5423
>>"RRC Connection Setup Complete Description"
value=support GSM (Dual Mode GSM<>UMTS)
value= Chipering Algorithm A5/3
value= support Compressed Mode (CM) uplink and downlink
value= support HSDPA, UE Category 6
>>"Radio Bearer Description"
value= SF16(uplink)-> PS64
value= HSDPA Channel Information
value= hs-SCCH , Fixed SF 128 , Code No=4,5,6,7
In theory, one cell can configure up to 15 HS-SCCH. But now commercial UE can only monitor up to 4 HS-SCCH channels s
value= SF256(downlink)
value= HSDPA Serving Cell's Primary SC = 30
value= SF256(downlink)
Cell Identity=RNCid(12bits)+Cellid(16bits) value= 000000000001 0001010100101111 => RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(0001010100101111)=5
value= PrimarySC=30, no longer a HSDPA serving cell ( HSDPA Serving Cell Change)
(Old HSDPA's Serving Cell) Cell Identity=RNCid(12bits)+Cellid(16bits)
value= 000000000001 0001010100101111 => RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(0001010100101111)=5
value= PrimarySC=9 is a new HSDPA serving cell ( HSDPA Serving Cell Change)
(New HSDPA's Serving Cell) Cell Identity=RNCid(12bits)+Cellid(16bits)
value= 000000000001 0001000111011100 => RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(0001000111011100)=45
PCPICH Power
UL Interference
UL DPCCH Initial Power
33
-107
-16
33
-107
-26
nd delivered to UE in RRC Connection Setup.
00101111)=5423
tor up to 4 HS-SCCH channels simultaneously. So one cell only configure up to 4 HS-SCCH channels
=bin2dec(0001010100101111)=5423
=bin2dec(0001010100101111)=5423
=bin2dec(0001000111011100)=4572
Click to return to main page
L3 Messages - PS(HSUPA) Call Proc UE
NodeB
S-RNC
1.RRC: RRC Connection Request (RACH) 2.NBAP:Radio Link Setup Req Start Rx 3.NBAP:Radio Link Setup Resp. 4.ALCAP: Iub User Plane Setup RRC Connection Establishment Timing
Start Tx
5.RRC: RRC Connection Setup (FACH) L1 Synchonization 7.NBAP:Synchonization Indicator 8.RRC: RRC Connection Setup Completed (DCH)
RRC: Initial Direct Transfer (GMM: Service Request)
RRC: Security Mode Command RRC: Security Mode Completed
RRC: Uplink Direct Transfer (SM: Activate PDP Context Request)
NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready
ALCAP: Iub User Plane Setup RRC: Radio Bearer Setup NBAP: Radio Link Reconfiguration Commit Apply new transport format set RRC: Radio Bearer Setup Complete RRC:Measurement Control RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept)
PS Session Established RRC:Measurement Report (e1d) NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready ALCAP: Iub User Plane Setup NBAP: Radio Link Reconfiguration Commit
RRC: Physical Channel Reconfiguration (DCCH) RRC:Physical Channel Reconfiguration Complete (DCCH)
RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)
RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept) NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready
ALCAP: Iub User Plane Setup NBAP: Radio Link Reconfiguration Commit RRC: Radio Bearer Release
RRC: Radio Bearer Release Completed RRC: Downlink Direct Transfer (CC: RRC Connection Release) RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete) RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete) NBAP: Radio Link Deletion Request NBAP: Radio Link Deletion Response ALCAP: Iub User Plane Release
SUPA) Call Procedure S-RNC
CN
etup
>>RRC Procedure Description
1.RRC Connection Establi
RANAP: GMM:Service Request
RANAP: Security Mode Command
RANAP: Security Mode Complete RANAP: Common ID(IMSI)
RANAP: SM: Activate PDP Context Request RANAP: RAB Assignment Request ALCAP : Iu User Plane Setup
2.PS Session Setup
etup
3. Radio Bearer Setup
set
RANAP: RAB Assignment Response RANAP: SM: Activate PDP Context Accept
n Established
4. Downlink and Uplink Da
etup
HSPA's Serving Cell Chang
RANAP: SM: Deactivate PDP Context Request RANAP: SM: Deactivate PDP Context Accept
5.PS Session Release
etup
ease
RANAP: Iu Release Command ALCAP: Iu User Plane Release RANAP: Iu Release Complete
6.RRC Connection Relea
RRC connection setup procedure is performed for the UE to set up a signalin maximum of one RRC connection at a time.
Triggering Conditions : The UE in idle mode intitiates the RRC connection setu
SRNC receives an RRC CONNECTION REQUEST message from the UE, the Rad connection request, based on a specific algorithm. If accepting the request, the RR (DCH)or on a Common Channel (CCH),based on a specific RRM algorithm. Typica
>>RRC Procedure Description .RRC Connection Establishment
The procedure shown is described as follows: 1.The UE sends an RRC CONNECTION REQUEST message to the SRNC throug 2.Based on the cause in the RRC connection request and the system resource stat NetworkTemporary Identity(RNTI),radio resources, and L1 and L2 resources. Then allocate the specific radio link resources required for an RRC connection. 3.The NodeB responds with a RADIO LINK SETUP RESPONSE message to the S 4.The SRNC uses the ALCAP protocol to set up the Iub user plane transport beare is required for the ATM-based Iub interface only. 5.The SRNC sends an RRC CONNECTION SETUP message to the UE through th 6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Synchonization I 7. The UE sends an RRC CONNECTION SETUP COMPLETE message to the SR indicates that the RRC connection setup procedure ends. If the RNC judges that the RRC connection request cannot be set up (for instance, theUE, and indicates the reject reason in the message
The PS Session Setup procedure is performed to set up a PS session
Triggering Conditions: The UE send Activate PDP context request message to R Mobility Management Connected that enables the user to transmitt and receive dat virtual data channel between a terminal connected to a UE and a GGSN. PDP cont bearer establishes on request of the SGSN in order to realize the air interface conn (Temporary Logical Link Identity) associated to IMSI.
IP addresses can be allocated dynamically or statistically. If allocated dynamically, t enables subscribers to provide their own IP addresses. This can be useful when ac QoS enables the operator to differentiate GPRS services.
.PS Session Setup
When dynamic addressing from the home PLMN or the Visitor PLMN is used, it is t The procedure shown is described as follows: 1. The UE initiates the PS Session by using the Service Request (Service Type=Da sets-up an SCCP connection with the SGSN and transfers the initial service reque 2 .The UE sends an Activate PDP Context Request (NSAPI, TI(Teardown Indication Options) message to the SGSN The UE shall use PDP Address to indicate whethe 3. The SGSN sends a RAB Assignment Request message to the RNC to establish 4.The RNC establishes the appropriate radio bearer In WCDMA, RAB setup is don 5.The RNC returns a RAB Assignment Response message to the SGSN 6. The SGSN validates the active PDP Context Request using PDP Type (optional) records.The SGSN sends a Create PDP Context Request message to the affected Name to find an external network and optionally to activate a service for this APN 7. The GGSN creates a new entry in its PDP context table and generates a Chargin the SGSN and the external PDP network, and to start charging 8.The SGSN inserts the Network layer Service Access Point Identifier, NSAPI along SGSN selects Radio Priority and Packet flow Id based on QoS Negotiated, and retu theGGSN and the UE and to start charging The Radio Bearer Setup procedure shown is described as follows:
records.The SGSN sends a Create PDP Context Request message to the affected Name to find an external network and optionally to activate a service for this APN 7. The GGSN creates a new entry in its PDP context table and generates a Chargin the SGSN and the external PDP network, and to start charging 8.The SGSN inserts the Network layer Service Access Point Identifier, NSAPI along SGSN selects Radio Priority and Packet flow Id based on QoS Negotiated, and retu theGGSN and the UE and to start charging
. Radio Bearer Setup
The Radio Bearer Setup procedure shown is described as follows: 1.The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initia 2.(Optional; applicable to the ATM-based Iu-CS interface only) The SRNC maps the characteristic parameters. Based on the AAL2 link characteristic parameters,the AL 3.The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to t RAB. 4.The NodeB allocates the associated resources and then sends a RADIO LINKRE 5.(Optional; required for the ATM-based Iub interface only) The Iub ALCAP at the S synchronization by exchanging uplink and downlink synchronization frames in the D 6.The SRNC sends a RADIO BEARER SETUP message to the UE. 7.The SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to the 8.After performing the radio bearer setup, the UE sends a RADIO BEARER SETUP 9.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The R The procedure when RAB Setup Failure shown is described as follows: 1.The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initia 2.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The m
The PS session release procedure is performed to release services and reso
Triggering Conditions : The UE send Deactivate PDP context request message deactivation,the UE has the state Active. After the PDP Context deactivation proced PDP contexts activated.PDP Deactivation may be initiated by a:UE procedure,SGS
. Downlink and Uplink Data Transfer
The procedure shown is described as follows: 1.The UE sends a Deactivate PDP Context Request (TI, Teardown Indication) mes 2.The SGSN sends a Delete PDP Context Request (TEID, NSAPI, Teardown Indic message, then the SGSN deactivates all PDP contexts associated with this PDP ad 3.The GGSN removes the PDP context(s) and returns a delete PDP Context Respo 4.The SGSN returns a Deactivate PDP Context Accept (TI) message to the UE via 5. In Iu mode, radio access bearer release is done by the RAB Assignment procedu 6. The SCCP connection between RNC and SGSN is released. At GPRS detach, a
HSPA's Serving Cell Change
The RRC Connection Release procedure is performed to release the signaling co
Triggering Conditions: After a n RAB is released,the SRNC judges whether the R of the UE,the SRNC initiates an RRC connection release procedure.
The procedure shown is described as follows: based on the resouce occupied DCH and release of an RRC connection from CCH (If an RRC connection needs to a radio bearers fails to be setup ,the RRC connection on the CCH is released)
1.The SRNC sends an RRC CONNECTION RELEASE message to the UE through (NOTE: The SRNC may send the RRC CONNECTION RELEASE message severa the same. The number of retransmissions and the transmission intervals are determ COMPLETE message from the UE after sending the RRC CONNECTION RELEAS
2.The UE sends an RRC CONNECTION RELEASE COMPLETE message to the S 3.The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB, 4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESP 5.(Optional; required for the ATM-based Iub interface only) The SRNC uses the AL procedure ends.
(NOTE: The SRNC may send the RRC CONNECTION RELEASE message severa the same. The number of retransmissions and the transmission intervals are determ COMPLETE message from the UE after sending the RRC CONNECTION RELEAS
.PS Session Release
.RRC Connection Release
2.The UE sends an RRC CONNECTION RELEASE COMPLETE message to the S 3.The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB, 4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESP 5.(Optional; required for the ATM-based Iub interface only) The SRNC uses the AL procedure ends.
rmed for the UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a
e intitiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling connection When the EST message from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or reject the RRC hm. If accepting the request, the RRM module further determines whether to set up the RRC connection on a Dedicated Channel n a specific RRM algorithm. Typically, an RRC connection is set up on the DCH.
s: EST message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection. quest and the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio es, and L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to d for an RRC connection. UP RESPONSE message to the SRNC after successfully preparing the resources. the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. It . TUP message to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocated by the SRNC odeB sends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state P COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message ure ends. est cannot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to essage
rmed to set up a PS session
PDP context request message to RNC. PDP Context Activation is performed when the UE initiates a packet call setup. The UE has the state he user to transmitt and receive data while moving within a PLMN. and starts the PDP context activation procedure used to set up and remov ed to a UE and a GGSN. PDP contexts deal with allocation of IP addresses to the UE and Quality of Service, QoS, parameters. A Radio Acc der to realize the air interface connection. At the end the UE has an IP address NSAPI (Network layer Service Access Point Identifier) and a MSI.
atistically. If allocated dynamically, this significantly reduces the total number of IP addresses required per PLMN. Support of static IP addres resses. This can be useful when accesing secure networks that use the calling IP address as a form of security check. The support of services.
N or the Visitor PLMN is used, it is the responsibility of the GGSN to allocate and release the dynamic PDP address. s: Service Request (Service Type=Data) message. After the RR setup completion the UE asks for initial direct transfer to the serving node. The d transfers the initial service request (Authentication and ciphering may performed depends on operator's setting) est (NSAPI, TI(Teardown Indication), PDP Type, Address, APN (Access Point Name), QoS (Quality of Service) Requested, PDP Configurat se PDP Address to indicate whether it requires the use of a static PDP address or whether it requires the use of a dynamic PDP address. t message to the RNC to establish a RABs arer In WCDMA, RAB setup is done by the RAB Assignment procedure e message to the SGSN Request using PDP Type (optional), PDP Address, APN (Access Point Name (optional) provided by the UE and the PDP context subscriptio t Request message to the affected GGSN. Access Point Name shall be the APN Network Identifier of the APN. The GGSN may use Access to activate a service for this APN ntext table and generates a Charging Id. The new entry allows the GGSN to route PDP PDUs (Policy Decision Point Protocol Data Units) bet o start charging Access Point Identifier, NSAPI along with the GGSN address in its PDP context and informs the UE via RNC that the PDP Context is Accepte based on QoS Negotiated, and returns an Activate PDP Context Accept message to the UE. The SGSN is now able to route PDP PDUs bet
described as follows:
t Request message to the affected GGSN. Access Point Name shall be the APN Network Identifier of the APN. The GGSN may use Access to activate a service for this APN ntext table and generates a Charging Id. The new entry allows the GGSN to route PDP PDUs (Policy Decision Point Protocol Data Units) bet o start charging Access Point Identifier, NSAPI along with the GGSN address in its PDP context and informs the UE via RNC that the PDP Context is Accepte based on QoS Negotiated, and returns an Activate PDP Context Accept message to the UE. The SGSN is now able to route PDP PDUs bet
described as follows: EST message to the SRNC to initiate the RAB setup procedure. interface only) The SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and radio re nk characteristic parameters,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup procedure. URATION PREPARE message to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio links for c
s and then sends a RADIO LINKRECONFIGURATION READY message to the SRNC. rface only) The Iub ALCAP at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SRNC perform ink synchronization frames in the DCH frame protocol. message to the UE. URATION COMMIT message to theNodeB. E sends a RADIO BEARER SETUP COMPLETE message to the SRNC. SPONSE message to the CN. The RAB isset up. wn is described as follows: EST message to the SRNC to initiate the RAB setup procedure. SPONSE message to the CN. The message indicates the ID of the RAB that fails to be set up and the reason for the failure.
ormed to release services and resources after a session ends.
ate PDP context request message to RNC. A PDP Context Deactivation is performed when the UE terminates a packet call. Before the he PDP Context deactivation procedure the state becomes Packet Mobility Management Connected.The RAB will be released if there are no be initiated by a:UE procedure,SGSN procedure,GGSN procedure
s: uest (TI, Teardown Indication) message to the SGSN via the RNC est (TEID, NSAPI, Teardown Indication) message to the GGSN. If Teardown Indication was included by the UE in the Deactivate PDP Cont ontexts associated with this PDP address by including Teardown Indication in the Delete PDP Context Request message eturns a delete PDP Context Response (TEID) message to the SGSN. The Delete PDP Context messages are sent over the backbone netw Accept (TI) message to the UE via the RNC ne by the RAB Assignment procedure SN is released. At GPRS detach, all PDP contexts for the UE are implicitly deactivated
erformed to release the signaling connection and all radio bearers between UE and the UTRAN
ed,the SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry other n release procedure.
s: based on the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: release of an RRC con CH (If an RRC connection needs to be released after a successful outgoing call,, the RRC connection on the DCH is released and if ection on the CCH is released)
LEASE message to the UE through the DCCH. CTION RELEASE message several times to increase the probability of proper reception of the message by the UE. The RRC SNs of these he transmission intervals are determined by the SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE g the RRC CONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC connection.)
ASE COMPLETE message to the SRNC. REQUEST message to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB. s a RADIO LINK DELETION RESPONSE message to the SRNC. rface only) The SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC connection
CTION RELEASE message several times to increase the probability of proper reception of the message by the UE. The RRC SNs of these he transmission intervals are determined by the SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE g the RRC CONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC connection.)
ASE COMPLETE message to the SRNC. REQUEST message to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB. s a RADIO LINK DELETION RESPONSE message to the SRNC. rface only) The SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC connection
ed by the UE. One UE has a
f a signaling connection When the whether to accept or reject the RRC n on a Dedicated Channel
C connection. and allocates the Radio e NodeB, requesting the NodeB to
eB. This procedure is optional. It
about the DCH allocated by the SRNC.
st set up. The message
ON REJECT message to
acket call setup. The UE has the state Packet n procedure used to set up and remove a ervice, QoS, parameters. A Radio Access Service Access Point Identifier) and a TLLI
per PLMN. Support of static IP address allocation security check. The support of
PDP address.
direct transfer to the serving node. The RNC or's setting) Service) Requested, PDP Configuration he use of a dynamic PDP address.
e UE and the PDP context subscription he APN. The GGSN may use Access Point
ecision Point Protocol Data Units) between
RNC that the PDP Context is Accepted. The N is now able to route PDP PDUs between
he APN. The GGSN may use Access Point
ecision Point Protocol Data Units) between
RNC that the PDP Context is Accepted. The N is now able to route PDP PDUs between
characteristic parameters and radio resource etup procedure. DCHs to the existing radio links for carrying the
The NodeB and the SRNC perform
eason for the failure.
minates a packet call. Before the e RAB will be released if there are no other
by the UE in the Deactivate PDP Context Request Request message ages are sent over the backbone network
RRC connection does not carry other RAB
ase procedure: release of an RRC connection from on the DCH is released and if
ge by the UE. The RRC SNs of these messages are CTION RELEASE sed the RRC connection.)
B.
rocedure. Then, the RRC connection release
ge by the UE. The RRC SNs of these messages are CTION RELEASE sed the RRC connection.)
B.
rocedure. Then, the RRC connection release
Click to return to main page RRC:RRC Connection Request (RACH)
>>"RRC Connection Request Desc
>>"Geographical and UTRAN Entit
value=hex2dec(5)=5 , hex2dec
value=hex2dec(9)=9 , hex2dec
value=hex2dec(03EA)= 1002
value= OriginatingBackground
value=(-24+ (39/2))=-4.5 dB
value=Primary Scrambling Cod
value=(-24+ (37/2))=-5.5 dB
value= HSPA Release6
value= UE support HSDPA and
RRC:RRC Connection Setup (FACH)
>>"RRC Connection Setup Descrip
>>"Geographical and UTRAN Entit
value=hex2dec(5)=5 , hex2dec
value=hex2dec(9)=9 , hex2dec
value=hex2dec(03EA)= 1002
value=UE capable to support F
value=Signaling Radio Bearer
value=Radio Bearer Mapping
value=Signaling Radio Bearer
value=Signaling Radio Bearer
value=Signaling Radio Bearer
value=BLER Target= -20 dB
value=MaxAllowedULTxPower
value=(-47*2)= -94 dBm (step o
value= use Closed Loop Powe
value= use long SC on Uplink
value=Spreading Factor 64 (Up
value=Spreading Factor 128 (D
value=Primary Scrambling cod
value=Spreading Factor 128 (D
Cell Identity=RNCid(12bits)+Ce value= 000001100110 00000101
RRC:RRC Connection Setup Complete (DCCH)
value= not support GSM (Lock
value= Chipering Algorithm A5
value= support Compressed M
value= support HSDPA, UE Ca
RRC: Initial Direct Transfer (GMM: Service Request)
RANAP: GMM:Service Request
RRC: Security Mode Command
RRC: Security Mode Complete
RRC: Uplink Direct Transfer (SM: Activate PDP Context Request)
RANAP: SM: Activate PDP Context Request
RRC: Radio Bearer Setup
RRC: Radio Bearer Setup Complete
RANAP: SM: Activate PDP Context Accept
RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept)
RRC: Physical Channel Reconfiguration (DCCH)
RRC:Physical Channel Reconfiguration Complete (DCCH)
RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)
RANAP: SM: Deactivate PDP Context Request
RANAP: SM: Deactivate PDP Context Accept
RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept)
RRC: Radio Bearer Release
RRC: Radio Bearer Release Completed
RRC: Downlink Direct Transfer (CC: RRC Connection Release)
RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)
RRC:Measurement Report (e1d)
RRC:Measurement Control
>>"RRC Connection Request Description"
>>"Geographical and UTRAN Entity Identifiers"
value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520
value=hex2dec(9)=9 , hex2dec(9)=9 --> MNC=99
value=hex2dec(03EA)= 1002 value= OriginatingBackgroundCall (PS MOC)
value=(-24+ (39/2))=-4.5 dB
value=Primary Scrambling Code=60 ( Neighbour's SC)
value=(-24+ (37/2))=-5.5 dB
value= HSPA Release6
value= UE support HSDPA and E-DCH (HSUPA)
>>"RRC Connection Setup Description"
>>"Geographical and UTRAN Entity Identifiers"
value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520
value=hex2dec(9)=9 , hex2dec(9)=9 --> MNC=99
value=hex2dec(03EA)= 1002
value=UE capable to support FDD , not TDD
value=Signaling Radio Bearer Information Setup ,RB-1
value=Radio Bearer Mapping
value=Signaling Radio Bearer Information Setup ,RB-2
value=Signaling Radio Bearer Information Setup ,RB-3
value=Signaling Radio Bearer Information Setup ,RB-4
value=BLER Target= -20 dB value=MaxAllowedULTxPower=24 dBm
value=(-47*2)= -94 dBm (step of 2 dB)
Default Constant value= use Closed Loop Power Control Algorithm1
DPCCH_Power_offsetCPICH_RSCP
-22
-94
-80
-22
-94
-70
Note :DPCCH_Power_offset is configured by RNC and delivered to UE in RRC
value= use long SC on Uplink
value=Spreading Factor 64 (Uplink)
value=Spreading Factor 128 (Downlink)
value=Primary Scrambling code=60
value=Spreading Factor 128 (Downlink)
Cell Identity=RNCid(12bits)+Cellid(16bits) value= 000001100110 0000010100101001 => RNCid=bin2dec(000001100110)=102 and Cellid=bin2dec(0000010100101001)=1321
>>"RRC Connection Setup Complete Description"
value= not support GSM (Locked UMTS Mode)
value= Chipering Algorithm A5/3
value= support Compressed Mode (CM) uplink and downlink
value= support HSDPA, UE Category 8
>>"Radio Bearer Description"
value= Uplink e-DPDCH (HSUPA) channel information
value= Downlink HS-PDSCH channel information
value= HSDPA and HSUPA Serving Cell's Primary SC = 68
value= PrimarySC=68, no longer a HSDPA & HSUPA serving cell ( HSPA Serving Cell Change)
value= PrimarySC=60 is a new HSDPA&HSUPA serving cell ( HSPA Serving Cell Change)
PCPICH Power
UL Interference UL DPCCH Initial Power
33
-105
-14
33
-105
-24
C and delivered to UE in RRC Connection Setup.
101001)=1321
Click to return to main page
L3 Messages - Intra-Frequency Soft Handover Procedure UE
NodeB1 Intra-Frequency Soft Handover within NodeB(Softer-HO) RRC:Measurement Control RRC:Measurement Report (e1a)
"or" RRC:Measurement Report (e1c)
1.RRC: Active Set Update (DCCH) 2. RRC: Active Set Update Complete (DCCH)
RRC:Measurement Control RRC:Measurement Report (e1b)
1.RRC: Active Set Update (DCCH) 2. RRC: Active Set Update Complete (DCCH)
L3 Messages - Intra-Frequency Soft Handover Procedure UE
NodeB1 *Source
NodeB2
Intra-Frequency Soft Handover between NodeBs in a RNC RRC:Measurement Control RRC:Measurement Report (e1a)
"or" RRC:Measurement Report (e1c)
ALCAP:
1.RRC: Active Set Update (DCCH)
2. RRC: Active Set Update Complete (DCCH)
RRC:Measurement Control RRC:Measurement Report (e1b)
1.RRC: Active Set Update (DCCH) 2. RRC: Active Set Update Complete (DCCH)
ALCAP: Iu
Note: the following information about the procedure , 1. During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB. 2.If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iubinterface after radio links are set up or deleted.
L3 Messages - Intra-Frequency Soft Hand UE
NodeB2 *Target
D-RNC
Intra-Frequency Soft Handover betwee RRC:Measurement Control RRC:Measurement Report (e1a)
"or" RRC:Measurement Report (e1c)
2.NBAP:Radio Link Setup Request
3.NBAP:Radio Link Setup Response
ALCAP: Iub User Plane Setup 1.QAAL2 Establish Request 2.QAAL2 Establish Confirm 1.NBAP:Radio Link Restore Indication
1.RRC: Active Set Update (DCCH)
2.RRC: Active Set Update Complete (DC
RRC:Measurement Control RRC:Measurement Report (e1b)
1.RRC: Active Set Update (DCCH)
2. RRC: Active Set Update Complete (DC
NBAP:Radio Link Deletion Req NBAP:Radio Link Deletion Resp ALCAP: Iub User Plane Release QAAL2 Release Request QAAL2 Release Confirm
Note : the following information about the procedure , 1.During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB. 2. If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface after radio links are set up or deleted. 3.If IP transport is applied to the Iur interface, no ALCAP procedure is performed on the Iurinterface after radio links are set up or deleted.
>>Intra-Frequency SHO Algorithm and related parameters (Module II)
over Procedure S-RNC
Measurement Control: changed, the RNC notifie
B(Softer-HO) Measurement Control & Measurement Report Decision to setup new radio link
Measurement Report: t the results to the RNC as
Radio Link Addition Pro Triggering Conditions:
1.NBAP:Radio Link Setup Req Radio Link Addition 2.NBAP:Radio Link Setup Resp
Active Set Update
CCH)
Measurement Control & Measurement Report
Decision to delete old radio link
Active Set Update
CH) 1.NBAP:Radio Link Deletion Req
Radio Link Deletion
The procedure of radio 1.The CRNC sends a RA the new radio link or links 2.The NodeB sends a re -If all the requested rad andsends a RADIO LINK -If any radio link fails to
The active set update
Triggering Conditions: The procedure is desc 1.The SRNC sends an A deleted, themessage ind 2.The UE adds or delete message. 3.The UE sends a respon -lf adding or deleting th Link Control (RLC). -If the ACTIVE SET UPD Radio Link Removal Inf
2.NBAP:Radio Link Deletion Resp
Radio Link Deletion P
Triggering Conditions: The procedure of radio 1.The CRNC sends a RA 2.The NodeB sends a re -If the radio link are del -If the radio link fails to
over Procedure *Target
Click to return to main page
S-RNC
Measurement Control: changed, the RNC notifie
Measurement Report: t the results to the RNC as
deBs in a RNC Measurement Control & Measurement Report
The radio link setup pro
Decision to setup new radio link
1.NBAP:Radio Link Setup Req Radio Link Setup 2.NBAP:Radio Link Setup Resp ALCAP: Iub User Plane Setup QAAL2 Establish Request
Triggering Conditions: The procedure of radio 1.The CRNC sends a RA new radio link according 2.The NodeB sends a re -If the radio link is set u RADIOLINK SETUP RES -If the radio link fails to
Iub user plane Setup
QAAL2 Establish Confirm
The Iub user plane setu Iub radio link restore Indication
NBAP:Radio Link Restore Indication
Active Set Update
CH)
Measurement Control & Measurement Report
Triggering Conditions: 1. The common transpor 2. The dedicated transpo The procedure is descr 1.The CRNC uses the AL 2.The NodeB uses the A -If the Iub data transpor -If an Iub data transpor
The radio link restoratio synchronization of one or Triggering Conditions:
Decision to delete old radio link
After performing UL sync
Active Set Update
The active set update
CH) 1.NBAP:Radio Link Deletion Req Radio Link Deletion
Triggering Conditions: The procedure is desc 1.The SRNC sends an A deleted, themessage ind 2.The UE adds or delete message. 3.The UE sends a respon -lf adding or deleting th
Triggering Conditions: The procedure is desc 1.The SRNC sends an A deleted, themessage ind 2.The UE adds or delete message. 3.The UE sends a respon -lf adding or deleting th Link Control (RLC). -If the ACTIVE SET UPD Radio Link Removal Inf
Radio Link Deletion 2.NBAP:Radio Link Deletion Resp ALCAP: Iub User Plane Release QAAL2 Release Request
Iub user plane release
QAAL2 Release Confirm
Radio Link Deletion P
Triggering Conditions: The procedure of radio 1.The CRNC sends a RA 2.The NodeB sends a re -If the radio link are del -If the radio link fails to
The Iub user plane re
Triggering Conditions: The procedure is descr 1.The CRNC uses the AL 2.The NodeB uses the A -If the Iub data transpor -lf an Iub data transpor
quency Soft Handover Procedure *Target
Click to return to main pa
NodeB1 *Source
S-RNC
oft Handover between RNCs
Measurement Control
Measurement Contro & Measurement
asurement Report (e1a) Decision to setup new radio link
asurement Report (e1c) 1.RNSAP:Radio Link Setup Request
Radio Link Setup
Iub user plane Setup
4.RNSAP:Radio Link Setup Response
Iub Radio Link Resto
ALCAP: Iur User Plane Setup Iur user plane Setup
1.QAAL2 Establish Request 2.QAAL2 Establish Confirm
Iur Radio Link Restore
2.RNSAP:Radio Link Restore Indication
tive Set Update (DCCH) Active Set
Set Update Complete (DCCH)
Measurement Control
Measurement Contro & Measurement
asurement Report (e1b) Decision to delete old radio link
tive Set Update (DCCH) Active Set
Set Update Complete (DCCH) 1.RNSAP:Radio Link Deletion Req
Radio Link Deletion Iub user plane release
2.NBAP:Radio Link Deletion Resp ALCAP: Iur User Plane Release QAAL2 Release Request QAAL2 Release Confirm
Iur user plane relea
eters (Module II)
Measurement Control: is used to notify the UE of the objects to be measured, neighbor cell list, report method, and event parameters.Wh changed, the RNC notifies the UE of new conditions.
Measurement Report: the UE continue measure the radio link condition of serving and neighbour cell and when the measurement reportin the results to the RNC as an event. The Measurement report is also can be sent in periodic mode.
Radio Link Addition Procedure is performed to add one or more radio links towards a UE. Triggering Conditions: The CRNC sends a RADIO LINK ADDITION REQUEST message.
The procedure of radio link setup is described as follows: 1.The CRNC sends a RADIO LINK ADDITION REQUEST message to the NodeB. After receiving the message, the NodeB reserves the ne the new radio link or links according to the parameters given in the message. 2.The NodeB sends a response message to the CRNC. -If all the requested radio links are added, the NodeB saves the value of the Configuration Generation ID IE contained in the RADIO LIN andsends a RADIO LINK ADDITION RESPONSE message. -If any radio link fails to be added, the NodeB sends a RADIO LINK ADDITION FAILURE message. The message contains the failure ca
The active set update procedure is performed to update the active set of radio links between theUE and the UTRAN.
Triggering Conditions: The active set update procedure can be triggered in either of the following conditions: Radio link addition or Radio The procedure is described as follows: 1.The SRNC sends an ACTIVE SET UPDATE message to the UE. If a radio link needs to be added, the message indicates radio link addit deleted, themessage indicates radio link deletion. 2.The UE adds or deletes the radio links according to the Radio Link Addition Informationor Radio Link Removal Information IE contained in message. 3.The UE sends a response message to the SRNC. -lf adding or deleting the radio links successfully, the UE sends an ACTIVE SETUPDATE COMPLETE message on the DCCH by usin Link Control (RLC). -If the ACTIVE SET UPDATE message contains the configuration not supported by the UE or if the active set does not contain the Radio Link Removal Information IE, the UE sends an ACTIVE SET UPDATE FAILURE message.
Radio Link Deletion Procedure is performed to release resources in a NodeB for one or more established radio links towards a UE
Triggering Conditions: The CRNC sends a RADIO LINK DELETION REQUEST message. The procedure of radio link deletion is described as follows: 1.The CRNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB deletes the radio li 2.The NodeB sends a response message to the CRNC. -If the radio link are deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. -If the radio link fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The message contains the failur
Measurement Control: is used to notify the UE of the objects to be measured, neighbor cell list, report method, and event parameters.Wh changed, the RNC notifies the UE of new conditions.
Measurement Report: the UE continue measure the radio link condition of serving and neighbour cell and when the measurement reportin the results to the RNC as an event. The Measurement report is also can be sent in periodic mode.
The radio link setup procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed to set up a radio link in an SRNC
Triggering Conditions: The CRNC sends a RADIO LINK SETUP REQUEST message. The procedure of radio link setup is described as follows: 1.The CRNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB reserves the nece new radio link according to the parameters given in the message. 2.The NodeB sends a response message to the CRNC. -If the radio link is set up, the NodeB saves the value of the Configuration Generation ID IE contained in the RADIO LINK SETUP REQUE RADIOLINK SETUP RESPONSE message. -If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE message. The message contains the failure cause
The Iub user plane setup procedure is performed to set up bearers for data transmission on the Iub interface Triggering Conditions: The Iub user plane setup procedure can be triggered in one of the following conditions: 1. The common transport channels are setup 2. The dedicated transport channels are setup The procedure is described as follows: 1.The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST messageto the NodeB. 2.The NodeB uses the ALCAP protocol to send a response message to the CRNC. -If the Iub data transport bearers are set up, the NodeB sends a QAAL2 ESTABLISH CONFIRM message. -If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH RELEASE CONFIRM message.
The radio link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed for a NodeB to notify the C synchronization of one or more radio links is achieved or re-achieved Triggering Conditions: The nodeB detect UL signals from the UE. That is ,the NodeB finishs UL synchronization with the UE After performing UL synchronization with the UE, the NodeB sends a RADIO LINK RESTORE INDICATION message to the CRNC.
The active set update procedure is performed to update the active set of radio links between theUE and the UTRAN.
Triggering Conditions: The active set update procedure can be triggered in either of the following conditions: Radio link addition or Radio The procedure is described as follows: 1.The SRNC sends an ACTIVE SET UPDATE message to the UE. If a radio link needs to be added, the message indicates radio link addit deleted, themessage indicates radio link deletion. 2.The UE adds or deletes the radio links according to the Radio Link Addition Informationor Radio Link Removal Information IE contained in message. 3.The UE sends a response message to the SRNC. -lf adding or deleting the radio links successfully, the UE sends an ACTIVE SETUPDATE COMPLETE message on the DCCH by usin
Triggering Conditions: The active set update procedure can be triggered in either of the following conditions: Radio link addition or Radio The procedure is described as follows: 1.The SRNC sends an ACTIVE SET UPDATE message to the UE. If a radio link needs to be added, the message indicates radio link addit deleted, themessage indicates radio link deletion. 2.The UE adds or deletes the radio links according to the Radio Link Addition Informationor Radio Link Removal Information IE contained in message. 3.The UE sends a response message to the SRNC. -lf adding or deleting the radio links successfully, the UE sends an ACTIVE SETUPDATE COMPLETE message on the DCCH by usin Link Control (RLC). -If the ACTIVE SET UPDATE message contains the configuration not supported by the UE or if the active set does not contain the Radio Link Removal Information IE, the UE sends an ACTIVE SET UPDATE FAILURE message.
Radio Link Deletion Procedure is performed to release resources in a NodeB for one or more established radio links towards a UE
Triggering Conditions: The CRNC sends a RADIO LINK DELETION REQUEST message. The procedure of radio link deletion is described as follows: 1.The CRNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB deletes the radio li 2.The NodeB sends a response message to the CRNC. -If the radio link are deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. -If the radio link fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The message contains the failur
The Iub user plane release procedure is performed to release data transport bearers from the Iub interface. Triggering Conditions: The transport channels on the Iub user plane need to be removed The procedure is described as follows: 1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST messageto the NodeB. 2.The NodeB uses the ALCAP protocol to send a response message to the CRNC. -If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the release. -lf an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECONFIRM message that indicates the failure
Click to return to main page
Measurement Control: is used to notify the UE of the objects to be measured, neighbor ce changed, the RNC notifies the UE of new conditions.
Measurement Control & Measurement Report
Measurement Report: the UE continue measure the radio link condition of serving and ne results to the RNC as an event. The Measurement report is also can be sent in periodic mo
The radio link setup procedure for inter-RNC handover is performed to set up a radio li
Triggering Conditions: The SRNC sends a RADIO LINK SETUP REQUEST message The procedure is described as follows: 1.The SRNC sends a RADIO LINK SETUP REQUEST message to the DRNC. 2.The DRNC sends a RADIO LINK SETUP REQUEST message to the target NodeB. 3.The NodeB reserves the necessary resources and configures the new radio link accordin 4.The NodeB reports the radio link setup result to the DRNC -If the radio link is set up, the NodeB saves the value of the Configuration GenerationID I SETUP RESPONSE message. -If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE me
Link Setup Iub user plane Setup
Iub Radio Link Restore Indication
Triggering Conditions: The SRNC sends a RADIO LINK SETUP REQUEST message The procedure is described as follows: 1.The SRNC sends a RADIO LINK SETUP REQUEST message to the DRNC. 2.The DRNC sends a RADIO LINK SETUP REQUEST message to the target NodeB. 3.The NodeB reserves the necessary resources and configures the new radio link accordin 4.The NodeB reports the radio link setup result to the DRNC -If the radio link is set up, the NodeB saves the value of the Configuration GenerationID I SETUP RESPONSE message. -If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE me 5.The DRNC reports the radio link setup result to the SRNC -If the radio link is set up, the DRNC sends a RADIO LINK SETUP RESPONSEmessage -If the radio link fails to be set up, the DRNC sends a RADIO LINK SETUP FAILUREme
The Iub user plane setup procedure is performed to set up bearers for data transmission
Triggering Conditions: The Iub user plane setup procedure can be triggered in one o 1. The common transport channels are setup 2. The dedicated transport channels are setup Iur user plane Setup
Iur Radio Link Restore Indication
Active Set Update
The procedure is described as follows: 1.The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST message 2.The NodeB uses the ALCAP protocol to send a response message to the CRNC. -If the Iub data transport bearers are set up, the NodeB sends a QAAL2 ESTABLISH CO -If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLIS
The radio link restoration procedure for inter-RNC handover is performed for a NodeB achieved or re-achieved.
Triggering Conditons: The NodeB detects UL signals from the UE. That is, the NodeB fin Measurement Control & Measurement Report
The procedure is described as follows: 1.After performing UL synchronization with the UE, the NodeB sends a RADIO LINKRESTO 2.The DRNC sends a RADIO LINK RESTORE INDICATION message to the SRNC.
The Iur user plane setup procedure is performed to set up bearers for data transmission Active Set Update
Triggering Conditons: The DCHs are set up
The procedure is described as follows: 1.The SRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST message 2.The DRNC uses the ALCAP protocol to send a response message to the SRNC. -If the Iur data transport bearers are set up, the DRNC sends a QAAL2 ESTABLISHCON -If an Iur data transport bearer fails to be set up, the DRNC sends a QAAL2 ESTABLISH
Radio Link Deletion Iub user plane release
The active set update procedure is performed to update the active set of radio links betw
Triggering Conditions: The active set update procedure can be triggered in either of the f
The procedure is described as follows: 1.The SRNC sends an ACTIVE SET UPDATE message to the UE. If a radio link needs to b themessage indicates radio link deletion. 2.The UE adds or deletes the radio links according to the Radio Link Addition Informationor 3.The UE sends a response message to the SRNC. -lf adding or deleting the radio links successfully, the UE sends an ACTIVE SETUPDA Control (RLC). -If the ACTIVE SET UPDATE message contains the configuration not supported by th
Iur user plane release
The procedure is described as follows: 1.The SRNC sends an ACTIVE SET UPDATE message to the UE. If a radio link needs to b themessage indicates radio link deletion. 2.The UE adds or deletes the radio links according to the Radio Link Addition Informationor 3.The UE sends a response message to the SRNC. -lf adding or deleting the radio links successfully, the UE sends an ACTIVE SETUPDA Control (RLC). -If the ACTIVE SET UPDATE message contains the configuration not supported by th Link Removal Information IE, the UE sends an ACTIVE SET UPDATE FAILURE messag
The radio link deletion procedure is performed to release resources in a NodeB for one o
Triggering Conditions: The CRNC sends a RADIO LINK DELETION REQUEST message The procedure is described as follows: 1.The CRNC sends a RADIO LINK DELETION REQUEST message to the NodeB. After re 2.The NodeB sends a response message to the CRNC. -If all the radio links are deleted, the NodeB sends a RADIO LINK DELETION RESPONS -If any radio link fails to be deleted, the NodeB sends a RADIO LINK DELETIONRESPO cause.
The Iub user plane release procedure is performed to release data transport bearers from
Triggering Conditions: The transport channels on the Iub user plane need to be removed The procedure is described as follows: 1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST messageto 2.The NodeB uses the ALCAP protocol to send a response message to the CRNC. -If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEASECO -If an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEAS
The Iur user plane release procedure is performed to releaseto release data transport be
Triggering Conditions: The transport channels on the Iub user plane need to be removed The procedure is described as follows: 1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST messageto 2.The NodeB uses the ALCAP protocol to send a response message to the CRNC. -If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEASECO -If an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEAS
d, and event parameters.When measurement conditions are
en the measurement reporting criterias are met, the UE reports
e, the NodeB reserves the necessary resources and configures
contained in the RADIO LINK ADDITION REQUEST message
ssage contains the failure cause in the Cause IE.
the UTRAN. Radio link addition or Radio link deletion
age indicates radio link addition. If a radio link needs to be
al Information IE contained in the ACTIVE SET UPDATE
essage on the DCCH by using Acknowledged Mode (AM)Radio
ve set does not contain the radio links specified by the
d radio links towards a UE
he NodeB deletes the radio links specified by the message
e message contains the failure cause.
d, and event parameters.When measurement conditions are
en the measurement reporting criterias are met, the UE reports
s
et up a radio link in an SRNC-controlled NodeB for a UE
he NodeB reserves the necessary resources and configures the
RADIO LINK SETUP REQUEST message and sends a
ge contains the failure cause.
e
s:
FIRM message.
ed for a NodeB to notify the CRNC that the uplink
tion with the UE
essage to the CRNC.
the UTRAN. Radio link addition or Radio link deletion
age indicates radio link addition. If a radio link needs to be
al Information IE contained in the ACTIVE SET UPDATE
essage on the DCCH by using Acknowledged Mode (AM)Radio
Radio link addition or Radio link deletion
age indicates radio link addition. If a radio link needs to be
al Information IE contained in the ACTIVE SET UPDATE
essage on the DCCH by using Acknowledged Mode (AM)Radio
ve set does not contain the radio links specified by the
d radio links towards a UE
he NodeB deletes the radio links specified by the message
e message contains the failure cause.
ace.
o confirm the release. age that indicates the failure cause
to be measured, neighbor cell list, report method, and event parameters.When measurement conditions are
k condition of serving and neighbour cell and when the measurement reporting criterias are met, the UE reports the o can be sent in periodic mode.
performed to set up a radio link in a DRNC-controlled NodeB for a UE
TUP REQUEST message
ge to the DRNC. ge to the target NodeB. s the new radio link accordingto the parameters given in the message.
Configuration GenerationID IE contained in the RADIO LINK SETUP REQUEST message and sends a RADIOLINK
O LINK SETUP FAILURE message.
TUP REQUEST message
ge to the DRNC. ge to the target NodeB. s the new radio link accordingto the parameters given in the message.
Configuration GenerationID IE contained in the RADIO LINK SETUP REQUEST message and sends a RADIOLINK
O LINK SETUP FAILURE message.
ETUP RESPONSEmessage. O LINK SETUP FAILUREmessage, indicating the failure cause.
bearers for data transmission on the Iub interface
e can be triggered in one of the following conditions:
ABLISH REQUEST messageto the NodeB. essage to the CRNC. ds a QAAL2 ESTABLISH CONFIRM message. B sends a QAAL2 ESTABLISH RELEASE CONFIRM message.
er is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is
he UE. That is, the NodeB finishes UL synchronizationwith the UE.
sends a RADIO LINKRESTORE INDICATION message to the DRNC. message to the SRNC.
earers for data transmission on the Iur interface
ABLISH REQUEST messageto the DRNC. ssage to the SRNC. s a QAAL2 ESTABLISHCONFIRM message. sends a QAAL2 ESTABLISHRELEASE CONFIRM message.
active set of radio links between the UE and the UTRAN.
be triggered in either of the following conditions: Radio link addition or Radio link deletion
UE. If a radio link needs to be added, the message indicates radio link addition. If a radio link needs to be deleted,
o Link Addition Informationor Radio Link Removal Information IE contained in the ACTIVE SET UPDATE message.
ends an ACTIVE SETUPDATE COMPLETE message on the DCCH by using Acknowledged Mode (AM)Radio Link
uration not supported by the UE or if the active set does not contain the radio links specified by the Radio
UE. If a radio link needs to be added, the message indicates radio link addition. If a radio link needs to be deleted,
o Link Addition Informationor Radio Link Removal Information IE contained in the ACTIVE SET UPDATE message.
ends an ACTIVE SETUPDATE COMPLETE message on the DCCH by using Acknowledged Mode (AM)Radio Link
uration not supported by the UE or if the active set does not contain the radio links specified by the Radio UPDATE FAILURE message.
sources in a NodeB for one or more established radio links towards a UE.
LETION REQUEST message.
ssage to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the message.
LINK DELETION RESPONSE message DIO LINK DELETIONRESPONSE message. The Criticality Diagnostics field in the message indicates the failure
e data transport bearers from the Iub interface.
er plane need to be removed.
EASE REQUEST messageto the NodeB. essage to the CRNC. ends a QAAL2 RELEASECONFIRM message to confirm the release. deB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause.
eto release data transport bearers from the Iur interface.
er plane need to be removed.
EASE REQUEST messageto the NodeB. essage to the CRNC. ends a QAAL2 RELEASECONFIRM message to confirm the release. deB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause.
Click to return to main page RRC:Measurement Control
value=Intra-freq m
value=Intra-freq M
value=event1a trig
value=3 dB (IntraR
value=0 value=Maximum ac value=16 value=4000ms value=0 value=320ms
value=UE report A
value=event1b trig
value=6 dB (IntraR value=0 value=0 value=640ms
value=UE report A
value=event1C trig value=16 value=4000ms
value=4 dB (1C hy value=640ms
value=UE report A
value=4dB (1D hys value=640ms
value=UE report A
value= 1F event ab
value= 4 dB,step: 0 value=640ms
RRC:Measurement Report (e1a)
value=Event1a is t
value=To add neig
RRC:Measurement Report (e1b)
value=CPICH Ec/N
value=CPICH RSC
value=CPICH Ec/N
value=CPICH RSC
value=Event1b is t
value=To delete ne
RRC:Measurement Report (e1c)
RRC: Active Set Update (DCCH)
RRC: Active Set Update Complete (DCCH)
RRC: Active Set Update (DCCH)
RRC: Active Set Update Complete (DCCH)
>>"Measurement Control and Measurement Report"
value=intraFrequencyMeasurement value=intraFrequencyCell List
value=IntraFreqCellID of Serving Cell=0
value=Primary Scrambling Code of Serving Cell=74
value=IntraFreqCellID of Serving 1st neighbourCell=1
value=CIO=0 (No offset on this neighbour cell)
value=Primary Scrambling Code of 1st Neighbour Cell=106
value=Intra-freq meas L3 filter coeff=3
value=Intra-freq Measure Quantity use CPICH Ec/No
>>Intra-Frequency SHO Algorithm and related parameters (Module II)
value=event1a triggered by detected and MonitorSet Cells ( DETSET_ADD_TO_ACTSET_SWITCH and DETSET_RPRT_SWITCH is value=3 dB (IntraRelThdFor1A),step: 0.5 value=0 value=Maximum active set size =3 ( if number of cell in Active Set more than 2 then cannot trigger e1a) value=16 value=4000ms value=0 value=320ms
value=UE report All Active Set Cells + 6 Monitor/Detected Set Cells
value=event1b triggered by Active Set Cells Only value=6 dB (IntraRelThdFor1B) ,step: 0.5 value=0 value=0 value=640ms value=UE report All 3 Active Set Cells
value=event1C triggered when Active Set is full (Maximum 3 cells in Active Set) value=16 value=4000ms value=4 dB (1C hysteresis),step: 0.5 value=640ms
value=UE report All Active Set Cells + 6 Monitor/Detected Set Cells
value=4dB (1D hysteresis),step: 0.5 value=640ms
value=UE report All Active Set Cells +3 Monitor Set Cells
value=event1f triggered by Active Set Cells Only value= 1F event absolute EcNo threshold = -24 dB value= 4 dB,step: 0.5 value=640ms value=UE report All 3 Active Set Cells
>>"Measurement Report"
value=CPICH Ec/No= -24+(25/2) = -11.5 dB value=CPICH RSCP= -115+32= -83 dBm
value=Event1a is triggered
value=To add neighbour Primary Scrambling Code=13 into Active Set
value=CPICH Ec/No= -24+(31/2) = -8.5 dB value=CPICH RSCP= -115+34= -81 dBm
value=CPICH Ec/No= -24+(7/2) = -20.5 dB value=CPICH RSCP= -115+22= -93 dBm
value=Event1b is triggered
value=To delete neighbour Primary Scrambling Code=74 from Active Set
value=CPICH Ec/No= -24+(23/2) = -12.5 dB value=CPICH RSCP= -115+30= -85 dBm
value=CPICH Ec/No= -24+(20/2) = -14 dB value=CPICH RSCP= -115+29= -86 dBm
value=CPICH Ec/No= -24+(8/2) = -20 dB value=CPICH RSCP= -115+23= -92 dBm value=Event1c is triggered
value=To replace Cell Primary Scrambling Code=56 by Cell Primary Scrambling Code=106
ETSET_RPRT_SWITCH is "Active")
Click to return to main page
L3 Messages - Intra-Frequency Hard Handover Procedure UE
NodeB1 *Source
NodeB2
Intra-Frequency Hard Handover between NodeBs in a RNC RRC:Measurement Control RRC:Measurement Report (e1d)
Start Rx
ALCAP
Start Tx
1.RRC: Physical Channel Reconfiguration (DCCH)
2. RRC:Physical Channel Reconfiguration Complete (DCCH)
1.NBAP:Radio Link Deletion Req Stop Rx/Tx
2.NBAP:Radio Link Deletion Resp
ALCAP: Iub User Plane Release 1.QAAL2 Release Request 2.QAAL2 Release Confirm
Note: the following information about the procedure , 1. During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB. 2.If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface after radio links are set up or deleted.
L3 Messages - Intra-Frequency Hard Han UE
NodeB2 *Target
D-RNC
Intra-Frequency Hard Handover betwe RRC:Measurement Control RRC:Measurement Report (e1d)
2.NBAP:Radio Link Setup Request Start Rx 3.NBAP:Radio Link Setup Response ALCAP: Iub User Plane Setup
1.QAAL2 Establish Request 2.QAAL2 Establish Confirm 1.NBAP:Radio Link Restore Indication
Start Tx
1. RRC:Physical Channel Reconfiguration (
2. RRC:Physical Channel Reconfiguration Comp
Note : the following information about the procedure , 1.During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB. 2. If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface after radio links are set up or deleted. 3.If IP transport is applied to the Iur interface, no ALCAP procedure is performed on the Iurinterface after radio links are set up or deleted.
>>Intra-Frequency HHO Algorithm and related parameters
andover Procedure NodeB2 *Target
S-RNC
NodeBs in a RNC Measurement Control & Measurement Report
) Decision to setup new radio link
1.NBAP:Radio Link Setup Req Start Rx Radio Link Setup 2.NBAP:Radio Link Setup Resp ALCAP: Iub User Plane Setup 1.QAAL2 Establish Request
Iub user plane Setup
2.QAAL2 Establish Confirm
NBAP:Radio Link Restore Indication
Iub radio link restore Indication
Start Tx
n (DCCH) Physical Reconfiguration
mplete (DCCH) Decision to delete old radio link
AP:Radio Link Deletion Req
AP:Radio Link Deletion Resp
Radio Link Deletion
P: Iub User Plane Release Iub user plane release
QAAL2 Release Request
QAAL2 Release Confirm
Measurement Control & Measurement Report
Measurement Control & Measurement Report
requency Hard Handover Procedure NodeB1 *Source
D-RNC *Target
S-RNC *Source
y Hard Handover between RNCs
>>Measurement C
C:Measurement Control
Measurement Report (e1d)
RadioLink Setup Iub user plane Setup
Radio Link Setup Iub user plane Setup Iub Radio Link Restore Indication 1.RNSAP:Radio Link Setup Request Iub Radio Link Restore Indication Iur user plane Setup
Iur user plane Setup Iur Radio Link Restore Indication
Iur Radio Link Restore Indication
Active Set Update
Decision to setup new radio link
Iub user plane
Iub Radio Link 2.RNSAP:Radio Link Setup Response ALCAP: Iur User Plane Setup 1.QAAL2 Establish Request 2.QAAL2 Establish Confirm
2.RNSAP:Radio Link Restore Indication
al Channel Reconfiguration (DCCH)
annel Reconfiguration Complete (DCCH) Decision to delete old radio link
1.NBAP:Radio Link Deletion Req Stop Rx/Tx 2.NBAP:Radio Link Deletion Resp ALCAP: Iub User Plane Release 1.QAAL2 Release Request 2.QAAL2 Release Confirm
ALCAP: Iur User Plane Release 1.QAAL2 Release Request
2.QAAL2 Release Confirm
parameters
Measurement Control is used to notify the UE of the objects to be measured, neighbor cell list, report method, and even conditions are changed, the RNC notifies the UE of new conditions.
Measurement Report, the UE continue measure the radio link condition of serving and neighbour cell and when the me met, the UE reports the results to the RNC as an event. The Measurement report is also can be sent in periodic mode.
The radio link setup procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed to set up a radio for a UE The procedure of radio link setup is described as follows:
1.The CRNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB and configures the new radio link according to the parameters given in the message. 2.The NodeB sends a response message to the CRNC.If the radio link is set up, the NodeB saves the value of the Config in the RADIO LINK SETUP REQUEST message and sends a RADIOLINK SETUP RESPONSE message.If the radio link sends a RADIO LINK SETUP FAILURE message. The message contains the failure cause.
The Iub user plane setup procedure is performed to set up bearers for data transmission on the Iub interface
The procedure is described as follows: 1.The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST messageto the NodeB. 2.The NodeB uses the ALCAP protocol to send a response message to the CRNC.lIf the Iub data transport bearers are s ESTABLISH CONFIRM message.If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLIS
The radio link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover)is performed for a NodeB synchronization of one or more radio links is achieved or re-achieved
After performing UL synchronization with the UE, the NodeB sends a RADIO LINK RESTOREINDICATION message to t
The physical channel reconfiguration procedure is performed to set up, reconfigure, or releasea physical channel The procedure is described as follows: 1.The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a ph 2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.The UE sends a respons ->If successfully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION messa CHANNELRECONFIGURATION COMPLETE message on the uplink DCCH by using AM RLC ->If failing to reconfigure the physical channels specified by the PHYSICAL CHANNELRECONFIGURATION message, th the old physicalchannel configuration and sends a PHYSICAL CHANNEL RECONFIGURATION FAILURE message on t value of the Failure cause IE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE message is "physic
The procedure is described as follows: 1.The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a ph 2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.The UE sends a respons ->If successfully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION messa CHANNELRECONFIGURATION COMPLETE message on the uplink DCCH by using AM RLC ->If failing to reconfigure the physical channels specified by the PHYSICAL CHANNELRECONFIGURATION message, th the old physicalchannel configuration and sends a PHYSICAL CHANNEL RECONFIGURATION FAILURE message on t value of the Failure cause IE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE message is "physic
The radio link deletion procedure is performed to release resources in a NodeB for one or more established radio links The procedure is described as follows: 1.The CRNC sends a RADIO LINK DELETION REQUEST message to the NodeB. After receiving the message, the Nod by the message. 2.The NodeB sends a response message to the CRNC.lf all the radio links are deleted, the NodeB sends a RADIO LINK message. 3. lf any radio link fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The Criticality indicates the failure cause.
The Iub user plane release procedure is performed to release data transport bearers from the Iubinterface. The procedure is described as follows: 1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST messageto the NodeB. 2.The NodeB uses the ALCAP protocol to send a response message to the CRNC. ->If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm th ->lf an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECONFIRM message that indic
Click to return to main page
*Source
>>Measurement Control&Report Description Measurement Control & Measurement Report
Radio Link Setup
Measurement Control is used to notify the UE of the objects to be mea notifies the UE of new conditions.
Measurement Report, the UE continue measure the radio link condition the RNC as an event. The Measurement report is also can be sent in pe
The radio link setup procedure for inter-RNC handover is performed to s The procedure is described as follows: 1.The SRNC sends a RADIO LINK SETUP REQUEST message to the D 2.The DRNC sends a RADIO LINK SETUP REQUEST message to the t 3.The NodeB reserves the necessary resources and configures the new DRNC. ->If the radio link is set up, the NodeB saves the value of the Configurati RESPONSE message. ->If the radio link fails to be set up, the NodeB sends a RADIO LINK SET 4.The DRNC reports the radio link setup result to the SRNC. ->If the radio link is set up, the DRNC sends a RADIO LINK SETUP RES ->If the radio link fails to be set up, the DRNC sends a RADIO LINK SET
Radio Link Setup
->If the radio link is set up, the NodeB saves the value of the Configurati RESPONSE message. ->If the radio link fails to be set up, the NodeB sends a RADIO LINK SET 4.The DRNC reports the radio link setup result to the SRNC. ->If the radio link is set up, the DRNC sends a RADIO LINK SETUP RES ->If the radio link fails to be set up, the DRNC sends a RADIO LINK SET
Iub user plane Setup
Iub Radio Link Restore Indication
The Iub user plane setup procedure is performed to set up bearers for The procedure is described as follows:
1.The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH R 2.The NodeB uses the ALCAP protocol to send a response message to ->If the Iub data transport bearers are set up, the NodeB sends a QAAL ->If an Iub data transport bearer fails to be set up, the NodeB sends a Q Iur user plane Setup
The radio link restoration procedure for inter-RNC handover is perform achieved. Iur Radio Link Restore Indication
1.After performing UL synchronization with the UE, the NodeB sends a R 2.The DRNC sends a RADIO LINK RESTORE INDICATION message to
The Iur user plane setup procedure is performed to set up bearers for The procedure is described as follows: Physical Reconfiguration
1.The SRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH R 2.The DRNC uses the ALCAP protocol to send a response message to ->If the Iur data transport bearers are set up, the DRNC sends a QAAL2 ->If an Iur data transport bearer fails to be set up, the DRNC sends a QA
The physical channel reconfiguration procedure is performed to set u
Radio Link Deletion
The procedure is described as follows: 1.The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION mes 2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channe ->If successfully reconfiguring the physical channels specified by the PH COMPLETE message on the uplink DCCH by using AM RLC ->If failing to reconfigure the physical channels specified by the PHYSIC configuration and sends a PHYSICAL CHANNEL RECONFIGURATION CHANNEL RECONFIGURATION FAILURE message is "physical chann
Iub user plane release
The radio link deletion procedure is performed to release resources in
The procedure is described as follows: 1.The CRNC sends a RADIO LINK DELETION REQUEST message to 2.The NodeB sends a response message to the CRNC. ->lf all the radio links are deleted, the NodeB sends a RADIO LINK DELE ->lf any radio link fails to be deleted, the NodeB sends a RADIO LINK D Iur user plane release
The Iub user plane release procedure is performed to release data tra
The procedure is described as follows: 1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQ 2.The NodeB uses the ALCAP protocol to send a response message to ->If the Iub data transport bearers are released, the NodeB sends a QAA ->lf an Iub data transport bearer fails to be released, the NodeB sends a
The Iur user plane release procedure is performed to release data tran
The procedure is described as follows: 1.The SRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQ 2.The DRNC uses the ALCAP protocol to send a response message to ->If the Iur data transport bearers are released, the DRNC sends a QAA ->If an Iur data transport bearer fails to be released, the DRNC sends a
t, report method, and event parameters.When measurement
our cell and when the measurement reporting criterias are e sent in periodic mode.
erformed to set up a radio link in an SRNC-controlled NodeB
the message, the NodeB reserves the necessary resources
ves the value of the Configuration Generation ID IE contained E message.If the radio link fails to be set up, the NodeB
he Iub interface
he NodeB. ata transport bearers are set up, the NodeB sends a QAAL2 ends a QAAL2 ESTABLISH RELEASE CONFIRM message.
is performed for a NodeB to notify the CRNC that the uplink
NDICATION message to the CRNC.
asea physical channel
est reconfiguration of a physical channel. .The UE sends a response message to the SRNC. CONFIGURATION message, the UE sends a PHYSICAL
FIGURATION message, the UE restores the configuration to N FAILURE message on the DCCH by using AM RLC. The ILURE message is "physical channel failure".
est reconfiguration of a physical channel. .The UE sends a response message to the SRNC. CONFIGURATION message, the UE sends a PHYSICAL
FIGURATION message, the UE restores the configuration to N FAILURE message on the DCCH by using AM RLC. The ILURE message is "physical channel failure".
ore established radio links towards a UE.
ving the message, the NodeB deletes the radio links specified
deB sends a RADIO LINK DELETION RESPONSE message. The Criticality Diagnostics field in the message
e Iubinterface. NodeB.
RM message to confirm the release. NFIRM message that indicates the failure cause
E of the objects to be measured, neighbor cell list, report method, and event parameters.When measurement conditions are changed, the R
ure the radio link condition of serving and neighbour cell and when the measurement reporting criterias are met, the UE reports the results to t is also can be sent in periodic mode.
andover is performed to set up a radio link in a DRNC-controlled NodeB for a UE
EQUEST message to the DRNC. EQUEST message to the target NodeB. es and configures the new radio link according to the parameters given in the message.The NodeB reports the radio link setup result to the
he value of the Configuration GenerationID IE contained in the RADIO LINK SETUP REQUEST message and sends a RADIOLINK SETUP
sends a RADIO LINK SETUP FAILUREmessage. to the SRNC. RADIO LINK SETUP RESPONSEmessage. sends a RADIO LINK SETUP FAILURE message, indicating the failure cause.
he value of the Configuration GenerationID IE contained in the RADIO LINK SETUP REQUEST message and sends a RADIOLINK SETUP
sends a RADIO LINK SETUP FAILUREmessage. to the SRNC. RADIO LINK SETUP RESPONSEmessage. sends a RADIO LINK SETUP FAILURE message, indicating the failure cause.
rmed to set up bearers for data transmission on the Iub interface
d a QAAL2 ESTABLISH REQUEST messageto the NodeB. d a response message to the CRNC. he NodeB sends a QAAL2 ESTABLISH CONFIRM message. up, the NodeB sends a QAAL2 ESTABLISH RELEASE CONFIRM message
-RNC handover is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is achieved or re-
UE, the NodeB sends a RADIO LINKRESTORE INDICATION message to the DRNC. INDICATION message to the SRNC.
med to set up bearers for data transmission on the Iur interface
d a QAAL2 ESTABLISH REQUEST message to the DRNC. d a response message to the SRNC. he DRNC sends a QAAL2 ESTABLISHCONFIRM message. up, the DRNC sends a QAAL2 ESTABLISHRELEASE CONFIRM message.
edure is performed to set up, reconfigure, or releasea physical channel
RECONFIGURATION message to the UE to request reconfiguration of a physical channel. er (RB), transport channel, and physical channel.The UE sends a response message to the SRNC. nnels specified by the PHYSICALCHANNEL RECONFIGURATION message, the UE sends a PHYSICAL CHANNELRECONFIGURATION using AM RLC specified by the PHYSICAL CHANNELRECONFIGURATION message, the UE restores the configuration to the old physicalchannel EL RECONFIGURATION FAILURE message on the DCCH by using AM RLC. The value of the Failure cause IE contained in the PHYSICAL essage is "physical channel failure".
ed to release resources in a NodeB for one or more established radio links towards a UE.
N REQUEST message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the message. he CRNC. ends a RADIO LINK DELETION RESPONSE message. B sends a RADIO LINK DELETION RESPONSE message. The Criticality Diagnostics field in the message indicates the failure cause.
ormed to release data transport bearers from the Iubinterface.
d a QAAL2 RELEASE REQUEST messageto the NodeB. d a response message to the CRNC. d, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the release. ased, the NodeB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause
ormed to release data transport bearers from the Iur interface
d a QAAL2 RELEASE REQUEST messageto the DRNC. d a response message to the SRNC. , the DRNC sends a QAAL2 RELEASECONFIRM message to confirm the release. ased, the DRNC sends a QAAL2 RELEASECONFIRM message that indicates the failure cause.
t conditions are changed, the RNC
met, the UE reports the results to
e radio link setup result to the
d sends a RADIOLINK SETUP
d sends a RADIOLINK SETUP
radio links is achieved or re-
HANNELRECONFIGURATION
the old physicalchannel e IE contained in the PHYSICAL
d by the message.
dicates the failure cause.
Click to return to main page
L3 Messages - Inter-Frequency Hard Handover Procedure UE
NodeB1 *Source
NodeB2
Inter-Frequency Hard Handover between NodeBs in a RNC RRC:Measurement Control RRC:Measurement Report (e2d)
NBAP: Radio Link Reconfiguration Prep
NBAP: Radio Link Reconfiguration Rea
NBAP: Radio Link Reconfiguration Com RRC:Physical Channel Reconfiguration (DCCH) RRC:Physical Channel Reconfiguration Complete (DCCH)
NBAP: Compressed Mode Command RRC:Measurement Control RRC:Measurement Report RRC:Measurement Report
Start Rx
ALCAP
Start Tx
1.RRC: Physical Channel Reconfiguration (DCCH)
2. RRC:Physical Channel Reconfiguration Complete (DCCH)
1.NBAP:Radio Link Deletion Req Stop Rx/Tx 2.NBAP:Radio Link Deletion Resp ALCAP: Iub User Plane Release 1.QAAL2 Release Request 2.QAAL2 Release Confirm
Note: the following information about the procedure , 1.The radio link setup procedure shown in the figure applies when the source and target cellsof the handover are controlled by different NodeBs. If the source and target cells arecontrolled by the same NodeB, the radio link setup procedure should be replaced by theradio link addition procedure, and the radio link restoration procedure is excluded. 2.During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB. 3.If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface after radio links are set up or deleted.
L3 Messages - Inter-Frequency Hard Han UE
NodeB2 *Target
D-RNC
Inter-Frequency Hard Handover betwe
2.NBAP:Radio Link Setup Request Start Rx 3.NBAP:Radio Link Setup Response ALCAP: Iub User Plane Setup 1.QAAL2 Establish Request 2.QAAL2 Establish Confirm 1.NBAP:Radio Link Restore Indication
Start Tx
1. RRC:Physical Channel Reconfiguration (
2. RRC:Physical Channel Reconfiguration Comp
Note : the following information about the procedure , 1.During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB. 2. If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface after radio links are set up or deleted. 3.If IP transport is applied to the Iur interface, no ALCAP procedure is performed on the Iurinterface after radio links are set up or deleted.
>>Intrer-Frequency HHO Algorithm and related parameters
over Procedure *Target
S-RNC
eBs in a RNC Measurement Control & Measurement Report
nk Reconfiguration Prepare
ink Reconfiguration Ready
>>Compressed Mode Description Module II
nk Reconfiguration Commit Initial Compressed Mode Configuration
CH) (DCCH)
pressed Mode Command
Inter-Freq Neighbour cells measurement
Decision to setup new radio link
1.NBAP:Radio Link Setup Req
Radio Link Setup 2.NBAP:Radio Link Setup Resp ALCAP: Iub User Plane Setup 1.QAAL2 Establish Request
Iub user plane Setup
2.QAAL2 Establish Confirm
NBAP:Radio Link Restore Indication
Iub radio link restore Indication
Iub radio link restore Indication
CCH) Physical Reconfiguration
e (DCCH) Decision to delete old radio link
adio Link Deletion Req Radio Link Deletion
adio Link Deletion Resp
b User Plane Release Iub user plane release
2 Release Request
2 Release Confirm
uency Hard Handover *Target
Measurement Control Procedure & Measurement Report
Measurement Control & Measurement Report
NodeB1 *Source
S-RNC
*Source
rd Handover between RNCs Decision to setup new radio link
1.RNSAP:Radio Link Setup Request
Radio
Iub user plane Se
Iub Radio Link Re 2.RNSAP:Radio Link Setup Response ALCAP: Iur User Plane Setup 1.QAAL2 Establish Request 2.QAAL2 Establish Confirm
2.RNSAP:Radio Link Restore Indication
Iur Radio Link Restore I
annel Reconfiguration (DCCH)
Physical Reconfig
l Reconfiguration Complete (DCCH)
Decision to delete old radio link
1.NBAP:Radio Link Deletion Req Stop Rx/Tx
Radio Link Deleti
2.NBAP:Radio Link Deletion Resp ALCAP: Iub User Plane Release 1.QAAL2 Release Request
Iub user plane re
2.QAAL2 Release Confirm
ALCAP: Iur User Plane Release 1.QAAL2 Release Request 2.QAAL2 Release Confirm
Iur user plane re
eters
Measurement Control is used to notify the UE of the objects to be measured, neighbor cell list, report method, and event par conditions are changed, the RNC notifies the UE of new conditions.
Measurement Report, the UE continue measure the radio link condition of serving and neighbour cell and when the measure the UE reports the results to the RNC as an event. The Measurement report is also can be sent in periodic mode.
Compressed Mode was introduced to WCDMA to allow inter-frequency and Inter-RAT Handovers. It is used to create idle pe during which neighbour cells measurements on another frequency can be made.
The radio link setup procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed to set up a radio link in UE The procedure of radio link setup is described as follows:
1.The CRNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB reser configures the new radio link according to the parameters given in the message. 2.The NodeB sends a response message to the CRNC.If the radio link is set up, the NodeB saves the value of the Configurati the RADIO LINK SETUP REQUEST message and sends a RADIOLINK SETUP RESPONSE message.If the radio link fails to RADIO LINK SETUP FAILURE message. The message contains the failure cause.
The Iub user plane setup procedure is performed to set up bearers for data transmission on the Iub interface
The procedure is described as follows: 1.The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST messageto the NodeB. 2.The NodeB uses the ALCAP protocol to send a response message to the CRNC.lIf the Iub data transport bearers are set up ESTABLISH CONFIRM message.If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH RE
The radio link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover)is performed for a NodeB to no synchronization of one or more radio links is achieved or re-achieved
After performing UL synchronization with the UE, the NodeB sends a RADIO LINK RESTOREINDICATION message to the CR
The physical channel reconfiguration procedure is performed to set up, reconfigure, or releasea physical channel The procedure is described as follows: 1.The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physica 2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.The UE sends a response mes ->If successfully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION message, th CHANNELRECONFIGURATION COMPLETE message on the uplink DCCH by using AM RLC
The physical channel reconfiguration procedure is performed to set up, reconfigure, or releasea physical channel The procedure is described as follows: 1.The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physica 2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.The UE sends a response mes ->If successfully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION message, th CHANNELRECONFIGURATION COMPLETE message on the uplink DCCH by using AM RLC ->If failing to reconfigure the physical channels specified by the PHYSICAL CHANNELRECONFIGURATION message, the UE old physicalchannel configuration and sends a PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH the Failure cause IE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE message is "physical channel fa
The radio link deletion procedure is performed to release resources in a NodeB for one or more established radio links towa The procedure is described as follows: 1.The CRNC sends a RADIO LINK DELETION REQUEST message to the NodeB. After receiving the message, the NodeB d the message. 2.The NodeB sends a response message to the CRNC.lf all the radio links are deleted, the NodeB sends a RADIO LINK DELE 3. lf any radio link fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The Criticality Diagn indicates the failure cause.
The Iub user plane release procedure is performed to release data transport bearers from the Iubinterface. The procedure is described as follows: 1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST messageto the NodeB. 2.The NodeB uses the ALCAP protocol to send a response message to the CRNC. ->If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the rele ->lf an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECONFIRM message that indicates
Click to return to main page
The radio link setup procedure for inter-RNC handover is performed to s The procedure is described as follows: 1.The SRNC sends a RADIO LINK SETUP REQUEST message to the D 2.The DRNC sends a RADIO LINK SETUP REQUEST message to the t
The radio link setup procedure for inter-RNC handover is performed to s The procedure is described as follows: 1.The SRNC sends a RADIO LINK SETUP REQUEST message to the D 2.The DRNC sends a RADIO LINK SETUP REQUEST message to the t 3.The NodeB reserves the necessary resources and configures the new DRNC. ->If the radio link is set up, the NodeB saves the value of the Configurati RESPONSE message. ->If the radio link fails to be set up, the NodeB sends a RADIO LINK SET 4.The DRNC reports the radio link setup result to the SRNC. ->If the radio link is set up, the DRNC sends a RADIO LINK SETUP RES ->If the radio link fails to be set up, the DRNC sends a RADIO LINK SET
Radio Link Setup
The Iub user plane setup procedure is performed to set up bearers for The procedure is described as follows: Iub user plane Setup
Iub Radio Link Restore Indication
Iur user plane Setup
1.The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH R 2.The NodeB uses the ALCAP protocol to send a response message to ->If the Iub data transport bearers are set up, the NodeB sends a QAAL ->If an Iub data transport bearer fails to be set up, the NodeB sends a Q
The radio link restoration procedure for inter-RNC handover is perform achieved.
1.After performing UL synchronization with the UE, the NodeB sends a R 2.The DRNC sends a RADIO LINK RESTORE INDICATION message to
ur Radio Link Restore Indication
Physical Reconfiguration
The Iur user plane setup procedure is performed to set up bearers for The procedure is described as follows:
1.The SRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH R 2.The DRNC uses the ALCAP protocol to send a response message to ->If the Iur data transport bearers are set up, the DRNC sends a QAAL2 ->If an Iur data transport bearer fails to be set up, the DRNC sends a QA
The physical channel reconfiguration procedure is performed to set u
The procedure is described as follows: 1.The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION mes 2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channe ->If successfully reconfiguring the physical channels specified by the PH COMPLETE message on the uplink DCCH by using AM RLC ->If failing to reconfigure the physical channels specified by the PHYSIC configuration and sends a PHYSICAL CHANNEL RECONFIGURATION CHANNEL RECONFIGURATION FAILURE message is "physical chann Radio Link Deletion
The radio link deletion procedure is performed to release resources in
Iub user plane release
The procedure is described as follows: 1.The CRNC sends a RADIO LINK DELETION REQUEST message to 2.The NodeB sends a response message to the CRNC. ->lf all the radio links are deleted, the NodeB sends a RADIO LINK DELE ->lf any radio link fails to be deleted, the NodeB sends a RADIO LINK D
The Iub user plane release procedure is performed to release data tra Iur user plane release
The procedure is described as follows: 1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQ 2.The NodeB uses the ALCAP protocol to send a response message to ->If the Iub data transport bearers are released, the NodeB sends a QAA ->lf an Iub data transport bearer fails to be released, the NodeB sends a
The Iur user plane release procedure is performed to release data tran
The procedure is described as follows: 1.The SRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQ 2.The DRNC uses the ALCAP protocol to send a response message to ->If the Iur data transport bearers are released, the DRNC sends a QAA ->If an Iur data transport bearer fails to be released, the DRNC sends a
ort method, and event parameters.When measurement
ell and when the measurement reporting criterias are met, eriodic mode.
It is used to create idle periods (gaps) in the transmission
med to set up a radio link in an SRNC-controlled NodeB for a
essage, the NodeB reserves the necessary resources and
e value of the Configuration Generation ID IE contained in age.If the radio link fails to be set up, the NodeB sends a
b interface
odeB. ansport bearers are set up, the NodeB sends a QAAL2 a QAAL2 ESTABLISH RELEASE CONFIRM message.
formed for a NodeB to notify the CRNC that the uplink
ATION message to the CRNC.
physical channel
econfiguration of a physical channel. UE sends a response message to the SRNC. FIGURATION message, the UE sends a PHYSICAL
physical channel
econfiguration of a physical channel. UE sends a response message to the SRNC. FIGURATION message, the UE sends a PHYSICAL
RATION message, the UE restores the configuration to the RE message on the DCCH by using AM RLC. The value of ge is "physical channel failure".
stablished radio links towards a UE.
he message, the NodeB deletes the radio links specified by
ends a RADIO LINK DELETION RESPONSE message. sage. The Criticality Diagnostics field in the message
nterface.
eB.
essage to confirm the release. M message that indicates the failure cause
andover is performed to set up a radio link in a DRNC-controlled NodeB for a UE
EQUEST message to the DRNC. EQUEST message to the target NodeB.
andover is performed to set up a radio link in a DRNC-controlled NodeB for a UE
EQUEST message to the DRNC. EQUEST message to the target NodeB. es and configures the new radio link according to the parameters given in the message.The NodeB reports the radio link setup result to the
he value of the Configuration GenerationID IE contained in the RADIO LINK SETUP REQUEST message and sends a RADIOLINK SETUP
sends a RADIO LINK SETUP FAILUREmessage. to the SRNC. RADIO LINK SETUP RESPONSEmessage. sends a RADIO LINK SETUP FAILURE message, indicating the failure cause.
rmed to set up bearers for data transmission on the Iub interface
d a QAAL2 ESTABLISH REQUEST messageto the NodeB. d a response message to the CRNC. he NodeB sends a QAAL2 ESTABLISH CONFIRM message. up, the NodeB sends a QAAL2 ESTABLISH RELEASE CONFIRM message
-RNC handover is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is achieved or re-
UE, the NodeB sends a RADIO LINKRESTORE INDICATION message to the DRNC. INDICATION message to the SRNC.
med to set up bearers for data transmission on the Iur interface
d a QAAL2 ESTABLISH REQUEST message to the DRNC. d a response message to the SRNC. he DRNC sends a QAAL2 ESTABLISHCONFIRM message. up, the DRNC sends a QAAL2 ESTABLISHRELEASE CONFIRM message.
edure is performed to set up, reconfigure, or releasea physical channel
RECONFIGURATION message to the UE to request reconfiguration of a physical channel. er (RB), transport channel, and physical channel.The UE sends a response message to the SRNC. nnels specified by the PHYSICALCHANNEL RECONFIGURATION message, the UE sends a PHYSICAL CHANNELRECONFIGURATION using AM RLC specified by the PHYSICAL CHANNELRECONFIGURATION message, the UE restores the configuration to the old physicalchannel EL RECONFIGURATION FAILURE message on the DCCH by using AM RLC. The value of the Failure cause IE contained in the PHYSICAL essage is "physical channel failure".
ed to release resources in a NodeB for one or more established radio links towards a UE.
N REQUEST message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the message. he CRNC. ends a RADIO LINK DELETION RESPONSE message. B sends a RADIO LINK DELETION RESPONSE message. The Criticality Diagnostics field in the message indicates the failure cause.
ormed to release data transport bearers from the Iubinterface.
d a QAAL2 RELEASE REQUEST messageto the NodeB. d a response message to the CRNC. d, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the release. ased, the NodeB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause
ormed to release data transport bearers from the Iur interface
d a QAAL2 RELEASE REQUEST messageto the DRNC. d a response message to the SRNC. , the DRNC sends a QAAL2 RELEASECONFIRM message to confirm the release. ased, the DRNC sends a QAAL2 RELEASECONFIRM message that indicates the failure cause.
e radio link setup result to the
d sends a RADIOLINK SETUP
radio links is achieved or re-
HANNELRECONFIGURATION
the old physicalchannel e IE contained in the PHYSICAL
d by the message.
dicates the failure cause.
Click to return to main page
L3 Messages - Inter-RAT Han UE
NodeB
S-RNC Inter-RAT CS Handover from
RRC:Measurement Control RRC:Measurement Report (e2d) RRC:Measurement Report (e2f) RRC:Measurement Report (e2d) NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready NBAP: Radio Link Reconfiguration Commit 1. RRC:Physical Channel Reconfiguration (DCCH) 2. RRC: Physical Channel Reconfiguration Complete (DCCH) NBAP: Compressed Mode Command RRC:Measurement Control RRC:Measurement Report RRC:Measurement Report Decision to HO to GSM cell
7.RRC: Handover from UTRAN Command
9.Handover Comple
NBAP:Radio Link Deletion Request NBAP:Radio Link Deletion Response
Note: the following information about the procedure , 1.This figure presents only a brief of the signaling between the MSC server and the MSC(GSM) and that between the MSC (GSM) and the BSC (GSM). 2.The SRNC sends a HANDOVER FROM UTRAN COMMAND message to the UE. The message contains the RAB ID, the activation time, the GSM frequency, and the GSM information in bit strings.
Click to return to main page
L3 Messages - Inter-RAT Han UE
NodeB
S-RNC Inter-RAT CS Handover from
4.NBAP:Radio Link Setup Request 5.NBAP:Radio Link setup Response
9.Inter-System to UTRAN Hando 10.NBAP:Radio Link Restore Indication 12.RRC: Handover to UTRAN Complete(DCCH) 13.RRC: UE Capability Enquiry(DCCH) 14.RRC: UE Capability Information (DCCH) 15.RRC: UE Capability Information Confirm (DCCH) 16.RRC: Security Mode Command(DCCH) 17.RRC: Security Mode Complete(DCCH)
23.RRC: UTRAN Mobility Information (DCCH) 24.RRC: UTRAN Mobility Information Confirm (DCCH)
Note: the following information about the procedure , 1.This figure presents only a brief of the signaling between the MSC server and the MSC(GSM) and that between the MSC (GSM) and the BSC (GSM). 2.After receiving a RADIO LINK RESTORE INDICATION message, the RNC sends a RELOCATION DETECT message to the MSC server to inform the MSC server that the UE has been handed over from GSM to WCDMA. 3.After the UE is handed over, it sends a HANDOVER TO UTRAN COMPLETE message to the RNC. If the handover fails, the UE reports the failure to the GSM system. 4.After receiving a HANDOVER TO UTRAN COMPLETE message, the RNC sends a RELOCATION COMPLETE message to the MSC server. In addition, the RNC controls the UE to perform the UTRAN mobility information procedure, the UE capability enquiry procedure, and the security mode control procedure. 5.In practice, the signaling messages traced may differ from the signaling message shown inthe figure in terms of the sequence
perform the UTRAN mobility information procedure, the UE capability enquiry procedure, and the security mode control procedure. 5.In practice, the signaling messages traced may differ from the signaling message shown inthe figure in terms of the sequence
es - Inter-RAT Handover Procedure MSC 2G
MSC 3G
T CS Handover from WCDMA to GSM
1.RANAP: Relocation Required 2.Prepare Handover 3.Handover Request 4.Handover Request Acknowledge 5.Prepare Handover Response 6.RANAP:Relocation Command
8.Handover Detect 9.Handover Completed 10.Handover Complete 11.Send End Signal Request 12.RANAP: IU Release Command
13.RANAP: IU Release Complete 14.Send End Signal Response
Measurement Control & Measurement Report
es - Inter-RAT Handover Procedure Measurement Control & Measurement Report
MSC-3G
MSC-2G
T CS Handover from GSM to WCDMA 1.Handover Required RadioLink Setup
2.Prepare Handover
3.RANAP: Relocation Request Iub user plane Setup
6.RANAP:Relocation Request Radio Link Setup Acknowledge Iub user plane Setup
Iub Radio Link Restore Indication
Iub Radio Link Restore Indication
7.Prepare Handover Response Iur user plane Setup
8.Handover Command 9.Handover Complete
r-System to UTRAN Handover Command
11.RANAP:Relocation Detect
18.RANAP:Relocation Complete 19.Send End Signal Request 20.Clear Command Measurement Control & Measurement Report 22.Send End Signal
Response
RadioLink Setup Iub user plane Setup
Iub Radio Link Restore Indication
Measurement Control & Measurement Report Iur user plane Setup
Iur Radio Link Restore Indication
Active Set Update
21.Clear Complete
Measurement Control & Measurement Report
Measurement Control & Measurement Report
Measurement Control & Measurement Report
RadioLink Setup Iub user plane Setup
Iub Radio Link Restore Indication
Measurement Control & Measurement Report
>>Inter-RAT HO Algorithm and related parameters
BSC 2G
>>Measurement Control&Report (Inter-RAT) Description
Measurement Control is used to notify the UE changed, the RNC notifies the UE of new condit
Measurement Report, the UE continue measu the results to the RNC as an event. The Measur Measurement Control & Measurement Report
Compressed Mode was introduced to WCDMA neighbour cells measurements on another frequ
>>Compressed Mode Description Initial Compressed Mode Configuration
The relocation preparation procedure is perfo The procedure is described as follows:
1.The SRNC sends a RELOCATION REQUIRE source LAC,source SAC, target PLMN, and targ 2.The CN interacts with the target RNC or the ta 3.The CN sends a response message to the SR ->If the target RNC or the target network system complete. The message contains the L3 informa ->If the resources partially or totally fail to be allo GSM RSSI Measurement and BSIC Verification
The Inter-RAT Handover procedure is describe
Relocation Preparation
1. The SRNC sends the 3G MSC a RANAP mes 2. As indicated in the received message,the 3G Handover" 3. The 2G MSC forwards the request to the BSC 4. The BSC responds to this request. The mess 5. Once the initial procedures are completed in t 6. The 3G MSC sends the SRNC a RANAP mes 7. The SRNC send the UE and RRC message " several other systems 8. The BSC performs handover detection. The f reference and is subject to the actual conditon o 9. The UE send the BSC a "Handover Complete 10. The BSC sends the MSC a 'Handover Comp GSM 11. After detecting the UE in the coverage area 12. The CN sends the former SRNC and "Iu Re 13. After the bearer resource is related in the UM 14. After the call ends, the CN sends the MSC a
Handover
8. The BSC performs handover detection. The f reference and is subject to the actual conditon o 9. The UE send the BSC a "Handover Complete 10. The BSC sends the MSC a 'Handover Comp GSM 11. After detecting the UE in the coverage area 12. The CN sends the former SRNC and "Iu Re 13. After the bearer resource is related in the UM 14. After the call ends, the CN sends the MSC a
Iu release
The Iu release procedure is performed for the C
The procedure is described as follows: 1.The CN sends an IU RELEASE COMMAND m connection. NOTE: After sending the IU RELEASE COMMA
Radio Link Deletion
2.The SRNC releases the related UTRAN resou
The radio link deletion procedure is performed The procedure is described as follows: 1.The CRNC sends a RADIO LINK DELETION 2.The NodeB sends a response message to the ->If all the radio links are deleted, the NodeB se ->If any radio link fails to be deleted, the NodeB cause.
>>Inter-RAT HO Algorithm and related parameters
BSC 2G
The relocation resource allocation procedure The relocation resource allocation procedure ca 1. During an SRNS relocation, the CN applies fo 2. During an inter-RAT CS handover from GSM
Relocation Resource allocation
The procedure is described as follows: 1.The CN sends a RELOCATION REQUEST m cell identifier, encryption, integrity protection, Iu 2.The target RNC allocates radio resources for 3.The target RNC sends a response message to ->If the resources are allocated, the target RNC parameters allocated to the UE. The parameters encryption algorithm, and chosen integrity prote ->If the resources partially or totally fail to be allo FAILURE message,indicating the failure cause
3.The target RNC sends a response message to ->If the resources are allocated, the target RNC parameters allocated to the UE. The parameters encryption algorithm, and chosen integrity prote ->If the resources partially or totally fail to be allo FAILURE message,indicating the failure cause
The radio link setup procedure (intra-RNC han
Radio Link Restoration
The procedure is described as follows: 1.The CRNC sends a RADIO LINK SETUP REQ new radio link according to the parameters given 2.The NodeB sends a response message to the ->If the radio link is set up, the NodeB saves the LINK SETUP RESPONSE message. ->If the radio link fails to be set up, the NodeB s
UE Capability Enquiry
The radio link restoration procedure (intra-RN one or moreradio links is achieved or re-achieve
After performing UL synchronization with the UE Security Mode Control
The UE capability enquiry procedure is perfor data configuration based on the UE capability
The procedure is described as follows: 1.The SRNC sends a UE CAPABILITY ENQUIR 2.The UE sends a UE CAPABILITY INFORMAT capabilities. 3.The SRNC reads the UE capability information UMRLC.
UTRAN Mobility Information
The security mode control procedure is perfo triggered conditon is when the ciphering algorith The procedure is described as follows: 1.Through a SECURITY MODE COMMAND me theRBs or one CN domain and for all Signaling 2.The UE sends a response message to the SR ->If the UE completes configuring or reconfigurin COMPLETE message to inform the SRNC of th ->If the SECURITY MODE COMMAND messag information, the UE sends a SECURITY MODE
The UTRAN mobility information procedure is TemporaryIdentifier (C-RNTI) to a UE or to infor
1.The SRNC sends a UTRAN MOBILITY INFOR 2.The UE starts to update the related fields acco 3.The UE sends a response message to the SR ->If the UE succeeds in conducting the operatio CONFIRM message. ->If the UE fails to conduct the operations speci message, indicating the failure cause.
TemporaryIdentifier (C-RNTI) to a UE or to infor
1.The SRNC sends a UTRAN MOBILITY INFOR 2.The UE starts to update the related fields acco 3.The UE sends a response message to the SR ->If the UE succeeds in conducting the operatio CONFIRM message. ->If the UE fails to conduct the operations speci message, indicating the failure cause.
l is used to notify the UE of the objects to be measured, neighbor cell list, report method, and event parameters.When measurement conditi fies the UE of new conditions.
the UE continue measure the radio link condition of serving and neighbour cell and when the measurement reporting criterias are met, the as an event. The Measurement report is also can be sent in periodic mode.
as introduced to WCDMA to allow inter-frequency and Inter-RAT Handovers. It is used to create idle periods (gaps) in the transmission durin rements on another frequency can be made.
ation procedure is performed to prepare resources for relocation of the SRNS
cribed as follows:
RELOCATION REQUIRED message to the CN. The message contains certain information such as relocation type, relocation cause, source C, target PLMN, and target CI,LAC. h the target RNC or the target network system, such as the GSM system, to prepare relevant resources. ponse message to the SRNC. he target network system prepares the relevant resources successfully, the CN sends a RELOCATION COMMAND message when the prep e contains the L3 information IE, which carries the information about the relevant resources allocated by the target RNC or the target networ ally or totally fail to be allocated, the CN sends a RELOCATIONPREPARATION FAILURE message.
ver procedure is described as follows:
e 3G MSC a RANAP message "Relocation Required" if the condition of Inter-RAT Outgoing HO is met eceived message,the 3G MSC forwards this request to the 2G MSC on the MAP/E interface through a MAP message "Prepare
ds the request to the BSC. The message shown in the figure is for reference only and is subject to the actual conditon of the GSM o this request. The message shown in the figure is for reference only and is subject to the actual conditon of the GSM edures are completed in the 2G MSC/BSS,the 2G MSC returns a MAP/E message 'Prepare Handover Response" the SRNC a RANAP message "Relocation Command" UE and RRC message "Handover from UTRAN" through the existing RRC connection. This message may include information from one or
handover detection. The figure does not show such procedures as GSM BSS synchronization. The message shown in the figure is for ct to the actual conditon of GSM C a "Handover Complete" message e MSC a 'Handover Complete" message. The message shown in the figure for reference only and is subject to the actual condition of the
UE in the coverage area of the GSM,the MSC sends the CN a MAP/E message "Send End Signal Request" former SRNC and "Iu Release Command" message , requesting the former SRNC to release the allocated resource source is related in the UMTS, the former SRNC sends the CN an "Iu Release Complete" message the CN sends the MSC a MAP/E message "Send End Signal Response"
handover detection. The figure does not show such procedures as GSM BSS synchronization. The message shown in the figure is for ct to the actual conditon of GSM C a "Handover Complete" message e MSC a 'Handover Complete" message. The message shown in the figure for reference only and is subject to the actual condition of the
UE in the coverage area of the GSM,the MSC sends the CN a MAP/E message "Send End Signal Request" former SRNC and "Iu Release Command" message , requesting the former SRNC to release the allocated resource source is related in the UMTS, the former SRNC sends the CN an "Iu Release Complete" message the CN sends the MSC a MAP/E message "Send End Signal Response"
ure is performed for the CN to release an Iu connection and all the UTRANresources related only to that Iu connection
cribed as follows: RELEASE COMMAND message to the SRNC to initiate the Iu release procedure. The message indicates the cause for the release of the si
he IU RELEASE COMMAND message, the CN will not send further RANAP connection-oriented messages on this particular connection.
the related UTRAN resources and then sends an IU RELEASE COMPLETE message to the CN.
n procedure is performed to release resources in a NodeB for one or more established radio links towards a UE. cribed as follows: RADIO LINK DELETION REQUEST message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the response message to the CRNC. re deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. o be deleted, the NodeB sends a RADIO LINK DELETIONRESPONSE message. The Criticality Diagnostics field in the message indicates t
ce allocation procedure is performed to allocate resources from the targetRNS for an SRNS relocation. e allocation procedure can be triggered in either of the followingconditions: ocation, the CN applies for resources from the target RNC CS handover from GSM to WCDMA, the CN applies for resources from the target RNC
cribed as follows: LOCATION REQUEST message to the target RNC. The message contains certain information, such as the IMSI of the UE, CN domain indic n, integrity protection, Iu signaling connection ID, handover cause, andRAB parameters. ates radio resources for the relocation. ds a response message to the CN. allocated, the target RNC sends a RELOCATION REQUEST ACKNOWLEDGE message. The message contains the radio resources and ot o the UE. The parameters include the UTRAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transport layer and physical layer informa nd chosen integrity protection algorithm. ally or totally fail to be allocated or the target RNC rejects the SRNS relocation for some reason, the target RNC sends a RELOCATION icating the failure cause
ds a response message to the CN. allocated, the target RNC sends a RELOCATION REQUEST ACKNOWLEDGE message. The message contains the radio resources and ot o the UE. The parameters include the UTRAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transport layer and physical layer informa nd chosen integrity protection algorithm. ally or totally fail to be allocated or the target RNC rejects the SRNS relocation for some reason, the target RNC sends a RELOCATION icating the failure cause
procedure (intra-RNC handover or GSM to WCDMA CS handover) isperformed to set up a radio link in an SRNC-controlled NodeB for a UE
cribed as follows: RADIO LINK SETUP REQUEST message to the NodeB. Afterr eceiving the message, the NodeB reserves the necessary resources and con g to the parameters given in the message. response message to the CRNC. up, the NodeB saves the value of the Configuration GenerationID IE contained in the RADIO LINK SETUP REQUEST message and sends NSE message. o be set up, the NodeB sends a RADIO LINK SETUP FAILURE message. The message contains the failure cause.
tion procedure (intra-RNC handover or GSM to WCDMA CS handover)is performed for a NodeB to notify the CRNC that the uplink synchro is achieved or re-achieved
nchronization with the UE, the NodeB sends a RADIO LINK RESTOREINDICATION message to the CRNC
quiry procedure is performed to request a UE to transmit its capability information related to any radio access network so that the network ca ed on the UE capability
cribed as follows: UE CAPABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC. CAPABILITY INFORMATION message to the SRNC through the uplink DCCH using AM or UM RLC. The message contains the information
UE capability information and then sends a UE CAPABILITYINFORMA CONFIRM message to the UE through the downlink DCCH using AM
ntrol procedure is performed to configure or reconfigure one or both of the ciphering algorithm and the integrity protection algorithm for a U hen the ciphering algorithm or the integrity protection algorithm has changed cribed as follows: Y MODE COMMAND message sent to the UE, the SRNC starts or reconfigures one or both of the ciphering and integrity protection configur main and for all Signaling Radio Bearers (SRBs). onse message to the SRNC. configuring or reconfiguring the relevant parameters for one orboth of the ciphering and integrity protection algorithms, the UE sends a SECU to inform the SRNC of the completion. ODE COMMAND message contains neither Ciphering mode info IE nor Integrity protection mode info IE or if each of the two IEs has inconsis nds a SECURITY MODE FAILURE message, indicating the failure of the security mode control procedure as well as the failure cause.
nformation procedure is performed for the network to allocate a newUTRAN Radio Network Temporary Identifier (U-RNTI) or Cell Radio N -RNTI) to a UE or to inform the UE of mobility-related information such as timervalues and CN domain–related information
UTRAN MOBILITY INFORMATION message to the UE. ate the related fields according to the values of the IEs carried in themessage. onse message to the SRNC. n conducting the operations specified by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MOBILITY INFORMATIO
duct the operations specified by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MOBILITY INFORMATIONFAILU e failure cause.
-RNTI) to a UE or to inform the UE of mobility-related information such as timervalues and CN domain–related information
UTRAN MOBILITY INFORMATION message to the UE. ate the related fields according to the values of the IEs carried in themessage. onse message to the SRNC. n conducting the operations specified by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MOBILITY INFORMATIO
duct the operations specified by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MOBILITY INFORMATIONFAILU e failure cause.
s.When measurement conditions are
eporting criterias are met, the UE reports
aps) in the transmission during which
ype, relocation cause, source PLMN,
MAND message when the preparation is rget RNC or the target network system.
essage "Prepare
onditon of the GSM e GSM se"
lude information from one or
own in the figure is for
the actual condition of the
source
own in the figure is for
the actual condition of the
source
nnection
cause for the release of the signaling
this particular connection.
E.
he radio links specified by the message.
eld in the message indicates the failure
SI of the UE, CN domain indicator, target
ns the radio resources and other yer and physical layer information,chosen
C sends a RELOCATION
ns the radio resources and other yer and physical layer information,chosen
C sends a RELOCATION
C-controlled NodeB for a UE
necessary resources and configures the
QUEST message and sends a RADIO
ause.
CRNC that the uplink synchronization of
network so that the network can perform
sage contains the information about UE
h the downlink DCCH using AM or
y protection algorithm for a UE. The
nd integrity protection configurations for
orithms, the UE sends a SECURITYMODE
ch of the two IEs has inconsistent ell as the failure cause.
ifier (U-RNTI) or Cell Radio Network information
RAN MOBILITY INFORMATION
BILITY INFORMATIONFAILURE
information
RAN MOBILITY INFORMATION
BILITY INFORMATIONFAILURE
Click to return to main page RRC:Measurement Control
value=Inter-freq me
value=Inter-freq me
value=Event2D ( Sta
value= InterFreqCS value= 0 value=2 dB ,Step: value=320ms
value=Event2f ( Sto
value= 0 value=2 dB ,Step: value=320ms
RRC:Measurement Report (e2d)
RRC:Measurement Report (e2f)
value=UE trigger Ev
RRC:Physical Channel Reconfiguration (DCCH)
value=Compressed
RRC: Physical Channel Reconfiguration Complete (DCCH)
RRC:Measurement Control
value=InterRAT cell
value=InterRAT cell
value=InterRATCIO value=NCC=6 value=BCC=4
value=GSM900 ( GS value=BCCH=64
value=UE measure
value=InterRATFilte
value=UE need to v
value=InterRATPeri
value=UE report 6 In
RRC:Measurement Report
value=RSSI= -110 +
RRC: Handover from UTRAN Command
Handover Completed
>>"Measurement Control and Measurement Report"
value=interFrequencyMeasurement (RNC send mearuement control of InterFrequency because parameter CoexistMeasThdChoice="COEXIST_MEAS_THD_CHOICE_INTERFREQ")
value=Inter-freq meas L3 filter coeff=3
value=Inter-freq meas based on CPICH Ec/No
value=Event2D ( Start Compressed Mode) value= InterFreqCSThd2DEcN0=-14 dB value= 0 value=2 dB ,Step: 0.5 value=320ms
value=Event2f ( Stop Compressed Mode) value= InterFreqCSThd2FEcN0=-12 dB value= 0 value=2 dB ,Step: 0.5 value=320ms
value=UE trigger Event2D to start Compressed Mode
value=UE trigger Event2f to stop Compressed Mode
value=Compressed Mode Inforamtion
value=interRATMeasurement (RNC send mearuement control of InterRAT after enter Compressed Mode)
value=InterRAT cell list
value=InterRAT cell Index
value=InterRATCIO=0 value=NCC=6 value=BCC=4 value=GSM900 ( GSM1800 not used) value=BCCH=64
value=UE measure on GSM RSSI value=InterRATFilterCoef=3 value=UE need to verify BSIC
value=InterRATPeriodReportInterval= 1000ms
value=UE report 6 InterRATcells to RNC
value=RSSI= -110 + hex2dec(1E) = -80 dBm
value=BSIC=35 ( BCCH=112) refer to InterRAT CellID=7 in Measurement Control (GSM900)
ol of InterFrequency because CE_INTERFREQ")
terRAT after enter Compressed Mode)
ement Control (GSM900)
Click to return to main page
L3 UE
BSS
S-RNC
The procedure in ( "RRC: Handover from UTR 1.RRC:Cell Change Order from UTRAN 2.Routing Area Update Request UE Connected
4.SRNS Context Reques
4.SRNS Context Respons
6.S
UE Connected
8.SRNS Data Forward Comm 8.Forward Packets
UE Connected
13.Iu Release Command
13. Iu Release Complete
19.Routing Area Update Accept 20.Routing Area Update Complete
22. BSS Packet Flow Context Procedure
Note: the following information about the procedure ,
1.When the PS data volume is low, the UE may be in CELL_PCH, URA_PCH, or Cell_FACH state or when UE in information, the UE can initiate cell reselection to perform a handover to GSM. The cell reselection is initiated with SGSN to SRNC.
When the UE in Idle ,URA_PCH.Cell_PCH or Cell_FACH states, the cell reselection procedure does not include th
2.After cell reselection to a GSM cell, the NodeB sends a RADIO LINK FAILURE INDICATION message because cell.This message, however, is unnecessary to the procedure of inter-RAT PS handover from WCDMA to GSM. 3. After the UE accesses a GSM cell, the SGSN directly sends an IU RELEASE COMMAND message to the SRN to be transferred. 4.The SRNS context transfer is unnecessary to the procedure of inter-RAT PS handover from WCDMA to GSM.
Click to return to main page
L3 UE
BSC
S-RNC
1. Inter-RAT Handover Decision
2.Routing Area Update Request
5.Security Functions
16.Routing Area Update Accept
17.Routing Area Update Complete
19.Service Request 20. RAB Assignement Request Setup Radio Resources 20. RAB Assignement Response
L3 Messages - Inter-RAT Handover Procedure SGSN2G
SGSN3G
MSC2G
GGSN
Inter-RAT PS Handover from WCDMA to GSM
The procedure in this stage is simiilar to Inter-RAT CS Handover from WCDMA to GSM RRC: Handover from UTRAN Command " message is equivalent to "RRC:Cell Change Order from UTRAN" )
3.SGSN Context Request 4.SRNS Context Request 4.SRNS Context Response 5.SGSN Context Response 6.Security Functions 7.SGSN Context Acknowledge
C1
8.SRNS Data Forward Command 8.Forward Packets 9. Forward Packets 10. Update PDP Context Request 10. Update PDP Context Response 11. Update GPRS Location 12. Cancel Location 13.Iu Release Command 13. Iu Release Complete 12. Cancel Location Acknowledge
14. Insert Subscriber Data 14. Insert Subscriber Data Acknowledge 15. Update GPRS Location Acknowledge 16. Location Update Request 18 Location Update Accept
21. TMSI Reallocation Complete
_FACH state or when UE in Idle state. Based on the parameters in the system ell reselection is initiated with an SRNS CONTEXT REQUEST message sent from the
procedure does not include the sub-procedires which marked with "UE Connected)
ICATION message because the UE stops the transmission towards the WCDMA ver from WCDMA to GSM. MAND message to the SRNC, if the Packet Data Protocol (PDP) context does not need
ver from WCDMA to GSM.
L3 Messages - Inter-RAT Handover Procedure SGSN3G
SGSN2G
GGSN
Inter-RAT PS Handover from GSM to WCDMA
MSC3G
3.SGSN Context Request 4.SGSN Context Response 5.Security Functions 6.SGSN Context Acknowledge
C1 7. Forward Packets 8. Update PDP Context Request 8 Update PDP Context Response 9. Update GPRS Location 10. Cancel Location 10. Cancel Location Acknowledge 11. Insert Subscriber Data 11. Insert Subscriber Data Acknowledge 12. Update GPRS Location Acknowledge 13. Location Update Request
15 Location Update Accept
C2
C3
18. TMSI Reallocation Complete
>>Inter-RAT HO Algorithm
HLR
MSC3G
om UTRAN" )
SRNS Context Transfer
Cancel Location
l Location Acknowledge
Iu release
dge
edge
17. Update Location
>>Inter-RAT HO Algorithm
HLR
MSC2G
Cancel Location
l Location Acknowledge
dge
edge
14a. Update Location 14b.Cancel Location 14c. Cancel Location Ack 14d. Insert Subscriber Data 14e. Insert Subscriber Data Ack 14f. Update Location Ack
>>Inter-RAT HO Algorithm and related parameters
RNS Context Transfer
The Inter-RAT PS handover from WCDMA to GSM procedure is described as follows:
1.The UE in Cell_DCH state, the UTRAN decides to initiate an inter-RAT handover in the PS domai and stop the data transmission between the UE and the network
2. The UE sends a "Routing Area Update Request" message to the 2G SGSN. The update type in t attach. The BSS adds the CGI including the RAC and LAC of the cell to the received message befo
3. The new 2G SGSN sends an "SGSN Context Request" message to the old 3G SGSN to obtain t TMSI Signature is valid, the old 3G SGSN starts a timer. Otherwise, the old 3G SGSN respons with
4. If the UE stay in connected mode before handover, the old 3G SGSN sends an "SRNS Context R PDUs to the UE, and send an "SRNS Context Response" message to the old 3G SGSN 5. The old 3G SGSN sends an "SGSN Context Response" message to the 2G SGSN including the 6. The security functions can be excuted 7. The new 2G SGSN sends an 'SGSN Context Acknowledge" message to the old 3G SGSN. This ready to receive PDUs belonging to the activated PDP contexts
8. The old 3G SGSN sends a "Data Forward Command" message to the SRNS. The SRNS starts a the old 3G SGSN
9. The old 3G SGSN tunnels the GTP PDUs to the new 2G SGSN. In the PDUs, the sequence num
10. the new 2G SGSN sends an "Update PDP Context Request" message to each related GGSN. E message after updating it's PDP Context fields
11. The new 2G SGSN sends an "Update GPRS Location" message ,requesting the HLR to modify 12. The HLR sends a "Cancel Location" message to the old 3G SGSN. the old 3G SGSN responds timer expires,the old 3G SGSN removes the MM and PDP contexts.
13. The old 3G SGSN sends an "Iu release command" message to the SRNS. After data-forwardin Release complete"
14. The HLR sends an "Insert Subscriber Data" message to the new 2G SGSN. The 2G SGSN con returen an "Insert Subscriber Data Ack" message to the HLR
15.The HLR sends an "Update GPRS Location ACK" message to the new 2G SGSN 16. If the association has to be established, the new 2G SGSN sens a 'Location Update Request" m number for creating or updating the association
17. If the subscriber data in VLR is marked as not confirmed by the HLR. the new VLR informs the subscriber data in the new VLR - The new VLR sends an "Update Location" message to the HLR - The HLR cancels the data in the old VLR by sending a "Cancel Location" message to the old VLR - The old VLR acknowledge the message by responding with a "Cancel Location ACK" message - The HLR sends an "Insert Subscriber Data" message to the new VLR - The new VLR acknowledge the message by responding with an "Insert Subscriber Data ACK" me
16. If the association has to be established, the new 2G SGSN sens a 'Location Update Request" m number for creating or updating the association
17. If the subscriber data in VLR is marked as not confirmed by the HLR. the new VLR informs the subscriber data in the new VLR - The new VLR sends an "Update Location" message to the HLR - The HLR cancels the data in the old VLR by sending a "Cancel Location" message to the old VLR - The old VLR acknowledge the message by responding with a "Cancel Location ACK" message - The HLR sends an "Insert Subscriber Data" message to the new VLR - The new VLR acknowledge the message by responding with an "Insert Subscriber Data ACK" me - The HLR responds with an "Update Location Ack" message to the new VLR
18. The new VLR allocates a new TMSI and responds with a "Location Update Accept" message to 19. The new 2G SGSN checks the presence of the MS in the new RA. If all checks area successful established between the new 2G SGSN and the UE. The 2G SGSN responds to the UE with a "Ro
20. The UE acknowledge the new P-TMSI by returning a "Routing Area Update Complete" messag 21. The new 2G SGSN sends a "TMSI Reallocation Complete" message to the new VLR if the UE c 22. The 2G SGSN and the BSS perform the "BSS Packet Flow Context" procedure
>>Inter-RAT HO Algorithm and related parameters
The Inter-RAT PS handover from GSM to WCDMA procedure is described as follows:
1.The GSM decides to perform an inter-RAT handover in PS domanin and stops the data transmiss
2. The UE sends a "Routing Area Update Request" message to the 3G SGSN. The update type in t update with IMSI attach. The SRNC adds the the RAC and LAC of the cell to the received message
3. The new 3G SGSN obtain the address of the old 2G SGSN, and then sends an 'SGSN Context R the UE. The old 2G SGSN validates the old P-TMSI signature. If the old P-TMSI Signature is valid, cause.
4. The old 2G SGSN response with an "SGSN Context Response" message to the 3G SGSN includ 5. The security functions can be excuted 6. The new 3G SGSN sends an 'SGSN Context Acknowledge" message to the old 2G SGSN. This belonging to the activated PDP contexts
7. The old 2G SGSN copied and buffers N-PDUs, and then sends them to the 3G SGSN. Before th and sends them to the 3G SGSN. After the timer expires,the 2G SGSN does not send N-PDUs to t
8.The new 3G SGSN sends an "Update PDP Context Request" message to each related GGSN. E PDP Context fields 9. The new3G SGSN tsends an "Update GPRS Location" message to the HLR
10. The HLR sends a 'Cancel Location" message to the 2G SGSN. After the timer expires,the 2G S Location Ack" message
11.The HLR sens an "Insert Subscriber Data" message to the 3G SGSN. The 3G SGSN constructs
12. The HLR sends "Update GPRS Location" by returning an "Update GPRS Location Ack" messag
13. If the association has to be establilshed, that is . if the Update Type parameter indicates a comb update, the 2G SGSN sends a "Location update request" message to the VLR. The VLR stores the 14. If the subscriber data in VLR is marked as not confirmed by the HLR. the new VLR informs the
- The new VLR sends an "Update Location" message to the HLR - The HLR cancels the data in the old VLR by sending a "Cancel Location" message to the old VLR - The old VLR acknowledge the message by responding with a "Cancel Location ACK" message - The HLR sends an "Insert Subscriber Data" message to the new VLR - The new VLR acknowledge the message by responding with an "Insert Subscriber Data ACK" me - The HLR responds with an "Update Location Ack" message to the new VLR
15. The new VLR allocates a new TMSI and responds with a "Location Update Accept" message to 16. The new 3G SGSN checks the presence of the MS in the new RA. If all checks area successful established between the new 3G SGSN and the UE. The 3G SGSN responds to the UE with a "Ro
17. The UE sends a "Routing Area Update Complete" message to confirm the allocated P-TMSI 18. The new 3G SGSN sends a "TMSI Reallocation Complete" message to the new VLR if the UE c 19. If the UE has uplink data or signalling to send, the UE sends a "Service Request" message to th
20. The 3G SGSN sends a "RAB Assignment Request" message to the SRNS. The SRNS sens a ' Setup Complete" message. The SRNS sends a 'RAB assignment Response" message to the SGS
established between the new 3G SGSN and the UE. The 3G SGSN responds to the UE with a "Ro
17. The UE sends a "Routing Area Update Complete" message to confirm the allocated P-TMSI 18. The new 3G SGSN sends a "TMSI Reallocation Complete" message to the new VLR if the UE c 19. If the UE has uplink data or signalling to send, the UE sends a "Service Request" message to th
20. The 3G SGSN sends a "RAB Assignment Request" message to the SRNS. The SRNS sens a ' Setup Complete" message. The SRNS sends a 'RAB assignment Response" message to the SGS
dure is described as follows:
r-RAT handover in the PS domain be sending "Cell Change Order from UTRAN' messge to UE to handover to a new GSM cell
e 2G SGSN. The update type in the message indicates RA update, combined RA/LA update, or combined RA/LA update with IMSI ell to the received message before forwarding the message to a new 2G SGSN
e to the old 3G SGSN to obtain the MM and PDP contexts. The old 3G SGSN validates the old P-TMSI signature. If the old Pe, the old 3G SGSN respons with an error cause.
GSN sends an "SRNS Context Request" message. After receiving this message, the SRNS buffers the PDUs, stops sending the e to the old 3G SGSN
ge to the 2G SGSN including the MM and PDP context
ssage to the old 3G SGSN. This inform the old 3G SGSN that the new 2G SGSN is
to the SRNS. The SRNS starts a data-forwarding timer and sends the buffers PDUs to
In the PDUs, the sequence number in the GTP hearder remain unchange
essage to each related GGSN. Each GGSN sends an "Update PDP Context Response"
ge ,requesting the HLR to modify the SGSN number GSN. the old 3G SGSN responds with a "Cancel Location AcK" message. After the s. the SRNS. After data-forwarding timer expires,the SRNS responds with an "Iu
w 2G SGSN. The 2G SGSN constructs an MM context and PDP context for the UE and
he new 2G SGSN s a 'Location Update Request" message to the VLR. The VLR stores the SGSN
HLR. the new VLR informs the HLP. The HLR cancel the old VLR and inserts
ocation" message to the old VLR ancel Location ACK" message VLR "Insert Subscriber Data ACK" message
s a 'Location Update Request" message to the VLR. The VLR stores the SGSN
HLR. the new VLR informs the HLP. The HLR cancel the old VLR and inserts
ocation" message to the old VLR ancel Location ACK" message VLR "Insert Subscriber Data ACK" message e new VLR
tion Update Accept" message to the 2G SGSN RA. If all checks area successful,the new 2G SGSN constructs the MM and PDP contexts for the MS. A logical link is N responds to the UE with a "Routing Area Update Accept" message
Area Update Complete" message, including all PDUs successfully sent to the UE before the routing area update procedure ssage to the new VLR if the UE confirms the VLR TMSI ntext" procedure
dure is described as follows:
nin and stops the data transmission between the UE and the network
e 3G SGSN. The update type in the message indicates RA update, combined RA/LA update, or combined RA/LA the cell to the received message before forwarding the message to a new 3G SGSN
then sends an 'SGSN Context Request" message to the old 2G SGSN to construct the MM and PDP contects for he old P-TMSI Signature is valid, the old 2G SGSN starts a timer. Otherwise, the old 2G SGSN respons with an error
message to the 3G SGSN including the MM and PDP context
ssage to the old 2G SGSN. This inform the old 2G SGSN that the new 3G SGSN is ready to receive PDUs
hem to the 3G SGSN. Before the timer expires ,if there are other N-PDUs from the GGSN,the 2G SGSN compies GSN does not send N-PDUs to the 3G SGSN anymore
essage to each related GGSN. Each GGSN sends an "Update PDP Context Response" message after updating it's
e to the HLR After the timer expires,the 2G SGSN removes the MM and PDP contexts. The 2G SGSN response with a 'Cancel
SGSN. The 3G SGSN constructs an MM context and sends an "Insert Subscriber Data Ack" message to the HLR
ate GPRS Location Ack" message to the 3G SGSN
Type parameter indicates a combined RA/LA update with IMSI attach requested, or if the LA changed with the RA e to the VLR. The VLR stores the SGSN number for creating or updating the association HLR. the new VLR informs the HLP. The HLR cancel the old VLR and inserts subscriber data in the new VLR
ocation" message to the old VLR ancel Location ACK" message VLR "Insert Subscriber Data ACK" message e new VLR
tion Update Accept" message to the 3G SGSN RA. If all checks area successful,the new 3G SGSN constructs the MM and PDP contexts for the MS. A logical link is N responds to the UE with a "Routing Area Update Accept" message
confirm the allocated P-TMSI ssage to the new VLR if the UE confirms the VLR TMSI "Service Request" message to the SGSN. The service type indicates the required service
o the SRNS. The SRNS sens a 'Radion Beare Setup Request" message to the UE. The UE responds with a 'Radio Bearer Response" message to the SGSN. The SRNS sends N-PCDS to the UE
N responds to the UE with a "Routing Area Update Accept" message
confirm the allocated P-TMSI ssage to the new VLR if the UE confirms the VLR TMSI "Service Request" message to the SGSN. The service type indicates the required service
o the SRNS. The SRNS sens a 'Radion Beare Setup Request" message to the UE. The UE responds with a 'Radio Bearer Response" message to the SGSN. The SRNS sends N-PCDS to the UE
er to a new GSM cell
RA/LA update with IMSI
gnature. If the old P-
DUs, stops sending the
gical link is
update procedure
RA/LA
tects for th an error
s
compies
dating it's
a 'Cancel
he HLR
the RA
VLR
gical link is
a 'Radio Bearer
a 'Radio Bearer
Click to return to main page
L3 Messages - Inter-RAT Handover Procedure UE
2G/3G SGSN
BSS
Inter-RAT CS&PS Handover from WCDMA to GSM (Intra-SGS 1. Inter-RAT Handover 2.Suspend 3.Suspend
3. Suspend Ack 4. Resume 4. Resume NAck 5.Channel Release 6. Routing Area Update Request
Click to return to main page
L3 Messages - Inter-RAT Handover Procedure UE
2G SGSN
BSS
Inter-RAT CS&PS Handover from WCDMA to GSM (Inter-SGS 1. Inter-RAT Handover 2.Suspend 3.Suspend
Measurement Control & Measurement Report
3. Suspend Ack 4. Resume 4. Resume NAck 5.Channel Release 6. Routing Area Update Request
>>Inter-RAT HO Algorithm and related param
er-RAT Handover Procedure SRNS
MSC /VL
er from WCDMA to GSM (Intra-SGSN)
For a UE in Cell_DCH state u from the UTRAN. The UE pe message to the GSM/BSS, th on the GSM side, the inter-RA
if the inter-RAT handover from inititates a TBF towards the G connection in the original stat
nter-RAT Handover
The signalling procedures are 1. The UE in connection with 3. SRNS Context Request
2. The UE sends a suspend m
3. SRNS Context Response
3. The BSS forwards the 'Sus downlink PDUs. After receivin returns a "Suspend Ack" mes
4. When the CS connection i changed. Therefore,the SGS
5. The BSS sens an RR mes
6. The UE sends a 'Routing A use.
>>Inter-RAT HO Algorithm and related param
er-RAT Handover Procedure SRNS
3G SGSN
er from WCDMA to GSM (Inter-SGSN)
nter-RAT Handover
MSC /VL
For a UE in Cell_DCH state u from the UTRAN. The UE pe message to the GSM/BSS, th on the GSM side, the inter-RA
if the inter-RAT handover from inititates a TBF towards the G connection in the original stat
The signalling procedures are 1. The UE in connection with
Measurement Control & Measurement Report
Measurement Control & Measurement Report
2. The UE sends a suspend m
3. The BSS forwards the 'Sus
4. When the CS connection i changed. Therefore,the SGS
The signalling procedures are 1. The UE in connection with
2. The UE sends a suspend m
3. The BSS forwards the 'Sus
4. When the CS connection i changed. Therefore,the SGS
5. The BSS sens an RR mes
6. The UE sends a 'Routing A use.
Measurement Control & Measurement Report
RadioLink Setup Iub user plane Setup
Iub Radio Link Restore Indication
Measurement Control & Measurement Report
Algorithm and related parameters
For a UE in Cell_DCH state using both CS and PS domain services,the inter-RAT handover procedure is based on the measurement repor from the UTRAN. The UE performs the inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode first. After the UE message to the GSM/BSS, the UE initiates a temporary block flow (TBF) towards the GPRS to suspend the GPRS services. After the CS do on the GSM side, the inter-RAT handover in the PS domain resumes, which indicates that the handover is completed.
if the inter-RAT handover from UTRA RCC Conencted Mode to GSM Connected Mode succeeds,the handover is regards as successful.no inititates a TBF towards the GPRS or not. In case of inter-RAT handover failure, the UE may go back to the UTRA RRC Connected Mode a connection in the original state.
The signalling procedures are described as follows, 1. The UE in connection with both CS and PS domain perrforms the UMTS to GSM handover during which the CS service is handed over to 2. The UE sends a suspend message to the BSS
3. The BSS forwards the 'Suspend" message to the SGSN. The SGSN sends a "SRNS Context Request" message to the SRNS, requestin downlink PDUs. After receiving the message, the SRNS buffers downlink PDUs and respons to the SGSN with an 'SRNS Context Respons returns a "Suspend Ack" message to the BSS 4. When the CS connection is terminated , the BSS may send a 'Resume" message to the SGSN. However,resume is impossible since the changed. Therefore,the SGSN acknowledge the resume through a 'Resume NACK"
5. The BSS sens an RR message 'Channel Release" to the UE, indicating that the BSS fails to request the SGSN to resume the GPRS serv 6. The UE sends a 'Routing Area Update Request" message to the SGSN to resume the GPRS service. The update mode depends on the use.
Algorithm and related parameters
For a UE in Cell_DCH state using both CS and PS domain services,the inter-RAT handover procedure is based on the measurement repor from the UTRAN. The UE performs the inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode first. After the UE message to the GSM/BSS, the UE initiates a temporary block flow (TBF) towards the GPRS to suspend the GPRS services. After the CS do on the GSM side, the inter-RAT handover in the PS domain resumes, which indicates that the handover is completed.
if the inter-RAT handover from UTRA RCC Conencted Mode to GSM Connected Mode succeeds,the handover is regards as successful.no inititates a TBF towards the GPRS or not. In case of inter-RAT handover failure, the UE may go back to the UTRA RRC Connected Mode a connection in the original state.
The signalling procedures are described as follows, 1. The UE in connection with both CS and PS domain perrforms the UMTS to GSM handover during which the CS service is handed over to 2. The UE sends a suspend message to the BSS 3. The BSS forwards the 'Suspend" message to the SGSN. The SGSN returns a "Suspend Ack" message to the BSS 4. When the CS connection is terminated , the BSS may send a 'Resume" message to the SGSN. However,resume is impossible since the changed. Therefore,the SGSN acknowledge the resume through a 'Resume NACK"
The signalling procedures are described as follows, 1. The UE in connection with both CS and PS domain perrforms the UMTS to GSM handover during which the CS service is handed over to 2. The UE sends a suspend message to the BSS 3. The BSS forwards the 'Suspend" message to the SGSN. The SGSN returns a "Suspend Ack" message to the BSS 4. When the CS connection is terminated , the BSS may send a 'Resume" message to the SGSN. However,resume is impossible since the changed. Therefore,the SGSN acknowledge the resume through a 'Resume NACK"
5. The BSS sens an RR message 'Channel Release" to the UE, indicating that the BSS fails to request the SGSN to resume the GPRS serv 6. The UE sends a 'Routing Area Update Request" message to the SGSN to resume the GPRS service. The update mode depends on the use.
ed on the measurement reports from the UE but is initiated ected Mode first. After the UE sends a handover complete PRS services. After the CS domain services are released mpleted.
er is regards as successful.no matter whether the UE TRA RRC Connected Mode and re-establish the
e CS service is handed over to the GSM
ssage to the SRNS, requesting the SRNS to stop sending h an 'SRNS Context Response" messge. The SGSN
esume is impossible since the radio access system has
GSN to resume the GPRS service for the UE
update mode depends on the network operation mode in
ed on the measurement reports from the UE but is initiated ected Mode first. After the UE sends a handover complete PRS services. After the CS domain services are released mpleted.
er is regards as successful.no matter whether the UE TRA RRC Connected Mode and re-establish the
e CS service is handed over to the GSM
he BSS
esume is impossible since the radio access system has
e CS service is handed over to the GSM
he BSS
esume is impossible since the radio access system has
GSN to resume the GPRS service for the UE
update mode depends on the network operation mode in
Click to return to main page
L3 Messages - Intra-Frequency Hard Handover Proc UE
SRNC
DRNC
SRNS Static Relocation (UE not-involved relocation)
1.RANAP: Relocation Required
4.RANAP: Relocation Comman
5. RNSAP: Relocation Commit
7. RRC:UTRAN Mobility Information 8. RRC:UTRAN Mobility Information Confirm 9. RRC:UE Capability Enquiry (DCCH) 10. RRC:UE Capability Information (DCCH) 11. RRC:UE Capability Information Confirm (DCCH)
13. RANAP: Iu Release Comman
14. RANAP: Iu Release Comple
Click to return to main page
L3 Messages - Intra-Frequency Hard Handover Proc UE
SRNC
DRNC
SRNS Relocation with Cell/URA Update (UE not-involved relo 1. Cell Update/URA Update 2. RNSAP: Signalling Transfer Indication
3RANAP: Relocation Required Cell Update/U RA Update
6.RANAP: Relocation Comman
7. RNSAP: Relocation Commit
9. RRC:Cell Update Confirm/URA Update Confirm 10. RRC:Physical Channel Reconfiguration Complete/UTRAN Mobility Information Confirm 11. RRC:UE Capability Enquiry (DCCH) 12. RRC:UE Capability Information (DCCH) 13. RRC:UE Capability Information Confirm (DCCH)
15. RANAP: Iu Release Comman
16. RANAP: Iu Release Comple
Note the following information about the procedure : 1.The DRNC acquires the SRNC ID of the UE from the URNTI IE in the CELL UPDATEmessage and the SIGNALLING TRANSFER INDICATION messageto the SRNC to indicate that the UE requests a cell upd
2.To initiate a cell update, the UE sends a CELL UPDATE message to the DRNC. To initiate a URA upda UPDATE message to the DRNC. 3.After a successful cell update, the DRNC sends a CELL UPDATE CONFIRM message tothe UE. After the DRNC sends a URA UPDATE CONFIRM message to the UE.
4.After receiving the CELL UPDATE CONFIRM or URA UPDATE CONFIRM messagefrom the DRNC, th PHYSICAL CHANNEL RECONFIGURATION COMPLETE message (for the cell update) or a UTRAN MO CONFIRM message (for the URA update) to the DRNC. This response from the UE is optional.
Click to return to main page
L3 Messages - Intra-Frequency Hard Handover Proc UE
SRNC
DRNC
SRNS Relocation with Hard Handover(UE involved relocat
1.RANAP: Relocation Required
4.RANAP: Relocation Comman
5.RANAP: Forward SRNS Conte
PhysicalC hannel Reconfig
7.RRC:Physical Channel Reconfiguration
9. RRC:Physical Channel Reconfiguration Complete 9. RRC:UE Capability Enquiry (DCCH) 10. RRC:UE Capability Information (DCCH) 11. RRC:UE Capability Information Confirm (DCCH)
13. RANAP: Iu Release Comman
14. RANAP: Iu Release Comple
Note the following information about the procedure : 1.During the relocation with hard handover, if an RAB supporting lossless SRNS relocation is avai SRNC sends the GTP-U and PDCP sequence numbers to the DRNC through the FORWARD SR sequence numbers are required for data forwarding.
2.After receiving a RADIO LINK RESTORE INDICATION message from the NodeB, theDRNC se message to the CN.
3.If the DRNC does not obtain the information about the UE capability, the DRNC initiatesa UE ca
>>SRNC Relocation Algorithm and related parameters
ard Handover Procedure DRNC
The relocation prepara ->During an SRNS reloc ->During an inter-RAT C
CN
-involved relocation)
ANAP: Relocation Required 2.RANAP Relocation Request 3.RANAP Relocation Request Ack
Relocation Preparation Relocation Resource Allocation
The procedure is desc 1.The SRNC sends a R cause, source PLMN, s 2.The CN interacts with 3.The CN sends a respo RELOCATION COMMA relevant resources alloc to be allocated, the CN
ANAP: Relocation Command
The relocation resourc ->During an SRNS reloc ->During an inter-RAT C 6. RANAP:Relocation Detect
UTRAN mobility information Relocation Commit
UE capability enquiry
The procedure is desc 1.The CN sends a RELO indicator, target celliden 2.The target RNC alloca 3.The target RNC sends message. The message Identifier (U-RNTI), RAB partially or totally fail to b some reason, the target
12. Relocation Complete
The relocation commit
RANAP: Iu Release Command
RANAP: Iu Release Complete
Iu release
The procedure is desc 1.The SRNC sends a R RELOCATION COMMIT 2.The DRNC sends a R 3.The original DRNC se
The UTRAN mobility in Network TemporaryIden
The procedure is desc 1.The SRNC sends a U 2.The UE starts to upda 3.The UE sends a respo
->If the UE succeeds in INFORMATIONCONFIR ->If the UE fails to cond
The procedure is desc 1.The SRNC sends a U 2.The UE starts to upda 3.The UE sends a respo
->If the UE succeeds in INFORMATIONCONFIR ->If the UE fails to cond INFORMATIONFAILUR
The UE capability enqu can perform dataconfigu
The procedure is desc 1.The SRNC sends a U 2.The UE sends a UE C information about UE ca 3.The SRNC reads the U AM or UMRLC.
The Iu release procedu ->The transaction betwe ->The UTRAN requests ->The Serving Radio Ne ->The SRNS relocation
The procedure is desc 1.The CN sends an IU R signaling connection.NO particular connection.
2.The SRNC releases th
ard Handover Procedure DRNC
(UE not-involved relocation)
Click to return to main page
CN
The relocation prepara ->During an SRNS reloc ->During an inter-RAT C
The procedure is desc 1.The SRNC sends a R PLMN, source LAC,sou 2.The CN interacts with 3.The CN sends a respo RELOCATION COMMA relevant resources alloc RELOCATIONPREPAR
PLMN, source LAC,sou 2.The CN interacts with 3.The CN sends a respo RELOCATION COMMA relevant resources alloc RELOCATIONPREPAR
ANAP: Relocation Required 4.RANAP Relocation Request 5.RANAP Relocation Request Ack
Relocation Preparation Relocation Resource Allocation
ANAP: Relocation Command
The relocation resourc ->During an SRNS reloc ->During an inter-RAT C
The procedure is desc 1.The CN sends a RELO indicator, target celliden 2.The target RNC alloca 3.The target RNC sends message. The message include the UTRAN Rad , and chosen integrity pr some reason, the targe
8. RANAP:Relocation Detect
Relocation Commit
The cell update proced procedure takes the role
UE capability enquiry
The cell update procedu failure,Paging response
14. Relocation Complete
RANAP: Iu Release Command
RANAP: Iu Release Complete
L UPDATEmessage and then sends an UPLINK at the UE requests a cell update.
Iu release
The procedure is desc 1.The UE sends a CELL RNTI) andthe SRNC ID. 2.The RNC sends a CE channels, physicalchann 3.According to related IE messages: ->UTRAN MOBILITY IN ->PHYSICAL CHANNEL ->TRANSPORT CHANN ->RADIO BEARER REC ->RADIO BEARER REL
RNC. To initiate a URA update, the UE sends a URA
M message tothe UE. After a successful URA update,
messagefrom the DRNC, the UE can send a cell update) or a UTRAN MOBILITY INFORMATION the UE is optional.
The URA update proce update procedure can b
The procedure is desc 1.The UE sends a URA U-RNTI. 2.The RNC sends a UR ciphering and integritypr 3.The UE responds opti parameters intoeffect.
1.The UE sends a URA U-RNTI. 2.The RNC sends a UR ciphering and integritypr 3.The UE responds opti parameters intoeffect.
The relocation commit
The procedure is desc 1.The SRNC sends a R RELOCATION COMMIT 2.The DRNC sends a R 3.The original DRNC se
The UTRAN mobility in Network TemporaryIden
The procedure is desc 1.The SRNC sends a U 2.The UE starts to upda 3.The UE sends a respo
->If the UE succeeds in INFORMATIONCONFIR ->If the UE fails to cond INFORMATIONFAILUR
The UE capability enqu can perform dataconfigu
The procedure is desc 1.The SRNC sends a U 2.The UE sends a UE C information about UE ca 3.The SRNC reads the U AM or UMRLC.
The Iu release procedu ->The transaction betwe ->The UTRAN requests ->The Serving Radio Ne ->The SRNS relocation
The procedure is desc 1.The CN sends an IU R signaling connection.NO particular connection.
->The UTRAN requests ->The Serving Radio Ne ->The SRNS relocation
The procedure is desc 1.The CN sends an IU R signaling connection.NO particular connection.
2.The SRNC releases th
ard Handover Procedure DRNC
Click to return to main page
CN
The relocation prepara ->During an SRNS reloc ->During an inter-RAT C
er(UE involved relocation)
ANAP: Relocation Required 2.RANAP: Relocation Request 3.RANAP: Relocation Request Ack
Relocation Preparation Relocation Resource Allocation
The procedure is desc 1.The SRNC sends a R PLMN, source LAC,sou 2.The CN interacts with 3.The CN sends a respo RELOCATION COMMA relevant resources alloc RELOCATIONPREPAR
ANAP: Relocation Command
The relocation resourc ->During an SRNS reloc ->During an inter-RAT C
NAP: Forward SRNS Context 6.RANAP: Forward SRNS Context
8. RANAP:Relocation Detect Relocation Commit
The procedure is desc 1.The CN sends a RELO CN domain indicator, ta 2.The target RNC alloca 3.The target RNC sends REQUESTACKNOWLE include the UTRAN Rad and chosen integrity pro some reason, the target
UE capability enquiry
12. Relocation Complete
The relocation commit
RANAP: Iu Release Command
RANAP: Iu Release Complete
Iu release
The procedure is desc 1.When an RAB suppor message to the SGSN t forwarding. 2.After receiving the FO 3.The UE is handed ove RESTORE INDICATION 4.The original DRNC se
ess SRNS relocation is available on the Iu-PS interface, the through the FORWARD SRNS CONTEXT message. The
message to the SGSN t forwarding. 2.After receiving the FO 3.The UE is handed ove RESTORE INDICATION 4.The original DRNC se
m the NodeB, theDRNC sends a RELOCATION DETECT
The physical channel r the DRNC initiatesa UE capability enquiry procedure.
The procedure is desc 1.The SRNC sends a PH 2.The UE saves the IEs 3.The UE sends a respo ->If successfully reconfi CHANNELRE CONFIGU ->If failing to reconfigure old physicalchannel con the Failure causeIE con
The UE capability enqu can perform dataconfigu
The procedure is desc 1.The SRNC sends a U 2.The UE sends a UE C information about UE ca 3.The SRNC reads the U AM or UMRLC.
The Iu release procedu ->The transaction betwe ->The UTRAN requests ->The Serving Radio Ne ->The SRNS relocation
The procedure is desc 1.The CN sends an IU R signaling connection.NO particular connection.
2.The SRNC releases th
nd related parameters
The relocation preparation procedure can be triggered in either of the following conditions: ->During an SRNS relocation, the SRNC sends a RELOCATION REQUIRED message. ->During an inter-RAT CS handover from WCDMA to GSM, the SRNC sends aRELOCATION REQUIRED message.
The procedure is described as follows: 1.The SRNC sends a RELOCATION REQUIRED message to the CN. The message containscertain information such as relocation cause, source PLMN, source LAC,source SAC, target PLMN, and target LAC 2.The CN interacts with the target RNC or the target network system, such as the GSMsystem, to prepare relevant resources. 3.The CN sends a response message to the SRNC.lIf the target RNC or the target network system prepares the relevant resources RELOCATION COMMAND message when thepreparation is complete. The message contains the L3 information IE, which carries relevant resources allocated by the target RNC or the targetnetwork system.lIf the resources partially or totally fail to be allocated, the CN sends a RELOCATIONPREPARATION FAILURE message.
The relocation resource allocation procedure can be triggered in either of the following conditions: ->During an SRNS relocation, the CN applies for resources from the target RNC ->During an inter-RAT CS handover from GSM to WCDMA, the CN applies for resourcesfrom the target RNC
The procedure is described as follows: 1.The CN sends a RELOCATION REQUEST message to the target RNC. The messagecontains certain information, such as the IM indicator, target cellidentifier, encryption, integrity protection, Iu signaling connection ID, handover cause, and RAB parameters. 2.The target RNC allocates radio resources for the relocation. 3.The target RNC sends a response message to the CN.lIf the resources are allocated, the target RNC sends a RELOCATION REQ message. The message contains the radio resources and otherparameters allocated to the UE. The parameters include the UTRAN Identifier (U-RNTI), RAB, transport layer and physical layer information,chosen encryption algorithm, and chosen integrity protection partially or totally fail to be allocated or the target RNC rejects the SRNSrelocation for some reason, the target RNC sends a RELOCATION FAILURE message,indicating the failure cause.
The relocation commit procedure is performed to execute the change of control from the SRNCof a UE to the DRNC
The procedure is described as follows: 1.The SRNC sends a RELOCATION COMMIT message to the DRNC. If an RAB supportinglossless SRNS relocation is available on RELOCATION COMMITmessage carries the GTP-U and PDCP sequence numbers required for data forwarding.Then, the SRNC in 2.The DRNC sends a RELOCATION DETECT message to the CN to notify the CN of thedetection of the relocation commitment. 3.The original DRNC sends a RELOCATION COMPLETE message to the CN to notify thatthe relocation is successful.
The UTRAN mobility information procedure is performed for the network to allocate a newUTRAN Radio Network Temporary Ide Network TemporaryIdentifier (C-RNTI) to a UE or to inform the UE of mobility-related information such as timer values and CN dom The procedure is described as follows: 1.The SRNC sends a UTRAN MOBILITY INFORMATION message to the UE 2.The UE starts to update the related fields according to the values of the IEs carried in themessage. 3.The UE sends a response message to the SRNC.
->If the UE succeeds in conducting the operations specified by the UTRAN MOBILITYI NFORMATION message, the UE sends a U INFORMATIONCONFIRM message. ->If the UE fails to conduct the operations specified by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MO
The procedure is described as follows: 1.The SRNC sends a UTRAN MOBILITY INFORMATION message to the UE 2.The UE starts to update the related fields according to the values of the IEs carried in themessage. 3.The UE sends a response message to the SRNC.
->If the UE succeeds in conducting the operations specified by the UTRAN MOBILITYI NFORMATION message, the UE sends a U INFORMATIONCONFIRM message. ->If the UE fails to conduct the operations specified by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MO INFORMATIONFAILURE message, indicating the failure cause.
The UE capability enquiry procedure is performed to request a UE to transmit its capabilityinformation related to any radio access can perform dataconfiguration based on the UE capability.
The procedure is described as follows: 1.The SRNC sends a UE CAPABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC. 2.The UE sends a UE CAPABILITY INFORMATION message to the SRNC through theuplink DCCH using AM or UM RLC. The me information about UE capabilities. 3.The SRNC reads the UE capability information and then sends a UE CAPABILITYINFORMA CONFIRM message to the UE throu AM or UMRLC.
The Iu release procedure can be triggered in one of the following conditions: ->The transaction between the UE and the CN is complete. ->The UTRAN requests the CN to release the resources on the Iu interface by, for example,sending an IU RELEASE REQUEST me ->The Serving Radio Network Subsystem (SRNS) is relocated. ->The SRNS relocation is canceled after a relocation resource allocation procedure iscomplete.
The procedure is described as follows: 1.The CN sends an IU RELEASE COMMAND message to the SRNC to initiate the Iu releaseprocedure. The message indicates the signaling connection.NOTE After sending the IU RELEASE COMMAND message, the CN will not send further RANAPconnection-o particular connection. 2.The SRNC releases the related UTRAN resources and then sends an IU RELEASE COMPLETE message to the CN.
The relocation preparation procedure can be triggered in either of the following conditions: ->During an SRNS relocation, the SRNC sends a RELOCATION REQUIRED message. ->During an inter-RAT CS handover from WCDMA to GSM, the SRNC sends aRELOCATION REQUIRED message.
The procedure is described as follows: 1.The SRNC sends a RELOCATION REQUIRED message to the CN. The message containscertain information such as relocation PLMN, source LAC,source SAC, target PLMN, and target LAC 2.The CN interacts with the target RNC or the target network system, such as the GSMsystem, to prepare relevant resources. 3.The CN sends a response message to the SRNC.lIf the target RNC or the target network system prepares the relevant resources RELOCATION COMMAND message when thepreparation is complete. The message contains the L3 information IE, which carries relevant resources allocated by the target RNC or the targetnetwork system.lIf the resources partially or totally fail to be allocated, th RELOCATIONPREPARATION FAILURE message.
PLMN, source LAC,source SAC, target PLMN, and target LAC 2.The CN interacts with the target RNC or the target network system, such as the GSMsystem, to prepare relevant resources. 3.The CN sends a response message to the SRNC.lIf the target RNC or the target network system prepares the relevant resources RELOCATION COMMAND message when thepreparation is complete. The message contains the L3 information IE, which carries relevant resources allocated by the target RNC or the targetnetwork system.lIf the resources partially or totally fail to be allocated, th RELOCATIONPREPARATION FAILURE message.
The relocation resource allocation procedure can be triggered in either of the following conditions: ->During an SRNS relocation, the CN applies for resources from the target RNC ->During an inter-RAT CS handover from GSM to WCDMA, the CN applies for resourcesfrom the target RNC
The procedure is described as follows: 1.The CN sends a RELOCATION REQUEST message to the target RNC. The messagecontains certain information, such as the IM indicator, target cellidentifier, encryption, integrity protection, Iu signaling connection ID, handover cause, and RAB parameters. 2.The target RNC allocates radio resources for the relocation. 3.The target RNC sends a response message to the CN.lIf the resources are allocated, the target RNC sends a RELOCATION REQ message. The message contains the radio resources and otherparameters allocated to the UE. The parameters include the UTRAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transport layer and physical layer information,chosen encry , and chosen integrity protection algorithm.lIf the resources partially or totally fail to be allocated or the target RNC rejects the SRNS some reason, the target RNC sends a RELOCATION FAILURE message,indicating the failure cause.
The cell update procedure is performed to update the UE-related information on the UTRANside when the location of a UE change procedure takes the role ofmonitoring the RRC connection, switching the status of the RRC connection, reporting errors,and transfe
The cell update procedure can be triggered in one of the following conditions:Cell reselection,Re-entering the service area,Periodica failure,Paging response,Uplink data transmission and RLC unrecoverable error
The procedure is described as follows : 1.The UE sends a CELL UPDATE message to the RNC. The message contains the information such as the Serving RNC Radio Ne RNTI) andthe SRNC ID. 2.The RNC sends a CELL UPDATE CONFIRM message to the UE. The message containsthe information such as the U-RNTI and channels, physicalchannels, and radio bearers. 3.According to related IEs in the received message, the UE may respond with messages ornot. If the UE responds, the message ca messages: ->UTRAN MOBILITY INFORMATION CONFIRM ->PHYSICAL CHANNEL RECONFIGURATION COMPLETE ->TRANSPORT CHANNEL RECONFIGURATION COMPLETE ->RADIO BEARER RECONFIGURATION COMPLETE ->RADIO BEARER RELEASE COMPLETE
The URA update procedure is performed to update the URA-related location information on thenetwork side when the location of a update procedure can be triggered in either of the following conditions:URA reselection or Periodical URA update
The procedure is described as follows: 1.The UE sends a URA UPDATE message to the RNC to initiate the URA update. The message contains the cause for the URA up U-RNTI. 2.The RNC sends a URA UPDATE CONFIRM message to the UE. The message containsthe new C-RNTI and U-RNTI or the inform ciphering and integrityprotection modes. 3.The UE responds optionally. If there is a response, the UE sends a UTRAN MOBILITY INFORMATION CONFIRM message to the parameters intoeffect.
1.The UE sends a URA UPDATE message to the RNC to initiate the URA update. The message contains the cause for the URA up U-RNTI. 2.The RNC sends a URA UPDATE CONFIRM message to the UE. The message containsthe new C-RNTI and U-RNTI or the inform ciphering and integrityprotection modes. 3.The UE responds optionally. If there is a response, the UE sends a UTRAN MOBILITY INFORMATION CONFIRM message to the parameters intoeffect.
The relocation commit procedure is performed to execute the change of control from the SRNCof a UE to the DRNC
The procedure is described as follows: 1.The SRNC sends a RELOCATION COMMIT message to the DRNC. If an RAB supportinglossless SRNS relocation is available on RELOCATION COMMITmessage carries the GTP-U and PDCP sequence numbers required for data forwarding.Then, the SRNC in 2.The DRNC sends a RELOCATION DETECT message to the CN to notify the CN of thedetection of the relocation commitment. 3.The original DRNC sends a RELOCATION COMPLETE message to the CN to notify thatthe relocation is successful.
The UTRAN mobility information procedure is performed for the network to allocate a newUTRAN Radio Network Temporary Ide Network TemporaryIdentifier (C-RNTI) to a UE or to inform the UE of mobility-related information such as timer values and CN dom The procedure is described as follows: 1.The SRNC sends a UTRAN MOBILITY INFORMATION message to the UE 2.The UE starts to update the related fields according to the values of the IEs carried in themessage. 3.The UE sends a response message to the SRNC.
->If the UE succeeds in conducting the operations specified by the UTRAN MOBILITYI NFORMATION message, the UE sends a U INFORMATIONCONFIRM message. ->If the UE fails to conduct the operations specified by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MO INFORMATIONFAILURE message, indicating the failure cause.
The UE capability enquiry procedure is performed to request a UE to transmit its capabilityinformation related to any radio access can perform dataconfiguration based on the UE capability.
The procedure is described as follows: 1.The SRNC sends a UE CAPABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC. 2.The UE sends a UE CAPABILITY INFORMATION message to the SRNC through theuplink DCCH using AM or UM RLC. The me information about UE capabilities. 3.The SRNC reads the UE capability information and then sends a UE CAPABILITYINFORMA CONFIRM message to the UE throu AM or UMRLC.
The Iu release procedure can be triggered in one of the following conditions: ->The transaction between the UE and the CN is complete. ->The UTRAN requests the CN to release the resources on the Iu interface by, for example,sending an IU RELEASE REQUEST me ->The Serving Radio Network Subsystem (SRNS) is relocated. ->The SRNS relocation is canceled after a relocation resource allocation procedure iscomplete.
The procedure is described as follows: 1.The CN sends an IU RELEASE COMMAND message to the SRNC to initiate the Iu releaseprocedure. The message indicates the signaling connection.NOTE After sending the IU RELEASE COMMAND message, the CN will not send further RANAPconnection-o particular connection.
->The UTRAN requests the CN to release the resources on the Iu interface by, for example,sending an IU RELEASE REQUEST me ->The Serving Radio Network Subsystem (SRNS) is relocated. ->The SRNS relocation is canceled after a relocation resource allocation procedure iscomplete.
The procedure is described as follows: 1.The CN sends an IU RELEASE COMMAND message to the SRNC to initiate the Iu releaseprocedure. The message indicates the signaling connection.NOTE After sending the IU RELEASE COMMAND message, the CN will not send further RANAPconnection-o particular connection. 2.The SRNC releases the related UTRAN resources and then sends an IU RELEASE COMPLETE message to the CN.
The relocation preparation procedure can be triggered in either of the following conditions: ->During an SRNS relocation, the SRNC sends a RELOCATION REQUIRED message. ->During an inter-RAT CS handover from WCDMA to GSM, the SRNC sends aRELOCATION REQUIRED message.
The procedure is described as follows: 1.The SRNC sends a RELOCATION REQUIRED message to the CN. The message containscertain information such as relocation PLMN, source LAC,source SAC, target PLMN, and target LAC 2.The CN interacts with the target RNC or the target network system, such as the GSMsystem, to prepare relevant resources. 3.The CN sends a response message to the SRNC.lIf the target RNC or the target network system prepares the relevant resources RELOCATION COMMAND message when thepreparation is complete. The message contains the L3 information IE, which carries relevant resources allocated by the target RNC or the targetnetwork system.lIf the resources partially or totally fail to be allocated, th RELOCATIONPREPARATION FAILURE message.
The relocation resource allocation procedure can be triggered in either of the following conditions: ->During an SRNS relocation, the CN applies for resources from the target RNC ->During an inter-RAT CS handover from GSM to WCDMA, the CN applies for resourcesfrom the target RNC
The procedure is described as follows: 1.The CN sends a RELOCATION REQUEST message to the target RNC. The messagecontains certain information, such as the IM CN domain indicator, target cellidentifier, encryption, integrity protection, Iu signaling connection ID, handover cause, and RAB para 2.The target RNC allocates radio resources for the relocation. 3.The target RNC sends a response message to the CN.lIf the resources are allocated, the target RNC sends a RELOCATION REQUESTACKNOWLEDGE message. The message contains the radio resources and otherparameters allocated to the UE. The p include the UTRAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transport layer and physical layer information,chosen encry and chosen integrity protection algorithm.lIf the resources partially or totally fail to be allocated or the target RNC rejects the SRNSre some reason, the target RNC sends a RELOCATION FAILURE message,indicating the failure cause.
The relocation commit procedure is performed to execute the change of control from the SRNCof a UE to the DRNC.
The procedure is described as follows : 1.When an RAB supporting lossless SRNS relocation is available on the Iu-PS interface, theSRNC sends a FORWARD SRNS CON message to the SGSN to ask the SGSN totransfer the GTP-U and PDCP sequence numbers to the DRNC. The sequence numbers forwarding. 2.After receiving the FORWARD SRNS CONTEXT message, the SGSN forwards themessage to the DRNC. 3.The UE is handed over from the SRNC to the DRNC through a physical channelreconfiguration procedure. After receiving a RADI RESTORE INDICATIONmessage from the NodeB, the DRNC sends a RELOCATION DETECT message to theCN. 4.The original DRNC sends a RELOCATION COMPLETE message to the CN to notify thatthe relocation is successful.
message to the SGSN to ask the SGSN totransfer the GTP-U and PDCP sequence numbers to the DRNC. The sequence numbers forwarding. 2.After receiving the FORWARD SRNS CONTEXT message, the SGSN forwards themessage to the DRNC. 3.The UE is handed over from the SRNC to the DRNC through a physical channelreconfiguration procedure. After receiving a RADI RESTORE INDICATIONmessage from the NodeB, the DRNC sends a RELOCATION DETECT message to theCN. 4.The original DRNC sends a RELOCATION COMPLETE message to the CN to notify thatthe relocation is successful.
The physical channel reconfiguration procedure is performed to set up, reconfigure, or releasea physical channel.
The procedure is described as follows : 1.The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physical chan 2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel. 3.The UE sends a response message to the SRNC. ->If successfully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION message, the UE CHANNELRE CONFIGURATION COMPLETE message on the uplink DCCH by using AM RLC. ->If failing to reconfigure the physical channels specified by the PHYSICAL CHANNELRECONFIGURATION message, the UE resto old physicalchannel configuration and sends a PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH by us the Failure causeIE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE message is "physical channel failure".
The UE capability enquiry procedure is performed to request a UE to transmit its capabilityinformation related to any radio access can perform dataconfiguration based on the UE capability.
The procedure is described as follows: 1.The SRNC sends a UE CAPABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC. 2.The UE sends a UE CAPABILITY INFORMATION message to the SRNC through theuplink DCCH using AM or UM RLC. The me information about UE capabilities. 3.The SRNC reads the UE capability information and then sends a UE CAPABILITYINFORMA CONFIRM message to the UE throu AM or UMRLC.
The Iu release procedure can be triggered in one of the following conditions: ->The transaction between the UE and the CN is complete. ->The UTRAN requests the CN to release the resources on the Iu interface by, for example,sending an IU RELEASE REQUEST me ->The Serving Radio Network Subsystem (SRNS) is relocated. ->The SRNS relocation is canceled after a relocation resource allocation procedure iscomplete.
The procedure is described as follows: 1.The CN sends an IU RELEASE COMMAND message to the SRNC to initiate the Iu releaseprocedure. The message indicates the signaling connection.NOTE After sending the IU RELEASE COMMAND message, the CN will not send further RANAPconnection-o particular connection. 2.The SRNC releases the related UTRAN resources and then sends an IU RELEASE COMPLETE message to the CN.
RED message.
nformation such as relocation type, relocation
pare relevant resources. epares the relevant resourcessuccessfully, the CN sends a information IE, which carries theinformation about the or totally fail
et RNC
ain information, such as the IMSI of the UE, CN domain se, and RAB parameters.
C sends a RELOCATION REQUESTACKNOWLEDGE arameters include the UTRAN Radio NetworkTemporary nd chosen integrity protection algorithm.lIf the resources
a UE to the DRNC
SRNS relocation is available on the Iu-PS interface, the forwarding.Then, the SRNC initiates data forwarding. the relocation commitment. on is successful.
Radio Network Temporary Identifier (U-RNTI) or Cell Radio as timer values and CN domain–related information.
N message, the UE sends a UTRAN MOBILITY
e, the UE sends a UTRAN MOBILITY
N message, the UE sends a UTRAN MOBILITY
e, the UE sends a UTRAN MOBILITY
on related to any radio access network so that the network
ng AM RLC. using AM or UM RLC. The message contains the
RM message to the UE through the downlink DCCH using
n IU RELEASE REQUEST message.
re. The message indicates the cause for the release of the d further RANAPconnection-oriented messages on this
essage to the CN.
RED message.
nformation such as relocation type, relocation cause, source
pare relevant resources. epares the relevant resourcessuccessfully, the CN sends a information IE, which carries theinformation about the or totally fail to be allocated, the CN sends a
pare relevant resources. epares the relevant resourcessuccessfully, the CN sends a information IE, which carries theinformation about the or totally fail to be allocated, the CN sends a
et RNC
ain information, such as the IMSI of the UE, CN domain se, and RAB parameters.
C sends a RELOCATION REQUESTACKNOWLEDGE arameters ayer information,chosen encryption algorithm target RNC rejects the SRNSrelocation for .
en the location of a UE changes. In addition, the cell update n, reporting errors,and transferring information
ing the service area,Periodical cell updatelRadio link
as the Serving RNC Radio Network Temporary Identifier (S-
ation such as the U-RNTI and the IEs about the transport
UE responds, the message can be one of the following
ork side when the location of a UE changes. The URA URA update
ains the cause for the URA update and the IEs such as the
RNTI and U-RNTI or the information about the new
ON CONFIRM message to the RNC after taking the new
>>Cell Update Description
ains the cause for the URA update and the IEs such as the
RNTI and U-RNTI or the information about the new
ON CONFIRM message to the RNC after taking the new
a UE to the DRNC
SRNS relocation is available on the Iu-PS interface, the forwarding.Then, the SRNC initiates data forwarding. the relocation commitment. on is successful.
Radio Network Temporary Identifier (U-RNTI) or Cell Radio as timer values and CN domain–related information.
N message, the UE sends a UTRAN MOBILITY
e, the UE sends a UTRAN MOBILITY
on related to any radio access network so that the network
ng AM RLC. using AM or UM RLC. The message contains the
RM message to the UE through the downlink DCCH using
n IU RELEASE REQUEST message.
re. The message indicates the cause for the release of the d further RANAPconnection-oriented messages on this
n IU RELEASE REQUEST message.
re. The message indicates the cause for the release of the d further RANAPconnection-oriented messages on this
essage to the CN.
RED message.
nformation such as relocation type, relocation cause, source
pare relevant resources. epares the relevant resourcessuccessfully, the CN sends a information IE, which carries theinformation about the or totally fail to be allocated, the CN sends a
et RNC
ain information, such as the IMSI of the UE, andover cause, and RAB parameters.
C sends a RELOCATION ers allocated to the UE. The parameters ayer information,chosen encryption algorithm, arget RNC rejects the SRNSrelocation for
UE to the DRNC.
nds a FORWARD SRNS CONTEXT RNC. The sequence numbers arerequired for data
DRNC. edure. After receiving a RADIO LINK age to theCN. on is successful.
RNC. The sequence numbers arerequired for data
DRNC. edure. After receiving a RADIO LINK age to theCN. on is successful.
hysical channel.
onfiguration of a physical channel.
GURATION message, the UE sends a PHYSICAL
ATION message, the UE restores the configuration to the E message on the DCCH by using AM RLC. The value of e is "physical channel failure".
on related to any radio access network so that the network
ng AM RLC. using AM or UM RLC. The message contains the
RM message to the UE through the downlink DCCH using
n IU RELEASE REQUEST message.
re. The message indicates the cause for the release of the d further RANAPconnection-oriented messages on this
essage to the CN.
