Normal 2G Call Flow

flow of a normal 2G call.

Figure 1 Intra-MSC call flow
As shown in Figure 1, Px refers to the measurement point of the originating side and Qx refers to the measurement point of the
terminating side.

Caller:

P1, P2, P3, P4, P5, P6, P7

Callee:

Q1, Q2, Q3, Q4, Q5

Description of the Signaling Flow

The signaling flow of an intra-MSC 2G call is as follows:

1. The MS-O (BSC on the caller side) sends a CM service request message carrying the cell information, service type, user ID,
and authentication parameters about the MS-O to the MSC.
2. The authentication and encryption flow is started on the caller side. In this process, the MSC may need to obtain the
authentication set from the HLR/AUC. For details, see 2G Authentication and Encryption.
3. If the encryption process is not started after the authentication process ends, the MSC/VLR sends a CM service accept
message to notify the MS-O that the service access request has been accepted. If the encryption process is started after the
authentication process ends, it indicates that the service access request has been accepted by the MSC/VLR; thus, the
MSC/VLR does not need to send the CM service accept message, and the MS-O directly sends a Setup message carrying the
called number and the bearer capability of the MS-O to the MSC/VLR.
4. Upon receipt of the data about the MS-O, the MSC/VLR determines whether the call can continue based on the service type
and the subscription data about the MS-O. If the call can continue, the MSC/VLR returns a Call proceeding message to the
MS-O.
5. The MSC analyzes the called number, locates the HLR based on the called number, and then sends a
MAP_SEND_ROUTING_INFORMATION_REQ message to the HLR.
6. The HLR queries the VLR serving the MS-T based on the IMSI of the MS-T, and then sends a
MAP_PROVIDE_ROAMING_NUMBER_IND message to this VLR to request an MSRN.
7. The VLR allocates an MSRN for the MS-T, and then returns a MAP_PROVIDE_ROAMING_NUMBER_RSP message carrying
the MSRN to the HLR.
8. The HLR sends a MAP_SEND_ROUTING_INFORMATION_CNF message carrying the MSRN to the MSC/VLR serving the
MS-O.
9. The MSC sends a PAGING message to the MS-T through the BSC-T, and waits for a paging response.
10. The bearer establishment flow on the caller side is started. For details, see Bearer Establishment Flow (TDM-enabled A
Interface).
11. If the paging is successful, the MS-T sends a PAGING RESPONSE message to the BSC-T, which transparently forwards the
message to the MSC.
12. The authentication and encryption flow is started on the callee side, which is the same as that flow on the caller side.
13. The MSC/VLR sends a Setup message to the MS-T to set up the call.
14. The MS-T responds with a CALL CONFIRMED message to accept the call.
15. The MSC/VLR establishes the user plane bearer on the callee side in the same way as establishing the bearer on the caller
side.
16. The callee is alerted and the MS-T sends an Alerting message to the MSC/VLR. Upon receipt of the message, the MSC/VLR
also sends an Alerting message to the MS-O.
17. The MSC/VLR sends a MOD REQ message, instructing the MGW to play the ringback tone.
18. The MGW returns a MOD REPLY message to the MSC/VLR and plays the ringback tone.
19. The callee answers the call and the MS-T sends a Connect message to the MSC/VLR.
20. Upon receipt of the Connect message, the MSC/VLR sends a MOD REQ message, instructing the MGW to stop playing the
ringback tone.
21. The MGW returns a MOD REPLY message to the MSC/VLR and stops playing the ringback tone.
22. The MSC/VLR sends a Connect message to the MS-O.
23. The MS-O sends a Connect acknowledge message to the MSC/VLR. The MSC/VLR transparently forwards this message to
the MS-T. Then, the call is established.
24. The caller and the callee start the conversation.
25. After a period of time, the MS-O starts the call release flow. For details, see Bearer Release Flow (TDM-enabled A Interface).