Releasing connections with local GW when UE moves out of residential/enterprise network coverage
View Patent ↗A method, system and device are provided for managing LIPA and/or SIPTO connection releases when UE moves out of residential/enterprise network coverage in case service continuity is not supported for the LIPA/SIPTO PDN connection(s). To address problems caused by not providing service continuity for LIPA/SIPTO PDN connections, the PDN connection/PDP context created in the HeNB/HNB by the MME/SGSN includes context information related to the UE indicating whether such connection is a LIPA PDN connection PDN connection or not. In addition, each UE may be configured to reconnect or not reconnect to the PDN corresponding to a certain APN or service, depending on how the PDN connection was disconnected by the network.
1. A method in a core network communicatively connected to 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, at least one of a Local IP Access (LIPA) packet data network (PDN) connection or 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 via the second network element, the first identifying characteristic associated with the at least one of the LIPA PDN connection or the SIPTO PDN connection, and the first identifying characteristic stored at the mobility management node; 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 causing the UE to perform a new attach procedure.
2. The method of claim 1 , wherein the second NAS message includes at least one of an indication to force the UE to perform the new attach procedure, or a cause code with a value that represents at least one of “Implicitly Detached” and “No EPS Bearer Context Activated”.
3. The method of claim 2 , wherein the cause code with the value that represents “Implicitly Detached” is to cause the UE to release all bearer contexts.
4. 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.
5. 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.
6. The method of claim 3 , 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.
7. The method of claim 1 , wherein the first NAS message is a Tracking Area Update Request message and the second NAS message is a Tracking Area Update Reject message.
8. The method of claim 1 , wherein the first NAS message is a one of a Tracking Area Update Request message, a Service Request message, an Extended Service Request message, a Routing Area Update message, or a paging response message.
9. The method of claim 1 , wherein the mobility management node is either a Mobility Management Entity (MME) or a Serving GPRS Support Node (SGSN).
10. 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.
11. The method of claim 1 , wherein the first network element has connectivity to a Local Gateway (L-GW) that is associated with the at least one of the LIPA PDN connection or the SIPTO PDN connection.
12. 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 RAN comprising 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 UE has, with the first network element, at least one of a Local Internet Protocol (IP) Access (LIPA) packet data network (PDN) connection or 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 via the second network element, the first identifying characteristic associated with the at least one of the LIPA PDN connection or the SIPTO PDN connection, and the first identifying characteristic stored at the mobility management node; 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 causing the UE to perform a new attach procedure.
13. The mobility management node of claim 12 , wherein the second NAS message includes at least one of an indication to force the UE to perform the new attach procedure, or a cause code with a value that represents at least one of “Implicitly Detached” and “No EPS Bearer Context Activated”.
14. The mobility management node of claim 13 , wherein the cause code with the value that represents “Implicitly Detached” is to cause the UE to release all bearer contexts.
15. The mobility management node of claim 13 , 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.
16. The mobility management node of claim 12 , wherein the first NAS message is received with a second identifying characteristic, the second identifying characteristic different from the first identifying characteristic.
17. The mobility management node of claim 12 , wherein the first NAS message is a one of a Tracking Area Update Request message, a Service Request message, an Extended Service Request message, a Routing Area Update message, or a paging response message.
18. A non-transitory computer readable storage medium having computer readable program code embodied therein, the computer readable program code upon execution causing 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 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, at least one of a Local Internet Protocol (IP) Access (LIPA) packet data network (PDN) connection or 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 via the second network element, the first identifying characteristic associated with the at least one of the LIPA PDN connection or the SIPTO PDN connection, and the first identifying characteristic stored at the mobility management node; 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 causing the UE to perform a new attach procedure.
19. The non-transitory computer-readable storage medium of claim 18 , wherein the second NAS message includes at least one of an indication to force the UE to perform the new attach procedure, or a cause code with a value that represents at least one of “Implicitly Detached” and “No EPS Bearer Context Activated”.
20. The non-transitory computer-readable storage medium of claim 18 , wherein the first NAS message is received with a second identifying characteristic, the second identifying characteristic different from the first identifying characteristic.