EP3666037B1 - Communication de données distantes et locales dans une liaison sans fil de raccordement aux sites cellulaires - Google Patents

Communication de données distantes et locales dans une liaison sans fil de raccordement aux sites cellulaires Download PDF

Info

Publication number
EP3666037B1
EP3666037B1 EP18765230.0A EP18765230A EP3666037B1 EP 3666037 B1 EP3666037 B1 EP 3666037B1 EP 18765230 A EP18765230 A EP 18765230A EP 3666037 B1 EP3666037 B1 EP 3666037B1
Authority
EP
European Patent Office
Prior art keywords
relay
layer
wireless
radio bearer
data
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.)
Active
Application number
EP18765230.0A
Other languages
German (de)
English (en)
Other versions
EP3666037A1 (fr
Inventor
Karl Georg Hampel
Hong Cheng
Junyi Li
Navid Abedini
Sundar Subramanian
Muhammad Nazmul ISLAM
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.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
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 Qualcomm Inc filed Critical Qualcomm Inc
Publication of EP3666037A1 publication Critical patent/EP3666037A1/fr
Application granted granted Critical
Publication of EP3666037B1 publication Critical patent/EP3666037B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • 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/08—Access point devices
    • 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]

Definitions

  • the present disclosure relates generally to communication systems, and more particularly, to a method performed by a relay device, a computer readable medium and the relay device.
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power).
  • multiple-access technologies include Long Term Evolution (LTE) systems, code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
  • LTE Long Term Evolution
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single-carrier frequency division multiple access
  • TD-SCDMA time division synchronous code division multiple access
  • US 2010/0260096 A1 relates to routing data packets
  • a wireless multiple-access communication system may include a number of base stations, each simultaneously supporting communication for multiple communication devices, otherwise known as user equipment (UEs).
  • UEs user equipment
  • a set of one or more base stations may define an e NodeB (eNB).
  • eNB e NodeB
  • a wireless multiple access communication system may include a number of distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmission reception points (TRPs), etc.) in communication with a number of central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), where a set of one or more distributed units, in communication with a central unit, may define an access node (e.g., a new radio base station (NR BS), a new radio node-B (NR NB), a network node, 5G NB, eNB, gigabit NodeB (gNB), etc.).
  • DUs distributed units
  • EUs edge units
  • ENs edge nodes
  • RHs radio heads
  • RHs smart radio heads
  • TRPs transmission reception points
  • CUs central units
  • CNs central nodes
  • ANCs access node controllers
  • a base station or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a base station or to a UE) and uplink channels (e.g., for transmissions from a UE to a base station or distributed unit).
  • downlink channels e.g., for transmissions from a base station or to a UE
  • uplink channels e.g., for transmissions from a UE to a base station or distributed unit
  • NR new radio
  • 3GPP Third Generation Partnership Project
  • CP cyclic prefix
  • DL downlink
  • UL uplink
  • MIMO multiple-input multiple-output
  • aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for new radio (NR) (new radio access technology or 5G technology).
  • NR new radio access technology
  • 5G technology new radio access technology
  • NR may support various wireless communication services, such as Enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g. 80 MHz beyond), millimeter wave (mmW) targeting high carrier frequency (e.g. 60 GHz), massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra reliable low latency communications (URLLC).
  • eMBB Enhanced mobile broadband
  • mmW millimeter wave
  • mMTC massive MTC
  • URLLC ultra reliable low latency communications
  • These services may include latency and reliability requirements.
  • These services may also have different transmission time intervals (TTI) to meet respective quality of service (QoS) requirements.
  • TTI transmission time intervals
  • QoS quality of service
  • these services may co-exist in the same subframe.
  • gNBs e.g., DUs of gNBs
  • gNBs may be densely deployed in a geographic area to provide coverage for UEs.
  • the rollout of such densely deployed gNBs can create a backhaul/fronthaul problem since CUs and DUs of gNBs are typically connected together by wired connections, and the digging and construction required to place such wired connections may be expensive or not feasible.
  • gNBs e.g., DUs of gNBs
  • IAB integrated access backhauling
  • connections between DUs and with a CU may be referred to herein as a fronthaul instead of being referred to as part of the backhaul.
  • connection e.g., a wired connection
  • the connection from the CU to a core network may be referred to as a backhaul.
  • a second DU may be configured to act as a relay between remote UEs and a first DU.
  • the first DU may have a wired connection to the CU as part of the fronthaul.
  • the second DU may communicate wirelessly with the first DU over a wireless connection as part of the fronthaul (e.g., thereby using wireless fronthauling between DUs).
  • the second DU may receive data from remote UEs with a destination of the CU/core network and forward such data originated by the remote UEs to the first DU, which then forwards the data to the CU and then on to the core network.
  • Such data originated by the remote UEs may be referred to as remote data of the second DU.
  • the second DU itself may generate data with a destination of the CU/core network and forward such data originated by the second DU to the first DU, which then forwards the data to the CU and then on to the core network.
  • Such data originated by the second DU may be referred to as local data of the second DU.
  • the CU may generate data for the remote UE (e.g., referred to as remote data of the second DU) or data for the second DU (referred to as local data of the second DU) and send the data to the first DU, which sends the data to the second DU. If the data is local data, the second DU processes the data. If the data is remote data, the second DU forwards the data to the remote UE.
  • data for the remote UE e.g., referred to as remote data of the second DU
  • data for the second DU referred to as local data of the second DU
  • the second DU, first DU, and CU may each send/receive local or remote data of the second DU, and therefore may need to be able to distinguish between the local or remote data of the second DU in order to properly process/handle the data. Accordingly, aspects of the present disclosure relate to configuring and operating DUs and CUs to distinguish between local and remote traffic when using wireless fronthauling between DUs. Though certain aspects are described herein with respect to CUs and DUs, the same techniques may be applied for wireless communication between other components of or types of base stations or gNBs in place of CUs and DUs. Certain aspects provide a technical improvement to the technical field of telecommunications. In particular, certain aspects provide techniques to relay data between wireless devices that previously required directed wired connections.
  • Such wireless relaying of data reduces construction costs and allows for communications in previously inaccessible geographic locations. Certain aspects further provide advantages such as allowing devices to efficiently distinguish between data associated with different devices, thereby requiring less computational complexity and less compute cycles to process data. This may further reduce latency in processing data and transmitting it wirelessly at a relay between devices.
  • a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc.
  • UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
  • cdma2000 covers IS-2000, IS-95 and IS-856 standards.
  • a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM).
  • GSM Global System for Mobile Communications
  • An OFDMA network may implement a radio technology such as NR (e.g.
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • IEEE 802.16 WiMAX
  • IEEE 802.20 Flash-OFDMA
  • UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS).
  • NR is an emerging wireless communications technology under development in conjunction with the 5G Technology Forum (5GTF).
  • 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that use E-UTRA.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP).
  • cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
  • 3GPP2 3rd Generation Partnership Project 2
  • the techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies.
  • aspects may be described herein using terminology commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as 5G and later, including NR technologies.
  • FIG. 1 illustrates an example wireless network 100, such as a new radio (NR) or 5G network, in which aspects of the present disclosure may be performed.
  • BSs 110 e.g., including CUs and DUs corresponding to BSs 110
  • UEs 120 may be configured to perform techniques discussed herein for distinguishing between local and remote traffic when using wireless fronthauling.
  • the wireless network 100 may include a number of BSs 110 and other network entities.
  • a BS may be a station that communicates with UEs.
  • Each BS 110 may provide communication coverage for a particular geographic area.
  • the term "cell" can refer to a coverage area of a Node B and/or a Node B subsystem serving this coverage area, depending on the context in which the term is used.
  • the term "cell” and eNB, gNB, Node B, 5G NB, AP, NR BS, NR BS, or TRP may be interchangeable.
  • a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile base station.
  • the base stations may be interconnected to one another and/or to one or more other base stations or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces such as a direct physical connection, a virtual network, or the like using any suitable transport network.
  • any number of wireless networks may be deployed in a given geographic area.
  • Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies.
  • a RAT may also be referred to as a radio technology, an air interface, etc.
  • a frequency may also be referred to as a carrier, a frequency channel, etc.
  • Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • NR or 5G RAT networks may be deployed.
  • a BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cell.
  • a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription.
  • a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in the home, etc.).
  • CSG Closed Subscriber Group
  • a BS for a macro cell may be referred to as a macro BS.
  • a BS for a pico cell may be referred to as a pico BS.
  • a BS for a femto cell may be referred to as a femto BS or a home BS.
  • the BSs 110a, 110b and 110c may be macro BSs for the macro cells 102a, 102b and 102c, respectively.
  • the BS 110x may be a pico BS for a pico cell 102x.
  • the BSs 110y and 110z may be femto BS for the femto cells 102y and 102z, respectively.
  • a BS may support one or multiple (e.g., three) cells.
  • the wireless network 100 may also include relay stations.
  • a relay station is a station that receives a transmission of data and/or other information from an upstream station (e.g., a BS or a UE) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE or a BS).
  • a relay station may also be a UE that relays transmissions for other UEs.
  • a relay station 110r may communicate with the BS 110a and a UE 120r in order to facilitate communication between the BS 110a and the UE 120r.
  • a relay station may also be referred to as a relay BS, a relay, etc.
  • a relay station may be a DU.
  • the wireless network 100 may be a heterogeneous network that includes BSs of different types, e.g., macro BS, pico BS, femto BS, relays, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless network 100.
  • macro BS may have a high transmit power level (e.g., 20 Watts) whereas pico BS, femto BS, and relays may have a lower transmit power level (e.g., 1 Watt).
  • the wireless network 100 may support synchronous or asynchronous operation.
  • the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time.
  • the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time.
  • the techniques described herein may be used for both synchronous and asynchronous operation.
  • a network controller 130 may be coupled to a set of BSs and provide coordination and control for these BSs.
  • the network controller 130 may communicate with the BSs 110 via a backhaul.
  • the BSs 110 may also communicate with one another, e.g., directly or indirectly via wireless or wireline backhaul.
  • the UEs 120 may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile.
  • a UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, a Customer Premises Equipment (CPE), a cellular phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or medical equipment, a biometric sensor/device, a wearable device such as a smart watch, smart clothing, smart glasses, a smart wrist band, smart jewelry (e.g., a smart ring, a smart bracelet, etc.), an entertainment device (e.g., a music device, a video device, a
  • CPE Customer Premises Equipment
  • Some UEs may be considered evolved or machine-type communication (MTC) devices or evolved MTC (eMTC) devices.
  • MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that may communicate with a BS, another device (e.g., remote device), or some other entity.
  • a wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link.
  • Some UEs may be considered Internet-of-Things (IoT) devices.
  • IoT Internet-of-Things
  • a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and/or uplink.
  • a dashed line with double arrows indicates interfering transmissions between a UE and a BS.
  • Certain wireless networks utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink.
  • OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc.
  • K orthogonal subcarriers
  • Each subcarrier may be modulated with data.
  • modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM.
  • the spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth.
  • the spacing of the subcarriers may be 15 kHz and the minimum resource allocation (called a 'resource block') may be 12 subcarriers (or 180 kHz). Consequently, the nominal FFT size may be equal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10 or 20 megahertz (MHz), respectively.
  • the system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8 or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively.
  • NR may utilize OFDM with a CP on the uplink and downlink and include support for half-duplex operation using time division duplex (TDD).
  • TDD time division duplex
  • a single component carrier bandwidth of 100 MHz may be supported.
  • NR resource blocks may span 12 sub-carriers with a sub-carrier bandwidth of 75 kHz over a 0.1 ms duration.
  • Each radio frame may consist of 50 subframes with a length of 10 ms. Consequently, each subframe may have a length of 0.2 ms.
  • Each subframe may indicate a link direction (i.e., DL or UL) for data transmission and the link direction for each subframe may be dynamically switched.
  • Each subframe may include DL/UL data as well as DL/UL control data.
  • UL and DL subframes for NR may be as described in more detail below with respect to FIGs. 6 and 7 .
  • Beamforming may be supported and beam direction may be dynamically configured.
  • MIMO transmissions with precoding may also be supported.
  • MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL transmissions up to 8 streams and up to 2 streams per UE. Multi-layer transmissions with up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported with up to 8 serving cells.
  • NR may support a different air interface, other than an OFDM-based.
  • NR networks may include entities such CUs and/or DUs.
  • a scheduling entity e.g., a base station
  • the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize resources allocated by the scheduling entity.
  • Base stations are not the only entities that may function as a scheduling entity. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more subordinate entities (e.g., one or more other UEs).
  • the UE is functioning as a scheduling entity, and other UEs utilize resources scheduled by the UE for wireless communication.
  • a UE may function as a scheduling entity in a peer-to-peer (P2P) network, and/or in a mesh network.
  • P2P peer-to-peer
  • UEs may optionally communicate directly with one another in addition to communicating with the scheduling entity.
  • a scheduling entity and one or more subordinate entities may communicate utilizing the scheduled resources.
  • a RAN may include a CU and DUs.
  • a NR BS e.g., gNB, eNB, 5G Node B, Node B, transmission reception point (TRP), access point (AP)
  • NR cells can be configured as access cell (ACells) or data only cells (DCells).
  • the RAN e.g., a central unit or distributed unit
  • DCells may be cells used for carrier aggregation or dual connectivity, but not used for initial access, cell selection/reselection, or handover. In some cases DCells may not transmit synchronization signals-in some case cases DCells may transmit SS.
  • NR BSs may transmit downlink signals to UEs indicating the cell type. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine NR BSs to consider for cell selection, access, handover, and/or measurement based on the indicated cell type.
  • FIG. 2 illustrates an example logical architecture of a distributed radio access network (RAN) 200, which may be implemented in the wireless communication system illustrated in FIG. 1 .
  • a 5G access node 206 may include an access node controller (ANC) 202.
  • the ANC may be a central unit (CU) of the distributed RAN 200.
  • the backhaul interface to the next generation core network (NG-CN) 204 may terminate at the ANC.
  • the backhaul interface to neighboring next generation access nodes (NG-ANs) may terminate at the ANC.
  • the ANC may include one or more TRPs 208 (which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, or some other term). As described above, a TRP may be used interchangeably with "cell.”
  • the TRPs 208 may be a DU.
  • the TRPs may be connected to one ANC (ANC 202) or more than one ANC (not illustrated).
  • the TRP may be connected to more than one ANC.
  • a TRP may include one or more antenna ports.
  • the TRPs may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.
  • One or more TRPs 208 may communicate with one another over a wireless fronthaul as discussed herein.
  • one or more TRPs 208 may be configured to perform techniques discussed herein for distinguishing between local and remote traffic when using wireless fronthauling.
  • the local architecture 200 may be used to illustrate fronthaul definition.
  • the architecture may be defined that support fronthauling solutions across different deployment types.
  • the architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter).
  • the architecture may share features and/or components with LTE.
  • the next generation AN (NG-AN) 210 may support dual connectivity with NR.
  • the NG-AN may share a common fronthaul for LTE and NR.
  • the architecture may enable cooperation between and among TRPs 208 such as over a wireless fronthaul as discussed herein. For example, cooperation may be preset within a TRP and/or across TRPs via the ANC 202.
  • a dynamic configuration of split logical functions may be present within the architecture 200.
  • the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and a Physical (PHY) layers may be adaptably placed at the DU or CU (e.g., TRP or ANC, respectively).
  • a BS e.g., gNB
  • CU central unit
  • distributed units e.g., one or more TRPs 208.
  • FIG. 3 illustrates an example physical architecture of a distributed RAN 300, according to aspects of the present disclosure.
  • a centralized core network unit (C-CNU) 302 may host core network functions.
  • the C-CNU may be centrally deployed.
  • C-CNU functionality may be offloaded (e.g., to advanced wireless services (AWS)), in an effort to handle peak capacity.
  • AWS advanced wireless services
  • a centralized RAN unit (C-RU) 304 may host one or more ANC functions.
  • the C-RU may host core network functions locally.
  • the C-RU may have distributed deployment.
  • the C-RU may be closer to the network edge.
  • a DU 306 may host one or more TRPs (edge node (EN), an edge unit (EU), a radio head (RH), a smart radio head (SRH), or the like).
  • the DU may be located at edges of the network with radio frequency (RF) functionality.
  • DUs 306 may communicate with one another over a wireless fronthaul as discussed herein.
  • one or more DUs 306 may be configured to perform techniques discussed herein for distinguishing between local and remote traffic when using wireless fronthauling.
  • FIG. 4 illustrates example components of the BS 110 and UE 120 illustrated in FIG. 1 , which may be used to implement aspects of the present disclosure.
  • the BS may include a TRP.
  • One or more components of the BS 110 and UE 120 may be used to practice aspects of the present disclosure.
  • antennas 452, Tx/Rx 222, processors 466, 458, 464, and/or controller/processor 480 of the UE 120 and/or antennas 434, processors 460, 420, 438, and/or controller/processor 440 of the BS 110 may be used to perform the operations described herein related to distinguishing between local and remote traffic when using wireless fronthauling..
  • FIG. 4 shows a block diagram of a design of a BS 110 and a UE 120, which may be one of the BSs and one of the UEs in FIG. 1 .
  • the base station 110 may be the macro BS 110c in FIG. 1
  • the UE 120 may be the UE 120y.
  • the base station 110 may also be a base station of some other type.
  • the base station 110 may be equipped with antennas 434a through 434t, and the UE 120 may be equipped with antennas 452a through 452r.
  • a transmit processor 420 may receive data from a data source 412 and control information from a controller/processor 440.
  • the control information may be for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), etc.
  • the data may be for the Physical Downlink Shared Channel (PDSCH), etc.
  • the processor 420 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively.
  • the processor 420 may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signal.
  • a transmit (TX) multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 432a through 432t.
  • Each modulator 432 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream.
  • Each modulator 432 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal.
  • Downlink signals from modulators 432a through 432t may be transmitted via the antennas 434a through 434t, respectively.
  • the antennas 452a through 452r may receive the downlink signals from the base station 110 and may provide received signals to the demodulators (DEMODs) 454a through 454r, respectively.
  • Each demodulator 454 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples.
  • Each demodulator 454 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols.
  • a MIMO detector 456 may obtain received symbols from all the demodulators 454a through 454r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.
  • a receive processor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 460, and provide decoded control information to a controller/processor 480.
  • a transmit processor 464 may receive and process data (e.g., for the Physical Uplink Shared Channel (PUSCH)) from a data source 462 and control information (e.g., for the Physical Uplink Control Channel (PUCCH) from the controller/processor 480.
  • the transmit processor 464 may also generate reference symbols for a reference signal.
  • the symbols from the transmit processor 464 may be precoded by a TX MIMO processor 466 if applicable, further processed by the demodulators 454a through 454r (e.g., for SC-FDM, etc.), and transmitted to the base station 110.
  • the uplink signals from the UE 120 may be received by the antennas 434, processed by the modulators 432, detected by a MIMO detector 436 if applicable, and further processed by a receive processor 438 to obtain decoded data and control information sent by the UE 120.
  • the receive processor 438 may provide the decoded data to a data sink 439 and the decoded control information to the controller/processor 440.
  • the controllers/processors 440 and 480 may direct the operation at the base station 110 and the UE 120, respectively.
  • the processor 440 and/or other processors and modules at the base station 110 may perform or direct processes for the techniques described herein.
  • the processor 480 and/or other processors and modules at the UE 120 may also perform or direct processes for the techniques described herein.
  • the memories 442 and 482 may store data and program codes for the BS 110 and the UE 120, respectively.
  • a scheduler 444 may schedule UEs for data transmission on the downlink and/or uplink.
  • FIG. 5 illustrates a diagram 500 showing examples for implementing a communications protocol stack, according to aspects of the present disclosure.
  • the illustrated communications protocol stacks may be implemented by devices operating in a in a 5G system (e.g., a system that supports uplink-based mobility).
  • Diagram 500 illustrates a communications protocol stack including a Radio Resource Control (RRC) layer 510, a Packet Data Convergence Protocol (PDCP) layer 515, a Radio Link Control (RLC) layer 520, a Medium Access Control (MAC) layer 525, and a Physical (PHY) layer 530.
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • PHY Physical
  • the layers of a protocol stack may be implemented as separate modules of software, portions of a processor or ASIC, portions of non-collocated devices connected by a communications link, or various combinations thereof. Collocated and non-collocated implementations may be used, for example, in a protocol stack for a network access device (e.g., ANs, CUs, and/or DUs) or a UE.
  • a network access device e.g., ANs, CUs, and/or DUs
  • a first option 505-a shows a split implementation of a protocol stack, in which implementation of the protocol stack is split between a centralized network access device (e.g., an ANC 202 in FIG. 2 ) and distributed network access device (e.g., DU 208 in FIG. 2 ).
  • a centralized network access device e.g., an ANC 202 in FIG. 2
  • distributed network access device e.g., DU 208 in FIG. 2
  • an RRC layer 510 and a PDCP layer 515 may be implemented by the central unit
  • an RLC layer 520, a MAC layer 525, and a PHY layer 530 may be implemented by the DU.
  • the CU and the DU may be collocated or non-collocated.
  • the first option 505-a may be useful in a macro cell, micro cell, or pico cell deployment.
  • a second option 505-b shows a unified implementation of a protocol stack, in which the protocol stack is implemented in a single network access device (e.g., access node (AN), new radio base station (NR BS), a new radio Node-B (NR NB), a network node (NN), or the like.).
  • the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530 may each be implemented by the AN.
  • the second option 505-b may be useful in a femto cell deployment.
  • a UE may implement an entire protocol stack (e.g., the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530).
  • an entire protocol stack e.g., the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530.
  • FIG. 6 is a diagram 600 showing an example of a DL-centric subframe.
  • the DL-centric subframe may include a control portion 602.
  • the control portion 602 may exist in the initial or beginning portion of the DL-centric subframe.
  • the control portion 602 may include various scheduling information and/or control information corresponding to various portions of the DL-centric subframe.
  • the control portion 602 may be a physical DL control channel (PDCCH), as indicated in FIG. 6 .
  • the DL-centric subframe may also include a DL data portion 604.
  • the DL data portion 604 may sometimes be referred to as the payload of the DL-centric subframe.
  • the DL data portion 604 may include the communication resources utilized to communicate DL data from the scheduling entity (e.g., UE or BS) to the subordinate entity (e.g., UE).
  • the DL data portion 604 may be a physical DL shared channel (PDSCH).
  • PDSCH physical DL shared channel
  • the DL-centric subframe may also include a common UL portion 606.
  • the common UL portion 606 may sometimes be referred to as an UL burst, a common UL burst, and/or various other suitable terms.
  • the common UL portion 606 may include feedback information corresponding to various other portions of the DL-centric subframe.
  • the common UL portion 606 may include feedback information corresponding to the control portion 602.
  • Non-limiting examples of feedback information may include an ACK signal, a NACK signal, a HARQ indicator, and/or various other suitable types of information.
  • the common UL portion 606 may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests (SRs), and various other suitable types of information.
  • RACH random access channel
  • SRs scheduling requests
  • the end of the DL data portion 604 may be separated in time from the beginning of the common UL portion 606.
  • This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and/or various other suitable terms.
  • This separation provides time for the switch-over from DL communication (e.g., reception operation by the subordinate entity (e.g., UE)) to UL communication (e.g., transmission by the subordinate entity (e.g., UE)).
  • DL communication e.g., reception operation by the subordinate entity (e.g., UE)
  • UL communication e.g., transmission by the subordinate entity (e.g., UE)
  • FIG. 7 is a diagram 700 showing an example of an UL-centric subframe.
  • the UL -centric subframe may include a control portion 702.
  • the control portion 702 may exist in the initial or beginning portion of the UL-centric subframe.
  • the control portion 702 in FIG. 7 may be similar to the control portion described above with reference to FIG. 6 .
  • the UL-centric subframe may also include an UL data portion 704.
  • the UL data portion 704 may sometimes be referred to as the payload of the UL-centric subframe.
  • the UL portion may refer to the communication resources utilized to communicate UL data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or BS).
  • the control portion 702 may be a physical DL control channel (PDCCH).
  • PDCH physical DL control channel
  • the end of the control portion 702 may be separated in time from the beginning of the UL data portion 704. This time separation may sometimes be referred to as a gap, guard period, guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the scheduling entity) to UL communication (e.g., transmission by the scheduling entity).
  • the UL-centric subframe may also include a common UL portion 706.
  • the common UL portion 706 in FIG. 7 may be similar to the common UL portion 706 described above with reference to FIG. 7 .
  • the common UL portion 706 may additional or alternative include information pertaining to channel quality indicator (CQI), sounding reference signals (SRSs), and various other suitable types of information.
  • CQI channel quality indicator
  • SRSs sounding reference signals
  • One of ordinary skill in the art will understand that the foregoing is merely one example of an UL-centric subframe and alternative structures having similar features may exist without necessarily deviating from the aspects described herein.
  • two or more subordinate entities may communicate with each other using sidelink signals.
  • Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and/or various other suitable applications.
  • a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through the scheduling entity (e.g., UE or BS), even though the scheduling entity may be utilized for scheduling and/or control purposes.
  • the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum).
  • a UE may operate in various radio resource configurations, including a configuration associated with transmitting pilots using a dedicated set of resources (e.g., a radio resource control (RRC) dedicated state, etc.) or a configuration associated with transmitting pilots using a common set of resources (e.g., an RRC common state, etc.).
  • RRC radio resource control
  • the UE may select a dedicated set of resources for transmitting a pilot signal to a network.
  • the UE may select a common set of resources for transmitting a pilot signal to the network.
  • a pilot signal transmitted by the UE may be received by one or more network access devices, such as an AN, or a DU, or portions thereof.
  • Each receiving network access device may be configured to receive and measure pilot signals transmitted on the common set of resources, and also receive and measure pilot signals transmitted on dedicated sets of resources allocated to the UEs for which the network access device is a member of a monitoring set of network access devices for the UE.
  • One or more of the receiving network access devices, or a CU to which receiving network access device(s) transmit the measurements of the pilot signals may use the measurements to identify serving cells for the UEs, or to initiate a change of serving cell for one or more of the UEs.
  • communication between a UE (e.g., UE 120 of FIG. 1 ) and an AN (e.g., AN 206 of FIG. 2 ) may be via an ANC (e.g., ANC 202 of FIG. 2 , a CU (e.g., a type of network node)).
  • the CU may communicate via a backhaul interface (e.g., a wired interface) with the core network (e.g., NG-CN 204 of FIG. 2 ).
  • the CU may further be connected via a wired fronthaul interface to one or more TRPs (e.g., TRPs 208 of FIG. 2 , DUs).
  • TRPs e.g., TRPs 208 of FIG. 2 , DUs
  • the UE 120 may utilize communication technologies with limited range (e.g., mmW with line-of-sight range).
  • a backhaul interface e.g., a wired interface such as N2 (S1-MME), N3 (S1-U), etc.
  • S1-MME wireless interface
  • S1-U wireless interface
  • cost due to physical restrictions and/or cost.
  • a relay station e.g., relay DU
  • FIG. 8 is a block diagram illustrating an example physical architecture of a distributed RAN 800 (e.g., similar to RAN 200 of FIG. 2 ) that supports wireless relay, in accordance with certain aspects of the present disclosure.
  • the RAN 800 includes a CU central control plane (CU-C) 802a (e.g., similar to ANC 202 of FIG. 2 ) used for handling control plane packets (e.g., signaling information) and a CU user plane (CU-U) 802b (e.g., similar to ANC 202 of FIG. 2 ) used for handling user plane packets (e.g., traffic information).
  • CU-C CU central control plane
  • CU-U CU user plane
  • the RAN 800 further includes a DU 804 (e.g., similar to TRP 208 of FIG. 2 ) and a relay DU 806 (e.g., similar to TRP 208 of FIG. 2 ).
  • a DU 804 e.g., similar to TRP 208 of FIG. 2
  • a relay DU 806 e.g., similar to TRP 208 of FIG. 2 .
  • the CU-C 802a and CU-U 802b, DU 804, and relay DU 806 form an access node (e.g., 5G access node).
  • the CU-C 802a and CU-U 802b are connected by a wired interface to the DU 804.
  • CU-C 802a and CU-U 802b are connected directly to relay DU 806 via a wireless interface.
  • DU 804 and relay DU 806 are not connected by a wired interface and instead communicate over a wireless interface.
  • UE 808 (e.g., similar to UE 120 of FIG. 1 ) may be configured to communicate via a wireless interface with relay DU 806. Though now shown, there may be additional relay DUs 806 between DU 804 and UE 808 configured to wirelessly interface with one another to forward packets between one another.
  • relay DU 806 is configured to act as a wireless relay between DU 804 and UE 808. Accordingly, DU 804 and relay DU 806 may implement a portion of a wireless fronthaul for the CU-C 802a and CU-U 802b. For example, DU relay 806 may be configured to receive packets (e.g., UL packets) from UE 808 and forward the packets wirelessly to DU 804, which forwards the packets over a wired connection to CU-C 802a or CU-U 802b.
  • packets e.g., UL packets
  • DU 804 may be configured to receive packets (e.g., DL packets) from CU-C 802a or CU-U 802b over the wired connection and forward the packets wirelessly to relay DU 806, which forwards the packets wirelessly to UE 808.
  • DUs e.g., DU 804 and relay DU 806 acting as wireless relays
  • other devices may instead be used to perform the functions described with respect to any one or all of the DUs acting as wireless relays.
  • a UE, gNB, or other access node may perform the functions described with respect to the DU acting as a wireless relay.
  • CUs it should be noted that other devices (e.g., gNBs) may instead be used to perform the functions described with respect to any one or all of the CUs.
  • each of the wireless links between relay DUs 806, between relay DU 806 and UE 808, and between relay DU 806 and DU 804 is defined by one or more radio links (e.g., as identified by one or more cell radio network temporary identifiers (C-RNTIs)) (e.g., including one or more backhaul links, one or more access links, or a combination of one or more backhaul links and one or more access links).
  • C-RNTIs cell radio network temporary identifiers
  • the UE 808 connects to the relay DU 806/DU 804/CU-C 802a or CU-U 802b and establishes one or more radio bearers (RBs) corresponding to the connections.
  • RB radio bearers
  • the UE 808 establishes a signaling RB (SRB) for carrying signal information and a data RB (DRB) for carrying data traffic.
  • SRB signaling RB
  • DRB data RB
  • a RB may specify the configuration of protocol layers (e.g., Layer-2 and physical layer) between two devices.
  • FIG. 9 illustrates an example communications protocol stack for communicating in a RAN such as RAN 800, in accordance with certain aspects of the present disclosure.
  • UE 808 directly communicates wirelessly with DU 804, which communicates with CU 802 (e.g., a single physical CU implementing CU-C 802a or CU-U 802b) via a wired interface.
  • CU 802 e.g., a single physical CU implementing CU-C 802a or CU-U 802b
  • a RB 900 is established between UE 808 and CU 802, which is shown as a communications protocol stack.
  • the UE 808 utilizes the RB 900 established between UE 808 and CU 802 for communication with the DU 804.
  • RB 900 is divided into an RB upper portion (RB Up) 902 and an RB lower portion (RB Low) 904.
  • the RB Up 902 includes a PDCP layer, such as PDCP layer 515 of FIG. 5 .
  • the RB Up 902 may further include a portion of a RLC layer (e.g., RLC-hi, which performs retransmissions), such as RLC layer 520 of FIG. 5 .
  • the RB Low 904 includes a RLC layer (or a portion of a RLC layer, such as RLC-lo which performs segmentation only), such as RLC layer 520 of FIG. 5 .
  • RB Low 904 may further include a MAC layer (e.g., MAC layer 525 of FIG. 5 ) and a PHY layer (e.g., PHY layer 530 of FIG. 5 ).
  • the UE 808 only sustains (e.g., utilizes, maintains packet encapsulation, etc.) the RB Low 904 to connect with DU 804 and sustains the RB Up 902 to connect with CU 802 (via DU 804).
  • RB Low 904 is extended on the fronthaul from DU 804 to CU 802 using a normal fronthaul transport as shown and a tunnel layer (e.g., including a tunnel ID) to map the fronthaul transport to the RB 900 of the UE 808.
  • SRBs may be routed from UE 808 to CU-C 802a and DRBs may be routed from UE 808 to CU-U 802b.
  • a signaling connection is sustained between CU-C 802a and DU 804, referred to as F1-C.
  • One portion of Fl-C may be a fronthaul application protocol, referred to as F1-AP.
  • relay DU 806 for relay DU 806 to act as a wireless relay between UE 808 and DU 804, the relay DU 806 supports both a UE function (e.g., functionality similar to UE 808) and a DU function (e.g., functionality similar to DU 804).
  • relay DU 806 may utilize the DU function to communicate with UE 808 and the UE function to communicate with DU 804.
  • the UE 808 can connect to the relay DU 806 in a similar manner that it connects to a gNB (e.g., using a UMTS air interface (Uu interface)), so no changes need to be made to the UE 808 to support the relay function of relay DU 806.
  • a gNB e.g., using a UMTS air interface (Uu interface)
  • the relay DU 806 can connect to an access node including DU 804, CU-C 802a (via DU 804), and CU-U 802b (via DU 804) using SRBs and DRBs using the UE function in the same manner as UE 808 would.
  • relay DU 806 uses an upper portion of the SRBs and DRBs to connect to CU-C 802a and CU-U 802b (via DU 804) and a lower portion of the SRBs and DRBs to connect to DU 804 for communicating local data of the relay DU 806 (e.g., for an access link of DU 806). Further, in certain aspects, relay DU 806 uses the lower portion of the SRBs and DRBs to communicate remote data of the UE 808 (e.g., for an access link of UE 808).
  • the relay DU 806, DU 804, CU-C 802a, and CU-U 802b need to be able to distinguish between whether the data in the lower portion of the SRBs and DRBs is local data or remote data.
  • techniques herein relate to separating local and remote traffic in a RB by inserting a multiplexing (MUX) layer (also referred to as an adaptation layer) between the lower and upper portion of the RB.
  • MUX multiplexing
  • FIG. 10 illustrates an example communications protocol stack with a MUX layer between a lower and upper portion of a RB used for communicating remote data, in accordance with certain aspects of the present disclosure.
  • FIG. 10A illustrates an example communications protocol stack with a MUX layer between a lower and upper portion of a RB used for communicating local data, in accordance with certain aspects of the present disclosure.
  • UE 808 directly communicates wirelessly with relay DU 806, which communicates wirelessly with DU 804.
  • DU 804 communicates with CU 802 (e.g., a single physical CU implementing CU-C 802a or CU-U 802b) via a wired interface.
  • CU 802 e.g., a single physical CU implementing CU-C 802a or CU-U 802b
  • a RB 1000 is established between UE 808, relay DU 806, DU 804, and CU 802, which is shown as a communications protocol stack for the devices to communicate with one another.
  • RB 1000 is divided into an RB upper portion (RB-B Up) 1002 and an RB lower portion (RB-B Low) 1004.
  • the UE 808 only sustains the RB-B Low 1004 to connect with relay DU 806 (e.g., using a DU function of DU 806) and sustains the RB Up 1002 to connect with CU 802 (via relay DU 806 and DU 804).
  • relay DU 806 (e.g., a UE function of relay DU 806) is configured to sustain the RB-B Low 1004 of RB 1000 to communicate with DU 804 and CU 802.
  • RB-B Low 1004 is divided into multiple portions including a RB lower portion (RB-A Low) 1006.
  • the relay DU 806 only sustains the RB-A Low 1006 to connect with DU 804.
  • RB-A Low 1006 is extended on the fronthaul from DU 804 to CU 802 using a normal fronthaul transport as shown and a tunnel layer (Tunnel-A) including a tunnel ID to map the fronthaul transport to the RB 1000 of the relay DU 806 and UE 808 so packets can be forwarded to relay DU 806 from DU 804 based on the tunnel ID included in Tunnel-A.
  • tunnel-A tunnel layer
  • relay DU 806 extends RB-B Low 1004 to communicate with CU 802 (via DU 804) by sustaining with CU 802 a Tunnel B 1010.
  • the Tunnel B 1010 may include a tunnel ID that maps to UE 808 so that packets can be forwarded to the correct UE 808 based on the tunnel ID included in Tunnel-B 1010 by relay DU 806, without relay DU 806 needing to read RB-B Up 1002.
  • relay DU 806 sustains a RB upper portion (RB-A up) 1012 with CU 802 to communicate with CU 802.
  • RB-A low 1006 and Tunnel A may need to carry RB-A up 1012 for local data and Tunnel B 1010 (which holds RB-B Up 1002) for remote data.
  • a MUX layer 1008 is inserted between RB-A low 1006 and either RB-A up 1012 or Tunnel B 1010, depending on which is included.
  • MUX layer 1008 inserts a field into the protocol stack which indicates if the encapsulated data refers to local data or remote data.
  • CU 802 is configured to encapsulate DL packets destined for UE 808 (i.e., remote data) with the communications protocol stack shown in FIG. 10 in CU 802. Further, in certain aspects, on the DL, CU 802 is configured to encapsulate DL packets destined for relay DU 806 (i.e., local data) with the communications protocol stack shown in FIG. 10A in CU 802.
  • FIG. 11 illustrates example operations 1100 for processing DL packets from a CU at a relay DU. According to certain aspects, operations 1100 may be performed by a relay DU, such as relay DU 806.
  • the relay DU processes the lower portion of the RB corresponding to RB-A low of a received DL packet and determines the lower portion of the RB to be RB-A low.
  • the relay DU processes the MUX layer field of the DL packet based on the lower portion of the RB being RB-A low indicating (e.g., implicitly) that the DL packet includes a MUX layer field.
  • the relay DU determines if the packet includes remote data or local data based on an indicator in the MUX layer field.
  • the relay DU determines the packet includes a Tunnel-B header and identifies the tunnel ID in the Tunnel-B header.
  • the tunnel ID may identify the RB-B low (e.g., UE 808) over which to forward the packet.
  • the relay DU forwards the packet based on the tunnel ID to UE 808.
  • the relay DU determines the packet includes local data, the relay DU determines the packet includes a RB-A Up and processes the RB-A Up at the relay DU.
  • relay DU 806 is configured to encapsulate UL packets received from UE 808 (i.e., remote data) to send to CU 802 with the communications protocol stack shown in FIG. 10 in relay DU 806. Further, in certain aspects, on the UL, relay DU 806 is configured to encapsulate UL packets generated by relay DU 806 (i.e., local data) to send to CU 802 with the communications protocol stack shown in FIG. 10A in relay DU 806.
  • FIG. 12 illustrates example operations 1200 for processing UL packets from a relay DU to a CU. According to certain aspects, operations 1200 may be performed by a CU, such as CU 802.
  • the CU processes Tunnel-A and identifies a tunnel ID in Tunnel-A.
  • the CU processes the MUX layer field of the UL packet based on the Tunnel-A indicating (e.g., implicitly) that the UL packet includes a MUX layer field.
  • the CU determines if the packet includes remote data or local data based on an indicator in the MUX layer field.
  • the CU determines the packet includes remote data
  • the CU determines the packet includes a Tunnel-B header and identifies the tunnel ID in the Tunnel-B header.
  • the CU identifies the RB-B Up where the packet is to be forwarded and processed.
  • the CU determines the packet includes local data, the CU determines the packet includes a RB-A Up and processes the RB-A Up at the CU.
  • the MUX layer may only be extended between relay DU 806 to DU 804.
  • FIG. 13 illustrates an example communications protocol stack with a MUX layer between a lower and upper portion of a RB used for communicating remote data, in accordance with certain aspects of the present disclosure.
  • FIG. 13A illustrates an example communications protocol stack with a MUX layer between a lower and upper portion of a RB used for communicating local data, in accordance with certain aspects of the present disclosure.
  • UE 808 directly communicates wirelessly with relay DU 806, which communicates wirelessly with DU 804.
  • DU 804 communicates with CU 802 (e.g., a single physical CU implementing CU-C 802a or CU-U 802b) via a wired interface.
  • CU 802 e.g., a single physical CU implementing CU-C 802a or CU-U 802b
  • a RB 1300 is established between UE 808, relay DU 806, DU 804, and CU 802, which is shown as a communications protocol stack for the devices to communicate with one another.
  • RB 1300 is the same as RB 1000 as discussed, except that MUX layer 1308 (corresponding to MUX layer 1008) only extends from relay DU 806 to DU 804 and not to CU 802 as with RB 1000. Therefore, instead of the MUX layer carrying a field which indicates if the encapsulated data refers to local data or remote data between DU 804 and CU 802, Tunnel-A includes the field which indicates if the encapsulated data refers to local data or remote data between DU 804 and CU 802.
  • CU 802 is configured to encapsulate DL packets destined for UE 808 (i.e., remote data) with the communications protocol stack shown in FIG. 13 in CU 802. Further, in certain aspects, on the DL, CU 802 is configured to encapsulate DL packets destined for relay DU 806 (i.e., local data) with the communications protocol stack shown in FIG. 13A in CU 802.
  • the relay DU 806 may be configured to process DL packets from a CU 802 using operations similar to operations 1100 described with respect to FIG. 11 . However, when a DL packet arrives at DU 804 from CU 802, the DU 804 may process the tunnel header Tunnel-A and identify the multiplexing field. Based on the multiplexing field, DU 804 determines if the packet includes remote data or local data. The DU 804 then encapsulates the data with the MUX layer and sets a value in the MUX layer to indicate if the packet includes remote data or local data.
  • relay DU 806 is configured to encapsulate UL packets received from UE 808 (i.e., remote data) to send to CU 802 with the communications protocol stack shown in FIG. 13 in relay DU 806. Further, in certain aspects, on the UL, relay DU 806 is configured to encapsulate UL packets generated by relay DU 806 (i.e., local data) to send to CU 802 with the communications protocol stack shown in FIG. 13A in relay DU 806.
  • the DU 804 may process RB-A low, and based on an ID of RB-A low, identifier a tunnel ID.
  • the DU 804 then processes the MUX layer and translates a value in the MUX layer indicating if the packet includes remote data or local data to a corresponding field in the tunnel header Tunnel-A and then forwards the packet to CU 802.
  • the CU 802 may be configured to process UL packets from a CU 802 using operations similar to operations 1200 described with respect to FIG. 12 . However, at 1204 and 1206, instead of processing the MUX layer field to determine if the packet includes remote data or local data, the CU 802 processes the field in the tunnel header Tunnel-A.
  • techniques herein relate to separating local and remote traffic in a RB by inserting a MUX layer between the lower and upper portion of the RB can also be used for multi-hop scenarios where multiple relay DUs are used along the connection path between a UE and a CU.
  • each relay DU is configured to add a MUX layer above the lower portion of the RB communicated to the next DU.
  • FIG. 14 illustrates an example communications protocol stack with a MUX layer between a lower and upper portion of a RB used for communicating remote data, in accordance with certain aspects of the present disclosure.
  • FIG. 14A illustrates an example communications protocol stack with a MUX layer between a lower and upper portion of a RB used for communicating local data, in accordance with certain aspects of the present disclosure.
  • UE 808 directly communicates wirelessly with relay DU 806b, which communicates wirelessly with relay DU 806a, which communicates wirelessly with DU 804.
  • DU 804 communicates with CU 802 (e.g., a single physical CU implementing CU-C 802a or CU-U 802b) via a wired interface.
  • CU 802 e.g., a single physical CU implementing CU-C 802a or CU-U 802b
  • a RB 1400 is established between UE 808, relay DU 806b, DU 806a, DU 804, and CU 802, which is shown as a communications protocol stack for the devices to communicate with one another.
  • RB 1400 is divided into an RB upper portion (RB-C Up) and an RB lower portion (RB-C Low).
  • the UE 808 only sustains the RB-C Low to connect with relay DU 806b (e.g., using a DU function of DU 806b) and sustains the RB-C Up to connect with CU 802 (via relay DU 806b, relay DU 806a, and DU 804).
  • relay DU 806b (e.g., a UE function of relay DU 806b) is configured to sustain the RB-C Low of RB 1400 to communicate with relay DU 806a and CU 802.
  • RB-C Low is divided into multiple portions including a RB lower portion (RB-B Low).
  • RB-B Low of RB 1400 may be used similar to RB-B Low 1004 of RB 1000 in that relay DU 806b only sustains the RB-B Low to connect with relay DU 806a (e.g., using a DU function of DU 806b).
  • Relay DU 806b is further configured to insert a MUX layer 1420 above RB-B low which includes a field in the protocol stack which indicates if the encapsulated data refers to local data or remote data of relay DU 806b.
  • the relay DU 806b sustains the MUX layer 1420 with CU 802.
  • RB 1400 The remaining use of RB 1400 is similar to RB 1000 as described. However, the CU 802 processes multiple MUX layers corresponding to the number of relays DU 806 used in the multi-hop process to determine whether the data in higher layers is for the corresponding relay DU 806 (i.e., local data), or for another relay DU 806 or UE 808 (i.e., remote data).
  • the CU 802 processes multiple MUX layers corresponding to the number of relays DU 806 used in the multi-hop process to determine whether the data in higher layers is for the corresponding relay DU 806 (i.e., local data), or for another relay DU 806 or UE 808 (i.e., remote data).
  • relay DU 806b extends RB-C Low to communicate with CU 802 (via relay DU 806b and DU 804) by sustaining with CU 802 an additional MUX layer 1420.
  • relay DU 806b further sustains a RB upper portion (RB-B up) 1422 with CU 802 to communicate with CU 802.
  • CU 802 is configured to encapsulate DL packets destined for UE 808 (i.e., remote data) with the communications protocol stack shown in FIG. 14 in CU 802. Further, in certain aspects, on the DL, CU 802 is configured to encapsulate DL packets destined for relay DU 806b (i.e., local data) with the communications protocol stack shown in FIG. 14A in CU 802.
  • relay DU 806b is configured to encapsulate UL packets received from UE 808 (i.e., remote data) to send to CU 802 with the communications protocol stack shown in FIG. 14 in relay DU 806b. Further, in certain aspects, on the UL, relay DU 806b is configured to encapsulate UL packets generated by relay DU 806b (i.e., local data) to send to CU 802 with the communications protocol stack shown in FIG. 14A in relay DU 806b. In certain aspects, RB 1400 is processed similar to RB 1000.
  • the MUX layer may only be extended between relay DU 806 to DU 804.
  • FIG. 15 illustrates an example communications protocol stack with a MUX layer between a lower and upper portion of a RB used for communicating remote data, in accordance with certain aspects of the present disclosure.
  • FIG. 15A illustrates an example communications protocol stack with a MUX layer between a lower and upper portion of a RB used for communicating local data, in accordance with certain aspects of the present disclosure.
  • UE 808 directly communicates wirelessly with relay DU 806b, which communicates wirelessly with relay DU 806a, which communicates wirelessly with DU 804.
  • DU 804 communicates with CU 802 (e.g., a single physical CU implementing CU-C 802a or CU-U 802b) via a wired interface.
  • CU 802 e.g., a single physical CU implementing CU-C 802a or CU-U 802b
  • a RB 1400 is established between UE 808, relay DU 806b, DU 806a, DU 804, and CU 802, which is shown as a communications protocol stack for the devices to communicate with one another.
  • RB 1500 is the same as RB 1400 as discussed, except that MUX layer 1508 (corresponding to MUX layer 1008 as shown in RB 1000 and also included in RB 1400 as discussed) only extends from relay DU 806a to DU 804 and not to CU 802 as with RB 1400. Therefore, instead of the MUX layer carrying a field which indicates if the encapsulated data refers to local data or remote data between DU 804 and CU 802, Tunnel-A includes the field which indicates if the encapsulated data refers to local data or remote data between DU 804 and CU 802, as discussed with respect to RB 1300.
  • CU 802 is configured to encapsulate DL packets destined for UE 808 (i.e., remote data) with the communications protocol stack shown in FIG. 15 in CU 802. Further, in certain aspects, on the DL, CU 802 is configured to encapsulate DL packets destined for relay DU 806b (i.e., local data) with the communications protocol stack shown in FIG. 15A in CU 802.
  • relay DU 806b is configured to encapsulate UL packets received from UE 808 (i.e., remote data) to send to CU 802 with the communications protocol stack shown in FIG. 15 in relay DU 806b. Further, in certain aspects, on the UL, relay DU 806b is configured to encapsulate UL packets generated by relay DU 806b (i.e., local data) to send to CU 802 with the communications protocol stack shown in FIG. 15A in relay DU 806. In certain aspects, RB 1500 is processed similar to RB 1300.
  • techniques herein relate to separating local and remote traffic in a RB by inserting a MUX layer between the lower and upper portion of the RB can also be used for multi-hop scenarios where multiple relay DUs are used along the connection path between a UE and a CU in the presence of a routing layer in the protocol stack.
  • each relay DU is configured to add a MUX layer above the lower portion of the RB communicated to the next DU.
  • the multiple tunnels and MUX layers can be replaced with a flat routing layer (RT).
  • the MUX layer is used to differentiation between RT for remote data and an RB upper portion for local data of the relay DU.
  • FIG. 16 illustrates an example communications protocol stack with a MUX layer between a lower and upper portion of a RB used for communicating remote data, in accordance with certain aspects of the present disclosure.
  • FIG. 16A illustrates an example communications protocol stack with a MUX layer between a lower and upper portion of a RB used for communicating local data, in accordance with certain aspects of the present disclosure.
  • UE 808 directly communicates wirelessly with relay DU 806b, which communicates wirelessly with relay DU 806a, which communicates wirelessly with DU 804.
  • DU 804 communicates with CU 802 (e.g., a single physical CU implementing CU-C 802a or CU-U 802b) via a wired interface.
  • CU 802 e.g., a single physical CU implementing CU-C 802a or CU-U 802b
  • a RB 1600 is established between UE 808, relay DU 806b, DU 806a, DU 804, and CU 802, which is shown as a communications protocol stack for the devices to communicate with one another.
  • RB 1600 is divided into an RB upper portion (RB-C Up) and an RB lower portion (RB-C Low).
  • the UE 808 only sustains the RB-C Low to connect with relay DU 806b (e.g., using a DU function of DU 806b) and sustains the RB-C Up to connect with CU 802 (via relay DU 806b, relay DU 806a, and DU 804).
  • relay DU 806b (e.g., a UE function of relay DU 806b) is configured to sustain the RB-C Low of RB 1600 to communicate with relay DU 806a and CU 802.
  • RB-C Low is divided into multiple portions including a RB lower portion (RB-B Low).
  • Relay DU 806b may only sustain the RB-B Low to connect with relay DU 806a (e.g., using a DU function of DU 806b).
  • relay DU 806b extends RB-C Low to communicate with CU 802 (via relay DU 806a and DU 804) by sustaining with CU 802 a Tunnel C.
  • the Tunnel C may include a tunnel ID that maps to UE 808 so that packets can be forwarded to the correct UE 808 based on the tunnel ID included in Tunnel-C by relay DU 806b, without relay DU 806b needing to read RB-C Up.
  • the relay DU 806b further sustains a routing (RT) layer with relay DU 806a that includes routing information for routing packets between relay DU 806b and relay DU 806a.
  • RT routing
  • relay DU 806b sustains a RB upper portion (RB-B up) with CU 802 to communicate with CU 802.
  • relay DU 806b inserts a MUX layer between RB-B low and either RB-B Up or RT and Tunnel C.
  • the MUX layer may be extended across all relay DUs 806 including relay DU 806a to DU 804.
  • Relay DU 806a and DU 804 may be configured to change the routing information to indicate routing of packets between the appropriate devices.
  • FIG. 17 illustrates example operations that may be performed by a wireless device such as a relay DU (e.g., relay DU 806) for communicating remote and local data in a wireless fronthaul of a wireless network, in accordance with aspects of the present disclosure.
  • a wireless device such as a relay DU (e.g., relay DU 806) for communicating remote and local data in a wireless fronthaul of a wireless network, in accordance with aspects of the present disclosure.
  • a relay DU e.g., relay DU 806
  • Operations 1700 begin at block 1702 by relay DU communicating with a user equipment (UE) over a first wireless link. Further, at block 1704, the relay DU communicates with a base station (BS) over a second wireless link. Continuing, at block 1706, the relay DU terminates a lower portion of a radio bearer for the UE, wherein the radio bearer comprises an upper portion and a lower portion, wherein the radio bearer is established between the UE and a network node of the wireless network, and wherein the UE is configured to communicate with the network node via the relay DU and the BS.
  • UE user equipment
  • BS base station
  • the relay DU forwards the upper portion of the radio bearer for the UE to the network node over the second wireless link.
  • the relay DU carries a lower portion of a second radio bearer between the relay DU and the BS and a multiplexing layer indicating whether the lower portion of the second radio bearer includes an upper portion of the second radio bearer corresponding to local data or a tunnel with the upper portion of the radio bearer for the UE corresponding to remote data.
  • FIG. 18 illustrates a communications device 1800 that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations illustrated in FIG. 17 .
  • the communications device 1800 includes a processing system 1814 coupled to a transceiver 1812.
  • the transceiver 1812 is configured to transmit and receive signals for the communications device 1800 via an antenna 1820, such as the various signals described herein.
  • the processing system 1814 may be configured to perform processing functions for the communications device 1800, including processing signals received and/or to be transmitted by the communications device 1800.
  • the processing system 1814 includes a processor 1809 coupled to a computer-readable medium/memory 1810 via a bus 1824.
  • the computer-readable medium/memory 1810 is configured to store instructions that when executed by processor 1809, cause the processor 1809 to perform the operations illustrated in FIG. 17 , or other operations for performing the various techniques discussed herein.
  • the processing system 1814 further includes a communicating component 1802 for performing the operations illustrated at 1702 and/or 1704 in FIG. 17 . Additionally, the processing system 1814 includes a terminating component 1804 for performing the operations illustrated at 1706 in FIG. 17 . The processing system 1814 also includes a forwarding component 1806 for performing the operations illustrated at 1708 in FIG. 17 . The processing system 1814 further includes a carrying component 1808 for performing the operations illustrated at 1710 in FIG. 17 .
  • the communicating component 1802, terminating component 1804, forwarding component 1806, and carrying component 1808 may be coupled to the processor 1809 via bus 1824.
  • the communicating component 1802, terminating component 1804, forwarding component 1806, and carrying component 1808 may be hardware circuits.
  • the communicating component 1802, terminating component 1804, forwarding component 1806, and carrying component 1808 may be software components that are executed and run on processor 1809.
  • the methods disclosed herein comprise one or more steps or actions for achieving the described method.
  • the method steps and/or actions may be interchanged with one another without departing from the scope of the claims.
  • the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.
  • a phrase referring to "at least one of' a list of items refers to any combination of those items, including single members.
  • "at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).
  • determining encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.
  • the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions.
  • the means may include various hardware and/or software component(s) and/or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor.
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • PLD programmable logic device
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • an example hardware configuration may comprise a processing system in a wireless node.
  • the processing system may be implemented with a bus architecture.
  • the bus may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints.
  • the bus may link together various circuits including a processor, machine-readable media, and a bus interface.
  • the bus interface may be used to connect a network adapter, among other things, to the processing system via the bus.
  • the network adapter may be used to implement the signal processing functions of the PHY layer.
  • a user interface e.g., keypad, display, mouse, joystick, etc.
  • the bus may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further.
  • the processor may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Those skilled in the art will recognize how best to implement the described functionality for the processing system depending on the particular application and the overall design constraints imposed on the overall system.
  • the functions may be stored or transmitted over as one or more instructions or code on a computer readable medium.
  • Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • Computer-readable media include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • the processor may be responsible for managing the bus and general processing, including the execution of software modules stored on the machine-readable storage media.
  • a computer-readable storage medium may be coupled to a processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor.
  • the machine-readable media may include a transmission line, a carrier wave modulated by data, and/or a computer readable storage medium with instructions stored thereon separate from the wireless node, all of which may be accessed by the processor through the bus interface.
  • the machine-readable media, or any portion thereof may be integrated into the processor, such as the case may be with cache and/or general register files.
  • machine-readable storage media may include, by way of example, RAM (Random Access Memory), flash memory, ROM (Read Only Memory), PROM (Programmable Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof.
  • RAM Random Access Memory
  • ROM Read Only Memory
  • PROM PROM
  • EPROM Erasable Programmable Read-Only Memory
  • EEPROM Electrical Erasable Programmable Read-Only Memory
  • registers magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof.
  • the machine-readable media may be embodied in a computer-program product.
  • a software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media.
  • the computer-readable media may comprise a number of software modules.
  • the software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions.
  • the software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices.
  • a software module may be loaded into RAM from a hard drive when a triggering event occurs.
  • the processor may load some of the instructions into cache to increase access speed.
  • One or more cache lines may then be loaded into a general register file for execution by the processor.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • Disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray ® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.
  • computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media).
  • computer-readable media may comprise transitory computer-readable media (e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media.
  • certain aspects may comprise a computer program product for performing the operations presented herein.
  • a computer program product may comprise a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein.
  • modules and/or other appropriate means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station as applicable.
  • a user terminal and/or base station can be coupled to a server to facilitate the transfer of means for performing the methods described herein.
  • various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.), such that a user terminal and/or base station can obtain the various methods upon coupling or providing the storage means to the device.
  • storage means e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.
  • CD compact disc
  • floppy disk etc.
  • any other suitable technique for providing the methods and techniques described herein to a device can be utilized.

Landscapes

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

Claims (7)

  1. Procédé (1700) pour une communication de données distantes et locales dans une liaison frontale sans fil d'un réseau sans fil, la liaison frontale sans fil comprenant un relais (806) configuré pour communiquer sans fil avec un équipement d'utilisateur (808), UE, sur une première liaison sans fil et une station de base (804), BS, sur une seconde liaison sans fil, dans lequel une porteuse radio (1000) comprenant une partie supérieure (1002) incluant des couches de protocole supérieures et une partie inférieure (1004) incluant des couches de protocole inférieures est établie entre l'UE (808) et un nœud de réseau (802) du réseau sans fil, et dans lequel l'UE (808) communique (1702) avec le nœud de réseau (802) par l'intermédiaire du relais (806) et de la BS (804), dans lequel les couches de protocole supérieures comprennent au moins un élément parmi : une couche de protocole de convergence de données par paquets, PDCP ; une partie d'une commande de liaison radio, RLC, qui réalise des retransmissions ; et dans lequel les couches de protocole inférieures comprennent au moins un élément parmi : une couche RLC ou une partie d'une couche RLC, qui réalise uniquement une segmentation ; une couche de commande d'accès au support, MAC ; une couche physique, PHY, le procédé (1700) comprenant :
    une terminaison (1706), au niveau du relais, de la partie inférieure (1004) de la porteuse radio (1000) pour l'UE ;
    un transfert (1708), au niveau du relais, de la partie supérieure (1002) de la porteuse radio pour l'UE vers le nœud de réseau (802) sur la seconde liaison sans fil ;
    une division, au niveau du relais, de la partie inférieure (1004) de la porteuse radio pour l'UE en multiples parties incluant une deuxième partie (1006) et une troisième partie (1010, 1012) ;
    une insertion d'une couche de multiplexage (1008) entre la deuxième partie (1006) et la troisième partie (1010, 1012) des multiples parties ; et
    un acheminement (1710) de la troisième partie (1010, 1012) entre le relais et la BS (804), la couche de multiplexage (1008) indiquant un élément parmi :
    la troisième partie (1010, 1012) inclut des données locales générées au niveau du relais, qui est transmise dans une partie supérieure d'une porteuse radio établie entre le relais et la BS ;
    la troisième partie (1010, 1012) inclut des données distantes générées par l'UE, qui est transmise dans un tunnel entre le relais et la BS.
  2. Procédé selon la revendication 1, dans lequel le relais et la station de base comprennent chacun une unité distribuée distincte.
  3. Procédé selon la revendication 1, dans lequel la porteuse radio est une parmi une porteuse radio de signalisation ou une porteuse radio de données.
  4. Support lisible par ordinateur (1810) présentant des instructions stockées dessus qui lorsqu'exécutées par un processeur d'un relais amènent le relais à réaliser le procédé selon l'une quelconque des revendications 1 à 3.
  5. Dispositif relais pour une communication de données distantes et locales dans une liaison frontale sans fil d'un réseau sans fil, le dispositif relais comprenant :
    un moyen (1802) de communication avec un équipement d'utilisateur, UE (808) sur une première liaison sans fil ;
    un moyen (1802) de communication avec une station de base, BS, (804) sur une seconde liaison sans fil ;
    un moyen (1804) de terminaison d'une partie inférieure (1004) d'une porteuse radio (1000) pour l'UE (808), dans lequel la porteuse radio (1000) comprend une partie supérieure (1002) incluant des couches de protocole supérieures et la partie inférieure (1004) incluant des couches de protocole inférieures, dans lequel la porteuse radio (1000) est établie entre l'UE (808) et un nœud de réseau (802) du réseau sans fil, dans lequel les couches de protocole supérieures comprennent au moins un élément parmi : une couche de protocole de convergence de données par paquets, PDCP ; une partie d'une couche de commande de liaison radio, RLC, qui réalise des retransmissions ; et dans lequel les couches de protocole inférieures comprennent au moins un élément parmi : une couche RLC ou une partie d'une couche RLC, qui réalise uniquement une segmentation ; une couche de commande d'accès au support, MAC ; une couche physique, PHY ;
    un moyen (1806) de transfert de la partie supérieure (1002) de la porteuse radio (1000) pour l'UE vers le nœud de réseau sur la seconde liaison sans fil ;
    un moyen de division de la partie inférieure (1004) de la porteuse radio pour l'UE en de multiples parties incluant une deuxième partie (1006) et une troisième partie (1010, 1012);
    un moyen d'insertion d'une couche de multiplexage (1008) entre la deuxième partie (1006) et la troisième partie (1010, 1012) des multiples parties ; et
    un moyen (1808) d'acheminement de la troisième partie (1010, 1012) entre le dispositif relais et la BS (804), la couche de multiplexage (1008) indiquant un élément parmi :
    la troisième partie (1010) inclut des données locales générées au niveau du dispositif relais, qui est transmise dans une partie supérieure d'une porteuse radio établie entre le dispositif relais et la BS ;
    la troisième partie (1010) inclut des données distantes générées par l'UE, qui est transmise dans un tunnel entre le dispositif relais et la BS.
  6. Dispositif relais selon la revendication 5, dans lequel le dispositif sans fil et la station de base comprennent chacun une unité distribuée distincte.
  7. Dispositif relais selon la revendication 5, dans lequel la porteuse radio est une parmi une porteuse radio de signalisation ou une porteuse radio de données.
EP18765230.0A 2017-08-08 2018-08-07 Communication de données distantes et locales dans une liaison sans fil de raccordement aux sites cellulaires Active EP3666037B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201762542757P 2017-08-08 2017-08-08
US16/055,878 US10631346B2 (en) 2017-08-08 2018-08-06 Communicating remote and local data in a wireless fronthaul
PCT/US2018/045630 WO2019032596A1 (fr) 2017-08-08 2018-08-07 Communication de données distantes et locales dans une liaison sans fil de raccordement aux sites cellulaires

Publications (2)

Publication Number Publication Date
EP3666037A1 EP3666037A1 (fr) 2020-06-17
EP3666037B1 true EP3666037B1 (fr) 2022-11-30

Family

ID=63490677

Family Applications (1)

Application Number Title Priority Date Filing Date
EP18765230.0A Active EP3666037B1 (fr) 2017-08-08 2018-08-07 Communication de données distantes et locales dans une liaison sans fil de raccordement aux sites cellulaires

Country Status (5)

Country Link
US (1) US10631346B2 (fr)
EP (1) EP3666037B1 (fr)
CN (1) CN110999528B (fr)
TW (1) TWI772487B (fr)
WO (1) WO2019032596A1 (fr)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3319393B1 (fr) * 2016-11-07 2019-08-07 Koninklijke KPN N.V. Établissement d'une connexion entre un équipement d'utilisateur distant, ue, et un réseau de télécommunication par l'intermédiaire d'un ue compatible relais
KR102265526B1 (ko) * 2017-10-12 2021-06-16 에스케이텔레콤 주식회사 기지국장치 및 데이터 및 신호 전송 방법
US10432295B2 (en) * 2018-01-11 2019-10-01 At&T Intellectual Property I, L.P. Radio link control layer based relaying for integrated access and backhaul transmissions in wireless networks
CN113645189B (zh) * 2019-02-15 2022-06-28 华为技术有限公司 一种通信方法、网络节点、存储介质及系统芯片
CN111586890B (zh) * 2019-02-15 2022-10-04 华为技术有限公司 一种数据传输方法及装置
CN111586887B (zh) * 2019-02-15 2023-03-28 华为技术有限公司 无线回传系统、通信方法及其装置
CN111585725B (zh) * 2019-02-15 2022-07-29 华为技术有限公司 标识管理的方法和装置
CN111865802B (zh) * 2019-04-30 2022-03-11 华为技术有限公司 一种通信方法及装置
CN112566246B (zh) * 2019-09-10 2024-02-27 中磊电子股份有限公司 主控基站及资源分配指示方法
US11979227B2 (en) 2020-12-09 2024-05-07 Electronics And Telecommunications Research Institute Method and apparatus for relaying data in communication system

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102369765B (zh) * 2009-02-03 2014-02-19 华为技术有限公司 一种中继传输的方法、中继节点和基站
JP5479571B2 (ja) * 2009-03-20 2014-04-23 テレフオンアクチーボラゲット エル エム エリクソン（パブル） 高度ｌｔｅにおけるセルフバックホール処理及びリレー処理用の無線ベアラ識別
US8867428B2 (en) * 2009-04-13 2014-10-21 Qualcomm Incorporated Split-cell relay application protocol
WO2010121416A1 (fr) * 2009-04-21 2010-10-28 华为技术有限公司 Procédé, noeud de relais et système pour traiter des données dans une liaison de relais
US8687591B2 (en) * 2009-04-27 2014-04-01 Qualcomm Incorporated Relay node user plane support
CN101877860B (zh) * 2009-04-28 2016-01-20 中兴通讯股份有限公司 中继节点、服务网关、中继数据的传输方法及系统
CN101877915B (zh) * 2009-04-28 2014-07-02 中兴通讯股份有限公司 一种长期演进系统中继站的数据传输方法和系统
CN102026398B (zh) * 2009-09-15 2013-02-13 普天信息技术研究院有限公司 Lte中继系统中分组汇聚协议的实现方法和装置
US9019841B2 (en) 2012-10-19 2015-04-28 Qualcomm Incorporated Architecture for relays in LTE using D2D
KR102106134B1 (ko) * 2015-05-15 2020-05-04 주식회사 케이티 단말의 무선연결 구성방법 및 그 장치
WO2017039735A1 (fr) 2015-09-03 2017-03-09 Intel IP Corporation Équipement d'utilisateur, et nœuds b évolués prenant en charge le relais en couche 2 et la commutation d'itinéraires

Also Published As

Publication number Publication date
TW201921978A (zh) 2019-06-01
CN110999528B (zh) 2022-08-12
CN110999528A (zh) 2020-04-10
EP3666037A1 (fr) 2020-06-17
US20190053301A1 (en) 2019-02-14
TWI772487B (zh) 2022-08-01
WO2019032596A1 (fr) 2019-02-14
US10631346B2 (en) 2020-04-21

Similar Documents

Publication Publication Date Title
EP3625991B1 (fr) Relais à sauts multiples sans fil
EP3666037B1 (fr) Communication de données distantes et locales dans une liaison sans fil de raccordement aux sites cellulaires
EP3529937B1 (fr) Surveillance d'espace de recherche de commande basée sur un type de service
EP3579453B1 (fr) Indication de correspondance de faisceau, indication d'étalonnage d'ue, et procédure de synchronisation d'informations pour rach tdd
KR102212102B1 (ko) 나머지 시스템 정보 송신 윈도우의 구성
EP3597000B1 (fr) Découverte d'une fonction de dispositif de commande en vue d'une liaison terrestre sans fil à l'aide d'une technologie d'accès radio cellulaire
KR20200108850A (ko) 비주기적 채널 상태 정보 레퍼런스 신호 트리거들에 대한 유사 코로케이션 가정들
EP3602908B1 (fr) Sélection d'entité de commande de ressources radio (rrc) pour des messages rrc
EP3669590A1 (fr) Régulation de puissance de liaison montante
US20180176344A1 (en) Media access control transport block design
CN110892665B (zh) 物理上行链路控制信道(pucch)序列配置
US11553504B2 (en) Handling overhead messages in 5G
WO2018118375A1 (fr) Conception de bloc de transport
WO2018205265A1 (fr) Continuité de la signalisation dans un réseau d'accès radio à architecture divisée

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20200116

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20210510

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602018043686

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0084040000

Ipc: H04W0076120000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20220620

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 88/08 20090101ALI20220603BHEP

Ipc: H04W 84/04 20090101ALI20220603BHEP

Ipc: H04W 76/12 20180101AFI20220603BHEP

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1535696

Country of ref document: AT

Kind code of ref document: T

Effective date: 20221215

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602018043686

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230331

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230228

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1535696

Country of ref document: AT

Kind code of ref document: T

Effective date: 20221130

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230330

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230301

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20230720

Year of fee payment: 6

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602018043686

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230712

Year of fee payment: 6

26N No opposition filed

Effective date: 20230831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230710

Year of fee payment: 6

Ref country code: DE

Payment date: 20230626

Year of fee payment: 6

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221130

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230807

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230807

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230831

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20230831

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A