Avoiding formation of a call loop resulting from handling of a mobile terminated call in parallel with a location update in a wireless communication network

• US 9,949,110 B2
• Filed: 09/16/2016
• Issued: 04/17/2018
• Est. Priority Date: 05/02/2013
• Status: Active Grant

• Current Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Original Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Inventors: Tian, Lu, Landais, Bruno
• Primary Examiner(s): LE, DANH C
• Application Number:
  US15/267,641
• Publication Number:
  US 20170006461A1
• Time in Patent Office: 578 Days
• Field of Search: 455433, 4555501, 455445, 370328
• CPC Class Codes: H04M 1/724 User interfaces specially adapted for cordless or mobile telephones
• CPC Class Codes: H04M 2207/187 combining circuit and packet-switched, e.g. GPRS
• CPC Class Codes: H04M 3/545 with loop avoiding arrangements
• CPC Class Codes: H04W 36/0022 for transferring data sessions between adjacent core network technologies
• CPC Class Codes: H04W 76/30 Connection release
• CPC Class Codes: H04W 8/06 Registration at serving network Location Register, VLR or user mobility server
• CPC Class Codes: H04W 8/12 between location registers or mobility servers
• CPC Class Codes: H04W 8/245 from a network towards a terminal
• CPC Class Codes: H04W 88/16 Gateway arrangements

Abstract

A call loop avoidance capability is provided for preventing formation of a call loop resulting from handling of a mobile terminated (MT) call in parallel with a location update for a mobile device (MD) in a wireless communication network. The call loop avoidance capability prevents formation of a call loop between an old mobility and call management entity (MCME) and a new MCME when delivery of an MT call to an MD is performed while the MD is in the process of moving from the old MCME to the new MCME using a location update procedure. An enhanced call routing procedure supports direct delivery of the MT call from the new MCME to the MD (rather than delivery of the MT call by the new MCME to the MD via the old MCME) in order to prevent formation of a call loop between the old MCME and the new MCME.

Claims

1. A mobility and call management entity (MCME), the MCME comprising:

a processor and a memory communicatively connected to the processor, the processor configured to;

send, from the MCME toward a second MCME, a routing information request message associated with delivery of a mobile terminated (MT) call to a mobile device (MD), the routing information request message comprising an indication of a gateway MCME for the MD; and

receive, at the MCME from the second MCME, a release message instructing the MCME to release resources of the MCME associated with the MD.

2. The MCME of claim 1, wherein the indication of the gateway MCME for the MD comprises a gateway MCME address of the gateway MCME for the MD.

3. The MCME of claim 2, wherein the gateway MCME address of the gateway MCME for the MD identifies the second MCME.

4. The MCME of claim 1, wherein the routing information request message further comprises a Mobile Terminating Roaming Forwarding (MTRF) indicator.

5. The MCME of claim 1, wherein the routing information request message further comprises a call reference number.

6. The MCME of claim 1, wherein the processor is configured to:

release, by the MCME based on the release message, the resources of the MCME associated with the MD; and

send, from the MCME toward the second MCME, a release complete message indicative that the MCME has released the resources of the MCME associated with the MD.

7. The MCME of claim 1, wherein the processor is configured to:

receive, from the second MCME, a negative routing information response message.

8. The MCME of claim 7, wherein the negative routing information response message comprises an abort message.

9. The MCME of claim 1, wherein the processor is configured to:

prior to sending the routing information request message;

receive, from a home location register, a message comprising an indication of the gateway MCME for the MD.

10. The MCME of claim 9, wherein the message comprising the indication of the gateway MCME for the MD further comprises a call reference number.

11. The MCME of claim 9, wherein the message comprising the indication of the gateway MCME for the MD comprises a Mobile Application Part (MAP) Provide Roaming Number (PRN) message.

12. The MCME of claim 9, wherein the processor is configured to:

send, toward the home location register, an acknowledgement message.

13. The MCME of claim 12, wherein the acknowledgment message comprises a Mobile Station Roaming Number (MSRN) for the MD.

14. The MCME of claim 12, wherein the acknowledgment message comprises a Mobile Application Part (MAP) Provide Roaming Number (PRN) acknowledgment message.

15. The MCME of claim 1, wherein the MCME comprises a first Mobile Switching Center (MSC)/Visiting Location Register (VLR) element and the second MCME comprises a second MSC/VLR element.

16. A method, comprising:

sending, from a first mobility and call management entity (MCME) toward a second MCME, a routing information request message associated with delivery of a mobile terminated (MT) call to a mobile device (MD), the routing information request message comprising an indication of a gateway MCME for the MD; and

receiving, at the first MCME from the second MCME, a release message instructing the MCME to release resources of the MCME associated with the MD.

17. An apparatus, comprising:

a processor and a memory communicatively connected to the processor, the processor configured to;

receive, at a first mobility and call management entity (MCME) from a second MCME, a routing information request message associated with delivery of a mobile terminated (MT) call to a mobile device (MD); and

determine, at the first MCME based on the routing information request message, whether the first MCME performs a gateway MCME function for the MT call to the MD.

18. The apparatus of claim 17, wherein, to determine whether the first MCME performs the gateway MCME function for the MT call to the MD, the processor is configured to:

determine whether the routing information request message includes an indication of the gateway MCME.

19. The apparatus of claim 17, wherein the first MCME has an MCME address associated therewith, wherein, to determine whether the first MCME performs the gateway MCME function for the MT call to the MD, the processor is configured to:

determine whether an address of the gateway MCME for the MD that is indicated in the routing information request message matches the MCME address associated with the first MCME.

20. The apparatus of claim 17, wherein the processor is configured to:

based on a determination that the first MCME performs the gateway MCME function for the MT call to the MD;

initiate, from the first MCME toward the second MCME, release of the MT call to the MD; and

initiate, from the first MCME, delivery of the MT call to the MD.