5 Mapping between MAP message parameters and SSAP message parameters

09.133GPPSignalling interworking between ISDN supplementary services Application Service Element (ASE) and Mobile Application Part (MAP) protocolsTS

The mapping between MAP message parameters and SSAP message parameters is described. The precise coding of these messages is given in GSM 09.02 and ETS 300 356-18.

The following messages on the SSAP interface do not contain any parameters:

– RemoteUserFree;

– Suspend;

– Resume.

5.1 CCBS Request Invocation

VLRA HLRA DESTINATION
NETWORK B
+-+ +-+ +-+
| | | | | |
| | | | | |
| | RegisterCCEntry | | | |
| |————————->| | | |
| | TC-BEGIN | | | |
| | | | | |
| | | | CcbsRequest | |
| | | |———————–>| |
| | | | TC-BEGIN | |
| | | | | |
| | | | | |

Figure 5.1: Signalling flow for CCBS Request Invocation

Table 5.1: Mapping of CCBS Request Invocation parameters

RegisterCCEntry PARAMETERS

CcbsRequest PARAMETERS

ss-Code

not present

ccbs-Feature

– b-subscriberSubaddress (note 1)

accessTransportParameter (note 2)

translatedB-Number

calledPartynumber (note 3)

serviceIndicator

not present

callInfo

not present

networkSignalInfo

– ISDN BC Tag, Length, Content (note 4)

userServiceInf

networkSignalInfo

– HLC Tag, Length, Content (note 5)

accessTransportParameter (note 2)

networkSignalInfo

– LLC Tag, Length, Content (note 6)

accessTransportParameter (note 2)

not present

retainSupported (note 7)

not present

callingPartyNumber (note 8)

not present

userServiceInfPrime (note 9)

NOTE 1 CCBS-Feature contains the b-subscriberSubaddress parameter which is the called party subaddress. The GSM HLR A shall map the called party subaddress into the accessTransportParameter if received from the VLR. The entire called party subaddress information (i.e. called party subaddress IEI, LENGTH and CONTENT ) is mapped into the accessTransportParameter. See subclause 5.1.1. for details of the required encoding.

NOTE 2 The CcbsRequest contains only one accessTransportParameter. This parameter contains information on the ISDN HLC, LLC and Subaddress.

NOTE 3 The calledParty Number shall be in the international E.164 format.

NOTE 4 The networkSignalInfo contains three information elements ISDN BC, HLC, LLC. The structure of this is defined in GSM 09.02 and the content in GSM 09.07. The entire ISDN BC information element (i.e. ISDN BC TAG, LENGTH and CONTENT ) is mapped into the userServiceInf parameter.

NOTE 5 The networkSignalInfo contains three information elements ISDN BC, HLC, LLC. The structure of this is defined in GSM 09.02 and the content in GSM 09.07. The entire ISDN HLC information element (i.e. ISDN HLC TAG, LENGTH and CONTENT ) is mapped into the accessTransportParameter.

NOTE 6 The networkSignalInfo contains three information elements ISDN BC, HLC, LLC. The structure of this is defined in GSM 09.02 and the content in GSM 09.07. The entire ISDN LLC information element (i.e. ISDN LLC TAG, LENGTH and CONTENT ) is mapped into the accessTransportParameter.

NOTE 7 This information is local to the HLR A. This information element shall be coded by HLR A to reflect whether it supports CCBS Retention capability.

NOTE 8 This information is local to HLR A. The HLR A provides callingPartyNumber if CLIR was not invoked (See the serviceIndicator parameter in GSM 09.02 and GSM 03.93). If sent, the A subscriber’s identity shall be the Basic MSISDN (i.e. the main MSISDN) and shall be in the international E.164 format.

NOTE 9 The GSM HLR A shall not send the userServiceInfPrime

5.1.1 Encoding of called party subaddress information

The CCBS-Feature parameter is received from the VLR and it may include the b-subscriberSubaddress parameter as defined in GSM 09.02. The Called Party Subaddress information requires additional processing in HLR to ensure correct encoding of this information on the SSAP interface. The HLR shall add two octets to the ISDN-SubaddressString received from the VLR as indicated in figure 5.2.

NOTE 1 Called Party Subaddress Information Element Identifier (IEI) is defined by ETS 300 102-1. Its value is "01110001". This information is not sent from the VLR and has to be derived locally in the HLR for interworking purposes.

NOTE 2 This information has to be derived locally in the HLR for interworking purposes.

NOTE 3 This information is sent by the VLR. The ISDN-SubaddressString contents is defined in GSM 09.02.

Figure 5.2: Encoding of Called Party Subaddress information

5.2 CCBS Request Result

VLRA HLRA DESTINATION
NETWORK B
+-+ +-+ +-+
| | | | | |
| | | | | |
| | | | | |
| | | | CcbsRequest-Result | |
| | | |<———————–| |
| | | | TC-CONTINUE | |
| | | | | |
| | RegisterCCEntry-Result | | | |
| |<————————-| | | |
| | TC-END | | | |
| | | | | |
| | | | | |

Figure 5.3: Signalling flow for CCBS Request Result

Table 5.2: Mapping of CCBS Request Result parameters

CcbsRequest_Result PARAMETERS

RegisterCCEntry_Result PARAMETERS

retainSupported (note 1)

not present

not present

ccbs-Feature (note 2)

NOTE 1 This information is associated with each CCBS Request and indicates whether CCBS Retention is supported by the destination B network (see GSM 03.93).

NOTE 2 This information is local to the HLR A. Some of information contained in ccbs-Feature (e.g. ccbs-index) is allocated by the HLR A. The ccbs-Feature information is sent to the MS (see GSM 03.93, GSM 04.93).

5.3 CCBS Request Error

VLRA HLRA DESTINATION
NETWORK B
+-+ +-+ +-+
| | | | | |
| | | | | |
| | | | | |
| | | | CcbsRequest-Error | |
| | | |<———————–| |
| | | | TC-END | |
| | | | | |
| | RegisterCCEntry-Error | | | |
| |<————————-| | | |
| | TC-END | | | |
| | | | | |
| | | | | |
| | | | | |

Figure 5.4: Signalling flow for CCBS Request Error

Table 5.3: Mapping of CCBS Request Error parameters

CcbsRequest_Error PARAMETERS

RegisterCCEntry_Error PARAMETERS

shortTermDenial/ longTermDenial (note 1)

shortTermDenial/ longTermDenial (note 2)

NOTE 1 For coding of these User Errors see ETS 300 356-18.

NOTE 2 For coding of these User Errors see GSM 09.02. This information is sent to the MS (see GSM 04.93, GSM 04.80).