MAP Protocol.pdf

8/14/2019 MAP Protocol.pdf

http://slidepdf.com/reader/full/map-protocolpdf 1/75

K1205 MAP

Tektronix8-1

8 Mobile Application Part (MAP)

8.1 GOAL...............................................................................................................................8-3

8.2 GENERAL.......................................................................................................................8-3

8.3 FUNCTIONS PROVIDED BY MAP ............................................................................8-4

8.4 LOCAL OPERATIONS AND ARGUMENTS ............................................................8-5

8.5 USE OF SCCP...............................................................................................................8-6

8.5.1 SUBSYSTEM NUMBERS .............................................................................................8-6

8.5.2 SCCP ADDRESSING .................................................................................................8-6

8.6 USE OF TCAP ...............................................................................................................8-8

8.7 NUMBERING AND IDENTIFICATION PARAMETER ............................................8-9

8.7.1 MSISDN....................................................................................................................8-9

8.7.2 MSRN........................................................................................................................8-9

8.7.3 IMSI..........................................................................................................................8-11

8.7.4 TMSI........................................................................................................................8-128.7.5 LMSI........................................................................................................................8-12

8.8 MAP MESSAGE ...........................................................................................................8-13

8.8.1 EXAMPLES OF MAP OPERATIONS ..........................................................................8-15

8.8.1.1 Update location...............................................................................................8-15

8.8.1.2 Forward SM ....................................................................................................8-17

8.8.2 EXAMPLE OF MAP DATA TYPES.............................................................................8-188.8.3 EXAMPLE OF MAP ERRORS AND ERROR CODES...................................................8-23

8.9 MAP SERVICES ..........................................................................................................8-25

8.9.1 MOBILITY SERVICES ................................................................................................8-25

8.9.2 OPERATION AND MAINTENANCE SERVICES ............................................................8-288.9.3 C ALL HANDLING SERVICES......................................................................................8-28

8.9.4 SUPPLEMENTARY SERVICE RELATED SERVICES ...................................................8-29

8.9.5 SHORT MESSAGE SERVICE MANAGEMENT SERVICES ...........................................8-30

8.10 EXAMPLE PROCEDURES OF MAP ....................................................................8-31

8.10.1 DETACH IMSI / PURGE MS...................................................................................8-318.10.2 LOCATION UPDATE................................................................................................8-32

8.10.3 RETRIEVAL OF ROUTING INFORMATION.................................................................8-35

8.10.4 MOBILE TERMINATING CALL...................................................................................8-37

8.10.5 MOBILE ORIGINATING CALL....................................................................................8-39

8.10.6 H ANDOVER............................................................................................................8-40



MAP K1205

Tektronix8-2

8.10.7 S UPPLEMENTARY SERVICE ................................................................................. 8-41

8.10.7.1 Registration procedure ............................................................................... 8-41

8.10.7.2 Erasure procedure ...................................................................................... 8-42

8.10.7.3 Activation procedure ................................................................................... 8-438.10.7.4 Deactivation procedure .............................................................................. 8-44

8.10.7.5 Interrogation procedure...............................................................................8-45

8.10.7.6 Invocation procedure ................................................................................... 8-46

8.10.7.7 Password registration procedure ..............................................................8-47

8.10.8 S HORT MESSAGE SERVICE.................................................................................. 8-48

8.10.8.1 Mobile originated short message transfer................................................8-488.10.8.2 Mobile terminated short message transfer............................................... 8-49

8.10.8.3 Short message alert....................................................................................8-51

8.10.8.4 Short message delivery status report........................................................8-53

8.11 GENERAL FUNCTIONS OF SHORT MESSAGE SERVICES ........................8-54

8.11.1 SMS CONTROL PROTOCOL USER P ART............................................................. 8-588.11.1.1 SMS CP messages ....................................................................................8-58

8.11.1.2 SMS-CP parameters.................................................................................. 8-608.11.2 SMS RELAY PROTOCOL USER P ART ................................................................. 8-63

8.11.2.1 SMS RP messages ....................................................................................8-63

8.11.2.2 SMS-RP parameters .................................................................................. 8-65

8.12 EXERCISE................................................................................................................. 8-70

8.12.1 S OLUTION.............................................................................................................. 8-71



K1205 MAP

Tektronix8-3

8.1 Goal

In this section the course participants shall learn about:

?? the structure of MAP

?? functions provided by MAP

?? the structure of messages

?? procedures of MAP

8.2 General

It will be necessary to transfer between entities of a Public Land Mobile Network

(PLMN) information specific to the PLMN in order to deal with the specific

behaviour of roaming mobile stations. The Signalling System No. 7 is used totransfer this information.

MAP Slide 1 Tektronix

Structure of SS#7

MTP

SCCP

ISUP

Other

User

Par ts

...

TCAP

BSSAP TUP

MAP OMAP INAP



MAP K1205

Tektronix8-4

8.3 Functions provided by MAP

The Mobile Application Part (MAP) defines the signalling functions which are

concerned with information exchange related to the possibility for a mobile

station to roam.

?? provides transaction capability (TC) functions in a set of common procedures

which support the non-circuit related information transfer between two or more

signalling nodes.

?? defines the signalling functions which support, nationally and internationally, the

mobile functions for voice and non-voice applications.


MAP as TCAP user

Transaction Capability Application Part (TCAP)

M o b i l e A p p l i c a t i o n

P a

r t ( T C A P - U s e r )

MAP Application Entity (AE)

MAP Application Service

Element (ASE)

MAP Application Service

Element (ASE)



K1205 MAP

Tektronix8-5

8.4 Local Operations and Arguments

Use of MAP for:

?? Call Set-up (MOC and MTC)

?? Location update and cancellation

?? IMSI Detach/Attach

?? Retrieval of mobile subscriber parameters in a call set-up

?? Update of HLR and VLR mobile subscriber information with regard of changes

in subscriber parameters

?? Authentication and encryption

?? Handover

?? Information security

?? Mobile station security checking IMEI and allocating TMSI

?? Handling of supplementary services (procedures and state)

?? Charging (e.g. between MSC and HLR)

?? Fault recovery in case restart with automatic reload in any node

?? Support of O&M procedures

?? Short Message transfer

Use of the SCCP

The MAP makes use of services offered by the SCCP, only the protocol classes

0 and 1 (connectionless classes) are used.



MAP K1205

Tektronix8-6

8.5 Use of SCCP

8.5.1 Subsystem numbers

The Application Entities (AEs) defined for MAP consist of several Application

Service Elements (ASEs) and are addressed by sub -system numbers (SSNs).

The SSN for MAP are:

00000101 for the whole MAP (reserved for possible future use);00000110 HLR;

00000111 VLR;

00001000 MSC;

00001001 EIR;

00001010 is allocated for evolution (possible Authentication centre).00001100 SMSC

8.5.2 SCCP addressing

1) Intra-PLMN addressing

a) Called Party Address

?? SSN indicator = 1 (MAP SSNs always included);

?? a Global title or a point code may also be included;

b) Calling Party Address


?? a Global title or a point code may also be included; If none of

these parameters is present the MTP address (i.e. OPC) is

used;



K1205 MAP

Tektronix8-7

2) Inter-PLMN addressing

a) Called Party Address

?? SSN indicator = 1 (MAP SSN always included);

?? Global title indicator = 0100 (Global title includes translation

type, numbering plan, encoding scheme and nature of address

indicator);

?? the translation type field will be coded "00000000" (Not used);

?? Routing indicator = 0 (Routing on global title);

b) Calling Party Address


?? Point code indicator = 0;

?? Global title indicator = 0100 (Global title includes translationtype, numbering plan, encoding scheme and nature of address

indicator);

?? the translation type field will be coded "00000000" (Not used);

?? Routing indicator = 0 (Routing on Global Title).


I: SPC/GTE: GTT: VLR number

E: GTT: MSISDN

I: SPC/GTE: GTT: VLR number

SCCP addressing

To

Fixed Network

HLR

VLR

Fixed HLR

MSC

VLR MSC

From

EIR

Network

I: SPC/GTE: GTT: MGT/MSISDN/ HLR number I: SPC/GT

E: GTT: MSISDN

I: SPC/GT

E: GTT: VLR number

I: SPC/GT

E: GTT: MSC number

I: SPC/GT

E: GTT: EIR number

I: Intra-PLMN E: Extra(Inter)-PLMN T: Address TypeGT: Global Title MGT: Mobile Global Title SPC: Signalling Point Code



MAP K1205

Tektronix8-8

8.6 Use of TCAP

The MAP uses all the services provided by TC except the ones related to the

unstructured dialogue facility.

From a modelling perspective, the MAP is viewed as a single Application

Service Element.

TC is structured as a Component sub-layer above a Transaction sub-layer.

The Component sub-layer provides two types of application services: services for

the control of end-to-end dialogues and services for Remote Operation handling.

These services are accessed using the TC-Dialogue handling primitives and TC-Component handling primitives respectively.

Services for dialogue control include the ability to exchange information related to

application-context negotiation as well as initialisation data.

Services for Remote Operation handling provide for the exchange of protocoldata units invoking tasks (operations), and reporting their outcomes (results or

errors) plus any non-application-specific protocol errors detected by the

component sub-layer. The reporting of application-specific protocol errors by the

TC user, as distinct from application process errors, is also provided. The

Transaction sub-layer provides a simple end -to-end connection associationservice over which several related protocol data units (i.e. built by the Component

Sub-Layer) can be exchanged. A Transaction termination can be prearranged

(no indication provided to the TC user) or basic (indication provided).



K1205 MAP

Tektronix8-9

8.7 Numbering and identification parameter

8.7.1 MSISDN

The national (significant) mobile number could have the following form dependingupon the way in which the land mobile numbering plan is integrated with the

telephone numbering or ISDN plan:

?? The land mobile numbering plan might be fully integrated with the telephone

numbering or ISDN plan. In this case the mobile stations will be allocated a

subscriber number . The national (significant) mobile number then consists of

the trunk code or national destination code allocated to the numbering area

corresponding to the home area of the mobile station followed by the

subscriber number allocated to it.

??

The public land mobile network might be regarded as a separate numberingarea within the telephone network or the ISDN. In this case the national

(significant) mobile number will consist of the trunk code or national

destination code allocated to the PLMN and the subscriber number within the

PLMN.

8.7.2 MSRN

The mobile station roaming number is a number allocated to a land mobilestation for the purpose of rerouting calls to that station when it has roamed out of

the area covered by the PLMN [maritime switching centre MSC)] in which the

station is permanently registered.

The composition of the mobile station roaming number may vary depending uponwhere the mobile station is temporarily located and depending upon the method

by which it is allocated.

One acceptable method for allocating mobile station roaming numbers is for the

foreign PLMN (i.e. the network in which the mobile station is currently located) to

allocate a temporary national (significant) mobile number to the visiting mobilestation within its own numbering plan. The mobile station roaming number would

thus have the following composition:

(country code of the country in which the foreign PLMN is located)

+ (temporary national (significant) mobile number).

The mobile station roaming number is transferred to the home PLMN of the

mobile station.





K1205 MAP

Tektronix8-11

8.7.3 IMSI

A unique International Mobile Subscriber Identity (IMSI) shall be allocated to each

mobile subscriber in the GSM system.

IMSI is composed of three parts:

?? Mobile Country Code (MCC) consisting of three digits. The MCC identifies

uniquely the country of domicile of the mobile subscriber;

?? Mobile Network Code (MNC) consisting of two digits for GSM applications.

The MNC identifies the home GSM PLMN of the mobile subscriber;

?? Mobile Subscriber Identification Number (MSIN) identifying the mobilesubscriber within a GSM PLMN.

The National Mobile Subscriber Identity (NMSI) consists of the Mobile NetworkCode and the Mobile Subscriber Identification Number.


Structure of IMSI

MSINMNCMCC

2 digits3 digits

NMSI

IMSI

Not more than 15 digits



MAP K1205

Tektronix8-12

8.7.4 TMSI

Since the TMSI has only local significance (i.e. within the VLR and the area

controlled by the VLR), the structure and coding of it can be chosen by agreement

between operator and manufacturer in order to meet local needs.

The TMSI consists of 4 octets. It can be coded using a full hexadecimalrepresentation.

The network shall not allocate a TMSI with all 32 bits equal to 1 (this is because

the TMSI must be stored in the SIM, and the SIM uses 4 octets with all bits equal

to 1 for indicating that no valid TMSI is available.

8.7.5 LMSI

This parameter refers to a local identity allocated by the VLR to a given

subscriber for internal management of data in the VLR.

The LMSI consists of 4 octets.



K1205 MAP

Tektronix8-13

8.8 MAP message


Basic structure of MAP messages 1/3

Order of transmission

Ptr toCLD

SCCP-UDT message

Routinglabel

Msg codePtr toCLG

Ptr touser data

CLDparameter

CLGparameter

User data

LengthTransparentdata

MsgTypeTag

Transactionportion

Componentportion

Lengthfield

BEGIN message (TCAP)



MsgTypeTag

Transactionportion

Componentportion

Lengthfield

BEGIN message (TCAP)

ComponentType Tag

Lengthfield

Lengthfield

Componentportion Tag

Invoke Component

Invoke IDOperationParameters




MAP K1205

Tektronix8-14



ComponentType Tag

Lengthfield

Invoke IDOperationParameters


IMSI

MSC number

MSC signalling address signals

LMS ID

Update Location



K1205 MAP

Tektronix8-15

8.8.1 Examples of MAP operations


Location registration operation

UpdateLocation ::= OPERATION --Timer m

ARGUMENT

updateLocationArg UpdateLocationArg

RESULT

updateLocationRes UpdateLocationRes

ERRORS {

SystemFailure,

DataMissing,

-- DataMissing must not be used in version 1

UnexpectedDataValue,

UnknownSubscriber,

RoamingNotAllowed}

8.8.1.1 Update location

UpdateLocation ::= OPERATION --Timer m

ARGUMENT

updateLocationArg UpdateLocationArg

RESULT

updateLocationRes UpdateLocationRes

ERRORS {

SystemFailure,

DataMissing,



UnknownSubscriber,

RoamingNotAllowed}



MAP K1205

Tektronix8-16

Location updata (map.rec)

HH:MM:ss"m FROM TYPE DPC OPC SLS CIC NAME

07:27:51"9 1Tx> SCCP 13-7-00-1 02-7-00-0 8 UDT

E-GSM 09.02 (MAP) Rev 4.7.0 (MAP)

Begin

1 Origination Transaction ID

******** Orig Trans ID 0x6013565C2 Component Portion

2.1 Invoke

2.1.1 Invoke ID

00000000 Invoke ID value 0

2.1.2 Local Operation

00000010 Operation Code Update Location

2.1.3 Parameter Sequence

2.1.3.1 IMSI

******** MCC + MNC + MSIN 262018700001756

1111---- FILLER

2.1.3.2 MSC Number

1------- Extension Indicator No Extension

-001---- Nature of Address International number

----0001 Numbering Plan Indicator ISDN Telephony No plan (E.164)

******** MSC Address Signals 4917102000002.1.3.3 VLR Number




******** VLR Address Signals 491710200000

2.1.3.4 LMSI

******** LMSI ED 0E 00 09

- - - - - - - -

07:27:52"2 2Rx< SCCP 02-7-00-0 13-7-00-1 14 UDT

E-GSM 09.02 (MAP) Rev 4.7.0 (MAP)

End

1 Destination Transaction ID

******** Dest Trans ID 0x6013565C

2 Component Portion

2.1 Return Result Last

2.1.1 Invoke ID00000000 Invoke ID value 0

2.1.2 Return Result Sequence

2.1.2.1 Local Operation

00000010 Operation Code Update Location

2.1.2.2 HLR Number




******** HLR Address Signals 491718500000



K1205 MAP

Tektronix8-17

8.8.1.2 Forward SM

ForwardSM ::= OPERATION --Timer ml

ARGUMENT

forwardSM-Arg ForwardSM-ArgRESULT

ERRORS {

SystemFailure,

DataMissing,



FacilityNotSupported,

UnidentifiedSubscriber,

IllegalSubscriber,

IllegalEquipment,

-- IllegalEquipment must not be used in version 1AbsentSubscriber,

SubscriberBusyForMT-SMS,

-- SubscriberBusyForMT-SMS must not be used in version 1

SM-DeliveryFailure}

Forward SM (map.rec)


14:13:03"5 2Tx> SCCP 14-3-01-0 15-5-12-0 6 UDT

MAP BEG

Orig Trans ID 0x240

Invoke

Invoke ID value 1

Operation Code Forward SM

MCC + MNC + MSIN 238020100084731

Nature of Address International number

Numbering Plan Indicator ISDN Telephony No plan (E.164)

SC OA Address Signals 4540590000

SM RP UI 04 0A 91 54 04 86 20 00 00 00 69 90

90 51 41 20 40 56 F3 B7 FB DD 2C 36

9F 3A D0 92 ED 02 C5 6A BA D8 0C 44

2E BB 41 B0 9C 0E 96 D3 E5 6C 20 74

D8 4E 2E 83 88 65 50 0C E4 CE 97 41

ED 32 99 5C 66 97 D9 F3 B2 9C 05 82

81 DC F9 32 C8 9E 3E D3 D3 E7 32 A8

5D 26 93 CB EC 32 7B 5E 96 0314:13:04"7 2Rx< SCCP 15-5-12-0 14-3-01-0 4 UDT

MAP END

Dest Trans ID 0x240

Return Error

Invoke ID value 1

Error Code SM-Delivery Failure

SM Enumerated DF Cause Equipment Not SM-Equipped



MAP K1205

Tektronix8-18

8.8.2 Example of MAP data types


Data types

UpdateLocationArg ::= SEQUENCE {

imsi IMSI,

locationInfo LocationInfo,

vlr-Number ISDN-AddressString,

lmsi [10] LMSI OPTIONAL,

...}

IMSI ::= TBCD-STRING (SIZE (3..8))

-- digits of MCC, MNC, MSIN are concatenated in this order.



K1205 MAP

Tektronix8-19

AddressString ::= OCTET STRING (SIZE (1..maxAddressLength))

-- This type is used to represent a number for addressing

-- purposes. It is composed of

-- a) one octet for nature of address, and numbering plan

-- indicator.

-- b) digits of an address encoded as TBCD-String.

-- a) The first octet includes a one bit extension indicator, a

-- 3 bits nature of address indicator and a 4 bits numbering

-- plan indicator, encoded as follows:

-- bit 8: 1 (no extension)

-- bits 765: nature of address indicator

-- 000 unknown

-- 001 international number

-- 010 national significant number-- 011 network specific number

-- 100 subscriber number

-- 101 reserved

-- 110 abbreviated number

-- 111 reserved for extension

-- bits 4321: numbering plan indicator

-- 0000 unknown

-- 0001 ISDN/Telephony Numbering Plan (Rec CCITT E.164)

-- 0010 spare

-- 0011 data numbering plan (CCITT Rec X.121)-- 0100 telex numbering plan (CCITT Rec F.69)

-- 0101 spare

-- 0110 land mobile numbering plan (CCITT Rec E.212)

-- 0111 spare

-- 1000 national numbering plan

-- 1001 private numbering plan

-- 1111 reserved for extension

-- all other values are reserved.

-- b) The following octets representing digits of an address-- encoded as a TBCD-STRING.



MAP K1205

Tektronix8-20

ExtensibleUpdateLocationRes ::= SEQUENCE {

hlr-Number ISDN-AddressString,

...}

ForwardSM-Arg ::= SEQUENCE {

sm-RP-DA SM-RP-DA,sm-RP-OA SM-RP-OA,

sm-RP-UI SignalInfo,

moreMessagesToSend NULL OPTIONAL,

-- moreMessagesToSend must be absent in version 1

...}

IMSI ::= TBCD-STRING (SIZE (3..8))

-- digits of MCC, MNC, MSIN are concatenated in this order.

ISDN-AddressString ::= AddressString (SIZE (1..maxISDN-AddressLength))

-- This type is used to represent ISDN numbers.

LMSI ::= OCTET STRING (SIZE (4))

LocationInfo ::= CHOICE {

roamingNumber [0] ISDN- AddressString,

-- roamingNumber must not be used in version greater 1

msc-Number [1] ISDN- AddressString}

maxAddressLength INTEGER ::= 20

maxISDN-AddressLength INTEGER ::= 9

maxSignalInfoLength INTEGER ::= 200

-- This NamedValue represents the theoretical maximum number of

-- octets which are available to carry a single data type,

-- without requiring segmentation to cope with the network layer

-- service. However, the actual maximum size available for a data

-- type may be lower, especially when other information elements

-- have to be included in the same component.



K1205 MAP

Tektronix8-21

NetworkResource ::= ENUMERATED {

plmn (0),

hlr (1),

vlr (2),

pvlr (3),

controllingMSC (4),vmsc (5),

eir (6),

rss (7)}

RoamingNotAllowedCause ::= ENUMERATED {

plmnRoamingNotAllowed (0),

operatorDeterminedBarring (3)}

SignalInfo ::= OCTET STRING (SIZE (1..maxSignalInfoLength))

SM-DeliveryFailureCause ::= CHOICE {

sm-DeliveryFailureCauseWithDiagnostic

SM-DeliveryFailureCauseWithDiagnostic,

-- sm-DeliveryFailureCauseWithDiagnostic must not be used in version 1

sm-EnumeratedDeliveryFailureCause

SM-EnumeratedDeliveryFailureCause}

-- SM-EnumeratedDeliveryFailureCause must not be used in version greater 1

SM-DeliveryFailureCauseWithDiagnostic ::= SEQUENCE {

sm-EnumeratedDeliveryFailureCause

SM-EnumeratedDeliveryFailureCause,diagnosticInfo SignalInfo OPTIONAL,

...}

SM-EnumeratedDeliveryFailureCause ::= ENUMERATED {

memoryCapacityExceeded (0),

equipmentProtocolError (1),

equipmentNotSM-Equipped (2),

unknownServiceCentre (3),

sc-Congestion (4),

invalidSME-Address (5),

subscriberNotSC-Subscriber (6)}



MAP K1205

Tektronix8-22

SM-RP-DA ::= CHOICE {

imsi [0] IMSI,

lmsi [1] LMSI,

roamingNumber [3] ISDN- AddressString,

-- roaming number must not be used in version greater 1

serviceCentreAddressDA [4] AddressString,noSM-RP-DA [5] NULL}

-- noSM-RP-DA must not be used in version 1

SM-RP-OA ::= CHOICE {

msisdn [2] ISDN- AddressString,

serviceCentreAddressOA [4] AddressString,

noSM-RP-OA [5] NULL}

-- noSM-RP-OA must not be used in version 1

TBCD-STRING ::= OCTET STRING

-- This type (Telephony Binary Coded Decimal String) is used to-- represent several digits from 0 through 9, *, #, a, b, c, two

-- digits per octet, each digit encoded 0000 to 1001 (0 to 9),

-- 1010 (*), 1011 (#), 1100 (a), 1101 (b) or 1110 (c); 1111 used

-- as filler when there is an odd number of digits.

-- bits 8765 of octet n encoding digit 2n

-- bits 4321 of octet n encoding digit 2(n-1) +1

UpdateLocationArg ::= SEQUENCE {

imsi IMSI,

locationInfo LocationInfo,

vlr-Number ISDN-AddressString,

lmsi [10] LMSI OPTIONAL,

...}

UpdateLocationRes ::= CHOICE {

hlr-Number ISDN-AddressString,

-- hlr-Number must not be used in version greater 1

extensibleUpdateLocationRes ExtensibleUpdateLocationRes}

-- extensibleUpdateLocationRes must not be used in version 1



K1205 MAP

Tektronix8-23

8.8.3 Example of MAP errors and error codes


Error and error code

SystemFailure ::= ERROR

PARAMETER

networkResource NetworkResource

-- optional

systemFailure SystemFailure ::= localValue 34

AbsentSubscriber ::= ERROR

PARAMETER

mwd-Set BOOLEAN

-- optional

-- mwd-Set must be absent in version greater 1

DataMissing ::= ERROR

FacilityNotSupported::= ERROR

IllegalEquipment ::= ERROR

IllegalSubscriber ::= ERROR

RoamingNotAllowed::= ERRORPARAMETER

roamingNotAllowedCause RoamingNotAllowedCause

-- optional

-- roamingNotAllowedCause must be absent in version 1

-- roamingNotAllowedCause must be present in version greater 1



MAP K1205

Tektronix8-24

SM-DeliveryFailure ::= ERROR

PARAMETER

sm-DeliveryFailureCause SM-DeliveryFailureCause

SystemFailure ::= ERROR

PARAMETERnetworkResource NetworkResource

-- optional

UnexpectedDataValue ::= ERROR

UnidentifiedSubscriber ::= ERROR

UnknownSubscriber::= ERROR

absentSubscriber AbsentSubscriber ::= localValue 27

dataMissing DataMissing ::= localValue 35

facilityNotSupported FacilityNotSupported ::= localValue 21

illegalEquipment IllegalEquipment ::= localValue 12

illegalSubscriberIllegalSubscriber ::= localValue 9

roamingNotAllowed RoamingNotAllowed ::= localValue 8

systemFailure SystemFailure ::= localValue 34

unexpectedDataValue UnexpectedDataValue ::= localValue 36

unidentifiedSubscriber UnidentifiedSubscriber ::= localValue 5

unknownSubscriber UnknownSubscriber ::= localValue 1



K1205 MAP

Tektronix8-25

8.9 MAP services

8.9.1 Mobility services

MAP_UPDATE_LOCATION_AREA service: This service is used between

MSC and VLR to update location information in the network.

MAP_UPDATE_LOCATION service: This service is used by the VLR to update

the location information stored in the HLR.

MAP_CANCEL_LOCATION service: This service is used between HLR and

VLR to delete a subscriber record from the VLR.

MAP_SEND_IDENTIFICATION service: The MAP_SEND_IDENTIFICATION

service is used between a VLR and a previous VLR to retrieve IMSI andauthentication sets for a subscriber registering afresh in that VLR.

MAP_DETACH_IMSI service: The MAP_DETACH_IMSI service is used by the

MSC to indicate to the VLR that an MS is no longer reachable. Thenetwork needs this information e.g. to reject an incoming call without

initiating paging on the radio path.

MAP_PURGE_MS service: This service is used between the VLR and the HLR

to cause the HLR to mark its data for an MS so that any request for routinginformation for a mobile terminated call or a mobile terminated short

message will be treated as if the MS is not reachable.

MAP_PAGE service: This service is used between VLR and MSC to initiate

paging of an MS for mobile terminated call set-up, mobile terminated shortmessage or unstructured SS notification.

MAP_SEARCH_FOR_MS service: This service is used between VLR and

MSC to initiate paging of an MS in all location areas of that VLR.

MAP_PROCESS_ACCESS_REQUEST service: This service is used between

MSC and VLR to initiate processing of an MS access to the network, e.g.

in case of mobile originated call set-up or after being paged by the

network.

MAP_PREPARE_HANDOVER service: This service is used between MSC-A

and MSC-B (E-interface) when a call is to be handed over from MSC-A to

MSC-B.



MAP K1205

Tektronix8-26

MAP_SEND_END_SIGNAL service: This service is used between MSC-B and

MSC-A (E-interface) indicating that the radio path has been established

by MSC-B to the MS.

MAP_PROCESS_ACCESS_SIGNALLING service: This service is used

between MSC-B and MSC-A (E-interface) to pass information receivedon the A-interface in MSC-B to MSC-A.

MAP_FORWARD_ACCESS_SIGNALLING service: This service is used

between MSC-A and MSC-B (E-interface) to pass information to be

forwarded to the A-interface of MSC-B.

MAP_PREPARE_SUBSEQUENT_HANDOVER service: This service is used

between MSC-B and MSC-A (E-interface) to inform MSC-A that it hasbeen decided that a handover to either MSC-A or a third MSC (MSC-B')

is required.

MAP_ALLOCATE_HANDOVER_NUMBER service: This service is usedbetween MSC and VLR (B-interface) to request a handover number.

MAP_SEND_HANDOVER_REPORT service: This service is used between

VLR and MSC-B (B-interface) to transfer the handover number to be

forwarded to and used by MSC-A.

MAP_AUTHENTICATE service: This service is used between the VLR and the

MSC when the VLR receives a MAP service indication from the MSC

concerning a location registration, call set-up, operation on a

supplementary service or a request from the MSC to initiate

authentication.

MAP_SEND_AUTHENTICATION_INFO service: This service is used between

the VLR and the HLR for the VLR to retrieve authentication information

from the HLR.

MAP_SET_CIPHERING_MODE service: This service is used between the

VLR and the MSC to set the ciphering mode and to start ciphering if

applicable.

MAP_CHECK_IMEI service: This service is used between the VLR and the

MSC and between the MSC and the EIR to request check of IMEI.

MAP_OBTAIN_IMEI service: This service is used between the VLR and the

MSC to request the IMEI.



K1205 MAP

Tektronix8-27

MAP-INSERT-SUBSCRIBER-DATA service: This service is used by an HLR

to update a VLR with certain subscriber data in the following occasions:

?? the operator has changed the subscription of one or moresupplementary services, basic services or data of a subscriber.

Note that in case of withdrawal of a Basic or Supplementary

service this primitive shall not be used;

?? the operator has applied, changed or removed Operator

Determined Barring;

?? the subscriber has changed data concerning one or more

supplementary services by using a subscriber procedure;

?? the HLR provides the VLR with subscriber parameters at

location updating of a subscriber or at restoration. In this case,

this service is used to indicate explicitly that a supplementary

service is not provisioned, if the supplementary servicespecification requires it. The only supplementary services which

have this requirement are the CLIR and COLR services.

MAP-DELETE-SUBSCRIBER-DATA service: This service is used by an HLR

to remove certain subscriber data from a VLR if the subscription of one ormore supplementary services or basic services is withdrawn.

MAP-PROVIDE-IMSI service: This service is used by a VLR in order to get, via

the MSC, the IMSI of a subscriber (e.g. when a subscriber has identified

itself with a TMSI not allocated to any subscriber in the VLR).

MAP-FORWARD-NEW-TMSI service: This service is used by a VLR to

allocate, via MSC, a new TMSI to a subscriber during an ongoing

transaction (e.g. call set-up, location updating or supplementary services

operation).

MAP_RESET service: This service is used by the HLR, after a restart, to

indicate to a list of VLRs that a failure occurred.

MAP_FORWARD_CHECK_SS_INDICATION service: This service may be

used by an HLR as an implementation option, to indicate to a mobile

subscriber that supplementary services parameters may have beenaltered, e.g. due to a restart.

MAP_RESTORE_DATA service: This service is used to update the LMSI in the

HLR, if provided, and to request the HLR to send all data to the VLR that

are to be stored in the subscriber's IMSI record.



MAP K1205

Tektronix8-28

8.9.2 Operation and maintenance services

MAP-ACTIVATE-TRACE-MODE service: This service is used between the

HLR and the VLR to activate subscriber tracing in the VLR.

MAP-DEACTIVATE-TRACE-MODE service: This service is used between the

VLR and the HLR for deactivating subscriber tracing in the VLR.

MAP-TRACE-SUBSCRIBER-ACTIVITY service: This service is used between

the VLR and the MSC to activate the subscriber tracing in the MSC.

MAP-SEND-IMSI service: This service is used by a VLR in order to fetch the

IMSI of a subscriber in case of some Operation & Maintenance procedure

where subscriber data are needed in the Visited PLMN and MSISDN is

the only subscriber's identi ty known.

8.9.3 Call handling services

MAP_SEND_INFO_FOR_INCOMING_CALL service: This service is used

between an MSC and VLR. It is invoked by an MSC receiving an incoming

call (call to MS) to request the VLR for information to proceed and set up

the call.

MAP_SEND_INFO_FOR_OUTGOING_CALL service: This service is used

between an MSC and VLR. The service is invoked by an MSC to retrieve

the required information from a VLR to enable an outgoing call set up

request (call from an MS) to be actioned.

MAP_SEND_ROUTING_INFORMATION service: This service is used

between the Gateway MSC and the HLR. The service is invoked by the

Gateway MSC to perform the interrogation of the HLR in order to route a

call towards the called MS.

MAP_PROVIDE_ROAMING_NUMBER service: This service is invoked by the

HLR to request a VLR to send back a roaming number to enable the HLR

to instruct the GMSC to route an incoming call to the called MS.

MAP_COMPLETE_CALL service: This service is invoked by a VLR to requestthe MSC to set up a call to an MS in the case of an incoming call, and froman MS for an outgoing call.

MAP_PROCESS_CALL_WAITING service: This service is invoked by the

VLR to request the MSC to invoke the Call Waiting service.



K1205 MAP

Tektronix8-29

8.9.4 Supplementary service related services

MAP_REGISTER_SS service: This service is used between the MSC and the

VLR and between the VLR and the HLR to register data related to a

supplementary service.

MAP_ERASE_SS service: This service is used between the MSC and the VLR

and between the VLR and the HLR to erase data related to a

supplementary service.

MAP_ACTIVATE_SS service: This service is used between the MSC and the

VLR and between the VLR and the HLR to activate a supplementary

service.

MAP_DEACTIVATE_SS service: This service is used between the MSC and

the VLR and between the VLR and the HLR to deactivate a supplementaryservice.

MAP_INTERROGATE_SS service: This service is used between the MSC and

the VLR and between the VLR and the HLR to retrieve information related

to a supplementary service.

MAP_INVOKE_SS service: This service is used between the MSC and the

VLR to check the subscriber's subscription to a given supplementary

service in the VLR, in connection with in-call invocation of that

supplementary service, i.e. after the call set-up phase is finished.

MAP_REGISTER_PASSWORD service: This service is used between theMSC and the VLR and between the VLR and the HLR if the mobile

subscriber requests to register a new password.

MAP_GET_PASSWORD service: This service is used between the HLR and

the VLR and between the VLR and the MSC when the HLR receives a

request from the mobile subscriber for an operation on a supplementary

service which requires a password from the subscriber.

MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service: This service is

used between the MSC and the VLR and between the VLR and the HLR

to relay information in order to allow unstructured supplementary serviceoperation.

MAP_UNSTRUCTURED_SS_REQUEST service: This service is used

between the HLR and the VLR and between the VLR and the MSC when

the invoking entity requires information from the mobile user, in connection

with unstructured supplementary service handling.



MAP K1205

Tektronix8-30

MAP_UNSTRUCTURED_SS_NOTIFY service: This service is used between

the HLR and the VLR and between the VLR and the MSC when the

invoking entity requires a notification to be sent to the mobile user, in

connection with unstructured supplementary services handling.

8.9.5 Short message service management services

MAP-SEND-ROUTING-INFO-FOR-SM service: This service is used between

the gateway MSC and the HLR to retrieve the routing information needed

for routing the short message to the servicing MSC.

MAP-FORWARD-SHORT-MESSAGE service: This service is used between

the gateway MSC and the servicing MSC to forward mobile originated or

mobile terminated short messages.

MAP-REPORT-SM-DELIVERY-STATUS service: This service is used to set

the Message Waiting Data into the HLR or to inform the HLR of successful

SM transfer after polling.

MAP-READY-FOR-SM service: This service is used between the MSC and

VLR and as well between the VLR and the HLR. The MSC initiates this

service if a subscriber indicates memory available situation. The VLR

uses the service to indicate this to the HLR. The VLR initiates this service

if a subscriber, whose message waiting flag is active in the VLR, has

radio contact in the MSC.

MAP-ALERT-SERVICE-CENTRE service: This service is used between theHLR and the interworking MSC. The HLR initiates this service, if the HLR

detects that a subscriber, whose MSISDN is in the Message Waiting Data

file, is active or the mobile station has memory available.

MAP-INFORM-SERVICE-CENTRE service: This service is used between the

HLR and the gateway MSC to inform the Service Centre which MSISDN

number is stored in the Message Waiting Data file.

MAP-SEND-INFO-FOR-MT-SMS service: This service is invoked by the MSC

receiving an mobile terminated short message to request subscriber

related information from the VLR.

MAP-SEND-INFO-FOR-MO-SMS service: This service is invoked by the MSC

which has to handle a mobile originated short message request to request

the subscriber related information from the VLR.



K1205 MAP

Tektronix8-31

8.10 Example procedures of MAP

8.10.1 Detach IMSI / purge MS

On receipt of an A_LU_REQUEST (DETACH IMSI) indication from the radio

interface this procedure invokes the MAP_DETACH_IMSI service in order to

inform the visitor location register that a subscriber is no longer reachable, e.g.

due to switched off station. This information is used by the VLR to reject mobile

terminating calls or short messages without sending page messages on the

radio path. The service is unconfirmed as it is likely that the MS is switched offbefore receiving a confirmation.

When the VLR receives an indication on the O&M interface that the MS record is

to be purged (either because of administrative action or because the MS has

been inactive for an extended period), this procedure invokes theMAP_PURGE_MS service to request the HLR to set the "MS purged" flag for the

MS so that any request for routing information for a mobile terminated call or a

mobile terminated short message will be treated as if the MS is not reachable.


Detach IMSI and purge MS

VLRBSS HLRMSCMS A B D

A_LU_REQUEST (Detach IMSI)

MAP_DETACH_ IMSI

MAP_PURGE_ MS

MAP_PURGE_ MS ack



MAP K1205

Tektronix8-32

8.10.2 Location Update

The location updating procedure is used to update the location information held

in the network. This location information is used to route incoming calls, short

messages and unstructured supplementary service data to the roamingsubscriber.

To minimise the updates of the subscriber's HLR, the HLR holds only information

about the VLR and MSC the subscriber is attached to. The VLR contains more

detailed location information, i.e. the location area the subscriber is actually

roaming in. Therefore, the VLR needs to be updated at each location area

change, whereas the HLR needs updating only in the following cases:

?? when the subscriber registers in a new VLR

?? when the subscriber changes the MSC area

?? if the indicators "Confirmed by HLR" or "Location Information Confirmed in

HLR" is set to "Not Confirmed" receives an indication that the subscriber is

present.

The following MAP services are invoked by the location update procedure:

MAP_UPDATE_LOCATION_AREA

MAP_UPDATE_LOCATIONMAP_CANCEL_LOCATION

MAP_INSERT_SUBSCRIBER_DATA

MAP_SEND_IDENTIFICATION

MAP_PROVIDE_IMSI

Optional services:

MAP_AUTHENTICATE

MAP_SET_CIPHERING_MODE

MAP_FORWARD_NEW_TMSI

MAP_CHECK_IMEIMAP_ACTIVATE_TRACE_MODE

MAP_TRACE_SUBSCRIBER_ACTIVITY



K1205 MAP

Tektronix8-33


MAP_UPDATE_ LOCATION_AREA ack

Location updating when roaming within an VLR area

A_LU_CONFIRM

VLRBSS MSCMS A B

MAP_UPDATE_ LOCATION_AREA

A_LU_REQUEST


MAP_INSERT_SUBSCRIBER_DATA ack

MAP_UPDATE_LOCATION



A_LU_CONFIRM

A_LU_REQUEST

Location updating when changing the VLR area

PVLR

MSC HLRVLRMS B

G

DBSS A

D

MAP_SEND_ IDENTIFICATION

MAP_SEND_ IDENTIFICATION ack

MAP_CANCEL_ LOCATION

MAP_CANCEL_ LOCATION ack

MAP_UPDATE_LOCATION ack




MAP K1205

Tektronix8-34


Location updating involving both a VLR and an HLR,when IMSI can not be retrieved from the previous VLR

MAP_INSERT_SUBSCRIBER_DATA ack

MAP_UPDATE_LOCATION



A_LU_CONFIRM

A_LU_REQUEST PVLR

MSC HLRVLRMSB

G

DBSS

A

D

MAP_PROVIDE_ IMSI ack

MAP_PROVIDE_ IMSI

MAP_CANCEL_ LOCATION

MAP_CANCEL_ LOCATION ack

MAP_UPDATE_LOCATION ack


Cancel location (map.rec)


07:28:12"5 2Tx> SCCP 13-7-00-1 15-7-00-0 13 UDT

MAP BEG

Orig Trans ID 0x3AF90300

Invoke

Invoke ID value 1

Operation Code Update Location

MCC + MNC + MSIN 262012000002196Nature of Address International number


MSC Address Signals 491710600000



VLR Address Signals 491710600000

LMSI 00 00 38 2F

- - - - - - - -

07:28:12"8 1Rx< SCCP 15-5-00-0 13-7-00-1 11 UDT

MAP BEG

Orig Trans ID 0x3A520601

Invoke

Invoke ID value 1

Operation Code Cancel Location

MCC + MNC + MSIN 262012000002196

LMSI 00 00 5B 0A

- - - - - - - -

07:28:12"9 5Tx> SCCP 13-7-00-1 15-5-00-0 3 UDT

MAP END

Dest Trans ID 0x3A520601

Return Result Last

Invoke ID value 1



K1205 MAP

Tektronix8-35

8.10.3 Retrieval of routing information

It is assumed that signalling towards the fixed network uses the messages IAM

(Initial Address Message) and REL (Release).

The following MAP services are used to retrieve routing information:

MAP_SEND_ROUTING_INFORMATION

MAP_PROVIDE_ROAMING_NUMBER

Optional service:

MAP_RESTORE_DATA


Retrieval of routing information

MAP_SEND_ROUTING_INFORMATION

Nertwork

HLRGMSCE C

I_IAM

MAP_PROVIDE_

ROAMING_NUMBERack

MAP_PROVIDE_ ROAMING_NUMBER

MAP_SEND_ROUTING_INFORMATION ack

MSC VLRD

I_IAM



MAP K1205

Tektronix8-36

Send routing information (map.rec)


07:29:37"1 2Tx> SCCP 13-7-00-1 08-0-00-0 10 UDT

MAP BEG

Orig Trans ID 0xBA4A0001Invoke

Invoke ID value 1

Operation Code Send Routing Info

Nature of Address National specific number


MS ISDN Address Signals 1718705658

07:29:37"1 2Rx< SCCP 08-3-00-0 13-7-00-1 9 UDT

MAP BEG

Orig Trans ID 0x3A2B0701

Invoke

Invoke ID value 1

Operation Code Provide Roaming Number

MCC + MNC + MSIN 262018700006597

LMSI 00 00 22 4E

Protocol Id Gsm-0408

Signal Info 04 01 A0DTAP NO_HDR

Transaction Id value NOT PRESENT

Transaction Id flag NOT PRESENT

- - - - - - - -

07:29:37"3 6Tx> SCCP 13-7-00-1 08-3-00-0 9 UDT

MAP END

Dest Trans ID 0x3A2B0701

Return Result Last

Invoke ID value 1

Operation Code Provide Roaming Number



Roaming Address Signals 491710539124

07:29:37"3 1Rx< SCCP 08-0-00-0 13-7-00-1 10 UDT

MAP ENDDest Trans ID 0xBA4A0001

Return Result Last

Invoke ID value 1

Operation Code Send Routing Info

MCC + MNC + MSIN 262018700006597



Roaming Address Signals 491710539124



K1205 MAP

Tektronix8-37

8.10.4 Mobile terminating call

The procedure is an example sequence which assumes successful operation. It

is also assumed that the location of the subscriber has already been determined.

The following MAP services are used during MS terminating call set up:

MAP_SEND_INFO_FOR_INCOMING_CALL

MAP_PROCESS_ACCESS_REQUEST

MAP_PAGE

MAP_SEARCH_FOR_MS

MAP_COMPLETE_CALL

Optional services:

MAP_PROCESS_CALL_WAITING

MAP_PROVIDE_IMSIMAP_AUTHENTICATIONMAP_SET_CIPHERING_MODE


MAP_CHECK_IMEI



MAP K1205

Tektronix8-38


MS terminating call set-up (MTC) 1/2

VLRBSS GMSCMSCMS A B

I_IAM

MAP_PROCESS_ ACCESS_REQUEST


ack

MAP_SEND_INFO_ FOR_INCOMING_

CALL

MAP_COMPLETE_ CALL

MAP_PAGE or MAP_SEARCH_FOR_

MOBILE_SUBSCRIBERPaging

Layer 3 info


MS terminating call set-up (MTC) 2/2

VLRBSS GMSCMSCMS A B

I_ACM

A_ASS_COMP

A_ASS_REQ

MAP_SEND_INFO_ FOR_INCOMING_

CALL ack

A_ALERT

A_CONN

I_ANM A_CONN_ACK

A_SETUP

A_CALL_CONF



K1205 MAP

Tektronix8-39

8.10.5 Mobile originating call

The call can be established in two ways in the GSM. Either with the early

assignment or with the off air call set up (OACSU). The difference between these

is that in the latter case the radio channel is reserved at the last possible moment,i.e. when the called subscriber answers. The procedure with the early assignment

is shown as an example sequence which assumes successful operation.

The following MAP services are used during outgoing call set up:


MAP_SEND_INFO_FOR_OUTGOING_CALLMAP_COMPLETE_CALL

Optional services:

MAP_PROVIDE_IMSIMAP_SET_CIPHERING_MODEMAP_AUTHENTICATE


MAP_CHECK_IMEI

MAP_OBTAIN_IMEI


MS originating call set-up (MOC)

VLRBSS GMSCMSCMS A B B

A_CM_SER_REQ MAP_PROCESS_ ACCESS_REQUEST

A_ASS_COMP

A_ASS_REQ


ack A_CM_SER_ACC

A_SETUPMAP_SEND_INFO_ FOR_OUTGOING_

CALL

MAP_COMPLETE_ CALL

A_CALL_PROC

I_IAM

MAP_SEND_INFO_ FOR_OUTGOING_

CALL ack



MAP K1205

Tektronix8-40

8.10.6 Handover

The handover between different MSCs is called Inter-MSC handover. The call is

handed over from the controlling MSC, called MSC-A to another MSC, called

MSC-B.

The MAP handover procedures achieve the functionality required to set up anMSC-MSC dialogue, to optionally allocate a handover number and to transport

BSSAP messages. The transported BSSAP messages are controlled and

handled by the Handover Control Application in the MSCs. This information will

be transparent to the MAP protocol. If the MSC receives via the MAP protocol

BSSAP messages, this information will be forwarded to the Handover Control Application and vice versa if the Handover Control Application requires the

sending of BSSAP messages via the MAP protocol.


Successful basic handover procedure to MSC-B

VLR-BMSC-BMSC-AE B

MAP_ALLOCATE_HANDOVER_NUMBER

MAP_FORWARD_ACCESS_SIGNALLING

MAP_SEND_END_SIGNAL ack

MAP_SEND_HANDOVER_REPORT ack

MAP_SEND_END_SIGNAL

MAP_PREPARE_HANDOVER ack

MAP_PREPARE_HANDOVER

MAP_SEND_HANDOVER_REPORT

MAP_PROCESS_ACCESS_SIGNALLING

MAP_PROCESS_ACCESS_SIGNALLING

This can be sent at any time after theconnection between MSC-A and MSC-B

is established.



K1205 MAP

Tektronix8-41

8.10.7 Supplementary Service

8.10.7.1 Registration procedure

The registration procedure is used to register data related to a supplementary

service in the HLR. The registration procedure is a fully transparent

communication between the MS and the HLR, except that some services may be

invoked as a result of the procedure.

The following services may be used:



MAP_PROVIDE_IMSI

MAP_FORWARD_NEW_TMSIMAP_AUTHENTICATE


MAP_CHECK_IMEI

MAP_READY_FOR_SM

MAP_INSERT_SUBSCRIBER_DATAMAP_REGISTER_SS


Supplementary service registration


A_CM_SERV_REQMAP_PROC_ ACC_REQ

MAP_REGISTER_SS

MAP_REGISTER_ SS ack

MAP_REGISTER_SS

MAP_REGISTER_ SS ack

A_REGISTER_SS

A_REGISTER_SS ack



MAP K1205

Tektronix8-42

8.10.7.2 Erasure procedure

The erasure procedure is used to erase data related to a supplementary service

in the HLR. The erasure procedure is a fully transparent communication between

the MS and the HLR, except that some services may be invoked as a result of theprocedure.




MAP_PROVIDE_IMSIMAP_FORWARD_NEW_TMSI

MAP_AUTHENTICATE


MAP_CHECK_IMEI

MAP_READY_FOR_SMMAP_INSERT_SUBSCRIBER_DATAMAP_ERASE_SS


Supplementary service erasure



MAP_ERASE_SS

MAP_ERASE_ SS ack

MAP_ERASE_SS

MAP_ERASE_ SS ack

A_ERASE_SS

A_ERASE_SS ack



K1205 MAP

Tektronix8-43

8.10.7.3 Activation procedure

The activation procedure is used to activate a supplementary service in the HLR.

The activation procedure is a fully transparent communication between the MS

and the HLR, except that some services may be invoked as a result of theprocedure.





MAP_AUTHENTICATE


MAP_CHECK_IMEI

MAP_READY_FOR_SMMAP_GET_PASSWORDMAP_INSERT_SUBSCRIBER_DATA

MAP_ACTIVATE_SS


Supplementary service activation

VLREIR HLRMSCMS A B D


MAP_ ACTIVATE _SS

MAP_ ACTIVATE _ SS ack

MAP_ ACTIVATE _SS

MAP_ ACTIVATE _ SS ack

A_ACTIVATE_SS

A_ ACTIVATE _SS ack

MAP_GET_PW

MAP_GET_PW ack

MAP_GET_PW

MAP_GET_PW ack

A_GET_PW

A_GET_PW ack



MAP K1205

Tektronix8-44

8.10.7.4 Deactivation procedure

The deactivation procedure is used to deactivate a supplementary service in the

HLR. The deactivation procedure is a fully transparent communication between

the MS and the HLR, except that some services may be invoked as a result of theprocedure.





MAP_AUTHENTICATE


MAP_CHECK_IMEI

MAP_READY_FOR_SMMAP_GET_PASSWORDMAP_INSERT_SUBSCRIBER_DATA

MAP_DEACTIVATE_SS


Supplementary service deactivation



MAP_ DEACTIVATE _SS

MAP_ DEACTIVATE _ SS ack

MAP_ DEACTIVATE _SS

MAP_ DEACTIVATE _ SS ack

A_DEACTIVATE_SS

A_ DEACTIVATE _SS ack

MAP_GET_PW

MAP_GET_PW ack

MAP_GET_PW

MAP_GET_PW ack

A_GET_PW

A_GET_PW ack



K1205 MAP

Tektronix8-45

8.10.7.5 Interrogation procedure

The interrogation procedure is used to retrieve information related to a

supplementary service from the VLR or the HLR. It is the VLR which decides

whether an interrogation request should be forwarded to the HLR or not. Somenon-supplementary service related services may be invoked as a result of the

procedure.



MAP_TRACE_SUBSCRIBER_ACTIVITYMAP_PROVIDE_IMSI


MAP_AUTHENTICATE


MAP_CHECK_IMEIMAP_READY_FOR_SMMAP_INTERROGATE_SS


Supplementary service interrogation



MAP_INTERROGATE _SS

MAP_ INTERROGATE _

SS ack

MAP_ INTERROGATE _SS

MAP_ INTERROGATE _

SS ack

A_INTERROGATE_SS

A_ INTERROGATE _SS ack



MAP K1205

Tektronix8-46

8.10.7.6 Invocation procedure

The invocation procedure is used to check subscription data in the VLR for

certain supplementary services which are invoked after the call set-up phase is

finished.




MAP_PROVIDE_IMSI

MAP_FORWARD_NEW_TMSIMAP_AUTHENTICATE


MAP_CHECK_IMEI

MAP_READY_FOR_SM

MAP_INVOKE_SS


Supplementary service invocation

VLRBSS MSCMS A B


MAP_ INVOKE _SS

MAP_ INVOKE _ SS ack

A_INVOKE_SS

A_ INVOKE _SS ack



K1205 MAP

Tektronix8-47

8.10.7.7 Password registration procedure

The password registration procedure is used to register a password in the HLR.

The password registration procedure is a fully transparent communication

between the MS and the HLR, except that some services may be invoked as aresult of the procedure.





MAP_AUTHENTICATE


MAP_CHECK_IMEI

MAP_READY_FOR_SMMAP_GET_PASSWORD


Supplementary service password registration



MAP_REGISTER_PW

MAP_GET_PW

MAP_GET_PW ack

MAP_GET_PW

MAP_GET_PW ack

MAP_GET_PW

MAP_GET_PW ack

MAP_REGISTER_ PW ack

MAP_REGISTER_PW

MAP_GET_PW

MAP_GET_PW ack

MAP_GET_PW

MAP_GET_PW ack

MAP_GET_PW

MAP_GET_PW ack

MAP_REGISTER_ PW ack

A_REGISTER_PW

A_GET_PW

A_GET_PW ack

A_GET_PW

A_GET_PW ack

A_GET_PW

A_GET_PW ack

A_REGISTER_PW ack



MAP K1205

Tektronix8-48

8.10.8 Short message service

8.10.8.1 Mobile originated short message transfer

The mobile originated short message service procedure is used to forward short

message from a mobile subscriber to a Service Centre.

In addition the following MAP services are used:

MAP_PROCESS_ACCESS_REQUESTMAP_AUTHENTICATE


MAP_PROVIDE_IMSI

MAP_CHECK_IMEI

MAP_FORWARD_NEW_TMSIMAP_TRACE_SUBSCRIBER_ACTIVITY

MAP_READY_FOR_SM


Mobile originated short message transfer

InterworkingMSC

ServicingMSC

SCVLRMS

Short Message MAP_SEND_INFO_ FOR_MO_SMS

MAP_SEND_INFO_ FOR_MO_SMS ack

MAP_FORWARD_SHORT_MESSAGE

Short Message

Short Message ack

MAP_FORWARD_SHORT_MESSAGE ack

Short Message ack



K1205 MAP

Tektronix8-49

8.10.8.2 Mobile terminated short message transfer

The mobile terminated short message transfer procedure is used for forwarding

a short message or several short messages from a Service Centre to a mobile

subscriber.

In addition the following MAP services are used:


MAP_PAGE

MAP_SEARCH_FOR_MS

MAP_AUTHENTICATEMAP_SET_CIPHERING_MODE

MAP_CHECK_IMEI


MAP_REPORT_SM_DELIVERY_STATUS

MAP_INFORM_SERVICE_CENTREMAP_TRACE_SUBSCRIBER_ACTIVITYMAP_READY_FOR_SM



MAP K1205

Tektronix8-50


Mobile terminated multiple short message transfer 1/2

MSServicing

MSCVLR HLR

GatewayMSC

SC

Short messageMAP_SEND_ ROUTING_INFO_

FOR_SM

MAP_SEND_ ROUTING_INFO_

FOR_SM ack

MAP_FORWARD_SHORT_MESSAGE(The More Message To Send flag is TRUE)

MAP_SEND_ INFO_FOR_MT_

SMS

MAP_PAGE/MAP_SEARCH_ FOR_MOBILE_ SUBSCRIBER

Page

Page response


Mobile terminated multiple short message transfer 2/2

MSServicing

MSCVLR HLR

GatewayMSC

SC

Short message

MAP_FORWARD_SHORT_MESSAGE ack

MAP_SEND_ INFO_FOR_ MT_SMS ack

MAP_SEARCH_ FOR_MOBILE_ SUBSCRIBER ack

Short message ack

Short message ack

Short message

Short message

Short message ackMAP_FORWARD_SHORT_MESSAGE ack

Short message ack

MAP_PROCESS_ ACCESS_

REQUEST ack

MAP_FORWARD_SHORT_MESSAGE(The More Message To Send flag is FALSE)



K1205 MAP

Tektronix8-51

8.10.8.3 Short message alert

The Short Message Alert procedure is used for alerting the Service Centre when

the mobile subscriber is active after a short message transfer has failed because

the mobile subscriber is not reachable or when the mobile station has indicatedthat it has memory capacity to accept a short message.


Short message alert(Mobile is present)

MSServicing

MSCVLR HLR

InterworkingMSC

SC

MAP_READY_

FOR_SM ack

MAP_READY_ FOR_SM

(Mobile Present)

CM Service Request

Alert Service Centre

MAP_PROCESS_ ACCESS_ REQUEST

MAP_ALERT_ SERVICE_CENTRE






ack


ack


ack

The Short Message Alert procedure for the case where the mobile station

indicates that it has memory capacity to accept one or more short messages.

In addition the following MAP services are used in the mobile station memoryavailable case:


MAP_AUTHENTICATE

MAP_SET_CIPHERING_MODEMAP_PROVIDE_IMSI

MAP_CHECK_IMEI





MAP K1205

Tektronix8-52


Short message alert(Mobile station memory capacity available)

MS ServicingMSC

VLR HLR InterworkingMSC

SC

MAP_READY_ FOR_SM ack

MAP_READY_

FOR_SM(Memory available)

SM memorycapacity available








ack


ack


ack

MAP_READY_ FOR_SM(Memory available)

MAP_READY_ FOR_SM ack

SM memorycapacity available

ack

The Short Message Alert procedure when the mobile station indicates successful

transfer after polling.


Short message alert(Successful transfer after polling)

InterworkingMSC

GatewayMSC SCHLR

MAP_REPORT_SM_ DELIVERY_STATUS

MAP_REPORT_SM_ DELIVERY_STATUS

ack Alert Service Centre





ack


ack


ack





K1205 MAP

Tektronix8-53

8.10.8.4 Short message delivery status report

The Short Message Alert procedure when the mobile station indicates successful

transfer after polling.


Short message delivery status report

GatewayMSC

VLR SCHLRVisitedMSC

MAP_REPORT_ SM_DELIVERY_

STATUS

Short Messagenegativ ack

MAP_FORWARD_SHORT_MESSAGE ack / nack

MAP_REPORT_ SM_DELIVERY_

STATUS ack



MAP K1205

Tektronix8-54

8.11 General functions of Short Message Services

The purpose of the Short Message Service is to provide the means to transfer

messages between a GSM PLMN Mobile Station and a Short Message Entity

via a Service Centre.

These procedures are necessary to support the Short Message Service betweenthe MS and the MSC and vice versa. They are based on services provided by the

Mobility Management sublayer.

The hierarchical model shows the layer structure of the MSC and the MS.


Protocol hierarchy

SM-AL

SM-TL

CM-sublayer

SM-RL

RR-sublayer

MM-sublayer

MSC

SMR

SMC

MS

SMR

SMCSM-CP protocol

SM-RP protocol

Abbreviations:

SM-AL Short Message Application Layer

SM-TL Short Message Transfer Layer

SM-RL Short Message Relay Layer

SM-RP Short Message Relay ProtocolSMR Short Message Relay (entity)

CM-sub Connection Management sublayer

SM-CP Short Message Control Protocol

SMC Short Message Control (entity)

MM-sub Mobility Management sublayer

RR-sub Radio Resource Management sublayer



K1205 MAP

Tektronix8-55

The CM-sublayer, in terms of the Short Message Service Support, provides

services to the Short Message Relay Layer.

On the MS-side the Short Message Relay Layer provides services to the ShortMessage Transfer Layer. The Short Message Relay Layer is the upper layer on

the network side (MSC), and the SM-user information elements are mapped to

TCAP/MAP.

The peer protocol between two SMC entities is denoted SM-CP, and between

two SMR entities, SM-RP.







MAP K1205

Tektronix8-58

8.11.1 SMS Control Protocol User Part

An SMC entity communicates with a corresponding peer entity using an MM-

connection. Multiple MM-connections may be established at the same time,

allowing parallel transactions.

The procedures needed for short message control are:

?? connection establishment procedures;

?? RP Data Unit (RPDU) transfer procedures;

?? connection release procedures; and

?? procedures for abnormal cases.

8.11.1.1 SMS CP messages

The message shall consist of the following parts:

?? protocol discriminator;

?? transaction identifier;

?? message type;

?? other required information elements.

8 7 6 5 4 3 2 1

Transaction ID Protocol Discriminator

Message Type

:

Other Information Elements



K1205 MAP

Tektronix8-59

Abbreviations:

V Value only

LV Length and ValueTLV Type, Length and Value

M Mandatory

O Optional

CP-DATA message is sent between an MSC and an MS, in both directions. The

message contains the user data to be relayed between the CM-users, and

associated parameters.

Information element Presence Format Length

Protocol discriminator M V ½ octet

Transaction identifier M V ½ octet

Message type M V 1 octetCP-User data M LV ? 249 octets

CP-ACK message is sent between an MSC and an MS, in both directions, and

is used to acknowledge the reception of a CP-DATA message.




Message type M V 1 octet

CP-ERROR message is sent between an MSC and an MS, in both directions,

and used to convey error information.




Message type M V 1 octet

CP-Cause M V 1 octet





K1205 MAP

Tektronix8-61

Message type

The purpose of the message type, together with the protocol discriminator, is to

identify the function of the message being sent.

Bits 8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 1 CP-DATA

0 0 0 0 0 1 0 0 CP-ACK

0 0 0 1 0 0 0 0 CP-ERROR

CP-User data element

The CP-User data element is used to carry the RPDU. It has an informationelement identifier, a length indicator and a data field. The data field will contain

the RPDUs. The maximum length of the data field is 255 octets.

8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 1 1 octet

CP-User Data IEI

Length indicator 1 octet

RPDU ? octet

Maximum length 248 octets

CP-Cause element

This element is included in the CP-ERROR message.

8 7 6 5 4 3 2 1

0 0 0 0 0 0 1 0 1 octet

CP-User Data IEI

0 Cause value 1 octet



MAP K1205

Tektronix8-62

Error causes:

Cause value Cause nr. Cause

Bits 7 6 5 4 3 2 1 #

0 0 1 0 0 0 1 17 Network failure0 0 1 0 1 1 0 22 Congestion

1 0 1 0 0 0 1 81 Invalid Transaction Identifier value

1 0 1 1 1 1 1 95 Semantically incorrect message1 1 0 0 0 0 0 96 Invalid mandatory information

1 1 0 0 0 0 1 97 Message type non-existent or not

implemented

1 1 0 0 0 1 0 98 Message not compatible with the short

message protocol state1 1 0 0 0 1 1 99 Information element non-existent or

not implemented

1 1 0 1 1 1 1 111 Protocol error, unspecified

All other cause values shall be treated as cause number 111.



K1205 MAP

Tektronix8-63

8.11.2 SMS Relay Protocol User Part

An SMR entity communicates with a corresponding peer entity using a CM-

connection. Multiple CM-connections may be established at the same time,

allowing parallel transactions. There is a functional one to one relation betweenthe SMR entity and the SMC entity of the CM-sublayer.

The procedures needed for short message and notification relaying are:

?? TP Data Unit (TPDU) relay procedures;

?? notification relay procedures;

?? procedures for abnormal cases.

8.11.2.1 SMS RP messages

The message shall consist of the following parts:

?? message type indicator;

?? message reference;

?? other required information elements.

8 7 6 5 4 3 2 1

spare MTI

0 0 0 0 0

Message reference

:

Other Information Elements



MAP K1205

Tektronix8-64

Abbrevations see 8.11.1.1.

RP-DATA (Network to Mobile Station) is used to relay the TPDUs.


RP-Message Type M V 3 bits

RP-Message Reference M V 1 octet

RP-Originator Address M LV 1-12 octets

RP-Destination Address M LV 1 octet

RP-User Data M LV ? 234 octets

RP-DATA (Mobile Station to Network) is used to relay the TPDUs.



RP-Message Reference M V 1 octetRP-Originator Address M LV 1 octet

RP-Destination Address M LV 1-12 octets

RP-User Data M LV ? 234 octets

RP-SMMA is sent by the mobile station to relay a notification to the network that

the mobile has memory available to receive one or more short messages.




RP-ACK is sent between the MSC and the mobile station in both directions and

used to relay the acknowledgement of a RP-DATA or RP-SMMA message

reception.






K1205 MAP

Tektronix8-65

RP-ERROR is sent between the MSC and the mobile station in both directions

and used to relay an error cause from an erroneous short message or notification

transfer attempt.




RP-Cause M LV 2-3 octets

RP-User Data O TLV ? 240 octets

8.11.2.2 SMS-RP parameters

Message type indicator (MIT)

The message type indicator, MTI, is a 3-bit field, located in the first octet of all

RP-messages.

Bit value Direction RP-Message

Bits 3 2 1

0 0 0 ms -> n RP-DATA

0 0 0 n -> ms Reserved0 0 1 ms -> n Reserved

0 0 1 n -> ms RP-DATA

0 1 0 ms -> n RP-ACK

0 1 0 n -> ms Reserved

0 1 1 ms -> n Reserved0 1 1 n -> ms RP-ACK

1 0 0 ms -> n RP-ERROR


1 0 1 ms -> n Reserved

1 0 1 n -> ms RP-ERROR1 1 0 ms -> n RP-SMMA


1 1 1 ms -> n Reserved


Message reference

The message reference field contains a sequence number in the range 0 through

255, and is used to link an RP-ACK message or RP-ERROR message to the

associated (preceding) RP-DATA or RP-SMMA message transfer attempt.



MAP K1205

Tektronix8-66

Originator address element

In the case of mobile terminating transfer this element contains the originating

Service Centre address.

The RP-Originator Address is a type 4 information element. In the network to

mobile station direction the minimum value of the length octet is 2 and the

maximum value is 11. In the mobile station to network direction the value of the

length octet of the element is set to 0.

8 7 6 5 4 3 2 1

RP-Originator Address number IEI octet 1

Length of RP- Originator Address contents octet 2

1 ext type of number Numbering plan identification octet 3

Number digit 2 Number digit 1 octet 4


::

If the RP-Originator Address contains an odd number of digits, bits 5 to 8 of the

last octet shall be filled

Destination address element

In the case of mobile originating transfer, this element contains the destination

Service Centre address.

The RP-Destination Address is a type 4 information element. In the mobilestation to network direction the minimum value of the length octet is 2 and the

maximum value is 11. In the network to mobile station direction, the value of the

length octet of the element is set to 0.

8 7 6 5 4 3 2 1

RP-Destination Address number IEI octet 1

Length of RP-Destination Address contents octet 2

1 ext type of number Numbering plan identification octet 3



:

:

If the RP-Destination Address contains an odd number of digits, bits 5 to 8 of thelast octet shall be filled



K1205 MAP

Tektronix8-67

RP-User data element

The RP-User data field contains the TPDU and is mandatory in a RP-DATA

message. RP-User data is also optionally carried in an RP-Error message. Theelement has a variable length, up to 239 octets, the first octet sent being a length

indicator.

RP-User data in an RP-Error message is conveyed as diagnostic information

within the 'SM-DeliveryFailureCause' response to a MAP Forward-Short-Message procedure. The diagnostic information may be sent in both directions,

and shall always be forwarded by the MSC if it is received.

8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 1 1 octet

RP-User Data IEI


TPDU ? octetMaximum length 233 octets

RP-Cause element

This element is a variable length element always included in the RP-ERROR

message, conveying a negative result of a RP -DATA message transfer attempt

or RP-SMMA notification attempt. The element contains a cause value andoptionally a diagnostic field giving further details of the error cause.

8 7 6 5 4 3 2 1

0 1 0 0 0 0 1 0 1 octet

RP-User Data IE


0 ext Cause value 1 octet

Diagnostic field 1 octet



MAP K1205

Tektronix8-68

Error causes:

Mobile originating SM-transfer


Bits 7 6 5 4 3 2 1 #

0 0 0 0 0 0 1 1 Unassigned (unallocated) number

0 0 0 1 0 0 0 8 Operator determined barring0 0 0 1 0 1 0 10 Call barred

0 0 0 1 0 1 1 11 Reserved

0 0 1 0 1 0 1 21 Short message transfer rejected

0 0 1 1 0 1 1 27 Destination out of order

0 0 1 1 1 0 0 28 Unidentified subscriber0 0 1 1 1 0 1 29 Facility rejected

0 0 1 1 1 1 0 30 Unknown subscriber

0 1 0 0 1 1 0 38 Network out of order

0 1 0 1 0 0 1 41 Temporary failure0 1 0 1 0 1 0 42 Congestion0 1 0 1 1 1 1 47 Resources unavailable, unspecified

0 1 1 0 0 1 0 50 Requested facility not subscribed

1 0 0 0 1 0 1 69 Requested facility not implemented

1 0 1 0 0 0 1 81 Invalid short message transfer

reference value



implemented

1 1 0 0 0 1 0 98 Message not compatible with shortmessage protocolstate

1 1 0 0 0 1 1 99 Information element non-existent or

not implemented


1 1 1 1 1 1 1 127 Interworking, unspecified

All other cause values shall be treated as cause number 41, "Temporary Failure"



K1205 MAP

Tektronix8-69

Mobile terminating SM-transfer


Bits 7 6 5 4 3 2 1 #

0 0 1 0 1 1 0 22 Memory capacity exceeded1 0 1 0 0 0 1 81 Invalid short message transfer

reference value



implemented

1 1 0 0 0 1 0 98 Message not compatible with short

message protocol state1 1 0 0 0 1 1 99 Information element non-existent or

not implemented


All other cause values shall be treated as cause number 111, "Protocol error,

unspecified"

Memory available notification

Cause value Cause nr. Cause type/Cause

Bits 7 6 5 4 3 2 1 #

0 0 1 1 1 1 0 30 P/Unknown Subscriber

0 1 0 0 1 1 0 38 T/Network out of order0 1 0 1 0 0 1 41 T/Temporary failure0 1 0 1 0 1 0 42 T/Congestion

0 1 0 1 1 1 1 47 T/Resources unavailable, unspecified

1 0 0 0 1 0 1 69 P/Requested facility not implemented

1 0 1 1 1 1 1 95 P/Semantically incorrect message

1 1 0 0 0 0 0 96 P/Invalid mandatory information1 1 0 0 0 0 1 97 P/Message type non-existent or not

implemented

1 1 0 0 0 1 0 98 P/Message not compatible with short

message protocol state

1 1 0 0 0 1 1 99 P/Information element non-existent ornot implemented

1 1 0 1 1 1 1 111 P/Protocol error, unspecified

1 1 1 1 1 1 1 127 P/Interworking, unspecified

All other cause values are treated as cause number 41, "Temporary failure"

Each cause is classified as 'Temporary' or 'Permanent', as indicated by T and P

respectively in the cause type/cause column.



MAP K1205

Tektronix8-70

8.12 Exercise


Exercise 1/2

Select protocol stack: c:\k1103\awf\gsm2\gsmp2.txt

Use the Trigger to catch a transaction between a VLR ( SPC: 02-7-00-0 )

and a HLR.

The transaction is an Update Location procedure performed by the VLR,

serving a Mobile Subscriber with a MS-ISDN: 491718700691.

Mark the first triggerable message.

Mark the last message.

Record this transaction in a file: trigmap.rec

Select in playback the recording file: map.rec

Run playback with approx. 1000 frame / minute.


Exercise 2/2

The questions are:

IMSI of that MS?

In which MSC/VLR location area is the MS registered?

What is the address ( Global Title ) of the serving HLR?



K1205 MAP

Tektronix8-71

8.12.1 Solution

1.

Load protocol stack:Select in the main menu the menu icon Configuration.

Select Editor for protocol stack .

Select File.

Select Load protocol stack .

Select subdirectory gsm2 and within select gsmp2.txt.

Terminate the Editor for protocol stack answering the quetion about

saving the modifications with NO.

2.

Set the Trigger:

Select in the main menu the menu icon Trigger .

Select Trigger 1.

Activate the Initialize button to reset old settings.

Set the Source of the Criterion for Trigger 1 to All on.

Set the Trigger condition to Message and press the Define... button.

Within the Trigger 1; Trigger condition at message level selectParameter of message.

Now click once within the User Part menu on the MAP protocol.

Within the Message types menu click on the CON message.

Note: Within the complete Update Location procedure the MS-ISDN number

is located in the first TCAP-Continue message having the operation code set

to Insert Subscriber Data.

Press the Define parameters button. The window Parameters of the message

MAP | CON will appear.

In the scroll-box of Parameter select the entry for MS ISDN Address Signals

of the parameter MS Isdn Address Number ie. select entry 46.4.

Place the cursor within the text-box of Contents of parameter and enter the

MS-ISDN number given in the exercise.

Activate the Select parameter button. In the Selected parameters text-field theentry: 46.4 MS ISDN Address Signals.

Press the OK button to leave the parameter menu.



MAP K1205

Tektronix8-72

Now click once within theUser Part menu on the SCCP protocol.

Enter in the text-field of DPC the signalling point code of the VLR given in the

exercise.

Disable the x-field of Back-Dir. As well function.

Press the OK button to leave the Trigger selection menu.Press the OK button to leave the Trigger menu.

Select in the main menu the menu icon Trigger .

Select Trigger 2 .

Activate the Initialize button to reset old settings.

Set the Source of the Criterion for Trigger 2 to All on .

Set the Trigger condition to Message and press the Define... button.

Within the Trigger 2; Trigger conditiopn at message level select

Message type.

Now click once within theUser Part menu on the MAP protocol.

Within the Message types menu double-click on the END message ie. the listwill indicate END On.

Press the OK button to leave theTrigger selection menu.

Press the OK button to leave theTrigger menu.

3.

Set the Trigger action

Select in the main menu the menu icon Trigger and within select Trigger

Actions... . There is also the possibility to double-click on the Trigger symbol

on the main screen.

Define the Trigger action 1 by selecting the radio-button for that action.

Turn its state to On by selecting the radio-button.

To make the link to the special Trigger criterium select in the Trigger field

Trigger 1 ie. wait for CON with MS-ISDN number.To start the recording with this event activate the x-field of

Start of recording, prolog in s where the prolog should be 1 second.

The prolog is necessary because the transaction BEGIN message will be

received before the Continue message the Trigger is waiting for.

To mark the event activate the x-field of Mark Event .

Select the Enable/Disable trigger... button.

Activate the Enable Action 2 field and also the Disable Action 1 fieldie. set the Trigger 2 state to on and the Trigger action 1 state to off.

Press the OK button to leave this window.



K1205 MAP

Tektronix8-73

Select the Take Connection ID... button.

Activate the Trigger 2 field and the Disk recording filter field

ie. pass the connection id, which is for MAP the TCAP transaction ids to

Trigger 2 and to the Disk recording filter.


Define the Trigger action 2 by selecting the radio-button for that action.

If the Confirm changes function is active answer the question to Take alteredvalues ? with Yes.

Turn its state to Off by selecting the radio-button.

To make the link to the special Trigger criterium select in the Trigger field

Trigger 2 ie. wait for END with the same transaction id as the CON.

To stop the recording with this event activate the x-field ofStop of recording, epilog in s where the epilog should also be zero.

To mark the event activate the x-field of Mark Event .

Select theEnable/Disable trigger...

button. Activate the Disable Action 2 field ie. set the Trigger 2 state to off.


Press the OK button to leave the Definition of Trigger Actions window.

On the main screen the Trigger symbol will be active now.

4.

Open/Create recording file:

Select in the main menu the menu icon Recording and within select Open

recording file... .

Within the text-field of Filename enter the name of the new recording File

given in the exercise ( trigmap.rec ).

Press the Open button.

If the filename already exsist answer the question window by pressing the

Overwrite button.

The System Parameter for Recording file window will appear.

Reserve 20 Kbyte for the new recording file by entering this value in the

Memory to be reserved field.

The Recording mode has to be set to Linear .

Press the Open file button to activate the settings and to leave this window.

On the main screen the recording filename will be displayed in the box.

Note : the function is still not active. The Trigger action will activate the

recording.



MAP K1205

Tektronix8-74

5.

Start the playback:

Select in the main menu the menu icon Recording and within select

Playback... .

Select the Filename given in the exercise ( map.rec ).Press the Open button.

The Set Playback Speed window will appear. Set the value to 1000.

Press the Start playback button. The window will be closed.

6.

Analyse contents:

After approx. 10 seconds the transaction has been recorded.

The inactive Trigger symbol and the size of the recording file will indicate the

successful call trace.Select in the main menu the menu icon Recording and within select

Stop playback .

Select in the main menu the menu icon Recording and within select

Close recording file.

Open up the new recording trigmap.rec in the offline monitor.

7.

Zoom the transaction:

Because of the fact that it was necessary to use a prolog when recordingthere are much more messages within this File than messages belonging just

to the wanted transaction.Move the cursor to the bottom of the recording.

The Trigger events ie. CON and END message will be highlighted.

Place the cursor on the marked CON message and press the ZOOM key.

The bottom line will indicate the active zoom function.

Now there will be only these messages ( 4 messages ) displayed whichbelongs to the transaction.

Change the display format of level 4 and set it to medium 2 mode.



K1205 MAP

8.

Answers:

The IMSI is located in the TCAP BEGIN message as a parameter of the

Update Location operation. The IMSI or the TMSI is the parameter coming

from the MS to identify itself and which is used by the VLR to identify the HLRand the mobile subscriber.

IMSI: 262018700001756

The location area is also included in that message.

MSC/VLR Address Signals: 491710200000

The HLR address is the result of the Update Location procedure and is found

as a parameter in the TCAP END message indicating the component Return

Result Last. This address would be used as Global Title when international

Roaming would be performed.

HLR address: 491718500000

Date post:	04-Jun-2018
Category:	Documents
Upload:	nithishsingh8946
View:	238 times
Download:	1 times

MAP Protocol.pdf

Documents