13 umts-cm.ppt [kompatibilitätsmodus] · pdf file• 3g 23.060 gprs, service...

Communication Managementg

• Connection management (call control – CC) for CS mode

• Session management (SM) for PS mode

References:• Kaaranen, Ahtiainen, Laitinen, Naghian, Niemi: UMTS Networks – Architecture, Mobility

and Services. Wiley 2001, ch. 5.3• 3G 23.060 GPRS, Service Description, ch. 9

UMTS Networks 1Andreas Mitschele-Thiel 12-Nov-08

• 3G 24.007 Mobile radio interface signalling layer 3, General aspects

Fundamental Difference Between CS and PS Communication Differences require CS and PS CommunicationConnection (e.g. voice, CS data) • clearly defined start and end

qdifferent solutions to• mobility mgmt and

clearly defined start and end • no burstiness

minutes

• communication mgmt

minutesconnection

setupconnection

release

Packet session (e.g. web surfing)• start and end times are typically unknown to the UMTS system• traffic is highly bursty

hours


seconds

Connection Management – CS Mode

Basic activities of connection management

• number analysis (check called number for correctness, check of call y ( ,barring of calling number)

• set up of connection (according to routing rules)

• collection of charging information

• release of connection

Types of calls• normal voice call• normal voice call

• emergency call

• data call (FAX etc )• data call (FAX, etc.)

UMTS Networks 3Andreas Mitschele-Thiel 12-Nov-08 o

Connection Management

Access Domain Other ElementsMSC/VLR

Connection

MOC PTC

ConnectionManagement

MTCPOC

MTC

A call consists of several call legs (parts of the call)

• Mobile Originated Call (MOC)

• Mobile Terminated Call (MTC)

• PSTN Originated Call (POC)


• PSTN Terminated Call (PTC)

o

Connection ManagementNet o k Inte o kingNetwork Interworking• echo cancelation (2/4-line conversion echo, acustic echo)• modems and rate adapters

Charging• Collection of charging information for each leg due to UMTS commercial

model (subscriber, network operator, service provider, content ( , p , p ,provider)

• Fraud control between serving and home network• Cost control by charged partyy g p y• Itemized billing

Call Detail Record (CDR)– Charged partyg p y– Terminal identity and class – called address– Used 3G resources – QoS parameters– Serving 3G network and network element identities– Time stamps


– MM information– CDR identity

o

CS)

Cal

l (C

inat

ede-

Term

Mob

iletr

ol o

f ll

Con

t


Ca

Service graph of Call Control entity - Network sideMNCC-SETUP-REQ

MNCC-SETUP-REQ(excerpt)

RELEASE

NULL0

19MNCC-REL

MNCC-REJ-IND

MNCC-SETUP-REQ

MNCC-REJ-INDMNCC-REL-CNF

MNCC-DISC- IND

RELEASEREQUEST

DISONNECTINDICATION

DISCONNECT

CALL INIT CALL PRESENT

1 19

12

6

11

REL-IND

MNCC-CALL-CONF-IND

MNCC-CALLPROC-REQ

MNCC-RELREQ

INDICATIONREQUESTNO CALLPROCEEDING

MT CALLCONFIRMED

3 9MNCC-DISC-IND

MNCC-DISC- REQMNCC-

IND

MNCC-ALERT-

MNCC-PROGRESS-REQ MNCC-

ALERT-REQ

CALLDILIVERED

CALLRECEIVED

4

7

MNCCALERT-IND

STATES4,6,8,9,10

IND MNCC-SETUP-CNF

MNCCCONNECT28

MNCC-SETUP-RSP

CONNECTREQUEST

8

MNCC-SETUP-CNF

CONNECTINDICATION

28 RSP

Output des Automaten: • Request (REQ),

R (RSP)ACTIVE10

MNCC

MNCC-SETUP-COMPL-REQ• Response (RSP)Input des Automaten: • Indication (IND), • Confirmation (CNF)


MNCC-FACILITY-IND

ANY STATEEXCEPT 0 ANY STATE MNCC-

REL-IND

0ANY STATEEXCEPT 0,19

MNCC-FACILITYREQ

Service graph of Call Control entity - MS sideNULL0 MNCC-SETUP-IND

MNCC-SETUP-REQ(excerpt)

RELEASE CALL

NULL0

1 19

MNCC-REJ-REQ

MNCC-

MNCC-REJ-IND MNCC- REL- CNF

REQUESTCALL INITCALL PRESENT

1 19 6

MNCC-REL-REQ

MNCC- DISC-IND

MNCCREL-IND

MNCC-DISC- REQ

MNCC-DISC-IND

MNCC-CALLCONF-REQ

MNCC-CALLPROC-IND

DISONNECTINDICATION

STATES

DISCONNECTREQUEST

NO CALLPROCEEDING

MT CALLCONFIRMED

3 12 911

IND

MNCC-ALERT-REQ

MNCC-DISC-IND

MNCC-DISC-REQ

MNCC-ALERT-MNCC-REL-

MNCC-PROGRESS-IND

STATES3,4,7,8,9,10

RELEASE REQUEST

CALLDELIVERED

CALLRECEIVED419

7

MNCC-SETUP-RSP

REQ

MNCC-MNCC-SETUP-COMPL IND (ERR)

INDREQ

MNCC-SETUP-CNF

ALERTINDREQ

CONNECTREQUEST

8

SETUP-RSPCOMPL-IND (ERR)

MNCC SETUPACTIVE10 MNCC-SETUP-COMP-IND

MNCC-SETUP-CNF

MNCC


MNCC-FACILITY-IND

ANY STATEEXCEPT 0

ANY STATE MNCC-REL-IND

0ANY STATEEXCEPT 0,19

MNCC-FACILITYREQ

o

Session Management – PS Mode

States of SM (state of PDP contexts)– inactive: no packet data transfer, no valid routing information– active: packet data transfer possible, valid routing information

Support for various packet data protocols (PDP)Examples: IP, PPP, X.25

Attributes of packet session: PDP context– defines all parameters of the packet data session by end-to-end p p y

attributes and QoS– one PDP context per PS services with a certain QoS, e.g. for web

serving streaming video packet voice etcserving, streaming video, packet voice, etc.


Session Management: States of PDP Context

A GPRS subscription contains the subscription of one o mo e PDP dd e e

GPRS subscriptionone or more PDP addresses

Each PDP address is described by one or more PDP contexts in the MS SGSN and GGSNPDP PDP contexts in the MS, SGSN, and GGSN

Each PDP context is associated with – A QoS profile

PDPaddress

A QoS profile– a traffic flow template (TFT) to discriminate

flows sharing the same PDP addressPDPcontext

Every PDP context exists independently in one of two PDP states

The PDP state indicates whether data transfer is enabled for that PDP address and TFT or not

PDP stateinactive

PDP stateactive


Reference: 3G 23.060, ch 9

N

Field Description GSM UMTS

IMSI International Mobile Subscriber Identity. X X

NSAPI Network layer Service Access Point Identifier. X Xy

GG

SN MSISDN The basic MSISDN of the MS. X X

PDP Type PDP type; e.g. PPP or IP. X X

PDP Address PDP address; e.g. an IP address. X X

ned

by Dynamic Address Indicates whether PDP Address is static or dynamic. X X

APN in Use The APN Network Identifier currently used. X X

TEID Tunnel Endpoint Identifier. X X

mai

ntai

n

TFT Traffic flow template. X X

QoS Profile Negotiated The quality of service profile negotiated. X X

SGSN Address The IP address of the SGSN currently serving this MS. X X

elds

mre

ss

MNRG Indicates whether the MS is marked as not reachable for PS at the HLR.

X X

Recovery Indicates if the SGSN is performing database recovery. X X

GTP-SND GTP-U sequence number of the next downlink N-PDU to be sent X XCh 1

3

ntex

t fie

P A

ddr q

to the SGSN.GTP-SNU GTP-U sequence number of the next uplink N-PDU to be received

from the SGSN.X X

Charging Id Charging identifier, identifies charging records generated by SGSN and GGSN.

X X

.060

-4.1

.0, C

DP

con

r a P

DP SGSN and GGSN.Charging Characteristics The charging characteristics for this PDP context, e.g. normal,

prepaid, flat-rate, and/or hot billing.X X

Trace Reference Identifies a record or a collection of records for a particular trace. X X

Trace Type Indicates the type of trace. X Xrce:

3G

PP 2

3


PD for yp yp

Trigger Id Identifies the entity that initiated the trace. X X

OMC Identity Identifies the OMC that shall receive the trace record(s). X X

Sour

o


Inactive state:no valid routing or mappingPDP Context

INACTIVE

– no valid routing or mapping information to process data related to PDP address

Activate PDP Context

-> no data transfer-> no updates due to location

changes (even in GPRS attachedDeactivate PDP Context or PMM-DETACHED

changes (even in GPRS-attached states)

PDP context activation (transition to

PDP Context

PDP context activation (transition to active state):– MS-initiated PDP context activation

ACTIVE – network-requested PDP context activation


Reference: 3G 23.060, ch 9


Active state:valid routing or mapping

– valid routing or mapping

information to process data related to PDP address (MS, SGSN, GGSN)

PDP ContextINACTIVE

( )– Requires MM state PMM-idle or

PMM-connected> data transfer possible

Activate PDP Context

-> data transfer possible-> updates due to location changes

PDP context deactivation:

Deactivate PDP Context or PMM-DETACHED

PDP context deactivation:– PDP context deactivation procedure– MM state changes to PMM-PDP Context

detached

PDP context modification, e.g. to dif Q S fil

ACTIVE


Reference: 3G 23.060, ch 9modify QoS profile

Relation between PDP Context and MM

GPRS subscriptionRelation between MM and

PDP states:

PDP

• All PDP contexts of a subscriber are associated with the same MM contextPDP

address

Single

with the same MM contextfor the IMSI of that subscriber

PDPcontext

PDPcontext

PDPcontext

PDPcontext

SingleMM context • The MM state is

independent of the number and state of PDP contexts for the subscriber

• In both the PMM-IDLE and PDP stateinactive

PDP stateactive

the PMM-CONNECTED states, session management may or may not have


activated a PDP context

low RRC PMM SM

UE SGSN GGSNUTRANke

t Fl

idle detached inactive

Cell_ DCH detached inactiveRRC conn. establishment

GPRS attach

g Pa

c

Cell DCH connected active

Cell_DCH connected inactive

GPRS attach(incl. authentication & security)

PDP context establishment (UE originated)

Dur

ing Cell_DCH connected active

Cell_DCH connected active

Cell DCH connected active

RAB allocation CN bearer allocation

Packet data transfer

ates

D

_

URA_PCH connected activeRAB clearing CN bearer clearing

. . .

of S

ta

Cell_FACH connected active


UE initiated service request


mpl

e o


URA_PCH connected active


RAB clearing CN bearer clearing. . .

UMTS Networks 15Andreas Mitschele-Thiel 12-Nov-08Exam

. . .

For details see Kaaranen, ch 5.3.2

low RRC PMM SM

UE SGSN GGSNUTRANke

t Fl. . .

(packet) paging incoming data

URA_PCH connected active

g Pa

c

Cell_DCH connected activeUE initiated service request


(packet) paging incoming dataCell_FACH connected active

Dur

ing Cell_DCH connected active




RAB clearing CN bearer clearing

ates

D URA_PCH connected activec ea g C bea e c ea g

. . .

PDP t t d ti ti

of S

ta

Cell DCH connected inacti e


PDP ctxt deletion

PDP context deactivation and IMSI detach

mpl

e o

)

idle detached inactive

Cell_DCH connected inactive

RRC connection release

UMTS Networks 16Andreas Mitschele-Thiel 12-Nov-08Exam

(con

t‘d

Instead of cell_DCH, cell_FACH may be used for small messages

Service Request Procedures

Usage of procedure:

• MS in PMM-IDLE state:-> request the establishment of a secure connection to a SGSN

to send uplink signalling messages (e g PDP Context Activation– to send uplink signalling messages (e.g. PDP Context ActivationRequest) or

– to send user data or – as paging response or– after regain of radio coverage

• MS in PMM-CONNECTED state:-> request resource reservation for active PDP contexts> request resource reservation for active PDP contexts


Source: 3GPP 23.060-4.1.0, Ch 6.12

Service Request Procedure Initiated by MS

SGSNMS RNC 1. RRC Connection Request

HLR GGSN

Service type: data

2 Service Request

q

1. RRC Connection Setup

yp• setup of signaling connection• allocation of resources for active

PDP context(s)Service type: signaling

If none exists

2. Service Request

3. Security Functions

Service type: signaling• setup of signaling connection,

e.g. to activate PDP context

only

4. Radio Access Bearer Assignment Request

5 Radio Bearer Setup

4. Service Accept

type

dat

a

For PMM-idle mode only

6. Radio Access Bearer

5. Radio Bearer Setup

6. Radio Bearer Setup Complete

r se

rvic

e t

8. Uplink PDU

Assignment Response

7. SGSN-Initiated PDP Context Modification

Fo


Service Request Procedure Initiated by Network

SGSNMS RNC HLR GGSN

1. Downlink PDU2. Paging

2. Paging 3G-SGSN sends a paging request to UTRAN when it3. RRC Connection Request

3. RRC Connection Setup

request to UTRAN when itreceives a downlink packet (e.g., a request for PDP context activation

5. Security Functions

6. Radio Access Bearer Assignment

4. Service Request PDP context activation, MT SMS, user data) for an MS in PMM-IDLE stateThe paging request6. Radio Access Bearer Assignment

Request6. Radio Bearer Setup

6. Radio Bearer SetupC l t

The paging request triggers the Service Request procedure in the MS

7. SGSN-Initiated PDP Context Modification Procedure

8 D li k PDU

6. Radio Access Bearer AssignmentResponse

Complete MS


8. Downlink PDU

NAS Protocol Architecture Supporting PS Mode, MS side Source: 3GPP 24.007, Ch 5

M N SM S-SA P

CM

SM R EG -SA PR A B1-SA P R A Bn-SA P R A B2-SA P M N SM S-SA P

GSM SSESSIONM ANAGEM ENT

CMR A BM SM -SA P RAB M

RABRAB

Control

Suplem en .Services

(SS)

M M sublayer

PM M SM S-SA P G M M SM -SA P

T I G M M R EG-SA PG M M R A BM _SAP

PD P En tity

1 RAB

Entity 2

RAB Entity

n G M M SS-SA P

T I

M M -sublayer

GM M

PD

Access Stratum sublayer

R ABM A S-SAP G M M AS-SA P PD C Pn-SA P PD C P2-SAP PDC P1-SA P


RRC PDCP BM C

o

NAS Protocol Architecture Supporting CS/PS Mode, MS side Source: 3GPP 24.007, Ch 5

MNSMS-SAP MNSS-SAP MNCC-SAP

CM

CC SS GSMS

SMREG-SAP

P

RABM

RAB1-SAP

RAB

RABn-SAP RAB2-SAP

SM

GMMSM-SAP

GMMREG -SAP

MMSMS- MMCC-SAP MMSSSAP

PMMSMS -SAPGMMSMS-

SAP

TI TI PDP TI TI

RA

BM

SM-S

AP

RABEntity

1 RABEntity

2 RAB Entity

n

RABControl

GMMSSSAP

TI

GMMSS2SAP SAP

MM-sublayer

GMM

SAP

MM MM coord

n

GMM coord

PD

coordPD

GM

MR

AB

M-S

AP

Access Stratum sublayer

RABMAS-SAP GMMAS-SAP PDCPn-SAP PDCP2-SAP PDCP1-SAP RR-SAP


RRC PDCP BMC

o

13 umts-cm.ppt [kompatibilitätsmodus] · pdf file• 3g 23.060 gprs, service...

Documents