umts protocols

1 © NOKIA 1999 FILENAMs.PPT/ DATE / NN

UMTS Protocol Functionalities (cont.)

Matti Turunen

Nokia Mobile Phones

email: [email protected]


Radio Interface Protocol ArchitectureL3

cont

rol

cont

rol

cont

rol

cont

rol

Logi calChannel s

Transpor tChannel s

PHY

L2/M AC

L1

RLC L2/RLC

M AC

RLCRLC

RLCRLC

RLCRLC

RLC

BM C L2/BM C

RRC

cont rol

PDCPPDCP L2/PDCP

More information: 25.301 Radio Interface ProtocolArchitecture


Broadcast Multicast Control (BMC)Services

• Broadcast/multicast transmission service: The BM-SAP provides abroadcast/multicast transmission service in the user plane on the radiointerface 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 theUTRAN side, the BMC calculates the required transmission rate for CellBroadcast 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 informationtogether with each Cell Broadcast message over the CBC-RNC-interface. Basedon this scheduling information , at the UTRAN side, BMC generates schedulemessages and schedules BMC message sequences accordingly. At the UE side,BMC evaluates the schedule messages and indicates scheduling parameters toRRC, which are used by RRC to configure the lower layers for CBSdiscontinuous reception.

• Transmission of BMC messages to UE (NW): This function transmits the BMCmessages (Scheduling and Cell Broadcast messages) according to schedule.

• Delivery of Cell Broadcast messages to upper layer (NAS): This functionsdelivers the received Cell Broadcast messages to upper layer (NAS) in the UE.Only non-corrupted Cell Broadcast messages are delivered.



BMC Messages (PDUs)

Inform at ion Elem ent PresenceM essage Type MCB M essage ID MSerial Num ber MData Coding Schem e MCB Data M

Inform at ion Elem ent PresenceM essage Type MO ffset to Begin CTCH BS index MLengt h of CBS Schedul ingPeriod

M

New M essage Bitm ap MNew M essage Descr iption OO ther M essage Descr iption M

BMC CBS Message:

BMC ScheduleMessage:

More information: 25.324 Radio Interface for Broadcast/Multicast Services


UMTS Protocol Functionalitues: Summary

• Upper layer control plane protocols (MM, SM, CC) areadopted 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

Matti Turunen

Nokia Mobile Phones



Control plane protocols, PS data

Session Management (SM)

• Handling of PDP contexts (activation,modification, deletion)

Mobility Management (MM)

• Mobility management & Authentication

PM M -DETACHED

PS Attach

PS Signal lingConnect ion R elease

PS Signal lingConnect ion Establish

PS Detach

PM M -CO NNECTEDPM M -IDLE

Detach,PS Attach Reject ,RAU Reject

SM -ACTIVE orINACTIVE

SM -ACTIVE orINACTIVE

C C S M

M M M M

R R C

R LC -C

M A C

W C D M A P hy

More information: 24.008 Mobile radio interface layer 3 specification, Core Network Protocols -Stage 3


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 profileis different (Primary PDP context, Secondary PDP context)

• Traffic Flow Template (TFT) specifies which IP packets belong to a PDPcontext

• MS initiated PDP context modification is possible

• An example:

Primary PDP Context: Secondary PDP Context:

- 192.58.44.58 - 192.58.44.58

- Interactive QoS - Background QoS


PDP Context Activation Procedure in UMTS

3G-GGSN

5. Activat e PDP Context Accept

4. Create PDP Context Response

4. Create PDP Context Request

1. Activat e PDP Context Request

3G-SGSNUTRANM S

3. Radio Access Bearer Setup


Protocol Interactions in UE

R LC -U

R LC -Uent ity

P D C P

M A C

W C D M A P hy

S MC C

M M(G M M )

M M

R R C

R LC -C

R LCM gm t

R LC -Uent ity

R LC -Uent ity

R LC -Uent ity

H eader com pressi onP D C PM gm t

T ransport form at set

T ransport form at

P D P C ontext 1- IP v6 address- Interact ive Q oS

P D P C ontext 2- IP v6 address- B ackground Q oS

P D P C ontext 3- IP v4 address- Interact ive Q oS

T ransportform at com binat ion

C hannel codi ng,interl eavi ng

C ircui tS w itchedA ppl.


User Equipmet (UE) Identifiers andModes

Matti Turunen

Nokia Mobile Phones



User Identification on the Radio Interface

• UE identifier is needed on common and shared channels

• Radio Network Temporary Identifier (RNTI) is used as an UEidentifier

• 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 aRRC connection.

- U-RNTI (UTRAN RNTI): S-RNTI + SRNC Id (unique within aPLMN), 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



UE Modes

• Idle mode- UE enters this mode after power on- UE is identified using non-access stratum identifiers (IMSI, TMSI, P-

TMSI)- 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



UTRAN Interfaces

Matti Turunen

Nokia Mobile Phones



Overview of UTRAN, Basic Concepts

• RNC is responsible for the Handover decisions that require signalling to the UE.

• RNC comprises a combining/splitting function to support macro diversity between differentNode B.

• Inside the UTRAN, the RNCs can be interconnected together through the Iur. Iu and Iur arelogical interfaces. Iur can be conveyed over physical direct connection between RNCs or viaany suitable transport network.

UTRAN

RNC

RNC

Iub Iur

CN

RNS

RNS

Node B

Node B

Node B

Node B

Iu

• UTRAN consists of a set of Radio NetworkSubsystems connected to the CN through Iu.

• RNS consists of a Radio Network Controller andone or more Node Bs. A Node B is connected tothe RNC through Iub interface.

• A Node B can support FDD mode, TDD mode ordual-mode operation.

More information: 25.401 UTRAN Overall Description


General Protocol Model for UTRANTerrestrial Interfaces (Iu, Iur, Iub)

• The layers and planes are logically independent of each other

• if needed, protocol layers, or the whole protocol stack in a plane may bechanged in the future by decisions in the standardisation.

Applicat ionProtocol

DataStream (s)

ALCAP(s)

Transpor tNetwork

Layer

Physi cal Layer

Signal lingBearer(s)

Transpor tUser

NetworkPlane

Control Plane User Plane

Transpor tUser

NetworkPlane

Transpor t NetworkControl Plane

RadioNetwork

Layer

Signal lingBearer(s)

DataBearer(s)

More information: 25.401 UTRAN Overall Description


Iu Interface concept

• 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 flowPacket (3G SGSN): Several user flows are multiplexed on one or several AAL5

PVCs with IP and the user plane part of GTP

UTRAN

UE

BS

BS

RNC

RNC

W M SC/VLR

3G -SG SN

W CDM A

G G SN

G M SC

IP-network

PLM Ns, PSTN,ISDN, etc. ..

M AP

HLR SCP

M APe

M APe

CAP

Iu

Iub Iur

CAP CAP

CAP

BS

BS G n

G s (opt )

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


Iu CS Protocol Structure

Q.2150. 1

Q.2630. 1

RANAPIu User Plane

Prot ocol

Transpor tNetwork

Layer

Physi cal Layer

Transpor tUser

NetworkPlane


Transpor tUser

NetworkPlane


RadioNetwork

Layer

ATM

SSCOP

AAL5

SSCOP

SSCF-NNI

AAL2AAL5

M TP3bM TP3b

SCCP

SSCF-NNI



Iu PS Protocol Structure

SSCF-NNI

SSCOP

M TP3-B

AAL5

IP

SCTP

SCCP

UDP

ITUN

RANAPIu User Plane

Prot ocol

Transpor tNetwork

Layer

Physi cal Layer

Transpor tUser

NetworkPlane


Transpor tUser

NetworkPlane


RadioNetwork

Layer

ATM

AAL5

IP

UDP

GTP-U

Physi cal Layer

ATM



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 specifiedUE.

• Relocation: Handling both SRNS Relocation (UE already in target RNC with Iur) and HardHandover (simultaneous switch of Radio and Iu). Includes loss-less relocation and intersystem 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 andsets up the Iu signaling connection.

• Direct Transfer: Carries CN and UE signalling information over Iu. Contentnot interpreted by UTRAN.

• CN Information Broadcast: This procedure allows the CN to set systeminformation to be broadcasted to all users.

• Controlling overload: Used for flow control (to reduce flow) over the Iuinterface 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 errorsituations

• Error Indication : Used for protocol errors where no other error applies

More information: 25.413 UTRAN Iu Interface RANAP Signalling


• 1. Allows inter RNC URA updateand paging in multiple RNCs (Userin RRC URA_PCH (orCELL_PCH) state).

Functions of Iur interface in UTRAN (1/3)Support basic inter RNC mobility

CN

M S

BS BS

S-RNC RNC

• 2. Allows the Inter RNC cell update+ SRNC relocation (User in RRCCELL_FACH state).

CN

BS

M S

BS

S-RNCTarget

RNC

BS

URA

SRNC Relocat ion

Cell Update

• Only signalling, no user data• Iur interface is not involved in Inter RNC hard handover!

URA Update

pagi ng pagi ng


Functions of Iur interface in UTRAN (2/3)Support dedicated ch. traffic between two RNCs

• 1. Allows inter RNC soft handover • 2. Allows anchor SRNC when theUser is in dedicated channel state

CN

S-RNCD-RNC+ M DC

• Support user data transfer with dedicated connection

• Support of downlink shared transport channel (DSCH)

CN

BS

M S

BS

S-RNC + M DC

D-RNC

BS BS

M S


Functions of Iur interface in UTRAN (3/3)Support common ch. traffic between two RNCs

CN

BS

M S

S-RNC D-RNC

• Allows anchoring of SRNC also whenUE is in common channel(RACH/FACH) state

• Support user data transfer with commontransport connection


Iur protocol structure

AAL5

Q.2150. 1

SSCF-NNI

SSCOP

M TP3-B

AAL5

IP

SCTP

SCCP

UDP

ITUN

SSCF-NNI

SSCOP

M TP3-B

IP

SCTP

UDP

ITUN

RNSAP

Control Plane User PlaneRadioNetwork

LayerCCHFP

DCHFP

Transpor tNetwork

Layer

Physi cal Layer

Transpor tUser

NetworkPlane

Transpor tUser

NetworkPlane


ATM

Q.2630. 1

AAL2

More information: 25.420 UTRAN Iur Interface: General Aspects and Principles


RNSAP Functions

• Radio Link Management: This function allows the SRNC to manage radiolinks using dedicated resources in a DRNS.

• Physical Channel Reconfiguration: This function allows the DRNC toreallocate the physical channel resources for a Radio Link.

• Radio Link Supervision: This function allows the DRNC to report failures andrestorations of a Radio Link.

• Compressed Mode Control [FDD]: This function allows the SRNC to controlthe usage of compressed mode within a DRNS

• Measurements on Dedicated Resources: This function allows the SRNC toinitiate measurements on dedicated resources in the DRNS. The function alsoallows the DRNC to report the result of the measurements.

• DL Power Drifting Correction [FDD]: This function allows the SRNC toadjust the DL power level of one or more Radio Links in order to avoid DLpower 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 topass information between the UE and the SRNC on a CCCH controlled by theDRNS.

• Paging: This function allows the SRNC to page a UE in a URA or a cell in theDRNS.

• Common Transport Channel Resources Management: This functionallows the SRNC to utilise Common Transport Channel Resources within theDRNS (excluding DSCH resources for FDD).

• Relocation Execution: This function allows the SRNC to finalise aRelocation previously prepared via other interfaces.

• Reporting general error situations: This function allows reporting of generalerror situations, for which function specific error messages have not beendefined.

More information: 25.423 UTRAN Iur Interface RNSAP Signalling


Iub Protocol Structure (25.430)

AAL5

SSCOP

SSCF-UNI

Q.2150. 2

SSCOP

AAL5

SSCF-UNI

NBAP

Transpor tNetwork

Layer

Physi cal Layer

Transpor tUser

NetworkPlane


Transpor tUser

NetworkPlane


RadioNetwork

Layer

ATM

Q.2630. 1

AAL2

DC

H FP

RA

CH

FP

DS

CH

FP

FA

CH

FP

PC

H FP

US

CH

FP


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 thepossibility to manage the configuration of Common Transport Channels in a NodeB.

• System Information Management: This function gives the CRNC the ability tomanage the scheduling of System Information to be broadcast in a cell.

• Resource Event Management: This function gives the Node B the ability toinform the CRNC about the status of Node B resources.

• Configuration Alignment: This function gives the CRNC and the Node B thepossibility to verify that both nodes has the same information on the configurationof the radio resources.

• Measurements on Common Resources: This function allows the CRNC toinitiate measurements in the Node B. The function also allows the Node B toreport 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 tomanage the synchronisation of a TDD cell in a Node B.

• Radio Link Management: This function allows the CRNC to manage radio linksusing dedicated resources in a NodeB.

• Radio Link Supervision: This function allows the CRNC to report failures andrestorations of a Radio Link.

• Measurements on Dedicated Resources: This function allows the CRNC toinitiate measurements in the NodeB. The function also allows the NodeB to reportthe result of the measurements.

• DL Power Drifting Correction (FDD): This function allows the CRNC to adjustthe DL power level of one or more Radio Links in order to avoid DL powerdrifting between the Radio Links.

• Reporting general error situations: This function allows reporting of generalerror 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

Matti Turunen

Nokia Mobile Phones



Procedures Related to Data Transfer

3G-GGSN

Activat e PDP Context Accept

Create PDP Context Response

Create PDP Context Request

Activat e PDP Context Request

3G-SGSNUTRANM S

Radio Access Bearer Setup

Attach Request

A ttach Accept

RRC Connect ion Establ ishm ent


Typical Configuration CasesParam et er Layer A B C D E F

Radio bearerparam eters

RLC param eters RLC X

Logical channelm ultiplexi ng priority

M AC X

Transpor tchannelparam eters

Transpor t channelschedul ing priority

M AC X

TFS L1+M AC X XTFCS L1+M AC X XSubset of TFCS M AC X XTranspor t channeltype switchi ng

M AC X X X

Physi cal channel param eters L1 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


RRC Connection Establishment

UE UTRAN

RRC CO NNECTIO N REQ UEST

RRC CO NNECTIO N SETUP

RRC CO NNECTIO N SETUP CO M PLETE

CCCH; TR RLC- Initial UE identity- Establishment cause- Initial UE capability

CCCH; TR RLC- Initial UE identity- Establishment cause- Initial UE capability

CCCH; UM RLC- Initial UE identity- U-RNTI- Capability update requirement- Information about the radio bearer assigned for the signalling link- transport channel information

CCCH; UM RLC- Initial UE identity- U-RNTI- Capability update requirement- Information about the radio bearer assigned for the signalling link- transport channel information

DCCH; AM RLC- Integrity protection & ciphering configuration information- Capability information if requested

DCCH; AM RLC- Integrity protection & ciphering configuration information- Capability information if requested


Radio Bearer Establisment

UE UTRAN

RADIO BEARER SETUP

RADIO BEARER SETUP CO M PLETE

DCCH; AM or UM RLC- NAS binding info- Radio bearer information: - L1 configuration information - new/modified transport channels - MAC logical channel priority - Transport format set(s) - Transport format combination set(s) - RLC configuration information - PDCP configuration information

DCCH; AM or UM RLC- NAS binding info- Radio bearer information: - L1 configuration information - new/modified transport channels - MAC logical channel priority - Transport format set(s) - Transport format combination set(s) - RLC configuration information - PDCP configuration information

DCCH; AM RLC- Optional integrity check info



Radio Bearer Reconfiguration

UE UTRAN

RADIO BEARER RECO NFIG URATIO N

RADIO BEARER

RECO NFIG URATIO N CO M PLETE

DCCH; AM or UM RLC- Radio bearer information (change ofQoS): - L1 configuration information - new/modified transport channels - MAC logical channel priority - Transport format set(s) - Transport format combination set(s) - RLC configuration information - PDCP configuration information

DCCH; AM or UM RLC- Radio bearer information (change ofQoS): - L1 configuration information - new/modified transport channels - MAC logical channel priority - Transport format set(s) - Transport format combination set(s) - RLC configuration information - PDCP configuration information




Radio Bearer Release

UE UTRAN

RADIO BEARER RELEASE

RADIO BEARER RELEASE CO M PLETE

DCCH; AM or UM RLC- Identification of the radio bearer to be released- Radio bearer information for remaining radio bearers: - L1 configuration information - new/modified transport channels - MAC logical channel priority - Transport format set(s) - Transport format combination set(s)

DCCH; AM or UM RLC- Identification of the radio bearer to be released- Radio bearer information for remaining radio bearers: - L1 configuration information - new/modified transport channels - MAC logical channel priority - Transport format set(s) - Transport format combination set(s)




Transport Channel Reconfiguration

UE UTRAN

TRANSPO RT CHANNEL

RECO NFIG URATIO N

TRANSPO RT CHANNEL


DCCH; AM or UM RLC- Configuration info of transport formatset for a transport channel - L1 configuration information - new/modified transport channels - Transport format set(s) - Transport format combination set(s)

DCCH; AM or UM RLC- Configuration info of transport formatset for a transport channel - L1 configuration information - new/modified transport channels - Transport format set(s) - Transport format combination set(s)




Physical Channel Reconfiguration

UE UTRAN

PHYSICAL CHANNEL

RECO NFIG URATIO N

PHYSICAL CHANNEL


DCCH; AM or UM RLC- L1 physical channel configurationinformation- change of transport channel (no transport format information, if TFs change then Transport Channel Reconfiguration is used)

DCCH; AM or UM RLC- L1 physical channel configurationinformation- change of transport channel (no transport format information, if TFs change then Transport Channel Reconfiguration is used)




Transport Format Combination Control

UE UTRAN

TRANSPO RT FO R M ATCO M BINATIO N CO NTRO L

DCCH; TM, AM or UM RLC- Reconfiguration of allowed transport format combinations within thetransport format combination set- The network can optionally specify the duration for which a new transport format combination set applies

DCCH; TM, AM or UM RLC- Reconfiguration of allowed transport format combinations within thetransport format combination set- The network can optionally specify the duration for which a new transport format combination set applies


Dynamic Resource Allocation Control(DRAC) of Uplink DCH

UE UTRAN

SYSTEM INFORM ATION

RB Establ ishm entRB Reconf igurationRB ReleaseTranspor t Channel Reconf iguration

BCCH; TM RLC- DRAC procedures are applied in this cell- DRAC information: - Transmission probability (ptr ) - Maximum bit rate (Max bit rate)

BCCH; TM RLC- DRAC procedures are applied in this cell- DRAC information: - Transmission probability (ptr ) - Maximum bit rate (Max bit rate)

DCCH; UM or AM RLC- Dynamic Control -parameter included in messages, indicates that DCH iscontrolled by the DRAC procedure - Transmission time validity (Tvalidity ) - Time duration before retry (Tretry ) - Silent period duration before release

DCCH; UM or AM RLC- Dynamic Control -parameter included in messages, indicates that DCH iscontrolled by the DRAC procedure - Transmission time validity (Tvalidity ) - Time duration before retry (Tretry ) - Silent period duration before release

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 byDRAC)


Measurements

UE UTRAN

M EASUREM ENT CO NTRO L

UE UTRAN

M EASUREM ENT REPO RT

DCCH; AM RLC- Setup, modify or release measurements: - Intra-frequency measurement - Inter-frequency measurement - Inter-system measurement - Traffic volume measurement - Quality measurement

DCCH; AM RLC- Setup, modify or release measurements: - Intra-frequency measurement - Inter-frequency measurement - Inter-system measurement - Traffic volume measurement - Quality measurement

DCCH; AM or UM RLC- Measurements results- Can be periodic or triggered by an event

DCCH; AM or UM RLC- Measurements results- Can be periodic or triggered by an event


Traffic Volume Measurements

Threshol d

Payload

Report 1

Tim e

Report 2

Threshol d

Payload

Report 1

Tim e

No Report

Short pendi ngtim e after tri gger

Long pendi ngtim e after tri gger

Pending tim e after trigger Pending tim e after trigger

- 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

Documents