21.10 Resource Management
29.0023GPPMobile Application Part (MAP) specificationRelease 17TS
21.10.1 General
The message flow for successful release of resources is shown in figure 21.10/1.
1) I_IAM (Note 1)
2) MAP_SEND_ROUTING_INFORMATION_req/ind
3) MAP_PROVIDE_ROAMING_NUMBER_req/ind
4) I_REL (Note 1)
5) MAP_PROVIDE_ROAMING_NUMBER_rsp/cnf
6) MAP_SEND_ROUTING_INFORMATION_rsp/cnf
7) MAP_RELEASE_RESOURCES (Note 2)
NOTE 1: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the MSCs. For further details on the TUP and ISUP procedures refer to the following ITU-T Recommendations & ETSI specification:
– Q.721‑725 ‑ Telephone User Part (TUP);
– ETS 300 356-1 ‑ Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 2 for the international interface; Part 1: Basic services.
NOTE 2: Services printed in italics are optional.
Figure 21.10/1: Message flow for early release of resources
21.3.2 Process in the GMSC
The MAP process in the GMSC to release resources is shown in figure 21.10/2. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows:
Receive_Open_Cnf see clause 25.1.2;
Check_Confirmation see clause 25.2.2.
21.3.3 Process in the VMSC
The MAP process in the VMSC to handle a request for the GMSC to release resources is shown in figure 21.10/3. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows:
Receive_Open_Ind see clause 25.1.1;
Figure 21.10/2: Process Release Resources_GMSC
Figure 21.10/3: Process Release Resources_VMSC