100% found this document useful (1 vote)
2K views

UMTS Signalling

Uploaded by

Simranbir Singh
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
2K views

UMTS Signalling

Uploaded by

Simranbir Singh
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 53

UMTS

Universal Mobile
Telecommunications
System

Signalling

Signalling protocol details


Chapter contents

» UMTS Protocol Internetworking Architecture


» Part 1: Transport Network Protocols, CS and PS
» Part 2: Radio Network Protocols, CS and PS
» Part 3: System Network Protocols, CS and PS
» Examples of UMTS procedures
UMTS Network Protocol Architecture

Uu Iub Iu E / Gn
NodeB RNC MSC VLR SGSN GMSC GGSN

User Plane
Control Plane
System Network Layer
User Plane
Control Plane
Radio Network Layer
User Plane
Control Plane
Transport Network Layer
UMTS Network Transactions
Uu / Iub – Control-Plane

MM / SM / CC MM/SM/CC

RRC RRC AAL2L3 NBAP

RLC RLC STC

MAC MAC SSCF- UNI

UP FP SSCOP

AAL2 AAL5

WCDMA NodeB ATM RNC


Uu / Iub – User-Plane

Application data Application data

PDCP BMC PDCP BMC

RLC RLC

MAC MAC

UP FP

AAL2

WCDMA NodeB ATM RNC


Iur – User- / Control-Plane

Control-Plane User-Plane

MM/SM/CC Application data

RRC AAL2L3 RNSAP PDCP BMC

STC SCCP

RLC MTP3-B M3UA RLC

MAC SSCF-NNI SCTP MAC

UP FP SSCOP IP UP FP

AAL2 AAL5 AAL2

RNC ATM RNC ATM RNC


IuCS – User- / Control-Plane

Control-Plane User-Plane

MM/SM/CC Application data

RANAP AAL2L3 TAF AMR

SCCP STC RLP

MTP3-B M3UA

SSCF-NNI SCTP

SSCOP IP
Iu UP

AAL5 AAL2

RNC ATM MSC ATM RNC


IuPS – User- / Control-Plane

Control-Plane User-Plane

MM / CC / SS Application data

RANAP IP

SCCP

MTP3-B M3UA
GTP-U
SSCF-NNI SCTP
UDP
SSCOP IP
IP

AAL5 AAL5

RNC ATM SGSN ATM RNC


E – User- / Control-Plane

Control-Plane User-Plane

MAP Application data

TCAP ISUP

SCCP

MTP-L3

MTP-L2
MSC PCM MSC PCM MSC
VLR VLR VLR
Gn – User- / Control-Plane

Control-Plane User-Plane

Application data

IP

GTP-C GTP-U

UDP UDP

IP IP

AAL5 AAL5

SGSN ATM Ethernet GGSN ATM Ethernet SGSN


Signalling Part 2

Radio Network Layer

ASN.1
RRC, NBAP, RNSAP and RANAP
AAL2L3 (ALCAP)
Iu UP, AMR, TAF, RLP
PDCP and BMC
RRC

» Radio Resource Control


» Routing of higher layer messages to different MM/CM entities (UE side)
or different core network domains
» Creation and management of Radio Bearers
» Broadcasting of System Information
» Paging of UEs
» Dedicated Control handles all functions specific to one UE
» Location Management
» Handover
» Power Management (outer loop power control)
» Configuration of lower layer protocols
» Management of measurement reports

» Specified in 3GPP 25.331


RRC States

Idle Mode
Camping on a UTRAN cell Camping on a GSM cell
GPRS idle mode
Establish Establish Establish
Dedicated Shared Cell RR-
RRC- RRC- reselection Connection
Connection Connection Init Rel.
Release Release of of Release
Dedicated Shared TBF TBF RR-
RRC- RRC- Connection
Connection Connection GPRS
Packet
CELL_DCH CELL_FACH
Transfer
Mode

GSM: Handover GSM


URA_PCH CELL_PCH UTRAN: Connected
Inter-RAT Handover Mode
UTRAN Connected Mode
RRC – UMTS Connected Mode States

UTRAN Connected Mode

Release last dedicated channel


CELL_DCH CELL_FACH
Allocation of dedicated channel

P CH
RA_ r
r : U nsfe RRC State
RRC State Indicator: to a Indicator:
URA_PCH i ca L tr CELL_PCH
d U
e In i t.
at In
St g or Paging
C n
RR agi or
P Init. UL
transfer

URA_PCH CELL_PCH
RRC Connection Establishment

„ ... a point-to-point bi-directional connection between RRC peer entities


in the UE and the UTRAN characterised by the allocation of a U-RNTI.
A UE has either zero or one RRC connection.“
RNC

Idle
( RLC-SAP: TM, CCCH ) RRC CONNECTION REQUEST
[ RRC TAId, Initial UE Id, Establishment Cause ]
( RLC-SAP: UM, CCCH ) RRC CONNECTION SETUP
[ RRC TAId, new U-RNTI, SRB ]
( RLC-SAP: AM, DCCH ) RRC CONNECTION SETUP COMPLETE
Connected [ RRC TAId, UE Radio Acces Capability ]
Successful
Unsuccessful
( RLC-SAP: TM, CCCH ) RRC CONNECTION REQUEST
[ RRC TAId, Initial UE Id, Establishment Cause ]
( RLC-SAP: UM, CCCH ) RRC CONNECTION REJECT
[ RRC TAId, Cause ]
RRC Connection Release

RNC

( RLC-SAP: UM, DCCH ) RRC CONNECTION RELEASE


[ RRC TAId, Release Cause ]

( RLC-SAP: UM / AM, DCCH ) RRC CONNECTION RELEASE COMPLETE


[ RRC TAId ]

( RLC-SAP: UM, CCCH ) RRC CONNECTION RELEASE


[ U-RNTI, RRC TAId, Release Cause ]
RRC Signalling Connection

RNC

( RLC-SAP: AM, DCCH ) INITIAL DIRECT TRANSFER


[ CN Domain Id, NAS SDU ]
( RLC-SAP: AM, DCCH ) DOWNLINK DIRECT TRANSFER
[ RRC TAId, CN Domain Id, NAS SDU ]
( RLC-SAP: AM, DCCH ) UPLINK DIRECT TRANSFER
[ CN Domain Id, NAS SDU ]

( RLC-SAP: AM, DCCH ) SIGNALLING CONNECTION RELEASE


[ RRC TAId, CN Domain Id ]
RRC Radio Bearer Setup

RNC

( RLC-SAP: AM, DCCH ) RADIO BEARER SETUP *


[ RRC TAId, SRB and RB Info / List etc. ]

( RLC-SAP: AM, DCCH ) RADIO BEARER SETUP * COMPLETE


[ RRC TAId ]

( RLC-SAP: AM, DCCH ) RADIO BEARER SETUP *


[ RRC TAId, SRB and RB Info / List etc. ]

( RLC-SAP: AM, DCCH ) RADIO BEARER SETUP * FAILURE


[ RRC TAId , Failure Cause ]
NBAP

» Node B Application Part


» Cell Configuration Management
» Common Transport Channel Configuration
» System Information Management
» Resource Event Management
» Measurements on common and dedicated resources
» Radio Link Management of dedicated resources
» Radio Link Supervision

» Specified in 3GPP 25.433


NBAP Elementary Procedure

» Two classes of elementary procedures:


» Class 1: Elementary procedure with response,
success or failure
» Class 2: Elementary procedure without response
» NBAP Initiating Message is transporting the procedure request
» For Class 1 elementary procedure the response is transmitted
» Success: Successful Outcome Message
» Failure: Unsuccessful Outcome Message
» The elementary procedure is identified by the parameter
Procedure Identification Code.

» The CRNC Communication Context contains all info for the CRNC to
communicate with a specific UE.
» The Context is identified by the parameter
CRNC Communication Context Identifier.
NBAP Example Procedure

NodeB RNC

INITIATING MESSAGE
[ Procedure Code: RADIO LINK SETUP,
Transaction-Id, C-Id, Channel parameter ]
SUCCESSFUL OUTCOME
[ Procedure Code: RADIO LINK SETUP,
Transaction-Id, Channel parameter ]
Successful
Unsuccessful
INITIATING MESSAGE
[ Procedure Code: RADIO LINK SETUP,
Transaction-Id, C-Id, Channel parameter ]
UNSUCCESSFUL OUTCOME
[ Procedure Code: RADIO LINK SETUP,
Transaction-Id, Cause ]
RANAP

» Radio Access Network Application Part


» Transfer of NAS-PDU between CN and UTRAN
» Overall RAB management
» Relocating of SRNC
» Controlling the security mode of UTRAN
» Paging the UE
» Release of RAB and the Iu connection resources
» SCCP uses SSN=142 for RANAP identification

» Specified in 3GPP 25.413


RANAP Elementary Procedure

» Three classes of elementary procedures:


» Class 1: Elementary procedure with response
( success and / or failure )
» Class 2: Elementary procedure without response
» Class 3: Elementary procedure with possibility of
multiple responses ( success and/or failure )
» RANAP Initiating Message is transporting the procedure request
» For Class 1 elementary procedure the response is transmitted
» Success: Successful Outcome Message
» Failure: Unsuccessful Outcome Message
» For Class 3 elementary procedure the response is transmitted as
Outcome Message
RANAP Example Procedure

RNC MSC

INITIATING MESSAGE
Class 2
[ Procedure Code: INITIAL UE MESSAGE,
CN Domain Id, LAI, SAI, Iu Signal.Conn.Id, NAS PDU ]
INITIATING MESSAGE
[ Procedure Code: SECURITY MODE CONTROL,
Class 1 Integrity protection info, key status ]
SUCCESSFUL OUTCOME
[ Procedure Code: SECURITY MODE CONTROL,
Integrity protection algorithm ]

INITIATING MESSAGE
[ Procedure Code: RAB ASSIGNMENT,
Class 3 RAB Id and Info, Cause ]
OUTCOME
[ Procedure Code: RAB ASSIGNMENT,
Success or failure IEs for RAB Id and Info ]
Signalling Part 3

System Network Layer


Circuit Switched:
Mobility Management and Call Control
control plane between CN nodes
Packet Switched:
Mobility and Session Management
control plane between CN nodes
Location Based Services
CS Mobility Management

» Procedures well known from GSM


» MM procedures to establish and release connections.
» Transfer of Call Management (CM) sublayer messages.
» MM common procedures for security functions, e.g.
Authentication procedure.
» MM specific procedures for location functions like
Periodic location updating or IMSI attach procedure.
» UE identified by IMSI or TMSI.

» Specified in 3GPP 24.008


CS Call Control

» Procedures well known from GSM


» CC establishes and releases CC connections between UE and
CN.
» Activation of voice/multimedia codec.
» Based on 3G-324M, variant of H.324. See 3GPP 26.111.

» Interworking with RANAP for establishment of a RAB.


» CC SETUP QoS will be mapped onto RANAP RAB assignment.

» Specified in 3GPP 24.008


CS MOC Example

MSC VLR
MM: CM Service Request
[ Mobile Identity, MS Classmark ]
MM: CM Service Accept
CC: Setup
[ Called Party Number, Bearer Capability ]
CC: Call Proceeding
MM: Authentication Request
MM: Authentication Response
CC: Alert
CC: Connect
CC: Connect Ack.
Call set-up
Call release CC: Disconnect [ Cause ]
CC: Relase
CC: Reease Complete
PS Mobility Management

» Procedures well known from GPRS (GMM)


» GMM protocol makes use of a signalling connection between UE and
SGSN.
» GMM establishes and releases GMM contexts, e.g. GPRS Attach.
» GMM specific procedures for location functions like
Periodic routing area updating.
» New message implemented to provide service to CM sublayer on top
of GMM:
» SERVICE REQUEST message
» Initiated by UE, used to establish a secure connection to the network and
to request the bearer establishment for sending data.
» UE identified by IMSI or P-TMSI

» Specified in 3GPP 24.008


PS Session Management

» Procedures well known from GPRS (SM)


» Counterpart to CS CC protocol, i.e.
it is used to establish and release packet data sessions.
» SM procedures to setup and release one or more
PDP contexts.
» PDP Contexts are handled in UE and GGSN.
» SGSN represents interworking function.

» Specified in 3GPP 24.008


PS Activate PDP Context Example

SGSN

GMM: Service Request


[ Mobile Identity, MS Classmark ]
GMM: Service Accept

SM: Activate PDP Context Request


[ APN, Type of PDP-Address, QoS ]

SM: Activate PDP Context Accept


Connection [ PDP-Address, QoS ]
set-up
Connection
release SM: Deactivate PDP Context Request
SM: Deactivate PDP Context Accept
Iu Procedures

• Location Update on IuCS


• MOC on IuCS
• MTC on IuCS
• Attach on IuPS
• PDP Context on IuPS
Location Update on IuCS 1/2

* : Initiating Message
NodeB RNC MSC

RRC Connection Request


NBAP: Radio Link Setup

AAL2L3: Establish
RRC Connection Setup

Initial Direct Transfer [ NAS: LUREQ ]


CR – RANAP: * Initial UE Message [ MM: LUREQ ]

CC

DT1 – RANAP: * Direct Transfer [ MM: AUTREQ ]


DL Direct Transfer [ NAS: AUTREQ ]
UL Direct Transfer [ NAS: AUTRESP ]
DT1 – RANAP: * Direct Transfer [ MM: AUTRESP ]

DT1 – RANAP: * Common ID


Location Update on IuCS 2/2

* : Initiating Message
NodeB RNC MSC

Security Mode Command DT1 – RANAP: InitiatingMsg [ Security Mode Control ]

Security Mode Complete


DT1 – RANAP: SuccOutcome [ Security Mode Control ]

DT1 – RANAP: * Direct Transfer [ MM: LUACC ]


DL Direct Transfer [ NAS: LUACC ]

DT1 – RANAP: InitiatingMsg [ Iu Release ]


RRC Connection Release

NBAP: Radio Link Deletion

AAL2L3: Release DT1 – RANAP: SuccOutcome [ Iu Release ]

RLSD

RLC
MOC on IuCS 1/4

* : Initiating Message
NodeB RNC MSC

Initial Direct Transfer [ NAS: CMSREQ ]


CR – RANAP: * Initial UE Message [ MM: CMSREQ ]
CC

DT1 – RANAP: * Direct Transfer [ MM: AUTREQ ]


DL Direct Transfer [ NAS: AUTREQ ]
UL Direct Transfer [ NAS: AUTRESP ]
DT1 – RANAP: * Direct Transfer [ MM: AUTRESP ]

DT1 – RANAP: * Common ID

Security Mode Command DT1 – RANAP: InitiatingMsg [ Security Mode Control ]

Security Mode Complete


DT1 – RANAP: SuccOutcome [ Security Mode Control ]

UL Direct Transfer [ NAS: SETUP ]


DT1 – RANAP: * Direct Transfer [CC : SETUP ]
MOC on IuCS 2/4

* : Initiating Message
NodeB RNC MSC

DT1 – RANAP: * Direct Transfer [ MM: CPROC ]


DL Direct Transfer [ NAS: CPROC ]
DT1 – RANAP: InitiatingMsg [ RAB Assignment ]
NBAP: Synchronised Radio Link
Reconfiguration Preparation

AAL2L3: Establish Request AAL2L3: Establish Request

AAL2L3: Establish Confirm AAL2L3: Establish Confirm

Iu UP: ProcCode [ Initialisation ]


Iu UP: Ack

Radio Bearer Setup


DT1 – RANAP: Outcome [ RAB Assignment ]
MOC on IuCS 3/4

* : Initiating Message
NodeB RNC MSC

DT1 – RANAP: * Direct Transfer [CC : ALERT ]


DL Direct Transfer [ NAS: ALERT ]
DT1 – RANAP: * Direct Transfer [CC : CONNECT ]
DL Direct Transfer [ NAS: CONNECT ]
DT1 – RANAP: * Direct Transfer [CC : CONN ACK ]
DL Direct Transfer [ NAS: CONN ACK ]

Iu UP: Type 0 [ AMR data ]


Iu UP: Type 0 [ AMR data ]
Iu UP: Type 0 [ AMR data ]

DT1 – RANAP: * Direct Transfer [CC : DISC ]


DL Direct Transfer [ NAS: DISC ]
DT1 – RANAP: * Direct Transfer [CC : RELEASE ]
DL Direct Transfer [ NAS: RELEASE ]
DT1 – RANAP: * Direct Transfer [CC : REL COMP ]
DL Direct Transfer [ NAS: REL COMP ]
MOC on IuCS 4/4

NodeB RNC MSC

DT1 – RANAP: InitiatingMsg [ Iu Realease ]


RRC Connection Release

NBAP: Radio Link Deletion

AAL2L3: Relase ( DTCH )


AAL2L3: Relase ( DCCH )
DT1 – RANAP: SuccOutcome [ Iu Release ]

AAL2L3: Release Request

AAL2L3: Release Confirm

RLSD

RLC
MTC on IuCS 1/5

* : Initiating Message
NodeB RNC MSC

UDT – RANAP: Paging


( PCH ) Paging Type 1

RRC Connection Request


NBAP: Radio Link Setup

AAL2L3: Establish ( DCCH )


UL – DL – SYNC

RRC Connection Setup

RRC Connection Setup Comp

Initial Direct Transfer [ NAS: PRES ]


CR – RANAP: * Initial UE Message [ MM: PRES ]

CC
MTC on IuCS 2/5

* : Initiating Message
NodeB RNC MSC

DT1 – RANAP: * Direct Transfer [ MM: AUTREQ ]


DL Direct Transfer [ NAS: AUTREQ ]
UL Direct Transfer [ NAS: AUTRESP ]
DT1 – RANAP: * Direct Transfer [ MM: AUTRESP ]

DT1 – RANAP: * Common ID

Security Mode Command DT1 – RANAP: InitiatingMsg [ Security Mode Control ]

Security Mode Complete


DT1 – RANAP: SuccOutcome [ Security Mode Control ]

DT1 – RANAP: * Direct Transfer [CC : SETUP ]


DL Direct Transfer [ NAS: SETUP ]

UL Direct Transfer [ NAS: CCONF ]


DT1 – RANAP: * Direct Transfer [CC : CCONF ]
MTC on IuCS 3/5

NodeB RNC MSC

DT1 – RANAP: InitiatingMsg [ RAB Assignment ]


Synchronised Radio Link
Reconfiguration Preparation

AAL2L3: Establish Request AAL2L3: Establish Request

AAL2L3: Establish Confirm AAL2L3: Establish Confirm

Iu UP: ProcCode [ Initialisation ]

NBAP: Radio Bearer Setup Iu UP: Ack

DT1 – RANAP: Outcome [ RAB Assignment ]


MTC on IuCS 4/5

* : Initiating Message
NodeB RNC MSC

DL Direct Transfer [ NAS: ALERT ]


DT1 – RANAP: * Direct Transfer [ CC: ALERT ]
DL Direct Transfer [ NAS: CONNECT ]
DT1 – RANAP: * Direct Transfer [ CC: CONNECT ]
DL Direct Transfer [ NAS: CONN ACK ]
DT1 – RANAP: * Direct Transfer [ CC: CONN ACK ]

Iu UP: Type 0 [ AMR data ]


Iu UP: Type 0 [ AMR data ]
Iu UP: Type 0 [ AMR data ]

DT1 – RANAP: * Direct Transfer [CC : DISC ]


DL Direct Transfer [ NAS: DISC ]
DT1 – RANAP: * Direct Transfer [CC : RELEASE ]
DL Direct Transfer [ NAS: RELEASE ]
DT1 – RANAP: * Direct Transfer [CC : REL COMP ]
DL Direct Transfer [ NAS: REL COMP ]
MTC on IuCS 5/5

NodeB RNC MSC

DT1 – RANAP: InitiatingMsg [ Iu Realease ]


RRC Connection Release

NBAP: Radio Link Deletion

AAL2L3: Relase ( DTCH )


AAL2L3: Relase ( DCCH )
DT1 – RANAP: SuccOutcome [ Iu Release ]

AAL2L3: Release Request

AAL2L3: Release Confirm

RLSD

RLC
Attach on IuPS 1/2

* : Initiating Message
NodeB RNC SGSN

RRC Connection Request


NBAP: Radio Link Setup

AAL2L3: Establish
RRC Connection Setup

Initial Direct Transfer [ NAS: ATRQ ]


CR – RANAP: * Initial UE Message [ GMM: ATRQ ]

CC

DT1 – RANAP: * Direct Transfer [ GMM: ACRQ ]


DL Direct Transfer [ NAS: ACRQ ]
UL Direct Transfer [ NAS: ACRE ]
DT1 – RANAP: * Direct Transfer [ GMM: ACRE ]
Attach on IuPS 2/2

* : Initiating Message
NodeB RNC MSC

Security Mode Command DT1 – RANAP: InitiatingMsg [ Security Mode Control ]

Security Mode Complete


DT1 – RANAP: SuccOutcome [ Security Mode Control ]

DT1 – RANAP: * Direct Transfer [ GMM: ATAC ]


DL Direct Transfer [ NAS: ATAC ]

UL Direct Transfer [ NAS: ACOM ]


DT1 – RANAP: * Direct Transfer [ GMM: ACOM ]

DT1 – RANAP: InitiatingMsg [ Iu Release ]


RRC Connection Release

NBAP: Radio Link Deletion

AAL2L3: Release DT1 – RANAP: SuccOutcome [ Iu Release ]


RLSD
RLC
PDP Context on IuPS 1/3

* : Initiating Message
NodeB RNC MSC

Initial Direct Transfer [ NAS: SREQ ]


CR – RANAP: * Initial UE Message [ GMM: SREQ ]
CC

DT1 – RANAP: * Direct Transfer [ GMM: ACRQ ]


DL Direct Transfer [ NAS: ACRQ ]
UL Direct Transfer [ NAS: ACRE ]
DT1 – RANAP: * Direct Transfer [ GMM: ACRE ]

DT1 – RANAP: * Common ID

Security Mode Command DT1 – RANAP: InitiatingMsg [ Security Mode Control ]

Security Mode Complete


DT1 – RANAP: SuccOutcome [ Security Mode Control ]
PDP Context on IuPS 2/3

* : Initiating Message
NodeB RNC MSC

UL Direct Transfer [ NAS: APCR ]


DT1 – RANAP: * Direct Transfer [SM : APCR ]

DT1 – RANAP: InitiatingMsg [ RAB Assignment ]


NBAP: Synchronised Radio Link
Reconfiguration Preparation

AAL2L3: Establish

NBAP: Radio Bearer Setup

DT1 – RANAP: Outcome [ RAB Assignment ]

DT1 – RANAP: * Direct Transfer [ SM : APCA ]


DL Direct Transfer [ NAS: APCA ]

Application data flow


on dedicated VPI/VCI
using AAL5
PDP Context on IuPS 3/3

NodeB RNC MSC

UL Direct Transfer [ NAS: DPCR ]


DT1 – RANAP: * Direct Transfer [SM : DPCR ]
DT1 – RANAP: * Direct Transfer [ SM : DPCA ]
DL Direct Transfer [ NAS: DPCA ]

DT1 – RANAP: InitiatingMsg [ Iu Realease ]


RRC Connection Release

NBAP: Radio Link Deletion

AAL2L3: Relase ( DTCH )


AAL2L3: Relase ( DCCH )
DT1 – RANAP: SuccOutcome [ Iu Release ]

RLSD

RLC
CS-Control Plane between CN nodes

» Standard SS#7 protocols are used as control plane transport layers.


» For circuit switched procedures ISDN user part is used to setup
connections and to control the traffic channel.
» Procedures for network specific functions are handled by the MAP
protocol, known from GSM/GPRS.
» Procedures for subscriber specific functions are handled by INAP and
CAP protocol, also know from GSM/GPRS.
» More or less old specification numbers are used. Version number will
indicate the type of network standard
(GSM, GPRS or UMTS)
GPRS Tunneling Protocol Interfaces

» Three types of GTP protocols


1. GTP – Control Plane
2. GTP – User Plane
3. GTP‘
CGF
3.
2.

UTRAN SGSN GGSN


1. + 2.

SGSN

2.

UTRAN SGSN
other PLMN
GTP

» Tunnel is identified by Tunnel Endpoint Identifier


» C-Plane: TID-C; U-Plane: TID-D (Data)
» GTP-C:
» Establish, management and release of user specific tunnels between
GSNs for exchange of signalling information.
» supports creation, modification and deletion of PDP Contexts
» supports mobility management (relocation of RNC)

» GTP-U:
» Transport of application data

» GTP‘:
» Transport of charging data records from SGSN and GGSN to Charging
Gateway.

» Specified in 3GPP 29.060


GTP – C and – U Example

SGSN GGSN
GTP-C-TM: Create PDP Context Request
[ TID-C, DL-TID-D, MSISDN, NSAPI, APN, PDP-Info ]

GTP-C-TM: Create PDP Context Response


[ TID-C, UL-TID-D, PDP-Address, Cause ]

GTP-U: Tunnel-PDU
[ UL-TID-D, ]
GTP-U: Tunnel-PDU
[ UL-TID-D, ]
GTP-U: Tunnel-PDU
PDP Context [ DL-TID-D, ]
set-up
PDP Context
release GTP-C-TM: Delete PDP Context Request
[ TID-C, NSAPI, Teardown Ind ]

GTP-C-TM: Delete PDP Context Response


[ TID-C, Cause ]

You might also like