RESPONSE TO A NON ACCESS STRATUM MESSAGE

• US 20190124717A1
• Filed: 12/20/2018
• Published: 04/25/2019
• Est. Priority Date: 09/28/2010
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Choi, Noun, Faccin, Stefano, Chin, Chen Ho
• Granted Patent: US 10,743,366 B2
• Time in Patent Office: Days
• CPC Class Codes: H04W 36/0033 with transfer of context information
• CPC Class Codes: H04W 36/08 Reselecting an access point
• CPC Class Codes: H04W 36/24 Reselection being triggered by specific parameters
• CPC Class Codes: H04W 60/005 Multiple registrations, e.g. multihoming
• CPC Class Codes: H04W 76/30 Connection release
• CPC Class Codes: H04W 76/32 Release of transport tunnels
• CPC Class Codes: H04W 76/34 Selective release of ongoing connections
• CPC Class Codes: H04W 8/02 Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
• CPC Class Codes: H04W 84/045 using private Base Stations, e.g. femto Base Stations, home Node B

Abstract

A mobility management node in A core network receives a first Non Access Stratum (NAS) message via a second network element from a user equipment (UE), wherein the mobility management node stores a first identifying characteristic associated with at least one of a Local IP Access (LIPA) packet data network (PDN) connection or a selected IP traffic offload (SIPTO) PDN connection, the at least one of the LIPA PDN connection or the SIPTO PDN connection being via a first network element and for the UE. The mobility management node detects that the UE is connected to the second network element that is different from the first network element that has the first identifying characteristic, and in response to a condition that each PDN connection of the UE is a LIPA PDN connection or a SIPTO PDN connection, sends a second NAS message, the second NAS message including a cause code with a value that represents “No EPS Bearer Context Activated.”

Claims

1. A method in a core network communicatively connected to a radio access network (RAN) comprising a first network element and a second network element, comprising:

receiving, by a mobility management node in the core network, a first Non Access Stratum (NAS) message via the second network element from a user equipment (UE), wherein the mobility management node stores a first identifying characteristic associated with at least one of a Local IP Access (LIPA) packet data network (PDN) connection or a selected IP traffic offload (SIPTO) PDN connection, the at least one of the LIPA PDN connection or the SIPTO PDN connection being via the first network element and for the UE;

detecting, by the mobility management node, that the UE is connected to the second network element that is different from the first network element that has the first identifying characteristic, wherein the detecting comprises determining that the first NAS message is received via the second network element; and

in response to a condition that each PDN connection of the UE is a LIPA PDN connection or a SIPTO PDN connection, sending, by the mobility management node, a second NAS message, the second NAS message including a cause code with a value that represents “

No EPS Bearer Context Activated.”

2. The method of claim 1, wherein the second NAS message includes an indication to force the UE to perform a new attach procedure.

3. The method of claim 2, wherein the cause code with the value that represents “

No EPS Bearer Context Activated”

is to cause the UE to release context information of the UE and establish a new PDN connection.

4. The method of claim 1, wherein the receiving comprises receiving the first NAS message with a second identifying characteristic, the second identifying characteristic different from the first identifying characteristic.

5. The method of claim 4, wherein the first identifying characteristic comprises a closed identity group (CSG) identity associated with the first network element, and the second identifying characteristic comprises a second CSG identity associated with the second network element.

6. The method of claim 1, wherein the first NAS message is a Service Request message or an Extended Service Request message, and the second NAS message is a Service Reject message.

7. The method of claim 1, wherein the first NAS message is a one of a Tracking Area Update Request message, a Routing Area Update message, or a paging response message.

8. The method of claim 1, wherein the mobility management node is either a Mobility Management Entity (MME) or a Serving GPRS Support Node (SGSN).

9. The method of claim 1, wherein the first network element includes a Local Gateway (L-GW) that is associated with the at least one of the LIPA PDN connection or the SIPTO PDN connection.

10. A mobility management node for use in a core network communicatively connected to a first radio access network (RAN) comprising a first network element and a second network element, comprising:

a memory; and

at least one processor coupled to the memory and configured to;

receive a first Non Access Stratum (NAS) message via the second network element from a user equipment (UE), wherein the mobility management node is to store a first identifying characteristic associated with at least one of a Local IP Access (LIPA) packet data network (PDN) connection or a selected IP traffic offload (SIPTO) PDN connection, the at least one of the LIPA PDN connection or the SIPTO PDN connection being via the first network element and for the UE;

detect that the UE is connected to the second network element that is different from the first network element that has the first identifying characteristic, wherein the detecting comprises determining that the first NAS message is received via the second network element; and

in response to a condition that each PDN connection of the UE is a LIPA PDN connection or a SIPTO PDN connection, send a second NAS message, the second NAS message including a cause code with a value that represents “

No EPS Bearer Context Activated.”

11. The mobility management node of claim 10, wherein the second NAS message includes an indication to force the UE to perform a new attach procedure.

12. The mobility management node of claim 11, wherein the cause code with the value that represents “

No EPS Bearer Context Activated”

is to cause the UE to release context information of the UE and establish a new PDN connection.

13. The mobility management node of claim 10, wherein the receiving comprises receiving the first NAS message with a second identifying characteristic, the second identifying characteristic different from the first identifying characteristic.

14. The mobility management node of claim 13, wherein the first identifying characteristic comprises a closed identity group (CSG) identity associated with the first network element, and the second identifying characteristic comprises a second CSG identity associated with the second network element.

15. The mobility management node of claim 10, wherein the first NAS message is a Service Request message or an Extended Service Request message, and the second NAS message is a Service Reject message.

16. The mobility management node of claim 10, wherein the first NAS message is a one of a Tracking Area Update Request message, a Routing Area Update message, or a paging response message.

17. The mobility management node of claim 10, wherein the mobility management node is either a Mobility Management Entity (MME) or a Serving GPRS Support Node (SGSN).

18. The mobility management node of claim 10, wherein the first network element includes a Local Gateway (L-GW) that is associated with the at least one of the LIPA PDN connection or the SIPTO PDN connection.

19. A non-transitory machine-readable storage medium comprising instructions that upon execution cause a mobility management node in a core network communicatively connected to a first radio access network (RAN) comprising a first network element and a second network element, to:

receive a first Non Access Stratum (NAS) message via the second network element from a user equipment (UE), wherein the mobility management node is to store a first identifying characteristic associated with at least one of a Local IP Access (LIPA) packet data network (PDN) connection or a selected IP traffic offload (SIPTO) PDN connection, the at least one of the LIPA PDN connection or the SIPTO PDN connection being via the first network element and for the UE;

detect that the UE is connected to the second network element that is different from the first network element that has the first identifying characteristic, wherein the detecting comprises determining that the first NAS message is received via the second network element; and

in response to a condition that each PDN connection of the UE is a LIPA PDN connection or a SIPTO PDN connection, send a second NAS message, the second NAS message including a cause code with a value that represents “

No EPS Bearer Context Activated.”

20. The non-transitory machine-readable storage medium of claim 19, wherein the second NAS message includes an indication to force the UE to perform a new attach procedure, and the cause code with the value that represents “

No EPS Bearer Context Activated”

is to cause the UE to release context information of the UE and establish a new PDN connection.