A.2 IWF related to the SGd/Gdd interfaces between MME/SGSN and central SMS functions

29.3053GPPInterWorking Function (IWF) between MAP based and Diameter based interfacesRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

A.2.1 Introduction

The clause A.2 with its subclauses describes the IWFs used between an MME/SGSN, supporting the SGd/Gdd interface and Central SMS functions (SMS-GMSC, SMS-IWMSC, SMS Router) supporting a MAP E interface.

3GPP TS 23.204 [6] has specified the support of SMS for IMS UE to IMS UE without MSISDN which impacts the IWF description for the IP-SM-GW with SMS Central functions over SGd/Gdd.

A.2.2 General considerations

Void

A.2.3 Interworking scenarios

A.2.3.1 One IWF scenario

This interworking scenario, illustrated in figure A.2.3.1-1, is between a MME/SGSN supporting SGd/Gdd interface based on Diameter and central SMS functions (SMS-GMSC, SMS-IWMSC, SMS Router) supporting a MAP based E interface for SMS with one IWF in the path.

This interworking scenario also applies between an IP/SM/GW supporting SGd/Gdd interface based on Diameter and central SMS functions (SMS-GMSC, SMS-IWMSC) supporting a MAP based E interface for SMS with one IWF in the path, in particular for SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [6]).

This IWF scenario can be an inter PLMN use case where the MME/SGSN and the IWF are in the Visited PLMN.

This IWF scenario can be an intra PLMN use case where the central SMS functions are supporting MAP based interfaces.

Figure A.2.3.1-1 SGd – E for SMS interworking scenario with one IWF

For MO Forward short messages requests, the IWF shall use the SC address (E.164 number) received over SGd/Gdd for routing over MAP.

For MT Forward short messages, the IWF shall rely on the E.164 number of the MME/SGSN used to route the MAP message towards the IWF to locally determine the Diameter address of the MME/SGSN.

For ALR, the IWF shall use the SC address (E.164 number) received over SGd/Gdd for routing over MAP.

A.2.3.2 Two IWF scenario

This interworking scenario, illustrated in figure A.2.3.2-1 is between a MME/SGSN supporting a SGd/Gdd interface based on Diameter and central SMS functions (SMS-GMSC, SMS-IWMSC, SMS Router) supporting a SGd/Gdd interface based on Diameter with two IWF in the path, a MAP based E interface for SMS being used between the IWFs.

This interworking scenario, also applies between an IP-SM-GW supporting a SGd/Gdd interface based on Diameter and central SMS functions (SMS-GMSC) supporting a SGd/Gdd interface based on Diameter with two IWF in the path, a MAP based E interface for SMS being used between the IWFs, in particular for SMS for IMS UE to IMS UE without MSISDN (see 3GPP TS 23.204 [6]).

Figure A.2.3.2-1: Two IWFs scenario

The IWF1 is located in the PLMN of the MME/SGSN or in the PLMN of the IP-SM-GW. IWF2 is located in the PLMN of the SMS-GMSC or the SMS-IWMSC or the SMS Router. The SMS Router may be in a PLMN different from the PLMN of the SMS-GMSC.

The IWF1 needs not to be aware whether its connection via E for SMS interface is to an IWF or to central SMS functions (see One IWF scenario).

For routing of MO and MT forward short messages and ALR, the IWF1 shall behave as the IWF of the one IWF scenario.

For MO Forward short messages requests, the IWF2 shall rely on the E.164 number of the SMS-SC used to route the MAP message towards the IWF2 to locally determine the Diameter address of the SMS-IWMSC.

For MT Forward short messages requests, the IWF2 shall use the E.164 number of the MME/SGSN/IP-SM-GW received over SGd/Gdd to route the MAP message towards the IWF1.

For ALR, the IWF2 shall route the message using the SMS-GMSC Diameter Address received in the Alert Service Centre message.

A.2.4 The mapping of procedures

A.2.4.1 MO Forward Short Message

A.2.4.1.1 One IWF Scenario

The mapping of the MO Forward Short Message procedure for this scenario is shown in figure A.2.4.1.1-1:

Figure A.2.4.1.1-1: Mapping of MO Forward Short Message procedure with one IWF

1. The IWF receives a OFR message from the MME/SGSN/IP-SM-GW.

2. The IWF opens a MAP v3 dialogue towards the SMS-IWMSC by sending MO-ForwardSM.

3. The IWF receives MO-ForwardSM Ack from the SMS-IWMSC.

4. The IWF sends OFA to the MME/SGSN/IP-SM-GW.

A.2.4.1.2 Two IWFs Scenario

The mapping of the MO Forward Short Message procedure for this scenario is shown in figure A.2.4.1.2-1:

Figure A.2.4.1.2-1: Mapping of MO Forward Short Message procedure with two IWFs

1. The IWF1 receives an OFR message from the MME/SGSN.

2. The IWF1 opens a MAP v3 dialogue towards IWF2 by sending MO-ForwardSM.

3. The IWF2 constructs the OFR message and sends it to the SMS-IWMSC.

4. The IWF2 receives the OFA message from the SMS-IWMSC.

5. The IWF2 closes the MAP dialogue with the IWF2 by sending MO-ForwardSM Ack.

6. The IWF1 sends the OFA message to the MME/SGSN.

A.2.4.2 MT Forward Short Message

A.2.4.2.1 One IWF Scenario

The mapping of the MT Forward Short Message procedure for this scenario is shown in figure A.2.4.2.1-1:

Figure A.2.4.2.1-1: Mapping of MT Forward Short Message procedure with one IWF

1. The IWF receives a MT-ForwardSM MAP v3 message from the SMS-GMSC or from the SMS Router.

2. The IWF sends TFR to the MME/SGSN/IP-SM-GW.

3. The IWF receives TFA.

4. The IWF closes the MAP dialogue with the SMS-GMSC or the SMS Router by sending MT-ForwardSM Ack.

A.2.4.2.2 Two IWFs Scenario

The mapping of the MT Forward Short Message procedure for this scenario is shown in figure A.2.4.2.2-1:

Figure A.2.4.2.2-1: Mapping of MT Forward Short Message procedure with two IWFs

1. The IWF2 receives a TFR message from the SMS-GMSC or the SMS Router.

2. The IWF2 opens a MAP v3 dialogue towards IWF1 by sending MT-ForwardSM.

3. The IWF1 constructs the TFR message and sends it to the MME/SGSN/IP-SM/GW.

4. The IWF1 receives the TFA message from the MME/SGSN/IP-SM-GW.

5. The IWF1 closes the MAP dialogue with the IWF1 by sending MT-ForwardSM Ack.

6. The IWF2 sends an OFA message to the SMS-GMSC or the SMS Router.

A.2.4.3 Alert Service Centre

A.2.4.3.1 One IWF Scenario

The mapping of the Alert Service Center procedure for this scenario is shown in figure A.2.4.3.1-1:

Figure A.2.4.3.1-1: Mapping of Alert Service Centre procedure with one IWF

1. The IWF receives an ALR message from the MME or SGSN.

2. The IWF opens a MAP v3 dialogue towards the SMS-GMSC or SMS Router by sending an alertServiceCentre.

3. The IWF receives an alertServiceCentre Ack from the SMS-GMSC or SMS Router.

4. The IWF sends an ALA message to the MME or SGSN.

A.2.4.3.2 Two IWFs Scenario

The mapping of the Alert Service Center procedure for this scenario is shown in figure A.2.4.x.2-1:

Figure A.2.4.3.2-1: Mapping of Alert Service Centre procedure with two IWFs

1. The IWF1 receives an ALR message from the MME or SGSN.

2. The IWF1 opens a MAP v3 dialogue towards the IWF2 by sending an alertServiceCentre.

3. The IWF2 sends an ALR message to the SMS-GMSC or SMS Router.

4. The IWF2 receives an ALA from the SMS-GMSC or SMS Router.

5. The IWF2 sends an alertServiceCenter Ack to the IWF1.

6. The IWF1 sends an ALA message to the MME or SGSN.

A.2.5 The mapping of parameters

A.2.5.1 Mapping of Parameters for the MO Forward Short Message procedure

A.2.5.1.1 OFR mapping to MO-ForwardSM-Arg

When the IWF needs to construct a MAP MO-ForwardSM message as a result of receiving an OFR command (see subclause A.2.4.1.1 step 2), the IWF shall open a MAP dialogue in application context version 3 and populate sub-parameters of MO-ForwardSM-Arg as described below:

sm-RP-DA in MO-ForwardSM-Arg shall be present and populated with the value received within the SC-Address AVP within OFR.

sm-RP-OA in MO-ForwardSM-Arg shall be present and populated with the value received within the MSISDN AVP within the User-Identifier AVP within OFR.

sm-RP-UI in MO-ForwardSM-Arg shall be present and populated with the value received within the SM-RP-UI AVP within OFR

extensionContainer in MO-ForwardSM-Arg shall be present .

imsi in MO-ForwardSM-Arg shall be present and populated with the value received within the User-Name AVP in the User-Identifier AVP within OFR. .

correlationID in MO-ForwardSM-Arg shall be present if SMSMI-Correlation-ID AVP in OFR is present and be populated as follows:

hlr-id parameter shall be populated with the value received within HSS-ID AVP within SMSMI-Correlation-ID AVP within OFR.

sip-uri-A parameter shall be populated with the value received within Originating-SIP-URI AVP within SMSMI-Correlation-ID AVP within OFR.

sip-uri-B parameter shall be populated with the value received within Destination-SIP-URI AVP within SMSMI-Correlation-ID AVP within OFR.

sm-DeliveryOutcome in MO-ForwardSM-Arg shall be present if SMSMI-Correlation-ID AVP in OFR is present and be populated with the value received in SM-Delivery-Cause within IP-SM-GW-SM-Delivery-Outcome within SM-Delivery-Outcome within OFR.

A.2.5.1.2 MO-ForwardSM-Res / Error mapping to OFA

When the IWF needs to construct an OFA command as a result of receiving a MAP MO-ForwardSM Ack/Error message (see subclause A.2.4.1.1 step 4), the IWF shall populate AVPs of OFA as described below:

Result-Code / Experimental-Result AVP shall be set to:

– DIAMETER_SUCCESS if a MO-ForwardSM-Res parameter was received in the TCAP ResultLast component;

– DIAMETER_ERROR_FACILITY_NOT_SUPPORTED if an error of facilityNotSupported was received;

– DIAMETER_UNABLE_TO_COMPLY if an error of systemFailure was received;

– DIAMETER_SM_DELIVERY_FAILURE if an error of sm-DeliveryFailure was received;

– an appropriate DIAMETER base protocol result code otherwise.

SM-Delivery- Failure-Cause AVP: shall be populated as follows:

SM-Enumerated-Delivery-Failure-Cause AVP shall be present and populated with the value received within the SM-EnumeratedDeliveryFailureCause parameter, when present, within the sm-DeliveryFailureCause of the MO-ForwardSM message.

SM-Diagnostic-Info AVP shall be populated with the value received within the diagnosticInfo parameter, when present, within the sm-DeliveryFailureCause within the MO-ForwardSM message.

SM-RP-UI AVP shall be populated with the value received within the sm-RP-UI parameter, when present, of the MT-ForwardSM-Res message.

A.2.5.1.3 MO-ForwardSM-Arg mapping to OFR

When the IWF needs to construct a OFR command as a result of receiving a MAP MO-ForwardSM message (see subclause A.2.4.1.2 step 3), the IWF shall populate AVPs of OFR as described below:

User-Name AVP shall be present and populated with the value received within the sm-RP-DA parameter of MO-ForwardSM-Arg and translated into an UTF8String format.

User Identifier AVP shall be present and shall be populated as follows:

User-Name AVP shall be present and populated with the value received within the imsi parameter of MO-ForwardSM-Arg and translated into an UTF8String format.

MSISDN AVP shall be populated with the value received within the sm-RP-OA parameter of MO-ForwardSM-Arg

SM-RP-UI AVP shall be populated with the value received within the sm-RP-UI parameter of MO-ForwardSM-Arg

Supported-Features AVP shall be absent.

A.2.5.1.4 OFA mapping to MO-ForwardSM-Res/Error

When the IWF needs to construct MAP MO-ForwardSM Ack message as a result of receiving a OFA command (see subclause A.2.4.1.2 step 5), the IWF shall populate sub-parameters of MO-ForwardSM-Res/Error as described below:

mo-ForwardSM-Res:

sm-RP-UI in MO-ForwardSM-Res shall be populated with the value received within the SM-RP-UI AVP when present.

extensionContainer in MO-ForwardSM-Res shall be absent.

mo-ForwardSM Error:

Values other than SUCCESS within the Result-Code / Experimental-Result AVP shall be mapped onto the following MAP errors:

– An error of systemFailure if a DIAMETER_UNABLE_TO_COMPLY result was received;

– An error of unexpectedDataValue if a DIAMETER_INVALID_AVP_VALUE result was received;

– An error of facilityNotSupported if a DIAMETER_ERROR_FACILITY_NOT_SUPPORTED result was received;

– An error of sm-DeliveryFailure if a DIAMETER_ERROR_SM_DELIVERY_FAILURE.

– sm-DeliveryFailureCause when a DIAMETER_ERROR_SM_DELIVERY_FAILURE result was received, shall be populated as follows:

– SM-EnumeratedDeliveryFailureCause shall be populated with the value received within the SM-Enumerated-Delivery-Failure-Cause AVP within the SM-DeliveryFailureCause AVP within OFA;

– diagnosticInfo parameter shall be populated with the value received within the SM-Diagnostic-Info AVP, when present, within the SM-DeliveryFailureCause AVP within OFA.

A.2.5.2 Mapping of Parameters for the MT Forward Short Message Procedure

A.2.5.2.1 MT-ForwardSM-Arg mapping to TFR

When the IWF needs to construct a TFR command as a result of receiving a MAP MT-ForwardSM message (see subclause A.2.4.2.1 step 2), the IWF shall populate AVPs of TFR as described below:

User-Name AVP shall be populated with the value received within the sm-RP-DA parameter of MT-ForwardSM-Arg.

SC-Address AVP shall be populated with the value received within the sm-RP-OA parameter of MT-ForwardSM-Arg

SM-RP-UI AVP shall be populated with the value received within the sm-RP-UI parameter of MT-ForwardSM-Arg

SMSMI-Correlation-ID AVP shall be present if correlationID in MT-ForwardSM-Arg is present and be populated as follows:

Originating-SIP-URI AVP shall be populated with the value received within the sip-uri-A parameter within correlationID of MT-ForwardSM-Arg.

Destination-SIP-URI AVP shall be populated with the value received within the sip-uri-B parameter within correlationID of MT-ForwardSM-Arg.

TFR-Flags AVP: Flags shall be set as follows:

More-Messages- To-Send shall be set to 1 if the moreMessagesToSend parameter was present within MT-ForwardSM-Arg; otherwise shall be set to 0 or the AVP shall be absent.

Supported-Features AVP shall be absent.

SM-Delivery-Timer AVP shall be present and populated with the value of the smDeliveryTime, when present within the MT-ForwardSM-Arg.

SM-Delivery- Start-Time AVP shall be present and populated with the value of the smDeliveryStartTime, when present within the MT-ForwardSM-Arg.

Maximum-Retransmission-Time AVP shall be present and populated with the value of the maximumRetransmissionTime parameter, when present within the MT-ForwardSM-Arg.

SMS-GMSC Address AVP shall be present and populated with the value of the smsGmscAddress parameter, when present within the MT-ForwardSM-Arg.

A.2.5.2.2 TFA mapping to MT-ForwardSM-Res/Error

When the IWF needs to construct MAP MT-ForwardSM Ack message as a result of receiving a TFA command (see subclause A.2.4.2.1 step 4), the IWF shall populate sub-parameters of MT-ForwardSM-Res/Error as described below:

mt-ForwardSM-Res:

sm-RP-UI in MO-ForwardSM-Res shall be populated with the value received within the SM-RP-UI AVP when present.

extensionContainer in MT-ForwardSM-Res shall be absent.

mt-ForwardSM Error:

Values other than SUCCESS within the Result-Code / Experimental-Result AVP shall be mapped onto the following MAP errors:

– An error of systemFailure error if a DIAMETER_UNABLE_TO_COMPLY result was received;

– An error of dataMissing if a DIAMETER_MISSING_AVP result was received;

– An error of unexpectedDataValue if a DIAMETER_INVALID_AVP_VALUE result was received;

– An error of facilityNotSupported if a DIAMETER_ERROR_FACILITY_NOT_SUPPORTED result was received;

– An error of unidentifiedSubscriber if a DIAMETER_ERROR_USER_UNKNOWN result was received;

– An error of illegalSubscriber if a DIAMETER_ERROR_ILLEGAL_USER result was received;

– An error of illegalEquipment if a DIAMETER_ERROR_ILLEGAL_EQUIPMENT result was received;

– An error of subscriberBusyForMT-SMS if a DIAMETER_ERROR_USER_BUSY_FOR_MT_SMS result was received;

– An error of sm-DeliveryFailure if a DIAMETER_ERROR_SM_DELIVERY_FAILURE result was received;

– An error of absentSubscriberSM if a DIAMETER_ERROR_ABSENT_USER result was received.

– sm-DeliveryFailureCause, when a DIAMETER_ERROR_SM_DELIVERY_FAILURE result was received, shall be populated as follows:

– SM-EnumeratedDeliveryFailureCause shall be populated with the value received within the SM-Enumerated-Delivery-Failure-Cause AVP within the SM-DeliveryFailureCause AVP within TFA;

– diagnosticInfo shall be populated with the value received within the SM-Diagnostic-Info AVP, when present, within the SM-DeliveryFailureCause AVP within TFA.

– absentSubscriberDiagnosticSM, when a DIAMETER_ERROR_ABSENT_USER result was received, shall be populated with the value received within the Absent-Subscriber-Diagnostic-SM AVP, when present, within TFA.

– requestedRetransmissionTime shall be present and populated with the value received in the Requested-Retransmission-Time AVP, when present, within TFA.

A.2.5.2.3 TFR mapping to MT-ForwardSM-Arg

When the IWF needs to construct a MAP MT-ForwardSM message as a result of receiving a TFR command (see subclause A.2.4.2.2 step 2), the IWF shall open a MAP dialogue in application context version 3 and populate sub-parameters of MT-ForwardSM-Arg as described below:

sm-RP-DA in MT-ForwardSM-Arg shall be present and populated with the value received within the User-Name AVP within TFR.

sm-RP-OA in MT-ForwardSM-Arg shall be present and populated with the value received within the SC-Address AVP within TFR.

correlationID in MT-ForwardSM-Arg shall be present if SMSMI-Correlation-ID AVP in TFR is present and be populated as follows:

sip-uri-A parameter shall be populated with the value received within Originating-SIP-URI AVP within SMSMI-Correlation-ID AVP within TFR.

sip-uri-B parameter shall be populated with the value received within Destination-SIP-URI AVP within SMSMI-Correlation-ID AVP within TFR.

sm-RP-UI in MT-ForwardSM-Arg shall be present and populated with value received within the SM-RP-UI AVP within TFR

moreMessagesToSend shall be present if the More-Messages-To-Send flag is set to 1 within the TFR-Flags AVP within MT-ForwardSM-Arg.

smDeliveryTime in MT-ForwardSM-Arg shall be present and populated with the value within the SM-Delivery-Timer AVP when received within TFR.

smDeliveryStartTime in MT-ForwardSM-Arg shall be present and populated with the value within the SM-Delivery- Start-Time AVP when received within TFR.

maximumRetransmissionTime in MT-ForwardSM-Arg shall be present and populated with the value of the Maximum-Retransmission-Time AVP when received within TFR.

smsGmscAddress shall be present and populated with the value within the SMS-GMSC Address AVP, when received within TFR.

NOTE: The value of the MME-Number-For-MT-SMS AVP or of the SGSN-Number AVP is not conveyed in the MAP MT-ForwardSM message but is used by IWF2 for routing the MAP MT-ForwardSM message towards IWF1.

A.2.5.2.4 MT-ForwardSM-Res / Error mapping to TFA

When the IWF needs to construct a TFA command as a result of receiving a MAP MT-ForwardSM Ack/Error message (see subclause A.2.4.2.2 step 6), the IWF shall populate AVPs of TFA as described below:

Result-Code / Experimental-Result AVP shall be set to:

– DIAMETER_SUCCESS if a MT-ForwardSM-Res parameter was received in the TCAP ResultLast component;

– DIAMETER_ERROR_USER_UNKNOWN if an error of unidentifiedSubscriber was received;

– DIAMETER_ERROR_ABSENT_USER if an error of absentSubscriberSM was received;

– DIAMETER_ERROR_USER_BUSY_FOR_MT_SMS if an error of subscriberBusyForMT-SMS was received;

– DIAMETER_ERROR_ILLEGAL_USER if an error of illegalSubscriber was received;

– DIAMETER_ERROR_ILLEGAL_EQUIPMENT if an error of illegalEquipment was received

– DIAMETER_UNABLE_TO_COMPLY if an error of systemFailure was received

– DIAMETER_SM_DELIVERY_FAILURE if an error of sm-DeliveryFailure was received;

– an appropriate DIAMETER base protocol result code otherwise.

SM-Delivery-Failure-Cause AVP, when an error of sm-DeliveryFailure was received, shall be populated as follows:

– SM-Enumerated-Delivery-Failure-Cause AVP shall be present and populated with the value received within the SM-EnumeratedDeliveryFailureCause parameter of the MT-ForwardSM Error message.

– SM-Diagnostic-Info AVP shall be populated with the value received within the diagnosticInfo parameter, when present, within the sm-DeliveryFailureCause within the MT-ForwardSM Error message.

Absent-Subscriber-Diagnostic-SM AVP, when an error of absentSubscriberSM was received, shall be populated with the value received within the absentSubscriberDiagnosticSM parameter of the MT-ForwardSM Error message.

SM-RP-UI AVP shall be populated with the value received within the sm-RP-UI parameter, when present, of the MT-ForwardSM-Res message.

Requested-Retransmission-Time AVP shall be present and populated with the value received within the requestedRetransmissionTime parameter, when present within the MT-ForwardSM Error message.

A.2.5.3 Mapping of Parameters for the Alert Service Centre Procedure

A.2.5.x.1 ALR mapping to alertServiceCentre-Arg

When the IWF needs to construct a MAP alertServiceCentre message as a result of receiving an ALR command, the IWF shall open a MAP dialogue in application context version 3 and populate sub-parameters of alertServiceCentre-Arg as described below:

– msisdn shall be populated with the dummy MSISDN value (see clause 3 of 3GPP TS 23.003 [7])

NOTE: No MSISDN AVP is present in this scenario within the User-Identifier AVP in the ALR message.

– imsi shall be populated with the value received within User-Name AVP within the User-Identifier AVP within ALR.

– serviceCentreAddress shall be present and populated with the value received within the SC-Address AVP within ALR.

– newSgsnNumber shall be present and populated with the value received within the SGSN-Number AVP of the Serving-Node AVP within ALR.

– newMmeNumber shall be present and populated with the value received within the MME-Number-for-MT-SMS AVP of the Serving-Node AVP within ALR.

– newSgsnDiameterAddress shall be present and populated with the value received within the SGSN-Name and SGSN-Realm AVPs of the Serving-Node AVP, when present in ALR.

– newMmeDiameterAddress shall be present and populated with the value received within the MME-Name and MME-Realm AVPs of the Serving-Node AVP, when present in ALR.

– smsGmscAlertEvent shall be present and populated with the value received within the SMS-GMSC-Alert-Event AVP within ALR.

– smsGmscDiameterAddress shall be present and populated with the value received in the Destination-Host and Destination-Realm in ALR.

A.2.5.3.2 alertServiceCentre-Res / Error mapping to ALA

When the IWF needs to construct an ALA command as a result of receiving a MAP alertServiceCentre Ack/Error message, the IWF shall populate AVPs of ALA as described below:

Result-Code / Experimental-Result AVP shall be set to:

– DIAMETER_SUCCESS if no error was received in the TCAP ResultLast component;

– a DIAMETER base protocol result code according to the following table:

Table A.2.5.3.2-1 Mapping from MAP error codes to Diameter error codes

MAP error code	Diameter Result code / Experimental Result
systemFailure	DIAMETER_UNABLE_TO_COMPLY
dataMissing	DIAMETER_MISSING_AVP
unexpectedDataValue	DIAMETER_INVALID_AVP_VALUE

Supported Features AVP shall be absent.

A.2.5.3.3 alertServiceCentre-Arg mapping to ALR

When the IWF needs to construct an ALR command as a result of receiving a MAP alertServiceCentre message, the IWF shall populate the ALR as described below:

– User-Name AVP within User-Identifier AVP shall be present and populated with the value received within the imsi parameter of the alertServiceCenter-Arg.

– SC-Address AVP shall be present and populated with the value received within the serviceCentreAddress parameter of the alertServiceCenter-Arg.

– SGSN-Number AVP of the Serving-Node AVP shall be present and populated with the value received within the newSgsnNumber of the alertServiceCenter-Arg.

– MME-Number-for-MT-SMS AVP shall be present and populated with the value received within the newMmeNumber of the alertServiceCenter-Arg.

– SGSN-Name and SGSN-Realm AVPs of the Serving-Node AVP shall be present and populated with the value received within newSgsnDiameterAddress, when present in the alertServiceCenter-Arg.

– MME-Name and MME-Realm AVPs shall be present and populated with the value received within newMmeDiameterAddress, when present in the alertServiceCenter-Arg.

– SMS-GMSC-Alert-Event AVP shall be present and populated with the value received within the smsGmscAlertEvent of the alertServiceCenter-Arg.

– Destination-Host and Destination-Realm AVPs shall be present and populated with the value received in the smsGmscDiameterAddress in the alertServiceCenter-Arg.

A.2.5.3.4 ALA mapping to alertServiceCentre-Res

When the IWF needs to construct a MAP alertServiceCentre Ack/Error message as a result of receiving an ALA command, the IWF shall populate the MAP alertServiceCenter Ack/Error as described below:

MAP error code shall be set as follows:

Table A.2.5.3.4-1 Mapping from Diameter error codes to MAP error codes

Diameter Result code / Experimental Result	MAP error code
DIAMETER_UNABLE_TO_COMPLY	systemFailure
DIAMETER_MISSING_AVP	dataMissing
DIAMETER_INVALID_AVP_VALUE	unexpectedDataValue