WO2018063276A1

WO2018063276A1 - U-plane path selection and reselection for ue to ue communication

Info

Publication number: WO2018063276A1
Application number: PCT/US2016/054640
Authority: WO
Inventors: Yifan Yu
Original assignee: Intel Corporation
Priority date: 2016-09-30
Filing date: 2016-09-30
Publication date: 2018-04-05

Abstract

An apparatus is configured to be employed within an evolved Node B (eNodeB). The apparatus includes control circuitry. The control circuitry is configured to detect UE to UE communications, identify a remote eNodeB, request establishment of an inter-eNodeB tunnel and remap the UE to UE communications to utilize the inter-eNodeB tunnel.

Description

U-PLANE PATH SELECTION AND RESELECTION FOR UE TO UE

COMMUNICATION

FIELD

[0001] The present disclosure relates to mobile communication, including proximity communications.

BACKGROUND

[0002] Mobile communications, including cellular communications, involve the transfer of data between two mobile devices. The use of mobile communication is continuously increasing. Additionally, the bandwidth or amount of data used for mobile communications is continuously increasing.

[0003] In one approach, a first device establishes communications with a second device by using base stations and a central network or service gateway. The first device acquires a cell from a first base station, which communicates over a central network or the gateway with a second base station. The second device establishes a cell with the second base station. Thus, a cellular communication path is established for communication or transfer of data between the first and second devices.

[0004] The cellular path typically includes uplink and downlink communications between the first device and the first base station, uplink and downlink communications between the second device and the second base station and utilizes substantial base station resources and central network resources.

[0005] Thus, substantial resources are required for the mobile communications. The use of the substantial resources can limit connections and reduce available or usable bandwidth.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Fig. 1 is a diagram illustrating an arrangement for UE to UE communications.

[0007] Fig. 2 is a diagram illustrating a path selection procedure for UE to UE communications in accordance with an embodiment.

[0008] Fig. 3 is a diagram illustrating an example remapping for data packets for UE to UE communications.

[0009] Fig. 4 is a flow diagram illustrating a method of discovering or detecting UE to UE communications by an eNodeB. [0010] Fig. 5 is a flow diagram illustrating a method of establishing an inter-eNodeB tunnel for UE to UE communications in accordance with an embodiment.

[0011] Fig. 6 illustrates example components of a User Equipment (UE) device.

DETAILED DESCRIPTION

[0012] The present disclosure will now be described with reference to the attached drawing figures, wherein like reference numerals are used to refer to like elements throughout, and wherein the illustrated structures and devices are not necessarily drawn to scale. As utilized herein, terms "component," "system," "interface," and the like are intended to refer to a computer-related entity, hardware, software (e.g., in execution), and/or firmware. For example, a component can be a processor (e.g., a

microprocessor, a controller, or other processing device), a process running on a processor, a controller, an object, an executable, a program, a storage device, a computer, a tablet PC, an electronic circuit and/or a mobile phone with a processing device. By way of illustration, an application running on a server and the server can also be a component. One or more components can reside within a process, and a component can be localized on one computer and/or distributed between two or more computers. A set of elements or a set of other components can be described herein, in which the term "set" can be interpreted as "one or more."

[0013] Further, these components can execute from various computer readable storage media having various data structures stored thereon such as with a module, for example. The components can communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network, such as, the Internet, a local area network, a wide area network, or similar network with other systems via the signal).

[0014] As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, in which the electric or electronic circuitry can be operated by a software application or a firmware application executed by one or more processors. The one or more processors can be internal or external to the apparatus and can execute at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts; the electronic components can include one or more processors therein to execute software and/or firmware that confer(s), at least in part, the functionality of the electronic components.

[0015] Use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless specified otherwise, or clear from context, "X employs A or B" is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied under any of the foregoing instances. In addition, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms "including", "includes", "having", "has", "with", or variants thereof are used in either the detailed description and the claims, such terms are intended to be inclusive in a manner similar to the term

"comprising".

[0016] As used herein, 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. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware.

[0017] One approach used for mobile communication is to establish a path through a packet gateway (PGW). The path includes uplink (UL) and downlink (DL)

communications between a first device and a first base station, establishment of communications between the first base station and a second base station via a core or central network and establishment of communications between the second base station and a second device. This path for communication requires substantial resources. Furthermore, traffic load of the core or central network can degrade communications in terms of latency and/or connectivity.

[0018] One technique to avoid the traffic load and latency of using the core network is to use Proximity based Services (ProSe). This service allows devices in close proximity to conduct direct communication or locally routed communication with network assisted discovery. This approach uses location registration to an evolved packet core (EPC) network by a user equipment (UE) so that its location can be tracked by a network entity or function. Communication with other UEs in the proximity of the UE is enabled after the discovery process, which includes sharing target information among UEs. A third party Application Server (AS) registers applications requesting the UE to UE communications to the ProSe function.

[0019] The ProSe based technique avoids latency and load resulting from use of the core network. However, the technique requires UE devices to be within an evolved Node B to support the UE to UE communication. Additionally, the ProSe technique introduces interaction involving the UE, the third party AS and the ProSe function, which requires complex signaling messages to be exchanged. Additionally, signaling for the ProSe technique should be delivered over a U-plane of the UE, which also leads to additional radio resource consumption. The third party AS is also required to be modified to support the signaling within the ProSe function. In addition, updates to the UE and the mobility management entity (MME) are required to implement the ProSe function.

[0020] Various embodiments and variations thereof are disclosed that facilitate UE to UE communication. One or more evolved Node B (eNodeB)s are present and identify UE candidates for performing cellular communications without a core/central network. Without modification to the UEs, UEs are selected from the identified candidates and perform communication via the one or more eNodeBs using tunnels without using the core/central network.

[0021] Fig. 1 is a diagram illustrating an arrangement 100 for UE to UE

communications. The arrangement 100, which can also be an apparatus, facilitates communications by omitting use of a central network while using only evolved Node Bs (eNodeBs). As a result, overhead and latency can be reduced while increasing bandwidth.

[0022] The arrangement 100 includes an evolved Node B (eNodeB) 102, a transceiver 106, a user equipment (UE) 1 10 and a second or additional eNodeB 1 12. Although not shown, other components such as a packet gateway (PGW), a secondary gateway (SGW), a mobility management entity (MME), a packet data network (PDN), other UEs, other eNodeBs, and the like. The eNodeB can also be abbreviated as eNB.

[0023] The eNodeB 102 includes its transceiver 106, a storage component 1 1 8, and control circuitry or controller 104. The storage component 1 18 includes a memory, storage element and the like and is configured to store information for the eNodeB 102. The controller 104 is configured to perform various operations associated with the eNodeB 102. The controller 1 04 can include logic, components, circuitry, one or more processors and the like. The transceiver 106 includes transmitter functionality and receiver functionality. The eNodeB 102 also includes one or more antenna 1 08 for communications, which include communications 1 14 with the UEs 1 1 0, communications with other eNodeBs and other network devices.

[0024] The eNodeB 102 is configured to coordinate and establish communications via a packet gateway (PGW) or central network. Additionally, the eNodeB 102 is configured to establish and/or coordinate UE to UE communications with/for the group of UEs 1 10. The communications via the PGW utilize a single user plane (U-plane) path. However, the UE to UE communications can utilize a variety of U-plane paths. Thus, the eNodeB 102 is also configured to coordinate U-plane path selection for the UE to UE communications. In one example, the eNodeB 102 is configured to determine metrics for a plurality of U-plane paths and select a path for UE to UE communication based on the determined metrics.

[0025] The group of UEs 1 10 include UEs assigned or associated with the eNodeB 102. The UEs within the group can vary over time, for example, as UEs move within or out of range of the eNodeB. The UEs 1 10 typically include control circuitry or controller, a storage component and a transceiver. The storage component of the UEs includes a memory, storage element and the like and is configured to store information. The controller/control circuitry is configured to perform various operations. The controller can include logic, components, circuitry, one or more processors and the like. The transceiver includes transmitter functionality and receiver functionality.

[0026] The UEs 1 10 are configured to communicate with other UEs using the eNodeB 102. The UEs 1 10 establish UE to UE communications with other UEs.

[0027] The second eNodeB 1 12 is substantially similar to the eNodeB 102 and includes similar components, such as a storage element, controller and transceiver. There is a second group of UEs associated with the second eNodeB 1 12.

[0028] The eNodeB 102 is configured to establish UE to UE communications between members or UEs of the group. The eNodeB 102 is also configured to establish UE to UE communications with other UEs by establishing a tunnel 1 18 with another eNodeB, such as the second eNodeB.

[0029] The eNodeB 102 is configured to detect UE to UE communication of the group 1 10. In one example, the eNodeB 102 launches a query to a mobility management entity (MME) 122 upon detecting the UE to UE communication. The query includes information derived from the detected UE to UE communication, such as a source IP address. The MME 122 is a signaling node in an evolved packet core (EPC). Typically, the MME 122 is configured to initiate paging and authentication of UEs. The MME 122 also connects to the eNodeB 102 via an interface, such as an S1 - MME interface. Other MMEs can be present.

[0030] The query is for the acquisition of a Transport Layer Address of an eNodeB, where a remote UE of the UE to UE communication resides. The query can include a unique identification for the remote UE, such as a MME UE S1 Application Part (S1 AP) identification (ID). The S1 AP is a signaling service for the EPC that fulfils interface functions and the like. The unique identification can be acquired in a PDN connectivity setup procedure. The MME 122 responds/answers with the Transport Layer Address for the remote UE. The Transport Layer Address is available in the MME 122 after PDN connectivity is established and identifies another eNodeB, such as the second eNodeB 1 1 2. The eNodeB 102 is configured to initiate U-plane path selection once the

Transport Layer Address is obtained.

[0031] The eNodeB 102 facilitates or handles UE to UE communication without assistance for other entities or User plane entities, such as local gateways (LGW) and the like. The UE to UE communications includes UEs not covered by the same LGW, for example UEs that reside at a boundary of cells connected to different LGWs.

[0032] LGW enabled UE to UE communications utilize the PDN connection established by the UE tunnel establishment request with a specific APN.

[0033] Fig. 2 is a diagram illustrating a path selection procedure for UE to UE communications 200 in accordance with an embodiment. The path selection can be performed, for example, by the control circuitry 104 and/or the arrangement 1 00, described above. The diagram is provided as an example and is for illustrative purposes. It is appreciated that suitable variations are contemplated.

[0034] The path selection is described in conjunction with an arrangement that includes a UE A 202, an eNodeB A 204, a serving gateway (SGW) A 206, a packet gateway (PGW) 208, a SGW B 210, an eNodeB B 212 and a UE B 214.

[0035] The UE A 202 resides in or is associated with the eNodeB A 204 and the UE B 214 resides in or is associated with the eNodeB B 21 2.

[0036] The eNodeB A 204 then initiates or requests establishment of a tunnel with the eNodeB B 212, which the UE B 214 resides in. In one example, the eNodeB A 204 sends a packet to the eNodeB B 212 that includes the tunnel establishment request, including other information. The packet is sent via interfaces S1 , S5, and S8 through the PGW 208.

[0037] The eNodeB A 204 submits a query to an MME that requests information for establishment of the tunnel between the eNodeB A 204 and the eNodeB B 21 2. The MME response with the requested information, which includes information elements such as MME UE S1 AP ID, UE IP Address, E-RAB List, E-RAB item lEs, E-RAB ID, GTP-TEID. The MME UE S1 AP ID is a unique ID of the UE B 214 in the MME. The UE IP Address is an Internet Protocol (IP) address assigned to the UE B 214. The E-RAB list is a list of E-UTRAN Radio Access Bearers. The E-RAB ID is a unique identification and is provided for each of the E-RABs in the E-RAB list. The E-RAB IDs are contained in the PDN connectivity. A GPRS Tunneling Protocol (GTP) is a group of IP based communications protocols used to carry general packet radio service (GPRS) within GSM, UMTS and LTE networks. The GTP-TEID is a GTP tunneling endpoint identification (TEID). The GTP-TEID identifies the TEID at the eNodeB B 212.

[0038] The eNodeB A 202 obtains metrics associated with the paths between the eNodeB A 202 and the eNodeB 212. The paths include the E-RABs in the E-RAB list. The metrics indicate a cost of a particular path. The metrics can be generated from initial information, such as a hop count, a time stamp and the like. The initial hop count is used to calculate the distance between entities, such as the eNodeB A 202 and the eNodeB B 212 in terms of hop counts. The initial time stamp is used to determine end to end latency between the eNodeB A 202 and the eNodeB B 212. The hop count and time stamps can be used to determine path metrics for the various paths.

[0039] The eNodeB B 21 2 receives the tunnel establishment request and determines or obtians path metrics. In one example, the path metrics include three metrics; M_x, M_c and M_n. The M_x denotes the costs of the path between the eNodeB A 202 and the eNodeB B 212. The M_c denotes the cost of the path between the eNodeB A 204 and the PGW 208. The M_n denotes the cost of the path between the eNodeB B 212 and the PGW 208. The M_c can be provided by the eNodeB A 204 with the tunnel establishment request.

[0040] The path metric M_x is calculated based on a measurement associated with reception of the tunnel establishment request. If an initial metric is indicated as the hop counts, M_x = the initial metric - TTL, where TTL is a field contained within an IP packet that carries the tunnel establishment request. [0041] If the path metrics for establishment of the tunnel are suitable, such as less than the path metrics for communication via the PGW 208, the tunnel is allowed to be established. The tunnel is also referred to as an inter-eNodeB tunnel. Otherwise, the tunnel establishment procedure is terminated and the eNodeB B 212 sends a reject message using a packet via the PGW 208. On receiving the reject message, the eNodeB A 204 establishes communication using a user plane and path via the PGW 208.

[0042] Once the tunnel is established, user plane traffic can be delivered between the UE A 202 and the UE B 214 without passing through the PGW 208, the SGW 206, and/or the SGW 210. The user plane traffic typically includes IP packets. The eNodeB A 204 and the eNodeB B 212 perform packet remapping to redirect packets through the tunnel instead of the PGW 208. In one example, the eNodeBs 204 and 212 perform TEID and DAB-ID remapping. Existing bearers/interfaces, such as the S1 , S5 and S8 are not deleted.

[0043] After establishment of the tunnel, the user plan traffic destined for the other UE can be delivered using the more efficient path, using the tunnel, without passing through the PGW 208.

[0044] For illustrative purposes, the path selection is shown with particular components. However, the path selection procedure can be utilized between other eNodeBs and UEs.

[0045] The eNodeB 102 facilitates or handles UE to UE communication without assistance for other entities or User plane entities, such as local gateways (LGW) and the like. The UE to UE communications includes UEs not covered by the same LGW, for example UEs that reside at a boundary of cells connected to different LGWs.

[0046] LGW enabled UE to UE communications utilize the PDN connection established by the UE tunnel establishment request with a specific APN.

[0047] Fig. 3 is a diagram illustrating an example remapping 300 for data packets for UE to UE communications. Fig. 3 is described in conjunction with the arrangement of Fig. 2.

[0048] At this point, an inter-eNodeB tunnel has been established between the eNodeB A 204 and the eNodeB B 212 for UE to UE communications between the UE A 202 and the UE B 214.

[0049] In this example, the eNodeBs 204 and 212 have MME UE S1 AP ID and the E-RAB ID list, typically obtained from the tunnel establishment request. The eNodeBs 204 and 212 can create the TEID and the digital access bearer identification (DAB-ID) remapping uniquely oriented to each E-RAB bearer running over the prevous user plane path through the PGW. Thus, uplink user plan traffic associated with the E-RAB ID for the UEs is forwarded through the inter-eNodeB tunnel and the user plane traffic retrieved from the inter-eNodeB tunnel is forwarded through the downlink DRB associated with the E-RAB ID of the remote UE.

[0050] The inter-eNodeB tunnel is bidirectional and identified with X-ID.

[0051] There can be a plurality of tunnels between eNodeBs. Each tunnel is associated with an E-RAB ID.

[0052] In a situation where the tunnel establishment request including the E-RAB ID is associated with a remote UE resiging in the same eNodeB, the request is rejected. The eNodeB creates a direct DAB-ID to DAB-ID remapping for the user plane traffic delivery. Additionally, the UE to UE communication detection can include source IP address checking, for example after the GPRS tunneling protocol (GTP) decapsulation is disabled in the inter-eNodeB tunnel.

[0053] The inter-eNodeB tunnel is terminated as the associated E-RAB is deleted in one of the eNodeBs 204 and 212. Without the tunnel, packets between the UE A 202 and the UE B 214 are delivered through the PGW.

[0054] Fig. 4 is a flow diagram illustrating a method 400 of discovering or detecting UE to UE communications by an eNodeB. The method 400 is provided as an example and it is appreciated that suitable variations are contemplated. The method 400 can be used with the arrangement 100 and variations thereof.

[0055] A network prefix of an IP address set assigned to UEs in a network is previously known by the eNodeB. Thus, the network prefix can identify a remote eNodeB, identify packets sent or designated to UEs assigned to the eNodeB, and the like.

[0056] The eNodeB analyzes downlink communications to UEs assigned to the eNodeB at block 401 . The downlink communications utilize a GTP tunnel. An IP packet is checked to see if the IP source address belongs to an SGW. If the IP packet is from the SGW, the method moves to block 402.

[0057] At block 402, the IP source address of the downlink communication is analyzed with a network prefix for the network. If the IP source address has a matching network prefix, the associated UE is on the same network as the destination UE. The same network includes that the source UE is assigned to the remote eNodeB. Thus, a new UE to UE communication is discovered at 403 and the UE to UE communication can utilize an inter-eNodeB tunnel.

[0058] The eNodeB generates a query at 404 and sends the query to an MME. The query requests information for requesting establishment of an inter-eNodeB tunnel. The query requested information includes, for example, a transport layer address of the remote eNodeB where the source UE is assigned. The query includes identification of the source UE including, for example, the MME UE S1 AP ID acquired in a PDN connectivity setup procedure. The MME responds with the transport layer address. The eNodeB then sends the remote eNodeB a request for establishment of an inter- eNodeB tunnel. The eNodeB and/or the remote eNodeB can perform user plan path selection as described above and establish the inter-eNodeB tunnel between the eNodeB and the remote eNodeB.

[0059] The method 400 is described in terms of downlink communications between the source UE and the local or destination UE assigned to the eNodeB. It is also appreciated that the method can be applied to uplink communications between a local UE assigned to the eNodeB and a destination UE assigned to the remote eNodeB.

[0060] Fig. 5 is a flow diagram illustrating a method 500 of establishing an inter- eNodeB tunnel for UE to UE communications in accordance with an embodiment. The method 500 detects UE to UE communications and determines whether use of the tunnel is suitable. If so, the tunnel is established and used for the UE to UE

communications.

[0061] The method 500 can be performed with the arrangements and apparatuses described above and variations thereof.

[0062] The method 500 begins at block 502, where a local eNodeB detects UE to UE communications. The UE to UE communications are between a local UE assigned to the local eNodeB and a remote UE assigned to a remote UE.

[0063] The local eNodeB determines whether the remote UE is on the same network as the local UE at block 504. In one example, the UE to UE communications involve a downlink communication to the local UE. A source IP address is analysed and its network prefix compared to determine if it is on the same network.

[0064] The local eNodeB submits a query to an MME to identify the remote eNodeB at block 506. The query to the MME utilizes information from the remote UE, such as fields from a packet. The MME responds to the query with an identification for the remote eNodeB. [0065] The local eNodeB sends an inter-eNodeB tunnel establishment request to the remote eNodeB via a packet gateway (PGW) at block 508. The tunnel establishment request can include information regarding paths between the local UE and the remote UE.

[0066] The remote eNodeB determines path metrics for a plurality of user plane paths between the local eNodeB and the remote eNodeB at block 51 0. The path metrics can be determined on information based on the tunnel establishment request. For example, the information can include time to live (TTL) values and/or hop counts for the various user plane paths.

[0067] The remote eNodeB establishes the inter-eNodeB tunnel at block 512. The remote eNodeB establishes the tunnel if the determined path metrics for using the tunnel are below a threshold value, such as a path metric along the PGW. Otherwise, the remote eNodeB rejects the tunnel establishment request. The inter-eNodeB tunnel is typically bi directional.

[0068] The local eNodeB and the remote eNodeB remap packets for the UE to UE communication to travel by the inter-eNodeB tunnel instead of the PGW at block 514.

[0069] It is appreciated that the eNodeBs can terminate or end the inter-eNodeB tunnel at some point in time. It is also appreciataed that other inter-eNodeB tunnels can be established for UE to UE communications between other UEs using other eNodeBs.

[0070] While the methods described within this disclosure are illustrated in and described herein as a series of acts or events, it will be appreciated that the illustrated ordering of such acts or events are not to be interpreted in a limiting sense. For example, some acts may occur in different orders and/or concurrently with other acts or events apart from those illustrated and/or described herein. In addition, not all illustrated acts may be required to implement one or more aspects or embodiments of the description herein. Further, one or more of the acts depicted herein may be carried out in one or more separate acts and/or phases.

[0071] Embodiments described herein can be implemented into a system using any suitably configured hardware and/or software. FIG. 6 illustrates, for one embodiment, example components of a User Equipment (UE) device 600. In some embodiments, the UE device 600 (e.g., the wireless communication device) can include application circuitry 602, baseband circuitry 604, Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608 and one or more antennas 610, coupled together at least as shown. [0072] The application circuitry 602 can include one or more application processors. For example, the application circuitry 602 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors can be coupled with and/or can include memory/storage and can be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

[0073] The baseband circuitry 604 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 604 can include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RF circuitry 606. Baseband processing circuity 604 can interface with the application circuitry 602 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606. For example, in some embodiments, the baseband circuitry 604 can include a second generation (2G) baseband processor 604a, third generation (3G) baseband processor 604b, fourth generation (4G) baseband processor 604c, and/or other baseband processor(s) 604d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 604 (e.g., one or more of baseband processors 604a-d) can handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 606. The radio control functions can include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 604 can include Fast-Fourier Transform (FFT), precoding, and/or constellation

mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 604 can include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.

Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and can include other suitable functionality in other embodiments.

[0074] In some embodiments, the baseband circuitry 604 can include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. A central processing unit (CPU) 604e of the baseband circuitry 604 can be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some embodiments, the baseband circuitry can include one or more audio digital signal processor(s) (DSP) 604f. The audio DSP(s) 604f can be include elements for compression/decompression and echo cancellation and can include other suitable processing elements in other embodiments. Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 604 and the application circuitry 602 can be implemented together such as, for example, on a system on a chip (SOC).

[0075] In some embodiments, the baseband circuitry 604 can provide for

communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 604 can 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). Embodiments in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.

[0076] RF circuitry 606 can enable communication with wireless networks

using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 606 can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 606 can include a receive signal path which can include circuitry to down-convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 604. RF circuitry 606 can also include a transmit signal path which can include circuitry to up- convert baseband signals provided by the baseband circuitry 604 and provide RF output signals to the FEM circuitry 608 for transmission.

[0077] In some embodiments, the RF circuitry 606 can include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 606 can include mixer circuitry 606a, amplifier circuitry 606b and filter circuitry 606c. The transmit signal path of the RF circuitry 606 can include filter circuitry 606c and mixer circuitry 606a. RF circuitry 606 can also include synthesizer circuitry 606d for synthesizing a frequency for use by the mixer circuitry 606a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 606a of the receive signal path can be configured to down-convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d. The amplifier circuitry 606b can be configured to amplify the down-converted signals and the filter circuitry 606c can 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 can be provided to the baseband circuitry 604 for further processing. In some embodiments, the output baseband signals can be zero- frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 606a of the receive signal path can comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0078] In some embodiments, the mixer circuitry 606a of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606d to generate RF output signals for the FEM circuitry 608. The baseband signals can be provided by the baseband circuitry 604 and can be filtered by filter circuitry 606c. The filter circuitry 606c can include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

[0079] In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path can include two or more mixers and can be arranged for quadrature downconversion and/or upconversion respectively. In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path can include two or more mixers and can be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a can be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path can be configured for super-heterodyne operation.

[0080] In some embodiments, the output baseband signals and the input baseband signals can be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals can be digital baseband signals. In these alternate embodiments, the RF circuitry 606 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 604 can include a digital baseband interface to communicate with the RF circuitry 606.

[0081] In some dual-mode embodiments, a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the

embodiments is not limited in this respect.

[0082] In some embodiments, the synthesizer circuitry 606d can be a fractional-N synthesizer or a fractional N/N+8 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers can be suitable. For example, synthesizer circuitry 606d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0083] The synthesizer circuitry 606d can be configured to synthesize an output frequency for use by the mixer circuitry 606a of the RF circuitry 606 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 606d can be a fractional N/N+8 synthesizer.

[0084] In some embodiments, frequency input can be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input can be provided by either the baseband circuitry 604 or the applications processor 602 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) can be determined from a look-up table based on a channel indicated by the applications processor 602.

[0085] Synthesizer circuitry 606d of the RF circuitry 606 can include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some

embodiments, the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA). In some embodiments, the DMD can be configured to divide the input signal by either N or N+8 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements can 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. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0086] In some embodiments, synthesizer circuitry 606d can be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can 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. In some embodiments, the output frequency can be a LO frequency (f|_o)- In some embodiments, the RF circuitry 606 can include an IQ/polar converter.

[0087] FEM circuitry 608 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 680, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing. FEM circuitry 608 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of the one or more antennas 610.

[0088] In some embodiments, the FEM circuitry 608 can include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry can 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 606). The transmit signal path of the FEM circuitry 608 can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 680.

[0089] In some embodiments, the UE device 600 can include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.

[0090] It is appreciated that the described application circuitry 602, baseband circuitry 604, Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608 and one or more antennas 610 can also be utilized with an evolved Node B (eNodeB).

[0091] Examples herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine (e.g., a processor with memory or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to embodiments and examples described. [0092] Example 1 is an apparatus configured to be employed within an evolved Node B (eNodeB). The apparatus includes control circuitry. The control circuitry is configured to detect UE to UE communications, identify a remote eNodeB, request establishment of an inter-eNodeB tunnel; and remap the UE to UE communications to utilize the inter-eNodeB tunnel.

[0093] Example 2 includes the subject matter of Example 1 , including or omitting optional elements, where the control circuitry is further configured to determine path metrics for a plurality of user paths.

[0094] Example 3 includes the subject matter of any of Examples 1 -2, including or omitting optional elements, where the control circuitry is further configured to select a path using the inter-eNodeB tunnel based on the path metrics for the plurality of user paths.

[0095] Example 4 includes the subject matter of any of Examples 1 -3, including or omitting optional elements, where the control circuitry is further configured to query a mobility management entity (MME) with identification of a remote UE to identify the remote eNodeB.

[0096] Example 5 includes the subject matter of any of Examples 1 -4, including or omitting optional elements, where the control circuitry is further configured to include one or more path metrics in the inter-eNodeB tunnel establishment request.

[0097] Example 6 includes the subject matter of any of Examples 1 -5, including or omitting optional elements, where the control circuitry is configured to compare a source IP packet with a predetermined prefix to determine if a remote UE is part of a network.

[0098] Example 7 includes the subject matter of any of Examples 1 -6, including or omitting optional elements, where the control circuitry is configured to use the source IP packet to identify the remote eNodeB.

[0099] Example 8 includes the subject matter of any of Examples 1 -7, including or omitting optional elements, where the remote eNodeB is identified by a transport layer address.

[00100] Example 9 includes the subject matter of any of Examples 1 -8, including or omitting optional elements, where the remote eNodeB is configured to establish the inter-eNodeB tunnel based on path metrics.

[00101 ] Example 10 includes the subject matter of any of Examples 1 -9, including or omitting optional elements, where the path metrics include a cost from the eNodeB to a packet gateway (PGW), a cost from the remote eNodeB to the packet gateway and a cost from the eNodeB to the remote eNodeB.

[00102] Example 1 1 includes the subject matter of any of Examples 1 -1 0, including or omitting optional elements, where the path metrics are based on hop count.

[00103] Example 12 includes the subject matter of any of Examples 1 -1 1 , including or omitting optional elements, where the path metrics are based on time to live (TTL) values.

[00104] Example 13 is an apparatus configured to be employed within an evolved Node B (eNodeB). The apparatus includes control circuitry configured to receive an inter-eNodeB tunnel establishment request from a requesting eNodeB; determine a plurality of path metrics associated with the requesting eNodeB, the path metrics including an inter-eNodeB path metric from the requesting eNodeB to the eNodeB; and ,on the inter-eNodeB path metric being less than a threshold value, establish an inter- eNodeB tunnel between the requesting eNodeB and the eNodeB without routing through a packet gateway (PGW).

[00105] Example 14 includes the subject matter of Example 13, including or omitting optional elements, where the control circuitry is further configured to remap packets from an assigned UE to transport through the inter-eNodeB tunnel.

[00106] Example 15 includes the subject matter of any of Examples 13-14, including or omitting optional elements, where the path metrics include time to live (TTL) and/or hop counts.

[00107] Example 16 includes the subject matter of any of Examples 13-15, including or omitting optional elements, where the control circuitry is further configured to reject the inter-eNodeB tunnel establishment request on the inter-eNodeB path metric being more than the threshold value.

[00108] Example 17 includes the subject matter of any of Examples 13-16, including or omitting optional elements, where the threshold value is based on a path metric from the eNodeB to the PGW.

[00109] Example 18 is direct to one or more computer-readable media having instructions that, when executed, cause one or more evolved Node Bs (eNodeBs) to detect UE to UE communications between a local UE and a remote UE, where the local UE is assigned to a local eNodeB; determine that the remote UE is within a network used by the local eNodeB; identify a remote eNodeB based on an identification of the remote UE, wherein the remote UE is assigned to the remote eNodeB; generate an inter-eNodeB tunnel establishment request; and establish an inter-eNodeB tunnel between the local eNodeB and the remote eNodeB.

[00110] Example 19 includes the subject matter of Example 18, including or omitting optional elements, where the instructions, when executed, further cause the one or more eNodeBs to determine a plurality of path metrics for a plurality of user plane paths between the local eNodeB and the remote eNodeB.

[00111 ] Example 20 includes the subject matter of any of Examples 18-19, including or omitting optional elements, where the instructions, when executed, further cause the one or more eNodeBs to reject the inter-eNodeB tunnel establishment request based on the determined plurality of path metrics.

[00112] Example 21 is an apparatus configured to be employed within an evolved Node B (eNodeB). The apparatus includes a means to determine a plurality of path metrics associated with a requesting eNodeB in response to an inter-eNodeB tunnel establishment request and a means for establishing an inter-eNodeB tunnel between the requesting eNodeB and the eNodeB without routing through a packet gateway (PGW).

[00113] Example 22 includes the subject matter of Example 21 , including or omitting optional elements, further comprising a means to receive the inter-eNodeB tunnel establishment request.

[00114] Example 23 includes the subject matter of any of Examples 21 -22, including or omitting optional elements, further comprising a means to reject the inter-eNodeB tunnel establishment request based on the determined plurality of path metrics.

[00115] The above description of illustrated embodiments of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. While specific embodiments and examples are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such embodiments and examples, as those skilled in the relevant art can recognize.

[00116] In this regard, while the disclosed subject matter has been described in connection with various embodiments and corresponding Figures, where applicable, it is to be understood that other similar embodiments can be used or modifications and additions can be made to the described embodiments for performing the same, similar, alternative, or substitute function of the disclosed subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single embodiment described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.

[00117] In particular regard to the various functions performed by the above described components or structures (assemblies, devices, circuits, systems, etc.), the terms (including a reference to a "means") used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations of the invention. In addition, while a particular feature may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application.

Claims

CLAIMS What is claimed is:

1 . An apparatus configured to be employed within an evolved Node B (eNodeB), the apparatus comprising:

control circuitry configured to

detect UE to UE communications;

identify a remote eNodeB;

request establishment of an inter-eNodeB tunnel; and

remap the UE to UE communications to utilize the inter-eNodeB tunnel.

2. The apparatus of claim 1 , wherein the control circuitry is further configured to determine path metrics for a plurality of user paths.

3. The apparatus of claim 2, wherein the control circuitry is further configured to select a path using the inter-eNodeB tunnel based on the path metrics for the plurality of user paths.

4. The apparatus of claim 1 , wherein the control circuitry is further configured to query a mobility management entity (MME) with identification of a remote UE to identify the remote eNodeB.

5. The apparatus of claim 1 , wherein the control circuitry is further configured to include one or more path metrics in the inter-eNodeB tunnel establishment request.

6. The apparatus of any one of claims 1 -5, wherein the control circuitry is configured to compare a source IP packet with a predetermined prefix to determine if a remote UE is part of a network.

7. The apparatus of claim 6, wherein the control circuitry is configured to use the source IP packet to identify the remote eNodeB.

8. The apparatus of claim 6, wherein the remote eNodeB is identified by a transport layer address.

9. The apparatus of any one of claims 1 -5, wherein the remote eNodeB is configured to establish the inter-eNodeB tunnel based on path metrics.

10. The apparatus of claim 9, wherein the path metrics include a cost from the eNodeB to a packet gateway (PGW), a cost from the remote eNodeB to the packet gateway and a cost from the eNodeB to the remote eNodeB.

1 1 . The apparatus of claim 10, wherein the path metrics are based on hop count.

12. The apparatus of claim 10, wherein the path metrics are based on time to live (TTL) values.

13. An apparatus configured to be employed within an evolved Node B (eNodeB), the apparatus comprising:

control circuitry configured to:

receive an inter-eNodeB tunnel establishment request from a requesting eNodeB;

determine a plurality of path metrics associated with the requesting eNodeB, the path metrics including an inter-eNodeB path metric from the requesting eNodeB to the eNodeB; and

on the inter-eNodeB path metric being less than a threshold value, establis an inter-eNodeB tunnel between the requesting eNodeB and the eNodeB without routing through a packet gateway (PGW).

14. The apparatus of claim 13, wherein the control circuitry is further configured to remap packets from an assigned UE to transport through the inter-eNodeB tunnel.

15. The apparatus of claim 13, wherein the path metrics include time to live (TTL) and/or hop counts.

16. The apparatus of claim 13, wherein the control circuitry is further configured to reject the inter-eNodeB tunnel establishment request on the inter-eNodeB path metric being more than the threshold value.

17. The apparatus of claim 13, wherein the threshold value is based on a path metric from the eNodeB to the PGW.

18. One or more computer-readable media having instructions that, when executed, cause one or more evolved Node Bs (eNodeBs) to:

detect UE to UE communications between a local UE and a remote UE, where the local UE is assigned to a local eNodeB;

determine that the remote UE is within a network used by the local eNodeB; identify a remote eNodeB based on an identification of the remote UE, wherein the remote UE is assigned to the remote eNodeB;

generate an inter-eNodeB tunnel establishment request; and

establish an inter-eNodeB tunnel between the local eNodeB and the remote eNodeB.

19. The computer-readable media of claim 18, comprising one or more computer- readable media having instructions that, when executed, further cause the one or more eNodeBs to:

determine a plurality of path metrics for a plurality of user plane paths between the local eNodeB and the remote eNodeB.

20. The computer-readable media of claim 18, comprising one or more computer- readable media having instructions that, when executed, further cause the one or more eNodeBs to:

reject the inter-eNodeB tunnel establishment request based on the determined plurality of path metrics.

21 . An apparatus configured to be employed within an evolved Node B (eNodeB), the apparatus comprising:

a means to determine a plurality of path metrics associated with a requesting eNodeB in response to an inter-eNodeB tunnel establishment request; and

a means for establishing an inter-eNodeB tunnel between the requesting eNodeB and the eNodeB without routing through a packet gateway (PGW).