Top Banner
1 Communicatio n Protocol Engineering Kim, Myung-Jo GSM Network Signaling 2003. 4. 8. Kim Myung Jo ([email protected]) Communication Protocol Engineering Lab.
29
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Chap 10

1CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

GSM Network Signaling

2003. 4. 8.Kim Myung Jo

([email protected])Communication Protocol Engineering Lab.

Page 2: Chap 10

2CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

Contents GSM Protocol Interfaces

GSM MAP protocol Hierarchy

GSM MAP Service Framework

MAP Protocol Machine

MAP Dialogue

MAP Service Primitives

Page 3: Chap 10

3CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

GSM Protocol Interfaces(1/2) Databases

– VLR (visitor location register)– HLR (home location register)– AuC (authentication center)– EIR (equipment identity register)

Used to maintain a list of legitimate, fraudulent, or faulty mobile stations Works with HLR to block calls from illegitimate MS

Switches– MSC (mobile switching center)– GMSC (gateway MSC)– SSP (service switching point)

Radio systems– BSC (base station controller)– BTS (base transceiver station)– MS (mobile station)

Page 4: Chap 10

4CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

GSM Protocol Interfaces(2/2)

BSC

SSP

SSP

GMSC

MSC MSC

HLR EIRVLRVLR

BTS BTS BTS

Databases

Switches

Radio Systems

A-bis

UmMS

A

BC

E

D

F

G

A-bis

SS7/ISUP

SS7/ISUPPSTN

Page 5: Chap 10

5CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

GSM MAP protocol Hierarchy (1/2)

Service User

ServiceProvider

MobileApplicationPart (MAP)

Transaction CapabilitiesApplication Part (TCAP)

Signaling ConnectionControl Part(SCCP)

Message Transfer Part (MTP)

GSM MAPOSI

ApplicationPresentation

SessionTransport

Network

Datalink

Physical

Page 6: Chap 10

6CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

GSM MAP protocol Hierarchy (2/2)

The network entities may consist of several application service elements (ASEs)

The SCCP addresses these ASEs with subsystem numbers (SSNs)

Intra-GSM network message delivery– The destination address of the message may be a simple destination

point code (DPC) that can be used by the MTP for direct routing Inter-GSM network message delivery

– The origination node does not have enough knowledge to identify the actual address of the destination

– In this case, the SCCP translates the actual destination address by GTT(global title translation)

Application service element Subsystem number

HLR

VLR

MSC

00000110

00000111

00001000

Page 7: Chap 10

7CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

GSM MAP Service Framework(1/4)

GSM network entities– communicate with each other through MAP dialogues

by invoking MAP service primitives Service primitive

– Initiated by a MAP service user of a network entity called the dialogue initiator

– Request, Indication, Response, Confirm– Procedure

1. The service request is sent to the MAP service provider of the network entity

2. The service provider delivers the request to the peer network entity

3. the peer network entity invokes the same service primitive with type Indication to inform the destination MAP service user

4. The same service primitive with type Response in invoked by the MAP service user of the dialogue responder

5. After the MAP service provider of the dialogue type Confirm

Page 8: Chap 10

8CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

GSM MAP Service Framework(2/4)

MAP Service User

MAP Service Provider

Dialogue Initiator

MAP Service User

MAP Service Provider

Dialogue Responder

Service (Indication)Service_ack(confirm)

1 234

Service(request) Service_ack(Response)

<GSM MAP service model>

Page 9: Chap 10

9CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

GSM MAP Service Framework(3/4)

The parameters of a service primitive type– M (Mandatory)– O (Service Provider Option)– U (Service User Option)– C (Conditional)

Two type of MAP services– Specific MAP service

Mobility services Operation and maintenance services Call-handling service Supplementary service Short message service management service

Page 10: Chap 10

10CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

GSM MAP Service Framework(4/4)

– Common MAP services MAP-OPEN

– Used to establish a MAP dialog MAP-CLOSE

– Used to clear a MAP dialogue MAP-DELIMITER

– Used to explicitly request the TCAP to transfer the MAP protocol data units

MAP-U-ABORT– Used by the service user to abort a dialogue

MAP-P-ABORT– Used by the service provider to abort a dialogue

MAP-NOTICE– Used by the service provider to inform the service user

of protocol problems such as abnormal event detected by the peer and response rejected by the peer

Page 11: Chap 10

11CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP Protocol Machine(1/2) DSM(dialogue state machine)

– Coordinates the service state machines (SSMs)– For every MAP dialogue, an instance of DSM in created to handle the

dialogue RSM(requesting service state machine)

– Handles a MAP-specific service requested PSM(performing service state machine)

– Handles a MAP service performed Load Control

– Monitors the traffic generated by the service activities– If overload situation in detected, low-priority MAP operations may be i

gnored Handoff, mobility management, short message services, subscriber-contr

olled inputs

Page 12: Chap 10

12CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP Protocol Machine(2/2)

MAP_DSM

PSM

RSM

LOAD_CTRL

MAP_USER

TCAP

MAP_PROVIDER (MAP PM)

Page 13: Chap 10

13CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP DialogueService User Service Provider TCAP Service Provider Service User

(1)MAP_OPEN(req)MAP_Service 1(req)

MAP_DELIMITER(req) (2)TC-BEGIN(req)TC-INVOKE(req)

(3)TC-BEGIN(ind)TC-INVOKE(ind)

(4)MAP_OPEN(ind)MAP_Service 1(ind)

MAP_DELIMITER(ind)

(5)MAP_OPEN(rsp)MAP_Service 1(rsp)

MAP_DELIMITER(req)(6)TC-CONTINUE(req)TC-RESULT-L(req)

(7)TC-CONTINUE(ind)TC-RESULT-L(ind)

(8)MAP_OPEN(cnf)MAP_Service 1(cnf)

MAP_DELIMITER(ind)

(8)MAP_Service2(req)MAP_DELIMITER(req) (9)TC-CONTINUE(req)

TC-INVOKE(req) (10)TC-CONTINUE(ind)TC-INVOKE(ind)

(11)MAP_Service2(ind)MAP_DELIMITER(ind)

(12)MAP_Service2(rsp)MAP_CLOSE(req)(13)TC-END(req)

TC-RESULT-L(req)(14)TC-END(ind)TC-RESULT-L(ind)(15)MAP_Service2(cnf)

MAP_CLOSE(ind)

Page 14: Chap 10

14CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP Dialogue (contd.)

Step 1– A service user initiates a MAP dialogue by invoking the MAP-OPEN

Request servece primitive

Service User Service Provider TCAP Service Provider Service User

(1)MAP_OPEN(req)MAP_Service 1(req)

MAP_DELIMITER(req)

Page 15: Chap 10

15CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP Dialogue (contd.)

Step 2– The MAP PM creates an instance of DSM to handle the MAP-OPEN

Request primitive– For every one of the following user request primitives, an RSM is cre

ated– RSM uses the TC-INVOKE procedure to set the operation code and

TCAP parameters for the service request– The DSM continues to process the user request primitives until the

MAP-DELIMITER Request primitive is encountered– MAP PM enables the TC-BEGIN primitive

Service User Service Provider TCAP Service Provider Service User

(2)TC-BEGIN(req)TC-INVOKE(req)

Page 16: Chap 10

16CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP Dialogue (contd.)

Step 3– The TC-* Request primitives will be delivered by the TCAP and the l

ower-layer protocols of SS7 to the peer MAP PM– The primitives are now of type Indication

Service User Service Provider TCAP Service Provider Service User

(3)TC-BEGIN(ind)TC-INVOKE(ind)

Page 17: Chap 10

17CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP Dialogue (contd.)

Step 4– When the MAP PM of the dialogue responder receives the TC-BEGI

N Indication, a DSM is invoked If the DSM identifies any error from the received TC-BEGIN Indication, a

TC-U-ABORT Request in sent back to the dialogue initiator to terminate the dialogue

The DSM checks if the system is overloaded

– The DSM issues the MAP-OPEN Indication primitive to its MAP service user

– The DSM encounters the TC-INVOKE Indication primitive, it creates a PSM

Service User Service Provider TCAP Service Provider Service User

(4)MAP_OPEN(ind)MAP_Service 1(ind)

MAP_DELIMITER(ind)

Page 18: Chap 10

18CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP Dialogue (contd.)

Step 4 (contd.)– The PSM sends a MAP-NOTICE to its MAP service user– No error occurs, the PSM issues a MAP-Service1 Indication primitive

to be passed to its service user, and the control is passed back to the DSM

– After the DSM has processed all received components, it informs its MAP service user by the MAP-DELIMITER Indication primitive

Service User Service Provider TCAP Service Provider Service User

(4)MAP_OPEN(ind)MAP_Service 1(ind)

MAP_DELIMITER(ind)

Page 19: Chap 10

19CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP Dialogue (contd.)

Step 5– The MAP service user processes the Indication primitives received fr

om the MAP service provider, and returns the results with the MAP-OPEN and the MAP-Service1 Response primitives, followed by the MAP-DELINITER Request primitive

Service User Service Provider TCAP Service Provider Service User

(5)MAP_OPEN(rsp)MAP_Service 1(rsp)

MAP_DELIMITER(req)

Page 20: Chap 10

20CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP Dialogue (contd.)

Step 6– When the MAP service provider receives the MAP-OPEN Response

primitive, the DSM first checks if the response is negative If so, it generates a MAP_Refuse_PDU (Protocol Data Unit) to be deliver

ed by the Indication primitive TC-END

– The response is positive, a MAP_Accept_PDU is generated The DSM proceeds to receive the MAP-Servece1 Response primitive an

d passes the control to the PSM The PSM checks if any user error in present

– PSM issues a TC-RESULT-L Request primitive and passes the control to back to the DSM

Service User Service Provider TCAP Service Provider Service User

(6)TC-CONTINUE(req)TC-RESULT-L(req)

Page 21: Chap 10

21CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP Dialogue (contd.)

Step 6 (contd.)– The DSM continues to process the specific service primitives until th

e MAP-DELIMITER Request primitive is encountered– The DSM issues a TC-CONTINUE Request primitive with the MAP_

Accept_PDU

Service User Service Provider TCAP Service Provider Service User

(6)TC-CONTINUE(req)TC-RESULT-L(req)

Page 22: Chap 10

22CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP Dialogue (contd.)

Step 7– The TC-CONTINUE/ TC-RESULT-L Indication primitives are receive

d by the MAP service provider of the dialogue initiator– When the DSM receives the TC-CONTINUE, it performs tests, as de

scribed in step 4– It accepts the the dialogue and passes the control to the RSM to han

dle the specific service primitives– The RSM maps the TC-RESULT-L parameters to the MAP-Service1

Confirm primitive and passes the control back to the DSM– After all components have been processed, the DSM informs the MA

P service user

Service User Service Provider TCAP Service Provider Service User

(7)TC-CONTINUE(ind)TC-RESULT-L(ind)

Page 23: Chap 10

23CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP Dialogue (contd.)

Step 8– The MAP service user of the dialogue initiator handles the Confirm p

rimitives and, possibly, makes new requests

Service User Service Provider TCAP Service Provider Service User

(8)MAP_OPEN(cnf)MAP_Service 1(cnf)

MAP_DELIMITER(ind)

Page 24: Chap 10

24CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP Service Primitives(1/3)

PSTN GMSC

MSC

HLR VLR

MAP_SEND-ROUTING-INFORMATION

MAP_PORVIDE_ROAMING_NUMBER

IAM

MAP_PORVIDE_ROAMING_NUMBER_ack

MAP_SEND-ROUTING-INFORMATION_ack

IAM

D interfaceC interface

SS7 ISUP

SS7 ISUP

<Retrieval of routing information>

Page 25: Chap 10

25CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP_SEND_ROUTING_INFORMATION Parameters (1/3)

PARAMETER NAME REQUEST INDICATION RESPONSE CONFIRM

Invoke ID M M(=) M(=) M(=)

MSISDN M M(=)

CUG Interlock C C(=) C C(=)

CUG Outgoing Access C C(=) C C(=)

Number of Forwarding C C(=)

Network Signal Info C C(=)

IMSI C C(=)

MSRN C C(=)

Forwarding Data C C(=)

User Error C C(=)

Provider Error O

Page 26: Chap 10

26CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP_SEND_ROUTING_INFORMATION Parameters (2/3)

Invoke ID– A unique number generated by the MAP service user to

identify the corresponding service primitives in the MAP service user-provider interface

MSISDN– The mobile station ISDN number

CUG(closed user group) Interlock– A group of users (e.g company) with specific network

services– possible to limit the incoming/outgoing calls inside the

group

CUG Outgoing Access– Represents the outgoing access of a closed user group

Number of Forwarding– Counts the number of times the call has been forwarded

Page 27: Chap 10

27CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP_SEND_ROUTING_INFORMATION Parameters (3/3)

Network Signal Info– Provides external signal information

Signaling protocol between the GSM network and the PSTN

IMSI (International Mobile Subscriber Identity)– Used to identify the called MS

MSRN (Mobile Subscriber Roaming Number)– The routing number that identifies the current

location of the called MS

Forwarding Data– Used to invoke the call-forwarding service

User Error– Send by the responder when an error is detected

Page 28: Chap 10

28CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP_PROVIDE_ROAMING_NUMBER Parameters (1/2)

PARAMETER NAME REQUEST INDICATION RESPONSE CONFIRM

Invoke ID M M(=) M(=) M(=)

IMSI M M(=)

MSC Number M M(=)

MSISDN C C(=)

LMSI C C(=)

GSM Bearer Capability C C(=)

Network Signal Info C C(=)

MSRN C C(=)

User Error C C(=)

Provider Error O

Page 29: Chap 10

29CommunicationProtocolEngineering Lab.

Kim, Myung-Jo

MAP_PROVIDE_ROAMING_NUMBER Parameters (2/2)

MSC Number– The ISDN number of the MSC where the called MS resides

LMSI(Local Mobile Station Identity)– Used by the VLR for internal data management of the called MS

GSM Bearer Capability– Included if the connection is for nonspeech services such as short m

essage services User Error

– Sent when an error is detected