Configuring sidelink hybrid automatic repeat request

Abstract

Apparatuses, methods, and systems are disclosed for configuring sidelink hybrid automatic repeat request. One method includes communicating, via a first sidelink device, with a second sidelink device using a first sidelink communication interface. The second sidelink device communicates with a third sidelink device using a second sidelink communication interface. The method includes transmitting, via the first sidelink communication interface, a sidelink hybrid automatic repeat request configuration to the second sidelink device. The sidelink hybrid automatic repeat request configuration includes a sidelink hybrid automatic repeat request feedback enable indicator, a sidelink hybrid automatic repeat request feedback disable indicator, a sidelink hybrid automatic repeat request feedback option, a minimum communication range value, a cast type, a group size, a reflective indicator, a non-reflective indicator, or some combination thereof.

Description

[0001] Cross-reference to related applications

[0002] This application claims U.S. Patent Application Serial No. 63 / 061,715, filed August 5, 2020, entitled "Apparatus, Methods, and Systems for a Sidelink Resource Allocation Process for Sidelink Relay Communication," filed by Joachim Loehr; U.S. Patent Application Serial No. 63 / 061,715, filed August 5, 2020, entitled "Mechanisms for Improved Communication Using Relay Over Sidelink Radio Interface," filed by Prateek Basu Mallick; and U.S. Patent Application Serial No. 63 / 061,725, filed August 5, 2020, entitled "Selection of Relay Delivery in Sidelink." The priority of this application is given to U.S. Patent Application Serial No. 63 / 061,731, entitled "Selection of Relay Device in Sidelink Communications"; U.S. Patent Application Serial No. 63 / 061,734, entitled "MECHANISMSTO SUPPORT TRANSMISSION FEEDBACK OVER SIDELINK RELAY", filed August 5, 2020 by Prateek Basu Mallick; and U.S. Patent Application Serial No. 63 / 061,746, entitled "Apparatus, Methods, and Systems FOR DETERMINING THE BEHAVIOUROF A SIDELINK RELAY UE USING MCR AND ZONE", filed August 5, 2020 by Karthikeyan Ganesan, entitled "Apparatus, Methods, and Systems for Determining the Behaviour of a Sidelink Relay UE Using MCR and Zone". All applications are incorporated herein by reference in their entirety. Technical Field

[0003] The topics disclosed in this article generally relate to wireless communication, and more specifically to configuring sidelink hybrid automatic repeat requests. Background Technology

[0004] In some wireless communication networks, feedback can be transmitted via a side link. The configuration of the feedback mechanism may be unknown. Summary of the Invention

[0005] A method for configuring a sidelink hybrid auto-repeat request is disclosed. Apparatus and systems also perform the functions of the method. One embodiment of the method includes communicating with a second sidelink device via a first sidelink device using a first sidelink communication interface. The second sidelink device communicates with a third sidelink device using a second sidelink communication interface. In some embodiments, the method includes transmitting a sidelink hybrid auto-repeat request configuration to the second sidelink device via the first sidelink communication interface. In some embodiments, the sidelink hybrid auto-repeat request configuration includes a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, a playback type, a group size, a reflection indicator, a non-reflection indicator, or some combinations thereof.

[0006] An apparatus for configuring a sidelink hybrid auto-repeat request includes a first sidelink device. In some embodiments, the apparatus includes a transceiver that: communicates with a second sidelink device using a first sidelink communication interface, wherein the second sidelink device communicates with a third sidelink device using a second sidelink communication interface; and transmits a sidelink hybrid auto-repeat request configuration to the second sidelink device via the first sidelink communication interface. In some embodiments, the sidelink hybrid auto-repeat request configuration includes a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, a playback type, a group size, a reflection indicator, a non-reflection indicator, or combinations thereof.

[0007] Another embodiment of a method for configuring a sidelink hybrid auto-repeat request includes communicating with a first sidelink device via a second sidelink device using a first sidelink communication interface, and communicating with a third sidelink device using the second sidelink communication interface. In some embodiments, the method includes receiving a sidelink hybrid auto-repeat request configuration from the first sidelink device via the first sidelink communication interface. In some embodiments, the sidelink hybrid auto-repeat request configuration includes a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, a playback type, a group size, a reflection indicator, a non-reflection indicator, or some combinations thereof.

[0008] Another apparatus for configuring a sidelink hybrid auto-repeat request includes a second sidelink device. In some embodiments, the apparatus includes a transceiver that: communicates with a first sidelink device using a first sidelink communication interface, and communicates with a third sidelink device using a second sidelink communication interface; and receives a sidelink hybrid auto-repeat request configuration from the first sidelink device via the first sidelink communication interface. In various embodiments, the sidelink hybrid auto-repeat request configuration includes a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, a playback type, a group size, a reflection indicator, a non-reflection indicator, or some combination thereof. Attached Figure Description

[0009] A more detailed description of the embodiments briefly described above will be presented with reference to the specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only some embodiments and are not intended to be limiting of the scope; the embodiments will be described and explained with additional specificity and detail using the drawings, in which:

[0010] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system for configuring sidelink hybrid automatic repeat requests;

[0011] Figure 2 This is a schematic block diagram illustrating one embodiment of a device that can be used to configure a sidelink hybrid automatic repeat request;

[0012] Figure 3 This is a schematic block diagram illustrating one embodiment of a device that can be used to configure a sidelink hybrid automatic repeat request;

[0013] Figure 4 This is a schematic block diagram illustrating one embodiment of a system for relay communication;

[0014] Figure 5 This is a schematic block diagram illustrating one embodiment of a system in which the TX remote UE senses the MCR;

[0015] Figure 6 This is a schematic block diagram illustrating one embodiment of a system in which the relay UE senses the MCR;

[0016] Figure 7 This is a schematic block diagram illustrating one embodiment of a system that includes selection windows for TX remote UEs and relay UEs;

[0017] Figure 8 This is a flowchart illustrating one embodiment of a method for configuring sidelink hybrid automatic repeat requests; and

[0018] Figure 9 This is a flowchart illustrating another embodiment of a method for configuring sidelink hybrid automatic repeat requests. Detailed Implementation

[0019] As those skilled in the art will understand, aspects of the embodiments can be embodied as systems, apparatus, methods, or program products. Therefore, embodiments can take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects, which may generally be referred to herein as “circuit,” “module,” or “system.” Furthermore, embodiments can take the form of program products 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-transitory, and / or non-transferable. The storage device may not embody signals. In one embodiment, the storage device uses only signals for accessing the code.

[0020] Certain functional units described in this specification may be designated as modules to more specifically emphasize their implementation independence. For example, modules may be implemented as hardware circuits comprising custom very large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Modules may also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0021] Modules can also be implemented in code and / or software for execution by various types of processors. Identified code modules may, for example, comprise one or more physical or logical blocks of executable code, which may be organized, for example, as objects, procedures, or functions. However, the executable files of identified modules do not need to be physically located together, but may include different instructions stored in different locations that, when logically joined together, comprise the module and achieve its purpose.

[0022] In practice, a module of code can be a single instruction or many instructions, and can even be distributed across several different code segments, different programs, and across several memory devices. Similarly, in this document, operational data can be identified and visualized within a module, and can be represented in any suitable form and organized within any suitable type of data structure. Operational data can be collected as a single dataset or can be distributed across different locations, including different computer-readable storage devices. Where a module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0023] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof.

[0024] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable compact disk read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium capable of containing or storing programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0025] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer can 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 it can be connected to an external computer (e.g., via the Internet through an Internet service provider).

[0026] References to "an embodiment," "embodiment," or similar language in this specification mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Therefore, unless expressly stated otherwise, throughout this specification, the phrases "in an embodiment," "in an embodiment," and similar language may, but not necessarily all, refer to the same embodiment, but rather mean "one or more, but not all, embodiments." Unless expressly stated otherwise, the terms "comprising," "including," "having," and variations thereof mean "including, but not limited to,". Unless expressly stated otherwise, the list of enumerated items does not imply that any or all items are mutually exclusive. Unless expressly stated otherwise, the terms "a," "an," and "the" also mean "one or more".

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

[0028] The following description of aspects of embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to generate machinery, such that instructions executable via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / actions specified in the blocks or blocks of the schematic flowcharts and / or schematic block diagrams.

[0029] The code may also be stored in a storage device that can instruct a computer, other programmable data processing device or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of art including instructions that implement the functions / actions specified in the schematic flowchart and / or schematic block diagram boxes or blocks.

[0030] The code may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device, thereby producing a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the function / action specified in the flowchart and / or block diagram boxes or boxes.

[0031] The schematic flowcharts and / or schematic block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowcharts and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing a specified logical function.

[0032] It should also be noted that in some alternative implementations, the functions marked in the boxes may occur in a different order than those marked in the figures. For example, two boxes shown consecutively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order, depending on the functions involved. Other steps and methods that are functionally, logically, or effectively equivalent to one or more boxes or portions thereof in the illustrated figures can be envisioned.

[0033] While various arrow and line types may be used in flowcharts 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 may be used only to indicate the logical flow of the depicted embodiment. For example, an arrow may indicate a wait or monitoring period of unspecified duration between enumeration steps in a depicted embodiment. It will also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs a specific function or action.

[0034] The description of the elements in each figure can be referenced to the elements in the preceding figures. The same numbers refer to the same elements in all figures, including alternative embodiments of the same elements.

[0035] Figure 1 An embodiment of a wireless communication system 100 for configuring sidelink hybrid automatic repeat requests is described. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although in Figure 1 A specific number of remote units 102 and network units 104 are depicted, but those skilled in the art will recognize that any number of remote units 102 and network units 104 can be included in the wireless communication system 100.

[0036] In one embodiment, remote unit 102 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., internet-connected televisions), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), aircraft, drones, etc. In some embodiments, remote unit 102 includes wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 102 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, UE, user terminal, device, or other terms used in the art. Remote unit 102 may communicate directly with one or more network units 104 via UL communication signals. In some embodiments, remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0037] Network units 104 can be distributed across a geographical area. In some embodiments, network element 104 may also be referred to as and / or may include an access point, access terminal, base station, base station, location server, core network (“CN”), radio network entity, node-B, evolved node-B (“eNB”), 5G node-B (“gNB”), home node-B, relay node, device, core network, air server, radio access node, access point (“AP”), new radio (“NR”), network entity, access and mobility management function (“AMF”), unified data management (“UDM”), unified data repository (“UDR”), UDM / UDR, policy control function (“PCF”), radio access network (“RAN”), network slice selection function (“NSSF”), operations, administration and management (“OAM”), session management function (“SMF”), user plane function (“UPF”), application function, authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non-3GPP gateway function (“TNGF”), or one or more of any other terms used in the art. Network unit 104 is typically part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network units 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 the public switched telephone network, as well as other networks. These and other elements of the radio access and core networks are not illustrated, but are generally well known to those skilled in the art.

[0038] In one implementation, the wireless communication system 100 conforms to the NR protocol standardized in the 3rd Generation Partnership Project (“3GPP”), wherein network unit 104 transmits using an OFDM modulation scheme on the downlink (“DL”), and remote unit 102 transmits using a single-carrier frequency division multiple access (“SC-FDMA”) scheme or an orthogonal frequency division multiplexing (“OFDM”) scheme on the uplink (“UL”). However, more generally, the wireless communication system 100 may implement other open or proprietary communication protocols, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, and CDMA2000. ZigBee, Sigfoxx, and other protocols. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0039] Network unit 104 can serve multiple remote units 102 within a service area (e.g., a cell or cell sector) via a wireless communication link. Network unit 104 transmits DL communication signals in the time, frequency, and / or spatial domains to serve the remote units 102.

[0040] In various embodiments, remote unit 102 can communicate with a second sidelink device via a first sidelink device using a first sidelink communication interface. The second sidelink device communicates with a third sidelink device using a second sidelink communication interface. In some embodiments, remote unit 102 can transmit a sidelink hybrid auto-repeat request configuration to the second sidelink device via the first sidelink communication interface. In some embodiments, the sidelink hybrid auto-repeat request configuration includes a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, a playback type, a group size, a reflection indicator, a non-reflection indicator, or some combinations thereof. Therefore, remote unit 102 can be used to configure a sidelink hybrid auto-repeat request.

[0041] In some embodiments, remote unit 102 can communicate with a first sidelink device via a second sidelink device using a first sidelink communication interface, and communicate with a second sidelink device via a second sidelink communication interface. In some embodiments, remote unit 102 can receive sidelink hybrid auto-repeat request configuration from the first sidelink device via the first sidelink communication interface. In some embodiments, the sidelink hybrid auto-repeat request configuration includes a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, a playback type, a group size, a reflection indicator, a non-reflection indicator, or some combinations thereof. Therefore, remote unit 102 can be used to configure the sidelink hybrid auto-repeat request.

[0042] Figure 2 An embodiment of an apparatus 200 that can be used to configure a sidelink hybrid automatic repeat request is depicted. Apparatus 200 includes one embodiment of a remote unit 102. Furthermore, 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 touchscreen. 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, memory 204, transmitter 210, and receiver 212, and may not include the input device 206 and / or display 208.

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

[0044] 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 disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile 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 algorithms operating on remote unit 102.

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

[0046] In one embodiment, display 208 may include any known electronically controllable display or display device. Display 208 may be designed to output visual, auditory, 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, a liquid crystal display (“LCD”), a light-emitting diode (“LED”) display, an organic light-emitting diode (“OLED”) display, a projector, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, display 208 may include wearable displays such as smartwatches, smart glasses, head-up displays, etc. Furthermore, display 208 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0047] In some embodiments, display 208 includes one or more speakers for generating sound. For example, display 208 may generate an audible alarm or notification (e.g., a beep or ringtone). In some embodiments, display 208 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of display 208 may be integrated with input device 206. For example, input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, display 208 may be located near input device 206.

[0048] In some embodiments, the transceiver: communicates with a second sidelink device using a first sidelink communication interface, wherein the second sidelink device communicates with a third sidelink device using the same second sidelink communication interface; and transmits a sidelink hybrid auto-repeat request configuration to the second sidelink device via the first sidelink communication interface. In some embodiments, the sidelink hybrid auto-repeat request configuration includes a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, a playback type, a group size, a reflection indicator, a non-reflection indicator, or some combinations thereof.

[0049] In some embodiments, the transceiver: communicates with a first sidelink device using a first sidelink communication interface and with a third sidelink device using a second sidelink communication interface; and receives a sidelink hybrid auto-repeat request configuration from the first sidelink device via the first sidelink communication interface. In various embodiments, the sidelink hybrid auto-repeat request configuration includes a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, a playback type, a group size, a reflection indicator, a non-reflection indicator, or some combination thereof.

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

[0051] Figure 3 An embodiment of an apparatus 300 that can be used to configure a sidelink hybrid automatic repeat request is described. Apparatus 300 includes one embodiment of a network unit 104. Furthermore, 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. As will be understood, processor 302, memory 304, input device 306, display 308, transmitter 310, and receiver 312 may be substantially similar to processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212 of remote unit 102, respectively.

[0052] In some embodiments, two types of relays may exist: 1) UE to network coverage extension: UE to network (“Uu”) interface coverage accessibility may be necessary for the UE to reach a server in the packet data network (“PDN”) or a corresponding user equipment (“UE”) outside the vicinity area—various embodiments for UE to network relay may be limited to technologies based on Evolved Universal Terrestrial Access (“EUTRA”) and may not be applied to NR-based systems (e.g., for Next Generation (“NG”) Radio Access Networks (“RAN”) (“NG-RAN”) and NR-based sidelink communications); 2) UE to UE coverage extension: current proximity accessibility may be limited to single-hop sidelink links via EUTRA-based or NR-based sidelink technologies—given the limited single-hop sidelink coverage, this may not be sufficient if Uu coverage is not available.

[0053] In various embodiments, for both sidelink (“SL”) relay types, an SL remote UE can discover and select a relay for transmissions to another SL remote UE. In some embodiments, the reliability requirement is 10^-5 and may increase with public safety requirements. In some embodiments, communication applications such as the Industrial Internet of Things (“IIoT”) and other applications may use sidelinks and may require higher reliability and extended coverage. SL relays can be used to increase coverage using one-hop or multi-hop methods. The various embodiments found herein can be used to achieve higher reliability and extended coverage.

[0054] In some embodiments, transmission of the SL relay UE can be performed based on the minimum communication range (“MCR”) value to select the transport block (“TB”), and signaling and behavior of the SL relay UE can be taken into account using distance-based feedback of the MCR and area ID corresponding to the remote UE.

[0055] As used herein, the terms eNB and / or gNB can be used for a base station, but can be replaced by any other radio access node, such as a base station (“BS”), eNB, gNB, access point (“AP”), new radio (“NR”), etc. Furthermore, while the various embodiments described herein may relate to fifth-generation (“5G”) NR systems, the communication addresses are equally applicable to other mobile communication systems that support serving cells and / or are configured for sidelink communication via a UE-to-UE (“PC5”) interface.

[0056] It should be noted that the following terms are used in this document: 1) UE to network relay: N relay; 2) UE to UE relay: UE relay; and 3) relay = UE to network relay or UE to UE relay.

[0057] Figure 4 This is a schematic block diagram illustrating one embodiment of a system 400 for relay communication. System 400 includes UE1 402 (e.g., a TX-remote UE, a first UE, or one or more transmitting (“TX”) UEs), UE2 404 (e.g., a relay UE, a second UE), and UE3 406 (e.g., an RX-remote UE, a third UE, or one or more receiving (“RX”) UEs). UE1 402 communicates with UE2 404 via a first interface 408, while UE2 404 communicates with UE3 406 via a second interface 410.

[0058] UE1 402 is a UE with some application data to be transmitted via a relay (UE2 404) to another remote UE (UE3 406). It should be noted that UE3 406 may also have data to be transmitted to UE1 402 via UE2 404 (in this context, UE3 406 will act as the transmitter UE). Therefore, Figure 4 The terms and roles shown may be related to specific data packets. In some embodiments, more than one relay (e.g., UE2a and UE2b) is used, so UE2 404 may be a generalized representation of one or more relay UEs. In various embodiments, UE3 406 may act as a relay UE for another UE (e.g., UE4).

[0059] In a first embodiment, the UE may determine a minimum communication range (“MCR”) and / or there may be a hybrid automatic repeat request (“HARQ”) configuration including MCR and / or non-reflection. In the first embodiment, the TX remote UE maintains a unicast, multicast, and / or broadcast connection with the relay UE in a first interface, and the relay UE maintains a unicast, multicast, or broadcast connection with either the RX remote UE in a second interface.

[0060] In the first embodiment, the relay UE may use the MCR value, playback type and / or current area identifier (“ID”) (e.g., the area ID of the TX remote UE) received from the TX remote UE via the first interface to seek HARQ feedback option-1 from the RX remote UE for TB transmission to some destination ID in the second interface.

[0061] In one implementation of the first embodiment (e.g., with the same HARQ configuration for the first and second interfaces, reflection), the sidelink HARQ configuration describes the use of sidelink HARQ feedback enable and / or disable indications, sidelink HARQ feedback options, MCR values, playback types, group sizes, etc., which can be configured to reflect between the first and second interfaces to maintain end-to-end quality of service (“QoS”). This may mean that the same sidelink HARQ configuration is applied to the first and second interfaces as well as to the same set of destinations.

[0062] In another implementation of the first embodiment, the TX remote UE semi-statically transmits the MCR value, the current area ID of the TX remote UE, the playback type to be used in the second interface, the group size and / or group membership configuration using PC5 radio resource control (“RRC”) signaling for transmission in the first interface corresponding to the logical channel ID and the specific destination layer 2 (“L2”) ID, which can be used by the relay UE in the second interface to communicate with the corresponding RX remote UE.

[0063] In some embodiments, if the TX remote UE can multiplex data belonging to multiple logical channels within the same TB, the TX remote UE can separately signal the MCR value, playback type, group size, and group membership configuration for each logical channel in the Packet Data Convergence Protocol (“PDCP”) header or MAC subheader, and the MAC subheader can contain the current region (e.g., the region ID of the TX remote UE). The region ID of the TX remote UE can be updated periodically or based on changes in the region ID of the TX remote UE.

[0064] In some embodiments, the TX remote UE dynamically signals the MCR value, its current region ID (e.g., the region ID of the TX remote UE), and another playback type field in the SCI that can be set to unicast for use in the first interface and describes the playback type that can be set to multicast for use in the second interface, in Side Link Control Information (“SCI”) format 2-B or any new second SCI format. For the first interface, for unicast in SCI format 2-B or any new second SCI format, the MCR value can be set to infinity.

[0065] In various embodiments, the relay UE can signal the MCR value received from the TX remote UE and the area ID of the TX remote UE in the first interface to the RX remote UE belonging to certain destination IDs and logical channels (“LCH”) in the second interface, such as... Figure 5 As shown in the example. In one example, if the MCR value sent by signaling in the first interface is set to infinity, then the MCR value in the second interface is also set to infinity (e.g., seeking non-distance-based sidelink HARQ feedback).

[0066] In another example, if the MCR value signaled in the first interface is set to 300 meters, the relay UE can signal the same MCR value of 300 meters in the second interface to seek distance-based sidelink HARQ feedback.

[0067] Figure 5 This is a schematic block diagram illustrating one embodiment of a system 500 in which a TX remote UE senses the MCR. Limitations of the MCR 502 are illustrated by circles. The system 500 includes a TX remote UE 504, a relay UE 506, and RX remote UEs 508, 510, and 512. As illustrated, from the perspective of the TX remote UE 504, all other devices are within the MCR 502.

[0068] In some embodiments, the relay UE can determine to transmit the TB based on the MCR and the area ID. In such an embodiment, after receiving the MCR value and current area ID of the TX remote UE for the destination ID and each of the logical channels from the first interface, the relay UE can determine to transmit the TB to the RX remote UE in the second interface based on a comparison of the relay UE's current area ID with the MCR and the area ID of the TX remote UE for that TB. In one example, the transmission of the TB through the relay UE in the second interface is performed using geographic information, such as the area ID signaled in the first interface via a first sidelink device.

[0069] In some embodiments, if the current area ID of the relay UE is not within the signaled MCR value and regarding the area ID of the TX remote UE, the relay UE can perform one of the following actions: 1) The relay UE can disable sidelink HARQ feedback in the second interface, even if the relay UE's LCH is configured to seek sidelink HARQ feedback; 2) If configured to seek sidelink HARQ feedback, the relay UE can seek sidelink HARQ feedback in the second interface based on the relay UE's LCH; and 3) The relay UE does not transmit TB in the second interface. The relay UE can signal to the TX remote UE in the first interface that it is not transmitting TB in the second interface. In one example, the relay UE can use PC5RRC or a MAC control element (“CE”) via higher-layer signaling to signal to the TX remote UE in the first interface that it is not within the communication range specified by the TX remote UE. This feedback can be transmitted once the relay UE decodes the MCR value and area ID from the TX remote UE in the first interface.

[0070] In various embodiments, MCR-based TX remote UE relay selection may exist. In some embodiments, the TX remote UE may be configured with a set of MCR values ​​or an MCR threshold as part of the relay selection, and the TX remote UE may enable the use_relay field in the SCI only when the MCR provided to the TX remote UE by its higher layer matches or exceeds the configured MCR threshold.

[0071] Some embodiments can be considered non-reflective, where the relay UE determines the sidelink HARQ for the second interface. In such embodiments, the relay UE can determine to independently seek sidelink HARQ feedback based on its own LCH configuration, and the relay UE can ignore the sidelink HARQ feedback configuration provided by the TX remote UE in the first interface to set the sidelink HARQ configuration in the second interface.

[0072] In one example, the relay UE can set the sidelink HARQ feedback enable and / or disable indicator, as well as sidelink HARQ feedback option-1 or sidelink HARQ feedback option-2 (e.g., distance-based or non-distance-based) based on the availability and group size of the physical sidelink feedback channel (“PSFCH”) resources at the relay UE.

[0073] Some embodiments can be considered non-reflective, wherein the relay UE's region ID is signaled in the second interface. In such embodiments, the relay UE can signal its current region ID and the corresponding MCR value received from the TX remote UE in the first interface to the RX remote UE belonging to a certain destination ID and LCH. In one example, if there is no region ID signaled from the TX remote UE in the first interface, the relay UE can determine to signal its current region ID. In another example, the relay UE can ignore the TX remote UE's region ID signaled in the first interface and can independently choose to signal its region ID in the second interface.

[0074] Various embodiments may use the region ID of the TX remote UE and a modified MCR value signaled in the second interface. In such an embodiment, the relay UE may signal the current region ID of the TX remote UE in the second interface and determine the MCR value to be signaled in the second interface based on one of the following: 1) the relay UE adjusts the MCR signaled from the TX remote UE by "x" meters based on the location of the TX remote UE and the relay UE, which is similarly interpreted for many UEs within the MCR as perceived by the TX remote UE and the relay UE – subtracting or adding "x" meters based on the sidelink path loss calculated between the TX remote UE and the relay UE; as in Figure 6 As shown in the diagram; and 2) if the relay UE receives data from more than one TX remote UE and also receives data originating from the relay UE to the RX remote UE toward the same destination ID in the second interface, the relay UE may form a TB that multiplexes data from more than one TX remote UE to the same destination ID and may optionally use the highest MCR for transmitting this TB to the remote UE in the second interface.

[0075] In some embodiments, the relay UE can signal the region ID of the remote UE in the second interface and determine the MCR value to be signaled in the second interface according to one of the embodiments described herein.

[0076] Figure 6This is a schematic block diagram illustrating one embodiment of a system 600 in which the relay UE senses the MCR. The initial constraints of the MCR 602 are illustrated by circles. The system 600 includes a relay UE 604 and a TX remote UE 606 within the MCR. Furthermore, a modified MCR 608 shows RX remote UEs 610, 612, and 614 within the modified MCR 608. Path loss 616 between the relay UE 604 and the TX remote UE 606, and the TX power 618 of the relay UE 604 are illustrated.

[0077] Some embodiments may use area IDs transmitted to a relay UE from multiple TX remote UEs. In such embodiments, if the relay UE receives area IDs from multiple TX remote UEs in a first interface, the use of the area IDs and / or the multiplexing of data from LCHs belonging to multiple TX remote UEs to the same destination in a second interface depends on one of the following: 1) If the relay UE receives the same area ID from multiple TX remote UEs in the first interface, the relay UE may use the same area ID as received in the first interface to seek HARQ feedback in the second interface and / or may multiplex data from LCHs belonging to multiple TX remote UEs to the same destination in the second interface; 2) If the relay UE receives different area IDs from multiple TX remote UEs in the first interface, the relay UE does not signal the area IDs and / or the highest MCR in the second interface to seek HARQ feedback and does not multiplex data from LCHs belonging to multiple TX remote UEs to the same destination in the second interface. The data is multiplexed to the same destination; 3) If the relay UE receives different area IDs from multiple TX remote UEs in the first interface, the relay UE may independently decide to seek HARQ feedback by using the relay UE's area ID and / or the highest MCR in the second interface and / or may multiplex data from LCHs belonging to multiple TX remote UEs for the same destination in the second interface; 4) If the relay UE receives different area IDs from multiple TX remote UEs in the first interface, the relay UE may disable HARQ feedback in the second interface; and 5) If the relay UE receives different area IDs from multiple TX remote UEs in the first interface, the relay UE may use the average area value, the intermediate area value, and / or the area ID belonging to the TX remote UE that is at a greater distance from the relay UE, and / or the area ID belonging to the larger area configuration if there is more than one configured area configuration.

[0078] In various embodiments, the region ID of the RX remote UE can be signaled back to the TX remote UE using higher-layer signaling such as MAC CE or using SCI (e.g., it can be periodically transmitted or requested from the peer UE). In some embodiments, the TX remote UE can use the signaled region value to calculate the distance between itself and the RX remote UE, and can decide to enable sidelink HARQ in the second interface if it is higher than a configured value.

[0079] The second embodiment can correspond to TX power control. In the second embodiment, the relay UE can signal the current area ID of the TX remote UE in the second interface and the MCR value signaled in the first interface. The number of UEs interpreted by the relay UE as being within the MCR can be different from that of the TX remote UE and can depend on the distance between the TX remote UE and the relay UE.

[0080] In some embodiments, if the distance between the TX remote UE and the relay UE is within a configured threshold of "x" meters, an interpretation of the number of UEs within the MCR can be the same as that perceived from the TX remote UE and the relay UE. In one example, "x" meters can be equal to or less than the size of the area configured in the gNB. In another example, if the estimated sidelink path loss between the TX remote UE and the relay UE is within a configured threshold, there may be no additional behavior for the relay UE, where the threshold is configured such that it is less than the size of the area configured in the corresponding gNB.

[0081] In some embodiments, the transmit power of the relay UE in the second interface for transmission toward the RX remote UE can be increased and can be based on the sidelink path loss measured in the first interface between the TX remote UE and the relay UE.

[0082] Various embodiments can be reflective and / or non-reflective and can use P0 and alpha for the interface. In such embodiments, the configuration of P0 and alpha values ​​can be similarly configured between the first and second interfaces, and the transmit power of the relay UE to be used in the second interface can depend on the sidelink path loss of the TX remote UE and the relay UE. In one example, P0 and alpha values ​​can be exchanged using PC5 RRC signaling. In some embodiments, P0 and alpha values ​​can be configured independently in the first and second interfaces.

[0083] In the third embodiment, UE-to-UE relay can be used, where each interface uses a different radio access technology (“RAT”). In the third embodiment, a first RAT can be configured for use by the relay UE on a first interface and a second RAT can be configured for use on a second interface. The relay UE can support both RAT configurations that enable communication between TX remote UEs and RX remote UEs, and the mapping between the QoS of one RAT and the other RAT can be signaled to the relay UE by the gNB, and can be configured or pre-configured.

[0084] In some embodiments, the relay UE can independently determine the sidelink HARQ configuration for the second interface based on its own LCH configuration and the provided QoS mapping information.

[0085] In some embodiments, the first RAT and the second RAT in the various embodiments described herein may be frequency range 1 (“FR1”) (e.g., below 6 GHz) and frequency range 2 (“FR2”) and / or frequency range 4 (“FR4”) (e.g., above 6 GHz and / or above 52.6 GHz).

[0086] In the fourth embodiment, in Mode 2 autonomous resource allocation, the TX remote UE can use a PC5 RRC connection in the second interface to signal information to the relay UE involving parameters such as the PC5 5G QoS identifier (“PQI”), periodicity of packet arrival, latency, packet delay budget (“PDB”), packet size, and buffer status report, along with their respective source IDs and destination IDs, candidate resource selection windows containing start and end sidelink slots, or the ratio of PDBs to be used to select resources in each interface (or the PDBs used in each interface otherwise). The relay UE can trigger a resource selection and / or reselection mechanism once it receives auxiliary information from the TX remote UE in the first interface, and perform candidate resource selection taking into account the remaining PDBs (e.g., after the PDBs and / or candidate resource selection windows used by the TX remote UE in the first interface). The relay UE can pre-select and / or reserve resources within the candidate resource selection window to be used in the second interface, wherein the candidate resource window to be used in the second interface takes into account the PDBs to be used in the first interface and the PDBs to be used in the second interface.

[0087] Figure 7This is a schematic block diagram illustrating one embodiment of a system 700 including selection windows for a TX remote UE 702 and a relay UE 704. For the TX remote UE 702, a first candidate 706 and a second candidate 708 are within a candidate resource selection window 710, while for the relay UE 704, a first candidate 712 and a second candidate 714 are within a candidate resource selection window 716. The second candidate 708 of the TX remote UE 702 corresponds to the first candidate 712 of the relay UE 704.

[0088] In a fifth embodiment, a sidelink discontinuous reception (“DRX”) cycle configuration to be used on the first interface can be exchanged and / or negotiated between the TX remote UE and the relay UE. In one option, the sidelink DRX cycle can be negotiated by the relay UE on the first interface based on a sidelink DRX cycle configuration used on the second interface or based on a DRX cycle configuration of another TX remote UE on the first interface. The DRX cycle configuration may include the relay UE’s on-time duration, offset, and periodicity that can be signaled by both the TX remote UE and the RX remote UE.

[0089] In one example, a relay UE can perform data reception from a TX remote UE on a first interface and data transmission to a remote UE on a second interface using the same DRX enable duration and / or active receive period, or receive data during the first enable duration and transmit data during the second enable duration of the DRX configuration period. The inactivity timer for the TX remote UE can be started and / or restarted based on feedback from the first and second interfaces.

[0090] Figure 8 This is a flowchart illustrating one embodiment of a method 800 for configuring a sidelink hybrid automatic repeat request. In some embodiments, method 800 is executed by a device, such as remote unit 102. In some embodiments, method 800 may be executed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0091] In various embodiments, method 800 includes communicating with a second sidelink device via a first sidelink device using a first sidelink communication interface 802. The second sidelink device communicates with a third sidelink device using a second sidelink communication interface. In some embodiments, method 800 includes transmitting a sidelink hybrid auto-repeat request configuration 804 to the second sidelink device via the first sidelink communication interface. In some embodiments, the sidelink hybrid auto-repeat request configuration includes a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, a playback type, a group size, a reflection indicator, a non-reflection indicator, or some combinations thereof 806.

[0092] In some embodiments, the sidelink hybrid automatic repeat request configuration includes the playback type and minimum communication range value to be used by the second sidelink device, and this playback type and minimum communication range value are semi-statically signaled to the second sidelink device using radio resource configuration signaling transmitted through the first sidelink communication interface or using sidelink configuration information transmitted through the first sidelink communication interface. In some embodiments, the second sidelink device transmits transport blocks using the second sidelink communication interface based on the geographical area indicated in the sidelink hybrid automatic repeat request configuration.

[0093] In various embodiments, the second sidelink device multiplexes data received from multiple devices via a first sidelink communication interface based on the geographical region indicated in the sidelink hybrid auto-repeat request, and transmits the multiplexed data via the second sidelink communication interface. In one embodiment, the second sidelink device receives the same region identifier from multiple devices, transmits the multiplexed data via the second sidelink communication interface based on the same region identifier, and requests to receive hybrid auto-repeat request feedback.

[0094] In some embodiments, the second sidelink device receives different region identifiers from multiple devices and does not transmit multiplexed data based on a single region identifier. In some embodiments, the second sidelink device receives different region identifiers from multiple devices and transmits multiplexed data and requests to receive hybrid automatic repeat request feedback based on the region identifier of the second sidelink device.

[0095] In various embodiments, the second sidelink device receives different area identifiers from multiple devices and disables hybrid auto-repeat request feedback on the second sidelink communication interface. In one embodiment, a reflection indicator instructs the second sidelink device to provide the same sidelink hybrid auto-repeat request configuration to the third sidelink device.

[0096] In some embodiments, a non-reflective indicator instructs a second sidelink device to provide a second sidelink hybrid auto-repeat request configuration to a third sidelink device, and the sidelink hybrid auto-repeat request configuration differs from the second sidelink hybrid auto-repeat request configuration. In some embodiments, the sidelink hybrid auto-repeat request configuration includes a minimum communication range value, and the second sidelink device signals the same minimum communication range value to the third sidelink device. In various embodiments, the sidelink hybrid auto-repeat request configuration includes a minimum communication range value, and the second sidelink device signals a second minimum communication range value to the third sidelink device.

[0097] In one embodiment, the sidelink hybrid auto-repeat request configuration includes a region identifier, and the second sidelink device signals the region identifier to the third sidelink device. In some embodiments, the sidelink hybrid auto-repeat request configuration includes a region identifier, and the second sidelink device signals a second region identifier corresponding to the second sidelink device to the third sidelink device. In some embodiments, the second sidelink device requests a sidelink hybrid auto-repeat request response based on the logical channel configuration of the second sidelink device.

[0098] In various embodiments, the sidelink hybrid auto-repeat request configuration includes a region identifier and a minimum communication range value for a first sidelink device, and a second sidelink device determines to transmit transport blocks via a second interface based on a comparison of the second sidelink device's second region identifier, the first sidelink device's region identifier, and the minimum communication range value. In one embodiment, as a result that the second region identifier is not within the minimum communication range value for the first sidelink device's region identifier, the second sidelink device disables sidelink hybrid auto-repeat request feedback in the second interface.

[0099] In some embodiments, as a result that the second region identifier is not within the minimum communication range value of the region identifier of the first sidelink device, the second sidelink device does not transmit transport blocks in the second interface. In some embodiments, as a result that the second region identifier is not within the minimum communication range value of the region identifier of the first sidelink device, the second sidelink device enables sidelink hybrid automatic repeat request feedback in the second interface.

[0100] In various embodiments, the second sidelink device determines its transmit power in the second interface based on the sidelink path loss measured in the first interface between the first and second sidelink devices. In one embodiment, method 800 further includes enabling transmission to the second sidelink device as a result of a minimum communication range threshold that matches a minimum communication range value.

[0101] Figure 9This is a flowchart illustrating another embodiment of a method 900 for configuring a sidelink hybrid automatic repeat request. In some embodiments, method 900 is executed by a device, such as remote unit 102. In some embodiments, method 900 may be executed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0102] In various embodiments, method 900 includes 902 communicating with a first sidelink device via a second sidelink device using a first sidelink communication interface, and communicating with a third sidelink device using the second sidelink communication interface. In some embodiments, method 900 includes receiving 904 a sidelink hybrid auto-repeat request configuration from the first sidelink device via the first sidelink communication interface. In some embodiments, the sidelink hybrid auto-repeat request configuration includes 906 a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, a playback type, a group size, a reflection indicator, a non-reflection indicator, or some combination thereof.

[0103] In some embodiments, the sidelink hybrid automatic repeat request configuration includes a playback type and a minimum communication range value to be used by the second sidelink device, and this playback type and minimum communication range value are semi-statically signaled to the second sidelink device using radio resource configuration signaling transmitted through the first sidelink communication interface or using sidelink configuration information transmitted through the first sidelink communication interface. In some embodiments, method 900 further includes transmitting transport blocks using the second sidelink communication interface based on the geographical area indicated in the sidelink hybrid automatic repeat request configuration.

[0104] In various embodiments, method 900 further includes multiplexing data received from multiple devices via a first sidelink communication interface according to the geographic area indicated in the sidelink hybrid automatic repeat request, and transmitting the multiplexed data via a second sidelink communication interface. In one embodiment, method 900 further includes receiving the same area identifier from multiple devices, and transmitting the multiplexed data via the second sidelink communication interface based on the same area identifier and requesting to receive hybrid automatic repeat request feedback.

[0105] In some embodiments, method 900 further includes receiving different area identifiers from multiple devices and transmitting multiplexed data without based on the area identifiers. In some embodiments, method 900 further includes receiving different area identifiers from multiple devices, transmitting multiplexed data based on the area identifier of a second sidelink device, and requesting to receive hybrid automatic repeat request feedback. In various embodiments, method 900 further includes receiving different area identifiers from multiple devices and disabling hybrid automatic repeat request feedback on the second sidelink communication interface.

[0106] In one embodiment, a reflection indicator instructs a second sidelink device to provide the same sidelink hybrid auto-repeat request configuration to a third sidelink device. In some embodiments, a non-reflection indicator instructs a second sidelink device to provide a second sidelink hybrid auto-repeat request configuration to a third sidelink device, and this sidelink hybrid auto-repeat request configuration differs from the second sidelink hybrid auto-repeat request configuration. In some embodiments, the sidelink hybrid auto-repeat request configuration includes a minimum communication range value, and method 900 further includes signaling the same minimum communication range value to the third sidelink device.

[0107] In various embodiments, the sidelink hybrid auto-repeat request configuration includes a minimum communication range value, and the method further includes signaling a second minimum communication range value to a third sidelink device. In one embodiment, the sidelink hybrid auto-repeat request configuration includes a region identifier, and method 900 further includes signaling the region identifier to the third sidelink device. In some embodiments, the sidelink hybrid auto-repeat request configuration includes a region identifier, and method 900 further includes signaling a second region identifier corresponding to a second sidelink device to the third sidelink device.

[0108] In some embodiments, method 900 further includes requesting sidelink hybrid auto-repeat request feedback based on the logical channel configuration of the second sidelink device. In various embodiments, the sidelink hybrid auto-repeat request configuration includes a region identifier and a minimum communication range value for the first sidelink device, and the method further includes determining, based on a comparison of the second region identifier of the second sidelink device, the region identifier of the first sidelink device, and the minimum communication range value, to transmit a transport block through the second interface. In one embodiment, as a result that the second region identifier is not within the minimum communication range value for the region identifier of the first sidelink device, method 900 further includes disabling sidelink hybrid auto-repeat request feedback in the second interface.

[0109] In some embodiments, as a result that the second region identifier is not within the minimum communication range value of the region identifier with respect to the first sidelink device, method 900 further includes not transmitting transport blocks in the second interface. In some embodiments, as a result that the second region identifier is not within the minimum communication range value of the region identifier with respect to the first sidelink device, method 900 further includes enabling sidelink hybrid automatic repeat request feedback in the second interface.

[0110] In various embodiments, the method further includes determining the transmit power of the second sidelink device in a second interface based on the sidelink path loss measured in a first interface between the first and second sidelink devices. In one embodiment, transmission to the second sidelink device is enabled as a result of a minimum communication range threshold that matches a minimum communication range value.

[0111] In one embodiment, the method of the first sidelink device includes: communicating with a second sidelink device using a first sidelink communication interface, wherein the second sidelink device communicates with a third sidelink device using the second sidelink communication interface; and transmitting a sidelink hybrid auto-repeat request configuration to the second sidelink device via the first sidelink communication interface; wherein the sidelink hybrid auto-repeat request configuration includes a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, a playback type, a group size, a reflection indicator, a non-reflection indicator, or some combination thereof.

[0112] In some embodiments, the sidelink hybrid automatic repeat request configuration includes the playback type and minimum communication range value to be used by the second sidelink device, and the playback type and minimum communication range value are semi-statically signaled to the second sidelink device using radio resource configuration signaling transmitted through the first sidelink communication interface or using sidelink configuration information transmitted through the first sidelink communication interface.

[0113] In some embodiments, the second sidelink device transmits transport blocks using the second sidelink communication interface based on the geographical area indicated in the sidelink hybrid automatic repeat request configuration.

[0114] In various embodiments, the second sidelink device multiplexes data received from multiple devices via the first sidelink communication interface according to the geographical area indicated in the sidelink hybrid automatic repeat request, and transmits the multiplexed data via the second sidelink communication interface.

[0115] In one embodiment, the second sidelink device receives the same area identifier from multiple devices, transmits multiplexed data through the second sidelink communication interface based on the same area identifier, and requests to receive hybrid automatic repeat request feedback.

[0116] In some embodiments, the second side link device receives different region identifiers from multiple devices and transmits multiplexed data without relying on the region identifiers.

[0117] In some embodiments, the second sidelink device receives different area identifiers from multiple devices, and transmits multiplexed data based on the area identifier of the second sidelink device and requests to receive hybrid automatic repeat request feedback.

[0118] In various embodiments, the second sidelink device receives different area identifiers from multiple devices and disables hybrid automatic repeat request feedback on the second sidelink communication interface.

[0119] In one embodiment, the reflection indicator instructs the second sidelink device to provide the same sidelink hybrid automatic repeat request configuration to the third sidelink device.

[0120] In some embodiments, a non-reflective indicator instructs a second sidelink device to provide a second sidelink hybrid auto-repeat request configuration to a third sidelink device, and the sidelink hybrid auto-repeat request configuration differs from the second sidelink hybrid auto-repeat request configuration.

[0121] In some embodiments, the sidelink hybrid automatic repeat request configuration includes a minimum communication range value, and the second sidelink device signals the same minimum communication range value to the third sidelink device.

[0122] In various embodiments, the sidelink hybrid automatic repeat request configuration includes a minimum communication range value, and the second sidelink device signals a second minimum communication range value to the third sidelink device.

[0123] In one embodiment, the sidelink hybrid automatic repeat request configuration includes a region identifier, and the second sidelink device signals the region identifier to the third sidelink device.

[0124] In some embodiments, the sidelink hybrid automatic repeat request configuration includes a region identifier, and the second sidelink device signals a second region identifier corresponding to the second sidelink device to the third sidelink device.

[0125] In some embodiments, the second sidelink device requests a sidelink hybrid automatic repeat request feedback based on the logical channel configuration of the second sidelink device.

[0126] In various embodiments, the sidelink hybrid automatic repeat request configuration includes a region identifier and a minimum communication range value for a first sidelink device, and a second sidelink device determines to transmit transport blocks via a second interface based on a comparison of a second region identifier of the second sidelink device, a region identifier of the first sidelink device, and the minimum communication range value.

[0127] In one embodiment, as a result that the second region identifier is not within the minimum communication range value of the region identifier of the first sidelink device, the second sidelink device disables sidelink hybrid auto-repeating request feedback in the second interface.

[0128] In some embodiments, as a result that the second region identifier is not within the minimum communication range value of the region identifier of the first sidelink device, the second sidelink device does not transmit transport blocks in the second interface.

[0129] In some embodiments, as a result that the second region identifier is not within the minimum communication range value of the region identifier of the first sidelink device, the second sidelink device enables sidelink hybrid automatic repeat request feedback in the second interface.

[0130] In various embodiments, the second sidelink device determines the transmit power of the second sidelink device in the second interface based on the sidelink path loss measured in the first interface between the first sidelink device and the second sidelink device.

[0131] In one embodiment, the method further includes enabling transmission to a second sidelink device as a result of a minimum communication range threshold that matches the minimum communication range value.

[0132] In one embodiment, an apparatus includes a first sidelink device. The apparatus further includes a transceiver that: communicates with a second sidelink device using a first sidelink communication interface, wherein the second sidelink device communicates with a third sidelink device using the same interface; and transmits a sidelink hybrid auto-repeat request configuration to the second sidelink device via the first sidelink communication interface; wherein the sidelink hybrid auto-repeat request configuration includes a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, a playback type, a group size, a reflection indicator, a non-reflection indicator, or some combinations thereof.

[0133] In some embodiments, the sidelink hybrid automatic repeat request configuration includes the playback type and minimum communication range value to be used by the second sidelink device, and the playback type and minimum communication range value are semi-statically signaled to the second sidelink device using radio resource configuration signaling transmitted through the first sidelink communication interface or using sidelink configuration information transmitted through the first sidelink communication interface.

[0134] In some embodiments, the second sidelink device transmits transport blocks using the second sidelink communication interface based on the geographical area indicated in the sidelink hybrid automatic repeat request configuration.

[0135] In various embodiments, the second sidelink device multiplexes data received from multiple devices via the first sidelink communication interface according to the geographical area indicated in the sidelink hybrid automatic repeat request, and transmits the multiplexed data via the second sidelink communication interface.

[0136] In one embodiment, the second sidelink device receives the same area identifier from multiple devices, transmits multiplexed data through the second sidelink communication interface based on the same area identifier, and requests to receive hybrid automatic repeat request feedback.

[0137] In some embodiments, the second side link device receives different region identifiers from multiple devices and transmits multiplexed data without relying on the region identifiers.

[0138] In some embodiments, the second sidelink device receives different area identifiers from multiple devices, and transmits multiplexed data based on the area identifier of the second sidelink device and requests to receive hybrid automatic repeat request feedback.

[0139] In various embodiments, the second sidelink device receives different area identifiers from multiple devices and disables hybrid automatic repeat request feedback on the second sidelink communication interface.

[0140] In one embodiment, the reflection indicator instructs the second sidelink device to provide the same sidelink hybrid automatic repeat request configuration to the third sidelink device.

[0141] In some embodiments, a non-reflective indicator instructs a second sidelink device to provide a second sidelink hybrid auto-repeat request configuration to a third sidelink device, and the sidelink hybrid auto-repeat request configuration differs from the second sidelink hybrid auto-repeat request configuration.

[0142] In some embodiments, the sidelink hybrid automatic repeat request configuration includes a minimum communication range value, and the second sidelink device signals the same minimum communication range value to the third sidelink device.

[0143] In various embodiments, the sidelink hybrid automatic repeat request configuration includes a minimum communication range value, and the second sidelink device signals a second minimum communication range value to the third sidelink device.

[0144] In one embodiment, the sidelink hybrid automatic repeat request configuration includes a region identifier, and the second sidelink device signals the region identifier to the third sidelink device.

[0145] In some embodiments, the sidelink hybrid automatic repeat request configuration includes a region identifier, and the second sidelink device signals a second region identifier corresponding to the second sidelink device to the third sidelink device.

[0146] In some embodiments, the second sidelink device requests a sidelink hybrid automatic repeat request feedback based on the logical channel configuration of the second sidelink device.

[0147] In various embodiments, the sidelink hybrid automatic repeat request configuration includes a region identifier and a minimum communication range value for a first sidelink device, and a second sidelink device determines to transmit transport blocks via a second interface based on a comparison of a second region identifier of the second sidelink device, a region identifier of the first sidelink device, and the minimum communication range value.

[0148] In one embodiment, as a result that the second region identifier is not within the minimum communication range value of the region identifier of the first sidelink device, the second sidelink device disables sidelink hybrid auto-repeating request feedback in the second interface.

[0149] In some embodiments, as a result that the second region identifier is not within the minimum communication range value of the region identifier of the first sidelink device, the second sidelink device does not transmit transport blocks in the second interface.

[0150] In some embodiments, as a result that the second region identifier is not within the minimum communication range value of the region identifier of the first sidelink device, the second sidelink device enables sidelink hybrid automatic repeat request feedback in the second interface.

[0151] In various embodiments, the second sidelink device determines the transmit power of the second sidelink device in the second interface based on the sidelink path loss measured in the first interface between the first sidelink device and the second sidelink device.

[0152] In one embodiment, the device further includes a processor that enables transmission to a second sidelink device as a result of a minimum communication range threshold that matches a minimum communication range value.

[0153] In one embodiment, a method of a second sidelink device includes: communicating with a first sidelink device using a first sidelink communication interface, and communicating with a third sidelink device using a second sidelink communication interface; and receiving a sidelink hybrid auto-repeat request configuration from the first sidelink device via the first sidelink communication interface; wherein the sidelink hybrid auto-repeat request configuration includes a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, a playback type, a group size, a reflection indicator, a non-reflection indicator, or some combination thereof.

[0154] In some embodiments, the sidelink hybrid automatic repeat request configuration includes the playback type and minimum communication range value to be used by the second sidelink device, and the playback type and minimum communication range value are semi-statically signaled to the second sidelink device using radio resource configuration signaling transmitted through the first sidelink communication interface or using sidelink configuration information transmitted through the first sidelink communication interface.

[0155] In some embodiments, the method further includes transmitting transport blocks using a second sidelink communication interface based on a geographic region indicated in a sidelink hybrid automatic repeat request configuration.

[0156] In various embodiments, the method further includes multiplexing data received from multiple devices via a first sidelink communication interface according to the geographic area indicated in the sidelink hybrid automatic repeat request, and transmitting the multiplexed data via a second sidelink communication interface.

[0157] In one embodiment, the method further includes receiving the same area identifier from multiple devices, transmitting multiplexed data through a second sidelink communication interface based on the same area identifier, and requesting to receive a hybrid automatic repeat request feedback.

[0158] In some embodiments, the method further includes receiving different region identifiers from multiple devices and transmitting multiplexed data not based on the region identifiers.

[0159] In some embodiments, the method further includes receiving different area identifiers from multiple devices, transmitting multiplexed data based on the area identifier of the second sidelink device, and requesting to receive a hybrid automatic repeat request feedback.

[0160] In various embodiments, the method further includes receiving different area identifiers from multiple devices and disabling hybrid automatic repeat request feedback on a second-side link communication interface.

[0161] In one embodiment, the reflection indicator instructs the second sidelink device to provide the same sidelink hybrid automatic repeat request configuration to the third sidelink device.

[0162] In some embodiments, a non-reflective indicator instructs a second sidelink device to provide a second sidelink hybrid auto-repeat request configuration to a third sidelink device, and the sidelink hybrid auto-repeat request configuration differs from the second sidelink hybrid auto-repeat request configuration.

[0163] In some embodiments, the sidelink hybrid automatic repeat request configuration includes a minimum communication range value, and the method further includes signaling the same minimum communication range value to a third sidelink device.

[0164] In various embodiments, the sidelink hybrid automatic repeat request configuration includes a minimum communication range value, and the method further includes signaling a second minimum communication range value to a third sidelink device.

[0165] In one embodiment, the sidelink hybrid automatic repeat request configuration includes a region identifier, and the method further includes signaling the region identifier to a third sidelink device.

[0166] In some embodiments, the sidelink hybrid automatic repeat request configuration includes a region identifier, and the method further includes signaling a second region identifier corresponding to the second sidelink device to a third sidelink device.

[0167] In some embodiments, the method further includes a logical channel configuration request for sidelink hybrid automatic repeat request feedback based on the second sidelink device.

[0168] In various embodiments, the sidelink hybrid automatic repeat request configuration includes a region identifier of a first sidelink device and a minimum communication range value, and the method further includes determining to transmit a transport block via a second interface based on a comparison of a second region identifier of a second sidelink device, a region identifier of the first sidelink device, and the minimum communication range value.

[0169] In one embodiment, as a result that the second region identifier is not within the minimum communication range value of the region identifier of the first sidelink device, the method further includes disabling sidelink hybrid auto-repeating request feedback in the second interface.

[0170] In some embodiments, as a result that the second region identifier is not within the minimum communication range value of the region identifier of the first side link device, the method further includes not transmitting transport blocks in the second interface.

[0171] In some embodiments, as a result that the second region identifier is not within the minimum communication range value of the region identifier of the first sidelink device, the method further includes enabling sidelink hybrid automatic repeat request feedback in the second interface.

[0172] In various embodiments, the method further includes determining the transmit power of the second sidelink device in the second interface based on the sidelink path loss measured in the first interface between the first sidelink device and the second sidelink device.

[0173] In one embodiment, enabling transmission to the second-side link device is the result of a minimum communication range threshold that matches the minimum communication range value.

[0174] In one embodiment, an apparatus includes a second sidelink device. The apparatus further includes a transceiver that: communicates with a first sidelink device using a first sidelink communication interface and with a third sidelink device using a second sidelink communication interface; and receives a sidelink hybrid auto-repeat request configuration from the first sidelink device via the first sidelink communication interface; wherein the sidelink hybrid auto-repeat request configuration includes a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, a playback type, a group size, a reflection indicator, a non-reflection indicator, or some combination thereof.

[0175] In some embodiments, the sidelink hybrid automatic repeat request configuration includes the playback type and minimum communication range value to be used by the second sidelink device, and the playback type and minimum communication range value are semi-statically signaled to the second sidelink device using radio resource configuration signaling transmitted through the first sidelink communication interface or using sidelink configuration information transmitted through the first sidelink communication interface.

[0176] In some embodiments, the transceiver transmits transport blocks using a second sidelink communication interface based on the geographic region indicated in the sidelink hybrid auto-repeat request configuration.

[0177] In various embodiments, the device further includes a processor that multiplexes data received from multiple devices via a first sidelink communication interface according to a geographic area indicated in a sidelink hybrid automatic repeat request, and wherein the transceiver transmits the multiplexed data via a second sidelink communication interface.

[0178] In one embodiment, the transceiver receives the same area identifier from multiple devices, and the transceiver transmits multiplexed data through a second sidelink communication interface based on the same area identifier and requests to receive Hybrid Automatic Repeat Request Feedback.

[0179] In some embodiments, the transceiver receives different region identifiers from multiple devices, and the transceiver does not transmit multiplexed data based on the region identifiers.

[0180] In some embodiments, the transceiver receives different area identifiers from multiple devices, and the transceiver transmits multiplexed data based on the area identifier of the second sidelink device and requests to receive Hybrid Automatic Repeat Request Feedback.

[0181] In various embodiments, the device further includes a processor, wherein the transceiver receives different area identifiers from multiple devices, and the processor disables hybrid automatic repeat request feedback on a second-side link communication interface.

[0182] In one embodiment, the reflection indicator instructs the second sidelink device to provide the same sidelink hybrid automatic repeat request configuration to the third sidelink device.

[0183] In some embodiments, a non-reflective indicator instructs a second sidelink device to provide a second sidelink hybrid auto-repeat request configuration to a third sidelink device, and the sidelink hybrid auto-repeat request configuration differs from the second sidelink hybrid auto-repeat request configuration.

[0184] In some embodiments, the sidelink hybrid automatic repeat request configuration includes a minimum communication range value, and the method further includes signaling the same minimum communication range value to a third sidelink device.

[0185] In various embodiments, the sidelink hybrid automatic repeat request configuration includes a minimum communication range value, and the method further includes signaling a second minimum communication range value to a third sidelink device.

[0186] In one embodiment, the sidelink hybrid automatic repeat request configuration includes a region identifier, and the method further includes signaling the region identifier to a third sidelink device.

[0187] In some embodiments, the sidelink hybrid automatic repeat request configuration includes a region identifier, and the method further includes signaling a second region identifier corresponding to the second sidelink device to a third sidelink device.

[0188] In some embodiments, the method further includes a processor that requests sidelink hybrid automatic repeat request feedback based on the logical channel configuration of the second sidelink device.

[0189] In various embodiments, the device further includes a processor, wherein the sidelink hybrid automatic repeat request configuration includes a region identifier and a minimum communication range value for a first sidelink device, and the processor determines to transmit a transport block via a second interface based on a comparison of a second region identifier of a second sidelink device, a region identifier of the first sidelink device, and the minimum communication range value.

[0190] In one embodiment, as a result that the second region identifier is not within the minimum communication range value of the region identifier of the first sidelink device, the processor disables sidelink hybrid auto-repeating request feedback in the second interface.

[0191] In some embodiments, as a result that the second area identifier is not within the minimum communication range value of the area identifier of the first side link device, the transceiver does not transmit transport blocks in the second interface.

[0192] In some embodiments, as a result that the second region identifier is not within the minimum communication range value of the region identifier of the first sidelink device, the processor enables sidelink hybrid automatic repeat request feedback in the second interface.

[0193] In various embodiments, the device further includes a processor that determines the transmit power of the second sidelink device in the second interface based on the sidelink path loss measured in the first interface between the first sidelink device and the second sidelink device.

[0194] In one embodiment, enabling transmission to the second-side link device is the result of a minimum communication range threshold that matches the minimum communication range value.

[0195] Other specific embodiments may be practiced. The described embodiments should be considered in all respects as illustrative rather than restrictive. Therefore, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All variations falling within the meaning and equivalents of the claims should be included within their scope.

Claims

1. A method for a first-side link device, the method comprising: The first side link communication interface is used to communicate with the second side link device, wherein the second side link device uses the second side link communication interface to communicate with the third side link device; as well as Send a sidelink hybrid automatic repeat request configuration to the second sidelink device via the first sidelink communication interface; The sidelink hybrid auto-repeat request configuration includes a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, playback type, group size, reflection indicator, non-reflection indicator, or some combinations thereof. The sidelink hybrid automatic repeat request configuration includes a region identifier, and the second sidelink device sends the region identifier to the third sidelink device via a signal.

2. An apparatus including a first side link device, the apparatus further comprising: Transceiver, the transceiver: The first side link communication interface is used to communicate with the second side link device, wherein the second side link device uses the second side link communication interface to communicate with the third side link device; and Send a sidelink hybrid automatic repeat request configuration to the second sidelink device via the first sidelink communication interface; The sidelink hybrid auto-repeat request configuration includes a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, playback type, group size, reflection indicator, non-reflection indicator, or some combinations thereof. The sidelink hybrid automatic repeat request configuration includes a region identifier, and the second sidelink device sends the region identifier to the third sidelink device via a signal.

3. The apparatus according to claim 2, wherein, The sidelink hybrid automatic repeat request configuration includes the playback type and minimum communication range value to be used by the second sidelink device, and the playback type and minimum communication range value are semi-statically transmitted to the second sidelink device using radio resource configuration signaling transmitted through the first sidelink communication interface or using sidelink configuration information transmitted through the first sidelink communication interface.

4. The apparatus according to claim 2, wherein, The second sidelink device transmits transport blocks using the second sidelink communication interface based on the geographical area indicated in the sidelink hybrid automatic repeat request configuration.

5. The apparatus according to claim 2, wherein, The second sidelink device multiplexes data received from multiple devices through the first sidelink communication interface according to the geographical area indicated in the sidelink hybrid automatic repeat request, and transmits the multiplexed data through the second sidelink communication interface.

6. The apparatus according to claim 5, wherein, The second sidelink device receives the same area identifier from the plurality of devices, and transmits the multiplexed data through the second sidelink communication interface based on the same area identifier and requests to receive Hybrid Automatic Repeat Request Feedback.

7. The apparatus according to claim 5, wherein, The second side link device receives different region identifiers from the plurality of devices and transmits the multiplexed data without relying on the region identifiers.

8. The apparatus according to claim 5, wherein, The second side link device receives different area identifiers from the plurality of devices, and transmits the multiplexed data based on the area identifier of the second side link device and requests to receive Hybrid Automatic Repeat Request Feedback.

9. The apparatus according to claim 5, wherein, The second sidelink device receives different area identifiers from multiple devices and disables hybrid automatic repeat request feedback on the second sidelink communication interface.

10. The apparatus according to claim 2, wherein, The reflection indicator instructs the second sidelink device to provide the same sidelink hybrid automatic repeat request configuration to the third sidelink device.

11. The apparatus according to claim 2, wherein, The non-reflection indicator indicates to the second sidelink device to provide the third sidelink device with a second sidelink hybrid auto-repeat request configuration, and the sidelink hybrid auto-repeat request configuration is different from the second sidelink hybrid auto-repeat request configuration.

12. The apparatus according to claim 2, wherein, The sidelink hybrid automatic repeat request configuration includes the minimum communication range value, and the second sidelink device signals the same minimum communication range value to the third sidelink device.

13. The apparatus according to claim 2, wherein, The sidelink hybrid automatic repeat request configuration includes the minimum communication range value, and the second sidelink device signals the second minimum communication range value to the third sidelink device.

14. An apparatus including a second side link device, the apparatus further comprising: Transceiver, the transceiver: Use the first side link communication interface to communicate with the first side link device, and use the second side link communication interface to communicate with the third side link device; and Receive sidelink hybrid automatic repeat request configuration from the first sidelink device via the first sidelink communication interface; The sidelink hybrid auto-repeat request configuration includes a sidelink hybrid auto-repeat request feedback enable indicator, a sidelink hybrid auto-repeat request feedback disable indicator, a sidelink hybrid auto-repeat request feedback option, a minimum communication range value, playback type, group size, reflection indicator, non-reflection indicator, or some combinations thereof. The sidelink hybrid automatic repeat request configuration includes a region identifier, and the second sidelink device sends the region identifier to the third sidelink device via a signal.

15. The apparatus according to claim 14, wherein, The sidelink hybrid automatic repeat request configuration includes the playback type and minimum communication range value to be used by the second sidelink device, and the playback type and minimum communication range value are semi-statically transmitted to the second sidelink device using radio resource configuration signaling transmitted through the first sidelink communication interface or using sidelink configuration information transmitted through the first sidelink communication interface.

16. The apparatus according to claim 14, wherein, The transceiver transmits transport blocks using the second sidelink communication interface based on the geographical region indicated in the sidelink hybrid automatic repeat request configuration.

17. The apparatus of claim 14, further comprising a processor that multiplexes data received from a plurality of devices via the first sidelink communication interface according to a geographical region indicated in the sidelink hybrid automatic repeat request, and wherein, The multiplexed data is transmitted through the second side link communication interface.

18. The apparatus according to claim 17, wherein, The transceiver receives the same area identifier from the plurality of devices, and the transceiver transmits the multiplexed data through the second sidelink communication interface based on the same area identifier and requests to receive Hybrid Automatic Repeat Request Feedback.

19. The apparatus according to claim 17, wherein, The transceiver receives different region identifiers from the plurality of devices, and the transceiver does not transmit the multiplexed data based on the region identifiers.

Images