WO2023065151A1 - 边链路反馈信息的发送和接收方法以及装置 - Google Patents

边链路反馈信息的发送和接收方法以及装置 Download PDF

Info

Publication number
WO2023065151A1
WO2023065151A1 PCT/CN2021/124985 CN2021124985W WO2023065151A1 WO 2023065151 A1 WO2023065151 A1 WO 2023065151A1 CN 2021124985 W CN2021124985 W CN 2021124985W WO 2023065151 A1 WO2023065151 A1 WO 2023065151A1
Authority
WO
WIPO (PCT)
Prior art keywords
side link
feedback information
physical
harq
control channel
Prior art date
Application number
PCT/CN2021/124985
Other languages
English (en)
French (fr)
Inventor
张健
蒋琴艳
纪鹏宇
李国荣
王昕�
Original Assignee
富士通株式会社
张健
蒋琴艳
纪鹏宇
李国荣
王昕�
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社, 张健, 蒋琴艳, 纪鹏宇, 李国荣, 王昕� filed Critical 富士通株式会社
Priority to PCT/CN2021/124985 priority Critical patent/WO2023065151A1/zh
Priority to CN202180103300.0A priority patent/CN118120313A/zh
Publication of WO2023065151A1 publication Critical patent/WO2023065151A1/zh
Priority to US18/637,765 priority patent/US20240267950A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H04W74/0816—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA] with collision avoidance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/25—Control channels or signalling for resource management between terminals via a wireless link, e.g. sidelink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/40—Resource management for direct mode communication, e.g. D2D or sidelink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the embodiment of the present application relates to the technical field of communication.
  • 3GPP has standardized how the Uu interface uses the unlicensed (unlicensed) frequency band.
  • the standardization work of 5G NR mainly includes the NR-U project of Release 16 and the 52.6GHz-71GHz project of Release 17 in progress.
  • the use of unlicensed frequency bands increases the spectrum resources available for the Uu interface. These additional spectrum resources are beneficial to increase data rate (or throughput), improve reliability, and reduce delay.
  • the unlicensed frequency band can be deployed jointly with the licensed frequency band, and the licensed frequency band can be used to assist the use of the unlicensed frequency band, or the unlicensed frequency band can be deployed independently.
  • Relevant application scenarios include any coexistence with other wireless access technologies (such as WIFI), Industrial Internet of Things (IIoT) scenarios using unlicensed frequency bands, etc.
  • 3GPP has standardized the side link, and the standardization work of 5G NR includes the V2X project approval of Release 16 and the sidelink project approval of Release 17 in progress.
  • the physical channels defined by Rel-16NR V2X include Physical Sidelink Control Channel (PSCCH, Physical Sidelink Control Channel), Physical Sidelink Shared Channel (PSSCH, Physical Sidelink Shared Channel) and Physical Sidelink Feedback Channel (PSFCH, Physical Sidelink Feedback Channel).
  • PSCCH carries 1st stage side link control information (SCI, Sidelink Control Informaiton), and the 1st stage SCI is mainly used to reserve resources.
  • PSSCH carries 2nd stage SCI and transport block (TB, Transport Block), where 2nd stage SCI is mainly used for TB demodulation.
  • PSFCH carries side link feedback information (may be referred to as HARQ-ACK).
  • PSCCH and PSSCH are generally sent in the same time slot.
  • a PSCCH/PSSCH is associated with one or more PSFCH resources according to established rules.
  • the device can receive acknowledgment (ACK)/non-acknowledgement (NACK) on the associated PSFCH resource.
  • ACK acknowledgment
  • NACK non-acknowledgement
  • NR V2X supports HARQ-ACK feedback for unicast and multicast. Multicast also includes HARQ option 1 and HARQ option 2 two HARQ-ACK feedback modes.
  • HARQ option 1 For the multicast of HARQ option 1, only receiving devices within a certain communication range (communication range) will feedback HARQ-ACK, and use a way of only feeding back NACK (NACK-only), and the sending device does not know the details of NACK Which receiving device sent it.
  • NACK-only NACK-only
  • the PSFCH resources used by each receiving device to feed back ACK/NACK are independent, and the sending device knows which receiving device sent the ACK/NACK.
  • NR V2X defines two working modes. For NR V2X Mode 1 (Mode 1), the resources used by the terminal device for V2X communication are scheduled or configured by the network device (base station) through the NR Uu link. For NR V2X Mode 2 (Mode 2), terminal devices can autonomously select time-frequency resources for V2X communication based on the sensing results.
  • SL-U Sidelink-Unlicensed
  • HARQ-ACK retransmission is also one of the necessary functions, how to support HARQ-ACK retransmission in SL-U is still an open problem.
  • embodiments of the present application provide a method and device for sending and receiving side link feedback information.
  • a method for sending side link feedback information including:
  • PUCCH physical uplink control channel
  • PSCCH physical side link control channel
  • PSSCH physical side link shared channel
  • the side link feedback information that needs to be carried by the physical uplink control channel has not been received, and the physical side link control channel (PSCCH) and/or the physical side link control channel (PSCCH) associated with the side link feedback information has been sent to the second device.
  • the first device does not send the physical uplink control channel (PUCCH).
  • an apparatus for sending side link feedback information including:
  • a determining unit which determines whether the side link feedback information that needs to be carried by the physical uplink control channel is received and whether the side link feedback information that needs to be carried by the physical uplink control channel has been sent to the second device in the case that the physical uplink control channel needs to be sent to the network device.
  • a processing unit which needs to be carried by the physical uplink control channel when the side link feedback information is not received, and has sent the physical side link control channel associated with the side link feedback information to the second device and /or in the case of the physical side link shared channel, the physical uplink control channel is not sent.
  • a method for sending side link feedback information including:
  • the second device receives a Physical Sidelink Control Channel (PSCCH) and/or a Physical Sidelink Shared Channel (PSSCH) sent by the first device; and
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • the second device sends a plurality of side link feedback information to the first device; wherein the physical side link feedback channel (PSFCH) resources of the plurality of side link feedback information are at least composed of the plurality of side link
  • PSFCH physical side link feedback channel
  • an apparatus for sending side link feedback information including:
  • a receiving unit which receives the physical side link control channel and/or the physical side link shared channel sent by the first device
  • a sending unit which sends a plurality of side link feedback information to the first device; wherein the physical side link feedback channel resources of the plurality of side link feedback information are at least determined by the number of the plurality of side link feedback information Sure.
  • a communication system including:
  • the first device determines whether the side link feedback information that needs to be carried by the physical uplink control channel is received, and whether the side link feedback information that needs to be carried by the physical uplink control channel has been sent to the second device.
  • the physical side link control channel and/or the physical side link shared channel associated with the side link feedback information when the side link feedback information that needs to be carried by the physical uplink control channel has not been received, and has been sent to the second
  • the device sends the physical side link control channel and/or the physical side link shared channel associated with the side link feedback information, the physical uplink control channel is not sent; and/or
  • the second device receives the physical side link control channel and/or the physical side link shared channel sent by the first device; and sends a plurality of side link feedback information to the first device; wherein the plurality of side chains
  • the physical side link feedback channel resources of the channel feedback information are at least determined by the number of the plurality of side link feedback information.
  • One of the beneficial effects of the embodiments of the present application is: for the HARQ-ACK retransmission from the first device to the network device, if the first device has sent the PSCCH and/or PSSCH associated with the HARQ-ACK to the second device, but has not received
  • the first device does not send the PUCCH to the network device, thereby reducing or avoiding unnecessary occupation of the unlicensed frequency band , and may notify the network device to schedule HARQ-ACK retransmission.
  • the size of the HARQ-ACK codebook is additionally used to determine the PSFCH resource, so that PSFCH resource collision can be avoided in the multicast HARQ-ACK retransmission.
  • Fig. 1 is the schematic diagram of the communication system of the embodiment of the present application.
  • FIG. 2 is an example diagram of HARQ-ACK retransmission in NR-U
  • Figure 3 is an example diagram of Mode 1 resource allocation in NR V2X;
  • FIG. 4 is a schematic diagram of a method for sending side link feedback information according to an embodiment of the present application
  • FIG. 5 is an example diagram of side link feedback information in the embodiment of the present application.
  • FIG. 6 is another example diagram of side link feedback information in the embodiment of the present application.
  • FIG. 7 is another schematic diagram of a method for sending side link feedback information according to an embodiment of the present application.
  • FIG. 8 is another example diagram of side link feedback information in the embodiment of the present application.
  • FIG. 9 is another example diagram of side link feedback information in the embodiment of the present application.
  • FIG. 10 is a schematic diagram of an apparatus for sending side link feedback information according to an embodiment of the present application.
  • FIG. 11 is another schematic diagram of an apparatus for sending side link feedback information according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a network device according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements from the title, but do not indicate the spatial arrangement or time order of these elements, and these elements should not be referred to by these terms restricted.
  • the term “and/or” includes any and all combinations of one or more of the associated listed items.
  • the terms “comprising”, “including”, “having” and the like refer to the presence of stated features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.
  • the term “communication network” or “wireless communication network” may refer to a network conforming to any of the following communication standards, such as Long Term Evolution (LTE, Long Term Evolution), Enhanced Long Term Evolution (LTE-A, LTE- Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed Packet Access (HSPA, High-Speed Packet Access), etc.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • LTE-A Long Term Evolution-A
  • LTE- Advanced Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • High-Speed Packet Access High-Speed Packet Access
  • the communication between devices in the communication system can be carried out according to any stage of communication protocols, such as but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G , New Radio (NR, New Radio), etc., and/or other communication protocols that are currently known or will be developed in the future.
  • Network device refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
  • Network equipment may include but not limited to the following equipment: base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception Point), broadcast transmitter, mobile management entity (MME, Mobile Management Entity), gateway, server, radio network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller) and so on.
  • the base station may include but not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc., and may also include Remote Radio Head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay) or low-power nodes (such as femeto, pico, etc.).
  • Node B Node B
  • eNodeB or eNB evolved Node B
  • gNB 5G base station
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low-power nodes such as femeto, pico, etc.
  • base station may include some or all of their functions, each base station may provide communication coverage for a particular geographic area.
  • the term "cell” can refer to a base station and/or its coverage area depending on the context in which the term is used.
  • the term "User Equipment” (UE, User Equipment) or “terminal equipment” (TE, Terminal Equipment or Terminal Device), for example, refers to a device that accesses a communication network through a network device and receives network services.
  • a terminal device may be fixed or mobile, and may also be called a mobile station (MS, Mobile Station), a terminal, a subscriber station (SS, Subscriber Station), an access terminal (AT, Access Terminal), a station, etc.
  • the terminal equipment may include but not limited to the following equipment: Cellular Phone (Cellular Phone), Personal Digital Assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication equipment, handheld equipment, machine-type communication equipment, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
  • Cellular Phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem wireless communication equipment
  • handheld equipment machine-type communication equipment
  • laptop computer Cordless phones
  • Cordless phones smartphones, smart watches, digital cameras, and more.
  • the terminal device can also be a machine or device for monitoring or measurement, such as but not limited to: a machine type communication (MTC, Machine Type Communication) terminal, Vehicle communication terminal, device to device (D2D, Device to Device) terminal, machine to machine (M2M, Machine to Machine) terminal, etc.
  • MTC Machine Type Communication
  • Vehicle communication terminal device to device (D2D, Device to Device) terminal
  • M2M Machine to Machine
  • network side refers to one side of the network, which may be a certain base station, or may include one or more network devices as above.
  • user side or “terminal side” or “terminal device side” refers to a side of a user or a terminal, which may be a certain UE, or may include one or more terminal devices as above.
  • device may refer to network devices or terminal devices.
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a case where a terminal device and a network device are taken as examples.
  • a communication system 100 may include a network device 101 and terminal devices 102 and 103.
  • FIG. 1 only uses two terminal devices and one network device as an example for illustration, but this embodiment of the present application is not limited thereto.
  • eMBB enhanced mobile broadband
  • mMTC massive Machine Type Communication
  • URLLC Ultra-Reliable and Low -Latency Communication
  • Fig. 1 shows that both terminal devices 102 and 103 are within the coverage of the network device 101, but the present application is not limited thereto. Neither of the two terminal devices 102 and 103 may be within the coverage of the network device 101 , or one terminal device 102 may be within the coverage of the network device 101 while the other terminal device 103 is outside the coverage of the network device 101 .
  • side link transmission can be performed between two terminal devices 102 and 103 .
  • the two terminal devices 102 and 103 can both perform side link transmission within the coverage of the network device 101 to realize V2X communication, or both can perform side link transmission outside the coverage of the network device 101 to realize V2X
  • one terminal device 102 may be within the coverage of the network device 101 while the other terminal device 103 is outside the coverage of the network device 101 to perform side link transmission to realize V2X communication.
  • LBT Listen Before Talk
  • a device base station or terminal device
  • LBT can only transmit using an unlicensed frequency band if the LBT is successful. If LBT fails, the device cannot use the unlicensed frequency band for transmission.
  • the failure of LBT will affect some traditional processes of NR Uu, for example, it will affect the HARQ feedback process of NR. More specifically, LBT failure may cause the device not to feed back HARQ-ACK to the base station, or, because the HARQ-ACK feedback time cannot be within the current COT, the device does not feed back HARQ-ACK to the base station.
  • NR-U has enhanced the HARQ process, one of which is the introduction of an enhanced Type-2 HARQ-ACK codebook (codebook), which supports the grouping of the original Type-2 HARQ-ACK codebook and the HARQ- Retransmission of ACK bits.
  • codebook an enhanced Type-2 HARQ-ACK codebook
  • the details of the enhanced Type-2 HARQ-ACK codebook can refer to Section 9.1.3.3 of the standard TS 38.213.
  • Fig. 2 is an example diagram of HARQ-ACK retransmission in NR-U, which schematically illustrates the HARQ-ACK retransmission in NR-U.
  • a carrier or cell
  • DCI contains "PDSCH group index” field (G), DAI field (C-DAI/T-DAI), "new feedback indicator” field (F), and "number of requested PDSCH group(s)" field (R).
  • G indicates which group (group) the current PDSCH and the associated HARQ-ACK belong to.
  • DAI is counted in the group, and the counting method is the same as the traditional Type-2 HARQ-ACK codebook;
  • F indicates whether Empty the HARQ-ACK and DAI before the group, F value flip means clear;
  • the base station sends PDSCH to the device.
  • DCI 1 is used to schedule TB 1
  • DCI 2 is used to schedule TB 2
  • the device is instructed to feed back HARQ including HARQ-ACK 1 and HARQ-ACK 2 on PUCCH 1.
  • the base station uses DCI 3 to schedule TB 3.
  • the base station indicates a non-numeric value in the "HARQ feedback timing" field to instruct the device not to feedback HARQ-ACK 3 temporarily.
  • the base station can achieve the above purpose through grouping (G).
  • the device did not send HARQ-ACK 1 and HARQ-ACK 2 on PUCCH 1 due to LBT failure. So far, the base station has not received HARQ-ACK 1 ⁇ HARQ-ACK 3 in COT 1. However, the base station can schedule devices to retransmit HARQ-ACK 1 to HARQ-ACK 3 later.
  • the base station uses DCI 4 to schedule TB 4 in COT 2, and instructs the device to feed back HARQ-ACK for the two groups, that is, to feed back HARQ-ACK 1 to HARQ-ACK 4.
  • the device has no chance to send HARQ-ACK 1 ⁇ HARQ-ACK 3 before, when the base station schedules the device to feed back HARQ-ACK 4, it also schedules the device to retransmit HARQ-ACK 1 ⁇ HARQ-ACK 3, thus realizing HARQ-ACK Retransmission.
  • NR V2X defines two working modes, Mode 1 and Mode 2.
  • FIG 3 is an example diagram of Mode 1 resource allocation in NR V2X, which schematically illustrates the Mode 1 resource allocation method.
  • the network device uses DCI to allocate resources for the transmitting device (TX UE).
  • the TX UE sends the PSCCH/PSSCH to the receiving device (RX UE) on the allocated resources, and receives the PSFCH carrying the side link HARQ-ACK sent by the RX UE.
  • TX UE sends side link HARQ-ACK to gNB through PUCCH.
  • the DCI and PUCCH are sent through the Uu interface, and the PSSCH and PSFCH are sent through the side link PC5 interface. According to the standard, if the TX UE does not receive the PSFCH, a NACK is fed back to the gNB.
  • SL-U Servicelink-Unlicensed
  • SL-U uses unlicensed frequency bands for side link communication, that is, device-to-device communication.
  • SL-U can further reduce the delay through direct communication between devices.
  • SL-U can also improve the data rate and reliability of side link transmission by utilizing additional spectrum.
  • Interested application scenarios include Network Controlled Interactive Service (NCIS), Industrial Internet of Things (IIoT), Internet of Vehicles, smart home, etc.
  • 3GPP mainly discusses the necessity of SL-U project approval and possible research content, and does not involve any technical details.
  • existing standards support communication based on the Uu interface on an unlicensed frequency band, that is, communication between a base station and a device.
  • 3GPP standardized side-link communications using licensed frequency bands.
  • HARQ-ACK retransmission is also one of the necessary functions, how to support HARQ-ACK retransmission in SL-U is still an open problem.
  • the complexity is more reflected in the Mode 1 resource allocation of the side link, where the TX UE may not only need to retransmit the side link HARQ-ACK to the base station, but also need to request or trigger the RX UE to retransmit the side link HARQ-ACK to the TX UE , which requires a new method to realize the above-mentioned double HARQ-ACK retransmission, and the existing HARQ-ACK retransmission method cannot be directly applied to SL-U.
  • sidelink and “V2X” are interchangeable
  • PSFCH and “sidelink feedback channel” are interchangeable
  • PSCCH and “Sidelink Control Channel” or “Sidelink Control Information” are interchangeable
  • PSSCH and “Sidelink Data Channel” or “Sidelink Data” are also interchangeable.
  • sending (transmitting) or receiving (receiving) PSCCH can be understood as sending or receiving side link control information carried by PSCCH; sending or receiving PSSCH can be understood as sending or receiving side link data carried by PSSCH; sending or receiving PSFCH can be understood as sending or receiving side link feedback information carried by PSFCH.
  • Sidelink transmission (Sidelink transmission, also referred to as sidelink transmission) can be understood as PSCCH/PSSCH transmission or sidelink data/information transmission.
  • the first device refers to the sending device of the edge link
  • the second device refers to the receiving device of the edge link
  • HARQ-ACK retransmission refers to the retransmission of HARQ-ACK bits
  • HARQ-ACK is for PSCCH/ HARQ-ACK of PSSCH
  • PSCCH/PSSCH is also referred to as PSSCH for short
  • SCI can refer to 1st stage SCI and/or 2nd stage SCI.
  • the first device receives the side link HARQ-ACK (one or more HARQ-ACK bits) from the second device, and determines to pass the PUCCH according to the side link HARQ-ACK from the second device.
  • Feedback information (such as HARQ-ACK) sent to the network device (base station), the process of determining the feedback information sent to the network device (base station) can follow the existing standards, and can refer to Section 16.5 of TS 38.213.
  • “the feedback information that needs to be carried by the PUCCH is not received by the first device” means "the associated side link HARQ-ACK from the second device is not received by the first device".
  • An embodiment of the present application provides a method for sending and receiving side link feedback information, which is described from a first device and a network device.
  • FIG. 4 is a schematic diagram of a method for sending side link feedback information according to an embodiment of the present application. As shown in FIG. 4, the method includes:
  • the first device needs to send a physical uplink control channel (PUCCH) to the network device, determine whether the side link feedback information that needs to be carried by the physical uplink control channel has been received and whether it has been sent to the second device A physical sidelink control channel (PSCCH) and/or a physical sidelink shared channel (PSSCH) associated with the sidelink feedback information;
  • PUCCH physical uplink control channel
  • PSSCH physical sidelink shared channel
  • the side link feedback information that needs to be carried by the physical uplink control channel is not received, and the physical side link control channel (PSCCH) and/or associated with the side link feedback information have been sent to the second device Or in the case of a physical sidelink shared channel (PSSCH), the first device does not send the physical uplink control channel (PUCCH).
  • PSCCH physical side link control channel
  • PSSCH physical sidelink shared channel
  • the first device sends a Physical Sidelink Control Channel (PSCCH) and/or a Physical Sidelink Shared Channel (PSSCH) to the second device.
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • all side link feedback information that needs to be carried by the physical uplink control channel has not been received, and the physical side link associated with all the side link feedback information has been sent to the second device
  • the first device does not send the physical uplink control channel (PUCCH).
  • the number or proportion of side link feedback information that is not received among the plurality of side link feedback information that needs to be carried by the physical uplink control channel is greater than a configured or preconfigured threshold, and has been sent to
  • the second device sends the physical side link control channel (PSCCH) and/or the physical side link shared channel (PSSCH) associated with the plurality of side link feedback information
  • the first device does not send the physical uplink Control Channel (PUCCH).
  • the first device when the first device needs to send a physical uplink control channel (PUCCH) to the network device, determine whether the side link feedback information that needs to be carried by the physical uplink control channel is valid or whether it is a stuffing bit; In a case where the side link feedback information that needs to be carried by the physical uplink control channel is invalid or is stuffing bits, the first device does not send the physical uplink control channel (PUCCH).
  • PUCCH physical uplink control channel
  • the first device has not received the side link feedback information and has sent the physical side link control channel (PSCCH) and/or associated with the side link feedback information to the second device
  • PSCCH physical side link control channel
  • PSSCH physical sidelink shared channel
  • the first device in the case that all the side link feedback information that needs to be carried by the physical uplink control channel is invalid or all are filling bits, the first device does not send the physical uplink control channel (PUCCH).
  • PUCCH physical uplink control channel
  • the first device when the number or proportion of invalid side link feedback information or padding bits in the plurality of side link feedback information carried by the physical uplink control channel is greater than a configured or preconfigured threshold , the first device does not send the physical uplink control channel (PUCCH).
  • PUCCH physical uplink control channel
  • FIG. 5 is an example diagram of side link feedback information in the embodiment of the present application.
  • the network device uses the DCI to allocate resources for sending PSSCH to device 1 (first device or sending device), and indicate the PUCCH resources for sending side link HARQ-ACK.
  • the PSSCH resources are located in the unlicensed frequency band, the DCI can be sent using the unlicensed frequency band or the licensed frequency band, and the PUCCH can be sent using the unlicensed frequency band or the licensed frequency band.
  • DCI3 instructs device 1 not to feed back HARQ-ACK3 temporarily.
  • Device 1 sends TB1 and TB2 on resources allocated by DCI1 and DCI2.
  • device 1 needs to obtain HARQ-ACK1 and HARQ-ACK2 from device 2 (second device or receiving device) before time t1.
  • device 1 may not have received HARQ-ACK1 and HARQ-ACK2. In this case, device 1 does not transmit PUCCH1.
  • the base station will not receive HARQ-ACK1 and HARQ-ACK2 on PUCCH1, so the base station can choose to retransmit HARQ-ACK1 and HARQ-ACK2 (retransmit to the base station) at the next COT (COT2) scheduling device 1, and Device 1 is not scheduled to retransmit TB1 and TB2 (retransmit to device 2).
  • the base station uses DCI4 to allocate resources for sending TB4 to device 1.
  • DCI4 instructs device 1 to feed back HARQ-ACK for group 0 and group 1 on PUCCH2, that is, HARQ-ACK1 ⁇ HARQ-ACK4. Retransmission of ACK1 and HARQ-ACK2.
  • device 1 does not retransmit TB1 and TB2, but instructs device 2 to retransmit HARQ-ACK1 and HARQ-ACK2. For example, device 1 instructs device 2 to retransmit HARQ-ACK using a method similar to how the base station schedules device 1 to retransmit HARQ-ACK. After receiving DCI4, device 1 instructs device 2 to retransmit HARQ-ACK1 and HARQ-ACK2 through SCI. For retransmission, device 1 indicates parameters such as G and SAI in the SCI. The parameters can be determined independently, and can be the same as or different from the parameters indicated by the DCI of the base station.
  • the occupation of the unlicensed frequency band is reduced, and interference to other devices using the unlicensed frequency band is avoided.
  • device 1 does not transmit the PUCCH1, which can also reduce the occupation of the unlicensed frequency band and avoid interference to other devices using the unlicensed frequency band.
  • the DCI can also contain other Fields, such as "new feedback indicator” field, "number of requested group(s)” field, etc. The usage of these omitted fields is the same as that in the existing NR-U standard.
  • Fig. 6 is another example diagram of side link feedback information in the embodiment of the present application, showing the situation if the existing solution is followed.
  • the device 1 when the device 1 does not receive HARQ-ACK1 and HARQ-ACK2, it will send NACK1 and NACK2 to the base station, that is, NACK is filled.
  • the base station After receiving NACK1 and NACK2, the base station will consider that the device fails to demodulate and decode, and thus continue to schedule device 1 to retransmit TB1 and TB2, but will not schedule device 1 to retransmit HARQ-ACK1 and HARQ-ACK2.
  • the retransmission of TB1 and TB2 additionally occupies an unlicensed frequency band, reduces resource utilization, and may cause interference to other devices.
  • not sending PUCCH1 is actually equivalent to transferring an additional state information different from ACK and NACK to the base station. Based on this information, the base station can only schedule HARQ-ACK retransmissions, but not PSSCH retransmissions, thereby reducing the occupation of unlicensed frequency bands.
  • FIG. 5 schematically illustrates that PUCCH1 includes HARQ-ACK1 and HARQ-ACK2 as an example.
  • PUCCH1 may include only one HARQ-ACK, or may include more HARQ-ACKs. This embodiment of the present application is not limited thereto.
  • the embodiment of the present application does not limit the reason why the device 1 does not receive the HARQ-ACK (for example, HARQ-ACK 1 and HARQ-ACK 2).
  • device 2 does not send HARQ-ACK to device 1 due to LBT failure.
  • device 2 needs to send or receive other signals with higher priority at the same time, and based on the priority rule, device 2 does not send HARQ-ACK to device 1 .
  • device 2 sends HARQ-ACK to device 1
  • device 1 needs to send other signals with higher priority at the same time, and based on the priority rule, device 1 does not receive the HARQ-ACK sent by device 2.
  • device 1 not sending PUCCH1 may include the following actions. For example, device 1 does not perform LBT for PUCCH1. For another example, the LBT performed by device 1 on PUCCH1 is successful, but device 1 still does not send PUCCH1.
  • the first device sends non-acknowledgement (NACK) information to the network device in case the PSCCH and/or PSSCH were not sent to the second device due to LBT failure.
  • NACK non-acknowledgement
  • the first device sends a NACK to the base station.
  • the first device when the first device fails to send the PSSCH due to LBT failure, the first device sends a NACK to the base station.
  • the first device fails to send the PSSCH to the second device due to LBT failure, including not sending the PSSCH on the resource scheduled by the DCI, and also including not sending the PSSCH on the resource configured with a grant (configured grant).
  • the first device will not receive the HARQ-ACK from the second device.
  • the first device sends a NACK to the base station. After receiving the NACK, the base station will continue to allocate resources for the first device, and the first device can continue to send the PSSCH on the allocated resources.
  • the first device does not send the PUCCH ; Otherwise, the first device fills the unreceived HARQ-ACK with NACK.
  • the first device if the first device only receives a part of the HARQ-ACK bits, if the number of unreceived HARQ-ACK bits is greater than a certain threshold, or if the first device does not receive
  • the first device does not send the PUCCH; otherwise, the first device fills the unreceived HARQ-ACK as NACK.
  • greater than can also be replaced with “greater than or equal to”.
  • Thresholds can be configured or preconfigured.
  • the network device sends information for instructing retransmission of the side link feedback information when the physical uplink control channel is not received.
  • the first device may trigger retransmission of the side link feedback information after receiving the information indicating to retransmit the side link feedback information.
  • the first device is enabled to retransmit side link feedback information to the network device
  • the second device is enabled to retransmit side link feedback information to the first device .
  • the behavior of the first device not sending PUCCH needs to meet the following conditions: the first device is enabled to retransmit HARQ-ACK to the base station, and the second device is enabled to retransmit HARQ-ACK to the first device Function of HARQ-ACK.
  • the device needs to have a certain capability to support the retransmission of HARQ-ACK bits.
  • device 1 in FIG. 5 needs to be able to temporarily save HARQ-ACK3 and retransmit HARQ-ACK3 at a certain point in the future.
  • device 1 after receiving DCI4, device 1 will further instruct device 2 to retransmit HARQ-ACK1 and HARQ-ACK2, so device 2 needs to be able to save the results of HARQ-ACK1 and HARQ-ACK2.
  • the ability to support HARQ-ACK retransmission may also be referred to as the ability to support an enhanced HARQ-ACK codebook (enhanced HARQ-ACK codebook).
  • enhanced HARQ-ACK codebook enhanced HARQ-ACK codebook
  • the ability to support HARQ-ACK retransmission can be exchanged between devices and/or between the device and the base station, so that the base station can enable the first device to perform HARQ-ACK retransmission through configuration, and/or, the first The device may be configured to enable the second device to perform HARQ-ACK retransmission.
  • the first device sends capability information of whether the first device can support retransmission of side link feedback information and/or capability information of whether the second device can support retransmission of side link feedback information to the network device.
  • the first device receives indication information sent by the network device for enabling the first device to retransmit the side link feedback information.
  • the first device receives capability information sent by the second device about whether the second device can support retransmission of side link feedback information.
  • the first device sends indication information for enabling the second device to retransmit the side link feedback information to the second device.
  • the interaction and reporting of capabilities includes an indication of whether the device can support HARQ-ACK retransmission.
  • the device is configured with the parameter HARQ-ACK-Codebook, and the parameter value is configured as enhanced, it means that the device HARQ-ACK retransmission is enabled.
  • the interaction of the HARQ-ACK retransmission capability includes at least one of the following manners.
  • the second device reports the capability to the first device.
  • the first device reports the capability to the base station.
  • Enabling the HARQ-ACK retransmission function includes at least one of the following manners.
  • the base station enables HARQ-ACK retransmission of the first device.
  • the first device enables HARQ-ACK retransmission of the second device.
  • the embodiment of the present application may also include any combination of the foregoing manners.
  • the second device reports its ability to support HARQ-ACK retransmission to the first device.
  • the first device reports to the base station that it can support HARQ-ACK retransmission; otherwise, the first device reports to the base station that it cannot support HARQ-ACK retransmission .
  • the first device does not directly report its ability to support HARQ-ACK retransmission to the base station.
  • the base station determines whether to enable HARQ-ACK retransmission of the first device.
  • the first device determines whether to enable HARQ-ACK retransmission of the second device. For example, in the case that the base station enables the HARQ-ACK retransmission of the first device, the first device enables the HARQ-ACK retransmission of the second device.
  • the second device reports its ability to support HARQ-ACK retransmission to the first device.
  • the first device reports the capability of the first device to support HARQ-ACK retransmission and the capability of the second device to support HARQ-ACK retransmission to the base station.
  • the base station determines whether to enable HARQ-ACK retransmission of the first device.
  • the first device determines whether to enable HARQ-ACK retransmission of the second device. For example, in the case that the base station enables the HARQ-ACK retransmission of the first device, the first device enables the HARQ-ACK retransmission of the second device.
  • the second device reports its ability to support HARQ-ACK retransmission to the first device.
  • the first device reports the capability of the first device to support HARQ-ACK retransmission to the base station.
  • the base station determines whether to enable HARQ-ACK retransmission of the first device.
  • the first device determines whether to enable HARQ-ACK retransmission of the second device. For example, in the case that the base station enables the HARQ-ACK retransmission of the first device, the first device enables the HARQ-ACK retransmission of the second device.
  • the method for sending side-link feedback information is schematically described above from the perspective of the first device, and the method for receiving side-link feedback information is schematically described below from the perspective of network devices.
  • the content is the same as that of the previous embodiment No longer.
  • the network device receives side link feedback information carried by the first device through a physical uplink control channel; wherein, the physical uplink control channel (PUCCH) is determined by the first device when it needs to be transmitted by the physical uplink control channel. Sent when the side link feedback information carried by the control channel has been received.
  • PUCCH physical uplink control channel
  • the first device when the side link feedback information that needs to be carried by the physical uplink control channel is not received by the first device, and the first device has sent the physical side chain associated with the side link feedback information to the second device
  • the physical uplink control channel (PUCCH) is not sent by the first device.
  • all side link feedback information that needs to be carried by the physical uplink control channel has not been received by the first device, and the first device has sent the physical edge information associated with all side link feedback information to the second device.
  • the physical uplink control channel (PUCCH) is not sent by the first device.
  • the number or proportion of side link feedback information that is not received by the first device among the multiple side link feedback information that needs to be carried by the physical uplink control channel is greater than a configured or preconfigured threshold, and the second In a case where a device has sent a physical side link control channel (PSCCH) and/or a physical side link shared channel (PSSCH) associated with multiple side link feedback information to the second device, the physical uplink control channel ( PUCCH) is not sent by the first device.
  • PSCCH physical side link control channel
  • PSSCH physical side link shared channel
  • the network device sends information for instructing retransmission of the side link feedback information to the first device when the physical uplink control channel is not received.
  • the first device is enabled to retransmit the sidelink feedback information to the network device
  • the second device is enabled to retransmit the sidelink feedback information to the first device.
  • the network device receives capability information about whether the first device can support retransmission of side link feedback information and/or capability information about whether the second device can support retransmission of side link feedback information sent by the first device.
  • the network device sends indication information for enabling the first device to retransmit side link feedback information to the first device.
  • the above mainly describes the HARQ-ACK interaction between the first device and the network device, and there is no limitation on how the HARQ-ACK interaction between the first device and the second device is performed.
  • the first device for the HARQ-ACK retransmission from the first device to the network device, if the first device has sent the PSCCH and/or PSSCH associated with the HARQ-ACK to the second device, but has not received the PUCCH that needs to be carried by the PUCCH side link feedback information (that is, the PUCCH does not contain valid HARQ-ACK bits), the first device does not send the PUCCH to the network device, thereby reducing or avoiding unnecessary occupation of the unlicensed frequency band, and notifying the network The device schedules HARQ-ACK retransmission.
  • An embodiment of the present application provides a method for sending and receiving side link feedback information, which is described from a first device and a second device.
  • the embodiment of the present application schematically illustrates the HARQ-ACK interaction between the first device and the second device, which may be combined with the embodiment of the first aspect or implemented separately.
  • FIG. 7 is a schematic diagram of a method for sending side link feedback information according to an embodiment of the present application. As shown in FIG. 7, the method includes:
  • the first device sends a Physical Sidelink Control Channel (PSCCH) and/or a Physical Sidelink Shared Channel (PSSCH) to a second device;
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • the first device receives multiple pieces of side link feedback information sent by the second device; where a Physical Side Link Feedback Channel (PSFCH) resource carrying multiple side link feedback information is at least composed of the multiple side link feedback information The number is determined.
  • PSFCH Physical Side Link Feedback Channel
  • the first device sends a certain TB to the second device on the PSSCH, and then receives a HARQ-ACK on a certain PSFCH resource associated with the PSSCH.
  • the physical layer structure of the physical channels and physical signals of the side link may change.
  • the PSSCH of the traditional side link has a granularity of sub-channel (sub-channel), including several continuous sub-channels in the frequency domain
  • the PSSCH of the unlicensed frequency band of the side link may have the granularity of interlace (interlace), including several frequency domains. Continuous or non-sequential interleaving.
  • one PSSCH resource is associated with one PSFCH resource.
  • P ID represents the physical layer source identification (physical layer source ID), for multicast with HARQ option 2
  • P ID represents the physical layer source identification (physical layer source ID)
  • M ID represents the identification of high-level configuration, in fact, it is the member identification (group member ID) in the group, for unicast and Multicast with HARQ option 1
  • M ID 0.
  • the above method can be adaptively extended, for example, sub-channels of PSSCH are replaced by interleaving of PSSCH, and PSFCH is extended from using only one RB to multiple RBs.
  • the candidate PSFCH resources it is determined that the candidate PSFCH resources.
  • the index of the PSFCH resource used to send multiple HARQ-ACK bits finally associated with the PSSCH cannot follow the existing method The formula is determined.
  • the first device sends one PSSCH but instructs the second device to feed back more than one HARQ-ACK bit.
  • the first device sends TB4 on the PSSCH, and at the same time instructs the second device to feed back 4 HARQ-ACK bits including HARQ-ACK retransmission in the SCI.
  • the first device transmits PSSCH1 (TB1), but the associated PSFCH time slot is outside the current COT.
  • the first device instructs the second device not to feed back HARQ-ACK temporarily in the SCI, or the second device transmits HARQ-ACK according to the PSFCH
  • the first device sends PSSCH2 (TB2), use SCI to instruct the second device to feedback HARQ-ACK1 for TB1 and HARQ for TB2 - Multiple HARQ-ACK bits including ACK2.
  • the physical side link feedback channel (PSFCH) resource carrying multiple side link feedback information is at least determined by the number of multiple side link feedback information.
  • the Physical Sidelink Feedback Channel (PSFCH) resource is determined by the following formula:
  • P ID represents a physical layer source ID (physical layer source ID)
  • M ID represents a group member ID (group member ID) configured by a high layer
  • the M ID represents an identifier configured by a higher layer, that is, a group member ID (group member ID).
  • group member ID group member ID
  • M ID 0.
  • M ID 0.
  • the number of the plurality of side link feedback information is determined based on an assignment index (AI, Assignment Index) field in the side link control information sent by the first device to the second device, and the assignment index is, for example, Called SAI.
  • AI Assignment Index
  • the value of Q may be obtained based on signaling sent by the first device to the second device. For example, based on the C-SAI/T-SAI field in the 2nd stage SCI.
  • the plurality of sidelink feedback information includes: feedback information for the currently scheduled physical sidelink control channel (PSCCH) and/or physical sidelink shared channel (PSSCH), and/or, for the previous Feedback information of the scheduled Physical Sidelink Control Channel (PSCCH) and/or Physical Sidelink Shared Channel (PSSCH).
  • PSCCH physical sidelink control channel
  • PSSCH physical sidelink shared channel
  • the Q HARQ-ACK bits include: HARQ-ACK bits for the currently scheduled PSSCH, and/or, HARQ-ACK bits for the previously scheduled PSSCH.
  • the currently scheduled physical side link control channel (PSCCH) and/or the transport block (TB) carried by the physical side link shared channel (PSSCH) is different from the previously scheduled physical side link control channel (PSCCH). ) and/or a transport block (TB) carried on a physical sidelink shared channel (PSSCH).
  • the first device sends PSSCH in multicast mode, and instructs the second device (group member device) to send Q HARQ-ACK bits.
  • the Q HARQ-ACK bits include the HARQ-ACK bits for the PSSCH, and the HARQ-ACK bits for the retransmission of the previous PSSCH.
  • each group member device in order to send Q HARQ-ACK bits, each group member device sends Q PSFCHs, and each PSFCH carries 1 bit of HARQ-ACK according to the existing method.
  • the PSFCH resource used by group member device 0 is
  • the PSFCH resource used by group member device 1 is
  • the PSFCH resource used by group member device 2 is and so on.
  • PSFCH resources of different group member devices are different from each other.
  • the above-mentioned method for the device to send Q HARQ-ACK bits is not limited to the application scenario of the unlicensed frequency band of the side link. The same approach can be extended to other scenarios as well.
  • the above method can be applied to a carrier aggregation (CA) scenario.
  • the first device sends multiple PSSCHs to the second device on multiple carriers through cross-carrier scheduling or self-scheduling, and the second device simultaneously sends multiple HARQ-ACK bits on a certain cell (such as Pcell) to the first device.
  • CA carrier aggregation
  • FIG. 8 is another example diagram of side link feedback information in the embodiment of the present application, including a complete sending and receiving process of Uu and side link.
  • the upper part of Figure 8 shows the Uu process, and the lower part shows the side link process.
  • the network device obtains COT1, and schedules the first device to send TB1 within COT1 (that is, the base station allocates resource PSSCH1 for the first device, and the first device determines to send TB1 on PSSCH1), indicating that it is on PUCCH1 Feedback HARQ-ACK1. Since the LBT of the second device for PSFCH1 fails (the second device does not send PSFCH1), the first device does not receive HARQ-ACK1 for TB1 on PSFCH1, so the first device does not send PUCCH1.
  • the base station schedules the first device to send TB2, and because the HARQ-ACK2 for TB2 is too late to be fed back in COT1, the base station instructs the first device not to feed back the HARQ-ACK2 temporarily. Since the PSFCH2 associated with TB2 is located outside COT1, the first device instructs the second device not to feed back HARQ-ACK2 temporarily in SCI2, or the second device judges that it does not need to feed back HARQ on PSFCH2 based on the time slot of PSFCH2 and the time length of COT1. -ACK2.
  • the first device receives HARQ-ACK1-HARQ-ACK3 sent by the second device on PSFCH3, and then sends HARQ-ACK1-HARQ-ACK3 to the base station on PUCCH2.
  • PSFCH3 refers to all PSFCHs associated with the PSSCH carrying TB3, that is, the PSFCH resource carrying Q HARQ-ACK bits from a certain second device, and the method of determining the PSFCH resource of Q HARQ-ACK bits as described above can be used. method. Similar to the way Uu uses DCI, the side link uses SCI to indicate G, C-SAI/T-SAI, so as to achieve the purpose of scheduling HARQ-ACK retransmission. For example, in FIG. 8 , SCI3 instructs the second device to simultaneously send multiple HARQ-ACK bits, including retransmission of HARQ-ACK1 and HARQ-ACK2.
  • the side link control information (SCI) sent by the first device to the second device indicates the grouping and/or retransmission of the side link feedback information independently of the information sent by the network device to the first device.
  • FIG. 9 is another example diagram of side link feedback information in the embodiment of the present application, including a complete sending and receiving process of Uu and side link.
  • the difference from Figure 8 is that the values of G, C-SAI/T-SAI indicated by the SCI can be different from the values of G, C-DAI/T-DAI indicated by the DCI due to the different PSFCH resources contained in the COT different.
  • DCI and SCI can also contain other fields, such as "new feedback indicator” field, "number of requested group(s)" field, etc.
  • the values in the SCI may be different from those in the DCI. Due to LBT failure, the second device does not send HARQ-ACK1 on PSFCH1. Therefore, the first device does not send PUCCH1. Through the G and C-SAI/T-SAI indicated by the SCI, the first device instructs the second device to feed back HARQ-ACK1 and HARQ-ACK2 on PSFCH2 associated with TB2.
  • multiple PSFCH resources carrying HARQ-ACK1 and HARQ-ACK2 can be determined by using the embodiment of the present application.
  • the first device receives the HARQ-ACK1 and HARQ-ACK2 in the PSFCH2 time slot, it is too late to send them to the base station on the PUCCH1.
  • the first device receives HARQ-ACK3 on PSFCH3, and then sends HARQ-ACK1 to HARQ-ACK3 to the base station on PUCCH2. It can be seen from Fig.
  • the first device can guarantee to send HARQ-ACK1 ⁇ HARQ-ACK3 to the base station on PUCCH2, as for how to receive HARQ-ACK1 ⁇ HARQ-ACK3 through the side link, it can be done by the first device itself. It is determined that it is not necessary to copy the scheduling of the HARQ-ACK by the base station in the DCI.
  • the base station instructs the first device to transmit on PSSCH1 in DCI1, and instructs the first device to feed back HARQ-ACK1 associated with PSSCH1 on PUCCH1.
  • the first device sends TB1 on PSSCH1. Since the second device did not send HARQ-ACK1 on PSFCH1 associated with PSSCH1 (for example, due to LBT failure), the first device did not receive HARQ-ACK1 on PSFCH1.
  • the first device does not send PUCCH1 to the base station. Since the PUCCH1 is not received, the base station knows that it can find an opportunity to schedule the first device to retransmit the HARQ-ACK1 later.
  • the base station instructs the first device to send on the PSSCH2 in DCI2, and instructs the first device not to feed back HARQ-ACK2 temporarily.
  • the first device sends TB2 on the PSSCH2, and instructs the second device to send HARQ-ACK1 and HARQ-ACK2 in the time slot of PSFCH2 in SCI2, that is, retransmission of HARQ-ACK1 is scheduled.
  • PSFCH2 may include more than one PSFCH resource, and these PSFCH resources are all associated with PSSCH2, that is, one PSSCH is associated with multiple PSFCH resources.
  • Q is determined according to the C-SAI/T-SAI field in SCI2, and is equal to the number of HARQ-ACK bits that the second device needs to send simultaneously, and is also equal to the size of the HARQ-ACK codebook.
  • the second device sends HARQ-ACK1 and HARQ-ACK2 in the PSFCH2 time slot.
  • the first device receives HARQ-ACK1 and HARQ-ACK2 in PSFCH2 time slot.
  • the base station instructs the first device to send on PSSCH3 in DCI3, and instructs the first device to feed back HARQ-ACK1 to HARQ-ACK3 on PUCCH2, that is, retransmission of HARQ-ACK1 and HARQ-ACK2 is scheduled.
  • the first device sends TB3 on PSSCH3, and instructs the second device to send HARQ-ACK3 on PSFCH3 time slot in SCI3.
  • the first device receives HARQ-ACK3 in PSFCH3 time slot.
  • the first device sends HARQ-ACK1 to HARQ-ACK3 to the base station on PUCCH2.
  • the first device receives information sent by the second device for indicating the number of PSFCHs that the second device can send simultaneously.
  • the second device may notify the first device of the number N of PSFCHs that it can transmit simultaneously, so that the first device determines and schedules the number Q of PSFCHs that the second device transmits simultaneously.
  • the first device guarantees that Q ⁇ N during scheduling.
  • N ⁇ N max where N max represents the maximum number of PSFCHs that the second device can transmit simultaneously, and N max depends on the capability of the device.
  • the second device determines the number Q of PSFCHs that are scheduled to be sent simultaneously by the second device, which is actually determining the size of the HARQ-ACK codebook sent by the second device.
  • a plurality of sidelink feedback information is determined as a whole to be discarded, wherein the highest priority among the plurality of sidelink feedback information is used for priority comparison.
  • the second device may need to send the HARQ-ACK codebook to the first device, and also need to send the HARQ-ACK to the third device. This may cause the number of PSFCHs simultaneously transmitted by the second device to exceed N max . At this time, the second device needs to discard some PSFCHs, that is, only send a part of PSFCHs. Existing priority rules only select several PSFCHs with the highest priority for transmission. In the case of HARQ-ACK codebooks, if only a part of HARQ-ACK in the HARQ-ACK codebook is sent, the HARQ-ACK codebook will be destroyed. Integrity, so that the first device fails to receive the HARQ-ACK codebook. Therefore, the HARQ-ACK codebook should be determined as a whole to determine whether it is discarded. The priority of the HARQ-ACK codebook is equal to the highest priority among all HARQ-ACKs included in the HARQ-ACK codebook.
  • the size of the HARQ-ACK codebook is additionally used to determine the PSFCH resource, thereby avoiding A PSFCH resource collision occurs.
  • An embodiment of the present application provides a device for sending side link feedback information.
  • the apparatus may be, for example, a terminal device (such as the aforementioned first device), or may be one or some components or components configured on the terminal device, and the content that is the same as that in the first and second embodiments will not be repeated here.
  • FIG. 10 is a schematic diagram of an apparatus for sending side link feedback information according to an embodiment of the present application.
  • an apparatus 1000 for sending side link feedback information includes:
  • a determining unit 1001 which determines whether the side link feedback information that needs to be carried by the physical uplink control channel is received and whether the side link feedback information that needs to be carried by the physical uplink control channel has been sent to the second device in the case that the physical uplink control channel needs to be sent to the network device.
  • the processing unit 1002 is configured to send the physical side link control channel associated with the side link feedback information to the second device when the side link feedback information that needs to be carried by the physical uplink control channel is not received and/or the physical side link shared channel, the physical uplink control channel is not sent.
  • all side link feedback information that needs to be carried by the physical uplink control channel has not been received, and the physical side link associated with all the side link feedback information has been sent to the second device In the case of the control channel and/or the physical side link shared channel, the processing unit 1002 does not send the physical uplink control channel.
  • the number or proportion of side link feedback information that is not received among the plurality of side link feedback information that needs to be carried by the physical uplink control channel is greater than a configured or preconfigured threshold, and has been sent to When the second device sends the physical side link control channel and/or the physical side link shared channel associated with the multiple side link feedback information, the processing unit 1002 does not send the physical uplink control channel.
  • the device further includes:
  • a sending unit 1003, configured to send the physical side link control channel and/or the physical side link shared channel to the second device.
  • the device further includes:
  • a receiving unit 1004 configured to receive information indicating retransmission of the side link feedback information sent by the network device when the physical uplink control channel is not received.
  • the first device is enabled to retransmit side link feedback information to the network device
  • the second device is enabled to retransmit side link feedback information to the first device.
  • the sending unit 1003 also sends capability information of whether the first device can support side link feedback information retransmission and/or whether the second device can support side link information to the network device Feedback information retransmission capability information.
  • the receiving unit 1004 further receives instruction information sent by the network device for enabling the first device to retransmit side link feedback information.
  • the receiving unit 1004 further receives capability information sent by the second device about whether the second device can support retransmission of side link feedback information.
  • the sending unit 1003 further sends indication information for enabling the second device to retransmit side link feedback information to the second device.
  • the receiving unit 1004 further receives a plurality of side link feedback information sent by the second device; wherein the physical side link feedback channel resources carrying the plurality of side link feedback information are at least determined by the The number of the multiple side link feedback information is determined.
  • the number of the plurality of side link feedback information is determined based on an allocation index field in the side link control information sent by the first device to the second device.
  • the plurality of side link feedback information includes: feedback information for the currently scheduled physical side link control channel and/or physical side link shared channel, and/or, for the previously scheduled physical side link Feedback information of link control channel and/or physical side link shared channel.
  • the currently scheduled physical side link control channel and/or the transport block carried by the physical side link shared channel is different from the previously scheduled physical side link control channel and/or physical side link A transport block carried by a shared channel.
  • the physical side link feedback channel resource is determined by the following formula:
  • P ID represents a physical layer source identifier
  • M ID represents a group member identifier configured by a high layer
  • Q represents the number of multiple side link feedback information
  • q 0,1,...,Q-1.
  • the information indicating the grouping and/or retransmission of the side link feedback information in the side link control information sent by the first device to the second device is independent of the information sent by the network device to the second device.
  • Information indicating grouping and/or retransmission of the side link feedback information in the downlink control information sent by the first device is independent of the information sent by the network device to the second device.
  • the receiving unit 1004 further receives information sent by the second device for indicating the number of physical side link feedback channels that the second device can send simultaneously.
  • the plurality of sidelink feedback information as a whole is determined to be discarded, wherein the highest priority among the plurality of sidelink feedback information is used for priority comparison.
  • the apparatus 1000 for sending side link feedback information may also include other components or modules, and for specific content of these components or modules, reference may be made to related technologies.
  • FIG. 10 only exemplarily shows the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the implementation of the present application is not limited thereto.
  • the first device for the HARQ-ACK retransmission from the first device to the network device, if the first device has sent the PSCCH and/or PSSCH associated with the HARQ-ACK to the second device, but has not received the PUCCH that needs to be carried by the PUCCH side link feedback information (that is, the PUCCH does not contain valid HARQ-ACK bits), the first device does not send the PUCCH to the network device, thereby reducing or avoiding unnecessary occupation of the unlicensed frequency band, and notifying the network The device schedules HARQ-ACK retransmission.
  • the size of the HARQ-ACK codebook is additionally used to determine the PSFCH resource, so that PSFCH resource collision can be avoided in the multicast HARQ-ACK retransmission.
  • An embodiment of the present application provides a device for sending side link feedback information.
  • the apparatus may be, for example, a terminal device (such as the aforementioned second device), or may be one or some components or components configured on the terminal device, and details that are the same as those in the first and second embodiments will not be repeated here.
  • FIG. 11 is a schematic diagram of an apparatus for sending side link feedback information according to an embodiment of the present application.
  • an apparatus 1100 for sending side link feedback information includes:
  • a receiving unit 1101 configured to receive the physical side link control channel and/or the physical side link shared channel sent by the first device;
  • a sending unit 1102 configured to send multiple pieces of side link feedback information to the first device; where the physical side link feedback channel resources of the multiple side link feedback information are at least composed of the multiple side link feedback information The number is determined.
  • the sending unit 1102 determines the number of the plurality of side link feedback information based on an allocation index field in the side link control information sent by the first device to the second device.
  • the plurality of side link feedback information includes: feedback information for a currently scheduled physical side link control channel (PSCCH) and/or physical side link shared channel (PSSCH), and/or, Feedback information for a previously scheduled Physical Sidelink Control Channel (PSCCH) and/or Physical Sidelink Shared Channel (PSSCH).
  • PSCCH physical side link control channel
  • PSSCH physical side link shared channel
  • the currently scheduled Physical Sidelink Control Channel (PSCCH) and/or the Physical Sidelink Shared Channel (PSSCH) carries a transport block (TB) different from the previously scheduled physical sidelink A transport block (TB) carried by a control channel (PSCCH) and/or a physical sidelink shared channel (PSSCH).
  • TB transport block
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • the Physical Sidelink Feedback Channel (PSFCH) resource is determined by the following formula:
  • P ID represents a physical layer source ID (physical layer source ID)
  • M ID represents a group member ID (group member ID) configured by a high layer
  • the sending unit 1102 determines not to feed back the side link feedback information according to the instruction of the first device, or the physical side link feedback channel (PSFCH) carrying the side link feedback information is located outside the channel occupancy time In a case where it is determined not to feed back the side link feedback information.
  • PSFCH physical side link feedback channel
  • the information indicating grouping and/or retransmission of side link feedback information in the side link control information (SCI) sent by the first device to the second device is independent of the information sent by the network device to the second device.
  • Information indicating grouping and/or retransmission of side link feedback information in downlink control information (DCI) sent by the first device is independent of the information sent by the network device to the second device.
  • the sending unit 1102 sends to the first device information for indicating the number of PSFCHs that the second device can send simultaneously.
  • the sending unit 1102 determines whether to discard the plurality of side link feedback information as a whole, wherein the highest priority among the plurality of side link feedback information is used for priority comparison.
  • the apparatus 1100 for sending side link feedback information may also include other components or modules, and for the specific content of these components or modules, please refer to related technologies.
  • FIG. 11 only exemplarily shows the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the implementation of the present application is not limited thereto.
  • the first device for the HARQ-ACK retransmission from the first device to the network device, if the first device has sent the PSCCH and/or PSSCH associated with the HARQ-ACK to the second device, but has not received the PUCCH that needs to be carried by the PUCCH side link feedback information (that is, the PUCCH does not contain valid HARQ-ACK bits), the first device does not send the PUCCH to the network device, thereby reducing or avoiding unnecessary occupation of the unlicensed frequency band, and notifying the network The device schedules HARQ-ACK retransmission.
  • the size of the HARQ-ACK codebook is additionally used to determine the PSFCH resource, so that PSFCH resource collision can be avoided in the multicast HARQ-ACK retransmission.
  • the embodiment of the present application also provides a communication system, which can be referred to FIG. 1 , and the same content as the embodiments of the first aspect to the fourth aspect will not be described again.
  • the communication system 100 may at least include:
  • the first device determines whether the side link feedback information that needs to be carried by the physical uplink control channel is received, and whether the side link feedback information that needs to be carried by the physical uplink control channel has been sent to the second device.
  • the physical side link control channel and/or the physical side link shared channel associated with the side link feedback information when the side link feedback information that needs to be carried by the physical uplink control channel has not been received, and has been sent to the second
  • the device sends the physical side link control channel and/or the physical side link shared channel associated with the side link feedback information, the physical uplink control channel is not sent; and/or
  • the second device receives the physical side link control channel and/or the physical side link shared channel sent by the first device; and sends a plurality of side link feedback information to the first device; wherein the plurality of side chains
  • the physical side link feedback channel resources of the channel feedback information are at least determined by the number of the plurality of side link feedback information.
  • the embodiment of the present application also provides a network device, which may be, for example, a base station, but the present application is not limited thereto, and may be other network devices.
  • a network device which may be, for example, a base station, but the present application is not limited thereto, and may be other network devices.
  • FIG. 12 is a schematic diagram of a network device according to an embodiment of the present application.
  • the network device 1200 may include: a processor 1210 (such as a central processing unit CPU) and a memory 1220 ; the memory 1220 is coupled to the processor 1210 .
  • the memory 1220 can store various data; in addition, it also stores a program 1230 for information processing, and executes the program 1230 under the control of the processor 1210 .
  • the processor 1210 may be configured to execute a program to implement the method for receiving side link feedback information as described in the embodiment of the first aspect.
  • the processor 1210 may be configured to perform the following control: receive side link feedback information carried by the first device through a physical uplink control channel; wherein, the physical uplink control channel (PUCCH) is determined by the first device It is sent when the side link feedback information carried by the physical uplink control channel has been received.
  • PUCCH physical uplink control channel
  • the network device 1200 may further include: a transceiver 1240 and an antenna 1250 ; wherein, the functions of the above components are similar to those of the prior art, and will not be repeated here. It should be noted that the network device 1200 does not necessarily include all the components shown in FIG. 12 ; in addition, the network device 1200 may also include components not shown in FIG. 12 , and reference may be made to the prior art.
  • the embodiment of the present application also provides a terminal device, but the present application is not limited thereto, and may be other devices.
  • FIG. 13 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 1300 may include a processor 1310 and a memory 1320 ; the memory 1320 stores data and programs, and is coupled to the processor 1310 . It is worth noting that this figure is exemplary; other types of structures may also be used in addition to or instead of this structure to implement telecommunications functions or other functions.
  • the processor 1310 may be configured to execute a program to implement the method for sending side link feedback information as described in the embodiment of the first aspect.
  • the processor 1310 may be configured to perform the following control: in the case where a physical uplink control channel (PUCCH) needs to be sent to the network device, determine whether the side link feedback information that needs to be carried by the physical uplink control channel is received, And whether the physical side link control channel (PSCCH) and/or physical side link shared channel (PSSCH) associated with the side link feedback information has been sent to the second device; if it needs to be carried by the physical uplink control channel The side link feedback information has not been received, and the physical side link control channel (PSCCH) and/or physical side link shared channel (PSSCH) associated with the side link feedback information has been sent to the second device Next, the physical uplink control channel (PUCCH) is not sent.
  • PUCCH physical uplink control channel
  • the processor 1310 may be configured to execute a program to implement the method for sending side link feedback information as described in the embodiment of the second aspect.
  • the processor 1310 may be configured to perform the following control: receive a Physical Sidelink Control Channel (PSCCH) and/or a Physical Sidelink Shared Channel (PSSCH) sent by the first device; and send multiple side link feedback information; wherein the physical side link feedback channel (PSFCH) resources of the plurality of side link feedback information are at least determined by the number of the plurality of side link feedback information.
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • the terminal device 1300 may further include: a communication module 1330 , an input unit 1340 , a display 1350 , and a power supply 1360 .
  • a communication module 1330 the terminal device 1300 may further include: a communication module 1330 , an input unit 1340 , a display 1350 , and a power supply 1360 .
  • the functions of the above components are similar to those of the prior art, and will not be repeated here. It should be noted that the terminal device 1300 does not necessarily include all the components shown in FIG. have technology.
  • the embodiment of the present application also provides a computer program, wherein when the program is executed in the terminal device, the program enables the terminal device to perform the sending of the side link feedback information described in the embodiments of the first and second aspects method.
  • the embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables the terminal device to execute the methods for sending side link feedback information in the embodiments of the first aspect and the second aspect.
  • An embodiment of the present application further provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method for receiving side link feedback information in the embodiment of the first aspect.
  • An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the method for receiving side link feedback information in the embodiment of the first aspect.
  • the above devices and methods in this application can be implemented by hardware, or by combining hardware and software.
  • the present application relates to a computer-readable program that, when executed by a logic component, enables the logic component to realize the above-mentioned device or constituent component, or enables the logic component to realize the above-mentioned various methods or steps.
  • the present application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memories, and the like.
  • the method/device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of both.
  • one or more of the functional block diagrams shown in the figure and/or one or more combinations of the functional block diagrams may correspond to each software module or each hardware module of the computer program flow.
  • These software modules may respectively correspond to the steps shown in the figure.
  • These hardware modules for example, can be realized by solidifying these software modules by using a Field Programmable Gate Array (FPGA).
  • FPGA Field Programmable Gate Array
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other form of storage medium known in the art.
  • a storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium, or it can be an integral part of the processor.
  • the processor and storage medium can be located in the ASIC.
  • the software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or large-capacity flash memory device.
  • One or more of the functional blocks described in the accompanying drawings and/or one or more combinations of the functional blocks can be implemented as a general-purpose processor, a digital signal processor (DSP) for performing the functions described in this application ), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof.
  • DSP digital signal processor
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • One or more of the functional blocks described in the drawings and/or one or more combinations of the functional blocks can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors processor, one or more microprocessors in communication with a DSP, or any other such configuration.
  • a method for sending side link feedback information comprising:
  • PUCCH physical uplink control channel
  • PSCCH physical side link control channel
  • PSSCH physical side link shared channel
  • the side link feedback information that needs to be carried by the physical uplink control channel has not been received, and the physical side link control channel (PSCCH) and/or the physical side link control channel (PSCCH) associated with the side link feedback information has been sent to the second device.
  • the first device does not send the physical uplink control channel (PUCCH).
  • Supplement 2 The method according to Supplement 1, wherein all side-link feedback information that needs to be carried by the physical uplink control channel has not been received, and all side-chain feedback information related to the side-chain has been sent to the second device
  • the first device does not send the physical uplink control channel (PUCCH).
  • Supplement 3 The method according to Supplement 1, wherein the number or proportion of side link feedback information that is not received among the multiple side link feedback information that needs to be carried by the physical uplink control channel is greater than the configured or a pre-configured threshold, and the physical side link control channel (PSCCH) and/or physical side link shared channel (PSSCH) associated with the plurality of side link feedback information have been sent to the second device,
  • the first device does not send the physical uplink control channel (PUCCH).
  • Supplementary Note 4 The method according to any one of Supplementary Notes 1 to 3, wherein the method further comprises:
  • the first device receives information indicating retransmission of the side link feedback information sent by the network device when the physical uplink control channel is not received.
  • Supplement 5 The method according to any one of Supplements 1 to 4, wherein the first device is enabled to retransmit side link feedback information to the network device, and the second device is enabled to Retransmit side link feedback information to the first device.
  • Supplementary Note 6 The method according to any one of Supplementary Notes 1 to 5, wherein the method further comprises:
  • the first device sends capability information of whether the first device can support retransmission of side link feedback information and/or capability information of whether the second device can support retransmission of side link feedback information to the network device .
  • Supplementary Note 7 The method according to any one of Supplementary Notes 1 to 6, wherein the method further comprises:
  • the first device receives indication information sent by the network device for enabling the first device to retransmit side link feedback information.
  • Supplementary Note 8 The method according to any one of Supplementary Notes 1 to 7, wherein the method further comprises:
  • the first device receives capability information sent by the second device about whether the second device can support retransmission of side link feedback information.
  • Supplementary Note 9 The method according to any one of Supplementary Notes 1 to 8, wherein the method further comprises:
  • the first device sends indication information for enabling the second device to retransmit side link feedback information to the second device.
  • Supplement 10 The method according to any one of Supplements 1 to 9, wherein the method further comprises:
  • PSCCH physical sidelink control channel
  • PSSCH physical sidelink shared channel
  • NACK non-acknowledgement
  • Supplement 11 The method according to any one of Supplements 1 to 10, wherein the method further comprises:
  • the first device receives a plurality of side link feedback information sent by the second device; wherein a Physical Side Link Feedback Channel (PSFCH) resource carrying the plurality of side link feedback information is composed of at least the plurality of side link feedback information
  • PSFCH Physical Side Link Feedback Channel
  • Supplementary Note 12 The method according to Supplementary Note 11, wherein the number of the plurality of side link feedback information is based on the allocation index in the side link control information sent by the first device to the second device ( AI, Assignment Index) field is determined.
  • Supplementary Note 13 The method according to Supplementary Note 11 or 12, wherein the plurality of side link feedback information includes: for the currently scheduled physical side link control channel (PSCCH) and/or physical side link shared channel (PSSCH) feedback information, and/or feedback information for a previously scheduled Physical Sidelink Control Channel (PSCCH) and/or Physical Sidelink Shared Channel (PSSCH).
  • PSCCH physical side link control channel
  • PSSCH physical side link shared channel
  • Supplementary Note 14 The method according to Supplementary Note 13, wherein the transport block (TB) carried by the currently scheduled Physical Sidelink Control Channel (PSCCH) and/or Physical Sidelink Shared Channel (PSSCH) is different from Transport Blocks (TBs) carried by the previously scheduled Physical Sidelink Control Channel (PSCCH) and/or Physical Sidelink Shared Channel (PSSCH).
  • transport block (TB) carried by the currently scheduled Physical Sidelink Control Channel (PSCCH) and/or Physical Sidelink Shared Channel (PSSCH) is different from Transport Blocks (TBs) carried by the previously scheduled Physical Sidelink Control Channel (PSCCH) and/or Physical Sidelink Shared Channel (PSSCH).
  • Supplement 15 The method according to any one of Supplements 11 to 14, wherein the physical side link feedback channel (PSFCH) resource is determined by the following formula:
  • P ID represents a physical layer source ID (physical layer source ID)
  • M ID represents a group member ID (group member ID) configured by a high layer
  • Supplement 16 The method according to any one of Supplements 11 to 15, wherein the side link feedback is indicated in the side link control information (SCI) sent by the first device to the second device
  • SCI side link control information
  • DCI downlink control information
  • Supplementary Note 17 The method according to any one of Supplementary Notes 11 to 16, wherein the method further comprises:
  • the first device receives information sent by the second device for indicating the number of PSFCHs that the second device can send simultaneously.
  • Supplementary Note 18 The method according to any one of Supplementary Notes 11 to 17, wherein the plurality of side link feedback information as a whole is determined whether to be discarded, wherein the highest among the plurality of side link feedback information Priority is used for priority comparison.
  • Supplement 19 The method according to any one of Supplements 1 to 18, wherein the method further comprises:
  • the first device sends the physical side link control channel (PSCCH) and/or the physical side link shared channel (PSSCH) to the second device.
  • PSCCH physical side link control channel
  • PSSCH physical side link shared channel
  • a method for sending side link feedback information comprising:
  • the second device receives a Physical Sidelink Control Channel (PSCCH) and/or a Physical Sidelink Shared Channel (PSSCH) sent by the first device; and
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • the second device sends a plurality of side link feedback information to the first device; wherein the physical side link feedback channel (PSFCH) resources of the plurality of side link feedback information are at least composed of the plurality of side link
  • PSFCH physical side link feedback channel
  • Supplementary Note 21 The method according to Supplementary Note 20, wherein the method further comprises:
  • the second device determines the number of the multiple pieces of side link feedback information based on an allocation index field in the side link control information sent by the first device to the second device.
  • Supplementary Note 22 The method according to Supplementary Note 20 or 21, wherein the plurality of side link feedback information includes: for the currently scheduled physical side link control channel (PSCCH) and/or physical side link shared channel (PSSCH) feedback information, and/or feedback information for a previously scheduled Physical Sidelink Control Channel (PSCCH) and/or Physical Sidelink Shared Channel (PSSCH).
  • PSCCH physical side link control channel
  • PSSCH physical side link shared channel
  • Supplementary Note 23 The method according to Supplementary Note 22, wherein the currently scheduled Physical Sidelink Control Channel (PSCCH) and/or the Transport Block (TB) carried by the Physical Sidelink Shared Channel (PSSCH) is different from Transport Blocks (TBs) carried by the previously scheduled Physical Sidelink Control Channel (PSCCH) and/or Physical Sidelink Shared Channel (PSSCH).
  • PSCCH Physical Sidelink Control Channel
  • TB Transport Block
  • Supplement 24 The method according to any one of Supplements 20 to 23, wherein the physical side link feedback channel (PSFCH) resource is determined by the following formula:
  • P ID represents a physical layer source ID (physical layer source ID)
  • M ID represents a group member ID (group member ID) configured by a high layer
  • Supplement 25 The method according to any one of Supplements 20 to 24, wherein the method further comprises:
  • the second device determines not to feed back the side link feedback information according to the instruction of the first device, or determines when the physical side link feedback channel (PSFCH) carrying the side link feedback information is located outside the channel occupancy time The side link feedback information is not fed back.
  • PSFCH physical side link feedback channel
  • Supplementary Note 26 The method according to any one of Supplementary Notes 20 to 25, wherein the Side Link Control Information (SCI) sent by the first device to the second device indicates the side link feedback information
  • SCI Side Link Control Information
  • DCI downlink control information
  • Supplement 27 The method according to any one of Supplements 20 to 26, wherein the method further comprises:
  • the second device sends to the first device information used to indicate the number of PSFCHs that the second device can send simultaneously.
  • Supplement 28 The method according to any one of Supplements 20 to 27, wherein the method further comprises:
  • the second device determines whether to discard the plurality of side link feedback information as a whole, wherein the highest priority among the plurality of side link feedback information is used for priority comparison.
  • a method for sending side link feedback information comprising:
  • the first device needs to send a physical uplink control channel (PUCCH) to the network device, determine whether the side link feedback information that needs to be carried by the physical uplink control channel is valid or whether it is a stuffing bit;
  • PUCCH physical uplink control channel
  • the first device does not send the physical uplink control channel (PUCCH).
  • PUCCH physical uplink control channel
  • Supplement 30 The method according to Supplement 29, wherein the first device has not received the side link feedback information and has sent the physical information associated with the side link feedback information to the second device In the case of a sidelink control channel (PSCCH) and/or a physical sidelink shared channel (PSSCH), it is determined that the sidelink feedback information is invalid or is a stuffing bit.
  • PSCCH sidelink control channel
  • PSSCH physical sidelink shared channel
  • Supplementary Note 31 The method according to Supplementary Note 29, wherein, in the case that all side-link feedback information that needs to be carried by the physical uplink control channel is invalid or all are padding bits, the first device does not send The physical uplink control channel (PUCCH).
  • PUCCH physical uplink control channel
  • Supplementary Note 32 The method according to Supplementary Note 29, wherein the number or proportion of invalid side-link feedback information or padding bits in the multiple side-link feedback information that needs to be carried by the physical uplink control channel is greater than the configured In the case of the specified or preconfigured threshold, the first device does not send the physical uplink control channel (PUCCH).
  • PUCCH physical uplink control channel
  • a method for receiving side link feedback information comprising:
  • the network device receives side link feedback information carried by the first device through a physical uplink control channel
  • the physical uplink control channel (PUCCH) is sent by the first device when it is determined that the side link feedback information that needs to be carried by the physical uplink control channel has been received.
  • Supplementary note 34 The method according to supplementary note 33, wherein the side link feedback information that needs to be carried by the physical uplink control channel is not received by the first device, and the first device has sent the second When the device sends the physical side link control channel (PSCCH) and/or the physical side link shared channel (PSSCH) associated with the side link feedback information, the physical uplink control channel (PUCCH) is not used by the The first device sends.
  • PSCCH physical side link control channel
  • PSSCH physical side link shared channel
  • Supplementary note 35 The method according to supplementary note 34, wherein all side link feedback information that needs to be carried by the physical uplink control channel has not been received by the first device, and the first device has sent When the second device sends the Physical Sidelink Control Channel (PSCCH) and/or the Physical Sidelink Shared Channel (PSSCH) associated with all the sidelink feedback information, the Physical Uplink Control Channel (PUCCH) does not sent by the first device.
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • Supplement 36 The method according to Supplement 34, wherein, among the multiple side link feedback information that needs to be carried by the physical uplink control channel, the number of side link feedback information that is not received by the first device or the ratio is greater than a configured or pre-configured threshold, and the first device has sent a physical sidelink control channel (PSCCH) and/or a physical sidechain associated with the plurality of sidelink feedback information to the second device In the case of a channel shared channel (PSSCH), the physical uplink control channel (PUCCH) is not sent by the first device.
  • PSSCH channel shared channel
  • PUCCH physical uplink control channel
  • Supplementary Note 37 The method according to any one of Supplementary Notes 33 to 36, wherein the method further comprises:
  • the network device does not receive the physical uplink control channel, send information for instructing retransmission of the side link feedback information to the first device.
  • Supplement 38 The method according to any one of Supplements 33 to 37, wherein the first device is enabled to retransmit side link feedback information to the network device, and the second device is enabled to Retransmit side link feedback information to the first device.
  • Supplement 39 The method according to any one of Supplements 33 to 38, wherein the method further comprises:
  • the network device receives the capability information sent by the first device whether the first device can support retransmission of side link feedback information and/or whether the second device can support retransmission of side link feedback information information.
  • Supplement 40 The method according to any one of Supplements 33 to 39, wherein the method further comprises:
  • the network device sends indication information for enabling the first device to retransmit side link feedback information to the first device.
  • a terminal device including a memory and a processor, the memory stores a computer program, and the processor is configured to execute the computer program to realize the edge as described in any one of Supplements 1 to 32.
  • the method for sending link feedback information is configured to send link feedback information.
  • a network device including a memory and a processor, the memory stores a computer program, and the processor is configured to execute the computer program to implement the edge described in any one of Supplements 33 to 40.
  • the method for receiving link feedback information including a memory and a processor, the memory stores a computer program, and the processor is configured to execute the computer program to implement the edge described in any one of Supplements 33 to 40. The method for receiving link feedback information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供一种边链路反馈信息的发送和接收方法以及装置。对于第一设备向网络设备的HARQ-ACK重传，如果第一设备已经向第二设备发送与HARQ-ACK关联的PSCCH和/或PSSCH，但没有接收到需要由PUCCH承载的边链路反馈信息，则第一设备不向网络设备发送该PUCCH，从而可以减少或避免对非授权频段不必要的占用，并且可以通知网络设备调度HARQ-ACK重传。对于第二设备向第一设备的HARQ-ACK重传，HARQ-ACK码书的大小被额外地用于确定PSFCH资源，从而可以避免在组播的HARQ-ACK重传中发生PSFCH资源碰撞。

Description

边链路反馈信息的发送和接收方法以及装置 技术领域
本申请实施例涉及通信技术领域。
背景技术
3GPP对Uu接口如何利用非授权(unlicensed)频段进行了标准化，5G NR的标准化工作主要包括Release 16的NR-U立项和正在进行中的Release 17的52.6GHz～71GHz立项。在技术上，使用非授权频段增加了Uu接口可用的频谱资源，这些额外的频谱资源有利于提升数据速率(或吞吐量)、提高可靠性、降低时延等。在应用上，非授权频段可以和授权频段联合部署，使用授权频段来辅助对非授权频段的使用，或者，非授权频段可以独立部署。相关应用场景包括任何与其他无线接入技术(例如WIFI)共存的场景、使用非授权频段的工业物联网(IIoT)场景等。
3GPP对边链路进行了标准化，5G NR的标准化工作包括Release 16的V2X立项和正在进行中的Release 17的sidelink立项。Rel-16NR V2X定义的物理信道包括物理边链路控制信道(PSCCH，Physical Sidelink Control Channel)、物理边链路共享信道(PSSCH，Physical Sidelink Shared Channel)和物理边链路反馈信道(PSFCH，Physical Sidelink Feedback Channel)。PSCCH承载1st stage边链路控制信息(SCI，Sidelink Control Informaiton)，1st stage SCI主要用于预留资源。PSSCH承载2nd stage SCI以及传输块(TB，Transport Block)，其中2nd stage SCI主要用于TB解调。
PSFCH承载边链路反馈信息(可称为HARQ-ACK)。PSCCH和PSSCH一般在同一个时隙发送。一个PSCCH/PSSCH按照既定规则关联到一个或多个PSFCH资源，设备在发送PSCCH/PSSCH后，即可在关联的PSFCH资源上去接收确认(ACK)/非确认(NACK)。NR V2X对于单播和组播支持HARQ-ACK反馈。组播又包括HARQ选项1和HARQ选项2两种HARQ-ACK反馈方式。
对于HARQ选项1的组播，只有在一定的通信范围(communication range)内的接收设备才会反馈HARQ-ACK，并且使用一种只反馈NACK(NACK-only)的方式，发送设备不知道NACK具体是哪一个接收设备发送的。对于HARQ选项2的组播，每个接收设备用于反馈ACK/NACK的PSFCH资源是独立的，发送设备知道ACK/ NACK是由哪一个接收设备发送的。
边链路发送所使用的资源(时频资源)位于某一资源池内。NR V2X定义了两种工作模式。对于NR V2X模式1(Mode 1)，终端设备用于V2X通信的资源由网络设备(基站)通过NR Uu链路进行调度或配置。对于NR V2X模式2(Mode 2)，终端设备可以基于感知结果，自主地对用于V2X通信的时频资源进行选择。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
发明人发现：3GPP目前正在讨论Release 18的立项，SL-U(Sidelink-Unlicensed)是候选的立项内容之一。对于SL-U，HARQ-ACK重传也是必要功能之一，如何在SL-U中支持HARQ-ACK重传目前仍然是一个开放性的问题。
针对上述问题的至少之一，本申请实施例提供一种边链路反馈信息的发送和接收方法以及装置。
根据本申请实施例的一个方面，提供一种边链路反馈信息的发送方法，包括：
第一设备在需要向网络设备发送物理上行控制信道(PUCCH)的情况下，确定需要由所述物理上行控制信道承载的边链路反馈信息是否被接收，以及是否已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)；
在需要由所述物理上行控制信道承载的边链路反馈信息没有被接收，以及已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的情况下，所述第一设备不发送所述物理上行控制信道(PUCCH)。
根据本申请实施例的另一个方面，提供一种边链路反馈信息的发送装置，包括：
确定单元，其在需要向网络设备发送物理上行控制信道的情况下，确定需要由所述物理上行控制信道承载的边链路反馈信息是否被接收，以及是否已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道和/或物理边链路共享信道；
处理单元，其在需要由所述物理上行控制信道承载的边链路反馈信息没有被接收， 以及已经向所述第二设备发送与所述边链路反馈信息关联的物理边链路控制信道和/或物理边链路共享信道的情况下，不发送所述物理上行控制信道。
根据本申请实施例的另一个方面，提供一种边链路反馈信息的发送方法，包括：
第二设备接收第一设备发送的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)；以及
所述第二设备向所述第一设备发送多个边链路反馈信息；其中所述多个边链路反馈信息的物理边链路反馈信道(PSFCH)资源至少由所述多个边链路反馈信息的数目确定。
根据本申请实施例的另一个方面，提供一种边链路反馈信息的发送装置，包括：
接收单元，其接收第一设备发送的物理边链路控制信道和/或物理边链路共享信道；以及
发送单元，其向所述第一设备发送多个边链路反馈信息；其中所述多个边链路反馈信息的物理边链路反馈信道资源至少由所述多个边链路反馈信息的数目确定。
根据本申请实施例的另一个方面，提供一种通信系统，包括：
第一设备，其在需要向网络设备发送物理上行控制信道的情况下，确定需要由所述物理上行控制信道承载的边链路反馈信息是否被接收，以及是否已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道和/或物理边链路共享信道；在需要由所述物理上行控制信道承载的边链路反馈信息没有被接收，以及已经向所述第二设备发送与所述边链路反馈信息关联的物理边链路控制信道和/或物理边链路共享信道的情况下，不发送所述物理上行控制信道；和/或
第二设备，其接收第一设备发送的物理边链路控制信道和/或物理边链路共享信道；以及向所述第一设备发送多个边链路反馈信息；其中所述多个边链路反馈信息的物理边链路反馈信道资源至少由所述多个边链路反馈信息的数目确定。
本申请实施例的有益效果之一在于：对于第一设备向网络设备的HARQ-ACK重传，如果第一设备已经向第二设备发送与HARQ-ACK关联的PSCCH和/或PSSCH，但没有接收到需要由PUCCH承载的边链路反馈信息(即，PUCCH不包含有效的HARQ-ACK比特)，则第一设备不向网络设备发送该PUCCH，从而可以减少或避免对非授权频段不必要的占用，并且可以通知网络设备调度HARQ-ACK重传。对于第二设备向第一设备的HARQ-ACK重传，HARQ-ACK码书的大小被额外地用于确定 PSFCH资源，从而可以避免在组播的HARQ-ACK重传中发生PSFCH资源碰撞。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
图1是本申请实施例的通信系统的示意图；
图2是NR-U中的HARQ-ACK重传的一示例图；
图3是NR V2X中Mode 1资源分配的一示例图；
图4是本申请实施例的边链路反馈信息的发送方法的一示意图；
图5是本申请实施例中边链路反馈信息的一示例图；
图6是本申请实施例中边链路反馈信息的另一示例图；
图7是本申请实施例的边链路反馈信息的发送方法的另一示意图；
图8是本申请实施例中边链路反馈信息的另一示例图；
图9是本申请实施例中边链路反馈信息的另一示例图；
图10是本申请实施例的边链路反馈信息的发送装置的一示意图；
图11是本申请实施例的边链路反馈信息的发送装置的另一示意图；
图12是本申请实施例的网络设备的示意图；
图13是本申请实施例的终端设备的示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio  Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femeto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)或者“终端设备”(TE，Terminal Equipment或Terminal Device)例如是指通过网络设备接入通信网络并接收网络服务的设备。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
此外，术语“网络侧”或“网络设备侧”是指网络的一侧，可以是某一基站，也可以包括如上的一个或多个网络设备。术语“用户侧”或“终端侧”或“终端设备侧”是指用户或终端的一侧，可以是某一UE，也可以包括如上的一个或多个终端设备。本文在没有特别指出的情况下，“设备”可以指网络设备，也可以指终端设备。
以下通过示例对本申请实施例的场景进行说明，但本申请不限于此。
图1是本申请实施例的通信系统的示意图，示意性说明了以终端设备和网络设备为例的情况，如图1所示，通信系统100可以包括网络设备101和终端设备102、103。为简单起见，图1仅以两个终端设备和一个网络设备为例进行说明，但本申请实施例不限于此。
在本申请实施例中，网络设备101和终端设备102、103之间可以进行现有的业务或者未来可实施的业务发送。例如，这些业务可以包括但不限于：增强的移动宽带(eMBB，enhanced Mobile Broadband)、大规模机器类型通信(mMTC，massive  Machine Type Communication)和高可靠低时延通信(URLLC，Ultra-Reliable and Low-Latency Communication)，等等。
值得注意的是，图1示出了两个终端设备102、103均处于网络设备101的覆盖范围内，但本申请不限于此。两个终端设备102、103可以均不在网络设备101的覆盖范围内，或者一个终端设备102在网络设备101的覆盖范围之内而另一个终端设备103在网络设备101的覆盖范围之外。
在本申请实施例中，两个终端设备102、103之间可以进行边链路发送。例如，两个终端设备102、103可以都在网络设备101的覆盖范围之内进行边链路发送以实现V2X通信，也可以都在网络设备101的覆盖范围之外进行边链路发送以实现V2X通信，还可以一个终端设备102在网络设备101的覆盖范围之内而另一个终端设备103在网络设备101的覆盖范围之外进行边链路发送以实现V2X通信。
为了不影响与之共存的其他无线接入技术，对非授权频段的使用需要遵守相关法规(regulation)，法规对于发射功率、占用带宽、信道占用时间(COT，Channel Occupancy Time)、信道接入机制等进行了规定。
以信道接入机制为例，LBT(Listen Before Talk)是使用非授权频段时的一个重要方式。对于NR-U，设备(基站或终端设备)只有在LBT成功时，才能够使用非授权频段进行发送。如果LBT失败，则设备不能使用非授权频段进行发送。LBT失败会对NR Uu的某些传统流程带来影响，例如会对NR的HARQ反馈过程带来影响。更具体地，LBT失败可能导致设备没有向基站反馈HARQ-ACK，或者，由于HARQ-ACK反馈时刻无法位于当前COT之内，因此设备没有向基站反馈HARQ-ACK。
NR-U对HARQ过程进行了增强，其中一项增强是引入了增强的Type-2 HARQ-ACK码书(codebook)，从而支持对原有Type-2 HARQ-ACK码书的分组和对HARQ-ACK比特的重传。增强的Type-2 HARQ-ACK码书的细节可以参考标准TS 38.213的9.1.3.3小节。
图2是NR-U中的HARQ-ACK重传的一示例图，对NR-U中的HARQ-ACK重传进行了示意性说明。为简单起见，以一个载波(或cell)为例进行说明，可以轻易扩展到载波聚合的场景。DCI中包含“PDSCH group index”字段(G)、DAI字段(C-DAI/T-DAI)、“new feedback indicator”字段(F)、“number of requested PDSCH group(s)”字段(R)。G指示当前PDSCH以及关联的HARQ-ACK属于哪一组(group)， 总共有两组可供选择；DAI在组内进行计数，计数方法与传统Type-2 HARQ-ACK码书相同；F指示是否清空该组之前的HARQ-ACK以及DAI，F值翻转表示清空；R指示反馈针对哪一组的HARQ-ACK，R＝0表示反馈当前DCI调度的组的HARQ-ACK，R＝1表示反馈两个组的HARQ-ACK。
如图2所示，基站向设备发送PDSCH，在COT1内，使用DCI 1调度TB 1，使用DCI 2调度TB 2，并指示设备在PUCCH 1上反馈包含HARQ-ACK 1和HARQ-ACK 2的HARQ-ACK码书。基站使用DCI 3调度TB 3，考虑到设备来不及在当前COT1内反馈HARQ-ACK 3，因此基站通过在“HARQ feedback timing”字段指示一个非数字取值，指示设备暂时不反馈HARQ-ACK3。基站通过分组(G)可以达到上述目的。
由于LBT失败，设备没有在PUCCH 1上发送HARQ-ACK 1和HARQ-ACK 2。至此，基站在COT 1内并没有接收到HARQ-ACK 1～HARQ-ACK 3。然而，基站可以在之后调度设备重传HARQ-ACK 1～HARQ-ACK 3。
基站在COT 2内使用DCI 4调度TB 4，指示设备反馈针对两个组的HARQ-ACK，即反馈HARQ-ACK 1～HARQ-ACK 4。虽然设备之前没有机会发送HARQ-ACK 1～HARQ-ACK 3，但基站在调度设备反馈HARQ-ACK 4时，也调度设备重传了HARQ-ACK 1～HARQ-ACK 3，从而实现了HARQ-ACK重传。
另一方面，NR V2X定义了两种工作模式Mode 1和Mode 2。
图3是NR V2X中Mode 1资源分配的一示例图，对Mode 1资源分配方式进行了示意性说明。如图3所示，网络设备(gNB)使用DCI为发送设备(TX UE)分配资源。TX UE在分配的资源上向接收设备(RX UE)发送PSCCH/PSSCH，并接收RX UE发送的承载边链路HARQ-ACK的PSFCH。TX UE通过PUCCH向gNB发送边链路HARQ-ACK。其中，DCI和PUCCH通过Uu接口发送，PSSCH和PSFCH通过边链路PC5接口发送。根据标准，如果TX UE没有接收到PSFCH，则向gNB反馈NACK。
3GPP目前正在讨论Release 18的立项，其中SL-U(Sidelink-Unlicensed)是候选的立项内容之一。SL-U使用非授权频段进行边链路通信，即设备与设备间的通信。SL-U通过设备间直接通信，可以进一步降低时延，同样地，SL-U也可以通过对额外频谱的利用来提升边链路传输的数据速率和可靠性。感兴趣的应用场景包括网络控制的交互服务(NCIS，Network Controlled Interactive Service)、工业物联网(IIoT)、车 联网、智能家庭(smart home)等。
目前3GPP主要讨论SL-U立项的必要性以及可能的研究内容，并不涉及任何技术细节。如前所述，现有标准支持在非授权频段上进行基于Uu接口的通信，即基站与设备间的通信。此外，3GPP对使用授权频段的边链路通信进行了标准化。
然而，对于使用非授权频段进行边链路通信的SL-U，其技术细节还没有被3GPP讨论。对于SL-U，HARQ-ACK重传也是必要功能之一，如何在SL-U中支持HARQ-ACK重传目前仍然是一个开放性的问题。复杂性更加体现在边链路的Mode 1资源分配，其中，TX UE可能既需要向基站重传边链路HARQ-ACK，又需要请求或触发RX UE向TX UE重传边链路HARQ-ACK，这都需要新的方法来实现上述双重的HARQ-ACK重传，现有的HARQ-ACK重传方法无法直接应用于SL-U。
在以下的说明中，在不引起混淆的情况下，术语“边链路”和“V2X”可以互换，术语“PSFCH”和“边链路反馈信道”可以互换，术语“PSCCH”和“边链路控制信道”或“边链路控制信息”可以互换，术语“PSSCH”和“边链路数据信道”或“边链路数据”也可以互换。
另外，发送(transmitting)或接收(receiving)PSCCH可以理解为发送或接收由PSCCH承载的边链路控制信息；发送或接收PSSCH可以理解为发送或接收由PSSCH承载的边链路数据；发送或接收PSFCH可以理解为发送或接收由PSFCH承载的边链路反馈信息。边链路发送(Sidelink transmission，也可称为边链路传输)可以理解为PSCCH/PSSCH发送或者边链路数据/信息发送。
在本申请实施例中，第一设备指边链路的发送设备，第二设备指边链路的接收设备，HARQ-ACK重传指HARQ-ACK比特的重传，HARQ-ACK是针对PSCCH/PSSCH的HARQ-ACK，PSCCH/PSSCH也简称为PSSCH，SCI可以指1st stage SCI和/或2nd stage SCI。
在本申请实施例中，第一设备接收来自第二设备的边链路HARQ-ACK(一个或多个HARQ-ACK比特)，并且根据上述来自第二设备的边链路HARQ-ACK确定通过PUCCH向网络设备(基站)发送的反馈信息(例如HARQ-ACK)，该确定向网络设备(基站)发送的反馈信息的过程可以遵循现有标准，可以参见TS 38.213的16.5小节。在本申请实施例中，“需要由PUCCH承载的反馈信息没有被第一设备接收”，指“其关联的来自第二设备的边链路HARQ-ACK没有被第一设备接收”。
第一方面的实施例
本申请实施例提供一种边链路反馈信息的发送和接收方法，从第一设备和网络设备进行说明。
图4是本申请实施例的边链路反馈信息的发送方法的一示意图，如图4所示，该方法包括：
401，第一设备在需要向网络设备发送物理上行控制信道(PUCCH)的情况下，确定需要由所述物理上行控制信道承载的边链路反馈信息是否被接收，以及是否已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)；
402，在需要由所述物理上行控制信道承载的边链路反馈信息没有被接收，以及已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的情况下，第一设备不发送所述物理上行控制信道(PUCCH)。
值得注意的是，以上附图4仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图4的记载。
在一些实施例中，第一设备向第二设备发送物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)。
在一些实施例中，在需要由所述物理上行控制信道承载的所有边链路反馈信息均没有被接收，并且已经向第二设备发送与所述所有边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的情况下，第一设备不发送所述物理上行控制信道(PUCCH)。
在一些实施例中，在需要由所述物理上行控制信道承载的多个边链路反馈信息中没有被接收的边链路反馈信息的数目或比例大于配置的或预配置的阈值，并且已经向第二设备发送与所述多个边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的情况下，第一设备不发送所述物理上行控制信道(PUCCH)。
在一些实施例中，第一设备在需要向网络设备发送物理上行控制信道(PUCCH)的情况下，确定需要由所述物理上行控制信道承载的边链路反馈信息是否有效或者是否为填充比特；在需要由所述物理上行控制信道承载的边链路反馈信息无效或者为填充比特的情况下，第一设备不发送所述物理上行控制信道(PUCCH)。
在一些实施例中，第一设备在所述边链路反馈信息没有被接收，以及已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的情况下，确定所述边链路反馈信息无效或者为填充比特。
在一些实施例中，在需要由所述物理上行控制信道承载的所有边链路反馈信息均无效或者均为填充比特的情况下，第一设备不发送所述物理上行控制信道(PUCCH)。
在一些实施例中，在需要由所述物理上行控制信道承载的多个边链路反馈信息中无效的边链路反馈信息或者填充比特的数目或比例大于配置的或预配置的阈值的情况下，第一设备不发送所述物理上行控制信道(PUCCH)。
图5是本申请实施例中边链路反馈信息的一示例图。如图5所示，网络设备(基站)使用DCI为设备1(第一设备或发送设备)分配用于发送PSSCH的资源，并指示用于发送边链路HARQ-ACK的PUCCH资源。PSSCH资源位于非授权频段，DCI可以使用非授权频段或授权频段发送，PUCCH可以使用非授权频段或授权频段发送。
以下从基站的角度进行说明。DCI1和DCI2指示组0(G＝0)以及在组0内计数的C-DAI和T-DAI，并指示设备1在PUCCH1上反馈针对组0的HARQ-ACK，即HARQ-ACK1和HARQ-ACK2。DCI3指示组1(G＝1)以及在组1内计数的C-DAI和T-DAI。考虑到设备1来不及在COT1内(或在PUCCH1上)反馈针对DCI3(或TB3)的HARQ-ACK3，DCI3指示设备1暂时不反馈HARQ-ACK3。
以下从设备1的角度进行说明。设备1在DCI1和DCI2分配的资源上发送了TB1和TB2。为了在PUCCH1上向基站发送针对TB1和TB2的HARQ-ACK1和HARQ-ACK2，设备1需要在时间t1之前获得来自设备2(第二设备或接收设备)的HARQ-ACK1和HARQ-ACK2。然而，截至t1，设备1可能没有接收到HARQ-ACK1和HARQ-ACK2。在这种情况下，设备1不发送PUCCH1。因此，基站在PUCCH1上不会接收到HARQ-ACK1和HARQ-ACK2，从而基站可以选择在下一个COT(COT2)调度设备1对HARQ-ACK1和HARQ-ACK2进行重传(重传给基站)，而不调度设备1对TB1和TB2进行重传(重传给设备2)。例如，基站使用DCI4为设备1分配发 送TB4的资源，同时，DCI4指示设备1在PUCCH2上反馈针对组0和组1的HARQ-ACK，即HARQ-ACK1～HARQ-ACK4，从而实现了对HARQ-ACK1和HARQ-ACK2的重传。为获得HARQ-ACK1和HARQ-ACK2，设备1不对TB1和TB2进行重传，而是指示设备2对HARQ-ACK1和HARQ-ACK2进行重传。例如，设备1使用与基站调度设备1重传HARQ-ACK类似的方法来指示设备2重传HARQ-ACK，在接收到DCI4后，设备1通过SCI指示设备2对HARQ-ACK1和HARQ-ACK2进行重传，设备1在SCI中指示G、SAI等参数，参数可以独立确定，可以与基站DCI指示的参数相同或不同。由于没有对TB1和TB2进行重传，因此减少了对非授权频段的占用，避免了对使用非授权频段的其他设备产生干扰。此外，当PUCCH位于非授权频段时，设备1不发送PUCCH1同样可以减少对非授权频段的占用，避免对使用非授权频段的其他设备产生干扰。
为简单起见，图5中仅示出了DCI中的“group index”字段(G)和DAI字段(C-DAI/T-DAI)，为实现HARQ-ACK重传功能，DCI中还可以包含其他字段，例如“new feedback indicator”字段、“number of requested group(s)”字段等，这些被省略的字段的用法与现有NR-U标准中的用法相同。
图6是本申请实施例中边链路反馈信息的另一示例图，示出了如果沿用现有方案的情况。如图6所示，设备1在没有接收到HARQ-ACK1和HARQ-ACK2的情况下，会向基站发送NACK1和NACK2，即填充了NACK。基站在接收到NACK1和NACK2后，会认为设备解调译码失败，从而继续调度设备1对TB1和TB2进行重传，而不会调度设备1对HARQ-ACK1和HARQ-ACK2进行重传。对TB1和TB2的重传额外占用了非授权频段，降低了资源利用率，并有可能对其他设备造成干扰。
因此，相比于在PUCCH1上发送NACK，不发送PUCCH1实际上相当于向基站传递了一种不同于ACK和NACK的额外的状态信息。基于该信息，基站可以仅调度HARQ-ACK重传，而不调度PSSCH重传，从而可以减少对非授权频段的占用。
图5以PUCCH1包含HARQ-ACK1和HARQ-ACK2为例进行示意性说明，实际上PUCCH1可以只包含一个HARQ-ACK，也可以包含更多的HARQ-ACK，本申请实施例不限于此。
本申请实施例对于设备1没有接收到HARQ-ACK(例如HARQ-ACK 1和HARQ-ACK 2)的原因不做限制。例如，设备2由于LBT失败，没有向设备1发送HARQ-ACK。 又例如，设备2需要同时发送或接收具有更高优先级的其他信号，基于优先规则，设备2没有向设备1发送HARQ-ACK。又例如，虽然设备2向设备1发送了HARQ-ACK，但设备1需要同时发送具有更高优先级的其他信号，基于优先规则，设备1没有接收设备2发送的HARQ-ACK。
当PUCCH位于非授权频段时，设备1不发送PUCCH1可以包括以下行为。例如，设备1不针对PUCCH1进行LBT。又例如，设备1针对PUCCH1进行的LBT成功，但是设备1仍然不发送PUCCH1。
在一些实施例中，在由于LBT失败而没有向第二设备发送PSCCH和/或PSSCH的情况下，第一设备向网络设备发送非确认(NACK)信息。
作为一种实施方式，对于除上述情况之外的第一设备没有接收到HARQ-ACK的其他情况，第一设备向基站发送NACK。
作为一种实施方式，在第一设备由于LBT失败，因而没有发送PSSCH的情况下，第一设备向基站发送NACK。
例如，第一设备由于LBT失败，因而没有向第二设备发送PSSCH，包括没有在DCI调度的资源上发送PSSCH，也包括没有在配置授权(configured grant)的资源上发送PSSCH。此时第一设备也不会接收到来自第二设备的HARQ-ACK。在这种情况下，第一设备向基站发送NACK。基站接收到NACK后，会继续为第一设备分配资源，第一设备可以在分配的资源上继续发送PSSCH。
作为一种实施方式，对于除上述情况之外的第一设备没有接收到HARQ-ACK的其他情况，当没有接收到的HARQ-ACK的数目或比例大于某一阈值时，第一设备不发送PUCCH；否则，第一设备将没有接收到的HARQ-ACK填充为NACK。
例如，在PUCCH承载的所有HARQ-ACK比特中，如果第一设备仅接收到一部分HARQ-ACK比特，在没有接收到的HARQ-ACK比特的数目大于某一阈值的情况下，或者，在没有接收到的HARQ-ACK比特占所有HARQ-ACK比特的比例大于某一阈值的情况下，第一设备不发送PUCCH；否则，第一设备将没有接收到的HARQ-ACK填充为NACK。这里“大于”也可以被替换为“大于等于”。阈值可以是配置或预配置的。
在一些实施例中，网络设备在没有接收到所述物理上行控制信道的情况下，发送用于指示对所述边链路反馈信息进行重传的信息。第一设备接收到该用于指示对所述 边链路反馈信息进行重传的信息，可以触发对所述边链路反馈信息的重传。
在一些实施例中，第一设备被使能(enabled)向所述网络设备重传边链路反馈信息，并且所述第二设备被使能向所述第一设备重传边链路反馈信息。
即，可选地，第一设备不发送PUCCH的行为需要满足以下条件：第一设备被使能了向基站重传HARQ-ACK的功能，并且第二设备被使能了向第一设备重传HARQ-ACK的功能。
设备需要具有一定的能力来支持对HARQ-ACK比特的重传。例如，图5中设备1需要有能力暂时保存HARQ-ACK3，在未来某一时刻重传HARQ-ACK3。又例如，图5中由于设备1接收到DCI4后，会进一步指示设备2重传HARQ-ACK1和HARQ-ACK2，因此设备2需要有能力在之前一直保存有HARQ-ACK1和HARQ-ACK2的结果。
等价地，支持HARQ-ACK重传的能力也可以称为支持增强型HARQ-ACK码书(enhanced HARQ-ACK codebook)的能力。例如图5所示，重传的HARQ-ACK比特以HARQ-ACK码书的形式发送给基站。在不产生混淆的条件下，以下也将其简称为能力。
设备与设备之间，和/或，设备与基站之间可以交互支持HARQ-ACK重传的能力，从而基站可以通过配置来使能第一设备进行HARQ-ACK重传，和/或，第一设备可以通过配置来使能第二设备进行HARQ-ACK重传。
在一些实施例中，第一设备向网络设备发送第一设备能否支持边链路反馈信息重传的能力信息和/或第二设备能否支持边链路反馈信息重传的能力信息。
在一些实施例中，第一设备接收网络设备发送的用于使能第一设备进行边链路反馈信息重传的指示信息。
在一些实施例中，第一设备接收第二设备发送的第二设备能否支持边链路反馈信息重传的能力信息。
在一些实施例中，第一设备向第二设备发送用于使能第二设备进行边链路反馈信息重传的指示信息。
例如，能力的交互和上报包括了对设备能否支持HARQ-ACK重传的指示。对于通过配置(或通过指示信息)来使能HARQ-ACK重传的具体方式不做限制，例如，当设备被配置了参数HARQ-ACK-Codebook，并且参数取值被配置为enhanced时， 表示设备被使能了HARQ-ACK重传。
HARQ-ACK重传能力的交互包括以下至少一种方式。
-第二设备将能力上报给第一设备。
-第一设备将能力上报给基站。
HARQ-ACK重传功能的使能包括以下至少一种方式。
-基站使能第一设备的HARQ-ACK重传。
-第一设备使能第二设备的HARQ-ACK重传。
本申请实施例还可以包括上述方式的任何一种组合。
例如：第二设备将自身支持HARQ-ACK重传的能力上报给第一设备。在第一设备和第二设备都支持HARQ-ACK重传的情况下，第一设备向基站上报自己能够支持HARQ-ACK重传；否则，第一设备向基站上报自己不能支持HARQ-ACK重传。值得注意的是，这里第一设备并不是直接将自身支持HARQ-ACK重传的能力上报给基站。基站确定是否使能第一设备的HARQ-ACK重传。第一设备确定是否使能第二设备的HARQ-ACK重传。例如，在基站使能第一设备HARQ-ACK重传的情况下，第一设备使能第二设备的HARQ-ACK重传。
又例如：第二设备将自身支持HARQ-ACK重传的能力上报给第一设备。第一设备将第一设备支持HARQ-ACK重传的能力，以及第二设备支持HARQ-ACK重传的能力上报给基站。基站确定是否使能第一设备的HARQ-ACK重传。第一设备确定是否使能第二设备的HARQ-ACK重传。例如，在基站使能第一设备HARQ-ACK重传的情况下，第一设备使能第二设备的HARQ-ACK重传。
又例如：第二设备将自身支持HARQ-ACK重传的能力上报给第一设备。第一设备将第一设备支持HARQ-ACK重传的能力上报给基站。基站确定是否使能第一设备的HARQ-ACK重传。第一设备确定是否使能第二设备的HARQ-ACK重传。例如，在基站使能第一设备HARQ-ACK重传的情况下，第一设备使能第二设备的HARQ-ACK重传。
以上从第一设备的角度对边链路反馈信息的发送方法进行了示意性说明，以下再从网络设备的角度对边链路反馈信息的接收方法进行示意性说明，与之前实施例相同的内容不再赘述。
在一些实施例中，网络设备接收第一设备通过物理上行控制信道承载的边链路反 馈信息；其中，所述物理上行控制信道(PUCCH)由所述第一设备在确定需要由所述物理上行控制信道承载的边链路反馈信息已经被接收的情况下发送。
在一些实施例中，在需要由物理上行控制信道承载的边链路反馈信息没有被第一设备接收，以及第一设备已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的情况下，所述物理上行控制信道(PUCCH)不被所述第一设备发送。
在一些实施例中，在需要由物理上行控制信道承载的所有边链路反馈信息均没有被第一设备接收，并且第一设备已经向第二设备发送与所有边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的情况下，所述物理上行控制信道(PUCCH)不被所述第一设备发送。
在一些实施例中，在需要由物理上行控制信道承载的多个边链路反馈信息中没有被第一设备接收的边链路反馈信息的数目或比例大于配置的或预配置的阈值，并且第一设备已经向第二设备发送与多个边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的情况下，所述物理上行控制信道(PUCCH)不被所述第一设备发送。
在一些实施例中，网络设备在没有接收到所述物理上行控制信道的情况下，向第一设备发送用于指示对所述边链路反馈信息进行重传的信息。
在一些实施例中，第一设备被使能向网络设备重传边链路反馈信息，并且第二设备被使能向第一设备重传边链路反馈信息。
在一些实施例中，网络设备接收第一设备发送的第一设备能否支持边链路反馈信息重传的能力信息和/或第二设备能否支持边链路反馈信息重传的能力信息。
在一些实施例中，网络设备向第一设备发送用于使能第一设备进行边链路反馈信息重传的指示信息。
以上主要对第一设备和网络设备之间的HARQ-ACK交互进行了说明，对第一设备和第二设备之间的HARQ-ACK如何进行交互不做限制。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，对于第一设备向网络设备的HARQ-ACK重传，如果第一设 备已经向第二设备发送与HARQ-ACK关联的PSCCH和/或PSSCH，但没有接收到需要由PUCCH承载的边链路反馈信息(即，PUCCH不包含有效的HARQ-ACK比特)，则第一设备不向网络设备发送该PUCCH，从而可以减少或避免对非授权频段不必要的占用，并且可以通知网络设备调度HARQ-ACK重传。
第二方面的实施例
本申请实施例提供一种边链路反馈信息的发送和接收方法，从第一设备和第二设备进行说明。本申请实施例对第一设备和第二设备之间的HARQ-ACK交互进行示意性说明，可以与第一方面的实施例结合起来，也可以单独实施。
图7是本申请实施例的边链路反馈信息的发送方法的一示意图，如图7所示，该方法包括：
701，第一设备向第二设备发送物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)；
702，第一设备接收第二设备发送的多个边链路反馈信息；其中承载多个边链路反馈信息的物理边链路反馈信道(PSFCH)资源至少由所述多个边链路反馈信息的数目确定。
值得注意的是，以上附图7仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图7的记载。
第一设备在PSSCH上向第二设备发送某一TB，然后在与PSSCH相关联的某一PSFCH资源上接收HARQ-ACK。对于边链路非授权频段，为满足相关法规(regulation)的要求，边链路物理信道和物理信号的物理层结构可能会发生变化。例如，传统边链路的PSSCH以子信道(sub-channel)为粒度，包括若干频域上连续的子信道，边链路非授权频段的PSSCH可能以交织(interlace)为粒度，包括若干频域上连续或非连续的交织。
本申请实施例对于物理层结构不做限制，仅从逻辑资源层面进行说明。无论物理资源的结构如何，在逻辑上，一个PSSCH资源会关联有一个PSFCH资源。例如，根据现有标准，与某一PSSCH相关联的候选PSFCH资源有
Figure PCTCN2021124985-appb-000001
个，在这
Figure PCTCN2021124985-appb-000002
个 候选PSFCH资源中，最终与该PSSCH相关联的用于发送HARQ-ACK的PSFCH资源的索引为
Figure PCTCN2021124985-appb-000003
其中，P ID表示物理层源标识(physical layer source ID)，对于具有HARQ选项2的组播，M ID表示高层配置的标识，实际上是组内成员标识(group member ID)，对于单播和具有HARQ选项1的组播，M ID＝0。更加具体的参数定义以及确定PSSCH所关联的PSFCH的方法可以参见标准TS38.213的16.3小节。
对于PSSCH和PSFCH的物理层结构发生变化的情况，可以对上述方法进行适应性扩展，例如，将PSSCH的子信道替换为PSSCH的交织，将PSFCH仅使用一个RB扩展为可以使用多个RB。总之，通过上述方法或扩展方法，确定出与某一PSSCH相关联的
Figure PCTCN2021124985-appb-000004
个候选PSFCH资源。在第二设备需要发送多于一个HARQ-ACK比特的情况下，最终与该PSSCH相关联的用于发送多个HARQ-ACK比特的PSFCH资源的索引不能沿用现有方法中的
Figure PCTCN2021124985-appb-000005
式子进行确定。
以下对第二设备需要发送多于一个HARQ-ACK比特的情况进行说明。
在某些情况下，第一设备发送一个PSSCH，但指示第二设备反馈多于一个HARQ-ACK比特。例如，图5中，第一设备在PSSCH上发送TB4，同时在SCI中指示第二设备反馈包括HARQ-ACK重传在内的4个HARQ-ACK比特。又例如，第一设备发送PSSCH1(TB1)，但所关联的PSFCH时隙位于当前COT之外，因此，第一设备在SCI中指示第二设备暂时不反馈HARQ-ACK，或者第二设备根据PSFCH时隙位于COT之外这一事实自行判断暂时不反馈HARQ-ACK，之后，在第一设备发送PSSCH2(TB2)时，使用SCI指示第二设备反馈包括针对TB1的HARQ-ACK1和针对TB2的HARQ-ACK2在内的多个HARQ-ACK比特。
为了能够发送包括HARQ-ACK重传在内的多个HARQ-ACK比特，需要基于一个PSSCH确定多个PSFCH资源，而现有技术只能基于一个PSSCH确定一个PSFCH资源。针对这一问题，本申请实施例中承载多个边链路反馈信息的物理边链路反馈信道(PSFCH)资源至少由多个边链路反馈信息的数目确定。
例如，物理边链路反馈信道(PSFCH)资源通过如下公式被确定：
Figure PCTCN2021124985-appb-000006
其中，P ID表示物理层源标识(physical layer source ID)，M ID表示高层配置的组 内成员标识(group member ID)，Q表示所述多个边链路反馈信息的数目，q＝0,1,…,Q-1。
例如，对于具有HARQ选项2的组播，M ID表示高层配置的标识，即组内成员标识(group member ID)。对于单播，M ID＝0。对于HARQ选项1的组播，M ID＝0。
在一些实施例中，所述多个边链路反馈信息的数目基于第一设备向第二设备发送的边链路控制信息中的分配索引(AI，Assignment Index)字段被确定，该分配索引例如称为SAI。
例如，Q的取值可以基于第一设备发送给第二设备的信令获得。例如，基于2 nd stage SCI中的C-SAI/T-SAI字段获得。
在一些实施例中，多个边链路反馈信息包括：针对当前调度的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的反馈信息，和/或，针对之前调度的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的反馈信息。
例如，Q个HARQ-ACK比特包括：针对当前调度的PSSCH的HARQ-ACK比特，和/或，针对之前调度的PSSCH的HARQ-ACK比特。
在一些实施例中，当前调度的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)承载的传输块(TB)不同于之前调度的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)承载的传输块(TB)。
以具有HARQ选项2的组播为例，假设第一设备以组播方式发送PSSCH，并指示第二设备(组员设备)发送Q个HARQ-ACK比特。对于组播，一个第一设备对应有多个第二设备。Q个HARQ-ACK比特包括针对该PSSCH的HARQ-ACK比特，以及针对之前PSSCH的重传的HARQ-ACK比特。组员设备0具有M ID＝0，组员设备1具有M ID＝1，组员设备2具有M ID＝2，以此类推。
根据上述方法，为发送Q个HARQ-ACK比特，每个组员设备发送Q个PSFCH，每个PSFCH按照现有方式承载1比特HARQ-ACK。组员设备0使用的PSFCH资源为
Figure PCTCN2021124985-appb-000007
组员设备1使用的PSFCH资源为
Figure PCTCN2021124985-appb-000008
组员设备2使用的PSFCH资源为
Figure PCTCN2021124985-appb-000009
以此类推。通过本申请实施例，不 同组员设备的PSFCH资源互不相同。
反之，如果在现有方法发送PSFCH的资源为
Figure PCTCN2021124985-appb-000010
的基础上，将发送Q个PSFCH的资源确定为
Figure PCTCN2021124985-appb-000011
那么组员设备0使用的PSFCH资源为
Figure PCTCN2021124985-appb-000012
组员设备1使用的PSFCH资源为
Figure PCTCN2021124985-appb-000013
组员设备2使用的PSFCH资源为
Figure PCTCN2021124985-appb-000014
以此类推。因此可以看到，不同组员设备会使用相同的PSFCH资源发送HARQ-ACK，使得第一设备无法分辨接收到的HARQ-ACK来自哪个第二设备，从而产生混淆。例如，假设Q＝3，当q＝2时，组员设备0使用PSFCH资源
Figure PCTCN2021124985-appb-000015
当q＝1时，组员设备1使用PSFCH资源
Figure PCTCN2021124985-appb-000016
当q＝0时，组员设备2使用PSFCH资源
Figure PCTCN2021124985-appb-000017
多个组员设备使用了相同的PSFCH资源。
上述设备发送Q个HARQ-ACK比特的方法实际上不限于边链路非授权频段这一应用场景。同样的方法也可以扩展到其他场景。例如，上述方法可以应用于载波聚合(CA)场景。第一设备通过跨载波调度方式，或者通过自调度方式，在多个载波上发送多个PSSCH给第二设备，第二设备在某个cell(例如Pcell)上同时发送多个HARQ-ACK比特给第一设备。
图8是本申请实施例中边链路反馈信息的另一示例图，包含了Uu和边链路完整的收发流程。图8上半部分表示Uu流程，下半部分表示边链路流程。
如图8所示，网络设备(基站)获得COT1，在COT1内调度第一设备发送TB1(即基站为第一设备分配资源PSSCH1，第一设备确定在PSSCH1上发送TB1)，指示其在PUCCH1上反馈HARQ-ACK1。由于第二设备针对PSFCH1的LBT失败(第二设备没有发送PSFCH1)，第一设备在PSFCH1上没有接收到针对TB1的HARQ-ACK1，因此第一设备不发送PUCCH1。基站调度第一设备发送TB2，由于针对TB2的HARQ-ACK2来不及在COT1内反馈，基站指示第一设备暂时不反馈HARQ-ACK2。由于与TB2关联的PSFCH2位于COT1之外，第一设备在SCI2中指示第二设备暂时不反馈HARQ-ACK2，或者，第二设备基于PSFCH2时隙和COT1时间长度自行判断 不需要在PSFCH2上反馈HARQ-ACK2。
基站获得COT2，在COT2内调度第一设备发送TB3，指示其在PUCCH2上反馈针对组0(G＝0)和组1(G＝1)的HARQ-ACK，即反馈HARQ-ACK1～HARQ-ACK3。第一设备通过SCI3指示第二设备在与TB3关联的PSFCH3上反馈针对组0(G＝0)和组1(G＝1)的HARQ-ACK，即反馈HARQ-ACK1～HARQ-ACK3。第一设备在PSFCH3上接收到第二设备发送的HARQ-ACK1～HARQ-ACK3，然后在PUCCH2上将HARQ-ACK1～HARQ-ACK3发送给基站。这里PSFCH3指与承载TB3的PSSCH所关联的所有PSFCH，即来自某一个第二设备的承载Q个HARQ-ACK比特的PSFCH资源，可以使用前面所述的确定Q个HARQ-ACK比特的PSFCH资源的方法。与Uu使用DCI的方法类似，边链路使用SCI对G、C-SAI/T-SAI进行指示，从而达到调度HARQ-ACK重传的目的。例如图8中，SCI3指示第二设备同时发送多个HARQ-ACK比特，包括了对HARQ-ACK1和HARQ-ACK2的重传。
在一些实施例中，在第一设备向第二设备发送的边链路控制信息(SCI)中指示边链路反馈信息的分组和/或重传的信息独立于在网络设备向第一设备发送的下行控制信息(DCI)中指示边链路反馈信息的分组和/或重传的信息。
图9是本申请实施例中边链路反馈信息的另一示例图，包含了Uu和边链路完整的收发流程。与图8不同之处在于，由于COT内所包含的PSFCH资源不同，SCI指示的G、C-SAI/T-SAI的取值可以与DCI指示的G、C-DAI/T-DAI的取值不同。
简单起见，图9中仅示出了DCI和SCI中的“group index”字段(G)、DAI字段(C-DAI/T-DAI)和SAI字段(C-SAI/T-SAI)，为实现HARQ-ACK重传功能，DCI和SCI中还可以包含其他字段，例如“new feedback indicator”字段、“number of requested group(s)”字段等。同理，对这些被省略的字段，在SCI中的取值可以与在DCI中的取值不同。由于LBT失败，第二设备没有在PSFCH1上发送HARQ-ACK1。因此，第一设备不发送PUCCH1。通过SCI指示的G和C-SAI/T-SAI，第一设备指示第二设备在与TB2关联的PSFCH2上反馈HARQ-ACK1和HARQ-ACK2。
这里可以使用本申请实施例确定承载HARQ-ACK1和HARQ-ACK2的多个PSFCH资源。虽然第一设备在PSFCH2时隙接收到HARQ-ACK1和HARQ-ACK2，但来不及在PUCCH1上发送给基站。第一设备在PSFCH3上接收到HARQ-ACK3，然后在PUCCH2上将HARQ-ACK1～HARQ-ACK3发送给基站。由图9可以看到，第 一设备只要能够保证在PUCCH2上将HARQ-ACK1～HARQ-ACK3发送给基站即可，至于如何通过边链路接收HARQ-ACK1～HARQ-ACK3可以由第一设备自行确定，不必照搬基站在DCI中对HARQ-ACK的调度。
图9涉及的完整收发流程可以总结如下：
-基站在DCI1中指示第一设备在PSSCH1上发送，并且指示第一设备在PUCCH1上反馈与PSSCH1相关联的HARQ-ACK1。
-第一设备在PSSCH1上发送TB1。由于第二设备没有在与PSSCH1关联的PSFCH1上发送HARQ-ACK1(比如由于LBT失败)，第一设备没有在PSFCH1上接收到HARQ-ACK1。
-第一设备不向基站发送PUCCH1。由于没有收到PUCCH1，基站知道可以在以后寻找机会调度第一设备重传HARQ-ACK1。
-基站在DCI2中指示第一设备在PSSCH2上发送，并且指示第一设备暂时不反馈HARQ-ACK2。
-第一设备在PSSCH2上发送TB2，在SCI2中指示第二设备在PSFCH2时隙发送HARQ-ACK1和HARQ-ACK2，即调度了对HARQ-ACK1的重传。这里PSFCH2可以包括多于一个PSFCH资源，这些PSFCH资源都是与PSSCH2相关联的，即一个PSSCH关联了多个PSFCH资源。
-第二设备根据
Figure PCTCN2021124985-appb-000018
确定用于发送HARQ-ACK1和HARQ-ACK2的多个PSFCH资源。其中，Q根据SCI2中的C-SAI/T-SAI字段确定，等于第二设备需要同时发送的HARQ-ACK比特数，也等于HARQ-ACK码书的大小。第二设备在PSFCH2时隙发送HARQ-ACK1和HARQ-ACK2。
-第一设备在PSFCH2时隙接收HARQ-ACK1和HARQ-ACK2。
-基站在DCI3中指示第一设备在PSSCH3上发送，并且指示第一设备在PUCCH2上反馈HARQ-ACK1～HARQ-ACK3，即调度了对HARQ-ACK1和HARQ-ACK2的重传。
-第一设备在PSSCH3上发送TB3，在SCI3中指示第二设备在PSFCH3时隙发送HARQ-ACK3。
-第二设备根据
Figure PCTCN2021124985-appb-000019
确定用于发送HARQ-ACK3的PSFCH资源。根据SCI3中的C-SAI/T-SAI字段，这里Q＝1。
-第一设备在PSFCH3时隙接收HARQ-ACK3。
-第一设备在PUCCH2上将HARQ-ACK1～HARQ-ACK3发送给基站。
在一些实施例中，第一设备接收第二设备发送的用于指示所述第二设备能够同时发送的PSFCH数目的信息。
例如，第二设备可以将自己能够同时发送的PSFCH数N通知给第一设备，以便于第一设备确定调度第二设备同时发送的PSFCH数Q。例如，第一设备在调度时保证Q≤N。对第二设备如何确定N值不做限制。N≤N max，其中N max表示第二设备能够同时发送的最大的PSFCH数目，N max取决于设备能力。第二设备确定调度第二设备同时发送的PSFCH数Q，实际上也是在确定第二设备所发送的HARQ-ACK码书的大小。
在一些实施例中，多个边链路反馈信息作为整体被确定是否被丢弃，其中所述多个边链路反馈信息中的最高优先级被用于优先级比较。
例如，第二设备可能需要发送HARQ-ACK码书给第一设备，同时还需要发送HARQ-ACK给第三设备。这可能导致第二设备同时发送的PSFCH数目超过N max。此时，第二设备需要丢弃某些PSFCH，即只发送一部分PSFCH。现有优先规则仅选择优先级最高的若干PSFCH进行发送，在存在HARQ-ACK码书的情况下，如果只发送HARQ-ACK码书中的一部分HARQ-ACK，则会破坏HARQ-ACK码书的完整性，使得第一设备接收HARQ-ACK码书失败。因此，HARQ-ACK码书应该作为一个整体来被确定其是否被丢弃。HARQ-ACK码书的优先级等于HARQ-ACK码书所包含的所有HARQ-ACK中最高的优先级。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，对于第二设备向第一设备的HARQ-ACK重传，HARQ-ACK码书的大小被额外地用于确定PSFCH资源，从而可以避免在组播的HARQ-ACK重传中发生PSFCH资源碰撞。
第三方面的实施例
本申请实施例提供一种边链路反馈信息的发送装置。该装置例如可以是终端设备 (例如前述的第一设备)，也可以是配置于终端设备的某个或某些部件或者组件，与第一、二方面的实施例相同的内容不再赘述。
图10是本申请实施例的边链路反馈信息的发送装置的一示意图。如图10所示，边链路反馈信息的发送装置1000包括：
确定单元1001，其在需要向网络设备发送物理上行控制信道的情况下，确定需要由所述物理上行控制信道承载的边链路反馈信息是否被接收，以及是否已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道和/或物理边链路共享信道；
处理单元1002，其在需要由所述物理上行控制信道承载的边链路反馈信息没有被接收，以及已经向所述第二设备发送与所述边链路反馈信息关联的物理边链路控制信道和/或物理边链路共享信道的情况下，不发送所述物理上行控制信道。
在一些实施例中，在需要由所述物理上行控制信道承载的所有边链路反馈信息均没有被接收，并且已经向第二设备发送与所述所有边链路反馈信息关联的物理边链路控制信道和/或物理边链路共享信道的情况下，所述处理单元1002不发送所述物理上行控制信道。
在一些实施例中，在需要由所述物理上行控制信道承载的多个边链路反馈信息中没有被接收的边链路反馈信息的数目或比例大于配置的或预配置的阈值，并且已经向第二设备发送与所述多个边链路反馈信息关联的物理边链路控制信道和/或物理边链路共享信道的情况下，所述处理单元1002不发送所述物理上行控制信道。
在一些实施例中，如图10所示，所述装置还包括：
发送单元1003，其向所述第二设备发送所述物理边链路控制信道和/或物理边链路共享信道。
在一些实施例中，如图10所示，所述装置还包括：
接收单元1004，其接收所述网络设备在没有接收到所述物理上行控制信道的情况下发送的指示对所述边链路反馈信息进行重传的信息。
在一些实施例中，第一设备被使能向所述网络设备重传边链路反馈信息，并且所述第二设备被使能向所述第一设备重传边链路反馈信息。
在一些实施例中，所述发送单元1003还向所述网络设备发送所述第一设备能否支持边链路反馈信息重传的能力信息和/或所述第二设备能否支持边链路反馈信息重 传的能力信息。
在一些实施例中，所述接收单元1004还接收所述网络设备发送的用于使能所述第一设备进行边链路反馈信息重传的指示信息。
在一些实施例中，所述接收单元1004还接收所述第二设备发送的所述第二设备能否支持边链路反馈信息重传的能力信息。
在一些实施例中，所述发送单元1003还向所述第二设备发送用于使能所述第二设备进行边链路反馈信息重传的指示信息。
在一些实施例中，所述接收单元1004还接收所述第二设备发送的多个边链路反馈信息；其中承载所述多个边链路反馈信息的物理边链路反馈信道资源至少由所述多个边链路反馈信息的数目确定。
在一些实施例中，所述多个边链路反馈信息的数目基于所述第一设备向所述第二设备发送的边链路控制信息中的分配索引字段被确定。
在一些实施例中，所述多个边链路反馈信息包括：针对当前调度的物理边链路控制信道和/或物理边链路共享信道的反馈信息，和/或，针对之前调度的物理边链路控制信道和/或物理边链路共享信道的反馈信息。
在一些实施例中，所述当前调度的物理边链路控制信道和/或物理边链路共享信道承载的传输块不同于所述之前调度的物理边链路控制信道和/或物理边链路共享信道承载的传输块。
在一些实施例中，所述物理边链路反馈信道资源通过如下公式被确定：
Figure PCTCN2021124985-appb-000020
其中，P ID表示物理层源标识，M ID表示高层配置的组内成员标识，Q表示所述多个边链路反馈信息的数目，q＝0,1,…,Q-1。
在一些实施例中，在第一设备向所述第二设备发送的边链路控制信息中指示所述边链路反馈信息的分组和/或重传的信息独立于在所述网络设备向所述第一设备发送的下行控制信息中指示所述边链路反馈信息的分组和/或重传的信息。
在一些实施例中，所述接收单元1004还接收所述第二设备发送的用于指示所述第二设备能够同时发送的物理边链路反馈信道数目的信息。
在一些实施例中，所述多个边链路反馈信息作为整体被确定是否被丢弃，其中所述多个边链路反馈信息中的最高优先级被用于优先级比较。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。边链路反馈信息的发送装置1000还可以包括其他部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图10中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，对于第一设备向网络设备的HARQ-ACK重传，如果第一设备已经向第二设备发送与HARQ-ACK关联的PSCCH和/或PSSCH，但没有接收到需要由PUCCH承载的边链路反馈信息(即，PUCCH不包含有效的HARQ-ACK比特)，则第一设备不向网络设备发送该PUCCH，从而可以减少或避免对非授权频段不必要的占用，并且可以通知网络设备调度HARQ-ACK重传。对于第二设备向第一设备的HARQ-ACK重传，HARQ-ACK码书的大小被额外地用于确定PSFCH资源，从而可以避免在组播的HARQ-ACK重传中发生PSFCH资源碰撞。
第四方面的实施例
本申请实施例提供一种边链路反馈信息的发送装置。该装置例如可以是终端设备(例如前述的第二设备)，也可以是配置于终端设备的某个或某些部件或者组件，与第一、二方面的实施例相同的内容不再赘述。
图11是本申请实施例的边链路反馈信息的发送装置的一示意图。如图11所示，边链路反馈信息的发送装置1100包括：
接收单元1101，其接收第一设备发送的物理边链路控制信道和/或物理边链路共享信道；以及
发送单元1102，其向所述第一设备发送多个边链路反馈信息；其中所述多个边链路反馈信息的物理边链路反馈信道资源至少由所述多个边链路反馈信息的数目确定。
在一些实施例中，发送单元1102基于所述第一设备向所述第二设备发送的边链路控制信息中的分配索引字段确定所述多个边链路反馈信息的数目。
在一些实施例中，所述多个边链路反馈信息包括：针对当前调度的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的反馈信息，和/或，针对之前调度的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的反馈信息。
在一些实施例中，所述当前调度的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)承载的传输块(TB)不同于所述之前调度的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)承载的传输块(TB)。
在一些实施例中，所述物理边链路反馈信道(PSFCH)资源通过如下公式被确定：
Figure PCTCN2021124985-appb-000021
其中，P ID表示物理层源标识(physical layer source ID)，M ID表示高层配置的组内成员标识(group member ID)，Q表示所述多个边链路反馈信息的数目，q＝0,1,…,Q-1。
在一些实施例中，发送单元1102根据所述第一设备的指示确定不反馈边链路反馈信息，或者在承载边链路反馈信息的物理边链路反馈信道(PSFCH)位于信道占用时间之外的情况下确定不反馈所述边链路反馈信息。
在一些实施例中，在所述第一设备向所述第二设备发送的边链路控制信息(SCI)中指示边链路反馈信息的分组和/或重传的信息独立于在网络设备向所述第一设备发送的下行控制信息(DCI)中指示边链路反馈信息的分组和/或重传的信息。
在一些实施例中，发送单元1102向所述第一设备发送用于指示所述第二设备能够同时发送的PSFCH数目的信息。
在一些实施例中，发送单元1102将所述多个边链路反馈信息作为整体来确定是否被丢弃，其中所述多个边链路反馈信息中的最高优先级被用于优先级比较。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。边链路反馈信息的发送装置1100还可以包括其他部件或者模块，关于这些 部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图11中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，对于第一设备向网络设备的HARQ-ACK重传，如果第一设备已经向第二设备发送与HARQ-ACK关联的PSCCH和/或PSSCH，但没有接收到需要由PUCCH承载的边链路反馈信息(即，PUCCH不包含有效的HARQ-ACK比特)，则第一设备不向网络设备发送该PUCCH，从而可以减少或避免对非授权频段不必要的占用，并且可以通知网络设备调度HARQ-ACK重传。对于第二设备向第一设备的HARQ-ACK重传，HARQ-ACK码书的大小被额外地用于确定PSFCH资源，从而可以避免在组播的HARQ-ACK重传中发生PSFCH资源碰撞。
第五方面的实施例
本申请实施例还提供一种通信系统，可以参考图1，与第一方面至第四方面的实施例相同的内容不再赘述。
在一些实施例中，通信系统100至少可以包括：
第一设备，其在需要向网络设备发送物理上行控制信道的情况下，确定需要由所述物理上行控制信道承载的边链路反馈信息是否被接收，以及是否已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道和/或物理边链路共享信道；在需要由所述物理上行控制信道承载的边链路反馈信息没有被接收，以及已经向所述第二设备发送与所述边链路反馈信息关联的物理边链路控制信道和/或物理边链路共享信道的情况下，不发送所述物理上行控制信道；和/或
第二设备，其接收第一设备发送的物理边链路控制信道和/或物理边链路共享信道；以及向所述第一设备发送多个边链路反馈信息；其中所述多个边链路反馈信息的物理边链路反馈信道资源至少由所述多个边链路反馈信息的数目确定。
本申请实施例还提供一种网络设备，例如可以是基站，但本申请不限于此，还可以是其他的网络设备。
图12是本申请实施例的网络设备的构成示意图。如图12所示，网络设备1200 可以包括：处理器1210(例如中央处理器CPU)和存储器1220；存储器1220耦合到处理器1210。其中该存储器1220可存储各种数据；此外还存储信息处理的程序1230，并且在处理器1210的控制下执行该程序1230。
例如，处理器1210可以被配置为执行程序而实现如第一方面的实施例所述的边链路反馈信息的接收方法。例如处理器1210可以被配置为进行如下的控制：接收第一设备通过物理上行控制信道承载的边链路反馈信息；其中，所述物理上行控制信道(PUCCH)由所述第一设备在确定需要由所述物理上行控制信道承载的边链路反馈信息已经被接收的情况下发送。
此外，如图12所示，网络设备1200还可以包括：收发机1240和天线1250等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备1200也并不是必须要包括图12中所示的所有部件；此外，网络设备1200还可以包括图12中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种终端设备，但本申请不限于此，还可以是其他的设备。
图13是本申请实施例的终端设备的示意图。如图13所示，该终端设备1300可以包括处理器1310和存储器1320；存储器1320存储有数据和程序，并耦合到处理器1310。值得注意的是，该图是示例性的；还可以使用其他类型的结构，来补充或代替该结构，以实现电信功能或其他功能。
例如，处理器1310可以被配置为执行程序而实现如第一方面的实施例所述的边链路反馈信息的发送方法。例如处理器1310可以被配置为进行如下的控制：在需要向网络设备发送物理上行控制信道(PUCCH)的情况下，确定需要由所述物理上行控制信道承载的边链路反馈信息是否被接收，以及是否已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)；在需要由所述物理上行控制信道承载的边链路反馈信息没有被接收，以及已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的情况下，不发送所述物理上行控制信道(PUCCH)。
例如，处理器1310可以被配置为执行程序而实现如第二方面的实施例所述的边链路反馈信息的发送方法。例如处理器1310可以被配置为进行如下的控制：接收第一设备发送的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)； 以及向所述第一设备发送多个边链路反馈信息；其中所述多个边链路反馈信息的物理边链路反馈信道(PSFCH)资源至少由所述多个边链路反馈信息的数目确定。
如图13所示，该终端设备1300还可以包括：通信模块1330、输入单元1340、显示器1350、电源1360。其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，终端设备1300也并不是必须要包括图13中所示的所有部件，上述部件并不是必需的；此外，终端设备1300还可以包括图13中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机程序，其中当在终端设备中执行所述程序时，所述程序使得所述终端设备执行第一、二方面的实施例所述的边链路反馈信息的发送方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得终端设备执行第一、二方面的实施例所述的边链路反馈信息的发送方法。
本申请实施例还提供一种计算机程序，其中当在网络设备中执行所述程序时，所述程序使得所述网络设备执行第一方面的实施例所述的边链路反馈信息的接收方法。
本申请实施例还提供一种存储有计算机程序的存储介质，其中所述计算机程序使得网络设备执行第一方面的实施例所述的边链路反馈信息的接收方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器 和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于包括以上实施例的实施方式，还公开下述的附记：
附记1.一种边链路反馈信息的发送方法，包括：
第一设备在需要向网络设备发送物理上行控制信道(PUCCH)的情况下，确定需要由所述物理上行控制信道承载的边链路反馈信息是否被接收，以及是否已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)；
在需要由所述物理上行控制信道承载的边链路反馈信息没有被接收，以及已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的情况下，所述第一设备不发送所述物理上行控制信道(PUCCH)。
附记2.根据附记1所述的方法，其中，在需要由所述物理上行控制信道承载的所有边链路反馈信息均没有被接收，并且已经向第二设备发送与所述所有边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的情况下，所述第一设备不发送所述物理上行控制信道(PUCCH)。
附记3.根据附记1所述的方法，其中，在需要由所述物理上行控制信道承载的多个边链路反馈信息中没有被接收的边链路反馈信息的数目或比例大于配置的或预配置的阈值，并且已经向第二设备发送与所述多个边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的情况下，所述第一设备不发送所述物理上行控制信道(PUCCH)。
附记4.根据附记1至3任一项所述的方法，其中，所述方法还包括：
所述第一设备接收所述网络设备在没有接收到所述物理上行控制信道的情况下发送的指示对所述边链路反馈信息进行重传的信息。
附记5.根据附记1至4任一项所述的方法，其中，所述第一设备被使能向所述网络设备重传边链路反馈信息，并且所述第二设备被使能向所述第一设备重传边链路反馈信息。
附记6.根据附记1至5任一项所述的方法，其中，所述方法还包括：
所述第一设备向所述网络设备发送所述第一设备能否支持边链路反馈信息重传的能力信息和/或所述第二设备能否支持边链路反馈信息重传的能力信息。
附记7.根据附记1至6任一项所述的方法，其中，所述方法还包括：
所述第一设备接收所述网络设备发送的用于使能所述第一设备进行边链路反馈信息重传的指示信息。
附记8.根据附记1至7任一项所述的方法，其中，所述方法还包括：
所述第一设备接收所述第二设备发送的所述第二设备能否支持边链路反馈信息重传的能力信息。
附记9.根据附记1至8任一项所述的方法，其中，所述方法还包括：
所述第一设备向所述第二设备发送用于使能所述第二设备进行边链路反馈信息重传的指示信息。
附记10.根据附记1至9任一项所述的方法，其中，所述方法还包括：
所述第一设备在由于LBT失败而没有向所述第二设备发送所述物理边链路控制信道(PSCCH)和/或所述物理边链路共享信道(PSSCH)的情况下，向所述网络设备发送非确认(NACK)信息。
附记11.根据附记1至10任一项所述的方法，其中，所述方法还包括：
所述第一设备接收所述第二设备发送的多个边链路反馈信息；其中承载所述多个 边链路反馈信息的物理边链路反馈信道(PSFCH)资源至少由所述多个边链路反馈信息的数目确定。
附记12.根据附记11所述的方法，其中，所述多个边链路反馈信息的数目基于所述第一设备向所述第二设备发送的边链路控制信息中的分配索引(AI，Assignment Index)字段被确定。
附记13.根据附记11或12所述的方法，其中，所述多个边链路反馈信息包括：针对当前调度的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的反馈信息，和/或，针对之前调度的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的反馈信息。
附记14.根据附记13所述的方法，其中，所述当前调度的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)承载的传输块(TB)不同于所述之前调度的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)承载的传输块(TB)。
附记15.根据附记11至14任一项所述的方法，其中，所述物理边链路反馈信道(PSFCH)资源通过如下公式被确定：
Figure PCTCN2021124985-appb-000022
其中，P ID表示物理层源标识(physical layer source ID)，M ID表示高层配置的组内成员标识(group member ID)，Q表示所述多个边链路反馈信息的数目，q＝0,1,…,Q-1。
附记16.根据附记11至15任一项所述的方法，其中，在所述第一设备向所述第二设备发送的边链路控制信息(SCI)中指示所述边链路反馈信息的分组和/或重传的信息独立于在所述网络设备向所述第一设备发送的下行控制信息(DCI)中指示所述边链路反馈信息的分组和/或重传的信息。
附记17.根据附记11至16任一项所述的方法，其中，所述方法还包括：
所述第一设备接收所述第二设备发送的用于指示所述第二设备能够同时发送的PSFCH数目的信息。
附记18.根据附记11至17任一项所述的方法，其中，所述多个边链路反馈信息作为整体被确定是否被丢弃，其中所述多个边链路反馈信息中的最高优先级被用于优先级比较。
附记19.根据附记1至18任一项所述的方法，其中，所述方法还包括：
所述第一设备向所述第二设备发送所述物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)。
附记20.一种边链路反馈信息的发送方法，包括：
第二设备接收第一设备发送的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)；以及
所述第二设备向所述第一设备发送多个边链路反馈信息；其中所述多个边链路反馈信息的物理边链路反馈信道(PSFCH)资源至少由所述多个边链路反馈信息的数目确定。
附记21.根据附记20所述的方法，其中，所述方法还包括：
所述第二设备基于所述第一设备向所述第二设备发送的边链路控制信息中的分配索引字段确定所述多个边链路反馈信息的数目。
附记22.根据附记20或21所述的方法，其中，所述多个边链路反馈信息包括：针对当前调度的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的反馈信息，和/或，针对之前调度的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的反馈信息。
附记23.根据附记22所述的方法，其中，所述当前调度的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)承载的传输块(TB)不同于所述之前调度的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)承载的传输块(TB)。
附记24.根据附记20至23任一项所述的方法，其中，所述物理边链路反馈信道(PSFCH)资源通过如下公式被确定：
Figure PCTCN2021124985-appb-000023
其中，P ID表示物理层源标识(physical layer source ID)，M ID表示高层配置的组内成员标识(group member ID)，Q表示所述多个边链路反馈信息的数目，q＝0,1,…,Q-1。
附记25.根据附记20至24任一项所述的方法，其中，所述方法还包括：
所述第二设备根据所述第一设备的指示确定不反馈边链路反馈信息，或者在承载边链路反馈信息的物理边链路反馈信道(PSFCH)位于信道占用时间之外的情况下确 定不反馈所述边链路反馈信息。
附记26.根据附记20至25任一项所述的方法，其中，在所述第一设备向所述第二设备发送的边链路控制信息(SCI)中指示边链路反馈信息的分组和/或重传的信息独立于在网络设备向所述第一设备发送的下行控制信息(DCI)中指示边链路反馈信息的分组和/或重传的信息。
附记27.根据附记20至26任一项所述的方法，其中，所述方法还包括：
所述第二设备向所述第一设备发送用于指示所述第二设备能够同时发送的PSFCH数目的信息。
附记28.根据附记20至27任一项所述的方法，其中，所述方法还包括：
所述第二设备将所述多个边链路反馈信息作为整体来确定是否被丢弃，其中所述多个边链路反馈信息中的最高优先级被用于优先级比较。
附记29.一种边链路反馈信息的发送方法，包括：
第一设备在需要向网络设备发送物理上行控制信道(PUCCH)的情况下，确定需要由所述物理上行控制信道承载的边链路反馈信息是否有效或者是否为填充比特；
在需要由所述物理上行控制信道承载的边链路反馈信息无效或者为填充比特的情况下，所述第一设备不发送所述物理上行控制信道(PUCCH)。
附记30.根据附记29所述的方法，其中，所述第一设备在所述边链路反馈信息没有被接收，以及已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的情况下，确定所述边链路反馈信息无效或者为填充比特。
附记31.根据附记29所述的方法，其中，在需要由所述物理上行控制信道承载的所有边链路反馈信息均无效或者均为填充比特的情况下，所述第一设备不发送所述物理上行控制信道(PUCCH)。
附记32.根据附记29所述的方法，其中，在需要由所述物理上行控制信道承载的多个边链路反馈信息中无效的边链路反馈信息或者填充比特的数目或比例大于配置的或预配置的阈值的情况下，所述第一设备不发送所述物理上行控制信道(PUCCH)。
附记33.一种边链路反馈信息的接收方法，包括：
网络设备接收第一设备通过物理上行控制信道承载的边链路反馈信息；
其中，所述物理上行控制信道(PUCCH)由所述第一设备在确定需要由所述物理上行控制信道承载的边链路反馈信息已经被接收的情况下发送。
附记34.根据附记33所述的方法，其中，在需要由所述物理上行控制信道承载的边链路反馈信息没有被所述第一设备接收，以及所述第一设备已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的情况下，所述物理上行控制信道(PUCCH)不被所述第一设备发送。
附记35.根据附记34所述的方法，其中，在需要由所述物理上行控制信道承载的所有边链路反馈信息均没有被所述第一设备接收，并且所述第一设备已经向第二设备发送与所述所有边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的情况下，所述物理上行控制信道(PUCCH)不被所述第一设备发送。
附记36.根据附记34所述的方法，其中，在需要由所述物理上行控制信道承载的多个边链路反馈信息中没有被所述第一设备接收的边链路反馈信息的数目或比例大于配置的或预配置的阈值，并且所述第一设备已经向第二设备发送与所述多个边链路反馈信息关联的物理边链路控制信道(PSCCH)和/或物理边链路共享信道(PSSCH)的情况下，所述物理上行控制信道(PUCCH)不被所述第一设备发送。
附记37.根据附记33至36任一项所述的方法，其中，所述方法还包括：
所述网络设备在没有接收到所述物理上行控制信道的情况下，向所述第一设备发送用于指示对所述边链路反馈信息进行重传的信息。
附记38.根据附记33至37任一项所述的方法，其中，所述第一设备被使能向所述网络设备重传边链路反馈信息，并且所述第二设备被使能向所述第一设备重传边链路反馈信息。
附记39.根据附记33至38任一项所述的方法，其中，所述方法还包括：
所述网络设备接收所述第一设备发送的所述第一设备能否支持边链路反馈信息重传的能力信息和/或所述第二设备能否支持边链路反馈信息重传的能力信息。
附记40.根据附记33至39任一项所述的方法，其中，所述方法还包括：
所述网络设备向所述第一设备发送用于使能所述第一设备进行边链路反馈信息重传的指示信息。
附记41.一种终端设备，包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如附记1至32任一项所述的边链路反馈信息的发送方法。
附记42.一种网络设备，包括存储器和处理器，所述存储器存储有计算机程序，所述处理器被配置为执行所述计算机程序而实现如附记33至40任一项所述的边链路反馈信息的接收方法。

Claims (20)

  1. 一种边链路反馈信息的发送装置，包括：
    确定单元，其在需要向网络设备发送物理上行控制信道的情况下，确定需要由所述物理上行控制信道承载的边链路反馈信息是否被接收，以及是否已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道和/或物理边链路共享信道；
    处理单元，其在需要由所述物理上行控制信道承载的边链路反馈信息没有被接收，以及已经向所述第二设备发送与所述边链路反馈信息关联的物理边链路控制信道和/或物理边链路共享信道的情况下，不发送所述物理上行控制信道。
  2. 根据权利要求1所述的装置，其中，在需要由所述物理上行控制信道承载的所有边链路反馈信息均没有被接收，并且已经向第二设备发送与所述所有边链路反馈信息关联的物理边链路控制信道和/或物理边链路共享信道的情况下，所述处理单元不发送所述物理上行控制信道。
  3. 根据权利要求1所述的装置，其中，在需要由所述物理上行控制信道承载的多个边链路反馈信息中没有被接收的边链路反馈信息的数目或比例大于配置的或预配置的阈值，并且已经向第二设备发送与所述多个边链路反馈信息关联的物理边链路控制信道和/或物理边链路共享信道的情况下，所述处理单元不发送所述物理上行控制信道。
  4. 根据权利要求1所述的装置，其中，所述装置还包括：
    发送单元，其向所述第二设备发送所述物理边链路控制信道和/或物理边链路共享信道。
  5. 根据权利要求1所述的装置，其中，所述装置还包括：
    接收单元，其接收所述网络设备在没有接收到所述物理上行控制信道的情况下发送的指示对所述边链路反馈信息进行重传的信息。
  6. 根据权利要求1所述的装置，其中，第一设备被使能向所述网络设备重传边链路反馈信息，并且所述第二设备被使能向所述第一设备重传边链路反馈信息。
  7. 根据权利要求4所述的装置，其中，所述发送单元还向所述网络设备发送第一设备能否支持边链路反馈信息重传的能力信息和/或所述第二设备能否支持边链路反馈信息重传的能力信息。
  8. 根据权利要求5所述的装置，其中，所述接收单元还接收所述网络设备发送的用于使能第一设备进行边链路反馈信息重传的指示信息。
  9. 根据权利要求5所述的装置，其中，所述接收单元还接收所述第二设备发送的所述第二设备能否支持边链路反馈信息重传的能力信息。
  10. 根据权利要求4所述的装置，其中，所述发送单元还向所述第二设备发送用于使能所述第二设备进行边链路反馈信息重传的指示信息。
  11. 根据权利要求5所述的装置，其中，所述接收单元还接收所述第二设备发送的多个边链路反馈信息；其中承载所述多个边链路反馈信息的物理边链路反馈信道资源至少由所述多个边链路反馈信息的数目确定。
  12. 根据权利要求11所述的装置，其中，所述多个边链路反馈信息的数目基于第一设备向所述第二设备发送的边链路控制信息中的分配索引字段被确定。
  13. 根据权利要求11所述的装置，其中，所述多个边链路反馈信息包括：针对当前调度的物理边链路控制信道和/或物理边链路共享信道的反馈信息，和/或，针对之前调度的物理边链路控制信道和/或物理边链路共享信道的反馈信息。
  14. 根据权利要求13所述的装置，其中，所述当前调度的物理边链路控制信道和/或物理边链路共享信道承载的传输块不同于所述之前调度的物理边链路控制信道和/或物理边链路共享信道承载的传输块。
  15. 根据权利要求11所述的装置，其中，所述物理边链路反馈信道资源通过如下公式被确定：
    Figure PCTCN2021124985-appb-100001
    其中，P ID表示物理层源标识，M ID表示高层配置的组内成员标识，Q表示所述多个边链路反馈信息的数目，q＝0,1,…,Q-1。
  16. 根据权利要求11所述的装置，其中，在第一设备向所述第二设备发送的边链路控制信息中指示所述边链路反馈信息的分组和/或重传的信息独立于在所述网络设备向所述第一设备发送的下行控制信息中指示所述边链路反馈信息的分组和/或重传的信息。
  17. 根据权利要求5所述的装置，其中，所述接收单元还接收所述第二设备发送的用于指示所述第二设备能够同时发送的物理边链路反馈信道数目的信息。
  18. 根据权利要求11所述的装置，其中，所述多个边链路反馈信息作为整体被 确定是否被丢弃，其中所述多个边链路反馈信息中的最高优先级被用于优先级比较。
  19. 一种边链路反馈信息的发送装置，包括：
    接收单元，其接收第一设备发送的物理边链路控制信道和/或物理边链路共享信道；以及
    发送单元，其向所述第一设备发送多个边链路反馈信息；其中所述多个边链路反馈信息的物理边链路反馈信道资源至少由所述多个边链路反馈信息的数目确定。
  20. 一种通信系统，包括：
    第一设备，其在需要向网络设备发送物理上行控制信道的情况下，确定需要由所述物理上行控制信道承载的边链路反馈信息是否被接收，以及是否已经向第二设备发送与所述边链路反馈信息关联的物理边链路控制信道和/或物理边链路共享信道；在需要由所述物理上行控制信道承载的边链路反馈信息没有被接收，以及已经向所述第二设备发送与所述边链路反馈信息关联的物理边链路控制信道和/或物理边链路共享信道的情况下，不发送所述物理上行控制信道；和/或
    第二设备，其接收第一设备发送的物理边链路控制信道和/或物理边链路共享信道；以及向所述第一设备发送多个边链路反馈信息；其中所述多个边链路反馈信息的物理边链路反馈信道资源至少由所述多个边链路反馈信息的数目确定。
PCT/CN2021/124985 2021-10-20 2021-10-20 边链路反馈信息的发送和接收方法以及装置 WO2023065151A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/CN2021/124985 WO2023065151A1 (zh) 2021-10-20 2021-10-20 边链路反馈信息的发送和接收方法以及装置
CN202180103300.0A CN118120313A (zh) 2021-10-20 2021-10-20 边链路反馈信息的发送和接收方法以及装置
US18/637,765 US20240267950A1 (en) 2021-10-20 2024-04-17 Method and apparatus for transmitting and receiving sidelink feedback information

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/124985 WO2023065151A1 (zh) 2021-10-20 2021-10-20 边链路反馈信息的发送和接收方法以及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/637,765 Continuation US20240267950A1 (en) 2021-10-20 2024-04-17 Method and apparatus for transmitting and receiving sidelink feedback information

Publications (1)

Publication Number Publication Date
WO2023065151A1 true WO2023065151A1 (zh) 2023-04-27

Family

ID=86057778

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/124985 WO2023065151A1 (zh) 2021-10-20 2021-10-20 边链路反馈信息的发送和接收方法以及装置

Country Status (3)

Country Link
US (1) US20240267950A1 (zh)
CN (1) CN118120313A (zh)
WO (1) WO2023065151A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111431674A (zh) * 2019-01-10 2020-07-17 夏普株式会社 由用户设备执行的方法以及用户设备
CN112312351A (zh) * 2019-07-23 2021-02-02 北京三星通信技术研究有限公司 旁路传输的方法及设备
WO2021071331A1 (ko) * 2019-10-10 2021-04-15 엘지전자 주식회사 Nr v2x에서 sci 포맷을 기반으로 harq 피드백 정보를 송수신하는 방법 및 장치
WO2021071330A1 (ko) * 2019-10-10 2021-04-15 엘지전자 주식회사 Nr v2x에서 harq 피드백 정보를 기지국에게 보고하는 방법 및 장치

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111431674A (zh) * 2019-01-10 2020-07-17 夏普株式会社 由用户设备执行的方法以及用户设备
CN112312351A (zh) * 2019-07-23 2021-02-02 北京三星通信技术研究有限公司 旁路传输的方法及设备
WO2021071331A1 (ko) * 2019-10-10 2021-04-15 엘지전자 주식회사 Nr v2x에서 sci 포맷을 기반으로 harq 피드백 정보를 송수신하는 방법 및 장치
WO2021071330A1 (ko) * 2019-10-10 2021-04-15 엘지전자 주식회사 Nr v2x에서 harq 피드백 정보를 기지국에게 보고하는 방법 및 장치

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SPREADTRUM COMMUNICATIONS: "Remaining issues in physical layer procedures for sidelink", 3GPP DRAFT; R1-2002269, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200420 - 20200430, 11 April 2020 (2020-04-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051875513 *

Also Published As

Publication number Publication date
US20240267950A1 (en) 2024-08-08
CN118120313A (zh) 2024-05-31

Similar Documents

Publication Publication Date Title
WO2021008056A1 (zh) 用于传输侧行数据的方法、终端设备和网络设备
WO2020220359A1 (zh) 确定harq码本的方法和设备
WO2019214660A1 (zh) 通信方法和通信装置
US11729819B2 (en) Method and device for determining contention window
JP7140261B2 (ja) コンテンションウィンドウの調整方法、装置及び通信システム
WO2021031042A1 (zh) 信号发送和接收方法以及装置
WO2020191636A1 (zh) 通信方法、终端设备和网络设备
WO2020191559A1 (zh) 传输数据信道的方法和终端设备
US20220052796A1 (en) Harq information feedback method and device
US20220256470A1 (en) Power allocation method and apparatus
CN112237019B (zh) 数据发送和接收方法以及装置
WO2022006914A1 (zh) 混合自动重传请求应答harq-ack的反馈方法和终端设备
US20230199799A1 (en) Wireless communication method, terminal device and network device
WO2019192500A1 (zh) 通信方法和通信装置
WO2021088260A1 (zh) 传输反馈信息的方法、终端设备和网络设备
US20230057942A1 (en) Method and apparatus for transmitting and receiving sidelink feedback information
WO2020103028A1 (zh) 一种传输数据的方法和终端设备
TWI784764B (zh) 處理混合自動重傳請求重新傳送的裝置
WO2022117102A1 (zh) 上行控制信息传输方法、接收方法、终端和网络设备
WO2023065151A1 (zh) 边链路反馈信息的发送和接收方法以及装置
JP7277492B2 (ja) 物理的上りリンク制御チャネルの衝突を扱うための装置および方法
WO2022032515A1 (zh) 无线通信方法、终端设备和网络设备
WO2021159381A1 (zh) 上行信号处理方法、装置和系统
WO2021056419A1 (zh) 边链路资源的预留方法以及装置
WO2020133247A1 (zh) 无线通信方法、终端设备和网络设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21960907

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180103300.0

Country of ref document: CN

ENP Entry into the national phase

Ref document number: 2024523502

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE