Feedback information transmission method and communication apparatus

Abstract

A feedback information transmission method and a communication apparatus. In a dedicated resource pool for a sidelink positioning reference signal (SLPRS), a terminal device can send feedback information of the SLPRS to a network device, so that the network device can flexibly schedule or configure an SLPRS resource. The method may comprise: generating feedback information, which feedback information is used for indicating the sending state of at least one SLPRS, wherein the sending state may indicate that the SLPRS is sent successfully, the sending of the SLPRS fails, the SLPRS has been sent, or the SLPRS has not been sent; and sending the feedback information to a network device. If the feedback information is acknowledgement information, the network device may temporarily not schedule or configure the SLPRS resource for the terminal device; or if the feedback information is negative acknowledgement information, the network device may adjust a scheduling policy or a configuration policy of the SLPRS resource.

Description

Feedback information transmission method and communication device

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on November 3, 2023, with application number 202311466899.1 and application name “Feedback Information Transmission Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The embodiments of the present application relate to the field of communication technology, and in particular to a feedback information transmission method and a communication device. Background Art

[0003] Sidelink (SL) is a near-field communication technology that allows direct information connection between terminal devices via a PC5 interface. SL communication supports hybrid automatic repeat request (HARQ) technology. For example, after terminal device A sends data to terminal device B based on base station scheduling, terminal device B uses the physical sidelink feedback channel (PSFCH) to feedback to terminal device A whether the data is successfully received. Terminal device A then feeds back a HARQ response (HARQ-ACK) or a HARQ negative acknowledgement (HARQ-NACK) to the base station based on the feedback information. If the base station receives a HARQ-NACK, indicating that data transmission has failed, the base station can continue to allocate SL resources for data transmission to terminal device A to improve the reliability of data transmission.

[0004] For application scenarios such as vehicle to everything (V2X) and the industrial internet of things (IIoT), the 3rd Generation Partnership Project (3GPP) has proposed SL positioning, which can be achieved by transmitting a sidelink positioning reference signal. For example, two terminal devices can achieve mutual positioning, such as ranging or angle measurement, by sending a sidelink positioning reference signal. The sidelink positioning reference signal can also be simply referred to as a sidelink positioning reference signal.

[0005] In SL positioning, after terminal device A sends a side positioning reference signal to terminal device B, terminal device B will not feedback to terminal device A through PSFCH whether the side positioning reference signal is successfully received. Therefore, whether terminal device A feedbacks HARQ-ACK or HARQ-NACK to the base station is a technical problem that needs to be solved urgently.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide a feedback information transmission method and a communication device, which can enable a terminal device to send feedback information of a sidelink positioning reference signal to a network device, so that the network device can flexibly schedule or configure sidelink positioning reference signal resources.

[0008] In a first aspect, embodiments of the present application provide a method for transmitting feedback information. This method can be executed by a terminal device, or by a device compatible with the terminal device, such as a processor, chip, or chip system. The method can include: generating feedback information indicating the transmission status of at least one sidelink positioning reference signal; and transmitting the feedback information to a network device. By transmitting the feedback information to the network device, the network device can flexibly schedule or configure sidelink positioning reference signal resources based on the feedback information.

[0009] The feedback information may be sent to the network device via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).

[0010] In one possible implementation, one of the at least one sidelink positioning reference signals is successfully transmitted, generating feedback information, which is acknowledgement information. The acknowledgement information indicates that the transmission status of the at least one sidelink positioning reference signal is successful. That is, when one of the at least one sidelink positioning reference signal is successfully transmitted, the terminal device generates acknowledgement information and reports the acknowledgement information. Another possibility is that one of the at least one sidelink positioning reference signal is successfully transmitted at least once during multiple transmissions, and the acknowledgement information is reported. Consequently, based on the acknowledgement information, the network device may temporarily refrain from scheduling or configuring sidelink positioning reference signal resources for the terminal device.

[0011] In one possible implementation, if one of the at least one sidelink positioning reference signals fails to be transmitted, feedback information is generated, which is negative acknowledgement information. The negative acknowledgement information indicates that the transmission status of the at least one sidelink positioning reference signal is a transmission failure. That is, if one of the at least one sidelink positioning reference signals fails to be transmitted, the terminal device generates negative acknowledgement information and reports the negative acknowledgement information. Another possibility is that if one of the at least one sidelink positioning reference signals fails to be transmitted at least once during multiple transmissions, the negative acknowledgement information is reported. The network device can then schedule or configure sidelink positioning reference signal resources for the terminal device based on the negative acknowledgement information.

[0012] In one possible implementation, if the at least one sidelink positioning reference signal fails to be transmitted, feedback information is generated. The feedback information is negative acknowledgement information, and the negative acknowledgement information indicates that the transmission status of the at least one sidelink positioning reference signal is a transmission failure. In other words, if the at least one sidelink positioning reference signal fails to be transmitted, the terminal device generates negative acknowledgement information. Another possibility is that if the at least one sidelink positioning reference signal fails to be transmitted multiple times, the terminal device generates negative acknowledgement information. The network device can then schedule or configure sidelink positioning reference signal resources for the terminal device based on the negative acknowledgement information.

[0013] In one possible implementation, feedback information is generated based on the successful or failed transmission of each of the at least one sidelink positioning reference signal. The feedback information includes acknowledgement information or negative acknowledgement information for each sidelink positioning reference signal. The acknowledgement information indicates a successful transmission status, while the negative acknowledgement information indicates a failed transmission status. Taking three sidelink positioning reference signals as an example, assuming that the first and second sidelink positioning reference signals fail to transmit and the third sidelink positioning reference signal successfully transmits, the feedback information includes negative acknowledgement information for the first sidelink positioning reference signal, negative acknowledgement information for the second sidelink positioning reference signal, and acknowledgement information for the third sidelink positioning reference signal. Consequently, the network device can schedule or configure sidelink positioning reference signal resources for the terminal device based on the acknowledgement information or negative acknowledgement information for each sidelink positioning reference signal.

[0014] In one possible implementation, feedback information is generated for a sidelink positioning reference signal based on each successful or failed transmission. The feedback information includes acknowledgment information or negative acknowledgment information for each sidelink positioning reference signal transmission. Acknowledgment information indicates a successful transmission, while negative acknowledgment information indicates a failed transmission. Taking three transmissions as an example, assuming the first and second sidelink positioning reference signal transmissions fail, and the third sidelink positioning reference signal transmission succeeds, the feedback information includes negative acknowledgment information for the first sidelink positioning reference signal transmission, negative acknowledgment information for the second sidelink positioning reference signal transmission, and acknowledgment information for the third sidelink positioning reference signal transmission. This allows the network device to schedule or configure sidelink positioning reference signal resources for the terminal device based on the acknowledgment information or negative acknowledgment information for each sidelink positioning reference signal transmission.

[0015] In one possible implementation, when the feedback information includes acknowledgment information or negative acknowledgment information for each sidelink positioning reference signal, the feedback information may also include a count value corresponding to the acknowledgment information or negative acknowledgment information for each sidelink positioning reference signal. Taking three sidelink positioning reference signals as an example, assuming that the first and second sidelink positioning reference signals fail to be transmitted, but the third sidelink positioning reference signal is successfully transmitted, the feedback information may also include a count value corresponding to the negative acknowledgment information for the first sidelink positioning reference signal, a count value corresponding to the negative acknowledgment information for the second sidelink positioning reference signal, and a count value corresponding to the acknowledgment information for the third sidelink positioning reference signal. This allows network devices to more flexibly schedule sidelink positioning reference signal resources.

[0016] In one possible implementation, when the feedback information includes acknowledgment information or negative acknowledgment information for each transmission of a sideline positioning reference signal, the feedback information may also include a count value corresponding to the acknowledgment information or negative acknowledgment information for each transmission of the sideline positioning reference signal. Taking three transmissions as an example, assuming that the first and second sideline positioning reference signal transmissions fail, and the third sideline positioning reference signal transmission succeeds, the feedback information may also include a count value corresponding to the negative acknowledgment information for the first sideline positioning reference signal transmission, a count value corresponding to the negative acknowledgment information for the second sideline positioning reference signal transmission, and a count value corresponding to the acknowledgment information for the third sideline positioning reference signal transmission. This allows network devices to more flexibly schedule sideline positioning reference signal resources.

[0017] In one possible implementation, feedback information is generated based on a first sidelink positioning reference signal that was successfully transmitted among the at least one sidelink positioning reference signal. The feedback information includes acknowledgement information for the first sidelink positioning reference signal, but does not include negative acknowledgement information for a sidelink positioning reference signal that failed to be transmitted. The acknowledgement information indicates that the transmission status of the first sidelink positioning reference signal is successful. Taking three sidelink positioning reference signals as an example, assuming that the first and second sidelink positioning reference signals fail to be transmitted, but the third sidelink positioning reference signal is successfully transmitted, the feedback information includes acknowledgement information for the third sidelink positioning reference signal, but does not include negative acknowledgement information for the first and second sidelink positioning reference signals. Consequently, the network device may temporarily refrain from scheduling or configuring sidelink positioning reference signal resources for the terminal device based on the acknowledgement information for the first sidelink positioning reference signal.

[0018] In one possible implementation, feedback information is generated based on the number of successful transmissions of a first sidelink positioning reference signal. The feedback information includes acknowledgement information for the number of successful transmissions of the first sidelink positioning reference signal, but does not include negative acknowledgement information for the number of failed transmissions. The acknowledgement information indicates that the transmission status of the first sidelink positioning reference signal is successful. Taking the three transmissions of the first sidelink positioning reference signal as an example, assuming that the first and second sidelink positioning reference signal transmissions fail, but the third sidelink positioning reference signal transmission succeeds, the feedback information includes acknowledgement information for the third transmission of the first sidelink positioning reference signal, but does not include negative acknowledgement information for the first and second sidelink positioning reference signal transmissions. Consequently, the network device can temporarily refrain from scheduling or configuring sidelink positioning reference signal resources for the terminal device based on the acknowledgement information for the first sidelink positioning reference signal.

[0019] In one possible implementation, when the feedback information includes response information of the first sidelink positioning reference signal, the feedback information may also include a count value corresponding to the response information of the first sidelink positioning reference signal, so that the network device knows which one or more positioning reference signals are successfully sent, or which transmission of a sidelink positioning reference signal is successfully sent, and can adjust the scheduling or configuration of the sidelink positioning reference signal.

[0020] In one possible implementation, feedback information is generated based on a second sidelink positioning reference signal that failed to be transmitted among the at least one sidelink positioning reference signal. The feedback information includes negative acknowledgement information for the second sidelink positioning reference signal, but does not include acknowledgement information for the successfully transmitted sidelink positioning reference signal. The negative acknowledgement information indicates that the transmission status of the second sidelink positioning reference signal is a transmission failure. Taking three sidelink positioning reference signals as an example, assuming that the first and second sidelink positioning reference signals fail to be transmitted, but the third sidelink positioning reference signal is successfully transmitted, the feedback information includes negative acknowledgement information for the first and second sidelink positioning reference signals, but does not include acknowledgement information for the third sidelink positioning reference signal. Consequently, the network device can schedule or configure sidelink positioning reference signal resources for the terminal device based on the negative acknowledgement information for the second sidelink positioning reference signal.

[0021] In one possible implementation, feedback information is generated based on the number of failed transmissions of the second sidelink positioning reference signal. The feedback information includes negative acknowledgment information for the number of failed transmissions of the second sidelink positioning reference signal, but does not include acknowledgment information for the number of successful transmissions. The negative acknowledgment information indicates that the transmission status of the second sidelink positioning reference signal is a transmission failure. Taking three transmissions of the second sidelink positioning reference signal as an example, assuming that the first and second sidelink positioning reference signal transmissions fail, and the third sidelink positioning reference signal transmission succeeds, the feedback information includes negative acknowledgment information for the first and second transmissions of the second sidelink positioning reference signal, but does not include acknowledgment information for the third transmission of the second sidelink positioning reference signal. Consequently, the network device can schedule or configure sidelink positioning reference signal resources for the terminal device based on the negative acknowledgment information for the second sidelink positioning reference signal.

[0022] In one possible implementation, when the feedback information includes response information of the first sidelink positioning reference signal, the feedback information may also include a count value corresponding to the response information of the first sidelink positioning reference signal, so that the network device knows which one or more positioning reference signals failed to be sent, or which transmission of a sidelink positioning reference signal failed, and can adjust the scheduling or configuration of the sidelink positioning reference signal.

[0023] In one possible implementation, if at least one of the sidelink positioning reference signals is not transmitted within the scheduled time, feedback information is generated. The feedback information is response information, indicating that the transmission status of the at least one sidelink positioning reference signal is not transmitted. In other words, if at least one scheduled sidelink positioning reference signal is not transmitted within the scheduled time, the terminal device generates and reports the response information. Based on the response information, the network device can temporarily not schedule or configure sidelink positioning reference signal resources for the terminal device.

[0024] Optionally, the at least one sidelink positioning reference signal is not transmitted within the scheduled time, and resources for the at least one sidelink positioning reference signal are transmitted to other terminal devices, generating a response message. That is, if the at least one scheduled sidelink positioning reference signal is not transmitted within the scheduled time, and the terminal device intends to allocate the at least one sidelink positioning reference signal resource to other terminal devices, the terminal device generates and reports the response message, so that the network device may temporarily not schedule or configure sidelink positioning reference signal resources for the terminal device based on the response message.

[0025] Optionally, if the at least one sidelink positioning reference signal is not transmitted within the scheduled time, and it is determined not to transmit a sidelink positioning reference signal resource request to the network device within a first time period, and the first time period is later than the scheduled time, then a response message is generated. That is, if the at least one sidelink positioning reference signal is not transmitted within the scheduled time, and the terminal device does not intend to request a sidelink positioning reference signal resource from the network device, then the terminal device generates and reports the response message, so that the network device may temporarily not schedule or configure sidelink positioning reference signal resources for the terminal device based on the response message.

[0026] Optionally, the at least one sidelink positioning reference signal is not transmitted within the scheduled time, and at least one sidelink positioning reference signal is transmitted within a second time period, generating response information. That is, if the at least one sidelink positioning reference signal is not transmitted within the scheduled time, but is transmitted at a time after the scheduled time, the terminal device generates and reports the response information, allowing the network device to temporarily refrain from scheduling or configuring sidelink positioning reference signal resources for the terminal device based on the response information. Optionally, in addition to the response information, the feedback information also includes the transmission time of the at least one sidelink positioning reference signal, so that the network device can receive the at least one sidelink positioning reference signal based on the transmission time.

[0027] In one possible implementation, based on the fact that at least one sidelink positioning reference signal has been transmitted, feedback information is generated, the feedback information being negative acknowledgment information, indicating that the transmission status of the at least one sidelink positioning reference signal is transmitted. That is, upon transmitting at least one sidelink positioning reference signal, the terminal device generates negative acknowledgment information and reports the negative acknowledgment information, so that the network device can schedule or configure sidelink positioning reference signal resources for the terminal device based on the negative acknowledgment information. It is understood that regardless of whether the transmission is successful or not, if the terminal device intends to request sidelink positioning reference signal resources again after transmission, a negative acknowledgment information is generated.

[0028] In one possible implementation, when a negative acknowledgement message is generated, a first sidelink positioning reference signal resource may be received from the network device. That is, when the terminal device feeds back a negative acknowledgement message, the network device may schedule or configure a new sidelink positioning reference signal resource, i.e., the first sidelink positioning reference signal resource, for the terminal device based on the negative acknowledgement message.

[0029] Optionally, in response to receiving the first sidelink positioning reference signal resource, the first sidelink positioning reference signal resource is sent to other terminal devices. That is, after sending at least one sidelink positioning reference signal, the terminal device intends to request a new sidelink positioning reference signal resource from the network device. The new sidelink positioning reference signal resource is used by the terminal device to allocate to other terminal devices, and a negative acknowledgement message is generated to obtain the new sidelink positioning reference signal resource.

[0030] In one possible implementation, the at least one sidelink positioning reference signal is a sidelink positioning reference signal scheduled by downlink control information (DCI), that is, a sidelink positioning reference signal scheduled in a dynamic scheduling manner. Alternatively, the at least one sidelink positioning reference signal is a sidelink positioning reference signal configured by radio resource control (RRC) signaling, that is, a sidelink positioning reference signal configured in a periodic configuration manner. Alternatively, the at least one sidelink positioning reference signal is a sidelink positioning reference signal configured by RRC signaling and scheduled by DCI, that is, a sidelink positioning reference signal scheduled in a semi-persistent scheduling manner.

[0031] In a second aspect, an embodiment of the present application provides a communication device, which may be a terminal device, a device in a terminal device, or a device that can be used in conjunction with a terminal device. The communication device may also be a chip system. The communication device may execute the method described in the first aspect. The functions of the communication device may be implemented by hardware or by hardware executing corresponding software implementations. The hardware or software includes one or more units or modules corresponding to the above functions. The units or modules may be software and / or hardware. The operations and beneficial effects performed by the communication device may refer to the method and beneficial effects described in the first aspect above.

[0032] In a third aspect, an embodiment of the present application provides a communication device, the communication device including a processor, and the processor is used to execute the method described in the first aspect.

[0033] In a fourth aspect, an embodiment of the present application provides a communication device, which includes a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the program or instruction is executed by the processor, the communication device executes the method described in the first aspect.

[0034] In one possible implementation, the communication device further includes a memory. Optionally, the processor and the memory are integrated together. Optionally, the memory and the processor are independently provided.

[0035] In a fifth aspect, an embodiment of the present application provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method described in the first aspect through a logic circuit or executing code instructions.

[0036] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is executed by a communication device, the method described in the first aspect is implemented.

[0037] In a seventh aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when a communication device reads and executes the instructions, enables the communication device to execute the method described in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] FIG1 is a schematic diagram of an SL resource pool;

[0039] FIG2A is a schematic diagram of the feedback process of SL communication in the dynamic scheduling mode 1;

[0040] FIG2B is an example timing diagram corresponding to FIG2A ;

[0041] FIG3 is a schematic diagram of a network architecture using an embodiment of the present application;

[0042] FIG4 is a flow chart of a feedback information transmission method provided in an embodiment of the present application;

[0043] FIG5 is a schematic diagram of feedback information provided by an embodiment of the present application indicated by a bit map;

[0044] FIG6 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0045] FIG7 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0046] In this application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit differences. "And / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0047] It should be understood that, in this application, "at least one" refers to one or more, and "a plurality" refers to two or more. Furthermore, in this application, "equal to" can be used in conjunction with "greater than" or "less than." When "equal to" and "greater than" are used together, the technical solution of "greater than" is adopted; when "equal to" and "less than" are used together, the technical solution of "less than" is adopted.

[0048] In this application, "sending information to... (e.g., a terminal device)" can be understood as the destination of the information being the terminal device. This can include sending information to the terminal device directly or indirectly. "Receiving information from... (e.g., a terminal device)" or "receiving information from... (e.g., a terminal device)" can be understood as the source of the information being the terminal device, which can include receiving information from the terminal device directly or indirectly. The information may be processed as necessary between the source and destination of the information, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood similarly and will not be elaborated on here.

[0049] The following first explains the relevant names or terms involved in this application to facilitate understanding by those skilled in the art.

[0050] 1. Terminal Equipment

[0051] Terminal devices can also be called user equipment (UE), mobile station (MS), mobile terminal (MT), etc. They are devices used to provide voice or data connectivity to users, or they can be IoT devices. For example, terminal devices include handheld devices with wireless connectivity, in-vehicle devices, etc. Currently, terminal devices can include: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices (such as smart watches, smart bracelets, pedometers, etc.), vehicle-mounted devices (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), satellite terminals, virtual reality (VR) devices, augmented reality (AR) devices, smart point-of-sale (POS) machines, customer-premises equipment (CPE), wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminals in unmanned driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, and flying devices (such as intelligent robots, hot air balloons, drones, airplanes). Terminal devices can also be other devices with terminal functions, for example, terminal devices can also be devices that function as terminals in D2D communication.

[0052] 2. Network Equipment

[0053] A network device is a node in a radio access network (RAN), and can also be referred to as an access network device or a RAN node (or device). A network device is used to help terminal devices achieve wireless access. In one possible scenario, a network device can be a base station, an evolved NodeB (eNodeB), a transmitting and receiving point (TRP), a transmitting point (TP), a next-generation NodeB (gNB), a next-generation base station in a 6G system, a base station in a future mobile communication system, a satellite, an integrated access and backhaul (IAB) node, a mobile switching center, or an access network device in a non-terrestrial network (NTN) communication system, that is, it can be deployed on a high-altitude platform or satellite. A network device can be a macro base station, a micro base station or an indoor station, a relay node or a donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. A network device can also be a device that acts as a base station in device-to-device (D2D) communication, Internet of Vehicles (IoV) communication, drone communication, or machine communication. Alternatively, a network device can be a server, wearable device, vehicle, or vehicle-mounted device. For example, a network device in vehicle-to-everything (V2X) technology can be a roadside unit (RSU).

[0054] All or part of the functions of the network device in this application may also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform). The network device in this application may also be a logical node, logical module, or software that can implement all or part of the network device functions.

[0055] In another possible scenario, multiple network devices collaborate to assist the terminal in achieving wireless access, and different network devices respectively implement part of the functions of the base station. For example, the network device can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). It can be understood that the network device can be a CU node, a DU node, or a device including a CU node and a DU node. In addition, the CU can be divided into a network device in the access network RAN, or the CU can be divided into a network device in the core network CN, which is not limited here.

[0056] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in an open access network (open RAN, O-RAN or ORAN) system, CU may also be called O-CU (open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application takes CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0057] 3. Side Positioning Reference Signal

[0058] The positioning reference signal (PRS) is a known signal provided by the transmitting end to the receiving end for positioning. In the embodiment of the present application, a side positioning reference signal is used to describe the reference signal transmitted between terminal devices, or between a terminal device and a roadside unit (RSU), for realizing the positioning function. The positioning function can be realized by transmitting the side positioning reference signal between terminal devices. The full name of the side positioning reference signal is the sidelink positioning reference signal (SL PRS), and SLPRS can also be described as SL-PRS or SPRS, etc. It should be noted that with the evolution of the standard, the positioning reference signal between terminal devices may adopt other names. For the sake of convenience of description, the embodiment of the present application uses SLPRS to describe the side positioning reference signal, and uses SLPRS resources to describe the side positioning reference signal resources. SLPRS resources are used to transmit SLPRS.

[0059] 4. Resource Pool

[0060] A resource pool is broadly defined as a collection of resources. In this application, a resource pool refers to a sidelink (SL) resource pool, and an SL resource pool can be understood as a collection of SL resources.

[0061] For example, please refer to the schematic diagram of the SL resource pool shown in Figure 1. In Figure 1, in a carrier bandwidth (carrier bandwidth), part of the bandwidth (bandwidth part, BWP) is allocated to the SL for use, and the BWP allocated to the SL for use can be called SLBWP. The time-frequency resources corresponding to the SLBWP can be further divided into multiple SL resource pools, and each SL resource pool can be configured with independent channels, such as the physical sidelink control channel (PSCCH) or the physical sidelink shared channel (PSSCH) and other channels. Each SL resource pool performs independent perception and resource allocation. The frequency domain resources in the SL resource pool can be further divided into sub-channels with finer granularity, and resource allocation and data transmission are based on sub-channels, for example, allocating one or multiple consecutive sub-channels, or performing data transmission on one or multiple consecutive sub-channels. A sub-channel can include multiple physical resource blocks (PRBs). A sub-channel can also be used to represent specific frequency domain location information.

[0062] The embodiments of the present application relate to an SLPRS-specific resource pool, which may be the above-mentioned SL resource pool. However, the resources in the SL resource pool are used to transmit SLPRS and PSCCH, but not to transmit PSSCH.

[0063] For SL resources, there are two ways to allocate resources: Mode 1, allocated by the base station, mainly for UEs within the coverage area of ​​the base station; Mode 2, UEs reserve SL resources through perception. For Mode 1, the scheduling method can be dynamic scheduling (Dynamic grant), periodic configuration (i.e. Configured Grant Type 1) or semi-static scheduling (i.e. Configured Grant Type 2). Among them, the dynamic scheduling method is implemented through DCI indication; the periodic scheduling method is implemented through RRC signaling pre-configuration; the semi-static scheduling method is implemented through RRC signaling pre-configuration combined with DCI indication.

[0064] 5. Feedback Mechanism of SL Communication in Mode 1

[0065] Data and control information transmission in SL communications supports the HARQ mechanism. For example, after the transmitter sends SL data to the receiver, the receiver provides feedback to the transmitter indicating whether the SL data was successfully received. Based on the receiver's feedback, the transmitter then provides a HARQ-ACK or HARQ-NACK to the base station. SL data transmission supports the HARQ mechanism in all scheduling modes of Mode 1.

[0066] For example, see the feedback process of SL communication in the dynamic scheduling mode of Mode 1 shown in FIG2A . In FIG2A , UE A is used as a transmitting UE (i.e., TxUE) and UE B is used as a receiving UE (i.e., Rx UE). The feedback process may include the following steps:

[0067] 1. The UEA sends a scheduling request (SR) to the base station. The base station receives the SR from the UEA. If the UEA has data to send but no available resources, it can send an SR to the base station via the PUCCH.

[0068] 2. The base station sends DCI to the UEA. Correspondingly, the UEA receives the DCI from the base station. In response to the SR, the base station sends DCI to the UEA via the physical downlink control channel (PDCCH). The DCI is used to schedule SL resources, which are used by the UEA to send PSCCH and PSSCH to other UEs, for example, for the UEA to send PSCCH and PSSCH to UEB. DCI is also used to schedule PUCCH resources, which are used by the UEA to feedback SL HARQ to the base station.

[0069] 3. UEA sends the PSCCH and PSSCH to UEB. In return, UEB receives the PSCCH and PSSCH from UEA. UEA sends the PSCCH and PSSCH to UEB using the scheduled SL resources.

[0070] 4. UEB sends SLHARQ to UEA. Correspondingly, UEA receives SLHARQ from UEB. UEB sends SLHARQ to UEA via the physical sidelink feedback channel (PSFCH). If SLHARQ is HARQ-ACK, it means that UEB successfully received PSCCH and PSSCH; if SLHARQ is HARQ-NACK, it means that UEB failed to receive PSCCH and PSSCH, such as decoding failure.

[0071] 5. UEA sends a SLHARQ to the base station. The base station receives the SLHARQ from UEA. UEA sends the SLHARQ to the base station via the PUCCH resources scheduled by DCI. If UEA receives a HARQ-ACK from UEB, it sends a HARQ-ACK back to the base station, indicating that the data was successfully received. If UEA receives a HARQ-ACK from UEB, it sends a HARQ-ACK back to the base station, indicating that the data reception failed.

[0072] Figure 2A is a flowchart of the feedback process under the dynamic scheduling mode, and its corresponding timing can be seen in Figure 2B. In Figure 2B, UEA receives RRC signaling from the base station through the Uu port. The RRC signaling is used to configure the SL-BWP resource pool, that is, the above-mentioned SL resource pool. When the UEA has data to be sent to other UEs but there are no available resources, it can send an SR to the base station through the PUCCH. In response to the SR, the base station sends a DCI to the UEA. The DCI is used to indicate the time interval and time-frequency resources. The time interval refers to the time interval (e.g., time slot interval) between the receipt of the DCI and the first transmission of the PSCCH and PSSCH; the time-frequency resources refer to the SL resources, which are used to transmit the PSCCH and PSSCH. The DCI also includes the minimum time interval between the SL resources and the PSFCH. The PSFCH is used by the UEA to receive the SLHARQ from the UEB. The DCI also includes a PSFCH-to-HARQ field, which is used to indicate the time interval (e.g., time slot interval) between the PSFCH and the HARQ. The HARQ refers to the SLHARQ fed back by the UEA to the base station. It can be understood that the UEA uses the time slot where the PSFCH is located as a reference and, based on the time interval indicated by the PSFCH-to-HARQ field, determines the time slot (or the time slot described as the PUCCH carrying SLHARQ) for feeding back SLHARQ to the base station, so that the UEA feeds back SL HARQ to the base station on this time slot. For example, the time slot where the PSFCH is located is time slot i, and the time interval indicated by the PSFCH-to-HARQ field is j, then UE A feeds back SLHARQ to the base station on time slot i+j.

[0073] Figures 2A and 2B take the feedback process of SL communication in the dynamic scheduling mode of mode 1 as an example. For the feedback process of SL communication in the periodic configuration mode and semi-static scheduling mode of mode 1, UEB will also feedback SL HARQ to UEA, and UEA will feedback SL HARQ to the base station based on the content fed back by UEB.

[0074] However, for SLPRS, when UEB receives SLPRS from UEA, it does not need to demodulate SLPRS and can directly measure SLPRS. Therefore, UEB does not need to feedback SLHARQ to UEA. In addition, the SLPRS dedicated resource pool does not transmit PSSCH, so the above SL communication feedback process is not applicable to SLPRS feedback in the SLPRS dedicated resource pool. Therefore, whether UEA should feedback SLHARQ to the base station is a technical issue that needs to be solved urgently.

[0075] In view of this, an embodiment of the present application provides a feedback information transmission method and a communication device, which can enable a terminal device to send SLPRS feedback information to a network device, so that the network device can flexibly schedule or configure SLPRS resources. The embodiment of the present application clarifies that the terminal device sends SLPRS feedback information to the network device, and clarifies under what circumstances HARQ-ACK is fed back, under what circumstances HARQ-NACK is fed back, and under what circumstances HARQ-ACK and HARQ-NACK are fed back. For the convenience of description, the embodiment of the present application uses ACK to describe the response information, i.e., HARQ-ACK; and uses NACK to describe the negative response information, i.e., HARQ-NACK.

[0076] Before describing the feedback information transmission method provided in the embodiment of the present application, the network architecture and scenarios for applying the embodiment of the present application are explained.

[0077] Please refer to Figure 3, which is a schematic diagram of a network architecture applying an embodiment of the present application. The network architecture shown in Figure 3 may include a network device 301 and a terminal device 302, and optionally, further includes a terminal device 303. The device form and number of devices shown in Figure 3 are for example only and do not constitute a limitation on the embodiments of the present application. Figure 3 takes the case where the terminal device 302 is within the coverage of the network device 301 as an example, that is, the terminal device 302 can receive messages or signaling from the network device 301, such as DCI and / or RRC signaling.

[0078] Illustratively, under the control of the network device 301, the terminal device 302 may send an SLPRS to the terminal device 303; upon receiving the SLPRS, the terminal device 303 may measure the distance or angle by measuring the SLPRS, thereby obtaining a measurement result.

[0079] In this embodiment of the present application, terminal device 302 may generate SLPRS-related feedback information and send the feedback information to network device 301. The feedback information may include an ACK but not a NACK; alternatively, the feedback information may include a NACK but not an ACK; alternatively, the feedback information may include both an ACK and a NACK. Based on the feedback information, network device 301 may flexibly schedule or configure SLPRS resources for terminal device 302.

[0080] Based on whether the terminal device 303 is within the coverage of the network device 301, the scenario in which the embodiment of the present application is applied may be:

[0081] In scenario 1, terminal device 303 is within the coverage of network device 301. Terminal devices 302 and 303 can communicate with network device 301 via the Uu port. Terminal devices 302 and 303 can communicate via the PC5 port. Under the control of network device 301, terminal device 302 can send an SL PRS to terminal device 303; and under the control of network device 301, terminal device 303 can send an SL PRS to terminal device 302.

[0082] In scenario 2, terminal device 303 is outside the coverage of network device 301. Terminal device 302 can communicate with network device 301 via the Uu port, but terminal device 303 cannot. Terminal device 303 communicates with terminal device 302 via the PC5 port. Under the control of network device 301, terminal device 302 sends an SL PRS to terminal device 303.

[0083] The embodiment of the present application is applicable to the dynamic scheduling mode, periodic configuration mode and semi-static scheduling mode under Mode 1. In the SLPRS dedicated resource pool, the reporting of SLPRS-related feedback information can be realized, so that the network device can flexibly schedule or configure SLPRS resources.

[0084] Based on the network architecture shown in Figure 3, the feedback information transmission method provided in the embodiment of the present application is described in detail below. For ease of description, the terminal device is taken as an example of a UE, and the network device is taken as an example of a gNB.

[0085] Please refer to FIG4 , which is a flowchart of a feedback information transmission method provided in an embodiment of the present application. The method may include but is not limited to the following steps:

[0086] 401. The UE generates feedback information, where the feedback information is used to indicate a sending status of at least one SL PRS.

[0087] Among them, at least one SLPRS can be an SLPRS scheduled by DCI, that is, an SLPRS dynamically scheduled by DCI. For example, DCI dynamically schedules 3 SLPRSs. At least one SLPRS can also be an SLPRS configured by RRC signaling, that is, an SLPRS configured in a periodic configuration manner. At least one SLPRS can also be an SLPRS configured by RRC signaling and scheduled by DCI, that is, an SLPRS scheduled in a semi-static scheduling manner. That is, after RRC signaling configuration, DCI indicates the activated or deactivated SLPRS. The SLPRS scheduled by DCI refers to the SLPRS carried by the SLPRS resource indicated or activated by DCI. The SLPRS configured by RRC signaling refers to the SLPRS carried by the SLPRS resource configured by RRC signaling. At least one SLPRS refers to at least one SLPRS carried by at least one SLPRS resource, and one SLPRS resource carries one SLPRS. For an SLPRS resource, the SLPRS it carries can be sent once or multiple times on the SLPRS resource.

[0088] In one implementation, the feedback information may be an ACK or a NACK. For example, if the feedback information is an ACK, the ACK may indicate that the transmission status of at least one SLPRS is successfully transmitted. For another example, if the feedback information is a NACK, the NACK may indicate that the transmission status of at least one SLPRS is failed to transmit. For another example, if the feedback information is an ACK, the ACK may indicate that the transmission status of at least one SLPRS is not transmitted. For another example, if the feedback information is a NACK, the NACK may indicate that the transmission status of at least one SLPRS is transmitted.

[0089] In another implementation, the feedback information may include an ACK or NACK for at least one SLPRS, where one ACK corresponds to one SLPRS and one NACK corresponds to one SLPRS. For example, taking three SLPRSs as an example, if the first SLPRS fails to be sent, the second SLPRS fails to be sent, and the third SLPRS is successfully sent, then the feedback information may include a NACK for the first SLPRS, a NACK for the second SLPRS, and an ACK for the third SLPRS.

[0090] In another implementation, the feedback information may include an ACK for a successfully transmitted SLPRS, but not include a NACK for an unsuccessfully transmitted SLPRS. For example, taking three SLPRSs as an example, if the first SLPRS fails to be transmitted, the second SLPRS fails to be transmitted, and the third SLPRS is successfully transmitted, then the feedback information includes an ACK for the third SLPRS, but not include a NACK for the first SLPRS and a NACK for the second SLPRS.

[0091] In another implementation, the feedback information may include a NACK for the SLPRS that failed to be sent, but not an ACK for the SLPRS that was successfully sent. For example, taking three SLPRSs as an example, if the first SLPRS fails to be sent, the second SLPRS fails to be sent, and the third SLPRS is successfully sent, then the feedback information includes the NACK for the first SLPRS and the NACK for the second SLPRS, but not the ACK for the third SLPRS.

[0092] 402. The UE sends feedback information to the gNB.

[0093] The UE may send feedback information to the gNB via the PUCCH or PUSCH, so that the gNB can schedule or configure SLPRS resources based on the feedback information. The UE may send feedback information later than the SLPRS transmission time. The timing of sending the feedback information is not limited in this embodiment. For example, when dynamically scheduling SLPRS resources, the DCI may indicate the time slot in which the UE sends the feedback.

[0094] In the embodiment shown in Figure 4, the UE generates feedback information indicating the transmission status of at least one SLPRS and reports the feedback information to the gNB, so that the gNB can flexibly schedule or configure SLPRS resources based on the feedback information. For example, if the feedback information is an ACK, the gNB may temporarily not schedule or configure SLPRS resources for the UE. For another example, if the feedback information is a NACK, the gNB may reschedule or reconfigure SLPRS resources for the UE.

[0095] Based on the content of the feedback information, it can be divided into the following situations:

[0096] In case 1, the sending status of at least one SLPRS is successfully sent, and only one ACK is fed back.

[0097] If at least one of the at least one SLPRS is successfully transmitted, the UE generates an ACK and transmits it back to the gNB. The ACK indicates that the transmission status of the at least one SLPRS is successful. It should be understood that regardless of whether dynamic or semi-persistent scheduling is used for scheduling one or multiple SLPRSs, an ACK is generated and reported as long as at least one SLPRS is successfully transmitted. Regardless of the number of periodically configured SLPRSs, an ACK is generated and reported as long as at least one of the SLPRSs is successfully transmitted. If more than one of the at least one SLPRS is successfully transmitted, the UE also generates and reports an ACK.

[0098] If at least one SLPRS fails to be sent, the UE does not generate a NACK and does not report a NACK.

[0099] For example, taking three SLPRSs as an example, assuming that the first SLPRS fails to be sent, the second SLPRS fails to be sent, and the third SLPRS is sent successfully, the UE generates and reports an ACK; assuming that all three SLPRSs fail to be sent, the UE neither generates nor reports a NACK.

[0100] Optionally, the ACK feedback is related to the number of transmissions. If at least one of the multiple transmissions of at least one SLPRS is successful, the UE generates and reports an ACK. In other words, for a particular SLPRS, as long as at least one of its multiple transmissions is successful, the SLPRS is considered to be successfully transmitted, and an ACK is generated and reported.

[0101] For example, for a certain SLPRS, assuming that the number of transmissions is 3, the first and second transmissions fail, and the third transmission succeeds, then the UE generates and reports an ACK.

[0102] In case 2, the transmission status of at least one SLPRS is transmission failure, and only one NACK is fed back.

[0103] In one implementation, if one of at least one SLPRS fails to transmit, the UE generates a NACK and reports it back to the gNB. The NACK indicates that the transmission status of the at least one SLPRS is a transmission failure. It should be understood that regardless of whether one or multiple SLPRSs are scheduled using dynamic or semi-persistent scheduling, a NACK is generated and reported if at least one SLPRS fails to transmit. Regardless of the number of periodically configured SLPRSs, a NACK is generated and reported if at least one of the SLPRSs fails to transmit. The UE also generates and reports a NACK if more than one of the at least one SLPRS fails to transmit. If all at least one SLPRSs are successfully transmitted, the UE does not generate or report a NACK.

[0104] For example, taking three SLPRSs as an example, assuming that the first SLPRS fails to be sent, the second SLPRS fails to be sent, and the third SLPRS is sent successfully, the UE generates and reports a NACK; assuming that all three SLPRSs are sent successfully, the UE neither generates nor reports an ACK.

[0105] Optionally, the NACK feedback is related to the number of transmissions. If at least one of the multiple transmissions of at least one SLPRS fails, the UE generates and reports a NACK. In other words, for a particular SLPRS, if at least one of its multiple transmissions fails, the SLPRS is considered to have failed, and a NACK is generated and reported.

[0106] For example, for a certain SLPRS, assuming that it is sent three times, the first and second transmissions fail, and the third transmission succeeds, then the UE generates and reports a NACK.

[0107] In another implementation, if at least one SLPRS message fails to be transmitted, the UE generates a negative acknowledgement (NACK) and sends it back to the gNB. The NACK indicates that the transmission status of at least one SLPRS message failed. If at least one of the at least one SLPRS messages is successfully transmitted, the UE does not generate or report an ACK.

[0108] For example, taking three SLPRSs as an example, assuming that all three SLPRSs fail to be sent, the UE generates and reports a NACK; assuming that the first SLPRS fails to be sent, the second SLPRS fails to be sent, and the third SLPRS is sent successfully, the UE neither generates nor reports an ACK.

[0109] Optionally, the NACK fed back is related to the number of transmissions. If one of at least one SLPRS fails to be transmitted multiple times, the UE generates and reports a NACK. In other words, if multiple transmissions of a certain SLPRS fail, the SLPRS is considered to have failed, and a NACK is generated and reported.

[0110] For example, for a certain SLPRS, assuming that the number of transmission times is 3 and all the 3 transmissions fail, the UE generates and reports a NACK.

[0111] In case three, the sending status of at least one SLPRS is sending success, and an ACK is fed back; the sending status of at least one SLPRS is sending failure, and a NACK is fed back.

[0112] If one of the at least one SLPRSs is successfully transmitted, the UE generates an ACK and sends it back to the gNB. The ACK indicates that the transmission status of the at least one SLPRS is successful. It should be understood that regardless of whether one or multiple SLPRSs are scheduled using dynamic or semi-persistent scheduling, an ACK is generated and reported as long as at least one of the SLPRSs is successfully transmitted. Regardless of the number of periodically configured SLPRSs, an ACK is generated and reported as long as at least one of the SLPRSs is successfully transmitted. If more than one of the at least one SLPRSs is successfully transmitted, the UE also generates and reports an ACK. Optionally, the ACK sent back is related to the number of transmissions. If at least one of the multiple transmissions of one of the at least one SLPRSs is successfully transmitted, the UE generates and reports an ACK. In other words, for a particular SLPRS, as long as at least one of its multiple transmissions is successfully transmitted, the SLPRS is considered successfully transmitted, and an ACK is generated and reported.

[0113] If at least one SLPRS fails to transmit, the UE generates and reports a NACK, indicating that the transmission status of the at least one SLPRS is a transmission failure. Optionally, the NACK fed back is related to the number of transmissions. If one of the at least one SLPRS fails to transmit multiple times, the UE generates and reports a NACK. In other words, if multiple transmissions of a particular SLPRS fail, the SLPRS is considered to have failed, and a NACK is generated and reported.

[0114] That is, if at least one of the SLPRS messages is successfully transmitted, ACK is reported; otherwise, NACK is reported.

[0115] For example, taking three SLPRSs as an example, assuming that the first SLPRS fails to be sent, the second SLPRS fails to be sent, and the third SLPRS is sent successfully, the UE generates and reports an ACK; assuming that all three SLPRSs fail to be sent, the UE generates and reports a NACK.

[0116] Case 4: Feedback ACK or NACK for each SLPRS.

[0117] Based on the transmission status of each SLPRS in at least one SLPRS, feedback information is generated and reported, and the feedback information includes ACK or NACK for each SLPRS. ACK indicates that the transmission status is successful, and NACK indicates that the transmission status is failed.

[0118] For example, taking three SLPRSs as an example, assuming that the first SLPRS fails to send, the second SLPRS fails to send, and the third SLPRS is successfully sent, then the feedback information may include NACK for the first SLPRS (indicating that the first SLPRS fails to send), NACK for the second SLPRS (indicating that the second SLPRS fails to send), and ACK for the third SLPRS (indicating that the third SLPRS is successfully sent). Optionally, the feedback information may be indicated in the form of a bitmap. For example, see the bitmap shown in FIG5 . The bitmap takes "001" as an example to indicate NACK-NACK-ACK, i.e., the first SLPRS is NACK, the second SLPRS is NACK, and the third SLPRS is ACK.

[0119] Optionally, in addition to including the ACK or NACK for each SLPRS message, the feedback information may also include a count corresponding to each ACK or NACK for each SLPRS message, used to identify the SLPRS resource carrying each SLPRS message. For example, taking three SLPRS resources as an example, assuming that the SLPRS message carried by the first SLPRS resource fails to transmit, the SLPRS message carried by the second SLPRS resource fails to transmit, and the SLPRS message carried by the third SLPRS resource succeeds, the feedback information may be represented as {NACK-0, NACK-1, ACK-2}, meaning that the SLPRS message carried by the first SLPRS resource is NACK, the SLPRS message carried by the second SLPRS resource is NACK, and the SLPRS message carried by the third SLPRS resource is ACK. The feedback information also includes a count corresponding to each ACK or NACK for each SLPRS message, allowing the gNB to understand the correspondence between ACKs and SLPRS resources, and between NACKs and SLPRS resources, which facilitates more efficient resource coordination and scheduling in subsequent resource scheduling.

[0120] In case 4, the feedback information includes an ACK or NACK for each SLPRS in at least one SLPRS. Optionally, feedback information can be generated and reported separately for each SLPRS. Taking three SLPRS as an example, assuming that the first SLPRS fails to be sent, the second SLPRS fails to be sent, and the third SLPRS is successfully sent, then three pieces of feedback information can be generated and sent separately. The first feedback information is a NACK for the first SLPRS, the second feedback information is a NACK for the second SLPRS, and the third feedback information is an ACK for the third SLPRS.

[0121] Optionally, for one SLPRS among at least one SLPRS, its feedback information is related to the number of times it is transmitted. Feedback information is generated based on the success or failure of each SLPRS transmission, and the feedback information includes an ACK or NACK for each SLPRS transmission. Taking three transmissions as an example, assuming the first and second transmissions fail and the third transmission succeeds, the feedback information may include a NACK for the first transmission, a NACK for the second transmission, and an ACK for the third transmission. Optionally, the feedback information may also include a count value corresponding to the ACK or NACK for each SLPRS transmission. For example, for an SLPRS carried on a certain SLPRS resource, its feedback information may be represented as {NACK-0, NACK-1, ACK-2}, i.e., a NACK for the first transmission of the SLPRS, a NACK for the second transmission of the SLPRS, and an ACK for the third transmission of the SLPRS. Furthermore, the feedback information reported by the UE may include feedback information for each SLPRS, and the feedback information for each SLPRS may include an ACK or NACK for each transmission.

[0122] Case 5: Feedback of the ACK of the successfully sent SLPRS.

[0123] The successfully transmitted SLPRS among the at least one SLPRS is referred to as a first SLPRS. The feedback information generated and reported by the UE includes an ACK for the first SLPRS. An ACK is used to indicate that the transmission status of the corresponding first SLPRS is successful. It is understood that the UE only reports ACKs for successfully transmitted SLPRS and does not report NACKs for unsuccessfully transmitted SLPRS. The number of first SLPRSs may be one or more, depending on the specific situation.

[0124] For example, taking three SLPRS messages as an example, assuming that the first SLPRS message fails to be sent, the second SLPRS message fails to be sent, and the third SLPRS message is successfully sent, the feedback information may include an ACK for the third SLPRS message, but not include NACKs for the first and second SLPRS messages. Optionally, the feedback information may be indicated in the form of a bitmap, for example, see the bitmap shown in FIG5 , in which "001" is used as an example to indicate that the third SLPRS message is ACK.

[0125] Optionally, in addition to the ACK for the first SLPRS, the feedback information may also include a count value corresponding to the ACK for the first SLPRS, which is used to mark the SLPRS resource carrying the successfully transmitted SLPRS. For example, taking three SLPRS resources as an example, assuming that the SLPRS carried by the first SLPRS resource fails to be transmitted, the SLPRS carried by the second SLPRS resource fails to be transmitted, and the SLPRS carried by the third SLPRS resource is successfully transmitted, then the feedback information may be expressed as {ACK-2}, that is, the SLPRS carried by the third SLPRS resource is ACK.

[0126] If there are multiple first SLPRSs, the UE may optionally generate multiple pieces of feedback information and report each piece of feedback information separately, with one piece of feedback information corresponding to an ACK of the first SLPRS.

[0127] Optionally, for a first SLPRS, its feedback information is related to the number of times it is sent. Feedback information is generated based on the number of successful first SLPRS transmissions. The feedback information includes ACKs for the number of successful transmissions of the first SLPRS, but does not include NACKs for the number of failed transmissions. Taking three transmissions as an example, assuming that the first and second transmissions fail and the third transmission is successful, then the feedback information may include an ACK for the third transmission of the first SLPRS, but does not include NACKs for the first and second transmissions of the first SLPRS. Optionally, the feedback information may also include a count value corresponding to the ACK or NACK for each transmission of the first SLPRS. For example, for a certain first SLPRS, its feedback information may be expressed as {ACK-2}, that is, an ACK for the third transmission of the first SLPRS.

[0128] Case 6: Feedback of NACK of the SLPRS that failed to be sent.

[0129] The SLPRS message that fails to be sent among the at least one SLPRS message is referred to as a second SLPRS message. The feedback information generated and reported by the UE includes a NACK for the second SLPRS message. A NACK message indicates that the corresponding second SLPRS message has failed to be sent. It is understood that the UE only reports the NACK message for the SLPRS message that fails to be sent, and does not report the ACK message for the SLPRS message that is successfully sent. The number of the second SLPRS messages may be one or more, depending on the specific situation.

[0130] For example, taking three SLPRS messages as an example, assuming that the first SLPRS message fails to be sent, the second SLPRS message fails to be sent, and the third SLPRS message is successfully sent, the feedback information may include a NACK for the first SLPRS message and a NACK for the second SLPRS message, but not an ACK for the third SLPRS message. Optionally, the feedback information may be indicated in the form of a bitmap. For example, see the bitmap shown in FIG5 . The bitmap uses "001" as an example to indicate that the first SLPRS message is NACK and the second SLPRS message is NACK.

[0131] Optionally, in addition to including the NACK for the second SLPRS, the feedback information may also include a count value corresponding to the NACK for the second SLPRS, which is used to mark the SLPRS resource carrying the SLPRS that failed to send. For example, taking three SLPRS resources as an example, assuming that the SLPRS carried by the first SLPRS resource fails to send, the SLPRS carried by the second SLPRS resource fails to send, and the SLPRS carried by the third SLPRS resource is successfully sent, then the feedback information can be expressed as {NACK-0, NACK-1}, that is, the SLPRS carried by the first and second SLPRS resources are NACKs.

[0132] If there are multiple second SLPRSs, the UE may optionally generate multiple pieces of feedback information and report each piece of feedback information respectively, with one piece of feedback information corresponding to a NACK of the second SLPRS.

[0133] Optionally, for a second SLPRS, its feedback information is related to the number of times it is sent. Feedback information is generated based on the number of times the second SLPRS fails to be sent. The feedback information includes NACKs for the number of failed transmissions of the second SLPRS, but does not include ACKs for the number of successful transmissions. Taking three transmissions as an example, assuming that the first and second transmissions fail and the third transmission is successful, then the feedback information may include NACKs for the first and second transmissions of the second SLPRS, but does not include an ACK for the third transmission of the second SLPRS. Optionally, the feedback information may also include a count value corresponding to the ACK or NACK for each transmission of the second SLPRS. For example, for a certain second SLPRS, its feedback information may be expressed as {NACK-0, NACK-1}, that is, NACKs for the first and second transmissions of the second SLPRS.

[0134] The above cases 1 to 6 can all be understood as the UE sending at least one SLPRS within the scheduling time.

[0135] Case 7: No SLPRS is sent and an ACK is fed back.

[0136] If at least one SLPRS is not transmitted within the scheduled time, the UE generates and reports an ACK indicating that the transmission status of the at least one SLPRS is not transmitted. The scheduled time can be the time when the DCI schedules the transmission of the at least one SLPRS, the time when the SLPRS is periodically transmitted as configured by RRC signaling, or the time when the DCI schedules the transmission of an activated SLPRS. It is understood that if the gNB schedules the UE to transmit at least one SLPRS within the scheduled time, but the UE does not transmit the SLPRS within the scheduled time, the UE generates and reports an ACK, so that the gNB temporarily does not schedule or configure SLPRS resources for the UE.

[0137] Optionally, if at least one SLPRS signal is not transmitted within the scheduled time and at least one SLPRS resource is transmitted to another UE, the UE generates and reports an ACK. Transmitting at least one SLPRS resource to another UE, for example, UE A transmitting at least one SLPRS resource to UE B or UE C, can be understood as the UE allocating at least one SLPRS resource to another UE for use, and the other UE transmits SLPRS on these resources. Transmitting at least one SLPRS resource to another UE can be performed before or after generating and reporting an ACK.

[0138] Optionally, if at least one SLPRS signal is not transmitted within the scheduled time, and the UE determines not to send an SLPRS resource request to the gNB within a first time period, where the first time period is later than the scheduled time, then the UE generates and reports an ACK. That is, if at least one SLPRS signal is not transmitted within the scheduled time and the UE does not intend to request SLPRS resources from the gNB, then the UE generates and reports an ACK. It is understood that if the UE does not transmit at least one SLPRS signal within the scheduled time and does not intend to request SLPRS resources from the gNB, then the UE generates and reports an ACK.

[0139] Optionally, if at least one SLPRS message is not sent within the scheduled time, and at least one SLPRS message is sent within the second time period, an ACK is generated and reported. That is, if at least one SLPRS message is not sent within the scheduled time, but at least one SLPRS message is sent at a time after the scheduled time, the UE generates and reports an ACK. For example, the second time period may be a time window that starts at the feedback time of the feedback information or at the scheduled time of the last SLPRS message. The UE may send some or all of the at least one SLPRS message within this time window. The size of the time window may be predefined by the protocol.

[0140] Optionally, if at least one SLPRS is not transmitted within the scheduled time, and at least one SLPRS is transmitted after the second time period, an ACK is generated and reported. That is, if at least one SLPRS is not transmitted within the scheduled time, but at least one SLPRS is transmitted at a time after the scheduled time, the UE generates and reports an ACK. For example, the start time of the second time period may be the feedback time of the feedback information, the scheduling time of the last SLPRS, or the time when DCI is received. After the second time period, the UE transmits some or all of the at least one SLPRS. The duration of the second time period may be predefined by the protocol.

[0141] If the SLPRS is sent at a time after the scheduled time, the feedback information may include the SLPRS transmission time in addition to the ACK, so that the gNB can receive the SLPRS based on this time.

[0142] Case 8: SLPRS is sent and a NACK is fed back.

[0143] If the UE has transmitted at least one SLPRS, it generates and reports a NACK, which indicates that the transmission status of the at least one SLPRS is "sent." The UE has transmitted at least one SLPRS, which means that the UE has transmitted at least one SLPRS within the scheduled time. It is understood that regardless of whether the at least one SLPRS is successfully transmitted, as long as the UE has transmitted at least one SLPRS, the UE generates and reports a NACK. Alternatively, regardless of whether the transmission is successful, as long as the UE has transmitted at least one SLPRS and intends to request SLPRS resources again, the UE generates and reports a NACK.

[0144] Optionally, when a NACK is reported, the gNB may receive a first SLPRS resource from the gNB. That is, in response to the NACK, the gNB sends the first SLPRS resource to the UE. The first SLPRS resource may be a dynamically scheduled SLPRS resource, a periodically configured SLPRS resource, or a semi-persistently scheduled SLPRS resource. The gNB sending the first SLPRS resource to the UE in response to the NACK also applies to the NACK feedback scenarios described in Cases 2 and 3 above.

[0145] Optionally, in response to receiving the first SLPRS resource, the UE transmits the first SLPRS resource to other UEs. That is, after transmitting at least one SLPRS, the UE intends to request new SLPRS resources from the gNB for allocation to other UEs. The UE generates and reports a NACK. Optionally, the first SLPRS resource is used by the UE to transmit the SLPRS again.

[0146] It should be noted that the above cases 1 to 8 are for example only and do not constitute a limitation on the embodiments of the present application. For example, it may be defined that ACK and / or NACK may be fed back in certain circumstances.

[0147] The present application provides a communication device that can be used to implement the functions of the above-mentioned UE. The communication device can be a UE. The communication device includes a unit that corresponds one-to-one to the method / operation / step / action performed by the UE in the above-mentioned method embodiment. The unit can be a hardware circuit, or software, or a combination of a hardware circuit and software. Please refer to Figure 6, which shows a structural diagram of a communication device 600 in an embodiment of the present application. The communication device 600 may include an interface unit 601 and a processing unit 602. Specifically, the processing unit 602 is used to process signaling and / or data, and the signaling and / or data may be data received by the interface unit 601, and the processed signaling and / or data may also be sent by the interface unit 601;

[0148] In one embodiment, when the communication device 600 is a UE, wherein:

[0149] The processing unit 602 is configured to generate feedback information, where the feedback information is used to indicate a transmission status of at least one sidelink positioning reference signal;

[0150] The interface unit 601 is configured to send feedback information to the network device.

[0151] In this embodiment, for the specific implementation of the above-mentioned interface unit 601 and processing unit 602, reference may be made to the specific implementation steps of the UE in FIG4 , which will not be repeated here.

[0152] FIG7 shows a communication device 700 provided in an embodiment of the present application, configured to implement the aforementioned UE functionality. The device may be a communication device or a device used in a communication device, and the communication device may be a UE. The device used in a communication device may be a chip system or chip within the communication device. The chip system may consist of a chip alone, or may include a chip and other discrete components.

[0153] The communication device 700 includes at least one processor 710 for implementing the processing function of the device (e.g., UE or network device) in the method provided in the embodiment of the present application. The communication device 700 may also include a communication interface 720 for implementing the transceiver operation of the device (e.g., UE or network device) in the method provided in the embodiment of the present application. In the embodiment of the present application, the communication interface may be a transceiver, a circuit, a bus, a module, or other type of communication interface for communicating with other devices via a transmission medium. For example, the communication interface 720 is used for the device in the communication device 700 to communicate with other devices. The processor 710 uses the communication interface 720 to send and receive data and is used to implement the method described in the above method embodiment.

[0154] The communication device 700 may also include at least one memory 730 for storing program instructions and / or data. The memory 730 is coupled to the processor 710. Coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. The processor 710 may operate in conjunction with the memory 730. The processor 710 may execute program instructions stored in the memory 730. At least one of the at least one memory may be included in the processor.

[0155] The specific connection medium between the communication interface 720, processor 710, and memory 730 is not limited in the embodiments of the present application. In Figure 7, the memory 730, processor 710, and communication interface 720 are connected via a bus. The bus is represented by a bold line in Figure 7. The connection between other components is only for schematic illustration and is not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one bold line is used in Figure 7, but this does not mean that there is only one bus or one type of bus.

[0156] When the communication device 700 is specifically a device for a device (such as a UE or a network device), for example, when the communication device 700 is specifically a chip or a chip system, the communication interface 720 may output or receive a baseband signal. When the communication device 700 is specifically a device (such as a UE or a network device), the communication interface 720 may output or receive a radio frequency signal. In an embodiment of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0157] It should be noted that the communication interface 720 may be used to execute the functions of the interface unit 601 , and the processor 710 may be used to execute the functions of the processing unit 602 , which will not be described in detail here.

[0158] When the above-mentioned communication device is a chip applied to UE, the chip implements the function of the UE in the above-mentioned method embodiment, and the chip receives information from other devices; or the chip sends information to other devices.

[0159] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0160] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, mobile hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in an access network device or a terminal. Of course, the processor and storage medium can also exist as discrete components in a terminal or access network device.

[0161] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instruction can be stored in a computer-readable storage medium or transmitted via the computer-readable storage medium. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, a hard disk, or a tape; it can also be an optical medium, such as a DVD; it can also be a semiconductor medium, such as a solid state drive (SSD).

[0162] In the various embodiments of the present application, unless otherwise specified or there is any logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0163] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

[0164] An embodiment of the present application further provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed, the method executed by the UE or network device in the above method embodiment is implemented.

[0165] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed, the method performed by the UE or network device in the above method embodiment is implemented.

[0166] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0167] The descriptions of the various embodiments provided in this application can refer to each other. The descriptions of each embodiment have their own focus. For parts not described in detail in a particular embodiment, please refer to the relevant descriptions of other embodiments. For the convenience and brevity of description, for example, the functions and execution steps of the various devices and equipment provided in the embodiments of this application can refer to the relevant descriptions of the method embodiments of this application. The various method embodiments and the various device embodiments can also refer to, be combined with, or quote each other.

[0168] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A feedback information transmission method, characterized in that: include: generating feedback information, where the feedback information is used to indicate a sending status of at least one side positioning reference signal; The feedback information is sent to the network device.

2. The method according to claim 1, characterized in that The generating feedback information comprises: There is a side channel positioning reference signal among the at least one side channel positioning reference signal that is sent successfully, and feedback information is generated. The feedback information is response information, and the response information indicates that the sending status of the at least one side channel positioning reference signal is successfully sent.

3. The method according to claim 1, characterized in that The generating feedback information comprises: There is a side positioning reference signal in the at least one side positioning reference signal that fails to be sent, and feedback information is generated. The feedback information is negative acknowledgement information, and the negative acknowledgement information indicates that the sending status of the at least one side positioning reference signal is a sending failure.

4. The method according to claim 1, characterized in that The generating feedback information comprises: The at least one side positioning reference signal fails to be sent, and feedback information is generated. The feedback information is negative acknowledgement information. The negative acknowledgement information indicates that the sending status of the at least one side positioning reference signal is a sending failure.

5. The method according to claim 1, characterized in that The generating feedback information comprises: Based on the success or failure of sending each side positioning reference signal in the at least one side positioning reference signal, feedback information is generated, and the feedback information includes response information or negative response information of each side positioning reference signal, the response information indicates that the sending status is successful sending, and the negative response information indicates that the sending status is failed sending.

6. The method according to claim 5, characterized in that The feedback information also includes a count value corresponding to the response information or negative response information of each sideline positioning reference signal.

7. The method according to claim 1, characterized in that The generating feedback information comprises: Based on a first sidelink positioning reference signal that is successfully sent among the at least one sidelink positioning reference signal, feedback information is generated, the feedback information including response information of the first sidelink positioning reference signal, the response information indicating that the sending status of the first sidelink positioning reference signal is successful.

8. The method according to claim 7, characterized in that The feedback information also includes a count value corresponding to the response information of the first sideline positioning reference signal.

9. The method according to claim 1, characterized in that The generating feedback information comprises: Based on a second sidelink positioning reference signal that fails to be sent among the at least one sidelink positioning reference signal, feedback information is generated, the feedback information including negative acknowledgement information of the second sidelink positioning reference signal, and the negative acknowledgement information is used to indicate that the sending status of the second sidelink positioning reference signal is a sending failure.

10. The method according to claim 9, characterized in that The feedback information also includes a count value corresponding to negative acknowledgement information of the second sideline positioning reference signal.

11. The method according to claim 1, characterized in that The generating feedback information comprises: The at least one side positioning reference signal is not sent within the scheduling time, and feedback information is generated. The feedback information is response information, and the response information indicates that the sending status of the at least one side positioning reference signal is not sent.

12. The method according to claim 11, characterized in that The method further comprises: Sending resources of the at least one side positioning reference signal to other terminal devices; Alternatively, it is determined not to send a sidewalk positioning reference signal resource request to the network device within a first time period, and the first time period is later than the scheduling time.

13. The method according to claim 11, characterized in that The method further comprises: The at least one sideways positioning reference signal is sent within a second time period.

14. The method according to claim 13, characterized in that The feedback information also includes the sending time of the at least one sidelink positioning reference signal.

15. The method according to claim 1, wherein: The generating feedback information comprises: Based on the fact that the at least one side positioning reference signal has been sent, feedback information is generated, where the feedback information is negative acknowledgement information, and the negative acknowledgement information indicates that the sending status of the at least one side positioning reference signal is sent.

16. The method according to claim 3, 4 or 15, characterized in that The method further comprises: A first sideline positioning reference resource is received from the network device.

17. The method according to claim 15, characterized in that The method further comprises: The first sideline positioning reference resource is sent to other terminal devices.

18. The method according to any one of claims 1 to 17, characterized in that: The at least one sidelink positioning reference signal is a sidelink positioning reference signal scheduled by downlink control information; or, the at least one sidelink positioning reference signal is a sidelink positioning reference signal configured by wireless resource control signaling; or, the at least one sidelink positioning reference signal is a sidelink positioning reference signal configured by wireless resource control signaling and scheduled by downlink control information.

19. A communication device, characterized in that: Comprising means for executing the method as claimed in any one of claims 1 to 18.

20. A communication device, characterized in that: The device comprises a processor, wherein the processor is configured to implement the method according to any one of claims 1 to 18 through logic circuits and / or by executing computer programs or instructions.

21. The communication device according to claim 20, characterized in that: Also includes: The memory is used to store the computer program or instructions.

22. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in any one of claims 1 to 18 through a logic circuit or executing code instructions.

23. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or an instruction. When the computer program or the instruction is executed by the communication device, the method according to any one of claims 1 to 18 is implemented.

Images