[go: up one dir, main page]

WO2018031343A1 - Procédés d'optimisation d'opérations relais de couche 2 - Google Patents

Procédés d'optimisation d'opérations relais de couche 2 Download PDF

Info

Publication number
WO2018031343A1
WO2018031343A1 PCT/US2017/045163 US2017045163W WO2018031343A1 WO 2018031343 A1 WO2018031343 A1 WO 2018031343A1 US 2017045163 W US2017045163 W US 2017045163W WO 2018031343 A1 WO2018031343 A1 WO 2018031343A1
Authority
WO
WIPO (PCT)
Prior art keywords
relay
remote
data
interface
drb
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/US2017/045163
Other languages
English (en)
Inventor
Sangeetha Bangolae
Kyeongin Jeong
Richard Burbidge
Youn Hyoung Heo
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 IP Corp
Original Assignee
Intel IP 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 IP Corp filed Critical Intel IP Corp
Publication of WO2018031343A1 publication Critical patent/WO2018031343A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H04W12/062—Pre-authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • FIG. 2 is a communication diagram illustrating layer 2 relaying using network-aided discovery when a relay UE and remote UE are in connected mode, according to one embodiment.
  • FIG. 8 is a communication diagram illustrating packet relay by an eNB to a network with one bearer per UE, according to one embodiment.
  • FIG. 9 is a communication diagram illustrating packet relay by an eNB to a network with multiplexing of packets on a single bearer, according to one
  • FIG. 12 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • LTE technology can be used to connect and manage low power wearable devices.
  • the diverse set of wearable devices and use cases (ranging from low data rate delay tolerant monitoring to high data rate delay sensitive virtual reality) uses different communication capabilities.
  • Layer 2 relaying optimizations are used for a wearable device to transmit data over WLAN or BT to a relay or smartphone when it is in-coverage or out-of- coverage and get the data forwarded to a node in the network. This saves battery of the wearable device as it need not send or receive data over direct Uu connection and instead uses a nearby low power device as its relay. At the same time, the wearable device has to be identified, authenticated, and addressed.
  • UE-to-NW Relay or relay UE is a layer 3 relay (i.e., an IP router).
  • a relay at a layer 2 level sometimes referred to as FeD2D.
  • the system 100 further includes a boundary 1 12, which represents the geographic extent of the coverage network of the 3GPP access as provided by the eNB 106.
  • a WLAN channel 1 16 of the system 100 represents D2D WLAN
  • the remote UE 102 is a wearable device.
  • the remote UE 102 is not able to communicate directly with the eNB 106 to access the EPC 108 (and subsequently the Public Safety AS 1 10) because it is not in a 3GPP coverage range 1 12.
  • the remote UE 102 has established a connection with the ProSe UE-to-Network Relay 104 over interface PC5 using the WLAN D2D communication channel 1 16 and/or the BT D2D communication channel 1 18.
  • the remote UE 102 may send data over the PC5 interface to the ProSe UE-to-Network Relay 104.
  • the ProSe UE-to-Network Relay 104 is configured to receive this data and forward it to the eNB 106 via the Uu interface using 3GPP access methods. Once at the eNB 106, the data may be transferred to the EPC 108 and subsequently to the Public Safety AS 1 10. The relayed communications between the remote UE 102 and the EPC 108 are considered to be transferred along the virtual communications channel 1 14.
  • Remote UE may be any device capable of communicating in a D2D fashion with another device over a PC5 interface.
  • the ProSe UE-to-Network Relay 104 may be any device capable of receiving data from another device over a PC5 interface and forwarding that data over a 3GPP interface Uu.
  • FIGs. 2-4 show embodiments that describe how non-3GPP based access (e.g., WLAN based (Neighbor Aware Networking/WiFi Direct based), BluetoothTM, etc.) supports discovery of a remote UE of peer WiFi Direct UE.
  • non-3GPP based access e.g., WLAN based (Neighbor Aware Networking/WiFi Direct based), BluetoothTM, etc.
  • the relay UE can forward data received over non-3GPP access from another UE (which has 3GPP credentials and is registered in the 3GPP network).
  • the two UEs (one of them being the relay UE) can discover each other and begin 1 : 1 communication.
  • a method 200 of passing messages to configure data relaying from the remote UE 202 through the relay UE 204 to the eNB 206 when both the remote UE 202 and the relay UE 204 are in connected mode with the eNB 206 is shown in FIG. 2.
  • Both the relay UE 204 and the remote UE 202 registered and attached with 3GPP through the eNB 206 and the MME 208, as shown by operations 210 and 212.
  • the remote UE 202 has an active S1 connection through the eNB 206 and the MME 208.
  • a UE capability inquiry message is passed from the eNB 206 to the relay UE 204.
  • a broadcast configuration for relay message then passes from the eNB 206 to the relay UE 204.
  • the relay UE 204 determines to act as a relay for remote UEs on the network.
  • the remote UE 202 and the relay UE 204 are both in connected mode, as shown by states 218 and 216 respectively.
  • Operations 220 are then executed.
  • the eNB 206 passes an RRC
  • Connection Reconfiguration message to the remote UE 202; this message may also include a list of candidate relay UE IDs.
  • the remote UE 202 sends an RRC Connection Reconfiguration Complete message to the eNB 206.
  • One-to-one communication operations 226 are executed.
  • One-to-one communication between the remote UE 202 and the relay UE 204 may be established as the remote UE 202 passes a direct communication request message to the relay UE 204. Further messages may then be passed to provide for mutual authentication between the remote UE 202 and the relay UE 204.
  • a SidelinkUEInformation message is passed from the relay UE 204 to the eNB 206.
  • This message includes ID information corresponding to the remote UE 202.
  • This ID information can include a WLAN MAC address, a BT MAC address, a ProSe communication ID and/or code or token, or any other appropriate ID information corresponding to the remote UE 202.
  • the eNB 206 then authorizes the remote UE 202 with the MME 208 as shown in an authorization 230.
  • a SidelinkUEInformation response message is then passed from the eNB 206 to the relay UE 204.
  • This message can include an authorization for the remote UE, a data radio bearer (DRB) ID, resource information in the case of ProSe communication, or any other piece of information that may be of aid in facilitating the relay of forthcoming data information from the remote UE 202 through the relay UE 204 and on to the eNB 206.
  • DRB data radio bearer
  • the remote UE 202 may then begin sending data messages to relay UE 204.
  • the relay UE 204 may relay those data messages to the eNB 206.
  • the eNB 206 may then map this incoming data to the remote UE's own EPS bearer, as shown in step 232.
  • the remote UE informs the relay UE ID (e.g., MAC Address) obtained during non-3GPP access based discovery (e.g., WLAN beacon) to the eNB/base station as part of a new RRC message or existing
  • the eNB responds with an acknowledgement on whether the given relay UE supports layer 2 relaying or layer 3 relaying or no relaying over 3GPP/5G.
  • Relay UE has already informed the eNB that relay UE can operate as relay UE in advance and the eNB keeps that information in the database.
  • the eNB can also inform the corresponding/informed relay UE of the acknowledgement (including the remote UE's 3GPP, WLAN, BluetoothTM MAC ID and/or address information) of the remote UE so that it is aware of a remote UE.
  • the eNB can be performing network control based policing or admission control as the data arriving over non-3GPP access cannot be controlled later on, once admitted.
  • the relay UE ID provided by the remote UE may be its Bluetooth, WLAN MAC address or any other network provided ID or a paired form of ID in case the remote UE and relay UE are paired (although in some embodiments, when pairing is defined, it is assumed that the relay UE supports 3GPP relaying).
  • a method 300 begins with both the relay UE 304 and the remote UE 302 registered and attached with 3GPP through the eNB 306 and the MME 308, as shown by operations 310 and 312, respectively. As shown by the operation 312, the remote UE 302 further has an active S1 connection through the eNB 306 and the MME 308.
  • a UE capability inquiry message is passed from the eNB 306 to the relay UE 304.
  • Another UE capability inquiry message is passed from the eNB 306 to the remote UE 302.
  • the relay UE 304 passes a UE capability info message to the eNB 306, and the remote UE 302 passes a UE capability info message to the eNB 306. During this exchange, UE MAC addresses are provided to the eNB.
  • One-to-one communication operations 326 is then executed.
  • One-to-one communication between the remote UE 302 and the relay UE 304 may be established as the remote UE 302 passes a direct communication request message to the relay UE 304. Further messages may then be passed to provide for mutual confirmation between the remote UE 302 and the relay UE 304.
  • a sidelink UE information message is passed from the relay UE 304 to the eNB 306.
  • This message includes ID information corresponding to the remote UE 302.
  • This ID information can be a WLAN MAC address, a BluetoothTM MAC address, a ProSe communication ID or code or token, or any other appropriate ID information corresponding to the remote UE 302.
  • the eNB 306 then authorizes the remote UE with the MME 308 as shown in an operation 330.
  • a sidelink UE information response message is then passed from the eNB 306 to the relay UE 304.
  • This message may include an authorization for the remote UE, a DRB ID, resource information in the case of ProSe
  • the relay UE can inform the remote UE that it is also capable of performing non-3GPP access (for both discovery and communication over WLAN or BT as it applies) and the remote UE could then obtain the relay UE's MAC Address through this process and use it for non-3GPP discovery or directly performs communication with security exchange depending on the restrictions imposed by the non-3GPP access methodology.
  • a broadcast configuration for relay message then passes from the eNB 406 to the relay UE 404.
  • the relay UE 404 determines to act as a relay for remote UEs on the network.
  • the remote UE 402 and the relay UE 404 are both in connected mode, as shown by states 418 and 416 respectively.
  • Discovery operations 424 are executed. Discovery can occur through the sending of a ProSe discovery announcement message (including that layer 2 relay is supported and a relay UE ID) from the relay UE 404 to the remote UE 402.
  • a ProSe discovery announcement message including that layer 2 relay is supported and a relay UE ID
  • One-to-one communication operations 426 is then executed.
  • One-to-one communication between the remote UE 402 and the relay UE 404 may be established as the remote UE 402 passes a direct communication request message to the relay UE 404.
  • the relay UE 404 passes a direct communication response (including that layer 2 relay is supported and a relay UE ID). Further messages may then be passed to provide for mutual confirmation between the remote UE 402 and the relay UE 404.
  • a sidelink UE information message is passed from the relay UE 404 to the eNB 406.
  • This message includes ID information corresponding to the remote UE 402.
  • This ID information can be a WLAN MAC address, a BluetoothTM MAC address, a ProSe communication ID or code or token, or any other appropriate ID information corresponding to the remote UE 402.
  • the eNB 406 then authorizes the remote UE with the MME 408 as shown in an operation 430.
  • the remote UE 508, 608 goes out of coverage and/or into an RRC idle state.
  • the remote UE 508, 608 has established direct connection at attach with the same eNB 502, 602 (or cell). Then, either the remote UE 508, 608 enters idle or goes out of coverage.
  • the relay UE 510, 610 can carry control plane signaling or perform control plane signaling on behalf of the remote UE 508, 608 for downlink paging or service request procedure or similar procedure to activate or establish EPS bearer for the remote UE 508, 608 through the non-3GPP access data path.
  • the signalling radio bearer (SRB) data can be encapsulated within WLAN MAC data for example.
  • the eNB should be able to decipher the information and perform the corresponding procedure and respond accordingly.
  • the scenario for an out of coverage (OOC) remote UE is shown in FIGs. 5-6.
  • the relay UE there is an entity defined and implemented within the relay UE to support layer 2 relaying/data forwarding.
  • the entity receives incoming data (from the WLAN interface with the remote UE) in the buffer, the entity moves the data to the RLC buffer to trigger the UE to enter connected mode.
  • the remote UE can exchange messages with the eNB with the candidate relay UE ID (e.g., non- 3GPP access based MAC addresses) to select a final relay to be used for relaying communication.
  • the eNB can let the remote UE know if the relay UE is authorized and can perform layer 2 relaying, supports a defined PDN connection, and is in idle or connected mode, and whether the eNB can page the relay UE if RAN based paging is supported.
  • the eNB already has a remote UE ID of the non-3GPP access, when relay UE provides that ID (e.g., WLAN MAC address obtained from the first data packet), the authorization can be granted immediately as the remote UE is in connected mode and the eNB already has the remote UE's context information.
  • the eNB can assign a DRB ID for the relay UE to use for relaying or acknowledge that the remote UE is authorized for access.
  • the eNB can further check for authorization with other functions in the network (ProSe Function or MME, etc.).
  • the UEs 1001 and 1002 may be configured to connect, e.g.,
  • the RAN 1010 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UEs 1001 and 1002 utilize connections 1003 and 1004, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 1003 and 1004 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to-Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR New Radio
  • PSDCH Physical Sidelink Broadcast Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the RAN 1010 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 101 1 , and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 1012.
  • RAN nodes for providing macrocells e.g., macro RAN node 101 1
  • femtocells or picocells e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells
  • LP low power
  • the UEs 1001 and 1002 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 101 1 and 1012 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency- Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect.
  • OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 101 1 and 1012 to the UEs 1001 and 1002, while uplink transmissions can utilize similar techniques.
  • the grid can be a time- frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • the physical downlink shared channel may carry user data and higher-layer signaling to the UEs 1001 and 1002.
  • the physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 1001 and 1002 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 1002 within a cell) may be performed at any of the RAN nodes 101 1 and 1012 based on channel quality information fed back from any of the UEs 1001 and 1002.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 1001 and 1002.
  • the PDCCH may use control channel elements (CCEs) to convey the control information.
  • CCEs control channel elements
  • the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching.
  • Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs).
  • RAGs resource element groups
  • QPSK Quadrature Phase Shift Keying
  • the PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition.
  • DCI downlink control information
  • There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L 1 , 2, 4, or 8).
  • Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts.
  • some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission.
  • the EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
  • EPCCH enhanced physical downlink control channel
  • ECCEs enhanced the control channel elements
  • each ECCE may correspond to nine sets of four physical resource elements known as enhanced resource element groups (EREGs).
  • EREGs enhanced resource element groups
  • An ECCE may have other numbers of EREGs in some situations.
  • the RAN 1010 is shown to be communicatively coupled to a core network (CN) 1020—via an S1 interface 1013.
  • the CN 1020 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN.
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the S1 interface 1013 is split into two parts: the S1 -U interface 1014, which carries traffic data between the RAN nodes 101 1 and 1012 and a serving gateway (S-GW) 1022, and an S1 -mobility
  • the S-GW 1022 may terminate the S1 interface 1013 towards the RAN 1010, and routes data packets between the RAN 1010 and the CN 1020.
  • the S-GW 1022 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the P-GW 1023 may terminate an SGi interface toward a PDN.
  • the P-GW 1023 may route data packets between the CN 1020 (e.g., an EPC network) and external networks such as a network including the application server 1030
  • an application server 1030 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • the P-GW 1023 is shown to be communicatively coupled to an application server 1030 via an IP communications interface 1025.
  • the application server 1030 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 1001 and 1002 via the CN 1020.
  • VoIP Voice-over-Internet Protocol
  • the P-GW 1023 may further be a node for policy enforcement and charging data collection.
  • a Policy and Charging Enforcement Function (PCRF) 1026 is the policy and charging control element of the CN 1020.
  • PCRF Policy and Charging Enforcement Function
  • HPLMN Home Public Land Mobile Network
  • IP- CAN Internet Protocol Connectivity Access Network
  • HPLMN Home Public Land Mobile Network
  • V-PCRF Visited PCRF
  • VPLMN Visited Public Land Mobile Network
  • the device 1 100 may include application circuitry 1 102, baseband circuitry 1 104, Radio Frequency (RF) circuitry 1 106, front-end module (FEM) circuitry 1 108, one or more antennas 1 1 10, and power management circuitry (PMC) 1 1 12 coupled together at least as shown.
  • the components of the illustrated device 1 100 may be included in a UE or a RAN node.
  • the device 1 100 may include fewer elements (e.g., a RAN node may not utilize application circuitry 1 102, and instead include a
  • processor/controller to process IP data received from an EPC.
  • baseband processors 1 104A-D may be included in modules stored in the memory 1 104G and executed via a Central Processing Unit (CPU) 1 104E.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • signal modulation/demodulation e.g., a codec
  • encoding/decoding e.g., a codecation/frequency shifting, etc.
  • the RF circuitry 1 106 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1 108 and provide baseband signals to the baseband circuitry 1 104.
  • RF circuitry 1 106 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1 104 and provide RF output signals to the FEM circuitry 1 108 for transmission.
  • the mixer circuitry 1 106A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1 106D to generate RF output signals for the FEM circuitry 1 108.
  • the baseband signals may be provided by the baseband circuitry 1 104 and may be filtered by the filter circuitry 1 106C.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 1 106 may include analog- to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1 104 may include a digital baseband interface to communicate with the RF circuitry 1 106.
  • ADC analog- to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • synthesizer circuitry 1 106D may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 1 106D may be configured to synthesize an output frequency for use by the mixer circuitry 1 106A of the RF circuitry 1 106 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1 106D may be a fractional N/N+1 synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 1 104 or the application circuitry 1 102 (such as an applications processor) depending on the desired output frequency.
  • a divider control input e.g., N may be
  • Synthesizer circuitry 1 106D of the RF circuitry 1 106 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA).
  • the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the synthesizer circuitry 1 106D may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 1 106 may include an IQ/polar converter.
  • FEM circuitry 1 108 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1 1 10, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1 106 for further processing.
  • the FEM circuitry 1 108 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1 106 for transmission by one or more of the one or more antennas 1 1 10.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 1 106, solely in the FEM circuitry 1 108, or in both the RF circuitry 1 106 and the FEM circuitry 1 108.
  • the FEM circuitry 1 108 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry 1 108 may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry 1 108 may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1 106).
  • the transmit signal path of the FEM circuitry 1 108 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by the RF circuitry 1 106), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1 1 10).
  • PA power amplifier
  • FIG. 1 1 shows the PMC 1 1 12 coupled only with the baseband circuitry 1 104.
  • the PMC 1 1 12 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, the application circuitry 1 102, the RF circuitry 1 106, or the FEM circuitry 1 108.
  • the device 1 100 may transition off to an RRCJdle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 1 100 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 1 100 may not receive data in this state, and in order to receive data, it transitions back to an RRC_Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 1 102 and processors of the baseband circuitry 1 104 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 1 104 alone or in combination, may be used to execute layer 3, layer 2, or layer 1 functionality, while processors of the application circuitry 1 102 may utilize data (e.g., packet data) received from these layers and further execute layer 4 functionality (e.g.,
  • layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • FIG. 12 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 1 104 of FIG. 1 1 may comprise processors 1 104A-1 104E and a memory 1 104G utilized by said processors.
  • Each of the processors 1 104A-1 104E may include a memory interface, 1204A-1204E, respectively, to send/receive data to/from the memory 1 104G.
  • the baseband circuitry 1 104 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 1212 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 1 104), an application circuitry interface 1214 (e.g., an interface to send/receive data to/from the application circuitry 1 102 of FIG. 1 1 ), an RF circuitry interface 1216 (e.g., an interface to send/receive data to/from RF circuitry 1 106 of FIG. 1 1 ), a wireless hardware connectivity interface 1218 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components,
  • NFC Near Field Communication
  • FIG. 13 is an illustration of a control plane protocol stack in accordance with some embodiments.
  • a control plane 1300 is shown as a communications protocol stack between the UE 1001 (or alternatively, the UE 1002), the RAN node 101 1 (or alternatively, the RAN node 1012), and the MME 1021 .
  • a PHY layer 1301 may transmit or receive information used by the MAC layer 1302 over one or more air interfaces.
  • the PHY layer 1301 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as an RRC layer 1305.
  • the PHY layer 1301 may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MIMO) antenna processing.
  • FEC forward error correction
  • MIMO Multiple Input Multiple Output
  • the MAC layer 1302 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channels onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel prioritization.
  • SDUs MAC service data units
  • TB transport blocks
  • HARQ hybrid automatic repeat request
  • the RLC layer 1303 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.
  • a PDCP layer 1304 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).
  • security operations e.g., ciphering, deciphering, integrity protection, integrity verification, etc.
  • the main services and functions of the RRC layer 1305 may include broadcast of system information (e.g., included in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS)), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point-to-point radio bearers, security functions including key management, inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting.
  • SIBs may comprise one or more information elements (lEs), which may each comprise individual data fields or data structures.
  • the S1 Application Protocol (S1 -AP) layer 1315 may support the functions of the S1 interface and comprise Elementary Procedures (EPs).
  • An EP is a unit of interaction between the RAN node 101 1 and the CN 1020.
  • the S1 -AP layer services may comprise two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.
  • E-RAB E-UTRAN Radio Access Bearer
  • RIM RAN Information Management
  • the Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the stream control transmission protocol/internet protocol (SCTP/IP) layer) 1314 may ensure reliable delivery of signaling messages between the RAN node 101 1 and the MME 1021 based, in part, on the IP protocol, supported by an IP layer 1313.
  • An L2 layer 1312 and an L1 layer 131 1 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.
  • FIG. 14 is an illustration of a user plane protocol stack in accordance with some embodiments.
  • a user plane 1400 is shown as a
  • the user plane 1400 may utilize at least some of the same protocol layers as the control plane 1300.
  • the UE 1001 and the RAN node 101 1 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack comprising the PHY layer 1301 , the MAC layer 1302, the RLC layer 1303, the PDCP layer 1304.
  • a Uu interface e.g., an LTE-Uu interface
  • the General Packet Radio Service (GPRS) Tunneling Protocol for the user plane (GTP-U) layer 1404 may be used for carrying user data within the GPRS core network and between the radio access network and the core network.
  • the user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example.
  • the UDP and IP security (UDP/IP) layer 1403 may provide checksums for data integrity, port numbers for addressing different functions at the source and
  • the RAN node 101 1 and the S-GW 1022 may utilize an S1 -U interface to exchange user plane data via a protocol stack comprising the L1 layer 131 1 , the L2 layer 1312, the
  • FIG. 15 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
  • FIG. 15 shows a diagrammatic representation of hardware resources 1500 including one or more processors (or processor cores) 1510, one or more memory/storage devices 1520, and one or more communication resources 1530, each of which may be communicatively coupled via a bus 1540.
  • a hypervisor 1502 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1500.
  • the processors 1510 may include, for example, a processor 1512 and a processor 1514.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • RFIC radio-frequency integrated circuit
  • the memory/storage devices 1520 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 1520 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable
  • DRAM dynamic random access memory
  • SRAM static random-access memory
  • EPROM erasable programmable read-only memory
  • EEPROM programmable read-only memory
  • Flash memory solid-state storage, etc.
  • NFC components NFC components
  • Bluetooth® components e.g., Bluetooth® Low Energy
  • Wi-Fi® components Wi-Fi components
  • Example 1 is an apparatus for a user equipment (UE), comprising a memory interface and baseband processor circuitry.
  • the memory interface to store or access a relay UE identifier (ID) in a memory.
  • the baseband processor circuitry is configured to perform a UE discovery to identify a relay UE having the relay UE ID; generate a direct communication request for the relay UE utilizing the relay UE ID; perform mutual authentication with the relay UE, based on receiving approval from the relay UE for the direct communication request, to obtain an authorization from a radio access network (RAN) node to relay data to the RAN node; and generate a device-to-device (D2D) message to provide, via a D2D link, data to the relay UE to communicate with the RAN node in response to performing mutual authentication.
  • RAN radio access network
  • D2D device-to-device
  • Example 2 is the apparatus of Example 1 , wherein the one or more baseband processors configured to provide the data to the relay UE via the D2D interface are further configured to provide the data to the relay UE via a non-3rd Generation Partnership Project (3GPP) interface.
  • 3GPP 3rd Generation Partnership Project
  • Example 4 is the apparatus of Example 1 , wherein the one or more baseband processors are further configured to process a first radio resource control (RRC) connection reconfiguration message received from the RAN node, the RRC connection reconfiguration message comprising a plurality of relay UE IDs.
  • RRC radio resource control
  • Example 5 is the apparatus of Example 4, wherein the one or more baseband processors are further configured to generate a second RRC connection reconfiguration message for the RAN node comprising the plurality of relay UE IDs and the relay UE ID.
  • Example 6 is the apparatus of Example 1 , wherein the one or more baseband processors configured to perform the UE discovery are further configured to perform a layer 2 UE discovery through a proximity services (ProSe) D2D discovery procedure to obtain a plurality of relay UE IDs including the relay UE ID.
  • ProSe proximity services
  • Example 7 is the apparatus of Example 6, wherein the one or more baseband processors configured to provide the data to the relay UE via the D2D interface to communicate with the RAN node are further configured to provide the data to the relay UE via the D2D interface to communicate with the RAN node when the UE enters an out-of-coverage area to communicate with the RAN.
  • Example 1 1 is the apparatus of Example 10, wherein the one or more baseband processors are further configured to generate an uplink message for the RAN node comprising the MAC address to authorize the remote UE with a mobility management entity (MME) of the RAN.
  • Example 12 is the apparatus of Example 1 1 , wherein the one or more baseband processors are further configured to: process a downlink message, received from the RAN node in response to generating the uplink message, comprising a data radio bearer (DRB) ID of a DRB corresponding to the remote UE; and generate a mapping between the remote UE and the DRB over a Uu interface using the DRB ID.
  • DRB data radio bearer
  • Example 14 is the apparatus of Example 12, wherein the one or more baseband processors configured to generate the mapping are further configured to configure an adaptation layer to link the MAC address or remote UE ID over a short- range interface to the DRB ID over the Uu interface.
  • Example 15 is the apparatus of Example 14, wherein the adaptation layer is part of a packet data convergence protocol (PDCP).
  • PDCP packet data convergence protocol
  • Example 16 is the apparatus of Example 14, wherein the adaptation layer resides between a radio link control (RLC) and PDCP.
  • RLC radio link control
  • Example 17 is the apparatus of Example 8, wherein the one or more baseband processors are further configured to perform a proximity services (ProSe) D2D discovery procedure by providing an access ID and capabilities to perform layer 2 relaying of the UE.
  • ProSe proximity services
  • Example 18 is the apparatus of Example 8, wherein the one or more baseband processors are further configured to relay control plane information received from the RAN node via a Uu interface to the remote UE via the WLAN interface.
  • Example 20 is a computer-readable storage medium having stored thereon instructions that, when implemented by a radio access network (RAN) node, cause the RAN node to store a plurality of user equipment (UE) identifiers (IDs) corresponding to relay UEs; generate a first radio resource control (RRC) message to configure the relay UEs to relay data to a plurality of remote UEs; generate a second RRC message for a remote UE from the plurality of remote UEs to provide the remote UE with the plurality of UE IDs of the relay UEs; decode sidelink information identifying a relay UE from the relay UEs and the remote UE; assign a data radio bearer (DRB) ID to a relay UE to map the remote UE's data received over a layer 2 relay to a DRB having the DRB ID; and generate a configuration message to configure the relay UE to forward data received via a wireless local area network (WLAN) access device-to-device (D2D)
  • WLAN wireless
  • Example 21 is the computer-readable storage medium of Example 20, wherein the DRB is a shared DRB, shared across multiple UEs.
  • Example 22 is the computer-readable storage medium of Example 20, wherein the DRB is a dedicated DRB that services a single UE.
  • Example 23 is a method of enabling a relay user equipement (UE) by a radio access network (RAN) node, the method comprising storing a plurality of UE identifiers (IDs) corresponding to relay UEs; generating a first radio resource control (RRC) message to configure the relay UEs to relay data to a plurality of remote UEs; generating a second RRC message for a remote UE from the plurality of remote UEs to provide the remote UE with the plurality of UE IDs of the relay UEs; decoding sidelink information identifying a relay UE from the relay UEs and the remote UE; assigning a data radio bearer (DRB) ID to a relay UE to map the remote UE's data received over a layer 2 relay to a DRB having the DRB ID; and generating a configuration message to configure the relay UE to forward data received via a wireless local area network (WLAN) access device-to-device (D2D) based layer
  • WLAN
  • Example 26 is an apparatus for a user equipment (UE), comprising a memory interface to store or access a remote UE identifier (ID) in a memory; and means for authenticating a remote UE having the remote UE ID.
  • the apparatus also comprises means for obtaining an authorization from a radio access network (RAN) node to relay data to the RAN node; means for processing the data received from the remote UE via a wireless local area network (WLAN) interface; means for generating service data units (SDUs) comprising the data received from the remote UE based on the authorization; and means for encoding an uplink message to communicate the SDUs to a RAN node utilizing a wide area network (WAN) interface.
  • RAN radio access network
  • WLAN wireless local area network
  • SDUs service data units
  • Example 1 is a user equipment or (UE) referred to as (evolved) remote UE that is WiFi-enabled (or Bluetooth-enabled) and/or ProSe D2D and capable to communicate to the network either through communication over LTE Uu interface or through an evolved UE-to-Network Relay over BT or WiFi interface.
  • UE user equipment
  • WiFi-enabled or Bluetooth-enabled
  • ProSe D2D ProSe D2D
  • Additional Example 2 is an example of Additional Example 1 capable of receiving a list of candidate eRelay UEs within the cell along with its MAC address information.
  • Additional Example 3 is an example of Additional Example 1 capable of discovering evolved relay UEs using non-3GPP access and providing the list or a selected one to the eNB along with its MAC address information.
  • Additional Example 4 is an example of Additional Example 1 capable of discovering layer 2 relays through ProSe D2D discovery or association procedure and obtaining the relay UE IDs.
  • Additional Example 5 is an example of Additional Example 1 using the relay UEs list and capable of finding a suitable relay UE and performing layer 2 relaying when the UE enters out-of-coverage to communicate to the network.
  • Example 6 is a user equipment (UE) that is Bluetooth-enabled (or WiFi-enabled) and ProSe D2D enabled and capable of communicating to an evolved remote UE over a non-3GPP interface such as WiFi or BT and capable of layer 2 relaying of forwarding the SDUs of the evolved remote UEs over to the Uu interface with eNB.
  • UE user equipment
  • Additional Example 7 is an example of Additional Example 6 capable of providing remote UE ID information to the eNB wherein the ID could be a non-3GPP access based MAC address.
  • Additional Example 10 is an example of Additional Example 6 capable of relaying control plane information of evolved remote UE via non-3GPP D2D link to the network (both ways).
  • Additional Example 1 1 is an example of Additional Example 6 capable of entering connected mode based on incoming data in the buffer for relaying purposes only.
  • Additional Example 12 is an example of Additional Example 6 capable of receiving downlink paging for evolved remote UE with which it has associated a non- 3GPP D2D link and entering connected mode to relay the remote UE's information.
  • Additional Example 13 is an example of Additional Example 6 capable of distinguishing incoming remote UE's different data available over a non-3GPP D2D link and conveying it on its own (each remote UE) radio bearer and mapping to the assigned DRB ID from the network.
  • Additional Example 14 is an example of Additional Example 6 capable of multiplexing multiple remote UEs' data within the same radio bearer and adding header information to distinguish the remote UEs' non-3GPP access based data.
  • Example 15 is an evolved Node B (eNB) or similar network node which can support D2D communication along with relay operation and configure certain UEs to act as evolved UE-to-Network relays (relay UEs) and send or receive communication from such relays.
  • eNB evolved Node B
  • relay UEs evolved UE-to-Network relays
  • Additional Example 16 is an example of Additional Example 15 capable of maintaining a list of evolved layer 2 relay UEs supporting non-3GPP access and providing this information to the evolved remote UE upon request.
  • Additional Example 18 is an example of Additional Example 15 capable of storing evolved remote UE and relay UE non-3GPP based MAC address information as part of their context.
  • Additional Example 19 is an example of Additional Example 15 capable of assigning a DRB ID to the evolved relay UE on behalf of specific non-3GPP access D2D based evolved remote UE.
  • Additional Example 20 is an example of Additional Example 15 capable of mapping remote UE's non-3GPP access D2D data received over layer 2 relay on to its own EPS bearer.
  • Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, a non-transitory computer-readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques.
  • the computing device may include a processor, a storage medium readable by the processor (including volatile and nonvolatile memory and/or storage elements), at least one input device, and at least one output device.
  • the volatile and non-volatile memory and/or storage elements may be a RAM, an EPROM, a flash drive, an optical drive, a magnetic hard drive, or another medium for storing electronic data.
  • the eNodeB (or other base station) and UE (or other mobile station) may also include a transceiver component, a counter
  • One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high-level procedural or an object-oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or an interpreted language, and combined with hardware implementations.
  • API application programming interface
  • a component may be implemented as a hardware circuit comprising custom very large scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • VLSI very large scale integration
  • a component may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like.
  • Components may also be implemented in software for execution by various types of processors.
  • An identified component of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, a procedure, or a function.
  • executables of an identified component need not be physically located together, but may comprise disparate instructions stored in different locations that, when joined logically together, comprise the component and achieve the stated purpose for the component.
  • a component of executable code may be a single instruction, or many instructions, and may even be distributed over several different code

Landscapes

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

Abstract

L'invention concerne des procédés d'optimisation d'opérations de relais de couche 2 pour un équipement d'utilisateur (UE) distant qui transmet des données sur une liaison non 3GPP (par exemple, une liaison WLAN, Bluetooth (BT), etc.) à un UE relais (par exemple, un téléphone intelligent, etc.) qu'il soit sous ou hors couverture. L'UE relais transmet les données à un nœud dans le réseau. La batterie du dispositif est moins sollicitée car, au lieu d'envoyer ou de recevoir des données sur une connexion Uu directe, l'UE utilise un dispositif proche, à faible puissance, en tant que relais. Le dispositif vestimentaire peut être identifié, authentifié et géré au préalable ou via la liaison relais.
PCT/US2017/045163 2016-08-12 2017-08-02 Procédés d'optimisation d'opérations relais de couche 2 Ceased WO2018031343A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662374656P 2016-08-12 2016-08-12
US62/374,656 2016-08-12

Publications (1)

Publication Number Publication Date
WO2018031343A1 true WO2018031343A1 (fr) 2018-02-15

Family

ID=59702820

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/045163 Ceased WO2018031343A1 (fr) 2016-08-12 2017-08-02 Procédés d'optimisation d'opérations relais de couche 2

Country Status (1)

Country Link
WO (1) WO2018031343A1 (fr)

Cited By (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110366223A (zh) * 2019-08-01 2019-10-22 Oppo（重庆）智能科技有限公司 无线通信方法、控制电路、存储介质与用户设备
EP3761751A1 (fr) * 2019-07-03 2021-01-06 Koninklijke Philips N.V. Sélection de relais dans des réseaux cellulaires en tranches
WO2021001086A1 (fr) * 2019-07-03 2021-01-07 Koninklijke Philips N.V. Sélection de relais dans des réseaux cellulaires en tranches
WO2021040463A1 (fr) * 2019-08-29 2021-03-04 엘지전자 주식회사 Communication relative à un état de désactivation du service de données ps 3gpp
CN112740765A (zh) * 2018-09-27 2021-04-30 瑞典爱立信有限公司 用于唤醒信号的灵活的用户设备分组
WO2021088990A1 (fr) * 2019-11-07 2021-05-14 维沃移动通信有限公司 Procédé et dispositif d'établissement de connexion de relais
US20210160956A1 (en) * 2019-11-22 2021-05-27 Mediatek Singapore Pte. Ltd. Packet Routing for Layer-2-Based Sidelink Relay
WO2021156254A1 (fr) * 2020-02-03 2021-08-12 Telefonaktiebolaget Lm Ericsson (Publ) Section de chemin entre uu et pc5
WO2021162955A1 (fr) * 2020-02-14 2021-08-19 Qualcomm Incorporated Procédés et appareils pour un relais couche deux nouvelle radio, nr
WO2021163894A1 (fr) * 2020-02-18 2021-08-26 华为技术有限公司 Procédé et appareil de communication basés sur un relais
WO2021243518A1 (fr) * 2020-06-01 2021-12-09 Nokia Shanghai Bell Co., Ltd. Accès initial de dispositif distant via un relais
US20210409937A1 (en) * 2020-06-29 2021-12-30 Asustek Computer Inc. Method and apparatus for user equipment (ue) reporting sidelink ue capability information in a wireless communication system
EP3934370A1 (fr) * 2020-06-29 2022-01-05 ASUSTek Computer Inc. Procédé et appareil d'établissement de support radio de liaison latérale dans un système de communication sans fil
WO2022016381A1 (fr) * 2020-07-21 2022-01-27 Apple Inc. Transfert de radiomessagerie pour un dispositif sans fil à distance
WO2022042439A1 (fr) * 2020-08-23 2022-03-03 Qualcomm Incorporated Relais de communication sans fil vers une entité de réseau sur la base d'une connexion à distance
WO2022079572A1 (fr) * 2020-10-12 2022-04-21 Telefonaktiebolaget Lm Ericsson (Publ) Ue relais et autorisation d'ue distant
CN114449516A (zh) * 2020-11-05 2022-05-06 华为技术有限公司 一种通信方法及装置
EP3994921A1 (fr) * 2019-07-02 2022-05-11 Qualcomm Incorporated Procédés pour faire des économies d'énergie avec des relais à ondes millimétriques
WO2022158822A1 (fr) * 2021-01-19 2022-07-28 삼성전자 주식회사 Procédé et dispositif de configuration d'une connexion d'un terminal distant par l'intermédiaire d'un terminal de relais dans un système de communication sans fil
CN114845352A (zh) * 2021-02-02 2022-08-02 大唐移动通信设备有限公司 一种信息处理方法及装置
JPWO2022195814A1 (fr) * 2021-03-18 2022-09-22
US20220330352A1 (en) * 2021-04-09 2022-10-13 Qualcomm Incorporated Disaggregated ue
CN115280891A (zh) * 2020-03-12 2022-11-01 高通股份有限公司 层2用户设备中继过程
CN116210297A (zh) * 2020-08-20 2023-06-02 高通股份有限公司 经由中继用户设备在侧行链路上寻呼
US20240188014A1 (en) * 2018-07-02 2024-06-06 Interdigital Patent Holdings, Inc. 5g delay tolerant data services
US20240223681A1 (en) * 2023-01-04 2024-07-04 Getac Technology Corporation Device communication during emergent conditions
US12262427B2 (en) 2019-06-28 2025-03-25 Nokia Technologies Oy Apparatus, method and computer program
EP4395374B1 (fr) * 2021-09-28 2025-11-26 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé de communication sans fil, dispositif terminal et dispositif de réseau
US12490082B2 (en) * 2021-06-08 2025-12-02 Asustek Computer Inc. Method and apparatus for user equipment (UE) reporting sidelink UE capability information in a wireless communication system

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016116128A1 (fr) * 2015-01-19 2016-07-28 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil d'établissement de clés de communication directe

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016116128A1 (fr) * 2015-01-19 2016-07-28 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil d'établissement de clés de communication directe

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on extended architecture support for proximity-based services (Release 13)", 3GPP STANDARD; 3GPP TR 23.713, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V13.0.0, 15 September 2015 (2015-09-15), pages 1 - 80, XP051294298 *
HUAWEI ET AL: "L2 UE Relay technology consideration for wearable", vol. RAN WG2, no. Dubrovnik, Croatia; 20160411 - 20160415, 2 April 2016 (2016-04-02), XP051082482, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_93bis/Docs/> [retrieved on 20160402] *
HUAWEI ET AL: "Procedures of the remote UE connection establishment with CN via a relay UE", vol. RAN WG2, no. Gothenburg, Sweden; 20160822 - 20160826, 13 August 2016 (2016-08-13), XP051142822, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_95/Docs/> [retrieved on 20160813] *
ZTE: "Considerations on the UE-to-Network Relays", vol. RAN WG2, no. Bratislava, Slovakia; 20150420 - 20150424, 19 April 2015 (2015-04-19), XP050936143, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20150419] *

Cited By (42)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240188014A1 (en) * 2018-07-02 2024-06-06 Interdigital Patent Holdings, Inc. 5g delay tolerant data services
CN112740765A (zh) * 2018-09-27 2021-04-30 瑞典爱立信有限公司 用于唤醒信号的灵活的用户设备分组
US12262427B2 (en) 2019-06-28 2025-03-25 Nokia Technologies Oy Apparatus, method and computer program
EP3994921A1 (fr) * 2019-07-02 2022-05-11 Qualcomm Incorporated Procédés pour faire des économies d'énergie avec des relais à ondes millimétriques
EP3761751A1 (fr) * 2019-07-03 2021-01-06 Koninklijke Philips N.V. Sélection de relais dans des réseaux cellulaires en tranches
WO2021001086A1 (fr) * 2019-07-03 2021-01-07 Koninklijke Philips N.V. Sélection de relais dans des réseaux cellulaires en tranches
CN110366223A (zh) * 2019-08-01 2019-10-22 Oppo（重庆）智能科技有限公司 无线通信方法、控制电路、存储介质与用户设备
WO2021040463A1 (fr) * 2019-08-29 2021-03-04 엘지전자 주식회사 Communication relative à un état de désactivation du service de données ps 3gpp
US12219626B2 (en) 2019-08-29 2025-02-04 Lg Electronics Inc. Communication related to 3GPP PS data off
US12382521B2 (en) 2019-11-07 2025-08-05 Vivo Mobile Communication Co., Ltd. Relay connection establishment method and device
WO2021088990A1 (fr) * 2019-11-07 2021-05-14 维沃移动通信有限公司 Procédé et dispositif d'établissement de connexion de relais
US12396062B2 (en) * 2019-11-22 2025-08-19 Mediatek Singapore Pte. Ltd. Packet routing for layer-2-based sidelink relay
US20210160956A1 (en) * 2019-11-22 2021-05-27 Mediatek Singapore Pte. Ltd. Packet Routing for Layer-2-Based Sidelink Relay
WO2021156254A1 (fr) * 2020-02-03 2021-08-12 Telefonaktiebolaget Lm Ericsson (Publ) Section de chemin entre uu et pc5
CN115104375A (zh) * 2020-02-14 2022-09-23 高通股份有限公司 用于新无线电第二层中继的技术
WO2021162955A1 (fr) * 2020-02-14 2021-08-19 Qualcomm Incorporated Procédés et appareils pour un relais couche deux nouvelle radio, nr
US11924895B2 (en) 2020-02-14 2024-03-05 Qualcomm Incorporated Techniques for new radio layer two relay
WO2021163894A1 (fr) * 2020-02-18 2021-08-26 华为技术有限公司 Procédé et appareil de communication basés sur un relais
CN115280891A (zh) * 2020-03-12 2022-11-01 高通股份有限公司 层2用户设备中继过程
WO2021243518A1 (fr) * 2020-06-01 2021-12-09 Nokia Shanghai Bell Co., Ltd. Accès initial de dispositif distant via un relais
US20210409937A1 (en) * 2020-06-29 2021-12-30 Asustek Computer Inc. Method and apparatus for user equipment (ue) reporting sidelink ue capability information in a wireless communication system
EP3934370A1 (fr) * 2020-06-29 2022-01-05 ASUSTek Computer Inc. Procédé et appareil d'établissement de support radio de liaison latérale dans un système de communication sans fil
CN116210295A (zh) * 2020-07-21 2023-06-02 苹果公司 针对远程无线设备的寻呼转发
WO2022016381A1 (fr) * 2020-07-21 2022-01-27 Apple Inc. Transfert de radiomessagerie pour un dispositif sans fil à distance
US12120633B2 (en) 2020-07-21 2024-10-15 Apple Inc. Paging forwarding for a remote wireless device
CN116210297A (zh) * 2020-08-20 2023-06-02 高通股份有限公司 经由中继用户设备在侧行链路上寻呼
WO2022040830A1 (fr) * 2020-08-23 2022-03-03 Qualcomm Incorporated Relais de communication sans fil à une entité de réseau sur la base d'une connexion à distance
WO2022042439A1 (fr) * 2020-08-23 2022-03-03 Qualcomm Incorporated Relais de communication sans fil vers une entité de réseau sur la base d'une connexion à distance
WO2022079572A1 (fr) * 2020-10-12 2022-04-21 Telefonaktiebolaget Lm Ericsson (Publ) Ue relais et autorisation d'ue distant
US12457114B2 (en) * 2020-10-12 2025-10-28 Telefonaktiebolaget Lm Ericsson (Publ) Relay UE and remote UE authorization
CN114449516A (zh) * 2020-11-05 2022-05-06 华为技术有限公司 一种通信方法及装置
EP4224901A4 (fr) * 2020-11-05 2024-01-24 Huawei Technologies Co., Ltd. Procédé et appareil de communication
WO2022158822A1 (fr) * 2021-01-19 2022-07-28 삼성전자 주식회사 Procédé et dispositif de configuration d'une connexion d'un terminal distant par l'intermédiaire d'un terminal de relais dans un système de communication sans fil
CN114845352A (zh) * 2021-02-02 2022-08-02 大唐移动通信设备有限公司 一种信息处理方法及装置
JPWO2022195814A1 (fr) * 2021-03-18 2022-09-22
JP7297181B2 (ja) 2021-03-18 2023-06-23 三菱電機株式会社 中継装置、通信システム、信号中継方法、制御回路および記憶媒体
US20220330352A1 (en) * 2021-04-09 2022-10-13 Qualcomm Incorporated Disaggregated ue
US11800573B2 (en) 2021-04-09 2023-10-24 Qualcomm Incorporated Disaggregated UE
US12490082B2 (en) * 2021-06-08 2025-12-02 Asustek Computer Inc. Method and apparatus for user equipment (UE) reporting sidelink UE capability information in a wireless communication system
EP4395374B1 (fr) * 2021-09-28 2025-11-26 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé de communication sans fil, dispositif terminal et dispositif de réseau
US20240223681A1 (en) * 2023-01-04 2024-07-04 Getac Technology Corporation Device communication during emergent conditions
US12470642B2 (en) * 2023-01-04 2025-11-11 Getac Technology Corporation Device communication during emergent conditions

Similar Documents

Publication Publication Date Title
US12349014B2 (en) Devices and methods for dynamic RACH
WO2018031343A1 (fr) Procédés d&#39;optimisation d&#39;opérations relais de couche 2
EP3482602B1 (fr) Systèmes, procédés et dispositifs de séparation de plan utilisateur de commande pour des réseaux d&#39;accès radio 5g
US10749587B2 (en) Systems, methods and devices for using S-measure with new radio
US12160806B2 (en) V2X policy and parameters provisioning to user equipment by a policy and control function
US11122453B2 (en) Systems, methods and devices for measurement configuration by a secondary node in EN-DC
US10966274B2 (en) RRC coordination between a plurality of nodes
EP3620028B1 (fr) Unification de porteuses fractionnées pendant un interfonctionnement lte
US10979958B2 (en) Systems, methods, and apparatuses for providing and obtaining scheduling information for SIB1-BR during handover
CN109691222B (zh) 用于配置轻型连接的装置
WO2018085049A1 (fr) Systèmes, procédés et dispositifs de transfert intercellulaire à établissement avant rupture et reconfiguration de groupe de cellules secondaires
WO2018175593A1 (fr) Surveillance de liaison radio, récupération de faisceau et gestion de défaillance de liaison radio
US11082901B2 (en) Signaling of support for network controlled small gap, NCSG, for interruption control
US11265884B2 (en) Systems, methods and devices for uplink bearer and access category mapping
WO2018106429A1 (fr) Mécanisme de transfert intercellulaire amélioré
WO2018085416A1 (fr) Support de mobilité pour systèmes 5g nr
WO2018031802A1 (fr) Optimisations de radiomessagerie à base de réseau d&#39;accès radioélectrique
US20200220673A1 (en) Frame structure for unlicensed narrowband internet-of-things system
US10455405B2 (en) Telephone call procedures for power efficient mobile terminating packet switched services
EP3834484A1 (fr) Procédés pour améliorer la gestion de transfert de session d&#39;unité de données de protocole dans un réseau d&#39;accès radio de prochaine génération
EP3462770A1 (fr) Procédés et appareil pour de multiples associations tnl entre ran et amf pour des déploiements virtualisés
EP3646566B1 (fr) Dispositifs de déchargement partiel des tâches de traitements de protocole
WO2018031395A1 (fr) Message de liaison montante commun pour des scénarios initiés par un équipement d&#39;utilisateur
WO2018140608A1 (fr) Actions elwa/lwip suite à une déconnexion de wlan

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: 17757943

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: 17757943

Country of ref document: EP

Kind code of ref document: A1