TWI593299B - Connection management techniques for wireless network mobility procedures - Google Patents

Description

Connection management technology for wireless network mobility programs Related application

The present application claims the priority of the U.S. Provisional Patent Application Serial No. 61/806,821, filed on March 29, 2013, the entire disclosure of which is hereby incorporated by reference.

Embodiments of the present invention are generally related to communication between devices in a broadband wireless communication network.

In a wireless network such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), a Home evolved Node B (HeNB) may be deployed. In order to implement a femtocell, the tiny cells provide wireless network access in a small area such as an office or a home. In various embodiments, a local gateway (Local Gateway; L-GW), in order to improve the Packet Data Network (PDN) access in the general area of the HeNB service. In some examples, the L-GW can be co-occupied with the HeNB. In the following, such an L-GW will be referred to as a "co-structured L-GW." In other examples, the L-GW can be co-constructed with a Serving Gateway (S-GW) on an independent gateway (GW). In the following, such an L-GW will be referred to as an "independent L-GW."

A User Equipment (UE) served by an HeNB can communicate with a PDN such as the Internet through a L-GW. More specifically, the UE does not unload the selected Internet Protocol (IP) Traffic Offload at the Local Network (SIPTO@LN) via a core packet network. The PDN connection is used to communicate with the PDN via the L-GW. The SIPTO@LN PDN connection may be required and/or desired to be released when an action event occurs based on the UE moving away from the coverage area of the L-GW. However, traditional connection management techniques may not define the appropriate or optimal procedure for releasing certain SIPTO@LN PDN connections.

The present invention describes a connection management technique for a wireless network mobile program. In an embodiment, for example, an Evolved Packet Core (EPC) node may include a processor circuit for performing one of the following: receiving a user equipment (UE) One of the action procedures to notify; decide whether to release a packet data network (PDN) connection provided by a local gateway (L-GW) of the UE; and respond to a decision to release one of the PDN connections provided by the L-GW, and A separate request message or a delete session request message is transmitted to initiate a procedure for releasing the PDN connection provided by the L-GW. Other embodiments are also described, and the scope of the patents of these other embodiments is claimed.

100, 200, 300, 400‧‧‧ operating environment

102, 302‧‧‧ User equipment

104, 304, 306‧‧‧Home Evolved Node B

106, 206, 312, 412, 570 ‧ ‧ action management entities

108, 208, 310, 314, 414‧‧‧ service gateways

110, 316‧‧‧ packet data network gateway

120‧‧‧Internet

112, 308‧‧‧Local gateways

202, 402, 404‧‧‧ action events

204, 406, 560‧‧‧Evolved Node B

203‧‧‧ Coverage Area

301‧‧‧Home Area Network

500‧‧‧ equipment

502‧‧‧ processor circuit

504‧‧‧ memory unit

506‧‧‧Communication components

540‧‧‧ system

544‧‧‧RF transceiver

557‧‧‧RF antenna

510 ‧ ‧ action procedure notice

512‧‧‧Home Area Network Identification Number

514‧‧‧Action procedure control messages

516‧‧‧Connection release start message

900‧‧‧Storage media

1000‧‧‧Communication device

1028‧‧‧Logical Circuit

1010‧‧‧ radio interface

1020‧‧‧Base frequency circuit

1030‧‧‧ Computing Platform

1012‧‧‧ Receiver

1014‧‧‧ frequency synthesizer

1016‧‧‧transmitter

1018- f ‧‧‧Antenna

1022‧‧‧ Analog to Digital Converter

1024‧‧‧Digital to analog converter

1026‧‧‧ physical layer processing circuit

1027‧‧‧Media access control processing circuit

1032‧‧‧ memory controller

1034‧‧" interface

1040‧‧‧Processing components

1050‧‧‧Other platform components

1100‧‧‧Broadband wireless access system

1110‧‧‧Internet

1112, 1118‧‧‧ Radio Access Network

1114, 1120‧‧‧Evolved Node B

1116‧‧‧Fixed devices

1122‧‧‧Mobile devices

1124‧‧‧ Guest core network

1126‧‧‧Local core network

1128‧‧‧Operation Support System

Figure 1 shows an embodiment of a first operating environment.

Figure 2 illustrates an embodiment of a second operating environment.

Figure 3 illustrates an embodiment of a third operating environment.

Figure 4 illustrates an embodiment of a fourth operating environment.

Figure 5 illustrates an embodiment of an apparatus and an embodiment of a system.

Figure 6 shows an embodiment of a first logic flow.

Figure 7 shows an embodiment of a second logic flow.

Figure 8 illustrates an embodiment of a third logic flow.

Figure 9 shows an embodiment of a storage medium.

Figure 10 shows an embodiment of a device.

Figure 11 shows an embodiment of a wireless network.

Embodiments may be generally related to connection management techniques for wireless network mobile procedures. In an embodiment, for example, an evolved packet core network (EPC) node may include processor circuitry for performing one of the following operations: Receiving a notification of a mobile device (UE) of one of the mobile procedures; deciding whether to release a packet data network (PDN) connection provided by a local gateway (L-GW) of the UE; and responding that the L-GW is to be released One of the provided PDN connections determines to transmit a separate request message or a delete talk layer request message to initiate a procedure for releasing the PDN connection provided by the L-GW. Other embodiments are also described, and the scope of the patents of these other embodiments is claimed.

Embodiments may include one or more components. An element can include any structure configured to perform certain operations. Each element can be implemented as a hardware, a soft body, or any combination of the above, as required by a particular set of design parameters or performance limitations. Although an embodiment may be illustrated by way of a limited number of elements in a certain topology, the embodiment may include more or fewer elements in an alternate topology as desired. It is to be understood that the phrase "a" or "an" or "an" in. The appearances of the words "in one embodiment", "in some embodiments", and "in the embodiments" are not necessarily referring to the same embodiments.

The techniques disclosed herein may involve the transmission of data via one or more wireless connections using one or more wireless mobile broadband technologies. For example, embodiments may be directed to one or more 3rd Generation Partnership Project (3GPP), 3GPP Long Term Evolution (LTE), and/or 3GPP Advanced Long Range Evolution Painting (LTE-Advanced; LTE-referred to as A) Transmission of technology and/or standards (including their revisions, subsequent versions, and variants) via one or more wireless connections.

Embodiments may additionally or alternatively relate to one or more Global System for Mobile communications (GSM)/Enhanced Data Rates for GSM Evolution (EDGE), Global Operations GSM with General Packet Telecommunications System (UMTS)/High Speed Packet Access (HSPA), and/or GSM with General Packet Radio Service (GPRS); GSM for short /GPRS) Transmission of technology and/or standards (including their revisions, subsequent versions, and variants). Examples of wireless mobile broadband technology may also include, without limitation, Institute of Electrical and Electronics Engineers (IEEE) 802.16m and/or 802.16p, International Mobile Telecommunications Advanced (referred to as International Mobile Telecommunications Advanced; IMT-ADV), Worldwide Interoperability for Microwave Access (WiMAX) and/or WiMAX II, Code Division Multiple Access (CDMA) 2000 (eg, CDMA2000 1xRTT, CDMA2000 EV-) CDMA2000 series technology such as DO and CDMA EV-DV), High Performance Radio Metropolitan Area Network (HIPERMAN), Wireless Broadband (WiBro), and high-speed downlink packet access (High) Speed Downlink Packet Access; referred to as HSDPA), High Speed Orthogonal Frequency-Division Multiplexing (OFDM) Packet Access (HSOPA), High Speed Uplink Packet Access (HSUPA) And/or any technology in the standard (including its revisions, subsequent versions, and variants). The embodiments are not limited to this context.

In addition to transmission over one or more wireless connections, the techniques disclosed herein may involve the transmission of content via one or more wired connections using one or more wired communication media. Examples of wired communication media may include wires, cables, metal leads, printed circuit boards (PCBs), backplanes, switch fabrics, semiconductor materials, twisted pairs, coaxial cables, And wired communication media such as fiber optic connections. The embodiments are not limited to this context.

FIG. 1 illustrates an operating environment 100 such as may represent one of the various embodiments. More specifically, operating environment 100 may represent some embodiments in which a UE may establish a SIPTO@LN PDN connection using a co-located L-GW. As shown in FIG. 1, a UE 102 communicates with a HeNB 104 via a Uu interface. The HeNB 104 communicates with a Mobility Management Entity (MME) 106 via an S1-MME interface and communicates with a Serving Gateway (S-GW) 108 via an S1-U interface. The MME 106 communicates with the S-GW 108 via an S11 interface connection. The S-GW 108 communicates with a PDN Gateway (P-GW) 110 via an S5 interface connection. P-GW 110 via An SGi interface is connected to connect to the Internet 120. Co-constructed with HeNB 104 is an L-GW 112, which is also connected to the Internet 120 via an SGi interface connection. The UE 102 does not communicate with the Internet 120 via the P-GW 110, but can establish a SIPTO@LN PDN connection to the Internet 120 via the L-GW 112. Using the SIPTO@LN PDN connection to communicate with the Internet 120 enables the UE 302 to avoid delays associated with the use of the core packet network.

FIG. 2 illustrates an operating environment 200 such as may represent one of the various embodiments. More specifically, operating environment 200 may represent certain embodiments in which UE 102 of FIG. 1 moves away from HeNB 104. As shown in FIG. 2, an action event 202 occurs as the UE 102 moves away from the HeNB 104 and toward an eNB 204. During the course of the action event 202, the UE 102 exits the coverage area 203 of the HeNB 104. The eNB 204 communicates with an MME 206 via an S1-MME interface connection and communicates with an S-GW 208 via an S1-U interface connection. The MME 206 is connected to the S-GW 208 via an S11 interface, and the S-GW 208 is in communication with the P-GW 110 via an S5 interface connection. The MME 206 also communicates with the MME 106 via an S10 interface connection.

In response to action event 202, a mobile procedure can be performed in accordance with UE 102 establishing a service connection via eNB 204. The UE 102 can communicate with the eNB 204 via a Uu interface connection (not shown). If the UE 102 is in a connected mode at the time of the action event, the action program may include a connected mode action procedure such as a handover procedure. If the UE 102 is in an idle mode at the action event, then the course of action The sequence may include an idle mode action program such as a tracking area update program or a service request program. If the UE 102 has established a SIPTO@LN PDN connection to the Internet 120 prior to the action event 202, the SIPTO@LN PDN connection may not be available after the action event 202 because the UE 102 has moved out of the HeNB 104. The scope. Therefore, it may be desirable to release the SIPTO@LN PDN connection after the action procedure.

FIG. 3 illustrates an operating environment 300 such as may represent one of the various embodiments. More specifically, operating environment 300 may represent some embodiments in which a UE may establish a SIPTO@LN PDN connection via a separate L-GW. As shown in FIG. 3, a Home Home Network (LHN) 301 includes a UE 302, HeNBs 304 and 306, and an L-GW 308 co-constructed with an S-GW 310. In the example shown in FIG. 3, HeNB 304 includes a serving HeNB of UE 302 and communicates with UE 302 via a Uu interface connection. HeNBs 304 and 306 communicate with S-GW 310 via respective S1-U interface connections. One of the MMEs 312, one S-GW 314, and one P-GW 316, respectively, which may be included in a service provider network, are disposed outside of the LHN 301. HeNBs 304 and 306 communicate with MME 312 via respective S1-MME interface connections and communicate with S-GW 314 via respective S1-U interface connections. The MME 312 communicates with the S-GW 314 via an S11 interface connection. The S-GW 314 communicates with the P-GW 316 via an S5 interface connection. P-GW 316 communicates with Internet 120 via an SGi interface connection. The UE 302 does not communicate with the Internet 120 via the P-GW 316. Instead, a SIPTO@LN PDN connection to the Internet 120 can be established via the L-GW 308. Using the SIPTO@LN PDN connection to communicate with the Internet 120 enables the UE 302 to avoid delays associated with the use of the core packet network.

FIG. 4 illustrates an operating environment 400 such as may represent one of the various embodiments. More specifically, operating environment 400 illustrates certain embodiments in which UE 302, such as FIG. 3, moves away from HeNB 304. As shown in FIG. 4, according to an action event 402, the UE 302 moves outside of the LHN 301 and enters the range of an eNB 406. The eNB 406 communicates with an MME 412 via an S1-MME interface connection and communicates with an S-GW 414 via an S1-U interface connection. The MME 412 communicates with the S-GW 414 via an S11 interface connection, and the S-GW 414 communicates with the P-GW 316 via an S5 interface connection. The MME 412 also communicates with the MME 312 via an S10 interface connection.

Due to the action event 402, the UE 302 can move out of the range of the HeNB 304 and thus no longer get a service connection via the HeNB 304. Moreover, because UE 302 moves outside of LHN 301, UE 302 is unable to obtain a service connection from any other HeNB, such as HeNB 306, within LHN 301. Thus, in response to action event 402, a mobile procedure can be performed in accordance with UE 302 establishing a service connection via eNB 406. The UE 302 can communicate with the eNB 406 via a Uu interface connection (not shown). If the UE 302 is in a connected mode at the time of the action event, the action program may include a connected mode action procedure such as a handover procedure. If the UE 302 is in an idle mode at the action event, then the course of action The sequence may include an idle mode action program such as a tracking area update program or a service request program. If the UE 302 has established a SIPTO@LN PDN connection to the Internet 120 prior to the action event 402, the SIPTO@LN PDN connection may not be available after the action event 402 because the UE 302 has moved out of the LHN 301. And the range of HeNBs 304 and 306 has been removed. Therefore, it may be desirable to release the SIPTO@LN PDN connection after the action procedure executed in response to action event 402.

It is worth noting that in various embodiments, an action event may occur based on the UE 302 moving out of the range of the HeNB 304 but remaining within the LHN 301. In some such embodiments, in response to an action event, a mobile procedure can be performed in accordance with UE 302 establishing a service connection via another HeNB within LHN 301. For example, after the action event 404, a mobile procedure can be performed in accordance with the UE 302 establishing a service connection via the HeNB 306. In this case, the UE 302 is still able to communicate with the Internet 120 using the L-GW 308 due to the use of the HeNB 306. Thus, if the UE 302 has established a SIPTO@LN PDN connection to the Internet 120 prior to the action event 404, the UE 302 can still use the SIPTO@LN PDN connection after the action event 404. Therefore, it may be desirable to maintain the SIPTO@LN PDN connection after the action procedure performed in response to the action event 404.

The present invention discloses an improved connection management technique for wireless network mobile procedures. According to some such techniques, after a mobile procedure of a UE, a serving MME of the UE may decide whether to release one of the UEs SIPTO@LN PDN connection. In various embodiments, the serving MME may decide whether to release the SIPTO@LN PDN connection based on whether the UE has logged out of its LHN. In some embodiments, if the serving MME decides that the SIPTO@LN PDN connection should be released, the serving MME may also decide to release one of the SIPTO@LN PDN connections according to whether the UE has any other PDN connection. Appropriate procedures. In various embodiments, the mobile procedure may include a Tracking Area Update (TAU) procedure, and the serving MME may include a new MME that communicates with an old MME of the UE during the TAU procedure. For example, after the MME 312 includes an old MME of the UE 302 and the MME 412 includes one of the new MMEs of the UE 302, the MME 412 may include the serving MME of the UE 302. In some other embodiments, the mobile program can include a handover procedure, and the serving MME can include a target MME for the handover procedure. For example, after the MME 312 includes a source MME and the MME 412 includes a handover procedure for one of the UEs 302 of the target MME, the MME 412 may include the serving MME of the UE 302.

It is worth noting that the techniques described herein are not limited to applications in embodiments of the UE's serving MME that change during a mobile procedure. In various embodiments, the same MME may serve the UE before and after the mobile procedure, and the MME may decide whether to release the SIPTO@LN PDN connection of the UE. Likewise, the serving S-GW of the UE may or may not change during the course of the action. The embodiments are not limited to this context.

Figure 5 illustrates a block diagram of an apparatus 500, such as an improved connection management technique that can implement a wireless network mobile program. As shown in Figure 5, The device 500 includes a plurality of components including a processor circuit 502, a memory unit 504, a communication component 506, and a decision component 508. However, the embodiments are not limited to the types, numbers, or configurations of the various elements disclosed in the drawings.

In some embodiments, device 500 can include processor circuit 502. A Complex Instruction Set Computer (CISC) microprocessor, a Reduced Instruction Set Computer (RISC) microprocessor, and a Very Long Instruction Word (VLIW) can be used. A microprocessor, a processor compatible with the x86 instruction set, a processor implementing a combination of some instruction sets, a multi-core processor such as a dual core processor or a dual core mobile processor, or any other microprocessor or central Processor circuit 502 is implemented by any processor or logic device, such as a Central Processing Unit (CPU). The processor circuit 502 can also be implemented as a controller, a microcontroller, an embedded processor, a Chip Multiprocessor (CMP), a coprocessor, and a Digital Signal Processor (DSP). , network processor, media processor, input/output (I/O) processor, media access control (MAC) processor, radio baseband processor, specific application product A dedicated processor such as an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), and a Programmable Logic Device (PLD). In an embodiment, for example, at The processor circuit 502 can be implemented as a general purpose processor such as a processor manufactured by Intel® Corporation (located in Santa Clara, California, USA). The embodiments are not limited to this context.

In various embodiments, device 500 can include or be configured to be communicatively coupled to a memory unit 504. The memory unit 504 can be implemented using any machine readable or computer readable medium that can store data in volatile and non-volatile memory. For example, the memory unit 504 may include a read only memory (ROM), a random access memory (RAM), a dynamic memory (DRAM), and a dual Double Data Rate Memory (Double-Data-Rate DRAM; DDRAM), Synchronous DRAM (SDRAM), Static RAM (SRAM), Programmable Readable Memory (Programmable ROM; PROM for short), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (Electrically Erasable Programmable ROM; EEPROM for short) ), flash memory, polymer memory such as ferroelectric polymer memory, ovonic memory, phase change or ferroelectric memory, yttrium-oxide-nitride-oxide-矽Silicon-Oxide-Nitride-Oxide-Silicon; referred to as SONOS) memory, magnetic or optical card, or any other type of media suitable for storing information. It should be noted that some or all of the memory unit 504 may be included in the same integrated circuit as the processor circuit 502, or some of the memory unit 504. Some or all of these may be disposed in other media such as a hard disk drive or the like outside the integrated circuit of the integrated circuit or processor circuit 502. Although the memory unit 504 is included in the device 500 in FIG. 5, in some embodiments, the memory unit 504 can be external to the device 500. The embodiments are not limited to this context.

In some embodiments, device 500 can include a communication component 506. Communication component 506 can include logic, circuitry, and/or instructions operable to transmit messages to and/or receive messages from one or more remote devices. In various embodiments, communication component 506 is operable to transmit and/or receive messages via one or more wired connections, one or more wireless connections, or a combination of the two. In some embodiments, communication component 506 can additionally include logic, circuitry, and/or instructions operable to perform various operations for supporting such communications. Examples of such operations may include transmission and/or reception of parameters and/or timing selections, packets and/or Protocol Data Unit (PDU) construction and/or deconstruction, encoding and/or decoding, error detection. And/or bug fixes. These embodiments are not limited to these examples.

In various embodiments, device 500 and/or system 540 can include a decision component 508. Decision component 508 is operable to perform various types of decisions and/or decisions for supporting the action management operations performed by device 500 and/or system 540. In some embodiments, the decision component 508 is operable to perform setup, initiation, and/or execution of one or more connections affecting one or more UEs in a wireless network of the device 500 and/or the system 540 including an MME. / or release one or more decisions and / or decisions. These embodiments are not limited In this situation.

FIG. 5 also shows a block diagram of a system 540 that can include any of the elements of device 500 described above. System 540 can further include a radio frequency (RF) transceiver 544. The RF transceiver 544 can include one or more radios capable of transmitting and receiving signals using various suitable wireless communication technologies. Such techniques may involve communication across one or more wireless networks. The exemplary wireless network includes, but is not limited to, a Wireless Local Area Network (WLAN), a Wireless Personal Area Network (WPAN), and a Wireless Metropolitan Area Network (Wireless Metropolitan Area Network). (WMAN for short), cellular network, and satellite network. When communicating across such networks, the RF transceiver 544 can operate in accordance with any version of one or more applicable standards. The embodiments are not limited to this context.

In some embodiments, system 540 can include one or more RF antennas 557. Examples of any particular RF antenna 557 may include, but are not limited to, internal antennas, omnidirectional antennas, monopole antennas, dipole antennas, end-fed antennas, and circles. A circularly polarized antenna, a microstrip antenna, a diversity antenna, a dual antenna, a tri-band antenna, and a quad-band antenna Antennas. In various embodiments, RF transceiver 544 is operable to transmit and/or receive messages and/or data using one or more RF antennas 557. These embodiments are not Limited to this situation.

In various embodiments, device 500 and/or system 540 can include an MME. More specifically, device 500 and/or system 540 can include one of the UEs 550 serving the MME after a mobile procedure that is performed in response to an action event of a UE 550. In some embodiments, the mobile program can include a TAU procedure. In various such embodiments, device 500 and/or system 540 can include a new MME that communicates with an old MME of UE 550 during the TAU procedure. In some embodiments, device 500 and/or system 540 can also include the serving MME of the UE prior to the TAU procedure. In various embodiments, the action program can include a handover procedure. In some embodiments, device 500 and/or system 540 can include one of the handover procedures, the target MME. In various other embodiments, the serving MME of the UE may not change during the handover procedure, and thus the device 500 and/or system 540 may also include the serving MME of the UE prior to the handover procedure. The embodiments are not limited to this context.

In some embodiments, during a mobile program of UE 550, communication component 506 is operable to receive a mobile program notification 510. The mobile program notification 510 can include a message to generally indicate that the mobile program 550 has been activated. In various embodiments, the mobile program can include a TAU procedure, and the mobile program notification 510 can include receiving one of the TAU request messages from one of the serving eNBs 560 of the UE 550 included in the TAU procedure. In some embodiments, the mobile program can include a handover procedure, and the mobile procedure notification 510 can include a forward relocation request received from the MME 570, the request including One of the UEs 550 before the handover procedure serves the MME. In still other embodiments, the mobile program can include a handover procedure, and the mobile procedure notification 510 can include a required handover message received from an eNB that is served by one of the UEs 550 prior to the handover procedure. eNB. The embodiments are not limited to this context.

In various embodiments, the UE 550 may have established a SIPTO@LN PDN connection prior to the mobile procedure. In some embodiments, decision component 508 is operable to determine whether to release the SIPTO@LN PDN connection of UE 550 after the action procedure. In various embodiments, decision component 508 is operable to determine whether to release the SIPTO@LN PDN connection of UE 550 based on LHN-ID 512 of UE 550. In some embodiments, decision component 508 is operable to respond to one of the LHN changes of UE 550 in response to the action procedure made by LHN-ID 512, and to decide to release the SIPTO@LN PDN connection. In various embodiments, the decision component 508 is operable to respond to the action procedure made in accordance with the LHN-ID 512 without causing one of the LHN changes of the UE 550 to decide not to release the SIPTO@LN PDN connection.

In some embodiments, communication component 506 is operative to receive a mobile program control message 514 containing LHN-ID 512. In various embodiments, the mobile program control message 514 can include the same message as the mobile program notification 510. For example, in some embodiments, the mobile program can include a handover procedure, and the mobile procedure notification 510 can include a forward relocation request message including the LHN-ID 512. In various other embodiments, the mobile program control message 514 can include a different message than the mobile program notification 510. example For example, in some embodiments, the mobile program can include a TAU procedure, the mobile program notification 510 can include a TAU request message, and the mobile program control message 514 can include a context response message including the LHN-ID 512. In still other embodiments, communication component 506 can receive a mobile program control message 514 containing LHN-ID 512 without operation. For example, in various embodiments, device 500 and/or system 540 can include a serving MME of UE 550 prior to the mobile procedure and after the mobile procedure, and decision component 508 is operable from memory unit 504. LHN-ID 512 is retrieved during storage. It should be understood that although the example of FIG. 5 shows a mobile program control message 514 containing LHN-ID 512 and shows a mobile program control message 514 that is different from the mobile program notification 510, the embodiments do not. Limited to this example.

In some embodiments, in response to one of the SIPTO@LN PDN connections that will release the UE 550, the decision component 508 is operable to select a procedure for releasing the SIPTO@LN PDN connection. In various embodiments, decision component 508 is operable to determine the program selected to release the SIPTO@LN PDN connection based on whether the SIPTO@LN PDN connection includes one of the unique PDN connections of UE 550. In some embodiments, the SIPTO@LN PDN connection is determined by one of the unique PDN connections of the UE 550, and the decision component 508 is operable to select an MME-initiated split procedure for releasing the SIPTO@LN PDN connection. In various embodiments, the SIPTO@LN PDN connection is determined by one of the unique PDN connections that do not include the UE 550, and the decision component 508 is operable to select an MME required to release the SIPTO@LN PDN connection. Cut off the program. The embodiments are not limited to this context.

In some embodiments, after the action procedure, communication component 506 is operable to transmit a connection release initiation message 516 to initiate release of the SIPTO@LN PDN connection in accordance with the selected program. In various embodiments, the selected program can include an MME-initiated separate program, and the connection release initiation message 516 can include a separate request message. In some other embodiments, the selected program can include a PDN disconnection procedure requested by the MME, and the connection release initiation message 516 can include a delete session layer request message. In various embodiments, the connection release initiation message 516 may indicate that the PDN shutdown procedure requested by the MME will be initiated under a reactivation request. The embodiments are not limited to this context.

The operation of the above embodiment can be further explained with reference to the following drawings and accompanying examples. Some of the drawings may include logic flows. While such a schema provided in this specification can include a particular logic flow, it should be understood that the logic flow merely provides an example of how to implement the general functionality described herein. Moreover, unless otherwise indicated, it is not necessary to perform a particular logic flow in the order presented. Moreover, a particular logic flow can be implemented by a hardware component, a software component executed by a processor, or any combination of the above. The embodiments are not limited to this context.

FIG. 6 illustrates one embodiment of a logic flow 600 that may be representative of operations performed by one or more embodiments of the present invention (eg, operations that may be performed by device 500 and/or system 540 of FIG. 5). More specifically, logic flow 600 may represent some implementation of a serving MME for the UE after device 500 and/or system 540 includes a mobile application of a UE. example. As shown in logic flow 600, in operation 602, one of the action procedures of a UE may be received. For example, communication component 506 of FIG. 5 is operable to receive an activation of one of the mobile program notifications 510 for indicating a mobile program of UE 550. In operation 604, a determination may be made whether to release a SIPTO@LN PDN connection for the UE. For example, decision component 508 of FIG. 5 is operable to determine whether to release a SIPTO@LN PDN connection of UE 550. If it is decided in operation 604 not to release the SIPTO@LN PDN connection, the logic flow can be terminated. If it is determined in operation 604 that the SIPTO@LN PDN connection is to be released, then flow may proceed to operation 606.

In operation 606, a program for releasing the SIPTO@LN PDN connection can be selected. For example, decision component 508 of FIG. 5 is operable to select a program for releasing a SIPTO@LN PDN connection for UE 550 based on whether the SIPTO@LN PDN connection is a unique PDN connection for UE 550. In operation 608, after the action procedure, the selected program for releasing the SIPTO@LN PDN connection may be initiated. For example, after the mobile program of UE 550 of FIG. 5, communication component 506 is operable to transmit a connection release initiation message 516 to initiate a procedure for selecting one of the SIPTO@LN PDN connections for releasing UE 550. These embodiments are not limited to these examples.

FIG. 7 illustrates one embodiment of a logic flow 700 that may be representative of operations performed by one or more embodiments of the present invention (eg, operations that may be performed by device 500 and/or system 540 of FIG. 5). More specifically, logic flow 700 may represent device 500 and/or system 540 includes a UE Embodiments of a new MME for the UE in a TAU procedure. As shown in logic flow 700, in operation 702, one of the TAU request messages for initiating a TAU procedure for a UE may be received. For example, communication component 506 of FIG. 5 is operable to receive one of the TAU request messages 510 including a TAU request message for instructing activation of a TAU procedure by UE 550. In operation 704, a context response message may be received that includes one of the LHN-IDs of the UE. For example, communication component 506 of FIG. 5 is operable to receive an action program control message 514 that includes a context response message and includes an LHN-ID of UE 550. In operation 706, it may be determined whether the LHN of the UE changes according to the TAU procedure. For example, decision component 508 of FIG. 5 is operable to determine whether LHN of UE 550 changes according to a TAU procedure of UE 550 based on LHN-ID 512. If it is determined in operation 706 that the LHN of the UE has not changed according to the TAU procedure, then the logic flow may terminate. If it is determined in operation 706 that the LHN of the UE changes according to the TAU procedure, then flow may proceed to operation 708.

In operation 708, a SIPTO@LN PDN connection of the UE may be determined to include a unique PDN connection for the UE. For example, decision component 508 of FIG. 5 is operable to determine whether a SIPTO@LN PDN connection of UE 550 includes a unique PDN connection for UE 550. If it is determined in operation 708 that the SIPTO@LN PDN connection does not include a unique PDN connection for the UE, then flow may proceed to operation 710. In operation 710, after the TAU procedure of the UE, an MME-requested PDN disconnect procedure may be initiated to release the SIPTO@LN PDN connection of the UE. example For example, after a TAU procedure of the UE 550 of FIG. 5, the communication component 506 is operable to transmit a connection release initiation message 516 including a delete session layer request message, and initiate a PDN disconnect procedure requested by the MME so that Release one of the UE 550 SIPTO@LN PDN connections. If it is determined in operation 708 that the SIPTO@LN PDN connection contains a unique PDN connection for the UE, then flow may proceed to operation 712. In operation 712, after the TAU procedure of the UE, an MME initiated separation procedure may be initiated to release the SIPTO@LN PDN connection of the UE. For example, after a TAU procedure of the UE 550 of FIG. 5, the communication component 506 is operable to transmit a connection release initiation message 516 containing a separate request message, and initiate an MME initiated separation procedure to release the UE 550. A SIPTO@LN PDN connection. These embodiments are not limited to these examples.

FIG. 8 illustrates one embodiment of a logic flow 800 that may be representative of operations performed by one or more embodiments of the present invention (eg, operations that may be performed by device 500 and/or system 540 of FIG. 5). More specifically, logic flow 800 may represent some embodiments of device 500 and/or system 540 that include one of the handover procedures of a UE, a target MME. As shown in logic flow 800, in operation 802, a forward relocation request message indicating one of the LHN-IDs for initiating a handover procedure of a UE and including the UE may be received. For example, communication component 506 of FIG. 5 is operable to receive a one-way action notification 510 of a forward relocation request message including an LHN-ID 512 containing UE 550 and indicating the initiation of a handover procedure by UE 550. In operation 804, it may be determined whether the LHN of the UE is according to the Change the delivery procedure. For example, decision component 508 of FIG. 5 is operable to determine whether LHN of UE 550 changes according to a handover procedure of UE 550 based on LHN-ID 512. If it is determined in operation 804 that the LHN of the UE has not changed according to the handover procedure, then the logic flow may terminate. If it is determined in operation 804 that the LHN of the UE changes according to the handover procedure, then flow may proceed to operation 806.

In operation 806, a SIPTO@LN PDN connection of the UE may be determined to include a unique PDN connection for the UE. For example, decision component 508 of FIG. 5 is operable to determine whether a SIPTO@LN PDN connection of UE 550 includes a unique PDN connection for UE 550. If it is determined in operation 806 that the SIPTO@LN PDN connection does not include a unique PDN connection for the UE, then flow may proceed to operation 808. In operation 808, after the handover procedure of the UE, an MME-requested PDN disconnect procedure may be initiated to release the SIPTO@LN PDN connection of the UE. For example, after a handover procedure of the UE 550 of FIG. 5, the communication component 506 is operable to transmit a connection release initiation message 516 including a delete session layer request message, and initiate a PDN disconnect procedure requested by the MME. In order to release one of the UE 550 SIPTO@LN PDN connections. If it is determined in operation 806 that the SIPTO@LN PDN connection contains a unique PDN connection for the UE, then flow may proceed to operation 810. In operation 810, after the handover procedure of the UE, an MME initiated separation procedure may be initiated to release the SIPTO@LN PDN connection of the UE. For example, after a handover procedure of the UE 550 of FIG. 5, the communication component 506 is operable to transmit a connection release containing a separate request message therein. The message 516 is initiated and an MME initiated separation procedure is initiated to release one of the UE 550 SIPTO@LN PDN connections. These embodiments are not limited to these examples.

FIG. 9 illustrates an embodiment of a storage medium 900. Storage medium 900 can include any non-transitory computer readable storage medium or machine readable storage medium such as optical, magnetic, or semiconductor storage media. In various embodiments, storage medium 900 can include an article of manufacture. In some embodiments, the storage medium 900 can store a computer such as one or more of the logic flows 600 for performing the logic flow 600 of FIG. 6, the logic flow 700 of FIG. 7, and the logic flow 800 of FIG. Computer-executable instructions such as executable instructions. Examples of computer readable storage media or machine readable storage media may include any tangible medium capable of storing electronic data, including volatile or non-volatile memory, removable or non-removable media, Erasing or non-erasable memory, and tangible media that can be written or overwritten with memory. Examples of computer executable instructions may include any suitable type of code such as source code, compiled code, literal code, executable code, static code, dynamic code, object oriented code, and visual code. The embodiments are not limited to this context.

Figure 10 shows a device 500 and/or system 540 that can implement Figure 5, a logic flow 600 of Figure 6, a logic flow 700 of Figure 7, a logic flow 800 of Figure 8, and/or a Figure 9. A communication device 1000 that stores one or more of the media 900. In various embodiments, device 1000 can include a logic circuit 1028. Logic circuit 1028 can include means for performing apparatus 500 and/or system 540, such as FIG. 5, Figure 6 The physical circuit of the operation of one or more of the logic flow 600, the logic flow 700 of FIG. 7, and the logic flow 800 of FIG. As shown in FIG. 10, device 1000 can include a radio interface 1010, a baseband circuit 1020, and a computing platform 1030, although the embodiments are not limited to this configuration.

The apparatus 1000 can implement the apparatus 500 and/or system 540 of FIG. 5, the logic flow 600 of FIG. 6, the logic flow 700 of FIG. 7, the logic flow 800 of FIG. 8, the storage medium 900 of FIG. 9, and a single Some or all of the structure and/or operation of one or more of the logic circuits 1028 (eg, entirely within a single device) are computed. Alternatively, device 1000 may use, for example, a client-server architecture, a 3-tier architecture, an N-tier architecture, a tightly-coupled or clustered architecture, a peer-to-peer architecture (peer- To-peer architecture, a distributed system architecture such as a master-slave architecture, a shared database architecture, and other types of decentralized systems, dispersing the device 500 of Figure 5 and/or System 540, logic flow 600 of Figure 6, logic flow 700 of Figure 7, logic flow 800 of Figure 8, storage medium 900 of Figure 9, and logic circuit 1028 that spans multiple computing entities or Some parts of the structure and / or operation of the many. The embodiments are not limited to this context.

In an embodiment, the radio interface 1010 may comprise a single carrier or a multi-carrier modulated signal suitable for transmitting and/or receiving (eg, including Complementary Code Keying (CCK) and/or orthogonal frequency division). A component or combination of components of an Orthogonal Frequency Division Multiplexing (OFDM) system, but the embodiments are not limited to any particular over-the-air interface or modulation architecture. The radio interface 1010 can include, for example, a receiver 1012, a frequency synthesizer 1014, and/or a transmitter 1016. The radio interface 1010 can include bias control, a crystal oscillator, and/or one or more antennas 1018- f . In another embodiment, the radio interface 1010 can use an external voltage controlled oscillator (VCO), a surface acoustic wave filter, and an intermediate frequency (IF) filter as needed. And/or radio frequency (RF) filters. A detailed description of such RF interface design is omitted due to the many possible RF interface designs.

The baseband circuit 1020 can communicate with the radio interface 1010 to process receive and/or transmit signals, and can include, for example, an analogy to downconverting the received signal to a digital converter 1022 for upconverting the signal for One of the digits is transmitted to the analog converter 1024. In addition, baseband circuit 1020 can include a baseband or physical layer (PHY) processing circuit 1026 for PHY link layer processing of the respective received/transmitted signals. The baseband circuit 1020 can include, for example, a media access control (MAC) processing circuit 1027 for performing MAC/data link layer processing. The baseband circuit 1020 can include a memory controller 1032 for communicating with the MAC processing circuit 1027 and/or a computing platform 1030, such as via one or more interfaces 1034.

In some embodiments, PHY processing circuit 1026 can include a frame Constructing and/or detecting modules for constructing and/or deconstructing frames in conjunction with additional circuitry such as a buffer memory. Alternatively or additionally, MAC processing circuitry 1027 may share processing of some of these functions, or may perform these processes independently of PHY processing circuitry 1026. In some embodiments, the MAC and PHY processing can be integrated into a single circuit.

Computing platform 1030 can provide computing functionality to device 1000. As shown, computing platform 1030 can include a processing component 1040. In the event of or in place of the baseband circuit 1020, the apparatus 1000 can use the processing component 1040 to perform the apparatus 500 and/or system 540 of FIG. 5, the logic flow 600 of FIG. 6, and the logic of FIG. Processing operations or logic of one or more of the flow 700, the logic flow 800 of FIG. 8, the storage medium 900 of FIG. 9, and the logic circuit 1028. Processing component 1040 (and/or PHY 1026 and/or MAC 1027) can include various hardware components, software components, or a combination of the two. Examples of hardware components may include devices, logic devices, components, processors, microprocessors, circuits, processor circuits, circuit components (eg, circuit components such as transistors, resistors, capacitors, and inductors), integrated circuits Application-specific integrated circuits (ASICs), programmable logic devices (PLDs), digital signal processors (DSPs), field programmable gate arrays (FPGAs), memory cells, logic gates, scratchpads, semiconductor devices, wafers Hardware components such as microchips and wafer sets. Examples of software components may include software components, programs, application software, computer programs, applications, system programs, software development programs, machine programs, operating system software, intermediate software, firmware, software modules. Group, routine, subroutine, function, method, program, software interface, application program interface (API), instruction set, opcode, code segment, computer code segment, word, value, code , or any combination of the above. Depending on such calculation rate, power level, heat resistance, processing cycle budget, input data rate, output data rate, memory resources, data bus speed, and any other design or performance limitations required for a particular embodiment, etc. Any number of factors change the decision to implement an embodiment using hardware components and/or software components.

Computing platform 1030 can further include other platform components 1050. Other platform components 1050 include, for example, one or more processors, multi-core processors, coprocessors, memory cells, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia Input/output (I/O) components (eg, digital displays), and common computing components such as power supplies. Examples of memory cells may include, but are not limited to, such as read only memory (ROM), random access memory (RAM), dynamic machine access memory (DRAM), double data rate dynamic machine access memory. (DDRAM), Synchronous Dynamic Machine Access Memory (SDRAM), Static Machine Access Memory (SRAM), Programmable Read Only Memory (PROM), Erasable Programmable Read Only Memory (EPROM), Electrical Erasing programmable read-only memory (EEPROM), flash memory, polymer memory such as ferroelectric polymer memory, bidirectional memory, phase change or ferroelectric memory, germanium-oxide-nitride - Oxide-矽 (SONOS) memory, magnetic card or optical card, such as Redundant Array of Independent Disks drives (referred to as Redundant Array of Independent Disks drives; Device arrays such as RAID), solid state memory devices (eg, Universal Serial Bus (USB) memory, Solid State Drive (SSD), and any other type of media suitable for storing information, etc. Various types of computer readable and machine readable storage media for one or more higher speed memory cells.

The device 1000 may be, for example, a super mobile device, a mobile device, a fixed device, a Machine-to-Machine (M2M) device, a Personal Digital Assistant (PDA), a mobile computing device, a smart phone, Telephone, digital telephone, cell phone, user equipment, eBook reader, mobile phone, one-way pager, two-way pager, communication device, computer, personal computer (PC), desktop computer , laptop, notebook, simple notebook, handheld computer, tablet, server, server array or server farm, web server, web server, internet Web servers, workstations, mini computers, mainframe computers, supercomputers, networking devices, web devices, distributed computing systems, multiprocessor systems, processor-based systems, consumer electronics, programmable consumer electronics, games Devices, displays, televisions, digital TVs, set-top boxes, wireless access points, base stations, Node Bs, subscriber stations, operations User center, radio network controller, router, hub, gateway, bridge, switch, machine, or a combination of the above. Thus, in various embodiments of apparatus 1000, some of the functions and/or specific configurations of apparatus 1000 described herein may be included or omitted as desired.

Embodiments of apparatus 1000 may be implemented using a Single Input Single Output (SISO) architecture. However, some embodiments may use adaptive antenna techniques for beamforming or Spatial Division Multiple Access (SDMA) and/or using multiple input multiple output (MIMO) communication techniques, including Multiple antennas for transmission and/or reception (eg, antennas 1018- f ).

The components and features of device 1000 can be implemented using any combination of discrete circuits, application specific integrated circuits (ASICs), logic gates, and/or single wafer architectures. Moreover, where applicable, the features of device 1000 can be implemented using a microcontroller, a programmable logic array, and/or a microprocessor, or any combination of the above. It is noted that the present invention may collectively refer to or collectively refer to hardware, firmware, and/or software components as "logic" or "circuitry."

It should be understood that the exemplary device 1000 illustrated in the block diagram of FIG. 10 may represent one of the functionally descriptive examples of many possible embodiments. Accordingly, hardware components, circuits, software, and/or components that are used to implement these functions are inevitably divided in various embodiments without the division, omission, or inclusion of the block functions shown in the drawings. , omitted, or included.

Figure 11 shows an embodiment of a broadband wireless access system 1100. As shown in FIG. 11, the broadband wireless access system 1100 may be an Internet Protocol (IP) type network, and the IP type network includes an Internet type 1110 network or the like. Road, the network The road can support mobile wireless access and/or fixed wireless access to the Internet 1110. In one or more embodiments, the broadband wireless access system 1100 can include any type of orthogonal frequency division multiplexed access, such as a system compliant with one or more of the 3GPP LTE specifications and/or the IEEE 802.16 standard. (Orthogonal Frequency Division Multiple Access; OFDMA) wireless network, and the scope of the patent application scope is not limited to these aspects.

In the exemplary broadband wireless access system 1100, Radio Access Network (RAN) 1112 and 1118 can be coupled to evolved Node Bs (eNBs) 1114 and 1120, respectively, to provide one or more fixtures. A wireless connection between 1116 and Internet 1110, and/or a wireless connection between one or more mobile devices 1122 and Internet 1110. An example of a fixture 1116 and a mobile device 1122 is the device 1000 of FIG. 10, wherein the fixture 1116 includes a fixed version of the device 1000 and the mobile device 1122 includes a mobile version of the device 1000. The RANs 1112 and 1118 can implement profiles that can define one or more entities that map network functions to the broadband wireless access system 1100. The eNBs 1114 and 1120 can include radios for providing radio frequency communication with the fixtures 1116 and/or mobile devices 1122, such as described with reference to device 1000, and can include, for example, a PHY that conforms to a 3GPP LTE specification or an IEEE 802.16 standard. And MAC layer devices. The eNBs 1114 and 1120 may further include an IP backplane for coupling to the Internet 1110 via the RANs 1112 and 1118, respectively, but the scope of the patented scope is not limited in these respects.

The broadband wireless access system 1100 can further include a guest core network (Core Network; CN) 1124 and a local CN 1126, each of the core networks being capable of providing, among other things, including but not limited to Authentication, Authorization, and Accounting (Authoration, Authorization and Accounting; AAA) functions, Dynamic Host Configuration Protocol (DHCP) functions, or domain name service agents, etc. Or relay type functions, such as a public switched telephone network (PSTN) gateway or a voice over Internet Protocol (VoIP) gateway, etc. One or more network functions of the Internet, and/or Internet Protocol (IP) type server functions. However, these functions are merely examples of the types of functions that the guest CN 1124 and/or the local CN 1126 can provide, and the scope of the patented scope is not limited in these respects. In the case where the guest CN 1124 is not part of the regular service provider of the fixed device 1116 or the mobile device 1122, for example, when the fixed device 1116 or the mobile device 1122 roams away from its respective local CN 1126, or when broadband wireless storage The fetch system 1100 is part of a regular service provider of the fixed device 1116 or mobile device 1122 but the Internet 1110 may be in another location or state that is not the primary or local location of the fixed device 1116 or mobile device 1122, the guest CN 1124 may Known as a guest CN. The embodiments are not limited to this context.

The fixed device 1116 may be located anywhere within one or both of the eNBs 1114 and 1120, for example, the fixed device 1116 may In or near the home or business, broadband or local access to the Internet 1110 via the eNBs 1114 and 1120 and the RANs 1112 and 1118 and the local CN 1126 is provided. It is worth noting that although the fixture 1116 is typically configured in a fixed position, the fixture 1116 can be moved to a different location as needed. If the mobile device 1122 is within range of one or both of the eNBs 1114 and 1120, the mobile device 1122 can be used at one or more locations. According to one or more embodiments, an Operations Support System (OSS) 1128 may be part of the broadband wireless access system 1100 to provide management functions of the broadband wireless access system 1100, and to provide functional entities and broadband. The interface between the wireless access systems 1100. The broadband wireless access system 1100 of FIG. 11 is merely one type of wireless network showing a certain number of components of the broadband wireless access system 1100, and the scope of the patented scope is not limited in these respects.

The embodiments may be implemented using a hardware component, a software component, or a combination of the two. Examples of hardware components may include processors, microprocessors, circuits, circuit components (eg, circuit components such as transistors, resistors, capacitors, and inductors), integrated circuits, application-specific integrated circuits (ASICs), Hardware components such as Program Logic Devices (PLDs), Digital Signal Processors (DSPs), Field Programmable Gate Arrays (FPGAs), logic gates, scratchpads, semiconductor devices, wafers, microchips, and chipsets. Examples of software may include software components, programs, application software, computer programs, applications, system programs, machine programs, operating system software, intermediate software, firmware, software modules, routines, sub-normals, functions, squares. Method, program, software interface, application interface (API), instruction set, opcode, computer code, code segment, computer code segment, word, value, symbol, or any combination of the above. Can vary depending on any number of factors such as desired calculation rate, power level, heat resistance, processing cycle budget, input data rate, output data rate, memory resources, data bus speed, and other design or performance limitations. The decision of an embodiment is implemented using hardware components and/or software components.

The representative instructions stored in the machine readable medium implement one or more aspects of at least one embodiment, the representative instructions representing various logic within the processor, and the representative instructions being read by a machine This machine will be made to implement the logic of the techniques described herein. This representation, known as "IP core", can be stored on tangible, machine-readable media and supplied to customers or manufacturing facilities for loading to be physically manufactured. The logic or processor manufacturing machine. Certain embodiments may be implemented using a medium or article readable by a machine readable medium or article that can store an instruction or set of instructions that, when executed by a machine The machine performs a method and/or operations in accordance with the embodiments. The machine may include a machine such as any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, or processor, and the like, and may be implemented using any suitable combination of hardware and/or software. This kind of machine. The machine readable medium or article may include, for example, any suitable type of memory unit, memory device, memory item, memory medium, storage device, storage item, storage medium, and/or storage unit, such as: Pump Take-up or non-removable media, erasable or non-erasable media, writable or rewritable media, digital or analog media, hard disk, floppy disk, CD-ROM (Compact Disk Read Only Memory; CD-ROM ), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), optical disc, magnetic media, magneto-optical media, removable memory card or disc, various types A machine-readable medium or item such as a Digital Versatile Disk (DVD), a magnetic tape, or a cassette. Such instructions may include source code, compiled code, literal code, executable code, static code, such as implemented using any suitable high-order, low-order, object-oriented, visual, compiled, and/or literal language. Any suitable type of code, such as a dynamic code, and an encrypted code.

The following examples are related to further embodiments: Example 1 is an evolved packet core network (EPC) node that includes a processor circuit for performing the following operations: receiving an action from a user equipment (UE) a notification of one of the procedures; deciding whether to release a packet data network (PDN) connection provided by a local gateway (L-GW) of the UE; and transmitting a decision to release one of the PDN connections provided by the L-GW, and transmitting A separate request message or a delete talk layer request message to initiate a procedure for releasing the PDN connection provided by the L-GW.

In Example 2, the PDN connection provided by the L-GW of Example 1 may include a Select Internet Protocol Traffic Offload (SIPTO@LN) PDN connection on a regional network, if available.

In Example 3, the processor circuit of any of Examples 1 to 2 may, in the case of optional use, perform the following operations: the PDN connection provided by the L-GW should include one of the unique PDN connections of the UE. Deciding to transmit a separate request message to initiate a separate procedure initiated by a Mobile Management Entity (MME) to release the PDN connection provided by the L-GW.

In Example 4, the processor circuit of any of Examples 1 to 2 can, in the case of alternative use, perform the following operations: the PDN connection provided by the L-GW should not include the unique PDN connection of the UE. One decides to transmit a delete talk layer request message in order to initiate a PDN disconnect procedure requested by an action management entity (MME) and release the PDN connection provided by the L-GW.

In Example 5, the processor circuit of Example 4 can transmit the delete talk layer request message with a cause of a restart request, if it is optional.

In the example 6, the processor circuit of any of the examples 1 to 5 can transmit the separation request message or the deletion session layer request message after the action program, if it is optional.

In Example 7, the action program of any of Examples 1 through 6 may include a Tracking Area Update (TAU) if it is optional.

In the example 8, the action program of any of the examples 1 to 6 may include a handover if it is optional.

Example 9 is the EPC node of any of Examples 1 to 8, the EPC node comprising a radio frequency (RF) transceiver and one or more RF days line.

Example 10 is at least one non-transitory computer readable storage medium, the computer readable storage medium comprising a set of wireless connection management instructions, the set of wireless connection management command responses being executed on a Mobile Management Entity (MME) And causing the MME to perform the following operations: receiving a mobile program control message during a mobile procedure of a user equipment (UE); determining, according to the mobile program control message, selecting the selected Internet communication on a regional network of the UE A protocol traffic offload (SIPTO@LN) packet data network (PDN) connection; and after the action procedure, triggers the SIPTO@LN PDN connection to stop.

In the example 11, the at least one non-transitory computer readable storage medium of the example 10 may include a wireless connection management command if the wireless connection management command response is performed, and the wireless connection management command response is executed on the MME. The MME is caused to perform the following operations: The SIPTO@LN PDN connection determines that one of the unique PDN connections of the UE does not include the PDN disconnection procedure requested by the MME, and triggers the stop of the SIPTO@LN PDN connection.

In the example 12, the at least one non-transitory computer readable storage medium of the example 11 may include a wireless connection management command when the optional storage is available, and the wireless connection management command response is executed on the MME. The MME is caused to perform the following operations: start the PDN disconnection procedure required by the MME under a restart request.

In Example 13, the at least one non-transitory computer readable storage medium of Example 10 may include wireless connection management if it is optional. Instructing, the wireless connection management command response is performed on the MME, and causing the MME to perform the following operation: returning to the SIPTO@LN PDN connection, including one of the unique PDN connections of the UE, initiating an MME-initiated separate procedure, The triggering of the SIPTO@LN PDN connection is initiated.

In Example 14, the action program of any of the examples 10 to 13 may include a Tracking Area Update (TAU) program if the event program is optional, and the action program control message is available for selection. A context response message can be included.

In the example 15, the action program of any one of the examples 10 to 13 may include a handover procedure if the candidate program is optional, and the action program control message may include one if it is optional. Forward relocation request message.

In the example 16, the at least one non-transitory computer readable storage medium of any of the examples 10 to 15 may include a wireless connection management command if the optional storage medium is optional, and the wireless connection management command response Executed on the MME, the MME is caused to perform the following operation: receiving the mobile program control message from a previous serving MME of the UE.

In the example 17, the at least one non-transitory computer readable storage medium of any of the examples 10 to 16 may include a wireless connection management command if the optional storage medium is optional, and the wireless connection management command response Executed on the MME, the MME performs the following operations: receiving the mobile program control message via an S10 interface connection.

Example 18 is a wireless connection management method, which includes the following operations Receiving a notification of a Tracking Area Update (TAU) procedure of a User Equipment (UE); receiving a selected Internet Protocol Traffic Offload (SIPTO) on a regional network for identifying the UE during the TAU procedure @LN) a packet data network (PDN) connection and identifying a context response message of a home area network identifier (LHN-ID) of the UE; and determining, by the processor circuit, based on the LHN-ID Release of SIPTO@LN PDN connection.

In the example 19, the wireless connection management method of the example 18 may include the following operations in the case that the home network of the UE based on the LHN-ID is not changed according to the TAU procedure; Upon decision, the decision does not prompt the release of the SIPTO@LN PDN connection.

In the example 20, the wireless connection management method of the example 18 may include the following operations: in response to the selection, the home network of the UE based on the LHN-ID is changed according to the TAU procedure. Decide, and decide to promote the release of the SIPTO@LN PDN connection.

In Example 21, the wireless connection management method of Example 20 may include the following operations if it is optional: determining whether the SIPTO@LN PDN connection is a unique PDN connection for the UE.

In Example 22, the wireless connection management method of Example 21 may include the following operations: initiating a PDN disconnect procedure based on the SIPTO@LN PDN connection being one of the unique PDN connections of the UE. And prompt the release of the SIPTO@LN PDN connection.

In Example 23, the wireless connection management method of Example 22 is available. In the case of selection, the following operations may be included: the PDN disconnection procedure is started under a restart request.

In the example 24, the wireless connection management method of the example 21 may include the following operations in the case where the SIPTO@LN PDN connection is one of the UE's unique PDN connections, starting a separate procedure, and Promote the release of the SIPTO@LN PDN connection.

In the example 25, the wireless connection management method of any of the examples 18 to 23 may include the following operations in the case of optional use: receiving the context response message from an old MME of the UE.

Example 26 is at least one non-transitory computer readable storage medium, the computer readable storage medium comprising a set of instructions that are executed on a computing device, and the computing device is executed according to Example 18 One of the 25 examples of wireless connection management methods.

The example 27 is a device including means for performing the wireless connection management method according to any one of the examples 18 to 25.

Example 28 is a system comprising a device according to example 27, a radio frequency (RF) transceiver, and one or more RF antennas.

Example 29 is a Mobile Management Entity (MME), the MME containing logic, at least a portion of which is in the form of a hardware, the logic performing the following operations: receiving a mobile program control message during a mobile procedure of a User Equipment (UE) Determining a selected Internet Protocol Traffic Offload (SIPTO@LN) Packet Data Network (PDN) connection on a local area network of the UE based on the mobile program control message; and triggering the SIPTO after the action procedure The @LN PDN connection is stopped.

In Example 30, the logic of Example 29 can perform the following operations if it is optional: a SIPTO@LN PDN connection is determined by one of the unique PDN connections that do not include the UE, and a PDN cutoff required by an MME is initiated. The program starts while the SIPTO@LN PDN connection is triggered to stop.

In Example 31, the logic of Example 30, in the case where it is optional, can perform the following operations: Start the PDN shutdown procedure required by the MME under a restart request.

In Example 32, the logic of Example 29 can be implemented in the alternative: the SIPTO@LN PDN connection should be determined by one of the unique PDN connections containing the UE, and an MME-initiated split procedure is initiated, and Trigger the start of the SIPTO@LN PDN connection.

In the example 33, the action program of any of the examples 29 to 32 may include a tracking area update (TAU) program if the optional program is available, and the action program control message is available for selection. A context response message can be included.

In the example 34, the action program of any of the examples 29 to 32 may include a handover procedure if the candidate program is optional, and the action program control message may include one if it is optional. Forward relocation request message.

In the example 35, the logic of any of the examples 29 to 34 may, in the case of alternative use, perform the operation of receiving the mobile program control message from a previous serving MME of the UE.

In Example 36, the logic of any of Examples 29 through 35 In the case where it is optional, the following operations can be performed: receiving the mobile program control message via an S10 interface connection.

Example 37 is the MME of any of Examples 29 to 36, the MME comprising a radio frequency (RF) transceiver and one or more RF antennas.

Example 38 is at least one non-transitory computer readable storage medium, the computer readable storage medium including a set of wireless connection management instructions, the set of wireless connection management command responses being executed on a Mobile Management Entity (MME) And causing the MME to perform one of: receiving a notification of a Tracking Area Update (TAU) procedure of a User Equipment (UE); during the TAU procedure, receiving a selected Internet on a regional network for identifying the UE a traffic protocol offload (SIPTO@LN) packet data network (PDN) connection and identifying a context response message of a home area network identifier (LHN-ID) of the UE; and determining whether based on the LHN-ID Promote the release of the SIPTO@LN PDN connection.

In the example 39, the at least one non-transitory computer readable storage medium of the example 38 may include a wireless connection management command when the optional storage is available, and the wireless connection management command response is executed on the MME. And causing the MME to perform the following operation: responding to a home area network of the UE based on the LHN-ID according to the TAU procedure without changing one of the decisions, and deciding not to prompt release of the SIPTO@LN PDN connection.

In the example 40, the at least one non-transitory computer readable storage medium of the example 38 may include a wireless connection management command in the case of optional use, and the wireless connection management command response is executed on the MME. And causing the MME to perform the following operations: the response is based on the LHN-ID A home area network of the UE is determined according to one of the changes in the TAU procedure, and the decision is made to prompt the release of the SIPTO@LN PDN connection.

In the example 41, the at least one non-transitory computer readable storage medium of the example 40 may include a wireless connection management command when the optional storage is available, and the wireless connection management command response is executed on the MME. The MME is caused to perform the following operations: Decide whether the SIPTO@LN PDN connection is a unique PDN connection of the UE.

In the example 42, the at least one non-transitory computer readable storage medium of the example 41 may include a wireless connection management command when the optional storage is available, and the wireless connection management command response is executed on the MME. And causing the MME to perform the following operation: according to the SIPTO@LN PDN connection is not one of the UE's unique PDN connections, start a PDN disconnect procedure, and prompt the release of the SIPTO@LN PDN connection.

In the example 43, the at least one non-transitory computer readable storage medium of the example 42 may include a wireless connection management command if the wireless connection management command response is performed, and the wireless connection management command response is executed on the MME. The MME is caused to perform the following operation: starting the PDN disconnection procedure under a restart request.

In the example 44, the at least one non-transitory computer readable storage medium of the example 41 may include a wireless connection management command when the optional storage is available, and the wireless connection management command response is executed on the MME. And causing the MME to perform the following operation: according to the SIPTO@LN PDN connection is one of the UE's unique PDN connections, start a separate procedure, and prompt the release of the SIPTO@LN PDN connection.

In Example 45, the MME of any of Examples 38 to 44 may include one of the UE's new MMEs after the TAU procedure, and the MME is available for selection. The context response message can be received from an old MME of the UE.

Example 46 is a wireless connection management method, the method comprising: receiving a forward relocation request on a handover target action management entity (MME) of a user equipment (UE); Determining, to the relocation request, that a packet data network (PDN) connection provided by one of the local gateways (L-GWs) of the UE is to be disconnected; and whether the PDN connection provided according to the L-GW includes the unique PDN of the UE One of the connections determines the procedure for disconnecting one of the PDN connections provided by the L-GW.

In Example 47, the PDN connection provided by the L-GW of Example 46 may include a Select Internet Protocol Traffic Offload (SIPTO@LN) PDN connection on a regional network, if available.

In the example 48, the wireless connection management method of any of the examples 46 to 47 may include the following operations in the case of optional use: after the handover of the UE, the selected program is started, and The PDN connection provided by the L-GW is cut off.

In the example 49, the wireless connection management method of any of the examples 46 to 48 may include the following operations in the case of optional adoption: the PDN connection provided by the L-GW includes a unique PDN connection of the UE. Upon decision, a separate procedure initiated by the MME is selected.

In example 50, the wireless of any of the examples 46 to 48 The connection management method may include the following operations: the PDN connection provided by the L-GW is determined by one of the unique PDN connections of the UE, and the PDN disconnect procedure required by the MME is selected.

In the example 51, the wireless connection management method of the example 50 may include the following operations in the case where it is optional: the PDN disconnection procedure required by the MME is initiated under a restart request.

In the example 52, the wireless connection management method of any of the examples 46 to 51 may include the following operations in the case of optional use: receiving the forward relocation request from a handover source MME of the UE.

In the example 53, the wireless connection management method of any of the examples 46 to 52 may include the following operations in the case of optional use: according to the forward relocation requirement, and according to a home area network of the UE The way (LHN) does not change one of the decisions during the handover of the UE, but decides to disconnect the PDN connection provided by the L-GW of the UE.

Example 54 is at least one non-transitory computer readable storage medium, the computer readable storage medium comprising a set of instructions that are executed on a computing device, and the computing device is executed according to example 46 One of the examples of 53 is a wireless connection management method.

The example 55 is a device including means for performing the wireless connection management method according to any one of the examples 46 to 53.

Example 56 is a system comprising a device according to example 55, a radio frequency (RF) transceiver, and one or more RF antennas.

Example 57 is a Mobile Management Entity (MME), the MME comprising a processor circuit that performs the following operations: receiving a user Notification by one of the Tracking Area Update (TAU) procedures of the device (UE); during the TAU procedure, receiving selected Internet Protocol Traffic Offload (SIPTO@LN) packet data on a local area network for identifying the UE A network (PDN) connects and identifies a context response message of a home area network identifier (LHN-ID) of the UE; and determines whether to cause release of the SIPTO@LN PDN connection based on the LHN-ID.

In the example 58, the processor circuit of the example 57 can, in the case of being selectively employed, perform the following operations: responding to a home area network of the UE based on the LHN-ID according to the TAU procedure without changing one Decide, and decide not to promote the release of the SIPTO@LN PDN connection.

In the example 59, the processor circuit of the example 57 can, in the case of optional use, perform the following operations: responding to a home area network of the UE based on the LHN-ID, determining one of the changes according to the TAU procedure And decided to promote the release of the SIPTO@LN PDN connection.

In example 60, the processor circuit of example 59 can, in the alternative, perform the following operations: Decide whether the SIPTO@LN PDN connection is a unique PDN connection for the UE.

In the example 61, the processor circuit of the example 60 can, in the case of optional use, perform the following operations: start a PDN disconnection procedure based on the SIPTO@LN PDN connection being one of the unique PDN connections of the UE, And the release of the SIPTO@LN PDN connection is prompted.

In the example 62, the processor circuit of the example 61 can, in the case of alternative use, perform the following operations: starting the PDN shutdown procedure for a restart request.

In the example 63, the processor circuit of the example 60 can, in the case of optional use, perform the following operations: according to the SIPTO@LN PDN connection is one of the UE's unique PDN connections, start a separate procedure, and cause The release of the SIPTO@LN PDN connection.

In the example 64, the MME of any of the examples 57 to 63 may include one of the UE's new MMEs after the TAU procedure, and the processor circuit is available for selection. In this case, the context response message can be received from an old MME of the UE.

Example 65 is the MME of any of examples 57 to 64, the MME comprising a radio frequency (RF) transceiver and one or more RF antennas.

Example 66 is at least one non-transitory computer readable storage medium, the computer readable storage medium including a set of wireless connection management commands, the set of wireless connection management command responses being executed on a computing device, The computing device performs the following operations: receiving a forward relocation request on a handover target action management entity (MME) of a user equipment (UE); determining, based on the forward relocation request, that one of the UEs is to be disconnected locally a packet data network (PDN) connection provided by a gateway (L-GW); and selected to cut off the L-GW according to whether the PDN connection provided by the L-GW includes one of the UE's unique PDN connections One of the programs provided for the PDN connection.

In Example 67, the PDN connection provided by the L-GW of Example 66 may include a Select Internet Protocol Traffic Offload (SIPTO@LN) PDN connection on a regional network, if available.

In Example 68, the at least one of the examples 66 to 67 is at least A non-transitory computer readable storage medium can optionally include wireless connection management instructions that are executed on a computing device to cause the computing device to perform the following operations: After the handover of the UE, the selected procedure is initiated and the PDN connection provided by the L-GW is disconnected.

In the example 69, the at least one non-transitory computer readable storage medium of any of the examples 66 to 68 may include a wireless connection management command if the optional storage medium is optional, and the wireless connection management command response Executing on the computing device causes the computing device to perform the following operations: a PDN connection provided by the L-GW is determined by one of the unique PDN connections of the UE, and an MME initiated separation procedure is selected.

In the example 70, the at least one non-transitory computer readable storage medium of any of the examples 66 to 68 may include a wireless connection management command if the optional storage medium is optional, and the wireless connection management command response Executing on the computing device, causing the computing device to perform the following operations: the PDN connection provided by the L-GW is determined to be one of the unique PDN connections of the UE, and the PDN disconnect procedure requested by the MME is selected.

In example 71, the at least one non-transitory computer readable storage medium of the example 70 can include wireless connection management instructions that are executed on the computing device if the optional storage medium is optional. And causing the computing device to perform the following operations: to initiate the PDN disconnection procedure required by the MME under a restart request.

In Example 72, the at least one non-transitory computer readable storage medium of any of Examples 66 to 71 is optionally operative. A wireless connection management command can be included, the wireless connection management command response being performed on the computing device, and causing the computing device to perform the operation of receiving the forward relocation request from a handover source MME of the UE.

In the example 73, the at least one non-transitory computer readable storage medium of any one of the examples 66 to 72 may include a wireless connection management command if the optional storage medium is optional, and the wireless connection management command response Executing on the computing device, causing the computing device to perform the following operations: according to the forward relocation request, and according to a Home Network (LHN) of the UE, one of the handovers of the UE does not change during the handover Decide, and decide to cut off the PDN connection provided by the L-GW of the UE.

Example 74 is a wireless connection management method, the method comprising the steps of: receiving a notification of a mobile program of a user equipment (UE); determining, by a processor circuit, whether to release a local gateway of the UE (L-GW) Providing a packet data network (PDN) connection; and responding to a decision to release one of the PDN connections provided by the L-GW, transmitting a separate request message or deleting a session request message to initiate the release of the L- A program for the PDN connection provided by GW.

In Example 75, the LDN provided by the L-GW of Example 74 can optionally include a Select Internet Protocol Traffic Offload (SIPTO@LN) PDN connection on a regional network.

In the example 76, the wireless connection management method of any of the examples 74 to 75 may include the following operations in the case of optional adoption: the PDN connection provided by the L-GW should include the unique PDN connection of the UE. a decision to transmit a separate request message in order to initiate a action tube The MME initiates a separate procedure and releases the PDN connection provided by the L-GW.

In the example 77, the wireless connection management method of any of the examples 74 to 75 may include the following operations in the case of optional adoption: the PDN connection provided by the L-GW does not include the unique PDN of the UE. One of the connections determines, and a delete session layer request message is transmitted to initiate a PDN disconnect procedure requested by the Mobile Management Entity (MME), and the PDN connection provided by the L-GW is released.

In the example 78, the wireless connection management method of the example 77 may include the following operations in the case of optional use: transmitting the delete talk layer request message with a cause of a restart request.

In the example 79, the wireless connection management method of any of the examples 74 to 78 may include the following operations in the case of optional use: after the action procedure, transmitting the separation request message or the deletion session layer requirement message.

In the example 80, the action program of any of the examples 74 through 79 may include a Tracking Area Update (TAU) if it is optional.

In the example 81, the action program of any of the examples 74 to 80 may include a handover if it is optional.

Example 82 is at least one non-transitory computer readable storage medium, the computer readable storage medium including a set of instructions that are executed on a computing device, and the computing device is executed according to example 74 A wireless connection management method of any of the examples 81.

The example 83 is a device including means for performing the wireless connection management method according to any one of the examples 74 to 81.

Example 84 is a system comprising a device according to example 83, a radio frequency (RF) transceiver, and one or more RF antennas.

Example 85 is an evolved packet core network (EPC) node, the EPC node containing logic, at least a portion of which is in the form of a hardware, the logic performing the following operations: a handover target action on a user equipment (UE) Receiving a forward relocation request on the management entity (MME); determining, according to the forward relocation request, that a packet data network (PDN) connection provided by a local gateway (L-GW) of the UE is to be disconnected; And selecting one of the procedures for disconnecting the PDN connection provided by the L-GW according to whether the PDN connection provided by the L-GW includes one of the UE's unique PDN connections.

In Example 86, the LPN provided by the L-GW of Example 85 may optionally include a Select Internet Protocol Traffic Offload (SIPTO@LN) PDN connection on a regional network.

In the example 87, the logic of any of the examples 85 to 86 may, in the case of alternative use, perform the following operations: after the handover of the UE, the selected program is started, and the program is turned off. The PDN connection provided by the L-GW.

In the example 88, the logic of any of the examples 85 to 87 may, in the case of alternative use, perform the following operations: the PDN connection provided by the L-GW is determined by one of the unique PDN connections of the UE, Instead, a separate program initiated by the MME is selected.

In Example 89, the logic of any of the examples 85 through 87 may, in the case of alternative use, perform the following operations: the PDN connection provided by the L-GW is determined by one of the unique PDN connections not including the UE. And select a PDN cutoff procedure required by the MME.

In the example 90, the logic of the example 89 can be used to selectively initiate the PDN shutdown procedure required by the MME for a restart request.

In Example 91, the logic of any of Examples 85-90 can, in the alternative, perform the following operations: receiving the forward relocation request from a handover source MME of the UE.

In Example 92, the logic of any of Examples 85-91 may, in the alternative, perform the following operations: according to the forward relocation requirement, and according to a home area network (LHN of the UE) The one decision is not changed during the handover of the UE, and the PDN connection provided by the L-GW of the UE is determined to be disconnected.

Example 93 is the EPC node of any of Examples 85-92, the EPC node comprising a radio frequency (RF) transceiver and one or more RF antennas.

Example 94 is at least one non-transitory computer readable storage medium, the computer readable storage medium including a set of wireless connection management instructions, the set of wireless connection management command responses being executed on a Mobile Management Entity (MME) And causing the MME to perform the following operations: receiving a notification of one of the mobile devices (UE), and deciding whether to release a packet data network (PDN) connection provided by a local gateway (L-GW) of the UE. ;as well as In response to a decision to release one of the PDN connections provided by the L-GW, a separate request message or a delete session request message is transmitted to initiate a procedure for releasing the PDN connection provided by the L-GW.

In Example 95, the PDN connection provided by the L-GW of Example 94 may include a Select Internet Protocol Traffic Offload (SIPTO@LN) PDN connection on a regional network, if available.

In the example 96, the at least one non-transitory computer readable storage medium of any one of the examples 94 to 95 may include a wireless connection management command if the optional storage medium is optional, and the wireless connection management command response is The MME is executed, and the MME performs the following operations: the PDN connection provided by the L-GW is determined by one of the unique PDN connections of the UE, and a separation request message is transmitted to start an action management entity (MME). The separate program is initiated and the PDN connection provided by the L-GW is released.

In the example 97, the at least one non-transitory computer readable storage medium of any of the examples 94 to 95 may include a wireless connection management command if the optional storage medium is optional, and the wireless connection management command response Executed on the MME, the MME performs the following operations: the PDN connection provided by the L-GW does not include one of the UE's unique PDN connections, and a delete session layer request message is sent to initiate an action. The PDN disconnection procedure required by the Management Entity (MME) releases the PDN connection provided by the L-GW.

In Example 98, the at least one non-transitory computer readable storage medium of Example 97 can include wireless connection management if it is optional. Instructing that the wireless connection management command response is performed on the MME, and causing the MME to perform the operation of transmitting the delete talk layer request message with a cause of a restart request.

In the example 99, the at least one non-transitory computer readable storage medium of any of the examples 94 to 98 may include a wireless connection management command if the optional storage medium is optional, and the wireless connection management command response Executed on the MME, the MME is caused to perform the following operations: after the action procedure, transmitting the split request message or the delete talk layer request message.

In the example 100, the action program of any of the examples 94 through 99 may include a Tracking Area Update (TAU) if it is optional.

In the example 101, the action program of any of the examples 94 to 99 may include a handover if it is optional.

Example 102 is a wireless connection management method, the method comprising: receiving a mobile program control message during a mobile program of a user equipment (UE); and deciding to release the UE by a processor circuit according to the mobile program control message Selecting an Internet Protocol Traffic Unload (SIPTO@LN) Packet Data Network (PDN) connection on a local area network; and after the action procedure, triggering the SIPTO@LN PDN connection to stop starting.

In the example 103, the wireless connection management method of the example 102 may include the following operations in the case of optional use: the SIPTO@LN PDN connection is determined by one of the unique PDN connections not including the UE, and is initiated. A PDN disconnection procedure requested by the MME triggers the stop of the SIPTO@LN PDN connection.

In the example 104, the wireless connection management method of the example 103 may include the following operations in the case where it is optional: the PDN disconnection procedure required by the MME is initiated under a restart request.

In the example 105, the wireless connection management method of the example 102 may include the following operations in the case where it is optional: a SIPTO@LN PDN connection is determined by one of the unique PDN connections including the UE, and an MME startup separation is initiated. The program starts while the SIPTO@LN PDN connection is triggered to stop.

In the example 106, the action program of any of the examples 102 to 105 may include a Tracking Area Update (TAU) program if the event program is available for selection, and the action program control message is available for selection. A context response message can be included.

In the example 107, the action program of any of the examples 102 to 105 may include a handover procedure if the candidate program is optional, and the action program control message may include one if it is optional. Forward relocation request message.

In the example 108, the wireless connection management method of any of the examples 102 to 107 may, in the case of alternative use, include the operation of receiving the mobile program control message from a previous serving MME of the UE.

In the example 109, the wireless connection management method of any of the examples 102 to 108 may include the following operations in the case where it is optional. Action: Receive the mobile program control message via an S10 interface connection.

Example 110 is at least one non-transitory computer readable storage medium, the computer readable storage medium including a set of instructions that are executed on a computing device, and the computing device is executed according to example 102 A wireless connection management method of any of the examples 109.

The example 111 is a device including means for performing a wireless connection management method according to any one of the examples 102 to 109.

Example 112 is a system comprising a device according to example 111, a radio frequency (RF) transceiver, and one or more RF antennas.

The present invention has been described in many specific details in order to provide a thorough understanding of the embodiments. However, it will be understood by those skilled in the art that the embodiments may be practiced without these specific details. In other instances, well-known operations, components, and circuits have not been described in detail so as not to obscure the invention. It should be understood that the specific details of the structure and function of the invention disclosed herein may be representative, and not to limit the scope of the embodiments.

Certain embodiments may be described using the words "coupled" and "connected" and their derivatives. These terms will not be synonymous with each other. For example, the terms "connected" and/or "coupled" may be used to describe certain embodiments to indicate that two or more elements are in physical or electrical contact with each other. However, the term "coupled" may also mean that two or more elements are not in direct contact with each other, but still cooperate or function with each other.

Unless otherwise stated, we should be able to understand that terms such as "processing", "operation", "calculation", or "decision" mean computer Or the operation and/or processing of a computing system or similar electronic computing device, and such computing system operates and/or transforms the data stored in the scratchpad and/or memory of the computing system as physical quantities (eg, electronic). Other data that is also physically present in the memory, scratchpad, or other such information storage device, transmission device, or display device of the computing system. The embodiments are not limited to this context.

It is noted that the methods described herein are not required to be performed in the order described or in any order. Moreover, various actions described in connection with the methods identified in the present invention may be performed in a continuous or parallel manner.

While the present invention has been shown and described with respect to the specific embodiments, it should be understood that any configuration that can achieve the same objectives can be substituted for the particular embodiments shown. The disclosure of the present invention is intended to cover any and all modifications and variations of the embodiments. It should be understood that the foregoing description is provided by way of example and not limitation. Those skilled in the art will be able to readily appreciate the various combinations of the above-described embodiments, as well as other embodiments not specifically described in this specification. Accordingly, the scope of the various embodiments includes any other application of the components, structures, and methods described above.

It is emphasized herein that the "Summary of Invention" is provided in order to comply with the requirements of 37 C.F.R. § 1.72(b) which will allow the reader to determine the essence of the disclosure of the technology. The "Summary of the Invention" is submitted with the understanding that the "Summary of the Invention" will not be used to interpret or limit the scope or meaning of the scope of the patent application. Further, in the foregoing "embodiment", it can be seen that the features are classified into a single embodiment in order to make the disclosure clear. The invention should not be The method disclosed is intended to reflect the intent of the features described in the claims and the embodiments of the invention. Rather, as the subject matter of the appended claims, the subject matter of the invention may be characterized in less than all features of a single disclosed embodiment. Therefore, the scope of each of the patent applications is hereby incorporated by reference in its entirety in its entirety in its entirety in the the the the the the In the scope of the last patent application, the terms "including" and "in" are used as the ordinary English synonym for the respective terms "including" and "in". Moreover, the terms "first", "second", and "third" are used merely as a mark, and are not intended to imply the requirement of the number.

Although the subject matter of the present invention has been described in language relating to structural features and/or methodological actions, it is to be understood that the subject matter defined in the scope of the final application is not necessarily limited to the specific features or actions described hereinabove. . Rather, the specific features and acts described above are disclosed as an exemplification of the scope of the application.

100‧‧‧ Operating environment

102‧‧‧User equipment

104‧‧‧Home Evolved Node B

106‧‧‧Action Management Entity

108‧‧‧service gateway

110‧‧‧Package data network gateway

112‧‧‧Local gateway

120‧‧‧Internet

Claims (25)

An action management entity (MME) comprising: one or more radio frequency (RF) transceivers; one or more RF antennas; and logic, at least a portion of which is in hardware, the logic to perform the following operations: Receiving a forward relocation request during a handover procedure of a user equipment (UE); determining, according to the forward relocation requirement, whether the home area network of the user equipment changes, according to the home area network of the user equipment Whether the path changes and after the handover procedure, decide whether to maintain the selected Internet Protocol traffic offload (SIPTO@LN) packet data network (PDN) connection on a local area network of the user equipment, and respond to the user equipment The home area network does not change one of the decisions, maintaining the SIPTO@LN PDN connection. The MME of claim 1, wherein the logic is used to determine the home area of the user equipment according to the handover procedure based on a home area network identifier (ID) included in the forward relocation request. Whether the network has changed. For example, in the MME of claim 1, wherein the logic is used to initiate a procedure and one of the home area network changes of the user equipment is determined to release the SIPTO@LN PDN connection, the logic is based on whether the SIPTO is The @LN PDN connection selects one of the unique PDN connections for the user device and selects the program. For example, the MME of the third application patent scope, wherein the logic is used to perform the following operations: the SIPTO@LN PDN connection should not be included. One of the unique PDN connections of the device determines that a PDN disconnect procedure requested by the MME is initiated to release the SIPTO@LN PDN connection. For example, the MME of claim 4, wherein the logic is used to transmit a delete session layer request to initiate the PDN disconnect procedure required by the MME. For example, the MME of claim 5, wherein the logic is used to transmit the deletion negotiation layer requirement with a restart request reason. For example, in the MME of claim 3, the logic is used to perform the following operations: a SIPTO@LN PDN connection is determined by one of the unique PDN connections including the user equipment, and an MME initiated separation procedure is initiated to release the SIPTO@ LN PDN connection. An action management entity (MME) comprising: at least one radio frequency (RF) transceiver; at least one RF antenna; and logic, at least a portion of the logic being in hardware, the logic to perform the following operations: in a user equipment After a Tracking Area Update (TAU) procedure of the (UE), determining whether to release the selected Internet on a regional network of the user equipment based on the home area network identifier (ID) included in the received context response message The protocol traffic offload (SIPTO@LN) packet data network (PDN) connection, which includes a connection via a separate gateway (GW) to a packet data network. For example, in the MME of claim 8, wherein the logic is used to determine a home area of the user equipment based on the home area network identifier Whether the network changes, and whether the home area network of the user equipment changes, and whether to release the SIPTO@LN PDN connection. For example, in the MME of claim 9th, the logic is used to determine that the home area network of the user equipment does not change, and decides not to release the SIPTO@LN PDN connection. For example, the MME of claim 9th, wherein the logic is used to respond to the decision of the home area network change of the user equipment, and decide to release the SIPTO@LN PDN connection. For example, in the MME of claim 11, wherein the logic is used to perform the following operations: the SIPTO@LN PDN connection is determined by one of the unique PDN connections including the user equipment, and an MME-initiated separate procedure is used to release the SIPTO@ LN PDN connection. For example, the MME of claim 12, wherein the logic is used to transmit a separation request to initiate the separation procedure initiated by the MME. A non-transitory computer readable storage medium comprising a set of instructions, the set of command responses being executed in an Action Management Entity (MME), and causing the MME to perform the following operations: receiving a user equipment (UE) Receiving a forward relocation request message during a handover; and, after the handover, determining whether to release the selected Internet Protocol traffic offload on a local area network of the user equipment based on the forward relocation request message ( SIPTO@LN) A packet data network (PDN) connection that includes a connection to a packet data network via a separate gateway (GW). The at least one non-transitory computer readable storage medium of claim 14 includes instructions, wherein the command responses are executed at the MME, and the MME performs the following operations: based on the forward relocation request message Determining whether the home area network of the user equipment changes due to the handover; and after the handover, whether the home area network of the user equipment changes due to the handover, whether to release the SIPTO@LN PDN connection. The at least one non-transitory computer readable storage medium of claim 15 includes instructions, wherein the command responses are executed at the MME, and the MME performs the following operations: based on the forward relocation included The home area network identifier (ID) of the request message determines whether the home area network of the user equipment changes due to the handover. The at least one non-transitory computer readable storage medium of claim 15 includes instructions, wherein the command responses are executed at the MME, and the MME performs the following operations: after the handover, the response is The home area network of the user equipment decides to maintain the SIPTO@LN PDN connection due to the handover without changing one of the decisions. The at least one non-transitory computer readable storage medium of claim 15 includes instructions, wherein the command responses are executed at the MME, and the MME performs the following operations: after the handover, the response is The home area network of the user equipment decides to release the SIPTO@LN PDN connection due to one of the handover changes. At least one non-transitory computer readable as in claim 18 The fetched storage medium includes instructions, the command responses being executed at the MME, and causing the MME to perform an operation of selecting a program to release the SIPTO based on whether the SIPTO@LN PDN connection includes a unique PDN connection of the user equipment @LN PDN connection. A non-transitory computer readable storage medium comprising a set of instructions that are executed in a Mobile Management Entity (MME) to cause the MME to perform the following operations: a tracking of a User Equipment (UE) After the area update (TAU) procedure, based on whether the home area network of the user equipment changes, whether to release the selected Internet Protocol Traffic Unloading (SIPTO@LN) packet data network on a local area network of the user equipment ( PDN) connection, the SIPTO@LN PDN connection includes a connection via a separate gateway (GW) to a packet data network; and the home area network that decides not to release the SIPTO@LN PDN connection and back to the user equipment The road does not change the decision. At least one non-transitory computer readable storage medium as claimed in claim 20, comprising instructions, the instruction responses being executed at the MME, and causing the MME to perform the following operations: based on the received context response message The home area network identifier (ID) determines whether the home area network of the user equipment changes. At least one non-transitory computer readable storage medium, as claimed in claim 20, includes instructions that are executed at the MME, and cause the MME to perform the following operations: deciding to release the SIPTO@LN PDN connection And the home network of the user equipment should be changed. set. The at least one non-transitory computer readable storage medium of claim 22 includes instructions, wherein the command response is executed at the MME, and the MME performs the following operations: the SIPTO@LN PDN connection is not One of the unique PDN connections containing the user equipment determines to use the PDN disconnect procedure requested by the MME to release the SIPTO@LN PDN connection. At least one non-transitory computer readable storage medium as claimed in claim 23, comprising instructions, wherein the command response is executed at the MME, and causing the MME to transmit a delete session layer request to initiate the MME request PDN cuts off the program. At least one non-transitory computer readable storage medium as claimed in claim 24, comprising instructions, wherein the command response is executed at the MME, and causing the MME to transmit the deletion session layer request having a restart request reason .