16.2 Service specific procedures

09.023GPPMobile Application Part (MAP) specificationTS

Specific services are mapped to TC component handling services.

16.2.1 Directly mapped parameters

The Invoke Id parameter of the MAP request and indication primitive is directly mapped on to the Invoke Id parameter of the component handling primitives.

16.2.2 Use of other parameters of component handling primitives

16.2.2.1 Dialogue Id

The value of this parameter is associated with the MAP PM invocation in an implementation dependent manner.

16.2.2.2 Class

The value of this parameter is set by the MAP PM according to the type of the operation to be invoked.

16.2.2.3 Linked Id

When a service response is mapped to a class 4 operation, the value of this parameter is set by the MAP PM and corresponds to the value assigned by the user to the initial service request (i.e. the value of the invoke ID parameter of the request primitive). Otherwise if such a parameter is included in MAP request/indication primitives it is directly mapped to the linked ID parameter of the associated TC‑INVOKE request/indication primitives.

16.2.2.4 Operation

When mapping a request primitive on to a Remote Operations PDU (invoke), the MAP PM shall set the operation code according to the mapping described in table 16.2/1.

When mapping a response primitive on to a Remote Operations service, the MAP PM shall set the operation code of the TC-RESULT-L/NL primitive (if required) to the same value as the one received at invocation time.

Table 16.2/1: Mapping of MAP specific services on to MAP operations

MAP-SERVICE

operation

MAP-ACTIVATE-SS

activateSS

MAP-ACTIVATE-TRACE-MODE

activateTraceMode

MAP-ALERT-SERVICE-CENTRE

alertServiceCentre

MAP-ANY-TIME-INTERROGATION

anyTimeInterrogaton

MAP-CANCEL-LOCATION

cancelLocation

MAP-CHECK-IMEI

checkIMEI

MAP-DEACTIVATE-SS

deactivateSS

MAP-DEACTIVATE-TRACE-MODE

deactivateTraceMode

MAP-DELETE-SUBSCRIBER-DATA

deleteSubscriberData

MAP-ERASE-CC-ENTRY

eraseCC-Entry

MAP-ERASE-SS

eraseSS

MAP-FAILURE-REPORT

failureReport

MAP-FORWARD-ACCESS-SIGNALLING

forwardAccessSignalling

MAP-FORWARD-CHECK-SS-INDICATION

forwardCheckSsIndication

MAP-FORWARD-GROUP-CALL-SIGNALLING

forwardGroupCallSignalling

MAP-MT-FORWARD-SHORT-MESSAGE

mt-forwardSM

MAP-MO-FORWARD-SHORT-MESSAGE

mo-forwardSM

MAP-GET-PASSWORD

getPassword

MAP-INFORM-SERVICE-CENTRE

informServiceCentre

MAP-INSERT-SUBSCRIBER-DATA

insertSubscriberData

MAP-INTERROGATE-SS

interrogateSs

MAP-NOTE-MS-PRESENT-FOR-GPRS

noteMsPresentForGprs

MAP-PREPARE-GROUP-CALL

prepareGroupCall

MAP-PREPARE-HANDOVER

prepareHandover

MAP-PREPARE-SUBSEQUENT-HANDOVER

prepareSubsequentHandover

MAP-PROCESS-ACCESS-SIGNALLING

processAccessSignalling

MAP-PROCESS-GROUP-CALL-SIGNALLING

processGroupCallSignalling

MAP-PROCESS-UNSTRUCTURED-SS-REQUEST

processUnstructuredSS-Request

MAP-PROVIDE-ROAMING-NUMBER

provideRoamingNumber

MAP-PROVIDE-SIWFS-NUMBER

provideSIWFSNumber

MAP-PROVIDE-SUBSCRIBER-INFO

provideSubscriberInfo

MAP-PURGE-MS

purgeMS

MAP-READY-FOR-SM

readyForSM

MAP-REGISTER-CC-ENTRY

registerCC-Entry

MAP-REGISTER-PASSWORD

registerPassword

MAP-REGISTER-SS

registerSS

MAP-REMOTE-USER-FREE

remoteUserFree

MAP-REPORT-SM-DELIVERY-STATUS

reportSmDeliveryStatus

MAP-RESET

reset

MAP-RESTORE-DATA

restoreData

MAP-SEND_GROUP-CALL_END_SIGNAL

sendGroupCallEndSignal

MAP-SEND-END-SIGNAL

sendEndSignal

MAP-SEND-AUTHENTICATION-INFO

sendAuthenticationInfo

MAP-SEND-IMSI

sendIMSI

MAP-SEND-IDENTIFICATION

sendIdentification

MAP-SEND-ROUTING-INFO-FOR-SM

sendRoutingInfoForSM

MAP-SEND-ROUTING-INFO-FOR-GPRS

sendRoutingInfoForGprs

MAP-SEND-ROUTING-INFORMATION

sendRoutingInfo

MAP-SET-REPORTING-STATE

setReportingState

MAP-SIWFS-SIGNALLING-MODIFY

SIWFSSignallingModify

MAP-STATUS-REPORT

statusReport

MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION

ss-Invocation-Notification

MAP-UNSTRUCTURED-SS-NOTIFY

unstructuredSS-Notify

MAP-UNSTRUCTURED-SS-REQUEST

unstructuredSS-Request

MAP-UPDATE-GPRS-LOCATION

updateGprsLocation

MAP-UPDATE-LOCATION

updateLocation

16.2.2.5 Error

The error parameter in a TC-U-ERROR indication primitive is mapped to the user error parameter in the MAP confirm primitive of the service associated with the operation to which the error is attached.

The user error parameter in MAP response primitives is mapped to the error parameter of the TC‑U‑ERROR request primitive, except for "initiating-release" and "resource-limitation" which are mapped to the problem code parameter of the TC-U-REJECT request primitive.

16.2.2.6 Parameters

The parameters of MAP specific request and indication primitives are mapped to the argument parameter of TC-INVOKE primitives.

The parameters of MAP specific response and confirm primitives are mapped to the result parameter of TC-RESULT-L primitives, the parameter of TC-U-ERROR primitives or the argument of TC-INVOKE primitives when mapping on linked class 4 operations is used.

16.2.2.7 Time out

The value of this parameter is set by the MAP PM according to the type of operation invoked.

16.2.2.8 Last component

This parameter is used by the MAP PM as described in CCITT Recommendation Q.711. It is not visible from the MAP user.

16.2.2.9 Problem code

16.2.2.9.1 Mapping to MAP User Error

The following values of the user error parameter are mapped as follows to values of the TC problem code parameter. These values are generated by the MAP user. This mapping is valid from the TC-U-REJECT indication primitive to the MAP confirm service primitive and from the MAP response service primitive to the TC-U-REJECT request primitive.

Table 16.2/2: Mapping of MAP User Error parameter on to TC problem code in TC-U-REJECT primitives

MAP User Error

TC problem code

resource limitation

resource limitation

initiating release

initiating release

16.2.2.9.2 Mapping to MAP Provider Error parameter

The following values of the TC problem code parameter of the TC-U-REJECT indication primitive are mapped as follows to values of the MAP Provider Error parameter of the MAP confirm primitive.

Table 16.2/3: Mapping of TC problem code in TC-U-REJECT on to MAP Provider Error parameter

TC problem code

MAP Provider Error

duplicated invoke Id

duplicated invoke id

unrecognized operation

service not supported

mistyped parameter

mistyped parameter

The following values of the problem code parameters of the TC-L-REJECT primitive are mapped to values of the provider error parameter of the MAP confirm primitive as follows:

Table 16.2/4: Mapping of TC problem code in TC-L-REJECT on to MAP Provider Error parameter

TC problem code

MAP Provider Error

return result unexpected

unexpected response from the peer

return error unexpected

unexpected response from the peer

16.2.2.9.3 Mapping to diagnostic parameter

The following values of the problem code parameter of the TC-R-REJECT and TC-U-REJECT primitive are mapped to values of the diagnostic parameter of the MAP-NOTICE indication primitive as follows:

Table 16.2/5: Mapping of TC problem code of TC-R-REJECT and TC-U-REJECT on to diagnostic parameter

TC problem code

MAP diagnostic

General problem

abnormal event detected by the peer

Invoke problem

– unrecognized linked ID

– abnormal event detected by the peer

– linked response unexpected

– response rejected by the peer

– unexpected linked operation

– response rejected by the peer

Return result problem

– unrecognized invoke ID

– response rejected by the peer

– return result unexpected

– response rejected by the peer

– mistyped parameter

– response rejected by the peer

Return error problem

– unrecognized invoke ID

– response rejected by the peer

– return error unexpected

– response rejected by the peer

– unrecognized error

– response rejected by the peer

– unexpected error

– response rejected by the peer

– mistyped parameter

– response rejected by the peer

The following values of the problem code parameter of the TC-L-REJECT primitive are mapped to values of the diagnostic parameter of the MAP-NOTICE indication primitive as follows:

Table 16.2/6: Mapping of TC problem code of TC-L-REJECT on to diagnostic parameter

TC problem code

MAP diagnostic

General problems:

– abnormal event received from the peer

Invoke problem:

– unrecognized linked ID

– abnormal event received from the peer

Return result problem:

– unrecognized invoke ID

– abnormal event received from the peer

Return error problem:

– unrecognized invoke ID

– abnormal event received from the peer