04b Gr Interface

CN3203EN01GLN02 © Nokia Siemens Networks

1 (27)

PCNSIG

Gr Interface

Training Document

Gr Interface

2 (27) © Nokia Siemens Networks

CN3203EN01GLN02

Legal notice

Intellectual Property Rights

All copyrights and intellectual property rights for Nokia Siemens Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Siemens Networks training material, are the exclusive property of Nokia Siemens Networks. Nokia Siemens Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Siemens Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individuals can use the Nokia Siemens Networks training material for their own personal self-development only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia Siemens Networks. The Nokia Siemens Networks training material cannot be used outside of an agreed Nokia Siemens Networks training session for development of groups without the prior written agreement of Nokia Siemens Networks.

Indemnity

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products are given “as is” and all liability arising in connection with such hardware or software products shall be defined conclusively in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in the document as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY MONETARY LOSSES,SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT

This document and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

Wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2012. All rights reserved.

Contents


3 (27)

Contents

2 Objectives ................................................................................. 4

3 SGSN and HLR interaction ....................................................... 5 3.1 Gr interface in Nokia SGSN ........................................................ 6 3.1.1 Standard SS7 ............................................................................. 7 3.1.2 SS7 over IP ................................................................................ 7

4 Messages .................................................................................. 9 4.1 Update GPRS Location Procedure ............................................. 9 4.1.1 Example trace of the message ................................................. 10 4.1.2 Content of the message ............................................................ 12 4.2 Insert Subscriber Data .............................................................. 12 4.2.1 Example trace of Insert Subscriber Data ................................... 13 4.2.2 Content of the message ............................................................ 16 4.3 Purge Mobile Station ................................................................ 18 4.3.1 Example trace of Purge MS and Purge MS Ack

messages ................................................................................. 19 4.3.2 Content of the message ............................................................ 22 4.4 Cancel Location ........................................................................ 23 4.4.1 Example trace of Cancel Location message ............................. 23 4.4.2 Content of the message ............................................................ 25

5 Summary Q&A ........................................................................ 26

Glossary 27

Gr Interface


CN3203EN01GLN02

2 Objectives

By the end of this module the trainees should be able to:

Explain how the interaction between SGSN and HLR works

List the procedures supported by SGSN - HLR interaction

Describe procedures, their messages and information elements

SGSN and HLR interaction


5 (27)

3 SGSN and HLR interaction

The Gr interface is a standard SS7 MAP interface and connects the SGSN to the

HLR. The main purpose of the Gr interface is to provide the SGSN with an

access to the subscription information in the HLR. Also, Gr supports mobility

management; that is, the new SGSN is indicated to the HLR during inter-SGSN

routing area update. The interface is used for signalling purposes only.

In the GSM and 3G systems the HLR is used to store the subscriber data profile

while the Authentication Centre (AuC) contains authentication data of

subscribers and generates the authentication quintuplets. Both registers are

accessed by using standard Mobile Application Part (MAP) interface

[3GPP TS 29.002].

The Gr interface requires the MAP version 3, that is, the MAP protocol with

GPRS/UMTS additions. The operations supported between SGSN and HLR are

listed in Table 1.

Figure 1 standard SS7 Gr Interface

Gr Interface


CN3203EN01GLN02

The HLR will initiate dialogues towards the SGSN if it is aware that one of its

subscribers is in the SGSN serving area. This means that a GPRS location

updating has been successfully completed, i.e., the HLR has indicated

successful completion of the GPRS location update to the SGSN.

Message Type Message Name Responder Initiating Entity

Mobility Management

gprsLocationUpdate

(updateGPRSLocation/v3)

HLR SGSN

msPurging

(purgeMS/v3) HLR SGSN

locationCancel (cancelLocation v3)

SGSN HLR

reset (reset)

SGSN HLR

subscriberDataMngt (insertSubscriberData v3)

(deleteSubscriberData v3)

SGSN HLR

tracing (activateTraceMode)

(deactivateTraceMode)

SGSN HLR

Subscriber Controlled Inputs (Supplementary Services)

gprsLocationInfoRetrieval (sendRoutingInfoForGprs/v3)

HLR SGSN/ GGSN

failureReport (failureReport/v3)

HLR SGSN/ GGSN

authenticationFailureReport (authenticationFailureReport/v3)

HLR VLR/ SGSN

Table 1 MAP Messages on Gr interface

3.1 Gr interface in Nokia SGSN

The signalling interfaces on the SGSN are based on Signaling System No.7. In

the Nokia SGSN, it is possible to have a mixture of both types of interfaces to

enable a smooth transition from PCM based to IP based transport. Also, it may

SGSN and HLR interaction


7 (27)

be possible that not all the other network elements in the network support SS7

over IP, and thus this feature enables the SGSN to communicate with new and

legacy SS7 network elements. The only restriction is that the IP and PCM

transport layers cannot be used in the same link set but it is possible to use them

in the same route set.

In the SGSN, the SS7 protocol stacks are implemented on the SS7 Units, with

the exception of the MAP and CAP protocols, which are maintained on the

SMM Units. The SS7 Units also contain the physical connections to the external

SS7 network (E1,T1,JT1/IP ‘Ethernet’).

3.1.1 Standard SS7

The SS7 is a world-wide signaling standard which uses 64 kbit/s links over 2

Mbps PCM interfaces. The SS7 protocol stack for Narrowband SS7 is shown in

Figure 2.

Figure 2. Narrowband SS7 Protocol Stack

3.1.2 SS7 over IP

M3UA (SS7 MTP-3 User Adaption Layer) and SCTP (Stream Control

Transport Protocol) adapt the SS7 protocols to IP. SCTP refers to the Stream

Control Transmission Protocol developed by the SIGTRAN working group of

the IETF for the purpose of transporting various signaling protocols over IP

networks. M3UA refers to the SCCP adaptation layer "SS7 MTP3 – User

Adaptation Layer " also developed by the SIGTRAN working group of the

IETF. Nokia SGSN M3UA implementation is based on the SIGTRAN Internet

draft version 7.

Gr Interface


CN3203EN01GLN02

Note

Use of M3UA protocol is according to 3GPP specifications. However, M3UA

has not yet gained RFC status in IETF thus different versions of the draft may

not be compliant with each other.

Figure 3 Narrowband SS7 over IP Protocol Stack

Messages


9 (27)

4 Messages

4.1 Update GPRS Location Procedure

The Update GPRS Location Procedure to HLR is performed during Attach

procedure or Routing Area Update procedure if the current SGSN serving the

MS is changed. The Update Location Procedure is performed also when the MS

is performing its first Attach to the network.

The Update GPRS Location procedure is described in Figure 1-2.

HLRnew SGSN old SGSN

2. MAP. Cancel Location

2. MAP. Cancel Location Ack

1. MAP. Update Location

3. MAP. Insert subscriber Data

3. MAP. Insert subscriber Data Ack

4. MAP. Update Location Ack

HLRnew SGSN old SGSN

2. MAP. Cancel Location

2. MAP. Cancel Location Ack

1. MAP. Update Location

3. MAP. Insert subscriber Data

3. MAP. Insert subscriber Data Ack

4. MAP. Update Location Ack

Figure 1-2. Update location procedure to HLR

1. The SGSN sends a MAP.Update GPRS Location (IMSI, SGSN Number,

SGSN Address) to the HLR. SGSN Address is the IP address of SGSN

(In SGSN DX200 platform it represents the IP address of PAPU).

2. If the mobile was previously registered in another SGSN the HLR sends

MAP.Cancel Location (IMSI, Cancellation Type) to the old SGSN with

Cancellation Type set to Update Procedure. The old SGSN acknowledges

with MAP.Cancel Location Ack (IMSI). If there are any ongoing

Gr Interface


CN3203EN01GLN02

procedures for that MS, the old SGSN shall wait until these procedures

are finished before removing the MM and PDP contexts.

3. HLR sends MAP.Insert Subscriber Data (IMSI, GPRS subscription data)

to the new SGSN that shall return a MAP.Insert Subscriber Data Ack

(IMSI) message to the HLR. If subscription checking fails, the SGSN

rejects the Attach Request/ Routing Area update request with an

appropriate cause and SGSN returns a MAP.Insert Subscriber Data Ack

(IMSI, Cause) message to the HLR with appropriate error cause.

4. The HLR acknowledges the Update Location message by sending a

MAP.Update GPRS Location Ack to the SGSN. If the Update Location is

rejected by the HLR, the SGSN rejects the Attach Request/ Routing Area

update request from the MS with an appropriate cause

4.1.1 Example trace of the message

MSU

- BSN: 56 (38h) BIB: 1 FSN: 57 (39h) FIB: 1

- SCCP

- network indicator : reserved national

- data, length : 62, (3Eh)

UDT - UNIT DATA

SCCP DPC: 2400 (0960h)

SCCP OPC: 1856 (0740h)

SCCP SLS: 13 (0Dh)

Protocol Class

- protocol class : 80h, conn.less, return msg

Called Party Address

- length 13 (0Dh)

- full GT configuration

- routing based on global title

- subsystem is HLR

- translation type : 0 (00h)

- encoding : BCD, odd number of digits

- numbering plan : ISDN/mobile (E.214)

- nature of address : international number

- address signals : 392699900000012

Calling Party Address

- length 12 (0Ch)


Messages


11 (27)


- Subsystem nr: 149 (95h)



- numbering plan : ISDN/telephony (E.163, 164)



SCCP User Data

- length 83 (53h)

SUBSYSTEM 6 : HLR

BEGIN

OrigTransactionID: 87 C0 B3 00

DialoguePortion

External

ObjectIdentifier: 0-0-17-773-1-1-1

Single-ASN.1-type

DialogueRequest

Protocol-Version: 00000111 10000000

Application-Context-Name

ObjectIdentifier: 0-4-0-0-1-0-32-3

ComponentPortion

Invoke

InvokedID: 00

LocalOperationCode: 17

Parameter: 48 (30h) Length: 31 (1Fh)

Tag: Universal, Constructed, value: 10h

- length: 31 (1Fh)

Tag: Universal, Primitive, value: 04h

- length: 8 (08h)

- data: 22 02 93 09 00 00 10 F2


- length: 8 (08h)

- data: 91 93 62 99 00 00 01 F0


- length: 5 (05h)

- data: 04 AC 1F 2C 22

Tag: Context, Constructed, value: 00h

- length: 2 (02h)

Gr Interface


CN3203EN01GLN02

Tag: Context, Primitive, value: 03h

- length: 0 (00h)

UPDATE GPRS LOCATION ARG : 23 (17h)

UpdateGPRSLocationArg

IMSI

- TBCD String : 222039900000012

SGSN-Number

- nature of address ind. : international

- numbering plan ind. : ISDN/Telephony (E.164)

- TBCD String : 3926990000100

SGSN-Address

- IPv4 address : 172.31.44.34

sgsn-Capability

gprsEnhancementsSupportIndicator

Trace 1 MAP Message UpdateGPRSLocationArg

4.1.2 Content of the message

IMSI

This parameter is the International Mobile Subscriber Identity defined in 3GPP,

Rel.´99 023.003.

SGSN number

This parameter refers to the ISDN number of a SGSN.

SGSN address

This parameter refers to IP address of SGSN. For DX200 platform SGSN, this

SGSN address refers to IP address of PAPU.

4.2 Insert Subscriber Data

This service is used by an HLR to update an SGSN with certain subscriber data

in the following occasions:

Messages


13 (27)

- if the GPRS subscription has changed;

- if the network access mode is changed;

- the operator has applied, changed or removed Operator Determined Barring;

- the HLR provides the SGSN with subscriber parameters at GPRS location

updating of a subscriber.

4.2.1 Example trace of Insert Subscriber Data

MSU

- BSN: 57 (39h) BIB: 1 FSN: 57 (39h) FIB: 1

- SCCP



UDT - UNIT DATA

SCCP DPC: 1856 (0740h)

SCCP OPC: 2400 (0960h)

SCCP SLS: 1 (01h)

Protocol Class



- length 12 (0Ch)










- length 11 (0Bh)



- subsystem is HLR


- encoding : BCD, even number of digits


Gr Interface


CN3203EN01GLN02



SCCP User Data

- length 120 (78h)

SUBSYSTEM 6 : HLR

CONTINUE

OrigTransactionID: H...

DestTransactionID: ....

DialoguePortion

External


Single-ASN.1-type

DialogueResponse




Result

- Accepted (0)

Result-Source-Diagnostic

Dialogue-Service-User

- Null (0)

ComponentPortion

Invoke

InvokedID: .

LocalOperationCode: .

Parameter: 48 (30h) Length: 50 (32h)


- length: 50 (32h)


- length: 7 (07h)

- data: ..bYU.!


- length: 1 (01h)

- data: .


- length: 33 (21h)


- length: 0 (00h)

Messages


15 (27)


- length: 29 (1Dh)


- length: 27 (1Bh)


- length: 1 (01h)

- data: .


- length: 2 (02h)

- data: .!


- length: 3 (03h)

- data: #B.


- length: 2 (02h)

- data: .*


- length: 9 (09h)

- data: ...@@.A@@


- length: 1 (01h)

- data: .

INSERT SUBSCRIBER DATA ARG : 7 (07h)

InsertSubscriberDataArg

MS-ISDN



- TBCD String : 392695550012

SubscriberStatus

- ServiceGranted (00h)

GPRSSubscriptionData

completeDataListIncluded

GPRSDataList

PDP-Context

PDP-ContextId: 1

PDP-Type

- PDP type organization : IETF

- PDP type number : PPP

Gr Interface


CN3203EN01GLN02

QoS-Subscribed

- Reliability class : Unacknowledged GTP & LLC, ack. RLC

- Delay class : Delay class 4 (best effort)

- Subscribed precedence : Normal priority

- Peak throughput : Up to 8 000 octet/s

- Mean throughput : Unavailable

APN: .*

ext-QoS-Subscribed: ...@@.A@@

networkAccessMode

- bothMSCAndSGSN (00h)

Trace 2 MAP Message INSERT SUBSCRIBER DATA ARG


IMSI

It is only included if the service is not used in an ongoing transaction (e.g.

location updating). This parameter is used by the VLR and the SGSN.

MSISDN

It is included either at location updating or when it is changed. The MSISDN

sent shall be the basic MSISDN. This parameter is used by the VLR and the

SGSN.

Subscriber Status

It is included either at location updating or when it is changed. To apply,

remove or update Operator Determined Barring Categories the Subscriber

Status is set to Operator Determined Barring. In this case ODB General Data

shall also be present. If the Operator Determined Barring applies and the

subscriber is registered in the HPLMN and HPLMN specific Operator

Determined Barring applies then ODB HPLMN Specific Data shall also be

present. To remove all Operator Determined Barring Categories the Subscriber

Status shall be set to "Service Granted". This parameter is used by the VLR and

the SGSN.

Bearer service List

This parameter is used only by the VLR and if the SGSN receives this

parameter it shall ignore it.

Teleservice List

If it is included in the Request/Indication, it contains either all Extensible

Teleservices subscribed (at location updating or at restoration) or the ones

added (at subscriber data modification). Only the Extensible Teleservices that

Messages


17 (27)

are relevant to the node at which the message is received should be included in

the Teleservice List.

If the VLR or the SGSN receives an Indication containing any Extensible

Teleservice parameters which it does not support/allocate it returns them in the

response to the HLR and discards the unsupported Extensible Teleservices (no

error is sent back). This parameter is used by the VLR and the SGSN.

GPRS Subscription Data

This parameter contains a list of PDP-contexts a user has subscribed to. At

GPRS location updating the HLR shall include the complete GPRS

Subscription Data.

PDP-ContextId

Index of PDP Context subscribed in HLR for a specific user. In

NOKIA HLR M13, the max number of PDP ID is 50.

PDP-Type

Type of PDP Context, e.g. PPP or IP.

QoS-Subscribed

The quality of service profile subscribed. QoS Profile Subscribed is

the default level if a particular QoS profile is not requested. . QoS

Profile Subscribed is also the maximum QoS per PDP context to the

associated APN. This QoS is based on Release 97. Refer to Error!

Reference source not found. for details.

APN

A label according to DNS naming conventions describing the access

point to the external packet data network..

Ext-QoS-Subscribed

The quality of service profile subscribed. QoS Profile Subscribed is

the default level if a particular QoS profile is not requested. . QoS

Profile Subscribed is also the maximum QoS per PDP context to the

associated APN. This QoS is based on Release 99. Refer to Error!

Reference source not found. for details.

PDPChargingCharacteristic

The charging characteristics of this PDP context, e.g. normal, prepaid,

flat-rate, and/or hot billing..

When there is a change in GPRS subscriber data the HLR shall include only the

new and/or modified PDP contexts.

When the SGSN receives GPRS Subscription Data within a dialogue it shall

check if the received data has to be considered as the entire GPRS subscription

data. If so, it shall replace the stored GPRS Subscription Data with the received

data set, otherwise it shall replace the data only for the modified PDP contexts

(if any) and add the new PDP contexts (if any) to the stored GPRS Subscription

Data.

Gr Interface


CN3203EN01GLN02

If GPRS Subscription Data is omitted in the Insert Subscriber Data operation

the SGSN shall keep the previously stored GPRS Subscription Data.

If the SGSN detects that there is overlapping in the information received within

a dialogue, it shall send the error Unexpected Data Value. This parameter is

used only by the SGSN and if the VLR receives this parameter it shall ignore it.

Network access mode

This parameter defines if the subscriber has access to MSC/VLR and/or to

SGSN. This parameter is used by SGSN and MSC/VLR. In VLR, the parameter

is used only as part of Restore Data Procedure and the parameter is not stored in

the VLR. This parameter shall always be sent to the SGSN as part of the

subscriber data at GPRS location updating. It shall be sent to the SGSN or VLR

as appropriate if it is to be changed as a result of administrative action.

4.3 Purge Mobile Station

The Purge function allows an SGSN to inform the HLR that it has deleted the

MM and PDP contexts of a detached MS. It is invoked when the subscriber

record for the MS is to be deleted in the SGSN. You will find the related Purge

Timer in the SGSN Mobility Management Configuration.

When the MS detaches, SGSN keeps mobility management context and pdp

context information in the memory and starts the purge timer. The information

can be re-used in subsequent attaches without accessing HLR. When purge

timer expires, SGSN executes purge procedure and deletes information about

the MS from the memory of the SGSN.

Figure 4 Purge Message Flow

Each step is explained in the following list:

1) After deleting the MM and PDP contexts of a detached MS, the SGSN sends

a Purge MS (IMSI) message to the HLR.

2) The HLR sets the MS Purged for GPRS flag and acknowledges with a Purge

MS Ack message.

Messages


19 (27)

4.3.1 Example trace of Purge MS and Purge MS Ack messages

MSU

- BSN: 57 (39h) BIB: 1 FSN: 58 (3Ah) FIB: 1

- SCCP



UDT - UNIT DATA

SCCP DPC: 2400 (0960h)

SCCP OPC: 1856 (0740h)

SCCP SLS: 13 (0Dh)

Protocol Class



- length 11 (0Bh)



- subsystem is HLR







- length 12 (0Ch)









SCCP User Data

- length 72 (48h)

SUBSYSTEM 6 : HLR

BEGIN

Gr Interface


CN3203EN01GLN02

OrigTransactionID: ....

DialoguePortion

External


Single-ASN.1-type

DialogueRequest




ComponentPortion

Invoke

InvokedID: .

LocalOperationCode: C

Parameter: 163 (A3h) Length: 20 (14h)


- length: 20 (14h)


- length: 8 (08h)

- data: ".......


- length: 8 (08h)

- data: ..b.....

PURGE MS ARG : 67 (43h)

PurgeMS-Arg

IMSI

- TBCD String : 222039900000012

SGSN-Number



- TBCD String : 3926990000100

Messages


21 (27)

MSU

- BSN: 58 (3Ah) BIB: 1 FSN: 58 (3Ah)

FIB: 1

- SCCP



UDT - UNIT DATA

SCCP DPC: 1856 (0740h)

SCCP OPC: 2400 (0960h)

SCCP SLS: 13 (0Dh)

Protocol Class

- protocol class : 80h, conn.less, return

msg


- length 12 (0Ch)






- numbering plan : ISDN/telephony (E.163,

164)




- length 11 (0Bh)



- subsystem is HLR



- numbering plan : ISDN/telephony (E.163,

164)



SCCP User Data

- length 68 (44h)

SUBSYSTEM 6 : HLR

END

Gr Interface


CN3203EN01GLN02

DestTransactionID: ....

DialoguePortion

External


Single-ASN.1-type

DialogueResponse




Result

- Accepted (0)

Result-Source-Diagnostic

Dialogue-Service-User

- Null (0)

ComponentPortion

ReturnResultLast

InvokedID: .

Sequence

LocalOperationCode: C

Parameter: 48 (30h) Length: 2 (02h)

Tag: Universal, Constructed, value:

10h

- length: 2 (02h)


- length: 0 (00h)

PURGE MS RES : 67 (43h)

PurgeMS-Res

freezeP-TMSI

Trace 3 MAP Message PURGE MS ARG and PURGE MS RES


Freeze P-TMSI

This parameter is sent to the SGSN to indicate that the P-TMSI has to be frozen.

It shall be present if the received SGSN number matches the stored SGSN

number.

SGSN number

Messages


23 (27)

Shall be present if the sender is SGSN

4.4 Cancel Location

This service is used between HLR and SGSN to delete a subscriber record from

the SGSN. It may be invoked automatically when an MS moves from one

SGSN area to another, to remove the subscriber record from the old SGSN, or

by the HLR operator to enforce a location updating from the SGSN to the HLR.

This message can be provoked by typing the following MML command in the

Nokia HLR:

ZMNM:IMSI=262099300000036:SGSN=N;

ZMND:IMSI=262099300000036;

4.4.1 Example trace of Cancel Location message

MSU

- BSN: 58 (3Ah) BIB: 1 FSN: 59 (3Bh) FIB: 1

- SCCP



UDT - UNIT DATA

SCCP DPC: 1856 (0740h)

SCCP OPC: 2400 (0960h)

SCCP SLS: 14 (0Eh)

Protocol Class



- length 12 (0Ch)








Gr Interface


CN3203EN01GLN02



- length 11 (0Bh)



- subsystem is HLR






SCCP User Data

- length 65 (41h)

SUBSYSTEM 6 : HLR

BEGIN

OrigTransactionID: 1F 40 10 00

DialoguePortion

External


Single-ASN.1-type

DialogueRequest




ComponentPortion

Invoke

InvokedID: 00

LocalOperationCode: 03

Parameter: 163 (A3h) Length: 13 (0Dh)


- length: 13 (0Dh)


- length: 8 (08h)

- data: 22 02 93 09 00 00 10 F2

Tag: Universal, Primitive, value: 0Ah

- length: 1 (01h)

- data: 01

CANCEL LOCATION ARG : 3 (03h)

Messages


25 (27)

CancelLocationArg

IMSI

- TBCD String : 262099300000036

cancellationType

- subscriptionWithdraw (01h)

Trace 4 MAP Message CANCEL LOCATION ARG


Cancellation Type

The presence of this parameter is mandatory when the Cancel Location is sent

to the SGSN. If the VLR receives this parameter and do not understand it the

VLR shall ignore it.

Gr Interface


CN3203EN01GLN02

5 Summary Q&A

1. Draw the signalling flow for the Update GPRS location procedure

HLR new SGSN old SGSN

2. Describe the difference between the Purge Mobile Station and Cancel

Location Procedure. Why do we need them?

Glossary


27 (27)

Glossary

APN Access Point Name

CDR Charging Data Record

CG Charging Gateway

CN Core Networks

CRP Central Routing Processor

DNS Domain Name Server

EIR Equipment Identity Register

FTP File Transfer Protocol

GGSN Gateway GPRS Support Node

GPLC General Purpose Line Card

GTP GPRS Tunnelling Protocol

HLR Home Location Register

IP Internet Protocol

LIS Logical IP subnetwork

MAP Mobile Application Protocol

MM Mobility Management

NTP Network Time Protocol

PDP Packet Datagram Protocol

PVC Permanent Virtual Channel

QoS Quality of Service

RNC Radio Network Controller

RRC Radio Relay Control

SDH Synchronous Digital Hierarchy

SGSN Serving GPRS Support Node

SM Session Management

SMSC Short Message Services Centre

SNMP Simple Network Management Protocol

TID Tunneling Identifier

WSLC Wirespeed Line Card

04b Gr Interface

Documents

Transcript of 04b Gr Interface