6 Dialogue handling on the SSAP interface

29.0133GPPApplication Service Element (ASE) and Mobile Application Part (MAP) protocolsRelease 17Signalling interworking between ISDN supplementary servicesTS

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

The dialogue handling on the SSAP interface and the mapping between the corresponding TC transaction sublayer messages on the MAP D and SSAP interfaces is described. The diagrams show the general principle of dialogue handling. Specific message flows depend on the dynamics of the application in the network elements, see GSM 03.93 and GSM 09.02.

6.1 Dialogue Beginning

6.1.1 CCBS Request Invocation

Figure 6.1: Signalling flow for CCBS REQUEST INVOCATION

The CCBS Request invocation is carried by TC-BEGIN. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.1.

6.2 Dialogue Continuation

6.2.1 CCBS Request Result

Figure 6.2: Signalling flow for CCBS Request Result

The CCBS Request Result is carried by TC-CONTINUE. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.3.

6.2.2 CCBS Remote User Free Invocation

Figure 6.3: Signalling flow for Remote User Free Invocation

The CCBS Remote User Free Invocation is carried by TC-CONTINUE. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.3.

6.2.3 CCBS Suspend Invocation

NOTE 1 For conditions leading to a request being suspended, see GSM 03.93

Figure 6.4: Signalling flow for CCBS Suspend Invocation (RemoteUserFree_Result)

NOTE 1 For conditions leading to a request being suspended, see GSM 03.93

Figure 6.5: Signalling flow for CCBS Suspend Invocation (RemoteUserFree_Error)

The CCBS Suspend Invocation is carried by TC-CONTINUE. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.2

6.2.4 CCBS Resume Invocation

NOTE 1 For conditions leading to a request being resumed, see GSM 03.93

Figure 6.6: Signalling flow for CCBS Resume Invocation

The CCBS Resume Invocation is carried by TC-CONTINUE. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.2.

6.3 Dialogue End

6.3.1 Normal dialogue end

NOTE 1 If the monitoring function is active in VLR A and all outstanding CCBS Requests have been deactivated, the HLR A sends SetReportingState to deactivate the monitoring function (see GSM 03.93).

Figure 6.7: Signalling flow for normal dialogue end

The normal ending of CCBS dialogue from the B-side is carried by TC-END. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.3.

6.3.2 CCBS Cancel Invocation (from A-side)

NOTE 1 Where all outstanding CCBS Requests have been deactivated, CCBS Cancel is sent to each corresponding Destination Network B with the appropriate Destination Network B E.164 Called Party Address (see GSM 03.93, GSM 04.93).

Figure 6.8: Signalling flow for CCBS Cancel Invocation (from A-side)

The CCBS Cancel Invocation from the A-side is carried by TC-END. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.2.

6.3.3 CCBS Cancel Invocation (from B-side)

NOTE 1: If the monitoring function is active in VLR A and all outstanding CCBS Requests have been deactivated, the HLR A sends SetReportingState to deactivate the monitoring function (see GSM 03.93).

Figure 6.9: Signalling flow for CCBS Cancel Invocation (from B-side)

The CCBS Cancel Invocation from the B-side is carried by TC-END. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.3.

6.3.4 CCBS Request Error

Figure 6.10: Signalling flow for CCBS Request Error

The CCBS Request Error is carried by TC-END. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.3.