Wireless module and method for local IP access packet data network release

Various embodiments include systems, wireless modules, and methods for local IP access packet data network release. Handover data can be received at a target wireless module as part of a user equipment handover operation. The user equipment can include an active packet data network session associated with a source local home network. A determination that the target wireless module is not in the source local home network can be made based on the handover data. The target wireless module can trigger deactivation of the packet data network session in response to the determination that the target wireless module is not in the source local home network.

BACKGROUND

Cellular networks provide many services to user equipment (UE) attached to those networks. Example cellular networks can operate in accordance with one or more 3rd Generation Partnership Project (3GPP) standards, including: global system for mobile communication (GSM) enhanced data rates for GSM evolution (EDGE) radio access network (GERAN); universal mobile telecommunications system (UMTS); long term evolution (LTE) including universal terrestrial radio access network (UTRAN); LTE advanced (LTE-A) including evolved UMTS terrestrial radio access network (E-UTRAN). 3GPP release 10, released Q1 2011, and releases 11 and beyond, include, for example specifications for the GERAN, UMTS, LTE and LTE-A families of standards.

Cellular networks generally include a number of cells that provide the UE with a wireless link to the network and its services. A variety of cells can constitute the cellular network. These cell types are generally differentiated by their effective communication ranges. Example, cell types can include macrocells, microcells, picocells, and femotocells. Shorter range cells, such as femtocells, can be used to create localized networks, such as local home networks (LHNs). For example, one or more femtocells can be used in a warehouse to create an LHN servicing the warehouse. A variety of elements, defined in cellular network specifications, support a cell. As used herein, wireless module (e.g., wireless infrastructure module) refers to these discreet elements. In LTE and LTE-A networks, eNBs provide radio access and control. In UMTS networks, nodeBs and radio network controllers (RNCs) are used. In GERAN networks, bases station systems (BSSs) are used. In the warehouse example, under LTE-A, a home eNB (HeNB) is used. BSSs, NodeBs, RNCs, eNBs, and HeNBs are all examples of a wireless module.

A UE can move between cells provoking one or more handover operations between cells and the UE. The LTE and LTE-A specifications include interfaces to facilitate communications between cells. For example, E-UTRAN to E-UTRAN handover can be accomplished via the S1 interface and the X2 interface. E-UTRAN to UTRAN handover can be accomplished via the Iu interface and E-UTRAN to GERAN handover can be accomplished via the A/Gb interfaces.

Packet data network (PDN) access, such as to the Internet, can be a service offered by the cellular network to UE. Example wireless modules that directly or indirectly participate in providing PDN access include, in LTE-A and LTE, MMEs local gateways (L-GWs), PDN gateways (P-GWs) and, in UMTS, gateway general packet radio service (GPRS) support nodes (GGSNs) and server GPRS support nodes (SGSNs). Generally, the cellular network includes a gateway (e.g., L-GW, P-GW or GGSN) to provide the PDN access. Generally, the gateway assigns PDN characteristics to the UE to facilitate this access. When a UE moves from one cell to another, the new cell may not have access to, or it may be inefficient to use, the gateway to the PDN. If the UE has an active PDN session and moves from one cell to another, the PDN connection may need to be deactivated if the target cell will use a different gateway than the gateway responsible for establishing the PDN connection. For example, when a target eNB does not have access to an L-GW used to establish the PDN connection. In an LHN, cells can access the site's local area network (LAN) to provide the PDN access. This is known as local IP access (LIPA). An example of an LTE-A LIPA PDN release procedure, part of the PDN deactivation, is the 3GPP TS 23.401-a21 specification (released Jan. 4, 2011), which defines a mobility management entity (MME) PDN release procedure at clause 5.4.4.2 (MME release procedure). In an example of LIPA PDN release in a 3GPP release 10 system, the local gateway (L-GW) collocated with an eNB can release the LIPA PDN session.

DETAILED DESCRIPTION

In an LTE-A LHN, the LIPA LAN can be used by more than one cell (e.g., eNB) of the LHN. This is known as LIPA mobility within the LHN. To enhance a user's experience using an LHN, it is a goal of cellular networks to maintain PDN connections when possible to avoid service interruptions. However, when the UE transitions to a cell that is not in the LHN, the PDN connection is deactivated due to LIPA LAN access considerations. The decision to deactivate the PDN session can reside in the source HeNB, for example, by maintaining a listing of LHN HeNBs and triggering PDN deactivation when the cell is transitioning to a cell outside of the LHN. In this case, the source HeNB would need to maintain a list of active HeNBs in the LHN and update this list over time. Maintaining the list of LHN HeNBs can consume resources, such as storage space and processing time, among others.

A target wireless module is arranged to know its network identification (ID), such as its LHN ID. During a handover operation, the UE network ID is communicated to the target wireless module. Thus, an efficient decision to deactivate the PDN session can be made at the target wireless module by comparing the LHN ID of the UE to that of the target wireless module. In this way, waste of the networks' resources can be spared because the maintenance of LHN HeNBs is not required.

FIG. 1illustrates and example system100for LIPA PDN release, according to an embodiment. The system100can include: a target wireless module105in a target network110that also includes a L-GW115; a source LHN125including HeNB130, HeNB135, L-GW140; and a PDN145. The system100also includes a UE120, shown to be connected to the HeNB130and transitioning to the target network110. The source LHN125and the target network110are communicatively coupled to transfer information for UE120handover facilitation, among other things.

The target wireless module105can be arranged to receive handover data as part of a UE120handover operation. The UE120can include an active PDN session associated with the source LHN125. The target wireless module105can be arranged to determine that it is not in the source LHN125based on the handover data. The target wireless module150can be arranged to trigger deactivation of the PDN session in response to the determination that it is not in the source LHN125. Thus, the decision to deactivate the PDN session can be made quickly and efficiently. In an example, the target wireless module105is arranged to trigger the PDN session deactivation by indicating that the LIPA bearer of the PDN session will not be used in the target network110. The source MME in the source LHN125can then perform the PDN session deactivation for PDN sessions whose LIPA bearers will not be used in the target network110. In an example, the MME (e.g., the source MME in the source LHN125) uses the MME release procedure to deactivate the PDN session. In an example, the target wireless module105is arranged to indicate that the LIPA bearer will not be used in the target network110by omitting the LIPA bearer in a handover acknowledge message.

In an example, the target wireless module105can be arranged to trigger deactivation of the PDN session during a handover preparation operation. By making the decision early in the handover process, the source LHN125and target network110can avoid maintain PDN session information. This can reduce costs and increase operating efficiency by reducing the computational burden on the networks. Examples of triggering PDN session deactivation during handover preparation are given below inFIGS. 2 through 5.

In an example, the target wireless module105can be arranged to trigger deactivation of the PDN session during a handover completion operation. As used herein a handover completion operation is a part of the UE120handover operation that occurs after handover preparation and handover execution operations. At handover completion, the UE120has transitioned to the target network110. Thus, there is no chance that the UE120will not complete the handover operation. In contrast, during handover preparation, there is a chance that the UE120will not complete the handover. By waiting until the handover completion operation, the target wireless module105can ensure that the PDN session is deactivated only when the source L-GW140will not be used for UE120PDN145access. Examples of triggering PDN session deactivation during handover completion are given below inFIGS. 6 through 9.

FIGS. 2 through 9illustrate portions of UE120handover operation sequence diagrams. The y-axis is time and the x-axis includes the network components involved in sending UE120handover operation messages. For clarity, some messages in an illustrated handover operation may be omitted. Further, solid message lines indicate a message carrying the target wireless module indication that a LIPA bearer will not be used in the target network110while dashed lines indicate messages and dashed boxes indicate groups of operations involved in the handover operation to provide context for the solid line messages within the illustrated handover operations.

FIG. 2is an example of an X2 interface sequence diagram illustrating portions of a handover preparation operation200, according to an embodiment. In this example, the target wireless module105is a HeNB in accordance with a post 3GPP release 10 family of standards (e.g., release 11 and beyond). The following are the illustrated X2 application protocol (X2AP) messages in accordance with, for example, the 3GPP release 11 family of standards: a handover request201, a handover request acknowledge202, and a handover command203.

The part of the UE120handover operation received by the target wireless module105can be the handover request201. The handover request201can include the UE LHN-ID for the UE120and can also include the LIPA bearer for the PDN session. In order to determine that the target wireless module105is not in the source LHN125, the target wireless module105can be arranged to determine that an LHN-ID of the target wireless module105is different than the UE LHN-ID. In order to trigger deactivation of the PDN session, the target wireless module105can be arranged to omit, from the X2AP handover request acknowledge202, the LIPA bearer. In an example, the, the source HeNB130can deactivate the LIPA PDN session by sending an indication of bearer release message to the MME as specified in the MME release procedure and omits the LIPA bearer in the following handover.

FIG. 3is an example of an S1 interface sequence diagram illustrating portions of a handover preparation operation300, according to an embodiment. In an example, the target wireless module is a HeNB in accordance with the 3GPP post 3GPP release 10 family of standards (e.g., release 11 and beyond). The following are the illustrated S1 application protocol (S1AP) messages and operational groups in accordance with, for example, the 3GPP release 11 family of standards: decision to trigger a relocation via S1301, a handover required message302, a forward relocation request303, a create session request304, a create session response305, a handover request306, a handover request acknowledge307, a create indirect data forwarding tunnel request308, a create indirect data forwarding tunnel response309, a forward relocation response310, a create indirect data forwarding tunnel request311, a create indirect data forwarding tunnel response312, a handover command313, and a handover command314.

The part of the UE120handover operation received by the target wireless module105can be the handover request306. The handover request306can include the UE LHN-ID for the UE120and can include the LIPA bearer for the PDN session. In order to determine that the target wireless module105is not in the source LHN125, the target wireless module105can be arranged to determine that an LHN-ID of the target wireless module105is different than the UE LHN-ID. In order to trigger deactivation of the PDN session, the target wireless module105can be arranged to omit, from the handover request acknowledge307, the LIPA bearer. In an example, when receiving the handover request acknowledge307, the target MME can deactivate the LIPA PDN session using the MME release procedure. In an example, when receiving the forward relocation response310, the source MME can deactivate the LIPA PDN session(s) using the MME release procedure.

In an example, the target wireless module105can be a HeNB in accordance with the 3GPP release 10 family of standards while the messages are in accordance with a later 3GPP release (e.g., release 11 and beyond) family of standards. The part of the UE120handover operation received by the target wireless module105is the handover request306. The handover request306can include at least one E-UTRAN radio access bearer (E-RAB) information element (IE) not defined in the 3GPP release 10 family of standards. The at least E-RAB IE is associated with the LIPA bearer for the PDN session. In order to trigger deactivation of the PDN session, the target wireless module105can be arranged to omit, from the handover request acknowledge307, the at least one E-RAB IE.

FIG. 4is an example of an Iu interface sequence diagram illustrating portions of a handover preparation operation400, according to an embodiment. In this example, the target wireless module105can be an RNC in accordance with the UMTS family of standards. The following are the illustrated Iu UMTS messages and operational groups: handover initiation401, a handover required message402, a forward relocation request403, a create session request404, a create session response405, a relocation request406, a relocation request acknowledge407, a create indirect data forwarding tunnel request408, a create indirect forwarding tunnel response409, a forward relocation response410, a create indirect forwarding tunnel request411, and a create indirect forwarding tunnel response412.

The part of the UE120handover operation received by the target wireless module105is the relocation request406. The relocation request406can include UE LHN-ID for the UE120and include the LIPA bearer for the PDN session. In order to determine that the target wireless module105is not in the source LHN125, the target wireless module105can be arranged to determine that the LHN-ID of the target wireless module105is different than the UE LHN-ID. In order to trigger deactivation of the PDN session, the target wireless module105can be arranged to omit, from the relocation request acknowledge407, the LIPA bearer. In an example, after receiving the forward relocation response410, the source MME can deactivate the LIPA PDN session(s) using the MME release procedure.

FIG. 5is an example of an A/Gb interface sequence diagram illustrating portions of a handover preparation operation500, according to an embodiment. In this example, the target wireless module105can be a BSS in accordance with the GERAN family of standards. The following are the illustrated A/Gb messages and operational groups: handover initiation501, a handover required message502, a forward relocation request503, a create session request504, a create session response505, a path switch handover request506, a path switch handover request acknowledge507, a create indirect data forwarding tunnel request508, a create indirect forwarding tunnel response509, a forward relocation response510, a create indirect forwarding tunnel request511, and a create indirect forwarding tunnel response512.

The part of the UE120handover operation received by the target wireless module105is the relocation request path switch handover request506. The path switch handover request506can include UE LHN-ID for the UE120and include the LIPA bearer for the PDN session. In order to determine that the target wireless module105is not in the source LHN125, the target wireless module105can be arranged to determine that the LHN-ID of the target wireless module105is different than the UE LHN-ID. In order to trigger deactivation of the PDN session, the target wireless module105can be arranged to omit, from the path switch handover request acknowledge507, the LIPA bearer. In an example, after receiving the forward relocation response510, the source MME can deactivate the LIPA PDN session(s) using the MME release procedure.

FIG. 6is an example of an X2 interface sequence diagram illustrating portions of handover completion operation600, according an embodiment. In this example, the target wireless module105is a HeNB in accordance with post 3GPP release 10 family of standards (e.g., release 11 and beyond). The following are the illustrated messages and operational groups in accordance with, for example, the 3GPP release 11 family of standards (message protocol type in parens): handover preparation601(X2AP), handover execution602(X2AP), downlink data604(RRC), uplink data605(GTP-U), a path switch request606(S1AP), a modify bearer request607(GTP-C), a modify bearer request608(GTP-C), a modify bearer response609(GTP-C), a modify bearer response (GTP-C), an end marker611(GTP-U), an end marker612(GTP-U), a path switch request acknowledge613(S1AP), a release resource message614(X2AP), and a tracking area update procedure615(NAS).

The part of the UE120handover operation received by the target wireless module105can be one or more X2AP messages (e.g., from the handover preparation601, the handover execution602, or any illustrated message). The one or more X2AP messages can include the UE LHN-ID for the UE120and can also include the LIPA bearer for the PDN session. In order to determine that the target wireless module105is not in the source LHN125, the target wireless module105can be arranged to determine that an LHN-ID of the target wireless module105is different than the UE LHN-ID. In order to trigger deactivation of the PDN session, the target wireless module105can be arranged to omit, from path switch request606, the LIPA bearer.

FIG. 7is an example of an S1 interface sequence diagram illustrating portions of handover completion operation700, according to an embodiment. The following are the illustrated messages and operational groups in accordance with, for example, the 3GPP release 11 family of standards (message protocol type in parens): handover preparation701(S1AP), handover execution702(S1AP), a handover notify message703(S1AP), a forward relocation complete notification704(GTP-C), a forward relocation complete acknowledge705(GTP-C), a modify bearer request706(GTP-C), a modify bearer request707(GTP-C), a modify bearer response708(GTP-C), a modify bearer response709(GTP-C), and a tracking area update procedure710(NAS).

The part of the UE120handover operation received by the target wireless module105can be one or more S1AP messages (e.g., from the handover preparation701, the handover execution702, or any illustrated message). The one or more S1AP messages can include the UE LHN-ID for the UE120and can include the LIPA bearer for the PDN session. In order to determine that the target wireless module105is not in the source LHN125the target wireless module105can be arranged to determine that an LHN-ID of the target wireless module105is different than the UE LHN-ID.

In an example, the target wireless module is a HeNB in accordance with the post 3GPP release 10 family of standards (e.g., release 11 and beyond). In order to trigger deactivation of the PDN session, the target wireless module105can be arranged to omit, from the handover notify message703, the LIPA bearer.

In an example, the target wireless module is an MME in accordance with, for example, the 3GPP release 11 family of standards. In order to trigger deactivation of the PDN session the target wireless module105can be arranged to omit, from the forward relocation complete notification704, the LIPA bearer.

FIG. 8is an example of an Iu interface sequence diagram illustrating portions of handover completion operation800, according to an embodiment. In this example, the target wireless module105is an RNC in accordance with the UMTS family of standards. The following are the illustrated Iu UMTS messages and operational groups: handover preparation801, E-UTRAN to UTRAN handover802, a relocation complete message803, a forward relocation complete notification804, a forward relocation complete acknowledge805, a modify bearer request806, a modify bearer request807, a modify bearer response808, and a modify bearer response809.

The part of the UE102handover operation includes one or more messages (e.g., from the handover preparation801, the handover execution202, or any illustrated message). The one or more message can include the UE LHN-ID for the UE120and can include the LIPA bearer for the PDN session. In order to determine that the target wireless module105is not in the source LHN125, the target wireless module105can be arranged to determine that the LHN-ID of the target wireless module105is different than the UE LHN-ID. In order to trigger deactivation of the PDN session, the target wireless module105can be arranged to omit, from the relocation complete message803, the LIPA bearer.

FIG. 9is an example of an A/Gb interface sequence diagram illustrating portions of handover completion operation900, according to an embodiment. In this example, the target wireless module105is a SGSN in accordance the 3GPP family of standards. The following are the illustrated A/Gb messages and operational groups: handover preparation901, E-UTRAN to GERAN handover902, a path switch handover complete message903, an exchange identification response904, a forward relocation notification905, a forward relocation acknowledge906, a modify bearer request907, a modify bearer request908, a modify bearer response909, and a modify bearer response910.

The part of the UE102handover operation includes one or more messages (e.g., from the handover preparation901, the handover execution902, or any illustrated message). The one or more message can include the UE LHN-ID for the UE120and can include the LIPA bearer for the PDN session. In order to determine that the target wireless module105is not in the source LHN125, the target wireless module105can be arranged to determine that the LHN-ID of the target wireless module105is different than the UE LHN-ID. In order to trigger deactivation of the PDN session, the target wireless module105can be arranged to omit, from the relocation complete notification905, the LIPA bearer.

FIG. 10is flowchart illustrating an example of a method1000for LIPA PDN release, according to an embodiment. Any elements described above with respect toFIGS. 1 through 9may be used, in any combination, to implement the operations of method1000.

At operation1005, at the target wireless module105, handover data can be received as part of the UE120handover operation. The UE120can include an active PDN session associated with the source LHN125.

At operation1010, a determination that the target wireless module105is not in the source LHN125can be made based on the handover data.

At operation triggering1015, deactivation of the PDN session can be triggered by the target wireless module105in response to the determination that the target wireless module105is not in the source LHN.

In an example, triggering of the deactivation can occur during a handover preparation operation of the UE120handover operation. Additional examples of triggering PDN session deactivation during a handover preparation operation are given above with respect toFIGS. 2 through 5.

In an example, triggering of the deactivation can occur during a handover completion operation. The handover completion operation occurring after a handover preparation operation, where both the handover completion operation and the handover preparation operation are part of the UE120handover operation. Additional examples of triggering PDN session deactivation during a handover completion operation are given above with respect toFIGS. 6 through 9.

Examples, as described herein, can include, or can operate on, logic or a number of components, modules, or mechanisms. Modules are tangible entities capable of performing specified operations and can be configured or arranged in a certain manner. In an example, circuits can be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors can be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software can reside (1) on a non-transitory machine-readable medium or (2) in a transmission signal. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

Machine (e.g., computer system)1100can include a hardware processor1102(e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory1104and a static memory1106, some or all of which can communicate with each other via a bus1108. The machine1100can further include a display unit1110, an alphanumeric input device1112(e.g., a keyboard), and a user interface (UI) navigation device1111(e.g., a mouse). In an example, the display unit1110, input device1117and UI navigation device914can be a touch screen display. The machine1100can additionally include a storage device (e.g., drive unit)1116, a signal generation device1118(e.g., a speaker), a network interface device1120, and one or more sensors1121, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The machine1100can include an output controller1128, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR)) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

The storage device1116can include a machine-readable medium1122on which is stored one or more sets of data structures or instructions1124(e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions1124can also reside, completely or at least partially, within the main memory1104, within static memory1106, or within the hardware processor1102during execution thereof by the machine1100. In an example, one or any combination of the hardware processor1102, the main memory1104, the static memory1106, or the storage device1116can constitute machine readable media.

While the machine-readable medium1122is illustrated as a single medium, the term “machine readable medium” can include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that arranged to store the one or more instructions1124.

The term “machine-readable medium” can include any tangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine1100and that cause the machine1100to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine-readable medium examples can include solid-state memories, and optical and magnetic media. Specific examples of machine-readable media can include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

Additional Notes & Examples

Example 1 can include subject matter (such as an apparatus, device, machine, system, or wireless module) arranged to receive handover data as part of a user equipment (UE) handover operation, the UE including an active packet data network (PDN) session associated with a source local home network (LHN). The subject matter can also be arranged to determine that the wireless module is not in the source LHN based on the handover data, and trigger deactivation of the PDN session in response to the determination that the wireless module is not in the source LHN.

In Example 2, the subject matter of Example 1 can optionally include, wherein the wireless module is arranged to trigger deactivation during a handover preparation operation of the UE handover operation.

In Example 3, the subject matter of Example 2 can optionally include, wherein the wireless module is a home eNB (HeNB) in accordance with a 3GPP family of standards, wherein the part of the UE handover operation is an X2 application protocol (X2AP) handover request in accordance with the 3GPP family of standards, the X2AP handover request including a UE LHN-ID for the UE and including a local IP access (LIPA) bearer for the PDN session, wherein to determine that the wireless module is not in the source LHN the wireless module is arranged to determine that an LHN-ID of the wireless module is different than the UE LHN-ID, and wherein to trigger deactivation of the PDN session the wireless module is arranged to omit, from an X2AP handover request acknowledge, the LIPA bearer.

In Example 4, the subject matter of one or any of Examples 2-3 can optionally include, wherein the wireless module is a home eNB (HeNB) in accordance with a 3GPP family of standards, wherein the part of the UE handover operation is an S1 application protocol (S1AP) handover request in accordance with the 3GPP family of standards, the S1AP handover request including a UE LHN-ID for the UE and including a local IP access (LIPA) bearer for the PDN session, wherein to determine that the wireless module is not in the source LHN the wireless module is arranged to determine that an LHN-ID of the wireless module is different than the UE LHN-ID, and wherein to trigger deactivation of the PDN session the wireless module is arranged to omit, from an S1AP handover request acknowledge, the LIPA bearer.

In Example 5, the subject matter of one or any of Examples 2-4 can optionally include, wherein the wireless module is a home eNB (HeNB) in accordance with a 3GPP release 10 family of standards, wherein the part of the UE handover operation is a handover request in accordance with a 3GPP family of standards, the handover request including at least one evolved universal mobile telecommunications systems terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) information element (IE) not defined in the 3GPP release 10 family of standards, the at least E-RAB IE being associated with a local IP access (LIPA) bearer for the PDN session, and wherein to trigger deactivation of the PDN session the wireless module is arranged to omit, from a handover request acknowledge, the at least one E-RAB IE.

In Example 6, the subject matter of one or any of Examples 2-5 can optionally include, wherein the wireless module is a radio network controller (RNC) in accordance with a 3GPP universal mobile telecommunications system (UMTS) family of standards, wherein the part of the UE handover operation is a UMTS relocation request, the UMTS relocation request including a UE LHN-ID for the UE and including a local IP access (LIPA) bearer for the PDN session, wherein to determine that the wireless module is not in the source LHN the wireless module is arranged to determine that an LHN-ID of the wireless module is different than the UE LHN-ID, and wherein to trigger deactivation of the PDN session the wireless module is arranged to omit, from a UMTS relocation request acknowledge, the LIPA bearer.

In Example 7, the subject matter of one or any of Examples 1-6 can optionally include, wherein the wireless module is arranged to trigger deactivation during a handover completion operation, the handover completion operation occurring after a handover preparation operation in the UE handover operation.

In Example 8, the subject matter of Example 7 can optionally include, wherein the wireless module is a home eNB (HeNB) in accordance with a 3GPP family of standards, wherein the part of the UE handover operation is one or more X2 application protocol (X2AP) messages in accordance with the family of standards, the one or more X2AP messages including a UE LHN-ID for the UE and including a local IP access (LIPA) bearer for the PDN session, wherein to determine that the wireless module is not in the source LHN the wireless module is arranged to determine that an LHN-ID of the wireless module is different than the UE LHN-ID, and wherein to trigger deactivation of the PDN session the wireless module is arranged to omit, from an S1 application protocol (S1AP) path switch request, the LIPA bearer.

In Example 9, the subject matter of one or any of Examples 7-8 can optionally include, wherein the part of the UE handover operation is one or more S1 application protocol (S1AP) messages in accordance with the 3GPP family of standards, the one or more S1AP messages including a UE LHN-ID for the UE and including a local IP access (LIPA) bearer for the PDN session, and wherein to determine that the wireless module is not in the source LHN the wireless module is arranged to determine that an LHN-ID of the wireless module is different than the UE LHN-ID.

In Example 10, the subject matter of Example 9 can optionally include, wherein the wireless module is a home eNB (HeNB) in accordance with a 3GPP family of standards, and wherein to trigger deactivation of the PDN session the wireless module is arranged to omit, from an S1AP handover notify message, the LIPA bearer.

In Example 11, the subject matter of one or any of Examples 9-10 can optionally include, wherein the wireless module is a mobility management entity (MME) in accordance with a 3GPP family of standards, and wherein to trigger deactivation of the PDN session the wireless module is arranged to omit, from an S1AP forward relocation complete notification, the LIPA bearer.

In Example 12, the subject matter of one or any of Examples 7-11 can optionally include, wherein the wireless module is a radio network controller (RNC) in accordance with a 3GPP universal mobile telecommunications system (UMTS) family of standards, wherein the part of the UE handover operation includes one or more messages including a UE LHN-ID for the UE and including a local IP access (LIPA) bearer for the PDN session, wherein to determine that the wireless module is not in the source LHN the wireless module is arranged to determine that an LHN-ID of the wireless module is different than the UE LHN-ID, and wherein to trigger deactivation of the PDN session the wireless module is arranged to omit, from a relocation complete message, the LIPA bearer.

In Example 13, the subject matter of one or any of Examples 7-12 can optionally include, wherein the wireless module is a serving general packet radio service (GPRS) support node (SGSN) in accordance with a 3GPP universal mobile telecommunications system (UMTS) family of standards, wherein the part of the UE handover operation includes one or more messages including a UE LHN-ID for the UE and including a local IP access (LIPA) bearer for the PDN session, wherein to determine that the wireless module is not in the source LHN the wireless module is arranged to determine that an LHN-ID of the wireless module is different than the UE LHN-ID, and wherein to trigger deactivation of the PDN session the wireless module is arranged to omit, from a relocation complete notification, the LIPA bearer.

Example 14 can include, or can optionally be combined with the subject matter of one or any combination of Examples 1-13 to include, subject matter (such as a method, means for performing acts, or machine-readable medium including instructions that, when performed by a machine cause the machine to performs acts) comprising receiving, at a target wireless module, handover data as part of a user equipment (UE) handover operation, the UE including an active packet data network (PDN) session associated with a source local home network (LHN), determining that the target wireless module is not in the source LHN based on the handover data, and triggering, by the target wireless module, deactivation of the PDN session in response to the determination that the target wireless module is not in the source LHN.

In Example 15, the subject matter of Example 14 can optionally include, wherein the triggering of the deactivation occurs during a handover preparation operation of the UE handover operation.

In Example 16, the subject matter of Example 15 can optionally include, wherein the target wireless module is a home eNB (HeNB) in accordance with a 3GPP family of standards, wherein the part of the UE handover operation is an X2 application protocol (X2AP) handover request in accordance with the 3GPP family of standards, the X2AP handover request including a UE LHN-ID for the UE and including a local IP access (LIPA) bearer for the PDN session, wherein determining that the target wireless module is not in the source LHN includes determining that a target wireless module's LHN-ID is different than the UE LHN-ID, and wherein triggering deactivation of the PDN session includes omitting, from an X2AP handover request acknowledge, the LIPA bearer.

In Example 17, the subject matter of one or any of Examples 15-16 can optionally include, wherein the target wireless module is a home eNB (HeNB) in accordance with a 3GPP family of standards, wherein the part of the UE handover operation is an S1 application protocol (S1AP) handover request in accordance with the 3GPP family of standards, the S1AP handover request including a UE LHN-ID for the UE and including a local IP access (LIPA) bearer for the PDN session, wherein determining that the target wireless module is not in the source LHN includes determining that a target wireless module's LHN-ID is different than the UE LHN-ID, and wherein triggering deactivation of the PDN session includes omitting, from an S1AP handover request acknowledge, the LIPA bearer.

In Example 18, the subject matter of one or any of Examples 15-17 can optionally include, wherein the target wireless module is a home eNB (HeNB) in accordance with a 3GPP release 10 family of standards, wherein the part of the UE handover operation is a handover request in accordance with a 3GPP family of standards, the handover request including at least one evolved universal mobile telecommunications systems terrestrial radio access network (E-UTRAN) radio access bearer (E-RAB) information element (IE) not defined in the 3GPP release 10 family of standards, the at least E-RAB IE being associated with a local IP access (LIPA) bearer for the PDN session, and wherein triggering deactivation of the PDN session includes omitting, from a handover request acknowledge, the at least one E-RAB IE.

In Example 19, the subject matter of one or any of Examples 15-18 can optionally include, wherein the target wireless module is a radio network controller (RNC) in accordance with a 3GPP universal mobile telecommunications system (UMTS) family of standards, wherein the part of the UE handover operation is a UMTS relocation request, the UMTS relocation request including a UE LHN-ID for the UE and including a local IP access (LIPA) bearer for the PDN session, wherein determining that the target wireless module is not in the source LHN includes determining that a target wireless module's LHN-ID is different than the UE LHN-ID, and wherein triggering deactivation of the PDN session includes omitting, from a UMTS relocation request acknowledge, the LIPA bearer.

In Example 20, the subject matter of one or any of Examples 14-19 can optionally include, wherein the triggering of the deactivation occurs during a handover completion operation, the handover completion operation occurring after a handover preparation operation, both the handover completion operation and the handover preparation operation being part of the UE handover operation.

In Example 21, the subject matter of Example 20 can optionally include, wherein the target wireless module is a home eNB (HeNB) in accordance with a 3GPP family of standards, wherein the part of the UE handover operation is one or more X2 application protocol (X2AP) messages in accordance with the 3GPP family of standards, the one or more X2AP messages including a UE LHN-ID for the UE and including a local IP access (LIPA) bearer for the PDN session, wherein determining that the target wireless module is not in the source LHN includes determining that a target wireless module's LHN-ID is different than the UE LHN-ID, and wherein triggering deactivation of the PDN session includes omitting, from an S1 application protocol (S1AP) path switch request, the LIPA bearer.

In Example 22, the subject matter of one or any of Examples 20-21 can optionally include, wherein the part of the UE handover operation is one or more S1 application protocol (S1AP) messages in accordance with the 3GPP family of standards, the one or more S1AP messages including a UE LHN-ID for the UE and including a local IP access (LIPA) bearer for the PDN session, and wherein determining that the target wireless module is not in the source LHN includes determining that a target wireless module's LHN-ID is different than the UE LHN-ID.

In Example 23, the subject matter of Example 22 can optionally include, wherein the target wireless module is a home eNB (HeNB) in accordance with a 3GPP family of standards, and wherein triggering deactivation of the PDN session includes omitting, from an S1AP handover notify message, the LIPA bearer.

In Example 24, the subject matter of one or any of Examples 22-23 can optionally include, wherein the target wireless module is a mobility management entity (MME) in accordance with a 3GPP family of standards, and wherein triggering deactivation of the PDN session includes omitting, from an S1AP forward relocation complete notification, the LIPA bearer.

In Example 25, the subject matter of one or any of Examples 20-24 can optionally include, wherein the target wireless module is a radio network controller (RNC) in accordance with a 3GPP universal mobile telecommunications system (UMTS) family of standards, wherein the part of the UE handover operation includes one or more messages including a UE LHN-ID for the UE and including a local IP access (LIPA) bearer for the PDN session, wherein to determine that the wireless module is not in the source LHN includes determining that an LHN-ID of the target wireless module is different than the UE LHN-ID, and wherein triggering deactivation of the PDN session includes omitting, from a relocation complete message, the LIPA bearer.

In Example 26, the subject matter of one or any of Examples 20-25 can optionally include, wherein the target wireless module is a serving general packet radio service (GPRS) support node (SGSN) in accordance with a 3GPP universal mobile telecommunications system (UMTS) family of standards, wherein the part of the UE handover operation includes one or more messages including a UE LHN-ID for the UE and including a local IP access (LIPA) bearer for the PDN session, wherein determining that the target wireless module is not in the source LHN includes determining that a target wireless module's LHN-ID is different than the UE LHN-ID, and wherein triggering deactivation of the PDN session includes omitting, from a relocation complete notification, the LIPA bearer.

Example 27 can include, or can optionally be combined with the subject matter of one or any combination of Examples 1-26 to include, subject matter (such as a method, means for performing acts, or machine-readable medium including instructions that, when performed by a machine cause the machine to performs acts) comprising receiving handover data as part of a user equipment (UE) handover operation, the UE including an active packet data network (PDN) session associated with a source local home network (LHN), determining that the wireless module is not in the source LHN based on the handover data, and triggering deactivation of the PDN session in response to the determination that the wireless module is not in the source LHN.

In Example 28, the subject matter of Example 27 can optionally include, wherein the triggering of the deactivation occurs during a handover preparation operation of the UE handover operation.

In Example 29, the subject matter of one or any of Examples 27-28 can optionally include, wherein the triggering of the deactivation occurs during a handover completion operation, the handover completion operation occurring after a handover preparation operation, both the handover completion operation and the handover preparation operation being part of the UE handover operation.

Example 30 can include, or can optionally be combined with the subject matter of one or any combination of Examples 1-26 to include, subject matter (such as an apparatus, device, machine, system, or wireless module) comprising a source wireless module in a source local home network (LHN), the source wireless module arranged to deactivate an active packet data network (PDN) session for a user equipment (UE) in response to receiving a network interface handover message, and a target wireless module. The target wireless module can be arranged to receive handover data as part of a UE handover operation, the UE including the active PDN session associated with the source LHN, determine that the wireless module is not in the source LHN based on the handover data, and trigger deactivation of the PDN session via the network interface handover message in response to the determination that the wireless module is not in the source LHN.

In Example 31, the subject matter of Example 30 can optionally include, wherein to trigger deactivation of the PDN session via the network interface handover message, the target wireless module is configured to omit a local IP access (LIPA) bearer of the PDN session from the network interface handover message.

In Example 32, the subject matter of Example 31 can optionally include, wherein the source wireless module is a mobility management entity (MME) in accordance with a 3GPP family of standards, and wherein to deactivate the active PDN session the source wireless module is configured to deactivate active PDN sessions whose associated LIPA bearers are not in the network interface handover message.