Multiple transmission negative acknowledgement indication in physical sidelink feedback channel

Abstract

Techniques related to performing wireless sidelink communication are disclosed. An originating (e.g., transmitting) device and a target (e.g., receiving) device can operate in a NACK-only mode. In this mode, the target device only provides NACK feedback for transmissions it has not received. The lack of NACK feedback is interpreted by the originating device as a successful reception of the transmission. However, the target device may not be able to transmit NACK for every lost transmission. In NACK-only mode, the originator will not retransmit these lost transmissions. To address this issue, the target device can transmit multi-transmission NACK feedback to indicate multiple unsuccessfully received transmissions. Multi-transmission NACK is a single feedback, and therefore allows a target device with limited feedback capabilities to indicate NACK for multiple transmissions.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims the benefit of U.S. non-provisional application No. 16 / 940,540, filed July 28, 2020, entitled “MULTI-TRANSMISSION NEGATIVEACKNOWLEDGEMENT INDICATION IN PHYSICAL SIDELINK FEEDBACK CHANNEL,” which has been assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The various aspects described herein generally relate to wireless communication systems, and in particular to multiple negative acknowledgments (NACK) indications in the Physical Side Link Feedback Channel (PSFCH).

[0004] background

[0005] Wireless communication systems have undergone several generations of development, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data radio service with Internet capabilities, and fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog Advanced Mobile Phone Systems (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), and GSM TDMA variants.

[0006] The fifth-generation (5G) mobile standard demands higher data transmission speeds, a greater number of connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance (NGC), the 5G standard (also known as "New Radio" (NR)) is designed to provide tens of megabits per second (Mbps) of data rate to each of tens of thousands of users, and 1 gigabits per second (Gbps) to dozens of employees on an office floor. It should support hundreds of thousands of simultaneous connections to support large-scale sensor deployments. Therefore, 5G mobile communication should have significantly improved spectral efficiency compared to the current 4G standard. Furthermore, signaling efficiency should be improved and latency significantly reduced compared to the current standard.

[0007] Overview

[0008] The following is a simplified overview relating to one or more aspects and / or embodiments disclosed herein. Thus, this overview should not be considered an exhaustive overview relating to all contemplated aspects and / or embodiments, nor should it be considered to identify key or decisive elements relating to all contemplated aspects and / or embodiments or to depict the scope associated with any particular aspect and / or embodiment. Accordingly, the sole purpose of the following overview is to present, in a simplified form, certain concepts relating to one or more aspects and / or embodiments of the mechanisms disclosed herein before the detailed description given below.

[0009] One or more aspects may relate to a target device. The target device may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor, the memory, and / or the transceiver may be configured to receive control information from one or more originating devices. The control information may instruct resource scheduling for a data channel carrying several transmissions from the one or more originating devices and intended for use by the target device. The processor, the memory, and / or the transceiver may also be configured to listen on the data channel based on the control information to locate the several transmissions. The processor, the memory, and / or the transceiver may be further configured to send a multiple transmission negative acknowledgment (NACK) to the one or more originating devices on a feedback channel. The multiple transmission NACK may notify the one or more originating devices of a group of transmissions that were not successfully received. The group of transmissions that were not successfully received at the target device when listening on the data channel. The multiple transmission NACK may be a single feedback.

[0010] One or more aspects may relate to a method for targeting an apparatus. The method may include receiving control information from one or more originating devices. The control information may instruct resource scheduling for a data channel carrying several transmissions from the one or more originating devices and intended for use with the target apparatus. The method may further include listening on the data channel based on the control information to locate the several transmissions. The method may further include sending a multiple transmission negative acknowledgment (NACK) to the one or more originating devices on a feedback channel. The multiple transmission NACK may notify the one or more originating devices of a group of transmissions that were not successfully received. The group of transmissions that were not successfully received may include multiple transmissions among the several transmissions that were not successfully received at the target apparatus when listening on the data channel. The multiple transmission NACK may be a single feedback.

[0011] One or more aspects may also relate to a target device. The target device may include means for receiving control information from one or more originating devices. The control information may instruct resource scheduling for a data channel carrying several transmissions from the one or more originating devices and intended for use with the target device. The target device may also include means for listening on the data channel based on the control information to locate the several transmissions. The target device may further include means for sending a multiple transmission negative acknowledgment (NACK) to the one or more originating devices on a feedback channel. The multiple transmission NACK may notify the one or more originating devices of a group of transmissions that were not successfully received. The group of transmissions that were not successfully received at the target device when listening on the data channel. The multiple transmission NACK may be a single feedback.

[0012] One or more aspects may relate to a non-transient computer-readable medium storing computer-executable instructions for a target device. The computer-executable instructions may include one or more instructions causing the target device to receive control information from one or more originating devices. The control information may instruct resource scheduling for a data channel carrying several transmissions from the one or more originating devices and intended for use by the target device. The computer-executable instructions may also include one or more instructions causing the target device to listen on the data channel based on the control information to locate the several transmissions. The computer-executable instructions may further include one or more instructions causing the target device to send a multiple transmission negative acknowledgment (NACK) to the one or more originating devices on a feedback channel. The multiple transmission NACK may notify the one or more originating devices of a group of transmissions that were not successfully received. The group of transmissions that were not successfully received at the target device when listening on the data channel. The multiple transmission NACK may be a single feedback.

[0013] One or more aspects may relate to an originating device. The originating device may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor, the memory, and / or the transceiver may be configured to send control information to a target device. The control information may instruct resource scheduling for a data channel carrying several transmissions from the originating device and intended for use by the target device. The processor, the memory, and / or the transceiver may also be configured to transmit the several transmissions on the data channel. The processor, the memory, and / or the transceiver may be further configured to receive multiple transmission negative acknowledgments (NACKs) from the target device on a feedback channel. The multiple transmission NACKs may notify the originating device of a group of transmissions that were not successfully received. The group of transmissions that were not successfully received at the target device when listening on the data channel. The multiple transmission NACKs may be a single feedback. The processor, the memory, and / or the transceiver may be further configured to retransmit at least the plurality of transmissions in the unreceived transmission group on the data channel when the multitransmission NACK is received.

[0014] One or more aspects may relate to a method for an originating device. The method may include sending control information to a target device. The control information may instruct resource scheduling for a data channel carrying several transmissions from the originating device and intended for use by the target device. The method may further include transmitting the several transmissions on the data channel. The method may further include receiving a multiple transmission negative acknowledgment (NACK) from the target device on a feedback channel. The multiple transmission NACK may notify the originating device of a group of transmissions that were not successfully received. The group of transmissions that were not successfully received at the target device when listening on the data channel may include multiple transmissions among the several transmissions that were not successfully received at the target device. The multiple transmission NACK may be a single feedback. The method may further include retransmitting at least the multiple transmissions from the group of transmissions that were not received on the data channel when the multiple transmission NACK is received.

[0015] One or more aspects may also relate to an originating device. The originating device may include means for sending control information to a target device. The control information may instruct resource scheduling for a data channel carrying several transmissions from the originating device and intended for use with the target device. The originating device may also include means for transmitting the several transmissions on the data channel. The originating device may further include means for receiving a multiple transmission negative acknowledgment (NACK) from the target device on a feedback channel. The multiple transmission NACK may notify the originating device of the existence of a group of transmissions that were not successfully received. The group of transmissions that were not successfully received may include multiple transmissions among the several transmissions that were not successfully received at the target device when listening on the data channel. The multiple transmission NACK may be a single feedback. The originating device may further include means for retransmitting at least the multiple transmissions in the group of unreceived transmissions on the data channel when the multiple transmission NACK is received.

[0016] One or more aspects may relate to a non-transient computer-readable medium storing computer-executable instructions for an originating device. The computer-executable instructions may include one or more instructions causing the originating device to send control information to a target device. The control information may instruct resource scheduling for a data channel carrying several transmissions from the originating device and intended for use by the target device. The computer-executable instructions may also include one or more instructions causing the originating device to transmit the several transmissions on the data channel. The computer-executable instructions may further include one or more instructions causing the originating device to receive a multiple transmission negative acknowledgment (NACK) from the target device on a feedback channel. The multiple transmission NACK may notify the originating device of a group of transmissions that were not successfully received. The group of transmissions that were not successfully received at the target device when listening on the data channel. The multiple transmission NACK may be a single feedback. The computer-executable instructions may further include one or more instructions that cause the originating device to retransmit at least one of the multiple transmissions in the unreceived transmission group on the data channel when the multiple transmission NACK is received.

[0017] Based on the accompanying drawings and detailed description, other objectives and advantages associated with the aspects and embodiments disclosed herein will be apparent to those skilled in the art. Brief description of the attached diagram

[0019] A more complete understanding of the aspects and embodiments described herein, and their many accompanying advantages, will be readily available upon consideration of the following detailed description taken in conjunction with the accompanying drawings, which are given for illustrative purposes only and do not constitute any limitation, and wherein:

[0020] Figure 1It explains examples of vehicle-to-vehicle (V2V) scenarios;

[0021] Figure 2 An example of mapping subchannels of the Physical Side Link Shared Channel (PSSCH) to feedback resources of the Physical Side Link Feedback Channel (PSFCH) is explained;

[0022] Figure 3 Simplified block diagrams are provided for several examples of components that can be used in communication nodes, based on various aspects.

[0023] Figure 4 The document describes example signaling for sidelink communication between the originating and target devices when the devices are operating in NACK-only mode, based on various aspects.

[0024] Figure 5-6 An example flowchart illustrates a method and / or process performed by the originating device and the target device to perform sidelink communication according to one or more aspects; and

[0025] Figure 7-9 An example of mapping multiple transmission NACKs to feedback channel resources is explained, based on various aspects.

[0026] Detailed description

[0027] The various aspects described herein generally relate to wireless communication systems, and more particularly to multiple NACK indications in the PSFCH. These and other aspects are disclosed in the following description and accompanying drawings to illustrate specific examples relating to the various exemplary aspects. Alternative aspects will be apparent to those skilled in the art upon reading this disclosure and can be constructed and practiced without departing from the scope or spirit of this disclosure. Furthermore, well-known elements will not be described in detail or may be omitted so as not to obscure the relevant details of the aspects disclosed herein.

[0028] The term “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” need not be construed as superior to or better than other aspects. Similarly, the term “aspect” does not require all aspects to include the features, advantages, or modes of operation discussed.

[0029] The terminology used herein describes specific aspects only and should not be construed as limiting any aspect disclosed herein. As used herein, the singular forms “a,” “some,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. Those skilled in the art will further understand that the terms “comprising,” “having,” “including,” and / or “containing,” as used herein, specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0030] Furthermore, the various aspects can be described as sequences of actions performed by elements, such as computing devices. Those skilled in the art will recognize that the various actions described herein can be performed by special-purpose circuitry (e.g., application-specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequences of actions described herein can be considered to be fully implemented within any form of non-transitory computer-readable medium storing a corresponding set of computer instructions that, upon execution, will cause the associated processor to perform the functionality described herein. Thus, the various aspects described herein can be implemented in several different forms, all of which are contemplated to fall within the scope of the claimed subject matter. Furthermore, for each aspect described herein, a corresponding form of any such aspect can be described herein as, for example, "logic configured to perform the described actions" and / or other structural components configured to perform the described actions.

[0031] As used herein, the terms “User Equipment” (UE) and “base station” are not intended to be specific to or otherwise limited to any particular radio access technology (RAT) unless otherwise stated. Generally, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., mobile phone, router, tablet computer, laptop computer, tracking device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.). A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a radio access network (RAN). As used herein, the term “UE” can be interchangeably referred to as “access terminal” or “AT,” “client device,” “wireless device,” “subscriber equipment,” “subscriber terminal,” “subscriber station,” “user terminal” or “UT,” “mobile terminal,” “mobile station,” or variations thereof. Generally, a UE can communicate with the core network via the RAN, and through the core network, the UE can connect to external networks (such as the Internet) and other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through a wired access network, a wireless local area network (WLAN) (e.g., based on IEEE 802.11, etc.).

[0032] A base station may operate according to one of several RATs when communicating with a UE, depending on the network in which it is deployed, and may be alternatively referred to as an Access Point (AP), Network Node, B-Node, Evolved B-Node (eNB), New Radio (NR) B-Node (also known as gNB or gNodeB), etc. Additionally, in some systems, the base station may provide purely edge node signaling functions, while in others, it may provide additional control and / or network management functions. The communication link through which the UE can signal to the base station is called an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the base station can signal to the UE is called a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term traffic channel (TCH) may refer to either a UL / reverse or DL / forward traffic channel.

[0033] The term "base station" can refer to a single physical transmission point or multiple physical transmission points that may or may not be located in the same place. For example, when the term "base station" refers to a single physical transmission point, the physical transmission point may be a base station antenna corresponding to a cell of the base station. When the term "base station" refers to multiple physical transmission points located in the same place, these physical transmission points may be the antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). When the term "base station" refers to multiple physical transmission points not located in the same place, these physical transmission points may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio headend (RRH) (a remote base station connected to the serving base station). Alternatively, physical transmission points not located in the same place may be the serving base station from which the UE receives measurement reports and neighboring base stations from which the UE is measuring its reference signal.

[0034] The new radio (NR) allows network-independent communication between two UEs. In other words, instead of communicating through a base station acting as an intermediary, two UEs can perform sidelink communication with each other via a direct PC5 interface (also known as sidelink (SL) communication). Sidelink communication can occur in the context of cellular vehicle-to-everything (CV2X). One example is... Figure 1 The text describes a vehicle-to-vehicle (V2V) scenario 100. Here, two vehicles 1101 and 1102 can be considered as UEs communicating with each other via sidelinks. Each vehicle 1101 or 1102 can transmit data to and receive data from the other vehicle 1101 or 1102 via a wireless link 120. For ease of reference, the transmitting UE and the receiving UE can also be referred to as the "originating" UE and the "target" UE. Figure 1 At one moment, vehicle 110 1 can be the originating UE and vehicle 110 2 can be the target UE. At another moment, the roles can be reversed.

[0035] The following channels enable sidelink communication between one or more transmitting UEs and one or more receiving UEs: Physical Sidelink Control Channel (PSCCH), Physical Sidelink Feedback Channel (PSFCH), and Physical Sidelink Shared Channel (PSSCH). When traffic is available to be transmitted, the originating UE may transmit control information and / or signals on the PSCCH to prepare the target UE to receive traffic from the originating UE. For example, the PSCCH may instruct or otherwise notify the UE to reserve time-frequency resources (e.g., PSSCH resources) for data transmission. The originating UE may also include a portion of the Sidelink Control Information (SCI), demodulation reference signal (DMRS) mode, etc., to allow the target UE to adjust appropriately for channel conditions. The originating UE may then transmit data to the target UE on the PSSCH (e.g., on the reserved PSSCH resources). The PSSCH may be used to carry other information, such as another portion of the SCI, System Information Block (SIB), etc.

[0036] NR sidelinks support HARQ-ACK reports for PSSCH transmissions. In NR, sidelink feedback is limited to transport block (TB) level ACK / NACK. The target UE can use PSFCH to provide feedback to the originating UE. For example, the PSFCH can carry HARQ ACK / NACK feedback indicating whether the target UE has correctly received the transmission from the originating UE.

[0037] In Release 16 (Rel 16) of the 3GPP standard, two sidelink feedback modes are supported: ACK / NACK feedback and NACK-only feedback. In ACK / NACK feedback mode, the target UE sends either ACK or NACK feedback to the originating UE, depending on whether it successfully received the transmission from the originating UE at the target UE. In NACK-only feedback mode, the target UE sends NACK only if reception is unsuccessful; it does not send ACK feedback if reception is successful. In NACK-only feedback mode, the originating UE infers ACK if it has not received any feedback from the target UE. In either mode, upon receiving NACK feedback on the PSFCH, the originating UE may retransmit the unsuccessfully received traffic.

[0038] Incidentally, there might be a situation where the originating UE transmits data, but the target UE does not detect the transmission and therefore is unaware that it is the destination of the transmitted data. In such cases, the target UE will not provide any feedback to the originating UE, which would be inferred as ACK by the originating UE in NACK-only mode. As a mitigation measure, the originating UE can be configured to transmit the data multiple times.

[0039] In sidelink communication, there may be a mapping between PSCCH / PSSCH resources and feedback resources in PSFCH. Figure 2 An example of mapping PSSCH subchannels to feedback resources in PSFCH is explained. A subchannel can be considered as the smallest unit for scheduling resources (e.g., PSSCH) in the frequency domain, and depending on the configuration, it may include several coherent resource blocks (RBs). Figure 1 The solid arrows in the diagram illustrate examples of mappings between subchannels and NACK resources in the PSFCH, while the dashed arrows illustrate examples of mappings between subchannels and ACK resources. In NACK-only mode, it is not necessary to define the mappings indicated by the dashed arrows.

[0040] Note that ACK / NACK resources are not all contiguous. This means the target UE may need to transmit feedback on multiple non-contiguous PSFCH resources. This can be disadvantageous, as transmitting on non-contiguous bands typically requires more power than transmitting on contiguous bands. Perhaps even more significantly, in some instances, the characteristics of the PSFCH feedback resources to be transmitted may exceed the target UE's capabilities. For example, the target UE may be unable to transmit in non-adjacent bands, or may be limited in the number of non-adjacent bands available for transmission. As another example, the number of feedback resources to be transmitted may simply exceed the target UE's capabilities.

[0041] In ACK / NACK mode, this may not be a significant problem because the originating UE expects to retransmit without feedback from the target UE. In other words, in ACK / NACK mode, the originating UE treats the lack of feedback very similarly to receiving NACK feedback.

[0042] However, in NACK-only mode, exceeding the target UE's feedback capability can be quite serious. In this mode, the target UE may not correctly receive the TB. Unfortunately, when it cannot do so, it may also fail to send a NACK. However, when the originating UE does not receive feedback regarding the TB, it assumes that the target UE has successfully received the transmitted TB and moves on to the next TB. Therefore, the target UE does not receive the required retransmission.

[0043] To address some or all of the issues identified above, it is proposed that the target UE (more broadly, the target device) be able to indicate NACK for multiple transmissions from one or more originating UEs (more broadly, one or more originating devices) via multi-transmission NACK feedback, which is a single NACK feedback.

[0044] Figure 3Several exemplary components (represented by corresponding blocks) that can be incorporated into an originating device (e.g., a UE) and a target device (e.g., another UE) performing sidelink communication with each other are described. It should be understood that, in general, a device can be an originating device at one time and a target device at another. It will be appreciated that these components can be implemented in different types of devices (e.g., in an ASIC, in a system-on-a-chip (SoC), etc.) in different implementations. The described components can also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described to provide similar functionality. Furthermore, a given device may include one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0045] Devices 302 and 304 each include at least one wireless communication device (represented by communication devices 308 and 314) for communicating with other devices via a side link. For example, communication devices 308 and 314 can communicate with each other via wireless communication link 360. Communication device 308 may include at least one transmitter (represented by transmitter 310) for transmitting and encoding signals (e.g., messages, indications, information, etc.) and at least one receiver (represented by receiver 312) for receiving and decoding signals (e.g., messages, indications, information, pilots, etc.). Similarly, each communication device 314 may include at least one transmitter (represented by transmitter 316) for transmitting signals (e.g., messages, indications, information, pilots, etc.) and at least one receiver (represented by receiver 318) for receiving signals (e.g., messages, indications, information, etc.).

[0046] In some implementations, the transmitter and receiver may include integrated devices (e.g., transmitter and receiver circuitry implemented as a single communication device, often referred to as a "transceiver"), in some implementations may include separate transmitter and receiver devices, or in other implementations may be implemented in a different manner.

[0047] Devices 302 and 304 may also include other components that can be used for sidelink communication as disclosed herein. Originating device 302 may include a processing system 332 for providing functionality, for example, related to transmission initiation operations as described herein, and for providing other processing functionality. Device 304 may include a processing system 334 for providing functionality related to transmission reception operations as described herein, and for providing other processing functionality. Devices 302 and 304 may include memory components 338 and 340 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Furthermore, devices 302 and 304 may include user interfaces 350 and 351 for providing instructions to a user (e.g., audible and / or visual instructions) and / or for receiving user input (e.g., when the user actuates a sensing device such as a keypad, touchscreen, microphone, etc.).

[0048] At devices 302 and 304, receivers 312 and 318 can receive signals via their respective antennas. Receivers 312 and 318 can recover information modulated onto the RF carrier and provide that information to processing systems 332 and 334. Transmitters 310 and 316 and receivers 312 and 318 can implement Layer 1 functionality associated with various signal processing functions.

[0049] Processing systems 332 and 334 can provide RRC layer functionality, RLC layer functionality, MAC layer functionality, scheduling information reporting, and error correction via Hybrid Automatic Repeat Request (HARQ) associated with system information (e.g., MIB, SIB) transmission / acquisition, RRC connection, scheduling information reporting, and error correction.

[0050] In one aspect, devices 302 and 304 may include capability managers 344 and 358. Capability managers 344 and 358 may be hardware circuitry that is part of or coupled to processing systems 332 and 334, which, when executed, enables devices 302 and 304 to perform the functionality described herein. Alternatively, capability managers 344 and 358 may be memory modules stored in memory components 338 and 340, which, when executed by processing systems 332 and 334, enable devices 302 and 304 to perform the functionality described herein.

[0051] For convenience, devices 302 and 304 are... Figure 3 The box is shown as including various components that can be configured according to the various examples described herein. However, it will be understood that the illustrated box may have different functionalities in different designs.

[0052] The various components of devices 302 and 304 can communicate with each other on data buses 352 and 354. Figure 3Components can be implemented in various ways. In some implementations, Figure 3 The components can be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or incorporate at least one memory component for storing information or executable code used by that circuit to provide this functionality. For example, some or all of the functionality represented by blocks 308, 332, 338, 344, and 350 may be implemented by the processors and memory components of the originating device 302 (e.g., by executing appropriate code and / or by appropriately configuring the processor components). Similarly, some or all of the functionality represented by blocks 314, 320, 334, 340, and 358 may be implemented by the processors and memory components of the target device 304 (e.g., by executing appropriate code and / or by appropriately configuring the processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed "by the originating device UE", "by the target device", etc. However, as will be understood, such operations, actions and / or functions may actually be performed by specific components (such as processing systems 332, 334, communication devices 308, 314, capability managers 344, 358, etc.) or combinations of components of the originating device and the target device.

[0053] As discussed above, the proposed target device can indicate a NACK for multiple transmissions from one or more originating devices via a single feedback known as a multi-transmission NACK feedback. For example, the target device (e.g., target device 304) can be configured to provide one or more multi-transmission NACK feedbacks, where each multi-transmission NACK feedback can be considered as a single feedback indicating a NACK for multiple transmissions from one or more originating devices. As mentioned, this approach is less resource-intensive than responding with an individual NACK for each unreceived transmission.

[0054] Figure 4 This section describes example signaling for sidelink communication between an originating device and a target device when the device operates in NACK-only mode. In short, the originating device can send control information to the target device to prepare it for receiving transmissions. Subsequently, within a specific time duration (e.g., several frames, subframes, time slots, symbols, etc.), the originating device can send several transmissions, and the target device can listen to these transmissions. If the target device fails to receive multiple transmissions, it can send one or more multitransmission NACKs to the originating device. In response to a multitransmission NACK, the originating device can retransmit the unsuccessfully received transmissions over one or more subsequent time durations.

[0055] about Figure 5 and Figure 6 Details are provided, including flowcharts illustrating example methods 500 and 600 performed by the originating device and the target device (e.g., originating device 302, target device 304) to perform sidelink communication with each other. The memory component 338 of the originating device 302 may be used to store information for... Figure 3 Examples of computer-readable media comprising one or more of the communication device 308 (including transmitter 310 and / or receiver 312), processing system 334, memory component 340, and / or capability manager 344 of the originating device 302, which execute computer-executable instructions of method 800. The memory component 340 of the target device 304 may be a storage medium for storing instructions for... Figure 3 Examples of computer-readable media in which one or more of the target device 304 described herein, including communication device 314 (including transmitter 316 and / or receiver 318), processing system 334, memory component 340 and / or capability manager 358, execute computer-executable instructions of method 900, are described.

[0056] exist Figure 5 and 6 In the diagram, dashed arrows indicate the direction of the communication flow between the originating device and the target device. Although one originating device and one target device are shown, one or more originating devices and / or one or more target devices may exist (e.g., unicast and / or multicast communication may exist). However, for convenience and ease of description, the communication flow between one originating device and one target device is described. Extending the described concepts to multiple devices should be relatively straightforward. In block 510, the originating device may send control information, and in block 610, the target device may receive the control information. The device for performing block 510 may include... Figure 3 The originating device 302 described herein includes one or more of the communication device 308 (including transmitter 310 and / or receiver 312), processing system 332, and / or memory component 338. The means for executing block 610 may include... Figure 3 The target device 304 described herein includes one or more of the following: communication equipment 314 (including transmitter 316 and / or receiver 318), processing system 334 and / or memory component 340.

[0057] Control information may include information instructing resource scheduling for several data channels carrying data from the originating device and intended for use by the target device. Control information may include scheduling information for transmissions that will occur within a specific time duration (e.g., see...). Figure 4A specific duration can be specified as a time quantity or as a unit corresponding to time (e.g., the number of frames, subframes, time slots, symbols, etc.). The target device can decode the received control information so that it can prepare itself to listen for transmissions intended for the target device.

[0058] An example of control information could be 5G NR sidelink control information (SCI). Control information can be transmitted on a control channel (e.g., PSCCH). Alternatively, in addition to the control channel, control information can also be transmitted on a data channel (e.g., PSSCH). For example, control information can be transmitted in two parts, one part on the control channel and the other part on the data channel. In other words, control information can be transmitted / received at least on the control channel.

[0059] In block 520, the originating device may transmit several transmissions (e.g., multiple transport blocks (TBs)) on the data channel (e.g., PSSCH) within a specific time duration according to a schedule. In block 620, the target device may listen on the data channel based on the control information. For example, the target device may listen on scheduled resources (subchannels, time slots, subframes, frames, resource blocks (RBs), etc.) of the data channel during a specific time duration to locate the several transmissions.

[0060] The means for executing block 520 may include Figure 3 The originating device 302 described herein includes one or more of the communication device 308 (including transmitter 310 and / or receiver 312), processing system 332, and / or memory component 338. The means for executing block 620 may include... Figure 3 The target device 304 described herein includes one or more of the following: communication equipment 314 (including transmitter 316 and / or receiver 318), processing system 334 and / or memory component 340.

[0061] In the event that the target device fails to correctly receive many of the multiple transmissions, in block 630, the target device may send one or more multiple transmission NACKs to the originating device on a feedback channel (e.g., PSFCH). In block 530, the originating device may receive the multiple transmission NACKs. The means for performing block 630 may include... Figure 3 The target device 304 described herein includes one or more of the following: communication device 314 (including transmitter 316 and / or receiver 318), processing system 334, and / or memory component 340. The means for executing block 530 may include... Figure 3 The originating device 302 described herein includes one or more of the following: communication equipment 308 (including transmitter 310 and / or receiver 312), processing system 332 and / or memory component 338.

[0062] Each multitransmission NACK notifies the originating device that multiple transmissions out of several transmissions were not successfully received during the time duration while listening on the data channel according to control information. Multitransmission NACKs can be carried on one or more resources of the feedback channel.

[0063] On one hand, each multitransmission NACK may correspond to a specific group of transmissions, where each transmission in the group is either not received at all (e.g., not detected) or is received (e.g., detected) but the target device fails to decode the received transmission correctly. For ease of description, the term "unsuccessfully received" may be used to refer to a transmission that is not received at all or a transmission that is not correctly decoded. It can then be said that each multitransmission NACK notifies the originating device of the existence of a corresponding group of unsuccessfully received transmissions, also referred to as the group of unsuccessfully received transmissions. Each group of unsuccessfully received transmissions may include multiple transmissions that were not successfully received at the target device when listening on a data channel. Each multitransmission NACK may be a single feedback.

[0064] When there are two or more multitransmission NACKs, the corresponding unsuccessfully received groups can be different. On the one hand, if at least one unsuccessfully received transmission is a member of one group but not a member of another group, the two unsuccessfully received groups can be considered different.

[0065] Typically, when the target device is capable, it can individually NACK each unsuccessfully received transmission. In many instances, this may be preferred because it allows the originating device to more precisely pinpoint which of the transmissions to retransmit. Therefore, in one aspect, when the target device determines that it cannot individually NACK each unsuccessfully received transmission, it can send one or more multitransmission NACKs. However, it is also envisioned that in some instances, the target device can utilize multitransmission NACKs even when it is capable of sending individual NACKs.

[0066] Upon receiving a multiple transmission NACK, in box 540, the originating device may retransmit the unsuccessfully received group to the target device. In box 640, the target device may listen for the retransmission. The means for performing box 540 may include... Figure 3 The originating device 302 described herein includes one or more of the communication device 308 (including transmitter 310 and / or receiver 312), processing system 332, and / or memory component 338. The means for executing block 640 may include... Figure 3 The target device 304 described herein includes one or more of the following: communication equipment 314 (including transmitter 316 and / or receiver 318), processing system 334 and / or memory component 340.

[0067] It should be noted that retransmissions can be part of a scheduled transmission over one or more subsequent time periods. However, to minimize clutter, the transmission of control information from the originating device and the reception of control information for subsequent scheduling are not included in the retransmission process. Figure 4 and 5 As shown in the image.

[0068] For each multitransmission NACK, the originating device may retransmit at least those multiple transmissions from the corresponding group of unsuccessfully received transmissions. In one aspect, the multitransmission NACK may be one of multiple feedback scenarios, where each feedback scenario indicates a common characteristic of the multiple transmissions from the corresponding group of unsuccessfully received transmissions. The originating device may be able to determine, at least in part, which transmission to retransmit based on the feedback scenario of each multitransmission NACK. The following is a list of example feedback scenarios (not necessarily exhaustive):

[0069] • The first feedback scenario can indicate that multiple transmissions in the corresponding unsuccessfully received group are transmissions carried on a specific sub-channel;

[0070] • The second feedback scenario can indicate that the multiple transmissions in the corresponding unsuccessfully received group were transmissions transmitted at a specific time segment (e.g., frame, subframe, time slot, etc.);

[0071] The third feedback scenario can indicate that the multiple transmissions in the corresponding unsuccessfully received group are transmissions associated with a specific source ID. Note that different applications can configure different source IDs for the same UE;

[0072] The fourth feedback scenario indicates that the multiple transmissions in the corresponding unsuccessfully received group are transmissions associated with a specific destination ID. Note that different applications can configure different destination IDs for the same UE. The UE can also belong to different groups, each associated with a different ID;

[0073] • The fifth feedback scenario can indicate that the multiple transmissions in the corresponding unsuccessfully received group are transmissions associated with a uniquely identifying originator ID;

[0074] The sixth feedback scenario can indicate that the multiple transmissions in the corresponding unsuccessfully received group are transmissions associated with a specific originating group. In this scenario, the group can be a group of UEs that can be addressed using a single groupcast (multicast) transmission rather than addressing each UE individually;

[0075] • The seventh feedback scenario can indicate that the multiple transmissions in the corresponding unsuccessfully received group are transmissions associated with a target ID that uniquely identifies the target device;

[0076] • The eighth feedback scenario can indicate that the multiple transmissions in the corresponding unsuccessfully received group are transmissions associated with a specific target group, which is a group of receiving devices of the intended recipients of the multiple transmissions.

[0077] On one hand, each multitransmission NACK can be mapped to a feedback channel resource (e.g., a resource block (RB) mapped to the PSFCH), and the target device can transmit each multitransmission NACK on the corresponding mapped feedback channel resource. The mapping can be based on the common characteristics of the multiple transmissions in a group of unsuccessfully received transmissions. Through such feedback channel resource mapping, when the originating device receives a multitransmission NACK, it can determine which of the multiple transmissions to retransmit in a future time period.

[0078] Figure 7 The example of mapping multi-transmission NACKs to feedback channel resources based on sub-channel identity (ID) is explained. Figure 7 In resource mapping 700, sub-channels 1, 2, 3, and 4 are interpreted as being mapped to feedback channel resources 710, 720, 730, and 740, respectively. Therefore, for example, if the target device sends a multiple transmission NACK on feedback channel resource 710 in block 630, the originating device will subsequently recognize that the multiple transmissions in the corresponding unreceived group were transmitted on sub-channel 1. The originating device can then retransmit the multiple transmissions in the corresponding unreceived group on the same sub-channel or a different sub-channel in block 540. Although in Figure 7 Four sub-channels are shown. It should be noted that any number of sub-channels can exist in the data channel.

[0079] Figure 8 Another example where multi-transmission NACKs are mapped to feedback channel resources is explained. Here, the mapping is based on time segmentation, such as time slots. Figure 8 In resource mapping 800, time slots n, n+1, n+2, and n+3 are interpreted as being mapped to feedback channel resources 810, 820, 830, and 840, respectively. Therefore, for example, if the target device sends a multi-transmission NACK on feedback channel resource 810, the originating device will subsequently recognize that multiple transmissions in the corresponding unreceived group were transmitted on time slot n. The originating device can then retransmit the multiple transmissions in the corresponding unreceived group in the same time slot or in a different time slot. Although in Figure 8 The diagram shows four time slots. It should be noted that any number of time slots can exist in a data channel. Furthermore, other time subdivisions can be used for mapping, such as frames, subframes, time slots, etc.

[0080] Although not explicitly stated, other common characteristics can be used for resource mapping purposes. These include source ID, destination ID, originator ID, originator group, destination ID, and / or destination group. Each multitransmission NACK can be mapped based on any combination of common characteristics.

[0081] On the one hand, one or more of the multiple transmissions in NACK can be mapped one-to-one with the feedback channel resources. Figure 7 and 8 This is an example of such a one-to-one mapping. But on the other hand, as... Figure 9 As explained in the text, two or more multitransmission NACKs can be mapped to the same feedback channel resource. Similar to... Figure 7 , Figure 9 The example of mapping multi-transmission NACK to feedback channel resources based on sub-channels was explained. However, compared to... Figure 7 The difference lies in Figure 9 In resource mapping 900, multiple multitransmission NACKs are mapped to the same channel feedback resource. For example, subchannels 1 and 2 are mapped to feedback channel resource 910, and subchannels 3 and 4 are mapped to feedback channel resource 930. In this example, if the originating device receives a multitransmission NACK on channel feedback resource 910 in block 530, it can retransmit all transmissions transmitted on subchannels 1 and 2 in block 540.

[0082] On the other hand, even when multiple multitransmission NACKs are mapped to the same feedback channel resource, the target device can still indicate a specific multitransmission NACK through sequence attributes. For example, suppose the target device wants to indicate that a multitransmission NACK corresponds to subchannel 1, that is, to indicate that multiple transmissions transmitted on subchannel 1 were not successfully received. To distinguish between subchannel 1 and subchannel 2, when transmitting the multitransmission NACK in block 630, the target device can serialize the multitransmission NACK carried on feedback channel resource 910, serializing it for subchannel 1 in one manner and for subchannel 2 in a different manner. In addition to feedback resource mapping, the originating device can more accurately determine which transmissions to retransmit based on the sequence of the multitransmission NACKs.

[0083] It is recognized that multiple originating devices and / or multiple target devices can exist. This means that from the perspective of a target device, a multitransmission NACK can be mapped to feedback channel resources shared by one or more other target devices. In such instances, a target device can generate a sequence of multitransmission NACKs that differs from the sequences generated by other target devices. This allows the originating device to identify the correct target device for retransmission.

[0084] Note that the target device can generate the same or different sequences for each of the multiple transmission NACKs, regardless of whether the mapped resources are shared. For example, sequences can be generated based on any combination of subchannel ID, time segmentation ID (e.g., frame ID, subframe ID, time slot ID, etc.), source ID, destination ID, originating group ID, target ID, and / or target group ID.

[0085] The following provides an overview of the examples in this disclosure:

[0086] Example 1: A method for a target device includes: receiving control information from one or more originating devices, the control information indicating resource scheduling for a data channel carrying a plurality of transmissions from the one or more originating devices and intended for use by the target device; listening on the data channel based on the control information to locate the plurality of transmissions; and sending a multiple transmission negative acknowledgment (NACK) on a feedback channel to the one or more originating devices to notify the one or more originating devices of a group of unsuccessfully received transmissions, the group of unsuccessfully received transmissions including multiple transmissions of the plurality of transmissions that were unsuccessfully received at the target device when listening on the data channel, and the multiple transmission NACK being a single feedback.

[0087] Example 2: The method of Example 1, wherein: the control information is received at least on the Physical Side Link Control Channel (PSCCH), the data channel is the Physical Side Link Shared Channel (PSSCH), and the feedback channel is the Physical Side Link Feedback Channel (PSFCH).

[0088] Example 3: The method of any of Examples 1 to 2 further includes: determining whether the target device is capable of sending an individual NACK for each transmission in the unsuccessfully received group, and wherein the multi-transmission NACK is sent when it is determined that the target device is unable to send an individual NACK for each transmission in the unsuccessfully received group.

[0089] Example 4: The method of any of Examples 1 to 3, wherein: the multitransmission NACK applies to the number of transmissions scheduled to be carried on the data channel within a specific time duration.

[0090] Example 5: The method is similar to that in Example 4, where the duration of a particular time is several frames, several subframes, or several time slots.

[0091] Example 6: The method of any of Examples 4 to 5, wherein the multitransmission NACK is one or more of a plurality of feedback cases, each feedback case indicating a common characteristic of the plurality of transmissions in the group of unsuccessfully received transmissions.

[0092] Example 7: The method of Example 6, wherein the plurality of feedback scenarios include: a first feedback scenario indicating that the plurality of transmissions in the unsuccessfully received group are transmissions carried on a specific subchannel of the data channel; a second feedback scenario indicating that the plurality of transmissions in the unsuccessfully received group are transmissions transmitted at a specific time segment; a third feedback scenario indicating that the plurality of transmissions in the unsuccessfully received group are transmissions associated with a specific source identity (ID); a fourth feedback scenario indicating that the plurality of transmissions in the unsuccessfully received group are transmissions associated with a specific destination ID; a fifth feedback scenario indicating that the plurality of transmissions in the unsuccessfully received group are transmissions associated with an originator ID that uniquely identifies the one or more originating devices; a sixth feedback scenario indicating that the plurality of transmissions in the unsuccessfully received group are transmissions associated with a specific originating group; a seventh feedback scenario indicating that the plurality of transmissions in the unsuccessfully received group are transmissions associated with a target ID that uniquely identifies the target device; and an eighth feedback scenario indicating that the plurality of transmissions in the unsuccessfully received group are transmissions associated with a specific target group of receiving devices that are the intended recipients of the plurality of transmissions.

[0093] Example 8: The method of any of Examples 1 to 7, wherein the multitransmission NACK is mapped to a feedback channel resource based on the common characteristics of the multiple transmissions in the group of unsuccessfully received transmissions, and wherein the multitransmission NACK is transmitted on the feedback channel resource to which the multitransmission NACK is mapped.

[0094] Example 9: The method of Example 8, wherein the common feature is one or more of the following: specific sub-channel, specific time segmentation, specific source ID, specific destination ID, specific originator ID, specific originator group, specific target ID, and / or specific target group.

[0095] Example 10: The method of any of Examples 8 to 9, wherein the multitransmission NACK and another multitransmission NACK are mapped to the same feedback channel resource.

[0096] Example 11: The method of any of Examples 8 to 10 further includes generating a sequence of the multitransmission NACKs, which is different from the sequence generated for the other multitransmission NACK.

[0097] Example 12: The method of any of Examples 1 to 11, wherein the multitransmission NACK is transmitted on a feedback channel resource shared with one or more other target devices.

[0098] Example 13: The method of Example 12 further includes generating a sequence of multitransmission NACKs that is different from the sequence of multitransmission NACKs generated by at least one of the one or more other target devices.

[0099] Example 14: The method of any of Examples 12 to 13 further includes generating the sequence of multitransmission NACKs based on the source identity (ID) and / or destination ID provided in the control information.

[0100] Example 15: A method of an originating device, comprising: sending control information to a target device, the control information indicating resource scheduling for a data channel carrying a plurality of transmissions from the originating device and intended for use by the target device; transmitting the plurality of transmissions on the data channel; receiving a multiple transmission negative acknowledgment (NACK) from the target device on a feedback channel, the multiple transmission NACK notifying the originating device of the existence of a group of unsuccessfully received transmissions, the group of unsuccessfully received transmissions including multiple transmissions of the plurality of transmissions that were unsuccessfully received at the target device when listening on the data channel, and the multiple transmission NACK being a single feedback; and retransmitting at least the multiple transmissions of the group of unsuccessfully received transmissions on the data channel when the multiple transmission NACK is received.

[0101] Example 16: The method of Example 15, wherein: the control information is received at least on the Physical Side Link Control Channel (PSCCH), the data channel is the Physical Side Link Shared Channel (PSSCH), and the feedback channel is the Physical Side Link Feedback Channel (PSFCH).

[0102] Example 17: The method of any of Examples 15 to 16, wherein: the multitransmission NACK applies to the plurality of transmissions scheduled to be carried on the data channel within a specific time duration.

[0103] Example 18: The method of Example 17, where the duration of the particular time is several frames, several subframes, or several time slots.

[0104] Example 19: A method as in any of Examples 17 to 18, wherein the multitransmission NACK is one or more of a plurality of feedback conditions, each feedback condition indicating a common characteristic of the plurality of transmissions in the group of unsuccessfully received transmissions, and wherein the method further includes determining, based on the feedback condition of the multitransmission NACK, which of the plurality of transmissions should be retransmitted.

[0105] Example 20: The method of Example 19, wherein the plurality of feedback scenarios include: a first feedback scenario indicating that the plurality of transmissions in the unsuccessfully received group are transmissions carried on a specific subchannel of the data channel; a second feedback scenario indicating that the plurality of transmissions in the unsuccessfully received group are transmissions transmitted at a specific time segment; a third feedback scenario indicating that the plurality of transmissions in the unsuccessfully received group are transmissions associated with a specific source identity (ID); a fourth feedback scenario indicating that the plurality of transmissions in the unsuccessfully received group are transmissions associated with a specific destination ID; and a fifth feedback scenario indicating that the unsuccessfully received... The feedback scenarios are as follows: a fifth feedback scenario indicating that the multiple transmissions in the received group are transmissions associated with an originator ID that uniquely identifies the one or more originator devices; a sixth feedback scenario indicating that the multiple transmissions in the unreceived group are transmissions associated with a specific originator group; a seventh feedback scenario indicating that the multiple transmissions in the unreceived group are transmissions associated with a target ID that uniquely identifies the target device; and an eighth feedback scenario indicating that the multiple transmissions in the unreceived group are transmissions associated with a specific target group of receiver devices that are the intended recipients of the multiple transmissions.

[0106] Example 21: A method as in any of Examples 15 to 20, wherein the multitransmission NACK is mapped to a feedback channel resource based on common characteristics of the multiple transmissions in the unsuccessfully received group, and wherein the method further includes determining which of the multiple transmissions to retransmit based on the feedback channel resource used to carry the multitransmission NACK.

[0107] Example 22: The method of Example 21, wherein the common feature is one or more of the following: specific sub-channel, specific time segmentation, specific source ID, specific destination ID, specific originator ID, specific originator group, specific target ID and / or specific target group.

[0108] Example 23: The method of any of Examples 21 to 22, wherein the multitransmission NACK and another multitransmission NACK are mapped to the same feedback channel resource.

[0109] Example 24: The method of Example 23, wherein the method further includes determining which of the multiple transmissions to retransmit based on the sequence of the multiple transmission NACKs.

[0110] Example 25: The method of any of Examples 15 to 24, wherein the multitransmission NACK is received on a feedback channel resource shared by the target device and one or more other target devices.

[0111] Example 26: The method of Example 25, wherein the method further includes identifying the target device for retransmission based on the sequence of the multitransmission NACK.

[0112] Example 27: A method as in any of Examples 25 to 26, wherein the method further includes: identifying the source ID and / or destination ID of the plurality of messages in the unsuccessfully received group based on the sequence of the multiple transmission NACKs; and determining, based on the source ID and / or the destination ID, which of the plurality of transmissions should be retransmitted.

[0113] Example 28: A target device includes a processor communicatively coupled to a memory and a transceiver, wherein the processor, the memory, and / or the transceiver are configured to perform a method of any of Examples 1 to 14.

[0114] Example 29: An originator device includes a processor communicatively coupled to a memory and a transceiver, wherein the processor, the memory, and / or the transceiver are configured to perform a method of any of Examples 15 to 27.

[0115] Example 30: A target device comprising: at least one means for performing the method of any one of Examples 1 to 14.

[0116] Example 31: An originating device comprising: at least one means for performing the method of any of Examples 15 to 27.

[0117] Example 32: A non-transient computer-readable medium storing code for a target device, the target device including a processor communicatively coupled to a memory and a transceiver, and instructions stored in the memory and executable by the processor to cause the target device to perform any of the methods of Examples 1 to 14.

[0118] Example 33: A non-transient computer-readable medium storing code for an originating device, the originating device including a processor communicatively coupled to a memory and a transceiver, and instructions stored in the memory and executable by the processor to cause the target device to perform any of the methods of Examples 15 to 27.

[0119] Those skilled in the art will appreciate that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0120] Furthermore, those skilled in the art will appreciate that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps are described above in a generalized manner in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as departing from the scope of the aspects described herein.

[0121] The various illustrative logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternative embodiments, it may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or other such configurations).

[0122] The methods, sequences, and / or algorithms described in conjunction with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of both. The software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disks, removable disks, CD-ROMs, or any other form of non-transient computer-readable medium known in the art. An exemplary non-transient computer-readable medium may be communicatively coupled to a processor, enabling the processor to read / write information from / to the non-transient computer-readable medium. Alternatively, the non-transient computer-readable medium may be integrated into the processor. The processor and non-transient computer-readable medium may reside in an ASIC. The ASIC may reside in a user equipment (e.g., UE) or a base station. Alternatively, the processor and non-transient computer-readable medium may be discrete components within a user equipment or base station.

[0123] In one or more exemplary aspects, the functions described herein may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or codes on or transmitted via a non-transient computer-readable medium. Computer-readable media may include storage media and / or communication media, including any non-transient medium that facilitates the transfer of a computer program from one location to another. Storage media may be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and is accessible to a computer. Similarly, any connection is also legitimately referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. However, the terms disk and disc, which may be used interchangeably in this document, include compact discs (CDs), laser discs, optical discs, digital video discs (DVDs), floppy disks, and Blu-ray discs, which often reproduce data magnetically and / or optically using lasers. Combinations of these should also be included within the scope of computer-readable media.

[0124] Although the foregoing disclosure has shown illustrative aspects, those skilled in the art will appreciate that various changes and modifications may be made therein without departing from the scope of this disclosure as defined in the appended claims. Furthermore, based on the various illustrative aspects described herein, those skilled in the art will appreciate that the functions, steps, and / or actions recited in any of the foregoing methods and / or in any of the appended method claims need not be performed in any particular order. Moreover, with respect to any element described for the foregoing or recited in the appended claims in a singular form, those skilled in the art will appreciate that the singular form also contemplates a plural form, unless explicitly stated to be limited to the singular form.

Claims

1. A target device, comprising: transceiver; Memory; as well as A processor communicatively coupled to the transceiver and the memory. The processor, the transceiver, and / or the memory are configured to: Receive control information from one or more originating devices, the control information indicating resource scheduling for carrying data channels from the one or more originating devices and intended for use by the target device; Based on the control information, the system listens on the data channel to locate the plurality of transmissions; as well as In the Negative Acknowledgment Only (NACK) mode, a multitransmission NACK is sent to the one or more originating devices on the feedback channel to notify the one or more originating devices of a group of unsuccessfully received transmissions, the group of unsuccessfully received transmissions including multiple transmissions that were not successfully received at the target device when listening on the data channel, and the multitransmission NACK is a single feedback, wherein the multitransmission NACK corresponds to one of multiple feedback scenarios, each feedback scenario indicating a common characteristic of the multiple transmissions in the group of unsuccessfully received transmissions.

2. The target device of claim 1, wherein: The control information is received at least on the Physical Side Link Control Channel (PSCCH), the data channel is the Physical Side Link Shared Channel (PSSCH), and the feedback channel is the Physical Side Link Feedback Channel (PSFCH).

3. The target device as described in claim 1, The processor, transceiver, and / or memory are further configured to: determine whether the target device is capable of sending an individual NACK for each transmission in the group of unsuccessfully received transmissions, and The processor, the transceiver, and / or the memory are further configured to send the multitransmission NACK when it is determined that the target device cannot send an individual NACK for each transmission in the unsuccessfully received transmission group.

4. The target device as claimed in claim 1, wherein: The multitransmission NACK applies to the plurality of transmissions scheduled to be carried on the data channel within a specific time period.

5. The target device as claimed in claim 4, wherein the specific time duration is a number of frames, a number of subframes, or a number of time slots.

6. The target device as claimed in claim 1, wherein the plurality of feedback scenarios include: This indicates that the multiple transmissions in the group of unsuccessfully received transmissions are the first feedback scenario of transmissions carried on a specific sub-channel of the data channel. A second feedback scenario indicates that the plurality of transmissions in the group of unsuccessfully received transmissions are transmissions delivered at a specific time segment. A third feedback scenario indicates that the multiple transmissions in the group of unsuccessfully received transmissions are transmissions associated with a specific source identity (ID). A fourth feedback scenario indicates that the multiple transmissions in the group of unsuccessfully received transmissions are transmissions associated with a specific destination ID. The fifth feedback scenario indicates that the multiple transmissions in the group of unsuccessfully received transmissions are transmissions associated with an originator ID that uniquely identifies the one or more originating devices. The sixth feedback scenario indicates that the multiple transmissions in the group of unsuccessfully received transmissions are transmissions associated with a specific originating group. A seventh feedback scenario indicates that the plurality of transmissions in the group of unsuccessfully received transmissions are transmissions associated with a target ID that uniquely identifies the target device, and The eighth feedback scenario indicates that the plurality of transmissions in the group of unsuccessfully received transmissions are transmissions associated with a specific target group of a group of receiving devices that are the intended recipients of the plurality of transmissions.

7. The target device as described in claim 1, The multi-transmission NACK is mapped to feedback channel resources based on the common characteristics of the multiple transmissions in the unsuccessfully received transmission group, and The processor, the transceiver, and / or the memory are configured to transmit the multitransmission NACK on the feedback channel resources mapped to the multitransmission NACK.

8. The target device as claimed in claim 7, wherein the common characteristic is any one or more of the following: Specific sub-channel, specific time segmentation, specific source ID, specific destination ID, specific originator ID, specific originator group, specific target ID, and / or specific target group.

9. The target apparatus of claim 7, wherein the multiple transmission NACK and another multiple transmission NACK are mapped to the same feedback channel resource, wherein the other multiple transmission NACK is generated by the target apparatus.

10. The target apparatus of claim 9, wherein the processor, the transceiver, and / or the memory are configured to generate the sequence of the multitransmission NACKs, the sequence being different from the sequence generated for the other multitransmission NACK.

11. The target device of claim 1, wherein the multitransmission NACK is transmitted on a feedback channel resource shared with one or more other target devices.

12. The target apparatus of claim 11, wherein the processor, the transceiver, and / or the memory are configured to generate the sequence of multitransmission NACKs, the sequence being different from the sequence of multitransmission NACKs generated by at least one of the one or more other target apparatuses.

13. The target apparatus of claim 11, wherein the processor, the transceiver, and / or the memory are configured to generate the sequence of multitransmission NACKs based on the source identity (ID) and / or destination ID provided in the control information.

14. A launching device, comprising: transceiver; Memory; as well as A processor communicatively coupled to the transceiver and the memory. The processor, the transceiver, and / or the memory are configured to: Send control information to the target device, the control information instructing resource scheduling for several data channels carrying data from the originating device and intended for use by the target device; The plurality of transmissions are transmitted on the data channel; In the Negative Acknowledgment Only (NACK) mode, multiple transmission NACKs are received from the target device on the feedback channel. The multiple transmission NACKs notify the originating device of a group of transmissions that were not successfully received. The group of transmissions that were not successfully received at the target device when listening on the data channel includes multiple transmissions of several transmissions that were not successfully received at the target device. The multiple transmission NACKs are a single feedback. as well as When the multitransmission NACK is received, at least the plurality of transmissions in the group of unsuccessfully received transmissions are retransmitted on the data channel, wherein the multitransmission NACK corresponds to one of a plurality of feedback scenarios, each feedback scenario indicating a common characteristic of the plurality of transmissions in the group of unsuccessfully received transmissions.

15. The initiating device as claimed in claim 14, wherein: The control information is received at least on the Physical Side Link Control Channel (PSCCH), the data channel is the Physical Side Link Shared Channel (PSSCH), and the feedback channel is the Physical Side Link Feedback Channel (PSFCH).

16. The initiating device as claimed in claim 14, wherein: The multitransmission NACK applies to the plurality of transmissions scheduled to be carried on the data channel within a specific time period.

17. The originating device of claim 16, wherein the specific time duration is a number of frames, a number of subframes, or a number of time slots.

18. The initiating device as claimed in claim 16, The processor, the transceiver, and / or the memory are configured to determine which of the plurality of transmissions to retransmit based on the feedback condition of the multitransmission NACK.

19. The initiating device of claim 18, wherein the plurality of feedback scenarios include: This indicates that the multiple transmissions in the group of unsuccessfully received transmissions are the first feedback scenario of transmissions carried on a specific sub-channel of the data channel. A second feedback scenario indicates that the plurality of transmissions in the group of unsuccessfully received transmissions are transmissions delivered at a specific time segment. A third feedback scenario indicates that the multiple transmissions in the group of unsuccessfully received transmissions are transmissions associated with a specific source identity (ID). A fourth feedback scenario indicates that the multiple transmissions in the group of unsuccessfully received transmissions are transmissions associated with a specific destination ID. The fifth feedback scenario indicates that the plurality of transmissions in the group of unsuccessfully received transmissions are transmissions associated with an originator ID that uniquely identifies the originating device. The sixth feedback scenario indicates that the multiple transmissions in the group of unsuccessfully received transmissions are transmissions associated with a specific originating group. A seventh feedback scenario indicates that the plurality of transmissions in the group of unsuccessfully received transmissions are transmissions associated with a target ID that uniquely identifies the target device, and The eighth feedback scenario indicates that the plurality of transmissions in the group of unsuccessfully received transmissions are transmissions associated with a specific target group of a group of receiving devices that are the intended recipients of the plurality of transmissions.

20. The initiating device as claimed in claim 14, The multi-transmission NACK is mapped to feedback channel resources based on the common characteristics of the multiple transmissions in the unsuccessfully received transmission group, and The processor, the transceiver, and / or the memory are configured to determine which of the plurality of transmissions to retransmit based on the feedback channel resources used to carry the multitransmission NACK.

21. The initiating device of claim 20, wherein the common characteristic is any one or more of the following: Specific sub-channel, specific time segmentation, specific source ID, specific destination ID, specific originator ID, specific originator group, specific target ID, and / or specific target group.

22. The originating device of claim 20, wherein the multiple transmission NACK and another multiple transmission NACK are mapped to the same feedback channel resource, wherein the other multiple transmission NACK is generated by the target device or another target device.

23. The originating device of claim 22, wherein the processor, the transceiver, and / or the memory are configured to further determine which of the plurality of transmissions to retransmit based on the sequence of the multitransmission NACKs.

24. The originating device of claim 14, wherein the multitransmission NACK is received on a feedback channel resource shared by the target device and one or more other target devices.

25. The originating device of claim 24, wherein the processor, the transceiver, and / or the memory are configured to identify the target device for retransmission based on the sequence of multitransmission NACKs.

26. The originating device of claim 24, wherein the processor, the transceiver, and / or the memory are configured to: The source ID and / or destination ID of multiple messages in the unsuccessfully received transmission group are identified based on the sequence of multi-transmission NACKs; and The source ID and / or the destination ID are used to determine which of the several transmissions should be retransmitted.

27. A method for a target apparatus, the method comprising: Receive control information from one or more originating devices, the control information indicating resource scheduling for carrying data channels from the one or more originating devices and intended for use by the target device; Based on the control information, the system listens on the data channel to locate the plurality of transmissions; as well as In the Negative Acknowledgment Only (NACK) mode, a multitransmission NACK is sent to the one or more originating devices on the feedback channel to notify the one or more originating devices of a group of unsuccessfully received transmissions, the group of unsuccessfully received transmissions including multiple transmissions that were not successfully received at the target device when listening on the data channel, and the multitransmission NACK is a single feedback, wherein the multitransmission NACK corresponds to one of multiple feedback scenarios, each feedback scenario indicating a common characteristic of the multiple transmissions in the group of unsuccessfully received transmissions.

28. The method of claim 27, The multi-transmission NACK is mapped to feedback channel resources based on the common characteristics of the multiple transmissions in the unsuccessfully received transmission group, and Sending the multitransmission NACK includes sending the multitransmission NACK on the feedback channel resources mapped to the multitransmission NACK.

29. A method for using a starting device, the method comprising: Send control information to the target device, the control information instructing resource scheduling for several data channels carrying data from the originating device and intended for use by the target device; The plurality of transmissions are transmitted on the data channel; In the Negative Acknowledgment Only (NACK) mode, multiple transmission NACKs are received from the target device on the feedback channel. The multiple transmission NACKs notify the originating device of a group of transmissions that were not successfully received. The group of transmissions that were not successfully received at the target device when listening on the data channel includes multiple transmissions of several transmissions that were not successfully received at the target device. The multiple transmission NACKs are a single feedback. as well as When the multitransmission NACK is received, at least the plurality of transmissions in the group of unsuccessfully received transmissions are retransmitted on the data channel, wherein the multitransmission NACK corresponds to one of a plurality of feedback scenarios, each feedback scenario indicating a common characteristic of the plurality of transmissions in the group of unsuccessfully received transmissions.

Images