METHOD AND APPARATUS FOR RELEASING CONNECTION WITH LOCAL GW WHEN UE MOVES OUT OF THE RESIDENTIAL/ENTERPRISE NETWORK COVERAGE

• US 20180310218A1
• Filed: 06/07/2018
• Published: 10/25/2018
• Est. Priority Date: 09/28/2010
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Chin, Chen Ho, Choi, Noun, Faccin, Stefano
• Granted Patent: US 10,701,611 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04W 36/0022 for transferring data sessions between adjacent core network technologies
• CPC Class Codes: H04W 36/32 by location or mobility data, e.g. speed data
• CPC Class Codes: H04W 36/38 by fixed network equipment
• CPC Class Codes: H04W 48/08 Access restriction or access information delivery, e.g. discovery data delivery signalling during connection H04W76/00
• CPC Class Codes: H04W 64/003 locating network equipment
• CPC Class Codes: H04W 74/006 in the downlink, i.e. towards the terminal
• CPC Class Codes: H04W 76/30 Connection release
• CPC Class Codes: H04W 8/04 Registration at HLR or HSS [Home Subscriber Server]
• CPC Class Codes: H04W 8/082 for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
• CPC Class Codes: H04W 84/045 using private Base Stations, e.g. femto Base Stations, home Node B
• CPC Class Codes: H04W 88/02 Terminal devices
• CPC Class Codes: H04W 88/16 Gateway arrangements

Abstract

In some examples, a method in a core network communicatively connected with a first radio access network (RAN) comprising a first network element, and a second RAN comprising a second network element, includes receiving a first Non Access Stratum (NAS) message via the second network element from a User Equipment (UE), where the UE has, with the first network element, a selected IP traffic offload (SIPTO) PDN connection. 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 a first identifying characteristic, where the detecting comprises determining that the first NAS message is received with a second identifying characteristic of the second network element different from the first identifying characteristic associated with the SIPTO PDN connection.

Claims

1. A method in a core network communicatively connected with a first radio access network (RAN) comprising a first network element, and a second RAN comprising 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 UE has, with the first network element, a selected IP traffic offload (SIPTO) PDN connection;

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 a first identifying characteristic, wherein the detecting comprises determining that the first NAS message is received with a second identifying characteristic of the second network element different from the first identifying characteristic associated with the SIPTO PDN connection, the first identifying characteristic stored at the mobility management node; and

in response to the determining that the first NAS message is received with the second identifying characteristic of the second network element different from the first identifying characteristic;

determining that the UE has only a SIPTO PDN connection;

in response to determining that the UE has only a SIPTO PDN connection, sending, by the mobility management node, a second NAS message causing the UE to perform a new attach procedure, wherein the second NAS message includes at least one of an indication to force the UE to perform the new attach procedure, and a cause code with a value that represents at least one of “

Implicitly Detached” and

“

No EPS Bearer Context Activated.”

2. The method of claim 1, wherein the first and second identifying characteristics comprise first and second closed subscriber group (CSG) identities.

3. The method of claim 1, wherein the first and second identifying characteristics comprise first and second Radio Access Technology (RAT) types.

4. The method of claim 1, wherein the first and second identifying characteristics comprise first and second cell identifiers.

5. The method of claim 1, wherein the first NAS message comprises a TRACKING AREA UPDATE REQUEST message, and the second NAS message comprises a TRACKING AREA UPDATE REJECT message.

6. The method of claim 1, wherein the first NAS message comprises a SERVICE REQUEST message, and the second NAS message comprises a SERVICE REJECT message.

7. The method of claim 1, further comprising storing the first identifying characteristic in a memory of the mobility management mode.

8. The method of claim 1, where the second identifying characteristic indicates that there is no service continuity for the SIPTO PDN connection at a cell in the second RAN.

9. The method of claim 8, where when the second identifying characteristic indicates that there is no service continuity for the SIPTO PDN connection at the cell in the second RAN when the cell in the second RAN is a CSG cell having a second CSG identity that is different from a first CSG identity associated with a cell in the first RAN, or (2) that the cell in the second RAN does not have an associated CSG identity.

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

at least one processor configured to;

receive a first Non Access Stratum (NAS) message via the second network element from a User Equipment (UE), wherein the UE has, with the first network element, a selected IP traffic offload (SIPTO) PDN connection;

detect that the UE is connected to the second network element that is different from the first network element that has a first identifying characteristic, wherein the detecting comprises determining that the first NAS message is received with a second identifying characteristic of the second network element different from the first identifying characteristic associated with the SIPTO PDN connection, the first identifying characteristic stored at the mobility management node; and

in response to the determining that the first NAS message is received with the second identifying characteristic of the second network element different from the first identifying characteristic;

determine that the UE has only a SIPTO PDN connection;

in response to determining that the UE has only a SIPTO PDN connection,

send a second NAS message causing the UE to perform a new attach procedure, wherein the second NAS message includes at least one of an indication to force the UE to perform the new attach procedure, and a cause code with a value that represents at least one of “

Implicitly Detached” and

“

No EPS Bearer Context Activated.”

11. The mobility management node of claim 10, wherein the first and second identifying characteristics comprise first and second closed subscriber group (CSG) identities.

12. The mobility management node of claim 10, wherein the first and second identifying characteristics comprise first and second Radio Access Technology (RAT) types.

13. The mobility management node of claim 10, wherein the first and second identifying characteristics comprise first and second cell identifiers.

14. The mobility management node of claim 10, wherein the first NAS message comprises a TRACKING AREA UPDATE REQUEST message, and the second NAS message comprises a TRACKING AREA UPDATE REJECT message.

15. The mobility management node of claim 10, wherein the first NAS message comprises a SERVICE REQUEST message, and the second NAS message comprises a SERVICE REJECT message.

16. The mobility management node of claim 10, further comprising a memory to store the first identifying characteristic.

17. The mobility management node of claim 10, where the second identifying characteristic indicates that there is no service continuity for the SIPTO PDN connection at a cell in the second RAN.

18. The mobility management node of claim 17, where when the second identifying characteristic indicates that there is no service continuity for the SIPTO PDN connection at the cell in the second RAN when the cell in the second RAN is a CSG cell having a second CSG identity that is different from a first CSG identity associated with a cell in the first RAN, or (2) that the cell in the second RAN does not have an associated CSG identity.

19. A non-transitory storage medium storing instructions that upon execution cause a mobility management node in a core network communicatively connected with a first radio access network (RAN) comprising a first network element and a second RAN comprising 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 UE has, with the first network element, a selected IP traffic offload (SIPTO) PDN connection;

detect that the UE is connected to the second network element that is different from the first network element that has a first identifying characteristic, wherein the detecting comprises determining that the first NAS message is received with a second identifying characteristic of the second network element different from the first identifying characteristic associated with the SIPTO PDN connection, the first identifying characteristic stored at the mobility management node; and

in response to the determining that the first NAS message is received with the second identifying characteristic of the second network element different from the first identifying characteristic;

determine that the UE has only a SIPTO PDN connection;

in response to determining that the UE has only a SIPTO PDN connection, send a second NAS message causing the UE to perform a new attach procedure, wherein the second NAS message includes at least one of an indication to force the UE to perform the new attach procedure, and a cause code with a value that represents at least one of “

Implicitly Detached” and

“

No EPS Bearer Context Activated.”