21.5.3 Process in the SIWFS

09.023GPPMobile Application Part (MAP) specificationTS

The MAP process in the SIWFS to allocate and modify SIWFS resources for a mobile call is shown in figure 21.5/5. The MAP process invokes macros not defined in this subclause; the definitions of these macros can be found as follows:

Receive_Open_Ind see subclause 25.1.1.

Check_Confirmation see subclause 25.2.2.

21.5.3.1 Procedures for allocation of SIWFS resources

Successful outcome

When the MAP process receives a MAP_OPEN indication with the application context locInfoRetrieval, it checks it by invoking the macro Receive_Open_Ind.

If the macro takes the OK exit, the MAP process waits for a service indication.

If a MAP_PROVIDE_SIWFS_NUMBER service indication is received, the MAP process sends a Provide SIWFS number Info request to the call handling process in the SIWFS, and waits for a response. The Provide SIWFS number request contains the parameters received in the MAP_PROVIDE_SIWFS_NUMBER service indication.

If the call handling process in the SIWFS returns a Provide SIWFS number ack, the MAP process constructs a MAP_PROVIDE_SIWFS_NUMBER service response containing the routing information contained in the Provide SIWFS Number ack, constructs a MAP_DELIMITER service request, sends them to the VMSC and go to Wait_For_Modification state.

Earlier version MAP dialogue with the VMSC

If the macro Receive_Open_Ind takes the Vr exit, the MAP process returns to the idle state.

Dialogue opening failure

If the macro Receive_Open_Ind takes the Error exit, the MAP process returns to the idle state.

If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP process returns to the idle state.

If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle state.

Negative response from SIWFS call handling process

If the call handling process in the SIWFS returns a negative response the MAP process constructs a MAP_PROVIDE_SIWFS_NUMBER service response containing the appropriate error, constructs a MAP_CLOSE service request, sends them to the VMSC and returns to the idle state.

Call release

If the call handling process in the SIWFS indicates that the call has been aborted, the MAP process returns to the idle state. Any response from the VMSC will be discarded.

If the call handling process in the SIWFS indicates that the traffic channel has been released (i.e.call released by a user) a MAP_CLOSE_req is sent and the process is returned to the idle state.

Abort of VMSC dialogue

After the dialogoue with the VMSC has been established, the MAP servcie provider may abort the dialogue by issuing a MAP_P_ABORT indication, or the VMSC may send a MAP_U_ABORT indication or a MAP_CLOSE indication. In any of these cases, the MAP process returns to the idle state.

If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the dialogue with the VMSC, and returns to the idle state.

21.5.3.2 Process for modification of SIWFS resources initiated by the user

Successful outcome

If a MAP_SIWFS_SIGNALLING_MODIFY service indication is received, the MAP process sends an SIWFS signalling modify Info request to the call handling process in the SIWFS, and waits for a response. The SIWFS signalling modify request contains the parameters received in the MAP_SIWFS_SIGNALLING_MODIFY service indication.

If the call handling process in the SIWFS returns an SIWFS signalling modify ack, the MAP process constructs a MAP_SIWFS_SIGNALLING_MODIFY service response contained in the Provide SIWFS Number ack, send it to the VMSC and go to Wait_For_Modification state.

Negative response from SIWFS call handling process

If the call handling process in the SIWFS returns a negative response the MAP process constructs a MAP_SIWFS_SIGNALLING_MODIFY service response containing the appropriate error, send it to the VMSC and go to Wait_For_Modification state.

21.5.3.3 Process for modification of SIWFS resources initiated by the SIWFS

Successful Outcome

When the MAP process receives an SIWFS Signalling Modify request from the call handling process in the SIWF, it requests a dialogue with the VMSC whose identity is contained in the VMSC Signalling Modify request by sending a MAP_DELIMITER service request, requests resources in the VMSC using a MAP_SIWFS_SIGNALLING_MODIFY service request, the MAP process waits for a response from the VMSC.

If the MAP process receives a MAP_SIWFS_SIGNALLING_MODIFY service confirm from the VMSC, the MAP process invokes the macro Check_Confirmation to check the content of the confirm.

If the macro Check_Confirmation takes the OK exit, the MAP process sends an SIWFS Signalling Modify ack containing the response received from the VMSC to the call handling process in the SIWF and go to Wait_For_Modification state.

Error in MAP_SIWFS_SIGNALLING_MODIFY confirm

If the MAP_SIWFS_SIGNALLING_MODIFY service confirm contains a user error or a provider error, or the macro Check_Confirmation indicates that there is a data error, the MAP process sends an SIWFS Signalling Modify negative response to the call handling process in the SIWFS and go to Wait_For_Modification state.

Abort of SIWFS dialogue

During the time an answer is expected from the VMSC, the MAP service provider may abort the dialogue by issuing a MAP_P_ABORT indication, or the VMSC may send a MAP_U_ABORT indication or a MAP_CLOSE indication. In any of these cases, the MAP process sends an SIWFS Signalling Modify negative response to the call handling process in the SIWFS and returns to the idle state.

If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the dialogue with the VMSC, sends an SIWFS Signalling Modify negative response indicating system failure to the call handling process in the SIWFS and returns to the idle state.

Figure 21.5/5 (sheet 1 of 5): Process SRA_SIWFS

Figure 21.5/5 (sheet 2 of 5): Process SRA_SIWFS

Figure 21.5/5 (sheet 3 of 5): Process SRA_SIWFS

Figure 21.5/5 (sheet 4 of 5): Process SRA_SIWFS

Figure 21.5/5 (sheet 5 of 5): Process SRA_SIWFS