Technique for connection attempt handling in a circuit switched fallback situation
A technique for handling mobile terminating connection attempts for a mobile terminal for which a change of an association from a first routing node to a second routing node is accompanied by a Circuit Switched (CS) fallback is described. In one exemplary embodiment, a method may be performed by a Circuit Switched Fallback Interworking Function (CSFB-IWF) for handling mobile terminating connection attempts for a mobile terminal for which a change of an association from the CSFB-IWF to a Mobile Switching Center (MSC) is accompanied by a Circuit Switched Fallback (CSFB). The method may include receiving a mobile terminating connection attempt to the mobile terminal. In response to receiving the mobile terminating connection attempt, the method may include paging the mobile terminal using a Mobility Management Entity (MME). In response to paging the mobile terminal, the method may include triggering the mobile terminal to initiate a CSFB procedure. Further, the method may include determining an identity of the MSC based on a message received by the CSFB-IWF from the MSC. Also, the method may include transmitting, to the MSC, a second mobile terminating connection attempt for a CS connection to the mobile terminal.
1. A method performed by a Circuit Switched Fallback Interworking Function (CSFB-IWF) for handling mobile terminating connection attempts for a mobile terminal for which a change of an association from the CSFB-IWF to a Mobile Switching Center (MSC) is accompanied by a Circuit Switched Fallback (CSFB), comprising:
receiving a mobile terminating connection attempt to the mobile terminal;
in response to receiving the mobile terminating connection attempt, paging the mobile terminal using a Mobility Management Entity (MME);
in response to paging the mobile terminal, triggering the mobile terminal to initiate a CSFB procedure;
determining an identity of the MSC based on a message received by the CSFB-IWF from the MSC; and
transmitting, to the MSC, a second mobile terminating connection attempt for a CS connection to the mobile terminal.
2. The method of claim 1 , wherein the identity of the MSC is determined based on a Mobile Application Part (MAP) Send_Identification message received by the CSFB-IWF from the MSC.
3. The method of claim 1 , wherein the identity of the MSC is given by a network address.
4. The method of claim 1 , wherein the mobile terminal is registered in the MSC using a dedicated interface to the MME.
5. The method of claim 1 , wherein the MSC lacks a dedicated interface to an MME.
6. The method of claim 1 , wherein the MSC lacks support for CSFB functionality.
7. The method of claim 1 , further comprising:
in response to determining the identity of the MSC, requesting a roaming number for the mobile terminal from the MSC.
8. A Circuit Switched Fallback Interworking Function (CSFB-IWF) for handling mobile terminating connection attempts for a mobile terminal for which a change of an association from the CSFB-IWF to a Mobile Switching Center (MSC) is accompanied by a Circuit Switched Fallback (CSFB), comprising:
a processor operationally coupled to a memory, wherein the processor and memory are configured to:
receive a mobile terminating connection attempt to the mobile terminal;
in response to receiving the mobile terminating connection attempt, page the mobile terminal using a Mobility Management Entity (MME);
in response to paging the mobile terminal, trigger the mobile terminal to initiate a CSFB procedure;
determine an identity of the MSC based on a message received by the CSFB-IWF from the MSC; and
transmit, to the MSC, a second mobile terminating connection attempt for a CS connection to the mobile terminal.
9. The CSFB-IWF of claim 8 , wherein the identity of the MSC is determined based on a Mobile Application Part (MAP) Send_Identification message received by the CSFB-IWF from the MSC.
10. The CSFB-IWF of claim 8 , wherein the identity of the MSC is given by a network address.
11. The CSFB-IWF of claim 8 , wherein the mobile terminal is registered in the MSC using a dedicated interface to the MME.
12. The CSFB-IWF of claim 8 , wherein the MSC lacks a dedicated interface to an MME.
13. The CSFB-IWF of claim 8 , wherein the MSC lacks support for CSFB functionality.
14. The CSFB-IWF of claim 8 , wherein the processor and memory are further configured to:
in response to determining the identity of the MSC, request a roaming number for the mobile terminal from the MSC.
15. A non-transitory computer-readable storage medium that stores computer-executable instructions for handling mobile terminating connection attempts for a mobile terminal for which a change of an association from a Circuit Switched Fallback Interworking Function (CSFB-IWF) to a Mobile Switching Center (MSC) is accompanied by a Circuit Switched Fallback (CSFB), the computer-executable instructions, when executed by a processor of the CSFB-IWF, causes the CSFB-IWF to:
receive a mobile terminating connection attempt to the mobile terminal;
page, in response to receipt of the mobile terminating connection attempt, the mobile terminal using a Mobility Management Entity (MME);
trigger the mobile terminal to initiate a CSFB procedure, in response to page the mobile terminal;
determine an identity of the MSC based on a message received by the CSFB-IWF from the MSC; and
transmit, to the MSC, a second mobile terminating connection attempt for a CS connection to the mobile terminal.
16. The non-transitory computer-readable storage medium of claim 15 , wherein the identity of the MSC is determined based on a Mobile Application Part (MAP) Send_Identification message received by the CSFB-IWF from the MSC.
17. The non-transitory computer-readable storage medium of claim 15 , wherein the identity of the MSC is given by a network address.
18. The non-transitory computer-readable storage medium of claim 15 , wherein the mobile terminal is registered in the MSC using a dedicated interface to the MME.
19. The non-transitory computer-readable storage medium of claim 15 , wherein the MSC lacks a dedicated interface to an MME.
20. The non-transitory computer-readable storage medium of claim 15 , wherein the MSC lacks support for CSFB functionality.
21. The non-transitory computer-readable storage medium of claim 15 , wherein the computer-executable instructions, when executed by the processor of the CSFB-IWF, further causes the CSFB-IWF to:
in response to determining the identity of the MSC, request a roaming number for the mobile terminal from the MSC.