7 General on MAP services

09.023GPPMobile Application Part (MAP) specificationTS

7.1 Terminology and definitions

The term service is used in clauses 7 to 12 as defined in CCITT Recommendation X.200. The service definition conventions of CCITT Recommendation X.210 are also used.

7.2 Modelling principles

MAP provides its users with a specified set of services and can be viewed by its users as a "black box" or abstract machine representing the MAP service-provider. The service interface can then be depicted as shown in figure 7.2/1.

Figure 7.2/1: Modelling principles

The MAP service-users interact with the MAP service-provider by issuing or receiving MAP service-primitives at the service interface.

A MAP service-user may receive services from several instances of the MAP service-provider at the same time. In such cases the overall procedure is synchronised by the service-user.

The MAP service-primitives are named using the following notation:

MAP-ServicePrimitiveName type

where type can be any of: request (req), indication (ind), response (rsp) or confirm (cnf) (In the user arrow diagrams type is not indicated in the case of req/ind and indicated as "ack" in the case of rsp/cnf).

The services are further classified as unconfirmed-service, confirmed-service and provider-initiated-service where the first two categories refer to whether or not the service is confirmed by the service-provider. The confirmation may or may not correspond to a response provided by the other service-user.

MAP services are also classified as common MAP services which are available to all MAP service-users, and MAP service-user specific services which are services available to one or several, but not all, MAP service-users.

A MAP dialogue is defined as an exchange of information between two MAP users in order to perform a common task. A MAP dialogue will consist of one or several MAP services.

7.3 Common MAP services

All MAP service-users require access to services for performing basic application layer functions:

– for establishing and clearing MAP dialogues between peer MAP service-users;

– for accessing functions supported by layers below the applications layer;

– for reporting abnormal situations;

– for handling of different MAP versions;

– for testing whether or not a persistent MAP dialogue is still active at each side.

For these purposes the following common services are defined:

– MAP-OPEN service;

– MAP-CLOSE service;

– MAP-DELIMITER service;

– MAP-U-ABORT service;

– MAP-P-ABORT service;

– MAP-NOTICE service.

In defining the service-primitives the following convention is used for categorising parameters:

M the inclusion of the parameter is mandatory. The M category can be used for any primitive type and specifies that the corresponding parameter must be present in the indicated primitive type;

O the inclusion of the parameter is a service-provider option. The O category can be used in indication and confirm type primitives and is used for parameters that may optionally be included by the service-provider;

U the inclusion of the parameter is a service-user option. The U category can be used in request and response type primitives. The inclusion of the corresponding parameter is the choice of the service-user;

C the inclusion of the parameter is conditional. The C category can be used for the following purposes:

– to indicate that if the parameter is received from another entity it must be included for the service being considered;

– to indicate that the service user must decide whether to include the parameter, based on the context on which the service is used;

– to indicate that one of a number of mutually exclusive parameters must be included (e.g. parameters indicating a positive result versus parameters indicating a negative result);

– to indicate that a service user optional parameter (marked "U") or a conditional parameter (marked "C") presented by the service user in a request or response type primitive is to be presented to the service user in the corresponding indication or confirm type primitive;

(=) when appended to one of the above, this symbol means that the parameter takes the same value as the parameter appearing immediately to its left;

blank the parameter is not present.

A primitive type may also be without parameters, i.e. no parameter is required with the primitive type; in this case the corresponding column of the table is empty.

7.3.1 MAP-OPEN service

This service is used for establishing a MAP dialogue between two MAP service-users. The service is a confirmed service with service primitives as shown in table 7.3/1.

Table 7.3/1: Service-primitives for the MAP-OPEN service

Parameters

Request

Indication

Response

Confirm

Application context name

M

M(=)

U

C(=)

Destination address

M

M(=)

Destination reference

U

C(=)

Originating address

U

O

Originating reference

U

C(=)

Specific information

U

C(=)

U

C(=)

Responding address

U

C(=)

Result

M

M(=)

Refuse-reason

C

C(=)

Provider error

O

Application context name:

This parameter identifies the type of application context being established. If the dialogue is accepted the received application context name shall be echoed. In case of refusal of dialogue this parameter shall indicate the highest version supported.

Destination address:

A valid SCCP address identifying the destination peer entity (see also clause 6). As an implementation option, this parameter may also, in the indication, be implicitly associated with the service access point at which the primitive is issued.

Destination-reference:

This parameter is a reference which refines the identification of the called process. It may be identical to Destination address but its value is to be carried at MAP level. Table 7.3/2 describes the MAP services using this parameter. Only these services are allowed to use it.

Table 7.3/2: Use of the destination reference

MAP service

Reference type

Use of the parameter

MAP-REGISTER-SS

IMSI

Subscriber identity

MAP-ERASE-SS

IMSI

Subscriber identity

MAP-ACTIVATE-SS

IMSI

Subscriber identity

MAP-DEACTIVATE-SS

IMSI

Subscriber identity

MAP-INTERROGATE-SS

IMSI

Subscriber identity

MAP-REGISTER-PASSWORD

IMSI

Subscriber identity

MAP-PROCESS-UNSTRUCTURED-
SS-REQUEST

IMSI

Subscriber identity

MAP-UNSTRUCTURED-
SS-REQUEST

IMSI

Subscriber identity

MAP-UNSTRUCTURED-SS-NOTIFY

IMSI

Subscriber identity

MAP-FORWARD-SHORT-MESSAGE

IMSI (note)

Subscriber identity

MAP-REGISTER-CC-ENTRY

IMSI

Subscriber identity

MAP-ERASE-CC-ENTRY

IMSI

Subscriber identity

NOTE: Only when the IMSI and the LMSI are received together from the HLR in the mobile terminated short message transfer.

Originating address:

A valid SCCP address identifying the requestor of a MAP dialogue (see also clause 6). As an implementation option, this parameter may also, in the request, be implicitly associated with the service access point at which the primitive is issued.

Originating-reference:

This parameter is a reference which refines the identification of the calling process. It may be identical to the Originating address but its value is to be carried at MAP level. Table 7.3/3 describes the MAP services using the parameter. Only these services are allowed to use it. Processing of the Originating-reference shall be performed according to the supplementary service descriptions and other service descriptions, e.g. operator determined barring.

Table 7.3/3: Use of the originating reference

MAP service

Reference type

Use of the parameter

MAP-REGISTER-SS

ISDN-Address-String

Originated entity address

MAP-ERASE-SS

ISDN-Address-String

Originated entity address

MAP-ACTIVATE-SS

ISDN-Address-String

Originated entity address

MAP-DEACTIVATE-SS

ISDN-Address-String

Originated entity address

MAP-INTERROGATE-SS

ISDN-Address-String

Originated entity address

MAP-REGISTER-PASSWORD

ISDN-Address-String

Originated entity address

MAP-PROCESS-UNSTRUCTURED-
SS-REQUEST

ISDN-Address-String

Originated entity address

MAP-REGISTER-CC-ENTRY

ISDN-Address-String

Originated entity address

MAP-ERASE-CC-ENTRY

ISDN-Address-String

Originated entity address

Specific information:

This parameter may be used for passing any user specific information. Establishment and processing of the Specific information is not specified by GSM and shall be performed according to operator specific requirements.

Responding address:

An address identifying the responding entity. The responding address is included if required by the context (e.g. if it is different from the destination address).

Result:

This parameter indicates whether the dialogue is accepted by the peer.

Refuse reason:

This parameter is only present if the Result parameter indicates that the dialogue is refused. It takes one of the following values:

– Application-context-not-supported;

– Invalid-destination-reference;

– Invalid-originating-reference;

– No-reason-given;

– Remote node not reachable;

– Potential version incompatibility.

7.3.2 MAP-CLOSE service

This service is used for releasing a previously established MAP dialogue. The service may be invoked by either MAP service-user depending on rules defined within the service-user. The service is an unconfirmed service with parameters as shown in table 7.3/4.

Table 7.3/4: Service-primitives for the MAP-CLOSE service

Parameters

Request

Indication

Release method

M

Specific Information

U

C(=)

Release method:

This parameter can take the following two values:

– normal release; in this case the primitive is mapped onto the protocol and sent to the peer;

– prearranged end; in this case the primitive is not mapped onto the protocol. Prearranged end is managed independently by the two users, i.e. only the request type primitive is required in this case.

Specific information:

This parameter may be used for passing any user specific information. Establishment and processing of the Specific information is not specified by GSM GSM and shall be performed according to operator specific requirements.

7.3.3 MAP-DELIMITER service

This service is used to explicitly request the transfer of the MAP protocol data units to the peer entities.

See also subclause 7.4 and 7.5 for the detailed use of the MAP-DELIMITER service.

The service is an unconfirmed service with service-primitives as shown in table 7.3/5.

Table 7.3/5: Service-primitives for the MAP-DELIMITER service

Parameters

Request

Indication

7.3.4 MAP-U-ABORT service

This service enables the service-user to request the MAP dialogue to be aborted. The service is an unconfirmed service with service-primitives as shown in table 7.3/6.

Table 7.3/6: Service-primitives for the MAP-U-ABORT service

Parameters

Request

Indication

User reason

M

M(=)

Diagnostic information

U

C(=)

Specific information

U

C(=)

User reason:

This parameter can take the following values:

– resource limitation (congestion);

the requested user resource is unavailable due to congestion;

– resource unavailable;

the requested user resource is unavailable for reasons other than congestion;

– application procedure cancellation;

the procedure is cancelled for reason detailed in the diagnostic information parameter;

– procedure error;

processing of the procedure is terminated for procedural reasons.

Diagnostic information:

This parameter may be used to give additional information for some of the values of the user-reason parameter:

Table 7.3/7: User reason and diagnostic information

User reason

Diagnostic information

Resource limitation (congestion)

Resource unavailable

Short term/long term problem

Application procedure cancellation

Handover cancellation/
Radio Channel release/
Network path release/
Call release/
Associated procedure failure/
Tandem dialogue released/
Remote operations failure

Procedure error

Specific information:

This parameter may be used for passing any user specific information. Establishment and processing of the Specific information is not specified by GSM and shall be performed according to operator specific requirements.

7.3.5 MAP-P-ABORT service

This service enables the MAP service-provider to abort a MAP dialogue. The service is a provider-initiated service with service-primitive as shown in table 7.3/8.

Table 7.3/8: Service-primitive for the MAP-P-ABORT service

Parameters

Indication

Provider reason

M

Source

M

Provider reason:

This parameter indicates the reason for aborting the MAP dialogue:

– provider malfunction;

– supporting dialogue/transaction released;

– resource limitation;

– maintenance activity;

– version incompatibility;

– abnormal MAP dialogue.

Source:

This parameter indicates the source of the abort. For Transaction Capabilities (TC) applications the parameter may take the following values:

– MAP problem;

– TC problem;

– network service problem.

Table 7.3/9: Values of provider reason and source parameters and examples of corresponding events

Provider reason

Source

Corresponding event

Provider

MAP

Malfunction at MAP level at peer entity

malfunction

TC

"Unrecognised message type" or

"Badly formatted transaction portion" or

"Incorrect transaction portion" received in TC-P-ABORT

"Abnormal dialogue"

Network service

Malfunction at network service level at peer entity

Supporting dialogue/ transaction released

TC

"Unrecognised transaction ID" received in TC-ABORT

Resource

MAP

Congestion towards MAP peer service-user

limitation

TC

"Resource limitation" received in TC-P-ABORT

Maintenance

MAP

Maintenance at MAP peer service-user

activity

Network service

Maintenance at network peer service level

Abnormal MAP dialogue

MAP

MAP dialogue is not in accordance with specified application context

Version incompatibility

TC

A Provider Abort indicating "No common dialogue portion" is received in the dialogue initiated state

7.3.6 MAP-NOTICE service

This service is used to notify the MAP service-user about protocol problems related to a MAP dialogue not affecting the state of the protocol machines.

The service is a provider-initiated service with service-primitive as shown in table 7.3/10.

Table 7.3/10: Service-primitive for the MAP-NOTICE service

Parameters

Indication

Problem diagnostic

M

Problem diagnostic:

This parameter can take one of the following values:

– abnormal event detected by the peer;

– response rejected by the peer;

– abnormal event received from the peer

– message cannot be delivered to the peer.

7.4 Sequencing of services

The sequencing of services is shown in figure 7.4/1 and is as follows:

Opening:

The MAP-OPEN service is invoked before any user specific service-primitive is accepted. The sequence may contain none, one or several user specific service-primitives. If no user specific service-primitive is contained between the MAP-OPEN and the MAP-DELIMITER primitives, then this will correspond to sending an empty Begin message in TC. If more than one user specific service-primitive is included, all are to be sent in the same Begin message. The sequence ends with a MAP-DELIMITER primitive.

Continuing:

This sequence may not be present in some MAP dialogues. If it is present, it ends with a MAP-DELIMITER primitive. If more than one user specific service-primitive is included, all are to be included in the same Continue message.

Closing:

The sequence can only appear after an opening sequence or a continuing sequence. The sequence may contain none, one or several user specific service-primitives if the MAP-CLOSE primitive specifies normal release. If no user specific service-primitive is included, then this will correspond to sending an empty End message in TC. If more than one user specific service-primitive is included, all are to be sent in the same End message. If prearranged end is specified, the sequence cannot contain any user specific service-primitive. The MAP-CLOSE primitive must be sent after all user specific service-primitives have been delivered to the MAP service-provider.

Aborting:

A MAP service-user can issue a MAP-U-ABORT primitive at any time after the MAP dialogue has been opened or as a response to an attempt to open a MAP dialogue.

The MAP service-provider may issue at any time a MAP-P-ABORT primitive towards a MAP service-user for which a MAP dialogue exists.

MAP-U-ABORT primitives and MAP-P-ABORT primitives terminate the MAP dialogue.

Figure 7.4/1: Sequencing of services

If the reason "resource unavailable (short term problem)" is indicated in the MAP-U-ABORT indication primitive, the MAP service-user may decide to attempt a new MAP dialogue establishment immediately.

Sequencing of user specific service-primitives is done by the MAP service-user and based on rules applicable for each MAP service-user instance.

A MAP-NOTICE indication primitive may be received at any time during the active period of a MAP dialogue.

7.5 General rules for mapping of services onto TC

7.5.1 Mapping of common services

Table 7.5/1 gives an overview of the mapping rules for mapping of common services onto TC-services. Table 7.5/2 gives the mapping rules for mapping of TC-services onto common services.

Protocol machine description is given in clauses 14 to 17.

Table 7.5/1: Mapping of common services on to TC services

MAP service-primitive

TC service-primitive

MAP-OPEN request
(+ any user specific service primitives)
+ MAP-DELIMITER request

TC-BEGIN request
(+ component handling primitives)

MAP-OPEN response
(+ any user specific service primitives)
+ MAP-DELIMITER request

TC-CONTINUE request (note)
(+ component handling primitives)

(any user specific service primitives)
+ MAP-DELIMITER request

TC-CONTINUE request
(+ component handling primitives)

(any user specific service primitives)
+ MAP-CLOSE request

TC-END request
(+ component handling primitives)

MAP-U-ABORT request

TC-U-ABORT request

NOTE: or TC-END if the MAP-CLOSE request has been received before the MAP-DELIMITER request.

Table 7.5/2: Mapping of TC services on to common service

TC service-primitive

MAP service-primitive

TC-BEGIN indication
(+ component handling primitives)

MAP-OPEN indication
(+ user specific service primitives)
+ MAP-DELIMITER indication (note 1)

TC-CONTINUE indication
(+ component handling primitives)

First time:
MAP-OPEN confirm
(+ user specific service primitives)
+ MAP-DELIMITER indication (note 1)

Subsequent times:
(user specific service primitives)
+ MAP-DELIMITER indication (note 1)

TC-END indication
(+ component handling primitives)

MAP-OPEN confirm (note 6)
(user specific service primitives)
+ MAP-CLOSE indication

TC-U-ABORT indication

MAP-U-ABORT indication or
MAP-P-ABORT indication (note 2)
MAP-OPEN confirmation (note 3)

TC-P-ABORT indication

MAP-P-ABORT indication (note 4)
MAP-OPEN confirmation (note 5)

NOTE 1: It may not be necessary to present this primitive to the user for MAP version 2 applications.

NOTE 2: The mapping depends on whether the TC-U-ABORT indication primitive contains a MAP-abort-PDU from the remote MAP service-provider or a MAP-user-abort-PDU from the remote MAP service-user.

NOTE 3: Only if the opening sequence is pending and if the "Abort Reason" in the TC-U-ABORT indication is set to "Application Context Not Supported".

NOTE 4: If the "Abort Reason" in the TC-P-ABORT indication is set to a value different from "Incorrect Transaction Portion".

NOTE 5: Only if the opening sequence is pending and if the "Abort Reason" in the TC-P-ABORT indication is set to "Incorrect Transaction Portion".

NOTE 6: Only if opening sequence is pending.

7.5.2 Mapping of user specific services

Table 7.5/3 gives the general mapping rules which apply to mapping of MAP user specific services onto TC services and table 7.5/4 gives the similar rules for mapping of TC services onto MAP user specific services. Detailed mapping is given in clauses 14 to 17.

Table 7.5/3: Mapping of MAP user specific services onto TC services

MAP service-primitive

TC-service-primitive

MAP-xx request

TC-INVOKE request

MAP-xx response

TC-RESULT-L request

(note 1)

TC-U-ERROR request

TC-U-REJECT request

TC-INVOKE request (note 2)

Table 7.5/4: Mapping of TC services onto MAP user specific services

TC-service-primitive

MAP service-primitive

TC-INVOKE indication

MAP-xx indication

TC-RESULT-L indication (note 4)

MAP-xx confirm

TC-U-ERROR indication

TC-INVOKE indication (note 2)

TC-L-CANCEL indication

TC-U-REJECT indication

MAP-xx confirm or

TC-L-REJECT indication

MAP-NOTICE indication (note 3)

TC-R-REJECT indication

Notes to tables 7.5/3 and 7.5/4:

NOTE 1: The mapping is determined by parameters contained in the MAP-xx response primitive.

NOTE 2: This applies only to TC class 4 operations where the operation is used to pass a result of another class 2 or class 4 operation.

NOTE 3: The detailed mapping rules are given in clause 16.

NOTE 4: If RESULT-NL components are present they are mapped on to the same MAP-xx confirm.

7.6 Definition of parameters

Following is an alphabetic list of parameters used in the common MAP-services in subclause 7.3:

Application context name

7.3.1

Refuse reason

7.3.1

Destination address

7.3.1

Release method

7.3.2

Destination reference

7.3.1

Responding address

7.3.1

Diagnostic information

7.3.4

Result

7.3.1

Originating address

7.3.1

Source

7.3.5

Originating reference

7.3.1

Specific information

7.3.1/7.3.2/7.3.4

Problem diagnostic

7.3.6

User reason

7.3.4

Provider reason

7.3.5

Following is an alphabetic list of parameters contained in this clause:

Absent Subscriber Diagnostic SM

7.6.8.9

Invoke Id

7.6.1.1

Access connection status

7.6.9.3

ISDN Bearer Capability

7.6.3.41

Access signalling information

7.6.9.5

Kc

7.6.7.4

Additional Absent Subscriber Diagnostic SM

7.6.8.12

Linked Id

7.6.1.2

Additional number

7.6.2.46

LMSI

7.6.2.16

Additional SM Delivery Outcome

7.6.8.11

Location Information

7.6.2.30

Alert Reason

7.6.8.8

Location update type

7.6.9.6

Alert Reason Indicator

7.6.8.10

Lower Layer Compatibility

7.6.3.42

Alerting Pattern

7.6.3.44

Mobile Not Reachable Reason

7.6.3.51

All GPRS Data

7.6.3.53

More Messages To Send

7.6.8.7

APN

7.6.2.42

MS ISDN

7.6.2.17

Authentication set list

7.6.7.1

MSC number

7.6.2.11

B-subscriber Address

7.6.2.36

MSIsdn-Alert

7.6.2.29

B subscriber Number

7.6.2.48

MWD status

7.6.8.3

B subscriber subaddress

7.6.2.49

Network Access Mode

7.6.3.50

Basic Service Group

7.6.4.40

Network node number

7.6.2.43

Bearer service

7.6.4.38

Network resources

7.6.10.1

BSS-apdu

7.6.9.1

Network signal information

7.6.9.8

Call barring feature

7.6.4.19

New password

7.6.4.20

Call barring information

7.6.4.18

No reply condition timer

7.6.4.7

Call Direction

7.6.5.8

North American Equal Access

preferred Carrier Id

7.6.2.34

Call Info

7.6.9.9

ODB General Data

7.6.3.9

Call reference

7.6.5.1

ODB HPLMN Specific Data

7.6.3.10

Called number

7.6.2.24

OMC Id

7.6.2.18

Calling number

7.6.2.25

Originally dialled number

7.6.2.26

CAMEL Subscription Info Withdraw

7.6.3.38

Cancellation Type

7.6.3.52

Originating entity number

7.6.2.10

Category

7.6.3.1

Override Category

7.6.4.4

CCBS Feature

7.6.5.8

P-TMSI

7.6.2.47

Channel Type

7.6.5.9

PDP-Address

7.6.2.45

Chosen Channel

7.6.5.10

PDP-Context identifier

7.6.3.55

Ciphering mode

7.6.7.7

PDP-Type

7.6.2.44

Cksn

7.6.7.5

Previous location area Id

7.6.2.4

CLI Restriction

7.6.4.5

Protocol Id

7.6.9.7

CM service type

7.6.9.2

Provider error

7.6.1.3

Complete Data List Included

7.6.3.54

CUG feature

7.6.3.26

QoS-Subscribed

7.6.3.47

CUG index

7.6.3.25

Rand

7.6.7.2

CUG info

7.6.3.22

Regional Subscription Data

7.6.3.11

CUG interlock

7.6.3.24

Regional Subscription Response

7.6.3.12

CUG Outgoing Access indicator

7.6.3.8

Requested Info

7.6.3.31

CUG subscription

7.6.3.23

Roaming number

7.6.2.19

CUG Subscription Flag

7.6.3.37

Roaming Restricted In SGSN Due To Unsupported Feature

7.6.3.49

Current location area Id

7.6.2.6

Roaming Restriction Due To Unsupported Feature

7.6.3.13

Current password

7.6.4.21

Service centre address

7.6.2.27

eMLPP Information

7.6.4.41

Serving Cell Id

7.6.2.37

Equipment status

7.6.3.2

SGSN address

7.6.2.39

Extensible Basic Service Group

7.6.3.5

SGSN number

7.6.2.38

Extensible Bearer service

7.6.3.3

SIWF Number

7.6.2.35

Extensible Call barring feature

7.6.3.21

SM Delivery Outcome

7.6.8.6

Extensible Call barring information

7.6.3.20

SM-RP-DA

7.6.8.1

Extensible Forwarding feature

7.6.3.16

SM-RP-MTI

7.6.8.16

Extensible Forwarding info

7.6.3.15

SM-RP-OA

7.6.8.2

Extensible Forwarding Options

7.6.3.18

SM-RP-PRI

7.6.8.5

Extensible No reply condition timer

7.6.3.19

SM-RP-SMEA

7.6.8.17

Extensible SS-Data

7.6.3.29

SM-RP-UI

7.6.8.4

Extensible SS-Info

7.6.3.14

Sres

7.6.7.3

Extensible SS-Status

7.6.3.17

SS-Code

7.6.4.1

Extensible Teleservice

7.6.3.4

SS-Data

7.6.4.3

External Signal Information

7.6.9.4

SS-Event

7.6.4.42

Forwarded-to number

7.6.2.22

SS-Event-Data

7.6.4.43

Forwarded-to subaddress

7.6.2.23

SS-Info

7.6.4.24

Forwarding feature

7.6.4.16

SS-Status

7.6.4.2

Forwarding information

7.6.4.15

Stored location area Id

7.6.2.5

Forwarding Options

7.6.4.6

Subscriber State

7.6.3.30

GGSN address

7.6.2.40

Subscriber Status

7.6.3.7

GGSN number

7.6.2.41

Supported CAMEL Phases

7.6.3.36

GMSC CAMEL Subscription Info

7.6.3.34

Suppress T-CSI

7.6.3.33

GPRS Node Indicator

7.6.8.14

Suppression of Announcement

7.6.3.32

GPRS Subscription Data

7.6.3.46

Target cell Id

7.6.2.8

GPRS Subscription Data Withdraw

7.6.3.45

Target location area Id

7.6.2.7

GPRS Support Indicator

7.6.8.15

Target MSC number

7.6.2.12

Group Id

7.6.2.33

Teleservice

7.6.4.39

GSM bearer capability

7.6.3.6

TMSI

7.6.2.2

Guidance information

7.6.4.22

Trace reference

7.6.10.2

Handover number

7.6.2.21

Trace type

7.6.10.3

High Layer Compatibility

7.6.3.43

User error

7.6.1.4

HLR Id

7.6.2.15

USSD Data Coding Scheme

7.6.4.36

HLR number

7.6.2.13

USSD String

7.6.4.37

HO-Number Not Required

7.6.6.7

VBS Data

7.6.3.40

IMEI

7.6.2.3

VGCS Data

7.6.3.39

IMSI

7.6.2.1

VLR CAMEL Subscription Info

7.6.3.35

Inter CUG options

7.6.3.27

VLR number

7.6.2.14

Intra CUG restrictions

7.6.3.28

VPLMN address allowed

7.6.3.48

Zone Code

7.6.2.28

7.6.1 Common parameters

The following set of parameters are used in several MAP service-primitives:

7.6.1.1 Invoke Id

This parameter identifies corresponding service primitives. The parameter is supplied by the MAP service-user and must be unique over each service-user/service-provider interface.

7.6.1.2 Linked Id

This parameter us used for linked services and it takes the value of the invoke Id of the service linked to.

7.6.1.3 Provider error

This parameter is used to indicate a protocol related type of error:

– duplicated invoke Id;

– not supported service;

– mistyped parameter;

– resource limitation;

– initiating release, i.e. the peer has already initiated release of the dialogue and the service has to be released;

– unexpected response from the peer;

– service completion failure;

– no response from the peer;

– invalid response received.

7.6.1.4 User error

This parameter can take values as follows:

NOTE: The values are grouped in order to improve readability; the grouping has no other significance.

a) Generic error:

– system failure, i.e. a task cannot be performed because of a problem in another entity. The type of entity or network resource may be indicated by use of the network resource parameter;

– data missing, i.e. an optional parameter required by the context is missing;

– unexpected data value, i.e. the data type is formally correct but its value or presence is unexpected in the current context;

– resource limitation;

– initiating release, i.e. the receiving entity has started the release procedure;

– facility not supported, i.e. the requested facility is not supported by the PLMN;

– incompatible terminal, i.e. the requested facility is not supported by the terminal.

b) Identification or numbering problem:

– unknown subscriber, i.e. no such subscription exists;

– number changed, i.e. the subscription does not exist for that number any more;

– unknown MSC;

– unidentified subscriber, i.e. if the subscriber is not contained in the database and it has not or cannot be established whether or not a subscription exists;

– unallocated roaming number;

– unknown equipment;

– unknown location area.

c) Subscription problem:

– roaming not allowed, i.e. a location updating attempt is made in an area not covered by the subscription;

– illegal subscriber, i.e. illegality of the access has been established by use of authentication procedure;

– bearer service not provisioned;

– teleservice not provisioned;

– illegal equipment, i.e. the IMEI check procedure has shown that the IMEI is blacklisted or not whitelisted.

d) Handover problem:

– no handover number available;

– subsequent handover failure, i.e. handover to a third MSC failed for some reason.

e) Operation and maintenance problem:

– tracing buffer full, i.e. tracing cannot be performed because the tracing capacity is exceeded.

f) Call set-up problem:

– no roaming number available, i.e. a roaming number cannot be allocated because all available numbers are in use;

– absent subscriber, i.e. the subscriber has activated the detach service or the system detects the absence condition. This error may be qualified to indicate whether the subscriber was IMSI detached, in a restricted area or did not respond to paging;

– busy subscriber. This error may be qualified to indicate that the subscriber was busy due to CCBS and that CCBS is possible;

– no subscriber reply;

– forwarding violation, i.e. the call has already been forwarded the maximum number of times that is allowed;

– CUG reject, i.e. the call does not pass a CUG check; additional information may also be given in order to indicate rejection due to e.g. incoming call barred or non-CUG membership.

– call barred. Optionally, additional information may be included for indicating either that the call meets a barring condition set by the subscriber or that the call is barred for operator reasons. In case of barring of Mobil Terminating Short Message, the additional information may indicate a barring condition due to « unauthorised Message Originator».

– optimal routeing not allowed, i.e. the entity which sends the error does not support optimal routeing, or the HLR will not accept an optimal routeing interrogation from the GMSC, or the call cannot be optimally routed because it would contravene optimal routeing constraints.

– forwarding failed, i.e. the GMSC interrogated the HLR for forwarding information but the HLR returned an error.

g) Supplementary services problem:

– call barred;

– illegal SS operation;

– SS error status;

– SS not available;

– SS subscription violation;

– SS incompatibility;

– negative password check;

– password registration failure;

– Number of Password Attempts;

– USSD Busy;

– Unknown Alphabet.

– short term denial;

– long term denial.

For definition of these errors see GSM 04.80.

h) Short message problem:

– SM delivery failure with detailed reason as follows:

– memory capacity exceeded;

– MS protocol error;

– MS not equipped;

– unknown service centre (SC);

– SC congestion;

– invalid SME address;

– subscriber is not an SC subscriber;

– and possibly detailed diagnostic information, coded as specified in TS GSM 03.40, under SMS-SUBMIT-REPORT and SMS-DELIVERY-REPORT. If the SM entity which returns the SM Delivery Failure error includes detailed diagnostic information, it shall be forwarded in the MAP_MO_FORWARD_SHORT_MESSAGE and in the MAP_MT_FORWARD_SHORT_MESSAGE response.

– message waiting list full, i.e. no further SC address can be added to the message waiting list;

– Subscriber busy for MT SMS, i.e. the mobile terminated short message transfer cannot be completed because:

– another mobile terminated short message transfer is going on and the delivery node does not support message buffering; or

– another mobile terminated short message transfer is going on and it is not possible to buffer the message for later delivery; or

– the message was buffered but it is not possible to deliver the message before the expiry of the buffering time defined in GSM 03.40;

– Absent Subscriber SM, i.e. the mobile terminated short message transfer cannot be completed because the network cannot contact the subscriber. Diagnostic information regarding the reason for the subscriber’s absence may be included with this error.

7.6.2 Numbering and identification parameter

7.6.2.1 IMSI

This parameter is the International Mobile Subscriber Identity defined in GSM 03.03.

7.6.2.2 TMSI

This parameter is the Temporary Mobile Subscriber Identity defined in GSM 03.03.

7.6.2.3 IMEI

This parameter is the International Mobile Equipment Identity defined in GSM 03.03.

7.6.2.4 Previous location area Id

This parameter refers to the identity of the location area from which the subscriber has roamed.

7.6.2.5 Stored location area Id

This parameter refers to the location area where the subscriber is assumed to be located.

7.6.2.6 Current location area Id

This parameter is used to indicate the location area in which the subscriber is currently located.

7.6.2.7 Target location area Id

This parameter refers to the location area into which the subscriber intends to roam.

7.6.2.8 Target cell Id

This parameter refers to the identity of the cell to which a call has to be handed over.

7.6.2.9 Void

7.6.2.10 Originating entity number

This parameter refers to an application layer identification of a system component in terms of its associated ISDN number.

7.6.2.11 MSC number

This parameter refers to the ISDN number of an MSC.

7.6.2.12 Target MSC number

This parameter refers to the ISDN number of an MSC to which a call has to be handed over.

7.6.2.13 HLR number

This parameter refers to the ISDN number of an HLR.

7.6.2.14 VLR number

This parameter refers to the ISDN number of a VLR.

7.6.2.15 HLR Id

This parameter refers to the identity of an HLR derived from the IMSI defined in CCITT Recommendation E.212.

7.6.2.16 LMSI

This parameter refers to a local identity allocated by the VLR to a given subscriber for internal management of data in the VLR. LMSI shall not be sent to the SGSN.

7.6.2.17 MS ISDN

This parameter refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with CCITT Recommendation E.213.

7.6.2.18 OMC Id

This parameter refers to the identity of an operation and maintenance centre.

7.6.2.19 Roaming number

This parameter refers to the roaming number as defined in CCITT Recommendation E.213.

7.6.2.20 Void

7.6.2.21 Handover number

This parameter refers to the number used for routing a call between MSCs during handover.

7.6.2.22 Forwarded-to number

This parameter refers to the address to which a call is to be forwarded. This may include a subaddress. For subscribers having an originating CAMEL Phase 2 subscription this address need not be in non-E.164 international format.

7.6.2.23 Forwarded-to subaddress

This parameter refers to the sub-address attached to the address to which a call is to be forwarded.

7.6.2.24 Called number

This parameter refers to a called party number as defined in CCITT Recommendation Q.767.

7.6.2.25 Calling number

This parameter refers to a calling party number as defined in CCITT Recommendation Q.767.

7.6.2.26 Originally dialled number

This parameter refers to the number dialled by the calling party in order to reach a mobile subscriber.

7.6.2.27 Service centre address

This parameter represents the address of a Short Message Service Centre.

7.6.2.28 Zone Code

This parameter is used to define location areas into which the subscriber is allowed or not allowed to roam (regional subscription). With a complete list of Zone Codes the VLR or the SGSN is able to determine for all its location areas whether roaming is allowed or not.

7.6.2.29 MSIsdn-Alert

This parameter refers to the MSISDN stored in a Message Waiting Data File in the HLR. It is used to alert the Service Centre when the MS is again attainable.

7.6.2.30 Location Information

This parameter indicates the location of the served subscriber as defined in GSM 03.18.

7.6.2.31 GMSC Address

This parameter refers to the E.164 address of a GMSC.

7.6.2.32 VMSC Address

This parameter refers to the E.164 address of a VMSC.

7.6.2.33 Group Id

This parameter is used to describe groups a subscriber can be member of. A subscriber can partake in all group calls (VBS/VGCS) where he subscribed to the respective groups.

7.6.2.34 North American Equal Access preferred Carrier Id

This parameter refers to the carrier identity preferred by the subscriber for calls requiring routing via an interexchange carrier. This identity is used at:

– outgoing calls: when the subscriber does not specify at call setup a carrier identity;

– forwarded calls: when a call is forwarded by the subscriber;

– incoming calls: applicable to the roaming leg of the call.

7.6.2.35 SIWFS Number

This parameter refers to the number used for routing a call between the MSC and the SIWFS (used by ISUP).

7.6.2.36 B-subscriber address

This parameter refers to the address used by the SIWFS to route the outgoing call from the SIWFS to either the B-subscriber in case the non-loop method or back to the VMSC in case of the loop method.

7.6.2.37 Serving cell Id

This parameter indicates the cell currently being used by the served subscriber.

7.6.2.38 SGSN number

This parameter refers to the ISDN number of a SGSN.

7.6.2.39 SGSN address

This parameter refers to the IP-address of a SGSN. This parameter is defined in GSM 03.03.

7.6.2.40 GGSN address

This parameter refers to the IP-address of a GGSN. This parameter is defined in GSM 03.03.

7.6.2.41 GGSN number

This parameter refers to the ISDN number of a GGSN or the ISDN number of the protocol-converter if a protocol-converting GSN is used between the GGSN and the HLR..

7.6.2.42 APN

This parameter refers to the DNS name of a GGSN. This parameter is defined in GSM 03.60.

7.6.2.43 Network Node number

This parameter refers either to the ISDN number of SGSN or to the ISDN number of MSC.

7.6.2.44 PDP-Type

This parameter indicates which type of protocol is used by the MS as defined in GSM 03.60.

7.6.2.45 PDP-Address

This parameter indicates the address of the data protocol as defined in GSM 03.60.

7.6.2.46 Additional number

This parameter can refer either to the SGSN number or to the MSC number.

7.6.2.47 P-TMSI

This parameter is the Packet Temporary Mobile Subscriber Identity defined in GSM 03.03.

7.6.2.48 B-subscriber number

This parameter refers to the number of the destination B dialled by the A user. This may include a subaddress.

7.6.2.49 B-subscriber subaddress

This parameter refers to the sub-address attached to the destination B dialled by the A user.

7.6.3 Subscriber management parameters

7.6.3.1 Category

This parameter refers to the calling party category as defined in CCITT Recommendation Q.767.

7.6.3.2 Equipment status

This parameter refers to the status of the mobile equipment as defined in GSM 02.16.

7.6.3.3 Extensible Bearer service

This parameter may refer to a single bearer service, a set of bearer services or to all bearer services as defined in TS GSM 02.02. This parameter is used only for subscriber profile management. Extensible Bearer service values include all values defined for a Bearer service parameter (7.6.4.38).

7.6.3.4 Extensible Teleservice

This parameter may refer to a single teleservice, a set of teleservices or to all teleservices as defined in TS GSM 02.03. This parameter is used only for subscriber profile management. Extensible Teleservice values include all values defined for a Teleservice parameter (7.6.4.39).

7.6.3.5 Extensible Basic Service Group

This parameter refers to the Basic Service Group either as an extensible bearer service (see subclause 7.6.3.3) or an extensible teleservice (see subclause 7.6.3.4). This parameter is used only for subscriber profile management. The null value (i.e. neither extensible bearer service nor extensible teleservice) is used to denote the group containing all extensible bearer services and all extensible teleservices.

7.6.3.6 GSM bearer capability

This parameter refers to the GSM bearer capability information element defined in GSM 04.08.

7.6.3.7 Subscriber Status

This parameter refers to the barring status of the subscriber:

– service granted;

– Operator Determined Barring.

7.6.3.8 CUG Outgoing Access indicator

This parameter represents the Outgoing Access as defined in ETS 300 136.

7.6.3.9 Operator Determined Barring General Data

This parameter refers to the set of subscribers features that the network operator or the service provider can regulate. This set only includes those limitations that can be controlled in the VLR or in the SGSN:

– All outgoing calls barred; (*)

– International outgoing calls barred; (*)

– International outgoing calls except those to the home PLMN country barred; (*)

– Interzonal outgoing calls barred; (*)

– Interzonal outgoing calls except those to the home PLMN country barred; (*)

– Interzonal outgoing calls AND intenational outgoing calls except those directed to the home PLMN country barred; (*)

– Premium rate (information) outgoing calls barred;

– Premium rate (entertainment) outgoing calls barred;

– Supplementary service access barred;

– Invocation of call transfer barred;

– Invocation of chargeable call transfer barred;

– Invocation of internationally chargeable call transfer barred;

– Invocation of interzonally chargeable call transfer barred;

– Invocation of call transfer where both legs are chargeable barred.

(*) Only these ODBs are supported by the SGSN. The SGSN applies them only for short message transfer.

7.6.3.10 ODB HPLMN Specific Data

This parameter refers to the set of subscribers features that the network operator or the service provider can regulate only when the subscriber is registered in the HPLMN. This set only includes those limitations that can be controlled in the VLR or in the SGSN:

– Operator Determined Barring Type 1;

– Operator Determined Barring Type 2;

– Operator Determined Barring Type 3;

– Operator Determined Barring Type 4.

7.6.3.11 Regional Subscription Data

This parameter defines the regional subscription area in which the subscriber is allowed to roam. It consists of a list of Zone Codes (see subclause 7.6.2.28).

7.6.3.12 Regional Subscription Response

This parameter indicates either that the regional subscription data cannot be handled or that the current MSC or SGSN area is entirely restricted because of regional subscription.

7.6.3.13 Roaming Restriction Due To Unsupported Feature

This parameter defines that a subscriber is not allowed to roam in the current MSC area. It may be used by the HLR if a feature or service is indicated as unsupported by the VLR.

7.6.3.14 Extensible SS-Info

This parameter refers to all the information related to a supplementary service and is a choice between:

– extensible forwarding information (see subclause 7.6.3.15);

– extensible call barring information (see subclause 7.6.3.20);

– CUG info (see subclause 7.6.3.22);

– extensible SS-Data (see subclause 7.6.3.29).

7.6.3.15 Extensible Forwarding information

This parameter represents the information related to each call forwarding service:

– the SS-Code of the relevant call forwarding service (see subclause 7.6.4.1);

– if required, a list of extensible forwarding feature parameters (see subclause 7.6.3.16).

The list may contain one item per Basic Service Group.

7.6.3.16 Extensible Forwarding feature

This parameter applies to each combination of call forwarding service and Basic Service Group and contains the following information, as required:

– extensible Basic Service Group (see subclause 7.6.3.5);

– extensible SS-Status (see subclause 7.6.3.17);

– forwarded-to number (see subclause 7.6.2.22);

– forwarded-to subaddress (see subclause 7.6.2.23);

– extensible forwarding options (see subclause 7.6.3.18);

– extensible no reply condition timer (see subclause 7.6.4.19).

7.6.3.17 Extensible SS-Status

This parameter refers to the state information of individual supplementary services as defined in TS GSM 03.11.

7.6.3.18 Extensible Forwarding Options

This parameter refers to a set of forwarding options attached to a supplementary service. It contains the following informations:

– notification to forwarding party (see TS GSM 02.82 for the meaning of this parameter);

– notification to calling party (see TS GSM 02.82 for the meaning of this parameter);

– Forwarding reason (see TS GSM 02.82 for the meaning of this parameter).

7.6.3.19 Extensible No reply condition timer

This parameter refers to the extensible no reply condition timer for call forwarding on no reply.

7.6.3.20 Extensible Call barring information

This parameter contains for each call barring service:

– SS-Code (see subclause 7.6.4.1);

– a list of extensible call barring feature parameters (see subclause 7.6.3.21).

The list may contain one item per Basic Service Group.

7.6.3.21 Extensible Call barring feature

This parameter gives the status of call barring services as applicable to each Basic Service Group. The parameter contains the following information:

– Extensible Basic Service Group (see subclause 7.6.3.5);

– provisioned SS-Status (see subclause 7.6.3.17).

7.6.3.22 CUG info

This parameter refers to the overall information required for operation for each CUG:

– CUG subscriptionList;

– CUG featureList.

7.6.3.23 CUG subscription

This parameter refers to the set of basic information for each CUG defined in that subscription. The following information is stored:

– CUG index;

– CUG interlock;

– Intra CUG restrictions;

– Basic Service Group List.

7.6.3.24 CUG interlock

This parameter represents the CUG interlock code defined in ETS 300 138.

7.6.3.25 CUG index

This parameter represents the CUG index defined in ETS 300 138.

7.6.3.26 CUG feature

This parameter contains two parameters which are associated with the Basic Service Group. If the Basic Service Group Code is not present the feature applies to all Basic Services. The following parameters are included:

– Preferential CUG indicator:

indicates which CUG index is to be used at outgoing call set-up using the associated Basic Service Group;

– Inter CUG Option:

describes whether it for the associated Basic Service Group is allowed to make calls outside the CUG and whether incoming calls are allowed;

– Basic Service Group.

See TS GSM 02.85 for meaning of this parameter.

7.6.3.27 Inter CUG options

This parameter indicates the subscribers ability to make and receive calls outside a specific closed user group. It takes any of the following values:

– CUG only facility (only calls within CUG are allowed);

– CUG with outgoing access (calls outside CUG allowed);

– CUG with incoming access (calls from outside CUG into CUG allowed);

– CUG with both incoming and outgoing access (all calls allowed).

7.6.3.28 Intra CUG restrictions

This parameter describes whether or not the subscriber is allowed to originate calls to or to receive calls from within the CUG. It can take any of the following values:

– no CUG restrictions;

– CUG incoming calls barred;

– CUG outgoing calls barred.

7.6.3.29 Extensible SS-Data

This parameter refers to the necessary set of information required in order to characterise one supplementary service:

– SS-Code (see subclause 7.6.4.1);

– Extensible SS-Status (if applicable ) (see subclause 7.6.3.17);

– Extensible Override subscription option (if applicable) (see subclause 7.6.3.30);

– Extensible CLI Restriction (if applicable) (see subclause 7.6.3.31);

– Extensible Basic Service Group Code (see subclause 7.6.3.5).

7.6.3.30 Subscriber State

This parameter indicates the state of the MS as defined in GSM 03.18.

7.6.3.31 Requested Info

This parameter indicates the subscriber information being requested as defined in GSM 03.18.

7.6.3.32 Suppression of Announcement

This parameter indicates if the announcement or tones shall be suppressed as defined in GSM 03.78.

7.6.3.33 Suppress T-CSI

This parameter is used to suppress the invocation of terminating CAMEL services.

7.6.3.34 GMSC CAMEL Subscription Info

This parameter contains CAMEL subscription information, i.e.O-CSI and/or T-CSI, which indicates to the GMSC that originating and/or terminating CAMEL services shall be invoked for the incoming call.

7.6.3.35 VLR CAMEL Subscription Info

This parameter identifies the subscriber as having CAMEL services which are invoked in the MSC.

7.6.3.36 Supported CAMEL Phases

This parameter indicates which phases of CAMEL are supported.

7.6.3.37 CUG Subscription Flag

This parameter indicates a that a subscriber with a T-CSI also has a CUG subscription. It is defined in TS GSM 03.78.

7.6.3.38 CAMEL Subscription Info Withdraw

This parameter indicates that CAMEL Subscription Info shall be deleted from the VLR.

7.6.3.39 Voice Group Call Service (VGCS) Data

This parameter refers to one or more groups a subscriber may be member of for voice group calls.

7.6.3.40 Voice Broadcast Service (VBS) Data

This parameter refers to one or more groups a subscriber may be member of for the voice broadcast service. Per group it is further indicated whether the subscriber is only allowed to listen to respective group calls or whether he is in addition entitled to initiate respective voice broadcast calls.

7.6.3.41 ISDN bearer capability

This parameter refers to the ISDN bearer capability information element defined in GSM 09.07.

7.6.3.42 Lower layer Compatibility

This parameter refers to the lower layer compatibility information element defined in GSM 04.08.

7.6.3.43 High Layer Compatibility

This parameter refers to the high layer compatibility information element defined in GSM 04.08.

7.6.3.44 Alerting Pattern

This parameter is an indication that can be used by the MS to alert the user in a specific manner in case of mobile terminating traffic (switched call or USSD). That indication can be an alerting level or an alerting category.

7.6.3.45 GPRS Subscription Data Withdraw

This parameter indicates that GPRS Subscription Data shall be deleted from the SGSN.

7.6.3.46 GPRS Subscription Data

This parameter refers to the list of PDP-Contexts that subscriber has subscribed to.

7.6.3.47 QoS-Subscribed

This parameter indicates the quality of service subscribed for a certain service. It is defined in GSM 03.60.

7.6.3.48 VPLMN address allowed

This parameter specifies whether the MS is allowed to used a dynamic address allocated in the VPLMN. It is defined in GSM 03.60.

7.6.3.49 Roaming Restricted In SGSN Due To Unsupported Feature

This parameter defines that a subscriber is not allowed to roam in the current SGSN area. It may be used by the HLR if a feature or service is indicated as unsupported by the SGSN.

7.6.3.50 Network Access Mode

This parameter is defined in GSM 03.08.

7.6.3.51 Mobile Not Reachable Reason

This parameter stores the reason for the MS being absent when an attempt to deliver a short message to an MS fails at the MSC, SGSN or both. It is defined in TS GSM 03.40.

7.6.3.52 Cancellation Type

This parameter indicates the reason of location cancellation. It is defined in TS GSM 03.60.

7.6.3.53 All GPRS Data

This parameter indicates to the SGSN that all GPRS Subscription Data shall be deleted for the subscriber.

7.6.3.54 Complete Data List Included

This parameter indicates to the SGSN that the complete GPRS Subscription Data stored for the Subscriber shall be replaced with the GPRS Subscription Data received.

7.6.3.55 PDP Context Identifier

This parameter is used to identify a PDP context for the subscriber.

7.6.4 Supplementary services parameters

7.6.4.1 SS-Code

This parameter may refer to one supplementary service or a set of supplementary services as defined in TS GSM 02.04. For MAP Release ’97 this includes:

– Calling Line Identification Presentation service (CLIP);

– Calling Line Identification Restriction service (CLIR);

– Connected Line Identification Presentation service (COLP);

– Connected Line Identification Restriction service (COLR);

– Calling Name Presentation (CNAP)

– All Call Forwarding services;

– Call Waiting (CW);

– Call Hold (HOLD);

– Multi-Party service (MPTY);

– Closed User Group (CUG);

– All Charging services;

– All Call Restriction services;

– Explicit Call Transfer service (ECT);

– enhanced Multi-Level Precedence and Pre-emption service (eMLPP);

– Completion of Calls to Busy Subscriber, originating side (CCBS-A);

– Completion of Calls to Busy Subscriber, destination side (CCBS-B).

7.6.4.2 SS-Status

This parameter refers to the state information of individual supplementary services as defined in GSM 03.11.

7.6.4.3 SS-Data

This parameter refers to the necessary set of information required in order to characterise one supplementary service:

– SS-Code (see subclause 7.6.4.1);

– SS-Status (if applicable) (see subclause 7.6.4.2);

– Override subscription option (see subclause 7.6.4.4);

– CLI Restriction (see subclause 7.6.4.5);

– Basic Service Group Code (see subclause 7.6.4.40).

7.6.4.4 Override Category

This parameter refers to the subscription option Override Category attached to a supplementary service. It can take the following two values:

– Enabled;

– Disabled.

7.6.4.5 CLI Restriction Option

This parameter refers to the subscription option Restriction mode attached to the CLIR supplementary service. It can take the following three values:

– Permanent;

– Temporary (Default Restricted);

– Temporary (Default Allowed).

7.6.4.6 Forwarding Options

This parameter refers to a forwarding option attached to a supplementary service. It can take one of the following values:

– notification to forwarding party (see GSM 02.82 for the meaning of this parameter);

– notification to calling party (see GSM 02.82 for the meaning of this parameter);

– Forwarding reason (see GSM 02.82 for the meaning of this parameter).

7.6.4.7 No reply condition timer

This parameter refers to the no reply condition timer for call forwarding on no reply.

7.6.4.8 – 7.6.4.14 Void

7.6.4.15 Forwarding information

This parameter represents the information related to each call forwarding service:

– the SS-Code of the relevant call forwarding service (see subclause 7.6.4.1);

– if required, a list of forwarding feature parameters (see subclause 7.6.4.16).

The list may contain one item per Basic Service Group.

7.6.4.16 Forwarding feature

This parameter applies to each combination of call forwarding service and Basic Service Group and contains the following information, as required:

– Basic Service Group (see subclause 7.6.4.40);

– SS-Status (see subclause 7.6.4.2);

– forwarded-to number (see subclause 7.6.2.22);

– forwarded-to subaddress (see subclause 7.6.2.23);

– forwarding options (see subclause 7.6.4.6);

– no reply condition timer (see subclause 7.6.4.7).

7.6.4.17 Void

7.6.4.18 Call barring information

This parameter contains for each call barring service:

– SS-Code (see subclause 7.6.4.1);

– a list of call barring feature parameters (see subclause 7.6.4.19).

The list may contain one item per Basic Service Group.

7.6.4.19 Call barring feature

This parameter gives the status of call barring services as applicable to each Basic Service Group. The parameter contains the following information:

– Basic Service Group (see subclause 7.6.4.40);

– SS-Status (see subclause 7.6.4.2).

7.6.4.20 New password

This parameter refers to the password which the subscriber just registered in the network.

This parameter refers to a password used by the subscriber for supplementary service control.

7.6.4.21 Current password

This parameter refers to a password used by the subscriber for supplementary service control.

7.6.4.22 Guidance information

This parameter refers to guidance information given to a subscriber who is requested to provide a password. One of the following information may be given:

– "enter password";

This information is used for checking of the old password.

– "enter new password";

This information is used during password registration for the request of the first new password.

– "enter new password again";

This information is used during password registration for the request of the new password again for verification.

7.6.4.23 Void

7.6.4.24 SS-Info

This parameter refers to all the information related to a supplementary service and is a choice between:

– forwarding information (see subclause 7.6.4.15);

– call barring information (see subclause 7.6.4.18);

– CUG info (see subclause 7.6.4.8);

– SS-Data (see subclause 7.6.4.3).

– eMLPP information (see subclause 7.6.4.41).

7.6.4.25 ÷ 7.6.4.35 Void

7.6.4.36 USSD Data Coding Scheme

This parameter contains the information of the alphabet and the language used for the unstructured information in an Unstructured Supplementary Service Data operation. The coding of this parameter is according to the Cell Broadcast Data Coding Scheme as specified in GSM 03.38.

7.6.4.37 USSD String

This parameter contains a string of unstructured information in an Unstructured Supplementary Service Data operation. The string is sent either by the mobile user or the network. The contents of a string sent by the MS are interpreted by the network as specified in GSM 02.90.

7.6.4.38 Bearer service

This parameter may refer to a single bearer service, a set of bearer services or to all bearer services as defined in TS GSM 02.02. This parameter is used only for supplementary service management.

7.6.4.39 Teleservice

This parameter may refer to a single teleservice, a set of teleservices or to all teleservices as defined in TS GSM 02.03. This parameter is used only for supplementary service management.

7.6.4.40 Basic Service Group

This parameter refers to the Basic Service Group either as a bearer service (see subclause 7.6.4.38) or a teleservice (see subclause 7.6.4.39). This parameter is used only for supplementary service management. The null value (i.e. neither bearer service nor teleservice) is used to denote the group containing all bearer services and all teleservices.

7.6.4.41 eMLPP information

This parameter contains two parameters which are associated with the eMLPP service. The following two parameters are included:

– maximum entitled priority:

indicates the highest priority level the subscriber is allowed to apply for an outgoing call set-up;

– default priority:

defines the priority level which shall be assigned to a call if no explicit priority is indicated during call set-up.

7.6.4.42 SS-event

This parameter indicates the Supplementary Service for which an invocation notification is sent towards the gsmSCF. It can indicate one of the following services:

– Explicit Call Transfer (ECT)

– Call Deflection (CD)

– Multi-Party call (MPTY)

7.6.4.43 SS-event data

This parameter contains additional information related to Supplementary Service invocation. Depending on the service invoked it can contain the following information:

ECT A list with all Called Party Numbers involved.

CD The called Party number involved.

7.6.5 Call parameters

7.6.5.1 Call reference number

This parameter refers to a call reference number allocated by a call control MSC.

7.6.5.2 Interrogation type

This parameter refers to the type of interrogation for routing information which is sent from a GMSC to an HLR. It can take either of two values:

– basic call (for information to route a call before the call has been extended to the VMSC of the called party);

– forwarding (for information to route the call to the forwarded-to destination after the VMSC of the forwarding party has requested the GMSC to resume handling of the call.

7.6.5.3 OR interrogation

This parameter indicates that the GMSC which interrogated the HLR for routeing information is not in the same PLMN as the HLR, and therefore that the call will potentially be optimally routed.

7.6.5.4 OR capability

This parameter indicates the phase of OR which the GMSC supports.

7.6.5.5 Forwarding reason

This parameter indicates the reason for which the call is to be forwarded. It can take one of three values:

– busy subscriber;

– mobile subscriber not reachable;

– no subscriber reply.

7.6.5.6 Forwarding interrogation required

This parameter indicates that if the VMSC of the forwarding subscriber requests the GMSC to resume handling of the call the GMSC shall interrogate the HLR for forwarding information.

7.6.5.7 O-CSI

This parameter identifies the subscriber as having originating CAMEL services as defined in TS GSM 03.78

7.6.5.8 Call Direction

This parameter is used to indicate the direction of the call.

7.6.5.9 Channel Type

This parameter is the result of a Channel Mode Modification for TS61/62. It contains the changed Air Interface User Rate. The information is sent from the SIWFS to the MSC to assign the correct radio resource. This parameter is defined in GSM 08.08.

7.6.5.10 Chosen Channel

This parameter is sent from the MSC to the SIWFS to adjust the interworking unit to the assigned radio resources. This parameter is defined in GSM 08.08.

7.6.5.11 CCBS Feature

This parameter corresponds to the ‘CCBS Description’ parameter in GSM 03.93. It refers to the necessary set of information required in order to characterise a certain CCBS request. The parameter may contain the following information:

– CCBS Index (see GSM 03.93 for the use of this parameter);

– B-subscriber number (see subclause 7.6.2.48);

– B-subscriber subaddress (see subclause 7.6.2.49);

– Basic Service Group Code (see subclause 7.6.4.40).

7.6.6 Radio parameters

7.6.6.1 ÷ 7.6.6.6 Void

7.6.6.7 HO-Number Not Required

This parameter indicates that no handover number allocation is necessary.

7.6.7 Authentication parameters

7.6.7.1 Authentication set list

This parameter represents a list of sets of authentication parameters for a given subscriber:

– Rand;

– Sres;

– Kc.

7.6.7.2 Rand

This parameter represents a random number used for authentication.

7.6.7.3 Sres

This parameter represents the response to an authentication request.

7.6.7.4 Kc

This parameter refers to a key used for ciphering purposes.

7.6.7.5 Void

7.6.7.6 Cksn

This parameter refers to a ciphering key sequence number.

7.6.7.7 Ciphering mode

This parameter refers to the ciphering mode which is associated with a radio channel. It may take values as follows:

– no encryption;

– identification of specific ciphering algorithm.

7.6.8 Short message parameters

7.6.8.1 SM-RP-DA

This parameter represents the destination address used by the short message service relay sub-layer protocol. It can be either of the following:

– IMSI (see subclause 7.6.2.1);

– LMSI (see subclause 7.6.2.16);

– MS-ISDN (see subclause 7.6.2.17);

– roaming number (see subclause 7.6.2.19);

– service centre address (see subclause 7.6.2.27).

7.6.8.2 SM-RP-OA

This parameter refers to the originating address used by the short message service relay sub-layer protocol. It can be either of the following:

– MS-ISDN (see subclause 7.6.2.17);

– service centre address (see subclause 7.6.2.27).

7.6.8.3 MWD status

This parameter indicates whether or not the address of the originator service centre is already contained in the Message Waiting Data file. In addition, it contains the status of the Memory Capacity Exceeded Flag (MCEF), the status of the Mobile subscriber Not Reachable Flag (MNRF) and the status of the Mobile station Not Reachable for GPRS flag (MNRG).

7.6.8.4 SM-RP-UI

This parameter represents the user data field carried by the short message service relay sub-layer protocol.

7.6.8.5 SM-RP-PRI

This parameter is used to indicate whether or not delivery of the short message shall be attempted when a service centre address is already contained in the Message Waiting Data file.

7.6.8.6 SM Delivery Outcome

This parameter indicates the cause for setting the message waiting data. It can take one of the following values:

– Absent subscriber;

– MS memory capacity exceeded;

– Successful transfer.

7.6.8.7 More Messages To Send

This parameter is used to indicate whether or not the service centre has more short messages to send.

7.6.8.8 Alert Reason

This parameter is used to indicate the reason why the service centre is alerted. It can take one of the following values:

– MS present;

– Memory Available.

7.6.8.9 Absent Subscriber Diagnostic SM

This parameter is used to indicate the reason why the subscriber is absent. For the values for this parameter see TS GSM 03.40.

7.6.8.10 Alert Reason Indicator

This parameter indicates that the alert reason is sent to the HLR due to GPRS activity.

7.6.8.11 Additional SM Delivery Outcome

This parameter is used to indicate the GPRS delivery outcome in case a combination between delivery outcome for GPRS and non-GPRS are sent to the HLR.

7.6.8.12 Additional Absent Subscriber Diagnostic SM

This parameter indicates the reason of the additional SM Delivery Outcome.

7.6.8.13 Delivery Outcome Indicator

This parameter indicates that the delivery outcome sent to the HLR is for GPRS.

7.6.8.14 GPRS Node Indicator

This parameter indicates that the Network Node Number sent by the HLR is the SGSN number.

7.6.8.15 GPRS Support Indicator

This parameter indicates that the SMS-GMSC supports GPRS specific procedure of combine delivery of Short Message via MSC and/or via the SGSN.

7.6.8.16 SM-RP-MTI

This parameter represents the RP-Message Type Indicator of the Short Message. It is used to distinguish a SM sent to the mobile station in order to acknowledge an MO-SM initiated by the mobile from a normal MT-SM. This parameter is formatted according to the formatting rules of address fields as described in GSM 03.40.

7.6.8.17 SM-RP-SMEA

This parameter represents the RP-Originating SME-address of the Short Message Entity that has originated the SM. This parameter is used by the short message service relay sub-layer protocol and is formatted according to the formatting rules of address fields as described in GSM 03.40.

7.6.9 Access and signalling system related parameters

7.6.9.1 BSS-apdu

This parameter includes one or two concatenated complete 08.06 messages, as described in GSM 03.09 and GSM 09.10. The Protocol ID indicates that the message or messages are according to GSM 08.06. For the coding of the messages see GSM 08.06 and GSM 08.08.

7.6.9.2 CM service type

This parameter identifies the service category being requested by the subscriber:

– mobile originating call;

– emergency call establishment;

– short message service;

– mobile originating call re-establishment;

– mobile terminating call;

– SS request;

– Voice group call setup;

– Voice broadcast setup.

7.6.9.3 Access connection status

This parameter represents the following access connection status information:

– RR-connection status (established/not established);

– ciphering mode (on/off);

– authentication status (authenticated/not authenticated).

7.6.9.4 External Signal Information

This parameter contains concatenated information elements (including tag and length) which are defined by a common protocol version, preceded by the associated protocol ID. It is used to transport information of the indicated protocol via MAP interfaces.

7.6.9.5 Access signalling information

This parameter refers to any set of information elements imported from GSM 04.08.

7.6.9.6 Location update type

This parameter refers to the location update type (normal, periodic or IMSI attach) contained in the GSM 04.08 LOCATION REGISTRATION REQUEST message.

7.6.9.7 Protocol ID

This parameter refers to the protocol to which the coding of the content of the associated External Signal Information conforms.

The following values are defined:

– 04.08;

– 08.06;

– ETS 300 102-1.

This value indicates the protocol defined by ETS 300 102-1 (EDSS1).

7.6.9.8 Network signal information

This parameter is transported as external signal information. The protocol ID shall be set to "ETS 300 102-1".

The network signal information may include the following information elements as defined in GSM 09.07:

– ISDN BC; the tag and length are defined by ETS 300 102-1.

For the content, see GSM 09.07.

– HLC; the tag and length are defined by ETS 300 102-1.

For the content, see GSM 09.07.

– LLC; the tag and length are defined by ETS 300 102-1.

For the content, see GSM 09.07.

They are contained in the Signal Information parameter according to figure 7.6/1 (irrespective of the order):

Figure 7.6/1: Network signal information parameter

7.6.9.9 Call Info

This parameter is transported as external signal information. The protocol ID shall be set to "GSM 04.08".

The Call Info includes the set of information elements from the original SETUP message and is imported from GSM 04.08.

7.6.10 System operations parameters

7.6.10.1 Network resources

This parameter refers to a class or type of network resource:

– PLMN;

– HLR;

– VLR (current or previous);

– MSC (controlling or current);

– EIR;

– radio sub-system.

7.6.10.2 Trace reference

This parameter represents a reference associated with a tracing request. The parameter is managed by OMC.

7.6.10.3 Trace type

This parameter identifies the type of trace. Trace types are fully defined in GSM 12.08.

7.7 Representation of a list of a basic parameter in service-primitives

In some service-primitives several instances of a basic parameter of subclause 7.6 are required. In the service descriptions such cases will be represented as

ParameterNameLIST

in the tables where ParameterName refers to one of the parameters defined in subclause 7.6. This corresponds to the following construction rule:

Figure 7.7/1: Construction of Lists