RELEASING CONNECTIONS WITH LOCAL GW WHEN UE MOVES OUT OF RESIDENTIAL/ENTERPRISE NETWORK COVERAGE
First Claim
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 and 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 and the SIPTO PDN connection, and the first identifying characteristic stored at the mobility management node; and
in response to a condition that each active 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, 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.”
9 Assignments
0 Petitions
Accused Products
Abstract
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.
31 Citations
20 Claims
-
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 and 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 and the SIPTO PDN connection, and the first identifying characteristic stored at the mobility management node; and in response to a condition that each active 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, 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.” - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
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 and 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 and the SIPTO PDN connection, and the first identifying characteristic stored at the mobility management node; and in response to a condition that each active 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, 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.” - View Dependent Claims (13, 14, 15, 16, 17)
-
-
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 and 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 and the SIPTO PDN connection, and the first identifying characteristic stored at the mobility management node; and in response to a condition that each active 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, 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.”
. - View Dependent Claims (19, 20)
-
Specification