Data transmission using relay user equipment

Abstract

The present invention relates to transmitting data using a relay user equipment. Apparatus, methods and systems for transmitting data corresponding to a relay UE are disclosed. A method includes transmitting data and first information indicating relay information corresponding to a retransmission of the data by the relay UE to at least one UE. The first information includes a relay identifier, an indication that the retransmission of the data is based on feedback received by the relay UE, an indication that the retransmission of the data is based on a multi-hop count, an indication that the relay UE transfers the data from a receiver buffer to a transmission buffer and retransmits the data from the transmission buffer, an indication that the relay UE retransmits the data to an indicated destination node, or some combination thereof. The method includes transmitting second information indicating a remaining packet delay budget to at least one UE.

Description

[0001] This application is a divisional application of an application which entered the Chinese national phase on January 12, 2022, with PCT application number PCT / IB2019 / 000870, international application date July 23, 2019, Chinese application number 201980098397.3, and invention name “Data Transmission Using Relay User Equipment”. Technical Field

[0002] The subject matter disclosed herein relates generally to wireless communications, and more particularly to transmitting data using relay user equipment. Background Art

[0003] The following abbreviations are defined herein, and at least some of them are referred to in the following description: 3rd Generation Partnership Project (“3GPP”), 4th Generation (“4G”), 5th Generation (“5G”), 5G System (“5GS”), Acknowledgement (“ACK”), Aggregation Level (“AL”), Access and Mobility Management Function (“AMF”), Access Network (“AN”), Access Point (“AP”), Authentication Server Function (“AUSF”), Beam Failure Detection (“BFD”), Binary Phase Shift Keying (“BPSK”), Base Station (“BS”), Buffer Status Report (“BSR”), Bandwidth (“BW”), Bandwidth Part (“BWP”), Carrier Aggregation (“CA”), Contention-Based Random Access (CBA), QoS (QoS) “CBRA”), Clear Channel Assessment (“CCA”), Control Channel Element (“CCE”), Cyclic Delay Diversity (“CDD”), Code Division Multiple Access (“CDMA”), Control Element (“CE”), Contention-Free Random Access (“CFRA”), Closed Loop (“CL”), Coordinated Multi-Point (“CoMP”), Cyclic Prefix (“CP”), Cyclic Redundancy Check (“CRC”), Channel State Information (“CSI”), Channel State Information Reference Signal (“CSI-RS”), Common Search Space (“CSS”), Control Resource Set (“CORESET”), Device-to-Device (“D2D”), Discrete Fourier Transform Spreading (“DFTS”), Downlink Control Information (“DCI”) , downlink (“DL”), demodulation reference signal (“DMRS”), data radio bearer (“DRB”), discontinuous reception (“DRX”), downlink pilot time slot (“DwPTS”), enhanced clear channel assessment (“eCCA”), EPS connection management (“ECM”), enhanced mobile broadband (“eMBB”), evolved Node B (“eNB”), effective isotropic radiated power (“EIRP”), European Telecommunications Standards Institute (“ETSI”), evolved packet core (“EPC”), evolved packet system (“EPS”), evolved universal terrestrial access (“E-UTRA”), evolved universal terrestrial access network (“E-UTRAN”), frame-based equipment (“FBE”), frequency division duplex (“FDD”), frequency division multiplexing (“FDM”), frequency division multiple access (“FDMA”), frequency division orthogonal cover code (“FD-OCC”), 5G Node B or next generation Node B (“gNB”), group leader (“GL”), general packet radio service (“GPRS”), guard period (“GP”), global system for mobile communications (“GSM”), globally unique temporary UE identifier (“GUTI”), home AMF (“hAMF”), hybrid automatic repeat request (“HARQ”), home location register (“HLR”), home PLMN (“HPLMN”), home subscriber server (“HSS”), identity or identifier (“ID”),Information Element (“IE”), International Mobile Equipment Identity (“IMEI”), International Mobile Subscriber Identity (“IMSI”), International Mobile Telecommunications (“IMT”), Internet of Things (“IoT”), Layer 1 (“L1”), Layer 2 (“L2”), Layer 3 (“L3”), License Assisted Access (“LAA”), Load Based Equipment (“LBE”), Listen Before Talk (“LBT”), Logical Channel (“LCH”), Logical Channel Priority (“LCP”), Log Likelihood Ratio (“LLR”), Long Term Evolution (“LTE”), Multiple Access (“MA”), Medium Access Control (“MAC”), Multimedia Broadcast Multicast Service (“MBMS”), Minimum Communication Range (“MCR”), Modulation Codec MCS), Master Information Block (MIB), Multiple Input Multiple Output (MIMO), Mobility Management (MM), Mobility Management Entity (MME), Mobile Network Operator (MNO), Massive MTC (mMTC), Maximum Power Reduction (MPR), Machine Type Communication (MTC), Multi-User Shared Access (MUSA), Non-Access Stratum (NAS), Narrowband (NB), Negative Acknowledgement (NACK) or (NAK), Network Entity (NE), Network Function (NF), Next Generation RAN (NG-RAN), Non-Orthogonal Multiple Access (NOMA), New Radio (NR), Network Storage Function ), Network Slice Selection Assistance Information (“NSSAI”), Network Slice Selection Function (“NSSF”), Network Slice Selection Policy (“NSSP”), Operation and Maintenance System (“OAM”), Orthogonal Frequency Division Multiplexing (“OFDM”), Open Loop (“OL”), Other System Information (“OSI”), Power Angular Spectrum (“PAS”), Physical Broadcast Channel (“PBCH”), Power Control (“PC”), LTE to V2X Interface (“PC5”), Primary Cell (“PCell”), Policy Control Function (“PCF”), Physical Cell ID (“PCID”), Physical Downlink Control Channel (“PDCCH”), Segment Group Data Convergence Protocol ("PDCP"), Physical Downlink Shared Channel ("PDSCH"), Pattern Division Multiple Access ("PDMA"), Packet Data Unit ("PDU"), Physical Hybrid ARQ Indicator Channel ("PHICH"), Power Headroom ("PH"), Power Headroom Report ("PHR"), Physical Layer ("PHY"), Queue Leader ("PL"), Public Land Mobile Network ("PLMN"), Queue Member ("PM"), Physical Random Access Channel ("PRACH"), Physical Resource Block ("PRB"), Primary and Secondary Cell ("PSCell"), Physical Sidelink Control Channel ("PSCCH"), Physical Uplink Control Channel ("PUCCH"),Physical Uplink Shared Channel (“PUSCH”), Quasi Co-location (“QCL”), Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”), Registration Area (“RA”), Radio Access Network (“RAN”), Radio Access Technology (“RAT”), Random Access Procedure (“RACH”), Random Access Response (“RAR”), Resource Element Group (“REG”), Radio Link Control (“RLC”), Radio Link Monitoring (“RLM”), Radio Network Temporary Identifier (“RNTI”), Reference Signal (“RS”), Remaining Minimum System Information (“RMSI”), Radio Resource Control (“RRC”), Radio Resource Management (“RRM”), Resource Extended Multiple Access (“RSMA”), Reference Signal Received Power (“RSRP”), Round Trip Time (“RTT”), Reception (“RX”), Sparse Code Multiple Access (“SCMA”), Scheduling Request (“SR”), Sounding Reference Information (“SRI”), Single Carrier Frequency Division Multiple Access (“SC-FDMA”), Secondary Cell (“SCell”), Shared Channel (“SCH”), Sidelink Control Information (“SCI”), Subcarrier Spacing (“SCS”), Service Data Unit (“SDU”), System Information Block (“SIB”), System Information Block Type 1 (“SIB1”), System Information Block Type 2 (“SIB2”), Subscriber Identity / Identification Module (“SIM”), Signal and Interference Addition Noise Ratio (“SINR”), Sidelink (“SL”), Service Level Agreement (“SLA”), Session Management Function (“SMF”), Special Cell (“SpCell”), Single Network Slice Selection Assistance Information (“S-NSSAI”), Shortened TTI (“sTTI”), Synchronization Signal (“SS”), Synchronization Signal Block (“SSB”), Scheduled UE (“SUE”), Supplementary Uplink (“SUL”), Subscriber Permanent Identifier (“SUPI”), Candidate Resource Selection Time Window (“T2”), Tracking Area (“TA”), TA Indicator (“TAI”), Transport Block (“TB”), Transport Block Size (“TBS”), Time Division Duplex (“TDD”), Time Division Multiplexing ("TDM"), time division orthogonal cover code ("TD-OCC"), transmission power control ("TPC"), transmission reception point ("TRP"), transmission time interval ("TTI"), time to live ("TTL"), transmission ("TX"), uplink control information ("UCI"), unified data management function ("UDM"), unified data repository ("UDR"), user entity / equipment (mobile terminal) ("UE"), universal integrated circuit card ("UICC"), uplink ("UL"), universal mobile telecommunications system ("UMTS"), user plane ("UP"), uplink pilot time slot ("UpPTS"), ultra-reliable and low-latency communications ("URLLC"),UE Routing Selection Policy (“URSP”), LTE Radio Interface (“Uu”), Vehicle-to-Everything (“V2X”), Access AMF (“vAMF”), Access NSSF (“vNSSF”), Access PLMN (“vPLMN”), Interconnection Interface (“X2”) (“Xn”), and Worldwide Interoperability for Microwave Access (“WiMAX”).

[0004] In some wireless communication networks, V2X communication may be used. In such networks, V2X communication may be used to relay data. Summary of the invention

[0005] A method for transmitting data corresponding to a relay user device is disclosed. The apparatus and system also perform the functions of the apparatus. One embodiment of the method includes: transmitting data and first information indicating relay information corresponding to a retransmission of the data by the relay user device to at least one user device. In such an embodiment, the at least one user device is within a predetermined user device group or outside a predetermined user device group, and the first information includes a relay identifier, an indication that the retransmission of the data is based on feedback received by the relay user device, an indication that the retransmission of the data is based on a multi-hop count, an indication that the relay user device transfers the data from a receiver buffer to a transmission buffer and retransmits the data from the transmission buffer, an indication that the relay user device retransmits the data to an indicated destination node, or some combination thereof. In certain embodiments, the method includes transmitting second information indicating a remaining packet delay budget to at least one user device.

[0006] An apparatus for transmitting data corresponding to a relay user equipment comprises a transmitter, which: transmits data and first information indicating relay information corresponding to retransmission of the data by the relay user equipment to at least one user equipment, wherein the at least one user equipment is within a predetermined user equipment group or outside a predetermined user equipment group, the first information comprising a relay identifier, an indication that retransmission of the data is based on feedback received by the relay user equipment, an indication that retransmission of the data is based on a multi-hop count, an indication that the relay user equipment passes the data from a receiver buffer to a transmission buffer and retransmits the data from the transmission buffer, an indication that the relay user equipment retransmits the data to an indicated destination node, or some combination thereof; and transmits second information indicating a remaining packet delay budget to the at least one user equipment.

[0007] One embodiment of a method for receiving data corresponding to a relay user device includes: at least one user device receives data and first information indicating relay information corresponding to a retransmission of the data by the relay user device. In such an embodiment, the at least one user device is within a predetermined user device group or outside a predetermined user device group, and the first information includes a relay identifier, an indication that the retransmission of the data is based on feedback received by the relay user device, an indication that the retransmission of the data is based on a multi-hop count, an indication that the relay user device passes the data from a receiver buffer to a transmission buffer and retransmits the data from the transmission buffer, an indication that the relay user device retransmits the data to an indicated destination node, or some combination thereof. In some embodiments, the method includes receiving, by at least one user device, second information indicating a remaining packet delay budget.

[0008] An apparatus for receiving data corresponding to a relay user device comprises a receiver, which: receives data and first information indicating relay information corresponding to retransmission of the data by the relay user device by at least one user device, wherein the at least one user device is within a predetermined user device group or outside a predetermined user device group, the first information comprising a relay identifier, an indication that retransmission of the data is based on feedback received by the relay user device, an indication that retransmission of the data is based on a multi-hop count, an indication that the relay user device passes the data from a receiver buffer to a transmission buffer and retransmits the data from the transmission buffer, an indication that the relay user device retransmits the data to an indicated destination node, or some combination thereof; and receives second information indicating a remaining packet delay budget by the at least one user device. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] A more particular description of the embodiments briefly described above will be presented by reference to specific embodiments illustrated in the accompanying drawings. Understanding that these drawings depict only some embodiments and are therefore not to be considered limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0010] Figure 1 is a schematic block diagram illustrating an embodiment of a wireless communication system for transmitting data using a relay user equipment;

[0011] Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to transmit data using a relay user equipment;

[0012] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to configure a user equipment;

[0013] Figure 4 is a schematic block diagram illustrating one embodiment of communications corresponding to transmitting data using a relay user equipment;

[0014] Figure 5 is a schematic block diagram illustrating another embodiment of communications corresponding to transmitting data using a relay user equipment;

[0015] Figure 6 is a flow chart illustrating one embodiment of a method for transmitting data corresponding to a relay user equipment; and

[0016] Figure 7 is a flow chart illustrating one embodiment of a method for receiving data corresponding to a relay user equipment. DETAILED DESCRIPTION

[0017] As will be appreciated by those skilled in the art, aspects of the embodiments may be embodied as systems, devices, methods or program products. Therefore, the embodiments may take the form of a complete hardware embodiment, a complete software embodiment (including firmware, resident software, microcode, etc.) or a combination of software and hardware aspects, which may generally be referred to herein as "circuit", "module" or "system". In addition, the embodiments may take the form of a program product embodied in one or more computer-readable storage devices stored in machine-readable code, computer-readable code and / or program code, hereinafter referred to as code. The storage device may be tangible, non-temporary and / or non-transmitting. The storage device may not embody a signal. In a certain embodiment, the storage device only employs a signal for accessing the code.

[0018] Certain functional units described in this specification may be labeled as modules in order to more specifically emphasize their implementation independence. For example, a module may be implemented as a hardware circuit including a custom very large scale integration ("VLSI") circuit or gate array, an off-the-shelf semiconductor such as a logic chip, a transistor, or other discrete components. A module may also be implemented in a programmable hardware device such as a field programmable gate array, a programmable array logic, a programmable logic device, or the like.

[0019] Modules can also be implemented in code and / or software to be executed by various types of processors. The identified code modules can, for example, include one or more physical or logical blocks of executable code, which can, for example, be organized as objects, processes, or functions. However, the executable files of the identified modules do not need to be physically located together, but can include irrelevant instructions stored in different locations, which, when logically connected together, include the module and achieve the purpose of the module.

[0020] In fact, a code module can be a single instruction or many instructions, and can even be distributed in several different code segments, among different programs, and across several memory devices. Similarly, in this article, operating data can be identified and illustrated in a module, and can be embodied in any suitable form and organized in a data structure of any suitable type. Operating data can be collected as a single data set, or can be distributed in different locations, including on different computer-readable storage devices. When a module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0021] Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system, apparatus or device, or any suitable combination of the foregoing.

[0022] More specific examples of storage devices (a non-exhaustive list) would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or flash memory), a portable compact disc read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0023] The code for performing the operations of the embodiments may be any number of lines and may be written in any combination of one or more programming languages ​​including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and the like, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly languages. The code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer, partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0024] References to "one embodiment", "embodiment" or similar language in this specification mean that the specific features, structures or characteristics described in conjunction with the embodiment are included in at least one embodiment. Therefore, unless otherwise expressly stated, the phrases "in one embodiment", "in an embodiment" and similar language appearing throughout the specification may but do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments". Unless otherwise expressly stated, the terms "including", "comprising", "having" and their variations mean "including but not limited to". Unless otherwise expressly stated, the list of items listed does not imply that any or all items are mutually exclusive. Unless otherwise expressly stated, the terms "one", "an" and "the" also refer to "one or more".

[0025] In addition, the features, structures or characteristics of the described embodiments may be combined in any suitable manner. In the following description, many specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, those skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific details, or using other methods, components, materials, etc. In other cases, well-known structures, materials or operations are not shown or described in detail to avoid obscuring some aspects of the embodiments.

[0026] The various aspects of the embodiments are described below with reference to the schematic flow charts and / or schematic block diagrams of the methods, devices, systems and program products according to the embodiments. It will be understood that each block of the schematic flow charts and / or schematic block diagrams and the combination of blocks in the schematic flow charts and / or schematic block diagrams can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the functions / operations specified in the boxes or some boxes of the schematic flow charts and / or schematic block diagrams.

[0027] The code may also be stored in a storage device that is capable of instructing a computer, other programmable data processing device, or other device to operate in a specific manner so that the instructions stored in the storage device produce an article of manufacture including instructions that implement the functions / operations specified in the boxes or some boxes of the schematic flowchart and / or schematic block diagram.

[0028] The code may also be loaded onto a computer, other programmable data processing device or other device so that a series of operational steps are performed on the computer, other programmable device or other device to produce a computer-implemented process, so that the code executed on the computer or other programmable device provides a process for implementing the functions / operations specified in a box or some boxes of the flowchart and / or block diagram.

[0029] The schematic flow charts and / or schematic block diagrams in the accompanying drawings illustrate possible implementations of the apparatus, system, method, and program product according to various embodiments, architecture, functions, and operations. In this regard, each block in the schematic flow charts and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing a specified logical function.

[0030] It should also be noted that in some alternative implementations, the functions annotated in the blocks may not occur in the order annotated in the drawings. For example, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order, depending on the functions involved. Other steps and methods are contemplated that are equivalent in function, logic, or effect to one or more blocks or portions thereof of the illustrated drawings.

[0031] Although various arrow types and line types can be used in flow charts and / or block diagrams, it should be understood that they do not limit the scope of the corresponding embodiments. In fact, some arrows or other connectors can only be used to indicate the logical flow of the depicted embodiment. For example, an arrow can indicate a waiting or monitoring period of unspecified duration between the enumeration steps of the depicted embodiment. It will also be noted that each frame of the block diagram and / or flow chart and the combination of frames in the block diagram and / or flow chart can be implemented by a system based on dedicated hardware that performs a specific function or operation, or a combination of dedicated hardware and code.

[0032] The description of an element in each figure may refer to the elements of the previous figure. In all figures, the same numerals refer to the same elements, including alternative embodiments of the same elements.

[0033] Figure 1 An embodiment of a wireless communication system 100 for transmitting data using a relay user equipment is depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Figure 1 Although a particular number of remote units 102 and network units 104 are depicted in FIG. 1 , those skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100 .

[0034] In one embodiment, the remote unit 102 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant ("PDA"), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle computer, a network device (e.g., a router, a switch, a modem), an aerial vehicle, a drone, etc. In some embodiments, the remote unit 102 includes a wearable device such as a smart watch, a fitness band, an optical head-mounted display, etc. In addition, the remote unit 102 may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a UE, a user terminal, a device, or other terms used in the art. The remote unit 102 can communicate directly with one or more network units 104 via UL communication signals. The remote unit 102 can also communicate directly with one or more other remote units 102.

[0035] The network elements 104 may be distributed over a geographic area. In some embodiments, the network elements 104 may also be referred to as access points, access terminals, base stations, base stations, node-Bs, eNBs, gNBs, home node-Bs, relay nodes, devices, core networks, air servers, radio access nodes, APs, NRs, network entities, AMFs, UDMs, UDRs, UDM / UDRs, PCFs, RANs, NSSFs, or any other terminology used in the art. The network elements 104 are typically part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network elements 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks, such as the Internet and public switched telephone networks, among others. These and other elements of the radio access and core networks are not illustrated, but are generally well known to those of ordinary skill in the art.

[0036] In one embodiment, the wireless communication system 100 complies with the NR protocol standardized in 3GPP, wherein the network unit 104 transmits on the DL using an OFDM modulation scheme and the remote unit 102 transmits on the UL using an SC-FDMA scheme or an OFDM scheme. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication protocol, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, Other protocols include ZigBee, Sigfoxx, etc. The present disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0037] The network unit 104 may serve multiple remote units 102 within a service area, such as a cell or cell sector, via wireless communication links. The network unit 104 sends DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.

[0038] In one embodiment, the remote unit 102 may transmit data and first information indicating relay information corresponding to a retransmission of the data by the relay user device to at least one user device. In such an embodiment, the at least one user device is within a predetermined user device group or outside a predetermined user device group, and the first information includes a relay identifier, an indication that the retransmission of the data is based on feedback received by the relay user device, an indication that the retransmission of the data is based on a multi-hop count, an indication that the relay user device transfers the data from the receiver buffer to the transmission buffer and retransmits the data from the transmission buffer, an indication that the relay user device retransmits the data to the indicated destination node, or some combination thereof. In some embodiments, the remote unit 102 may transmit second information indicating a remaining packet delay budget to the at least one user device. Thus, the remote unit 102 may be used to transmit data corresponding to the relay user device.

[0039] In one embodiment, the remote unit 102 may receive data and first information indicating relay information corresponding to a retransmission of the data by a relay user device by at least one user device. In such an embodiment, the at least one user device is within a predetermined user device group or outside a predetermined user device group, and the first information includes a relay identifier, an indication that the retransmission of the data is based on feedback received by the relay user device, an indication that the retransmission of the data is based on a multi-hop count, an indication that the relay user device transfers the data from a receiver buffer to a transmission buffer and retransmits the data from the transmission buffer, an indication that the relay user device retransmits the data to an indicated destination node, or some combination thereof. In some embodiments, the remote unit 102 may receive second information indicating a remaining packet delay budget by at least one user device. Thus, the remote unit 102 may be used to receive data corresponding to the relay user device.

[0040] Figure 2An embodiment of an apparatus 200 that can be used to transmit data using a relay user device is depicted. The apparatus 200 includes an embodiment of a remote unit 102. In addition, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touch screen. In some embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and / or the display 208.

[0041] In one embodiment, the processor 202 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 202 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or a similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

[0042] In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. For example, memory 204 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, memory 204 includes non-volatile computer storage media. For example, memory 204 may include a hard drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile computer storage media and non-volatile computer storage media. In some embodiments, memory 204 also stores program code and related data, such as an operating system or other controller algorithm operating on remote unit 102.

[0043] In one embodiment, input device 206 may include any known computer input device, including a touchpad, buttons, keyboard, stylus, microphone, etc. In some embodiments, input device 206 may be integrated with display 208, for example, as a touch screen or similar touch-sensitive display. In some embodiments, input device 206 includes a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, input device 206 includes two or more different devices such as a keyboard and a touchpad.

[0044] In one embodiment, display 208 may include any known electronically controllable display or display device. Display 208 may be designed to output visual signals, auditory signals and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, display 208 may include a wearable display such as a smart watch, smart glasses, a head-up display, etc. In addition, display 208 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0045] In some embodiments, the display 208 includes one or more speakers for generating sounds. For example, the display 208 can generate an audible alarm or notification (e.g., a buzzer or beep). In some embodiments, the display 208 includes one or more tactile devices for generating vibration, motion, or other tactile feedback. In some embodiments, all or part of the display 208 can be integrated with the input device 206. For example, the input device 206 and the display 208 can form a touch screen or similar touch-sensitive display. In other embodiments, the display 208 can be located near the input device 206.

[0046] The transmitter 210 is configured to provide an UL communication signal to the network element 104, and the receiver 212 is configured to receive a DL communication signal from the network element 104, as described herein. In some embodiments, the transmitter 210: transmits data and first information indicating relay information corresponding to a retransmission of the data by a relay user equipment to at least one user equipment, wherein the at least one user equipment is within a predetermined user equipment group or outside a predetermined user equipment group, the first information comprising a relay identifier, an indication that the retransmission of the data is based on feedback received by the relay user equipment, an indication that the retransmission of the data is based on a multi-hop count, an indication that the relay user equipment passes the data from a receiver buffer to a transmission buffer and retransmits the data from the transmission buffer, an indication that the relay user equipment retransmits the data to an indicated destination node, or some combination thereof; and transmits second information indicating a remaining packet delay budget to the at least one user equipment.

[0047] In various embodiments, the receiver 212: receives data and first information indicating relay information corresponding to retransmission of the data by a relay user device by at least one user device, wherein the at least one user device is within a predetermined user device group or outside a predetermined user device group, the first information including a relay identifier, an indication that retransmission of the data is based on feedback received by the relay user device, an indication that retransmission of the data is based on a multi-hop count, an indication that the relay user device passes the data from a receiver buffer to a transmission buffer and retransmits the data from the transmission buffer, an indication that the relay user device retransmits the data to an indicated destination node, or some combination thereof; and receives second information indicating a remaining packet delay budget by at least one user device.

[0048] Although only one transmitter 210 and one receiver 212 are shown, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and receiver 212 may be any suitable type of transmitter and receiver. In one embodiment, the transmitter 210 and receiver 212 may be part of a transceiver.

[0049] Figure 3 One embodiment of an apparatus 300 that may be used to configure a user device is depicted. The apparatus 300 includes one embodiment of the network unit 104. In addition, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. It is understood that the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0050] Although only one transmitter 310 and one receiver 312 are shown, the network unit 104 may have any suitable number of transmitters 310 and receivers 312. The transmitter 310 and receiver 312 may be any suitable type of transmitter and receiver. In one embodiment, the transmitter 310 and receiver 312 may be part of a transceiver.

[0051] As used herein, the terms eNB and / or gNB may be used for a base station, but may be replaced by any other radio access node (e.g., BS, eNB, gNB, AP, NR, etc.). In addition, various embodiments herein may be described in the context of 5G NR; however, the embodiments may be applicable to other mobile communication systems supporting serving cells and / or carriers, such as systems configured for sidelink communication over a PC5 interface.

[0052] In some embodiments, for PL to PM communication, the PL may use multicast to transmit a CAM including details about trajectory, distance control, etc. to all PMs.

[0053] In various embodiments, for PM-to-PM communication, after the CAM from the PL is received by the platoon, each PM transmits its own CAM using multicast transmission or unicast transmission to update the latest platoon members.

[0054] In some embodiments, in order to enhance the reliability of the member UEs in the platoon to receive messages, HARQ feedback for multicast transmissions may be used. It is understood that due to vehicle shielding or self-blocking, some member UEs may not be able to reliably receive packets from the platoon leader, and relay messages from the platoon leader may be performed to enhance the reliability of message reception with the group.

[0055] In some embodiments, a queue leader may communicate outside a group (e.g., a queue) to discover new queue members and allow new queue members to join its group. In some embodiments, a queue member that leaves a group may notify its queue leader and / or other queue members of its intent to leave the group. In addition, a queue member may discover and / or join another queue. In various embodiments, a queue may be merged with another queue by creating a larger queue group. In such embodiments, coverage enhancement may be achieved by relaying messages originating from queue members or queue leaders.

[0056] In some embodiments, the message is relayed or retransmitted by an intermediate UE (e.g., a relay UE) based on HARQ feedback. For example, the queue leader transmits an initial multicast transmission message, and each of the queue members receives and processes the message for its V2X application. Each queue member then retransmits or relays the message to its neighboring members based on HARQ feedback (e.g., based on whether an ACK is received, based on whether a NACK is received, based on ACK signal strength, based on NACK signal strength, etc.). In such an embodiment, each member UE may be provided with a dedicated ACK / NACK resource and the feedback resource configuration of all UEs may be known to each other.

[0057] In some embodiments, the intermediate UEs relay or retransmit the message without HARQ feedback. In such embodiments, the queue leader transmits the initial multicast transmission within or outside the group without expecting any HARQ feedback.

[0058] Figure 4 4 is a schematic block diagram illustrating one embodiment of a communication 400 corresponding to transmitting data using a relay user equipment (e.g., based on HARQ feedback and relaying within a group). The communication 400 includes messages transmitted between a TX UE 402, a relay UE 404 (e.g., an intermediate UE, an intermediate node), and an RX UE 406. It is understood that any communication described herein may include one or more messages.

[0059] In one embodiment, in a first communication 408 transmitted from a TX UE 402 to a relay UE 404 (or multiple UEs, some or all of which may be relay UEs), the TX UE 402 transmits a transport block (e.g., data) with an indication for relaying the transport block by the relay UE 404 (e.g., any other UE in the group, all other UEs in the group, etc.) based on HARQ feedback (e.g., within an SCI).

[0060] In some embodiments, the TX UE 402 may reserve resources for the relay UE 404 for transmission (or retransmission) of the transport block. In addition, as part of the first communication 408 (or in another communication), the TX UE 402 may provide the relay UE 404 with reserved resource information. The reserved resource information may include auxiliary information for the reserved resources, such as periodic resource reservations used for periodic services. In some embodiments, the TX UE 402 may provide the reserved resource information to the relay UE 404 via the first or second phase of the SCI in L1 or L2. The relay UE 404 may use the reserved resources for retransmission based on the relay flag.

[0061] In some embodiments, if there is no resource reservation information transmitted from the TX UE 402 (e.g., in the SCI) to the relay UE 404, the relay UE 404 may select one or more resources for transmission (or retransmission) from a resource pool (e.g., a dedicated resource pool for such transmission) based on sensing which resources in the resource pool are available or by randomly selecting resources from within the resource pool. In some embodiments, the resource pool may operate based on mode 2d. For example, mode 2d may be applied to vehicle-mounted UEs in a group. In this scenario, only the leader can schedule the sidelink transmissions of other member UEs in the group. The scheduling UE may be selected by the application layer or the gNB. After the scheduling UE is selected by the application, the selection information (plus the group information) may be transmitted to the gNB so that the gNB can adjust the scheduling policy for scheduling the UE. It is understood that mode 2d may be applicable to both multicast and unicast services. For embodiments within coverage, the scheduling UE may be configured by the base station. For embodiments outside coverage, the scheduling UE may be pre-configured as a scheduling UE. For example, a UE with high capability or scheduling capability may be appointed as a scheduling UE. For multicast services, a leader UE in a group (eg, a leading vehicle in a platoon) may manage the group.

[0062] In certain embodiments, in a first communication 408 transmitted from the TX UE 402 to the relay UE 404 (or multiple UEs, some or all of which may be relay UEs), the TX UE 402 transmits end-to-end latency information to the relay UE 402 for use in delivering a transport block by the relay UE 404. The end-to-end latency information may be conveyed by transmitting a remaining packet delay budget (e.g., a TTL configuration for transport block reception).

[0063] In some embodiments, SCI (e.g., SCI fields) or other signaling may be used to transmit the following information from TX UE 402 to relay UE 404: 1) end-to-end latency information; 2) resource reservation information for relay UE 404 to transmit or retransmit data (e.g., transport blocks) (e.g., this may be included in the first or second phase of SCI); and / or 3) a relay flag indicating whether a received multicast transport block with a destination group ID should be transmitted or retransmitted by relay UE 404 (e.g., based on HARQ feedback). In some embodiments, the relay flag may be an L2 or L3 flag present in a MAC CE, RLC, or PDCP header, rather than part of the SCI.

[0064] In various embodiments, one or more relay UEs 404 may be selected for transmission (or retransmission) of a transport block received from the TX UE 402. The selection of the one or more relay UEs 404 may be a selection of one or more UEs within a group (e.g., a queue) configured to receive and process HARQ feedback information from all member UEs in the group. The selection may be based on one of the following options: 1) the gNB may configure (e.g., semi-statically, statically, dynamically, etc.) the SUEs in the group that monitor HARQ NACK feedback within the group and transmit (or retransmit) a transport block in response to the received HARQ NACK feedback (there may be one or more SUEs in the group, and the UE IDs of the one or more SUEs may be known to the group members of the UE); 2) the selection of one or more relay UEs 404 for transmission (or retransmission) may be dynamically determined by the UEs in the group based on the HARQ NACK feedback and / or HARQ ACK feedback reception threshold (e.g., signal strength) (the threshold may be an RSRP or SINR threshold configured by the gNB or TX UE 402—e.g., any UE in the group that receives HARQ NACK feedback with a signal strength above a certain threshold may act as a relay UE 404 and may transmit (or retransmit) a transport block within the group); 3) the selection of one or more relay UEs 404 may be determined by the group member UEs based on the HARQ ACK feedback, HARQ NACK feedback and / or explicit signaling (for example, in one example, the group member UE may not decode the initial groupcast transport block and all group UEs may monitor the HARQ ACK feedback resources of the surrounding member UEs by not receiving the HARQ ACK from the nearby UEs. In another example, the group member UE may know that it needs to transmit or retransmit the transport block. The UE that did not receive the initial groupcast transport block may explicitly signal the need for transmission or retransmission, and the group member UE close to the UE may act as a relay UE 404 based on the received signal strength of the HARQ ACK message. In one embodiment, the explicit signaling may include L1 SCI signaling with a relay request flag.); and / or 4) all group member UEs or a subset of the group member UEs may be used for transmission, retransmission and / or relay (for example, based on the reception of HARQ ACK and / or HARQ NACK feedback).

[0065] In some embodiments, a relay UE 404 within the group may receive an initial transport block from the TX UE 402 and may monitor a third communication 412 including HARQ feedback and / or signaling transmitted from the RX UE 406 (eg, a group member UE) to the relay UE 404 .

[0066] The relay UE 404 may determine 414 whether it should retransmit the transport block to the RX UE 406 based on: whether the relay UE 404 is selected for retransmission; whether a HARQ ACK and / or HARQ NACK is received; the signal strength of the received HARQ ACK; the signal strength of the received HARQ NACK; and / or an explicit signal indicating a retransmission.

[0067] In response to the relay UE 404 determining 414 to retransmit the transport block, in a fourth communication 416 , the relay UE 404 retransmits the transport block to the RX UE 406 .

[0068] In various embodiments, relay UE 404 schedules transmissions or retransmissions taking into account the remaining packet delay budget value transmitted by TX UE 402. In one embodiment, the delay budget value may be used as a T2 value (eg, number of subframes or time slots expressed in ms) for candidate resource selection.

[0069] In some embodiments, the relay UE 404 may transfer a transport block (e.g., data) from a receive buffer to a transmit buffer for transmission or retransmission (e.g., in a fourth communication 416) based on a relay flag (e.g., a relay flag in the SCI, an L1 relay flag, an L2 relay flag, an L3 relay flag, etc.). In such an embodiment, the relay UE 404 may choose to transmit a transport block having the same HARQ process ID as that used by the TX UE 402, or the relay UE 404 may separately signal the HARQ process ID used by the TX UE 402 in the SCI and may signal a redundancy version signal (e.g., for soft combining). In various embodiments, the relay UE 404 may check the destination group ID corresponding to the transport block and determine whether the message is for itself and / or for transmission or retransmission (e.g., based on the relay flag and / or HARQ feedback).

[0070] In certain embodiments, the relay UE 404 may have a configured maximum HARQ retransmission counter for transport blocks that do not originate from the relay UE 404 to count the number of times the relay UE 404 retransmits the transport block.

[0071] In various embodiments, in a fifth communication 418 transmitted from the relay UE 404 to the TX UE 402, the relay UE 404 may transmit a status of the multicast message delivery (e.g., a status of a transmission or retransmission of the relay UE 404) to the TX UE 402. In such an embodiment, the TX UE 402 may provide feedback timing and resources to the relay UE 404 so that the status of the multicast message delivery may be sent to the TX UE 402. In an embodiment corresponding to NR Mode 1 in which the gNB schedules sidelink transmissions of the relay UE 404, the downlink control information or semi-static configuration contains additional information elements regarding the beam scanning configuration, which includes the time, frequency, spatial direction, and / or antenna panel of the relay UE 404 selected for multicast or unicast control channel and data channel transmissions. In an embodiment corresponding to UE-to-UE relay, the TX UE 402 configures the relay UE 404 with side link control information or a semi-static configuration regarding a beam scanning configuration, including selection of time, frequency, spatial direction and / or antenna panel of the relay UE 404 for multicast or unicast control channel and data channel transmission.

[0072] Figure 5 5 is a schematic block diagram illustrating another embodiment of a communication 500 corresponding to transmitting data using a relay user equipment (e.g., relay based on blind hopping without HARQ feedback - within or outside the group). The communication 500 includes messages transmitted between a TX UE 502, a relay UE 504 (e.g., an intermediate UE), and an RX UE 506. It will be appreciated that any communication described herein may include one or more messages.

[0073] In one embodiment, in a first communication 508 transmitted from a TX UE 502 (or another relay UE) to a relay UE 504 (or multiple UEs, some or all of which may be relay UEs), the TX UE 502 transmits a transport block (e.g., data) with an indication for the transport block to be relayed by the relay UE 504 (e.g., any other UE in the group, all other UEs in the group, etc.) without waiting for any HARQ feedback and including a desired hop count for transport block delivery (e.g., in an SCI).

[0074] In some embodiments, the TX UE 502 may reserve resources for the relay UE 504 for transmission (or retransmission) of a transport block. In addition, as part of the first communication 508 (or in another communication), the TX UE 502 may provide the relay UE 504 with reserved resource information. The reserved resource information may include auxiliary information for reserved resources such as for periodic resource reservations used for periodic traffic. In some embodiments, the TX UE 502 may provide the reserved resource information to the relay UE 504 via the first or second phase of the SCI in L1 or L2.

[0075] In some embodiments, if there is no resource reservation information transmitted from TX UE 502 (e.g., in the SCI) to relay UE 504, then relay UE 504 may select one or more resources for transmission (or retransmission) from a resource pool (e.g., a dedicated resource pool for such transmission) based on sensing which resources in the resource pool are available or by randomly selecting resources from within the resource pool. In some embodiments, the resource pool may operate based on mode 2d.

[0076] In some embodiments, in a first communication 508 transmitted from the TX UE 502 to the relay UE 504 (or multiple UEs, some or all of which may be relay UEs), the TX UE 502 (or another relay UE) transmits end-to-end latency information to the relay UE 504 for the relay UE 504 to use for delivering the transport block. The end-to-end latency information may be conveyed by transmitting a remaining packet delay budget (e.g., a TTL configuration for transport block reception).

[0077] In some embodiments, SCI (e.g., SCI field) or other signaling may be used to transmit the following information from TX UE 502 to relay UE 504: 1) end-to-end delay information; 2) resource reservation information for relay UE 504 to transmit or retransmit data (e.g., transport block) (e.g., this may be included in the first or second phase of SCI); 3) direction of data to be relayed, such as information indicating area ID (e.g., ID corresponding to the area of ​​UE), direction of transmission data and / or communication range (e.g., MCR); and / or 4) remaining hop count, remaining packet delay budget, destination group ID, destination node ID and / or relay node ID. It is understood that the area ID may be an identifier corresponding to a geographic area or region.

[0078] In various embodiments, one or more relay UEs 504 may be selected for transmission (or retransmission) of a transport block received from the TX UE 502. The selection of one or more relay UEs 504 may be a selection of one or more UEs within a group (e.g., a queue). The selection may be based on one of the following options: 1) UEs within the group; 2) UEs outside the group; 3) relay node ID (e.g., transmitted by the gNB in ​​the DCI, such as part of the gNB assisted sidelink scheduling, L1 relay ID, L2 relay ID, etc.); 4) direction, geographic location, regional ID and / or MCR; 5) the gNB, group leader UE, or SUE may configure (e.g., semi-statically, statically, dynamically, etc.) one or more relay UEs 504 to transmit (or retransmit) a transport block; and / or 6) all group member UEs or a subset of group member UEs may be used for transmission, retransmission, and / or relaying. In certain embodiments, such as for NR Mode 1 scheduling, the TX UE 402, as part of the UE assistance information, may provide information such as direction, geolocation, area ID, and / or MCR to the gNB.

[0079] In various embodiments, the L1 or L2 destination ID field can be set as follows: 1) if a multicast message (e.g., data, transport block) needs to be relayed within the same group (e.g., blindly), the target group ID should be set to the group ID of the sending multicast message; 2) if a unicast message needs to be relayed within or outside the group, the destination node ID and relay node ID should be set so that the relay UE 504 (with the relay node ID) relays the message based on the destination node ID; 3) the relay UE 504 can implicitly understand from the destination group ID and the remaining hop count (value>0) that the message will be transmitted or retransmitted to the group with the destination group ID - so the relay UE 504 passes the received data from its RX buffer to its TX buffer and transmits or retransmits the message to the group with the destination group ID; and / or 4) the relay UE 504 (with the relay node ID) can implicitly understand from the destination node ID and the relay node ID that a message not for itself will be transmitted or retransmitted - so the relay UE 504 passes the received data from the RX buffer to the TX buffer for transmission to the destination node ID.

[0080] Relay UE 504 determines 512 whether to retransmit a transport block received from TX UE 502 (or another relay UE). To make this determination, relay UE 504 considers assistance information received from TX UE 502 (or another relay UE), such as remaining hop count and remaining packet delay budget.

[0081] In response to the relay UE 504 determining 512 to retransmit the transport block, in a third communication 514 , the relay UE 504 retransmits the transport block to the RX UE 506 .

[0082] In certain embodiments, for multicast transmission of a message, the relay UE 504 processes the message and then transmits or retransmits the message by passing the message from its RX buffer to its TX buffer with information such as the destination group ID and remaining hop count.

[0083] In various embodiments, for unicast transmission of a message, the relay UE 504 receives the message using the relay ID, does not process the message for itself, and then passes the message to its TX buffer with information such as the destination node ID and the relay ID to transmit or retransmit the message using the destination node ID.

[0084] In some embodiments, the relay UE 504 checks the area ID, MCR, and / or remaining hop count before transmitting or retransmitting the message to ensure that the message should be transmitted or retransmitted and transmits the message to correct the UE. For example, if the remaining hop count is greater than zero, the message should be transmitted or retransmitted. In some embodiments, the relay UE 504 adjusts the area ID, MCR, and / or remaining hop count and includes the adjusted area ID, adjusted MCR, and / or adjusted remaining hop count with the message being transmitted and / or retransmitted.

[0085] Figure 6 is a flow chart illustrating one embodiment of a method 600 for transmitting data corresponding to a relay user device. In some embodiments, the method 600 is performed by an apparatus such as the remote unit 102. In certain embodiments, the method 600 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0086] The method 600 may include transmitting 602 data and first information indicating relay information corresponding to a retransmission of the data by a relay user device to at least one user device. In such an embodiment, the at least one user device is within a predetermined user device group or outside a predetermined user device group, and the first information includes a relay identifier, an indication that the retransmission of the data is based on feedback received by the relay user device, an indication that the retransmission of the data is based on a multi-hop count, an indication that the relay user device transfers the data from a receiver buffer to a transmission buffer and retransmits the data from the transmission buffer, an indication that the relay user device retransmits the data to an indicated destination node, or some combination thereof. In some embodiments, the method 600 includes transmitting 604 second information indicating a remaining packet delay budget to at least one user device.

[0087] In some embodiments, the data includes a transport block. In some embodiments, the second information is part of scheduling assistance information. In various embodiments, the first information and the second information are part of side link control information. In some embodiments, the first information and the second information can be transmitted together for a single-stage SCI or separately for a two-stage SCI.

[0088] In one embodiment, at least one user device is selected based on the scheduled user device. In some embodiments, at least one user device is selected based on negative feedback signal strength, positive feedback signal strength, a signal indicating retransmission, or some combination thereof. In some embodiments, at least one user device is selected based on geographic location, direction, region, configuration, or some combination thereof.

[0089] In various embodiments, the method 600 further includes transmitting third information indicating resource reservation information for at least one user equipment to retransmit data, wherein the resource reservation information includes periodic resource reservation information. In one embodiment, the method 600 further includes transmitting scheduling assistance information including user equipment assistance information indicating a traffic arrival rate of periodic traffic. In some embodiments, the method 600 further includes transmitting third information including a destination group identifier, wherein the third information is used to determine whether to process the data internally, whether to retransmit the data, or a combination thereof.

[0090] In some embodiments, the first information is used to determine whether to process the data internally, whether to retransmit the data, or a combination thereof. In various embodiments, method 600 further includes transmitting third information including an area corresponding to the data, a minimum communication range, a remaining hop count, or some combination thereof.

[0091] Figure 7 is a flow chart illustrating one embodiment of a method 700 for receiving data corresponding to a relay user device. In some embodiments, the method 700 is performed by an apparatus such as the remote unit 102. In certain embodiments, the method 700 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0092] The method 700 may include receiving 702, by at least one user device, data and first information indicating relay information corresponding to a retransmission of the data by a relay user device. In such embodiments, the at least one user device is within a predetermined user device group or outside a predetermined user device group, and the first information includes a relay identifier, an indication that the retransmission of the data is based on feedback received by the relay user device, an indication that the retransmission of the data is based on a multi-hop count, an indication that the relay user device transfers the data from a receiver buffer to a transmission buffer and retransmits the data from the transmission buffer, an indication that the relay user device retransmits the data to an indicated destination node, or some combination thereof. In certain embodiments, the method 700 includes receiving 704, by at least one user device, second information indicating a remaining packet delay budget.

[0093] In some embodiments, the data includes a transport block. In some embodiments, the second information is part of scheduling assistance information. In various embodiments, the first information and the second information are part of side link control information. In some embodiments, the first information and the second information can be transmitted together for a single-stage SCI or separately for a two-stage SCI.

[0094] In one embodiment, at least one user device is selected based on the scheduled user device. In some embodiments, at least one user device is selected based on negative feedback signal strength, positive feedback signal strength, a signal indicating retransmission, or some combination thereof. In some embodiments, at least one user device is selected based on geographic location, direction, region, configuration, or some combination thereof.

[0095] In various embodiments, the method 700 further includes receiving third information indicating resource reservation information for at least one user equipment to retransmit data, wherein the resource reservation information includes periodic resource reservation information. In one embodiment, the method 700 further includes receiving scheduling assistance information, the scheduling assistance information including user equipment assistance information indicating a traffic arrival rate of periodic traffic. In some embodiments, the method 700 further includes receiving third information including a destination group identifier, wherein the third information is used to determine whether to process the data internally, whether to retransmit the data, or a combination thereof.

[0096] In some embodiments, the first information is used to determine whether to process the data internally, whether to retransmit the data, or a combination thereof. In various embodiments, method 700 further includes receiving third information including a region corresponding to the data, a minimum communication range, a remaining hop count, or some combination thereof.

[0097] In one embodiment, a method includes: transmitting data and first information indicating relay information corresponding to retransmission of the data by a relay user device to at least one user device, wherein the at least one user device is within a predetermined user device group or outside the predetermined user device group, the first information including a relay identifier, an indication that the retransmission of the data is based on feedback received by the relay user device, an indication that the retransmission of the data is based on a multi-hop count, an indication that the relay user device passes the data from a receiver buffer to a transmission buffer and retransmits the data from the transmission buffer, an indication that the relay user device retransmits the data to an indicated destination node, or some combination thereof; and transmitting second information indicating a remaining packet delay budget to the at least one user device.

[0098] In some embodiments, the data comprises a transport block.

[0099] In some embodiments, the second information is part of scheduling assistance information.

[0100] In various embodiments, the first information and the second information are part of sidelink control information.In some embodiments, the first information and the second information may be transmitted together for a single-stage SCI or separately for a two-stage SCI.

[0101] In one embodiment, the at least one user equipment is selected based on scheduling user equipment.

[0102] In some embodiments, the at least one user equipment is selected based on negative feedback signal strength, positive feedback signal strength, a signal indicating retransmission, or some combination thereof.

[0103] In some embodiments, the at least one user device is selected based on geographic location, direction, region, configuration, or some combination thereof.

[0104] In various embodiments, the method further comprises transmitting third information indicating resource reservation information for the at least one user equipment to retransmit the data, wherein the resource reservation information comprises periodic resource reservation information.

[0105] In one embodiment, the method further comprises transmitting scheduling assistance information, the scheduling assistance information comprising user equipment assistance information indicating a traffic arrival rate for the periodic traffic.

[0106] In some embodiments, the method further includes transmitting third information including a destination group identifier, wherein the third information is used to determine whether to process the data internally, whether to retransmit the data, or a combination thereof.

[0107] In some embodiments, the first information is used to determine whether to process the data internally, whether to retransmit the data, or a combination thereof.

[0108] In various embodiments, the method further includes transmitting third information including a region corresponding to the data, a minimum communication range, a remaining hop count, or some combination thereof.

[0109] In one embodiment, an apparatus comprises: a transmitter, which: transmits data and first information indicating relay information corresponding to retransmission of the data by a relay user device to at least one user device, wherein the at least one user device is within a predetermined user device group or outside the predetermined user device group, the first information comprising a relay identifier, an indication that the retransmission of the data is based on feedback received by the relay user device, an indication that the retransmission of the data is based on a multi-hop count, an indication that the relay user device passes the data from a receiver buffer to a transmission buffer and retransmits the data from the transmission buffer, an indication that the relay user device retransmits the data to an indicated destination node, or some combination thereof; and transmits second information indicating a remaining packet delay budget to the at least one user device.

[0110] In some embodiments, the data comprises a transport block.

[0111] In some embodiments, the second information is part of scheduling assistance information.

[0112] In various embodiments, the first information and the second information are part of sidelink control information.In some embodiments, the first information and the second information may be transmitted together for the single-stage SCI or separately for the two-stage SCI.

[0113] In one embodiment, the at least one user equipment is selected based on scheduling user equipment.

[0114] In some embodiments, the at least one user equipment is selected based on negative feedback signal strength, positive feedback signal strength, a signal indicating retransmission, or some combination thereof.

[0115] In some embodiments, the at least one user device is selected based on geographic location, direction, region, configuration, or some combination thereof.

[0116] In various embodiments, the transmitter transmits third information, the third information indicating resource reservation information for the at least one user equipment to retransmit the data, and the resource reservation information includes periodic resource reservation information.

[0117] In one embodiment, the transmitter transmits scheduling assistance information including user equipment assistance information indicating a traffic arrival rate for periodic traffic.

[0118] In some embodiments, the transmitter transmits third information including a destination group identifier, and the third information is used to determine whether to process the data internally, whether to retransmit the data, or a combination thereof.

[0119] In some embodiments, the first information is used to determine whether to process the data internally, whether to retransmit the data, or a combination thereof.

[0120] In various embodiments, the transmitter transmits third information including a region corresponding to the data, a minimum communication range, a remaining hop count, or some combination thereof.

[0121] In one embodiment, a method comprises: receiving, by at least one user device, data and first information indicating relay information corresponding to a retransmission of the data by a relay user device, wherein the at least one user device is within a predetermined user device group or outside the predetermined user device group, the first information comprising a relay identifier, an indication that the retransmission of the data is based on feedback received by the relay user device, an indication that the retransmission of the data is based on a multi-hop count, an indication that the relay user device passes the data from a receiver buffer to a transmission buffer and retransmits the data from the transmission buffer, an indication that the relay user device retransmits the data to an indicated destination node, or some combination thereof; and the at least one user device receiving second information indicating a remaining packet delay budget.

[0122] In some embodiments, the data comprises a transport block.

[0123] In some embodiments, the second information is part of scheduling assistance information.

[0124] In various embodiments, the first information and the second information are part of sidelink control information.In some embodiments, the first information and the second information may be transmitted together for a single-stage SCI or separately for a two-stage SCI.

[0125] In one embodiment, the at least one user equipment is selected based on scheduling user equipment.

[0126] In some embodiments, the at least one user equipment is selected based on negative feedback signal strength, positive feedback signal strength, a signal indicating retransmission, or some combination thereof.

[0127] In some embodiments, the at least one user device is selected based on geographic location, direction, region, configuration, or some combination thereof.

[0128] In various embodiments, the method further comprises receiving third information indicating resource reservation information for the at least one user equipment to retransmit the data, wherein the resource reservation information comprises periodic resource reservation information.

[0129] In one embodiment, the method further comprises receiving scheduling assistance information, the scheduling assistance information comprising user equipment assistance information indicating a traffic arrival rate for the periodic traffic.

[0130] In certain embodiments, the method further includes receiving third information including a destination group identifier, wherein the third information is used to determine whether to process the data internally, whether to retransmit the data, or a combination thereof.

[0131] In some embodiments, the first information is used to determine whether to process the data internally, whether to retransmit the data, or a combination thereof.

[0132] In various embodiments, the method further includes receiving third information including a region corresponding to the data, a minimum communication range, a remaining hop count, or some combination thereof.

[0133] In one embodiment, an apparatus comprises: a receiver: receiving data and first information indicating relay information corresponding to retransmission of the data by a relay user device by at least one user device, wherein the at least one user device is within a predetermined user device group or outside the predetermined user device group, the first information comprising a relay identifier, an indication that the retransmission of the data is based on feedback received by the relay user device, an indication that the retransmission of the data is based on a multi-hop count, an indication that the relay user device passes the data from a receiver buffer to a transmission buffer and retransmits the data from the transmission buffer, an indication that the relay user device retransmits the data to an indicated destination node, or some combination thereof; and receiving second information indicating a remaining packet delay budget by the at least one user device.

[0134] In some embodiments, the data comprises a transport block.

[0135] In some embodiments, the second information is part of scheduling assistance information.

[0136] In various embodiments, the first information and the second information are part of sidelink control information.In some embodiments, the first information and the second information may be transmitted together for a single-stage SCI or separately for a two-stage SCI.

[0137] In one embodiment, the at least one user equipment is selected based on scheduling user equipment.

[0138] In some embodiments, the at least one user equipment is selected based on negative feedback signal strength, positive feedback signal strength, a signal indicating retransmission, or some combination thereof.

[0139] In some embodiments, the at least one user device is selected based on geographic location, direction, region, configuration, or some combination thereof.

[0140] In various embodiments, the receiver receives third information indicating resource reservation information for the at least one user equipment to retransmit the data, and the resource reservation information includes periodic resource reservation information.

[0141] In one embodiment, the receiver receives scheduling assistance information, the scheduling assistance information comprising user equipment assistance information indicating a traffic arrival rate for periodic traffic.

[0142] In some embodiments, the receiver receives third information including a destination group identifier, and the third information is used to determine whether to process the data internally, whether to retransmit the data, or a combination thereof.

[0143] In some embodiments, the first information is used to determine whether to process the data internally, whether to retransmit the data, or a combination thereof.

[0144] In various embodiments, the receiver receives third information including a region corresponding to the data, a minimum communication range, a remaining hop count, or some combination thereof.

[0145] Embodiments may be practiced in other specific forms. The described embodiments should be considered in all respects as merely illustrative and not restrictive. Therefore, the scope of the present invention is indicated by the appended claims rather than the preceding description. All changes within the meaning and equivalent range of the claims are included within their scope.

Claims

1. A method performed or executable by a user equipment (UE), the method comprising: receiving data and first information indicating relay information corresponding to a retransmission of the data by a relay UE, wherein the UE is within a predetermined UE group or outside the predetermined UE group, the first information comprising a relay identifier, an indication that the retransmission of the data is based on feedback received by the relay UE, an indication that the retransmission of the data is based on a multi-hop count, an indication that the relay UE transfers the data from a receiver buffer to a transmission buffer and retransmits the data from the transmission buffer, an indication that the relay UE retransmits the data to an indicated destination node, or a combination thereof; as well as receiving second information indicating a remaining packet delay budget (PDB); and The first information and the remaining PDB are used to schedule retransmission of the data.

2. The method according to claim 1, wherein: The remaining PDB includes a time-to-live configuration for packet reception.

3. The method according to claim 1, wherein: The first information includes a relay flag.

4. The method of claim 1, further comprising receiving feedback resources and timing information to carry feedback corresponding to the data transmission.

5. A user equipment (UE), comprising: at least one memory; as well as at least one processor, the at least one processor being coupled to the at least one memory and configured to cause the UE to: receiving data and first information indicating relay information corresponding to a retransmission of the data by a relay UE, wherein the at least one UE is within a predetermined UE group or outside the predetermined UE group, the first information comprising a relay identifier, an indication that the retransmission of the data is based on feedback received by the relay UE, an indication that the retransmission of the data is based on a multi-hop count, an indication that the relay UE transfers the data from a receiver buffer to a transmission buffer and retransmits the data from the transmission buffer, an indication that the relay UE retransmits the data to an indicated destination node, or a combination thereof; as well as receiving second information indicating a remaining packet delay budget (PDB); and The first information and the remaining PDB are used to schedule retransmission of the data.

6. The UE according to claim 5, wherein: The remaining PDB includes a time-to-live configuration for packet reception.

7. The UE according to claim 5, wherein: The first information includes a relay flag.

8. The UE according to claim 5, wherein: The at least one processor is configured to cause the UE to: Feedback resources and timing information are received to carry feedback corresponding to the data transmission.

Images