[go: up one dir, main page]

WO2018063276A1 - Sélection et resélection de trajet en plan u pour une communication d'ue à ue - Google Patents

Sélection et resélection de trajet en plan u pour une communication d'ue à ue Download PDF

Info

Publication number
WO2018063276A1
WO2018063276A1 PCT/US2016/054640 US2016054640W WO2018063276A1 WO 2018063276 A1 WO2018063276 A1 WO 2018063276A1 US 2016054640 W US2016054640 W US 2016054640W WO 2018063276 A1 WO2018063276 A1 WO 2018063276A1
Authority
WO
WIPO (PCT)
Prior art keywords
enodeb
inter
remote
tunnel
circuitry
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/US2016/054640
Other languages
English (en)
Inventor
Yifan Yu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
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 Corp filed Critical Intel Corp
Priority to PCT/US2016/054640 priority Critical patent/WO2018063276A1/fr
Publication of WO2018063276A1 publication Critical patent/WO2018063276A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/12—Shortest path evaluation
    • H04L45/122—Shortest path evaluation by minimising distances, e.g. by selecting a route with minimum of number of hops
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/03—Reselecting a link using a direct mode connection
    • H04W36/033—Reselecting a link using a direct mode connection in pre-organised networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/12—Communication route or path selection, e.g. power-based or shortest path routing based on transmission quality or channel quality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/38—Modification of an existing route adapting due to varying relative distances between nodes
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the present disclosure relates to mobile communication, including proximity communications.
  • 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.
  • 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.
  • a cellular communication path is established for communication or transfer of data between the first and second devices.
  • 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.
  • FIG. 1 is a diagram illustrating an arrangement for UE to UE communications.
  • FIG. 2 is a diagram illustrating a path selection procedure for UE to UE communications in accordance with an embodiment.
  • FIG. 3 is a diagram illustrating an example remapping for data packets for UE to UE communications.
  • Fig. 4 is a flow diagram illustrating a method of discovering or detecting UE to UE communications by an eNodeB.
  • 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.
  • Fig. 6 illustrates example components of a User Equipment (UE) device.
  • UE User Equipment
  • 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.
  • 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.”
  • 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).
  • 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).
  • 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.
  • 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.
  • 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 circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • circuitry may include logic, at least partially operable in hardware.
  • PGW packet gateway
  • the path includes uplink (UL) and downlink (DL)
  • Proximity based Services 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.
  • the ProSe based technique avoids latency and load resulting from use of the core network.
  • the technique requires UE devices to be within an evolved Node B to support the UE to UE communication.
  • 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.
  • updates to the UE and the mobility management entity (MME) are required to implement the ProSe function.
  • eNodeB evolved Node B
  • UEs are selected from the identified candidates and perform communication via the one or more eNodeBs using tunnels without using the core/central network.
  • FIG. 1 is a diagram illustrating an arrangement 100 for UE to UE
  • 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.
  • eNodeBs evolved Node Bs
  • 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.
  • eNodeB evolved Node B
  • UE user equipment
  • eNodeB 1 a packet gateway
  • SGW secondary gateway
  • MME mobility management entity
  • PDN packet data network
  • UEs other eNodeBs, and the like.
  • eNodeB can also be abbreviated as eNB.
  • 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.
  • 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.
  • PGW packet gateway
  • U-plane user plane
  • 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
  • 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.
  • 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.
  • 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.
  • the eNodeB 102 is configured to detect UE to UE communication of the group 1 10.
  • 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).
  • EPC evolved packet core
  • 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.
  • 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).
  • 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
  • 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.
  • LGW local gateways
  • 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.
  • LGW enabled UE to UE communications utilize the PDN connection established by the UE tunnel establishment request with a specific APN.
  • 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.
  • 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.
  • SGW serving gateway
  • PGW packet gateway
  • 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.
  • the eNodeB A 204 then initiates or requests establishment of a tunnel with the eNodeB B 212, which the UE B 214 resides in.
  • 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.
  • 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.
  • the eNodeB B 21 2 receives the tunnel establishment request and determines or obtians path metrics.
  • 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.
  • 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.
  • the eNodeBs 204 and 212 perform TEID and DAB-ID remapping.
  • Existing bearers/interfaces, such as the S1 , S5 and S8 are not deleted.
  • 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.
  • the path selection is shown with particular components. However, the path selection procedure can be utilized between other eNodeBs and UEs.
  • 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.
  • LGW local gateways
  • 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.
  • LGW enabled UE to UE communications utilize the PDN connection established by the UE tunnel establishment request with a specific APN.
  • 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.
  • 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.
  • DRB-ID digital access bearer identification
  • the inter-eNodeB tunnel is bidirectional and identified with X-ID.
  • Each tunnel can be a plurality of tunnels between eNodeBs. Each tunnel is associated with an E-RAB ID.
  • the request is rejected.
  • the eNodeB creates a direct DAB-ID to DAB-ID remapping for the user plane traffic delivery.
  • 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.
  • GTP GPRS tunneling protocol
  • 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.
  • 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.
  • a network prefix of an IP address set assigned to UEs in a network is previously known by the eNodeB.
  • the network prefix can identify a remote eNodeB, identify packets sent or designated to UEs assigned to the eNodeB, and the like.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • the method 500 can be performed with the arrangements and apparatuses described above and variations thereof.
  • 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.
  • the local eNodeB determines whether the remote UE is on the same network as the local UE at block 504.
  • 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.
  • 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.
  • the local eNodeB sends an inter-eNodeB tunnel establishment request to the remote eNodeB via a packet gateway (PGW) at block 508.
  • PGW packet gateway
  • the tunnel establishment request can include information regarding paths between the local UE and the remote UE.
  • 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.
  • the information can include time to live (TTL) values and/or hop counts for the various user plane paths.
  • TTL time to live
  • 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.
  • 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.
  • 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.
  • FIG. 6 illustrates, for one embodiment, example components of a User Equipment (UE) device 600.
  • the UE device 600 e.g., the wireless communication device
  • the UE device 600 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.
  • the application circuitry 602 can include one or more application processors.
  • 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.
  • 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.
  • 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
  • the radio control functions can include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 604 can include Fast-Fourier Transform (FFT), precoding, and/or constellation
  • 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.
  • LDPC Low Density Parity Check
  • Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and can include other suitable functionality in other embodiments.
  • 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.
  • 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).
  • SOC system on a chip
  • the baseband circuitry 604 can provide for
  • 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).
  • 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 604 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 606 can enable communication with wireless networks
  • 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.
  • 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.
  • 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.
  • LPF low-pass filter
  • BPF band-pass filter
  • Output baseband signals can be provided to the baseband circuitry 604 for further processing.
  • the output baseband signals can be zero- frequency baseband signals, although this is not a requirement.
  • mixer circuitry 606a of the receive signal path can comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • the output baseband signals and the input baseband signals can be digital baseband signals.
  • 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.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the
  • 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.
  • synthesizer circuitry 606d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • 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.
  • the synthesizer circuitry 606d can be a fractional N/N+8 synthesizer.
  • frequency input can be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input can be provided by either the baseband circuitry 604 or the applications processor 602 depending on the desired output frequency.
  • a divider control input e.g., N
  • N can be determined from a look-up table based on a channel indicated by the applications processor 602.
  • Synthesizer circuitry 606d of the RF circuitry 606 can include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • DLL delay-locked loop
  • the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA).
  • 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.
  • the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • 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.
  • 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.
  • the output frequency can be a LO frequency (f
  • the RF circuitry 606 can include an IQ/polar converter.
  • 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.
  • 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).
  • LNA low-noise amplifier
  • 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.
  • PA power amplifier
  • the UE device 600 can include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.
  • additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.
  • RF Radio Frequency
  • FEM front-end module
  • eNodeB evolved Node B
  • 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.
  • 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.
  • 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.
  • 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.
  • MME mobility management entity
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • PGW packet gateway
  • 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.
  • 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.
  • TTL time to live
  • 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).
  • PGW packet gateway
  • 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.
  • 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.
  • TTL time to live
  • 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.
  • 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.
  • 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.
  • eNodeBs evolved Node Bs
  • 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.
  • 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.
  • 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).
  • PGW packet gateway
  • 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.
  • 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.

Landscapes

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

Abstract

Un appareil est configuré pour être employé dans un noeud B évolué (eNodeB). L'appareil comprend des circuits de commande. Les circuits de commande sont configurés pour détecter des communications d'UE à UE, identifier un eNodeB distant, demander l'établissement d'un tunnel inter-eNodeB et remapper des communications d'UE à UE pour utiliser le tunnel inter-eNodeB.
PCT/US2016/054640 2016-09-30 2016-09-30 Sélection et resélection de trajet en plan u pour une communication d'ue à ue Ceased WO2018063276A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2016/054640 WO2018063276A1 (fr) 2016-09-30 2016-09-30 Sélection et resélection de trajet en plan u pour une communication d'ue à ue

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2016/054640 WO2018063276A1 (fr) 2016-09-30 2016-09-30 Sélection et resélection de trajet en plan u pour une communication d'ue à ue

Publications (1)

Publication Number Publication Date
WO2018063276A1 true WO2018063276A1 (fr) 2018-04-05

Family

ID=57206350

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/054640 Ceased WO2018063276A1 (fr) 2016-09-30 2016-09-30 Sélection et resélection de trajet en plan u pour une communication d'ue à ue

Country Status (1)

Country Link
WO (1) WO2018063276A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023061069A1 (fr) * 2021-10-15 2023-04-20 中兴通讯股份有限公司 Procédé et appareil de traitement de paquet de routage, et support de stockage et appareil électronique

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110182249A1 (en) * 2010-01-28 2011-07-28 Verizon Patent And Licensing, Inc. Data offloading at wireless node
US20150138987A1 (en) * 2013-11-20 2015-05-21 At & T Mobility Ii Llc Method and system for efficient management of a communication system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110182249A1 (en) * 2010-01-28 2011-07-28 Verizon Patent And Licensing, Inc. Data offloading at wireless node
US20150138987A1 (en) * 2013-11-20 2015-05-21 At & T Mobility Ii Llc Method and system for efficient management of a communication system

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023061069A1 (fr) * 2021-10-15 2023-04-20 中兴通讯股份有限公司 Procédé et appareil de traitement de paquet de routage, et support de stockage et appareil électronique

Similar Documents

Publication Publication Date Title
US11979926B2 (en) Systems, methods, and apparatuses for enabling relay services for user equipment to access 5GC via a residential gateway
US12335803B2 (en) Network-initiated connection transfer
TWI738678B (zh) 使用裝置對裝置通訊（ｄ２ｄ）之超低省電裝置的下行鏈路可達性
CN108029148B (zh) 移动性中继方法和装置
CN109804592B (zh) 用于无线电资源管理测量的配置的装置及计算机可读介质
WO2017099833A1 (fr) Améliorations de plan de commande sur une liaison latérale pour dispositifs de faible puissance
US11018903B2 (en) Channel estimation using a plurality of beamformed reference signals
WO2017151259A1 (fr) Gestion d'état améliorée de repli par commutation de circuits (csfb)
US10499444B2 (en) Radio network access of wearable devices
TWI714647B (zh) 用於軟體定義無線電存取網路的行動管理
CN109076415B (zh) 用于业务卸荷功能的方法及装置
WO2018063276A1 (fr) Sélection et resélection de trajet en plan u pour une communication d'ue à ue
WO2016200487A1 (fr) Système et procédé destiné à un marquage dynamique pour une division de support de protocole internet
US11638135B2 (en) Core network design for mission-critical IoT
US11510094B2 (en) Lightweight S-1 lite protocol design for cellular internet of things
WO2025199856A1 (fr) Configuration et procédés d'ue pour mettre en œuvre une mobilité déclenchée par l1/l2 (ltm) inter-cu
WO2025208080A1 (fr) Identification de scénario et combinaison de cas pour positionnement par intelligence artificielle/apprentissage automatique (ia/ml)
HK40000226A (en) Solution for local breakout in cellular network
HK1254713B (zh) 网络发起的分组数据网络连接
HK40000226B (zh) 用於业务卸荷功能的方法及装置

Legal Events

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

Ref document number: 16787587

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16787587

Country of ref document: EP

Kind code of ref document: A1