Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for relaying data to or from a remote user equipment (UE) via a relay UE.
Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, etc. These 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, etc.). Examples of such multiple-access systems include 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE Advanced (LTE-A) 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, to name a few.
In some examples, a wireless multiple-access communication system may include a number of base stations (BSs), which are each capable of simultaneously supporting communication for multiple communication devices, otherwise known as user equipments (UEs). In an LTE or LTE-A network, a set of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in a next generation, a new radio (NR), or 5G network), 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 DUs, in communication with a CU, may define an access node (e.g., which may be referred to as a BS, 5G NB, next generation NodeB (gNB or gNodeB), transmission reception point (TRP), etc.). A BS or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a BS or DU to a UE) and uplink channels (e.g., for transmissions from a UE to BS or DU).
These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. NR (e.g., new radio or 5G) is an example of an emerging telecommunication standard. NR is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDMA with a cyclic prefix (CP) on the downlink (DL) and on the uplink (UL). To these ends, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
Sidelink communications are communications from one UE to another UE. As the demand for mobile broadband access continues to increase, there exists a need for further improvements in NR and LTE technology, including improvements to sidelink communications. Preferably, these improvements should be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.
The systems, methods, and devices of the disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure as expressed by the claims that follow, some features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled “Detailed Description” one will understand how the features of this disclosure provide advantages that include improved communications between access points and stations in a wireless network.
Certain aspects provide a method for wireless communications by a remote user equipment (UE). The method generally includes generating, while the remote UE is in an radio resource control (RRC) state with no dedicated resources allocated to the remote UE by a relay UE, a first message with data and an indication the relay UE is to forward the data to a network entity and transmitting the first message to the remote UE while still in the RRC state.
Certain aspects provide a method for wireless communications by a relay node. The method generally includes receiving, while a remote UE is in an radio resource control (RRC) state with the relay UE with no dedicated resources allocated to the remote UE, a first message from the remote UE with data and an indication the relay UE is to forward the data to a network entity and transmitting the data to the network entity while the remote UE is still in the RRC state with the relay UE.
Certain aspects provide a method for wireless communications by a network entity. The method generally includes receiving, from a relay UE, a first message with data and an indication the data is from a remote UE, determining, based on the indication provided with the first message, that the data is from the remote UE, and processing the data.
Aspects generally include methods, UEs, network entities, apparatuses, systems, computer readable mediums, and processing systems, as substantially described herein with reference to and as illustrated by the accompanying drawings.
To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the appended drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.
So that the manner in which the above-recited features of the present disclosure can be understood in detail, a more particular description, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects.
To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized on other aspects without specific recitation.
Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for relaying data to and/or from a remote UE in sidelink layer 2 (L2) relay systems.
The connection between the relay and the network entity, may be called a Uu connection or via a Uu path. The connection between the remote UE and the relay (e.g., another UE or a “relay UE”), may be called a PC5 connection or via a PC5 path. The PC5 connection is a device-to-device connection that may take advantage of the comparative proximity between the remote UE and the relay UE (e.g., when the remote UE is closer to the relay UE than to the closest base station). The relay UE may connect to an infrastructure node (e.g., gNB) via a Uu connection and relay the Uu connection to the remote UE through the PC5 connection.
The following description provides examples, and is not limiting of the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.
The techniques described herein may be used for various wireless communication technologies, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. The terms “network” and “system” are often used interchangeably. 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). An OFDMA network may implement a radio technology such as NR (e.g. 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS).
New Radio (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. 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). 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. For clarity, while 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.
New radio (NR) access (e.g., 5G technology) may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or beyond), millimeter wave (mmW) targeting high carrier frequency (e.g., 25 GHz or beyond), massive machine type communications MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low-latency communications (URLLC). 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. In addition, these services may co-exist in the same subframe.
As illustrated in
Wireless communication network 100 may also include relay UEs (e.g., relay UE 110r), also referred to as relays or the like, that receive a transmission of data and/or other information from an upstream station (e.g., a BS 110a or a UE 120r) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE 120 or a BS 110), or that relays transmissions between UEs 120, to facilitate communication between devices.
A network controller 130 may couple to a set of BSs 110 and provide coordination and control for these BSs 110. 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 (e.g., 120x, 120y, etc.) may be dispersed throughout the wireless communication 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 computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, an appliance, a medical device or medical equipment, a biometric sensor/device, a wearable device such as a smart watch, smart clothing, smart glasses, a smartwrist band, smartjewelry (e.g., a smart ring, a smart bracelet, etc.), an entertainment device (e.g., a music device, a video device, a satellite radio, etc.), a vehicular component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device that is configured to communicate via a wireless or wired medium. Some UEs may be considered 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, which may be narrowband IoT (NB-IoT) devices.
Certain wireless networks (e.g., LTE) 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. Each subcarrier may be modulated with data. In general, 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. For example, the spacing of the subcarriers may be 15 kHz and the minimum resource allocation (called a “resource block” (RB)) may be 12 subcarriers (or 180 kHz). Consequently, the nominal Fast Fourier Transfer (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.
While aspects of the examples described herein may be associated with LTE technologies, aspects of the present disclosure may be applicable with other wireless communications systems, such as NR. NR may utilize OFDM with a CP on the uplink and downlink and include support for half-duplex operation using TDD. 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.
In some examples, access to the air interface may be scheduled. A scheduling entity (e.g., a BS) allocates resources for communication among some or all devices and equipment within its service area or cell. 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. In some examples, a UE may function as a scheduling entity and may schedule resources for one or more subordinate entities (e.g., one or more other UEs), and the other UEs may utilize the resources scheduled by the UE for wireless communication. In some examples, a UE may function as a scheduling entity in a peer-to-peer (P2P) network, and/or in a mesh network. In a mesh network example, UEs may communicate directly with one another in addition to communicating with a scheduling entity.
In
The TRPs 208 may be a distributed unit (DU). TRPs 208 may be connected to a single ANC (e.g., ANC 202) or more than one ANC (not illustrated). For example, for RAN sharing, radio as a service (RaaS), and service specific AND deployments, TRPs 208 may be connected to more than one ANC. TRPs 208 may each include one or more antenna ports. TRPs 208 may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.
The logical architecture of distributed RAN 200 may support fronthauling solutions across different deployment types. For example, the logical architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter).
The logical architecture of distributed RAN 200 may share features and/or components with LTE. For example, next generation access node (NG-AN) 210 may support dual connectivity with NR and may share a common fronthaul for LTE and NR.
The logical architecture of distributed RAN 200 may enable cooperation between and among TRPs 208, for example, within a TRP and/or across TRPs via ANC 202. An inter-TRP interface may not be used.
Logical functions may be dynamically distributed in the logical architecture of distributed RAN 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 (e.g., TRP 208) or CU (e.g., ANC 202).
A centralized RAN unit (C-RU) 304 may host one or more ANC functions. Optionally, the C-RU 304 may host core network functions locally. The C-RU 304 may have distributed deployment. The C-RU 304 may be close 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.
At the BS 110a, 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), group common PDCCH (GC 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 primary synchronization signal (PSS), secondary synchronization signal (SSS), and cell-specific reference signal (CRS). 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 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.
At the UE 120a, the antennas 452a through 452r may receive the downlink signals from the base station 110a and may provide received signals to the demodulators (DEMODs) in transceivers 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 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 120a to a data sink 460, and provide decoded control information to a controller/processor 480.
On the uplink, at UE 120a, 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 (e.g., for the sounding reference signal (SRS)). The symbols from the transmit processor 464 may be precoded by a TX MIMO processor 466 if applicable, further processed by the demodulators in transceivers 454a through 454r (e.g., for SC-FDM, etc.), and transmitted to the base station 110a. At the BS 110a, the uplink signals from the UE 120a 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 120a. 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 BS 110a and the UE 120a, respectively. The processor 440 and/or other processors and modules at the BS 110a may perform or direct the execution of processes for the techniques described herein with reference to
In some circumstances, two or more subordinate entities (e.g., UEs) 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. Generally, 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. In some examples, the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks (WLANs), which typically use an unlicensed spectrum).
Aspects of the present disclosure involves a remote UE, a relay UE, and a network, as shown in
As shown in
Certain systems, such as NR, may support standalone (SA) capability for sidelink-based UE-to-network and UE-to-UE relay communications, for example, utilizing layer-3 (L3) and layer-2 (L2) relays, as noted above.
Particular relay procedures may depend on whether a relay is a L3 or L2 relay.
There are various issues to be addressed with sidelink relay DRX scenarios. One issue relates to support of a remote UE sidelink DRX for relay discovery. One assumption for relay discover in some cases is that the Relay UE is in CONNECTED mode only, rather than IDLE/INACTIVE. A remote UE, may be in a CONNECTED, IDLE/INACTIVE or out of coverage (OOC) modes.
Discovery for both relay selection and reselection may be supported. Different type of discovery models may be supported. For example, a first model (referred to as Model A discovery) is shown in
As noted above, for relay selection, the remote UE has not connected to any relay node (i.e. PC5 unicast link is not established between remote UE and relay node). In this case, it may be desirable to design DRX modes to reduce remote UE power consumption on monitoring relay discovery messages for relay selection.
As noted above, for relay reselection, the remote UE has connected to at least one relay node (e.g., with a PC5 unicast established between the emote UE and relay node). For relay reselection, it may be desirable to design a DRX configuration that helps reduce remote UE power consumption while monitoring for relay discovery messages for relay reselection and PC5 data transmission.
Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable mediums for relaying data to and/or from a remote UE in sidelink L2 relay systems. As will be described, the techniques may enable a remote UE that is in a radio resource control (RRC) state with no dedicated resources allocated to the remote UE by a relay UE, to still relay at least a small amount of data to another entity via a sidelink, whether the relay UE is in an RRC connected state or not.
Sidelink based relays have been considered as an efficient way to extend UE range and enhance service in various use cases. One example is a single-hop NR sidelink-based relay, where a relay UE relays data between a remote UE and a base station (e.g., a gNB). There are various aspects to consider and address in such systems in order to support standalone (SA) requirements for sidelink-based UE-to-network and UE-to-UE relay communications. For example, the following aspects may be considered for layer-3 (L3) relay and layer-2 (L2) relays: relay (re-)selection criterion and procedures, Relay/Remote UE authorization, Quality of Service (QoS) for relaying functionality, service continuity, security of relayed connections, and impact on user plane protocol stack and control plane procedure (e.g., connection management of relayed connection). Support of upper layer operations of discovery model/procedure for sidelink relaying, assuming no new physical layer channel/signal may also be studied.
The gNB and Relay UE may perform a relaying channel setup procedure for additional SRBs/DRBs over Uu. As illustrated, according to the configuration from the gNB, the Relay/Remote UE may establish additional RLC channels for relaying of SRBs/DRBs.
One work item of interest is small data transmission, for example, which would support a limited amount of data transfer to/from an RRC_INACTIVE remote UE without the need to enter the RRC_CONNECTED state. There are at least two solutions for such small data transfer.
A first solution is a random access channel (RACH) based solution, an example of which is shown in
A first solution is a configured grant (CG) based solution. In this case, the UE may send an RRC message using previously configured CG resource (e.g., an RRCResumeRequest), after which the UE may exchange a small amount of data with the gNB. Again, after the exchange, the gNB may release the UE, with the UE never entering the RRC_CONNECTED state.
Aspects of the present disclosure provide techniques that may allow a UE to participate in small data transfer with a gNB, through the use of a relay UE. As will be described, the present disclosure describes procedures and a signaling design to allow an RRC_INACTIVE/RRC_IDLE remote UE in coverage of an L2 relay to send small data to gNB via the L2 relay. In some cases, the remote UE may send its small data with one indication to relay the data via unicast PC5 link. In response, the relay may trigger a RACH-based or CG-based small data transmission for the remote UE. In such cases, both the remote UE and the relay may not change their RRC state during the procedure of remote UE small data transmission.
Operations 1500 begin at 1502, by generating, while the remote UE is in a radio resource control (RRC) state with no dedicated resources allocated to the remote UE by a relay UE, a first message with data and an indication the relay UE is to forward the data to a network entity.
At 1504, the remote UE transmits the first message to the relay UE while still in the RRC state.
Operations 1600 begin, at 1602, by receiving, while a remote UE is in a radio resource control (RRC) state with the relay UE with no dedicated resources allocated to the remote UE, a first message from the remote UE with data and an indication the relay UE is to forward the data to a network entity.
At block 1604, the relay UE transmits the data to the network entity while the remote UE is still in the RRC state with the relay UE.
Operations 1700 begin, at 1702, by receiving, from a relay UE, a first message with data and an indication the data is from a remote UE.
At 1704, the network entity determines, based on the indication provided with the first message, that the data is from the remote UE.
At 1706, the network entity processes the data. For example, the network entity may pass the data up to higher layers and/or may take action based on the data. In some cases, the network entity may send a response (e.g., with data) to be relayed back to the remote UE.
Operations of
In some cases, the Relay UE may include the indication and small data in the SidelinkUEinformationNR message for the gNB. In some cases, the gNB can also include response data, and an indication of remote UE ID in SidelinkUEinformationNR message for relay. As noted above, the relay may include response data and indication in unicast PC5 RRC message for remote UE.
There are also various signaling mechanisms (solutions) for when the relay UE is in an in RRC_IDLE or RRC_INACTIVE state.
The PC5 signaling triggers relay to initiate RACH-based small data transmission (per
As illustrated, in this case, the remote UE may send, via a PC5 message, an Uu RRC message, one indication on small data transmission, and its small data for gNB are included. In some cases, the RRC message (via Msg3/MsgA/CG) may be RRCResumeRequest for INACTIVE remote UE, or RRCSetupRequest for IDLE remote UE.
As illustrated, the PC5 signaling may trigger a relay to initiate a RACH-based solution (per or CG-based small data transmission with the following difference). The RRC message (e.g., via Msg3/MsgA/CG) may be an RRCResumeRequest for an INACTIVE remote UE. In response, the gNB schedules small data is scheduled via relay's C-RNTI. Both remote UE and relay don't change its RRC state during the procedure of remote UE small data transmission.
The processing system 2102 includes a processor 2104 coupled to a computer-readable medium/memory 2112 via a bus 2106. In certain aspects, the computer-readable medium/memory 2112 is configured to store instructions (e.g., computer-executable code) that when executed by the processor 2104, cause the processor 2104 to perform the operations illustrated in
The processing system 2202 includes a processor 2204 coupled to a computer-readable medium/memory 2212 via a bus 2206. In certain aspects, the computer-readable medium/memory 2212 is configured to store instructions (e.g., computer-executable code) that when executed by the processor 2204, cause the processor 2204 to perform the operations illustrated in
The processing system 2302 includes a processor 2304 coupled to a computer-readable medium/memory 2312 via a bus 2306. In certain aspects, the computer-readable medium/memory 2312 is configured to store instructions (e.g., computer-executable code) that when executed by the processor 2304, cause the processor 2304 to perform the operations illustrated in
Aspect 1: A method for wireless communications performed by a remote user equipment (UE), comprising: generating, while the remote UE is in an radio resource control (RRC) state with no dedicated resources allocated to the remote UE by a relay UE, a first message with data and an indication the relay UE is to forward the data to a network entity; and transmitting the first message to the remote UE while still in the RRC state.
Aspect 2. The method of Aspect 1, wherein the RRC state comprises an RRC idle state or an RRC inactive state.
Aspect 3. The method of any one of Aspects 1-2, further comprising: receiving a second message, from the relay UE, with response data from the network entity.
Aspect 4: The method of any one of Aspects 1-3, wherein the first message comprises a sidelink RRC reconfiguration message.
Aspect 5: The method of Aspect 4, further comprising: receiving, from the relay UE, a second sidelink RRC reconfiguration message with response data from the network entity.
Aspect 6: The method of Aspect 4, wherein the first message also includes an RRC message to be relayed to the network entity.
Aspect 7: A method for wireless communications performed by a relay user equipment (UE), comprising: receiving, while a remote UE is in an radio resource control (RRC) state with the relay UE with no dedicated resources allocated to the remote UE, a first message from the remote UE with data and an indication the relay UE is to forward the data to a network entity; and transmitting the data to the network entity while the remote UE is still in the RRC state with the relay UE.
Aspect 8: The method of Aspect 7, further comprising: transmitting a second message, to the remote UE, with response data from the network entity.
Aspect 9: The method of any one of Aspects 7-8, wherein the data is transmitted to the network entity while the relay UE is in an RRC connected state with the network entity.
Aspect 10: The method of any one of Aspects 7-9, wherein the data is transmitted to the network entity via a sidelink UE information message.
Aspect 11: The method of any one of Aspects 7-10, wherein the data is transmitted to the network entity while the relay UE is in an RRC idle state or RRC inactive state with the network entity.
Aspect 12: The method of any one of Aspects 7-11, wherein the data is transmitted to the network entity via a random access channel (RACH) based procedure.
Aspect 13: The method of any one of Aspects 7-12, wherein the data is transmitted to the network entity via a configured grant (CG) based procedure.
Aspect 14: The method of any one of Aspects 7-13, wherein the first message comprises a sidelink RRC reconfiguration message.
Aspect 15: The method of Aspect 14, further comprising: transmitting, to the remote UE, a second sidelink RRC reconfiguration message with response data from the network entity.
Aspect 16: The method of 14, wherein the first message also includes an RRC message and the method further comprises: relaying the RRC message go the network entity.
Aspect 17: A method for wireless communications performed by a network entity, comprising: receiving, from a relay UE, a first message with data and an indication the data is from a remote UE; determining, based on the indication provided with the first message, that the data is from the remote UE; and processing the data.
Aspect 18: The method of Aspect 17, wherein processing the data comprises: transmitting a second message, to the relay UE, with response data for the remote UE.
Aspect 19: The method of any one of Aspects 17-18, wherein the first message is received while the relay UE is in an RRC connected state with the network entity.
Aspect 20: The method of any one of Aspects 17-19, wherein the first message comprises a sidelink UE information message.
Aspect 21: The method of any one of Aspects 17-20, wherein the first message is received while the relay UE is in an RRC idle state or RRC inactive state with the network entity.
Aspect 22: The method of any one of Aspects 17-21, wherein the first message is received via a random access channel (RACH) based procedure.
Aspect 23: The method of any one of Aspects 17-22, wherein the first message is received via a configured grant (CG) based procedure.
Aspect 24: A remote user equipment, comprising means for performing the operations of one or more of Aspects 1-6.
Aspect 25: A remote user equipment, comprising a transceiver and a processing system including at least one processor configured to perform the operations of one or more of Aspects 1-6.
Aspect 26: An apparatus for wireless communications by a remote user equipment, comprising: a processing system configured to generate, while the remote UE is in an radio resource control (RRC) state with no dedicated resources allocated to the remote UE by a relay UE, a first message with data and an indication the relay UE is to forward the data to a network entity; and an interface configured to output the first message for transmission to the remote UE while still in the RRC state.
Aspect 27: A computer-readable medium for wireless communications by a remote user equipment, comprising codes executable to: generate, while the remote UE is in an radio resource control (RRC) state with no dedicated resources allocated to the remote UE by a relay UE, a first message with data and an indication the relay UE is to forward the data to a network entity; and output the first message for transmission to the remote UE while still in the RRC state.
Aspect 28: A relay user equipment, comprising means for performing the operations of one or more of Aspects 7-16.
Aspect 29: A relay user equipment, comprising a transceiver and a processing system including at least one processor configured to perform the operations of one or more of Aspects 7-16.
Aspect 30: An apparatus for wireless communications by a relay user equipment, comprising: an interface configured to obtain, while a remote UE is in an radio resource control (RRC) state with the relay UE with no dedicated resources allocated to the remote UE, a first message from the remote UE with data and an indication the relay UE is to forward the data to a network entity; and output the data for transmission to the network entity while the remote UE is still in the RRC state with the relay UE.
Aspect 31: A computer-readable medium for wireless communications by a relay user equipment, comprising codes executable to: obtain, while a remote UE is in an radio resource control (RRC) state with the relay UE with no dedicated resources allocated to the remote UE, a first message from the remote UE with data and an indication the relay UE is to forward the data to a network entity; and output the data for transmission to the network entity while the remote UE is still in the RRC state with the relay UE.
Aspect 32: A network entity, comprising means for performing the operations of one or more of Aspects 17-23.
Aspect 33: A network entity, comprising a transceiver and a processing system including at least one processor configured to perform the operations of one or more of Aspects 17-23.
Aspect 34: An apparatus for wireless communications by a network entity, comprising: an interface configured to obtain, from a relay UE, a first message with data and an indication the data is from a remote UE; and a processing system configured to determine, based on the indication provided with the first message, that the data is from the remote UE and process the data.
Aspect 35: A computer-readable medium for wireless communications by a network entity, comprising codes executable to: obtain, from a relay UE, a first message with data and an indication the data is from a remote UE; determine, based on the indication provided with the first message, that the data is from the remote UE; and process the data.
The methods disclosed herein comprise one or more steps or actions for achieving the methods. The method steps and/or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.
As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “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).
As used herein, the term “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 previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. § 112(f) unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for.”
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. Generally, where there are operations illustrated in figures, those operations may have corresponding counterpart means-plus-function components. For example, various operations shown in
Means for receiving may include a transceiver, a receiver or at least one antenna and at least one receive processor illustrated in
In some cases, rather than actually transmitting a frame a device may have an interface to output a frame for transmission (a means for outputting). For example, a processor may output a frame, via a bus interface, to a radio frequency (RF) front end for transmission. Similarly, rather than actually receiving a frame, a device may have an interface to obtain a frame received from another device (a means for obtaining). For example, a processor may obtain (or receive) a frame, via a bus interface, from an RF front end for reception.
The various illustrative logical blocks, modules and circuits described in connection with the present disclosure may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. 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.
If implemented in hardware, 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. In the case of a user terminal 120 (see
If implemented in software, 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. By way of example, 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. Alternatively, or in addition, 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. Examples of 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. 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. By way of example, a software module may be loaded into RAM from a hard drive when a triggering event occurs. During execution of the software module, 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. When referring to the functionality of a software module below, it will be understood that such functionality is implemented by the processor when executing instructions from that software module.
Also, any connection is properly termed a computer-readable medium. For example, if 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 (TR), radio, and microwave, then 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, as used herein, 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. Thus, in some aspects computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media). In addition, for other aspects 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.
Thus, certain aspects may comprise a computer program product for performing the operations presented herein. For example, such 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. For example, instructions for performing the operations described herein and illustrated in
Further, it should be appreciated that 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. For example, such a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, 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. Moreover, any other suitable technique for providing the methods and techniques described herein to a device can be utilized.
It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/CN2021/085510 | 4/5/2021 | WO |