Umts Protocols

UMTS Protocol Functionalities (cont.
)
Matti Turunen Nokia Mobile Phones email: matti.t.turunen@nokia.com
NOKIA 1999 FILENAMs.PPT/ DATE / NN
Radio information: 25.301 Radio Interface Protocol Interface Protocol Architecture More
Architecture
contol r RRC PD CP
L3
contol r
contol r
contol r contol r
PD CP
L2/ C P PD
BM C
L2/ C BM
RLC RLC RLC RLC RLC RLC RLC
RLC
L2/ LC R
Logi cal Channel s M AC
L2/ A C M
Tr por ans t Channel s
PH Y
L1
Broadcast Multicast Control (BMC) Services

Broadcast/multicast transmission service: The BM-SAP provides a broadcast/multicast transmission service in the user plane on the radio interface for common user data in transparent or unacknowledged mode
More information: 25.301 Radio Interface Protocol Architecture
BMC Functions
Storage of Cell Broadcast Messages (NW): The BMC stores the Cell Broadcast messages received over the CBC-RNC interface for scheduled transmission. Traffic volume monitoring and radio resource request for CBS (NW): At the UTRAN side, the BMC calculates the required transmission rate for Cell Broadcast Service based on the messages received over the CBC-RNC interface, and requests for appropriate CTCH/FACH resources from RRC. Scheduling of BMC messages: The BMC receives scheduling information together with each Cell Broadcast message over the CBC-RNC-interface. Based on this scheduling information , at the UTRAN side, BMC generates schedule messages and schedules BMC message sequences accordingly. At the UE side, BMC evaluates the schedule messages and indicates scheduling parameters to RRC, which are used by RRC to configure the lower layers for CBS discontinuous reception. Transmission of BMC messages to UE (NW): This function transmits the BMC messages (Scheduling and Cell Broadcast messages) according to schedule. Delivery of Cell Broadcast messages to upper layer (NAS): This functions delivers the received Cell Broadcast messages to upper layer (NAS) in the UE. Only non-corrupted Cell Broadcast messages are delivered.
4 NOKIA 1999 FILENAMs.PPT/ DATE / NN
More information: 25.301 Radio Interface Protocol Architecture
BMC Messages (PDUs)

BMC CBS Message:
I or aton El ent nf m i em M essage Type C B M essage I D SeralN um ber i D at C odi Schem e a ng C B D at a Pr esence M M M M M
BMC Schedule Message:
I or aton El ent nf m i em M essage Type O fsett Begi C TC H BS i f o n ndex Lengt ofC BS Schedulng h i Perod i N ew M essage Bim ap t N ew M essage D escrpton i i O t M essage D escrpton her i i
Pr esence M M M M O M
More information: 25.324 Radio Interface for Broadcast/Multicast Services

UMTS Protocol Functionalitues: Summary

Upper layer control plane protocols (MM, SM, CC) are adopted from GSM/GPRS as much as possible New development is needed in RAN protocols (BMC, PDCP, RLC, RRC and MAC) due to new air interface (WCDMA)
Overview of Protocol Interactions in UE

Control plane protocols, PS data

Session Management (SM) Handling of PDP contexts (activation, modification, deletion) Mobility Management (MM) Mobility management & Authentication
PM M D ETAC H ED
CC
SM
MM
MM
RRC R LC -C
PS D et ach PS Atach t PS Si gnali lng C onnecton R el i ease PM M -D LE I SM - TI or AC VE I AC TI N VE PS Si gnali lng C onnecton Est i i ablsh
D et ach, PS Atach R ej , t ect R AU R ej ect
M AC W C D M A P hy
PM M C O N N EC TED SM - TI or AC VE I AC TI N VE
More information: 24.008 Mobile radio interface layer 3 specification, Core Network Protocols 8 Stage 3 NOKIA 1999 FILENAMs.PPT/ DATE / NN
PDP Context in UMTS

Packet Data Protocol (PDP) Context defines: Upper layer protocol (PDP type: IPv4, IPv6) IP address (PDP address e.g. IPv4: 192.58.44.58) QoS profile (Conversational, Streaming, Interactive, Background)
Major change from GPRS Phase 1: It is possible to have several PDP contexts with same IP address, QoS profile is different (Primary PDP context, Secondary PDP context) Traffic Flow Template (TFT) specifies which IP packets belong to a PDP context MS initiated PDP context modification is possible An example:
Primary PDP Context: - 192.58.44.58
Secondary PDP Context: - 192.58.44.58 - Background QoS
- Interactive QoS
PDP Context Activation Procedure in UMTS
MS
U TRA N
3G - SN SG
3G - G SN G
1.A ctvat PD P Cont Reques i e ext t 3.Radi A cces Bear Set o s er up 4.Cr e PD P Cont Reques eat ext t 4.Cr e PD P Cont Res eat ext pons e 5.A ctvat PD P Cont A ccept i e ext
10
Protocol Interactions in UE
P D P C ont 1 ext - I v6 address P - I eractve Q oS nt i P D P C ont 2 ext - I v6 address P - B ackground Q oS P D P C ont 3 ext - I v4 address P - I eractve Q oS nt i PDCP CC SM PDCP M gm t H eader com pressi on Ci t rcui S w iched t A ppl .
MM
MM (G M M ) R LC -U RRC R LC M gm t R LC -C R LC -U entt iy R LC -U entt iy R LC -U entt iy R LC -U entt iy
M AC T ransport f orm at set T ransport f orm at T ransport f orm at com bi i naton C hannelcodi ng, i erl nt eavi ng
W C D M A P hy
User Equipmet (UE) Identifiers and Modes

12
User Identification on the Radio Interface

UE identifier is needed on common and shared channels Radio Network Temporary Identifier (RNTI) is used as an UE identifier RNTI types: - C-RNTI (Cell RNTI): Used within a cell controlled by a Controlling RNC (unique within a cell). - S-RNTI (Serving RNC RNTI): Used within the Serving RNC (unique within a SRNC). S-RNTI is allocated for UEs having a RRC connection. - U-RNTI (UTRAN RNTI): S-RNTI + SRNC Id (unique within a PLMN), identifies the UE within UTRAN . Usage of identifiers: - U-RNTI is used in cell update, URA update, RRC connection reestablishment and paging messages - C-RNTI is used in all other DCCH/DTCH common channel messages More information: 25.301 Radio Interface Protocol Architecture
UE Modes
Idle mode - UE enters this mode after power on - UE is identified using non-access stratum identifiers (IMSI, TMSI, PTMSI) - UTRAN does not have information about individual UEs - UTRAN can address only e.g. all UEs in a cell (paging), not individual UEs - UE does not have a signalling connection (RRC connection) - Data transfer is not possible - Reception of SMS cell broadcast is possible Connected mode - UE enters this mode when the RRC connection is established (between UE and SRNC) - UE is assigned a U-RNTI - Data transfer is possible - Reception of SMS cell broadcast is possible More information: 25.301 Radio Interface Protocol Architecture
UTRAN Interfaces
15
Overview of UTRAN, Basic Concepts

UTRAN consists of a set of Radio Network Subsystems connected to the CN through Iu. RNS consists of a Radio Network Controller and one or more Node Bs. A Node B is connected to the RNC through Iub interface. A Node B can support FDD mode, TDD mode or dual-mode operation.
N ode B RNC N ode B
RNS I ub
N ode B RNC N ode B
I ur
CN I u
RNS U TR AN
RNC is responsible for the Handover decisions that require signalling to the UE. RNC comprises a combining/splitting function to support macro diversity between different Node B. Inside the UTRAN, the RNCs can be interconnected together through the Iur. Iu and Iur are logical interfaces. Iur can be conveyed over physical direct connection between RNCs or via any suitable transport network.
More information: 25.401 UTRAN Overall Description

General Protocol Model for UTRAN Terrestrial Interfaces (Iu, Iur, Iub)
R adi o N et or w k Layer C ontolPl r ane Applcaton i i Pr ocol ot U serPl ane D at a Steam ( r s)
Tr anspor t N et or w k Layer
Tr anspor N et or t w k U ser Pl ane
Tr anspor N et or t w k C ontolPl r ane
Tr anspor N et or t w k U ser Pl ane
ALC AP( s) Si gnali lng Bear ( er s) Si gnali lng Bear ( er s) D at a Bear ( er s)
Physi Layer cal
The layers and planes are logically independent of each other if needed, protocol layers, or the whole protocol stack in a plane may be changed in the future by decisions in the standardisation. More information: 25.401 UTRAN Overall Description
Iu Interface concept
W CDM A
BS RNC BS
I u
W M SC / VLR
M APe Gs ( ) opt M AP
G M SC
C AP C AP C AP
PLM N s,PSTN , I N ,et . SD c..
UE BS
I ub
I ur
H LR
C AP
SC P
M APe
RNC BS
3G SG SN
G G SN
I net or P- w k
Gn U TR AN
Interface between WCDMA RAN and GSM/UMTS Core Network Two Instances of Iu; CS and PS domains Control Plane Application (RANAP) is the same for both User Plane is optimized separately: Circuit (3G MSC): Signaled (q.aal2) AAL2 connections per user flow Packet (3G SGSN): Several user flows are multiplexed on one or several AAL5 PVCs with IP and the user plane part of GTP
More information: 25.410 UTRAN Iu Interface: General Aspects and Principles
Iu CS Protocol Structure
Radi o N et or w k Layer
C ont Pl rol ane RANAP
U s Pl er ane I U s Pl u er ane Prot ocol
Tr por ans t N et or w k Layer
Tr por N et or ans t w k U s Pl er ane
Tr por N et or ans t w k ContolPl r ane

Q. 2630. 1
SCCP M TP3b SSCF- N I N SSCO P A A L5
Q. 2150. 1 M TP3b SSCF- N I N SSCO P A A L5 A A L2
A TM Phys calLayer i

Iu PS Protocol Structure
C ont Pl rol ane RANAP
U s Pl er ane I U s Pl u er ane Prot ocol
SCCP I N TU M TP3B SCTP SSCF- N I N SSCO P A A L5 UDP I P G TPU UDP I P A A L5

RANAP Functions
Radio Access Bearer (UE - CN bearer) handling: RAB Set-up RAB Modification Releasing RAB Iu Release: Releases all Iu resources (Signaling link and U-Plane) related to the specified UE. Relocation: Handling both SRNS Relocation (UE already in target RNC with Iur) and Hard Handover (simultaneous switch of Radio and Iu). Includes loss-less relocation and inter system handover. Paging: CN to page an idle UE for a terminating call/connection Common ID: UE NAS Id sent to RNC for paging co-ordination Trace Invocation: CN may request UTRAN to trace a specific UE Security Mode Control: Controls Ciphering and Integrity Checking.
More information: 25.413 UTRAN Iu Interface RANAP Signalling

RANAP Functions (cont.)

Location Reporting: Requesting (CN) and reporting (RNC) UE location Data Volume Reporting: Requesting (CN) and reporting (RNC) unsuccessfully transmitted DL data Initial UE Message: Carries the first Radio interface L3 message to the CN and sets up the Iu signaling connection. Direct Transfer: Carries CN and UE signalling information over Iu. Content not interpreted by UTRAN. CN Information Broadcast: This procedure allows the CN to set system information to be broadcasted to all users. Controlling overload: Used for flow control (to reduce flow) over the Iu interface e.g. due to processor overload at CN or UTRAN Reset: It is used to reset the CN or the UTRAN side of Iu interface in error situations Error Indication: Used for protocol errors where no other error applies More information: 25.413 UTRAN Iu Interface RANAP Signalling
Functions of Iur interface in UTRAN (1/3)

Support basic inter RNC mobility
1. Allows inter RNC URA update and paging in multiple RNCs (User in RRC URA_PCH (or CELL_PCH) state).
CN
2. Allows the Inter RNC cell update + SRNC relocation (User in RRC CELL_FACH state).
CN
SR N C R el ocaton i
Tar get RNC
S- N C R
RNC
S- N C R
URA BS BS BS BS BS
pagi ng
MS
pagi ng
MS
C el U pdat l e
U R A U pdat e
Only signalling, no user data Iur interface is not involved in Inter RNC hard handover!
23

Support dedicated ch. traffic between two RNCs
1. Allows inter RNC soft handover
CN
2. Allows anchor SRNC when the User is in dedicated channel state

CN
S- N C R + M DC
D- NC R
S- N C R
D- NC R + M DC
BS
BS
BS
BS
MS MS
Support user data transfer with dedicated connection Support of downlink shared transport channel (DSCH)

Support common ch. traffic between two RNCs
Allows anchoring of SRNC also when UE is in common channel (RACH/FACH) state Support user data transfer with common transport connection
S- N C R CN
D- NC R
BS
MS
25
Iur protocol structure

C ont Pl rol ane R N SA P
U s Pl er ane DCH FP CCH FP

Q. 2630. 1
SCCP I N TU M TP3B SCTP SSCF- N I N SSCO P A A L5 UDP I P
Q. 2150. 1 I N TU M TP3B SCTP SSCF- N I N SSCO P A A L5 UDP I P A A L2
More information: 25.420 UTRAN Iur Interface: General Aspects and Principles
RNSAP Functions
Radio Link Management: This function allows the SRNC to manage radio links using dedicated resources in a DRNS. Physical Channel Reconfiguration: This function allows the DRNC to reallocate the physical channel resources for a Radio Link. Radio Link Supervision: This function allows the DRNC to report failures and restorations of a Radio Link. Compressed Mode Control [FDD]: This function allows the SRNC to control the usage of compressed mode within a DRNS Measurements on Dedicated Resources: This function allows the SRNC to initiate measurements on dedicated resources in the DRNS. The function also allows the DRNC to report the result of the measurements. DL Power Drifting Correction [FDD]: This function allows the SRNC to adjust the DL power level of one or more Radio Links in order to avoid DL power drifting between the Radio Links. More information: 25.423 UTRAN Iur Interface RNSAP Signalling
RNSAP Functions (cont.)

CCCH Signalling Transfer: This function allows the SRNC and DRNC to pass information between the UE and the SRNC on a CCCH controlled by the DRNS. Paging: This function allows the SRNC to page a UE in a URA or a cell in the DRNS. Common Transport Channel Resources Management: This function allows the SRNC to utilise Common Transport Channel Resources within the DRNS (excluding DSCH resources for FDD). Relocation Execution: This function allows the SRNC to finalise a Relocation previously prepared via other interfaces. Reporting general error situations: This function allows reporting of general error situations, for which function specific error messages have not been defined.
More information: 25.423 UTRAN Iur Interface RNSAP Signalling

Iub Protocol Structure (25.430)

C ont Pl rol ane

RA CH FP D CH FP
U s Pl er ane
PCH FP FA CH FP D SCH FP U SCH FP
N BA P
Q. 2630. 1
Q. 2150. 2 SSCF- N I U SSCO P A A L5 SSCF- N I U SSCO P A A L5 A A L2
29
NBAP Functions
Cell Configuration Management: This function gives the Controlling RNC (CRNC) the possibility to manage the cell configuration information in a Node B. Common Transport Channel Management: This function gives the CRNC the possibility to manage the configuration of Common Transport Channels in a Node B. System Information Management: This function gives the CRNC the ability to manage the scheduling of System Information to be broadcast in a cell. Resource Event Management: This function gives the Node B the ability to inform the CRNC about the status of Node B resources. Configuration Alignment: This function gives the CRNC and the Node B the possibility to verify that both nodes has the same information on the configuration of the radio resources. Measurements on Common Resources: This function allows the CRNC to initiate measurements in the Node B. The function also allows the Node B to report the result of the measurements. More information: 25.433 UTRAN Iub Interface NBAP Signalling
NBAP Functions (cont.)

Synchronisation Management (TDD): This function allows the CRNC to manage the synchronisation of a TDD cell in a Node B. Radio Link Management: This function allows the CRNC to manage radio links using dedicated resources in a NodeB. Radio Link Supervision: This function allows the CRNC to report failures and restorations of a Radio Link. Measurements on Dedicated Resources: This function allows the CRNC to initiate measurements in the NodeB. The function also allows the NodeB to report the result of the measurements. DL Power Drifting Correction (FDD): This function allows the CRNC to adjust the DL power level of one or more Radio Links in order to avoid DL power drifting between the Radio Links. Reporting general error situations: This function allows reporting of general error situations, for which function specific error messages have not been defined.
More information: 25.433 UTRAN Iub Interface NBAP Signalling

Procedures Related to Data Transfer

32
Procedures Related to Data Transfer

MS U TRA N 3G - SN SG 3G - G SN G RRC Connecton Es abls ent i t i hm
A tach Reques t t A tach A ccept t A ctvat PD P Cont Reques i e ext t Radi A cces Bear Set o s er up Cr e PD P Cont Reques eat ext t Cr e PD P Cont Res eat ext pons e A ctvat PD P Cont A ccept i e ext
33
Typical Configuration Cases

Par et am er R adi bear o er R LC par et s am er par et s am er Logi channel cal m uli exi prort tpl ng i iy Tr anspor t Tr anspor channel t channel schedulng prort i i iy par et s am er TFS TFC S SubsetofTFC S Tr anspor channel t t ype sw ichi t ng Physi channelpar et s cal am er Layer R LC M AC M AC A X X X B C D E F
L1+M AC L1+M AC M AC M AC L1
X X X X
X X X X X X X X X
Case A: Radio bearer establisment or QoS of an existing radio bearer need to be changed Case B: Traffic volume of a radio bearer has changed so that the TFS used on the DCH need to be changed Case C: Traffic volume of a radio bearer has changed so that the used transport channel type is changed (e.g. FACH --> DCH) Case D: E.g. change of used DL channelization code Case E: Temporary restriction or a release of restriction for usage of the TCFS by the UE Case F: Dynamic control of resources allocated on uplink DCHs in the CRNC, using broadcast information such as transmission probability and maximum bitrate
RRC Elementary Procedures

Radio Bearer Configuration (Case A):
Radio Bearer Establishment Radio Bearer Release Radio Bearer Reconfiguration
Transport Channel Configuration (Case B):

Transport Channel Reconfiguration
Physical Channel Configuration (Case C and D):

Physical Channel Reconfiguration
Transport Format Combination Restriction (Case E):

Transport Format Combination Control
Uplink Dedicated Channel Control in CRNC (Case F):

Dynamic Resource Allocation Control of Uplink DCHs
35
RRC Connection Establishment

UE R R C C O N N EC TI N R EQ U EST O U TR AN
CCCH; TR RLC CCCH; TR RLC - -Initial UE identity Initial UE identity - -Establishment cause Establishment cause - -Initial UE capability Initial UE capability CCCH; UM RLC CCCH; UM RLC - -Initial UE identity Initial UE identity - -U-RNTI U-RNTI - -Capability update requirement Capability update requirement - -Information about the radio Information about the radio bearer assigned for the signalling bearer assigned for the signalling link link - -transport channel information transport channel information DCCH; AM RLC DCCH; AM RLC - -Integrity protection & ciphering Integrity protection & ciphering configuration information configuration information - -Capability information if Capability information if requested requested
R R C C O N N EC TI N SETU P O
R R C C O N N EC TI N SETU P C O M PLETE O
Radio Bearer Establisment

DCCH; AM or UM RLC DCCH; AM or UM RLC - -NAS binding info NAS binding info - -Radio bearer information: Radio bearer information: - -L1 configuration information L1 configuration information - -new/modified transport channels new/modified transport channels - -MAC logical channel priority MAC logical channel priority - -Transport format set(s) Transport format set(s) - -Transport format combination set(s) Transport format combination set(s) - -RLC configuration information RLC configuration information - -PDCP configuration information PDCP configuration information DCCH; AM RLC DCCH; AM RLC - -Optional integrity check info Optional integrity check info
UE R AD I BEAR ER SETU P O
U TR AN
R AD I BEAR ER SETU P C O M PLETE O
37
Radio Bearer Reconfiguration

DCCH; AM or UM RLC DCCH; AM or UM RLC - -Radio bearer information (change of Radio bearer information (change of QoS): QoS): - -L1 configuration information L1 configuration information - -new/modified transport channels new/modified transport channels - -MAC logical channel priority MAC logical channel priority - -Transport format set(s) Transport format set(s) - -Transport format combination set(s) Transport format combination set(s) - -RLC configuration information RLC configuration information - -PDCP configuration information PDCP configuration information
UE
U TR AN
R AD I BEAR ER R EC O N FI U R ATI N O G O
R AD I BEAR ER O R EC O N FI U R ATI N C O M PLETE G O
DCCH; AM RLC DCCH; AM RLC - -Optional integrity check info Optional integrity check info
38
Radio Bearer Release

DCCH; AM or UM RLC DCCH; AM or UM RLC - -Identification of the radio bearer to be Identification of the radio bearer to be released released - -Radio bearer information for remaining Radio bearer information for remaining radio bearers: radio bearers: - -L1 configuration information L1 configuration information - -new/modified transport channels new/modified transport channels - -MAC logical channel priority MAC logical channel priority - -Transport format set(s) Transport format set(s) - -Transport format combination set(s) Transport format combination set(s)
UE R AD I BEAR ER R ELEASE O
U TR AN
R AD I BEAR ER R ELEASE C O M PLETE O
39
Transport Channel Reconfiguration
UE TR AN SPO R T C H AN N EL R EC O N FI U R ATI N G O
U TR AN
TR AN SPO R T C H AN N EL R EC O N FI U R ATI N C O M PLETE G O
DCCH; AM or UM RLC DCCH; AM or UM RLC - -Configuration info of transport format Configuration info of transport format set set for aatransport channel for transport channel - -L1 configuration information L1 configuration information - -new/modified transport channels new/modified transport channels - -Transport format set(s) Transport format set(s) - -Transport format combination set(s) Transport format combination set(s) DCCH; AM RLC DCCH; AM RLC - -Optional integrity check info Optional integrity check info
40
Physical Channel Reconfiguration
UE PH YSI AL C H AN N EL C R EC O N FI U R ATI N G O
U TR AN
DCCH; AM or UM RLC DCCH; AM or UM RLC - -L1 physical channel configuration L1 physical channel configuration information information - -change of transport channel change of transport channel (no transport format information, if TFs (no transport format information, if TFs change then Transport Channel change then Transport Channel Reconfiguration is used) Reconfiguration is used)
PH YSI AL C H AN N EL C R EC O N FI U R ATI N C O M PLETE G O
41
Transport Format Combination Control
UE
U TR AN
TR AN SPO R T FO R M AT C O M BI ATI N C O N TR O L N O
DCCH; TM, AM or UM RLC DCCH; TM, AM or UM RLC - -Reconfiguration of allowed transport Reconfiguration of allowed transport format combinations within the format combinations within the transport transport format combination set format combination set - -The network can optionally specify the The network can optionally specify the duration for which aanew transport duration for which new transport format combination set applies format combination set applies
42
Dynamic Resource Allocation Control (DRAC) of Uplink DCH

UE U TRA N SY STEM I FO RM A TI N N O
BCCH; TM RLC BCCH; TM RLC - -DRAC procedures are applied in this cell DRAC procedures are applied in this cell - -DRAC information: DRAC information: - -Transmission probability (ptr) ) Transmission probability (ptr - -Maximum bit rate (Max bit rate) Maximum bit rate (Max bit rate)
RB Es abls ent t i hm RB Reconfgur i i aton RB Rel e eas Tr por ChannelReconfgur i ans t i aton
1. The UE randomly selects p [0,1] 2. The UE then checks permission: if p < ptr the permission is granted Tvalidity frames, otherwise UE waits for Tretry frames before re-attempting access 3. RRC configures MAC with a new subset of TFCS according to the permission result and maximum bitrate (affects only DCHs that are controlled by DRAC)
DCCH; UM or AM RLC DCCH; UM or AM RLC - -Dynamic Control -parameter included in Dynamic Control -parameter included in messages, indicates that DCH is messages, indicates that DCH is controlled controlled by the DRAC procedure by the DRAC procedure - -Transmission time validity (Tvalidity) ) Transmission time validity (Tvalidity - -Time duration before retry (Tretry) ) Time duration before retry (Tretry - -Silent period duration before release Silent period duration before release
Measurements
UE M EASU R EM EN T C O N TR O L U TR AN
DCCH; AM RLC DCCH; AM RLC - -Setup, modify or release measurements: Setup, modify or release measurements: - -Intra-frequency measurement Intra-frequency measurement - -Inter-frequency measurement Inter-frequency measurement - -Inter-system measurement Inter-system measurement - -Traffic volume measurement Traffic volume measurement - -Quality measurement Quality measurement
UE M EASU R EM EN T R EPO R T
U TR AN
DCCH; AM or UM RLC DCCH; AM or UM RLC - -Measurements results Measurements results - -Can be periodic or triggered by an event Can be periodic or triggered by an event
44
Traffic Volume Measurements

Shortpendi ng tm e af er t gger i t ri
Payl oad Payl oad
Long pendi ng tm e af er t gger i t ri
Thr hol es d
Thr hol es d Ti e m Ti e m
Repor 1 t
Repor 2 t
Repor 1 t
N o Repor t
Pendi tm e aferti ng i t rgger
Pendi tm e aferti ng i t rgger
- UE measures RLC buffer payload in bytes (UM and AM RLC) - UE sends periodic and event triggered measurement reports. Event triggered reporting is performed when a threshold is exceeded. - According to traffic volume measurements, the NW initiates possible reconfiguration procedures.

Umts Protocols

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Umts Protocols

Uploaded by

Copyright:

Available Formats

UMTS Protocol Functionalities (cont.

NOKIA 1999 FILENAMs.PPT/ DATE / NN

RLC RLC RLC RLC RLC RLC RLC

Logi cal Channel s M AC

NOKIA 1999 FILENAMs.PPT/ DATE / NN

Broadcast Multicast Control (BMC) Services

More information: 25.301 Radio Interface Protocol Architecture

NOKIA 1999 FILENAMs.PPT/ DATE / NN

More information: 25.301 Radio Interface Protocol Architecture

BMC Messages (PDUs)

BMC Schedule Message:

More information: 25.324 Radio Interface for Broadcast/Multicast Services

UMTS Protocol Functionalitues: Summary

NOKIA 1999 FILENAMs.PPT/ DATE / NN

Overview of Protocol Interactions in UE

NOKIA 1999 FILENAMs.PPT/ DATE / NN

Control plane protocols, PS data

D et ach, PS Atach R ej , t ect R AU R ej ect

PDP Context in UMTS

Secondary PDP Context: - 192.58.44.58 - Background QoS

PDP Context Activation Procedure in UMTS

NOKIA 1999 FILENAMs.PPT/ DATE / NN

MM (G M M ) R LC -U RRC R LC M gm t R LC -C R LC -U entt iy R LC -U entt iy R LC -U entt iy R LC -U entt iy

User Equipmet (UE) Identifiers and Modes

NOKIA 1999 FILENAMs.PPT/ DATE / NN

User Identification on the Radio Interface

NOKIA 1999 FILENAMs.PPT/ DATE / NN

Overview of UTRAN, Basic Concepts

More information: 25.401 UTRAN Overall Description

Tr anspor N et or t w k U ser Pl ane

Tr anspor N et or t w k C ontolPl r ane

Tr anspor N et or t w k U ser Pl ane

ALC AP( s) Si gnali lng Bear ( er s) Si gnali lng Bear ( er s) D at a Bear ( er s)

Physi Layer cal

PLM N s,PSTN , I N ,et . SD c..

C ont Pl rol ane RANAP

U s Pl er ane I U s Pl u er ane Prot ocol

Tr por ans t N et or w k Layer

Tr por N et or ans t w k U s Pl er ane

Tr por N et or ans t w k ContolPl r ane

Tr por N et or ans t w k U s Pl er ane

SCCP M TP3b SSCF- N I N SSCO P A A L5

Q. 2150. 1 M TP3b SSCF- N I N SSCO P A A L5 A A L2

More information: 25.410 UTRAN Iu Interface: General Aspects and Principles

C ont Pl rol ane RANAP

U s Pl er ane I U s Pl u er ane Prot ocol

Tr por ans t N et or w k Layer

Tr por N et or ans t w k U s Pl er ane

Tr por N et or ans t w k ContolPl r ane

Tr por N et or ans t w k U s Pl er ane

SCCP I N TU M TP3B SCTP SSCF- N I N SSCO P A A L5 UDP I P G TPU UDP I P A A L5

More information: 25.410 UTRAN Iu Interface: General Aspects and Principles

More information: 25.413 UTRAN Iu Interface RANAP Signalling

RANAP Functions (cont.)

Functions of Iur interface in UTRAN (1/3)

NOKIA 1999 FILENAMs.PPT/ DATE / NN

Functions of Iur interface in UTRAN (2/3)

2. Allows anchor SRNC when the User is in dedicated channel state

Functions of Iur interface in UTRAN (3/3)

NOKIA 1999 FILENAMs.PPT/ DATE / NN

Iur protocol structure

C ont Pl rol ane R N SA P

U s Pl er ane DCH FP CCH FP