10 Call handling services

09.023GPPMobile Application Part (MAP) specificationTS

10.1 MAP_SEND_ROUTING_INFORMATION service

10.1.1 Definition

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.

This is a confirmed service using the primitives listed in table 10.1/1.

10.1.2 Service primitives

Table 10.1/1: MAP_SEND_ROUTING_INFORMATION parameters

Parameter name

Request

Indication

Response

Confirm

Invoke Id

M

M(=)

M(=)

M(=)

Interrogation Type

M

M(=)

GMSC Address

M

M(=)

MSISDN

M

M(=)

OR Interrogation

C

C(=)

OR Capability

C

C(=)

CUG Interlock

C

C(=)

C

C(=)

CUG Outgoing Access

C

C(=)

C

C(=)

Number of Forwarding

C

C(=)

Network Signal Info

C

C(=)

Supported CAMEL Phases

C

C(=)

Suppress T-CSI

C

C(=)

Suppression of Announcement

C

C(=)

Call Reference Number

C

C(=)

Forwarding Reason

C

C(=)

Basic Service Group

C

C(=)

Alerting Pattern

C

C(=)

CCBS Call

C

C(=)

Supported CCBS Phase

C

C(=)

IMSI

C

C(=)

MSRN

C

C(=)

Forwarding Data

C

C(=)

Forwarding Interrogation Required

C

C(=)

VMSC address

C

C(=)

GMSC Camel Subscription Info

C

C(=)

Location Information

C

C(=)

Subscriber State

C

C(=)

Basic Service Code

C

C(=)

CUG Subscription Flag

C

C(=)

North American Equal Access preferred Carrier Id

U

C(=)

User error

C

C(=)

SS-List

U

C(=)

CCBS Target

C

C(=)

Keep CCBS Call Indicator

C

C(=)

Provider error

O

10.1.3 Parameter use

See subclause 7.6 for a definition of the parameters used in addition to the following. Note that:

– a conditional parameter whose use is defined only in GSM 03.78 shall be absent if the sending entity does not support CAMEL;

– a conditional parameter whose use is defined only in GSM 03.79 shall be absent if the sending entity does not support optimal routeing;

– a conditional parameter whose use is defined only in GSM 03.78 & GSM 03.79 shall be absent if the sending entity supports neither CAMEL nor optimal routeing.

Interrogation Type

See GSM 03.79 [99] for the use of this parameter.

GMSC address

The E.164 address of the GMSC.

MSISDN

This is the Mobile Subscriber ISDN number assigned to the called subscriber.

OR Interrogation

See GSM 03.79 [99] for the use of this parameter and the conditions for its presence.

OR Capability

See GSM 03.79 [99] for the use of this parameter and the conditions for its presence.

CUG Interlock

See GSM 03.18 [97] for the use of this parameter and the conditions for its presence.

CUG Outgoing Access

See GSM 03.18 [97] for the use of this parameter and the conditions for its presence.

Number of Forwarding

See GSM 03.18 [97] for the use of this parameter and the conditions for its presence.

Network Signal Info

See GSM 03.18 [97] for the conditions for the presence of the components of this parameter.

Supported CAMEL Phases

The use of this parameter and the requirements for its presence are specified in GSM 03.78

T-CSI Suppression

The use of this parameter and the requirements for its presence are specified in GSM 03.78

Suppression Of Announcement

The use of this parameter and the requirements for its presence are specified in GSM 03.78

Call Reference Number

The use of this parameter and the conditions for its presence are specified in GSM 03.78 [98] and GSM 03.79 [99].

Forwarding Reason

See GSM 03.79 [99] for the use of this parameter and the conditions for its presence.

Basic Service Group

See GSM 03.79 [99] for the use of this parameter and the conditions for its presence.

Alerting Pattern

See GSM 03.18 [97] for the use of this parameter and the conditions for its presence.

CCBS Call

See GSM 03.93 [107] for the use of this parameter and the conditions for its presence.

Supported CCBS Phase

This parameter indicates by its presence that CCBS is supported and the phase of CCBS which is supported.

IMSI

See GSM 03.18 [97] for the use of this parameter and the conditions for its presence.

MSRN

See GSM 03.18 [97] and GSM 03.79 [99] for the use of this parameter and the conditions for its presence.

Forwarding Data

This parameter includes the forwarded-to number, the forwarding option Notification to calling party and the forwarding reason, and can include the forwarded-to subaddress. See GSM 03.18 [97] and GSM 03.79 [99] for the conditions for the presence of its components.

Forwarding Interrogation Required

See GSM 03.79 [99] for the use of this parameter and the conditions for its presence.

VMSC address

See GSM 03.79 [99] for the use of this parameter and the conditions for its presence.

GMSC CAMEL Subscription Info

The use of this parameter and the requirements for its presence are specified in GSM 03.78

Location Information

The use of this parameter and the requirements for its presence are specified in GSM 03.78

Subscriber State

The use of this parameter and the requirements for its presence are specified in GSM 03.78

CUG Subscription Flag

The use of this parameter and the requirements for its presence are specified in GSM 03.78.

North American Equal Access preferred Carrier Id

This parameter is returned to indicate the preferred carrier identity to be used to setup the call (i.e. forwarding the call or establishing the roaming leg).

SS-List

This parameter includes SS-codes and will be returned as an operator option. The HLR shall not send PLMN-specific SS-codes across PLMN boundaries. However if the GMSC receives PLMN-specific SS-codes from a foreign PLMN’s HLR the GMSC may ignore it. If the GMSC attempts to process the PLMN specific SS codes, this may lead to unpredictable behaviour but the GMSC shall continue call processing.

Basic Service Code

The use of this parameter and the requirements for its presence are specified in GSM 03.78.

If the CAMEL service is not involved, this parameter includes the basic service code and will be returned as an operator option. The HLR shall not send a PLMN-specific Basic Service Code across PLMN boundaries. However if the GMSC receives a PLMN-specific Basic Service Code from a foreign PLMN’s HLR the GMSC may ignore it. If the GMSC attempts to process the PLMN specific Basic Service codes, this may lead to unpredictable behaviour but the GMSC shall continue call processing.

CCBS Target

See GSM 03.93 for the use of this parameter and the conditions for its presence.

Keep CCBS Call Indicator

See GSM 03.93 for the use of this parameter and the conditions for its presence.

User error

This parameter is sent by the responder when an error is detected and if present, takes one of the following values:

– Unknown Subscriber;

– Number changed;

– Call Barred;

This error will indicate that either incoming calls are barred for this MS or that calls are barred due to Operator Determined Barring (see GSM 02.41 for a definition of this network feature).

– CUG Reject;

The value of this error cause will indicate the reason for CUG Reject.

– Bearer Service Not Provisioned;

– Teleservice Not Provisioned;

A subscription check has been performed and the call has not passed the check due to incompatibility with regard to the requested service. Depending on the nature of the incompatibility, either of these messages will be returned.

– Facility Not Supported;

– Absent Subscriber;

This indicates that the location of the MS is not known (either the station is not registered and there is no location information available or the Provide Roaming Number procedure fails due to IMSI detached flag being set), or the GMSC requested forwarding information with a forwarding reason of not reachable, and the call forwarding on MS not reachable service is not active.

– Busy Subscriber;

This indicates that Call Forwarding on Busy was not active for the specified basic service group when the GMSC requested forwarding information with a forwarding reason of busy.

The error may also indicate that the subscriber is busy due to an outstanding CCBS recall. In the error data it may then be specified that CCBS is possible for the busy encountered call.

– No Subscriber Reply;

This indicates that Call Forwarding on No Reply was not active for the specified basic service group when the GMSC requested forwarding information with a forwarding reason of no reply.

– OR Not Allowed;

This indicates that the HLR is not prepared to accept an OR interrogation from the GMSC, or that calls to the specified subscriber are not allowed to be optimally routed.

– Forwarding Violation;

– System Failure;

– Data Missing;

– Unexpected Data Value.

See subclause 7.6 for a definition of these errors.

Provider error

These are defined in subclause 7.6.

10.2 MAP_PROVIDE_ROAMING_NUMBER service

10.2.1 Definition

This service is used between the HLR and VLR. The 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.

This is a confirmed service which uses the Primitives described in table 10.2/1.

10.2.2 Service primitives

Table 10.2/1: MAP_PROVIDE_ROAMING_NUMBER parameters

Parameter name

Request

Indication

Response

Confirm

Invoke Id

M

M(=)

M(=)

M(=)

IMSI

M

M(=)

MSC Number

M

M(=)

MSISDN

U

C(=)

LMSI

C

C(=)

GSM Bearer Capability

C

C(=)

Network Signal Info

C

C(=)

Suppression Of Announcement

C

C(=)

Call Reference Number

C

C(=)

GMSC Address

C

C(=)

OR Interrogation

C

C(=)

Alerting Pattern

C

C(=)

CCBS Call

Supported CAMEL Phases in GMSC

C

C

C(=)

C(=)

Roaming Number

C

C(=)

User error

C

C(=)

Provider error

O

10.2.3 Parameter use

See subclause 7.6 for a definition of the parameters used, in addition to the following. Note that:

– a conditional parameter whose use is defined only in GSM 03.78 shall be absent if the sending entity does not support CAMEL;

– a conditional parameter whose use is defined only in GSM 03.79 shall be absent if the sending entity does not support optimal routeing;

– a conditional parameter whose use is defined only in GSM 03.78 & GSM 03.79 shall be absent if the sending entity supports neither CAMEL nor optimal routeing.

IMSI

This is the IMSI of the called Subscriber.

MSC Number

This is the ISDN number assigned to the MSC currently serving the MS. The MSC number will have been stored in the HLR as provided at location updating.

MSISDN

See GSM 03.18 [97] for the use of this parameter and the conditions for its presence.

LMSI

See GSM 03.18 [97] for the use of this parameter and the conditions for its presence.

GSM Bearer Capability

See GSM 03.18 [97] for the use of this parameter and the conditions for its presence.

This information is passed according to the rules specified in TS GSM 09.07.

There may be two GSM Bearer Capabilities supplied.

Network Signal Info

See GSM 03.18 [97] for the conditions for the presence of the components of this parameter.

Suppression Of Announcement

The use of this parameter and the requirements for its presence are specified in GSM 03.78.

Call Reference Number

The use of this parameter and the conditions for its presence are specified in GSM 03.78 [98] and GSM 03.79 [99].

GMSC Address

The use of this parameter and the conditions for its presence are specified in GSM 03.78 [98] and GSM 03.79 [99].

OR Interrogation

See GSM 03.79 [99] for the use of this parameter and the conditions for its presence.

Supported CAMEL Phases in GMSC

See GSM 03.78 [98] for the use of this parameter and the conditions for its presence.

Alerting Pattern

See GSM 03.78 [98] for the use of this parameter and the conditions for its presence.

CCBS Call

See GSM 03.93 [xx] for the use of this parameter and the conditions for its presence.

Roaming Number

See GSM 03.18 [97] for the use of this parameter and the conditions for its presence.

User error

This parameter is sent by the responder when an error is detected and if present, takes one of the following values:

– Absent Subscriber;

This error will be returned if the IMSI detach flag is set.

– No Roaming Number Available;

– OR Not Allowed;

This indicates that the MAP_PROVIDE_ROAMING_NUMBER indication included the OR interrogation indicator, but the VLR does not support optimal routeing.

– Facility Not Supported;

– System Failure;

– Data Missing;

– Unexpected Data Value.

See subclause 7.6 for a definition of these reasons.

Provider error

These are defined in subclause 7.6.

10.3 MAP_RESUME_CALL_HANDLING service

10.3.1 Definition

This service is used between the terminating VMSC and the GMSC. The service is invoked by the terminating VMSC to request the GMSC to resume handling the call and forward it to the specified destination.

This is a confirmed service which uses the Primitives listed in table 10.3/1.

10.3.2 Service primitives

Table 10.3/1: MAP_RESUME_CALL_HANDLING parameters

Parameter name

Request

Indication

Response

Confirm

Invoke Id

M

M(=)

M(=)

M(=)

Call Reference Number

M

M(=)

Basic Service Group

M

M(=)

IMSI

M

M(=)

Forwarding Data

M

M(=)

CUG Interlock

C

C(=)

CUG Outgoing Access

C

C(=)

O-CSI

C

C(=)

CCBS Target

C

C(=)

User error

C

C(=)

Provider error

O

10.3.3 Parameter use

See subclause 7.6 for a definition of the parameters used, in addition to the following.

Call Reference Number

See GSM 03.79 [99] for the use of this parameter.

Basic Service Group

See GSM 03.79 [99] for the use of this parameter.

IMSI

This is the IMSI of the forwarding Subscriber.

Forwarding Data

Includes the forwarded-to number, the forwarding reason, an indication of whether the calling party is to be notified that the call has been forwarded and possibly a forwarded-to subaddress.

CUG Interlock

See GSM 03.79 [99] for the use of this parameter and the conditions for its presence.

CUG Outgoing Access

See GSM 03.79 [99] for the use of this parameter and the conditions for its presence.

O-CSI

See GSM 03.79 [99] for the use of this parameter and the conditions for its presence.

For CAMEL phases 1 & 2, the O-CSI shall contain only one set of O-BCSM TDP data.

CCBS Target

See GSM 03.93 [107] for the use of this parameter and the conditions for its presence.

User error

This parameter is sent by the responder when an error is detected and if present, takes one of the following values:

– Optimal Routeing not allowed;

– Forwarding failed.

Provider error

These are defined in subclause 7.6.

10.4 MAP_PREPARE_GROUP_CALL service

10.4.1 Definition

This service is used by the Anchor_MSC to inform the Relay_MSC about a group call setup.

The MAP_PREPARE_GROUP_CALL service is a confirmed service using the service primitives given in table 10.4

10.4.2 Service primitives

Table 10.4/1: MAP_PREPARE_GROUP_CALL service

Parameter name

Request

Indication

Response

Confirm

Invoke Id

M

M(=)

M(=)

M(=)

Teleservice

M

M(=)

ASCI Call Reference

M

M(=)

Ciphering Algorithm

M

M(=)

Group Key Number

C

C(=)

Group Key

C

C(=)

Priority

C

C(=)

CODEC-Information

M

M(=)

Uplink Free Indicator

M

M(=)

Group Call Number

M

M(=)

User Error

C

C(=)

Provider Error

O

10.4.3 Parameter definitions and use

Invoke Id

See definition in section 7.6.1

Teleservice

Voice Broadcast Service or Voice Group Call Service

ASCI Call Reference

Broadcast call reference or group call reference. This item is used to access the VBS-GCR or VGCS-GCR within the Relay_MSC.

Ciphering Algorithm

The ciphering algorithm to be used for the group call.

Group Key Number

This number has to be broadcasted and is used by the mobile station to select the chosen group key.

Shall be present if the ciphering applies.

Group Key

This key is used for ciphering on the radio interface.

Shall be present if the ciphering applies.

Priority

Default priority level related to the call if eMLPP applies.

CODEC-Information

Information on the codecs allowed for this call.

Uplink Free Indicator

A flag indicating whether the call is initiated from a dispatcher.

Group Call Number

This temporary allocated E.164 number is used for routing the call from the Anchor MSC to the Relay MSC.

User Error

For definition of this parameter see section 7.6.1 The following errors defined in section 7.6.1 may be used, depending on the nature of the fault:

– No Group Call Number available

– System Failure

– Unexpected Data Value.

Provider Error

See definition of provider error in section 7.6.1.

10.5 MAP_PROCESS_GROUP CALL_SIGNALLING service

10.5.1 Definitions

This service is used between Relay MSC and Anchor MSC for transmission of Group Call notifications.

The MAP_PROCESS_GROUP_CALL_SIGNALLING service is a non-confirmed service using the service primitives given in table 10.5

10.5.2 Service primitives

Table 10.5/1: MAP_PROCESS_GROUP_CALL_SIGNALLING service

Parameter name

Request

Indication

Invoke Id

M

M(=)

Uplink Request

C

C(=)

Uplink Release Indication

C

C(=)

Release Group Call

C

C(=)

10.5.3 Parameter definitions and use

Invoke Id

See definition in section 7.6.1

Uplink Request

This information element indicates to the anchor MSC that a service subscriber roaming in the relay MSC area requests access to the uplink.

Uplink Release Indication

This information element if included by the Relay MSC indicates to the Anchor MSC that the uplink has become free.

Release Group Call

This information element if included by the Relay MSC indicates to the Anchor MSC that the service subscriber who has initiated the call and who currently has access to the uplink terminates the call.

10.6 MAP_FORWARD_GROUP_CALL_SIGNALLING service

10.6.1 Definitions

This service is used between Anchor MSC and Relay MSC for transmission of Group Call notifications.

The MAP_FORWARD_GROUP_CALL_SIGNALLING service is a non-confirmed service using the service primitives given in table 10.6

10.6.2 Service primitives

Table 10.6: MAP_FORWARD_GROUP_CALL_SIGNALLING service

Parameter name

Request

Indication

Invoke Id

M

M(=)

IMSI

C

C(=)

Uplink Request Acknowledgement

C

C(=)

Uplink Release Indication

C

C(=)

Uplink Reject Command

C

C(=)

Uplink Seized Command

C

C(=)

Uplink Release Command

C

C(=)

10.6.3 Parameter definitions and use

IMSI

Identity of the service subscriber who has established the call and who is allowed to terminate the call.

Invoke Id

See definition in section 7.6.1

Uplink Request Acknowledgement

This information element is used for positive acknowledgement of an uplink request

Uplink Release Indication

This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink has become free.

Uplink Reject Command

This information element is used for negative acknowledgement of an uplink request

Uplink Seized Command

This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink is no longer free.

Uplink Release Command

This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink which is granted to a MS in the relay MSC area shall be released.

10.7 MAP_SEND_GROUP_CALL_END_SIGNAL service

10.7.1 Definitions

This service is used between the Relay MSC and the Anchor MSC indicating that VGCS / VBS channels have been established in the Relay MSC area. The response is used by the Anchor MSC to inform Relay MSC that all resources for the call can be released in Relay MSC because the call has been released in the Anchor MSC.

The MAP_SEND_GROUP_CALL_END_SIGNAL service is a confirmed service using the service primitives given in table 10.7

10.7.2 Service primitives

Table 10.7: MAP_SEND_GROUP_CALL_END_SIGNAL service

Parameter name

Request

Indication

Response

Confirm

Invoke Id

M

M(=)

M(=)

M(=)

IMSI

C

C(=)

Provider Error

O

10.7.3 Parameter definitions and use

IMSI

Identity of the service subscriber who has established the call and who is allowed to terminate the call.

Shall be present if the call was established by a service subscriber roaming in the relay MSC area.

Invoke Id

See definition in section 7.6.1

Provider Error

See definition of provider error in section 7.6.1.

10.8 MAP_Provide_SIWFS_Number

10.8.1 Definition

This service is used between an MSC and SIWFS. It is invoked by an MSC receiving an incoming call (call to or from MS) to request the SIWFS to allocate IWU resources. The service is defined in GSM 03.54.

This is a confirmed service using the primitives described in table 10.8.

10.8.2 Service primitive

Table 10.8: MAP_Provide_SIWFS_Number service

Parameter name

Request

Indication

Response

Confirm

Invoke ID

M

M(=)

M(=)

M(=)

GSM Bearer Capability

M

M(=)

ISDN Bearer Capability

M

M(=)

Call Direction

M

M(=)

B-subscriber address

M

M(=)

Chosen Channel

M

M(=)

Lower Layer Compatibility

C

C(=)

High Layer Compatibility

C

C(=)

SIWFS number

C

C(=)

User error

C

C(=)

Provider error

O

10.8.3 Parameter use

See subclause 7.6 for a definition of the parameter used, in addition to the following.

GSM Bearer Capability

This information is the result from the negotiation with the mobile station. The information is sent from the MSC to the SIWFS to allocate the correct IWU.

ISDN Bearer Capability

This parameter refers to the ISDN Bearer Capability information element. For the MTC this parameter is received in the ISUP User Service Information parameter. For the MOC call this parameter is mapped from the GSM BC parameter according to GSM 09.07. The parameter is used by the SIWFS to route the call and to allocate the outgoing circuit.

Call Direction

This parameter indicates the direction of the call (mobile originated or mobile terminated) at call set-up.

B-subscriber address

This parameter is sent from the MSC to the SIWFS to inform the SIWFS where to route the call i.e. where to send the IAM. If the loop method is used this parameter will indicate the address to the VMSC. This address is allocated by the VMSC in the same way as a MSRN and is used to correlate the incoming IAM to the corresponding MAP dialogue. If the non-loop method is used this parameter will indicate the address to the B-subscriber.

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.

Lower Layer Compatibility

This parameter is sent from the MSC to the SIWF to allow the interworking unit to perform a compatibility check. This parameter is handled as specified in GSM 09.07. This parameter is defined in GSM 04.08.

High Layer Compatibility

This parameter is sent from the MSC to the SIWF to allow the interworking unit to perform a compatibility check. This parameter is handled as specified in GSM 09.07. This parameter is defined in GSM 04.08.

SIWFS number

This parameter is sent from the SIWFS to the MSC. This address is used by the visited MSC to route the call, i.e. the IAM to the SIWFS (similar to MSRN) and will be used by the SIWFS to correlate the incoming IAM to the corresponding MAP message. This parameter must always be sent from the SIWFS when a successful allocation of SIWFS resources has been made.

User error

This parameter is sent by the responder when an error is detected and if present, takes one of the following values:

– Resource limitation;

– Facility Not Supported;

– Unexpected Data Value;

– System Failure.

See subclause 7.6 for a definition of these reasons.

Provider error

These are defined in subclause 7.6.

10.9 MAP_SIWFS_Signalling_Modify

10.9.1 Definition

This service is used to transport signalling information between an MSC and an SIWFS in the case of a request to modify the configuration (e.g. HSCSD). It is invoked either by an MSC or by the SIWFS. The service is defined in GSM 03.54.

This is a confirmed service using the primitives described in table 10.9.

10.9.2 Service primitive

Table 10.9: MAP_SIWFS_Signalling_Modify service

Parameter name

Request

Indication

Response

Confirm

Invoke ID

M

M(=)

M(=)

M(=)

Channel Type

C

C(=)

Chosen Channel

C

C(=)

C(=)

C(=)

User error

C

C(=)

Provider error

O

10.9.3 Parameter use

See subclause 7.6 for a definition of the parameter used, in addition to the following.

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.

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.

User error

This parameter is sent by the responder when an error is detected and if present , takes one of the following values:

– Resource limitation;

– Facility Not Supported;

– Data Missing;

– Unexpected Data Value;

– System Failure.

See subclause 7.6 for a definition of these reasons.

Provider error

These are defined in subclause 7.6.

10.10 MAP_SET_REPORTING_STATE service

10.10.1 Definition

This service is used between the HLR and the VLR to set the reporting state for a requested service. It is a confirmed service using the service primitives shown in table 10.10/1.

10.10.2 Service primitives

The service primitives are shown in table 10.10/1.

Table 10.10/1: MAP_SET_REPORTING_STATE parameters

Parameter name

Request

Indication

Response

Confirm

Invoke id

M

M(=)

M(=)

M(=)

IMSI

C

C(=)

LMSI

C

C(=)

CCBS Monitoring

C

C(=)

CCBS Subscriber Status

C

C(=)

User error

C

C(=)

Provider error

O

10.10.3 Parameter use

See subclause 7.6 for a definition of the parameters used, in addition to the following.

IMSI

The IMSI is a mandatory parameter if the service is used as the only one in a dialogue.

CCBS Monitoring

This parameter indicates whether monitoring for CCBS shall be started or stopped. If it indicates that monitoring shall be started this service corresponds to the message ‘Start Reporting’ in GSM 03.93; if it indicates that monitoring shall be stopped this service corresponds to the message ‘Stop Reporting’ in GSM 03.93.

CCBS Subscriber Status

See GSM 03.93 for the use of this parameter and the conditions for its presence.

User error

This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following values defined in subclause 7.6.1:

– System Failure;

– Unidentified Subscriber;

– Unexpected Data Value;

– Data Missing;

– Resource Limitation;

– Facility Not Supported.

NOTE: This error is reserved for future use.

Provider error

These are defined in subclause 7.6.

10.11 MAP_STATUS_REPORT service

10.11.1 Definition

This service is used by the VLR to report an event or call outcome to the HLR.It is a confirmed service using the service primitives shown in table 10.11/1.

10.11.2 Service primitives

The service primitives are shown in table 10.11/1.

Table 10.11/1: MAP_STATUS_REPORT parameters

Parameter name

Request

Indication

Response

Confirm

Invoke id

M

M(=)

M(=)

M(=)

IMSI

M

M(=)

CCBS Subscriber Status

C

C(=)

Monitoring Mode

C

C(=)

Call Outcome

C

C(=)

User error

C

C(=)

Provider error

O

10.11.3 Parameter use

See subclause 7.6 for a definition of the parameters used, in addition to the following.

CCBS Subscriber Status

If this parameter is present without Monitoring Mode and Call Outcome this service corresponds to the message ‘Event Report’ in GSM 03.93 [107]. See GSM 03.93 [107] for the use of this parameter and the conditions for its presence.

Monitoring Mode

If this parameter is present with CCBS Call Outcome this service corresponds to the message ‘CCBS Call Report’ in GSM 03.93. See GSM 03.93 for the use of this parameter and the conditions for its presence.

Call Outcome

See GSM 03.93 for the use of this parameter and the conditions for its presence.

User error

This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following values defined in subclause 7.6.1:

– Unknown Subscriber ;

– System Failure;

– Unexpected Data Value;

– Data Missing.

Provider error

These are defined in subclause 7.6.

10.12 MAP_REMOTE_USER_FREE service

10.12.1 Definition

This service is used between the HLR and the VLR to report that the B subscriber is now idle and that the A subscriber can be notified. It is a confirmed service using the service primitives shown in table 10.12/1.

10.12.2 Service primitives

The service primitives are shown in table 10.12/1.

Table 10.12/1: MAP_REMOTE_USER_FREE parameters

Parameter name

Request

Indication

Response

Confirm

Invoke id

M

M(=)

M(=)

M(=)

IMSI

M

M(=)

Call Info

M

M(=)

CCBS Feature

M

M(=)

Translated B Number

M

M(=)

Replace B Number

C

C(=)

Alerting Pattern

C

C(=)

RUF Outcome

C

C(=)

User error

C

C(=)

Provider error

O

10.12.3 Parameter use

See subclause 7.6 for a definition of the parameters used, in addition to the following.

Call Info

See GSM 03.93 for the use of this parameter.

CCBS Feature

See GSM 03.93 for the conditions for the presence of the parameters included in the CCBS feature.

Translated B Number

See GSM 03.93 for the use of this parameter.

Replace B Number

See GSM 03.93 for the use of this parameter and the conditions for its presence.

Alerting Pattern

See GSM 03.93 for the use of this parameter and the conditions for its presence.

RUF Outcome

See GSM 03.93 for the use of this parameter and the conditions for its presence.

User error

This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following values defined in subclause 7.6.1:

– Unexpected Data Value;

– Data Missing;

– Incompatible Terminal;

This error is returned by the responder when the terminal used for CCBS activation is not compatible with the terminal used for the CCBS recall. For details refer to GSM 04.08.

– Absent Subscriber (IMSI Detach; Restricted Area; No Page Response);

– System Failure;

– Busy Subscriber (CCBS Busy).

Provider error

These are defined in subclause 7.6.