7 The Mapping of the Procedures

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

7.1 Authentication Information Retrieval

7.1.1 One IWF Scenario

The mapping of procedures for this scenario is shown in figure 7.1.1-1:

Figure 7.1.1-1: Mapping of Authentication Info Retrieval Procedure for scenario with one IWF

1. The IWF receives an AIR message from the MME, SGSN or combined MME/SGSN.

2. The IWF opens a MAP v3 dialogue towards the HSS by sending SendAuthenticationInfo.

3. The HSS may initiate MAP version fallback and/or send partial results. The IWF performs the version fallback and/or stores the partial results. If EPS-Vectors are requested for immediate use, version fallback is not applicable;

4. The HSS closes the MAP dialogue by sending the (final) SendAuthenticationInfo Ack to the IWF.

5. The IWF uses the information received from the HSS to construct an AIA which is sent to the MME, SGSN, or combined MME/SGSN.

7.1.2 Two IWFs Scenario

The mapping of procedures for this scenario is shown in figure 7.1.2-1:

Figure 7.1.2-1: Mapping of Authentication Info Retrieval Procedure for scenario with two IWFs

1. The IWF1 receives an AIR message from the MME, SGSN or combined MME/SGSN.

2. The IWF1 opens a MAP v3 dialogue towards IWF2 by sending SendAuthenticationInfo.

3. The IWF2 constructs an AIR message and sends it to the HSS.

4. The IWF2 receives AIA from the HSS.

5. If segmentation is required, the IWF2 sends partial results to the IWF1 which stores the partial results.

6. The IWF2 closes the MAP dialogue by sending the (final) SendAuthenticationInfo Ack to IWF1.

7. The IWF1 uses the information received from the IWF2 to construct an AIA which is sent to the MME, SGSN, or combined MME/SGSN.

7.2 Update Location

7.2.1 One IWF Scenario

The mapping of procedures for this scenario is shown in figure 7.2.1-1:

Figure 7.2.1-1: Mapping of Update Location Procedure for scenario with one IWF

1. The IWF receives an ULR message from the MME, SGSN or combined MME/SGSN.

2. The IWF shall open a MAP v3 dialogue towards the HSS by sending UpdateGprsLocation.

3. Depending on "skip subscriber data" indication received in the ULR (bullet 1 aboveand hence sent as per bullet 2 in the UpdateGprsLocation), the HSS may continue the MAP dialogue by sending one or several InsertSubscriberData messages (in acknowledgement mode or in burst mode) to the IWF. The IWF then temporarily stores the received data and sends InsertSubscriberData Ack messages to the HSS.

Note that the HSS may send InsertSubscriberData messages although a "skip subscriber data" indication was present. In this case InsertSubscriberData messages received from the HSS shall be acknowledged but need not be stored in the IWF.

When sending InsertSubscriberData Ack messages to the HSS the IWF shall mirror back any services requested by the HSS (within the InsertSubscriberData message) but not supported by the MME or SGSN or combined MME/SGSN (as indicated in 1.ULR). The IWF shall reject a MAP ActivateTraceMode message received from the HSS by returning ActivateTraceMode Error (facilityNotSupported).

If the IWF received a MAP ActivateTraceMode message from the HSS, the IWF needs to store the received trace data. Based upon support of tracing (as indicated the ULR received in bullet 1 above), the MME/SGSN sends an ActivateTraceMode Result (positive Ack) or Error FacilityNotSupported (negative Ack) to the HSS.

4. The HSS shallclose the MAP dialogue by sending UpdateGprsLocation Ack to the IWF.

5. The IWF shal use the information received from the HSS to construct an ULA which is sent to the MME, SGSN, or combined MME/SGSN.

7.2.2 Two IWFs Scenario

The mapping of procedures for this scenario is shown in figure 7.2.2-1:

Figure 7.2.2-1: Mapping of Update Location Procedure for scenario with two IWFs

1. The IWF1 receives an ULR message from the MME, SGSN or combined MME/SGSN.

2. The IWF1 shall open a MAP v3 dialogue towards IWF2 by sending UpdateGprsLocation.

3. The IWF2 shall construct a ULR message and shall send it to the HSS.

4. The IWF2 receives ULA from the HSS.

5. If subscriber data is included in the ULA(as per bullet 4), the IWF2 shall send one or several InsertSubscriberData messages (in acknowledgement mode or in burst mode) to the IWF1. IWF1 then temporarily stores the received data and sends InsertSubscriberData Ack messages to the IWF2. If trace data is included in the ULA (bullet 4. above) , the IWF2 sends an ActivateTraceMode message to the IWF1, which sends an ActivateTraceMode Ack message to the IWF2.

6. The IWF2 shall close the MAP dialogue by sending UpdateGprsLocation Ack to IWF1.

7. The IWF1 shall use the information received from the IWF2 to construct an ULA which shall be sent to the MME, SGSN, or combined MME/SGSN.

7.3 Cancel Location

7.3.1 One IWF Scenario

The mapping of procedures for this scenario is shown in figure 7.3.1-1:

Figure 7.3.1-1: Mapping of Cancel Location Procedure for scenario with one IWF

1. The IWF receives a CancelLocation MAP v3 message from the HSS (the IWF shall reject CancelLocation messages in version <3 and shall initiate version fallback when receiving CancelLocation messages in versions >3; not shown in figure 7.3.1-1).

2. The IWF sends CLR to the MME or SGSN or combined MME/SGSN.

3. The IWF receives CLA.

4. The IWF closes the MAP dialogue with the HSS by sending CancelLocation Ack.

7.3.2 Two IWFs Scenario

The mapping of procedures for this scenario is shown in figure 7.3.2-1:

Figure 7.3.2-1: Mapping of Cancel Location Procedure for scenario with two IWFs

1. The IWF2 receives a CLR message from the HSS.

2. The IWF2 opens a MAP v3 dialogue towards IWF1 by sending CancelLocation.

3. The IWF1 constructs a CLR message and sends it to the MME, SGSN, or combined MME/SGSN.

4. The IWF1 receives CLA from the MME, SGSN or combined MME/SGSN.

5. The IWF1 closes the MAP dialogue with the IWF2 by sending CancelLocation Ack.

6. The IWF2 sends CLA to the HSS.

7.4 Purge

7.4.1 One IWF Scenario

The mapping of procedures for this scenario is shown in figure 7.4.1-1:

Figure 7.4.1-1: Mapping of Purge Procedure for scenario with one IWF

1. The IWF receives a PUR message from the MME, SGSN, or combined MME/SGSN.

2. The IWF opens a MAP v3 dialogue towards the HSS by sending PurgeMS.

3. The IWF receives PurgeMS Ack from the HSS.

4. The IWF sends PUA to the MME, SGSN, or combined MME/SGSN.

7.4.2 Two IWFs Scenario

The mapping of procedures for this scenario is shown in figure 7.4.2-1:

Figure 7.4.2-1: Mapping of Purge Procedure for scenario with two IWFs

1. The IWF1 receives a PUR message from the MME, SGSN, or combined MME/SGSN.

2. The IWF1 opens a MAP v3 dialogue towards IWF2 by sending PurgeMS.

3. The IWF2 constructs a PUR message and sends it to the HSS.

4. The IWF2 receives PUA from the HSS.

5. The IWF2 closes the MAP dialogue with the IWF1 by sending PurgeMS Ack.

6. The IWF1 sends PUA to the MME, SGSN, or combined MME/SGSN.

7.5 Insert Subscriber Data

7.5.1 One IWF Scenario

The mapping of procedures for this scenario is shown in figure 7.5.1-1:

Figure 7.5.1-1: Mapping of Insert Subscriber Data Procedure for scenario with one IWF

1. The IWF receives an (stand alone) InsertSubscriberData or ProvideSubscriberInfo message from the HSS.

2. The IWF constructs an IDR message and sends it to the MME, SGSN, or combined MME/SGSN.

3. The IWF receives IDA from the MME, SGSN, or combined MME/SGSN.

4. The IWF sends InsertSubscriberData or ProvideSubscriberInfo Ack to the HSS.

5. Steps 1 to 4 may be repeated several times for InsertSubscriberData. The repetition may be in burst mode or in acknowledge mode.

6. The HSS closes the MAP dialogue.

NOTE: In a mapping procedure, the IWF correlates the MAP Dialogue ID of the MAP request message and the Diameter Session-ID of the mapped Diameter request message which is to be used in the subsequent mapping from Diameter Answer message to corresponding MAP Ack message.

7.5.2 Two IWFs Scenario

The mapping of procedures for this scenario is shown in figure 7.5.2-1:

Figure 7.5.2-1: Mapping of Insert Subscriber Data Procedure for scenario with two IWFs

1. The IWF2 receives a IDR message from the HSS.

2. The IWF2 opens a MAP v3 dialogue towards IWF1 by sending InsertSubscriberData (if the IDR-Flags AVP within the IDR is not present or the "UE Reachability Request" flag was set in the IDR-Flags AVP within the IDR) or ProvideSubscriberInfo in other cases. If segmentation of the data (on MAP level) is required the IWF2 temporarily stores the data that could not be sent in this step.

3. The IWF1 constructs a IDR message and sends it to the MME, SGSN, or combined MME/SGSN.

4. The IWF1 receives IDA from the MME, SGSN, or combined MME/SGSN.

5. The IWF1 sends InsertSubscriberData or ProvideSubscriberInfo Ack to IWF2.

6. If segmentation is required for InsertSubscriberData, steps 2 to 5 are be repeated until all data are sent. Repetition may be in burst mode or in acknowledge mode.

7. IWF2 closes the MAP dialogue with IWF1.

8. IWF2 sends IDA to the HSS.

NOTE: In a mapping procedure, the IWFs correlates the MAP Dialogue ID of the MAP request message and the Diameter Session-ID of the mapped Diameter request message which is to be used in the subsequent mapping from Diameter Answer message to corresponding MAP Ack message or vice versa.

7.6 Delete Subscriber Data

7.6.1 One IWF Scenario

The mapping of procedures for this scenario is shown in figure 7.6.1-1:

Figure 7.6.1-1: Mapping of Delete Subscriber Data Procedure for scenario with one IWF

1. The IWF receives a DeleteSubscriberData MAP v3 message from the HSS (the IWF shall reject DeleteSubscriberData messages in version <3 and shall initiate version fallback when receiving DeleteSubscriberData messages in versions >3; not shown in figure 7.6.1-1).

2. The IWF sends DSR to the MME or SGSN or combined MME/SGSN.

3. The IWF receives DSA.

4. The IWF closes the MAP dialogue with the HSS by sending DeleteSubscriberData Ack.

7.6.2 Two IWFs Scenario

The mapping of procedures for this scenario is shown in figure 7.6.2-1:

Figure 7.6.2-1: Mapping of Delete Subscriber Data Procedure for scenario with two IWFs

1. The IWF2 receives a DSR message from the HSS.

2. The IWF2 opens a MAP v3 dialogue towards IWF1 by sending DeleteSubscriberData.

3. The IWF1 constructs a DSR message and sends it to the MME, SGSN, or combined MME/SGSN.

4. The IWF1 receives DSA from the MME, SGSN or combined MME/SGSN.

5. The IWF1 closes the MAP dialogue with the IWF2 by sending DeleteSubscriberData Ack.

6. The IWF2 sends DSA to the HSS.

7.7 Reset

7.7.1 One IWF Scenario

The mapping of procedures for this scenario is shown in figure 7.7.1-1:

Figure 7.7.1-1: Mapping of Reset Procedure for scenario with one IWF

1. The IWF receives a Reset MAP v1 or v2 message from the HSS.

2. The IWF sends RSR to the MME or SGSN or combined MME/SGSN.

3. The IWF receives RSA.

7.7.2 Two IWFs Scenario

The mapping of procedures for this scenario is shown in figure 7.7.2-1:

Figure 7.7.2-1: Mapping of Reset Procedure for scenario with two IWFs

1. The IWF2 receives a RSR message from the HSS.

2. The IWF2 opens a MAP v1 or v2 (vendor option) dialogue towards IWF1 by sending Reset.

3. The IWF2 sends RSA to the HSS.

4. The IWF1 constructs a RSR message and sends it to the MME, SGSN, or combined MME/SGSN.

5. The IWF1 receives RSA from the MME, SGSN or combined MME/SGSN.

7.8 Notification

7.8.1 One IWF Scenario

The mapping of procedures for this scenario is shown in figure 7.8.1-1:

Figure 7.8.1-1: Mapping of Notification Procedure for scenario with one IWF

1. The IWF receives a NOR message from the MME, SGSN, or combined MME/SGSN.

2. The IWF sends UpdateGprsLocation or ReadyForSM to the HSS.

3. The IWF sends NOA to the MME, SGSN, or combined MME/SGSN.

4. The HSS (if it does not support the "skip subscriber data" indication) may continue the MAP dialogue by sending InsertSubscriberData messages which are positively acknowledged and discarded by the IWF.

5. The HSS closes the MAP dialogue by sending UpdateGprsLocation Ack or ReadyForSM Ack.

7.8.2 Two IWFs Scenario

The mapping of procedures for this scenario is shown in figure 7.8.2-1:

Figure 7.8.2-1: Mapping of Notification Procedure for scenario with two IWFs

1. The IWF1 receives a NOR message from the MME, SGSN, or combined MME/SGSN.

2. The IWF1 sends UpdateGprsLocation or ReadyForSM to the IWF2.

3. The IWF1 sends NOA to the MME, SGSN, or combined MME/SGSN.

4. The IWF2 sends NOR to the HSS.

5. The IWF2 closes the MAP dialogue with IWF1 by sending UpdateGprsLocation Ack or ReadyForSM Ack.

6. The IWF2 receives NOA from the HSS.

7.9 IMEI Check

7.9.1 One IWF Scenario

The mapping of procedures for this scenario is shown in figure 7.9.1-1:

Figure 7.9.1-1: Mapping of IMEI Check Procedure with one IWF

1. The IWF receives an ECR message from the MME/SGSN.

2. The IWF sends Check IMEI to the EIR.

3. The IWF receives Check IMEI Ack from the EIR.

4. The IWF sends ECA to the MME/SGSN.

7.10 Trace Activation

7.10.1 One IWF Scenario

The mapping of procedures for this scenario is shown in figure 7.10.1-1:

Figure 7.10.1-1: Mapping of Trace Activation Procedure for scenario with one IWF

1. The IWF receives an ActivateTraceMode message from the HSS.

2. The IWF shall construct an IDR message and send it to the MME, SGSN, or combined MME/SGSN.

3. The IWF receives IDA from the MME, SGSN, or combined MME/SGSN.

4. The IWF shall send an ActivateTraceMode Ack to the HSS.

7.10.2 Two IWFs Scenario

Figure 7.10.2-1: Mapping of Trace Activation Procedure for scenario with two IWFs

1. The IWF2 receives an IDR message from the HSS.

2. If the IWF2 finds that Trace Data is included in the IDR, it shall open a MAP v3 dialogue towards IWF1 by sending ActivateTraceMode.

3. The IWF1 shall construct an IDR message and shall send it to the MME, SGSN, or combined MME/SGSN.

4. The IWF1 receives IDA from the MME, SGSN, or combined MME/SGSN.

5. The IWF1 shall send an ActivateTraceMode Ack to IWF2.

6. IWF2 shall send an IDA to the HSS.

7.11 Trace Deactivation

7.11.1 One IWF Scenario

The mapping of procedures for this scenario is shown in figure 7.11.1-1:

Figure 7.11.1-1: Mapping of Trace Deactivation Procedure for scenario with one IWF

1. The IWF receives a DeactivateTraceMode message from the HSS.

2. The IWF shall construct a DSR message and shall send it to the MME, SGSN, or the combined MME/SGSN.

3. The IWF receives DSA from the MME, SGSN, or combined MME/SGSN.

4. The IWF shall send a DeactivateTraceMode Ack to the HSS.

7.11.2 Two IWFs Scenario

Figure 7.11.2-1: Mapping of Trace Deactivation Procedure for scenario with two IWFs

1. The IWF2 receives a DSR message from the HSS.

2. If the IWF2 finds that a Trace Data Withdrawal indication is included in the DSR, it shall open a MAP v3 dialogue towards IWF1 by sending DeactivateTraceMode.

3. The IWF1 shall construct a DSR message and shall send it to the MME, SGSN, or the combined MME/SGSN.

4. The IWF1 receives DSA from the MME, SGSN, or combined MME/SGSN.

5. The IWF1 shall send a DeactivateTraceMode Ack to the IWF2.

6. The IWF2 shall send a DSA to the HSS.