21.6.3 Status Reporting
29.0023GPPMobile Application Part (MAP) specificationRelease 17TS
The message flows for reporting the status of a subscriber are shown in figures 21.6/2 and 21.6/3.
1) MAP_STATUS_REPORT_req/ind
2) MAP_STATUS_REPORT_rsp/cnf
Figure 21.6/2: Message flow for status reporting, when monitoring continues in the VLR
1) MAP_STATUS_REPORT_req/ind
2) MAP_STATUS_REPORT_rsp/cnf
3) MAP_SET_REPORTING_STATE_req/ind
4) MAP_SET_REPORTING_STATE_rsp/cnf
Figure 21.6/3: Message flow for status reporting, when monitoring stops
The MAP_SET_REPORTING_STATE request is used to stop monitoring in the VLR. If the HLR requires the VLR to continue monitoring, it closes the dialogue without sending a MAP_SET_REPORTING_STATE request.
21.6.3.1 Process in the VLR
The MAP process in the VLR to send a status report to the HLR is shown in figure 21.6/10. 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.
This process can be used to report:
– an event, such as the user becoming free, or
– the result of a CCBS call attempt
to the HLR
21.6.3.2 Process in the HLR
The MAP process in the HLR to handle a status report is shown in figure 21.6/11. 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;
It is an implementation option whether to send the MAP_DELIMITER request before invoking the macro Set_Reporting_State_HLR.
The macro Receive_Status_Report_HLR is shown in figure 21.6/12.
The macro Set_Reporting_State_HLR is shown in figure 21.6/13. The macro invokes a macro not defined in this clause; the definition of this macro can be found as follows:
Check_Confirmation see clause 25.2.2.