Feedback information transmission method and communication device

By introducing feedback information transmission method of terminal devices to network devices in SL positioning, the problem of lack of feedback mechanism in SL positioning is solved, effective feedback and resource scheduling of the transmission status of the side-direction positioning reference signal is realized, and the reliability of data transmission is improved.

CN119945631APending Publication Date: 2025-05-06HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311466899.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-11-03
Publication Date
2025-05-06

AI Technical Summary

Technical Problem

In SL positioning, after the terminal device A sends a side-row positioning reference signal to the terminal device B, there is a lack of a feedback mechanism, so that the terminal device A cannot effectively feedback HARQ-ACK or HARQ-NACK to the base station.

Method used

A feedback information transmission method is provided, which generates and sends feedback information to a network device through a terminal device, indicating the transmission status of the side-line positioning reference signal. The feedback information may be a response information (ACK) or a negative response information (NACK) to indicate whether the signal is successfully received.

Benefits of technology

The feedback information transmission of terminal equipment to network equipment is realized, so that network equipment can flexibly schedule or configure side-direction positioning reference signal resources to improve the reliability of data transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119945631A_ABST
    Figure CN119945631A_ABST
Patent Text Reader

Abstract

According to the feedback information transmission method and the communication device, in a sidelink positioning reference signal (SLPRS) exclusive resource pool, a terminal device can send feedback information of the SLPRS to a network device, so that the network device can flexibly schedule or configure SLPRS resources. The method may comprise the following steps: generating feedback information, wherein the feedback information is used for indicating a sending state of at least one SLPRS; the sending state can be sending success, sending failure, sent or not sent; and sending the feedback information to the network equipment. The feedback information is response information, and the network equipment can temporarily not schedule or configure the SLPRS resources for the terminal equipment; the feedback information is negative response information, and the network equipment can adjust a scheduling strategy or a configuration strategy of the SLPRS resources.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] 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

[0002] Sidelink (SL) is a near-field communication technology that directly connects terminal devices to each other through 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 the scheduling of the base station, terminal device B feedbacks to terminal device A whether the data is successfully received through the physical sidelink feedback channel (PSFCH). Terminal device A feedbacks HARQ response (HARQ-acknowledgement, HARQ-ACK) or HARQ negative response (HARQ-negative acknowledgement, HARQ-NACK) to the base station based on the feedback information. If the base station receives HARQ-NACK, it means that the 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.

[0003] For application scenarios such as vehicle to everything (V2X) and industrial internet of things (IIoT), the 3rd generation partnership project (3GPP) 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 referred to as a sidelink positioning reference signal.

[0004] 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 feeds back HARQ-ACK or HARQ-NACK to the base station is a technical problem that needs to be solved urgently. Summary of the invention

[0005] 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 side positioning reference signal to a network device, so that the network device can flexibly schedule or configure side positioning reference signal resources.

[0006] In a first aspect, an embodiment of the present application provides a feedback information transmission method, which can be executed by a terminal device, or by a device matching the terminal device, such as a processor, a chip, or a chip system. The method may include: generating feedback information, the feedback information is used to indicate the transmission status of at least one side positioning reference signal; sending the feedback information to a network device. By sending the feedback information to the network device, the network device can flexibly schedule or configure the side positioning reference signal resources based on the feedback information.

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

[0008] In a possible implementation, one of the at least one side positioning reference signal is successfully sent, 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 successfully sent. That is to say, one of the at least one side positioning reference signal is successfully sent, and the terminal device generates response information and reports the response information. Another possibility is that one of the at least one side positioning reference signal is successfully sent in multiple transmissions, and the response information is reported. Therefore, the network device can temporarily not schedule or configure the side positioning reference signal resources for the terminal device based on the response information.

[0009] In a possible implementation, one of the at least one side positioning reference signals fails to be sent, and feedback information is generated, the feedback information is negative acknowledgment information, and the negative acknowledgment information indicates that the sending status of the at least one side positioning reference signal is a sending failure. That is to say, if one of the at least one side positioning reference signal fails to be sent, the terminal device generates negative acknowledgment information and reports the negative acknowledgment information. Another possibility is that one of the at least one side positioning reference signal fails to be sent at least once in multiple transmissions, and the negative acknowledgment information is reported. Therefore, the network device can schedule or configure the side positioning reference signal resources for the terminal device based on the negative acknowledgment information.

[0010] In a possible implementation, the at least one side positioning reference signal fails to be sent, and feedback information is generated, the feedback information is negative acknowledgment information, and the negative acknowledgment information indicates that the sending state of the at least one side positioning reference signal is a sending failure. That is, once the at least one side positioning reference signal fails to be sent, the terminal device generates negative acknowledgment information. Another possibility is that once the at least one side positioning reference signal fails to be sent in multiple transmissions, the terminal device generates negative acknowledgment information. Thereby, the network device can schedule or configure the side positioning reference signal resources for the terminal device based on the negative acknowledgment information.

[0011] In a possible implementation, feedback information is generated based on the success or failure of each side positioning reference signal in the at least one side positioning reference signal, and the feedback information includes response information or negative response information of each side positioning reference signal, the response information indicates that the transmission status is successful, and the negative response information indicates that the transmission status is failed. Taking three side positioning reference signals as an example, assuming that the first and second side positioning reference signals fail to be transmitted, and the third side positioning reference signal is successfully transmitted, then the feedback information includes negative response information of the first side positioning reference signal, negative response information of the second side positioning reference signal, and response information of the third side positioning reference signal. Therefore, the network device can schedule or configure the side positioning reference signal resources for the terminal device based on the response information or negative response information of each side positioning reference signal.

[0012] In a possible implementation, for a sideline positioning reference signal, feedback information is generated based on each successful or failed transmission, and the feedback information includes response information or negative response information for each transmission of the sideline positioning reference signal, the response information indicates that the transmission status is successful, and the negative response information indicates that the transmission status is failed. Taking three transmissions as an example, assuming that the first and second transmissions of the sideline positioning reference signal fail, and the third transmission of the sideline positioning reference signal succeeds, then the feedback information includes negative response information for the first transmission of the sideline positioning reference signal, negative response information for the second transmission of the sideline positioning reference signal, and response information for the third transmission of the sideline positioning reference signal. Thus, the network device can schedule or configure the sideline positioning reference signal resources for the terminal device based on the response information or negative response information for each transmission of the sideline positioning reference signal.

[0013] In a possible implementation, when the feedback information includes the response information or negative response information of each side positioning reference signal, the feedback information may also include the count value corresponding to the response information or negative response information of each side positioning reference signal. Taking three side positioning reference signals as an example, assuming that the first and second side positioning reference signals fail to be sent, and the third side positioning reference signal is sent successfully, the feedback information may also include the count value corresponding to the negative response information of the first side positioning reference signal, the count value corresponding to the negative response information of the second side positioning reference signal, and the count value corresponding to the response information of the third side positioning reference signal. Thus, the network device can schedule the side positioning reference signal resources more flexibly.

[0014] In a possible implementation, in the case where the feedback information includes the response information or negative response information of each transmission of the sideline positioning reference signal, the feedback information may also include the count value corresponding to the response information or negative response information of each transmission of the sideline positioning reference signal. Taking three transmissions as an example, assuming that the first and second transmissions of the sideline positioning reference signal fail, and the third transmission of the sideline positioning reference signal succeeds, the feedback information may also include the count value corresponding to the negative response information of the first transmission of the sideline positioning reference signal, the count value corresponding to the negative response information of the second transmission of the sideline positioning reference signal, and the count value corresponding to the response information of the third transmission of the sideline positioning reference signal. Thus, the network device can schedule the sideline positioning reference signal resources more flexibly.

[0015] In a possible implementation, feedback information is generated based on the first sideline positioning reference signal that is successfully sent among the at least one sideline positioning reference signal, and the feedback information includes response information of the first sideline positioning reference signal, but does not include negative response information of the sideline positioning reference signal that fails to be sent, and the response information indicates that the sending status of the first sideline positioning reference signal is successfully sent. Taking three sideline positioning reference signals as an example, assuming that the first and second sideline positioning reference signals fail to be sent, and the third sideline positioning reference signal is successfully sent, then the feedback information includes the response information of the third sideline positioning reference signal, but does not include negative response information of the first and second sideline positioning reference signals. Therefore, the network device can temporarily not schedule or configure the sideline positioning reference signal resources for the terminal device based on the response information of the first sideline positioning reference signal.

[0016] In a possible implementation, feedback information is generated based on the number of times the first sideline positioning reference signal is successfully sent, and the feedback information includes response information of the number of times the first sideline positioning reference signal is successfully sent, but does not include negative response information of the number of times the first sideline positioning reference signal is failed to be sent, and the response information indicates that the sending status of the first sideline positioning reference signal is successfully sent. Taking the three times of sending the first sideline positioning reference signal as an example, assuming that the first and second times the sideline positioning reference signal is sent unsuccessfully, and the third time the sideline positioning reference signal is sent successfully, then the feedback information includes response information of the third time the first sideline positioning reference signal is sent, but does not include negative response information of the first and second times the first sideline positioning reference signal is sent. Therefore, the network device may temporarily not schedule or configure the sideline positioning reference signal resources for the terminal device based on the response information of the first sideline positioning reference signal.

[0017] In one possible implementation, when the feedback information includes response information of a 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 sent successfully, or which transmission of a sidelink positioning reference signal is sent successfully, and can adjust the scheduling or configuration of the sidelink positioning reference signal.

[0018] In a possible implementation, feedback information is generated based on the second sideline positioning reference signal that fails to be sent among the at least one sideline positioning reference signal, and the feedback information includes negative acknowledgment information of the second sideline positioning reference signal, but does not include acknowledgment information of the successfully sent sideline positioning reference signal, and the negative acknowledgment information indicates that the sending status of the second sideline positioning reference signal is a sending failure. Taking three sideline positioning reference signals as an example, assuming that the first and second sideline positioning reference signals fail to be sent, and the third sideline positioning reference signal is sent successfully, then the feedback information includes negative acknowledgment information of the first and second sideline positioning reference signals, but does not include acknowledgment information of the third sideline positioning reference signal. Thus, the network device can schedule or configure the sideline positioning reference signal resources for the terminal device based on the negative acknowledgment information of the second sideline positioning reference signal.

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

[0020] In one possible implementation, when the feedback information includes response information of a 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 positioning reference signal or 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.

[0021] In a possible implementation, if the at least one side positioning reference signal is not sent within the scheduling time, feedback information is generated, and the feedback information is response information, and the response information indicates that the sending state of the at least one side positioning reference signal is not sent. That is to say, if the at least one scheduled side positioning reference signal is not sent within the scheduling time, the terminal device generates response information and reports the response information. Therefore, the network device can temporarily not schedule or configure the side positioning reference signal resources for the terminal device based on the response information.

[0022] Optionally, the at least one side positioning reference signal is not sent within the scheduling time, and the resources of the at least one side positioning reference signal are sent to other terminal devices, and a response message is generated. That is to say, if the at least one scheduled side positioning reference signal is not sent within the scheduling time, and the terminal device intends to allocate the resources of the at least one side positioning reference signal to other terminal devices, then the terminal device generates a response message and reports the response message, so that the network device can temporarily not schedule or configure the side positioning reference signal resources for the terminal device based on the response information.

[0023] Optionally, the at least one side positioning reference signal is not sent within the scheduling time, and it is determined not to send a side 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, and a response message is generated. That is to say, if at least one side positioning reference signal is not sent within the scheduling time, and the terminal device does not intend to request a side positioning reference signal resource from the network device, then the terminal device generates a response message and reports the response message, so that the network device can temporarily not schedule or configure a side positioning reference signal resource for the terminal device based on the response information.

[0024] Optionally, the at least one side positioning reference signal is not sent within the scheduling time, and at least one side positioning reference signal is sent within the second time period to generate a response message. That is to say, if at least one side positioning reference signal is not sent within the scheduling time, but at least one side positioning reference signal is sent at a time after the scheduling time, then the terminal device generates a response message and reports the response message, so that the network device can temporarily not schedule or configure the side 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 sending time of at least one side positioning reference signal, so that the network device receives at least one side positioning reference signal based on the time.

[0025] In a possible implementation, based on the fact that at least one side positioning reference signal has been sent, feedback information is generated, and the feedback information is negative acknowledgment information, and the negative acknowledgment information indicates that the sending status of at least one side positioning reference signal is sent. That is, in the case of sending at least one side 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 the side positioning reference signal resources for the terminal device based on the negative acknowledgment information. It can be understood that regardless of whether the sending is successful or not, in the case of sending, if the terminal device intends to request the side positioning reference signal resources again, then a negative acknowledgment information is generated.

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

[0027] Optionally, in response to the received first side positioning reference signal resource, the first side positioning reference signal resource is sent to other terminal devices. That is, in the case of sending at least one side positioning reference signal, the terminal device intends to request a new side positioning reference signal resource from the network device, and the new positioning reference signal resource is used by the terminal device to allocate to other terminal devices, and a negative response message is generated to obtain the new side positioning reference signal resource.

[0028] In a 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-static scheduling manner.

[0029] In a second aspect, an embodiment of the present application provides a communication device, which may be a terminal device, or a device in a terminal device, or a device that can be used in combination with a terminal device. Among them, 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 unit or module 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.

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

[0031] In a fourth aspect, an embodiment of the present application provides a communication device, comprising a processor, the processor being coupled to a memory, the memory being used to store programs or instructions, and when the programs or instructions are executed by the processor, the communication device executes the method described in the first aspect.

[0032] In a 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 configured.

[0033] 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.

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

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

[0036] Figure 1 It is a schematic diagram of a SL resource pool;

[0037] Figure 2A It is a schematic diagram of the feedback process of SL communication under the dynamic scheduling method of mode 1;

[0038] Figure 2B yes Figure 2A The corresponding timing example diagram;

[0039] Figure 3 is a schematic diagram of a network architecture to which an embodiment of the present application is applied;

[0040] Figure 4 It is a flowchart of a feedback information transmission method provided in an embodiment of the present application;

[0041] Figure 5 It is a schematic diagram of feedback information provided by an embodiment of the present application indicated by a bit map;

[0042] Figure 6 is a structural diagram of a communication device provided in an embodiment of the present application;

[0043] Figure 7 It is a structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0044] In the present 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 them to be different. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previously associated objects are in an "or" relationship.

[0045] It should be understood that in this application, "at least one" means one or more; "plurality" means two or more. In addition, "equal to" in this application can be used in conjunction with "greater than" or "less than". When "equal to" is used in conjunction with "greater than", the technical solution of "greater than" is adopted; when "equal to" is used in conjunction with "less than", the technical solution of "less than" is adopted.

[0046] In the present 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 the present application can be understood similarly and will not be repeated here.

[0047] The following is an explanation of the relevant names or terms involved in this application to facilitate understanding by those skilled in the art.

[0048] 1. Terminal equipment

[0049] Terminal equipment can also be called user equipment (UE), mobile station (MS), mobile terminal (MT), etc., or equipment used to provide voice or data connectivity to users, or IoT devices. For example, terminal equipment includes handheld devices with wireless connection functions, vehicle-mounted devices, etc. At present, terminal devices can be: mobile phones, tablet computers, laptops, PDAs, mobile internet devices (MID), 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, TVs, air conditioners, electric meters, etc.), smart 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, or wireless terminals in smart homes, flight equipment (such as smart robots, hot air balloons, drones, airplanes), etc. The terminal device can also be other devices with terminal functions, for example, the terminal device can also be a device that serves as a terminal function in D2D communication.

[0050] 2. Network equipment

[0051] The network device is a node in the radio access network (RAN), which can also be called an access network device, or a RAN node (or device). The network device is used to help terminal devices achieve wireless access. In one possible scenario, the 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, an access network device in a mobile switching center non-terrestrial network (NTN) communication system, that is, it can be deployed on a high altitude platform or satellite, etc. The 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. The network device may also be a device that acts as a base station in device-to-device (D2D) communication, Internet of Vehicles communication, drone communication, and machine communication. Optionally, the network device may also be a server, a wearable device, a vehicle or an onboard device, etc. For example, the network device in vehicle to everything (V2X) technology may be a road side unit (RSU).

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

[0053] 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 may 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 may be set separately, or may be included in the same network element, such as a baseband unit (BBU). The RU may 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 is understandable that the network device may be a CU node, a DU node, or a device including a CU node and a DU node. In addition, the CU may be divided into a network device in the access network RAN, or the CU may be divided into a network device in the core network CN, without limitation here.

[0054] 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, CU, CU-CP, CU-UP, DU and RU are described as examples in this application. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0055] 3. Side Positioning Reference Signal

[0056] The positioning reference signal (PRS) is a known signal provided by the transmitter to the receiver for positioning. The embodiment of the present application uses a side positioning reference signal to describe a 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 a side positioning reference signal between terminal devices. The full name of the side positioning reference signal is the sidelink positioning reference signal (SLPRS), 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 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.

[0057] 4. Resource Pool

[0058] The broad definition of a resource pool is 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.

[0059] For example, see Figure 1 A schematic diagram of the SL resource pool is shown. 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 (physical sidelink control channel, PSCCH) or the physical sidelink shared channel (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. Resource allocation and data transmission are based on sub-channels, such as 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 (physical resource blocks, PRBs). A sub-channel can also be used to represent specific frequency domain location information.

[0060] An embodiment of the present application relates to an SLPRS-exclusive 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.

[0061] For SL resources, there are two ways to allocate resources: Mode 1, allocated by the base station, mainly for UEs within the coverage 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 (ie, Configured Grant Type 1) or semi-static scheduling (ie, 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.

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

[0063] Data transmission and control information transmission in SL communication support the HARQ mechanism. Taking data transmission as an example, after the sender sends SL data to the receiver, the receiver feeds back to the sender whether the SL data is successfully received. The sender feeds back HARQ-ACK or HARQ-NACK to the base station based on the feedback information of the receiver. SL data transmission supports the HARQ mechanism in several scheduling modes of mode 1.

[0064] For example, see Figure 2A The feedback process of SL communication in the dynamic scheduling mode of Mode 1 is shown. Figure 2A In the example, UEA is used as a transmitting UE (ie, TxUE) and UEB is used as a receiving UE (ie, Rx UE). The feedback process may include the following steps:

[0065] 1. The UEA sends a scheduling request (SR) to the base station. Correspondingly, the base station receives the SR from the UEA.

[0066] When the UEA has data to be sent but no available resources, it can send an SR to the base station through the PUCCH.

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

[0068] 3. UEA sends PSCCH and PSSCH to UEB. Correspondingly, UEB receives PSCCH and PSSCH from UEA. UEA sends PSCCH and PSSCH to UEB through the scheduled SL resources.

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

[0070] 5. UEA sends SLHARQ to the base station. Correspondingly, the base station receives SLHARQ from UEA. UEA sends SLHARQ to the base station through the PUCCH resources scheduled by DCI. When UEA receives HARQ-ACK from UEB, it feeds back HARQ-ACK to the base station, indicating that the data has been successfully received; when UEA receives HARQ-ACK from UEB, it feeds back HARQ-ACK to the base station, indicating that the data reception has failed.

[0071] Figure 2A This is a flow chart of the feedback process under dynamic scheduling. The corresponding timing can be found in Figure 2B shown. Figure 2BIn the process, UEA receives RRC signaling from the base station through the Uu port, and the RRC signaling is used to configure the SL-BWP resource pool, that is, the above-mentioned SL resource pool. When UEA has data to be sent to other UEs but there are no available resources, it can send SR to the base station through PUCCH. In response to the SR, the base station sends DCI to UEA, and the DCI is used to indicate the time interval and time-frequency resources. The time interval refers to the time interval (such as the 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 PSCCH and PSSCH. The DCI also includes the minimum time interval between the SL resources and the PSFCH, and the PSFCH is used by UEA to receive the SLHARQ from UEB. The DCI also includes a PSFCH-to-HARQ field, which is used to indicate the time interval (such as the 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 UEA uses the time slot where 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 UEA feeds back SL HARQ to the base station in this time slot. For example, the time slot where 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 in time slot i+j.

[0072] Figure 2A and Figure 2B Taking 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.

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

[0074] In view of this, the embodiments of the present application provide 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 embodiments of the present application clarify that the terminal device sends SLPRS feedback information to the network device, and clarify 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 embodiments of the present application use ACK to describe the response information, i.e., HARQ-ACK; and use NACK to describe the negative response information, i.e., HARQ-NACK.

[0075] 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.

[0076] See also Figure 3 , is a schematic diagram of a network architecture applying an embodiment of the present application. Figure 3 The network architecture shown may include a network device 301 and a terminal device 302 , and optionally, a terminal device 303 . Figure 3 The device form and device quantity shown are for illustrative purposes only and do not constitute a limitation on the embodiments of the present application. Figure 3 For example, the terminal device 302 is within the coverage of the network device 301 , that is, the terminal device 302 can receive messages or signaling from the network device 301 , such as DCI and / or RRC signaling.

[0077] Exemplarily, 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 perform distance measurement or angle measurement by measuring the SLPRS, thereby obtaining a measurement result.

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

[0079] 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:

[0080] Scenario 1: Terminal device 303 is within the coverage of network device 301. Terminal device 302 and terminal device 303 can communicate with network device 301 through Uu port. Terminal device 302 and terminal device 303 can communicate through PC5 port. Under the control of network device 301, terminal device 302 can send SL PRS to terminal device 303; under the control of network device 301, terminal device 303 can send SL PRS to terminal device 302.

[0081] Scenario 2: Terminal device 303 is not within the coverage of network device 301. Terminal device 302 can communicate with network device 301 through Uu port, but terminal device 303 cannot communicate with network device 301 through Uu port. Terminal device 303 communicates with terminal device 302 through PC5 port. Under the control of network device 301, terminal device 302 sends SL PRS to terminal device 303.

[0082] The embodiments of the present application are applicable to the dynamic scheduling method, periodic configuration method and semi-static scheduling method 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.

[0083] based on Figure 3 The network architecture shown in the figure, the feedback information transmission method provided in the embodiment of the present application is described in detail below. For the convenience of description, the terminal device takes UE as an example, and the network device takes gNB as an example.

[0084] See also Figure 4 , is a flow chart of a feedback information transmission method provided in an embodiment of the present application, which may include but is not limited to the following steps:

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

[0086] Among them, at least one SLPRS can be a SLPRS scheduled by DCI, that is, a SLPRS dynamically scheduled by DCI. For example, DCI dynamically schedules 3 SLPRS. At least one SLPRS can also be a SLPRS configured by RRC signaling, that is, a SLPRS configured in a periodic configuration manner. At least one SLPRS can also be a SLPRS configured by RRC signaling and scheduled by DCI, that is, a SLPRS scheduled in a semi-static scheduling manner. That is to say, after the RRC signaling configuration, the 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.

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

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

[0089] In another implementation, the feedback information may include an ACK for a successfully sent SLPRS, but not include a NACK for a failed SLPRS. For example, taking three SLPRS as an example, 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 an ACK for the third SLPRS, but not a NACK for the first SLPRS and a NACK for the second SLPRS.

[0090] In another implementation, the feedback information may include the NACK of the SLPRS that failed to be sent, but does not include the ACK of the SLPRS that was successfully sent. For example, taking 3 SLPRS as an example, 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 of the first SLPRS and the NACK of the second SLPRS, but does not include the ACK of the third SLPRS.

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

[0092] The UE may send feedback information to the gNB via PUCCH or PUSCH so that the gNB schedules or configures SLPRS resources based on the feedback information. The time when the UE sends the feedback information is later than the SLPRS sending time. As for when the feedback information is sent, it is not limited in the embodiment of the present application. For example, when the DCI dynamically schedules the SLPRS resources, it may indicate the time slot of the UE to send the feedback time.

[0093] exist Figure 4 In the illustrated embodiment, 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, when the feedback information is an ACK, the gNB may temporarily not schedule or configure SLPRS resources for the UE. For another example, when the feedback information is a NACK, the gNB may reschedule or configure SLPRS resources for the UE.

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

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

[0096] If one of the at least one SLPRS is successfully transmitted, the UE generates an ACK and feeds back the ACK to the gNB, where the ACK indicates that the transmission status of the at least one SLPRS is successfully transmitted. It can be understood that, regardless of whether one SLPRS or multiple SLPRS are scheduled in the dynamic scheduling mode or the semi-static scheduling mode, as long as one SLPRS is successfully transmitted, an ACK is generated and reported; regardless of the number of periodically configured SLPRS, as long as one of these SLPRS is successfully transmitted, an ACK is generated and reported. If more than one SLPRS is successfully transmitted in at least one SLPRS, the UE also generates and reports an ACK.

[0097] If at least one SLPRS fails to be sent, the UE neither generates a NACK nor reports a NACK.

[0098] Exemplarily, 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 sent successfully, then the UE generates and reports an ACK; assuming that all three SLPRS fail to be sent, then the UE does not generate or report a NACK.

[0099] Optionally, the ACK fed back 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. That is, for a certain SLPRS, as long as one of the multiple transmissions is successful, the SLPRS is considered to be successfully transmitted, and an ACK is generated and reported.

[0100] Exemplarily, for a certain SLPRS, assuming that it is sent three times, the first and second sending both fail, and the third sending succeeds, then the UE generates and reports an ACK.

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

[0102] In one implementation, if one of at least one SLPRS fails to be sent, the UE generates a NACK and feeds back the NACK to the gNB, where the NACK indicates that the sending status of at least one SLPRS is a sending failure. It is understandable that, regardless of whether one SLPRS or multiple SLPRSs are scheduled in a dynamic scheduling mode or a semi-static scheduling mode, as long as one SLPRS fails to be sent, a NACK is generated and reported; regardless of the number of periodically configured SLPRSs, as long as one of these SLPRSs fails to be sent, a NACK is generated and reported. If there are more than one SLPRS that fails to be sent in at least one SLPRS, the UE also generates and reports a NACK. If at least one SLPRS is successfully sent, the UE does not generate a NACK or report a NACK.

[0103] Exemplarily, 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 sent successfully, the UE generates and reports NACK; assuming that all three SLPRS are sent successfully, the UE does not generate or report ACK.

[0104] Optionally, the NACK fed back 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. That is, for a certain SLPRS, as long as one of the multiple transmissions fails, the SLPRS is considered to have failed to be transmitted, and a NACK is generated and reported.

[0105] Exemplarily, for a certain SLPRS, assuming that it is sent three times, the first and second sending both fail, and the third sending succeeds, then the UE generates and reports a NACK.

[0106] In another implementation, if at least one SLPRS fails to be sent, the UE generates a NACK and feeds back the NACK to the gNB, where the NACK indicates that the sending status of at least one SLPRS is a sending failure. If at least one SLPRS is successfully sent, the UE does not generate an ACK or report an ACK.

[0107] Exemplarily, taking three SLPRS as an example, assuming that all three SLPRS fail to be sent, the UE generates and reports 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 does not generate or report ACK.

[0108] Optionally, the NACK fed back is related to the number of transmissions. If one of at least one SLPRS fails to be transmitted in multiple transmissions, the UE generates and reports a NACK. That is, for a certain SLPRS, if its multiple transmissions fail, it is considered that the SLPRS fails to be transmitted, and thus a NACK is generated and reported.

[0109] Exemplarily, for a certain SLPRS, assuming that the number of transmissions is 3 and all the 3 transmissions fail, the UE generates and reports a NACK.

[0110] 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.

[0111] If one of at least one SLPRS is successfully transmitted, the UE generates an ACK and feeds back the ACK to the gNB, where the ACK indicates that the transmission status of at least one SLPRS is successfully transmitted. It can be understood that, regardless of whether one SLPRS or multiple SLPRS are scheduled in a dynamic scheduling mode or a semi-static scheduling mode, as long as one SLPRS is successfully transmitted, an ACK is generated and reported; regardless of the number of periodically configured SLPRSs, as long as one of these SLPRS is successfully transmitted, an ACK is generated and reported. If more than one of at least one SLPRS is successfully transmitted, the UE also generates and reports an ACK. Optionally, the fed-back ACK is related to the number of transmissions. If at least one of the multiple transmissions of at least one SLPRS is successfully transmitted, the UE generates and reports an ACK. That is, for a certain SLPRS, as long as one of its multiple transmissions is successfully transmitted, the SLPRS is considered to be successfully transmitted, and an ACK is generated and reported.

[0112] If at least one SLPRS fails to be sent, the UE generates and reports a NACK, and the NACK indicates that the sending status of at least one SLPRS is a sending failure. Optionally, the NACK fed back is related to the number of transmissions. If at least one SLPRS fails to be sent in multiple transmissions, the UE generates and reports a NACK. That is, for a certain SLPRS, if its multiple transmissions fail, it is considered that the SLPRS fails to be sent, and thus a NACK is generated and reported.

[0113] That is, if at least one of the SLPRS is successfully sent, ACK is reported, otherwise NACK is reported.

[0114] Exemplarily, 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 sent successfully, then the UE generates and reports ACK; assuming that all three SLPRS fail to be sent, then the UE generates and reports NACK.

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

[0116] 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 of each SLPRS. ACK indicates that the transmission status is successful, and NACK indicates that the transmission status is failed.

[0117] Exemplarily, taking three SLPRS as an example, assuming that the first SLPRS fails to send, the second SLPRS fails to send, and the third SLPRS is sent successfully, then the feedback information may include NACK of the first SLPRS (indicating that the first SLPRS fails to send), NACK of the second SLPRS (indicating that the second SLPRS fails to send), and ACK of the third SLPRS (indicating that the third SLPRS is sent successfully). Optionally, the feedback information may be indicated in the form of a bitmap, for example, see Figure 5 The bit map shown in the figure takes "001" as an example, which indicates NACK-NACK-ACK, that is, the first SLPRS is NACK, the second SLPRS is NACK, and the third SLPRS is ACK.

[0118] Optionally, in addition to including the ACK or NACK of each SLPRS, the feedback information may also include a count value corresponding to the ACK or NACK of each SLPRS, which is used to mark the SLPRS resource carrying each SLPRS. For example, taking three SLPRS resources as an example, assuming that the SLPRS carried by the first SLPRS resource fails to be sent, the SLPRS carried by the second SLPRS resource fails to be sent, and the SLPRS carried by the third SLPRS resource is sent successfully, then the feedback information can be expressed as {NACK-0, NACK-1, ACK-2}, that is, the SLPRS carried by the first SLPRS resource is NACK, the SLPRS carried by the second SLPRS resource is NACK, and the SLPRS carried by the third SLPRS resource is ACK. The feedback information also includes the count value corresponding to the ACK or NACK of each SLPRS, so that the gNB can know the corresponding relationship between ACK and SLPRS resources, and the corresponding relationship between NACK and SLPRS resources, which helps the gNB to coordinate and schedule resources more effectively in subsequent resource scheduling.

[0119] Case 4: Taking the feedback information including the ACK or NACK of each SLPRS in at least one SLPRS as an example, optionally, feedback information can be generated and reported for each SLPRS separately. Taking three SLPRS as an example, assuming that the first SLPRS fails to send, the second SLPRS fails to send, and the third SLPRS is sent successfully, then three feedback information can be generated and each feedback information is sent separately, the first feedback information is the NACK of the first SLPRS, the second feedback information is the NACK of the second SLPRS, and the third feedback information is the ACK of the third SLPRS.

[0120] Optionally, for one SLPRS in at least one SLPRS, its feedback information is related to the number of times it is sent. Based on the success or failure of each transmission of the SLPRS, its feedback information is generated, and the feedback information includes an ACK or NACK for each transmission of the SLPRS. Taking three transmissions as an example, assuming that the first and second transmissions fail and the third transmission succeeds, then the feedback information may include the first NACK, the second NACK, and the third ACK. Optionally, the feedback information may also include a count value corresponding to the ACK or NACK for each transmission of the SLPRS. For example, for an SLPRS carried on a certain SLPRS resource, its feedback information may be expressed as {NACK-0, NACK-1, ACK-2}, i.e., NACK for the first transmission of the SLPRS, NACK for the second transmission of the SLPRS, and 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 ACK or NACK for each transmission.

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

[0122] The successfully sent SLPRS in at least one SLPRS is called the first SLPRS, and the feedback information generated and reported by the UE includes the ACK of the first SLPRS, and one ACK is used to indicate that the sending state of the corresponding first SLPRS is successfully sent. It can be understood that the UE only reports the ACK of the successfully sent SLPRS, and the NACK of the failed SLPRS is not reported. The number of the first SLPRS is one or more, depending on the specific situation.

[0123] For example, taking three SLPRS as an example, assuming that the first SLPRS fails to send, the second SLPRS fails to send, and the third SLPRS is sent successfully, then the feedback information may include the ACK of the third SLPRS, but does not include the NACK of the first SLPRS and the second SLPRS. Optionally, the feedback information may be indicated in the form of a bitmap, for example, see Figure 5 The bit map shown in the figure takes "001" as an example, indicating that the third SLPRS is ACK.

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

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

[0126] Optionally, for a first SLPRS, its feedback information is related to the number of times it is sent. Based on the number of times the first SLPRS is successfully sent, feedback information is generated, and the feedback information includes ACKs for the number of times the first SLPRS is successfully sent, but does not include NACKs for the number of times the sending fails. 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 ACKs 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 first SLPRS, its feedback information may be expressed as {ACK-2}, that is, ACK for the third transmission of the first SLPRS.

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

[0128] The SLPRS that fails to be sent in at least one SLPRS is called a second SLPRS, and the feedback information generated and reported by the UE includes a NACK of the second SLPRS, and a NACK is used to indicate that the sending state of the corresponding second SLPRS is a sending failure. It can be understood that the UE only reports the NACK of the SLPRS that fails to be sent, and the ACK of the SLPRS that is successfully sent is not reported. The number of the second SLPRS is one or more, depending on the specific situation.

[0129] For example, taking three SLPRS as an example, assuming that the first SLPRS fails to send, the second SLPRS fails to send, and the third SLPRS is sent successfully, then the feedback information may include the NACK of the first SLPRS and the NACK of the second SLPRS, but does not include the ACK of the third SLPRS. Optionally, the feedback information may be indicated in the form of a bitmap, for example, see Figure 5 The bit map shown in the figure takes "001" as an example, indicating that the first SLPRS is NACK and the second SLPRS is NACK.

[0130] Optionally, in addition to the NACK of the second SLPRS, the feedback information may also include a count value corresponding to the NACK of the second SLPRS, which is used to mark the SLPRS resource carrying the SLPRS that failed to send. Exemplarily, 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 sent successfully, 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 NACK.

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

[0132] Optionally, for a second SLPRS, its feedback information is related to the number of times it is sent. Based on the number of times the second SLPRS fails to be sent, feedback information is generated, and the feedback information includes NACKs for the number of times the second SLPRS fails to be sent, but does not include ACKs for the number of times it is successfully sent. 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 ACKs for the third transmission of the second SLPRS. Optionally, the feedback information may also include a count value corresponding to an ACK or NACK for each transmission of the second SLPRS. For example, for a second SLPRS, its feedback information may be expressed as {NACK-0, NACK-1}, i.e., NACKs for the first and second transmissions of the second SLPRS.

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

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

[0135] At least one SLPRS is not sent within the scheduled time, and the UE generates and reports an ACK, where the ACK indicates that the transmission status of at least one SLPRS is not sent. The scheduling time can be the time when the DCI schedules the transmission of at least one SLPRS, or the time when the SLPRS is transmitted periodically configured by RRC signaling, or the transmission time of the activated SLPRS scheduled by DCI. It can be understood that if the gNB schedules the UE to send at least one SLPRS within the scheduling time, but the UE does not send these SLPRS within the scheduling time, then the UE generates and reports an ACK so that the gNB does not schedule or configure SLPRS resources for the UE temporarily.

[0136] Optionally, if at least one SLPRS is not sent within the scheduled time, and the resources of at least one SLPRS are sent to other UEs, then the UE generates and reports an ACK. Sending at least one SLPRS resource to other UEs, for example, UEA sends at least one SLPRS resource to UEB or UEC, etc., can be understood as the UE allocating at least one SLPRS resource to other UEs for use, and other UEs send SLPRS on these resources. Sending at least one SLPRS resource to other UEs can be performed before generating and reporting ACK, or it can be performed after generating and reporting ACK.

[0137] Optionally, at least one SLPRS is not sent within the scheduled time, and it is determined not to send an SLPRS resource request to the gNB within a first time period, and the first time period is later than the scheduled time, and an ACK is generated and reported. That is, at least one SLPRS is not sent 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 can be understood that the UE does not send at least one SLPRS within the scheduled time, and does not want to request SLPRS resources from the gNB again, and generates and reports an ACK.

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

[0139] Optionally, at least one SLPRS is not sent within the scheduling time, and at least one SLPRS is sent after the second time period, and an ACK is generated and reported. That is, at least one SLPRS is not sent within the scheduling time, but at least one SLPRS is sent at a certain time after the scheduling time, then 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 the DCI is received, and the UE sends part or all of the at least one SLPRS after the second time period. The duration of the second time period may be predefined by the protocol.

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

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

[0142] If the UE has sent at least one SLPRS, a NACK is generated and reported, and the NACK indicates that the sending status of at least one SLPRS is sent. The UE has sent at least one SLPRS, which means that the UE has sent at least one SLPRS within the scheduled time. It can be understood that regardless of whether the sending of at least one SLPRS is successful or not, as long as the UE sends at least one SLPRS, the UE generates and reports a NACK. Optionally, regardless of whether the sending is successful or not, as long as the UE sends at least one SLPRS and the UE intends to request SLPRS resources again, the UE generates and reports a NACK.

[0143] Optionally, in the case of reporting NACK, the first SLPRS resource from the gNB may be received. That is, in response to NACK, the gNB sends the first SLPRS resource to the UE, and the first SLPRS resource may be an SLPRS resource scheduled by dynamic scheduling, an SLPRS resource configured by periodic configuration, or an SLPRS resource scheduled by semi-static scheduling. In response to NACK, the gNB sends the first SLPRS resource to the UE, which is also applicable to the scenarios where NACK is fed back in the above-mentioned cases 2 and 3.

[0144] Optionally, the UE sends the first SLPRS resource to other UEs in response to the received first SLPRS resource. That is, after sending at least one SLPRS, the UE intends to request a new SLPRS resource from the gNB, and the new SLPRS resource is used for the UE to allocate to other UEs, then the UE generates and reports a NACK. Optionally, the first SLPRS resource is used for the UE to send the SLPRS again.

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

[0146] 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 corresponding 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. Figure 6 , Figure 6 The structure diagram of a communication device 600 according to an embodiment of the present application is shown. 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;

[0147] In one implementation, when the communication device 600 is a UE, wherein:

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

[0149] The interface unit 601 is used to send feedback information to the network device.

[0150] In this embodiment, for the specific implementation of the above interface unit 601 and the processing unit 602, please refer to Figure 4 The specific implementation steps of the UE are not repeated here.

[0151] like Figure 7 A communication device 700 provided in an embodiment of the present application is shown, which is used to implement the functions of the above-mentioned UE. 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 the communication device may be a chip system or a chip in the communication device. Among them, the chip system may be composed of a chip, or may include a chip and other discrete devices.

[0152] The communication device 700 includes at least one processor 710, which is used to implement the processing function of the device (such as UE or network equipment) in the method provided in the embodiment of the present application. The communication device 700 may also include a communication interface 720, which is used to implement the transceiver operation of the device (such as UE or network equipment) in the method provided in the embodiment of the present application. In the embodiment of the present application, the communication interface can be a transceiver, a circuit, a bus, a module or other type of communication interface, which is used to communicate with other devices through 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.

[0153] 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. The coupling in the embodiment of the present application is an indirect coupling or communication connection between devices, units or modules, which may 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.

[0154] The specific connection medium between the communication interface 720, the processor 710 and the memory 730 is not limited in the embodiment of the present application. Figure 7 The memory 730, the processor 710 and the communication interface 720 are connected via a bus. Figure 7 The connections between the other components are shown in bold lines, which are only for illustration and are 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, Figure 7 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0155] 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.

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

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

[0158] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or 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.

[0159] 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, and the software modules can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable ROM (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 a component of the processor. The processor and the 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 the storage medium can also be present in a terminal or an access network device as discrete components.

[0160] 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 may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instruction may be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer-readable storage medium may 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 may be a magnetic medium, such as a floppy disk, a hard disk, or a tape; it may also be an optical medium, such as a DVD; it may also be a semiconductor medium, such as a solid state drive (SSD).

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

[0162] It is understood that the various numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic.

[0163] 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.

[0164] 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 the network device in the above method embodiment is implemented.

[0165] 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 the present application is not limited by the described order of actions, because according to the present 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 the present application.

[0166] The descriptions of the various embodiments provided in this application can refer to each other, and the descriptions of the various embodiments have their own emphasis. For parts that are not described in detail in a certain embodiment, refer to the relevant descriptions of other embodiments. For the convenience and simplicity of description, for example, the functions of the various devices and equipment provided in the embodiments of this application and the steps of execution can refer to the relevant descriptions of the method embodiments of this application, and the various method embodiments and the various device embodiments can also refer to, combine or quote each other.

[0167] 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 it. 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 replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate 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.