TW201810994A - Solution for local breakout in cellular network - Google Patents

Abstract

An apparatus of a traffic offloading function (TOF) may comprise a processor to detect a destination address of a traffic associated with a user equipment (UE) from a first base station and to determine whether to offload the traffic from the first base station to a first server or a second server based on the destination address; and a transmitter coupled to the processor, to transmit the traffic to the first server in response to the processor determining that the destination address of the traffic is destined to the first server and to transmit the traffic to the second server in response to the processor determining that the traffic not destined to the first server meets a local breakout policy.

Description

Solution for local distribution in a cellular network

The present invention relates to a solution for sinking in a local domain of a cellular network.

Wireless mobile communication technologies use various standards and protocols to provide telecommunications services to fixed or mobile users, such as base stations and wireless mobile devices. In a Third Generation Mobile Communications Partnership Project (3GPP) Long Term Evolution (LTE) system, a base station may be an evolved Node B (eNode B or eNB) that communicates with a wireless mobile device (referred to as a User Equipment (UE)).

100,200‧‧‧Network

110,204‧‧‧eNB

112,122,712‧‧‧transmitters

114,124,714‧‧ ‧ controller

116,126,716‧‧‧ Receiver

118,128,718‧‧‧Antenna

120‧‧‧UE

204s‧‧‧Source eNB

204t‧‧‧Target eNB

206‧‧‧SGW

208‧‧‧PGW

210‧‧‧Regional Network

212‧‧‧TOF

212s‧‧‧Source TOF

212t‧‧‧Target TOF

214‧‧‧Regional Application Service (AS)

216‧‧‧External AS

220‧‧‧Serving LAN server

230‧‧‧Internet

232‧‧‧DNS server

502‧‧‧Handing Request Message

504‧‧‧Dialog migration request

506‧‧‧Dialog migration request confirmation

508‧‧‧Dialog relay request

510‧‧‧Dialog relay request confirmation

512‧‧‧Traffic flow

514‧‧‧Dialog relay termination request

516‧‧‧Dialog relay termination request confirmation

600‧‧‧Information

610‧‧‧Connection list

612‧‧‧Background information

614‧‧‧IP address

616‧‧‧埠 number

700‧‧‧ Equipment

800,900‧‧‧ system

802‧‧‧eNB interface

804‧‧‧SGW interface

806‧‧‧AS interface

808‧‧‧Internet interface

810‧‧Depacking/packaging module

812‧‧‧Destination/source address check module or unit

814‧‧‧Unloading module

816‧‧‧Local Divide Strategy Check Module

818‧‧‧NAT module

820‧‧‧Dialog migration module

822‧‧‧Dialog relay module

824‧‧‧DNS proxy

830,920‧‧‧ processor

832,922‧‧‧ memory

840‧‧‧ transceiver

902‧‧‧TOF interface

904‧‧‧Service Server Interface

910‧‧‧DNS query check module

912‧‧‧ address acquisition module

914‧‧‧DNS Query Response Module

916‧‧‧Package Module or Unit

920‧‧‧ processor

922‧‧‧ memory

1002‧‧‧ display

1004‧‧‧ camera

1006‧‧‧Sensor

1008‧‧‧Input/Output (I/O) interface

1010‧‧‧Application Circuit

1020‧‧‧baseband circuit

1020a‧‧‧Second Generation (2G) Baseband Processor

1020b‧‧‧, third generation (3G) baseband processor

1020c‧‧‧ fourth generation (4G) baseband processor

1020d‧‧‧Other baseband processors

1020e‧‧‧Central Processing Unit

1020f‧‧‧Video Digital Signal Processor (DSP)

1030‧‧‧ Radio Frequency (RF) Circuit

1030a‧‧‧Mixer circuit

1030b‧‧‧Amplifier Circuit

1030c‧‧‧Filter circuit

1030d‧‧‧Synthesizer circuit

1040‧‧‧Memory/storage

1050‧‧‧Antenna

1060‧‧‧ Front End Module (FEM) Circuit

The disclosure herein is illustrated by way of example and not of limitation. The elements shown in the figures are not necessarily drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. In addition, where the appropriateness is taken into consideration, the component numbers repeated in the drawing are used to indicate Corresponding or similar components. The description of the present invention will be apparent from the accompanying drawings, in which

1 is a block diagram schematically showing an example of a wireless network in accordance with various embodiments.

2 is a block diagram schematically showing an example of a wireless network in accordance with various embodiments.

3 is a flow chart diagrammatically showing an example of one or more programs in accordance with various embodiments.

4 is an illustration of an example of one or more programs diagrammatically in accordance with various embodiments.

FIG. 5 is a diagram schematically showing an example of one or more programs in accordance with various embodiments.

6 is an illustration of an example of a handover request message diagrammatically in accordance with various embodiments.

7 is a block diagram schematically showing an example of an electronic device circuit in accordance with various embodiments.

FIG. 8 is a block diagram schematically showing an example of a system in accordance with various embodiments.

9 is a block diagram schematically showing an example of a system in accordance with various embodiments.

10 is a block diagram schematically showing an example of a system in accordance with various embodiments.

Reference will now be made to the exemplary embodiments shown, and The language is defined to describe them. However, it should be understood that it is not intended to limit the scope of the disclosure.

SUMMARY OF THE INVENTION AND EMBODIMENT

Before the present invention is disclosed and described, it is understood that the disclosure is not limited to the specific structures, processing acts or materials of the invention, which can be extended to the equivalents of those of ordinary skill in the art. It is to be understood that the terminology employed herein is for the purpose of the description The same component numbers in different figures represent the same components.

References to "one embodiment", "an embodiment", "exemplary embodiment" and the like in the specification are intended to include a particular feature, structure or feature, but each embodiment may not necessarily include a particular feature or structure. Or characteristics. Moreover, such terms are not necessarily referring to the same embodiment. In addition, the specific features, structures, or characteristics of the other embodiments may be combined with other embodiments without departing from the scope of the invention.

Embodiments of the invention may be implemented in a hardware, a firmware, a soft body, or a combination thereof. Embodiments of the invention may also be implemented as instructions stored on a machine readable medium, which may be read and executed by one or more processors. Machine readable media can include any type of information for storing or transmitting in a form readable by a machine (eg, a computing device, a mobile device, a smart phone, etc.). For example, non-transitory machine readable media can include read only Memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices. For other examples, the transitory machine readable medium can include electrical, optical, acoustic or other forms of transmitted signals (eg, carrier waves, infrared signals, digital signals, etc.).

The following description may include terms (such as first, second, etc.) that are used for descriptive purposes only and are not to be construed as limiting. As used herein, the terms "module" and/or "unit" may refer to, in part, or include an application-specific integrated circuit (ASIC), an electronic circuit, or a processor that executes one or more software or firmware programs ( Shared, dedicated or grouped and/or memory (shared, dedicated or grouped), combinatorial logic and/or other suitable components that provide the described functionality.

In addition, the various operations are described as a plurality of discrete operations, which in turn are described in a manner that is most helpful in understanding the illustrative embodiments, however, the order of description should not be construed as implying that the operations are necessarily dependent on the order. In particular, these operations do not necessarily need to be performed in the order presented.

The following embodiments can be used in a variety of applications including transmitters and receivers in radio systems, although the invention is not limited in this respect. Examples of radio systems include, but are not limited to, network interface cards (NICs), network adapters, fixed or mobile client devices, relays, base stations, femtocells, gateways, bridges, hubs, routers, Access point or other network device. Furthermore, radio systems within the scope of the present invention can be implemented in cellular radiotelephone systems, satellite systems, dual-purpose radio systems, and computing devices including, for example, radio systems, such as personal computers, tablets, and related peripheral devices, personal digital assistants. One Human computing accessories, handheld communication devices, and all systems that can be related in nature and can suitably apply the principles of embodiments of the present invention.

In the Third Generation Mobile Communications Partnership Project (3GPP) Radio Access Network (RAN) Long Term Evolution (LTE) system, the transmitting station may include an Evolved Universal Land Surface Radio Access Network (E-UTRAN) Node B ( Also typically represented as a combination of an evolved Node B, an enhanced Node B, an eNodeB, or an eNB, which communicates with a wireless mobile device (referred to as a User Equipment (UE)). The downlink transmission may include communication from the transmitting station (or eNodeB) to the wireless mobile device (or UE), and the uplink transmission may include communication from the wireless mobile device to the transmitting station.

Some embodiments may be used in conjunction with various devices and/or systems, such as UEs, mobile devices, mobile wireless devices, mobile communication devices, wireless stations, mobile stations, personal computers, desktop computers, mobile computers, laptop computers, Small notebook, notebook, tablet, smart phone device, mobile phone, cellular phone, server computer, handheld computer, handheld mobile device, personal digital assistant (PDA) device, handheld PDA device, car device, off-board Device, hybrid device, vehicle device, non-vehicle device, mobile or portable device, consumer device, non-mobile or non-portable device, wireless communication station, wireless communication device, wireless access point (AP), wireless node , base station (BS), wired or wireless router, wired or wireless data modem, video device, audio device, audio/video (A/V) device, wired or wireless network, wireless local area network, cellular network, cellular node , Honeycomb device, Wireless LAN (WLAN) device, Universal Integrated Circuit Card (UICC), Ultra Mobile PC (UMPC), customer premises equipment (CPE), multiple input multiple output (MIMO) transceiver or device, device with one or more internal antennas and/or external antennas, digital video broadcasting (DVB) devices, multi-standard radios , wired or wireless handheld devices, wireless application protocol (WAP) devices, vending machines, point-of-sale devices, wearable devices, cell phones, and/or other consumer electronics such as MP3 players, digital cameras, personal computing accessories, and existing and Wireless mobile devices that appear in the future may be related in nature and the principles of the embodiments may be applied as appropriate.

1 schematically illustrates a wireless communication network 100 in accordance with an embodiment of the present invention. In one embodiment, wireless communication network 100 (hereinafter "network 100") can include a base station 110 (e.g., an evolved Node B (eNB)) that can communicate with a mobile wireless device (e.g., UE 120). In various embodiments, eNB 110 may be a fixed station (e.g., a fixed node) or a mobile station/node. In various embodiments, network 100 may include access networks for access networks of 3GPP LTE networks, such as E-UTRAN, 3GPP LTE-A networks, 4G networks, 4.5G networks, 5G networks. , 6G network or any other future communication network, WiMAX cellular network, HSPA, Bluetooth, WiFi or other type of wireless access network or any other future standard.

In various embodiments, eNB 110 and/or UE 120 may support multiple input multiple output (MIMO) communication with each other. For example, eNB 110 and/or UE 120 may include one or more antennas for utilizing one or more radio resources of wireless communication network 100. As shown in FIG. 1, eNB 110 and/or UE 120 may each be included to implement multiple input multiple output (MIMO). One or more antenna groups of the transmission/reception system. The MIMO transmission/reception system is operable in various MIMO modes including single user MIMO (SU-MIMO), multiple user MIMO (MU-MIMO), closed MIMO, open MIMO, full MIMO (FD-MIMO) or smart Variation in antenna processing. As shown in FIG. 1, eNB 110 may include one or more antennas 118, and UE 120 may include one or more antennas 128.

In some embodiments, eNB 110 can include controller 114. Controller 114 can be coupled to transmitter 112 and receiver 116 and/or to one or more communication modules or units in eNB 110. In some embodiments, transmitter 112 and/or receiver 116 may be components or modules of a transceiver. Transmitter 112 and/or receiver 116 may be coupled to one or more antennas 118 for communicating with UE 120. UE 120 may include transmitter 122 and receiver 126 and/or one or more communication modules or units. Transmitter 122 and/or receiver 126 may communicate with a base station (BS) (e.g., eNB 110) or other type of wireless access point (such as a wide area network (WWAN)) via one or more antennas 128 of UE 120.

In some embodiments, eNB 110 may include other hardware, software, and/or firmware components (eg, memory, storage, input modules, output modules, one or more radio modules, and/or one or Multiple digital modules, and/or other components). Transmitter 112 can be configured to transmit signals to UE 120 via one or more antennas 118. Receiver 116 can be configured to receive signals from UE 120 via one or more antennas 118. In some embodiments, transmitter 112 and/or receiver 116 can be an element or module of a transceiver circuit.

In some embodiments, the controller 114 can control the functionality of one or more eNBs 110 and/or control one or more communications performed by the eNB 110. In some embodiments, controller 114 may execute instructions of software and/or firmware (eg, eNB 110 and/or one or more application operating systems (OS)). Controller 114 may include or may be implemented using suitable circuitry, such as controller circuitry, configuration circuitry, baseband circuitry, scheduler circuitry, processor circuitry, memory circuitry, and/or any other circuitry that may be configured to perform control Part of the functionality of the device 114. In some embodiments, one or more functions of controller 114 may be implemented by logic, which may be performed by a machine and/or one or more processors.

In various embodiments, UE 120 may communicate using one or more wireless communication standards, including 3GPP LTE, Worldwide Interoperability for Microwave Access (WiMAX), High Speed Packet Access (HSPA), Bluetooth, WiFi, 5G standards, and/or Other wireless standards or future wireless standards. The UE 120 can communicate via a separate antenna for each wireless communication standard or a shared antenna for multiple wireless communication standards. In some embodiments, the UE 120 can communicate over a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a wireless wide area network (WWAN) or other network.

In some embodiments, the UE 120 can include a controller 124, a transmitter 122, a receiver 124, and one or more antennas 128. In some embodiments, UE 120 may include other hardware components, software components, and/or firmware components, such as memory, storage, input units, output units, and/or any other components. Transmitter 122 can transmit signals to eNB 110 via one or more antennas 128. Receiver 124 can be via one or more antennas 128 receives the signal from eNB 110. In some embodiments, transmitter 122 and/or receiver 126 can be a component or module of a transceiver.

In some embodiments, the controller 124 can be coupled to the receiver 124 and the transmitter 122. In some embodiments, controller 124 can control one or more functions of UE 120 and/or control one or more communications performed by UE 120. In some embodiments, controller 124 may execute instructions of software and/or firmware (eg, UE 120 and/or one or more application operating systems (OS)). Controller 124 may include or may be implemented using suitable circuitry, such as controller circuitry, scheduler circuitry, processor circuitry, memory circuitry, and/or any other circuitry that may be configured to perform part of the functionality of controller 12 . In some embodiments, one or more functions of controller 124 may be implemented by logic, which may be performed by a machine and/or one or more processors.

For example, the controller 124 can include a central processing unit (CPU), a digital signal processor (DSP), a graphics processing unit (GPU), one or more processor cores, a single core processor, a dual core processor, and a multi-core processor. , microprocessor, host processor, controller, plurality of processors or controllers, chips, microchips, one or more circuits, circuits, baseband circuits, configuration circuits, radio frequency (RF) circuits, logic units, integrated An electrical circuit (IC), an application specific IC (ASIC), or any other suitable versatile or special purpose processor or controller and/or any combination thereof.

Transmitter 112 may include or be coupled to one or more antennas 118 of eNB 110 for wirelessly communicating with other wireless communication networks 100 The component (eg, UE 120) communicates. Transmitter 122 may include or be coupled to one or more antennas 128 of UE 120 for wirelessly communicating with other components of wireless communication network 100 (e.g., eNB 110). In some embodiments, the transmitters 112 and/or the transmitters 122 may each include one or more transmitters, one or more receivers, and may transmit and/or receive wireless communication signals, radio frequency (RF) signals, frames. One or more transmitters, one or more receivers, and/or multiple transceivers, blocks, transport streams, packets, messages, data items, materials, information, and/or any other signals.

In some embodiments, antenna 118 and/or antenna 128 may comprise any type suitable for transmitting and/or receiving wireless communication signals, RF signals, blocks, frames, transport streams, packets, messages, data items, and/or materials. antenna. For example, antenna 118 and/or antenna 128 may comprise any suitable configuration, structure, and/or arrangement of one or more antenna elements, components, units, combinations, and/or arrays. In some embodiments, antenna 118 and/or antenna 128 may implement transmission and/or reception functions using separate transmission and/or reception antenna elements. In some embodiments, antenna 118 and/or antenna 128 may implement transmission and/or reception functions using general and/or integrated transmission/reception elements. The antenna may comprise, for example, a phased array antenna, a single element antenna, a dipole antenna, a beam antenna of a set of switches, and the like.

While FIG. 1 illustrates some components of eNB 110, in some embodiments, eNB 110 can optionally include other suitable hardware, software, and/or operatively associated with one or more components in eNB 110. / or firmware components. While FIG. 1 illustrates some components of UE 120, in some embodiments, UE 120 may include interfacing with one or more components in UE 120. Other suitable hardware, software and/or firmware components are associated or operatively associated. For example, eNB 110 and/or UE 120 may include one or more radio modules (not shown) for modulating and/or demodulating signals transmitted or received over the air interface and for processing transmissions over the air interface. And one or more digital modules (not shown) of the received signal.

In some embodiments, eNB 110 and/or UE 120 may include one or more input units (not shown) and/or one or more output units (not shown). For example, one or more of the input units may include a keyboard, keypad, mouse, touch screen, trackpad, trackball, stylus, microphone, or any other indicator/input unit or device. For example, one or more output units may include a monitor, a screen, a touch screen, a flat panel display, a cathode ray tube (CRT) display unit, a liquid crystal display (LCD) display unit, a plasma display unit, one or more audio speakers. Or headphones or any other output unit or device.

In some embodiments, UE 120 may comprise, for example, mobile computers, mobile station, a laptop computing device, a laptop computing device, a small notebook, a tablet computing device, a ^thin-TM laptop computing device, a handheld computing device, Handheld device, storage device, PDA device, handheld PDA device, in-vehicle device, off-board device, hybrid device (eg, combining cellular phone function with PDA device function), consumer device, vehicle device, non-vehicle device, action or Portable device, mobile phone, cellular phone, PCS device, mobile or portable GPS device, DVB device, wearable device, relatively small computing device, non-desktop computer, "portable, happy life" (Carry Small Live) Large, CSLL) device, Ultra Mobile Device (UMD), Ultra Mobile PC (UMPC), Mobile Internet Device (MID), Origami device or computing device, video device , audio devices, audio/video (A/V) devices, gaming devices, media players, smart phones, mobile stations (MS), mobile wireless devices, Communication devices, cell phones, cellular phones, mobile phones, personal computers (PCs), handheld mobile devices, universal integrated circuit cards (UICC), user terminal equipment (CPE) or other consumer electronic devices such as digital cameras, personal computing Accessories, as well as existing and future wireless mobile devices, may be relevant in nature and the principles of the embodiments may be applied as appropriate.

Although FIG. 1 illustrates one or more components in eNB 110 and/or UE 120, eNB 110 and/or UE 120 may each include one of the signals used to modulate and/or demodulate transmission or reception on the air interface. Or a plurality of radio modules or units (not shown) and/or one or more digital modules or units (not shown) that can be used to process signals transmitted and received over the air interface.

2 is a block diagram schematically showing an example of a wireless communication network 200 in accordance with some embodiments.

In some embodiments, wireless communication network 200 can include one or more wireless communication devices that can communicate content, data, information, and/or signals via one or more wireless media, such as radio channels, cellular channels, RF channel, Wireless Fidelity (WiFi) channel, Infrared Radio (IR) channel, etc. For example, as described below). One or more components of wireless communication network 200 are selectively capable of communicating over any suitable wired communication link.

In some embodiments, wireless communication network 200 can include user equipment (UE) 202, which can communicate with eNB 104, for example, via a Uu interface or any other suitable interface.

In some embodiments, wireless communication network 200 can include a packet data network (PDN) gateway (PGW) 208. In some embodiments, PGW 208 can communicate with SGW 206, such as via an S5 interface or any other suitable interface. In some embodiments, the PGW 208 can be associated with an Access Point Name (APN). In some embodiments, UE 202 may utilize the APN of PGW 208 to facilitate connection to an external network via PGW 208. PGW 208 can communicate with a serving area network (LAN) server 220 via an SGi interface or any other interface.

In some embodiments, wireless communication network 200 can include a traffic offload function (TOF) 212, which can be provided between eNB 204 and a service gateway (SGW) 206, such as through an S1-u interface or any other suitable interface. In some embodiments, the TOF 212 can be implemented in an entity, device, device, system, circuit, module, unit, and/or any other structure using any suitably configured hardware, software, and/or firmware. In some embodiments, TOF 212 can be configured to perform one or more of the procedures and/or functions as described herein. In some embodiments, the TOF 212 can be used in a 3G network, an LTE network, a 5G network, and/or any other existing or future wireless communication network and/or the European Telecommunications Standards Institute (ETSI) Mobile Edge Computing (MEC). One or more.

In some embodiments, TOF 212 can be collocated with eNB 204. For example, TOF 212 and eNB 204 may be in the same physical device or system, such as at the same server, entity, system, and the like. In some embodiments, TOF 212 and eNB 204 may be physically located together. In some other embodiments, the TOF 212 can be external to the eNB 204. For example, as shown in FIG. 2, TOF 212 can reside between eNB 204 and SGW 206, such as the S1-U interface.

In some embodiments, network 200 can include one or more regional networks 210 and/or any other service servers that can each include TOF 212 and/or one or more regional application services (AS) 214. In some embodiments, the area AS 214 that is collocated with the TOF 212 can provide services, such as for the UE 202 at the edge of the network. In some embodiments, access to the Internet 230 can be allowed within the TOF 212. In some embodiments, region AS 214 and TOF 212 may be in the same physical device, such as in the same server, entity, system, or the like. In some embodiments, area AS 214 and TOF 212 may be physically located together, such as in area network 210.

In some embodiments, the network may include one or more non-regional or external ASs 216 that are not collocated with TOF 212. In some embodiments, the external AS 216 can be outside of the TOF 212. In some embodiments, the external AS 216 can be external to the local area network 210 in which the TOF 212 is located. In some embodiments, the external AS 216 can include a server in the Internet 230, such as a DNS server 232.

Although FIG. 2 illustrates regional network 210 in wireless network 200 For example, in some embodiments, wireless network 200 can include one or more networks 210, each of which can include TOF 212 and/or one or more zones AS 214. In some embodiments, wireless network 200 can include one or more external ASs 216 that can be external to any regional network 210. In some embodiments, TOF 212 at regional network 210 can communicate with one or more external ASs 216 via an SGi interface or any other suitable interface.

In some other embodiments, the area AS 214 can be configured to communicate with the TOF 212, such as via the SGi interface or any other suitable interface. In some demonstrative embodiments, region AS 214 may be configured to establish a direct connection to TOF 212, such as via an SGi interface. In some embodiments, TOF 212 can be configured to allow access to Internet 230 within TOF 212, such as via SGi agent 824 of FIG. 8, through the SGi interface or any other suitable interface. In some embodiments, the area AS 214 can be coupled to the network 200 and/or the UE 202 via the TOF 212 without network address translation. In some embodiments, area AS 214 can be used as a DNS proxy.

In some embodiments, TOF 212 may be configured to enable local sinking that may be configured on the network side (eg, TOF 212) to implement local sinking without notifying UE 202. In some embodiments, TOF 212 can be configured to enable local sinking to support service continuity across multiple points of exchange (eg, one or more TOFs 212).

In some embodiments, the TOF 212 may not always initiate the NAT function during traffic offloading. In some embodiments, if the application is available in the area AS 214, the area AS 214 can deliver the application to The UE 202 does not enable the NAT function of the TOF 212 to reduce system resource waste. In some embodiments, an application can include one or more services for a UE (eg, 202). In some embodiments, an example of one or more services may include file downloads, video streams, and/or any other service that may be requested by the UE based on the application. In some embodiments, TOF 212 can be configured to offload traffic (eg, one or more packets) from UE 202 to region AS 214 (eg, regionally) without enabling Network Address Translation (NAT) functionality, if traffic Described to area AS 214.

In some embodiments, TOF 212 may check the destination address of the traffic (eg, one or more packets), which may be received from UE 202 via eNB 204. In some embodiments, TOF 212 may decapsulate traffic encapsulated in one or more GTP-U packets in eNB 204 to obtain one or more IP packets. In some embodiments, the IP packet may have a source IP address representing a source node from which the IP packet can be sent and a destination IP address indicating a destination or destination node to which the IP packet may be destined. In some embodiments, in response to determining that the packet is destined to area AS 214, TOF 212 may disable or disable one or more packets of NAT functionality or traffic for traffic. In some embodiments, TOF 212 may offload traffic to zone AS 214 without enabling NAT functionality to reduce system resource waste.

Rather, in some embodiments, the TOF 212 may enable the NAT function in response to determining that traffic from the UE 202 may not be destined to the area AS 214, but may satisfy a local sinking policy. In some embodiments, TOF 204 may offload traffic to Internet 230 and/or DNS server 232 in response to completing a NAT function on the traffic.

In some embodiments, UE 202 may not always perform APN selection for local sinking to reduce network operations and service maintenance. In some embodiments, eNB 204 may not always notify UE 202 of service deployments in network 200. In some embodiments, UE 202 may not always know if the service requested by UE 202 is available for APN selection in network 200 associated with current eNB 204.

In some embodiments, TOF point-to-point tunnels may be established in response to handovers (eg, X2 handovers) across different eNBs to enable handover across different TOF points. In some embodiments, the handover procedure can be utilized to maintain cross-sectional traffic offload points for one or more services (eg, archive downloads, video streams, and/or any other services) requested by the UE 202 (eg, Service continuity of one or more TOF/TOF points). In some embodiments, referring to FIG. 5, source TOF 212s and/or target TOF 212t can be configured to provide a TOF point-to-point tunnel.

For example, the target eNB (e.g., 204t) to which UE 202 is to handoff may be configured to issue a handover request message in response to initiation of X2 handover. The handover request message may contain one or more information elements that may be used to tunnel the establishment. In some embodiments, an inter-droppoint tunnel (eg, a TOF inter-point tunnel) may be established based on a handover request message to support mobility and/or service persistence across different gateways.

In some embodiments, network 200 can be configured to enable local sinking with mobility support. In some embodiments, network 200 can be configured to allow for changes to service presence points (eg, area AS 214 and/or external AS 216 and/or other service servers) without notifying the network One or more UEs in 200. In some embodiments, resiliency may be provided to service deployments for one or more UEs in network 200.

In some embodiments, a Domain Name System (DNS) lookup procedure can be utilized to reduce complexity in network and/or service operations. In some embodiments, the DNS proxy in TOF 212 can be configured to query DNS server 232 (eg, via a DNS request) on behalf of a terminal (eg, UE 202) that may issue a DNS request.

In some embodiments, the UE 202 can be configured to utilize a DNS query or request to obtain one or more service servers (eg, one or more regional ASs 214 or one or more external ASs 216) prior to service acquisition. Internet Protocol (IP) address. In some embodiments, the DNS server 232 can be configured to respond to DNS requests with a DNS response, which can include the IP address of one or more AS or other service servers, which can be provided by the UE 202 in a DNS request. One or more services requested. In some embodiments, the UE 202 can be configured to have one or more AS or other services via the TOF 212 and/or the eNB 204 in response to knowledge of IP addresses having one or more ASs or other service servers. One or more service sessions of the server communicate or establish one or more service sessions for one or more AS or other service servers, wherein one or more services requested by the UE 202 in the DNS query are deployed. In some embodiments, TOF 212 may be configured to transfer traffic from one or more ASs and/or other service servers to UE 202 via eNB 204, and/or to transfer traffic received from UE 202 via eNB 204. To one or more AS or other service servers.

In some embodiments, TOF 212 may include a DNS proxy (e.g., 824 of Figure 8 or a regional AS) for a terminal (e.g., UE 202) that may issue a DNS query or request (e.g., origin). In some embodiments, the UE 202 may encapsulate the DNS request in one or more User Datagram Protocol (UDP) packets of the destination port number 53. In some embodiments, the destination port number 53 can be used to indicate that the traffic with the destination port number 53 is a DNS request. In some embodiments, the eNB 204 can be configured to encapsulate one or more UDP packets carrying the DNS request into one or more General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) packets, and / Or one or more GTP-U packets may be transmitted to the TOF 212.

In some embodiments, in response to receiving a DNS request (eg, one or more GTP-U packets) from the eNB 204, the TOF 212 can be configured to transform or decapsulate one or more GTP-U packets into one or more Internet Protocol (IP) packets. In some embodiments, TOF 212 may determine whether one or more IP packets from the eNB 204 with a DNS request have a destination address destined to area AS 214.

In some embodiments, for DNS requests from the eNB 204, the destination address of one or more IP packets may not be destined to the area AS 214. In response to determining that one or more IP packets having a DNS request are not destined to any of the regional ASs 214, the TOF 212 can be configured to further determine whether one or more IP packets satisfy the local distribution policy. For example, based on a local distribution policy associated with the DNS request, the TOF 212 can determine whether one or more IP packets contain a destination 埠 number of 53 or Multiple UDP packets. In response to determining that the one or more IP packets include one or more UDP packets having a destination number of 53, the TOF 212 can be configured to offload one or more IP packets to the DNS proxy (eg, 824 of FIG. 8) . In some embodiments, the area AS 214 can be used as a DNS agent that performs one or more operations of the DNS agent 824.

In some embodiments, in response to receiving one or more IP packets from the TOF 212, the DNS proxy 824 can extract DNS requests from one or more UPD packets encapsulated in one or more IP packets from the TOF 212. In some embodiments, the DNS proxy 824 can encapsulate the extracted DNS request in one or more UDP packets, and/or can forward to the TOF 212 one or more UDP packets that can be encapsulated in one or more IP packets. .

In some embodiments, TOF 212 can be configured to initiate NAT from one or more IP packets of DNS proxy 824 for forwarding to DNS server 232. In some embodiments, TOF 212 may perform NAT on one or more IP packets to translate the source IP address of one or more IP packets to the global IP address of TOF 212 in which DNS proxy 824 may reside. . In some embodiments, TOF 212 can be configured to translate a source address (eg, a private address) of one or more IP packets into a global IP address of TOF 212 based on NAT. In some embodiments, TOF 212 may be configured to offload one or more IP packets containing one or more UDP packets carrying DNS requests to Internet 230 and/or DNS server 232 after the NAT.

In some embodiments, the DNS server 232 is available from the TOF 212 receives one or more IP packets that may each have a source IP address set to the global IP address of TOF 212. In some embodiments, one or more IP packets from TOF 212 may include one or more UDP packets carrying a DNS request.

In some embodiments, before the service is set up at the UE 202, the administrator of the DNS server 232 can be aware of the IP address of one or more service servers, which can be deployed with the corresponding service to serve by the UE 202 One or more requests. In some embodiments, one or more service servers may include one or more regional ASs 214 that may be deployed with the services of the UE 202 and/or one or more external ASs 216 that may be deployed with the services of the UE 202. . In some embodiments, the administrator of DNS server 232 can generate the global IP address of TOF 212 and one or more regional AS 214 and/or one or more external AS 216 IP addresses in DNS server 232. The mapping between. In some embodiments, DNS server 232 can maintain mappings in the database or mappings in other data structures in the memory of DNS server 232. In some embodiments, the mapping can be associated with a service deployment of the UE 202. In some embodiments, DNS server 232 can maintain one or more mappings, such as if one or more ASs for service are used in regional network 210. In some embodiments, the number of ASs that can be used for a service may depend on the service provider's service deployment. In some embodiments, one or more zones AS and/or another external AS may serve the same service. In some embodiments, one or more mappings can be associated with an initial service deployment related to service settings.

In some embodiments, DNS server 232 can be configured To maintain one or more DNS records or information in the database or one or more DNS records or information in other data structures in the memory of the DNS server 232. In some embodiments, an example of one or more DNS records may include one or more primary domain name groups, and/or one or more regions AS and/or one or more external ASs in one or more mappings A list of IP addresses that may be responsive to access by one or more primary domain names, and/or a mapping between the global IP address of TOF 212 and the IP address of zone AS 214 or external AS 216. In some embodiments, one or more primary domain names may be associated with one or more web sites that may be deployed in region AS 214 or external AS 216 in one or more mappings. In some embodiments, DNS server 214 may determine from which TOF 212 DNS was received based on, for example, one or more primary domain name groups and/or an IP address list of one or more of the one or more mappings. request.

In some embodiments, in response to receiving one or more IP packets from the TOF 212 regarding the DNS request for the UE 202, the DNS server 232 can check which of the one or more mappings associated with the TOF 212 is the AS 214 and / or external AS 216 may provide one or more services of UE 202 requested in the DNS request.

For example, DNS server 232 can determine which of the one or more mappings AS 214 and/or external AS 216 can be capable of providing the service requested by UE 202, or in which region AS 214 or external AS 216 can deploy UE 202 request Service. One or more services requested by the UE 202, or one requested by the UE 202, may be provided in response to one or more of the regions AS 214 and/or the external AS 216 in one or more mappings. Or the plurality of services are deployed in one or more of the one or more regions AS 214, the DNS server 232 can retrieve the mapping to obtain the IP address and/or response of the one or more regions AS 214 A DNS request for the retrieved IP address of one or more of the zones AS 214.

In some embodiments, if there is a new service deployment for the UE 202 and/or one or more requested services for the UE 202, one or more new regional ASs 214 and/or one or more new external ASs 216 In the deployment or available instead of one or more mappings, the administrator of the DNS server 232 may know the IP address of one or more new regional ASs 214 and/or new external ASs 216 and/or may be based on new One or more services in a service deployment and/or service deployment to update one or more mappings. In some embodiments, the administrator of DNS server 232 can update the mapping (eg, manually) to include one or more new regional AS 214 and/or IP addresses of external AS 216, and/or in TOF One or more new mappings of 212 global IP addresses and one or more new regional ASs and/or new external AS 216 IP addresses update one or more mappings. In some embodiments, the administrator of the DNS server 232 can add one or more new mappings based on the new service deployment, and/or delete one or more that may correspond to the previous service deployment instead of the new service deployment. Previous mapping.

In some embodiments, DNS server 232 can check and/or select the IP address of one or more new zone AS 214 and/or new external AS 216 in the updated mapping in response to the DNS request and can The TOF 214 transmits a DNS response, which may include the selected IP address of one or more new ASs in the DNS request for one or more requesting services.

In some embodiments, the DNS server 232 is responsive to determining that the requested service is not available in any of the areas AS 214 in the local area network 210 (eg, in one or more mappings or not in one or more mappings), The DNS server 232 can check which of the one or more maps the external AS 216 can deploy the requested service.

For example, in response to determining that the requested service is not deployed in any of the one or more maps AS 214 or not deployed in the local area network 210, the DNS server 232 can check the external AS 216 in one or more maps. The availability of the requested service. In response to the requesting service being deployed in one or more of the one or more external ASs 216, the DNS server 232 can retrieve one or more mappings to obtain one or more of the requested services that can be provided to the UE 202. The IP address of the external AS 216 and/or a DNS response may be used to echo the DNS request that may include the IP address of one or more of the obtained external ASs 216.

In some embodiments, DNS server 232 can send a DNS response to TOF 212, which can include the IP address of one or more ASs that UE 202 can couple for the requested service. In some embodiments, in response to determining that the requested service is not available in any of the regional AS or external AS, the DNS server 232 can send a DNS response to the TOF 212 to indicate unavailability of any AS for the requested service.

In some embodiments, the DNS server 232 can be configured to allocate one or more services requested by the UE 202 in one or more of the one or more regions AS 214 and/or the external AS 216, eg, based on AS load balanced AS load. For example, DNS server 232 can choose One or more of the areas AS 214 and/or one or more external ASs 216 have a smaller load to provide the requested service. In some embodiments, DNS server 232 can retrieve the database to obtain an IP address of one or more selected regions AS 214 and/or external AS 216 having a smaller load in response to the allocation decision, and/or to The TOF 212 transmits a DNS response to include the retrieved IP address of the area AS 214. In some embodiments, in response to the AS assignment, the DNS server 232 can update one or more mappings with one or more new mappings. In some embodiments, DNS server 232 can perform an AS IP address retrieval, such as before updating one or more mappings based on AS allocation. In some other embodiments, DNS server 232 can perform an AS IP address retrieval in response to updating one or more mappings with the new one or more mappings. In some embodiments, AS load balancing can be applied to zone AS 214 and/or can be applied to zone AS 214 and/or external AS 216 collectively based on the policy of the service provider.

In some embodiments, DNS server 232 can place the global IP address of TOF 212 and one or more areas AS that can provide one or more requests for one or more requests of UE 202 in a table, array, list, or any other form. One or more mappings between the 214 and/or the IP address of the external AS 216 are stored in memory. In some embodiments, the administrator of the DNS server 232 can be configured to update one or more of the databases using one or more new mappings and/or AS assignments corresponding to the new service deployment of the UE 202. Mappings (for example, dynamically). In some embodiments, the DNS server 232 can store one or more new associated devices in a table, array, list, or any other form of new service deployment and/or AS assignment in memory. Or updated mapping. In some embodiments, UE 202 may not be updated in response to updates and/or service presence point changes and/or service deployment changes in one or more mappings.

In some embodiments, DNS server 232 can transmit a DNS response to TOF 212 as one or more UDP packets that can be encapsulated in one or more IP packets. In some embodiments, DNS server 232 can send one or more IP packets containing one or more UDP packets to TOF 212.

In some embodiments, in response to receiving one or more IP packets associated with the DNS response from the DNS server 232, the TOF 212 may offload one or more IP packets to the DNS agent 824 in the TOF 212.

In some embodiments, in response to receiving one or more IP packets from the TOF 212, the DNS proxy 824 can extract from one or more IP packets that are carried by one or more UDP packets in one or more IP packets. DNS response. For example, the extracted DNS response may include an IP address to provide one or more ASs of the service requested in the DNS request. In response to extracting the DNS response, the DNS proxy 824 can encapsulate the extracted DNS response as one or more UDP packets with the source number 53 and/or the destination address to the UE 202. In some embodiments, DNS proxy 824 can send the extracted DNS response to TOF 212 as one or more UDP packets that can encapsulate source number 53 in one or more IP packets. In some embodiments, DNS proxy 824 can encapsulate one or more UDP packets for transmission to one or more IP packets of TOF 212.

In some embodiments, DNS proxy 824 in TOF 212 may store or cache one or more DNS responses received from DNS server 232 via TOF 212, and/or retrieve cached DNS responses in response to one or Multiple subsequent DNS requests. In some embodiments, DNS proxy 824 can send the retrieved DNS response to TOF 212 as one or more UDP packets that can be encapsulated in one or more IP packets.

In some embodiments, in response to receiving one or more IP packets from the DNS proxy 824 that include one or more UDP packets carrying the extracted DNS responses or retrieved DNS responses, the TOF 212 may encapsulate one or more IP packets. Packets for one or more GTP-Us. In some embodiments, TOF 212 may offload one or more GTP-U packets to eNB 204.

In some embodiments, eNB 204 may decapsulate one or more GTP-U packets to recover one or more UDP packets of a portable DNS response or retrieved DNS response, and may have source 53. The eNB 204 may send one or more UDP packets carrying a DNS response to the UE 202. In some embodiments, the UE 202 can communicate with one or more ASs via the TOF 212 and the eNB 204 in response to an IP address of one or more ASs that can be retrieved from the DNs extracted in the received UDP packet.

Although some embodiments may be described herein with respect to a 3GPP LTE network, some embodiments may be implemented in any other suitable cellular network or system, such as a Global Mobile Telecommunications System (UMTS) cellular system, a GSM network, a 3G cellular network. Road, 4G cellular network, 4.5G network, 5G cellular network, WiMax cellular network or any other traditional or not The network or system that comes. In some embodiments, some embodiments may be applied to action edge calculations and the like.

FIG. 3 is an illustration of an example of one or more processes that are illustratively shown in accordance with some embodiments. In some embodiments, one or more programs may be used by TOF 212 for traffic offloading. In some embodiments, traffic offloading may be based on, for example, user profiles and/or may be activated by an operator to determine one or more policies. In some embodiments, examples of user profiles may include, but are not limited to, user profiles that may indicate whether the user is a regional user or a roaming user and/or other user related information. In some embodiments, an example of an operator policy may include, but is not limited to, for example, carrying a DNS query or requesting one or more UDP packets may have a destination number 53, or carrying one or more UDP packets. There is a source number 53 and/or other policies that can be set by the operator. In some embodiments, TOF 212 may perform one or more of the other operations as described herein.

In some embodiments, at 302, TOF 212 may receive traffic associated with the service from UE 202 via eNB 204. In some embodiments, the eNB 204 may encapsulate traffic from the UE 202 in the General Packet Radio Service (GPRS) Tunneling Agreement User Plane (GTP-U) format and transfer traffic to the TOF 212. In some embodiments, TOF 212 may decapsulate one or more GTP-U packets in the received traffic to obtain one or more Internet Protocol (IP) packets.

In some embodiments, at 304, the TOF 212 may determine whether the destination address of the one or more obtained IP packets is destined to the area AS 214 in the area network 210. In some embodiments, at 306, the response To determine that one or more of the obtained IP packets contain a destination IP address to the area AS 214 in the area network 210, the TOF 212 may offload traffic (eg, one or more IP packets) to the area AS 214.

Rather, in some embodiments, in response to determining that one or more IP packets may not be destined to any of the areas AS 214 in the local area network 210, the TOF 212 may further determine whether one or more IP packets meet the local distribution policy. (at 308).

In some embodiments, the local sink policy may include one or more rules indicating which type of packet may be sent to the regional network 210 (eg, the DNS proxy 824 and/or the inter-TOF tunnel). In some embodiments, based on the local distribution policy, the IP packet can be offloaded to the regional network even if the destination IP address of the packet is not the IP address of any of the regional ASs or other regional servers within the regional network 210. 210. For other examples, based on the local sinking strategy, the source TOF 212s and/or the target TOF 212t (eg, as shown in FIG. 5) may transfer traffic from the AS 214 or the UE 202 via the inter-TOF tunnel.

In some embodiments, TOF 212 may be based on one or more types, destination IP address, destination port number, agreement ID, source IP address, source number of the packet, and/or one of the IP headers in the packet. Or multiple fields (eg, service type) to check if the packet satisfies the local distribution policy, and/or to determine if the packet can be offloaded to the local area network 210. In some embodiments, the mobile operator can configure one or more local distribution policies. In some other embodiments, the local distribution policy may include one or more other rules regarding traffic offloading.

In some other embodiments, based on the local sinking policy, in response to determining that, for example, one or more decapsulated IP packets may include one or more UDP packets having a destination number of 53 or belonging to a DNS query or request, the TOF 212 may It is configured to offload one or more IP packets to a DNS proxy, such as 824 of Figure 8 or an area AS 214 that can be used as a DNS proxy. In some embodiments, the DNS proxy may be transparent to the UE 202 that may not be aware of the DNS proxy. In some embodiments, DNS proxy 824 can decapsulate one or more IP packets to extract DNS requests from one or more UDP packets that are decapsulated in one or more IP packets. In some embodiments, DNS proxy 824 can encapsulate the extracted DNS request as one or more UDP packets with destination port number 53, which can be provided to TOF 212 as one or more IP packets.

In some embodiments, at 310, in response to receiving one or more IP packets from the DNS proxy 824, the TOF 212 can initiate a NAT on one or more received IP packets to translate one or more IP packets. The source IP address (eg, the address provided) is the global IP address of TOF 212. In some embodiments, at 312, the TOF 212 may offload one or more IP packets subsequent to the NAT to the DNS server 232 in the Internet 230. In some embodiments, TOF 212 can be configured to send one or more IP packets having a source IP address translated to a global IP address to DNS server 232 in Internet 230, for example, representing a DNS may be originally issued The requested terminal, such as UE 202.

Conversely, in some embodiments, at 314, in response to determining that one or more IP packets do not satisfy a local distribution policy (eg, one or more The IP packets are not unloadable to the local area network 210), and the TOF 212 may encapsulate one or more IP packets in the form of one or more GTP-U packets. In some embodiments, at 316, TOF 212 may send one or more GTP-U packets to SGW 206. In some embodiments, SGW 206 can be configured to establish, for example, a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) between SGW 206 and eNB 204 to transmit one or more GTP-U packets to the eNB via a GTP tunnel. 204. In some embodiments, eNB 204 may send one or more UDP packets each corresponding to a GTP-U packet to UE 202. The GTP tunnel can be established, for example, based on one or more instructions from, for example, a Mobility Management Entity (MME) based on (3GPP TS 24.301).

Figure 4 illustrates a program diagram in accordance with one or more embodiments. In some embodiments, one or more of the operations of FIG. 4 can be used to establish a service session between the UE and the AS. In some embodiments, the UE 202 may use a DNS query or request (eg, having one or more UDP packets of the destination port number 53) to obtain the IP address of the AS (eg, the UE 202 for requesting in the DNS request) Service area AS 214 or external AS 216). In some embodiments, the UE 202 can utilize the obtained IP address of the AS to initiate a service session with the AS (eg, via the controller 114 of FIG. 1 or the baseband circuitry 1020 of FIG. 10). In some embodiments, one or more operations may be performed as described with reference to other figures.

In some embodiments, UE 202 may transmit one or more UDP packets with destination 埠 53 that may carry DNS request 402 to eNB 204. In some embodiments, in response to receiving a DNS from the UE 202 Request 402, the eNB 204 may transform or encapsulate one or more UDP packets carrying the DNS request 402 into one or more GTP-U packets to generate a DNS request 404 in the GTP-U format. The eNB 204 may transmit a DNS request 404 to the TOF 212 as one or more UDP packets that may be encapsulated in one or more GTP-U packets.

In some embodiments, TOF 212 may receive one or more GTP-U packets from eNB 204 associated with DNS request 404. The TOF 212 may decapsulate one or more GTP-U packets that may carry one or more UDP packets of the DNS request 404 into one or more IP packets.

In some embodiments, TOF 212 may offload one or more IP packets decapsulated from the GTP-U packet of eNB 204 to a DNS proxy in TOF 212 based on a local sinking policy. In some embodiments, the DNS proxy in TOF 212 may include, for example, 824 of Figure 8 or an area AS 214 that may be used as a DNS proxy. In some embodiments, DNS proxy 824 can extract DNS request 404 that includes one or more UDP packets. In some embodiments, DNS proxy 824 can encapsulate the extracted DNS request 404 as one or more UDP packets that can be sent to TOF 212 as one or more IP packets.

In some embodiments, in response to receiving one or more IP packets from the DNS proxy 824, the TOF 212 can initiate a NAT function to translate the source IP address of the one or more IP packets to the global IP address of the TOF 212, To generate a DNS request after NAT 406. In some embodiments, the DNS request after NAT 406 may include a source IP with one or more IP packets of a global IP address translated into TOF 212 based on NAT. One or more IP packets of the address. In some embodiments, TOF 212 may offload DNS requests to DNS server 232 in Internet 230 after NAT 406 as one or more IP packets that may be encapsulated in a source IP address belonging to TOF 212. One or more UDP packets.

In some embodiments, DNS server 232 can maintain mapping between one or more mapping tables in the database or the global IP address of TOF 212 and the IP address of one or more AS or other service servers. One or more of the UEs 202 are deployed based on the service deployment of the UE 202. In some embodiments, the mapping corresponding to the service can be identified by the domain name.

In some embodiments, in response to receiving one or more IP packets associated with a DNS request subsequent to NAT 406, DNS server 232 can determine one or more of the one or more mappings (eg, region AS 214) And/or external AS 216) whether one or more services requested by UE 202 indicated in the DNS request can be provided after NAT 406. In some embodiments, in response to determining that one or more ASs (eg, region AS 214 and/or external AS 216) may provide one or more services requested by UE 202 indicated in the DNS request after NAT 406, DNS server 232 can select or retrieve the IP address of one or more ASs to respond to DNS requests after NAT 406.

In some embodiments, DNS server 232 can provide DNS response 408 to TOF 212, which can include retrieval of one or more regional ASs 214 or one or more external ASs 216 that provide one or more requested services. IP address. In some embodiments, the DNS server 232 may transmit a DNS response 408 to TOF 212 as one or more UDP packets that may be encapsulated in one or more IP packets (eg, via the SGi interface).

For example, if the service requested by the UE 202 is deployed in one or more of the zones AS 214 and/or one or more external ASs 216 indicated in the mapping table corresponding to the service, the DNS server 232 can retrieve the mapping table to obtain The IP address of one or more regions AS 214 and/or one or more external ASs 216 corresponding to the global IP address of TOF 212. In some embodiments, the DNS server 232 can reply to the TOF 212 with a DNS response 408, which can include an IP address retrieved in response to the regional AS 214 of the DNS request 406 and/or the external AS 216.

In some other embodiments, the service in response to the determination request is not deployed in any of the ASs in the mapping table, but is deployed in one or more new regions AS 214 and/or external AS 216 that are not in the mapping table, The administrator of the DNS server 232 can update the mapping table in the database to indicate a new mapping corresponding to the global IP address of the TOF 212 and the IP address of the new regional AS 214 and/or the new external AS 216. , where the requested service is deployed. In some embodiments, the DNS server 232 can include the IP address of the new area AS 214 and/or the new external AS 216 used to reply to the DNS request after the NAT 406 in the DNS response 408.

In some embodiments, in response to determining that the requested service is not deployed in any of the regions AS 214 in the mapping table or the local area network 210, but is deployed in one or more external ASs 216, the DNS server 232 can be in the NAT 406 After that, it can be included in the mapping table or not in the mapping table. The DNS response 408 of the IP address of one or more external ASs 216, replies to the DNS request.

In some embodiments, if the requested service is not deployed in any of the regional ASs 214 or any external AS 216, or if no AS is capable of providing the UE's requested service, the DNS server 232 may respond to the determination in any of the zones AS 214 or any external AS. The unavailability of the service requested in 216 replies to the DNS request 406 with a DNS response 408 indicating that no AS can provide the requested service. In some embodiments, in response to receiving a DNS response to indicate that no AS can act as a service request, UE 202 may not publish any packets related to the service.

In some embodiments, DNS server 232 can transmit DNS response 408 to TOF 212 as one or more UDP packets encapsulated in one or more IP packets. In some embodiments, in response to receiving from the DNS server 232 one or more IP packets that may include one or more UDP packets carrying the DNS response 408, the TOF 212 may unload one or more IP packets into the TOF 212. The DNS proxy 824 is used in the area AS 214 as a DNS proxy.

In some embodiments, in response to receiving one or more IP packets from TOF 212, DNS proxy 824 in TOF 212 may decapsulate one or more IP packets from TOF 212 to resume one carrying DNS response 408 Or multiple UDP packets. In some embodiments, DNS proxy 824 can extract DNS responses 408 from one or more UDP packets. In some embodiments, DNS proxy 824 can store or cache one or more extracted DNS responses in the memory of TOF 212. in DNS proxy 824 in TOF 212 can be configured to retrieve or select in a stored DNS response to obtain a service DNS response 408 for request in DNS request 402 or a subsequent service in a subsequent DNS request from UE 202 .

In some embodiments, DNS proxy 824 may encapsulate the extracted or retrieved DNS response 408 as having one of source code number 53 and/or one of the destination addresses to UE 202 or multiple UDP packets. The DNS proxy 824 can transmit the extracted or retrieved DNS response 408 to the TOF 212 as one or more UDP packets encapsulated as being sent to one or more IP packets of the eNB 204.

In some embodiments, in response to receiving from the DNS proxy 824 one or more IP packets that may include one or more UDP packets carrying the DNS response 408, the TOF 212 may encapsulate one or more IP packets into one or more The GTP-U packet is obtained to obtain a DNS response 410 in the GTP-U format. In some embodiments, TOF 212 may offload one or more GTP-U packets to eNB 204, such as through an S1-U interface.

In some embodiments, eNB 204 may transform (eg, decapsulate) one or more GTP-U packets received from TOF 212 to reply to one or more UDP packets encapsulated in the GTP-U packet to provide The DNS response 412 is delivered to the UE 202. In some embodiments, a UDP packet having one or more replies to the source number 53 may carry a DNS response 412, which may include an area AS 214 and/or an external AS 216 to provide the service requested by the DNS request 202. IP address. In some embodiments, a DNS response 412 may occur in the eNB 202 with a source of 53. One or more UDP packets. In some embodiments, eNB 204 may transmit a DNS response 412 in UDP format to UE 202. In some embodiments, the eNB 204 may transmit a DNS response 412 to the UE 202 as one or more replies of the UDP packet.

In some embodiments, in response to receiving a DNS response 412 from the eNB 204, the UE 202 may obtain (e.g., extract) one or more regions AS 214 and/or one or more externals that may be carried in the DNS response 412. IP address of AS 216. In some embodiments, the UE 202 can use the IP address included in the DNS response 412 to establish one or more service sessions 420 with corresponding ASs having IP addresses. In some embodiments, the UE 202 can communicate with the respective AS (e.g., via the TOF 214 and/or the eNB 204) to perform one or more service sessions 420 based on the IP address of the corresponding AS.

FIG. 5 is a diagram that illustrates one or more programs in a demonstration, in accordance with some embodiments. In some embodiments, one or more programs may be used to implement, for example, a service connection that is handed over across multiple TOF points. In some embodiments, AS 214 and/or AS 216 or other AS of FIG. 2 may be used as one or more ASs for the services of UE 202. In some embodiments, one or more of the operations as described in this disclosure can be performed.

In some embodiments, source eNB 204s and/or target eNB 204t may perform one or more functions of eNB 204. In some embodiments, source TOF 202s and/or target TOF 204t may perform one or more functions of TOF 204. In some embodiments, the UE 202 can communicate with the source eNB 204s, and the source eNB 204s can be via the source TOF. 212s communicates with the service server (e.g., 214 or 216) prior to the handover from the source eNB 204s to the target eNB 204t.

In some embodiments, the target eNB 204t to which the UE 202 is to handoff may be configured to issue a handover request message in response to initiation of X2 handover (eg, from the source eNB 204s to the target eNB 204t). In some embodiments, the handover request message 502 can include an X2 Application Agreement (X2AP) handover request associated with X2 handover. In some embodiments, the handover request message 502 can include one or more information elements that can enable, for example, handover from the source eNB 204s to the target eNB 204t.

In some embodiments, the target eNB 204t may receive the handover request message 502 to complete the handover from the source eNB 204s to the target eNB 204t. In some embodiments, the handover from the source eNB 204s to the target eNB 204t may be completed based on the handover request message 502.

In some embodiments, the handover across different TOFs (eg, handover from source TOF 212s to target TOF 212t) may be initiated in response to completion of handover from source eNB 204s to target eNB 204t.

In some embodiments, the handover request message 502 can further include one or more extended information elements, such as described with respect to FIG. In some embodiments, one or more extended information elements may be used to enable handover and/or conversational migration, such as, for example, source TOF 212s to target TOF 212t.

In some embodiments, in response to completion of the handover from the source eNB 204s to the target eNB 204t, the target eNB 204t may notify the target TOF 212t of one or more extensions via the dialog migration request message 504. Information element. In some embodiments, the conversation migration request 504 can include one or more extended information elements, which can be included in the handover request message 502.

In some embodiments, in response to receiving the conversational migration request 504 and/or one or more extended information elements, the target TOF 212t may transmit the conversational migration request acknowledgement 506 to the target eNB 204t.

In some embodiments, the target TOF 212t may establish a tunnel to the source TOF 212s based on one or more extended information elements that may be delivered with the dialog migration request 504. Referring to Figure 6, in some embodiments, one or more extended information elements are available for use in the handover across the TOF.

FIG. 6 is an illustration of an example of a message 600 that is shown in accordance with various embodiments. In some embodiments, message 600 can include a handover request message (e.g., handover request message 502) that can be used for handover (e.g., from source eNB 204s to target eNB 204t). In some embodiments, message 600 may include one or more information elements, such as old eNB UE X2AP identification (ID), cause, target cell ID, GUMMEI ID, globally unique mobility management entity identification (GUMMEI ID), UE Background information (eg, Mobility Management Entity (MME)) UE S1 Application Agreement (S1AP) ID, UE security capabilities, access layer security information such as key eNB, etc.), evolved radio access bearer (eRAB) to be established The list, Radio Resource Control (RRC) context, and/or other information elements that may be used to effect handover and/or session migration, for example, from source eNB 204s to target eNB 204t.

In some embodiments, the handover request message 600 can include one or more extended information elements, such as source TOF context information, such as a source TOF to-be-connected list 610. In some embodiments, the source TOF to-be-connected list 610 can include background information 612 for each item in the source TOF to-be-connected list 610. For example, the background information 612 can include the IP address 614 of the source TOF in the source TOF to-be-connected list 610 and/or can be used to establish a tunnel number 616 between the source TOF 212s and the target TOF 212t. In some embodiments, the source TOF 212s and the target TOF 212t may communicate via a port number 616 to establish an inter-TOF tunnel that may be, for example, a bidirectional tunnel. In some embodiments, the handover request message 600 can include an IP address 620 of the UE (e.g., UE 202) that can be assigned one or more ongoing service conversations.

Referring to FIG. 5, in some embodiments, the target TOF 212t may transmit a dialog relay request message 508 to the source TOF 212s to request a source TOF 212s to a target TOF 212t via a TOF between the target TOF 212t and the source TOF 212s. Relay of traffic flow. In some embodiments, in response to receiving a dialog relay request message 508 from the target TOF 212t, the source TOF 212s may relay the dialog request confirmation message 510 to the target TOF 212t via the inter-TOF tunnel. In some embodiments, in response to the exchange of the dialog relay request message 508 and the dialog relay confirmation message 510 between the target TOF 212t and the source TOF 212s (eg, as shown in FIG. 5), the TOF tunnel may be based on the handover One or more extended information elements in the request message are created.

Responding between target TOF 212t and source TOF 212s The establishment of the inter-TOF tunnel, source TOF 212s may continue to communicate with AS 214 and/or 216 to maintain traffic flow 512 for ongoing service conversations between UE 202 and possibly initiated ASs 214 and/or 216. (for example, a conversation stream), for example before the establishment of a tunnel between TOFs. The source TOF 212s may tunnel or relay the traffic stream 512 to the target TOF 212t via the inter-TOF tunnel. The target TOF 212t may transfer or relay the traffic stream 512 to the UE 202, such as via the target eNB 204t.

In some embodiments, in response to the establishment of the inter-TOF tunnel, the source TOF 212s may check the destination address, the destination number, and/or the agreement number in each packet, such as traffic flow from AS 214 and/or 216. 512. In some embodiments, in response to determining that the destination address, destination number, and/or the agreed number of the packet is associated with or destined to the tunnel, the source TOF 212s may tunnel the packet to the target TOF 212t. For example, one or more packets having a corresponding destination address, destination number, and/or agreement number should be delivered through the tunnel. In some embodiments, if a TOF tunnel can be used to relay a service session between the UE 202 and an AS (eg, 214 or 216), the IP address of the UE 202 can be associated with the tunnel. In some embodiments, the target TOF 212t may transfer the packet received via the tunnel to the UE 202 via the target eNB 204t.

On the other hand, in some embodiments, the target TOF 212t may check the source address, source number, and/or agreement number in each packet, such as traffic flow 512 from the UE 202, such as via the target eNB 204t. In response to determining the source address, source number, and/or packet The agreement number in the association is associated with the tunnel, and the target TOF 212t can send the packet to the source TOF 212s through the tunnel. In some embodiments, the source TOF 212t may transfer the packet to the AS 214 and/or 216.

In some embodiments, the source TOF 212s may send a conversation relay termination request 514 to the target TOF 212t in response to a predetermined period of inactivity of the traffic flow (eg, 512) between the AS 214 and/or 216 and the source TOF 212s. It can respond to the target TOF 212t with the dialog relay termination confirmation 516 to remove the tunnel. In some embodiments, the inter-TOF tunnel may be removed in response to the exchange of the conversation relay termination request 514 and the conversation relay termination request acknowledgement 516 between the source TOF 212s and the target TOF 212t. In response to the removal of the tunnel, subsequent traffic flows between the UE 202 and the ASs 214 and/or 216 may be supported by the target eNB 204t and/or the target TOF 212t.

FIG. 7 is a block diagram showing an example of a device 700 in accordance with an embodiment. In accordance with various embodiments, device 700 may be further implemented in a device, entity, system, circuit, module, logic, unit, electronic device circuit entity, and/or using any suitably configured hardware, software, and/or firmware. Any other structure. In some embodiments, device 700 can be used in, for example, UE 202, eNB 204, TOF 212, AS 214, SGW 206, PGW 208, serving LAN server 220, DNS server 232, and/or other in network 200. structure.

In some embodiments, device 700 may use one or more wireless communications such as 3GPP LTE, WiMAX, HSPA, Bluetooth, WiFi, 5G standards, future standards, and/or other wireless communications in various embodiments. Communication standards. Device 700 can communicate over a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a wireless wide area network (WWAN) or other network in various embodiments.

In various embodiments, structure 700 may be or may be integrated into a UE, base station, TOF, AS, serving LAN server, SGW, and/or PGW or other type of device, device, and/or system, or otherwise It is part of a UE, base station, TOF, AS, serving LAN server, SGW, and/or PGW or other type of device, device, and/or system. Device 700 can include a transmit circuit or transmitter 712 and a receive circuit or receiver 716 that are coupled to a control circuit or controller 714. In some embodiments, transmitter 712 and/or receiver 716 can be a component or module of a transceiver circuit or transceiver.

In some embodiments, device 700 can be coupled to one or more of a plurality of antenna elements 718. Components of device 700 and/or device 700 can be configured to perform operations similar to those described herein.

In some embodiments, device 700 may be part of or may include application specific integrated circuits (ASICs), electronic circuits, processors (shared, dedicated, or in groups) and/or execute one or more software or The memory of the firmware (shared, dedicated, or grouped), combinatorial logic, and/or other suitable components that provide the described functionality. In some embodiments, device 700 can be implemented in one or more software or firmware modules, or the functions associated with the circuits can be implemented by one or more software or firmware modules.

In some embodiments, controller 714 can be coupled to transmitter 712 and/or receiver 716. In some embodiments, controller 714 can control one or more functions of device 700 and one or more communications of device 700. In some embodiments, controller 714 can execute instructions for software and/or firmware (eg, operating system (OS) and/or one or more applications of device 700). Controller 714 can include or can be implemented using suitable circuitry, such as controller circuitry, scheduler circuitry, processor circuitry, memory circuitry, and/or any other circuitry that can be configured to perform part of the functionality of controller 714 . In some embodiments, one or more functions of controller 714 can be implemented by logic, which can be performed by a machine and/or one or more processors.

In some embodiments, controller 714 can include a central processing unit (CPU), a digital signal processor (DSP), a graphics processing unit (GPU), one or more processor cores, a single core processor, a dual core processor , multi-core processor, microprocessor, host processor, controller, multiple processors or controllers, chips, microchips, baseband circuits, radio frequency (RF) circuits, logic units, integrated circuits (ICs), applications An application specific IC (ASIC) or any other suitable or dedicated processor or controller or one or more circuits or circuits and/or any combination thereof.

Although FIG. 7 illustrates one or more components in structure 700, in some other embodiments, structure 700 can include any other hardware/software/firmware components and/or communication/digit/control components. For example, in the example of FIG. 2, one or more of the elements may be implemented by a device, device, entity, system, or any other suitable format based on device 700. In some In an embodiment, the controller in fabric 700 can perform one or more of the procedures or functions as described herein.

FIG. 8 is an illustration of an example of a system 800 that is illustratively shown in accordance with some embodiments. In some embodiments, system 800 can be configured to implement a traffic offload function (TOF), such as TOF 212, source TOF 212s, and/or target TOF 212t. In some embodiments, system 800 can be configured to have one or more local sinks as described in connection with the present invention. In some embodiments, system 800 can be implemented in a device, apparatus, system, circuit, entity, and/or any other structure using any suitably configured hardware, software, and/or firmware. In some embodiments, system 800 can be configured to perform one or more programs and/or functions as described in relation to TOF 212, source TOF 212s, and/or target TOF 212t and/or DNS agent 824.

In some embodiments, system 800 can include a TOF that includes one or more interfaces to interface between TOF 800 and one or more other components or elements described in this disclosure.

In some embodiments, TOF 800 can include an eNB interface 802 to communicate with a base station (e.g., eNB 204). For example, the eNB interface 802 can include an S1-U interface or any other suitable interface to communicate with the eNB 204.

In some embodiments, TOF 800 can include an SGW interface 804 to communicate with an SGW (eg, SGW 206) as described above. For example, SGW interface 804 can include an S1-U interface or any other suitable interface to communicate with SGW 206.

In some embodiments, TOF 800 can include an AS interface 806, to communicate with an AS (eg, AS 214). For example, the AS interface 806 can include an SGi interface or any other suitable interface to communicate with the AS 214.

In some embodiments, TOF 800 can include an internet interface 808 to communicate with, for example, Internet 230 and/or DNS server 232. For example, the internet interface 808 can include an SGi interface or any other suitable interface to communicate with the Internet 230 and/or the DNS server 232.

In some embodiments, TOF 800 can include processor 830 and/or memory 832 coupled to one another. The TOF 800 may further comprise one or more other suitable hardware components and/or software and/or firmware components. In some embodiments, some or all of the components of TOF 800 may be enclosed in a housing or package and may be interconnected or operatively associated using one or more wired or wireless links. In other embodiments, the components of the TOF 800 can be dispersed in multiple or separate devices.

The processor 830 can include, for example, a central processing unit (CPU), a digital signal processor (DSP), a graphics processing unit (GPU), one or more processor cores, a single core processor, a dual core processor, a multi-core processor. , microprocessor, host processor, controller, multiple processors or controllers, chips, microchips, baseband circuits, radio frequency (RF) circuits, logic cells, integrated circuits (ICs), application specific ICs (ASICs) Or any other suitable multi-purpose or dedicated processor or controller or one or more circuits or circuits and/or any combination thereof. The processor 830 can execute an operating system (OS) such as TOF 800 or one or Instructions for multiple suitable applications.

In some embodiments, memory 832 can include, for example, random access memory (RAM), read only memory (ROM), dynamic RAM (DRAM), synchronous DRAM (SD-RAM), flash memory, volatile Memory, non-volatile memory, cache memory, buffer, short-term memory unit, long-term memory unit or other suitable memory unit or storage unit. Memory 832 can be configured to store data and/or instructions, such as for TOF 800.

In some embodiments, TOF 800 can be configured to receive (eg, via transceiver 840) one or more GTP-U packets from eNB 204 through eNB interface 202.

In some embodiments, TOF 800 can include a decapsulation/packaging module or unit 810 that is coupled to one or more other components in TOF 800. The decapsulation/encapsulation module 810 can be configured to decapsulate one or more GTP-Us from the eNB 204 into one or more IP packets.

In some embodiments, TOF 800 can include a destination/source address check module or unit 812 that can be configured to determine whether a destination IP address of one or more IP packets is destined to be comparable to TOF 800 Area AS (for example, 214).

In some embodiments, TOF 800 can include an unloading module or unit 814. In some embodiments, the offload module 814 can be configured to in response to the destination/source address check module 812 determining that the destination address of one or more IP packets is destined to the area AS 214, offloading traffic through the AS interface 806 ( For example, one or more IP packets) to the area AS 214 (eg For example, via transceiver 840).

In some embodiments, TOF 800 can include a local distribution policy checking module or unit 816 configurable in response to destination/source address checking module 812 determining that the destination address of one or more IP packets is not destined to The area AS 214 checks to see if one or more IP packets meet the local distribution policy.

In some embodiments, TOF 800 can include a Network Address Translation (NAT) module or unit 818. In some embodiments, in response to the local split policy check module 816, one or more IP packets are determined to satisfy the local sink policy. The NAT module 818 can be configured to initiate a NAT function and/or translate the source IP address of one or more IP packets to a global IP address of the TOF 800. In some embodiments, an example of NAT module 818 may include a translator, translation for network address translation (eg, from a source IP address of one or more IP packets to a global IP address of TOF 800) Modules, translation circuits or translation logic, etc.

In some embodiments, the decapsulation/encapsulation module 810 can be configured to encapsulate one or more IP packets into a GTP-U format in response to determining that one or more IP packets do not satisfy a local distribution policy. Although FIG. 8 illustrates an example of a decapsulation/packaging module or unit 810 in accordance with some embodiments, in some other embodiments, TOF 800 may include decapsulation modules or units to perform decapsulation, respectively, and/or to perform A packaged module or unit that is packaged.

In some embodiments, TOF 800 can be configured to transmit (via transceiver 840) one or more packages through SGW interface 804 The GTP-U is packetized to the SGW 206. In some embodiments, SGW 206 can be configured to establish a GTP tunnel between SGW 206 and eNB 204 to transmit a GTP-U packet to eNB 204, which transmits a UDP packet corresponding to the GTP-U packet to UE 202.

In some embodiments, the eNB 204 can be configured to transmit a DNS query or request from the UE 202 to the TOF 800 as one or more UDP packets that can be encapsulated in one or more GTP-U packets. In some embodiments, the eNB 204 can be configured to transform, for example, encapsulate a DNS query or request from the UE 202, eg, one or more UDP packets of the destination 53 having the GTP-U format.

In some embodiments, TOF 800 can include a DNS proxy 824. In response to receiving from the eNB 204 one or more GTP-U packets that may include one or more UDP packets carrying a DNS query or request, the decapsulation/encapsulation module 810 may be configured to decapsulate one or more GTP-U packets Packets for one or more IPs. In some embodiments, the offload module 814 can be configured to offload one or more of the UDP packets carrying one or more UDP packets to the DNS server 824.

In some embodiments, the DNS proxy 824 can be configured to encapsulate one or more UDP packets in the IP packet from the offload module 814 to extract DNS requests. In some embodiments, the DNS proxy 824 can be configured to encapsulate the extracted DNS request for one or more UDP packets and/or can deliver one or more IP packets that can include one or more UDP packets carrying the DNS request to TOF 800 (for example, NAT module 818). In some embodiments, one or more UDP packets may include a destination number 53.

In some embodiments, the NAT module 818 can perform a NAT function to translate the source IP address from one or more IP packets of the DNS proxy 824 to the global IP address of the TOF 800. In some embodiments, in response to the NAT module 818 translating the source IP address of the one or more IP packets to the global IP address of the TOF 800, the offload module 814 can send one or more IP packets to the DNS after the NAT. Server 232 and/or Internet 230, such as via transceiver 840 and/or internet interface 808.

In some embodiments, DNS server 232 can determine which AS 212 and/or one or more mappings between the global IP address of TOF 800 and the IP address of one or more ASs 212 and/or 216 The service 216 can provide the service requested by the UE 202 based on the DNS request. In some embodiments, DNS server 232 can retrieve one or more mappings to obtain a DNS response, which can include an IP address that can provide one or more of AS212 and/or 216 of the service.

In some embodiments, DNS server 232 can provide a DNS response to TOF 800 as one or more UDP packets that can be packaged in one or more IP packets. In some embodiments, TOF 800 (eg, offload module 814) may send one or more IP packets from DNS server 232 to DNS proxy 824 in TOF 800 in response to receiving an IP packet.

In some embodiments, DNS proxy 824 in TOF 800 can be configured to encapsulate one or more UDP packets from one or more IP packets from unloading module 814 to extract DNS responses. In some implementations In an example, DNS proxy 824 can store or cache one or more extracted DNS responses in memory 832 and/or in any other storage medium of TOF 800 and/or in DNS proxy 824. In some embodiments, DNS proxy 824 can retrieve one or more cached DNS responses to obtain a DNS response with a DNS request from UE 202. In some embodiments, DNS proxy 824 can encapsulate the extracted or retrieved DNS responses as one or more UDP packets with source number 53 indicating one or more UDP packets associated with the DNS response. In some embodiments, one or more UDP packets may have a destination address to the UE 202. In some embodiments, DNS proxy 824 can send a DNS response (eg, decapsulation/encapsulation module 810) to TOF 800 as one or more UDP packets that can be encapsulated in one or more IP packets.

In some embodiments, in response to receiving one or more IP packets from the DNS proxy 824, the decapsulation/encapsulation module 810 can encapsulate one or more IP packets for transmission to one or more GTP-Us of the eNB 204. Packet. In some embodiments, the offload module 814 can send one or more GTP-U packets to the eNB 204 via, for example, the transceiver 840 and/or the eNB interface 820. In some embodiments, one or more GTP-U packets may include one or more UDP packets carrying a DNS response, such as an IP address or service server with an AS.

In some embodiments, eNB 204 may transform (e.g., decapsulate) one or more GTP-U packets from TOF 800 to obtain one or more UDP packets with source 埠53. In some embodiments, eNB 204 may transfer one or more UDP packets to UE 202. In some real In an embodiment, in response to receiving one or more UDP packets, the UE 202 can establish the AS 214 and/or 216 based on the IP addresses of the ASs 214 and/or 216 included in the DNS responses of the one or more UDP packets. Service dialogue.

In some embodiments, TOF 800 can include a dialog migration module or unit 820 and/or a dialog relay module or unit 822, which can each execute one or more programs, such as shown in FIG. Referring to FIG. 5, in some embodiments, target eNB 204t may issue handover request 502 in response to initiation of handover from source eNB 204s to target eNB 204t. In some embodiments, the handover request 502 can include one or more information elements that can enable handover from the source eNB 204s to the target eNB 204t. In some embodiments, the handover and/or conversational migration from the source eNB 204s to the target eNB 204t may be performed based on delivering one or more information elements with the handover request 502.

In some embodiments, the handover across the TOF may be initiated in response to completion of the handover of the source eNB 204s to the target eNB 204t. In some embodiments, the handover request 502 can include one or more extended information elements to enable handover across the TOF. In some embodiments, in response to completion of handover from source eNB 204s to target eNB 204t, target eNB 204t may transmit session migration request 504 to TOF 800 (eg, if targeted TOF 212t), dialog migration request 504 may include One or more extended information elements delivered by the delivery request 502. In some embodiments, TOF 800 (if as a target TOF) may establish a tunnel to source TOF 212s based on one or more extended information elements.

In some embodiments, in response to receiving from the target eNB 204t The session migration request 504 (e.g., via the eNB interface 804 via the transceiver 840), the dialog migration module 820 can be configured to transmit a session migration request acknowledgement 506 that can be used to confirm whether the inter-TOF tunnel was successfully established, to the target eNB 204t .

In some embodiments, TOF 800 can include a conversation relay module or unit 822. In some embodiments, in response to the dialog migration module 820 responding to the conversation migration request 504 with the conversation migration request confirmation 506, the dialog relay module 822 can be configured to transmit the conversation relay request 508 to the source TOF 212s to request the relay to be available. Traffic flow 512 to TOF 800 of the ongoing conversation between AS 214 and/or 216 and UE 202 is assigned to the ongoing conversation.

In some embodiments, the handover request 502 and/or the conversation migration request 504 can include one or more extended information elements (eg, source TOF context information 612) to indicate the IP address 614, eg, for tunnel establishment. The source TO address or destination IP address of the source TOF 212t in the source TOF to-be-listed list 610 and/or the number 616 (eg, source number or destination number).

In some embodiments, the handover request 502 and/or the conversation migration request 504 can include one or more extended information elements (UE IP address 620) to indicate the IP address of the UE 202 as shown in FIG. It can be assigned to an ongoing conversation with AS 214 and/or 216.

In some embodiments, in response to exchanging dialog relay request 508 and dialog relay request acknowledgement 510 with source TOF 212s, TOF 800 (eg, as target TOF 212t) may be configured to be based on the handover request One or more extended information elements in 502 establish a TOF tunnel to the source TOF 212s. In some embodiments, the target TOF 212t and/or the source TOF 212s may use inter-TOF tunneling to relay one or more service sessions between the UE (eg, UE 202) and ASs 214 and/or 216. In some embodiments, the IP address of the UE 202 can be associated with a tunnel between TOFs. In some embodiments, the source TOF 212s may tunnel one or more IP packets from the UE 202 to the target TOF 212t via the inter-TOF tunnel. In some embodiments, the target TOF 212t may send one or more IP packets with the source IP address 616 of the UE 202' to the UE 202 via the eNB 204.

In some embodiments, in response to the establishment of the tunnel, the destination inspection module in the source TOF 212s may check the destination address, destination destination number, and/or from the AS 214 that may have a conversation with the UE 202. / or 216 of the traffic number in each packet of the stream 512. In some embodiments, in response to the destination/source address checking module determining one or more destination addresses, the destination port number and the agreement number are associated with the tunnel, the source TOF 212s is configurable to use the tunnel to relay ( For example, a packet in traffic flow 512A from the AS 214 and/or 216 to the TOF 800 (e.g., as the target TOF 212t) via the transceiver. In some embodiments, in response to receiving a packet of traffic flow 512 that may be relayed from AS 214 and/or 216 by source TOF 212s, transceiver 840 of TOF 800 (eg, target TOF 212t) may be configured to pass the target The eNB 204t transfers the packet to the UE 202.

On the other hand, in some embodiments, at TOF 800 The destination/source address check module 812 (e.g., target TOF 212t) may check the source address, the source number, and/or the agreement number in each packet, such as may have an AS 214 from the UE 202. And/or 216 of the ongoing traffic flow 512 of the conversation. In some embodiments, in response to the destination/source address check module 812 determining that one or more information elements are associated with the tunnel, the transceiver 840 in the TOF 800 (eg, the target TOF 212t) can be configured to tunnel through the tunnel. The packet in the traffic stream 512 from the UE 202 is sent (e.g., via the transceiver 840) to the source TOF 212s. In some embodiments, in response to a packet in the traffic stream 512 that may be relayed by the TOF 800 from the UE 202, the transceiver in the source TOF 212s may be configured to transfer the received packet to the AS 214 and/or 216.

Although FIG. 8 illustrates some embodiments relating to a destination/source address check module or unit 812, in some embodiments, TOF 800 may include a destination address check module or unit for performing a destination address check, respectively. And/or a source address check module or unit for performing source address inspection.

In some embodiments, in response to detecting inactivity of a traffic flow (eg, 512) in a tunnel for establishment of a predefined period, a dialog relay module in the source TOF 212s may send (eg, via The transceiver in source TOF 212s) talks relay termination request 514 to TOF 800 (eg, as target TOF 212t). In some embodiments, the dialog relay module 822 in the TOF 800 can be configured to transmit (eg, via the transceiver 840) the dialog relay termination request acknowledgement 516 to Source TOF 212s. In some embodiments, the tunnel between the source TOF 212s and the TOF 800 as the target TOF 212t may be terminated or removed in response to the exchange of the conversation relay termination request 514 and the conversation relay termination request acknowledgement 516. In some embodiments, the source TOF 212s may remove the tunnel in response to the exchange of the conversation relay termination request 514 and the conversation relay termination request acknowledgement 516. In some embodiments, in response to the removal of the tunnel, the target TOF 212t (eg, TOF 800) can be configured to support communication between the UE 202 and the ASs 214 and/or 216 via the target eNB 204t. In some embodiments, the handover from the source TOF 212s to the target TOF 212t may be completed in response to the removal of the tunnel.

Although FIG. 8 shows that the TOF 800 can include a decapsulation/packaging module 810, a destination/source address checking module 812, an unloading module 814, a local distribution policy checking module 816, and a network address translation module 818. , dialog migration module 820, dialog relay module 822, and/or DNS proxy 824, in some embodiments, one or more modules of TOF 800 may be provided with one or more processors 830 or other controls It may be implemented by one or more processors 830 or other controllers, or in the same processor or controller.

Although FIG. 8 illustrates some embodiments relating to transceiver 840, in some embodiments, transceiver 840 may be implemented by one or more transmitters and one or more receivers and/or implemented in other transmission/reception structures.

Although FIG. 8 illustrates some embodiments relating to one or more interfaces (eg, 802, 804, 806, or 808), in some embodiments, one or more interfaces may be included in a network (eg, 200). In a In some embodiments, one or more interfaces may be implemented at transceiver 840 or by transceiver 840.

Although FIG. 8 illustrates an example of a DNS proxy 824, in some embodiments, the DNS proxy 824 can include one or more decapsulation modules and/or encapsulation modules, a DNS request/response extraction module, A DNS response storage module, a DNS response retrieval module, a memory or other storage medium (eg, a cache), memory or other storage medium may be based on, for example, about TOF 212 and/or 800 and/or DNS proxy 824. One or more of the procedures, operations, or functions described to store one or more DNS responses and/or include one or more DNS responses or one or more other UDP or IP packets of one or more other modules.

FIG. 9 is an illustration of an example of a system 900 that is illustratively shown in accordance with some embodiments. In some embodiments, system 900 can be configured to include a DNS system (eg, DNS server 232). In some embodiments, system 900 can be provided in internet 230. In some embodiments, system 900 can be implemented in a device, device, system, entity, server, circuit, and/or any other structure using any suitably configured hardware, software, and/or firmware. In some embodiments, system 900 can be configured to perform one or more programs and/or functions as described with respect to DNS server 232.

In some embodiments, system 900 can include one or more interfaces that interface between system 900 and one or more other components in the present invention.

In some embodiments, as shown in FIG. 2, system 900 can include a TOF interface 902 for use with TOF 212 and/or at TOF 212. The TOF agent 824 in the communication. For example, the TOF interface 902 can include an SGi interface or any other suitable interface to communicate with the TOF 212.

In some embodiments, system 900 can include a service server interface 904 to communicate with service LAN server 220 and/or AS 214 and/or 216. For example, the internet interface 904 can include an SGi interface or any other suitable interface to communicate with the serving LAN server 220 and/or AS 214 and/or 216.

In some embodiments, system 900 can include processor 920 and/or memory 922 coupled to one another. System 900 can further include one or more other suitable hardware components and/or software and/or firmware components. In some embodiments, some or all of the components of system 900 can be enclosed in a housing or package and can be interconnected or operatively associated using one or more wired or wireless links. In other embodiments, the components of system 900 can be distributed across multiple or separate devices.

Processor 920 can include, for example, a central processing unit (CPU), a digital signal processor (DSP), a graphics processing unit (GPU), one or more processor cores, a single core processor, a dual core processor, a multi-core processor , microprocessor, host processor, controller, one or more processor or controller sets, chips, microchips, baseband circuits, radio frequency (RF) circuits, logic units, integrated circuits (ICs), application-specific ICs (ASIC) or any other suitable multi-purpose or dedicated processor or controller or one or more circuits or circuits and/or any combination thereof. Processor 920 can execute instructions such as the operating system (OS) of system 900 and/or one or more suitable applications.

In some embodiments, memory 922 can include, for example, random access memory (RAM), read only memory (ROM), dynamic RAM (DRAM), synchronous DRAM (SD-RAM), flash memory, volatile Memory, non-volatile memory, cache memory, buffer, short-term memory unit, long-term memory unit or other suitable memory unit or storage unit. Memory 922 can be configured to store, for example, data and/or instructions for system 900.

In some embodiments, system 900 can include a DNS query or request check module or unit 910 that is coupled to one or more other components in system 900. In some embodiments, TOF 212 may receive one or more UDP packets of destination 53 associated with UE 202 from eNB 204, such as in a DNS request 404 having a GTP-U format. The TOF 212 may decapsulate one or more GTP-U packets from the eNB 204 with the portable DNS request 404 to obtain one or more IP packets. In some embodiments, TOF 212 may send one or more IP packets to DNS proxy 824 in TOF 212 or other DNS proxy that may include zone AS 214.

In some embodiments, DNS proxy 824 may extract DNS request 404 from one or more of the one or more IP packets from TOF 212, and/or may be packaged with one or more of destinations 53 The extracted DNS request 404 in the UDP packet. In some embodiments, DNS proxy 824 can send one or more UDP packets carrying DNS request 404 that may be encapsulated in more than one IP packet to TOF 212.

In some embodiments, TOF 212 may perform NAT on one or more IP packets from DNS proxy 824 in TOF 212 to translate the source IP address of the IP packet into the global IP address of TOF 212 to provide DNS request 406. The TOF 212 may offload one or more IP packets carrying the DNS request 406 to the system 900.

In some embodiments, system 900 can be configured to receive one or more IP packets associated with DNS request 406 from TOF 212 (via transceiver 930) through TOF interface 902.

In some embodiments, in response to receiving one or more IP packets from the TOF 212, the DNS query checking module 910 can be configured to determine whether the service requested by the UE 202 is deployed in one or more mappings stored in the memory 922. One or more ASs (eg, zone AS 214 or external AS 216). In response to the DNS query checking module 910 determining that the service requested by the UE 202 is deployed in one or more of the one or more mappings 214 and/or 216, the address obtaining module 912 can be configured to obtain one or more One or more IP addresses of the AS 214/216. In some embodiments, the address obtaining module 912 can be configured to retrieve one or more mappings between the global IP address of the TOF 212 and the IP address of the AS 214/216 to obtain for request by the UE 202. The IP address of one or more AS 214/216 services. In some embodiments, one or more mappings may be stored in memory 922, for example, in a table, array, list, or any other structure or form. In some embodiments, system 900 can echo TOF 212 with DNS response 408 in response to DNS request 406, which can include the retrieved IP address of one or more ASs 214/216.

In some embodiments, in response to determining that the requested service is not deployed in any of the regions AS 214 or any of the external ASs 216 of one or more mappings, but is deployed in one or more of the new ASs 214/ In 216, the administrator of system 900 can update one or more mappings in system 900, such as removing one or more mappings and/or including one or more new AS 214/216 IP addresses and/or One or more new mappings between the global IP address of the TOF 212 and the IP address of the new AS 214/216. In some embodiments, the address obtaining module 912 can retrieve the IP address of the new AS 214/216 from a new or updated mapping in the memory 922. In some embodiments, DNS 408 may include retrieved IP addresses of one or more new ASs 214/216.

In some embodiments, the encapsulation module or unit 916 can encapsulate the DNS response 408 as one or more UDP packets and/or can further encapsulate one or more UDP packets in one or more IP packets that are sent to the TOF 212. . In some embodiments, the DNS query response module 914 can send a DNS response 408 to the TOF 212 as one or more UDP packets that can be encapsulated in one or more IP packets to indicate one or more in response to the DNS request 406. IP address of AS 214/216 or new AS 214/216. In some embodiments, system 900 can transmit DNS response 408 to TOF 212 as one or more UDP packets indicating that no AS can be able to provide the service requested in DNS request 406.

In response to receiving one or more IP packets from system 900, TOF 212 may send the received IP packets to DNS proxy 824 in TOF 212. In some embodiments, DNS proxy 824 can extract IP A DNS response 408 in one or more UDP packets of the packet. In some embodiments, DNS proxy 824 stores or caches one or more DNS responses 408. The DNS proxy 824 can retrieve the cached DNS response to obtain a DNS response 408 in response to a subsequent DNS request without querying the system 900 again. In some embodiments, the DNS proxy 824 can encapsulate the extracted DNS response 408 or the queried DNS response 408 as one or more UDP packets that can include the source port number 53 and/or the destination address to the UE 202. In some embodiments, DNS proxy 824 can encapsulate one or more UDP packets into one or more IP packets, and/or can send one or more IP packets to TOF 212.

In some embodiments, TOF 212 may encapsulate one or more IP packets of DNS proxy 824 into one or more GTP-U packets to generate a DNS response 410 that is sent to eNB 204. The TOF 212 may send a GTP-U packet containing the DNS response 410 to the eNB 204. The eNB 204 may decapsulate the received DNS response 410 to obtain one or more UDP packets with a source 埠 53 of the portable DNS response 410, and/or may have one or more UDP packets with source 埠 53 as a DNS response 412. It is transmitted to the UE 202, which may initially send the DNS response 402.

In some embodiments, the UE 202 can establish a communication or service session with one or more ASs 214/216 that can have an IP address indicated in the DNS response 412, such as via the eNB 204 and/or the TOF 212.

Although FIG. 9 shows that system 900 can include DNS query check module 910, address obtaining module 912, DNS request response module 914, and/or package module 917, in some embodiments, modules 910 through 916 One or more may be provided in one or more processors 920 or other controllers or control circuits or implemented by one or more processors 920 or other controllers or control circuits.

Although FIG. 9 illustrates some embodiments of a transceiver 930, in some embodiments, the transceiver 930 can be implemented by one or more transmitters and one or more receivers, and/or implemented in other transmission/reception structures.

Although FIG. 9 illustrates some embodiments of one or more interfaces (eg, 902 or 904), in some embodiments, one or more interfaces may be included in a network (eg, 200). In some embodiments, one or more interfaces can be implemented at transceiver 930 or by transceiver 930.

Embodiments described herein can be implemented in systems using suitably configured hardware, software, and/or firmware. 10 shows (for an embodiment) a radio frequency (RF) circuit 1030, a baseband circuit 1020, an application circuit 1010, a front end module (FEM) circuit 1060, a memory/storage 1040, including at least mutual coupling as shown. An example system of one or more antennas 1050, display 1002, camera 1004, sensor 1006, and input/output (I/O) interface 1008. For an embodiment, FIG. 10 illustrates example components of a UE device 1000 in accordance with some implementations.

Application circuit 1010 can include one or more application processors. For example, application circuit 1010 can include circuitry such as, but not limited to, one or more single core or multi-core processors. A processor can include any combination of a general purpose processor and a special purpose processor (eg, a graphics processor, an application processor, etc.). The processor can be coupled to the memory/storage and/or can include a memory/storage and can be configured to be stored in a memory/storage The instructions enable various applications and/or operating systems to run on the system.

Baseband circuitry 1020 may include circuitry such as, but not limited to, one or more single core or multi-core processors. The baseband circuit 1020 can include a baseband processor and/or control logic for processing one or more baseband signals received from the receive signal path of the RF circuit 1030 and for generating baseband signals for the transmit signal path of the RF circuit 1030. . Baseband processing circuitry 1020 can interface with application circuitry 1010 for baseband signal generation and processing and for control operations of RF circuitry 1030. For example, in some embodiments, baseband circuitry 1020 can include a second generation (2G) baseband processor 1020a, a third generation (3G) baseband processor 1020b, a fourth generation (4G) baseband processor 1020c, and/or Other existing generation or developing generations or other baseband processors 1020d that will be developed in the future (eg, fifth generation (5G), 6G, etc.). Baseband circuitry 1020 (e.g., one or more baseband processors) can handle various radio control functions that can communicate with one or more radio networks via RF circuitry 1030. Radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, and the like. In some embodiments, the modulation/demodulation circuitry of baseband circuitry 1020 can include Fast Fourier Transform (FFT) precoding and/or cluster mapping/demapping functionality. In some embodiments, the encoding/decoding circuitry of baseband circuitry 1020 may include convolution, tail-biting convolution, acceleration, Viterbi, and/or low density parity checking (Low Density Parity). Check; LDPC) Encoder/Decoder function. Embodiments of modulation/demodulation and encoder/decoder functions are not limited to these examples and may be included in other implementations Other suitable features in the example.

In some embodiments, baseband circuitry 1020 may comprise elements of a protocol stack, such as, for example, elements of an EUTRAN protocol, including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data Aggregation Protocol (PDCP) and/or RRC components. The central processing unit (CPU) 1020e of the baseband circuit 1020 can be configured to operate elements of a protocol stack for PHY, MAC, RLC, PDCP, and/or RRC layer communication. In some embodiments, baseband circuitry 1020 can include one or more video digital signal processors (DSPs) 1020f, which can include compression/decompression and echo cancellation components, and can include other suitable processing in other embodiments. element. The components of the baseband circuit can be suitably combined in a single wafer, in a single wafer set, or in some embodiments on the same circuit board. In some embodiments, some or all of the constituent components of baseband circuit 1020 and application circuit 1010 can be implemented together, for example, on a system single chip (SOC).

In some embodiments, baseband circuitry 1020 can provide communication compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 1020 can support EUTRAN and/or other wireless metropolitan area networks (WMANs), wireless local area networks (WLANs). , wireless personal area network (WPAN) communication. Embodiments in which baseband circuitry 1020 is configured to support more than one wireless protocol for radio communication may refer to a multimode baseband circuitry.

The RF circuit 1030 is capable of communicating with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, RF circuit 1030 can include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. The RF circuit 1030 can include a receive signal path that can include circuitry for down-converting the RF signal received from the FEM circuit 1060 and providing a baseband signal to the baseband circuit 1020. The RF circuit 1030 can also include a transmit signal path that can include circuitry for up-converting the baseband signals provided by the baseband circuitry 1020 and providing RF output signals to the FEM circuitry 1060 for transmission.

In some embodiments, RF circuit 1030 can include a receive signal path and a transmit signal path. The receive signal path of RF circuit 1030 can include mixer circuit 1030a, amplifier circuit 1030b, and/or filter circuit 1030c. The transmit signal path of RF circuit 1030 can include filter circuit 1030c and/or mixer circuit 1030a.

The RF circuit 1030 can also include a synthesizer circuit 1030d for synthesizing a frequency for use by the mixer circuit 1030a that receives the signal path and the transmission signal path. In some embodiments, the mixer circuit 1030a that receives the signal path can be configured to convert the RF signals received from the FEM circuit 1060 based on the synthesized frequency drop provided by the synthesizer circuit 1030d.

Amplifier circuit 1030b can be configured to amplify the down conversion signal. The filter circuit 1030c can be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to produce an output baseband signal. Output baseband signal can be provided to the baseband circuit 1020 for further processing. In some embodiments, the output baseband signal can be a zero frequency baseband signal, although this is not required. In some embodiments, the mixer circuit 1030a that receives the signal path can include a passive mixer, although the scope of the embodiments is not limited thereto.

In some embodiments, the mixer circuit 1030a that transmits the signal path can be configured to convert the input baseband signal based on the synthesized frequency signal provided by the synthesizer circuit 1030d to generate an RF output signal for the FEM circuit 1060. The baseband signal may be provided by baseband circuitry 1020 and may be filtered by filter circuitry 1030c. The filter circuit 1030c may include a low pass filter (LPF), although the scope of the embodiments is not limited thereto.

In some embodiments, the mixer circuit 1030a that receives the signal path and the mixer circuit 1030a that transmits the signal path can include two or more mixers and can be configured for quadrature down conversion and/or liter, respectively. Conversion. In some embodiments, the mixer circuit 1030a that receives the signal path and the mixer circuit 1030a that transmits the signal path can include two or more mixers and can be configured for image rejection (eg, Hartley image rejection (Hartley image) Rejection)). In some embodiments, the mixer circuit 1030a that receives the signal path and the mixer circuit 1030a that transmits the signal path can be configured for direct down conversion and/or direct up conversion, respectively. In some embodiments, the mixer circuit 1030a that receives the signal path and the mixer circuit 1030a that transmits the signal path can be configured for superheterodyne operation.

In some embodiments, the output baseband signal and the input baseband The signal can be an analog baseband signal, although the scope of the embodiments is not limited thereto. In some alternative embodiments, the output baseband signal and the input baseband signal can be digital baseband signals. In these alternate embodiments, RF circuit 1030 can include an analog to digital converter (ADC) and a digital to analog converter (DAC) circuit and baseband circuit 1020 can include a digital baseband interface to communicate with RF circuit 1030.

In some dual mode embodiments, separate radio IC circuits may provide processing signals for each spectrum, although the scope of the embodiments is not limited thereto.

In some embodiments, the synthesizer circuit 1030d can be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not Other types of frequency synthesizers can be used. For example, the synthesizer circuit 1030d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop and a frequency divider (divider).

Synthesizer circuit 1030d can be configured to synthesize an output frequency for use by mixer circuit 1030a of RF circuit 1030 based on the frequency output and the divider control input. In some embodiments, synthesizer circuit 1030d can be a fractional N/N+1 synthesizer.

In some embodiments, the frequency input can be provided by a voltage controlled oscillator (VCO) (which is not required). The divider control input can be provided by baseband circuitry 1020 or application processor 1010 based on the desired output frequency. In some embodiments The divider control input (eg, X) may be determined from the lookup table based on the channel indicated by the application processor 1010.

The synthesizer circuit 1030d of the RF circuit 1030 can include a divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA). In some embodiments, the DMD can be configured to divide the input signal by N or N+1 (eg, based on carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of series, adjustable, delay elements, phase detectors, charge pumps, and D-type flip-flops. In these embodiments, the delay element can be configured to break the VCO period into phases of Nd identical packets, where Nd is the number of delay elements in the delay line. In this way, the DLL provides a negative feedback to help ensure that the total delay of the entire delay line is one VCO cycle.

In some embodiments, synthesizer circuit 1030d can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (eg, twice the carrier frequency, quadruple carrier frequency) and The quadrature generator and divider circuit are used together to generate a plurality of signals having a plurality of different phases with respect to each other at a carrier frequency. In some embodiments, the output frequency can be the LO frequency (f _LO ). In some embodiments, RF circuit 1030 can include an IQ/pole converter.

FEM circuit 1060 can include a receive signal path that can include an RF signal configured to operate from one or more antennas 1050, Amplifying the received signal and providing an amplified version of the received signal to the RF circuit 1030 for further processing. FEM circuit 1060 can also include a transmission signal path that can include circuitry configured to amplify signals provided by RF circuit 1030 for transmission for transmission by one or more of one or more antennas 1050.

In some embodiments, FEM circuit 1060 can include a transmit/receive (TX/RX) switch to switch between transmit mode and receive mode operation.

The FEM circuit can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit can include a low-noise amplifier (LNA) for amplifying the received RF signal and providing an amplified received RF signal as an output (eg, to RF circuit 1030). The transmit signal path of the FEM circuit 1060 can include a power amplifier (PA) for amplifying the input RF signal (eg, provided by the RF circuit 1030) and for generating an RF signal for subsequent transmission (eg, by one or more antennas 1050) One or more filters of one or more of them.

In some embodiments, the UE 1000 includes a plurality of power saving mechanisms. If the UE 1000 is in the RRC_Connected state and is still connected to the eNB if it expects to receive traffic in a short time, it may enter a state called discontinuous reception mode (DRX) after a period of inactivity. During this state, the device can be powered down briefly, saving power.

If there is no data traffic activity for a long time, the UE 1000 can transition to the RRC_Idle state where it is disconnected from the network and does not perform operations such as channel quality feedback, handover, and the like. UE 1000 A very low power state is entered, and it performs paging again, while it periodically wakes up to listen to the network and then powers down again. In this state, the device cannot receive data, and in order to receive data, it must be converted back to the RRC_Connected state.

An additional power saving mode may allow the device to be longer than the paging interval (from a few seconds to a few hours) in an unavailable network. During this time, the device is completely unable to access the network and may be completely powered down. Any data sent during this time will have a large delay and it is assumed that the delay is acceptable.

In various embodiments, the transmission, control, and/or reception circuits discussed or recited herein may be embodied in whole or in part in one of RF circuit 1030, baseband circuit 1020, FEM circuit 1060, and/or application circuit 1010. Or multiple. As used herein, the term "circuitry" may mean, partially, or include an application-specific integrated circuit (ASIC), electronic circuit, processor (shared, dedicated, or group) and/or perform one or more Software or firmware (shared, dedicated, or grouped), combinatorial logic, and/or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry can be implemented in one or more software or firmware modules or units, or the functions associated with the circuitry can be implemented by one or more software or firmware modules or units.

In some embodiments, some or all of the constituent components of baseband circuit 1020, application circuit 1010, and/or memory/storage may be implemented together on a system single chip (SOC).

Memory/storage 1040 can be used to load and store data and/or instructions, such as for a system. The memory/storage 1040 of an embodiment may include a combination of suitable volatile memory (eg, dynamic random access memory (DRAM)) and/or non-volatile memory (eg, flash memory). .

In various embodiments, I/O interface 1008 can include one or more user interfaces designed to enable a user to interact with the system and/or a peripheral component interface designed to enable peripheral components to interact with the system. The user interface can include, but is not limited to, a physical keyboard or keypad, a touchpad, a speaker, a microphone, and the like. Peripheral component interfaces may include, but are not limited to, non-volatile memory cartridges, universal serial bus (USB) ports, audio jacks, and power supply interfaces.

In various embodiments, the sensor can include one or more sensing devices to determine environmental conditions and/or location information related to the system. In some embodiments, the sensor can include, but is not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit has a portion of a baseband circuit and/or RF circuit that can communicate with components of the positioning network (eg, Global Positioning System (GPS) satellites), or with components of the positioning network (eg, a global positioning system ( GPS) satellite) communication baseband circuit and / or RF circuit interaction.

In various embodiments, display 1002 can include a display (eg, a liquid crystal display, a touch screen display, etc.).

In various embodiments, the system can be a mobile computing device, Such as but not limited to laptop computing devices, tablet computing devices, small notebooks, thin and light notebooks, smart phones, and the like. In various embodiments, the system may have more or fewer components, and/or different architectures.

As used herein, the term "circuitry" may mean, partially, or include an application-specific integrated circuit (ASIC), electronic circuit, processor (shared, dedicated, or group) and/or perform one or more Software or firmware (shared, dedicated, or grouped), combinatorial logic, and/or other suitable components that provide the described functionality. In some embodiments, the electronic device circuitry can be implemented in one or more software or firmware modules or units, or the functions associated with the circuitry can be implemented by one or more software or firmware modules or units.

example

Example 1 can include a traffic offload function (TOF) device, which can include a memory that includes one or more instructions, and a processor that executes one or more of the instructions to: detect and a destination address of the traffic associated with the user equipment (UE) of the first base station, and determining whether to offload the traffic from the first base station to the first server or the second server based on the destination address; The processor determines that the destination address of the traffic is destined to the first server, providing the traffic to the first server; and responsive to the processor determining that the traffic destined to the first server is local A splitting policy that provides the traffic to the second server.

Example 2 may include the device of Example 1 or some of its As an example, the processor can further perform a network address translation (NAT) to translate the source address of the traffic transmitted to the second server to a global address of the TOF entity.

Example 3 can include any of the examples 1 through 2 or some other examples herein, wherein the processor can further decapsulate the traffic into one or more Internet Protocol (IP) packets.

Example 4 can include any one of the examples 1 to 3 or some other examples herein, wherein the processor is further responsive to determining that the one or more IP packets do not conform to the local distribution policy, the one of the traffic The plurality of IP packets are encapsulated for one of a server gateway (SGW) or a plurality of General Packet Radio Service (GPRS) Tunneling Agreement User Plane (GTP-U) packets.

Example 5 can include any of the examples 1 through 4 or some other examples herein, wherein the processor can further transmit the one or more GTP-U packets to the SGW.

Example 6 can include any one of the examples 1 to 5 or some other examples herein, wherein the processor can further decapsulate the traffic into one or more IP packets, wherein the traffic includes a domain associated with the UE Name system request; and providing the one or more IP packets corresponding to the DNS request to a Domain Name System (DNS) agent in the device.

Example 7 can include any one of the examples 1 to 6 or some other examples herein, wherein the processor can further translate the source IP address of the DNS request extracted by the DNS proxy to the device a global IP address; sending the DNS request to the second server including the DNS server; and providing a DNS response from the second server to the first base station in response to the DNS request, wherein the DNS response Indicates an IP address of the first server that includes an application server that provides the service requested in the DNS request.

Example 8 can include any one of the examples 1-7 or some other examples herein, wherein the processor can further establish the TOF entity and the second in response to initiation of a handover from the second TOF entity to the TOF entity TOF point-to-point tunnel between TOF entities.

Example 9 can include any of the examples 1-8 or some other examples herein, wherein the processor can be further based on a deal associated with a handover from a first base station to a second base station in communication with the UE Transmitting one or more information elements in the request to establish the TOF inter-point tunnel, wherein the one or more information elements include background information from the second TOF entity, an IP address of the second TOF entity, One or more of the 埠 number of the TOF point tunnel and the group of IP addresses of the UE.

Example 10 can include any one of the examples 1-9 or some other examples herein, wherein the processor can further provide a dialog relay request to the second TOF entity in response to receiving a dialog migration request from the second base station And establishing the TOF point-to-point tunnel based on the dialog relay request confirmation message from the second TOF entity.

Example 11 can include any of the examples 1 to 10 or some other examples herein, wherein the processor can further derive from the second base The ground station receives a conversation migration request, wherein the conversation migration request includes the one or more information elements.

Example 12 may include any one of the examples 1 to 11 or some other examples herein, wherein the processor is further responsive to the processor determining one of a source address, a source number, and an agreement number in the traffic A plurality of points are associated with the TOF point tunnel, and the traffic associated with the UE is provided to the second TOF entity via the inter-TOF tunnel.

Example 13 can include any one of the examples 1 to 12 or some other examples herein, wherein the processor can further provide a dialog relay termination request acknowledgement in response to receiving a dialog relay termination request from the second TOF entity, The TOF tunnel is removed by the second TOF entity in response to the inactivity of the traffic in the inter-TOF tunnel.

Example 14 can include a Domain Name System (DNS), which can include a receiver that receives a DNS request associated with a User Equipment (UE) from a Traffic Offload Function (TOF) entity, wherein the DNS request includes a TOF corresponding to the TOF a source address of the entity's global IP address; a memory that stores a mapping table between the global IP address of the TOF entity and an IP address of the first application server (AS); and a processor responsive to Determining that the service requested in the DNS request is deployed in the first AS, retrieving the mapping table to obtain the IP address of the first AS; and a transmitter transmitting the first AS in the DNS response The IP address is addressed to the TOF entity.

Example 15 can include the DNS of Example 14 or some other examples herein, wherein the processor can be further responsive to the determination by the DNS Requesting the requested service to be available in the first AS and deployed in the second AS, updating the mapping table to include the global IP address of the TOF entity and the IP address of the second AS The mapping between the two.

Example 16 can include any of the examples 14 through 15 or some other examples herein, wherein the processor can further retrieve the mapping table to obtain the IP address of the second AS.

Example 17 can include any of the examples 14 to 16 or some other examples herein, wherein the DNS can further include a transmitter responsive to the processor determining that the service requested by the DNS request is deployed at the second AS Transmitting a DNS response to the TOF entity to include the IP address of the second AS.

Example 18 can include any of the examples 14 through 17, or some other examples herein, wherein the first AS includes a region AS that is in contrast to the TOF entity or an external AS that is outside the regional network of the TOF entity.

The example 19 may include the DNS of any one of claims 14 to 18, wherein the second AS includes a region AS that is in contrast to the TOF entity or an external AS outside the regional network of the TOF entity.

Example 20 can include a user equipment (UE) including: a transceiver that transmits a Domain Name System (DNS) request associated with a service for the UE to a first base station, and receives from the first a DNS response of the base station to indicate an Internet Protocol (IP) address of a first application server (AS) for providing the service for the UE; and a controller coupled to the transceiver, Where the controller is based on the first The IP address of the AS initiates a service dialogue with the first AS.

Example 21 may include the UE of Example 20 or some other example herein, wherein the DNS request includes a User Datagram Protocol (UDP) packet having a destination address associated with the DNS.

Example 22 can include any of the examples 20 through 21 or some other examples herein, wherein the DNS response includes a UDP packet having a source address associated with the DNS.

Example 23 can include any of the examples 20 through 22 or some other examples herein, wherein the controller is further responsive to the transceiver receiving the DNS response from the first base station indicating the IP address of the second AS, starting A session with the service of the second AS, wherein the second AS provides the UE with a service that is not available in the first AS.

Example 24 can include any of the examples 20 through 23 or some other examples herein, wherein the controller can further initiate the second base station in response to the handover from the first base station to the second base station communication.

Example 25 can include any of the examples 20 through 24 or some other examples herein, wherein the controller can be further responsive to the transfer from the first traffic offload function (TOF) entity to the second TOF entity, initiating and second Communication of the TOF entity, which communicates with the first TOF entity via a TOF tunnel between the first TOF entity and the second TOF entity.

Example 26 can include a base station device that can include a memory that includes one or more instructions; a controller that is configured to perform Passing the one or more instructions to transform a first user datagram protocol (UDP packet) from a User Name Authority (UE) Domain Name System (DNS) request to a first General Packet Radio Service (GPRS) tunneling protocol a user plane (GTP-U) packet; providing the first GTP-U packet to a first traffic offload function (TOF) entity; and receiving an internet protocol (IP) including an application server (AS) from the TOF entity The second GTP-U packet of the DNS response of the address.

Example 27 can include the device of Example 26 or some other example herein, wherein the processor can further provide the second UDP packet to the UE in response to the controller converting the second GTP-U packet to a second UDP packet.

Example 28 can include any one of the examples 26 through 27 or some other examples herein, wherein the processor can further provide a dialog migration request to the second in response to the handover from the first TOF entity to the second TOF entity a TOF, wherein the dialog migration request includes one or more information elements in the group, the group includes background information from the second TOF entity, an IP address of the second TOF entity, and a location for the TOF The number of the tunnel, the IP address of the UE.

Example 29 can include any of the examples 26-28, or some other examples herein, wherein the processor can further receive a dialog migration request confirmation from the second TOF entity.

Example 30 can include any of the examples 26 through 29 or some other examples herein, wherein the device can further include a transceiver coupled to the processor and coupled to one or more antennas of the processor.

Example 31 can include machine readable media having instructions stored thereon that, when executed, cause a first traffic offload function (TOF) entity to transmit a first universal packet radio service from a first base station (GPRS) The tunneling protocol user plane (GTP-U) packet is decapsulated into an internet protocol (IP) packet; in response to determining that the destination address of the IP packet is destined to the application server (AS) to offload the IP packet to the first And applying the server; and in response to determining that the IP packet is not destined to the AS, the IP packet satisfies a local distribution policy, and the IP packet is offloaded to the Internet.

Example 32 may include machine readable media of example 31 or some other examples herein having instructions stored thereon that, when executed, cause the first traffic offload function (TOF) entity to further offload the IP packet Perform network address translation on the IP packet before the Internet.

Example 33 can include the machine readable medium of Example 31 or 32 or some other example herein, wherein the first AS is collocated with the first TOF entity.

The example 34 can include any one of the machine readable media of any of the examples 31-33, or some other examples herein, having instructions stored thereon that, when executed, cause the first traffic offload function (TOF) entity to further respond Determining that the IP packet does not conform to the local distribution policy, decapsulating the IP packet into a second universal packet radio service (GPRS) tunneling protocol user plane (GTP-U) packet for a server gateway (SGW) .

Example 35 can include any of the machine readable media of any of examples 31-34 or some other examples herein, having instructions stored thereon that, when executed, cause the first traffic offload function (TOF) entity to further respond The destination address of the IP packet is translated to the global IP address of the first TOF entity by determining that the IP packet is a DNS request destined to a Domain Name System (DNS) in the Internet.

The example 36 can include any one of the machine readable media of any of the examples 31-35 or some other examples herein, having instructions stored thereon that, when executed, cause the first traffic offload function (TOF) entity to be further unloaded An IP packet having the global IP address to the DNS; and transferring a DNS response from the DNS to the first base station, wherein the DNS response is used to indicate the first of the services that can be requested in the DNS request The IP address of the server.

The example 37 can include any of the machine readable media of any of the examples 31-35 or some other examples herein, having instructions stored thereon that, when executed, cause the first traffic offload function (TOF) entity to further respond The IP packet requested to be requested in the DNS request is deployed in the second AS, and the IP packet is offloaded to the second AS.

The example 38 can include any one of the machine readable media of any of the examples 31-37 or some other examples herein, having instructions stored thereon that, when executed, cause the first traffic offload function (TOF) entity to further respond And establishing a TOF point tunnel with the second TOF entity in the handover from the first TOF entity to the second TOF entity.

Example 39 can include any of the examples 31 to 38. Reading media or some other examples herein, having instructions stored thereon, when the instructions are executed, causing the first traffic offload function (TOF) entity to further receive a dialog relay request from the second TOF entity; Transmitting a dialog relay request acknowledgement message to the second TOF entity to establish the TOF inter-point tunnel.

The example 40 can include any one of the machine readable media of any of the examples 31-39 or some other examples herein, having instructions stored thereon that, when executed, cause the first traffic offload function (TOF) entity to be further based The TOF point-to-point tunnel is established at one or more information elements in the dialog relay request from the second TOF entity.

Example 41 may include any one of the machine readable media of any one of examples 31 to 40 or some other examples herein, wherein the one or more information elements include background information of the second TOF entity, an IP address of the second TOF entity And one or more of the 埠 number for the TOF point tunnel and the IP address of the UE.

Example 42 can include any of the machine readable media of any of examples 31-41 or some other examples herein, having instructions stored thereon that, when executed, cause the first traffic offload function (TOF) entity to further respond Receiving the dialog relay request from the second TOF entity, transmitting a dialog relay request confirmation to the second TOF entity.

Example 43 can include any of the machine readable media of any of examples 31-42 or some other examples herein, having instructions stored thereon that, when executed, cause the first traffic offload function (TOF) entity to further respond Determining the destination in the packet from the service server One or more of the location address, the destination number, and the agreement number relate to the TOF pointpoint tunnel, and the packet is transmitted to the second TOF entity via the TOF pointpoint tunnel.

The example 44 can include any of the machine readable media of any of the examples 31-43 or some other examples herein, having instructions stored thereon that, when executed, cause the first traffic offload function (TOF) entity to further The TOF point tunnel receives a packet from the second TOF entity, wherein one or more of a destination address, a destination number, and a protocol number in the packet from the second TOF and the TOF point tunnel Correlating; and transmitting the packet from the second TOF entity to the service server.

Example 45 can include machine readable media having instructions stored thereon that, when executed, cause a Domain Name System (DNS) to receive from a first traffic offload function (TOF) entity with a user equipment (UE) An associated DNS request, wherein the DNS request includes a source address corresponding to a global IP address of the first TOF entity; and responsive to determining that the service requested in the DNS request is deployed on the first application server (AS), retrieving the mapping table to obtain an IP address of the first AS, wherein the mapping table includes a set of one or more global IP addresses of the first TOF entity and a set of one or more IPs of the first AS The mapping between addresses.

Example 46 can include machine readable media of example 45 or some other examples herein, having instructions stored thereon that, when executed, cause the DNS to further respond to the first AS in a DNS response The IP address is transmitted to the first TOF entity.

Example 47 can include any of the machine readable media of any of Examples 45-46 or some other examples herein, having instructions stored thereon that, when executed, cause the DNS to further respond to a request to be requested by the DNS request The service is unavailable in the first AS and available in the second AS, updating the mapping table to include between the global IP address of the first TOF entity and the IP address of the second AS Mapping.

Example 48 can include any of the machine readable media of any of Examples 45-47 or some other examples herein, having instructions stored thereon that, when executed, cause the DNS to further retrieve the mapping table to obtain the The IP address of the second AS.

Example 49 can include any of the machine readable media of any of Examples 45-48 or some other examples herein, having instructions stored thereon that, when executed, cause the DNS to further respond to a request to be requested by the DNS request The service is available in the second AS, and the DNS response is transmitted to the first TOF entity to include the IP address of the second AS.

Example 50 can include machine readable media having instructions stored thereon that, when executed, cause a user equipment (UE) to transmit to a first base station a domain associated with a service for the UE a name system (DNS) request; and receiving a DNS response from the first base station indicating an Internet Protocol (IP) address of a first application server (AS) for providing the service for the UE; Starting a service session with the first AS based on the IP address of the first AS.

The example 51 can include the machine readable medium of the example 50 or some other example herein, wherein the DNS request includes a User Datagram Protocol (UDP) packet having a destination address destined to the DNS.

Example 52 can include any of the machine readable media of Examples 50-51 or some other examples herein, wherein the DNS response includes a User Datagram Protocol (UDP) packet having a source address to the DNS.

Example 53 can include any of the machine readable media of any of examples 50-52 or some other examples herein having instructions stored thereon that, when executed, cause the UE to further respond to the transceiver from the first Receiving, by the base station, the DNS response including the IP address of the second application server (AS), initiating a service session with the second AS, wherein the service for the UE is not available in the first AS, The second AS provides the service for the UE.

Example 54 can include any of the machine readable media of any of examples 50-53 or some other examples herein, having instructions stored thereon that, when executed, cause the UE to further respond to the first base station The handover of the second base station initiates communication with the second base station.

Example 55 can include any of the machine readable media of any of examples 50-54 or some other examples herein having instructions stored thereon that, when executed, cause the UE to further respond to the unloading function from the first traffic The handover of the (TOF) entity to the second TOF entity initiates communication with the second TOF entity, which communicates with the first TOF entity via a TOF tunnel between the first TOF entity and the second TOF entity.

Example 56 can include machine readable media having instructions stored thereon that, when executed, cause the base station to initiate a first use of a Domain Name System (DNS) request from a User Equipment (UE) a Datagram Protocol (UDP) packet is a first General Packet Radio Service (GPRS) Tunneling Agreement User Plane (GTP-U) packet; and transmitting the first GTP-U packet to a first Traffic Offload Function (TOF) entity and A second GTP-U packet containing a DNS response of an Internet Protocol (IP) address of an application server (AS) is received from the first TOF entity.

Example 57 can include machine readable media of example 56 or some other examples herein having instructions stored thereon that, when executed, cause the base station to further respond to transforming the second GTP-U packet For the second UDP packet, the second UDP packet is transmitted to the UE.

Example 58 can include any of the machine readable media of any of examples 56-57 or some other examples herein having instructions stored thereon that, when executed, cause the base station to further respond to the first TOF Transmitting an entity to the second TOF entity, transmitting a dialog migration request to a second TOF, wherein the dialog migration request includes one or more information elements in the group, the group including background information of the second TOF entity, The IP address of the second TOF entity, the 埠 number for the TOF inter-point tunnel, and the IP address of the UE.

Example 59 can include any of the machine readable media of any of examples 56-58 or some other examples herein having instructions stored thereon that, when executed, cause the base station to further proceed from the second TOF The entity receives the dialog migration request confirmation.

Example 60 may include means including control circuitry, transmission circuitry, and/or reception circuitry to perform one or more of the devices described in Examples 1-59 or with respect to any of the Examples 1-59 TOF, DNS, UE, or eNB. Components, and/or any other described herein.

Example 61 can include the methods as illustrated and described herein, and/or include one or more of the elements described in any of Examples 1-60 and/or any other embodiments described herein.

Example 62 can include a wireless communication system as shown and described herein, and/or one of the TOF, DNS, UE, or eNB described in any of the Examples 1-61 and/or any other embodiments described herein. Or multiple components.

Example 63 can include a wireless communication device as illustrated and described herein, and/or one of a TOF, DNS, UE, or eNB as described in any of Examples 1-62 and/or any other embodiments described herein. Or multiple components.

It should be understood that many of the functions described in the specification can be labeled as modules or units in order to more particularly emphasize their implementation independence. For example, a module or unit can be implemented as a hardware circuit comprising a custom VLSI circuit or gate array, an existing semiconductor such as a logic die, a transistor, or other discrete components. Modules or units may also be implemented in a programmable hardware device, such as a field programmable gate array, programmable array logic, programmable logic devices, or the like.

Modules or units can also be implemented in software for use by Execution of various types of processors. An identified module or unit of executable code may, for example, comprise one or more entities or logical blocks of computer instructions, which may, for example, be organized into an object, program or function. However, the executable modules of the identified modules need not be physically located together, but may include different instructions stored in different locations that are logically combined together, include the module or unit and are used for The state of use of the module or unit.

A module or unit of executable code can be a single instruction or many instructions and can even be distributed across many different code segments, distributed across different programs, and across many memory devices. Similarly, operational data may be identified and may be shown herein in a module or unit and may be implemented in any suitable form and organized into any suitable type of data structure. The selection data may be collected as a single data set or may be distributed between different locations, including between different storage devices and may be at least partially electronically present on the system or network. Modules or units can be passive or active, including agents that operate to perform the required functions.

The "example" referred to in this specification means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the invention. Therefore, the words "in an example" appearing in various places in this specification are not necessarily referring to the same embodiment.

As used herein, for convenience, a plurality of objects, structural elements, component elements, and/or materials may be presented in a common table. However, such tables should be construed as though each member of the table is independently identified as a separate and distinct member. Therefore, this list is not independent Members should be interpreted as being in fact equivalent to any other member of the same list, but only based on their presence in the shared group, without the need to indicate the opposite. Furthermore, various embodiments and examples of the invention may be referred to herein by reference to the various alternatives. It should be understood that the examples, examples, and alternatives are not to be construed as equivalent to each other, but are considered to be separate and independent.

Further, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the foregoing description, numerous specific details have been set forth, such as examples of search space examples, to provide a thorough understanding of some embodiments. It will be appreciated by those skilled in the art that the embodiments may be practiced without the specific details or other methods, components, materials, etc.. In other instances, well-known structures, materials, or operations are not shown or described further to avoid obscuring aspects of the various embodiments.

Although the previous examples are illustrative of the principles used in the various embodiments in various specific applications, various modifications in form and usage and implementation details may be made without progress for those skilled in the art. Make obvious modifications under labor without departing from the principles and concepts of the examples. Accordingly, the present invention should not be limited, except as claimed in the appended claims.

Although the methods of Figures 3-5 are shown as including a sequence of programs, the methods in some embodiments may perform the illustrated programs in a different order.

Although certain features of the present invention have been described with reference to the embodiments The levy, but the narrative is not intended to be construed in a limiting sense. It is apparent to those skilled in the art that the present invention is to be construed as being within the spirit and scope of the present disclosure.

Claims (25)

A flow offloading function (TOF) device, comprising: a memory that stores one or more instructions; and a processor that executes the one or more instructions in the memory for: detecting and coming from a destination address of a traffic associated with a user equipment (UE) of a base station, and determining whether to offload the traffic from the first base station to the first server or the second server based on the destination address; in response to determining The destination address of the traffic destined to the first server, the traffic is provided to the first server; and the traffic is provided in response to determining that the traffic not destined to the first server satisfies a local distribution policy To the second server. The device of claim 1, wherein the processor is further configured to: perform a network address translation (NAT), and translate the source address of the traffic transmitted to the second server into the The global IP address of the TOF entity. The device of claim 1, wherein the processor is further configured to: encapsulate the one or more IP packets of the traffic in response to determining that the one or more IP packets do not conform to the local distribution policy Used for one of the server gateways (SGW) or multiple general packet radio services (GPRS) tunnels Road Protocol User Plane (GTP-U) packet. The device of claim 1, wherein the processor is further configured to: decapsulate the traffic into one or more IP packets, wherein the traffic includes a domain name system request associated with the UE; The one or more IP packets corresponding to the DNS request are provided to a Domain Name System (DNS) agent in the device. The device of claim 4, wherein the processor is further configured to: translate the source IP address of the DNS request extracted by the DNS proxy into a global IP address of the device; send the DNS request to a second server including a DNS server; and responsive to the DNS request, providing a DNS response from the second server to the first base station, wherein the DNS response indication includes the first server of the application server The IP address is to provide the service requested in the DNS request. The device of claim 1, wherein the processor is further configured to: establish, between the TOF entity and the second TOF entity, in response to initiation of the handover from the second TOF entity to the TOF entity TOF inter-tunnel Road. The device of claim 6, wherein the processor is further configured to: based on one of a handover request associated with the handover from the first base station to the second base station in communication with the UE Or the plurality of information elements, the inter-TOF tunnel is established, wherein the one or more information elements include background information from the second TOF entity, an IP address of the second TOF entity, and the tunnel for the TOF One or more of the group number, the group of IP addresses of the UE. The device of claim 7, wherein the processor is further configured to: in response to receiving a dialog migration request from the second base station, provide a dialog relay request to the second TOF entity; and based on the The dialog of the second TOF entity relays the request confirmation to establish the tunnel between the TOFs. The device of claim 7, wherein the processor is further configured to: receive a dialog migration request from the second base station, wherein the dialog migration request includes the one or more information elements. The device of claim 7, wherein the processor is more Used to: in response to the processor determining that one or more of a source address, a source number, and a protocol number in the traffic are associated with the TOF tunnel, providing an association with the UE via the TOF tunnel The flow is to the second TOF entity. The device of claim 7, wherein the processor is further configured to: in response to receiving a dialog relay termination request from the second TOF entity, providing a dialog relay termination request acknowledgement for responding to the TOF The inactivity of the traffic in the inter-channel is removed by the second TOF entity. A Domain Name System (DNS), comprising: a receiver that receives a DNS request associated with a User Equipment (UE) from a Traffic Offload Function (TOF) entity, wherein the DNS request includes a global IP corresponding to the TOF entity a source address of the address; a memory that stores a mapping table between the global IP address of the TOF entity and an IP address of the first application server (AS); the processor responsive to determining the DNS request The service requested in the first AS is available, the mapping table is retrieved to obtain the IP address of the first AS; and the transmitter transmits the IP address of the first AS in the DNS response to the TOF entity. The DNS of claim 12, wherein the processor is further configured to: update the service in response to determining that the service requested by the DNS request is unavailable in the first AS and available in the second AS Mapping the table to include a mapping between the global IP address of the TOF entity and the IP address of the second AS. The DNS of claim 12, wherein the processor is further configured to: retrieve the mapping table to obtain the IP address of the second AS. The DNS of claim 12, wherein the processor is further configured to: in response to the processor determining that the service requested by the DNS request is available in the second AS, providing a DNS response to the TOF entity The IP address of the second AS is included. The DNS as claimed in claim 12, wherein the second AS comprises a zone AS in contrast to the TOF entity or an external AS outside the regional network of the TOF entity. A user equipment (UE) includes: a transceiver that transmits to a first base station a service phase for the UE An associated Domain Name System (DNS) request, and receiving a DNS response from the first base station to indicate an Internet Protocol for providing a first application server (AS) for the service of the UE ( An IP) address; and a controller coupled to the transceiver, wherein the controller initiates a service session with the first AS based on the IP address of the first AS. The user equipment of claim 17, wherein the controller is further configured to: in response to the transceiver receiving the DNS response including the IP address of the second AS from the first base station, starting and A service session of the second AS, wherein the second AS provides the service for the UE in response to the service for the UE being unavailable at the first AS. The user equipment of claim 17, wherein the controller is further configured to: initiate communication with the second base station in response to the handover from the first base station to the second base station. The user equipment of claim 17, wherein the controller is further configured to: initiate, with the second TOF entity, in response to the handover from the first traffic offload function (TOF) entity to the second TOF entity Communication, via the TOF tunnel between the first TOF entity and the second TOF entity A TOF entity communication. A base station device comprising: a memory for containing one or more instructions; and a controller for executing the one or more instructions to transform a domain name system from a user equipment (UE) ( The first User Datagram Protocol (UDP) packet of the DNS request is a first General Packet Radio Service (GPRS) Tunneling Agreement User Plane (GTP-U) packet; the first GTP-U packet is provided to the first traffic offload A function (TOF) entity; and a second GTP-U packet from the TOF entity that receives a DNS response containing an Internet Protocol (IP) address of the application server (AS). The device of claim 21, wherein the processor is further configured to: in response to the controller transforming the second GTP-U packet into a second UDP packet, providing the second UDP packet to the UE. The device of claim 21, wherein the processor is further configured to: in response to the handover from the first TOF entity to the second TOF entity, providing a dialog migration request to the second TOF, wherein the conversation The migration request includes one or more information elements in the group, the group includes background information of the second TOF entity, an IP address of the second TOF entity, the UI number for the inter-TOF tunnel, the UE IP address. The device of claim 23, wherein the processor is further configured to: receive a dialog migration request confirmation from the second TOF entity. The device of claim 21, further comprising: a transceiver coupled to the processor; and one or more antennas coupled to the processor.