12 Short message service management services

09.023GPPMobile Application Part (MAP) specificationTS

12.1 MAP-SEND-ROUTING-INFO-FOR-SM service

12.1.1 Definition

This service is used between the gateway MSC and the HLR to retrieve the routing information needed for routing the short message to the servicing MSC.

The MAP-SEND-ROUTING-INFO-FOR-SM is a confirmed service using the primitives from table 12.1/1.

12.1.2 Service primitives

The service primitives are shown in table 12.1/1.

Table 12.1/1: MAP-SEND-ROUTING-INFO-FOR-SM

Parameter name

Request

Indication

Response

Confirm

Invoke Id

M

M(=)

M(=)

M(=)

MSISDN

M

M(=)

SM-RP-PRI

M

M(=)

Service Centre Address

M

M(=)

SM-RP-MTI

C

C(=)

SM-RP-SMEA

C

C(=)

GPRS Support Indicator

C

C(=)

IMSI

C

C(=)

Network Node Number

C

C(=)

LMSI

C

C(=)

GPRS Node Indicator

C

C(=)

Additional Number

C

C(=)

User error

C

C(=)

Provider error

O

12.1.3 Parameter use

Invoke id:

See definition in subclause 7.6.1.

MSISDN:

See definition in subclause 7.6.2.

SM-RP-PRI:

See definition in subclause 7.6.8.

Service Centre Address:

See definition in subclause 7.6.2.

SM-RP-MTI :

See definition in subclause 7.6.8. This parameter shall be present when the feature « SM filtering by the HPLMN » is supported by the SMS-GMSC and when the equivalent parameter is received from the short message service relay sub-layer protocol.

SM-RP-SMEA:

See definition in subclause 7.6.8. This parameter shall be present when the feature « SM filtering by the HPLMN » is supported by the SMS-GMSC and when the equivalent parameter is received from the the short message service relay sub-layer protocol.

GPRS Support Indicator:

See definition in subclause 7.6.8. The presence of this parameter is mandatory if the SMS-GMSC supports receiving of the two numbers from the HLR.

IMSI:

See definition in subclause 7.6.2. The presence of this parameter is mandatory in a successful case.

Network Node Number:

See definition in subclause 7.6.2. This parameter is provided in a successful response.

LMSI:

See definition in subclause 7.6.2. It is an operator option to provide this parameter from the VLR; it is mandatory for the HLR to include the LMSI in a successful response, if the VLR has used the LMSI.

GPRS Node Indicator:

See definition in subclause 7.6.8. The presence of this parameter is mandatory if only the SGSN number is sent in the Network Node Number.

Additional Number:

See definition in subclause 7.6.2. This parameter is provided in a successful response.

User error:

The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault:

– Unknown subscriber;

– Call Barred;

– Teleservice Not Provisioned;

– Absent Subscriber_SM;

– Facility Not Supported;

– System failure;

– Unexpected Data Value;

– Data missing.

Provider error:

For definition of provider errors see subclause 7.6.1.

12.2 MAP-MO-FORWARD-SHORT-MESSAGE service

12.2.1 Definition

This service is used between the serving MSC or the SGSN and the SMS Interworking MSC to forward mobile originated short messages.

The MAP-MO-FORWARD-SHORT-MESSAGE service is a confirmed service using the service primitives given in table 12.2/1.

12.2.2 Service primitives

The service primitives are shown in table 12.2/1.

Table 12.2/1: MAP-MO-FORWARD-SHORT-MESSAGE

Parameter name

Request

Indication

Response

Confirm

Invoke Id

M

M(=)

M(=)

M(=)

SM RP DA

M

M(=)

SM RP OA

M

M(=)

SM RP UI

M

M(=)

C

C(=)

User error

C

C(=)

Provider error

O

12.2.3 Parameter use

Invoke id:

See definition in subclause 7.6.1.

SM RP DA:

See definition in subclause 7.6.8.

In the mobile originated SM transfer this parameter contains the Service Centre address received from the mobile station.

SM RP OA:

See definition in subclause 7.6.8.

The MSISDN received from the VLR or from the SGSN is inserted in this parameter in the mobile originated SM transfer.

SM RP UI:

See definition in subclause 7.6.8. The short message transfer protocol data unit received from the Service Centre is inserted in this parameter.

User error:

The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault:

– Facility Not Supported;

– System Failure;

– SM Delivery Failure;

– The reason of the SM Delivery Failure can be one of the following in the mobile originated SM:

– unknown Service Centre address;

– Service Centre congestion;

– invalid Short Message Entity address;

– subscriber not Service Centre subscriber;

– protocol error.

– Unexpected Data Value

Provider error:

For definition of provider errors see subclause 7.6.1.

12.3 MAP-REPORT-SM-DELIVERY-STATUS service

12.3.1 Definition

This service is used between the gateway MSC and the HLR. The MAP-REPORT-SM-DELIVERY-STATUS service is used to set the Message Waiting Data into the HLR or to inform the HLR of successful SM transfer after polling. This service is invoked by the gateway MSC.

The MAP-REPORT-SM-DELIVERY-STATUS service is a confirmed service using the service primitives given in table 12.3/1.

12.3.2 Service primitives

The service primitives are shown in table 12.3/1.

Table 12.3/1: MAP-REPORT-SM-DELIVERY-STATUS

Parameter name

Request

Indication

Response

Confirm

Invoke Id

M

M(=)

M(=)

M(=)

MSISDN

M

M(=)

Service Centre Address

M

M(=)

SM Delivery Outcome

M

M(=)

Absent Subscriber Diagnostic SM

C

C(=)

GPRS Support Indicator

C

C(=)

Delivery Outcome Indicator

C

C(=)

Additional SM Delivery Outcome

C

C(=)

Additional Absent Subscriber Diagnostic SM

C

C(=)

MSIsdn-Alert

C

C(=)

User error

C

C(=)

Provider error

O

12.3.3 Parameter use

Invoke id:

See definition in subclause 7.6.1.

MSISDN:

See definition in subclause 7.6.2.

Service Centre Address:

See definition in subclause 7.6.2.

SM Delivery Outcome:

See definition in subclause 7.6.8. This parameter indicates the status of the mobile terminated SM delivery.

Absent Subscriber Diagnostic SM:

See definition in subclause 7.6.8.

GPRS Support Indicator:

See definition in subclause 7.6.8. The presence of this parameter is mandatory if the SMS-GMSC supports handling of two delivery outcomes.

Delivery Outcome Indicator:

See definition in subclause 7.6.8.

Additional SM Delivery Outcome:

See definition in subclause 7.6.8.

Additional Absent Subscriber Diagnostic SM:

See definition in subclause 7.6.8.

MSIsdn-Alert:

See definition in subclause 7.6.2. This parameter shall be present in case of unsuccessful delivery, when the MSISDN received in the operation is different from the stored MSIsdn-Alert; the stored MSIsdn-Alert is the value that is returned to the gateway MSC.

User error:

The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault:

– Unknown Subscriber;

– Message Waiting List Full;

– Unexpected Data Value;

– Data missing.

Provider error:

For definition of provider errors see subclause 7.6.1.

12.4 MAP-READY-FOR-SM service

12.4.1 Definition

This service is used between the MSC and VLR and as well between the VLR and the HLR. The MSC initiates this service if a subscriber indicates memory available situation. The VLR uses the service to indicate this to the HLR.

The VLR initiates this service if a subscriber, whose message waiting flag is active in the VLR, has radio contact in the MSC.

Also this service is used between the SGSN and the HLR. The SGSN initiates this service if a subscriber indicates memory available situation. The SGSN uses the service to indicate this to the HLR.

The SGSN initiates this service if a subscriber, whose message waiting flag is active in the SGSN, has radio contact in the GPRS.

The MAP-READY-FOR-SM service is a confirmed service using the primitives from table 12.4/1.

12.4.2 Service primitives

The service primitives are shown in table 12.4/1.

Table 12.4/1: MAP-READY-FOR-SM

Parameter name

Request

Indication

Response

Confirm

Invoke Id

M

M(=)

M(=)

M(=)

IMSI

C

C(=)

TMSI

C

C(=)

Alert Reason

M

M(=)

Alert Reason Indicator

C

C(=)

User error

C

C(=)

Provider error

O

12.4.3 Parameter use

Invoke id:

See definition in subclause 7.6.1.

See definition in subclause 7.6.2. The IMSI is used always between the VLR and the HLR and between the SGSN and the HLR. Between the MSC and the VLR the identification can be either IMSI or TMSI.

TMSI:

See definition in subclause 7.6.2. The identification can be either IMSI or TMSI between MSC and VLR.

Alert Reason:

See definition in subclause 7.6.8. This parameter indicates if the mobile subscriber is present or the MS has memory available.

Alert Reason Indicator:

See definition in subclause 7.6.8.

User error:

The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault:

– Unknown Subscriber;

– Facility Not Supported:

– System Failure;

– Unexpected Data Value;

– Data missing;

Provider error:

For definition of provider errors see subclause 7.6.1.

12.5 MAP-ALERT-SERVICE-CENTRE service

12.5.1 Definition

This service is used between the HLR and the interworking MSC. The HLR initiates this service, if the HLR detects that a subscriber, whose MSISDN is in the Message Waiting Data file, is active or the MS has memory available.

The MAP-ALERT-SERVICE-CENTRE service is a confirmed service using the primitives from table 12.5/1.

12.5.2 Service primitives

The service primitives are shown in table 12.5/1.

Table 12.5/1: MAP-ALERT-SERVICE-CENTRE

Parameter name

Request

Indication

Response

Confirm

Invoke Id

M

M(=)

M(=)

M(=)

MSIsdn-Alert

M

M(=)

Service Centre Address

M

M(=)

User error

C

C(=)

Provider error

O

12.5.3 Parameter use

Invoke id:

See definition in subclause 7.6.1.

MSIsdn-Alert:

See definition in subclause 7.6.2. The provided MSISDN shall be the one which is stored in the Message Waiting Data file.

Service Centre Address:

See definition in subclause 7.6.2.

User error:

The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault:

– System Failure;

– Unexpected Data Value;

– Data missing.

Provider error:

For definition of provider errors see subclause 7.6.1.

12.6 MAP-INFORM-SERVICE-CENTRE service

12.6.1 Definition

This service is used between the HLR and the gateway MSC to inform the Service Centre which MSISDN number is stored in the Message Waiting Data file. If the stored MSISDN number is not the same than the one received from the gateway MSC in the MAP-SEND-ROUTING-INFO-FOR-SM service primitive the stored MSISDN number is included in the message.

Additionally the status of MCEF, MNRF and MNRG flags and the inclusion of the particular Service Centre address in the Message Waiting Data list is informed to the gateway MSC when appropriate.

The MAP-INFORM-SERVICE-CENTRE service is a non-confirmed service using the primitives from table 12.6/1.

12.6.2 Service primitives

The service primitives are shown in table 12.6/1.

Table 12.6/1: MAP-INFORM-SERVICE-CENTRE

Parameter name

Request

Indication

Invoke Id

M

M(=)

MSIsdn-Alert

C

C(=)

MWD Status

C

C(=)

12.6.3 Parameter use

Invoke id:

See definition in subclause 7.6.1.

MSIsdn-Alert:

See definition in subclause 7.6.2 This parameter refers to the MSISDN stored in a Message Waiting Data file in the HLR.

MWD Status:

See definition in subclause 7.6.8. This parameter indicates the status of the MCEF, MNRF and MNRG flags and the status of the particular SC address presence in the Message Waiting Data list.

12.7 MAP-SEND-INFO-FOR-MT-SMS service

12.7.1 Definition

This service is used between the MSC and the VLR. The service is invoked by the MSC receiving an mobile terminated short message to request subscriber related information from the VLR.

The MAP-SEND-INFO-FOR-MT-SMS service is a confirmed service using the primitives from table 12.7/1.

12.7.2 Service primitives

The service primitives are shown in table 12.7/1.

Table 12.7/1: MAP-SEND-INFO-FOR-MT-SMS

Parameter name

Request

Indication

Response

Confirm

Invoke Id

M

M(=)

M(=)

M(=)

SM RP DA

M

M(=)

MSISDN

C

C(=)

User error

C

C(=)

Provider error

O

12.7.3 Parameter use

Invoke id:

See definition in subclause 7.6.1.

SM RP DA:

See definition in subclause 7.6.8. This parameter shall contain either an IMSI or a LMSI.

MSISDN:

See definition in subclause 7.6.2.

User error:

The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault:

– Unknown subscriber;

– Unidentified Subscriber;

– Absent subscriber;

– Unexpected Data Value;

– Data Missing;

– Illegal subscriber;

– Illegal equipment;

– Subscriber busy for MT SMS;

– System Failure.

Provider error:

For definition of provider errors see subclause 7.6.1.

12.8 MAP-SEND-INFO-FOR-MO-SMS service

12.8.1 Definition

This service is used between the MSC and the VLR. The service is invoked by the MSC which has to handle a mobile originated short message request to request the subscriber related information from the VLR.

The MAP-SEND-INFO-FOR-MO-SMS service is a confirmed service using the primitives from table 12.8/1.

12.8.2 Service primitives

The service primitives are shown in table 12.8/1.

Table 12.8/1: MAP-SEND-INFO-FOR-MO-SMS

Parameter name

Request

Indication

Response

Confirm

Invoke Id

M

M(=)

M(=)

M(=)

Service Centre Address

M

M(=)

MSISDN

C

C(=)

User error

C

C(=)

Provider error

O

12.8.3 Parameter use

Invoke id:

See definition in subclause 7.6.1.

Service Centre Address:

See definition in subclause 7.6.2.

MSISDN:

See definition in subclause 7.6.2.

User error:

The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault:

– Teleservice Not Provisioned;

– Call Barred;

– Unexpected Data Value;

– Data Missing.

Provider error:

For definition of provider errors see subclause 7.6.1.

12.9 MAP-MT-FORWARD-SHORT-MESSAGE service

12.9.1 Definition

This service is used between the gateway MSC and the servicing MSC or the SGSN to forward mobile mobile terminated short messages.

The MAP-MT-FORWARD-SHORT-MESSAGE service is a confirmed service using the service primitives given in table 12.9/1.

12.9.2 Service primitives

The service primitives are shown in table 12.9/1.

Table 12.9/1: MAP-MT-FORWARD-SHORT-MESSAGE

Parameter name

Request

Indication

Response

Confirm

Invoke Id

M

M(=)

M(=)

M(=)

SM RP DA

M

M(=)

SM RP OA

M

M(=)

SM RP UI

M

M(=)

C

C(=)

More Messages To Send

C

C(=)

User error

C

C(=)

Provider error

O

12.9.3 Parameter use

Invoke id:

See definition in subclause 7.6.1.

SM RP DA:

See definition in subclause 7.6.8. This parameter can contain either an IMSI or a LMSI. The use of the LMSI is an operator option. The LMSI can be provided if it is received from the HLR. The IMSI is used if the use of the LMSI is not available.

This parameter is omitted in the mobile terminated subsequent SM transfers.

SM RP OA:

See definition in subclause 7.6.8. The Service Centre address received from the originating Service Centre is inserted in this parameter .

This parameter is omitted in the mobile terminated subsequent SM transfers.

SM RP UI:

See definition in subclause 7.6.8. The short message transfer protocol data unit received from the Service Centre is inserted in this parameter. A short message transfer protocol data unit may also be inserted in this parameter in the message delivery acknowlegment from the MSC or from the SGSN to the Service Centre.

More Messages To Send:

See definition in subclause 7.6.8. The information from the MMS indication received from the Service Centre is inserted in this parameter.

User error:

The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault:

– Unidentified subscriber;

– Absent Subscriber_SM;

– Subscriber busy for MT SMS;

– Facility Not Supported;

– Illegal Subscriber indicates that delivery of the mobile terminated short message failed because the mobile station failed authentication;

– Illegal equipment indicates that delivery of the mobile terminated short message failed because an IMEI check failed, i.e. the IMEI was blacklisted or not white-listed;

– System Failure;

– SM Delivery Failure;

– The reason of the SM Delivery Failure can be one of the following in the mobile terminated SM:

– memory capacity exceeded in the mobile equipment;

– protocol error;

– mobile equipment does not support the mobile terminated short message service.

– Unexpected Data Value;

– Data Missing.

Provider error:

For definition of provider errors see subclause 7.6.1.