System and method for managing call routing in a network environment including IMS
View Patent ↗In one embodiment, a scheme is disclosed for managing call routing in a network environment including a circuit-switched (CS) network and an IP multimedia subsystem (IMS) network. When a call is originated by a user equipment (UE) device in the CS network, call information associated with the call is provided to a call continuity control function (CCCF) network node disposed in the IMS network. At the CCCF node, a pool of E.164 numbers are maintained as IP multimedia routing numbers (IMRNs) which are mapped to or otherwise associated with called party numbers. The CCCF node dynamically allocates a select IMRN with respect to a called party number received from the UE device and returns it to the UE device. The dynamically allocated IMRN is then utilized for routing the call towards the called party.
1. A method for call routing by a network node disposed in a network environment including a circuit-switched (CS) network and an Internet Protocol (IP) multimedia subsystem (IMS) network, the method comprising:
receiving a message for setting up a mobile-originated call;
generating an IP Multimedia Routing Number (IMRN) for purposes of setting up the mobile-originated call;
sending the IMRN to a mobile switching center (MSC);
receiving a subsequent message containing the IMRN; and
setting up the mobile-originated call using an original called number that maps to the IMRN, wherein the setting up of the mobile-originated call comprises inserting a CallerID by said IMS.
2. The method as recited in claim 1 , wherein the network node comprises a call continuity control function (CCCF) portion.
3. The method as recited in claim 1 , wherein the subsequent message is a SIP INVITE message.
4. The method as recited in claim 1 , wherein the mobile-originated call was originated by a user equipment (UE) device in the CS network.
5. The method as recited in claim 4 , wherein the UE device is configured to operate in CS domain and IMS domain modes of functionality.
6. The method as recited in claim 1 , wherein the subsequent message was routed to the network node because the mobile-originated call may require call continuity.
7. The method as recited in claim 1 , wherein the CallerID is inserted upon determining that the subsequent message did not include a CallerID.
8. The method as recited in claim 7 , wherein the setting up of the mobile-originated call further comprises inserting privacy options.
9. The method as recited in claim 1 , wherein the IMRN was allocated by the network node.
10. The method as recited in claim 1 , wherein the IMRN was dynamically allocated.
11. The method as recited in claim 1 , further comprising quarantining the IMRN upon releasing it to a pool of IMRNs for future use.
12. The method as recited in claim 1 , wherein the IMRN comprises an E.164 number.
13. The method as recited in claim 1 , further comprising verifying that the IMRN received in the subsequent message is valid.
14. The method as recited in claim 1 , wherein the IMRN is generated by selecting an E.164 number from a pool of numbers.
15. A network node configured for facilitating call routing in a network environment including a circuit-switched (CS) network and an Internet Protocol (IP) multimedia subsystem (IMS) network, the network node comprising:
a component configured to process a message received with respect to setting up a mobile-originated call;
a component configured to generate an IP Multimedia Routing Number (IMRN) for purposes of setting up the mobile-originated call;
a component configured to send the IMRN to a mobile switching center (MSC);
a component configured to receive and process a subsequent message containing the IMRN; and
a component configured to set up the mobile-originated call using an original called number that maps to the IMRN, wherein the setting up of the mobile-originated call comprises inserting a CallerID by said IMS.
16. The network node as recited in claim 15 , wherein the subsequent message is a SIP INVITE message.
17. The network node as recited in claim 15 , wherein the mobile-originated call was originated by a user equipment (UE) device in the CS network.
18. The network node as recited in claim 17 , wherein the UE device is configured to operate in CS domain and IMS domain modes of functionality.
19. The network node as recited in claim 15 , wherein the CallerlD is inserted upon determining that the subsequent message did not include a CallerlD.
20. The network node as recited in claim 19 , wherein the setting up of the mobile-originated call further comprises inserting privacy options.
21. The network node as recited in claim 15 , wherein the IMRN was dynamically allocated.
22. The network node as recited in claim 15 , further comprising a component configured for quarantining the IMRN upon releasing it to a pool of IMRNs for future use.
23. The network node as recited in claim 15 , wherein the IMRN comprises an E.164 number.
24. The network node as recited in claim 15 , further comprising a component configured to verify that the IMRN received in the subsequent message is valid.
25. The network node as recited in claim 15 , wherein the IMRN is generated by selecting an E.164 number from a pool of numbers.