Professional Documents
Culture Documents
Contact: aumpikav@yahoo.com
1.6 RB Procedures
2. Paging Messages
5.3 PS-R99
5.4 PS-HSDPA
5.5 PS-HSUPA
6. HO Procedure & L3-messages (Intra-Freq HO)
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
Genex Assistant
Tool Version Release Date Genex Probe Version
Version
V100R005C01B040 (V1.51 V100R005C01B040
Ver1.0 25-Jun-09
20090210 ) (V1.52 20090210 )
n schemes
10.0 V200R010C01B061
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
- 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 chipherin
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.
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
transfer to other RNCs are possible via Iur interface and to the connected Node Bs via Iub interface.
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
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 ra
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
- 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 ra
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 Combining
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 implemen
cells are serviced by a Node B in UMTS
It is also essential to address different physical,geographical or logical entities within UMTS. The geographical and physical enti
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
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 a
(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
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
Horizontal Layer:
The general protocol model consists of t
are visible in the Radio Network Layer o
specific requirements.
- Transport Network Layer : The Trans
layer and its transport frame layer,also t
- Radio Network Layer : The Radio Ne
streams, to be transported through UTR
Vertical Plane:
There is also a vertical structure, the ele
next to eachother. The general protocol
Plane.
-User Plane: The user plane supports th
Vertical Layer protocols will be transmitted via data be
explicit signalling.
-Control Plane: The control plane cons
application protocol,one or several signa
signaling,which is UMTS-specific. It inclu
Application Protocol messages.
-Transport Network Control Plane: Th
protocols are used to set up and release
not necessary to use the ALCAP for all d
are used. The Transport Network Contro
information.
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 be
The CS control plane is used for the exchange of control information which are related to CS services. In addition ,the CS control plane is
-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
The CS control plane is used for the exchange of control information which are related to CS services. In addition ,the CS control plane is
-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
-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
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 strea
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.
For Packet Switched (PS) service,there are different procedures. So there is a need for special proctocols for PS services. In fact these sp
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 ess
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 increase
-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. I
-AAL5 /ATM : The UDP/IP datagrams (packets) are transmitted on ATM using the adaptaiton layer 5.
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 c
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 th
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 matchin
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 necc
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
L3 Functions
The RRC performs the functions listed below:
UMTS system has different application parts depending on interface being used and each application part controls signaling information fo
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 traffi
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
-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 traffi
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 D
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 signali
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 t
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, the
the application protocol can control the bearer via abstract parameters (QOS parameters) only. This principle is the same as for BICC (Bea
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 tr
e User Equipment UE.
It is responsible for serving the radio interface. Some of the tasks of the Mobile Equipment ares CDMA coding and
ments,Ciphering and authorization,Mobility management and equipment identification.
erminal equipment. It supports call handling,contains security parameters,user-specific data e.g. telephone directory
pdated e.g. via SMS or cell broadcasting.
on for authentication and chiphering for circuit and packet switched applications,PLMN selector and HPLMN search
c.
es etc.
ain, which is labelled Iu-PS, and to the cs domain, which is called Iu-CS. In both cases, ATM is used as transmission
terface.
ndover situations, where a UE‘s active cells are under the control of more than one RNC. One RNC is responsible for
alling information.
(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 and to the PS dom
ows,
hat is connected with the NodeB serving the cell. The tasks of the C-RNC covers the following areas:
the NodeB).This means the C-RNC of a cell is responsible for all lower layer funcions related to the radio technology
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 higher layer fu
cation/modification or release of radio resources,for Outer Loop Power Control and for Handover decisions/initiation.
oward the CN. It decides to add or remove cells in the Soft Handover. The S-RNC is in most cases (but not always)
y. It can be re-allocated to another RNC with the S-RNS reallocation procedure.
and corresponding RANAP signalling to/from the core network per UE. The S-RNC terminates the RRC signalling
ed 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
ll the UE is connected to, but its not the S-RNC.Therefore D-RNC performs the C-RNC functions for the cells not
eB is a physical unit for implementing a UMTS radio transmission. Depending on the sectoring of the cells ,one (omni) cell or multiple (sector) cells can be s
re serviced by a Node B in UMTS.
e B can be used for Frequency Division Duplex (Uplink and Downlink separated by different frequency bands),Time division Duplex (Uplink and Downli
tion. A Node B converts user and signalling information received from the RNC for transport via the radio interface,and in the opposite direction. Node Bs a
res the signal to noise ratio (SIR) of the User Equipment ,compares the value with a predefined one and instructs the UE to control its transmission power.
th of the links and determines the Frame Error Rate (FER). The following are examples of NodeB functions:
o Channel functions: Transport to physical channel mappings. Encoding/Decoding – Spreading/De-spreading user traffic and signalling.
nterface management. Controlling Uplink and Downlink radio paths on the Uu Air Interface,Baseband to RF conversion,Antenna multi-coupling,
odeB SofterHO,Power Control,Quality and signal strength measurements
Processing,Interfacing with M2000 and RNC for alarm and control (Operations and Maintenance) functions.
lar Transmission management. Managing ATM switching and multiplexing over the Iub interface. Control of AAL2/AAL5 connections. Control
physical transmission interfaces – E1, PDH, SDH or microwave.
rk is possible,is sub-divided into National Service Areas.
C) and Country Code (CC). The National Service Area is sub-divided into one or more PLMN Service Areas.
and Country Code (CC). The National Service Area is sub-divided into one or more MSC and SGSN Service Areas.
SGSN (PS-domain). MSC and SGSN Service Area may differ, but they are on the same hierachical level. The MSCs and
e VLR) of UMTS. A Location Area is world-wide uniquely identified by its Location Area Identity LAI
of a Location Area i.e. one LA may contain one or more RAs. The RA is the most precise UE information, which is
Identity. The RA is sub-divided into the Cell-Areas.
he PLMN (in the RNC). The cell is world-wide uniquely identified by the Cell Global Identity (CGI)
st 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 E212.
ther 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
RA)
h two types of identifiers according to the point of generation of the identifier:
by the core network. In detail there are IMSI,TMSI and P-TMSI (and IMEI)
RNTIs). This means they are allocated to the UE for the time of the need. After the last procedure the identifiers are released.
Country Code,MCC (3 digits) + Mobile Network Code,MNC (2-3 digits)+Mobile Subscriber Identification Number,MSIN. The total length of the IMSI is less
lity. 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. The TMSI consi
the EIR. The IMEI(15 digits) consists of a Type Approval Code TAC (6 digits),the Final Assembly Code FAC(2 digits)which
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
d for the first cell access (at cell change) at existing RRC connection and for UTRAN originating Paging including
ed as an in-band UE identifier in all DCCH/DTCH common channel messages on Uu despite the first access
1. Access Stratum(AS) : The Access Stratum covers all signalling exchange used to control the access of an UE to the network. Access Stra
UTRAN and between UTRAN and CN. The difference between the access stratum UE-
UTRAN and UTRAN-CN is ,that the UTRAN-CN access stratum shall be independent of the radio technology used in UTRAN. This
enables the CN to support several different radio access technologies.
2. Transport Stratum: The Transport Stratum protocols and messages have the task to transport higher layer PDUs (Protocol Data Unit)
and user data. Because UTRAN has the task to transparently transport data between UE and CN,there will be transport stratum
messages between UE and UTRAN and between UTRAN and CN.
3. Non-Access Stratum (NAS) : The Non-Access-Stratum covers all messages of higher layers and user data, that do not deal with
access or transport tasks.This cover pure application control (application stratum), service request and control (serving stratum)
,handling of subscription data and subscriber specific services (home stratum).
MTS network 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
ation (including requesting the service,controlling different transmission resources,handover etc) are exchanged between the CN and the UEs using the Ra
s Stratum (AS).
gher layer protocols of the Non-Access Stratum(NAS) handle control aspects e.g. (GPRS)Mobility Management (G)MM,Connection Management (CM) or S
dures (of Rel. '99) are in most cases unchanged compared to the GSM Phase 2+
dures. The radio and Iu protocols contain mechanism for transparent NAS message transfer. So-called Direct Transfer (DT) procedures are
n the Iu and radio protocols for these these transparent NAS message transfer.
otocol structures of the UTRAN interfaces are designed in horizontal layers and vertical planes. The general protocol model describes these layers and p
The modularity of this model allows changing parts of the protocol structure in the future,if neccessary,while other parts remain intact.
ansport system used within UTRAN is ATM. There is difference between the usage of ATM and the use PCM lines in a GSM-BSS. ATM supports
nt types of bearer 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 A
ing. This means before a AAL type 2 virtual channel can be used,there might be signalling between the corresponding ATM switches. This behavior results
earer set up and release occur.
ontal Layer:
eneral protocol model consists of two main horizontal layers- the Radio Network Layer and Transport Network Layer.All UTRAN related issues
ible in the Radio Network Layer only.The Transport Network Layer is used for UTRAN,offering transport technologies.It is without any UTRAN
c requirements.
sport Network Layer : The Transport Network Layer consists of all protocols used for the transport network solution. This includes the physical
nd its transport frame layer,also the bearer service protocols are included.
o Network Layer : The Radio Network Layer contains all protocols,that are specific to the radio access and transport stratum. Also all other data
ms, to be transported through UTRAN, belong to this layer.
al Plane:
is also a vertical structure, the elements of this vertical structure are planes. A plane principle is protocol stack,more than one plane can coexist
eachother. The general protocol model consists of three vertical planes- the Control Plane,the User Plane and the Transport Network Control
Plane: The user plane supports the data streams for user data. Therefore the data streams are packed into frame protocols. These frame
ols will be transmitted via data bearers. In contrast to the signalling bearers of the control plane,the data bearer can require to be set up with
signalling.
ol Plane: The control plane consists of all application protocols that are used for radio network controlling. To transport the messages of an
ation protocol,one or several signaling bearers,provided by the transport network are neccesary. The Control Plane is used for all control
ng,which is UMTS-specific. It includes the Application Protocols (i.e. RANAP,RNSAP and NBAP) and the signaling bearer for transport the
ation Protocol messages.
sport Network Control Plane: The transport network control plane contains the ALCAP (Access Link Control Application Part). The ALCAP
ols are used to set up and release the data bearers of the user plane. Also ALCAP messages require a signaling bearer for transmission. It is
cessary to use the ALCAP for all data bearers. Expecially the transport network control plane is not necessary when pre-configured bearers only
ed. The Transport Network Control Plane is used for all control signaling within the Transport Layer. It contains no Radio Network Layer
ation.
ansport Network Control Plane acts as plane between the Control Plane and User Plane, it enables the Application Protocol in the Control Plane
otal independent of the technology selected for data bearer in the User Plane.
Control Plane
s.
ort plane is the setup of a data bearer for the user plane
n addition ,the CS control plane is used for controlling supplementary services and it can be used for the exchange of short messages. It contains of followi
radio interface. Therefore it performs spreading,scrambling.modulation,channel conding,rate matching etc.
trol of random access and the multiplexing/de-multiplexing of different UEs onto shared radio resources.
liabilty modes for every radio bearer. These modes are : Acknowledge (AM),Unacknowledge(UM) and Transparent (TM).
erforms all higher layer tasks related to the access stratum on the air interface (e.g. radio bearer setup)
he CS service these are: MM (Mobility Management),CC (Call Control),SS(Supplementary Services) and SMS (Short
all tasks related to transport stratum for control signaling and access stratum between UTRAN and CN. It is the
ish a singling connection for a UE. So the UE can then be identified by the signaling connection and not by an explicit
ation layer provides a bearer channel (virtual channel of AAL type 2) with certain QOS gurantees. Additonally the AAL 2 cirtual channel includes time stamp
e Iub interface (<>NBAP). On the other hand, the real time AAL 2 is used for relaying UE- data and UE-signaling
C and MSC.
User Plane -PS
ls 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 services.
PS and CS. UMTS has been designed to support both types of services, so that there are no special protocols.
the Iu interface towards the MSC.
aling conenction to the SGSN in the core network. RANAP handles all signaling transport and access related tasks.
protocols. Because there are essential differences how to handle a packet switched service request, the PS core
the SM (Session Management) protocol is used. The SMS is in fact the same as for CS.
nt differences.
ternet). These external data network have their own special network protocols ( e.g. internet) . These external data
nnected with such an external network, the UE has to send packets of this special network protocol, for the UMTS
ed Packet Data Protocol (PDP). It is the task of the UMTS network to provide a tunnel (PDP context) for transparent
packet header. This shall increase the efficiency of the air interface usage.
on Iu. GTP-U organizes addressing and identification of the originator and destination of the data between RNC and SGSN.
less unreliable transport service. In principle only routing is performed with UDP/IP
Uu interface is the interface between User Equipment (UE) and UMTS Terrestrial Radio Access Network (UTRAN) and it is the most i
The layer 1 supports all functions required for the transmission of bit streams on the physical medium. It is also in charge of measurements fu
layers, for example, Frame Error Rate (FER), Signal to Interference Ratio (SIR),interference power, transmit power, … It is basically compose
“transport channel” entity, and a
“physical channel” entity.
The layer 2 protocol is responsible for providing functions such as mapping, ciphering, retransmission and segmentation. It is made of four su
RLC (Radio Link Control), PDCP (Packet Data Convergence Protocol) and BMC (Broadcast/Multicast Control).
The layer 3 is split into 2 parts: the access stratum and the non access stratum. The access stratum part is made of “RRC (Radio
Resource Control)” entity and “duplication avoidance” entity. The non access stratum part is made of CC, MM parts.The RRC functions of
L3 are implemented by RNC, and the MM and CC functions of L3 are implemented by CN.
The protocol layers are located in the UE and the peer entities are in the node B or the RNC.
ayer has the following steps,that can be identified with the presented functional blocks:
used for error detection
ed 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 afterwards
terference.UTRAN FDD and TDD offer four different channel coding schemes as FEC(Forward Error Correction). These
te. the physical layer gets matching parameters from RRC layer
e padding bits are appended
t fading and interference of the channel
posite Transport Channels)
y
transmission) bits are inserted. This is only for downlink
ted to several radio frames
o several physical channels if neccesary
and transmitted in physical channels,there has to be an indication which transport formats are used for every transport
NodeB the value of the TFCI can be translated into:
and transmission power)
hese procedures are triggered and mastered by higher layers like MAC and RRC. The procedures can be devided into
d chip synchronization to physical channels. In the TDD mode also timing advance procedures are used to synchronize
m. The solution for this is a very fast power control mechanism,using a closed control loop ( UE<>NodeB<>UE)
use random access mechanism to establish a radio connection between an UE and the Network. BNut also for
o perform measurements of radio signal quality (bit error rate) and radio signal strength (signal interference
handover procedures. For the measurments the UE physical layer has uses so called compressed mode mode radio
are then performed.
Multicast Control (BMC) and Packet Data 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
P (NodeB Application Part) : The NBAP protocol is the application protocol of the Iub interface. It organizes all controlling tasks between RNC and NodeB
uration).
,AAL 5, ATM : These protocols constitute the signalling bearer for the NBAP messages.
ser plane of the Iub interface has to transfer the downlink and uplink data to and from the UE. Therefore different frames are defined in the same
consists of:
e Protocols : The Frame Protocols encapsulate the UE data (UL&DL) on the Iub interface
2 ,ATM : The frame protocol,that encapsulate the UE data,are transported over AAL 2 virtual channels of ATM. These AAL 2 virtual channels have to be se
ype 2 signaling protocol : The AAL type 2 SP provides the messages and functions to setup, release and modify AAL 2 virtual channels.
SAAL,AAL 5,ATM : The STC (Signaling Transport Converter),SAAL,AAL 5 and ATM provide the signaling bearer for AAL type 2 signaling protocol.
hysical layer is not standardized. it is up to the operator and verndor to choose an appropiate physical transmission system.
ontrol plane of the Iur interface contains the following protocols:
AP (Radio Network Subsystem Application Part) : The RNSAP protocol is responsible for the communication between S-RNC and D-RNC. This
resource allocation 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
S relocation)
P (Signaling Connection Control Part) : The SCCP is used to set up a signaling connection between S-RNC and D-RNC for the UE. This means
RNC sets up one SCCP signaling connection for every D-RNC and UE. The signaling connection will be used for fast identification of the UE in
ng messages
3B,SAAL,AAL5,ATM : These protocols form the signaling bearer used for the RNSAP protocol messages.
ser plane of the Iur interface has the tasks to transport uplink and downlink data for the UE connected to a D-RNC. This tasks requires the follow
e Protocols : The data to and from the UE will be encapsulated into frame. These frames are defined by so called frame protocols. These frame
ols allow traffic management with in-band signaling
2 ,ATM : The frame protocol packets are transmitted via Iub using AAL 2 virtual channels. So AAL 2 ,ATM form the data bearer on the Iub interface.
ype 2 signaling protocol : The AAL type 2 SP provides the messages and functions to setup, release and modify AAL 2 virtual channels.
MTP3B, SAAL,AAL 5,ATM : These protocols provide the signaling bearer for the AAL type2 signaling protocol. The STC(Signaling Transport
rter) provides functionality for congestion handling and load control. The protocol suite MTP3B,SAAL,AAL5 and ATM can be shared with the
ng bearer of RNSAP of Control Plane
llowing protocol model is applied to the UTRAN interfaces Iu, there are differences between Iu-CS toward the CS-core network domain and Iu-PS towards
CS protocol stack
ontrol plane for Iu-CS is formed out of the following protocols:
AP ( Radio Access Network Application Part) : The RANAP protocol is responsible for all access and signaling transport related tasks. It is the applicatio
P (Signaling Connection Control Part) : The SCCP is used to setup signaling connection between RNC and MSC. There will be one and only one SCCP
rvice.
3B,SAAL,AAL5,ATM : Theses protocols provide the signaling bearer for RANAP/SCCP messages
ser plane on Iu-CS has to support the transfer of real time CS data streams. Therefore the Iu-CS plane has the following protocols:
(User Plane) protocol : The Iu UP protocol is used to provide additional support functions for CS data streams on Iu. These functions can be : timing cont
ction.
,ATM : For the data bearer to transport the data streams the AAL 2 virtual channels are used.
ansport network control plane is necessary ,because AAL2 virtual channels need to be setup and released. The protocol suite on the transport
k control plane consisting of:
ype 2 signaling protocol : used to setup ,modify and release AAL 2 virtual channels.
MTP 3B,SAAL,AAL5,ATM : These protocols provide the signaling bearer for the AAL type 2 signalling protocol messages.
S protocol stack
-PS interface is the interface between RNC and SGSN. The control plane of Iu-PS is similar to the Iu-CS plane. It consists of:
control plane
AP : The application protocol for Iu-CS and Iu-PS
P : Provides signaling connection on Iu-PS. There will be one and only one SCCP connection between RNC and SGSN for every UE using PS
e. SCCP connections on Iu-PS and Iu-CS do not affect each other.
3B,SAAL,AAL5,ATM : The signaling bearer for SCCP/RANAP
ser plane on 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
sary. The UTRAN provides the following protocols on the Iu-PS user plane:
protocol : As for Iu-CS the Iu UP protocol can provide additional support functions for the data stream.
U (GPRS Tunneling Protocol-User Plane): GTP-U provides a frame for the user data to be transported. In a GTP-U frame a reference number for
DP context and sequence numbers for the data are contained.
P : The UDP/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
ersa.
5,ATM : The ATM adaptation layer of type 5 is used as bearer for the packets of IP/UDP/GTP-U.
AL 5 virtual 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
e packet transfer. Therefore on Iu-PS there is no need for a transport network control plane. no bearer set up with explicit signalling is necessary.
RANAP
t controls signaling information for the call setup between nodes. Basically these applications message structure is similar to the SS7 signaling format, con
ignaling for the control plane and one application part (ALCAP) to set up the transport bearer for the user plane.
protocol that contains all the control information specified for the Radio Network Layer. The fucntions of RANAP are
ne or more EP.
a connected RAB
cedure,the NodeB assigns a traffic termination point to control UE signaling. All of the subsequent signaling related to
NC.
s.
provides the signaling capability to establish,release and maintain AAL2 connections by a series of ATM VCCs. In other
n the UTRAN. The transport bearer in the User Plane are setup first sending signals by the Application Protocol in the
the ALCAP is dependent on the type of bearer to be used. The signaling bearers are usually pre-configured. This means
p ,performs all necessary procedures to configure the bearer. When the application part receives the notification of a
nformed to start the data stream transmission.
via Iu(CS) interface and to the PS domain via Iu(PS) interface. Signalling and data
hnology
erving RNC handles all higher layer functions related to radio access and
alling
rent
cell or multiple (sector) cells can be serviced by a Node B. Generally,up to six
b
leased.
which
o the
RAN has the functions to provide access links between UE and UTRAN and
types of signalling between UE,UTRAN and CN as follows,
UE via Uu(radio) interface. User data (radio access bearer services) and control
een the CN and the UEs using the Radio protocols and the Iu protocols of the
TM).
t
lane. The following protocols involved into the user data transport,
L 2 cirtual channel includes time stamps in the transport frames. This allows
ng
ame as for the CS services.
SGSN.
etwork (UTRAN) and it is the most important interface in the UMTS system.
rt
o
ze
rent frames are defined in the same way as on the Iur interface. The user
mission system.
een S-RNC and D-RNC. This
functionality to a D-RNC
ing protocols:
u. These functions can be : timing control,data rate control,backward error
ages.
nsists of:
NBAP
milar to the SS7 signaling format, consisting each message of mandatory fixed
soft
er
e
eans
e
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 d
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
GSM Idle Cell_DCH
3GPP TS 25.304
GSM TS 05.08 3GPP TS 25.331
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
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
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 b
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 transparen
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 tran
-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 chann
For RRC messages the protocol specified which RLC mode and with this which radio bearer can be chosen for transport of
URA_PCH CELL_PCH
CELL_DCH CELL_FACH
The RRC protocol is an application part (Radio Resource Management) and transport protocol (NAS message transport). Therefore the R
The RRC state definiton describes the RRC protocol behavior as a nested set of stated. Two main states are defined:
The RRC protocol is an application part (Radio Resource Management) and transport protocol (NAS message transport). Therefore the R
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 hav
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 m
For multi-mode mobile phones (e.g. UMTS,GSM/GPRS) the RRC states can be combined with the radio resource management st
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).Therefor
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.
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
UE and UTRAN, the UE is identified by a Radio Network Temporary Identity (RNTI). As can be seen in the
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 l
instance, the DCHs are not available in the sub-states CELL_PCH and CELL_URA. The UE leaves the RRC idle
mode when sending the RRC Connection Request message to UTRAN. When UTRAN accepts the UE‘s request, the UE enters either the
CELL_DCH
In this sub-state, dedicated physical channels are allocated to the UE. DCCH and – if configured – DTCH information can be transmitted.
allocated to this UE. UTRAN knows the active set cells for the radio links and thus the location of the the UE. Also downlink shared chann
BCCH, if it owns specific capabilities). The cell system information is broadcasted on the FACH. The UE reads the cell system information
cell system information. This state can only be entered from Cell_FACH by setting up a DCH. When the last DCH is released the UE ente
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 higher
transmitted. In this case, an exclusive allocation of one physical channel to the UE would result in a waste of resources. Only common tran
UEs. Each UE must be explicitly addressed, for instance by the RNTI. It has to monitor the FACH permanently in the downlink, not to miss
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 th
responsible for cell re-selection. By listening to the cell system information from the BCCH, it gains all relevant measurement qualities, thre
learned from the BCCH. The UE receives
RRC messages on the BCCH, CCCH and DCCH channels. Due to the discontinuous type of traffic, UTRAN can command the UE to perf
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 th
responsible for cell re-selection. By listening to the cell system information from the BCCH, it gains all relevant measurement qualities, thre
learned from the BCCH. The UE receives
RRC messages on the BCCH, CCCH and DCCH channels. Due to the discontinuous type of traffic, UTRAN can command the UE to perf
The UE listens to the cell system information, broadcasted on the BCCH. It performs measurements accordingly, and is responsible for ce
transmit data to the UE, it must be paged first. Therefore, the UE has to monitor paging occasions on its PICH, i.e. it receives RRC messa
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
Depending on the UE‘s RRC message, UTRAN returns the RRC message Cell Update Confirm or URA Update Confirm – if it accepts the
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 to
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
A periodic update is a supervision mechanism, which can be used by the mobile operator to keep track of the UE. If a cell or URA update
URA_PCH, or in the RRC mode idle.
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
resources.
The timers can be broadcasted with the System Information Block 1 (or as part of the UTRAN Mobility Information message):
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
when it was active. The UE has to transmit the RRC Cell Update message to UTRAN, indicating the cause of the
cell update: re-entering service area. If the timer T317 expires, the UE moves to the idle mode. It releases all dedicated resources.
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
when it was active. The UE has to transmit the RRC Cell Update message to UTRAN, indicating the cause of the
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
ng radio tasks are in the responsibility of RRC. The RRC has following functions:
trol tasks are performed and it belongs to the transport stratum,because it carriers the higher layer control plane protocol messages.
MTS radio interface. The radio bearers in an UE will be numbered from 0 to 31.
ed:
he RACH with RLC transparent mode, the downlink CCCH is mapped to the
GSM-UMTS Handover
GSM
Connected
Mode
UTRA: Inter-RAT Handover
Release RR
Connection
GPRS Packet
Cell Transfer
Reselection Mode
Release
of a TBF
Initiation
stablish RRC of a TBF Establish RR
onnection Connection
Idle Mode
(MS camps on a GSM/GPRS cell)
ssage transport). Therefore the RRC protocol requires state definition with transitions between states.
n states are defined:
n the access stratum level between the UE and UTRAN. UTRAN has no information about UEs in the RRC idle mode. If UTRAN wants to
ending the "RRC Connection Request" message to UTRAN. If common transport channels used to exchange messages and data between the
he
tates depend on the connectivity level between the UE and UTRAN. The set of usable transport channels depend also on the sub-states. For
RRC idle
s request, the UE enters either the sub-state CELL_DCH or CELL_FACH.
escribe, on which level the UE is known by UTRAN and which resources are allocated by the UE. UTRAN can know any UE either on cell level
ansport channel for control message exchange. Therefore the four connected states are introduced:
H information can be transmitted. There no need to identify the UE on a dedicated channel, because the physical channels are exclusively
UE. Also downlink shared channels can be allocated to the UE. In this state, the UE is capable to receive RRC messages on the DCCH (and
reads the cell system information and acts accordingly. For instance, it determines the measurement quality and the reporting events from the
last DCH is released the UE enters Cell_FACH,Cell_PCH,URA_PCH or idle mode
This is the case when only higher layer signalling information (NAS signalling) or small amount of user data (e.g. SMS messages) have to be
te of resources. Only common transport channel FACH can be used by the UE to transmit higher layer data, which it has to share with other
nently in the downlink, not to miss user data for it. The UE‘s FACH is mapped on one S-CCPCH.
only connected to one cell, and this is the location information, known within UTRAN. No soft handover takes place in this sub-state. The UE is
levant measurement qualities, threshold values, neighbourhood lists to perform the cell re-selection process. Other relevant information is also
ordingly, and is responsible for cell-reselection. In addition to that, it periodically looks for a PLMN with a higher priority. When UTRAN wants to
PICH, i.e. it receives RRC messages both on the BCCH and the PCCH.
data with the UE, it only needs to page the UE there. If the UE changes the cell, it
es, the UE must change to the CELL_FACH sub-state. (Please note, that no
E is in CELL_PCH
UTRAN about a detected change of location. The UE then moves (or is) in the CELL_FACH state and send the RRC message Cell Update or
Update Confirm – if it accepts the UE‘s update request. Otherwise, it return the RRC Connection Release message.
it.
formation message):
arts timer T316. The UE attempts to find a serving cell again. If it is successful,
mer is active. Being back in the service area can mean, that the UE is served
has changed, the cell or URA update has to be initiated by the UE. But what
FACH and starts timer T317. If the UE is back in the service area, it performs
the UE starts timer T317, if it was not yet active. If the UE enters the service area again, the timer T317 is stopped. Also timer T307 is stopped,
se of the
es all dedicated resources.
Click to return to main page
protocol messages.
Click to return to main page
>>State Transistions Parameters Description (Module II)
Click to return to main page
TRAN wants to
he sub-states. For
are exclusively
on the DCCH (and
ting events from the
ssages) have to be
o share with other
sub-state. The UE is
t information is also
ger time, no
the UE and UTRAN. If
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
settings. With that, the UE knows how to receive and transmit data via the WCDMA radio interface. The RNC uses the NodeB Application
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
-Radio Bearer Control Procedures :These procedures for radio bearer establishment, transport channel and physical channel reconfigur
-RRC Connection Mobility Procedures :These procedures such as cell and URA updates, UTRAN mobility information, active set update
-Measurement Procedures Measurement control and report, etc. is managed here.
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 protocols
logical channel CCCH.
UTRAN returns a response. If UTRAN accepts the UE‘s RRC Connection Request, it returns the message RRC Connection Setup messag
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
Connection Setup message to the UE, it uses the UTRAN specific signalling protocol NBAP to send these parameters to the Node B.
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 t
If the UE has received the message RRC Connection Setup, it returns the RRC Connection Setup Complete message to the RNC, using t
-Establishment cause :
There is a huge list of causes for a connection request
The UE also delivers measurement results; the corresponding IE is called Measured Results on the RACH, because the measurement
broadcasted as cell system information. The cells, listed in the measurement result list, are ordered in accordance to the measurement res
with the best one in the beginning of the list.
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
PDU. For instance, if two DTCHs are multiplexed on one DCH, then field C/T is added in the MAC header to identify the logical channel, to
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.
After the UE transmits RRC CONNECTION REQUEST message, the T300 timer will be started, and the timer will be stopped after the UE
times specified by the constant N300, the UE repeats RRC CONNECTION REQUEST; otherwise it will be in the idle mode,consider the pr
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.
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 B
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 re
- 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
UE Sycnchronization Status
Layer 1 in the Node B shall every radio frame check synchronisation status of all radio link sets. Synchronisation status is indicated to the R
CPHY-Out-of Sync IND primitive. Hence, only one synchronisation status indication shall be given per radio link set.The exact criteria for in
the same criteria as for the downlink synchronisation status primitives.
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 the
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 is
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 D
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 notifie
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 consider
uplink DPCCH transmission shall not start before the downlink physical channel has been established and the activation time has been rea
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 obtain
shall be considered to be in the in-sync state.The RL Restore procedure may be triggered several times, indicating when synchronisation i
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 w
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 Node
obtained synchronisation. When RL Restore is triggered the radio link set shall be considered to be in the in-sync state.The RL Restore pro
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 sync
layers every radio frame.
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
unacknowledged mode(UM) bearers. T315 is controlling acknowledged(AM) mode bearers
->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 U
->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 CONFIRM
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
-When the BTS L1 has detected N_INSYNC_IND consecutive indications with In-sync status, the radio link is moved from the initial state t
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 synchroni
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_IN
in the NBAP: CONFIGURATION DATA message)
When the UE starts to set up the dedicated channel, it starts the T312 timer, and after the UE detects N312 synchronization indications fro
->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
lling and control data to establish, maintain, and release connections. The UE gets informed about the radio bearer characteristics, the transport channel c
he RNC uses the NodeB Application Part (NBAP) protocol to inform the Node B about the radio interface configuration.
V3.12.0:
m information, paging, RRC connection establishment and release, UE capability inquiry, security mode control, Inter-RAT handover information transfer, etc
nnel and physical channel reconfiguration, physical channel failure, etc. can be found here.
mobility information, active set update, and various handover procedures are covered here.
main identity.
ties are examples of data, associated with these IEs.
quirements, PDCP and FDD RF capabilities, radio access capabilities, cell update causes,etc.
s of a radio bearer, such as RB information to setup.
escribed, such as the description of TFCs and TFCSs.
uch as the description of CCTrCHs or compressed mode information.
exchanged here.
idle mode, and higher layer protocols in the UE request a signalling connection to UTRAN. Please note, that an RRC connection establishment is always in
sage RRC Connection Setup message. The UE gets all relevant parameters regarding the signalling bearers, transport channels, and physical channels.
e Node B must also get all relevant parameters to serve the UE on the radio interface adequately, and to relay data between the Iub-interface and Uu-inter
hese parameters to the Node B.
mplete message to the RNC, using the transport channel DCH. Beforehand it performed a L1 Synchronization.
s can be found in this message:
e RACH, because the measurement results are transmitted via the transport channel RACH. The measured quantity can be set by the operator, but it is an
accordance to the measurement results,
The RRC Connection Setup message is used to specify the (signalling) radio bearer, the transport channel and the physical ch
downlink directions. The RRC Connection Setup message is sent from the RRC layer in the RNC to the RRC layer in the UE.
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.
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.
When the RRC Connection Setup message is sent from the RNC to the UE, then the RB IEs describe, how the
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 distinguishe
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 oth
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 opt
This is indicated with the IE Signalling RB to Setup List. Given the number, either 3 or 4 descriptions of radio b
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 ge
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 a
also logical channel identities.
or two logical channels. This was part of the RB setup information. The information carried on radio bearers must be
ansmitted? How can higher layer information be segmented? This is described with the information elements for
nt describes the the allowed TFs, which can be transmitted via this TrCH.This information element also describes,
peer entity. RLC PDUs from several RBs (RLC layers) can be multiplexed on one transport channel. The MAC header of a MAC PDU holds relevant inform
ader to identify the logical channel, to which
H, CPCH, DSCH.
the physical channels. One of the PhyCH IEs is the carrier frequency band, where the signalling connection is
signalling bearer setup. Also the available UL and DL radio resources have to be described.
tup message. When we have a closer look to the IE „Downlink information common for all radio links“, we detect
AT measurements on neighbouring cells and at the same time receive data from the active set cells. If this is the case,
ore, this mode is often called Slotted Mode. In order to transmit still the user data with a given data rate, more
short while.
all active set cells receive the UE‘s signals, only one is making a transmission downlink. The UE tells the active set
Node B, so that this device can decide, how to set the weighting to the individual antennas. There are two different so-
Hereby, the feedback command rate is 1 bit per timeslot. - closed loop mode 2: Phase and amplitude adjustments
The UE has received the RRC Connection Setup message and returns the RRC Connection Setup Complete m
transmitted via the logical channel DCCH on the radio signalling bearer, which offers acknowledged mode of o
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 han
-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 c
"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.
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.
he timer will be stopped after the UE receives RRC CONNECTION SETUP message. Once the timer times out, if RRC CONNECTION REQUEST messag
ll be in the idle mode,consider the procedure to be unsuccessful. The procedures in details are as follows:
l UE identity" equal to the value of the variable INITIAL_UE_IDENTITY; and if cell re-selection or expiry of timer T300 occurs;
k CCCH;
on status of radio links, both in uplink and downlink.
ated channels in order to detect a loss of the signal on Layer 1, as specified in TS 25.214. The synchronization state of
ER is the relation of the incorrectly detected pilot bits to the total number of pilot bits in a radio frame),the thresholds
urn its power on respectively. The synchronisation status is reported to the higher layer.
n-sync status
e fulfilled:
Qin. Qin is defined implicitly by the relevant tests(def.20% BER)
n a TTI ending in the current frame with correct CRC. If no transport blocks are received, or no transport block has a
hall be considered only for TrCHs using CRC in all transport formats.
RL Failure
In-sync
state
RL Restore
NodeB Radio Link Set States and Transistions
hronisation status is indicated to the RL Failure/Restored triggering function using either the CPHY-Sync-IND or
radio 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 DPCCH quality or CRC
Uplink Direction
nk failure detection in DL is based on counter N313 (counting “out of sync” indicator) and timer T313 in UE. In CELL_DCH State, after receiving N313 cons
Once the radio link sets have been established, they will be in the in-sync or out-of-sync states. Transitions between
ync-IND and CPHY-Out-of-Sync-IND, indicating in-sync and out-of-sync respectively. Note that only one
o link is moved from the initial state to an In-sync state. L1 informs BTS L3 about the established synchronization and
N_OUTSYNC_IND consecutive out-of-sync indications. Node B shall stop and reset timer T_RLFAILURE upon
ger the RL Failure procedure and indicate which radio link set is out-of-sync. When the RL Failure procedure is
L1 keeps on searching the synchronization as long as the synchronization has been re-established or the radio link is
indications Node B shall trigger the RL Restore procedure and indicate which radio link set has re-established
the in-sync state. BTS L3 sends the NBAP:SYNCHRONIZATION INDICATION message to the RNC
of the downlink DPCH is controlled based on the TPC bits transmitted by the UE. Also, the TPC bits transmitted in the
e parameters Qin and Qout and N_INSYNC_IND, N_OUTSYNC_IND, T_RLFAILURE are given by the RNC to the BTS
N312 synchronization indications from L1, it will stop the T312 timer. Once the timer times out, it means that the physical channel setup has failed.
Downlink Direction
Uplink Direction
and wait for layer 1 to indicate N312 "in sync" indications
er T312 is stopped and reset
SYNCHRONIZATION INDICATION –message to RNC after which the closed loop and outer loop PC start to control the powers
Downlink Direction
Uplink Direction
on –message to RNC
nk Deletion -message
Downlink Direction
Uplink Direction
ge to RNC
essage to RNC
ching for the synchronization
characteristics, the transport channel configurations, and the physical layer
ation.
a between the Iub-interface and Uu-interface. Before the RNC returns the RRC
y can be set by the operator, but it is an option. If set by the operator, it is
eraction with the Node B to establish a radio link connection over the interface Iub.
he transport channel and the physical channel characteristics both in the UL and
in the RNC to the RRC layer in the UE. The UE‘s RRC uses management
ers are:
management messages between the UE and the RNC. The RRC layer also takes
bearers.
e UE, then the RB IEs describe, how the Radio Link Control layer(RLC) has to
der of a MAC PDU holds relevant information to identify the receiver of the RLC
se,
o-
nts
s the RRC Connection Setup Complete message to the S-RNC. This message is
r, which offers acknowledged mode of operation (RB2). The information elements
00 occurs;
e of
s
RC
Initial
state
RL Failure
Out-of-sync
state
RL Restore
Set States and Transistions
ased on received DPCCH quality or CRC checks. One example would be to have
L_DCH State, after receiving N313 consecutive "out of sync" indications from layer
en
nd
is
the
BTS
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 ha
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.
Every RRC request, which is mentioned above, can be conducted successfully or fail.
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.
If the UE is in the RRC idle mode, it receives relevant measurement information from the BCCH. The SIB type 3 contains parameters
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
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
UTRAN may control a measurement in the UE either by broadcast system information and/or by transmitting a MEASUREMEN
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
UTRAN may control a measurement in the UE either by broadcast system information and/or by transmitting a MEASUREMEN
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.
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.
When a new measurement is initiated, UTRAN should set the IE "Measurement identity" to a value, which is not used for other measure
"Measurement type", "Measurement object" can be set differently for each measurement with different "Measurement identity ".
When a current measurement is modified or released, UTRAN should set the IE "Measurement identity" to the value, which is used for t
than modifying IEs, and the UE continues to use the current values of the IEs that are not modified.
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 "
--> 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.
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 reportin
measurements that are being performed in the UE.
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 reportin
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 reporti
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 trans
MEASUREMENT REPORT message on the uplink DCCH when the reporting criteria stored in variable MEASUREMENT_
performed in the UE.
e different categories:
in the active set are involved in soft handover.
assigned by the UTRAN belong to the monitored set.
belong to the detected set. Reporting of measurements of the detected set is only required for intra-frequency
SIB type 3 contains parameters for cell selection and re-selection. In parallel, the SIB type 11 is used to deliver measurement control information to the UE f
ell only and responsible for cell selection and re-selection. It retrieves the parameters for cell selection from SIB
d and valid, when the UE is in the CELL_FACH, CELL_PCH and URA_PCH sub-state. If SIB 4 resp. SIB 12 is
e 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
mitted to the UE. This message informs the UE about the type of measurement, which has to be conducted. Each
quantities, reporting criteria, type, etc.
to be distinguished:
mation Elements, which contain intra-frequency, inter-frequency, inter-RAT and traffic volume measurement
nt report, when a measurement reporting criteria is fulfilled. As soon as the UE receives a Measurement
ed data based on the SIB11 by the parameters delivered with the Measurement Control message.
measurement control parameters. If the UE transits to the CELL_DCH sub-state, the system information stays
t happens, if the UE was in the CELL_DCH sub-state, it has received Measurement Control messages, and
1), and its measurement control parameters become valid. But when the UE then transits back to the
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
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.
In the RRC message Measurement Control, the is an PhyCH information elements, where
the UE can gain DPCH compressed mode status information
ransmitting a MEASUREMENT CONTROL message. The latter message includes the following measurement control information:
.
r absence of the following control information depends on the measurement type
asurements.
at are mandatory to report for the specific event.
MENT CONTROL message, which is transmitted on the downlink DCCH using AM RLC.The UTRAN should take the UE capabilities into account when a m
ch is not used for other measurements. UTRAN may use several "Measurement identity" for the same "Measurement type". In case of setting several "Meas
Measurement identity ".
to the value, which is used for the measurement being modified or released. In case of modifying IEs within a "Measurement identity", it is not needed for U
identity";
urements and a compressed mode pattern sequence with an appropriate measurement purpose is
he measurements: begin measurements according to the stored control information for this measurement
iable MEASUREMENT_IDENTITY.
eactivate this pattern sequence at the beginning of the frame indicated by IE "TGPS reconfiguration CFN"
PSI" for which the "TGPS status flag" is set to "active" at the time indicated by IE "TGCFN"; and
asurement purpose of each activated pattern sequence;
n sequence immediately at that CFN;
e variable TRANSACTIONS;
ink DCCH when the reporting criteria stored in variable MEASUREMENT_IDENTITY are met for any ongoing
rement control information to the UE for the serving cell. SIB 3 and SIB
nt in the UE.
s. A measurement is either
eport. The Measurement
mode. I.e. the UE is either in
ement fails, the UE returns
a an RLC entity in the acknowledged mode.
. A measurement identity
ies and identifies the
ch can be conducted:
control information:
UE capabilities into account when a measurement is assigned to the
rement identity", it is not needed for UTRAN to indicate the IEs other
oing
Click to return to main page
Paging
In UTRAN, we distinguish two different types of paging, depending on the existence of a RL connection between UE and UTRA
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.
The CN originated paging precedure: is used to establish a signaling connection. It is divided into co-ordination paging and non co-ordinatio
The CN indicates in the RANAP paging message whether the RNC shall
perform the UTRAN co-ordination paging
-Co-ordination paging, the RNC shall check whether the UE has other CN domain signaling connections
besides the paging domain connection. If so and the UE is in Cell_DCH or Cell_FACH state, the paging
message shall be transmitted on the already connected DCCH on the radio interface. if so and the UE is in Cell_PCH or URA_PCH state,the
message shall be transmitted on the PCCH on the radio interface. If no, the paging message shall be transmitted on the PCCH.
-Non-co-ordinating paging, the RNC need not check whether the UE has other CN domain signaling connections
besides the paging domain connection but directly transmit the paging message on the PCCH in the CN
specified paging area.
The UTRAN orignated paing : The UTRAN may initiate paging for a UE in Cell_PCH or URA_PCH state to trgiger
a cell update procedure to enable the transition to Cell_FACH state. In additon,the UTRAN may initiate paging for
a UE to trigger reading of updated system information.
For a UE in idle mode or in CELL_PCH or URA_PCH state, the RNC initiates the paging procedure by transmitting
a PAGING TYPE 1 message on the PCCH. For a UE in CELL_FACH or CELL_DCH state, the RNC initiates the
paging procedure by transmitting a PAGING TYPE 2 message on the DCCH
d to a UE, which is either in the RRC idle mode, or in the RRC connected mode sub-states
message from the CN has to be forwarded to the UE. . In this case, the UE adds the IE Paging
mitted on an existing ps connection (PMM-IDLE or PMM-CONNECTED). UTRAN has to page the
ata.
eives a paging message, it reads the UE identity to check, whether it is the receiver of the
PE 1 message to a UE on several paging occasions message on an appropriate paging
e., when at least dedicated control channel resources were allocated to the UE.
ne DDCH and one DCCH to the user. Consequently, a connection between the UE and the 3G-
the user. While the subscriber is serving, he receives a call. The 3G-MSC is sending a paging
eived by a RNC, which is currently serving the UE. It then uses the existing DCCH to forward the
tions
ng
E is in Cell_PCH or URA_PCH state,the paging
transmitted on the PCCH.
g connections
CN
state to trgiger
te paging for
y transmitting
nitiates the
Click to return to main page
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&SIB12-1&SIB18-1;
(The SIB switch is only valid for SIB2,SIB4,SIB12 and SIB18)
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 re-read the SIB. Therefore, the UE can know by monitoring the MIB whether a SIB
containing static parameters is updated
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
Scheduling block 1
Cell
Scheduling block 2
There are two ways of notifying a UE of system information modification: by a value tag and by a timer
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,star
new SIB information. Notification by a Timer consider the stored system information content invalid, start the timer, and re-acquire new SIB inf
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 t
block in the cell.
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 "GS
- check the IE "PLMN identity" in the master information block and verify that it is the selected PLMN, stored as "PLMN identity" in the variable
- 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 mast
When selecting a new cell, the UE shall read the master information block. The UE may use the pre-defined scheduling information to locate t
block in the cell.
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 "GS
- check the IE "PLMN identity" in the master information block and verify that it is the selected PLMN, stored as "PLMN identity" in the variable
- 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 mast
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 t
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_TAG
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 informa
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 sy
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 in
that system information block or scheduling block into the variable VALUE_TAG; read and store the IEs of that system information block or sc
- 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 PLM
information.
For system information blocks, not supported by the UE, but referenced either in the master information block or in the scheduling blocks, th
- skip reading this system information block;
- skip monitoring changes to this system information block
The UE may use the scheduling information included within the master information block and the scheduling blocks to locate each system info
acquired.
The UE should only expect one occurrence of the scheduling information for a system information block in the master information block and a
However, to enable future introduction of new system information blocks, the UE shall also be able to receive system information blocks other
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 informa
- consider the content of the system information block valid until, if used, the value tag in the scheduling information for the system information
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 information
- 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 accordin
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 with
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 a scheduling block in a position where it should be according to its scheduling information, but a transport block with
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 "
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, includin
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 a
additional system information blocks. (The SBs are applied when the scheduling resources of MIB are insufficient) Scheduling information for a system informa
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
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 th
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 syste
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
parameters periodically
includes measurement control information of cell. The UE gets here the relevant date for traffic measurement, intra-frequency measurements, etc. It is also va
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 UL outer loop control parameters of common and dedicated physical channels. Only used in TDD
includes parameters of radio bearer, transport channel and physical channel. These parameters are stored in UE (either in idle mode or connected mode). It u
UTRAN. RB, The parameters are used during a handover to UTRAN. Consequently, these parameters stay valid, when the UE is connected to GSM and GPR
includes the rapid changed parameters used to configure the shared physical channel in connected mode. Only used in TDD.
n Notification
e read by the UE. This requires a lot of battery power. Therefore, a Master Information Block (MIB) was introduced, which gives references and scheduling
n the P-CCPCH (on position SFN mod 8 = 0, and with a TTI of 20 ms). For most of the SIBs used within the system, the MIB may carry a value tag. The on
the 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 value tag e.g
ation is used to inform the UE, where and when a specific system information is transmitted.
sends a SYSTEM INFORMATION CHANGE INDICATION message on the BCCH to transmit the new MIB value tag.
ge or SYSTEM INFORMATCHANGE INDICATION message from UTRAN, the UE shall read the changed information
en the timer expires, the UE shall consider the stored system information content invalid,start the timer, and re-acquire
ider the stored system information content invalid, start the timer, and re-acquire new SIB information. The UE may
ded
tate are addressed directly by the RNC via the Measurement Control message
master information block. The UE may use the pre-defined scheduling information to locate the master information
PLMN has the value "GSM-MAP" and the IE "PLMN Type" has the value "GSM-MAP" or "GSM-MAP and ANSI-41",:
mation block and verify that it is the selected PLMN, stored as "PLMN identity" in the variable SELECTED_PLMN.
PLMN has the value "ANSI-41 "and the IE "PLMN Type" has the value "ANSI-41" or "GSM-MAP and ANSI-41",:
n block with the value tag stored for this cell and this PLMN in the variable VALUE_TAG.
r information block are stored: store the value tag into the variable VALUE_TAG for the master information block; read
UE mode/state when block is valid UE mode/state when block is read
URA_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 (TDD
(TDD only)) only))
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 Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD
(TDD only) only)
CELL_DCH 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_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 Idle mode, CELL_FACH, CELL_PCH, URA_PCH
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.
value=6s
value=50
value=20s
value=30s
value=infinity
value=2000ms
value=3
value=6s
value=1
value=hex2dec(0065)=101
Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(01110111100100
>>>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)
value=33dBm
value=-20dBm
value=2dB(step of 1 dB)
value=20attempts
value=8attempts
value=
Click to return to main page
value=-105dBm
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
1)=11 and Cellid=bin2dec(0111011110010010)=30610
II)
Click to return to main page
L3 Messages - Locat
UE NodeB
Start Rx
L1 Synchonization
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
example.
2 If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface after radio links ar
deleted.
L3 Messages - Location Update Procedure
S-RNC
n Request (RACH)
on Setup (FACH)
NBAP:Synchonization Indicator
Authentication and Securitty Mode Control may exist depends on Operator's setting (refer to signaling in AMR call precedures)
ect Transfer
ction Release
Release Complete
Release Complete
The UE in idle mode intitiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling conn
RRC CONNECTION REQUEST message from the UE, the Radio Resource Management (RRM) module of the RNC determines whether
the RRC connection on a Dedicated Channel (DCH)or on a Common Channel (CCH), based on a specific RRM algorithm. Typically, an RR
scribed as follows:
NNECTION REQUEST message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.
RRC connection request and the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the
ources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the specific ra
C connection.
a RADIO LINK SETUP RESPONSE message to the SRNC after successfully preparing the resources.
P protocol to set up the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedu
ce only.
CONNECTION SETUP message to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allo
Synchronization. NodeB sends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state
ONNECTION SETUP COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The mes
dure ends.
RC connection request cannot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT mes
the message
RRC connection is set up between the UE and the Serving RNC (SRNC)
d as follows:
DIRECT TRANSFER message to the SRNC through the RRC connection. The message contains the Non Access Stratum (NAS) informatio
AL UE MESSAGE to the CS service domain of the CN through the Iu interface. The message indicates LOCATION UPDATE REQUEST an
MSI),International Mobile Subscriber Identity (IMSI), and Location Area Identity (LAI).The SRNC sends an INITIAL UE MESSAGE to the PS
ssage indicates ATTACH REQUEST and contains the Routing Area Identity (RAI)
n area information of the UE and saves the new LAI. The CN might also perform authentication and ciphering. Then, the CN sends a DIRE
E ACCEPT and contains the TMSI that is assigned to the UE.For routing area update, the CN updates the routing area information of the U
Then, the CN sendsa DIRECT TRANSFER message to the SRNC. The message indicates ATTACH ACCEPTand contains the TMSI that
ends the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
TION UPDATE ACCEPT information and sends an UPLINK DIRECT TRANSFER message to the SRNC. The message contains the inform
H ACCEPT information that the UE receives.
ends the contents of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message. The DIRECT TRANSF
Iu release procedure can be triggered in one of the following conditions: The transaction between the UE and the CN is complete,The UTR
ystem (SRNS) is relocated.4.The SRNS relocation is canceled after a relocation resource allocation procedure iscomplete.
scribed as follows:
ASE COMMAND message to the SRNC to initiate the Iu release procedure. The message indicates the cause for the release of the signalin
ELEASE COMMAND message, the CN will not send further RANAP connection-oriented messages on this particular connection.
ated UTRAN resources and then sends an IU RELEASE COMPLETE message to the CN.
se procedure is performed to release the signaling connection and all radio bearers between UE and the UTRAN
r a n RAB is released,the SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection d
scribed as follows: based on the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: rel
ease of an RRC connection from CCH (If an RRC connection needs to be released after a successful outgoing call,, the RRC connection o
he RNC determines whether to accept or reject theRRC connection request, based on a specific algorithm. If accepting the request, the RR
RM algorithm. Typically, an RRC connection is set up on the DCH.
t of an RRC connection.
n on a DCH and allocates the Radio NetworkTemporary Identity(RNTI),radio
deB to allocate the specific radio link
. Then, the CN sends a DIRECT TRANSFER message to the SRNC. The message
uting area information of the UE and savesthe new RAI. The CN might also perform
Tand contains the TMSI that is assigned to the UE
R message.
e message contains the information suchas the NAS information and the CN ID.For routing
the CN is complete,The UTRAN requests the CN to release the resources on the Iu interface by, for example,sending an IU RELEASE RE
e iscomplete.
RAN
ing that the RRC connection does not carry other RAB of the UE,the SRNC initiates an RRC connection release procedure.
the message by the UE. The RRC SNs of these messages are the same. The number of retransmissions and the transmission intervals ar
in the NodeB.
release procedure.
value=MaxAllowedULTxPower=24 dBm
Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000000010101101011001010 => RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(0111011110010010)=23242
value= MCC=456
value= MNC=02
value=hex2dec(75AA)=30122
pt)
DPCCH_Power_offset CPICH_RSCP PCPICH Power UL Interference
-74 -80 33 -85
-74 -70 33 -85
Power_offset is configured by RNC and delivered to UE in RRC Connection Setup.
nd Cellid=bin2dec(0111011110010010)=23242
UL DPCCH Initial Power
6
-4
Click to return to main page
Start Rx
L1 Synchonization
Call Esta
RRC:Measurement Control
RRC:Measurement Report
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
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
L3 Messages - AMR Voice (MOC) Call Procedure
S-RNC
n Request (RACH)
on Setup (FACH)
NBAP:Synchonization Indicator
M: Authentication Response)
ode Command
de Completed
ansfer (CC: Setup)
earer Setup
Setup Complete
Call Established
ent Control
ent Report
oft Handover
ard Handover
Handover
ction Release
Release Complete
Release Complete
is performed on the
re is performed on the
C) Call Procedure
CN
d
2.RANAP: Direct Transfer (CC: Disconnect)
3.Authentication &
Security Mode Control
The authentication and security mode control procedure is pe
algorithm and ciphering algorithm. This procedure ensures integrity and
6.Conversation
7.Call Release
mode intitiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling connection When th
ermines whether to accept or reject theRRC connection request, based on a specific
module further determines whether to set up the RRC connection on a Dedicated Channel (DCH)or on a Common Channel (CCH),based
et up on the DCH.
lows:
EQUEST message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.
n request and the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio Network
L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the spec
SETUP RESPONSE message to the SRNC after successfully preparing the resources.
t up the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. I
SETUP message to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocated by the S
n. NodeB sends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state
ETUP COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message indicates
request cannot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to the UE
edure is performed to exchange the NAS (Non Access Stratum) information between the UE and the CN.
lows:
SFER message to the SRNC through the RRC connection. The message contains the initial NAS information to be sent to the CN by the UE
TRANSFER message from the UE and sends an INITIAL UE MESSAGE to the CN over the Iu interface. The INITIAL UE MESSAGE conta
t of the NAS information is CM SERVICE REQUEST.
SRNC.
CONNECTION CONFIRM (CC) message to the SRNC. The message indicates that the SCCP connection is set up. After receivingthe mes
t up.
ONNECTION REJECT (CJ) message to the SRNC. The message indicates that the SCCP connection fails to be set up. After receiving the
to be setup and then initiates the RRC release procedure.
e control procedure is performed for the UE and the network to implement bi-directional authentication and to negotiate and configure th
edure ensures integrity and correctness of signaling
N exchange signaling. The network initiates the authentication and securitymode control procedure
lows:
ssage to the SRNC. The message indicates AUTHENTICATION REQUEST.
nts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
SFER message to the SRNC.
nts of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION RESPO
at the authentication is successful, the UE returns a message with an XRES IE.
MAND message to the SRNC to initiate the security mode control procedure. The message contains the information about the supported ci
OMMAND message to the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.
o set up a call.
call
lows:
SFER message to the SRNC. The message contains the number of the called party and the information about the bearer capability of the c
nts of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message.
ssage to the SRNC. The message indicates CALL PROCEEDING and contains the information about the negotiated bearer capability of th
nts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
see more details in RAB Setup Procedure below)
nds a DIRECT TRANSFER message to the SRNC. The message indicates ALERTING.
nts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
ssage to the SRNC. The message indicates CONNECT, which means that the called party has answered the call.
nts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
NSFER message to the SRNC.
ents of the UPLINK DIRECT TRANSFER message to the CN through a DIRECT TRANSFER message, indicating CONNECT ACKNOWLED
n is described as follows:
QUEST message to the SRNC to initiate the RAB setup procedure.
-CS interface only) The SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and ra
L2 link characteristic parameters,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup procedure.
FIGURATION PREPARE message to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio links
urces and then sends a RADIO LINKRECONFIGURATION READY message to the SRNC.
interface only) The Iub ALCAP at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SRNC perfor
nization frames in the DCH frame protocol.
UP message to the UE.
FIGURATION COMMIT message to theNodeB.
e UE sends a RADIO BEARER SETUP COMPLETE message to the SRNC.
RESPONSE message to the CN. The RAB isset up.
shown is described as follows:
QUEST message to the SRNC to initiate the RAB setup procedure.
RESPONSE message to the CN. The message indicates the ID of the RAB that fails to be set up and the reason for the failure.
lows:
SFER message to the SRNC.
nts of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating DISCONNECT. This conten
ssage to the SRNC. The message indicates RELEASE to request release of the call.
nts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
is performed to release the signaling connection and all radio bearers between UE and the UTRAN
eased,the SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry o
lows: based on the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: release of an RRC
going call,, the RRC connection on the DCH is released and if a radio bearers
CCH is released)
naling connection When the SRNC receives an RRC CONNECTION REQUEST message from the UE, the Radio Resource
ection.
llocates the Radio NetworkTemporary
NodeB to allocate the specific radio link resources
N selects.
he bearer capability of the call.
ll.
g CONNECT ACKNOWLEDGE.
DISCONNECT. This content informs the CN that the UE has hanged up.
connection does not carry other RAB of the UE,the SRNC initiates an RRC connection release procedure.
ocedure: release of an RRC connection from DCH and release of an RRC connection from CCH (If an RRC connection
value=hex2dec(2908)= 10504
value=(-24+ (43/2))=-2.5 dB
value=hex2dec(2908)= 10504
value=UE capable to support FDD , not TDD
value=MaxAllowedULTxPower=24 dBm
Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)
est)
equest)
ponse)
onse)
value= Call B-Party number = 0812713339
ng)
Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2de
ge)
edge)
e)
ete)
Release)
e Complete)
DPCCH_Power_offset CPICH_RSCP PCPICH Power UL Interference
-94 -80 33 -105
-94 -70 33 -105
_Power_offset is configured by RNC and delivered to UE in RRC Connection Setup.
Cellid=bin2dec(0111011110010010)=30610
0000001011)=11 and Cellid=bin2dec(0111011110010010)=30610
UL DPCCH Initial Power
-14
-24
Click to return to main page
L3 Messages -AMR Voice
UE NodeB
*** The different messages between MOC & MTC are highlighted in "Red" color
Start Rx
L1 Synchonization
Call Esta
RRC:Measurement Control
RRC:Measurement Report
1.The RRC connection can be set up on a DCH or a CCH. This procedure takes the RRC connection set up on the DC
an example.
2. If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iubinterface after radio links a
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
up or a call is released
L3 Messages -AMR Voice Call (MTC) Call Procedure
S-RNC
ed in "Red" color
g Type 1
n Request (RACH)
on Setup (FACH)
NBAP:Synchonization Indicator
M: Authentication Response)
ode Command
de Completed
Transfer (CC: Setup)
earer Setup
Setup Complete
Call Established
ent Control
ent Report
5.Radio Bearer S
2.RRC ConnectionSetup
setup procedure is performed for the UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the
C connection at a time.
ions: The UE in idle mode intitiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a signalin
eives an RRC CONNECTION REQUEST message from the UE, the Radio Resource Management (RRM) module of the RNC determines w
ction request, based on a specific algorithm. If accepting the request, the RRM module further determines whether to set up the RRC conn
a Common Channel (CCH), based on a specific RRM algorithm. Typically, an RRC connection is set up on the DCH.
wn is described as follows:
RRC CONNECTION REQUEST message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connecti
e in the RRC connection request and the system resource status, the SRNC determines to set up the RRC connection on a DCH and alloca
dentity (RNTI), radio resources, and L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB
e specific radio link resources required for an RRC connection.
ds with a RADIO LINK SETUP RESPONSE message to the SRNC after successfully preparing the resources.
e ALCAP protocol to set up the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This
ATM-based Iub interface only.
an RRC CONNECTION SETUP message to the UE through the downlink CCCH (FACH). The message contains the information about the
iate L1 Synchronization. NodeB sends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state
RRC CONNECTION SETUP COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up.
C connection setup procedure ends.
at the RRC connection request cannot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJE
e reject reason in the message
nection setup procedure is performed to exchange the NAS (Non Access Stratum) information between the UE and the CN.
ions: The UE sends a direct transfer message to initiate the signaling connection setup procedure.
s the INITIAL DIRECT TRANSFER message from the UE and sendsan INITIAL UE MESSAGE to the CN through the Iu interface. The INIT
n and security mode control procedure is performed for the UE and the network to implement bi-directional authentication and to ne
ntegrity and correctness of signaling.
ons: The UE and the CN exchange signaling. The network initiates the authentication and securitymode control procedure
wn is described as follows:
RECT TRANSFER message to the SRNC. The message indicates AUTHENTICATION REQUEST.
rently sends the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
UPLINK DIRECT TRANSFER message to the SRNC.
rently sends the contents of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUT
MTS Subscriber Identity Module (USIM) judges that the authentication is successful, the UE returns a message with an XRES IE.
ECURITY MODE COMMAND message to the SRNC to initiate the security mode control procedure. The message contains the information
y protection algorithms.
a SECURITY MODE COMMAND message to the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN s
sponse message to the SRNC.
ection and ciphering algorithms are configured successfully, the UE sends a SECURITY MODE COMMAND COMPLETE message to
RITY MODE COMMAND COMPLETE message to the CN.The message contains the information about the integrity protection and cipherin
support the integrity protection and ciphering algorithms, the UE sends a SECURITY MODE COMMAND FAILURE message to the SR
ormation and the reason for the failure. The SRNC then sends a SECURITY MODE COMMAND REJECT message to the CN
n Release procedure is performed to release the signaling connection and all radio bearers between UE and the UTRAN
ns: After a n RAB is released,the SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC con
the SRNC initiates an RRC connection release procedure.
wn is described as follows: based on the resouce occupied by the RRC connection,there are two types of RRC connection release proce
C connection needs to be released after a successful outgoing call,, the RRC connection on the DCH is released and if a radio bearers fails
ure ends.
n-Sync" state
CCH) that is just set up. The message
cedure
ER message.
FER message.
party has hanged up.
ER message.
message. The DIRECT TRANSFER messageindicates RELEASE which requests release of the call.
ER message.
he reason for the Iu release.
er release procedure.
UTRAN
onnection release procedure: release of an RRC connection from DCH and release of an RRC connection
d if a radio bearers fails to be setup ,the RRC connection on the CCH is released)
value=hex2dec(2908)= 10504
value= terminatingConversationalcall (CS MTC)
value=(-24+ (44/2))=-2.0 dB
value=hex2dec(2908)= 10504
value=MaxAllowedULTxPower=24 dBm
-22
-22
Cell Identity=RNCid(12bits)+Cellid(16bits)
uest)
nse)
e)
ease)
ase)
DPCCH_Power_offset CPICH_RSCP PCPICH Power UL Interference
-16
-26
Click to return to main page
Start Rx
L1 Synchonization
Call Esta
RRC:Measurement Control
RRC:Measurement Report
1.RRC: Uplink Direct Transfer (CC: Disconnect)
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
an example.
2. If IP transport is applied to the Iub interface, no ALCAP procedure is
L3 Messages - Video Call (CS64) Call Procedure
S-RNC
n Request (RACH)
on Setup (FACH)
NBAP:Synchonization Indicator
M: Authentication Response)
ode Command
de Completed
ansfer (CC: Setup)
earer Setup
Setup Complete
Call Established
ent Control
ent Report
sfer (CC: Disconnect)
ction Release
Release Complete
Release Complete
is
64) Call Procedure
CN
d
2.RANAP: Direct Transfer (CC: Disconnect)
3.Authentication &
Security Mode Control
The authentication and security mode control procedure is pe
the integrity protection algorithm and ciphering algorithm. This procedur
6.Conversation
mode intitiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling connection When th
message from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or reject theRRC conn
cepting the request, the RRM module further determines whether to set up the RRC connection on a
Channel (CCH),based on a specific RRM algorithm. Typically, an RRC connection is set up on the DCH.
lows:
EQUEST message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.
n request and the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio Network
he SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the specific radio link resourc
SETUP RESPONSE message to the SRNC after successfully preparing the resources.
t up the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. I
SETUP message to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocated by the S
n. NodeB sends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state
ETUP COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message
cedure ends.
request cannot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to
he message
edure is performed to exchange the NAS (Non Access Stratum) information between the UE and the CN.
lows:
SFER message to the SRNC through the RRC connection. The message contains the initial NAS information to be sent to the CN by the UE
TRANSFER message from the UE and sends an INITIAL UE MESSAGE to the CN over the Iu interface. The INITIAL UE MESSAGE conta
mation is CM SERVICE REQUEST.
SRNC.
CONNECTION CONFIRM (CC) message to the SRNC. The message indicates that the SCCP connection is set up. After receivingthe mes
n is set up.
ONNECTION 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.
e control procedure is performed for the UE and the network to implement bi-directional authentication and to negotiate and configure
ing algorithm. This procedure ensures integrity and correctness of signaling
N exchange signaling. The network initiates the authentication and securitymode control procedure
lows:
ssage to the SRNC. The message indicates AUTHENTICATION REQUEST.
nts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
SFER message to the SRNC.
nts of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION RESPO
n is successful, the UE returns a message with an XRES IE.
MAND message to the SRNC to initiate the security mode control procedure. The message contains the information about the supported ci
OMMAND message to the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.
o set up a call.
call
lows:
SFER message to the SRNC. The message contains the number of the called party and the information about the bearer capability of the c
nts of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message.
ssage to the SRNC. The message indicates CALL PROCEEDING and contains the information about the negotiated bearer capability of th
nts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
see more details in RAB Setup Procedure below)
nds a DIRECT TRANSFER message to the SRNC. The message indicates ALERTING.
nts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
ssage to the SRNC. The message indicates CONNECT, which means that the called party has answered the call.
nts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
NSFER message to the SRNC.
ents of the UPLINK DIRECT TRANSFER message to the CN through a DIRECT TRANSFER message, indicating CONNECT ACKNOWLED
n is described as follows:
QUEST message to the SRNC to initiate the RAB setup procedure.
-CS interface only) The SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and ra
eristic parameters,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup procedure.
FIGURATION PREPARE message to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio links
urces and then sends a RADIO LINKRECONFIGURATION READY message to the SRNC.
interface only) The Iub ALCAP at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SRNC perfor
in the DCH frame protocol.
UP message to the UE.
FIGURATION COMMIT message to theNodeB.
e UE sends a RADIO BEARER SETUP COMPLETE message to the SRNC.
RESPONSE message to the CN. The RAB isset up.
shown is described as follows:
QUEST message to the SRNC to initiate the RAB setup procedure.
RESPONSE message to the CN. The message indicates the ID of the RAB that fails to be set up and the reason for the failure.
lows:
SFER message to the SRNC.
nts of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating DISCONNECT. This conten
ssage to the SRNC. The message indicates RELEASE to request release of the call.
is performed to release the signaling connection and all radio bearers between UE and the UTRAN
eased,the SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry o
release procedure.
lows: based on the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: release of an RRC
cessful outgoing call,, the RRC connection on the DCH is released and if a radio
on on the CCH is released)
ection.
llocates the Radio NetworkTemporary Identity(RNTI),radio
e specific radio link resources required for an RRC connection.
EJECT message to
N selects.
he bearer capability of the call.
ll.
g CONNECT ACKNOWLEDGE.
ocedure: release of an RRC connection from DCH and release of an RRC connection from CCH (If an RRC
he UE. The RRC SNs of these messages are the same. The number of retransmissions and the transmission intervals
e RRC connection.)
value=hex2dec(2908)= 10504
value=(-24+ (44/2))=-2.0 dB
>>"RRC Connection Setup Description"
value=hex2dec(2908)= 10504
value=MaxAllowedULTxPower=24 dBm
Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)
est)
equest)
ponse)
onse)
value= Call B-Party number = 0812713339
ng)
Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2de
ge)
edge)
e)
ete)
Release)
e Complete)
DPCCH_Power_offset CPICH_RSCP PCPICH Power UL Interference
-96 -80 33 -107
-96 -70 33 -107
_Power_offset is configured by RNC and delivered to UE in RRC Connection Setup.
Cellid=bin2dec(0111011110010010)=30610
0000001011)=11 and Cellid=bin2dec(0111011110010010)=30610
UL DPCCH Initial Power
-16
-26
Click to return to main page
L3
UE NodeB
Start Rx
4.ALCA
L1 Synchonization
ALCAP
Apply n
RRC:Measurement Control
RRC:Measurement Report
ALCAP
RRC: Radio Bearer Reconfiguration
ALCAP
n Request (RACH)
on Setup (FACH)
7.NBAP:Synchonization Indicator
de Command
de Completed
er (MM: Attach Accept)
arer Setup
Setup Complete
ent Control
PS Session Established
ent Report
Reconfiguration
figuration Complete
rer Release
lease Completed
5. Radio Bearer S
shed
Radio Bearer Rec
Upgrade/Downgr
4.PS Session Setup 10. Iu (Iu Interface) and SCCP signalling connections are r
UE in idle mode intitiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling connecti
CTION REQUEST message from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or re
specific algorithm. If accepting the request, the RRM module further determines whether to set up the RRC connection on a Dedicated Cha
(CCH),based on a specific RRM algorithm. Typically, an RRC connection is set up on the DCH.
bed as follows:
ECTION REQUEST message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.
C connection request and the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Rad
),radio resources, and L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting
ources required for an RRC connection.
ADIO LINK SETUP RESPONSE message to the SRNC after successfully preparing the resources.
otocol to set up the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is
b interface only.
NNECTION SETUP message to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocate
chronization. NodeB sends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state
ECTION SETUP COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The messag
n setup procedure ends.
connection request cannot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message
reason in the message
is performed in order to make UE presence known to the network by performing a Packet Service Attach (GPRS attach). This makes the U
h procedure, the UE shall provide its identity and an indication of which type of attach that is to be executed.
S attach.The identity provided to the network shall be the UE's Packet TMSI (P-TMSI) or IMSI
sends a GPRS Attach Request message to initiate the signaling connection setup procedure.
bed as follows:
re by the transmission of an Attach Request message to the RNC. IMSI shall be included if the UE does not have a valid P-TMSI (Packet T
Signalling Connection Control Part) connection and sends the Attach request to SGSN
TMSI and the SGSN has changed since detach, the new SGSN sends an Identification Request (P-TMSI, old RAI, old P-TMSI Signature) t
responds with Identification Response (IMSI, Authentication vector). The old SGSN also validates the old P-TMSI
e old and new SGSN, the SGSN sends an Identity Request (Identity Type = IMSI) to the UE. The UE responds with Identity Response (IMS
to authenticate the UE. HLR sends back to SGSN the Authentication data received from AUC (Authentication Center). The HLR contains G
N sends the Authentication and Ciphering Request to the UE. At authentication of a WCDMA subscriber, the SGSN transmitts the RAND (R
) to the UE. At reception of this message, the UE (USIM, WCDMA Subscriber Identity module in the UE) verifies AUTN and if accepted the
ponse (RES) message to the SGSN. During generation of authentication vectors, the USIM in the UE also computes a new Ciphering Key.
stored together with the CKSN (Ciphering key sequence number of Kc) until CKSN is updated at the next authentication. The SGSN verifie
it stream is encrypted and decrypted in SGSN and UE.
ged since the GPRS detach, or if it is the very first attach, then the SGSN informs the HLR:
E and the CN exchange signaling. The network initiates the authentication and securitymode control procedure
bed as follows:
NSFER message to the SRNC. The message indicates AUTHENTICATION REQUEST.
the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
ECT TRANSFER message to the SRNC.
the contents of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICAT
e (USIM) judges that the authentication is successful, the UE returns a message with an XRES IE.
ODE COMMAND message to the SRNC to initiate the security mode control procedure. The message contains the information about the su
ms.
Y MODE COMMAND message to the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.
sage to the SRNC.
ciphering algorithms are configured successfully, the UE sends a SECURITY MODE COMMAND COMPLETE message to the SRNC.
COMMAND COMPLETE message to the CN.The message contains the information about the integrity protection and ciphering algorithms
integrity protection and ciphering algorithms, the UE sends a SECURITY MODE COMMAND FAILURE message to the SRNC. The m
d the reason for the failure. The SRNC then sends a SECURITY MODE COMMAND REJECT message to the CN
age is used to transport the permanent UE Identity(IMSI) to SRNC
send Activate PDP context request message to RNC. PDP Context Activation is performed when the UE initiates a packet call setup. The U
that enables the user to transmitt and receive data while moving within a PLMN. and starts the PDP context activation procedure used to s
rminal connected to a UE and a GGSN. PDP contexts deal with allocation of IP addresses to the UE and Quality of Service, QoS, paramet
the SGSN in order to realize the air interface connection. At the end the UE has an IP address NSAPI (Network layer Service Access Point
associated to IMSI.
ynamically or statistically. If allocated dynamically, this significantly reduces the total number of IP addresses required per PLMN. Support o
hen accesing secure networks that use the calling IP address as a form of security check. The support of
cedure is performed to release services and resources after a session ends.
E send Deactivate PDP context request message to RNC. A PDP Context Deactivation is performed when the UE terminates a packet call.
Active. After the PDP Context deactivation procedure the state becomes Packet Mobility Management Connected.The RAB will be release
activation may be initiated by a:UE procedure,SGSN procedure,GGSN procedure
bed as follows:
P Context Request (TI, Teardown Indication) message to the SGSN via the RNC
P Context Request (TEID, NSAPI, Teardown Indication) message to the GGSN. If Teardown Indication was included by the UE in the Deac
s PDP address by including Teardown Indication in the Delete PDP Context Request message
ontext(s) and returns a delete PDP Context Response (TEID) message to the SGSN. The Delete PDP Context messages are sent over the
e PDP Context Accept (TI) message to the UE via the RNC
er release is done by the RAB Assignment procedure
n RNC and SGSN is released. At GPRS detach, all PDP contexts for the UE are implicitly deactivated
procedure is performed to release the signaling connection and all radio bearers between UE and the UTRAN
n RAB is released,the SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does
RRC connection release procedure.
bed as follows: based on the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: releas
needs to be released after a successful outgoing call,, the RRC connection on the DCH is released and if
,the RRC connection on the CCH is released)
RRC connection.
DCH and allocates the Radio
to the NodeB, requesting the NodeB to
S attach). This makes the UE available for SMS over PS data paging via the SGSN, and notification
age.
ired per PLMN. Support of static IP address allocation enables subscribers to provide their own IP
E terminates a packet call. Before the
ed.The RAB will be released if there are no other
ded by the UE in the Deactivate PDP Context Request message, then the SGSN deactivates all
release procedure: release of an RRC connection from DCH and release of an RRC connection
ssage by the UE. The RRC SNs of these messages are the same. The number of retransmissions
NodeB.
value=hex2dec(2908)= 10504
value=(-24+ (33/2))=-7.5 dB
>>"RRC Connection Setup Description"
value=hex2dec(2908)= 10504
value=UE capable to support FDD , not TDD
Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610
)
)
ng Request)
Response)
t)
d)
equest)
>>"Radio Bearer Description"
value= SF16(uplink)-> PS64
value=Primary Scrambling code=97
Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(01110111
Accept)
value= SF16(uplink)-> PS64
value= SF16(downlink)-> PS128
Request)
xt Accept)
elease)
Complete)
)
t)
DPCCH_Power_offset CPICH_RSCP PCPICH Power UL Interference
-96 -80 33 -107
-96 -70 33 -107
_Power_offset is configured by RNC and delivered to UE in RRC Connection Setup.
Cellid=bin2dec(0111011110010010)=30610
0001011)=11 and Cellid=bin2dec(0111011110010010)=30610
UL DPCCH Initial Power
-16
-26
Click to return to main page
L3 Messages - PS(H
UE NodeB
Start Rx
L1 Synchonization
RRC:Measurement Control
PS Session
n Request (RACH)
on Setup (FACH)
7.NBAP:Synchonization Indicator
de Command
de Completed
arer Setup
Setup Complete
ent Control
PS Session Established
Report (e1d)
configuration (DCCH)
rer Release
lease Completed
shed
HSDPA's Servin
UE in idle mode intitiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling connecti
CTION REQUEST message from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or re
specific algorithm. If accepting the request, the RRM module further determines whether to set up the RRC connection on a Dedicated Cha
(CCH),based on a specific RRM algorithm. Typically, an RRC connection is set up on the DCH.
bed as follows:
ECTION REQUEST message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.
C connection request and the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Rad
),radio resources, and L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting
ources required for an RRC connection.
ADIO LINK SETUP RESPONSE message to the SRNC after successfully preparing the resources.
otocol to set up the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is
b interface only.
NNECTION SETUP message to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocate
chronization. NodeB sends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state
ECTION SETUP COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The messag
n setup procedure ends.
connection request cannot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message
reason in the message
send Activate PDP context request message to RNC. PDP Context Activation is performed when the UE initiates a packet call setup. The U
that enables the user to transmitt and receive data while moving within a PLMN. and starts the PDP context activation procedure used to s
rminal connected to a UE and a GGSN. PDP contexts deal with allocation of IP addresses to the UE and Quality of Service, QoS, paramet
the SGSN in order to realize the air interface connection. At the end the UE has an IP address NSAPI (Network layer Service Access Point
associated to IMSI.
ynamically or statistically. If allocated dynamically, this significantly reduces the total number of IP addresses required per PLMN. Support o
hen accesing secure networks that use the calling IP address as a form of security check. The support of
erentiate GPRS services.
he home PLMN or the Visitor PLMN is used, it is the responsibility of the GGSN to allocate and release the dynamic PDP address.
bed as follows:
on by using the Service Request (Service Type=Data) message. After the RR setup completion the UE asks for initial direct transfer to the s
h the SGSN and transfers the initial service request (Authentication and ciphering may performed depends on operator's setting)
P Context Request (NSAPI, TI(Teardown Indication), PDP Type, Address, APN (Access Point Name), QoS (Quality of Service) Requested,
The UE shall use PDP Address to indicate whether it requires the use of a static PDP address or whether it requires the use of a dynamic P
gnment Request message to the RNC to establish a RABs
opriate radio bearer In WCDMA, RAB setup is done by the RAB Assignment procedure
nment Response message to the SGSN
e PDP Context Request using PDP Type (optional), PDP Address, APN (Access Point Name (optional) provided by the UE and the PDP co
te PDP Context Request message to the affected GGSN. Access Point Name shall be the APN Network Identifier of the APN. The GGSN
and optionally to activate a service for this APN
y in its PDP context table and generates a Charging Id. The new entry allows the GGSN to route PDP PDUs (Policy Decision Point Protoco
network, and to start charging
layer Service Access Point Identifier, NSAPI along with the GGSN address in its PDP context and informs the UE via RNC that the PDP C
Packet flow Id based on QoS Negotiated, and returns an Activate PDP Context Accept message to the UE. The SGSN is now able to route
t charging
E send Deactivate PDP context request message to RNC. A PDP Context Deactivation is performed when the UE terminates a packet call.
Active. After the PDP Context deactivation procedure the state becomes Packet Mobility Management Connected.The RAB will be release
activation may be initiated by a:UE procedure,SGSN procedure,GGSN procedure
bed as follows:
P Context Request (TI, Teardown Indication) message to the SGSN via the RNC
P Context Request (TEID, NSAPI, Teardown Indication) message to the GGSN. If Teardown Indication was included by the UE in the Deac
s PDP address by including Teardown Indication in the Delete PDP Context Request message
ontext(s) and returns a delete PDP Context Response (TEID) message to the SGSN. The Delete PDP Context messages are sent over the
e PDP Context Accept (TI) message to the UE via the RNC
er release is done by the RAB Assignment procedure
n RNC and SGSN is released. At GPRS detach, all PDP contexts for the UE are implicitly deactivated
procedure is performed to release the signaling connection and all radio bearers between UE and the UTRAN
n RAB is released,the SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does
RRC connection release procedure.
bed as follows: based on the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: releas
needs to be released after a successful outgoing call,, the RRC connection on the DCH is released and if
,the RRC connection on the CCH is released)
RRC connection.
DCH and allocates the Radio
to the NodeB, requesting the NodeB to
ired per PLMN. Support of static IP address allocation enables subscribers to provide their own IP
ded by the UE in the Deactivate PDP Context Request message, then the SGSN deactivates all
release procedure: release of an RRC connection from DCH and release of an RRC connection
ssage by the UE. The RRC SNs of these messages are the same. The number of retransmissions
NodeB.
value=hex2dec(7594)= 30100
value=(-24+ (37/2))=-5.5 dB
value= HSDPA Release5
value=hex2dec(7594)= 30100
value=UE capable to support FDD , not TDD
Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000000010001010100101111 => RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(0001010100101111)=5423
value= SF256(downlink)
value= HSDPA Serving Cell's Primary SC = 30
value= SF256(downlink)
Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000000010001010100101111 => RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(0001
Accept)
value= PrimarySC=30, no longer a HSDPA serving cell ( HSDPA Serving Cell Change)
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=0000000000010001000111011100=> RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(00010
H)
equest)
Accept)
ase)
omplete)
DPCCH_Power_offset CPICH_RSCP PCPICH Power UL Interference
-96 -80 33 -107
-96 -70 33 -107
_Power_offset is configured by RNC and delivered to UE in RRC Connection Setup.
bin2dec(0001010100101111)=5423
mmercial UE can only monitor up to 4 HS-SCCH channels simultaneously. So one cell only configure up to 4 HS-SCCH channels
0000001)=1 and Cellid=bin2dec(0001010100101111)=5423
Serving Cell Change)
ng Cell Change)
0000001)=1 and Cellid=bin2dec(0001000111011100)=4572
UL DPCCH Initial Power
-16
-26
figure up to 4 HS-SCCH channels
Click to return to main page
L3 Messages - PS(H
UE NodeB
Start Rx
L1 Synchonization
RRC:Measurement Control
PS Session
n Request (RACH)
on Setup (FACH)
7.NBAP:Synchonization Indicator
de Command
de Completed
arer Setup
Setup Complete
ent Control
PS Session Established
Report (e1d)
configuration (DCCH)
rer Release
lease Completed
shed
HSPA's Serving
UE in idle mode intitiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling connecti
CTION REQUEST message from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or re
specific algorithm. If accepting the request, the RRM module further determines whether to set up the RRC connection on a Dedicated Cha
(CCH),based on a specific RRM algorithm. Typically, an RRC connection is set up on the DCH.
bed as follows:
ECTION REQUEST message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.
C connection request and the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Rad
),radio resources, and L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting
ources required for an RRC connection.
ADIO LINK SETUP RESPONSE message to the SRNC after successfully preparing the resources.
otocol to set up the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is
b interface only.
NNECTION SETUP message to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocate
chronization. NodeB sends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state
ECTION SETUP COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The messag
n setup procedure ends.
connection request cannot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message
reason in the message
send Activate PDP context request message to RNC. PDP Context Activation is performed when the UE initiates a packet call setup. The U
that enables the user to transmitt and receive data while moving within a PLMN. and starts the PDP context activation procedure used to s
rminal connected to a UE and a GGSN. PDP contexts deal with allocation of IP addresses to the UE and Quality of Service, QoS, paramet
the SGSN in order to realize the air interface connection. At the end the UE has an IP address NSAPI (Network layer Service Access Point
associated to IMSI.
ynamically or statistically. If allocated dynamically, this significantly reduces the total number of IP addresses required per PLMN. Support o
hen accesing secure networks that use the calling IP address as a form of security check. The support of
erentiate GPRS services.
he home PLMN or the Visitor PLMN is used, it is the responsibility of the GGSN to allocate and release the dynamic PDP address.
bed as follows:
on by using the Service Request (Service Type=Data) message. After the RR setup completion the UE asks for initial direct transfer to the s
h the SGSN and transfers the initial service request (Authentication and ciphering may performed depends on operator's setting)
P Context Request (NSAPI, TI(Teardown Indication), PDP Type, Address, APN (Access Point Name), QoS (Quality of Service) Requested,
The UE shall use PDP Address to indicate whether it requires the use of a static PDP address or whether it requires the use of a dynamic P
gnment Request message to the RNC to establish a RABs
opriate radio bearer In WCDMA, RAB setup is done by the RAB Assignment procedure
nment Response message to the SGSN
e PDP Context Request using PDP Type (optional), PDP Address, APN (Access Point Name (optional) provided by the UE and the PDP co
te PDP Context Request message to the affected GGSN. Access Point Name shall be the APN Network Identifier of the APN. The GGSN
and optionally to activate a service for this APN
y in its PDP context table and generates a Charging Id. The new entry allows the GGSN to route PDP PDUs (Policy Decision Point Protoco
network, and to start charging
layer Service Access Point Identifier, NSAPI along with the GGSN address in its PDP context and informs the UE via RNC that the PDP C
Packet flow Id based on QoS Negotiated, and returns an Activate PDP Context Accept message to the UE. The SGSN is now able to route
t charging
E send Deactivate PDP context request message to RNC. A PDP Context Deactivation is performed when the UE terminates a packet call.
Active. After the PDP Context deactivation procedure the state becomes Packet Mobility Management Connected.The RAB will be release
activation may be initiated by a:UE procedure,SGSN procedure,GGSN procedure
bed as follows:
P Context Request (TI, Teardown Indication) message to the SGSN via the RNC
P Context Request (TEID, NSAPI, Teardown Indication) message to the GGSN. If Teardown Indication was included by the UE in the Deac
s PDP address by including Teardown Indication in the Delete PDP Context Request message
ontext(s) and returns a delete PDP Context Response (TEID) message to the SGSN. The Delete PDP Context messages are sent over the
e PDP Context Accept (TI) message to the UE via the RNC
er release is done by the RAB Assignment procedure
n RNC and SGSN is released. At GPRS detach, all PDP contexts for the UE are implicitly deactivated
procedure is performed to release the signaling connection and all radio bearers between UE and the UTRAN
n RAB is released,the SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does
RRC connection release procedure.
bed as follows: based on the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: releas
needs to be released after a successful outgoing call,, the RRC connection on the DCH is released and if
,the RRC connection on the CCH is released)
RRC connection.
DCH and allocates the Radio
to the NodeB, requesting the NodeB to
ired per PLMN. Support of static IP address allocation enables subscribers to provide their own IP
ded by the UE in the Deactivate PDP Context Request message, then the SGSN deactivates all
release procedure: release of an RRC connection from DCH and release of an RRC connection
ssage by the UE. The RRC SNs of these messages are the same. The number of retransmissions
NodeB.
value=hex2dec(03EA)= 1002
value=(-24+ (39/2))=-4.5 dB
value=hex2dec(03EA)= 1002
value=UE capable to support FDD , not TDD
value=MaxAllowedULTxPower=24 dBm
Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000011001100000010100101001 => RNCid=bin2dec(000001100110)=102 and Cellid=bin2dec(0000010100101001)=1321
H)
equest)
Accept)
ase)
omplete)
Default Constant DPCCH_Power_offset CPICH_RSCP PCPICH Power
-22 -94 -80 33
-22 -94 -70 33
Note :DPCCH_Power_offset is configured by RNC and delivered to UE in RRC Connection Setup.
)=102 and Cellid=bin2dec(0000010100101001)=1321
PA serving cell ( HSPA Serving Cell Change)
erving cell ( HSPA Serving Cell Change)
UL Interference UL DPCCH Initial Power
-105 -14
-105 -24
Click to return to main page
RRC:Measurement Control
RRC:Measurement Control
RRC:Measurement Control
RRC:Measurement Control
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 a
up or deleted.
L3 Messages - Intra-Fre
UE NodeB2
Intra-Frequency S
RRC:M
RRC:Mea
"or"
RRC:Mea
ALCAP: Iub User Plane Setup
1.RRC: Ac
2.RRC: Active S
RRC:M
RRC:Mea
1.RRC: Ac
2. RRC: Active S
ALCAP: Iub User Plane Release
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 a
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
up or deleted.
essages - Intra-Frequency Soft Handover Procedure
NodeB1
RRC:Measurement Control
RRC:Measurement Control
RRC:Measurement Control
RRC:Measurement Control
RRC:Measurement Control
2.QAAL2 Establish Co
RRC:Measurement Control
S-RNC
Measurement Control: is used to notify the UE o
conditions.
Decision to
setup new Radio Link Addition Procedure is performed to
radio link
Triggering Conditions: The CRNC sends a RAD
Radio Link Addition
The procedure of radio link setup is described
1.The CRNC sends a RADIO LINK ADDITION RE
the parameters given in the message.
2.The NodeB sends a response message to the C
-If all the requested radio links are added, the
Active Set Update
RESPONSE message.
-If any radio link fails to be added, the NodeB s
Measurement Control
& Measurement Report
Decision to
setup new The radio link setup procedure (intra-RNC han
radio link
Triggering Conditions: The CRNC sends a RAD
The procedure of radio link setup is described
Radio Link Setup 1.The CRNC sends a RADIO LINK SETUP REQU
parameters given in the message.
2.The NodeB sends a response message to the C
-If the radio link is set up, the NodeB saves the
up -If the radio link fails to be set up, the NodeB s
Measurement Control
& Measurement Report
Decision to
setup new
radio link
Decision to
setup new
radio link
Measurement Control
& Measurement Report
Decision to
delete old
radio link
Report: the UE continue measure the radio link condition of serving and neighbour cell and when the measurement reporting criterias are m
eport is also can be sent in periodic mode.
dition Procedure is performed to add one or more radio links towards a UE.
t update procedure is performed to update the active set of radio links between theUE and the UTRAN.
ditions: The active set update procedure can be triggered in either of the following conditions: Radio link addition or Radio link deletion
is described as follows:
nds an ACTIVE SET UPDATE message to the UE. If a radio link needs to be added, the message indicates radio link addition. If a radio lin
or deletes the radio links according to the Radio Link Addition Informationor Radio Link Removal Information IE contained in the ACTIVE S
a response message to the SRNC.
eleting the radio links successfully, the UE sends an ACTIVE SETUPDATE COMPLETE message on the DCCH by using Acknowledged
SET UPDATE message contains the configuration not supported by the UE or if the active set does not contain the radio links spe
CTIVE SET UPDATE FAILURE message.
eletion Procedure is performed to release resources in a NodeB for one or more established radio links towards a UE
Report: the UE continue measure the radio link condition of serving and neighbour cell and when the measurement reporting criterias are m
eport is also can be sent in periodic mode.
setup procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed to set up a radio link in an SRNC-controlled Node
ane setup procedure is performed to set up bearers for data transmission on the Iub interface
ditions: The Iub user plane setup procedure can be triggered in one of the following conditions:
transport channels are setup
d transport channels are setup
is described as follows:
es the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST messageto the NodeB.
ses the ALCAP protocol to send a response message to the CRNC.
transport bearers are set up, the NodeB sends a QAAL2 ESTABLISH CONFIRM message.
ransport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH RELEASE CONFIRM message.
estoration procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed for a NodeB to notify the CRNC that the up
ditions: The nodeB detect UL signals from the UE. That is ,the NodeB finishs UL synchronization with the UE
UL synchronization with the UE, the NodeB sends a RADIO LINK RESTORE INDICATION message to the CRNC.
t update procedure is performed to update the active set of radio links between theUE and the UTRAN.
ditions: The active set update procedure can be triggered in either of the following conditions: Radio link addition or Radio link deletion
is described as follows:
nds an ACTIVE SET UPDATE message to the UE. If a radio link needs to be added, the message indicates radio link addition. If a radio lin
or deletes the radio links according to the Radio Link Addition Informationor Radio Link Removal Information IE contained in the ACTIVE S
a response message to the SRNC.
eletion Procedure is performed to release resources in a NodeB for one or more established radio links towards a UE
plane release procedure is performed to release data transport bearers from the Iub interface.
ditions: The transport channels on the Iub user plane need to be removed
is described as follows:
es the ALCAP protocol to send a QAAL2 RELEASE REQUEST messageto the NodeB.
ses the ALCAP protocol to send a response message to the CRNC.
transport bearers are released, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the release.
ransport bearer fails to be released, the NodeB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause
o main page
Measurement Control: is used to notify the UE of the objects to be measured, neighbor cell list,
conditions.
Measurement Report: the UE continue measure the radio link condition of serving and neighbo
Measurement report is also can be sent in periodic mode.
nt Control
ment Report
The radio link setup procedure for inter-RNC handover is performed to set up a radio link in a
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.
The radio link setup procedure for inter-RNC handover is performed to set up a radio link in a
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 accordingto th
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 IE con
-If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE messag
Setup 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 FAILUREmessage
ne Setup
nk Restore Indication The Iub user plane setup procedure is performed to set up bearers for data transmission on th
Triggering Conditions: The Iub user plane setup procedure can be triggered in one of the
1. The common transport channels are setup
2. The dedicated transport channels are setup
ne Setup The procedure is described as follows:
1.The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST messageto the
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 CONFIR
-If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH RE
Restore Indication
pdate The radio link restoration procedure for inter-RNC handover is performed for a NodeB to no
Triggering Conditons: The NodeB detects UL signals from the UE. That is, the NodeB finishes
The Iur user plane setup procedure is performed to set up bearers for data transmission on th
ne release
The radio link deletion procedure is performed to release resources in a NodeB for one or mor
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 receivin
2.The NodeB sends a response message to the CRNC.
-If all the radio links are deleted, the NodeB sends a RADIO LINK DELETION RESPONSE me
-If any radio link fails to be deleted, the NodeB sends a RADIO LINK DELETIONRESPONSE
The Iub user plane release procedure is performed to release data transport bearers from the
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 N
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 RELEASECONFIR
-If an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECO
The Iur user plane release procedure is performed to releaseto release data transport bearers
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 N
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 RELEASECONFIR
-If an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECO
parameters.When measurement conditions are changed, the RNC notifies the UE of new
urement reporting criterias are met, the UE reports the results to the RNC as an event. The
reserves the necessary resources and configures the new radio link or links according to
the RADIO LINK ADDITION REQUEST message andsends a RADIO LINK ADDITION
s radio link addition. If a radio link needs to be deleted, themessage indicates radio link
owards a UE
urement reporting criterias are met, the UE reports the results to the RNC as an event. The
serves the necessary resources and configures the new radio link according to the
ge.
B to notify the CRNC that the uplink synchronization of one or more radio links is achieved
UE
e CRNC.
s radio link addition. If a radio link needs to be deleted, themessage indicates radio link
e release.
cates the failure cause
be measured, neighbor cell list, report method, and event parameters.When measurement conditions are changed, the RNC notifies the U
ondition of serving and neighbour cell and when the measurement reporting criterias are met, the UE reports the results to the RNC as an e
P REQUEST message
to the DRNC.
to the target NodeB.
arers for data transmission on the Iub interface
is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is achieved or re-achieved.
e triggered in either of the following conditions: Radio link addition or Radio link deletion
E. If a radio link needs to be added, the message indicates radio link addition. If a radio link needs to be deleted, themessage indicates rad
Link Addition Informationor Radio Link Removal Information IE contained in the ACTIVE SET UPDATE message.
nds an ACTIVE SETUPDATE COMPLETE message on the DCCH by using Acknowledged Mode (AM)Radio Link Control (RLC).
ation not supported by the UE or if the active set does not contain the radio links specified by the Radio Link Removal Information
urces in a NodeB for one or more established radio links towards a UE.
age to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the message.
Control (RLC).
k Removal Information IE, the UE
e.
Click to return to main page
RRC:Measurement Control
RRC:Measurement Report (e1a)
RRC:Measurement Report (e1b)
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=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=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
>>"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=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=Event1c is triggered
value=To replace Cell Primary Scrambling Code=56 by Cell Primary Scrambling Code=106
II)
n Active Set)
y Scrambling Code=106
Click to return to main page
RRC:Measurement Control
Stop Rx/Tx
ALCAP:
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
up or deleted.
L3 Messages - Intra-Freq
UE NodeB2
Intra-Frequency H
RRC:M
RRC:Me
Start Rx
ALCAP: Iub User Plane Setup
Start Tx
1. RRC:Physical C
2. RRC:Physical Chann
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 a
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
or deleted.
essages - Intra-Frequency Hard Handover Procedure
*Source NodeB2 *Target
RRC:Measurement Control
Start Rx
Start Tx
procedure is performed on the Iub interface after radio links are set
RRC:Measurement Control
1.QAAL2 Establish Re
2.QAAL2 Establish C
1.QAAL2 Release Re
2.QAAL2 Release Co
S-RNC
Measurement Control is used to n
notifies the UE of new conditions.
Decision to
setup new
radio link
The radio link setup procedure (i
Physical Reconfiguration
>>Measurement Control&Report D
Measurement Control
& Measurement Report
Decision to
setup new radio
link
Physical Reconfiguration
Decision to
delete old radio
link
ement Report, the UE continue measure the radio link condition of serving and neighbour cell and when the measurement reporting criteria
as an event. The Measurement report is also can be sent in periodic mode.
o link setup procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed to set up a radio link in an SRNC-controlled
RNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB reserves the necessary res
g to the parameters given in the message.
odeB 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 c
ST message and sends a RADIOLINK SETUP RESPONSE message.If the radio link fails to be set up, the NodeB sends a RADIO LINK SE
the failure cause.
user plane setup procedure is performed to set up bearers for data transmission on the Iub interface
o link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover)is performed for a NodeB to notify the CRNC that the
ks is achieved or re-achieved
forming UL synchronization with the UE, the NodeB sends a RADIO LINK RESTOREINDICATION message to the CRNC.
sical channel reconfiguration procedure is performed to set up, reconfigure, or releasea physical channel
cedure is described as follows:
RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physical channel.
E saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.The UE sends a response message to the SRNC.
essfully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION message, the UE sends a PHYS
ETE message on the uplink DCCH by using AM RLC
g to reconfigure the physical channels specified by the PHYSICAL CHANNELRECONFIGURATION message, the UE restores the configur
ation and sends a PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH by using AM RLC. The value of the Failu
EL RECONFIGURATION FAILURE message is "physical channel failure".
o link deletion procedure is performed to release resources in a NodeB for one or more established radio links towards a UE.
cedure is described as follows:
RNC sends a RADIO LINK DELETION REQUEST message to the NodeB. After receiving the message, the NodeB deletes the radio links s
odeB sends a response message to the CRNC.lf all the radio links are deleted, the NodeB sends a RADIO LINK DELETION RESPONSE m
radio link fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The Criticality Diagnostics field in the me
user plane release procedure is performed to release data transport bearers from the Iubinterface.
cedure is described as follows:
RNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST messageto the NodeB.
odeB uses the ALCAP protocol to send a response message to the CRNC.
ub data transport bearers are released, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the release.
b data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause
nt Control&Report Description Measurement Report, the UE continue measure the radio link condition of serving and
report is also can be sent in periodic mode.
t Control
ent Report
The radio link setup procedure for inter-RNC handover is performed to set up a radio link
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 accor
->If the radio link is set up, the NodeB saves the value of the Configuration GenerationID
->If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILUREm
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 RESPONSEmessag
->If the radio link fails to be set up, the DRNC sends a RADIO LINK SETUP FAILURE m
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 accor
->If the radio link is set up, the NodeB saves the value of the Configuration GenerationID
->If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILUREm
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 RESPONSEmessag
etup ->If the radio link fails to be set up, the DRNC sends a RADIO LINK SETUP FAILURE m
Setup
The Iub user plane setup procedure is performed to set up bearers for data transmissio
Restore Indication The procedure is described as follows:
1.The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST messa
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 C
->If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLIS
e Setup
The radio link restoration procedure for inter-RNC handover is performed for a NodeB
1.After performing UL synchronization with the UE, the NodeB sends a RADIO LINKRES
Restore Indication 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 transmissio
The procedure is described as follows:
onfiguration
1.The SRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST messa
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 ESTABLISHCO
->If an Iur data transport bearer fails to be set up, the DRNC sends a QAAL2 ESTABLIS
e release
The radio link deletion procedure is performed to release resources in a NodeB for one
e release
The Iub user plane release procedure is performed to release data transport bearers fr
The Iur user plane release procedure is performed to release data transport bearers fro
B reserves the necessary resources and configures the new radio link
o the CRNC.
physical channel.
nse message to the SRNC.
ssage, the UE sends a PHYSICAL CHANNELRECONFIGURATION
the release.
dicates the failure cause
cts to be measured, neighbor cell list, report method, and event parameters.When measurement conditions are changed, the RNC notifies
link condition of serving and neighbour cell and when the measurement reporting criterias are met, the UE reports the results to the RNC a
ver is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is achieved or re-achieved.
y the PHYSICAL CHANNELRECONFIGURATION message, the UE restores the configuration to the old physicalchannel configuration and
y using AM RLC. The value of the Failure cause IE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE message is "ph
resources in a NodeB for one or more established radio links towards a UE.
message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the message.
e message.
RRC:Measurement Control
RRC:Measurement Control
RRC:Measurement Report
RRC:Measurement Report
1.RRC: Physical Channel Reconfiguration (DCCH
Stop Rx/Tx
ALCAP:
1.The radio link setup procedure shown in the figure applies when the source and target cellsof the handover are cont
different NodeBs. If the source and target cells arecontrolled by the same NodeB, the radio link setup procedure shou
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
up or deleted.
L3 Messages - Inter-Freq
UE NodeB2
Inter-Frequency H
Start Rx
Start Tx
1. RRC:Physical C
2. RRC:Physical Chann
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 a
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
or deleted.
essages - Inter-Frequency Hard Handover Procedure
*Source NodeB2 *Target
RRC:Measurement Control
RRC:Measurement Control
RRC:Measurement Report
RRC:Measurement Report
Start Rx
Start Tx
es when the source and target cellsof the handover are controlled by
ed by the same NodeB, the radio link setup procedure should be
o link restoration procedure is excluded.
d NodeB 2 is the target NodeB.
procedure is performed on the Iub interface after radio links are set
1.QAAL2 Establish Re
2.QAAL2 Establish C
1.QAAL2 Release Re
2.QAAL2 Release Co
S-RNC
Measurement Control is used
notifies the UE of new condition
up
Decision to
delete old radio
link
Decision to setup
new radio link
Physical Reconfiguration
Decision to
delete old radio
link
1.NBAP:Radio Link Deletion Req
Radio Link Deletion
Stop Rx/Tx
Measurement Report, the UE continue measure the radio link condition of serving and neighbour cell and when the measurement re
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 periods (g
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 an SRN
1.The CRNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB reserves the
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 Gen
message and sends a RADIOLINK SETUP RESPONSE message.If the radio link fails to be set up, the NodeB sends a RADIO LINK
cause.
The Iub user plane setup procedure is performed to set up bearers for data transmission on the Iub interface
The radio link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover)is performed for a NodeB to notify the C
is achieved or re-achieved
After performing UL synchronization with the UE, the NodeB sends a RADIO LINK RESTOREINDICATION message to the CRNC.
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 chann
2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.The UE sends a response message t
->If successfully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION message, the UE s
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 restore
and sends a PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH by using AM RLC. The value of the Failu
RECONFIGURATION FAILURE message is "physical channel failure".
The radio link deletion procedure is performed to release resources in a NodeB for one or more established radio links towards a UE
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 deletes th
2.The NodeB sends a response message to the CRNC.lf all the radio links are deleted, the NodeB sends a RADIO LINK DELETION
3. lf any radio link fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The Criticality Diagnostics
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 release.
->lf an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECONFIRM message that indicates the failu
o Link Deletion
ur cell and when the measurement reporting criterias are met, the UE reports the results to the RNC
rs. It is used to create idle periods (gaps) in the transmission during which neighbour cells
he message, the NodeB reserves the necessary resources and configures the new radio link
es the value of the Configuration Generation ID IE contained in the RADIO LINK SETUP REQUEST
up, the NodeB sends a RADIO LINK SETUP FAILURE message. The message contains the failure
e Iub interface
e NodeB.
a transport bearers are set up, the NodeB sends a QAAL2 ESTABLISH CONFIRM message.If an
CONFIRM message.
performed for a NodeB to notify the CRNC that the uplink synchronization of one or more radio links
GURATION message, the UE restores the configuration to the old physicalchannel configuration
using AM RLC. The value of the Failure cause IE contained in the PHYSICAL CHANNEL
g the message, the NodeB deletes the radio links specified by the message.
eB sends a RADIO LINK DELETION RESPONSE message.
message. The Criticality Diagnostics field in the message indicates the failure cause.
ubinterface.
NodeB.
cedure is performed to set up bearers for data transmission on the Iub interface
as follows:
cedure for inter-RNC handover is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is ac
nization with the UE, the NodeB sends a RADIO LINKRESTORE INDICATION message to the DRNC.
LINK RESTORE INDICATION message to the SRNC.
cedure is performed to set up bearers for data transmission on the Iur interface
as follows:
as follows:
AL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physical channel.
UE, Radio Bearer (RB), transport channel, and physical channel.The UE sends a response message to the SRNC.
the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION message, the UE sends a PHYSICAL CHANNELRECO
hysical channels specified by the PHYSICAL CHANNELRECONFIGURATION message, the UE restores the configuration to the old physic
E message on the DCCH by using AM RLC. The value of the Failure cause IE contained in the PHYSICAL CHANNEL RECONFIGURATIO
dure is performed to release resources in a NodeB for one or more established radio links towards a UE.
as follows:
LINK DELETION REQUEST message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the messa
e message to the CRNC.
ed, the NodeB sends a RADIO LINK DELETION RESPONSE message.
leted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The Criticality Diagnostics field in the message indicates the fai
as follows:
protocol to send a QAAL2 RELEASE REQUEST messageto the NodeB.
protocol to send a response message to the CRNC.
ers are released, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the release.
er fails to be released, the NodeB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause
ocedure is performed to release data transport bearers from the Iur interface
as follows:
protocol to send a QAAL2 RELEASE REQUEST messageto the DRNC.
protocol to send a response message to the SRNC.
ers are released, the DRNC sends a QAAL2 RELEASECONFIRM message to confirm the release.
r fails to be released, the DRNC sends a QAAL2 RELEASECONFIRM message that indicates the failure cause.
The NodeB reports the radio link setup result to the DRNC.
QUEST message and sends a RADIOLINK SETUP RESPONSE message.
el.
o the SRNC.
ends a PHYSICAL CHANNELRECONFIGURATION COMPLETE message on the uplink DCCH
es the configuration to the old physicalchannel configuration and sends a PHYSICAL CHANNEL
CAL CHANNEL RECONFIGURATION FAILURE message is "physical channel failure".
E.
ure cause
re cause.
Click to return to main page
L3 Messag
UE NodeB
Inter-RA
RRC:Measurement Control
RRC:Measurement Control
RRC:Measurement Report
RRC:Measurement Report
7.RRC: Handover from UTRAN Command
1.This figure presents only a brief of the signaling between the MSC server and the MSC(GSM) and that between the M
(GSM) and the BSC (GSM).
2.The SRNC sends a HANDOVER FROM UTRAN COMMAND message to the UE. The message contains the RAB ID,
activation time, the GSM frequency, and the GSM information in bit strings.
L3 Messag
UE NodeB
Inter-RA
9.Int
1.This figure presents only a brief of the signaling between the MSC server and the MSC(GSM) and that between the M
(GSM) and the BSC (GSM).
2.After receiving a RADIO LINK RESTORE INDICATION message, the RNC sends a RELOCATION DETECT message
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 fa
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
3.After the UE is handed over, it sends a HANDOVER TO UTRAN COMPLETE message to the RNC. If the handover fa
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
L3 Messages - Inter-RAT Handover Procedure
S-RNC
RRC:Measurement Control
RRC:Measurement Control
RRC:Measurement Report
RRC:Measurement Report
Decision to
HO to GSM
cell
C: Handover from UTRAN Command
9.Handover Completed
edure ,
ng between the MSC server and the MSC(GSM) and that between the MSC
RAN COMMAND message to the UE. The message contains the RAB ID, the
SM information in bit strings.
edure ,
ng between the MSC server and the MSC(GSM) and that between the MSC
5.Prepare Handover
Response
6.RANAP:Relocation Command
9.Handover Completed
2.Prepare Handover
3.RANAP: Relocation Request
6.RANAP:Relocation Request Acknowledge
7.Prepare Handover
Response
11.RANAP:Relocation Detect
18.RANAP:Relocation
Complete
19.Send End Signal
Request
BSC2
G
Measurement Control
& Measurement Report
3.Handover Request
10.Handover Complete
Iu release
BSC2
G
1.Handover Required
8.Handover Command
9.Handover Complete
UE Capability Enquiry
20.Clear Command
21.Clear Complete
Measurement Control is used to notify the UE of the objects to be measured, neighbor cell lis
Report (Inter-RAT) conditions.
Measurement Report, the UE continue measure the radio link condition of serving and neighb
The Measurement report is also can be sent in periodic mode.
Compressed Mode was introduced to WCDMA to allow inter-frequency and Inter-RAT Hando
another frequency can be made.
uration
The relocation preparation procedure is performed to prepare resources for relocation of the
1.The SRNC sends a RELOCATION REQUIRED message to the CN. The message contains
and target CI,LAC.
2.The CN interacts with the target RNC or the target network system, such as the GSM system
3.The CN sends a response message to the SRNC.
->If the target RNC or the target network system prepares the relevant resources successfully,
L3 information IE, which carries the information about the relevant resources allocated by the t
->If the resources partially or totally fail to be allocated, the CN sends a RELOCATIONPREPA
1. The SRNC sends the 3G MSC a RANAP message "Relocation Required" if the condition of
2. As indicated in the received message,the 3G MSC forwards this request to the 2G MSC on
Handover"
3. The 2G MSC forwards the request to the BSC. The message shown in the figure is for refer
4. The BSC responds to this request. The message shown in the figure is for reference only an
5. Once the initial procedures are completed in the 2G MSC/BSS,the 2G MSC returns a MAP/
6. The 3G MSC sends the SRNC a RANAP message "Relocation Command"
7. The SRNC send the UE and RRC message "Handover from UTRAN" through the existing R
several other systems
8. The BSC performs handover detection. The figure does not show such procedures as GSM
reference and is subject to the actual conditon of GSM
9. The UE send the BSC a "Handover Complete" message
10. The BSC sends the MSC a 'Handover Complete" message. The message shown in the fig
GSM
11. After detecting the UE in the coverage area of the GSM,the MSC sends the CN a MAP/E m
12. The CN sends the former SRNC and "Iu Release Command" message , requesting the for
13. After the bearer resource is related in the UMTS, the former SRNC sends the CN an "Iu Re
14. After the call ends, the CN sends the MSC a MAP/E message "Send End Signal Response
several other systems
8. The BSC performs handover detection. The figure does not show such procedures as GSM
reference and is subject to the actual conditon of GSM
9. The UE send the BSC a "Handover Complete" message
10. The BSC sends the MSC a 'Handover Complete" message. The message shown in the fig
GSM
11. After detecting the UE in the coverage area of the GSM,the MSC sends the CN a MAP/E m
12. The CN sends the former SRNC and "Iu Release Command" message , requesting the for
13. After the bearer resource is related in the UMTS, the former SRNC sends the CN an "Iu Re
14. After the call ends, the CN sends the MSC a MAP/E message "Send End Signal Response
The Iu release procedure is performed for the CN to release an Iu connection and all the UTR
2.The SRNC releases the related UTRAN resources and then sends an IU RELEASE COMPL
The radio link deletion procedure is performed to release resources in a NodeB for one or m
The procedure is described as follows:
1.The CRNC sends a RADIO LINK DELETION REQUEST message to the NodeB. After receiv
2.The NodeB sends a response message to the CRNC.
->If all the radio links are deleted, the NodeB sends a RADIO LINK DELETION RESPONSE m
->If any radio link fails to be deleted, the NodeB sends a RADIO LINK DELETIONRESPONSE
The relocation resource allocation procedure is performed to allocate resources from the ta
The relocation resource allocation procedure can be triggered in either of the followingconditio
1. During an SRNS relocation, the CN applies for resources from the target RNC
2. During an inter-RAT CS handover from GSM to WCDMA, the CN applies for resources from
The radio link setup procedure (intra-RNC handover or GSM to WCDMA CS handover) isper
The radio link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover)
re-achieved
After performing UL synchronization with the UE, the NodeB sends a RADIO LINK RESTORE
The security mode control procedure is performed to configure or reconfigure one or both of
algorithm or the integrity protection algorithm has changed
The procedure is described as follows:
1.Through a SECURITY MODE COMMAND message sent to the UE, the SRNC starts or reco
Signaling Radio Bearers (SRBs).
2.The UE sends a response message to the SRNC.
->If the UE completes configuring or reconfiguring the relevant parameters for one orboth of th
SRNC of the completion.
->If the SECURITY MODE COMMAND message contains neither Ciphering mode info IE nor I
MODE FAILURE message, indicating the failure of the security mode control procedure as we
The UTRAN mobility information procedure is performed for the network to allocate a newUT
inform the UE of mobility-related information such as timervalues and CN domain–related infor
link condition of serving and neighbour cell and when the measurement reporting criterias are met, the UE reports the results to the RNC a
de.
ter-frequency and Inter-RAT Handovers. It is used to create idle periods (gaps) in the transmission during which neighbour cells measurem
e to the CN. The message contains certain information such as relocation type, relocation cause, source PLMN, source LAC,source SAC, ta
the relevant resources successfully, the CN sends a RELOCATION COMMAND message when the preparation is complete. The message
elevant resources allocated by the target RNC or the target network system.
CN sends a RELOCATIONPREPARATION FAILURE message.
ws:
sage shown in the figure is for reference only and is subject to the actual conditon of the GSM
in the figure is for reference only and is subject to the actual conditon of the GSM
C/BSS,the 2G MSC returns a MAP/E message 'Prepare Handover Response"
ocation Command"
rom UTRAN" through the existing RRC connection. This message may include information from one or
not show such procedures as GSM BSS synchronization. The message shown in the figure is for
age. The message shown in the figure for reference only and is subject to the actual condition of the
M,the MSC sends the CN a MAP/E message "Send End Signal Request"
mand" message , requesting the former SRNC to release the allocated resource
rmer SRNC sends the CN an "Iu Release Complete" message
essage "Send End Signal Response"
se an Iu connection and all the UTRANresources related only to that Iu connection
the SRNC to initiate the Iu release procedure. The message indicates the cause for the release of the signaling connection.
ge, the CN will not send further RANAP connection-oriented messages on this particular connection.
resources in a NodeB for one or more established radio links towards a UE.
message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the message.
he target RNC. The message contains certain information, such as the IMSI of the UE, CN domain indicator, target cell identifier, encryptio
dRAB parameters.
on.
ELOCATION REQUEST ACKNOWLEDGE message. The message contains the radio resources and other parameters allocated to the UE
Identifier (U-RNTI), RAB, transport layer and physical layer information,chosen encryption algorithm, and chosen integrity protection algorith
he target RNC rejects the SRNS relocation for some reason, the target RNC sends a RELOCATION
SM to WCDMA CS handover) isperformed to set up a radio link in an SRNC-controlled NodeB for a UE
ssage to the NodeB. Afterr eceiving the message, the NodeB reserves the necessary resources and configures the new radio link accordin
he Configuration GenerationID IE contained in the RADIO LINK SETUP REQUEST message and sends a RADIO LINK SETUP RESPONS
DIO LINK SETUP FAILURE message. The message contains the failure cause.
r or GSM to WCDMA CS handover)is performed for a NodeB to notify the CRNC that the uplink synchronization of one or moreradio links is
uest a UE to transmit its capability information related to any radio access network so that the network can perform data configuration based
figure or reconfigure one or both of the ciphering algorithm and the integrity protection algorithm for a UE. The triggered conditon is when t
to the UE, the SRNC starts or reconfigures one or both of the ciphering and integrity protection configurations for theRBs or one CN doma
vant parameters for one orboth of the ciphering and integrity protection algorithms, the UE sends a SECURITYMODE COMPLETE messag
neither Ciphering mode info IE nor Integrity protection mode info IE or if each of the two IEs has inconsistent information, the UE sends a S
urity mode control procedure as well as the failure cause.
for the network to allocate a newUTRAN Radio Network Temporary Identifier (U-RNTI) or Cell Radio Network TemporaryIdentifier (C-RNTI
values and CN domain–related information
d by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MOBILITY INFORMATION CONFIRM message.
UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MOBILITY INFORMATIONFAILURE message, indicating the failure
ns are changed, the RNC notifies the UE of new
message.
he failure cause.
about UE capabilities.
M or UMRLC.
N CONFIRM message.
RE message, indicating the failure cause.
Click to return to main page
RRC:Measurement Control
RRC:Measurement Report (e2d)
RRC:Measurement Report (e2f)
RRC:Measurement Control
RRC:Measurement Report
RRC: Handover from UTRAN Command
Handover Completed
>>"Measurement Control and Measurement Report"
value= InterFreqCSThd2DEcN0=-14 dB
value= 0
value=2 dB ,Step: 0.5
value=320ms
value= InterFreqCSThd2FEcN0=-12 dB
value= 0
value=2 dB ,Step: 0.5
value=320ms
value=UE trigger Event2D to start Compressed Mode
CCH)
value=Compressed Mode Inforamtion
te (DCCH)
value=interRATMeasurement (RNC send mearuement control of InterRAT after enter Compressed Mode
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
d
f InterFrequency because
_INTERFREQ")
RAT after enter Compressed Mode)
nt Control (GSM900)
Click to return to main page
UE BSS S-RNC
UE Connected
UE Connected
19.Routing Area Update Accept
1.When the PS data volume is low, the UE may be in CELL_PCH, URA_PCH, or Cell_FACH state or when UE
perform a handover to GSM. The cell reselection is initiated with an SRNS CONTEXT REQUEST message se
When the UE in Idle ,URA_PCH.Cell_PCH or Cell_FACH states, the cell reselection procedure does not includ
2.After cell reselection to a GSM cell, the NodeB sends a RADIO LINK FAILURE INDICATION message becau
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 S
4.The SRNS context transfer is unnecessary to the procedure of inter-RAT PS handover from WCDMA to GSM
UE BSC S-RNC
1. Inter-RAT Handover
Decision
5
16.Routing Area Update Accept
19.Service Request
Update Request
UE Connected 3.SGSN Context Request
6.Security Functions
UE Connected C1
8.Forward Packets
9. Forward Packets
UE Connected
15. Upd
Update Complete
21.
2. BSS Packet Flow Context Procedure
PCH, URA_PCH, or Cell_FACH state or when UE in Idle state. Based on the parameters in the system information, the UE can initiate cell r
with an SRNS CONTEXT REQUEST message sent from the SGSN to SRNC.
es, the cell reselection procedure does not include the sub-procedires which marked with "UE Connected)
DIO LINK FAILURE INDICATION message because the UE stops the transmission towards the WCDMA cell.This message, however, is un
M.
s an IU RELEASE COMMAND message to the SRNC, if the Packet Data Protocol (PDP) context does not need to be transferred.
e of inter-RAT PS handover from WCDMA to GSM.
Update Request
3.SGSN Context Request
5.Security Functions
C1
7. Forward Packets
11. Inse
12. Upd
a Update Accept
C3
Update Complete
ce Request
C1
ntext Request
text Response
to be transferred.
C1
text Request
ext Response
Iu release
17. Update Location
1.The UE in Cell_DCH state, the UTRAN decides to initiate an inter-RAT handover in the PS domain be se
and the network
2. The UE sends a "Routing Area Update Request" message to the 2G SGSN. The update type in the mes
RAC and LAC of the cell to the received message before forwarding the message to a new 2G SGSN
3. The new 2G SGSN sends an "SGSN Context Request" message to the old 3G SGSN to obtain the MM
a timer. Otherwise, the old 3G SGSN respons with an error cause.
4. If the UE stay in connected mode before handover, the old 3G SGSN sends an "SRNS Context Reques
Response" message to the old 3G SGSN
ansfer 5. The old 3G SGSN sends an "SGSN Context Response" message to the 2G SGSN including the MM an
6. The security functions can be excuted
7. The new 2G SGSN sends an 'SGSN Context Acknowledge" message to the old 3G SGSN. This inform
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 data-fo
the old 3G SGSN
9. The old 3G SGSN tunnels the GTP PDUs to the new 2G SGSN. In the PDUs, the sequence number in t
10. the new 2G SGSN sends an "Update PDP Context Request" message to each related GGSN. Each G
message after updating it's PDP Context fields
11. The new 2G SGSN sends an "Update GPRS Location" message ,requesting the HLR to modify the SG
12. The HLR sends a "Cancel Location" message to the old 3G SGSN. the old 3G SGSN responds with a
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-forwarding timer
Release complete"
14. The HLR sends an "Insert Subscriber Data" message to the new 2G SGSN. The 2G SGSN constructs
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" messag
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 HLP. Th
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" message
- The HLR responds with an "Update Location Ack" message to the new VLR
16. If the association has to be established, the new 2G SGSN sens a 'Location Update Request" messag
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 HLP. Th
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" message
- 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 the 2G
19. The new 2G SGSN checks the presence of the MS in the new RA. If all checks area successful,the new
established between the new 2G SGSN and the UE. The 2G SGSN responds to the UE with a "Routing A
20. The UE acknowledge the new P-TMSI by returning a "Routing Area Update Complete" message, inclu
21. The new 2G SGSN sends a "TMSI Reallocation Complete" message to the new VLR if the UE confirm
22. The 2G SGSN and the BSS perform the "BSS Packet Flow Context" procedure
1.The GSM decides to perform an inter-RAT handover in PS domanin and stops the data transmission bet
2. The UE sends a "Routing Area Update Request" message to the 3G SGSN. The update type in the mes
update with IMSI attach. The SRNC adds the the RAC and LAC of the cell to the received message before
3. The new 3G SGSN obtain the address of the old 2G SGSN, and then sends an 'SGSN Context Reques
the UE. The old 2G SGSN validates the old P-TMSI signature. If the old P-TMSI Signature is valid, the old
cause.
4. The old 2G SGSN response with an "SGSN Context Response" message to the 3G SGSN including the
7. The old 2G SGSN copied and buffers N-PDUs, and then sends them to the 3G SGSN. Before the timer
and sends them to the 3G SGSN. After the timer expires,the 2G SGSN does not send N-PDUs to the 3G S
8.The new 3G SGSN sends an "Update PDP Context Request" message to each related GGSN. Each GG
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 SGSN re
Location Ack" message
11.The HLR sens an "Insert Subscriber Data" message to the 3G SGSN. The 3G SGSN constructs an MM
12. The HLR sends "Update GPRS Location" by returning an "Update GPRS Location Ack" message to th
13. If the association has to be establilshed, that is . if the Update Type parameter indicates a combined R
update, the 2G SGSN sends a "Location update request" message to the VLR. The VLR stores the SGSN
14. If the subscriber data in VLR is marked as not confirmed by the HLR. the new VLR informs the HLP. Th
15. The new VLR allocates a new TMSI and responds with a "Location Update Accept" message to the 3G
16. The new 3G SGSN checks the presence of the MS in the new RA. If all checks area successful,the new
established between the new 3G SGSN and the UE. The 3G SGSN responds to the UE with a "Routing A
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 confirm
19. If the UE has uplink data or signalling to send, the UE sends a "Service Request" message to the SGS
20. The 3G SGSN sends a "RAB Assignment Request" message to the SRNS. The SRNS sens a 'Radion
15. The new VLR allocates a new TMSI and responds with a "Location Update Accept" message to the 3G
16. The new 3G SGSN checks the presence of the MS in the new RA. If all checks area successful,the new
established between the new 3G SGSN and the UE. The 3G SGSN responds to the UE with a "Routing A
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 confirm
19. If the UE has uplink data or signalling to send, the UE sends a "Service Request" message to the SGS
20. The 3G SGSN sends a "RAB Assignment Request" message to the SRNS. The SRNS sens a 'Radion
Setup Complete" message. The SRNS sends a 'RAB assignment Response" message to the SGSN. The
re is described as follows:
RAT handover in the PS domain be sending "Cell Change Order from UTRAN' messge to UE to handover to a new GSM cell and stop the d
G SGSN. The update type in the message indicates RA update, combined RA/LA update, or combined RA/LA update with IMSI attach. Th
the message to a new 2G SGSN
o the old 3G SGSN to obtain the MM and PDP contexts. The old 3G SGSN validates the old P-TMSI signature. If the old P-TMSI Signature
SN sends an "SRNS Context Request" message. After receiving this message, the SRNS buffers the PDUs, stops sending the PDUs to the
age to the old 3G SGSN. This inform the old 3G SGSN that the new 2G SGSN is
the SRNS. The SRNS starts a data-forwarding timer and sends the buffers PDUs to
the PDUs, the sequence number in the GTP hearder remain unchange
ssage to each related GGSN. Each GGSN sends an "Update PDP Context Response"
2G SGSN. The 2G SGSN constructs an MM context and PDP context for the UE and
new 2G SGSN
a 'Location Update Request" message to the VLR. The VLR stores the SGSN
LR. the new VLR informs the HLP. The HLR cancel the old VLR and inserts
n and stops the data transmission between the UE and the network
G SGSN. The update type in the message indicates RA update, combined RA/LA update, or combined RA/LA
he cell to the received message before forwarding the message to a new 3G SGSN
hen sends an 'SGSN Context Request" message to the old 2G SGSN to construct the MM and PDP contects for
old P-TMSI Signature is valid, the old 2G SGSN starts a timer. Otherwise, the old 2G SGSN respons with an error
age to the old 2G SGSN. This inform the old 2G SGSN that the new 3G SGSN is ready to receive PDUs
em to the 3G SGSN. Before the timer expires ,if there are other N-PDUs from the GGSN,the 2G SGSN compies
SN does not send N-PDUs to the 3G SGSN anymore
sage to each related GGSN. Each GGSN sends an "Update PDP Context Response" message after updating it's
o the HLR
fter the timer expires,the 2G SGSN removes the MM and PDP contexts. The 2G SGSN response with a 'Cancel
SN. The 3G SGSN constructs an MM context and sends an "Insert Subscriber Data Ack" message to the HLR
pe parameter indicates a combined RA/LA update with IMSI attach requested, or if the LA changed with the RA
o the VLR. The VLR stores the SGSN number for creating or updating the association
LR. the new VLR informs the HLP. The HLR cancel the old VLR and inserts subscriber data in the new VLR
he SRNS. The SRNS sens a 'Radion Beare Setup Request" message to the UE. The UE responds with a 'Radio Bearer
w GSM cell and stop the data transmission between the UE
date with IMSI attach. The BSS adds the CGI including the
Bearer
Click to return to main page
1. Inter-RAT Handover
2.Suspend
3.Suspend
3. Suspend Ack
4. Resume
4. Resume NAck
5.Channel Release
1. Inter-RAT Handover
2.Suspend
3.Suspend
3. Suspend Ack
4. Resume
4. Resume NAck
5.Channel Release
1. Inter-RAT Handover
>>Inter-RAT HO
parameters
Inter-RAT Handover Procedure
2G MSC/
3G SGSN SRNS
SGSN VLR
1. Inter-RAT Handover
M e a s u r e m e n t C o n tr o l
& M e a Rs eu pr eo mr t e n t
>>Inter-RAT HO 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 o
performs the inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode first. After the UE
block flow (TBF) towards the GPRS to suspend the GPRS services. After the CS domain services are released o
the handover is completed.
if the inter-RAT handover from UTRA RCC Conencted Mode to GSM Connected Mode succeeds,the handover is
not. In case of inter-RAT handover failure, the UE may go back to the UTRA RRC Connected Mode and re-estab
3. The BSS forwards the 'Suspend" message to the SGSN. The SGSN sends a "SRNS Context Request" messa
message, the SRNS buffers downlink PDUs and respons to the SGSN with an 'SRNS Context Response" messg
4. When the CS connection is terminated , the BSS may send a 'Resume" message to the SGSN. However,resum
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
6. The UE sends a 'Routing Area Update Request" message to the SGSN to resume the GPRS service. The upd
For a UE in Cell_DCH state using both CS and PS domain services,the inter-RAT handover procedure is based o
performs the inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode first. After the UE
block flow (TBF) towards the GPRS to suspend the GPRS services. After the CS domain services are released o
the handover is completed.
if the inter-RAT handover from UTRA RCC Conencted Mode to GSM Connected Mode succeeds,the handover is
not. In case of inter-RAT handover failure, the UE may go back to the UTRA RRC Connected Mode and re-estab
3. The BSS forwards the 'Suspend" message to the SGSN. The SGSN returns a "Suspend Ack" message to the
4. When the CS connection is terminated , the BSS may send a 'Resume" message to the SGSN. However,resum
if the inter-RAT handover from UTRA RCC Conencted Mode to GSM Connected Mode succeeds,the handover is
not. In case of inter-RAT handover failure, the UE may go back to the UTRA RRC Connected Mode and re-estab
3. The BSS forwards the 'Suspend" message to the SGSN. The SGSN returns a "Suspend Ack" message to the
4. When the CS connection is terminated , the BSS may send a 'Resume" message to the SGSN. However,resum
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
6. The UE sends a 'Routing Area Update Request" message to the SGSN to resume the GPRS service. The upd
AT handover procedure is based on the measurement reports from the UE but is initiated from the UTRAN. The UE
Connected Mode first. After the UE sends a handover complete message to the GSM/BSS, the UE initiates a temporary
CS domain services are released on the GSM side, the inter-RAT handover in the PS domain resumes, which indicates that
ed Mode succeeds,the handover is regards as successful.no matter whether the UE inititates a TBF towards the GPRS or
RC Connected Mode and re-establish the connection in the original state.
GSM handover during which the CS service is handed over to the GSM
a "SRNS Context Request" message to the SRNS, requesting the SRNS to stop sending downlink PDUs. After receiving the
'SRNS Context Response" messge. The SGSN returns a "Suspend Ack" message to the BSS
ssage to the SGSN. However,resume is impossible since the radio access system has changed. Therefore,the SGSN
the BSS fails to request the SGSN to resume the GPRS service for the UE
esume the GPRS service. The update mode depends on the network operation mode in use.
AT handover procedure is based on the measurement reports from the UE but is initiated from the UTRAN. The UE
Connected Mode first. After the UE sends a handover complete message to the GSM/BSS, the UE initiates a temporary
CS domain services are released on the GSM side, the inter-RAT handover in the PS domain resumes, which indicates that
ed Mode succeeds,the handover is regards as successful.no matter whether the UE inititates a TBF towards the GPRS or
RC Connected Mode and re-establish the connection in the original state.
GSM handover during which the CS service is handed over to the GSM
ssage to the SGSN. However,resume is impossible since the radio access system has changed. Therefore,the SGSN
Click to return to main page
2.To initiate a cell update, the UE sends a CELL UPDATE message to the DRNC. To initiate a URA
DRNC.
3.After a successful cell update, the DRNC sends a CELL UPDATE CONFIRM message tothe UE.
UPDATE CONFIRM message to the UE.
4.After receiving the CELL UPDATE CONFIRM or URA UPDATE CONFIRM messagefrom the DRN
RECONFIGURATION COMPLETE message (for the cell update) or a UTRAN MOBILITY INFORM
This response from the UE is optional.
4.After receiving the CELL UPDATE CONFIRM or URA UPDATE CONFIRM messagefrom the DRN
RECONFIGURATION COMPLETE message (for the cell update) or a UTRAN MOBILITY INFORM
This response from the UE is optional.
Click to return to main page
7.RRC:Physical Channel
PhysicalChanne Reconfiguration
l Reconfig
2.After receiving a RADIO LINK RESTORE INDICATION message from the NodeB, theDR
3.If the DRNC does not obtain the information about the UE capability, the DRNC initiatesa
3 Messages - Intra-Frequency Hard Handover Procedure
DRNC CN
procedure :
E from the URNTI IE in the CELL UPDATEmessage and then sends an UPLINK SIGNALLING TRANSFER
e that the UE requests a cell update.
ELL UPDATE message to the DRNC. To initiate a URA update, the UE sends a URA UPDATE message to the
ends a CELL UPDATE CONFIRM message tothe UE. After a successful URA update, the DRNC sends a URA
RM or URA UPDATE CONFIRM messagefrom the DRNC, the UE can send a PHYSICAL CHANNEL
(for the cell update) or a UTRAN MOBILITY INFORMATION CONFIRM message (for the URA update) to the DRNC.
3 Messages - Intra-Frequency Hard Handover Procedure
DRNC CN
8. RANAP:Relocation Detect
STORE INDICATION message from the NodeB, theDRNC sends a RELOCATION DETECT message to the CN.
formation about the UE capability, the DRNC initiatesa UE capability enquiry procedure.
>>SRNC Relocation Algorithm and related
parameters
Relocation Preparation
ed as follows:
OCATION REQUIRED message to the CN. The message containscertain information such as relocation type, relocation
rce LAC,source SAC, target PLMN, and target LAC
e target RNC or the target network system, such as the GSMsystem, to prepare relevant resources.
e message to the SRNC.lIf the target RNC or the target network system prepares the relevant resourcessuccessfully, the CN sends a REL
tion is complete. The message contains the L3 information IE, which carries theinformation about the relevant resources allocated by the ta
artially or totally fail
nds a RELOCATIONPREPARATION FAILURE message.
ed as follows:
ATION REQUEST message to the target RNC. The messagecontains certain information, such as the IMSI of the UE, CN domain indicator
tion, Iu signaling connection ID, handover cause, and RAB parameters.
s radio resources for the relocation.
response message to the CN.lIf the resources are allocated, the target RNC sends a RELOCATION REQUESTACKNOWLEDGE message
parameters allocated to the UE. The parameters include the UTRAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transport layer and
tion algorithm, and chosen integrity protection algorithm.lIf the resources partially or totally fail to be allocated or the target RNC rejects the
NC sends a RELOCATION FAILURE message,indicating the failure cause.
ocedure is performed to execute the change of control from the SRNCof a UE to the DRNC
ed as follows:
OCATION COMMIT message to the DRNC. If an RAB supportinglossless SRNS relocation is available on the Iu-PS interface, the RELOCA
CP sequence numbers required for data forwarding.Then, the SRNC initiates data forwarding.
OCATION DETECT message to the CN to notify the CN of thedetection of the relocation commitment.
s a RELOCATION COMPLETE message to the CN to notify thatthe relocation is successful.
rmation procedure is performed for the network to allocate a newUTRAN Radio Network Temporary Identifier (U-RNTI) or Cell Radio Netw
the UE of mobility-related information such as timer values and CN domain–related information.
ed as follows:
AN MOBILITY INFORMATION message to the UE
the related fields according to the values of the IEs carried in themessage.
e message to the SRNC.
nducting the operations specified by the UTRAN MOBILITYI NFORMATION message, the UE sends a UTRAN MOBILITY INFORMATIONC
y procedure is performed to request a UE to transmit its capabilityinformation related to any radio access network so that the network can p
.
ed as follows:
CAPABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC.
PABILITY INFORMATION message to the SRNC through theuplink DCCH using AM or UM RLC. The message contains the information ab
capability information and then sends a UE CAPABILITYINFORMA CONFIRM message to the UE through the downlink DCCH using AM o
ed as follows:
LEASE COMMAND message to the SRNC to initiate the Iu releaseprocedure. The message indicates the cause for the release of the signa
COMMAND message, the CN will not send further RANAPconnection-oriented messages on this particular connection.
related UTRAN resources and then sends an IU RELEASE COMPLETE message to the CN.
ed as follows:
OCATION REQUIRED message to the CN. The message containscertain information such as relocation type, relocation cause, source PLM
AC
e target RNC or the target network system, such as the GSMsystem, to prepare relevant resources.
e message to the SRNC.lIf the target RNC or the target network system prepares the relevant resourcessuccessfully, the CN sends a REL
tion is complete. The message contains the L3 information IE, which carries theinformation about the relevant resources allocated by the ta
artially or totally fail to be allocated, the CN sends a RELOCATIONPREPARATION FAILURE message.
allocation procedure can be triggered in either of the following conditions:
on, the CN applies for resources from the target RNC
handover from GSM to WCDMA, the CN applies for resourcesfrom the target RNC
ed as follows:
ATION REQUEST message to the target RNC. The messagecontains certain information, such as the IMSI of the UE, CN domain indicator
tion, Iu signaling connection ID, handover cause, and RAB parameters.
s radio resources for the relocation.
response message to the CN.lIf the resources are allocated, the target RNC sends a RELOCATION REQUESTACKNOWLEDGE message
parameters allocated to the UE. The parameters
NetworkTemporary Identifier (U-RNTI), RAB, transport layer and physical layer information,chosen encryption algorithm
ection algorithm.lIf the resources partially or totally fail to be allocated or the target RNC rejects the SRNSrelocation for
NC sends a RELOCATION FAILURE message,indicating the failure cause.
e is performed to update the UE-related information on the UTRANside when the location of a UE changes. In addition, the cell update proc
nection, switching the status of the RRC connection, reporting errors,and transferring information
can be triggered in one of the following conditions:Cell reselection,Re-entering the service area,Periodical cell updatelRadio link failure,Pag
ecoverable error
ed as follows:
PDATE message to the RNC. The message contains the information such as the Serving RNC Radio Network Temporary Identifier (S-RNT
UPDATE CONFIRM message to the UE. The message containsthe information such as the U-RNTI and the IEs about the transport chann
in the received message, the UE may respond with messages ornot. If the UE responds, the message can be one of the following message
ORMATION CONFIRM
ECONFIGURATION COMPLETE
L RECONFIGURATION COMPLETE
NFIGURATION COMPLETE
ASE COMPLETE
re is performed to update the URA-related location information on thenetwork side when the location of a UE changes. The URA update pro
itions:URA reselection or Periodical URA update
ed as follows:
PDATE message to the RNC to initiate the URA update. The message contains the cause for the URA update and the IEs such as the U-RN
UPDATE CONFIRM message to the UE. The message containsthe new C-RNTI and U-RNTI or the information about the new ciphering an
ally. If there is a response, the UE sends a UTRAN MOBILITY INFORMATION CONFIRM message to the RNC after taking the new param
ocedure is performed to execute the change of control from the SRNCof a UE to the DRNC
ed as follows:
OCATION COMMIT message to the DRNC. If an RAB supportinglossless SRNS relocation is available on the Iu-PS interface, the RELOCA
CP sequence numbers required for data forwarding.Then, the SRNC initiates data forwarding.
OCATION DETECT message to the CN to notify the CN of thedetection of the relocation commitment.
s a RELOCATION COMPLETE message to the CN to notify thatthe relocation is successful.
rmation procedure is performed for the network to allocate a newUTRAN Radio Network Temporary Identifier (U-RNTI) or Cell Radio Netw
the UE of mobility-related information such as timer values and CN domain–related information.
ed as follows:
AN MOBILITY INFORMATION message to the UE
the related fields according to the values of the IEs carried in themessage.
e message to the SRNC.
nducting the operations specified by the UTRAN MOBILITYI NFORMATION message, the UE sends a UTRAN MOBILITY INFORMATIONC
the operations specified by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MOBILITY INFORMATIONFAILURE
y procedure is performed to request a UE to transmit its capabilityinformation related to any radio access network so that the network can p
.
ed as follows:
CAPABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC.
PABILITY INFORMATION message to the SRNC through theuplink DCCH using AM or UM RLC. The message contains the information ab
capability information and then sends a UE CAPABILITYINFORMA CONFIRM message to the UE through the downlink DCCH using AM o
ed as follows:
OCATION REQUIRED message to the CN. The message containscertain information such as relocation type, relocation cause, source PLM
AC
e target RNC or the target network system, such as the GSMsystem, to prepare relevant resources.
e message to the SRNC.lIf the target RNC or the target network system prepares the relevant resourcessuccessfully, the CN sends a REL
tion is complete. The message contains the L3 information IE, which carries theinformation about the relevant resources allocated by the ta
artially or totally fail to be allocated, the CN sends a RELOCATIONPREPARATION FAILURE message.
ed as follows:
ATION REQUEST message to the target RNC. The messagecontains certain information, such as the IMSI of the UE,
t cellidentifier, encryption, integrity protection, Iu signaling connection ID, handover cause, and RAB parameters.
s radio resources for the relocation.
response message to the CN.lIf the resources are allocated, the target RNC sends a RELOCATION
GE message. The message contains the radio resources and otherparameters allocated to the UE. The parameters
NetworkTemporary Identifier (U-RNTI), RAB, transport layer and physical layer information,chosen encryption algorithm,
ction algorithm.lIf the resources partially or totally fail to be allocated or the target RNC rejects the SRNSrelocation for
NC sends a RELOCATION FAILURE message,indicating the failure cause.
ocedure is performed to execute the change of control from the SRNCof a UE to the DRNC.
bed as follows:
g lossless SRNS relocation is available on the Iu-PS interface, theSRNC sends a FORWARD SRNS CONTEXT
onfiguration procedure is performed to set up, reconfigure, or releasea physical channel.
bed as follows:
SICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physical channel.
the UE, Radio Bearer (RB), transport channel, and physical channel.
e message to the SRNC.
ing the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION message, the UE sends a PHYSICAL CHANNELR
he uplink DCCH by using AM RLC.
e physical channels specified by the PHYSICAL CHANNELRECONFIGURATION message, the UE restores the configuration to the old ph
HANNEL RECONFIGURATION FAILURE message on the DCCH by using AM RLC. The value of the Failure causeIE contained in the PHY
LURE message is "physical channel failure".
y procedure is performed to request a UE to transmit its capabilityinformation related to any radio access network so that the network can p
.
ed as follows:
CAPABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC.
PABILITY INFORMATION message to the SRNC through theuplink DCCH using AM or UM RLC. The message contains the information ab
capability information and then sends a UE CAPABILITYINFORMA CONFIRM message to the UE through the downlink DCCH using AM o
ed as follows:
LEASE COMMAND message to the SRNC to initiate the Iu releaseprocedure. The message indicates the cause for the release of the signa
COMMAND message, the CN will not send further RANAPconnection-oriented messages on this particular connection.
related UTRAN resources and then sends an IU RELEASE COMPLETE message to the CN.
ocation
gorithm
on for
e UE,
rs
gorithm,
n for
a PHYSICAL CHANNELRE CONFIGURATION