Avoiding unlimited number of unsuccessful location update or packet data connection establishment attempts

• US 9,392,566 B2
• Filed: 11/22/2012
• Issued: 07/12/2016
• Est. Priority Date: 03/14/2012
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Tranberg, Hkan, Olsson, Lasse
• Primary Examiner(s): Qureshi, Afsar M
• Application Number:
  US14/384,951
• Publication Number:
  US 20150029978A1
• Time in Patent Office: 1,328 Days
• Field of Search: 370/329
• US Class Current: 1/1
• CPC Class Codes: H04W 60/04 using triggered events
• CPC Class Codes: H04W 60/06 De-registration or detaching
• CPC Class Codes: H04W 76/12 Setup of transport tunnels
• CPC Class Codes: H04W 76/18 Management of setup rejection or failure
• CPC Class Codes: H04W 88/16 Gateway arrangements

Abstract

The application relates to the procedures Routing Area Update RAU in UTRAN and Tracking Area Update TAU in LTE. Furthermore, it relates to PDP context procedure in UTRAN as well as PDN connection procedure in LTE. In the current RAU procedure, a SGSN, which fails to update the Routing Area, e.g. because it receives the DNS return error, sends a RAU Reject with the cause code CC#17 indicating a network failure back to the user equipment (114b). The cause code CC#17 in the RAU Reject causes the user equipment to send a new RAU Request. Thus, the user equipment is stuck in a loop of sending a RAU Request and receiving a RAU Reject. This problem is solved by the present application in that SGSN keeps track of the number of rejections when doing RAU. When the number of rejections is above a certain threshold, the SGSN will send a RAU Reject with cause code CC#10 to the user equipment (115b), whereby the cause code CC#10 indicates implicit detach of the user equipment. In other words, the cause code is changed from CC#17 to CC#10 and in order to avoid further looping. The same principle is applied to TAU in LTE as well as to PDP procedures in UTRAN and LTE.

Claims

1. A method in a first network node for handling a user equipment in a communication network, wherein the first network node is connected to the user equipment, the method comprising:

receiving a request message from the user equipment, which request message is a Routing Area Update, RAU, message or a Tracking Area Update, TAU, message, which RAU or TAU message is a request for an update related to an area to which the user equipment has moved, or

which request message is an activate Packet Data Protocol, PDP, context request message or an activate Packet Data Network, PDN, connection request message, which PDP context request or activate PDN connection request message is a request for transmitting data in the communication network;

obtaining information about rejection of the request message;

increasing a parameter indicating a number of rejections associated with the user equipment based on the obtained information; and

transmitting, to the user equipment, instructions to detach the user equipment from the first network node when the parameter is above a threshold, wherein the instruction to detach the user equipment is comprised in a RAU reject message or a TAU reject message when the received request message is a PDP context request or activate PDN connection request message; and

wherein the instructions to detach the user equipment is comprised in a detach request message when the received request message is an activate PDP context request or activate PDN connection request message; and

wherein the first network node is a Serving General packet radio service Support Node, SGSN, or a Mobility Management Entity, MME, or a combined SGSN and MME.

2. The method according to claim 1, further comprising:

transmitting a reject message to the user equipment when the parameter is below the threshold.

3. The method according to claim 2, wherein the reject message comprises an information indicating a first cause of the rejection, and wherein the instructions to detach the user equipment comprises information indicating a second cause of the rejection, which second cause is different from the first cause.

4. The method according to claim 3, wherein the first cause indicates a failure of the communication network, and wherein the second cause indicates detach of the user equipment from the first network node.

5. The method according to claim 1, wherein the obtaining information about rejection of the request message further comprises:

receiving information about the rejection from a second network node, wherein the second network node is a Domain Name Server, DNS or a Gateway General packet radio service Support Node, GGSN or a Serving GateWay, SGW or a Packet data network GateWay, PGW, or a radius server;

or

determining that the request message should be rejected.

6. The method according to claim 1, further comprising:

transmitting information indicating the request message to a second network node.

7. The method according to claim 1, further comprising:

clearing the parameter when a time parameter associated with the received rejection information is above a limit.

8. The method according to claim 1, further comprising:

receiving an attach request message from the user equipment when the user equipment has been detached.

9. The method according to claim 1, wherein the information about rejection is obtained by receipt from a Domain Name Server, DNSor internally within the first network node or from a cooperating Serving General packet radio service Support Node, SGSN, when the received request message is a RAU or TAU message and the instructions to detach is comprised in a RAU or TAU reject message.

10. The method according to claim 1, wherein the information about rejection is obtained by receipt from a Gateway General packet radio service Support Node, GGSN, or a Serving GateWay, SGW, or a Packet data network GateWay, PGW, or a radius server, when the received request message is an activate PDP context request or activate PDN connection request message and the instructions to detach is comprised in a detach request message.

11. The method according to claim 1, wherein the information about rejection of the request message is obtained internally within the first network node when the received request message is an activate PDP context request or activate PDN connection request message and the instructions to detach is comprised in a detach request message.

12. A first network node for handling a user equipment in a communication network, wherein the first network node is configured to be connected to the user equipment, the first network node comprising:

a receiver configured to;

receive a request message from the user equipment, which request message is a Routing Area Update, RAU, message or a Tracking Area Update, TAU, message, which RAU or TAU message is a request for an update related to an area to which the user equipment is configured to move, or which request message is an activate Packet Data Protocol, PDP, context request message or an activate Packet Data Network, PDN, connection request message, which PDP context request or activate PDN connection request message is a request for transmitting data in the communication network; and

to

obtain information about rejection of the request message;

a processor configured to increase a parameter indicating a number of rejections associated with the user equipment based on the obtained information; and

a transmitter configured to transmit, to the user equipment, instructions to detach the user equipment from the first network node when the parameter is above a threshold,

wherein the instruction to detach the user equipment is comprised in a RAU reject message or a TAU reject message when the received request message is a PDP context request or activate PDN connection request message; and

wherein the instructions to detach the user equipment is comprised in a detach request message when the received request message is an activate PDP context request or activate PDN connection request message; and

wherein the first network node is a Serving General packet radio service Support Node, SGSN, or a Mobility Management Entity, MME, or a combined SGSN and MME.

13. The first network node according to claim 12, wherein the transmitter is further configured to transmit a reject message to the user equipment when the parameter is below a threshold.

14. The first network node according to claim 13, wherein the reject message comprises an information indicating a first cause of the rejection, and wherein the instructions to detach the user equipment comprises information indicating a second cause of the rejection, which second cause is different from the first cause.

15. The first network node according to claim 12, wherein the first cause indicates a failure of the communication network, and wherein the second cause indicates detach of the user equipment from the first network node.

16. The first network node according to claim 12, wherein the receiver is further configured to receive information about the rejection from a second network node, wherein the second network node is a Domain Name Server, DNS, or a Gateway General packet radio service Support Node, GGSN, or a Serving GateWay, SGW, or a Packet data network GateWay, PGW, or a radius server;

and

wherein the processor is further configured to determine that the request message should be rejected.

17. The first network node according to claim 12, wherein the transmitter is further configured to transmit information indicating the request message to a second network node.

18. The first network node according to claim 12, wherein the processor is further configured to clear the parameter when a time parameter associated with the rejection information is above a limit.

19. The first network node according to claim 12, wherein the receiver is further configured to receive an attach request message from the user equipment when the user equipment has been detached.

20. The first network node according to claim 13, wherein the receiver is further configured to obtain the information about rejection by receipt from a Domain Name Server, DNS, or internally within the first network node or by receipt from a cooperating Serving General packet radio service Support Node, SGSN when the received request message is a RAU or TAU message and the instructions to detach is comprised in a RAU or TAU reject message.

21. The first network node according to claim 12, wherein the receiver is further configured to obtain the information about rejection of the request message by receipt of the information from a Gateway General packet radio service Support Node, GGSN, or a Serving GateWay, SGW, or a Packet data network GateWay, PGW, or a radius server when the received request message is an activate PDP context request or activate PDN connection request message and the instructions to detach is comprised in a detach request message.

22. The first network node according to claim 12, wherein the receiver is further configured to obtain the information about rejection of the request message internally within the first network node when the received request message is an activate PDP context request or activate PDN connection request message and the instructions to detach is comprised in a detach request message.