WO2017177381A1 - Solution de branchement local dans un réseau cellulaire - Google Patents

Solution de branchement local dans un réseau cellulaire Download PDF

Info

Publication number
WO2017177381A1
WO2017177381A1 PCT/CN2016/079086 CN2016079086W WO2017177381A1 WO 2017177381 A1 WO2017177381 A1 WO 2017177381A1 CN 2016079086 W CN2016079086 W CN 2016079086W WO 2017177381 A1 WO2017177381 A1 WO 2017177381A1
Authority
WO
WIPO (PCT)
Prior art keywords
tof
dns
address
response
request
Prior art date
Application number
PCT/CN2016/079086
Other languages
English (en)
Inventor
Yifan Yu
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Priority to CN201680083723.XA priority Critical patent/CN109076415B/zh
Priority to PCT/CN2016/079086 priority patent/WO2017177381A1/fr
Priority to TW106107249A priority patent/TWI728062B/zh
Publication of WO2017177381A1 publication Critical patent/WO2017177381A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents

Definitions

  • Wireless mobile communication technology uses various standards and protocols to provide telecommunication services to fixed or mobile subscribers, e.g., a base station and a wireless mobile device.
  • a base station may be an evolved Node Bs (eNode Bs or eNBs) that may communicate with the wireless mobile device, known as a user equipment (UE) .
  • eNode Bs or eNBs evolved Node Bs
  • UE user equipment
  • Figure 1 schematically illustrates a block diagram of an example of a wireless network in accordance with various embodiments
  • Figure 2 schematically illustrates a block diagram of an example of a wireless network in accordance with various embodiments
  • Figure 3 schematically illustrates a flow chart of an example of one or more processes in accordance with various embodiments
  • FIG. 4 schematically illustrates an example of one or more processes in accordance with various embodiments
  • FIG. 5 schematically illustrates an example of one or more processes in accordance with various embodiments
  • Figure 6 schematically illustrates an example of a handover request message in accordance with various embodiments
  • Figure 7 schematically illustrates a block diagram of an example of an electronic device circuitry in accordance with various embodiments
  • Figure 8 schematically illustrates a block diagram of an example of a system in accordance with various embodiments
  • Figure 9 schematically illustrates a block diagram of an example of a system in accordance with various embodiments.
  • Figure 10 schematically illustrates a block diagram of an example of a system in accordance with various embodiments.
  • Embodiments of the disclosure may be implemented in hardware, firmware, software, or any combination thereof. Embodiments of the disclosure may also be implemented as instructions stored on a machine-readable medium, which may be read and executed by one or more processors.
  • a machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computing device, a mobile device, a smartphone, etc. ) .
  • a non-transitory machine-readable medium may include read only memory (ROM) ; random access memory (RAM) ; magnetic disk storage media; optical storage media; flash memory devices.
  • a transitory machine-readable medium may include electrical, optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc. ) , and others.
  • module and/or “unit” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC) , an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • radio systems may include, but are not limited to, network interface cards (NICs) , network adaptors, fixed or mobile client devices, relays, base stations, femtocells, gateways, bridges, hubs, routers, access points, or other network devices.
  • NICs network interface cards
  • network adaptors fixed or mobile client devices
  • relays base stations
  • femtocells gateways
  • bridges hubs
  • routers access points, or other network devices.
  • radio systems within the scope of the disclosure may be implemented in cellular radiotelephone systems, satellite systems, two-way radio systems as well as computing devices including such radio systems, e.g., personal computers, tablets and related peripherals, personal digital assistants, personal computing accessories, hand-held communication devices and all systems which may be related in nature and to which the principles of the inventive embodiments could be suitably applied.
  • computing devices including such radio systems, e.g., personal computers, tablets and related peripherals, personal digital assistants, personal computing accessories, hand-held communication devices and all systems which may be related in nature and to which the principles of the inventive embodiments could be suitably applied.
  • a transmission station may comprise a combination of an evolved universal terrestrial radio access network (E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs) , which may communicate with a wireless mobile device, known as a user equipment (UE) .
  • E-UTRAN evolved universal terrestrial radio access network
  • Node Bs also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs
  • a downlink transmission may comprise a communication from the transmission station (or eNodeB) to the wireless mobile device (or UE)
  • an uplink transmission may comprise a communication from the wireless mobile device to the transmission station.
  • Some embodiments may be used in conjunction with various devices and/or systems, for example, a UE, a mobile device, a mobile wireless device, a mobile communication device, a wireless station, a mobile station, a personal computer, a desktop computer, a mobile computer, a laptop computer, a netbook computer, a notebook computer, a tablet computer, a smartphone device, a mobile phone, a cellular phone, a server computer, a handheld computer, a handheld mobile device, a personal digital assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP) , a wireless node, a base station (BS) , a wired or wireless router, a wired or wireless modem, a video device, an
  • wireless communication network 100 may comprise a base station 110, e.g., an evolved Node B (eNB) , that may communicate with a mobile wireless device, e.g., UE 120.
  • eNB 110 may be a fixed station (e.g., a fixed node) or a mobile station/node.
  • the network 100 may comprise an access network of an access network of a 3GPP LTE network such as E-UTRAN, 3GPP LTE-A network, 4G network, 4.5G network, a 5G network, a 6G network or any other future communication network, a WiMax cellular network, HSPA, Bluetooth, WiFi or other type of wireless access networks or any other future standards.
  • a 3GPP LTE network such as E-UTRAN, 3GPP LTE-A network, 4G network, 4.5G network, a 5G network, a 6G network or any other future communication network, a WiMax cellular network, HSPA, Bluetooth, WiFi or other type of wireless access networks or any other future standards.
  • eNB 110 and/or UE 120 may support multiple-input and multiple-output (MIMO) communication with each other.
  • eNB 110 and/or UE 120 may comprise one or more antennas to utilize one or more radio resources of the wireless communication network 100.
  • eNB 110 and/or UE 120 may each comprise a set of one or more antennas to implement a multiple-input-multiple-output (MIMO) transmission/reception system.
  • MIMO multiple-input-multiple-output
  • the MIMO transmission/reception system may operate in a variety of MIMO modes, including single-user MIMO (SU-MIMO) , multi-user MIMO (MU-MIMO) , close loop MIMO, open loop MIMO, full-dimension MIMO (FD-MIMO) or variations of smart antenna processing.
  • SU-MIMO single-user MIMO
  • MU-MIMO multi-user MIMO
  • close loop MIMO open loop MIMO
  • full-dimension MIMO FD-MIMO
  • smart antenna processing eNB 110 may comprise one or more antennas 118 while UE 120 may comprise one or more antennas 128.
  • eNB 110 may include a controller 114.
  • the controller 114 may be coupled with a transmitter 112 and a receiver 116 and/or one or more communications modules or units in eNB 110.
  • the transmitter 112 and/or the receiver 116 may be elements or modules of a transceiver.
  • the transmitter 112 and/or the receiver 116 may be coupled with the one or more antennas 118 to communicate with UE 120.
  • UE 120 may comprise a transmitter 122 and a receiver 126 and/or one or more communications modules or units.
  • the transmitter 122 and/or the receiver 126 may communicate with a base station (BS) , e.g., eNB 110 or other type of wireless access point such as wide area network (WWAN) via one or more antennas 128 of the UE 120.
  • BS base station
  • WWAN wide area network
  • eNB 110 may comprise other hardware, software and/or firmware components, e.g., a memory, a storage, an input module, an output module, one or more radio modules and/or one or more digital modules, and/or other components.
  • Transmitter 112 may be configured to transmit signals to UE 120 via one or more antennas 118.
  • Receiver 116 may be configured to receive signals from UE 120 via one or more antennas 118.
  • the transmitter 112 and/or the receiver 116 may be elements or modules of a transceiver circuitry.
  • controller 114 may control one or more functionalities of eNB 110 and/or control one or more communications performed by eNB 110.
  • controller 114 may execute instructions of software and/or firmware, e.g., of an operating system (OS) of eNB 110 and/or of one or more applications.
  • Controller 114 may comprise or may be implemented using suitable circuitry, e.g., controller circuitry, configuration circuitry, baseband circuitry, scheduler circuitry, processor circuitry, memory circuitry, and/or any other circuitry, which may be configured to perform at least part of the functionality of controller 114.
  • one or more functionalities of controller 114 may be implemented by logic, which may be executed by a machine and/or one or more processors.
  • 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 standard, and/or other wireless standards or future wireless standards.
  • UE 120 may communicate via separate antenna (s) for each wireless communication standard or shared antenna (s) for multiple wireless communication standards.
  • UE 120 may communicate in a wireless local area network (WLAN) , a wireless personal area network (WPAN) , and/or a wireless wide area network (WWAN) or other network.
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • WWAN wireless wide area network
  • UE 120 may comprise a controller 124, a transmitter 122, a receiver 124 and one or more antennas 128.
  • UE 120 may comprise other hardware components, software components and/or firmware components, e.g., a memory, a storage, an input unit, an output unit and/or any other components.
  • Transmitter 122 may transmit signals to eNB 110 via one or more antennas 128.
  • Receiver 124 may receive signals from eNB 110 via one or more antennas 128.
  • the transmitter 122 and/or the receiver 126 may be elements or modules of a transceiver.
  • controller 124 may be coupled to receiver 124 and transmitter 122. In some embodiments, controller 124 may control one or more functionalities 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, e.g., of an operating system (OS) of UE 120 and/or of one or more applications. Controller 124 may comprise or may be implemented using suitable circuitry, e.g., controller circuitry, scheduler circuitry, processor circuitry, memory circuitry, and/or any other circuitry, which may be configured to perform at least part of the functionality of controller 12. In some embodiments, one or more functionalities of controller 124 may be implemented by logic, which may be executed by a machine and/or one or more processors.
  • OS operating system
  • controller 124 may comprise a central processing unit (CPU) , a digital signal processor (DSP) , a graphic processing unit (GPU) , one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, circuitry, a baseband circuitry, a configuration circuitry, a radio frequency (RF) circuitry, a logic unit, an integrated circuit (IC) , an application-specific IC (ASIC) , or any other suitable multi-purpose or specific processor or controller and/or any combination thereof.
  • CPU central processing unit
  • DSP digital signal processor
  • GPU graphic processing unit
  • Transmitter 112 may comprise, or may be coupled with one or more antennas 118 of eNB 110 to communicate wirelessly with other components of the wireless communication network 100, e.g., UE 120.
  • Transmitter 122 may comprise, or may be coupled with one or more antennas 128 of UE 120 to communicate wirelessly with other components of the wireless communication network 100, e.g., eNB 110.
  • transmitter 112 and/or transmitter 122 may each comprise one or more transmitters, one or more receivers, one or more transmitters, one or more receivers and/or one or more transceivers that may send and/or receive wireless communication signals, radio frequency (RF) signals, frames, blocks, transmission streams, packets, messages, data items, data, information and/or any other signals.
  • RF radio frequency
  • the antennas 118 and/or the antennas 128 may comprise any type of antennas suitable to transmit and/or receive wireless communication signals, RF signals, blocks, frames, transmission streams, packets, messages, data items and/or data.
  • the antennas 118 and/or the antennas 128 may comprise any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays.
  • the antennas 118 and/or the antennas 128 may implement transmit and/or receive functionalities using separate transmit and/or receive antenna elements.
  • the antennas 118 and/or the antennas 128 may implement transmit and/or receive functionalities using common and/or integrated transmit/receive elements.
  • the antenna may comprise, for example, a phased array antenna, a single element antenna, a dipole antenna, a set of switched beam antennas, and/or the like.
  • Fig. 1 illustrates some components of eNB 110
  • the eNB 110 may optionally comprise other suitable hardware, software and/or firmware components that may be interconnected or operably associated with one or more components in the eNB 110.
  • Fig. 1 illustrates some components of UE 120
  • UE 120 may comprise other suitable hardware, software and/or firmware components that may be interconnected or operably associated with one or more components in UE 120.
  • eNB 110 and/or UE 120 may comprise one or more radio modules (not shown) to modulate and/or demodulate signals transmitted or received on an air interface, and one or more digital modules (not shown) to process signals transmitted and received on the air interface.
  • eNB 110 and/or UE 120 may comprise one or more input units (not shown) and/or one or more output units (not shown) .
  • one or more input units may comprise a keyboard, a keypad, a mouse, a touch-screen, a touch-pad, a track-ball, a stylus, a microphone, or any other pointing/input unit or device.
  • one or more output units may comprise 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 earphones, or any other output unit or device.
  • CTR Cathode Ray Tube
  • LCD Liquid Crystal Display
  • UE 120 may comprise, for example, a mobile computer, a mobile device, a station, a laptop computing device, a notebook computing device, a netbook, a tablet computing device, an Ultrabook TM computing device, a handheld computing device, a handheld device, a storage device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities) , a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a mobile phone, a cellular telephone, a PCS device, a mobile or portable GPS device, a DVB device, a wearable device, a relatively small computing device, a non-desktop computer, a “carry small live large” (CSLL) device, an ultra mobile device (UMD) , an ultra mobile PC (UMPC) , a mobile internet device (MID) , an “O”
  • eNB 110 and/or UE 120 may each comprise one or more radio modules or units (not shown) that may modulate and/or demodulate signals transmitted or received on an air interface, and/or one or more digital modules or units (not shown) that may process signals transmitted and received on the air interface.
  • Figure 2 schematically illustrates a block diagram of an example of a wireless communication network 200 in accordance with some embodiments.
  • the wireless communication network 200 may comprise one or more wireless communication devices that may communicate content, data, information and/or signals via one or more wireless mediums, for example, a radio channel, a cellular channel, an RF channel, a Wireless Fidelity (WiFi) channel, an infrared radio (IR) channel, and the like, e.g., as described below.
  • a radio channel for example, a radio channel, a cellular channel, an RF channel, a Wireless Fidelity (WiFi) channel, an infrared radio (IR) channel, and the like, e.g., as described below.
  • WiFi Wireless Fidelity
  • IR infrared radio
  • wireless communication network 200 may comprise a user equipment (UE) 202 that may communicate with an eNB 104, e.g., via a Uu interface or any other suitable interface.
  • UE user equipment
  • the wireless communication network 200 may comprise a packet data network (PDN) gateway (PGW) 208.
  • PGW 208 may communicate with SGW 206, e.g., via a S5 interface or any other suitable interface.
  • the PGW 208 may be associated with an Access Point Name (APN) .
  • UE 202 may utilize the APN of PGW 208 to facilitate a connection to an external network via the PGW 208.
  • the PGW 208 may communicate with a service Local Area Network (LAN) server 220 via a SGi interface or any other interface.
  • LAN Local Area Network
  • the wireless communication network 200 may comprise a traffic offload function (TOF) 212 that may be provided between eNB 204 and a serving gateway (SGW) 206, e.g., over an S1-u interface or any other suitable interface.
  • TOF 212 may be implemented in an entity, an apparatus, a device, a system, a circuitry, a module, a unit, and/or any other structure using any suitably configured hardware, software and/or firmware.
  • TOF 212 may be configured to perform one or more processes and/or functions as described in the disclosure.
  • TOF 212 may be used in one or more of a 3G network, a LTE network, a 5G network and/or any other existing or future wireless communication network and/or European Telecommunication Standards Institute (ETSI) mobile edge computing (MEC) .
  • ETSI European Telecommunication Standards Institute
  • TOF 212 may be collocated with eNB 204.
  • TOF 212 and the eNB 204 may be in a same physical device or system, e.g., in the same server, entity, system, etc.
  • TOF 212 and eNB 204 may be physically located together.
  • TOF 212 may be outside of eNB 204.
  • TOF 212 may be reside between eNB 204 and SGW 206 over, e.g., a S1-U interface.
  • the network 200 may comprise one or more local network 210 that may each comprise a TOF 212 and/or one or more local application servers (ASs) 214 and/or any other service servers.
  • a local AS 214 collocated with TOF 212 may provide a service, e.g., for UE 202 at a network edge.
  • an access to Internet 230 may be allowed within TOF 212.
  • local AS 214 and TOF 212 may be in the same physical device, e.g., in the same server, entity, system, etc.
  • local AS 214 and TOF 212 may be physically located together, e.g., in the local network 210.
  • the network may comprise one or more non-local or external ASs 216 that may not be collocated with the TOF 212.
  • the external AS 216 may be outside TOF 212.
  • the external AS 216 may be outside of the local network 210 where TOF 212 is located.
  • the external AS 216 may comprise a server in Internet 230, e.g., DNS server 232.
  • the wireless network 200 may comprise one or more local networks 210 that may each comprise a TOF 212 and/or one or more local ASs 214.
  • the wireless network 200 may comprise one or more external ASs 216 that may be outside of any local network 210.
  • a TOF 212 in a local network 210 may communicate with one or more external ASs 216 via a SGi interface or any other suitable interface.
  • local AS 214 may be configured to communicate with TOF 212, e.g., via a SGi interface or any other suitable interface.
  • local AS 214 may be configured to create a direct connection to TOF 212, e.g., via the SGi interface.
  • TOF 212 may be configured to allow access to Internet 230 within TOF 212, e.g., via a DNS proxy 824 of Figure 8, through a SGi interface or any other suitable interface.
  • a local AS 214 may be coupled to network 200 and/or UE 202 through TOF 212 without network address translation.
  • a local AS 214 may be used as a DNS proxy.
  • TOF 212 may be configured to enable a local breakout with a local breakout policy that may be configured at a network side, e.g., TOF 212, without informing UE 202.
  • TOF 212 may be configured to enable a local breakout to support service continuity across diverse breakout points, e.g., one or more TOFs 212.
  • TOF 212 may not always activate NAT functionality in traffic offloading.
  • the local AS 214 may deliver the application to UE 202 without activating NAT functionality of TOF 212 to reduce system resource waste.
  • an application may comprise one or more services for a UE, e.g., 202.
  • examples of one or more services may comprise file downloading, video streaming and/or any other service (s) that may be requested by a UE based on an application.
  • TOF 212 may be configured to offload a traffic, e.g., one or more packets, from UE 202 to the local AS 214, e.g., locally, without activating a network address translation (NAT) functionality if the traffic is destined to the local AS 214.
  • a traffic e.g., one or more packets
  • NAT network address translation
  • TOF 212 may check a destination address of the traffic, e.g., one or more packets, that may be received from UE 202 via eNB 204. In some embodiments, TOF 212 may decapsulate the traffic that may be encapsulated in one or more GTP-U packets in eNB 204 to obtain one or more IP packets. In some embodiments, an IP packet may have a source IP address to represent a source node that may send the IP packet and a destination IP address to indicate a target or destination node, to which the IP packet may be destined.
  • TOF 212 may disable or turn off NAT functionality for the traffic or one or more packets of the traffic in response to determining that the packet is destined to a local AS 214. In some embodiments, TOF 212 may offload the traffic to the local AS 214 without activating NAT functionality to reduce a system resource waste.
  • TOF 212 may enable NAT functionality in response to determining that the traffic from UE 202 may not destined to the local AS 214 but may meet with a local breakout policy.
  • TOF 204 may offload the traffic to Internet 230 and/or DNS server 232 in response to completing the NAT functionality on the traffic.
  • UE 202 may not always perform an APN selection for a local breakout to reduce network operation and service maintenance.
  • eNB 204 may not always inform UE 202 of a service deployment in the network 200.
  • UE 202 may not always have knowledge whether a service requested by UE 202 is available in the network 200 associated with a current eNB 204 for an APN selection.
  • an inter-TOF point tunnel may be established to enable a handover across different TOF points in response to a handover, e.g., an X2 handover, across different eNBs.
  • a handover procedure may be utilized to keep a service continuity across various traffic offload points, e.g., one or more TOFs/TOF points, for one or more services requested by UE 202, e.g., file downloading, video streaming and/or any other service (s) .
  • a source TOF 212s and/or a target TOF 212t may be configured to provide the inter-TOF point tunnel.
  • a target eNB e.g., 204t, to which UE 202 is to handover, may be configured to issue a handover request message in response to initiation of an X2 handover.
  • the handover request message may comprise one or more information elements that may be used for the tunnel establishment.
  • an inter-breakout point tunnel e.g., inter-TOF point tunnel, may be established based on the handover request message to support mobility and/or service continuity across the different breakout points.
  • network 200 may be configured to enable a local breakout with mobility supporting.
  • network 200 may be configured to allow a change of service presence point (s) , e.g., a local AS 214 and/or an external AS 216 and/or other service server, without informing one or more UEs in the network 200.
  • a change of service presence point e.g., a local AS 214 and/or an external AS 216 and/or other service server
  • flexibility may be provided to a service deployment for the one or more UEs in the network 200.
  • a domain name system (DNS) query procedure may be utilized to reduce complexity in network and/or service operation.
  • DNS domain name system
  • a DNS proxy in TOF 212 may be configured to query the DNS server 232, e.g., by a DNS request, on behalf of a terminal that may issue the DNS request, e.g., UE 202.
  • UE 202 may be configured to utilize a DNS query or request to acquire Internet Protocol (IP) address of one or more service servers, e.g., one or more local ASs 214 or one or more external ASs 216, prior to a service acquisition.
  • DNS server 232 may be configured to respond to the DNS request with a DNS response that may comprise IP address of one or more ASs or other service servers that may provide one or more services requested by UE 202 in the DNS request.
  • UE 202 may be configured to communicate with or establish one or more service sessions with the one or more ASs or other service servers via TOF 212 and/or eNB 204 in response to having knowledge of the IP address of the one or more ASs or other service servers, in which the one or more services requested in the DNS query by UE 202 are deployed.
  • TOF 212 may be configured to transfer a traffic from one or more of the ASs and/or the other service servers to UE 202 via eNB 204 and/or a traffic received from UE 202 via eNB 204 to one or more of the ASs or the other service servers.
  • TOF 212 may comprise a DNS proxy, e.g., 824 of Figure 8 or a local AS, for a terminal, e.g., UE 202, that may issue the DNS query or request, e.g., originally.
  • UE 202 may encapsulate the DNS request in one or more user datagram protocol (UDP) packets with a destination port number of 53.
  • UDP user datagram protocol
  • the destination port number of 53 may be used to indicate that a traffic with the destination port number of 53 is a DNS request.
  • eNB 204 may be configured to encapsulate the one or more UDP packets carrying the DNS request as one or more general packet radio service (GPRS) tunneling protocol user plane (GTP-U) packets and/or may transmit the one or more GTP-U packets to TOF 212.
  • GPRS general packet radio service
  • GTP-U tunneling protocol user plane
  • TOF 212 in response to receiving the DNS request, e.g., in one or more GTP-U packets, from eNB 204, TOF 212 may be configured to transform or decapsulate the one or more GTP-U packets as one or more Internet Protocol (IP) packets. In some embodiment, TOF 212 may determine if the one or more IP packets with the DNS request from eNB 204 have a destination address destined to a local AS 214.
  • IP Internet Protocol
  • the destination address of the one or more IP packets may not be destined to a local AS 214.
  • TOF 212 may be configured to further determine if the one or more IP packets meet with a local breakout policy. For example, based on a local breakout policy associated with a DNS request, TOF 212 may determine if the one or more IP packets comprise one or more UDP packets with a destination port number of 53.
  • TOF 212 may be configured to offload the one or more IP packets to a DNS proxy, e.g., 824 of Figure 8.
  • a DNS proxy e.g. 824 of Figure 8.
  • a local AS 214 may be used as a DNS proxy that may preform one or more operations of the DNS proxy 824.
  • DNS proxy 824 may extract the DNS request from the one or more UPD packets encapsulated in the one or more IP packets from TOF 212. In some embodiments, DNS proxy 824 may encapsulate the extracted DNS request in one or more UDP packets and/or may forward to TOF 212 the one or more UDP packets that may be encapsulated in one or more IP packets.
  • TOF 212 may be configured to activate a NAT on the one or more IP packets from DNS proxy 824 to be forwarded to DNS server 232. In some embodiments, TOF 212 may perform a NAT on the one or more IP packets to translate a source IP address of the one or more IP packets as a global IP address of TOF 212 where the DNS proxy 824 may reside. In some embodiments, TOF 212 may be configured to translate a source address, e.g., a private address, of the one or more IP packets into a global IP address of TOF 212 based on the NAT. In some embodiments, TOF 212 may be configured to offload to Internet 230 and/or DNS server 232 the one or more IP packets after NAT that may comprise the one or more UDP packets carrying the DNS request.
  • DNS server 232 may receive from TOF 212 the one or more IP packets that may each have a source IP address set as the global IP address of the TOF 212.
  • the one or more IP packets from TOF 212 may comprise the one or more UDP packets carrying the DNS request.
  • an administrator of DNS server 232 may be aware of IP address of one or more service servers that may be deployed with the corresponding service to serve one or more requests by UE 202.
  • the one or more service servers may comprise one or more local ASs 214 that may be deployed with the service of UE 202 and/or one or more external ASs 216 that may be deployed with the service of UE 202.
  • the administrator of DNS server 232 may generate in the DNS server 232 a mapping between a global IP address of TOF 212 and IP address of the one or more local ASs 214 and/or the one or more external ASs 216.
  • the DNS server 232 may maintain the mapping in a database or in other data structure in a memory of DNS server 232. In some embodiments, the mapping may be associated with the service deployment of UE 202. In some embodiments, DNS server 232 may maintain one or more mappings, e.g., if one or more ASs for a service are used in the local network 210. In some embodiments, a number of ASs that may be used for a service may depend on a service deployment of a service provider. In some embodiments, one more local ASs and/or one more external ASs may be serve the same service. In some embodiments, the one or more mappings may be associated with an initial service deployment relating to the service setup.
  • DNS server 232 may be configured to maintain one or more DNS records or information in a database or in other data structure in the memory of DNS server 232.
  • examples of one or more DNS records may comprise a set of one or more domain names, and/or a list of IP address of one or more local ASs and/or one or more external ASs in the one or more mappings, that may respond to a visit to one or more of the domain names, and/or the mapping between the global IP address of TOF 212 and the IP address of the local AS (s) 214 or the external AS (s) 216.
  • the one or more domain names may relate to one or more websites that may be deployed in the local AS (s) 214 or the external AS (s) 216 in the one or more mappings.
  • DNS server 214 may determine from which TOF 212 a DNS request is received, e.g., based on the set of one or more domain names and/or the list of IP address of the one or more ASs in the one or more mappings.
  • DNS server 232 may check which local AS (s) 214 and/or external AS (s) 216 in the one or more mappings associated with TOF 212 may provide one or more services of UE 202 requested in the DNS request.
  • DNS server 232 may determine which local AS (s) 214 and/or external AS (s) 216 in the one or more mappings may be able to provide the service (s) requested by UE 202 or in which local AS (s) 214 or external AS (s) 216 the service (s) requested by UE 202 may be deployed.
  • DNS server 232 may retrieve the mapping to obtain IP address of the one or more local ASs 214 and/or respond to the DNS request with the retrieved IP address of the one or more local ASs 214.
  • the administrator of DNS server 232 may be aware of IP address of the one or more new local ASs 214 and/or new external ASs 216 and/or may update the one or more mappings based on the new service deployment and/or the one or more services in the service deployment.
  • the administrator of the DNS server 232 may update the mapping, e.g., manually, to include the IP address of the one or more new local ASs 214 and/or external AS 216 and/or update the one or more mappings with one or more new mappings between the global IP address of TOF 212 and the IP address of the one or more new local ASs and/or new external ASs 216.
  • the administrator of DNS server 232 may add one or more new mappings based on the new service deployment and/or remove one or more previous mappings that may correspond to a previous service deployment but not the new service deployment.
  • DNS server 232 may check and/or select the IP address of the one or more new local ASs 214 and/or new external ASs 216 in the updated mapping (s) to respond to the DNS request and may transmit to TOF 214 a DNS response that may comprise the selected IP address of the one or more new ASs for the one or more requested services in the DNS request.
  • DNS server 232 may check in which external AS (s) 216 in one or more mappings the requested service (s) may be deployed in response to determining that the requested service (s) is unavailable in any local AS 214 in the local network 210, e.g., in the one or more mappings or not in the one or more mappings.
  • DNS server 232 may check availability of the requested service (s) in external AS (s) 216 in the one or more mappings. In response to determining that the requested service (s) is deployed in one or more external ASs 216 in the one or more mappings, DNS server 232 may retrieve the one or more mappings to obtain IP address of the one or more external ASs 216 that are able to provide the requested service (s) for UE 202 and/or reply to the DNS request with a DNS response that may comprise the obtained IP address of the one or more external ASs 216.
  • DNS server 232 may send to TOF 212 the DNS response that may comprise IP address of one or more ASs that UE 202 may couple to for the requested service (s) .
  • DNS server 232 may send to TOF 212 a DNS response to indicate unavailability of any AS for the requested service (s) .
  • DNS server 232 may be configured to allocate one or more services requested by UE 202 among one or more local ASs 214 and/or external ASs 216 in the one or more mappings, e.g., based on an AS load for an AS load balance. For example, DNS server 232 may select one or more local ASs 214 and/or one or more external ASs 216 with smaller loads to provide a requested service. In some embodiments, DNS server 232 may retrieve the database to obtain IP address of the one or more selected local ASs 214 and/or external ASs 216 with the smaller loads in response to an allocation determination and/or transmit to TOF 212 a DNS response to include the retrieved IP address of the local AS 214.
  • the DNS server 232 may update the one or more mappings with one or more new mappings in response to the AS allocation.
  • DNS server 232 may perform AS IP address retrieving, e.g., prior to updating the one or more mappings based on the AS allocation.
  • DNS server 232 may perform AS IP address retrieving in response to updating the one or more mappings with the new one or more mappings.
  • an AS load balance may be applied to local AS (s) 214 and/or may be applied to local AS (s) 214 and/or external AS (s) 216 jointly based on a policy of a service provider.
  • DNS server 232 may store in the memory one or more mappings between the global IP address of TOF 212 and IP address of one or more local ASs 214 and/or external ASs 216 that may provide one or more requested services of UE 202 in a table, an array, a list or any other form.
  • the administrator of DNS server 232 may be configured to update the one or more mappings in the database with one or more new mappings corresponding to a new service deployment for UE 202 and/or an AS allocation, e.g., dynamically.
  • DNS server 232 may store in the memory one or more new or updated mappings associated with a new service deployment and/or an AS allocation in a table, an array, a list or any other form.
  • UE 202 may not be updated in response to an update in the one or more mappings, and/or a service presence point change and/or a service deployment change.
  • DNS server 232 may transmit to TOF 212 the DNS response as one or more UDP packets that may be encapsulated in one or more IP packets. In some embodiments, DNS server 232 may forward to TOF 212 the one or more IP packets that may comprise the one or more UDP packets.
  • TOF 212 in response to receiving the one or more IP packets associated with the DNS response from DNS server 232, TOF 212 may offload the one or more IP packets to DNS proxy 824 in TOF 212.
  • DNS proxy 824 may extract from the one or more IP packets the DNS response carried by one or more UDP packets in the one or more IP packets.
  • the extracted DNS response may comprise, e.g., IP address of one or more ASs to provide service (s) requested in the DNS request.
  • DNS proxy 824 may encapsulate the extracted DNS response as one or more UDP packets with a source port number of 53 and/or a destination address to UE 202.
  • DNS proxy 824 may forward to TOF 212 the extracted DNS response as the one or more UDP packets with source port number of 53 that may be encapsulated in one or more IP packets. In some embodiments, DNS proxy 824 may encapsulate the one or more UDP packets as the one or more IP packets to be sent to TOF 212.
  • 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 the cached DNS responses to respond to one or more subsequent DNS requests. In some embodiments, DNS proxy 824 may forward to TOF 212 a retrieved DNS response as the one or more UDP packets with a source port of 53 that may be encapsulated in the one or more IP packets.
  • TOF 212 in response to receiving from DNS proxy 824 the one or more IP packets that comprise the one or more UDP packets carrying the extracted DNS response or the retrieved DNS response, may encapsulate the one or more IP packets as one or more GTP-U packets. In some embodiments, TOF 212 may offload the one or more GTP-U packets to eNB 204.
  • eNB 204 may decapsulate the one or more GTP-U packets to recover the one or more UDP packets that may carry the DNS response or the retrieved DNS response and may have the source port of 53. The eNB 204 may forward the one or more UDP packets carrying the DNS response to UE 202. In some embodiments, UE 202 may communicate with one or more ASs via TOF 212 and eNB 204 in response to obtaining the IP address of the one or more ASs that may be extracted from the DNs response in the received UDP packets.
  • 3GPP LTE 3rd Generation Partnership Project
  • some embodiments may be implemented in any other suitable cellular network or system, e.g., a Universal Mobile Telecommunications System (UMTS) cellular system, a GSM network, a 3G cellular network, a 4G cellular network, a 4.5G network, a 5G cellular network, a WiMax cellular network, or any other legacy or future network or system or the like.
  • UMTS Universal Mobile Telecommunications System
  • GSM Global System
  • 3G cellular network 3G cellular network
  • 4G cellular network 4G cellular network
  • 4.5G network 4.5G network
  • 5G cellular network a WiMax cellular network
  • WiMax WiMax cellular network
  • Figure 3 demonstrative illustrates an example of one or more processes in accordance with some embodiments.
  • the one or more processes may be used by a TOF 212 for traffic offloading.
  • the traffic offloading may be activated based on, e.g., subscriber data and/or one or more policies that may be determined by an operator.
  • examples of subscriber data may comprise but not limited to a user profile that may indicate whether a subscriber is a local user or a roaming user and/or other subscriber related information.
  • examples of an operator policy may comprise but not limited to, e.g., one or more UDP packets carrying a DNS query or request may have a destination port number of 53, or one or more UDP packets carrying a DNS response may have a source port number of 53, and/or other policies that may be set by an operator.
  • TOF 212 may perform one or more other operations as described in the disclosure.
  • TOF 212 may receive a traffic associated with a service from UE 202 via eNB 204.
  • eNB 204 may encapsulate the traffic from UE 202 in a general packet radio service (GPRS) tunneling protocol user plane (GTP-U) format and may transfer the traffic to TOF 212.
  • GPRS general packet radio service
  • GTP-U tunneling protocol user plane
  • TOF 212 may decapsulate one or more GTP-U packets in the received traffic to obtain one or more internet protocol (IP) packets.
  • IP internet protocol
  • TOF 212 may determine whether a destination address of one or more obtained IP packets is destined to a local AS 214 in the local network 210. In some embodiments, at 306, in response to determining that the one or more obtained IP packets comprise the destination IP address to a local AS 214 in the local network 210, TOF 212 may offload the traffic, e.g., the one or more IP packets, to the local AS 214.
  • TOF 212 may further determine whether the one or more IP packets meet with a local breakout policy (at 308) .
  • a local breakout policy may comprise one or more rules that may indicate which type of packet (s) may be forwarded to the local network 210, e.g., DNS proxy 824 and/or an inter-TOF tunnel.
  • an IP packet may be offloaded to the local network 210 even if a destination IP address of the packet is not an IP address of any local AS or other local service server in the local network 210.
  • a source TOF 212s and/or a target TOF 212t may transfer a traffic from an AS 214 or a UE 202 via an inter-TOF tunnel.
  • TOF 212 may check if a packet meets with a local breakout policy based on one or more of a type, a destination IP address, a destination port number, a protocol ID, a source IP address, a source port number of a packet and/or one or more fields, e.g., Type of Service, in an IP header of the packet, and/or to determine if the packet is offloadable to the local network 210.
  • a mobile operator may configure one or more local breakout policies.
  • a local breakout policy may comprise one or more other rules associated with traffic offloading.
  • TOF 212 may be configured to offload the one or more IP packets to a DNS proxy, e.g. 824 of Figure 8 or a local AS 214 that may be used as the DNS proxy.
  • the DNS proxy may be transparent to UE 202 that may be unaware of the DNS proxy.
  • the DNS proxy 824 may decapsulate the one or more IP packets to extract the DNS request from the one or more UDP packets encapsulated in the one or more IP packets.
  • the DNS proxy 824 may encapsulate the extracted DNS request as one or more UDP packets with a destination port number of 53 that may be provided to TOF 212 as one or more IP packets.
  • TOF 212 may activate a NAT on the one or more received IP packets to translate source IP address, e.g., a provide address, of the one or more IP packets as a global IP address of TOF 212.
  • TOF 212 may offload the one or more IP packets after NAT to DNS server 232 in Internet 230.
  • TOF 212 may be configured to forward the one or more IP packets with the source IP address translated as the global IP address to DNS server 232 in Internet 230, e.g., on behalf of a terminal that may originally issue the DNS request, e.g., UE 202.
  • TOF 212 may encapsulate the one or more IP packets in a form of one or more GTP-U packets. In some embodiments, at 316, TOF 212 may forward the one or more GTP-U packets to SGW 206.
  • SGW 206 may be configured to establish, e.g., a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) tunnel between SGW 206 and eNB 204 to forward the one or more GTP-U packets to eNB 204 via the GTP tunnel.
  • GTP General Packet Radio Service
  • eNB 204 may forward to UE 202 one or more UDP packets that may each correspond to a GTP-U packet.
  • the GTP tunnel may be established, e.g., based on one or more instructions from, e.g., a Mobility Management Entity (MME) based on, e.g., 3GPP TS 24.301.
  • MME Mobility Management Entity
  • Figure 4 demonstratively illustrates a diagram of processes according to one or more embodiments.
  • one or more operations of Figure 4 may be used to establish a service session between a UE and an AS.
  • UE 202 may use a DNS query or request, e.g., one or more UDP packets with a destination port of 53, to obtain an IP address of an AS, e.g., a local AS 214 or an external AS 216 for a service of UE 202 requested in the DNS request.
  • UE 202 may utilize the obtained IP address of the AS to initiate a service session with the AS, e.g., via a controller 114 of Figure 1 or a baseband circuitry 1020 of Figure 10.
  • one or more operations as described with reference to other figures may be performed.
  • UE 202 may transmit to eNB 204 one or more UDP packets with a destination port of 53 that may carry a DNS request 402.
  • eNB 204 may transform or encapsulate the one or more UDP packets carrying the DNS request 402 as one or more GTP-U packets to generate a DNS request 404 in GTP-U format.
  • the eNB 204 may transmit to TOF 212 the DNS request 404 as one or more UDP packets that may be encapsulated in the one or more GTP-U packets.
  • TOF 212 may receive from eNB 204 the one or more GTP-U packets associated with the DNS request 404.
  • TOF 212 may decapsulate the one or more GTP-U packets that may comprise one or more UDP packets carrying the DNS request 404 as one or more IP packets.
  • TOF 212 may offload the one or more IP packets decapsulated from the GTP-U packets of eNB 204 to a DNS proxy in TOF 212 based on a local breakout policy.
  • the DNS proxy in TOF 212 may comprise, e.g., 824 of Figure 8 or a local AS 214 that may be used as the DNS proxy.
  • DNS proxy 824 may extract the DNS request 404 included in the one or more UDP packets.
  • DNS proxy 824 may encapsulate the extracted DNS request 404 as one or more UDP packets that may be forwarded to TOF 212 as one or more IP packets.
  • TOF 212 may activate a NAT functionality to translate a source IP address of the one or more IP packets into a global IP address of TOF 212 to generate a DNS request after NAT 406.
  • the DNS request after NAT 406 may comprise the one or more IP packets with the source IP address of the one or more IP packets translated as the global IP address of TOF 212 based on the NAT.
  • TOF 212 may offload to the DNS server 232 in the Internet 230 the DNS request after NAT 406 as one or more UDP packets that may be encapsulated in one or more IP packets with source IP address belonging to TOF 212.
  • DNS server 232 may maintain in a database one or more mapping tables or mappings between a global IP address of TOF 212 and IP address of one or more ASs or other service servers, in which one or more services of UE 202 are deployed based on a service deployment of UE 202.
  • a mapping may correspond to a service may be identified with a domain name.
  • DNS server 232 may determine if one or more ASs, e.g., local AS (s) 214 and/or external AS (s) 216, in the one or more mappings, may provide one or more services requested by UE 202 indicated in the DNS request after NAT 406. In some embodiments, in response to determining that the one or more ASs, e.g., local AS (s) 214 and/or external AS (s) 216, can provide one or more services requested by UE 202 indicated in the DNS request after NAT 406, DNS server 232 may select or retrieve IP address of the one or more ASs to respond to the DNS request after NAT 406.
  • ASs e.g., local AS (s) 214 and/or external AS (s) 216
  • DNS server 232 may provide to TOF 212 a DNS response 408 that may comprise the retrieved IP address of the one or more local ASs 214 or one or more external ASs 216 that may provide the one or more requested services.
  • DNS server 232 may transmit to TOF 212 the DNS response 408 as one or more UDP packets that may be encapsulated in one or more IP packets, e.g., via a SGi interface.
  • DNS server 232 may retrieve the mapping table to obtain the IP address of the one or more local ASs 214 and/or the one or more external ASs 216 that may correspond to the global IP address of TOF 212.
  • the DNS server 232 may reply to TOF 212 with the DNS response 408 that may comprise the retrieved IP address of the local AS (s) 214 and/or the external AS (s) 216 in response to the DNS request 406.
  • an administrator of DNS server 232 may update the mapping table in the database to indicate a new mapping corresponding to the global IP address of TOF 212 and IP address of the new local AS (s) 214 and/or new external AS (s) 216, in which the requested service (s) is deployed.
  • DNS server 232 may include the IP address of the new local AS (s) 214 and/or new external AS (s) 216 in the DNS response 408 to reply to the DNS request after NAT 406.
  • DNS server 232 may reply to the DNS request after NAT 406 with the DNS response 408 that may comprise IP address of one or more external ASs 216 in the mapping table or not in the mapping table in response to determining that the requested service (s) is not deployed in any local AS 214 in the mapping table or in the local network 210 but in the one or more external ASs 216.
  • DNS server 232 may reply to the DNS request 406 with a DNS response 408 to indicate no AS is able to provide the requested service in response to determining the unavailability of the requested service in any local AS 214 or any external AS 216.
  • UE 202 may not issue any packets relating to the service.
  • DNS server 232 may transmit to TOF 212 the DNS response 408 as one or more UDP packets that are encapsulated in one or more IP packets.
  • TOF 212 in response to receiving from DNS server 232 the one or more IP packets that comprise one or more UDP packets carrying the DNS response 408, TOF 212 may offload the one or more IP packets to the DNS proxy 824 in TOF 212 or a local AS 214 used as the DNS proxy.
  • DNS proxy 824 in TOF 212 may decapsulate the one or more IP packets from TOF 212 to recover one or more UDP packets carrying the DNS response 408.
  • DNS proxy 824 may extract the DNS response 408 from the one or more UDP packets.
  • DNS proxy 824 may store or cache one or more extracted DNS responses in a memory of the TOF 212.
  • the DNS proxy 824 in TOF 212 may be configured to retrieve or select in the stored DNS responses to obtain a DNS response 408 for a requested service in the DNS request 402 or a subsequent service in a subsequent DNS request from UE 202.
  • DNS proxy 824 may encapsulate the extracted or retrieved DNS response 408 as one or more UDP packets with a source port number of 53 and/or a destination address to UE 202. DNS proxy 824 may transmit to TOF 212 the extracted or retrieved DNS response 408 as the one or more UDP packets that are encapsulated as one or more IP packets to be forwarded to eNB 204.
  • TOF 212 may encapsulate the one or more IP packets as one or more GTP-U packets to obtain a DNS response 410 in GTP-U format. In some embodiments, TOF 212 may offload the one or more GTP-U packets to eNB 204, e.g., through a S1-U interface.
  • eNB 204 may transform, e.g., decapsulate, the one or more GTP-U packets received from TOF 212 to recover the one or more UDP packets encapsulated in the GTP-U packets to provide a DNS response 412 to be delivered to UE 202.
  • the one or more recovered UDP packets with the source port number of 53 may carry the DNS response 412 that may comprise IP address of the local AS (s) 214 and/or the external AS (s) 216 to provide the service requested by the DNS request 202.
  • the DNS response 412 may appear as one or more UDP packets with the source port of 53 in eNB 202.
  • eNB 204 may transmit the DNS response 412 in UDP format to UE 202.
  • eNB 204 may transmit DNS response 412 as the one or more recovered UDP packets to UE 202.
  • UE 202 in response to receiving the DNS response 412 from eNB 204, may obtain, e.g., extract, the IP address of the one or more local ASs 214 and/or the one or more external ASs 216 that may be carried in the DNS response 412. In some embodiments, UE 202 may use an IP address included in the DNS response 412 to establish one or more service sessions 420 with a corresponding AS having the IP address. In some embodiments, UE 202 may communicate with the corresponding AS, e.g., via TOF 214 and/or eNB 204, to perform the one or more service sessions 420 based on the IP address of the corresponding AS.
  • Figure 5 demonstratively illustrates a diagram of one or more processes in accordance with some embodiments.
  • the one or more processes may be used to enable a service connectivity for, e.g., a handover across diverse TOF points.
  • AS 214 and/or AS 216 of Figure 2 or other AS may be used as one or more ASs for a service of UE 202.
  • one or more operations as described in the disclosure may be performed.
  • a source eNB 204s and/or a target eNB 204t may perform one or more functionalities of eNB 204.
  • a source TOF 202s and/or a target TOF 204t may perform one or more functionalities of TOF 204.
  • UE 202 may communicate with the source eNB 204s that may communicate with a service server, e.g., 214 or 216, via the source TOF 212s, prior to a handover from the source eNB 204s to the target eNB 204t,
  • the target eNB 204t to which UE 202 is to handover, may be configured to issue a handover request message in response to initiation of an X2 handover, e.g., from the source eNB 204s to the target eNB 204t.
  • the handover request message 502 may comprise a X2 application protocol (X2AP) handover request associated with the X2 handover.
  • the handover request message 502 may comprise one or more information elements that may enable the handover, e.g., from the source eNB 204s to the target eNB 204t.
  • 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.
  • a handover across different TOFs may be initiated in response to the completion of the handover from the source eNB 204s to the target eNB 204t.
  • the handover request message 502 may further comprise one or more extended information elements, e.g., as described with regard to Figure 6.
  • the one or more extended information elements may be used to enable a handover and/or a session migration, e.g., the source TOF 212s to the target TOF 212t.
  • the target eNB 204t may notify the target TOF 212t of the one or more extended information elements by a session migration request message 504.
  • the session migration request 504 may comprise the one or more extended information elements that may be included in the handover request message 502.
  • the target TOF 212t may transmit a session migration request acknowledgement 506 to the target eNB 204t.
  • the target TOF 212t may establish a tunnel to the source TOF 212s based on the one or more extended information elements that may be delivered with the session migration request 504.
  • one or more extended information elements may be used in the handover across TOFs.
  • the message 600 may comprise a handover request message, e.g., the handover request message 502, that may be used in the handover, e.g., from the source eNB 204s to the target eNB 204t.
  • a handover request message e.g., the handover request message 502
  • the handover request message 502 may be used in the handover, e.g., from the source eNB 204s to the target eNB 204t.
  • the message 600 may comprise one or more information elements, e.g., Old eNB UE X2AP Identity (ID) , Cause, Target Cell ID, GUMMEI ID, Globally Unique Mobility Management Entity Identity (GUMMEI ID) , UE context information (e.g., Mobility Management Entity (MME) UE S1 Application Protocol (S1AP) ID, UE Security Capabilities, Access-Stratum Security Information such as Key eNB, etc.
  • ID Old eNB UE X2AP Identity
  • GUMMEI ID Globally Unique Mobility Management Entity Identity
  • MME Mobility Management Entity
  • S1AP Application Protocol
  • UE Security Capabilities e.g., Access-Stratum Security Information such as Key eNB, etc.
  • Evolved Radio Access Bearers eRABs
  • RRC Radio Resource Control
  • the handover request message 600 may comprise one or more extended information elements, e.g., source TOF context information, e.g., Source TOFs to be Connected List 610.
  • the Source TOFs to be Connected List 610 may comprise Context Information 612 for each item in the Source TOFs to be Connected List 610.
  • the Context Information 612 may comprise an IP Address 614 of a source TOF in the Source TOFs to be Connected List 610 and/or a Port Number 616 that may be used to establish the tunnel between source TOF 212s and target TOF 212t.
  • source TOF 212s and target TOF 212t may communicate over a port with the Port Number 616 to create the inter-TOF tunnel that may be, e.g., a bi-directional tunnel.
  • the handover request message 600 may comprise an IP Address 620 of a UE, e.g., UE 202 that may be assigned one or more ongoing service sessions.
  • the target TOF 212t may transmit a session relay request message 508 to the source TOF 212s to request for a relay of a traffic flow from the source TOF 212s to the target TOF 212t via the inter-TOF tunnel between the target TOF 212t and the source TOF 212s.
  • the source TOF 212s in response to receiving the session relay request message 508 from the target TOF 212t, may transfer a session relay request acknowledge message 510 to the target TOF 212t via the inter-TOF tunnel.
  • the inter-TOF tunnel may be established based on the one or more extended information elements in the handover request message, in response to an exchange of the session relay request message 508 and the session relay acknowledgement message 510 between the target TOF 212t and the source TOF 212s, e.g., as shown in Figure 5.
  • the source TOF 212s may continue a communication with the AS 214 and/or 216 to maintain a traffic flow 512, e.g., a session data flow, for an ongoing service session between UE 202 and the AS 214 and/or 216 that may be initiated, e.g., prior to the establishment of the inter-TOF tunnel.
  • the source TOF 212s may transfer or relay the traffic flow 512 to the target TOF 212t via the inter-TOF tunnel.
  • the target TOF 212t may transfer or relay the traffic flow 512 to UE 202, e.g., via the target eNB 204t.
  • the source TOF 212s may check a destination address, a destination port number and/or a protocol number in each packet, e.g., in the traffic flow 512 from the AS 214 and/or 216. In some embodiments, in response to determining that the destination address, the destination port number and/or the protocol number of a packet is associated with or destined to the tunnel, the source TOF 212s may send the packet to the target TOF 212t through the tunnel. For example, one or more packets with the corresponding destination address, the destination port number and/or the protocol number should be delivered through the tunnel.
  • the inter-TOF tunnel may be used to relay a service session between UE 202 and an AS, e.g. 214 or 216
  • the IP address of the UE 202 may be associated with the tunnel.
  • the target TOF 212t may transfer the packet received via the tunnel to UE 202 via the target eNB 204t.
  • the target TOF 212t may check a source address, a source port number and/or a protocol number in each packet, e.g., in the traffic flow 512 from UE 202, e.g., via the target eNB 204t.
  • the target TOF 212t may send the packet to the source TOF 212s through the tunnel.
  • the source TOF 212t may transfer the packet to the AS 214 and/or 216.
  • the source TOF 212s may send a session relay termination request 514 to the target TOF 212t that may respond to the target TOF 212t with a session relay termination acknowledge 516 to remove the tunnel.
  • the inter-TOF tunnel may be removed in response to the exchange of the session relay termination request 514 and the session relay termination request acknowledgement 516 between the source TOF 212s and the target TOF 212t.
  • a subsequent traffic flow between UE 202 and the AS 214 and/or 216 may be supported by the target eNB 204t and/or the target TOF 212t.
  • Figure 7 illustrates a block diagram of an example of an apparatus 700 according to an embodiment.
  • the apparatus 700 may be further implemented in a device, an entity, a system, a circuitry, a module, a logic, a unit, an electronic device circuitry entity, and/or any other structure using any suitably configured hardware, software and/or firmware.
  • the apparatus 700 may be used in, e.g., UE 202, eNB 204, TOF 212, AS 214, SGW 206, PGW 208, service LAN server 220, DNS server 232 and/or other structures in the network 200.
  • the apparatus 700 may communicate using one or more wireless communication standards such as 3GPP LTE, WiMAX, HSPA, Bluetooth, WiFi, 5G standards, future standards and/or other wireless communication in various embodiments.
  • the apparatus 700 may communicate in 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.
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • WWAN wireless wide area network
  • the structure 700 may be, or may be incorporated into or otherwise a part of, a UE, a base station, a TOF, an AS, a service LAN server, a SGW and/or a PGW or other type of devices, apparatus and/or systems.
  • the apparatus 700 may comprise a transmit circuitry or transmitter 712 and a receive circuitry or receiver 716 coupled to a control circuitry or controller 714.
  • the transmitter 712 and/or the receiver 716 may be elements or modules of a transceiver circuitry or transceiver.
  • the apparatus 700 may be coupled with one or more plurality of antenna elements of one or more antennas 718.
  • the apparatus 700 and/or the components of the apparatus 700 may be configured to perform operations similar to those described herein.
  • the apparatus 700 may be part of or comprise an application specific integrated circuit (ASIC) , an electronic circuit, a processor (shared, dedicated, or group) , and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.
  • ASIC application specific integrated circuit
  • the apparatus 700 may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • controller 714 may be coupled to transmitter 712 and/or receiver 716. In some embodiments, controller 714 may control one or more functionalities and one or more communications of apparatus 700. In some embodiments, controller 714 may execute instructions of software and/or firmware, e.g., of an operating system (OS) and/or one or more applications of the apparatus 700. Controller 714 may comprise or may be implemented using suitable circuitry, e.g., controller circuitry, scheduler circuitry, processor circuitry, memory circuitry, and/or any other circuitry, which may be configured to perform at least part of the functionality of the controller 714. In some embodiments, one or more functionalities of controller 714 may be implemented by logic, which may be executed by a machine and/or one or more processors.
  • suitable circuitry e.g., controller circuitry, scheduler circuitry, processor circuitry, memory circuitry, and/or any other circuitry, which may be configured to perform at least part of the functionality of the controller 714.
  • one or more functionalities of controller 714 may be implemented by logic
  • controller 714 may comprise a central processing unit (CPU) , a digital signal processor (DSP) , a graphic processing unit (GPU) , one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, a baseband circuitry, a radio frequency (RF) circuitry, a logic unit, an integrated circuit (IC) , an application-specific IC (ASIC) , or any other suitable or specific processor or controller, or one or more circuits or circuitry, and/or any combination thereof.
  • CPU central processing unit
  • DSP digital signal processor
  • GPU graphic processing unit
  • the structure 700 may comprise any other hardware/software/firmware components and/or communication/digital/control components.
  • the structure 700 may comprise any other hardware/software/firmware components and/or communication/digital/control components.
  • one or more elements therein may be implemented by an apparatus, a device, an entity, a system or any other suitable format based on apparatus 700.
  • a controller in structure 700 may perform one or more processes or functions as described in the disclosure.
  • Figure 8 demonstratively illustrates an example of a system 800 in accordance with some embodiments.
  • the system 800 may be configured to implement a traffic offloading function (TOF) , e.g., TOF 212, the source TOF 212s and/or the target TOF 212t.
  • TOF traffic offloading function
  • the system 800 may be configured with one or more local breakout related aspects as described in the disclosure.
  • system 800 may be implemented in an apparatus, a device, a system, a circuitry, an entity and/or any other structure using any suitably configured hardware, software and/or firmware.
  • the system 800 may be configured to perform one or more processes and/or functions as described with regard to TOF 212, the source TOF 212s and/or the target TOF 212t and/or DNS proxy 824.
  • system 800 may comprise a TOF that may include one or more interfaces to interface between TOF 800 and one or more other components or elements as described in the disclosure.
  • TOF 800 may comprise an eNB interface 802 to communicate with a base station, e.g., eNB 204.
  • the eNB interface 802 may include a S1-U interface or any other suitable interface to communicate with eNB 204.
  • TOF 800 may comprise a SGW interface 804 to communicate with a SGW, e.g., SGW 206 as described above.
  • SGW interface 804 may include a S1-U interface or any other suitable interface to communicate with SGW 206.
  • TOF 800 may comprise an AS interface 806 to communicate with an AS, e.g., AS 214.
  • AS interface 806 may include a SGi interface or any other suitable interface to communicate with AS 214.
  • TOF 800 may comprise an internet interface 808 to communicate with, e.g., the Internet 230 and/or DNS server 232.
  • the internet interface 808 may include a SGi interface or any other suitable interface to communicate with internet 230 and/or DNS server 232.
  • TOF 800 may comprise a processor 830 and/or a memory 832 that may be coupled with each other. 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 packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of TOF 800 may be distributed among multiple or separate devices.
  • Processor 830 may include, for example, a central processing unit (CPU) , a digital signal processor (DSP) , a graphic processing unit (GPU) , one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, a baseband circuitry, a radio frequency (RF) circuitry, a logic unit, an integrated circuit (IC) , an application-specific IC (ASIC) , or any other suitable multi-purpose or specific processor or controller, or one or more circuits or circuitry, and/or any combination thereof.
  • Processor 830 may executes instructions, for example, of an operating system (OS) of TOF 800 and/or of one or more suitable applications.
  • OS operating system
  • TOF 800 one or more suitable applications.
  • memory 832 may include, for example, a random access memory (RAM) , a read only memory (ROM) , a dynamic RAM (DRAM) , a synchronous DRAM (SD-RAM) , a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units or storage units.
  • RAM random access memory
  • ROM read only memory
  • DRAM dynamic RAM
  • SD-RAM synchronous DRAM
  • flash memory a volatile memory
  • non-volatile memory a cache memory
  • buffer a buffer
  • short term memory unit a long term memory unit
  • memory 832 may be configured to store, for example, data and/or instructions for TOF 800.
  • TOF 800 may be configured to receive, e.g., via transceiver 840, one or more GTP-U packets from eNB 204 through eNB interface 202.
  • TOF 800 may comprise a decapsulating/encapsulating module or unit 810 that may be coupled to one or more other components in TOF 800.
  • the decapsulating/encapsulating module 810 may be configured to decapsulate the one or more GTP-U packets from eNB 204 into one or more IP packets.
  • TOF 800 may comprise a destination/source address checking module or unit 812 that may be configured to determine if a destination IP address of the one or more IP packets is destined to a local AS, e.g., 214, that may be collated with TOF 800.
  • a destination/source address checking module or unit 812 may be configured to determine if a destination IP address of the one or more IP packets is destined to a local AS, e.g., 214, that may be collated with TOF 800.
  • TOF 800 may comprise an offloading module or unit 814.
  • the offloading module 814 may be configured to offload a traffic, e.g., the one or more IP packets to the local AS 214, e.g., via the transceiver 840 through the AS interface 806, in response to the destination/source address checking module 812 determining that the destination address of the one or more IP packets is destined to the local AS 214.
  • TOF 800 may comprise a local breakout policy checking module or unit 816 that may be configured to check if the one or more IP packets meet with a local breakout policy in response to the destination/source address checking module 812 determining that the destination address of the one or more IP packets is not destined to the local AS 214.
  • TOF 800 may comprise a network address translating (NAT) module or unit 818.
  • the NAT module 818 in response to the local breakout policy checking module 816 determining that the one or more IP packets meet with the local breakout policy.
  • the NAT module 818 may be configured to activate a NAT functionality and/or to translate source IP address of the one or more IP packets into a global IP address of TOF 800.
  • examples of the NAT module 818 may comprise a translator, a translating module, a translating circuitry, or a translating logic, etc., for the network address translation, e.g., from the source IP address of the one or more IP packets to a global IP address of TOF 800.
  • the decapsulating/encapsulating module 810 may be configured to encapsulate the one or more IP packets as GTP-U format in response to determining that the one or more IP packets do not meet the local breakout policy. While Figure 8 illustrates an example of the decapsulating/encapsulating module or unit 810 in accordance with some embodiments, in some other embodiments, TOF 800 may comprise a decapsulating module or unit to perform decapsulating and/or an encapsulating module or unit to perform encapsulating, respectively.
  • TOF 800 may be configured to forward, via transceiver 840, the one or more encapsulated GTP-U packets to SGW 206 through the SGW interface 804.
  • SGW 206 may be configured to establish a GTP tunnel between SGW 206 and eNB 204 to forward the GTP-U packet to eNB 204 that may forward to UE 202 a UDP packet corresponding to the GTP-U packet.
  • eNB 204 may be configured to transmit to TOF 800 a DNS query or request from UE 202 as one or more UDP packets that may be encapsulated in one or more GTP-U packets.
  • eNB 204 may be configured to transform, e.g., encapsulate the DNS query or request from UE 202, e.g., the one or more UDP packets with a destination port of 53 in the GTP-U format.
  • TOF 800 may comprise a DNS proxy 824.
  • the decapsulating/encapsulating module 810 may be configured to decapsulate the one or more GTP-U packets into one or more IP packets.
  • the offloading module 814 may be configured to offload to the DNS proxy 824 the one or more IP packets that may comprise the one or more UDP packets carrying the DNS request.
  • DNS proxy 824 may be configured to extract the DNS request from the one or more UDP packets encapsulated in the IP packet (s) from the offloading module 814. In some embodiments, DNS proxy 824 may be configured to encapsulate the extracted DNS request as one or more UDP packets and/or may deliver to TOF 800, e.g., NAT module 818, one or more IP packets that may comprise the one or more UDP packets carrying the DNS request. In some embodiments, the one or more UDP packets may comprise a destination port number of 53.
  • NAT module 818 may perform a NAT functionality to translate a source IP address of the one or more IP packets from DNS proxy 824 to a global IP address of the TOF 800.
  • the offloading module 814 may send the one or more IP packets after NAT to DNS server 232 and/or Internet 230, e.g., via the transceiver 840 and/or the Internet interface 808.
  • the DNS server 232 may determine which AS 212 and/or 216 in one or more mappings between global IP address of TOF 800 and IP address of one or more ASs 212 and/or 216 can provide a service requested by UE 202 based on the DNS request. In some embodiments, DNS server 232 may retrieve the one or more mappings to obtain a DNS response that may comprise IP address of the one or more ASs 212 and/or 216 that can provide the service.
  • DNS server 232 may provide to TOF 800 the DNS response as one or more UDP packets that may be encapsulated in one or more IP packets.
  • TOF 800 e.g., offloading module 814 may send the one or more IP packets from DNS server 232 to DNS proxy 824 in TOF 800 in response to receiving the IP packets.
  • DNS proxy 824 in TOF 800 may be configured to extract the DNS response from the one or more UDP packets encapsulated in the one or more IP packets from offloading module 814.
  • DNS proxy 824 may store or cache one or more extracted DNS responses in memory 832 and/or any other storage medium in TOF 800 and/or in DNS proxy 824.
  • DNS proxy 824 may retrieve the one or more cached DNS response to obtain a DNS response with regard to the DNS request from UE 202.
  • DNS proxy 824 may encapsulate the extracted or retrieved DNS response as one or more UDP packets with a source port number of 53 to indicate the one or more UDP packets relate to a DNS response.
  • the one or more UDP packets may have a destination address to UE 202.
  • DNS proxy 824 may forward to TOF 800, e.g., the decapsulating/encapsulating module 810, the DNS response as the one or more UDP packets that may be encapsulated in one or more IP packets.
  • the decapsulating/encapsulating module 810 may encapsulate the one or more IP packets as one or more GTP-U packets to be forwarded to eNB 204.
  • the offloading module 814 may send the one or more GTP-U packets to eNB 204 via, e.g., the transceiver 840 and/or the eNB interface 820.
  • the one or more GTP-U packets that may comprise the one or more UDP packets carrying the DNS response, e.g., with the IP address of the AS or service server.
  • eNB 204 may transform, e.g., decapsulate, the one or more GTP-U packets from TOF 800 to obtain the one or more UDP packets with the source port of 53. In some embodiments, eNB 204 may transfer the one or more UDP packets to UE 202. In some embodiments, in response to receiving the one or more UDP packets, UE 202 may establish a service session with the AS 214 and/or 216 based on the IP address of the AS 214 and/or 216 included in the DNS response in the one or more UDP packets.
  • TOF 800 may comprise a session migration module or unit 820 and/or a session relaying module or unit 822 that may each perform one or more processes, e.g., as shown in Figure 5.
  • a target eNB 204t may issue a handover request 502 in response to initiation of a handover from source eNB 204s to target eNB 204t.
  • the handover request 502 may comprise one or more information elements that may enable the handover from source eNB 204s to target eNB 204t.
  • the handover and/or session migration from source eNB 204s to target eNB 204t may be performed based on the one or more information elements delivered with the handover request 502.
  • a handover across TOFs may be initiated.
  • the handover request 502 may comprise one or more extended information elements to enable the handover across TOFs.
  • the target eNB 204t may transmit to TOF 800, e.g., if as a target TOF 212t, a session migration request 504 that may comprise the one or more extended information elements delivered with the handover request 502.
  • TOF 800 if used as the target TOF, may establish a tunnel to a source TOF 212s based on the one or more extended information elements.
  • the session migrating module 820 in response to receiving the session migration request 504 from the target eNB 204t, e.g., via transceiver 840 through the eNB interface 804, the session migrating module 820 may be configured to transmit to the target eNB 204t a session migration request acknowledgement 506 that may be used to confirm whether the inter-TOF tunnel is successfully established.
  • TOF 800 may comprise a session relaying module or unit 822.
  • the session relaying module 822 in response to the session migrating module 820 responding to the session migration request 504 with the session migration request acknowledgement 506, the session relaying module 822 may be configured to transmit to a source TOF212s a session relay request 508 to request for relaying to TOF 800 a traffic flow 512 of an ongoing session between the AS 214 and/or 216 and UE 202 that may be assigned to the ongoing session.
  • the handover request 502 and/or the session migration request 504 may comprise one or more extended information elements, e.g., Source TOF Context Information 612, to indicate an IP Address 614, e.g., a source IP address or a destination IP address of the source TOF 212t in Source TOFs to be Connected List 610 and/or a Port Number 616, e.g., a source port number or a destination port number, for the tunnel establishment.
  • an IP Address 614 e.g., a source IP address or a destination IP address of the source TOF 212t in Source TOFs to be Connected List 610 and/or a Port Number 616, e.g., a source port number or a destination port number, for the tunnel establishment.
  • the handover request 502 and/or the session migration request 504 may comprise one or more extended information elements, e.g., a UE IP Address 620 to indicate an IP address of UE 202 as shown in Figure 5 that may be assigned to the ongoing session with the AS 214 and/or 216.
  • extended information elements e.g., a UE IP Address 620 to indicate an IP address of UE 202 as shown in Figure 5 that may be assigned to the ongoing session with the AS 214 and/or 216.
  • TOF 800 may be configured to establish the inter-TOF tunnel to the source TOF 212s based on the one or more extended information elements in the handover request 502 in response to exchanging the session relay request 508 and the session relay request acknowledge 510 with the source TOF 212s.
  • a target TOF 212t and/or a source TOF 212s may use an inter-TOF tunnel to relay one or more service sessions between a UE, e.g., UE 202, and an AS 214 and/or 216.
  • the IP address of the UE 202 may be associated with the inter-TOF tunnel.
  • the source TOF 212s may forward one or more IP packets whose source IP address is UE 202 to the target TOF 212t through inter-TOF tunnel.
  • the target TOF 212t may forward to UE 202 the one or more IP packets with UE 202’s source IP address 616 via eNB 204.
  • a destination checking module in the source TOF 212s may check a destination address, a destination port number and/or a protocol number in each packet in a traffic flow 512 from the AS 214 and/or 216 that may have an ongoing session with the UE 202.
  • the source TOF 212s in response to the destination/source address checking module determining that one or more of the destination address, the destination port number and the protocol number are associated with the tunnel, the source TOF 212s may be configured to use the tunnel to relay, e.g., via a transceiver, the packet (s) in traffic flow 512A from the AS 214 and/or 216 to TOF 800, e.g., as the target TOF 212t.
  • transceiver 840 of TOF 800 in response to receiving the packet (s) of the traffic flow 512 that may be relayed from the AS 214 and/or 216 by the source TOF 212s, transceiver 840 of TOF 800, e.g., the target TOF 212t, may be configured to transfer the packet (s) to UE 202 via the target eNB 204t.
  • the destination/source address checking module 812 in TOF 800 may check a source address, a source port number and/or a protocol number in each packet, e.g., in the traffic flow 512 from the UE 202 that may have an ongoing session with the AS 214 and/or 216.
  • the transceiver 840 in TOF 800 in response to the destination/source address checking module 812 determining that one or more of the information elements are associated with the tunnel, the transceiver 840 in TOF 800, e.g., the target TOF 212t, may be configured to send the packet (s) in the traffic flow 512 from UE 202 to the source TOF 212s through the tunnel, e.g., via transceiver 840.
  • the transceiver in the source TOF 212s in response to the packet (s) in the traffic flow 512 from UE 202 that may be relayed by TOF 800, the transceiver in the source TOF 212s may be configured to transfer the received packet (s) to the AS 214 and/or 216.
  • TOF 800 may comprise a destination address checking module or unit to perform destination address checking and/or a source address checking module or unit to perform source address checking, respectively.
  • the session relaying module in the source TOF 212s may send, e.g., via the transceiver in source TOF 212s, a session relay termination request 514 to TOF 800, e.g., used as the target TOF 212t.
  • the session relaying module 822 in target TOF 800 may be configured to send, e.g., via the transceiver 840, a session relay termination request acknowledge 516 to the source TOF 212s.
  • the tunnel between the source TOF 212s and TOF 800 as the target TOF 212t may be terminated or removed in response to the exchange of the session relay termination request 514 and the session relay termination request acknowledge 516.
  • the source TOF 212s may remove the tunnel in response to the exchange of the session relay termination request 514 and the session relay termination request acknowledge 516.
  • the target TOF 212t e.g., TOF 800, may be configured to support a communication between UE 202 and the AS 214 and/or 216 via the target eNB 204t, in response to the removal of the tunnel.
  • a handover from the source TOF 212s to the target TOF 212t may be completed in response to the removal of the tunnel.
  • the TOF 800 may comprise decapsulating/encapsulating module 810, destination/source address checking module 812, offloading module 814, local breakout policy checking module 816, network address translating module 818, session migrating module 820, session relaying module 822, and/or DNS proxy 824, in some embodiments, one or more of the modules of TOF 800 may be provided in or implemented by one or more processors 830 or other controllers or in the same processor or controller.
  • transceiver 840 may be implemented by one or more transmitters and one or more receivers and/or or in other transmitting/receiving structure.
  • Figure 8 illustrates some embodiments relating to one or more interfaces, e.g., 802, 804, 806 or 808, in some embodiments, the one or more interfaces may be included in a network, e.g., 200. In some embodiments, the one or more interfaces may be implemented in or by the transceiver 840.
  • DNS proxy 824 may comprise one or more of a decapsulating module and/or an encapsulating module, a DNS request/response extracting module, a DNS response storing module, a DNS response retrieving module, a memory or other storage medium, e.g., a cache, that may store one or more DNS responses and/or one or more UDP or IP packets comprising the one or more DNS responses or one or more other modules based on one or more processes, operations or functions as described with regard to, e.g., TOF 212 and/or 800 and/or DNS proxy 824.
  • Figure 9 demonstratively illustrates an example of a system 900 in accordance with some embodiments.
  • the system 900 may be configured to comprise a DNS system, e.g., DNS server 232.
  • the system 900 may be provided in Internet 230.
  • the system 900 may be implemented in an apparatus, a device, a system, an entity, a server, a circuitry and/or any other structure using any suitably configured hardware, software and/or firmware.
  • the system 900 may be configured to perform one or more processes and/or functions as described with regard to the DNS server 232.
  • system 900 may include one or more interfaces to interface between the system 900 and one or more other components or elements in the disclosure.
  • system 900 may comprise a TOF interface 902 to communicate with a TOF 212 and/or TOF proxy 824 in TOF 212 as shown in Figure 2.
  • the TOF interface 902 may include a SGi interface or any other suitable interface to communicate with TOF 212.
  • system 900 may comprise a service server interface 904 to communicate with the service LAN server 220 and/or AS 214 and/or 216.
  • the internet interface 904 may include a SGi interface or any other suitable interface to communicate with the service LAN server 220 and/or AS 214 and/or 216.
  • system 900 may comprise a processor 920 and/or a memory 922 that may be coupled with each other.
  • System 900 may further comprise one or more other suitable hardware components and/or software and/or firmware components.
  • some or all of the components of system 900 may be enclosed in a housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links.
  • components of system 900 may be distributed among multiple or separate devices.
  • Processor 920 may include, for example, a central processing unit (CPU) , a digital signal processor (DSP) , a graphic processing unit (GPU) , one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a set of one or more processors or controllers, a chip, a microchip, a baseband circuitry, a radio frequency (RF) circuitry, a logic unit, an integrated circuit (IC) , an application-specific IC (ASIC) , or any other suitable multi-purpose or specific processor or controller, or one or more circuits or circuitry, and/or any combination thereof.
  • Processor 920 may executes instructions, for example, of an operating system (OS) of system 900 and/or of one or more suitable applications.
  • OS operating system
  • ASIC application-specific IC
  • memory 922 may include, for example, a random access memory (RAM) , a read only memory (ROM) , a dynamic RAM (DRAM) , a synchronous DRAM (SD-RAM) , a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units or storage units.
  • RAM random access memory
  • ROM read only memory
  • DRAM dynamic RAM
  • SD-RAM synchronous DRAM
  • flash memory a volatile memory
  • non-volatile memory a cache memory
  • buffer a buffer
  • short term memory unit a long term memory unit
  • memory 922 may be configured to store, for example, data and/or instructions for system 900.
  • system 900 may comprise a DNS query or request checking module or unit 910 that may be coupled to one or more other components in system 900.
  • TOF 212 may receive from eNB 204 one or more UDP packets with a destination port of 53 relating to UE 202, e.g., in a DNS request 404 with a GTP-U format.
  • TOF 212 may decapsulate the one or more GTP-U packets from eNB 204 that may carry the DNS request 404 to obtain one or more IP packets.
  • TOF 212 may forward the one or more IP packets to DNS proxy 824 in the TOF 212 or other DNS proxy that may comprise a local AS 214.
  • the DNS proxy 824 may extract the DNS request 404 from the one or more UDP packets in the one or more IP packets from TOF 212 and/or may encapsulate the extracted DNS request 404 in one or more UDP packets with a destination port of 53. In some embodiments, DNS proxy 824 may send to TOF 212 the one or more UDP packets carrying the DNS request 404 that may be encapsulated in one more IP packets.
  • TOF 212 may perform a NAT on the one or more IP packets from DNS proxy 824 in TOF 212 to translate source IP address of the IP packets into global IP address of the TOF 212 to provide DNS request 406.
  • TOF 212 may offload the one or more IP packets carrying the DNS request 406 to system 900.
  • system 900 may be configured to receive from TOF 212, e.g., via transceiver 930, the one or more IP packets associated with the DNS request 406 through the TOF interface 902.
  • the DNS query checking module 910 may be configured to determine whether a service requested by UE 202 is deployed in one or more ASs, e.g., local AS 214 or external AS 216 in one or more mappings stored in the memory 922. In response to the DNS query checking module 910 determining that the service requested by UE 202 is deployed in one or more ASs 214 and/or 216 in the one or more mappings, the address obtaining module 912 may be configured to obtain IP address of the one or more ASs 214/216 from the one or more mappings.
  • the address obtaining module 912 may be configured to retrieve the one or more mappings between a global IP address of TOF 212 and IP address of AS (s) 214/216 to obtain the IP address of the one or more ASs 214/216 for the service requested by UE 202.
  • the one or more mappings may be stored in memory 922 in, e.g., a table, an array, a list or any other structure or form.
  • the system 900 may reply to TOF 212 with DNS response 408 that may comprise the retrieved IP address of the one or more AS 214/216 in response to the DNS request 406.
  • the administrator of system 900 may update the one or more mappings in system 900, e.g., remove the one or more mappings and/or include IP address of the one or more new ASs 214/216 and/or one or more new mappings between the global IP address of TOF 212 and the IP address of the new ASs 214/216.
  • the address obtaining module 912 may retrieve the IP address of the new AS (s) 214/216 from the new or updated mapping (s) in memory 922.
  • DNS 408 may comprise the retrieved IP address of the one or more new ASs 214/216.
  • encapsulating module or unit 916 may encapsulate the DNS response 408 as one or more UDP packets and/or may further encapsulate the one or more UDP packets in one or more IP packets to be forwarded to TOF 212.
  • DNS query responding module 914 may send to TOF 212 the DNS response 408 as one or more UDP packets that may be encapsulated in one or more IP packets to indicate IP address of the one or more ASs 214/216 or the new AS (s) 214/216 in response to the DNS request 406.
  • the system 900 may transmit to TOF 212 a DNS response 408 as one or more UDP packets to indicate no AS may be able to provide the service requested in the DNS request 406.
  • TOF 212 may forward the received IP packets to DNS proxy 824 in TOF 212.
  • the DNS proxy 824 may extract the DNS response 408 in the one or more UDP packets in the IP packets.
  • DNS proxy 824 may store or cache one or more DNS responses 408.
  • DNS proxy 824 may retrieve the cached DNS responses to obtain a DNS response 408 in response to a subsequent DNS request without querying the system 900 again.
  • DNS proxy 824 may encapsulate the extracted DNS response 408 or the retrieved DNS response 408 as one or more UDP packets that may comprise a source port number of 53 and/or a destination address to UE 202.
  • the DNS proxy 824 may encapsulated the one or more UDP packets as one or more IP packets and/or may forward the one or more IP packets to TOF 212.
  • TOF 212 may encapsulate the one or more IP packets of DNS proxy 824 as one or more GTP-U packets to generate DNS response 410 to be forwarded to eNB 204.
  • TOF 212 may send the GTP-U packets comprising DNS response 410 to eNB 204.
  • the eNB 204 may decapsulate the received DNS response 410 to obtain the one or more UDP packets with the source port of 53 that may carry the DNS response 410 and/or may transmit the one or more UDP packets with the source port of 53 as DNS response 412 to UE 202 that may send the DNS response 402 originally.
  • UE 202 may establish a communication or a service session with the one or more ASs 214/216 that may have the IP address indicated in the DNS response 412, e.g., via the eNB 204 and/or the TOF 212.
  • FIG. 9 illustrates that the system 900 may comprise DNS query checking module 910, address obtaining module 912, DNS request responding module 914 and/or encapsulating module 917, in some embodiments, one or more of the modules 910 to 916 may be provided in or implemented by one or more processors 920 or other controllers or control circuitry.
  • the transceiver 930 may be implemented by one or more transmitters and one or more receivers and/or or in other transmitting/receiving structure.
  • Figure 9 illustrates some embodiments of one or more interfaces, e.g., 902 or 904, in some embodiments, the one or more interfaces may be included in a network, e.g., 200. In some embodiments, the one or more interfaces may be implemented in or by the transceiver 930.
  • Figure 10 illustrates, for one embodiment, an example system comprising radio frequency (RF) circuitry 1030, baseband circuitry 1020, application circuitry 1010, front end module (FEM) circuitry 1060, memory/storage 1040, one or more antennas 1050, display 1002, camera 1004, sensor 1006, and input/output (I/O) interface 1008, coupled with each other at least as shown.
  • RF radio frequency
  • FEM front end module
  • I/O input/output
  • Figure 10 illustrates example components of a UE device 1000 in accordance with some embodiments.
  • the application circuitry 1010 may include one or more application processors.
  • the application circuitry 1010 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor (s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc. ) .
  • the processors may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.
  • the baseband circuitry 1020 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 1020 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 1030 and to generate baseband signals for a transmit signal path of the RF circuitry 1030.
  • Baseband processing circuity 1020 may interface with the application circuitry 1010 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1030.
  • the baseband circuitry 1020 may 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 baseband processor (s) 1020d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G) , 6G, etc. ) .
  • the baseband circuitry 1020 e.g., one or more of baseband processors
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 1020 may include Fast-Fourier Transform (FFT) , precoding, and/or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 1020 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 1020 may include 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 convergence protocol (PDCP) , and/or RRC elements.
  • a central processing unit (CPU) 1020e of the baseband circuitry 1020 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers.
  • the baseband circuitry 1020 may include one or more audio digital signal processor (s) (DSP) 1020f that may include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • DSP audio digital signal processor
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 1020 and the application circuitry 1010 may be implemented together such as, for example, on a system on a chip (SOC) .
  • SOC system on a chip
  • the baseband circuitry 1020 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 1020 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN) , a wireless local area network (WLAN) , a wireless personal area network (WPAN) .
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • multi-mode baseband circuitry Embodiments in which the baseband circuitry 1020 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 1030 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 1030 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 1030 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1060 and provide baseband signals to the baseband circuitry 1020.
  • RF circuitry 1030 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1020 and provide RF output signals to the FEM circuitry 1060 for transmission.
  • the RF circuitry 1030 may include a receive signal path and a transmit signal path.
  • the receive signal path of the RF circuitry 1030 may include mixer circuitry 1030a, amplifier circuitry 1030b and/or filter circuitry 1030c.
  • the transmit signal path of the RF circuitry 1030 may include filter circuitry 1030c and/or mixer circuitry 1030a.
  • RF circuitry 1030 may also include synthesizer circuitry 1030d for synthesizing a frequency for use by the mixer circuitry 1030a of the receive signal path and the transmit signal path.
  • the mixer circuitry 1030a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1060 based on the synthesized frequency provided by synthesizer circuitry 1030d.
  • the amplifier circuitry 1030b may be configured to amplify the down-converted signals.
  • the filter circuitry 1030c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 1020 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 1030a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 1030a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1030d to generate RF output signals for the FEM circuitry 1060.
  • the baseband signals may be provided by the baseband circuitry 1020 and may be filtered by filter circuitry 1030c.
  • the filter circuitry 1030c may include a low-pass filter (LPF) , although the scope of the embodiments is not limited in this respect.
  • LPF low-pass filter
  • the mixer circuitry 1030a of the receive signal path and the mixer circuitry 1030a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively.
  • the mixer circuitry 1030a of the receive signal path and the mixer circuitry 1030a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection) .
  • the mixer circuitry 1030a of the receive signal path and the mixer circuitry 1030a may be arranged for direct downconversion and/or direct upconversion, respectively.
  • the mixer circuitry 1030a of the receive signal path and the mixer circuitry 1030a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 1030 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1020 may include a digital baseband interface to communicate with the RF circuitry 1030.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 1030d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 1030d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 1030d may be configured to synthesize an output frequency for use by the mixer circuitry 1030a of the RF circuitry 1030 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1030d may be a fractional N/N+1 synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO) , although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 1020 or the applications processor 1010 depending on the desired output frequency.
  • a divider control input (e.g., X) may be determined from a look-up table based on a channel indicated by the applications processor 1010.
  • Synthesizer circuitry 1030d of the RF circuitry 1030 may include a divider, a delay-locked loop (DLL) , a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA) .
  • the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 1030d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (f LO ) .
  • the RF circuitry 1030 may include an IQ/polar converter.
  • FEM circuitry 1060 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1050, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1030 for further processing.
  • FEM circuitry 1060 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1030 for transmission by one or more of the one or more antennas 1050.
  • the FEM circuitry 1060 may include a transmit/receive (TX/RX) switch to switch between transmit mode and receive mode operation.
  • TX/RX transmit/receive
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1030) .
  • the transmit signal path of the FEM circuitry 1060 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1030) , and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1050.
  • PA power amplifier
  • the UE 1000 comprises a plurality of power saving mechanisms. If the UE 1000 is in an RRC_Connected state, where it is still connected to the eNB as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the UE 1000 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the UE 1000 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device cannot receive data in this state, in order to receive data, it must transition back to RRC_Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours) . During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • transmit circuitry, control circuitry, and/or receive circuitry discussed or described herein may be embodied in whole or in part in one or more of the RF circuitry 1030, the baseband circuitry 1020, FEM circuitry 1060 and/or the application circuitry 1010.
  • the term "circuitry” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC) , an electronic circuit, a processor (shared, dedicated, or group) , and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules or units.
  • some or all of the constituent components of the baseband circuitry 1020, the application circuitry 1010, and/or the memory/storage may be implemented together on a system on a chip (SOC) .
  • SOC system on a chip
  • Memory/storage 1040 may be used to load and store data and/or instructions, for example, for system.
  • Memory/storage 1040 for one embodiment may include any combination of suitable volatile memory (e.g., dynamic random access memory (DRAM) ) and/or non-volatile memory (e.g., Flash memory) .
  • suitable volatile memory e.g., dynamic random access memory (DRAM)
  • non-volatile memory e.g., Flash memory
  • the I/O interface 1008 may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system.
  • User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc.
  • Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface.
  • USB universal serial bus
  • sensor may include one or more sensing devices to determine environmental conditions and/or location information related to the system.
  • the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit.
  • the positioning unit may also be part of, or interact with, the baseband circuitry and/or RF circuitry to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite.
  • GPS global positioning system
  • the display 1002 may include a display (e.g., a liquid crystal display, a touch screen display, etc. ) .
  • a display e.g., a liquid crystal display, a touch screen display, etc.
  • system may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, etc.
  • system may have more or less components, and/or different architectures.
  • circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC) , an electronic circuit, a processor (shared, dedicated, or group) , and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules or units.
  • Example 1 may comprise an apparatus of traffic offloading function (TOF) that may comprise a memory to comprise one or more instructions; and a processor to execute one or more of the instructions 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; provide 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 provide 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.
  • TOF traffic offloading function
  • Example 2 may comprise the apparatus of Example 1 or some other example (s) herein, wherein the processor may further perform a network address translation (NAT) to translate a source address of the traffic to be transmitted to the second server into a global address of the TOF entity.
  • NAT network address translation
  • Example 3 may comprise the apparatus of any one of Examples 1 to 2 or some other example (s) herein, wherein the processor may further decapsulate the traffic into one or more Internet Protocol (IP) packets.
  • IP Internet Protocol
  • Example 4 may comprise the apparatus of any one of Example 1 to 3 or some other example (s) herein, wherein the processor may further encapsulate the one or more IP packets of the traffic into one or more General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) packets for a server gateway (SGW) in response to determining that the one or more IP packets do not meet with the local breakout policy.
  • GPRS General Packet Radio Service
  • GTP-U General Packet Radio Service Tunneling Protocol User Plane
  • SGW server gateway
  • Example 5 may comprise the apparatus of any one of Example 1 to 4 or some other example (s) herein, wherein the processor may further forward the one or more GTP-U packets to the SGW.
  • Example 6 may comprise the apparatus of any one of Example 1 to 5 or some other example (s) herein, wherein the processor may further decapsulate the traffic into one or more IP packets, wherein the traffic comprises a domain name system request associated with the UE; and provide the one or more IP packets corresponding to the DNS request to a domain name system (DNS) proxy in the apparatus.
  • the processor may further decapsulate the traffic into one or more IP packets, wherein the traffic comprises a domain name system request associated with the UE; and provide the one or more IP packets corresponding to the DNS request to a domain name system (DNS) proxy in the apparatus.
  • DNS domain name system
  • Example 7 may comprise the apparatus of any one of Example 1 to 6 or some other example (s) herein, wherein the processor may further translate a source IP address of the DNS request extracted by the DNS proxy to a global IP address of the apparatus; forward the DNS request to the second server that to comprise a DNS server; and provide a DNS response from the second server to the first base station in response to the DNS request, wherein the DNS response to indicate an IP address of the first server that comprises an application server to provide a service requested in the DNS request.
  • the processor may further translate a source IP address of the DNS request extracted by the DNS proxy to a global IP address of the apparatus; forward the DNS request to the second server that to comprise a DNS server; and provide a DNS response from the second server to the first base station in response to the DNS request, wherein the DNS response to indicate an IP address of the first server that comprises an application server to provide a service requested in the DNS request.
  • Example 8 may comprise the apparatus of any one of Example 1 to 7 or some other example (s) herein, wherein the processor may further establish an inter-TOF point tunnel between the TOF entity and a second TOF entity in response to an initiation of a handover from the second TOF entity to the TOF entity.
  • Example 9 may comprise the apparatus of any one of Example 1 to 8 or some other example (s) herein, wherein the processor may further establish the inter-TOF point tunnel based on one or more information elements in a handover request associated with a handover from a first base station to a second base station that is to communicate with the UE, wherein the one or more information elements comprise one or more from a group that to comprise context information of the second TOF entity, an IP address of the second TOF entity, the port number for the inter-TOF point tunnel, an IP address of the UE.
  • Example 10 may comprise the apparatus of any one of Example 1 to 9 or some other example (s) herein, wherein the processor may further provide a session relay request to the second TOF entity in response to receiving a session migration request from the second base station; and establish the inter-TOF point tunnel based on a session relay request acknowledge from the second TOF entity.
  • Example 11 may comprise the apparatus of any one of Example 1 to 10 or some other example (s) herein, wherein the processor may further receive a session migration request from the second base station, wherein the session migration request to comprise the one or more information elements.
  • Example 12 may comprise the apparatus of any one of Example 1 to 11 or some other example (s) herein, wherein the processor may further provide the traffic associated with the UE to the second TOF entity via the inter-TOF point tunnel in response to the processor determining that one or more of a source address, a source port number and a protocol number in the traffic is associated with the inter-TOF tunnel.
  • Example 13 may comprise the apparatus of any one of Example 1 to 12 or some other example (s) herein, wherein the processor may further provide a session relay termination request acknowledge in response to receiving from the second TOF entity a session relay termination request to remove, by the second TOF entity, the inter-TOF tunnel in response to inactivity of the traffic in the inter-TOF tunnel.
  • Example 14 may comprise a domain name system (DNS) that may comprise a receiver to receive from a traffic offloading function (TOF) entity a DNS request associated with a user equipment (UE) , wherein the DNS request comprises a source address corresponding to a global IP address of the TOF entity; a memory to store a mapping table between a global IP address of the TOF entity and an IP address of a first application server (AS) ; and a processor to retrieve the mapping table to obtain the IP address of the first AS, in response to determining that a service requested in the DNS request is deployed in the first AS; and a transmitter to transmit the IP address of the first AS in a DNS response to the TOF entity.
  • DNS domain name system
  • TOF traffic offloading function
  • UE user equipment
  • AS application server
  • Example 15 may comprise the DNS of Example 14 or some other example (s) herein, wherein the processor may further, in response to determining that the service requested by the DNS request is unavailable in the first AS and is deployed in a second AS, update the mapping table to include a mapping between the global IP address of the TOF entity and the IP address of the second AS.
  • Example 16 may comprise the DNS of any one of Examples 14 to 15 or some other example (s) herein, wherein the processor may further retrieve the mapping table to obtain the IP address of the second AS.
  • Example 17 may comprise the DNS of any one of Examples 14 to 16 or some other example (s) herein, wherein the DNS may further comprise a transmitter to transmit to the TOF entity a DNS response to comprise the IP address of the second AS, in response to the processor determining that a service requested by the DNS request is deployed in the second AS.
  • Example 18 may comprise the DNS of any one of Examples 14 to 17 or some other example (s) herein, wherein the first AS to comprise a local AS collated with the TOF entity or an external AS that is outside of a local network of the TOF entity.
  • Example 19 may comprise the DNS of any one of claims 14 to 18, wherein the second AS to comprise a local AS collated with the TOF entity or an external AS that is outside of a local network of the TOF entity.
  • Example 20 may comprise a user equipment (UE) that may comprise a transceiver to transmit to a first base station a domain name system (DNS) request associated with a service for the UE and to receive from the first base station a DNS response that to indicate an Internet Protocol (IP) address of a first application server (AS) that to provide the service for the UE; and a controller that is coupled to the transceiver, wherein the controller to initiate a service session with the first AS based on the IP address of the first AS.
  • DNS domain name system
  • AS application server
  • Example 21 may comprise the UE of Example 20 or some other example (s) herein, wherein the DNS request to comprise a user datagram protocol (UDP) packet with a destination address associated with a DNS.
  • UDP user datagram protocol
  • Example 22 may comprise the DNS of any one of Examples 20 to 21 or some other example (s) herein, wherein the DNS response to comprise a UDP packet with a source address associated with a DNS.
  • Example 23 may comprise the DNS of any one of Examples 20 to 22 or some other example (s) herein, wherein the controller may further initiate a service session with a second AS in response to the transceiver receiving from the first base station the DNS response that to indicate an IP address of the second AS, wherein the second AS to provide the service for the UE that is unavailable in the first AS.
  • Example 24 may comprise the DNS of any one of Examples 20 to 23 or some other example (s) herein, wherein the controller may further initiate a communication with a second base station in response to a handover from the first base station to the second base station.
  • Example 25 may comprise the DNS of any one of Examples 20 to 24 or some other example (s) herein, wherein the controller may further in response to a handover from a first traffic offloading function (TOF) entity to a second TOF entity, initiate a communication with a second TOF entity that to communicate with the first TOF entity via an inter-TOF tunnel between the first TOF entity and the second TOF entity.
  • TOF traffic offloading function
  • Example 26 may comprise an apparatus of a base station that may comprise a memory to comprise one or more instructions; a controller to performed the one or more instructions to transform a first user datagram protocol (UDP) packet of a domain name system (DNS) request from a user equipment (UE) into a first general packet radio service (GPRS) tunneling protocol user plane (GTP-U) packet; provide the first GTP-U packet to a first traffic offloading function (TOF) entity; and receive from the TOF entity a second GTP-U packet of a DNS response that to comprise an internet protocol (IP) address of an application server (AS) .
  • UDP user datagram protocol
  • DNS domain name system
  • GTP-U general packet radio service
  • TOF traffic offloading function
  • Example 27 may comprise the apparatus of Example 26 or some other example (s) herein, wherein the processor may further, in response to the controller transforming the second GTP-U packet into a second UDP packet, provide the second UDP packet to the UE.
  • Example 28 may comprise the apparatus of any one of Examples 26 to 27 or some other example (s) herein, wherein the processor may further provide a session migration request to a second TOF in response to a handover from the first TOF entity to the second TOF entity, wherein the session migration request to comprise one or more information elements in a group that to comprise context information of the second TOF entity, an IP address of the second TOF entity, the port number for the inter-TOF point tunnel, an IP address of the UE.
  • the processor may further provide a session migration request to a second TOF in response to a handover from the first TOF entity to the second TOF entity, wherein the session migration request to comprise one or more information elements in a group that to comprise context information of the second TOF entity, an IP address of the second TOF entity, the port number for the inter-TOF point tunnel, an IP address of the UE.
  • Example 29 may comprise the apparatus of any one of Examples 26 to 28 or some other example (s) herein, wherein the processor may further receive a session migration request acknowledge from the second TOF entity.
  • Example 30 may comprise the apparatus of any one of Examples 26 to 29 or some other example (s) herein, wherein the apparatus may further comprise a transceiver coupled to the processor and one or more antennas coupled to the processor.
  • Example 31 may comprise a machine-readable medium having instructions, stored thereon, that, when executed cause a first traffic offloading function (TOF) entity to decapsulate a first general packet radio service (GPRS) tunneling protocol user plane (GTP-U) packet from a first base station into an internet protocol (IP) packet; offload the IP packet to a first application server in response to determining that a destination address of the IP packet is destined to an application server (AS) ; and offload the IP packet to an internet in response to determining that the IP packet not destined to the AS meets with a local breakout policy.
  • TOF traffic offloading function
  • GTP-U tunneling protocol user plane
  • Example 32 may comprise the machine-readable medium of Example 31 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the first traffic offloading function (TOF) entity further to perform a network address translation on the IP packet prior to offloading the IP packet to the internet.
  • TOF traffic offloading function
  • Example 33 may comprise the machine-readable medium of Examples 31 or 32 or some other example (s) herein, wherein the first AS is collocated with the first TOF entity.
  • Example 34 may comprise the machine-readable medium of any one of Examples 31 to 33 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the first traffic offloading function (TOF) entity further to encapsulate the IP packet into a second General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) packet for a server gateway (SGW) in response to determining that the IP packet does not meet with the local breakout policy.
  • TOF traffic offloading function
  • GTP-U General Packet Radio Service
  • SGW server gateway
  • Example 35 may comprise the machine-readable medium of any one of Examples 31 to 34 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the first traffic offloading function (TOF) entity further to translate the destination address of the IP packet to a global IP address of the first TOF entity in response to determining that the IP packet is a DNS request destined to a domain name system (DNS) in the internet.
  • TOF traffic offloading function
  • Example 36 may comprise the machine-readable medium of any one of Examples 31 to 35 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the first traffic offloading function (TOF) entity further to offload the IP packet with the global IP address to the DNS; and transfer a DNS response from the DNS to the first base station, wherein the DNS response to indicate an IP address of the first server that is able to provide a service requested in the DNS request.
  • TOF traffic offloading function
  • Example 37 may comprise the machine-readable medium of any one of Examples 31 to 35 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the first traffic offloading function (TOF) entity further to offload the IP packet to a second AS in response to determining that the service requested in the DNS request is only deployed in the second AS.
  • TOF traffic offloading function
  • Example 38 may comprise the machine-readable medium of any one of Examples 31 to 37 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the first traffic offloading function (TOF) entity further to establish an inter-TOF point tunnel with a second TOF entity in response to a handover from the first TOF entity to the second TOF entity.
  • TOF traffic offloading function
  • Example 39 may comprise the machine-readable medium of any one of Examples 31 to 38 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the first traffic offloading function (TOF) entity further to receive a session relay request from the second TOF entity; and transmit a session relay request acknowledge message to the second TOF entity to establish the inter-TOF point tunnel.
  • TOF traffic offloading function
  • Example 40 may comprise the machine-readable medium of any one of Examples 31 to 39 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the first traffic offloading function (TOF) entity further to establish the inter-TOF point tunnel based on one or more information elements in a session relay request from the second TOF entity.
  • TOF traffic offloading function
  • Example 41 may comprise the machine-readable medium of any one of Examples 31 to 40 or some other example (s) herein, wherein the one or more information elements to comprise one or more of context information of the second TOF entity, an IP address of the second TOF entity, the port number for the inter-TOF point tunnel, an IP address of the UE.
  • Example 42 may comprise the machine-readable medium of any one of Examples 31 to 41 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the first traffic offloading function (TOF) entity further to transmit a session relay request acknowledge to the second TOF entity in response to receiving the session relay request from the second TOF entity.
  • TOF traffic offloading function
  • Example 43 may comprise the machine-readable medium of any one of Examples 31 to 42or some other example (s) herein, having instructions, stored thereon, that, when executed cause the first traffic offloading function (TOF) entity further to, in response to determining that one or more of a destination address, a destination port number and a protocol number in a packet from the service server relate to the inter-TOF point tunnel, transmit the packet to the second TOF entity via the inter-TOF point tunnel.
  • TOF traffic offloading function
  • Example 44 may comprise the machine-readable medium of any one of Examples 31 to 43 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the first traffic offloading function (TOF) entity further to receive a packet from the second TOF entity via the inter-TOF point tunnel, wherein one or more of a source address, a source port number and a protocol number in the packet from the second TOF entity is associated with the inter-TOF point tunnel; and send the packet from the second TOF entity to the service server.
  • TOF traffic offloading function
  • Example 45 may comprise a machine-readable medium having instructions, stored thereon, that, when executed cause a domain name system (DNS) to receive from a first traffic offloading function (TOF) entity a DNS request associated with a user equipment (UE) , wherein the DNS request comprises a source address corresponding to a global IP address of a first TOF entity; and retrieve a mapping table to obtain an IP address of a first application server (AS) , in response to determining that a service requested in the DNS request is deployed in the first AS, wherein the mapping table to comprise a mapping between a set of one or more global IP address of the first TOF entity and a set of one or more IP address of the first AS;
  • DNS domain name system
  • TOF traffic offloading function
  • UE user equipment
  • AS application server
  • Example 46 may comprise the machine-readable medium of Example 45 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the DNS further to transmit the IP address of the first AS in a DNS response to the first TOF entity.
  • Example 47 may comprise the machine-readable medium of any one of Examples 45 to 46 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the DNS further to in response to determining that the service requested by the DNS request is unavailable in the first AS and is available in a second AS, update the mapping table to include a mapping between the global IP address of the first TOF entity and the IP address of the second AS.
  • Example 48 may comprise the machine-readable medium of any one of Examples 45 to 47 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the DNS further to retrieve the mapping table to obtain the IP address of the second AS.
  • Example 49 may comprise the machine-readable medium of any one of Examples 45 to 48 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the DNS further to transmit to the first TOF entity a DNS response to comprise the IP address of the second AS, in response to determining that a service requested by the DNS request is available in the second AS.
  • Example 50 may comprise a machine-readable medium having instructions, stored thereon, that, when executed cause a user equipment (UE) to transmit to a first base station a domain name system (DNS) request associated with a service for the UE; and receive from the first base station a DNS response that to indicate an Internet Protocol (IP) address of a first application server (AS) that to provide the service for the UE; and initiate a service session with the first AS based on the IP address of the first AS.
  • DNS domain name system
  • IP Internet Protocol
  • AS application server
  • Example 51 may comprise the machine-readable medium of Example 50 or some other example (s) herein, wherein the DNS request to comprise a user datagram protocol (UDP) packet with a destination address destined to a DNS.
  • UDP user datagram protocol
  • Example 52 may comprise the machine-readable medium of any one of Examples 50 to 51 or some other example (s) herein, wherein the DNS response to comprise a user datagram protocol (UDP) packet with a source address of the DNS.
  • UDP user datagram protocol
  • Example 53 may comprise the machine-readable medium of any one of Examples 50 to 52 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the UE further to initiate a service session with a second application server (AS) in response to the transceiver receiving from the first base station the DNS response that to comprise an IP address of the second AS, wherein the second AS to provide the service for the UE in response to the service for the UE being unavailable in the first AS.
  • AS application server
  • Example 54 may comprise the machine-readable medium of any one of Examples 50 to 53 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the UE further to initiate a communication with a second base station in response to a handover from the first base station to the second base station.
  • Example 55 may comprise the machine-readable medium of any one of Examples 50 to 54 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the UE further to in response to a handover from a first traffic offloading function (TOF) entity to a second TOF entity, initiate a communication with a second TOF entity that to communicate with the first TOF entity via an inter-TOF tunnel between the first TOF entity and the second TOF entity.
  • TOF traffic offloading function
  • Example 56 may comprise a machine-readable medium having instructions, stored thereon, that, when executed cause a base station to transform a first user datagram protocol (UDP) packet of a domain name system (DNS) request from a user equipment (UE) into a first general packet radio service (GPRS) tunneling protocol user plane (GTP-U) packet; and transmit the first GTP-U packet to a first traffic offloading function (TOF) entity and to receive from the first TOF entity a second GTP-U packet of a DNS response that to comprise an internet protocol (IP) address of an application server (AS) .
  • UDP user datagram protocol
  • DNS domain name system
  • GTP-U general packet radio service
  • TOF traffic offloading function
  • IP internet protocol
  • AS application server
  • Example 57 may comprise the machine-readable medium of Example 56 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the base station further to in response to transforming the second GTP-U packet into a second UDP packet, transmit the second UDP packet to the UE.
  • Example 58 may comprise the machine-readable medium of any one of Examples 56 to 57 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the base station further to transmit a session migration request to a second TOF in response to a handover from the first TOF entity to the second TOF entity, wherein the session migration request to comprise one or more information elements in a group that to comprise context information of the second TOF entity, an IP address of the second TOF entity, the port number for the inter-TOF point tunnel, an IP address of the UE, .
  • Example 59 may comprise the machine-readable medium of any one of Examples 56 to 58 or some other example (s) herein, having instructions, stored thereon, that, when executed cause the base station further to receive a session migration request acknowledge from the second TOF entity.
  • Example 60 may include an apparatus comprising control circuitry, transmit circuitry, and/or receive circuitry to perform one or more elements of an apparatus of a TOF, a DNS, a UE or an eNB described in or related to any of examples 1-59 and/or any other embodiments described herein.
  • Example 61 may include a method as shown and described herein and/or comprising one or more elements described in or related to any of examples 1-60 and/or any other method or process described herein.
  • Example 62 may include a wireless communication system as shown and described herein and/or comprising one or more elements of a TOF, a DNS, a UE or an eNB described in or related to any of examples 1-61 and/or any other embodiments described herein.
  • Example 63 may include a wireless communication device as shown and described herein and/or comprising one or more elements of a TOF, a DNS, a UE or an eNB described in or related to any of examples 1-62 and/or any other embodiments described herein.
  • modules or units may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • a module or unit may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
  • Modules or units may also be implemented in software for execution by various types of processors.
  • An identified module or unit of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executable code of an identified module or unit need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module or unit and achieve the stated purpose for the module or unit.
  • a module or unit of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
  • operational data may be identified and illustrated herein within modules or units, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
  • the modules or units may be passive or active, including agents operable to perform desired functions.
  • FIGs. 3-5 are illustrated to comprise a sequence of processes, the methods in some embodiments may perform illustrated processes in a different order.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon la présente invention, l'appareil d'une fonction de déchargement de trafic (TOF) peut comprendre un processeur servant à détecter l'adresse de destination d'un trafic associé à un équipement utilisateur (UE) à partir d'une première station de base et à déterminer s'il faut décharger le trafic de la première station de base dans un premier serveur ou dans un second serveur sur la base de l'adresse de destination ; et un émetteur couplé au processeur, servant à transmettre le trafic au premier serveur en réponse à la détermination par le processeur que l'adresse de destination du trafic est destinée au premier serveur et à transmettre le trafic au second serveur en réponse à la détermination par le processeur que le trafic qui n'est pas destiné au premier serveur répond à une politique de branchement local.
PCT/CN2016/079086 2016-04-12 2016-04-12 Solution de branchement local dans un réseau cellulaire WO2017177381A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201680083723.XA CN109076415B (zh) 2016-04-12 2016-04-12 用于业务卸荷功能的方法及装置
PCT/CN2016/079086 WO2017177381A1 (fr) 2016-04-12 2016-04-12 Solution de branchement local dans un réseau cellulaire
TW106107249A TWI728062B (zh) 2016-04-12 2017-03-06 用於在蜂巢式網路中本地分匯的解決方案

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/079086 WO2017177381A1 (fr) 2016-04-12 2016-04-12 Solution de branchement local dans un réseau cellulaire

Publications (1)

Publication Number Publication Date
WO2017177381A1 true WO2017177381A1 (fr) 2017-10-19

Family

ID=60041284

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/079086 WO2017177381A1 (fr) 2016-04-12 2016-04-12 Solution de branchement local dans un réseau cellulaire

Country Status (3)

Country Link
CN (1) CN109076415B (fr)
TW (1) TWI728062B (fr)
WO (1) WO2017177381A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3503508A1 (fr) * 2017-12-21 2019-06-26 Orange Procédé de traitement de requêtes et serveur proxy

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111988227B (zh) * 2019-05-24 2023-05-09 中兴通讯股份有限公司 一种流量处理方法及相关设备、建立转发表的方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120182940A1 (en) * 2009-08-20 2012-07-19 Nec Europe Ltd. Method for controlling the traffic within a network structure and a network structure
CN102843727A (zh) * 2011-06-24 2012-12-26 中兴通讯股份有限公司 Ip分流连接处理方法、装置及系统
CN102891900A (zh) * 2012-09-19 2013-01-23 邦讯技术股份有限公司 一种在流量卸载时域名解析的方法、装置及系统
CN103139915A (zh) * 2011-11-23 2013-06-05 中兴通讯股份有限公司 一种对本地卸载数据进行资源控制的方法和系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8477724B2 (en) * 2010-01-11 2013-07-02 Research In Motion Limited System and method for enabling session context continuity of local service availability in local cellular coverage
WO2011095358A1 (fr) * 2010-02-05 2011-08-11 Nec Europe Ltd. Procédé de routage d'un trafic à l'intérieur d'un réseau et réseau
EP2606631B1 (fr) * 2010-08-17 2019-02-27 Telefonaktiebolaget LM Ericsson (publ) Technique de traitement du trafic réseau qui a été envoyé sur un tunnel
CN102958128B (zh) * 2011-08-16 2015-11-25 华为终端有限公司 为ue业务选择pdn连接的方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120182940A1 (en) * 2009-08-20 2012-07-19 Nec Europe Ltd. Method for controlling the traffic within a network structure and a network structure
CN102843727A (zh) * 2011-06-24 2012-12-26 中兴通讯股份有限公司 Ip分流连接处理方法、装置及系统
CN103139915A (zh) * 2011-11-23 2013-06-05 中兴通讯股份有限公司 一种对本地卸载数据进行资源控制的方法和系统
CN102891900A (zh) * 2012-09-19 2013-01-23 邦讯技术股份有限公司 一种在流量卸载时域名解析的方法、装置及系统

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3503508A1 (fr) * 2017-12-21 2019-06-26 Orange Procédé de traitement de requêtes et serveur proxy
FR3076141A1 (fr) * 2017-12-21 2019-06-28 Orange Procede de traitement de requetes et serveur proxy
US10999360B2 (en) 2017-12-21 2021-05-04 Orange Method of processing requests, and a proxy server

Also Published As

Publication number Publication date
TW201810994A (zh) 2018-03-16
CN109076415B (zh) 2021-09-10
TWI728062B (zh) 2021-05-21
CN109076415A (zh) 2018-12-21

Similar Documents

Publication Publication Date Title
US11343861B2 (en) Layer 2 relay protocols and mobility relay method
TWI707563B (zh) 用於有效率資料傳輸的行動物聯網架構
US10708973B2 (en) Cellular internet of things (CIoT) optimizations for narrowband (NB) and non-NB IoT networks
CN107258107B (zh) 用于支持扩展非连续接收机制的移动性管理实体、用户设备和方法
KR102132101B1 (ko) 5세대 셀룰러 아키텍처용 사용자 평면
US10511418B2 (en) Measurement method in carrier aggregation and asynchronous dual connectivity
US20180083684A1 (en) Carrier aggregation enhancement
US11770692B2 (en) Enhancements for radio access capability signaling (RACS)
WO2017189176A2 (fr) Protocoles génériques multi-accès pour réseaux multi-accès de nouvelle génération
US10791588B2 (en) Timer configuration techniques for coverage enhancement
US20200015243A1 (en) System and method for dynamic marking for internet protocol bearer splitting
WO2017082955A1 (fr) Communication d'ue directe améliorée
WO2017078789A1 (fr) Solution pour prendre en charge de multiples zones de rapport de présence pour une connexion à un réseau de données public
WO2017177381A1 (fr) Solution de branchement local dans un réseau cellulaire
JP7013423B2 (ja) ハンドオーバーでのアップリンクベアラーバインディング
WO2017142575A1 (fr) Reconfiguration de taille d'unité de transmission maximale (mtu) pour une opération lwip
US11638135B2 (en) Core network design for mission-critical IoT
WO2017078794A1 (fr) Solution pour fonction de commande de session d'appel avec mandataire
US20240283771A1 (en) Method for Sending DNS Message, Terminal, and Network-Side Device
WO2018063276A1 (fr) Sélection et resélection de trajet en plan u pour une communication d'ue à ue
WO2017111781A1 (fr) Architecture de porteuse de système de paquet évolué (eps) basée sur un groupe
KR20230172598A (ko) 통신 방법 및 장치, 저장 매체, 및 칩 시스템

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16898200

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16898200

Country of ref document: EP

Kind code of ref document: A1