12 Short message service management services

29.0023GPPMobile Application Part (MAP) specificationRelease 17TS

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 or MME but not both, or SGSN, or (for T4-device triggering via the IMS) IP-SM-GW, or SMSF. This service is also used between the gateway MSC and SMS Router, and SMS Router and HLR in order to enforce routing of the SM delivery via the HPLMN of the receiving MS. This service is also used between HLR and IP-SM-GW, and between IP-SM-GW and HLR in order to allow MT-SM delivery (other than T4-device triggering) via the IMS.

This service is also used with an IWF interfacing the S6c interface.

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

12.1.2 Service primitives

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(=)
SM-Delivery Not Intended		U		C(=)
IP-SM-GW Guidance Support Indicator		U		C(=)
Single Attempt Delivery		C		C(=)
IMSI		C		C(=)		C		C(=)
Correlation ID		C		C(=)
T4 Trigger Indicator		C		C(=)
SMSF Support Indicator		C		C(=)
Network Node Number						C		C(=)
Network Node Diameter Address						C		C(=)
LMSI						C		C(=)
GPRS Node Indicator						C		C(=)
Additional Number						C		C(=)
Additional Network Node Diameter Address						C		C(=)
IP-SM-GW Guidance						U		C(=)
Third Number						C		C(=)
Third Network Node Diameter Address						C		C(=)
IMS Node Indicator						C		C(=)
SMSF 3GPP Number						C		C(=)
SMSF 3GPP Diameter Address						C		C(=)
SMSF Non-3GPP Number						C		C(=)
SMSF Non-3GPP Diameter Address						C		C(=)
SMSF 3GPP Address Indicator						C		C(=)
SMSF Non 3GPP Address Indicator						C		C(=)
User error						C		C(=)
Provider error								O

12.1.3 Parameter use

Invoke id

See definition in clause 7.6.1.

MSISDN

See definition in clause 7.6.2.

When SEND-ROUTING-INFO-FOR-SM is sent by the SMS-GMSC to the HLR following an T4 Submit Trigger (see 3GPP TS 23.682 [148]), MSISDN may not be available. In this case the UE shall be identified by the IMSI and the MSISDN shall take the dummy MSISDN value (see clause 3 of 3GPP TS 23.003 [17]).

When SEND-ROUTING-INFO-FOR-SM is sent by the SMS-GMSC to the HLR in a retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [134]), MSISDN may not be available. In this case the UE shall be identified by a Correlation ID (SIP-URI-B) and the MSISDN shall take the dummy MSISDN value (see clause 3 of 3GPP TS 23.003 [17]).

SM-RP-PRI

See definition in clause 7.6.8.

Service Centre Address

See definition in clause 7.6.2.

SM-RP-MTI

See definition in clause 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 clause 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.

GPRS Support Indicator

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

SM-Delivery Not Intended

This parameter indicates by its presence that delivery of a short message is not intended. It further indicates whether only IMSI or only MCC+MNC are requested.

This parameter may be set by entities that request the service without intending to deliver a short message (e.g. MMS Relay/Server), and shall be evaluated by the SMS Router and may be evaluated by the HLR.

IP-SM-GW Guidance Support Indicator

This parameter indicates whether or not the SMS-GMSC is prepared to receive IP-SM-GW Guidance in the response.

Single Attempt Delivery

This parameter indicates the short message is only valid for delivering once, and the HLR/HSS does not need to add the received SC address into MWD list in the case there is no serving node available to provide SMS to the user.

IMSI

See definition in clause 7.6.2.

In Request and Indication:

IMSI shall be present if MSISDN is not available. When SEND-ROUTING-INFO-FOR-SM is sent by the SMS-GMSC to the HLR in a retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [134]), IMSI may not be available. In this case the IMSI parameter shall be populated with the HLR-ID value.

In Response and Confirm: If enforcement of routing an SM via the HPLMN of the receiving MS is deployed, this parameter contains an MT Correlation ID instead of an IMSI when the service is used between SMS-GMSC and SMS Router (see 3GPP TS 23.040 [26] for more information). If the "SM-Delivery Not Intended" parameter was present in the Indication with a value of "only MCC+MNC requested", then this parameter may contain MCC+MNC+dummy MSIN.

The presence of this parameter is mandatory in a successful case.

T4 Trigger Indicator

This indicator indicates by its presence that the request is sent in the context of T4 device triggering (see 3GPP TS 23.682 [148]). When received, the HLR may return up to three serving node numbers and shall not forward the request to an IP-SM-GW or SMS Router.

SMSF Support Indicator

It indicates that the requesting node is capable of receiving ISDN numbers and/or Diameter addresses of the SMSF as target of MT-SMS.

Correlation ID

The Correlation ID parameter contains the SIP-URI-B identifying the (MSISDN-less) destination user. SIP-URI-A and HLR-ID shall be absent from this parameter.

The Correlation ID indicates by its presence that the request is sent in the context of MSISDN-less SMS delivery in IMS (see 3GPP TS 23.204 [134]). When received, the HLR shall return the IP-SM-GW number and shall not forward the request to an IP-SM-GW.

Network Node Number

See definition in clause 7.6.2. This parameter is provided in a successful response. If the "SM-Delivery Not Intended" parameter was present in the Indication a dummy address (encoded in the same manner as the dummy MSISDN defined in clause 3.3 of 3GPP TS 23.003 [17]) may be provided. See clause 12.1.4.

Network Node Diameter Address

See definition in clause 7.6.2. See clause 12.1.4.

LMSI

See definition in clause 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 clause 7.6.8.
Outside the context of T4 device triggering: The presence of this parameter is mandatory if only the SGSN number is sent in the Network Node Number (i.e. if the value within Network Node Number is to be considered as SGSN-Number and Additional Number is absent).
Within the context of T4 device triggering: The presence of this parameter is mandatory if the value within Network Node Number is to be considered as SGSN-Number and Third Number is absent.

Additional Number

See definition in clause 7.6.2. See clause 12.1.4.

Additional Network Node Diameter Address

See definition in clause 7.6.2. See clause 12.1.4.

IP-SM-GW Guidance

This parameter contains the recommended and the minimum timer values for supervision of MT-Forward-Short-Message response. Shall be absent if the IP-SM-GW-Guidance Support Indicator in the request is absent. This parameter is only used by IP-SM-GW and SMS-GMSC.

Third Number

See definition in clause 7.6.2. See clause 12.1.4.

Third Network Node Diameter Address

See definition in clause 7.6.2. See clause 12.1.4

IMS Node Indicator

See definition in clause 7.6.8.
Outside the context of T4 device triggering: The parameter is not applicable and shall be absent.
Within the context of T4 device triggering: The presence of this parameter is mandatory if the value within Network Node Number is to be considered as IP-SM-GW-Number and Third Number is absent.

SMSF 3GPP Number

This parameter contains the ISDN number of the SMSF target node for MT-SMS over 3GPP access.

SMSF 3GPP Diameter Address

This parameter contains the Diameter Name and Realm of the SMSF target node for MT-SMS over 3GPP access.

SMSF Non-3GPP Number

This parameter contains the ISDN number of the SMSF target node for MT-SMS over non-3GPP access.

SMSF Non-3GPP Diameter Address

This parameter contains the Diameter Name and Realm of the SMSF target node for MT-SMS over non-3GPP access.

SMSF 3GPP Address Indicator

It indicates that the parameter Network Node Number (and Network Node Diameter Address, if present) contains the address of an SMSF for 3GPP access.

SMSF Non-3GPP Address Indicator

It indicates that the parameter Network Node Number (and Network Node Diameter Address, if present) contains the address of an SMSF for non-3GPP access.

User error

The following errors defined in clause 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 clause 7.6.1.

12.1.4 Identities of MT-SMS Target Nodes

In a successful MAP-Send-Routing-Info-For-SM response at least one MT-SMS Target Node identity or an SMS Router identity shall be present and this shall be an E.164 number within the Network Node Number parameter.

In addition, optionally a second Target Node identity or an SMS Router identity may be present as E.164 number within the Additional Number Parameter.

In T4 device trigger scenarios in addition to a second Target Node identity, a third Target Node Identity may be present as E.164 number within the Third Number parameter.

In addition to the E.164 identity of an MT-SMS Target Node or an SMSRouter, the presence of the Diameter Name/Realm of the corresponding target node or SMS Router follows the hereafter rules:

– If Network Node Number contains an MME number for SMS, Network Node Diameter Address shall be present and contain the Diameter address of the MME.

– If Network Node Number contains an MSC number, Network Node Diameter Address may be present and shall contain the Diameter address of the MME.

– If Network Node Number contains an SGSN number, Network Node Diameter Address shall be present only if the HSS has received the information that SGSN supports the Gdd interface.

– If Network Node Number contains an SMS Router number, Network Node Diameter Address may be present and shall contain the SMS Router Diameter address.

– If Network Node Number contains an IP-SM-GW number, Network Node Diameter Address may be present and shall contain the IP-SM-GW Diameter address.

Similar for Additional Number – Additional Network Node Diameter Address;

Similar for Third Number – Third Network Node Diameter Address.

In scenarios supporting interworking with 5G System, an E.164 Number and a Diameter Address of the SMSF may be present, for both 3GPP and non-3GPP accesses. In addition:

– If Network Node Number contains an SMSF 3GPP number, Network Node Diameter Address may be present and shall contain the SMSF 3GPP Diameter address.

– If Network Node Number contains an SMSF Non-3GPP number, Network Node Diameter Address may be present and shall contain the SMSF Non-3GPP Diameter address.

12.2 MAP-MO-FORWARD-SHORT-MESSAGE service

12.2.1 Definition

This service is used between the serving MSC or the SGSN or IP-SM-GW 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

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(=)
IMSI	C	C(=)
Correlation ID	C	C(=)
SM Delivery Outcome	C	C(=)
User error			C	C(=)
Provider error				O

12.2.3 Parameter use

Invoke id

See definition in clause 7.6.1.

SM RP DA

See definition in clause 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 clause 7.6.8.

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

A Dummy MSISDN value is used for MSISDN-less SMS in IMS. In this case the originating user is identified by SIP-URI-A (see Correlation ID).

SM RP UI

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

IMSI

See definition in clause 7.6.2.1. The IMSI of the originating subscriber shall be inserted in this parameter in the mobile originated SM transfer.

Correlation ID

The Correlation ID is composed of an HLR-Id identifying the destination user’s HLR, a SIP-URI-B identifying the MSISDN-less destination user, and a SIP-URI-A identifying the originating user.

The Correlation ID indicates by its presence that the request is sent in the context of MSISDN-less SMS delivery in IMS (see 3GPP TS 23.204 [134]), and that a Report-SM-Delivery status needs to be sent to the HLR to add the SC address to the MWD.

SM Delivery Outcome

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

Shall be present if Correlation ID is present and shall take one of the unsuccessful outcome values.

User error

The following errors defined in clause 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 clause 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 or the external Short Message Gateway (IP-SM-GW) 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 or the external Short Message Gateway (IP-SM-GW).

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

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

Parameter name		Request		Indication		Response		Confirm
Invoke Id		M		M(=)		M(=)		M(=)
MSISDN		M		M(=)
IMSI		C		C(=)
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(=)
IP-SM-GW-Indicator		C		C(=)
IP-SM-GW SM Delivery Outcome		C		C(=)
IP-SM-GW Absent Subscriber Diagnostic SM		C		C(=)
Single Attempt Delivery		C		C(=)
Correlation ID		C		C(=)
SMSF 3GPP Delivery Outcome Indicator		C		C(=)
SMSF 3GPP SM Delivery Outcome		C		C(=)
SMSF 3GPP Absent Subscriber Diagnostic SM		C		C(=)
SMSF non-3GPP Delivery Outcome Indicator		C		C(=)
SMSF non-3GPP SM Delivery Outcome		C		C(=)
SMSF non-3GPP 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 clause 7.6.1.

MSISDN

See definition in clause 7.6.2.

When REPORT-SM-DELIVERY-STATUS is sent by the SMS-GMSC to the HLR following an T4 Submit Trigger (see 3GPP TS 23.682 [148]), MSISDN may not be available. In this case the UE shall be identified by the IMSI and the MSISDN shall take the dummy MSISDN value (see clause 3 of 3GPP TS 23.003 [17]).

When REPORT-SM-DELIVERY-STATUS is sent by the SMS-GMSC to the HLR in a retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [134]), MSISDN may not be available. In this case the UE shall be identified by a Correlation ID (SIP-URI-B) and the MSISDN shall take the dummy MSISDN value (see clause 3 of 3GPP TS 23.003 [17]).

IMSI

See definition in clause 7.6.2. When REPORT-SM-DELIVERY-STATUS is sent by the SMS-GMSC to the HLR in a retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [134]), IMSI may not be available. In this case the IMSI parameter shall be populated with an HLR-ID).

Service Centre Address

See definition in clause 7.6.2.

SM Delivery Outcome

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

Absent Subscriber Diagnostic SM

See definition in clause 7.6.8.

GPRS Support Indicator

See definition in clause 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 clause 7.6.8.

Additional SM Delivery Outcome

See definition in clause 7.6.8.

Additional Absent Subscriber Diagnostic SM

See definition in clause 7.6.8.

IP-SM-GW Indicator

See definition in clause 7.6.8.

IP-SM-GW SM Delivery Outcome

See definition in clause 7.6.8.

IP-SM-GW Absent Subscriber Diagnostic SM

See definition in clause 7.6.8.

Single Attempt Delivery

This parameter indicates the short message is only valid for delivering once, and the HLR/HSS does not need to add the received SC address into MWD list. It may only be present in the case the delivery of the short message failed due to absent subscriber or MS memory capacity exceeded.

Editor’s Note: Description of the use of this parameter might be needed in 3GPP TS 23.040.

Correlation ID

The Correlation ID parameter contains the SIP-URI-B identifying the (MSISDN-less) destination user. SIP-URI-A and HLR-ID shall be absent from this parameter.

SMSF 3GPP Delivery Outcome Indicator

See definition in clause 7.6.8.

SMSF 3GPP SM Delivery Outcome

See definition in clause 7.6.8.

SMSF 3GPP Absent Subscriber Diagnostic SM

See definition in clause 7.6.8.

SMSF Non-3GPP Delivery Outcome Indicator

See definition in clause 7.6.8.

SMSF Non-3GPP SM Delivery Outcome

See definition in clause 7.6.8.

SMSF Non-3GPP Absent Subscriber Diagnostic SM

See definition in clause 7.6.8.

MSIsdn-Alert

See definition in clause 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 clause 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 clause 7.6.1.

12.4 MAP-READY-FOR-SM service

12.4.1 Definition

This service is used between the MSC and VLR as well as 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.

Also this service is used between the HSS and the MME via an IWF. The MME initiates this service if a subscriber indicates memory available situation. The MME 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 MME initiates this service if a subscriber, whose message waiting flag is active in the MME, has radio contact via LTE.

Also this service is used between the external Short Message Gateway (IP-SM-GW) and the HLR. The IP-SM-GW initiates this service if a subscriber indicates memory available situation. The IP-SM-GW uses the service to indicate this to the HLR.

The IP-SM-GW initiates this service if a subscriber, whose message waiting flag is active in the IP-SM-GW, is reachable in IMS.

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

12.4.2 Service primitives

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(=)
Additional Alert Reason Indicator	C	C(=)
Maximum UE Availability Time	C	C(=)
User error			C	C(=)
Provider error				O

12.4.3 Parameter use

Invoke id

See definition in clause 7.6.1.

IMSI

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

TMSI

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

Alert Reason

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

Alert Reason Indicator

See definition in clause 7.6.8. This parameter by its presence indicates the message is sent from SGSN, and by its absence indicates the message is sent from VLR or MME via IWF.

Additional Alert Reason Indicator

See definition in clause 7.6.8.

Maximum UE Availability Time

See definition in clause 7.6.8. This information element may be included by the SGSN or MSC when notifying the HLR that the MS is reachable.

User error

The following errors defined in clause 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 clause 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.

This service is also used between an MME (via an IWF), SGSN or an MSC using Deployment Option 2 (see clause 8.2.4a.1 of 3GPP TS 23.272 [143] and 3GPP TS 23.040 [6]) and the SMS-GMSC (possibly via an SMS Router), to indicate that a MS, for which one or more MT SMS have been requested to be retransmitted at a later time, is now available for MT SMS delivery or has moved under the coverage of another MME, SGSN or MSC. This procedure is used according to the call flows described in clause 10.1 of 3GPP TS 23.040 [26].

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

12.5.2 Service primitives

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

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
MSIsdn-Alert	M	M(=)
IMSI	C	C(=)
Correlation ID	C	C(=)
Service Centre Address	M	M(=)
Maximum UE Availability Time	C	C(=)
SMS-GMSC Alert Event	C	C(=)
SMS-GMSC Diameter Address	C	C(=)
New SGSN Number	C	C(=)
New SGSN Diameter Address	C	C(=)
New MME Number	C	C(=)
New MME Diameter Address	C	C(=)
New MSC Number	C	C(=)
User error			C	C(=)
Provider error				O

12.5.3 Parameter use

Invoke id

See definition in clause 7.6.1.

MSIsdn-Alert

See definition in clause 7.6.2.

When the service is used between the HLR and the SMS-IWMSC, the provided MSISDN shall be the one which is stored in the Message Waiting Data file. If no MSISDN is available, the dummy MSISDN value (see clause 3 of 3GPP TS 23.003 [17]) shall be sent and an IMSI or Correlation ID (SIP-URI-B) shall be present.

When the service is used between an MME (via an IWF), SGSN or MSC and the SMS-GMSC, the dummy MSISDN value (see clause 3 of 3GPP TS 23.003 [17]) shall be sent and an IMSI shall be present.

IMSI

When the service is used between the HLR and the SMS-IWMSC, the provided IMSI shall be the identifier which is stored in the Message Waiting Data file if no MSISDN is available in the context of T4 device triggering (see 3GPP TS 23.682 [148]).

When the service is used between an MME (via an IWF), SGSN or MSC and the SMS-GMSC, this information element shall contain the IMSI in the request sent from the MME (via an IWF), SGSN or MSC, or the User Identifier Alert previously sent in the MT Forward Short Message response, when the request is sent from the SMS Router to the SMS-GMSC.

Correlation ID

When the service is used between the HLR and the SMS-IWMSC, the provided SIP-URI-B within the Correlation ID parameter shall be the identifier which is stored in the Message Waiting Data file if no MSISDN is available in a retry context of SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [134]). HLR-ID and SIP-URI-A shall be absent.

When the service is used between an MME (via an IWF), SGSN or MSC and the SMS-GMSC, this information element shall not be included.

Service Centre Address

See definition in clause 7.6.2.

When the service is used between the HLR and the SMS-IWMSC, this information element shall contain the E.164 number of the Service Center.

When the service is used between an MME (via an IWF), SGSN or MSC and the SMS-GMSC, this information element shall contain the E.164 number of the SMS-GMSC (or SMS Router) previously received in the SMS-GMSC Address IE in the MT Forward Short Message Request.

Maximum UE Availability Time

See definition in clause 7.6.8.

When the service is used between the HLR and the SMS-IWMSC, this information element shall be included, if available.

When the service is used between an MME (via an IWF), SGSN or MSC and the SMS-GMSC, this information element shall not be included.

SMS-GMSC Alert Event

See definition in clause 7.6.8.

When the service is used between the HLR and the SMS-IWMSC, this information element shall not be included.

When the service is used between an MME (via an IWF), SGSN or MSC and the SMS-GMSC, this information element shall either indicate that the MS is now available for MT SMS or that the MS has moved under the coverage of another MME, SGSN or MSC.

New SGSN Number

See definition in clause 7.6.8.

When the service is used between the HLR and the SMS-IWMSC, this information element shall not be included.

When the service is used between an MME (via an IWF) or SGSN and the SMS-GMSC, this information element may be included if the SMS-GMSC Alert Event indicates that the MS has moved under the coverage of another SGSN. When present, it shall contain the E.164 number of the new SGSN serving the MS.

New MME Number

See definition in clause 7.6.8.

When the service is used between the HLR and the SMS-IWMSC, this information element shall not be included.

When the service is used between an MME (via an IWF) or SGSN and the SMS-GMSC, this information element may be included if the SMS-GMSC Alert Event indicates that the MS has moved under the coverage of another MME. When present, it shall contain the E.164 number of the new MME serving the MS.

New SGSN Diameter Address

See definition in clause 7.6.8.

When the service is used between the HLR and the SMS-IWMSC, this information element shall not be included.

When the service is used between an MME (via an IWF) or SGSN and the SMS-GMSC, this information element shall be included if available and if the SMS-GMSC Alert Event indicates that the MS has moved under the coverage of another SGSN. When present, it shall contain the Diameter Identity of the new SGSN serving the MS.

New MME Diameter Address

See definition in clause 7.6.8.

When the service is used between the HLR and the SMS-IWMSC, this information element shall not be included.

When the service is used between an MME (via an IWF) or SGSN and the SMS-GMSC, this information element shall be included if available and if the SMS-GMSC Alert Event indicates that the MS has moved under the coverage of another MME. When present, it shall contain the Diameter Identity of the new MME serving the MS.

SMS-GMSC Diameter Address

See definition in clause 7.6.2.

When the service is used between the HLR and the SMS-IWMSC, this information element shall not be included.

When the service is used between an MME (via an IWF), SGSN or MSC and the SMS-GMSC, this information element shall contain, if available, the Diameter Identity of the SMS-GMSC (or SMS Router) previously received in the SMS-GMSC Diameter Address IE in the MT Forward Short Message Request.

New MSC Number

See definition in clause 7.6.8.33.

When the service is used between the HLR and the SMS-IWMSC, this information element shall not be included.

When the service is used between an MSC and the SMS-GMSC, this information element may be included if the SMS-GMSC Alert Event indicates that the MS has moved under the coverage of another MSC. When present, it shall contain the E.164 number of the new MSC serving the MS.

User error

The following errors defined in clause 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 clause 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 (transiting an SMS Router, if present) 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 as 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, MNRG, MNR5G and MNR5GN3G flags and the inclusion of the particular Service Centre address in the Message Waiting Data list is informed to the gateway MSC when appropriate.

If the HLR has stored a single MNRR, the value is included in the Absent Subscriber Diagnostic SM parameter.

If the HLR has stored a second MNRR, the value of the MNRR for the MSC is included in the Absent Subscriber Diagnostic SM parameter and the value of the MNRR for the SGSN is included in the Additional Absent Subscriber Diagnostic SM parameter.

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

12.6.2 Service primitives

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

Parameter name	Request	Indication
Invoke Id	M	M(=)
MSIsdn-Alert	C	C(=)
MWD Status	C	C(=)
Absent Subscriber Diagnostic SM	C	C(=)
Additional Absent Subscriber Diagnostic SM	C	C(=)
SMSF 3GPP Absent Subscriber Diagnostic SM	C	C(=)
SMSF Non 3GPP Absent Subscriber Diagnostic SM	C	C(=)

12.6.3 Parameter use

Invoke id

See definition in clause 7.6.1.

MSIsdn-Alert

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

MWD Status

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

Absent Subscriber Diagnostic SM

See definition in clause 7.6.8.

Additional Absent Subscriber Diagnostic SM

See definition in clause 7.6.8.

SMSF 3GPP Absent Subscriber Diagnostic SM

See definition in clause 7.6.8.

SMSF Non 3GPP Absent Subscriber Diagnostic SM

See definition in clause 7.6.8.

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 a 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

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(=)
IMSI	C	C(=)
MSISDN			C	C(=)
User error			C	C(=)
Provider error				O

12.7.3 Parameter use

Invoke id

See definition in clause 7.6.1.

SM RP DA

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

IMSI

See definition in clause 7.6.2. This parameter shall be present if the SM RP DA parameter contains an LMSI; otherwise it shall be absent.

MSISDN

See definition in clause 7.6.2.

User error

The following errors defined in clause 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 clause 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

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 clause 7.6.1.

Service Centre Address

See definition in clause 7.6.2.

MSISDN

See definition in clause 7.6.2.

User error

The following errors defined in clause 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 clause 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 serving MSC or the SGSN (transiting an SMS Router, if present) or the IP-SM-GW to forward 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

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(=)
SM Delivery Timer	C	C(=)
SM Delivery Start Time	C	C(=)
SMS Over IP Only Indicator	C	C(=)
Correlation ID	C	C(=)
Maximum Retransmission Time	C	C(=)
SMS-GMSC Address	C	C(=)
SMS-GMSC Diameter Address	C	C(=)
Requested Retransmission Time			C	C(=)
User Identifier Alert			C	C(=)
User error			C	C(=)
Provider error				O

12.9.3 Parameter use

Invoke id

See definition in clause 7.6.1.

SM RP DA

See definition in clause 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 (i.e. is present and takes the value "noSM-RP-DA") in the mobile terminated subsequent SM transfers.

When a Correlation ID is present, the IMSI parameter within SM RP DA shall be populated with the HLR-ID and the destination user is identified by the SIP-URI-B within the Correlation ID.

SM RP OA

See definition in clause 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 clause 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 acknowledgement from the MSC or from the SGSN to the Service Centre.

More Messages To Send

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

SM Delivery Timer

See definition in clause 7.6.8.

SM Delivery Start Time

See definition in clause 7.6.8.

SMS Over IP Only Indicator

This indicator indicates by its presence that the IP-SM-GW shall try to deliver the short message via IMS without retrying to other domains. It shall be present in messages sent to the IP-SM-GW following a T4-Submit Trigger message (see 3GPP TS 23.682 [148]) but not in messages sent to MSC or SGSN (possibly transiting an SMS-Router).

The indicator also indicates to the IP-SM-GW by its presence that the IMSI within the message is a real IMSI and not a MT-Correlation ID allocated by the IP-SM-GW.

Correlation ID

The Correlation ID parameter contains the SIP-URI-B identifying the (MSISDN-less) destination user and the SIP-URI-A identifying the (MSISDN-less) originating user. HLR-ID shall be absent from this parameter.

Maximum Retransmission Time

See definition in clause 7.6.8.

SMS-GMSC Address

See definition in clause 7.6.8.

This information element shall be present if the Maximum Retransmission Time IE is present in the message. When present, it shall contain the E.164 number of the SMS-GMSC in the request sent by the SMS-GMSC or the E.164 number of the SMS Router in the request sent by the SMS Router.

SMS-GMSC Diameter Address

See definition in clause 7.6.8.

This information element shall be present if available and if the Maximum Retransmission Time IE is present in the message. When present, it shall contain the Diameter Identity of the SMS-GMSC in the request sent by the SMS-GMSC or the Diameter Identity of the SMS Router in the request sent by the SMS Router.

Requested Retransmission Time

See definition in clause 7.6.8. This information element may only be present if the MT Forward Short Message Response contains the User error set to Absent Subscriber_SM and if the Maximum Retransmission Time information element is present in the MT Forward Short Message Request. It may be included by an MSC using Deployment Option 2 (see clause 8.2.4a.1 of 3GPP TS 23.272 [143] and 3GPP TS 23.040 [6]) or the SGSN if the UE is using a power saving mechanism (such as extended idle mode DRX) and the UE is currently not reachable.

The Requested Retransmission Time shall not exceed the Maximum Retransmission Time received from the SMS-GMSC.

User-Identifier-Alert

See definition in clause 7.6.8.

This information element shall be present in the message from the SMS Router to the SMS-GMSC, if the Requested Retransmission Time IE is present in the message. When present, this information shall contain an MT Correlation ID.

User error

The following errors defined in clause 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 prohibited-listed or not permitted-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 clause 7.6.1.

12.10 MAP-MT-FORWARD-SM-FOR-VGCS service

12.10.1 Definition

This service is used between the SMS gateway MSC and the Group Call Anchor MSC to forward mobile terminated short messages into an ongoing voice group call.

The MAP-MT-FORWARD-SM-FOR-VGCS service is a confirmed service using the service primitives given in table 12.10/1.

12.10.2 Service primitives

Table 12.10/1: MAP-MT-FORWARD-SM-VGCS

Parameter name	Request	Indication	Response	Confirm
Invoke Id	M	M(=)	M(=)	M(=)
ASCI Call Reference	M	M(=)
SM RP OA	M	M(=)
SM RP UI	M	M(=)	C	C(=)
Dispatcher List			C	C(=)
Ongoing Call Indicator			C	C(=)
User error			C	C(=)
Provider error				O

12.10.3 Parameter use

Invoke id

See definition in clause 7.6.1.

ASCI Call Reference

Group call reference. This item is used to access the VGCS-GCR within the Anchor_MSC.

SM RP OA

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

SM RP UI

See definition in clause 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 acknowledgement from the MSC to the Service Centre.

Dispatcher List

A list of identities (international E.164 phone numbers) identifying the dispatchers of the VGCS call. It shall be present if received from the GCR; otherwise shall be absent.

Ongoing Call Indicator

Indicates by its presence that the VGCS call is ongoing.

User error

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

– System Failure;

– Unexpected Data Value.

Provider error

For definition of provider errors see clause 7.6.1.