WO2021062840A1 - 通信方法及装置 - Google Patents

通信方法及装置 Download PDF

Info

Publication number
WO2021062840A1
WO2021062840A1 PCT/CN2019/109769 CN2019109769W WO2021062840A1 WO 2021062840 A1 WO2021062840 A1 WO 2021062840A1 CN 2019109769 W CN2019109769 W CN 2019109769W WO 2021062840 A1 WO2021062840 A1 WO 2021062840A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq process
terminal
authorization
harq
resource
Prior art date
Application number
PCT/CN2019/109769
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 KR1020227014653A priority Critical patent/KR20220072870A/ko
Priority to BR112022005581A priority patent/BR112022005581A2/pt
Priority to PCT/CN2019/109769 priority patent/WO2021062840A1/zh
Priority to EP19947645.8A priority patent/EP4030840A4/en
Priority to CN201980099873.3A priority patent/CN114375602A/zh
Publication of WO2021062840A1 publication Critical patent/WO2021062840A1/zh
Priority to US17/706,961 priority patent/US20220217768A1/en

Links

Images

Classifications

    • 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/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • 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
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1858—Transmission or retransmission of more than one copy of acknowledgement message
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1864—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1874—Buffer management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/188—Time-out mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • 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

  • This application relates to the field of communication technology, and in particular to a communication method and device.
  • the Internet of Vehicles (vehicle to everything, V2X) is the key technology of the intelligent transportation system, and it is considered to be one of the fields with the most industrial potential and the clearest market demand in the Internet of Things system. Telematics generally refer to information provided by the vehicle sensors in the car load, car terminal, etc., to achieve a vehicle to the vehicle (vehicle to vehicle, V2V), vehicle-to-infrastructure (vehicle to infrastructure, V2I), the vehicle network (vehicle to network, V2N) and a communication network for mutual communication between vehicles to pedestrians (V2P).
  • V2V vehicle to vehicle
  • V2I vehicle-to-infrastructure
  • V2N vehicle network
  • V2P vehicle to network
  • V2X has the characteristics of wide application space, great industrial potential, and strong social benefits. It is useful for promoting the innovative development of the automobile and information and communication industries, building new models and new business formats for automobiles and transportation services, and promoting unmanned driving, assisted driving, intelligent driving, and connected driving.
  • the innovation and application of technologies such as, intelligent networked driving, autonomous driving, and car sharing, as well as the improvement of traffic efficiency and safety levels, are of great significance.
  • a communication link for direct communication between a terminal and other terminals may be called a side link (sidelink, SL) or a side link.
  • sidelink sidelink
  • HARQ hybrid automatic repeat request
  • ID process identification
  • the embodiments of the present application provide a communication method and device for determining the HARQ process ID of the SL.
  • a communication method including: a first terminal determines first HARQ information associated with a first sideline authorization, and sends the first HARQ information to a second terminal through a sideline link.
  • the first side line authorization is used to carry data between the first terminal and the second terminal
  • the first HARQ information includes: the first HARQ process identifier associated with the first side line authorization
  • the side line link is the first The wireless direct communication link between the terminal and the second terminal.
  • the first terminal can determine the HARQ process ID associated with the side-line authorization by itself. In this case, the first terminal can determine the HARQ process ID associated with the side-line authorization according to requirements without being affected by the network equipment.
  • the first HARQ information further includes: new data indication information used to indicate that the corresponding transmission is a new transmission or a retransmission.
  • the first HARQ process identifier is greater than or equal to 0 and less than N
  • N is the maximum number of HARQ processes supported by the first terminal on a carrier
  • N is an integer greater than zero. This possible implementation can save the number of bits occupied by the HARQ process identifier in the SCI.
  • the first terminal determining the first HARQ process identifier in the first HARQ information associated with the first side row authorization includes: the first terminal determines the maximum N that the first terminal supports on a carrier. The identifier of the unoccupied HARQ process among the two HARQ processes is determined to be the first HARQ process identifier; or, in the case that the first side line is authorized to preempt the second side line authorization, the first terminal compares the identification determined by the first terminal with The HARQ process identifier associated with the second side row authorization is determined as the first HARQ process identifier.
  • the method further includes: the first terminal saves the correspondence between the first side authorization and the first HARQ process identifier; or, the first terminal saves the first HARQ process identifier and the second HARQ process identifier.
  • the corresponding relationship between process IDs; or, the first terminal saves the corresponding relationship between the first side authorization, the first HARQ process ID, and the second HARQ process ID; for example, the second HARQ process ID is the first terminal
  • the method further includes: the first terminal obtains a third side authorization for retransmitting data; the first terminal determines the first HARQ process identifier as the HARQ process associated with the third side authorization Identification; the first terminal sends second HARQ information to the second terminal, the second HARQ information includes: the first HARQ process identification associated with the third side line authorization.
  • the second HARQ information further includes: new data indication information used to indicate that the corresponding transmission is a retransmission.
  • the first terminal acquiring the third side authorization for retransmitting the data includes: the first terminal determines the third side authorization for retransmitting the data; or, the first terminal sends to the network
  • the device sends a request message, which is used to request resources for retransmission of data; the request message includes the second HARQ process identifier, or the resource for the transmission request message is associated with the second HARQ process identifier; the first terminal receives the request response from the network device,
  • the request response includes information for indicating authorization of the third side.
  • the first terminal determining the third side authorization for retransmitting the data includes: the first terminal selects the third side authorization for retransmitting the data from the first resource, and the first terminal Resources include any one or any of the following types of resources: resources of the side link; resources of the first mode of the side link; resources of the second mode of the side link; resources of the side link Configure authorized resources; the first type of side links configure authorized resources; the second type of side links configure authorized resources; the dynamic authorized resources of side links; the set of configured authorized resources of side links, configure authorized resources The set includes one or more configuration authorization resources corresponding to the configuration authorization resource index.
  • the method further includes: the first terminal receives configuration information of the network device, where the configuration information is used to configure the type of resource included in the first resource.
  • This possible implementation can enable the first terminal to determine the first resource, so that the first terminal can learn which resources can be used for data retransmission.
  • the second HARQ process identifier associated with the first side line authorization is the same or different from the fourth HARQ process identifier associated with the third side line authorization.
  • the fourth HARQ process identifier is the first The terminal authorizes the HARQ process identifier determined for the third side according to a preset algorithm or the network device is the HARQ process identifier indicated by the third side authorization.
  • the method further includes: the first terminal updates the correspondence between the first side authorization and the first HARQ process identifier to: between the third side authorization and the first HARQ process identifier Or, the first terminal updates the corresponding relationship between the first HARQ process identifier and the second HARQ process identifier to: the corresponding relationship between the first HARQ process identifier and the fourth HARQ process identifier; or, the first The terminal updates the correspondence between the first side authorization, the first HARQ process identifier, and the second HARQ process identifier to: the correspondence between the third side authorization, the first HARQ process identifier, and the fourth HARQ process identifier;
  • the fourth HARQ process identifier is the HARQ process identifier determined by the first terminal according to the preset algorithm for the third side authorization or the network device is the HARQ process identifier indicated by the third side authorization.
  • the method further includes: in the case where the HARQ process corresponding to the first HARQ process identifier ends, the first terminal authorizes the corresponding relationship between the first side line authorization and the first HARQ process identifier, Or, the correspondence between the first HARQ process ID and the second HARQ process ID, or the correspondence between the first side authorization, the first HARQ process ID and the second HARQ process ID is deleted.
  • This possible implementation method releases storage resources in time, can improve the utilization of storage resources, and can also be used to identify occupied and unoccupied HARQ processes.
  • the end of the HARQ process corresponding to the first HARQ process identifier includes any one or more of the following situations: 1) The first terminal does not receive the HARQ process corresponding to the first HARQ process identifier Feedback; 2) the first terminal receives the positive confirmation of the HARQ process corresponding to the first HARQ process identifier; 3) the first terminal only receives the positive confirmation of the HARQ process corresponding to the first HARQ process identifier; 4) the first terminal Send a positive confirmation of the HARQ process corresponding to the first HARQ process identifier to the network device; 5) the data transmission associated with the HARQ process corresponding to the first HARQ process identifier reaches the maximum transmission time; 6) the HARQ corresponding to the first HARQ process identifier The data transmission associated with the process reaches the maximum number of transmissions; 7) the first terminal releases the HARQ process corresponding to the first HARQ process identifier; 8) the first terminal clears the HARQ buffer
  • the method further includes: in the case that the fourth side row authorization preempts the first side row authorization, the first terminal determines third HARQ information associated with the fourth side row authorization, and the third HARQ The information includes: the fifth HARQ process identifier associated with the fourth side authorization.
  • the method further includes: the first terminal updates the corresponding relationship between the first side row authorization and the first HARQ process identification to: between the fourth side row authorization and the fifth HARQ process identification Or, the first terminal updates the corresponding relationship between the first HARQ process identifier and the second HARQ process identifier to: the corresponding relationship between the fifth HARQ process identifier and the sixth HARQ process identifier; or, the first The terminal updates the correspondence between the first side authorization, the first HARQ process identifier, and the second HARQ process identifier to: the correspondence between the fourth side authorization, the fifth HARQ process identifier, and the sixth HARQ process identifier;
  • the sixth HARQ process identifier is the HARQ process identifier determined by the first terminal according to the preset algorithm for the fourth side bank authorization or the network device is the HARQ process identifier indicated by the fourth side bank authorization.
  • the first side-line authorization belongs to the second resource
  • the second resource includes any one or any of the following types of resources: resources of the side-link; Resources in the first mode; resources in the second mode of side links; authorized resources in the configuration of side links; authorized resources in the first type of side links; authorized resources of the second type in side links; side
  • the dynamic authorized resource of the uplink; the configuration authorized resource set of the side link, the configuration authorized resource set includes one or more configuration authorized resource corresponding to the configuration authorized resource index.
  • the method before the first terminal determines the first HARQ information for the first side authorization, the method further includes: the first terminal determines that there is data to be sent on the first side authorization.
  • a communication method including: a network device generates configuration information used to configure a type of resource included in a first resource, and sends the configuration information to a first terminal.
  • the first resource is used for the retransmission of data between the first terminal and other terminals.
  • the first terminal and other terminals communicate through side-links, and the side-links are between the first terminal and other terminals.
  • the first resource includes any one or any of the following types of resources: resources of the side link; resources of the first mode of the side link; side Resources of the second mode of the uplink; authorized resources of the configuration of the side links; authorized resources of the first type of the side links; authorized resources of the second type of the side links; dynamic authorization of the side links Resources; a collection of configuration authorization resources for side links, the configuration authorization resource collection includes one or more configuration authorization resources corresponding to the configuration authorization resource index.
  • the method provided in the second aspect can configure the type of resources included in the first resource for the first terminal, so that the first terminal can determine the first resource, so that the first terminal can learn which resources can be used for data retransmission.
  • the first resource is specifically used for retransmission of data carried on the second resource between the first terminal and other terminals;
  • the second resource includes any one or more of the following Types of resources: resources of the side link; resources of the first mode of the side link; resources of the second mode of the side link; configuration authorization resources of the side link; the first type of the side link Configure authorized resources; the second type of side link configuration authorized resources; the side link dynamic authorized resources; the side link configuration authorized resource collection, the configuration authorized resource collection includes one or more configuration authorized resource index corresponding Configure authorized resources.
  • a communication method which includes: a first terminal determines first HARQ information associated with a first side-line authorization.
  • the first side-line authorization is used to carry the first terminal and
  • the first HARQ information includes: the HARQ process identifier associated with the first side authorization; the first terminal obtains the third side authorization for retransmitting the data;
  • the first terminal determines second HARQ information associated with the third side line authorization, the second HARQ information includes: the HARQ process identifier associated with the third side line authorization, and the third side line authorization associated with the HARQ process identifier
  • the HARQ process identifier is the same as the HARQ process identifier associated with the first side row authorization.
  • the first HARQ information further includes: new data indication information, which is used to indicate that the corresponding transmission is a new transmission or a retransmission; and/or, the second HARQ The information also includes: new data indication information, where the new data indication information is used to indicate that the corresponding transmission is a retransmission.
  • a resource allocation method including: a network device starts a first timer associated with a second HARQ process ID of a first terminal, where the second HARQ process ID is the network device according to a preset algorithm The HARQ process ID determined for the first side line authorization of the first terminal; if the first timer expires, if the network device does not receive the HARQ process corresponding to the second HARQ process ID
  • the network device sends resource indication information to the first terminal, where the resource indication information is used to indicate the sideline link resource for retransmitting the sideline data.
  • a method for clearing an HARQ buffer including: a terminal determines that uplink data transmission is completed; and the terminal clears the HARQ buffer corresponding to the HARQ process used to transmit the uplink data.
  • the method provided by the fifth aspect can clear the HARQ buffer when the data transmission is completed, thereby saving buffer space.
  • a method for clearing the HARQ buffer including: a terminal determines that side-line data transmission is completed, and the side-line data transmission completion includes that the side-line data transmission is successful or the side-line data transmission reaches the maximum number of transmissions Or the transmission of the sideline data reaches the maximum transmission time; the terminal clears the HARQ buffer corresponding to the HARQ process used to transmit the sideline data.
  • the method provided by the sixth aspect can clear the HARQ buffer when the data transmission is completed, thereby saving buffer space.
  • the successful transmission of the side-line data includes any one or more of the following situations: the terminal does not receive a negative confirmation for the side-line data; the terminal receives A positive confirmation of the side row data; the terminal receives a positive confirmation for the side row data, and does not receive a negative confirmation for the side row data.
  • a communication device including: a processing unit and a communication unit; the processing unit is configured to determine the first HARQ information associated with the first side authorization.
  • the first side authorization is used for carrying
  • the first HARQ information includes: the first HARQ process identifier associated with the first sideline authorization;
  • the communication unit is configured to send the first HARQ information to the second terminal through the sideline link,
  • the side link is a wireless direct communication link between the device and the second terminal.
  • the first HARQ information further includes: new data indication information, where the new data indication information is used to indicate that the corresponding transmission is a new transmission or a retransmission.
  • the first HARQ process identifier is greater than or equal to 0 and less than N
  • N is the maximum number of HARQ processes supported by the device on a carrier
  • N is an integer greater than zero.
  • the processing unit is specifically configured to: determine an unoccupied HARQ process identifier among the N HARQ processes supported by the device on a carrier as the first HARQ process identifier; or In the case that the first side line authorization preempts the second side line authorization, the HARQ process identifier associated with the second side line authorization determined by the device is determined as the first HARQ process identifier.
  • the processing unit is further configured to: save the correspondence between the first side row authorization and the first HARQ process identifier; or, save the relationship between the first HARQ process identifier and the second HARQ process identifier Or, save the corresponding relationship between the first side authorization, the first HARQ process identifier and the second HARQ process identifier; for example, the second HARQ process identifier means that the device is the first side according to a preset algorithm The HARQ process identifier determined by the line authorization or the HARQ process identifier indicated by the first side line authorization by the network device.
  • the processing unit is further configured to obtain the third side authorization for retransmitting data; the processing unit is also used to determine the first HARQ process identifier as the HARQ associated with the third side authorization Process ID; the communication unit is also used to send second HARQ information to the second terminal.
  • the second HARQ information includes: the first HARQ process ID associated with the third side line authorization.
  • the second HARQ information further includes: new data indication information, where the new data indication information is used to indicate that the corresponding transmission is a retransmission.
  • the processing unit is specifically configured to: determine the third side authorization for retransmission of data; or, send a request message to the network device through the communication unit, and the request message is used for requesting retransmission of data.
  • Resource the request message includes the second HARQ process identifier, or the resource for transmitting the request message is associated with the second HARQ process identifier;
  • the request response is received from the network device through the communication unit, and the request response includes information for indicating authorization of the third side .
  • the processing unit is specifically configured to: select a third side row authorization for retransmission of data from the first resource, and the first resource includes any one or several types of the following Resources: resources of the side link; resources of the first mode of the side link; resources of the second mode of the side link; resources of the side link configuration authorization; the first type of configuration authorization of the side link Resources; the second type of side link configuration authorization resources; the side link dynamic authorization resources; the side link configuration authorization resource collection, the configuration authorization resource collection includes one or more configuration authorization resource indexes corresponding to the configuration authorization Resources.
  • the communication unit is further configured to receive configuration information of the network device, and the configuration information is used to configure the type of resource included in the first resource.
  • the second HARQ process identifier associated with the first side line authorization is the same or different from the fourth HARQ process identifier associated with the third side line authorization.
  • the fourth HARQ process identifier is the device According to a preset algorithm, the HARQ process identifier determined for the third-party authorization or the network device is the HARQ process identifier indicated by the third-party authorization.
  • the processing unit is further configured to: update the corresponding relationship between the first side row authorization and the first HARQ process identifier to: the third side row authorization and the first HARQ process identifier Correspondence; or, update the correspondence between the first HARQ process ID and the second HARQ process ID to: the correspondence between the first HARQ process ID and the fourth HARQ process ID; or, authorize the first side row ,
  • the corresponding relationship between the first HARQ process identifier and the second HARQ process identifier is updated to: the third side authorization, the corresponding relationship between the first HARQ process identifier and the fourth HARQ process identifier; exemplary, the fourth HARQ
  • the process identifier is the HARQ process identifier determined by the device for the third-party authorization according to the preset algorithm or the HARQ process identifier indicated by the third-party authorization by the network device.
  • the processing unit is further configured to: in the case where the HARQ process corresponding to the first HARQ process identifier ends, the corresponding relationship between the first side row authorization and the first HARQ process identifier, or , The corresponding relationship between the first HARQ process identifier and the second HARQ process identifier, or the corresponding relationship between the first side authorization, the first HARQ process identifier and the second HARQ process identifier is deleted.
  • the end of the HARQ process corresponding to the first HARQ process identifier includes any one or more of the following situations: 1) The device does not receive the feedback of the HARQ process corresponding to the first HARQ process identifier 2) The device receives the positive confirmation of the HARQ process corresponding to the first HARQ process identifier; 3) The device only receives the positive confirmation of the HARQ process corresponding to the first HARQ process identifier; 4) The device sends to the network device Positive confirmation of the HARQ process corresponding to the first HARQ process identifier; 5) The data transmission associated with the HARQ process corresponding to the first HARQ process identifier reaches the maximum transmission time; 6) The data associated with the HARQ process corresponding to the first HARQ process identifier The transmission reaches the maximum number of transmissions; 7) The device releases the HARQ process corresponding to the first HARQ process identifier; 8) The device clears the HARQ buffer corresponding to the HARQ buffer corresponding to the
  • the processing unit is further configured to: in the case that the fourth side row authorization preempts the first side row authorization, determine the third HARQ information associated with the fourth side row authorization, and the third HARQ information It includes: the fifth HARQ process identifier associated with the fourth side authorization.
  • the processing unit is further configured to: update the correspondence between the first side row authorization and the first HARQ process identifier to: the fourth side row authorization and the fifth HARQ process identifier Correspondence; or, update the correspondence between the first HARQ process ID and the second HARQ process ID to: the correspondence between the fifth HARQ process ID and the sixth HARQ process ID; or, authorize the first side row ,
  • the corresponding relationship between the first HARQ process identifier and the second HARQ process identifier is updated to: the fourth side authorization, the corresponding relationship between the fifth HARQ process identifier and the sixth HARQ process identifier; exemplary, the sixth HARQ
  • the process identifier is the HARQ process identifier determined for the fourth side authorization by the device according to the preset algorithm or the HARQ process identifier indicated by the fourth side authorization by the network device.
  • the first side-line authorization belongs to the second resource
  • the second resource includes any one or any of the following types of resources: resources of the side-link; Resources of the first mode; resources of the second mode of the side link; authorized resources of the configuration of the side link; authorized resources of the first type of the side link; authorized resources of the second type of the side link; side
  • the dynamic authorized resource of the uplink; the configuration authorized resource set of the side link, the configuration authorized resource set includes one or more configuration authorized resource corresponding to the configuration authorized resource index.
  • the processing unit is further configured to: determine that there is data to be sent on the first side line authorization.
  • a communication device including: a processing unit and a communication unit; the processing unit is configured to generate configuration information, the configuration information is used to configure the type of resource included in the first resource, and the first resource is used for the first terminal For retransmission of data with other terminals, the first terminal communicates with other terminals through a side-line link.
  • the side-line link is a wireless direct communication link between the first terminal and other terminals; the communication unit, Used to send configuration information to the first terminal; for example, the first resource includes any one or any of the following types of resources: resources of the side link; resources of the first mode of the side link; The second mode of side link resources; side link configuration authorized resources; the first type of side link configuration authorized resources; the second type of side link configuration authorized resources; side link dynamics Authorized resources; a set of configuration authorized resources for side links, the set of configuration authorized resources includes one or more configuration authorized resources corresponding to the index of configuration authorized resources.
  • the first resource is specifically used for retransmission of data carried on the second resource between the first terminal and other terminals;
  • the second resource includes any one or more of the following Types of resources: resources of the side link; resources of the first mode of the side link; resources of the second mode of the side link; configuration authorization resources of the side link; the first type of the side link Configure authorized resources; the second type of side link configuration authorized resources; the side link dynamic authorized resources; the side link configuration authorized resource collection, the configuration authorized resource collection includes one or more configuration authorized resource index corresponding Configure authorized resources.
  • a communication device including: a processing unit; the processing unit is configured to determine first HARQ information associated with a first side authorization.
  • the first side authorization is used for Carrying data between the device and the second terminal
  • the first HARQ information includes: the HARQ process identifier associated with the first side line authorization
  • the processing unit is further configured to obtain the data used to retransmit the data
  • the processing unit is further configured to determine second HARQ information associated with the third side authorization
  • the second HARQ information includes: the HARQ process associated with the third side authorization ID, the HARQ process ID associated with the third side line authorization is the same as the HARQ process ID associated with the first side line authorization.
  • the first HARQ information further includes: new data indication information, which is used to indicate that the corresponding transmission is a new transmission or a retransmission; and/or, the second HARQ The information also includes: new data indication information, where the new data indication information is used to indicate that the corresponding transmission is a retransmission.
  • a resource allocation device including: a processing unit and a communication unit, the processing unit is configured to start a first timer associated with a second HARQ process ID of a first terminal, and the second HARQ
  • the process ID is the HARQ process ID determined by the device for the first side line authorization of the first terminal according to a preset algorithm; in the case that the first timer expires, if the device does not receive the
  • the communication unit is configured to send resource indication information to the first terminal, and the resource indication information is used to instruct to retransmit the side line.
  • the side link resource of the row data is provided, including: a processing unit and a communication unit, the processing unit is configured to start a first timer associated with a second HARQ process ID of a first terminal, and the second HARQ
  • the process ID is the HARQ process ID determined by the device for the first side line authorization of the first terminal according to a preset algorithm; in the case that the first timer expires, if the device does not receive the
  • an apparatus for clearing HARQ buffers including: a processing unit, configured to determine that uplink data transmission is completed, and clear the HARQ buffer corresponding to the HARQ process used to transmit the uplink data.
  • a device for clearing HARQ buffers including: a processing unit, configured to determine that side-line data transmission is complete, and clear the HARQ buffer corresponding to the HARQ process used to transmit the side-line data, the side
  • the completion of the line data transmission includes that the side line data transmission is successful or the side line data transmission reaches the maximum number of transmission times or the side line data transmission reaches the maximum transmission time.
  • the successful transmission of the side line data includes any one or more of the following: the terminal does not receive a negative confirmation for the side line data; the terminal receives a negative confirmation for the side line data; The positive confirmation of the side row data; the terminal receives the positive confirmation for the side row data, and does not receive the negative confirmation for the side row data.
  • a communication device including a processor.
  • the processor is connected to the memory, the memory is used to store computer-executed instructions, and the processor executes the computer-executed instructions stored in the memory, so as to implement any one of the methods provided in any one of the first aspect to the sixth aspect.
  • the memory and the processor may be integrated together, or may be independent devices. In the latter case, the memory may be located in the communication device or outside the communication device.
  • the processor includes a logic circuit, and also includes at least one of an input interface and an output interface.
  • the output interface is used to execute the sending action in the corresponding method
  • the input interface is used to execute the receiving action in the corresponding method.
  • the communication device further includes a communication interface and a communication bus, and the processor, the memory, and the communication interface are connected through the communication bus.
  • the communication interface is used to perform the sending and receiving actions in the corresponding method.
  • the communication interface may also be called a transceiver.
  • the communication interface includes at least one of a transmitter and a receiver. In this case, the transmitter is used to perform the sending action in the corresponding method, and the receiver is used to perform the receiving action in the corresponding method.
  • the communication device exists in the form of a chip product.
  • a communication system including: the communication device provided in the seventh aspect and the communication device provided in the eighth aspect.
  • a computer-readable storage medium including instructions, which when run on a computer, cause the computer to execute any one of the methods provided in any one of the first to sixth aspects.
  • a computer program product containing instructions is provided. When the instructions are run on a computer, the computer executes any one of the methods provided in any one of the first to sixth aspects.
  • FIG. 1 is a schematic diagram of a communication scenario provided by an embodiment of this application.
  • Figure 2 is a schematic diagram of a side authorization provided by an embodiment of the application
  • FIG. 3 is a schematic diagram of a parallel HARQ process provided by an embodiment of this application.
  • FIG. 4 is a schematic diagram of an uplink grant and its corresponding HARQ process ID provided by an embodiment of this application;
  • FIG. 8 are schematic diagrams of sideline authorizations and their associated HARQ process IDs in multiple SL transmission resources provided by embodiments of the application;
  • 9 and 10 are respectively flowcharts of a communication method provided by an embodiment of this application.
  • FIG. 10A is a flow chart of a communication method provided by an embodiment of this application.
  • 10B is a schematic diagram of data transmission between a sending terminal and a receiving terminal according to an embodiment of the application
  • FIG. 11 is a schematic diagram of a side-line authorization and its corresponding HARQ process ID provided by an embodiment of this application;
  • FIG. 12 is a schematic diagram of a corresponding relationship stored in a first terminal according to an embodiment of this application.
  • FIG. 13 is a schematic diagram of a side-line authorization and its corresponding HARQ process ID provided by an embodiment of this application;
  • 14 and 15 are respectively schematic diagrams of corresponding relationships stored in a first terminal according to an embodiment of the application.
  • FIG. 16 and FIG. 17 are respectively flowcharts of a method for clearing HARQ buffers according to an embodiment of the application
  • FIG. 18 is a schematic diagram of the composition of a communication device provided by an embodiment of the application.
  • FIG. 19 and FIG. 20 are respectively schematic diagrams of the hardware structure of a communication device according to an embodiment of the application.
  • A/B can mean A or B.
  • “And/or” in this article is only an association relationship describing the associated objects, which means that there can be three kinds of relationships.
  • a and/or B can mean: A alone exists, A and B exist at the same time, and B exists alone. These three situations.
  • “at least one” means one or more, and “plurality” means two or more.
  • the words “first” and “second” do not limit the quantity and order of execution, and the words “first” and “second” do not limit the difference.
  • D2D device to device
  • V2X unmanned driving
  • ADS automated driving
  • driver assistance driver assistance
  • ADAS driver assistance
  • the network elements involved in this application include network equipment and terminals in a communication system.
  • the method provided by the embodiment of the present application mainly involves the communication between the terminal and the terminal, and the communication between the terminal and the network device.
  • the communication systems in the embodiments of the present application include, but are not limited to, long term evolution (LTE) systems, fifth-generation (5th-generation, 5G) systems, new radio (NR) systems, and wireless local area networks (wireless local area networks). area networks, WLAN) systems and future evolution systems or multiple communication fusion systems.
  • LTE long term evolution
  • 5th-generation 5th-generation
  • NR new radio
  • wireless local area networks wireless local area networks
  • area networks wireless local area networks
  • WLAN wireless local area networks
  • future evolution systems or multiple communication fusion systems wireless local area networks
  • the 5G system can be a non-standalone (NSA) 5G system or a standalone (SA) 5G system.
  • the network device in the embodiment of the present application is an entity on the network side that is used to send signals, receive signals, or send signals and receive signals.
  • the network equipment may be a device that is deployed in a radio access network (RAN) to provide wireless communication functions for the terminal, such as a transmission reception point (TRP), a base station, and various forms of control nodes ( For example, a network controller, a wireless controller (for example, a wireless controller in a cloud radio access network (CRAN) scenario)).
  • the network equipment may be various forms of macro base stations, micro base stations (also referred to as small stations), relay stations, access points (access points, AP), etc., and may also be antenna panels of base stations.
  • the control node may be connected to multiple base stations and configure resources for multiple terminals under the coverage of the multiple base stations.
  • the names of devices with base station functions may be different.
  • the LTE system may be called an evolved NodeB (eNB or eNodeB), and the 5G system or NR system may be called the next generation node base station (gNB).
  • eNB evolved NodeB
  • gNB next generation node base station
  • the specific name of the base station in this application Not limited.
  • the network equipment may also be the network equipment in the public land mobile network (PLMN) that will evolve in the future.
  • PLMN public land mobile network
  • the terminal in the embodiment of the present application is an entity on the user side that is used to receive signals, or send signals, or receive signals and send signals.
  • the terminal is used to provide users with one or more of voice services and data connectivity services.
  • the terminal can also be called user equipment (UE), terminal equipment, access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user Device.
  • the terminal can be a V2X device, for example, a smart car (smart car or intelligent car), a digital car (digital car), an unmanned car (unmanned car or driverless car or pilotless car or automobile), and an automatic car (self-driving car or autonomous car).
  • the terminal can also be a D2D device, such as an electric meter, a water meter, and so on.
  • the terminal can also be a mobile station (MS), subscriber unit (subscriber unit), drone, Internet of things (IoT) equipment, station (ST) in WLAN, and cellular phone (cellular phone).
  • the terminal may also be a terminal in a next-generation communication system, for example, a terminal in a 5G system or a terminal in a future evolved PLMN, a terminal in an NR system, and so on.
  • the wireless communication link through which the terminal sends data (ie, uplink data) to the network device may be referred to as UL.
  • the wireless communication link through which the network device sends data (ie, downlink data) to the terminal may be referred to as DL.
  • UL interface and DL interface can be collectively referred to as Uu interface, therefore, UL and DL can be collectively referred to as Uu interface link.
  • the communication link of the direct communication between the terminal and the terminal may be referred to as SL.
  • SL can also be called a side link.
  • the data transmitted between the terminal and the terminal can be referred to as SL data.
  • the data in the embodiment of the present application may be understood as a transport block (transport block, TB) or medium access control (medium access control, MAC) protocol data unit (protocol data unit, PDU).
  • Transport block transport block
  • MAC medium access control
  • PDU protocol data unit
  • the SL transmission resources used by the sending terminal of the two terminals can be determined by any of the following methods A and B.
  • Method A network equipment scheduling
  • the mode in which the network device schedules SL transmission resources may include a mode 1 (mode1) resource configuration mode (name in NR) or a mode 3 (mode3) resource configuration mode (name in LTE).
  • mode1 mode 1
  • mode3 mode 3 resource configuration mode
  • the SL transmission resources scheduled by the network equipment are of the following two types:
  • each data transmission of the sending terminal does not always require the network device to allocate resources separately.
  • the sending terminal can use the above allocated resources for a period of time in the future.
  • the network device may configure a period of time domain resources that appear periodically for the sending terminal. Exemplarily, referring to FIG. 2, the first time domain resource in this segment of periodically occurring time domain resources is symbol 4 to symbol 9 of time slot 1, and the period is 1 time slot.
  • the time domain resource that appears each time is an SL authorization (hereinafter referred to as a side-line authorization), it can be understood that 4 side-line authorizations are shown in Figure 2, and one side-line authorization corresponds to one Side authorization ID, the side authorization IDs corresponding to the 4 side authorizations are side authorization 0, side authorization 1, side authorization 2, and side authorization 3.
  • CG resources can include type 1 (type 1) CG (SL configured grant type-1) resources, type 2 (type 2) CG (SL configured grant type-2) resources, authorization-free (SL grant free) resources, and semi-static scheduling (SL) resources.
  • SL SPS Semi-Persistent Scheduling, SL SPS) resources.
  • the type1CG resource may be an SL transmission resource that the network device directly configures to the sending terminal through radio resource control (radio resource control, RRC) signaling, and the sending terminal can directly use the CG resource to transmit data without additional activation.
  • radio resource control radio resource control
  • the type2CG resource can be the period in which the network device defines the SL transmission resource through RRC signaling, and then activates the SL transmission resource through downlink control information (DCI) in the physical downlink control channel (PDCCH), and sends
  • the terminal cannot directly use the SL transmission resource to transmit data, and can only be used after activation.
  • the authorization-free resource may be an SL transmission resource directly configured by the network device to the sending terminal through RRC signaling, and the sending terminal may directly use the SL transmission resource to transmit data without additional activation.
  • the semi-persistent scheduling resource may be a network device defining the SL transmission resource cycle through RRC signaling, and then activating the SL transmission resource through the DCI in the PDCCH. The sending terminal cannot directly use the SL transmission resource to transmit data, and can only be used after activation.
  • CG resources whose indexes are 1, 2, and 3 can be denoted as CG1, CG2, and CG3, respectively.
  • the second type dynamic grant (DG) resources
  • each data transmission of the sending terminal requires the network device to allocate resources separately, which is characterized by "one time allocation, one use".
  • the network device may dynamically allocate SL transmission resources to the sending terminal through DCI.
  • the DCI can be carried in the PDCCH.
  • DG the network device needs to allocate authorization for each data transmission of the sending terminal, and the resource allocation is flexible, but the resource allocation overhead is relatively large.
  • CG one-time authorized allocation of network equipment, the sending terminal can be used multiple times, the resource allocation overhead is small, but the allocated resources have not changed and adjusted for a long time, and the resource allocation is not flexible.
  • DG generally uses physical channels (for example, PDCCH) to allocate, and the allocation is relatively fast.
  • the CG is generally configured using high-level signaling (for example, RRC signaling) or high-level signaling (for example, RRC signaling) plus a physical channel (for example, PDCCH), and resource allocation is slow.
  • Method B the sending terminal determines by itself
  • the mode for the sending terminal to determine the SL transmission resource by itself may include mode 2 (mode2) resource configuration mode (name in NR) or mode 4 (mode4) resource configuration mode (name in LTE).
  • mode2 mode 2
  • mode4 mode 4
  • the network device when the sending terminal is within the communication coverage of the network device, the network device can configure the SL resource pool for the sending terminal through a system information block (SIB) message or dedicated RRC signaling, and the sending terminal can independently obtain the SL resources
  • SIB system information block
  • the SL transmission resources are acquired in the pool to send control signals and/or data signals to the receiving terminal.
  • the sending terminal can autonomously obtain SL transmission resources from the pre-configured SL resource pool to send control signals and/or data signals to the receiving terminal.
  • the sending terminal When acquiring SL transmission resources from the SL resource pool, the sending terminal can perceive or compete for SL transmission resources. Specifically, the sending terminal transmits control signals and/or data signals by competing with other terminals to obtain appropriate SL transmission resources in the SL resource pool. Among them, the higher the priority of the V2X service or data to be transmitted in the sending terminal, the greater the chance of it competing for suitable SL transmission resources in the SL resource pool.
  • mode3 and mode4 cannot exist at the same time.
  • mode1 and mode2 can exist at the same time.
  • the above SL resources can be divided into multiple types, including the following:
  • SL transmission resources scheduled by the network device may include: resources configured in the above-mentioned mode1 resource configuration mode, or resources configured in the above-mentioned mode3 resource configuration mode.
  • the resources configured in the above-mentioned mode1 resource configuration mode or the resources configured in the above-mentioned mode3 resource configuration mode may include: CG resources of SL and/or DG resources of SL.
  • SL transmission resources that the terminal needs to select or compete or perceive by itself which may include resources configured in the above-mentioned mode2 resource configuration mode, or resources configured in the above-mentioned mode4 resource configuration mode.
  • SL's first type CG resources CG resources that can be used directly without activation, which may include: the above-mentioned type1CG resources, and/or the above-mentioned authorization-free resources.
  • the second type of CG resource of the SL the CG resource that cannot be used directly by the terminal and can be used after activation may include: the above-mentioned type2CG resource, and/or the above-mentioned semi-persistent scheduling resource.
  • SL resources resources in the first mode of the above SL, and/or resources in the second mode of the above SL.
  • CG resources of the SL the first type CG resources of the above SL, and/or the second type CG resources of the above SL.
  • DG resources of SL SL transmission resources dynamically allocated to the terminal by network equipment through DCI.
  • the CG resource set includes one or more CG resources corresponding to the CG resource index, for example, a resource set composed of CG1, CG2, and CG3.
  • CG resource set 1 is one type of resource
  • CG resource set 2 is another type of resource.
  • HARQ is a technology that combines forward error correction (or forward error correction code) (FEC) and automatic repeat request (ARQ) methods.
  • FEC forward error correction code
  • ARQ automatic repeat request
  • FEC means that the data sent by the sender includes forward error correction code or redundant information.
  • the receiver receives the data, it passes a check (for example, cyclic redundancy check, CRC). ) After the error is found, it can be corrected by forward error correction code or redundant information, so that the sender can reduce the number of retransmissions (ie, retransmission of data).
  • CRC cyclic redundancy check
  • ARQ means that the receiving end judges the correctness of the received data through verification (for example, CRC check). If the data is received correctly, the receiving end sends an acknowledgement (ACK) to inform the sending end, otherwise the receiving end sends a negative confirmation ( Negative acknowledgement (NACK) informs the sender that when the sender receives the NACK, it can retransmit the data to the receiver.
  • ACK and NACK are HARQ feedback.
  • LTE V2X since LTE V2X only supports broadcast services, SL HARQ feedback is not supported.
  • NR V2X supports unicast, multicast and broadcast services, and supports SL HARQ feedback.
  • HARQ uses stop-and-wait protocol to send data.
  • the stop-and-wait protocol after the sender sends a transport block (TB), it stops and waits for the confirmation message.
  • the receiving end can feed back ACK or NACK for the TB.
  • the sender stops and waits for confirmation, which results in very low throughput. Therefore, multiple parallel HARQ processes can be used: when one HARQ process is waiting for confirmation, the sender can use another HARQ process to continue sending data.
  • the terminal uses the first HARQ process to send TB1, sends TB1 at time T1, receives HARQ feedback from TB1 at time T2, and waits for TB1's confirmation during the time period from T1 to T2.
  • the second HARQ process can be used to send TB2, send TB2 at time T2, receive HARQ feedback from TB2 at time T3, and wait for TB2’s confirmation during the time period from T2 to T3.
  • the third HARQ process can be used to send TB3.
  • each HARQ process can handle one TB in one transmission time interval (TTI), and can also handle multiple TBs (for example, in the case of space division multiplexing).
  • TTI transmission time interval
  • multiple TBs for example, in the case of space division multiplexing
  • one side-line authorization is associated with one HARQ process.
  • multiple side-line authorizations included in a bundle are associated with the same HARQ process, that is, the transmissions (for example, uplink transmission, or side-line transmission) on multiple side-line authorizations included in a bundle correspond to the same HARQ process.
  • HARQ process the transmissions (for example, uplink transmission, or side-line transmission) on multiple side-line authorizations included in a bundle correspond to the same HARQ process.
  • the transmission in a bundle can be understood as a TB that needs to be retransmitted one or more times after a new transmission.
  • multiple transmissions of the same TB are associated with the same HARQ process.
  • data received multiple times in the same HARQ process can be placed in the same buffer (for example, HARQ buffer or soft buffer) for soft combining and decoding.
  • a HARQ process is identified by a HARQ process ID.
  • the descriptions of the HARQ process of the terminal in the embodiments of the present application are all for one carrier.
  • the situation on each carrier is the same as in this application document.
  • Each HARQ process has a corresponding buffer (for example, HARQ buffer or soft buffer) at the receiving end, so that the received data can be soft combined and decoded.
  • a corresponding buffer for example, HARQ buffer or soft buffer
  • the receiving end After the receiving end receives the newly transmitted data sent by the transmitting end using a HARQ process, it can put the received newly transmitted data into a buffer (for example, HARQ buffer or soft buffer) corresponding to the HARQ process for decoding. If the decoding fails, when the retransmitted data of the newly transmitted data is received again, the received retransmitted data and the newly transmitted data previously stored in the buffer can be combined, put into the buffer, and decoded again. This way can be Called soft combined decoding, compared to separate decoding (that is, each transmitted data is decoded separately, and is not combined with the previous data for decoding), which improves the probability of successful decoding. Similarly, if the decoding still fails, you can continue to repeat the above process, combine the newly received retransmitted data with the data in the buffer, and decode it again.
  • a buffer for example, HARQ buffer or soft buffer
  • the retransmitted data and the newly transmitted data of the sender may be the same redundancy version (redundancy version, RV) of the same TB or different RVs.
  • RV redundancy version
  • one CG resource is supported on one carrier.
  • a CG resource supports up to 16 HARQ processes.
  • the formula specified in the agreement can be used (for details, see 3GPP TS 38.321: "NR; Medium Access Control (MAC); Protocol specification”. Section 5.4.1) (this formula is called the default algorithm) 1)
  • the maximum range of the HARQ process ID is 0 to 15.
  • the terminal and network equipment can calculate the HARQ process ID corresponding to each uplink grant according to the preset algorithm 1.
  • the network device can indicate the HARQ process ID associated with each uplink grant to the terminal in the DCI.
  • the starting system frame number (SFN) of a UL CG resource is 5, and the starting time slot is time slot 1.
  • the initial symbol is symbol 4
  • an uplink authorization occupies 6 symbols, and the period is 1 time slot.
  • the number of HARQ processes available for this CG resource is 16. Calculations based on the preset algorithm 1 can get the HARQ associated with each uplink authorization. Process ID, see Figure 4 for details.
  • the HARQ process ID associated with each side authorization can be calculated by the following method C or method D (the HARQ process in the following content refers to the SL HARQ process, HARQ process ID refers to SL HARQ process ID).
  • a formula similar to the preset algorithm 1 can be used to calculate the HARQ process ID associated with each side row authorization in the CG resource.
  • the HARQ process ID associated with the side authorization on different CG resources may overlap.
  • the HARQ process ID associated with each side authorization in the resources of the first mode of the SL may be indicated to the terminal by the network device or calculated by the terminal according to a preset rule (for example, the foregoing preset algorithm 1).
  • the HARQ process ID associated with each side authorization in the resources of the second mode of SL may be determined by the terminal. Therefore, the resources of the first mode of the SL and the HARQ process IDs associated with the side authorization in the resources of the second mode of the SL may overlap.
  • the network device may determine the HARQ process ID, and indicate the HARQ process ID to the terminal through DCI.
  • the HARQ process ID may overlap with the HARQ process ID associated with other side authorizations.
  • Different resources may be different data.
  • the HARQ process IDs associated with the side-line authorizations are the same, which means that the receiving terminal may soft-combine different data, resulting in decoding errors.
  • the preset algorithm 2 is used to calculate the HARQ process ID associated with the side-line authorization on different CG resources.
  • the preset algorithm 2 can be to add an offset value (offset) on the basis of the preset algorithm 1, and the network device can configure the number of HARQ processes and the offset available for each CG resource, so as to enable the side authorization on different CG resources
  • the associated HARQ process ID is different.
  • the purpose of method D is to ensure that different resources (for example, different CG resources, or resources in the first mode and resources in the second mode, or DG resources and CG resources) have different side authorization associations.
  • HARQ process ID If the HARQ process ID available on all resources ranges from 0 to M-1.
  • N the maximum number of HARQ processes supported by the terminal on a carrier
  • the terminal can select N HARQ process IDs from M HARQ process IDs to simultaneously transmit data.
  • the maximum number of HARQ processes supported by the terminal on one carrier can be understood as the maximum number of HARQ processes supported by the terminal at the same time on one carrier.
  • the method D which calculates the HARQ process ID, has the following problems.
  • the sending terminal may carry the HARQ process ID corresponding to the HARQ process adopted by the sending terminal in the SL control information (sidelink control information, SCI) that schedules the data.
  • SCI sidelink control information
  • the network device configures 8 CG resources for the terminal, the number of HARQ processes supported by each CG resource is 2, and the terminal allocates 16 HARQ processes for the resources of the second mode of SL, then the terminal
  • the HARQ process ID ranges from 0 to 31.
  • the HARQ process ID in SCI needs to occupy 5 bits. If the HARQ process ID range of the terminal is larger, more bits need to be occupied, which will increase the burden of SCI transmission.
  • Question 2 specifically includes the following 3 issues related to retransmission.
  • the HARQ process used for the new transmission and retransmission of the same data needs to correspond to the same HARQ process ID, so that the receiving terminal can softly merge the newly transmitted and retransmitted data.
  • the new transmission and retransmission of the same data can only be performed on the side authorization associated with the same HARQ process ID in a CG resource, and the retransmission delay cannot be guaranteed.
  • the network device configures 7 CG resources for the terminal, the number of HARQ processes supported by each CG resource is 2, and the HARQ process ID corresponding to the CG resource is 0-13.
  • the network device also configures a DG resource for the terminal, and indicates that the HARQ process ID corresponding to the DG resource is 14.
  • the HARQ process ID corresponding to the resources of the second mode of SL is 16-31.
  • the small squares in Figures 5 to 8 and Figures 11 and 13 are side-line authorizations, and the number next to the small squares is the HARQ process ID corresponding to the side-line authorization.
  • the sending terminal transmits a new data to the receiving terminal in HARQ process 0, and the receiving terminal feeds back the NACK of HARQ process 0 to the sending terminal at T1, then the sending terminal also retransmits this data in HARQ process 0, and the side associated with HARQ process 0
  • the longer time interval between row authorizations will lead to longer retransmission delays.
  • the HARQ process IDs between the three CG resources should be shared, and new transmissions and retransmissions should also be shared.
  • the method of calculating the HARQ process ID according to the current method D cannot make the HARQ process ID sharing among the three CG resources.
  • the HARQ process ID associated with the DG resource is separate. Therefore, the data transmitted on the DG resource cannot be retransmitted.
  • the sending terminal can only request retransmission resources from the network device, and the time delay is relatively large.
  • the network device allocates 5 type1 CGs to the sending terminal, the number of HARQ processes supported by each type1 CG is 2, and also allocates 2 type2 CGs to the sending terminal, and each type2 CG supports HARQ The number of processes is 2. If the sending terminal can only use type2 CG to transmit data at this time, and cannot use type1 CG to transmit data, then the sending terminal can only use 4 HARQ processes (that is, HARQ process 10 to HARQ process 13) to transmit data at this time, which limits the sending terminal’s data transmission. The number of HARQ processes available at this moment reduces the efficiency of data transmission.
  • the data sent by the sending terminal in the HARQ process 10 will receive the ACK of the data at time T1.
  • the ACK of the data is received at time T2, so the two side authorizations circled in the figure (respectively associated with the HARQ process 10 and the HARQ process 11) cannot transmit data, resulting in a waste of resources.
  • the sending terminal supports up to 16 HARQ processes on a carrier
  • 16 HARQ processes after 16 HARQ processes are occupied, if the sending terminal receives HARQ feedback of data transmitted on a certain HARQ process, it can release the HARQ Process, transmit data on HARQ processes associated with other HARQ process IDs.
  • the sending terminal if the sending terminal receives an ACK of the data transmitted on HARQ process 0, the sending terminal releases the HARQ process associated with HARQ process 0 and starts HARQ process 13.
  • each HARQ process may be used for data transmission.
  • the sending terminal and the receiving terminal maintain a buffer (for example, HARQ buffer or soft buffer) for each HARQ process ID.
  • the buffer overhead is the buffer overhead of 32 HARQ processes.
  • the sending terminal receives the HARQ feedback of the data transmitted on a certain HARQ process, the sending terminal does not release the HARQ process, and can only continue with the previous HARQ process ID Data transmission is performed on the same HARQ process.
  • the terminal can only use 16 HARQ process IDs of the 32 HARQ process IDs for data transmission on the HARQ process, which means that the side authorization associated with the HARQ process IDs other than these 16 HARQ process IDs Cannot be used, resulting in a waste of resources.
  • an embodiment of the present application provides a communication method, as shown in FIG. 9, including:
  • the first terminal determines first HARQ information associated with the first side row authorization.
  • the first side line authorization is used to carry data between the first terminal and the second terminal.
  • the first terminal is the sending terminal of the two terminals
  • the second terminal is the receiving terminal of the two terminals.
  • the first side authorization is one of the SL transmission resources obtained by the first terminal.
  • the first side authorization belongs to the second resource, and the second resource includes any one or any of the following types of resources (at this time, it can be considered that only the side authorization in the second resource allows the first
  • the terminal determines the associated HARQ information for it):
  • the CG resource set of the SL, the CG resource set includes one or more CG resources corresponding to the CG resource index.
  • the second resource may include: SL resources in the second mode, or, the second resources may include: SL first-type CG resources and SL resources in the second mode, or, the second resources may include SL resources.
  • the type of resources included in the second resource may be configured by the network device to the first terminal, may also be determined by the first terminal itself, or may be pre-configured.
  • the method may further include: the network device generates configuration information for configuring the type of resource included in the second resource, and sends the configuration information to the first terminal Configuration information.
  • the terminal receives the configuration information from the network device, and determines the second resource according to the configuration information.
  • the second resource may be used for data transmission between the first terminal and other terminals (for example, the aforementioned second terminal).
  • the network device when the network device configures the type of resources included in the second resource for the first terminal, it may be for each logical channel (logical channel, LCH) or logical channel group (logical channel group, LCG). At this time, one LCH or LCG may correspond to a second resource, and when the data on the LCH or LCG is transmitted using the side authorization belonging to the second resource, the first terminal determines the associated HARQ information for the side authorization.
  • LCH logical channel
  • LCG logical channel group
  • the type of resource included in the second resource may be specified in the protocol, or stored in the first terminal by the device manufacturer before the first terminal leaves the factory, or The network device is pre-configured in the first terminal when the first terminal is connected to the network.
  • the first HARQ information includes any one or several of the following:
  • New data indication (new data indication, NDI) associated with the first side bank authorization, NDI is used to indicate whether the corresponding transmission is a new transmission or a retransmission.
  • MCS modulation and coding scheme
  • the first terminal may determine the first HARQ process ID associated with the first side row authorization by itself.
  • the first HARQ process ID and the second HARQ process ID may be the same or different.
  • the second HARQ process ID is the HARQ process ID determined by the first terminal for the first side line authorization according to the preset algorithm or the HARQ process ID indicated by the network device for the first side line authorization.
  • the first terminal may also use a preset algorithm to calculate the first HARQ process ID associated with the first side line authorization or the network device indicates to the first terminal the first HARQ process ID associated with the first side line authorization.
  • the first HARQ The process ID is the same as the above-mentioned second HARQ process ID.
  • the preset algorithm is the algorithm used by the network device to calculate the HARQ process ID associated with the side-line authorization, for example, the foregoing Preset Algorithm 1 or Preset Algorithm 2.
  • NDI may occupy 1 bit.
  • the new transmission may be identified by the inversion of the NDI, and the retransmission may be identified by the inversion of the NDI; or the retransmission may be identified by the inversion of the NDI, and the new transmission may be identified by the inversion of the NDI.
  • NDI is 1 to indicate new transmission, and NDI is 0 to indicate retransmission; or, NDI is 1 to indicate retransmission, and NDI is 0 to indicate new transmission.
  • the first terminal determines by itself the NDI associated with the first side authorization, that is, the first terminal determines by itself whether the first side authorization is used for new transmission or retransmission.
  • the first terminal determines the RV associated with the first side authorization, that is, the first terminal determines the RV of the data sent on the first side authorization.
  • the first terminal determines by itself the MCS associated with the first side authorization, that is, the first terminal determines by itself the MCS used for data transmission on the first side authorization.
  • the method further includes: the first terminal determines that there is data to be sent on the first side line authorization.
  • the first terminal determines that there is data to be sent on the first side row authorization.
  • the first terminal determines that there is data to be sent on the first side line authorization.
  • the first terminal determines that there is data to be sent on the first side authorization.
  • the first terminal sends the first HARQ information to the second terminal through the SL, where the SL is a wireless direct communication link between the first terminal and the second terminal.
  • the first HARQ information may be carried in the SCI or other messages.
  • the method further includes:
  • the first terminal uses the first side line authorization to send data to the second terminal.
  • the data may be scheduled by the aforementioned SCI carrying the first HARQ information.
  • the first terminal can determine the HARQ process ID associated with the side-line authorization by itself.
  • the first terminal can determine the HARQ process ID associated with the side-line authorization according to requirements without being affected by the network equipment. .
  • the first terminal determines the HARQ process ID associated with the side-line authorization on its own.
  • the terminal can associate different HARQ process IDs for different side authorizations, for example, for certain services or for data transmission of certain LCHs, if the sending terminal can only use type2CG resources to transmit data during a period of communication time , Type1CG resources cannot be used to transmit data.
  • the sending terminal supports up to N HARQ processes. During this communication time, all N HARQ processes can be used for transmission on type2CG resources. This ensures that at any time, no matter what type of resource the terminal is using for transmission, it can support N HARQ processes, which improves the transmission efficiency of the terminal.
  • the sending terminal can associate the sideline authorization associated with the HARQ process 10 circled in the figure with the HARQ process 10 before the HARQ process 10 circled in the figure.
  • the side row authorizes to associate different HARQ process IDs to avoid problem 4. The same is true for HARQ process 11.
  • the sending terminal and/or the receiving terminal maintains a buffer for each of the N HARQ process IDs, but the side authorization associated with the same HARQ process ID may belong to different SL transmission resources (for example, different CG resources). Therefore, Avoid the waste of cache resources and transmission resources.
  • this application adopts the following first method (the first terminal determines the HARQ process ID associated with the side line authorization by itself) and the second method (The first terminal uses a preset algorithm to calculate the HARQ process ID associated with the side-line authorization or the network device indicates the HARQ process ID associated with the side-line authorization for the first terminal)
  • the method for determining the HARQ process ID in this application is further explained, and The other technical solutions of this application under the first mode and the second mode are described in detail.
  • the first method the first terminal determines (or selects by itself) the HARQ process ID associated with the side-line authorization.
  • the first terminal to determine the HARQ process ID associated with the side-line authorization means that the first terminal independently determines the HARQ process ID associated with the side-line authorization, and is not affected by the network equipment. That is, the first terminal and the network device use different rules or algorithms to determine the HARQ process ID associated with the side-line authorization.
  • the first method can be applied to the following scenarios 1 to 4.
  • Scenario 1 The first side authorization preempts the second side authorization.
  • Scenario 1 may specifically include the following scenario 1.1 and scenario 1.2.
  • Scenario 1.1 The second HARQ process ID associated with the first side row authorization is the same as the seventh HARQ process ID associated with the second side row authorization.
  • the second HARQ process ID is the HARQ process ID associated with the first side authorization calculated by the first terminal using a preset algorithm or the HARQ process ID associated with the first side authorization indicated by the first terminal by the network device.
  • the seventh HARQ process ID is the HARQ process ID associated with the second side authorization calculated by the first terminal using a preset algorithm or the HARQ process ID associated with the second side authorization indicated by the first terminal by the network device.
  • the first side row is authorized as a DG resource
  • the second side row is authorized as a CG resource.
  • the HARQ process associated with the second side line authorization is still occupied, if the first terminal receives the information configuring the first side line authorization, and the second HARQ process ID associated with the first side line authorization and the second side line
  • the seventh HARQ process ID associated with authorization is the same, it can be considered that the first side authorization preempts the second side authorization.
  • Scenario 1.2 The first side line authorization and the second side line authorization overlap in the time domain.
  • the overlap here can be partial overlap or full overlap.
  • the first side row is authorized as DG resources, and the second side row is authorized as CG resources. If the first terminal receives the information for configuring the first side authorization, and the first side authorization and the second side authorization overlap in the time domain, it can be considered that the first side authorization preempts the second side authorization.
  • the first terminal receives information for configuring the first side row authorization on the PDCCH, and the DCI in the PDCCH is scrambled by a radio network temporary identity (RNTI).
  • RNTI radio network temporary identity
  • the first method can be specifically implemented by the following method 1 or method 2.
  • Manner 1 The first terminal determines the eighth HARQ process ID associated with the second side row authorization as the first HARQ process ID, that is, the eighth HARQ process ID is the same as the first HARQ process ID.
  • the eighth HARQ process ID is the HARQ process ID determined by the first terminal and associated with the second side line authorization.
  • the first terminal saves the corresponding relationship associated with the second side authorization, and the corresponding relationship is: the second side authorization and the first 8. Correspondence between the HARQ process ID, or the correspondence between the eighth HARQ process ID and the seventh HARQ process ID, or, the correspondence between the second side authorization, the eighth HARQ process ID and the seventh HARQ process ID relationship.
  • the first terminal may also perform the following step 11):
  • the first terminal updates the corresponding relationship associated with the second side line authorization to the corresponding relationship associated with the first side line authorization.
  • the correspondence relationship between the second side row authorization and the eighth HARQ process ID may be updated to: the correspondence relationship between the first side row authorization and the first HARQ process ID; or, the eighth HARQ process ID and the seventh HARQ process ID
  • the corresponding relationship between the process IDs is updated to: the corresponding relationship between the first HARQ process ID and the second HARQ process ID; or, the second side authorization, the eighth HARQ process ID and the seventh HARQ process ID
  • the corresponding relationship is updated as: the corresponding relationship between the first side row authorization, the first HARQ process ID, and the second HARQ process ID.
  • the update in the embodiment of the present application may specifically be to modify the original correspondence relationship to a new correspondence relationship or delete the original correspondence relationship and then save the new correspondence relationship.
  • the updated correspondence associated with the first side authorization may also include the first side authorization Information about the resource to which it belongs.
  • the resource to which a side authorization (for example, the second side authorization or the first side authorization) belongs in the embodiment of the present application is one of the following:
  • the CG resource set of the SL, the CG resource set includes one or more CG resources corresponding to the CG resource index.
  • different side authorizations can belong to different resources.
  • the corresponding relationship with the second side authorization may be: CG1+second side authorization
  • the eighth HARQ process ID The updated corresponding relationship with the first-side authorization can be: CG2+first-side authorization ID of the first HARQ process, or CG2+ID of the second HARQ process ID of the first HARQ process, or CG2+first side line authorization+ID of the second HARQ process ID of the first HARQ process.
  • Manner 2 The first terminal determines the identifier of an unoccupied HARQ process as the first HARQ process ID.
  • the first terminal determines the identifier of an unoccupied HARQ process among the N HARQ processes as the first HARQ process ID.
  • the first terminal can no longer select the HARQ process ID for the first side line authorization.
  • N HARQ processes are the most HARQ processes supported by the first terminal on one carrier, and N is an integer greater than 0.
  • N may be 8, 16, or other values.
  • N may be 8, 16, or other values.
  • the first terminal supports a maximum of 16 HARQ processes on one carrier, for example, the HARQ processes associated with HARQ process 0 to HARQ process 2 and HARQ process 6 to HARQ process 15 are all occupied, then the first terminal One of HARQ process 3 to HARQ process 5 may be selected and determined as the first HARQ process ID.
  • the first terminal may select the smallest or largest ID value among HARQ process IDs corresponding to unoccupied HARQ processes as the first HARQ process ID.
  • the first HARQ process ID may be selected according to some other rules, and this application is not limited.
  • the first HARQ process ID is an integer greater than or equal to 0 and less than N, and N is the maximum number of HARQ processes supported by the first terminal on one carrier.
  • N is the maximum number of HARQ processes supported by the first terminal on one carrier.
  • one HARQ process being occupied includes any one or more of the following situations:
  • the data transmission associated with the HARQ process has not yet been completed or not completed.
  • a scenario is: without HARQ feedback, the first terminal uses the HARQ process to send data to other terminals, and the blindness has not yet been reached. The number of retransmissions or repetitions.
  • the first terminal does not receive the feedback of the HARQ process.
  • a scenario is: the first terminal uses the HARQ process to send data to other terminals, and the first terminal is still waiting to receive feedback from other terminals, or the first terminal One terminal did not receive feedback information at the time when other terminals gave feedback.
  • the first terminal receives the NACK of the HARQ process.
  • a scenario is: the first terminal uses the HARQ process to send data to other terminals, and the first terminal receives the NACK from the other terminals.
  • the first terminal does not receive the ACK of the HARQ process.
  • a scenario is: the first terminal uses the HARQ process to send data to other terminals, and the first terminal does not receive ACKs from other terminals, and may have received NACK , May not receive any feedback.
  • the first terminal does not feed back the ACK of the HARQ process to the network device.
  • the first terminal does not release the HARQ process.
  • the first terminal has not cleared the HARQ buffer corresponding to the HARQ process.
  • the first terminal saves or does not release the corresponding relationship associated with the HARQ process.
  • the corresponding relationship associated with a HARQ process refers to the corresponding relationship between the side authorization associated with the HARQ process and the HARQ process ID self-determined by the first terminal associated with the HARQ process, or with the The corresponding relationship between the HARQ process ID determined by the first terminal associated with the HARQ process and the HARQ process ID determined by the first terminal associated with the HARQ process according to a preset algorithm (or indicated by the network device for the first terminal), or , The side authorization associated with the HARQ process, the HARQ process ID determined by the first terminal associated with the HARQ process, and the first terminal associated with the HARQ process determined according to a preset algorithm (or the network device is the first terminal (Indicated) correspondence between HARQ process IDs.
  • an unoccupied HARQ process includes any one or more of the following situations:
  • the data transmission associated with the HARQ process is completed or ended.
  • a scenario is: without HARQ feedback, the first terminal uses the HARQ process to send data to other terminals, achieving blind retransmission or repetition The number of times.
  • the first terminal does not receive the feedback of the HARQ process.
  • a scenario is: the first terminal performs multicast communication with other terminals, and the HARQ feedback is NACK only (that is, the sending terminal sends data to the receiving terminal Later, if the receiving terminal correctly receives the data, the receiving terminal does not provide feedback. If the receiving terminal fails to receive the data, the receiving terminal feeds back NACK to the sending terminal.
  • the first terminal uses the HARQ process to send data to other terminals, The first terminal does not receive the feedback information at the time when other terminals perform feedback, and the first terminal considers that all other terminals have correctly received the data.
  • the first terminal receives the ACK of the HARQ process.
  • a scenario is: the first terminal uses the HARQ process to send data to other terminals, the first terminal receives ACKs from other terminals, and the first terminal considers other terminals The data was received correctly.
  • the first terminal receives the ACK of the HARQ process
  • the first terminal only receives the ACK of the HARQ process.
  • the first terminal uses the HARQ process to send data to other terminals, the first terminal only receives ACKs from other terminals, and the first terminal It is assumed that other terminals have received the data correctly.
  • the first terminal feeds back the ACK of the HARQ process to the network device.
  • a scenario is: the first terminal uses the HARQ process to send data to other terminals, and the first terminal determines that the data transmission corresponding to the HARQ process is successful (for example, receiving an ACK from another terminal, or not receiving an ACK from another terminal). After the NACK of the terminal), the ACK is fed back to the network device.
  • the data transmission associated with the HARQ process has reached the maximum transmission time or the maximum number of transmissions.
  • the first terminal releases the HARQ process.
  • the first terminal empties the HARQ buffer corresponding to the HARQ process.
  • the first terminal has not saved or released the corresponding relationship associated with the HARQ process. After the first terminal determines the first HARQ process ID in way 2, the first terminal may also perform the following step 21):
  • the first terminal saves the corresponding relationship associated with the first side line authorization (denoted as the first corresponding relationship).
  • the first correspondence may be: the correspondence between the first side authorization and the first HARQ process ID, the correspondence between the first HARQ process ID and the second HARQ process ID, or the first side authorization, the first HARQ process ID Correspondence between the process ID and the second HARQ process ID.
  • the first correspondence stored by the first terminal may include information about the resource to which the first side authorization belongs.
  • the first corresponding relationship may be: CG+first side authorization ID of the first HARQ process, or CG+ID of the second HARQ process The first HARQ process ID, or CG+first side line authorization+second HARQ process ID ID of the first HARQ process.
  • the first corresponding relationship may be: CG1 + the first side row authorization ID of the first HARQ process, or CG1+ID of the second HARQ process The first HARQ process ID, or CG1 + the first side line authorization + the second HARQ process ID ID of the first HARQ process.
  • the terminal can directly save the corresponding relationship associated with the side-line authorization, or it may meet one of the following conditions: After more than one, save the corresponding relationship associated with the side line authorization.
  • 1) HARQ feedback is turned on.
  • the first terminal determines by itself a HARQ process ID associated with a sideline authorization, and the first terminal uses the HARQ process ID to communicate with other terminals, and the first terminal receives
  • the NACK corresponding to the HARQ process ID is received from other terminals
  • the first terminal may need to request retransmission resources from the network device.
  • the first terminal needs to know the HARQ process ID that can be identified by the network device corresponding to the HARQ process ID. Only a terminal can use the HARQ process ID that can be identified by the network device to request retransmission resources, and at this time, it needs to save the corresponding relationship associated with the side line authorization.
  • the first terminal needs to request retransmission resources from the network device. For example, when the first terminal determines the HARQ process ID associated with a side-line authorization, and the first terminal uses the HARQ process ID to communicate with other terminals, and the first terminal receives the NACK corresponding to the HARQ process ID from other terminals, the first terminal A terminal may need to request retransmission resources from the network device. At this time, the first terminal needs to know the HARQ process ID that can be recognized by the network device corresponding to the HARQ process ID, so that the first terminal can use the HARQ process ID that can be recognized by the network device. When requesting retransmission of resources, the corresponding relationship associated with the authorization of the side line needs to be saved.
  • the first terminal needs to feed back the transmission status on the SL to the network device.
  • the first terminal determines the HARQ process ID associated with a side-line authorization, and the first terminal uses the HARQ process ID to communicate with other terminals, and the first terminal receives the NACK corresponding to the HARQ process ID from the other terminals, the first terminal It may be necessary to request retransmission resources from the network device.
  • the first terminal needs to know the HARQ process ID that can be recognized by the network device corresponding to the HARQ process ID, so that the first terminal can use the HARQ process ID recognized by the network device to inform the network
  • the transmission on the HARQ process of the device fails and may request retransmission resources from the network device, or when the first terminal receives the NACK corresponding to the HARQ process ID from other terminals, the first terminal may need to request retransmission from the network device Resource.
  • the first terminal needs to know the HARQ process ID that can be recognized by the network device corresponding to the HARQ process ID, so that the first terminal can use the HARQ process ID recognized by the network device to inform the network device that the HARQ process is successfully transmitted.
  • the first terminal can all store corresponding corresponding relationships, and the first terminal can store up to N corresponding relationships for N side-line authorizations.
  • the first terminal may also delete the above-mentioned corresponding relationship associated with the second side row authorization, release storage resources in time, and improve the utilization of storage resources.
  • the NDI in the first HARQ information indicates that the corresponding transmission is a new transmission.
  • the second HARQ process ID associated with the first side row authorization is the same as the eleventh HARQ process ID associated with the sixth side row authorization, and the HARQ process associated with the sixth side row authorization is not occupied.
  • the eleventh HARQ process ID is the HARQ process ID associated with the sixth side authorization calculated by the first terminal using a preset algorithm, or the HARQ process ID associated with the sixth side authorization indicated by the first terminal by the network device .
  • the first method can be specifically implemented through the above method 1 or 2.
  • the method after determining the first HARQ process ID according to Manner 1 or Manner 2 is similar to scenario 1, and only needs to understand the second side authorization in the corresponding method as the sixth side authorization, which will not be repeated.
  • Scenario 3 The data transmitted on the first side authorization is a retransmission of the data transmitted on the fifth side authorization.
  • the first method specifically includes: the first terminal determines the ninth HARQ process ID associated with the fifth side row authorization as the first HARQ process ID, that is, the ninth HARQ process ID is the same as the first HARQ process ID.
  • This possible implementation manner can ensure that the receiving terminal puts the new transmission and retransmission of the same data into the same buffer for processing, and ensures that the receiving terminal decodes the data correctly.
  • the ninth HARQ process ID is the HARQ process ID determined by the first terminal and associated with the fifth side authorization.
  • the fifth side authorization is associated with the ninth HARQ process ID, and the first terminal retransmits the data on the first side authorization 1 (for example, because the first terminal receives a NACK from the second terminal for data 1, or the first terminal performs a blind retransmission of the data 1, etc.), the first terminal authorizes the ninth HARQ process associated with the fifth side row
  • the ID is determined to be the first HARQ process ID.
  • the first terminal may store the corresponding relationship associated with the fifth side authorization, and the corresponding relationship may be: Correspondence between the five-side authorization and the ninth HARQ process ID, or the correspondence between the ninth HARQ process ID and the tenth HARQ process ID, or, the fifth-side authorization, the ninth HARQ process ID and the tenth HARQ Correspondence between process IDs.
  • the tenth HARQ process ID is the HARQ process ID associated with the fifth side authorization calculated by the first terminal using a preset algorithm or the HARQ process ID associated with the fifth side authorization indicated by the first terminal by the network device.
  • the first terminal may also perform the following step 31):
  • the first terminal updates the corresponding relationship associated with the fifth side row authorization to the corresponding relationship associated with the first side row authorization.
  • the correspondence relationship between the fifth side row authorization and the ninth HARQ process ID may be updated to: the correspondence relationship between the first side row authorization and the first HARQ process ID; or, the ninth HARQ process ID and the tenth HARQ process ID
  • the corresponding relationship between the process IDs is updated to: the corresponding relationship between the first HARQ process ID and the second HARQ process ID; or, the fifth side authorization, the ninth HARQ process ID and the tenth HARQ process ID
  • the corresponding relationship is updated as: the corresponding relationship between the first side row authorization, the first HARQ process ID, and the second HARQ process ID.
  • the updated correspondence associated with the first side authorization may also include the first side authorization Information about the resource to which it belongs. The details are similar to the update of the corresponding relationship associated with the authorization of the second side bank, which can be understood by referring to the above, and will not be repeated.
  • the NDI in the first HARQ information indicates that the corresponding transmission is a retransmission.
  • Scene 4 Other scenes except scene 1, scene 2, and scene 3.
  • the first way can be specifically implemented through way 2 above.
  • the first terminal saves the above-mentioned first corresponding relationship, and the process of saving the above-mentioned first corresponding relationship can be referred to the above, and will not be repeated here.
  • the second way the first terminal uses a preset algorithm to calculate the HARQ process ID associated with the side authorization or the network device indicates the HARQ process ID associated with the side authorization for the first terminal.
  • the second method can be applied to the above scenario 1, scenario 2, and scenario 3.
  • the first terminal can use a preset algorithm to calculate the first HARQ process ID or the network device associated with the first side line authorization as the first terminal Indicates the HARQ process ID associated with the first side line authorization.
  • the first terminal determines the first HARQ process ID in the first or second way, the following events 1 (the HARQ process corresponding to the first HARQ process ID ends) and event 2 (the first side authorization is on The transmitted data needs to be retransmitted) or event 3 (the fourth side bank authorizes to preempt the first side bank authorization).
  • events 1 the HARQ process corresponding to the first HARQ process ID ends
  • event 2 the first side authorization is on
  • event 3 the fourth side bank authorizes to preempt the first side bank authorization.
  • Event 1 The HARQ process corresponding to the first HARQ process ID ends
  • the end of the HARQ process corresponding to the first HARQ process ID includes any one or more of the following situations:
  • the first terminal does not receive the feedback of the HARQ process corresponding to the first HARQ process ID.
  • a scenario is: when the first terminal performs multicast communication with other terminals, and the HARQ feedback is NACK only (send After the terminal sends data to the receiving terminal, if the receiving terminal correctly receives the data, the receiving terminal does not feedback; if the receiving terminal fails to receive the data, the receiving terminal feeds back NACK to the sending terminal), the first terminal uses the HARQ process When sending data to other terminals, the first terminal does not receive the feedback information at the time when the other terminals give feedback, and the first terminal thinks that all other terminals have correctly received the data.
  • the first terminal receives the ACK of the HARQ process corresponding to the first HARQ process ID.
  • a scenario is: the first terminal uses the HARQ process to send data to other terminals, and the first terminal receives ACKs from other terminals , The first terminal thinks that other terminals have correctly received the data.
  • the first terminal only receives the ACK of the HARQ process corresponding to the first HARQ process ID.
  • the first terminal performs multicast communication with other terminals, and the HARQ feedback is ACK/ NACK (after the sending terminal sends data to the receiving terminal, if the receiving terminal correctly receives the data, the receiving terminal sends back an ACK to the sending terminal, if the receiving terminal fails to receive the data, the receiving terminal feeds back NACK to the sending terminal), the first The terminal uses the HARQ process to send data to other terminals. The first terminal only receives ACKs from other terminals, and the first terminal believes that all other terminals have correctly received the data.
  • the first terminal sends the ACK of the HARQ process corresponding to the first HARQ process ID to the network device; for example, a scenario is: the first terminal uses the HARQ process to send data to other terminals, and the first terminal determines that the HARQ process corresponds to After successful transmission (for example, receiving an ACK from another terminal, or not receiving a NACK from another terminal), the ACK is fed back to the network device.
  • the data transmission associated with the HARQ process corresponding to the first HARQ process ID reaches the maximum transmission time, for example, the timer expires.
  • the first terminal releases the HARQ process corresponding to the first HARQ process ID.
  • the first terminal clears the HARQ buffer corresponding to the HARQ process corresponding to the first HARQ process ID.
  • the data transmission associated with the HARQ process is completed or ended.
  • a scenario is: without HARQ feedback, the first terminal uses the HARQ process to send data to other terminals, achieving blind retransmission or repetition The number of times.
  • the situation where one side-line authorization preempts another side-line authorization is similar to the above-mentioned situation where the first side-line authorization preempts the second side-line authorization.
  • the relevant part above for understanding please refer to the relevant part above for understanding. No longer.
  • the method also includes:
  • the first terminal deletes the foregoing first correspondence relationship.
  • the first terminal may not delete the above-mentioned first corresponding relationship.
  • the first corresponding relationship associated with the first HARQ process ID needs to be saved or updated subsequently, the first corresponding relationship is updated on the basis of the first corresponding relationship. can.
  • Event 2 The data transmitted on the first side authorization needs to be retransmitted.
  • the method further includes the following steps 51) to 53):
  • the first terminal obtains the third side authorization for data retransmission.
  • the method further includes:
  • the first terminal receives a NACK from the second terminal for the HARQ process associated with the first HARQ process ID. That is to say, the first terminal obtains the third side authorization for retransmitting the data when it is determined that the data is not successfully transmitted.
  • the first terminal retransmits the data transmitted on the first side authorization (for example, blind retransmission, repetition), and the first terminal obtains the third side authorization for retransmitting the foregoing data.
  • the first side authorization for example, blind retransmission, repetition
  • the first terminal determines the first HARQ process ID as the HARQ process ID associated with the third side line authorization.
  • the first terminal sends second HARQ information to the second terminal.
  • the second HARQ information includes: the first HARQ process ID associated with the third side line authorization.
  • the second HARQ information further includes: one or more of NDI information, RV, and MCS.
  • the NDI information is used to indicate that the corresponding transmission is a retransmission.
  • the functions and determination methods of RV and MCS are similar to the information in the first HARQ information. The difference is only that the third side authorization is targeted here. For details, please refer to the above for understanding, and will not be repeated.
  • step 51) to step 53) can be an independent solution.
  • step 51) to step 53 can be an independent solution.
  • step 51) to step 53) can solve the above-mentioned problem 2.
  • the data transmitted on the side row authorization in a CG resource can be retransmitted using the side row authorization in the CG resource.
  • the data transmitted on the side-line authorization of CG can also be retransmitted using the side-line authorization in another CG resource, so that the retransmission delay can be guaranteed.
  • the HARQ process ID can also be shared between different CG resources.
  • the data transmitted on the DG resource can also be retransmitted using the side row authorization in the CG resource.
  • step 53 the method further includes the following step 54):
  • the first terminal uses the third side authorization to retransmit the above data to the second terminal.
  • the method further includes:
  • the first terminal updates the foregoing first correspondence relationship to a correspondence relationship associated with the third side row authorization.
  • the first correspondence is the correspondence between the first side authorization and the first HARQ process ID
  • the first correspondence is updated to: the correspondence between the third side authorization and the first HARQ process ID.
  • the first correspondence is the correspondence between the first HARQ process ID and the second HARQ process ID
  • the first correspondence is updated to: the correspondence between the first HARQ process ID and the fourth HARQ process ID.
  • the first correspondence is the correspondence between the first side authorization, the first HARQ process ID, and the second HARQ process ID
  • the first correspondence is updated to: the third side authorization, the first HARQ process ID, and Correspondence between the fourth HARQ process IDs.
  • the fourth HARQ process ID is the HARQ process ID determined by the first terminal according to the preset algorithm for the third side authorization or the network device is the HARQ process ID indicated by the third side authorization.
  • the second HARQ process ID associated with the first side line authorization is the same or different from the fourth HARQ process ID associated with the third side line authorization.
  • the updated correspondence with the third side authorization may also include the information of the resource to which the third side authorization belongs.
  • the details are similar to the update of the corresponding relationship associated with the authorization of the second side bank, which can be understood by referring to the above, and will not be repeated.
  • the method further includes:
  • the first terminal saves the corresponding relationship associated with the third side line authorization (denoted as the second corresponding relationship).
  • the second correspondence is: the correspondence between the third side authorization and the first HARQ process ID, or the correspondence between the first HARQ process ID and the fourth HARQ process ID, or the third side authorization, the first Correspondence between the HARQ process ID and the fourth HARQ process ID.
  • the second correspondence stored by the first terminal includes the information of the resource to which the third side row authorization belongs, which is specifically similar to when the first correspondence is stored, and can be understood by referring to the above, and will not be repeated.
  • step 51) can be implemented in the following manner (1) or manner (2) or manner (3) in specific implementation.
  • the specific method used may be configured by the network device for the first terminal, or may be determined by the first terminal itself.
  • Manner (1) The first terminal determines the third side authorization for retransmitting data.
  • the manner (1) specifically includes: the first terminal selects a third side row authorization for retransmitting data from the first resource.
  • the first resource includes any one or several types of resources in the following:
  • the CG resource set of the SL, the CG resource set includes one or more CG resources corresponding to the CG resource index.
  • the first resource may include: SL resources in the second mode, or, the first resources may include: SL second-type CG resources and SL resources in the second mode, or, the first resources may include SL resources.
  • the type of the resource included in the first resource may be configured by the network device for the first terminal, or may be determined by the first terminal itself. If it is the former, the method further includes: the network device generates configuration information and sends the configuration information to the first terminal, where the configuration information is used to configure the type of resource included in the first resource.
  • the terminal receives configuration information from the network device, determines the type of resource included in the first resource according to the configuration information, and then determines the first resource according to the SL transmission resource previously configured for the first terminal by the network device, and determines the first resource in the first resource Third side authorization for retransmission of data.
  • the configuration information is the value of the resource included in the first resource configured by the first terminal.
  • the type is: the first type of CG resource of the SL
  • the first terminal determines the third side authorization for retransmitting the data in the first type of CG resource of the SL configured by the network device for the first terminal.
  • the network device may configure the type of resource included in the first resource for each LCH or LCG.
  • the first terminal can select the retransmission resource for the first side row authorization in the first resource.
  • the type of the resource included in the first resource configured for the LCH may be type1CG.
  • the type of resources included in the first resource configured for the LCG may be a CG resource set (for example, CG resource set 1).
  • the network device may also configure the type of resource included in the first resource for each type of resource included in the second resource.
  • the type of resources included in the second resource may be a CG resource set
  • the type of resources included in the first resource may also be a CG resource set
  • the two CG resource sets may be the same or different.
  • the CG resource set can be configured for a certain service.
  • the second resource may be a type2CG resource
  • the first resource may be a type2CG resource and a DG resource.
  • the first terminal may determine the third side authorization for retransmission of the data from the type2CG resource and the DG resource.
  • the network device may not configure the type of resource included in the first resource for any parameter, and directly configure a certain resource type or resource types for the first terminal.
  • the certain resource type or resource types indicate The side authorizations in the resource set (for example, a CG resource set, or a resource set composed of multiple types of resources) can share the HARQ process ID or can be used for retransmission with each other.
  • the first resource and the second resource are the same resource, that is, the first resource and the second resource are both resource sets indicated by the one or several resource types.
  • some other conditions can also be configured for the first terminal.
  • the Type1CG resource since the Type1CG resource is used in an emergency, it can be configured whether the DG resource and/or the transmission on the Type2CG resource can use the type1CG resource for retransmission.
  • the transmission on DG resources and/or Type2CG resources can use type1CG resources for retransmission it can be pre-configured, configured by network equipment, or defined by the protocol.
  • the configuration can be for each LCH or each LCG or each second resource is configured. For another example, you can configure whether the resources of mode1 and mode2 can use each other's resources as retransmission resources.
  • the resources of mode1 and mode2 can use each other's resources as retransmission resources, it can be pre-configured, configured by the network device, or defined by the protocol.
  • the configuration can also be for each LCH or each LCG or each As a second resource.
  • method (1) when the first terminal selects the third side line authorization, any one or more of the following factors may be considered:
  • the size of the side-line authorization for example, judge whether to consider the side-line authorization as the third-line authorization based on whether the side-line authorization can accommodate the data transmitted on the first-line authorization, if the side-line authorization can accommodate the first
  • the data transmitted on the side authorization that is, the data transmitted on the first side authorization can be retransmitted using the side authorization, and the side authorization can be considered as the third side authorization.
  • the priority of the data transmitted on the side line authorization and the priority of the data transmitted on the first side line authorization for example, according to the priority of the data to be transmitted on the side line authorization and the data transmitted on the first side line authorization
  • the priority comparison of the side row authorization is judged whether to consider the side row authorization as the third side row authorization. If the priority of the data to be transmitted on the side row authorization is lower than the priority of the data transmitted on the first side row authorization, it can be considered Use this side authorization as the third side authorization.
  • the priority includes the quality of service (QoS) information, or the short-range packet granularity priority (PPPP) value, or the priority of the logical channel in the MAC PDU, or the MAC The priority of the highest priority logical channel in the PDU, etc.
  • QoS quality of service
  • PPPP short-range packet granularity priority
  • the comparison when comparing the priorities of logical channels, the comparison may be performed according to the priorities of the logical channels where the two data are located, or the comparison may be performed according to the priorities of the logical channels with the highest priority where the two data are located.
  • the time interval between the side authorization and the first side authorization determine whether to consider the side authorization as the third side authorization If the time interval between the side authorization and the first side authorization is short (for example, less than the first threshold), the side authorization can be considered as the third side authorization.
  • the first threshold may be pre-configured, or configured by the network device for the first terminal, or specified by the communication protocol, or determined by the network device according to certain rules and notified to the first terminal, or
  • the first terminal is defined when it leaves the factory, which is not specifically limited in this application.
  • the first terminal may determine the side authorization with the shortest time interval with the first side authorization, no data transmission on the side authorization, and capable of accommodating the data transmitted on the first side authorization as the third side.
  • Line authorization For another example, the first terminal may minimize the time interval with the first side-line authorization, the priority of the data to be transmitted on the side-line authorization is lower than the priority of the data transmitted on the first side-line authorization, and can The side authorization that accommodates the data transmitted on the first side authorization is determined to be the third side authorization.
  • the retransmission of the data transmitted on the first side authorization preempts the newly transmitted data originally authorized on the third side.
  • the first terminal can request retransmission resources for the newly transmitted data originally to be authorized on the third side, or continue to use the newly transmitted data as the amount of newly transmitted data to be transmitted.
  • the terminal sends the newly transmitted data to the network.
  • the reported buffer status report (BSR) contains the size of the newly transmitted data to be transmitted.
  • a CG resource or a CG resource set can be set for a CG resource or a set of CG resources.
  • this ratio threshold or number of times threshold is exceeded, the CG resource or the CG resource set can no longer be used for retransmission, so that the retransmission of high-priority services does not always preempt the new transmission of low-priority services.
  • the ratio threshold or the frequency threshold may be pre-configured, or configured by the network device for the first terminal, or specified by the communication protocol, or determined by the network device according to certain rules and notified to the first terminal, Or it is defined by the first terminal when it leaves the factory, which is not specifically limited by this application.
  • Manner (2) The first terminal requests the third side authorization from the network device.
  • Mode (2) may include the following steps 81) and step 82) in specific implementation:
  • the first terminal sends a request message to the network device.
  • the request message is used to request a retransmission resource from the network device.
  • the retransmission resource is used to retransmit the data authorized to be transmitted on the first side.
  • the request message includes the second HARQ process ID. And/or the information of the resource to which the first side authorization belongs, or the resource of the transmission request message is associated with the second HARQ process ID and/or the resource to which the first side authorization belongs.
  • the network device receives the request message from the first terminal.
  • the first terminal may determine the second HARQ process ID associated with the first side authorization and/or the information of the resource to which the first side authorization belongs according to the corresponding relationship associated with the first side authorization.
  • the network device sends a request response to the first terminal according to the request message, and the request response includes the third side authorization information for retransmitting the data transmitted on the first side authorization.
  • the first terminal receives the request response from the network device, and determines the third side line authorization according to the request response.
  • Method (3) The network device configures the third side authorization for the first terminal to retransmit the above-mentioned data by itself.
  • method (3) may specifically include: the network device starts a first timer associated with the second HARQ process ID of the first terminal or the first side authorization, and if the first timer expires, if the network When the device does not receive the ACK for the side row data transmitted by the first HARQ process, the network device sends resource indication information to the first terminal.
  • the resource indication information is used to indicate the retransmission of the SL transmission of the failed data on the first side row authorization.
  • Resources for example, third-party authorization).
  • the network device may be the first terminal or each HARQ process of the first terminal or each HARQ process ID of the first terminal or each side authorization of the first terminal or a bundle of the first terminal. Each side line within is authorized to maintain a timer.
  • the network device receives the transmission feedback (for example, ACK or NACK) corresponding to the timer, the network device restarts or starts the timer. If the timer expires, the network device has not received the transmission feedback (for example, ACK) corresponding to the timer sent by the first terminal, and the network device sends a retransmission resource to the first terminal and restarts the timer.
  • the transmission feedback for example, ACK or NACK
  • the duration of the timer depends on the time from when the sending terminal sends data to when the receiving terminal receives the data, the time when the receiving terminal feeds back to the sending terminal, and the time when the sending terminal feeds back to the network device.
  • the timer is greater than or equal to "the time from the sending terminal sending data to the receiving terminal receiving the data + the receiving terminal feedback time to the sending terminal + the sending terminal feedback time to the network device.
  • Manner (3) can be implemented as an independent solution.
  • the side authorization acquisition method used for multiple retransmissions can be the same (for example, all are acquired through the above method (1) or method (2) or method (3)) , Can also be different (for example, one part is obtained through the above-mentioned method (1), and the other part is obtained through the above-mentioned method (2)), and this application is not limited.
  • Event 3 The fourth side authorization preempts the first side authorization
  • the method may also include:
  • the first terminal determines the third HARQ information associated with the fourth side authorization, and the third HARQ information includes: the fifth HARQ process ID associated with the fourth side authorization.
  • the first terminal may determine the first HARQ process ID as the fifth HARQ process ID associated with the fourth side authorization.
  • the method may further include: the first terminal updates the corresponding relationship associated with the first side row authorization to: the corresponding relationship between the fourth side row authorization and the fifth HARQ process ID; or, The correspondence between the fifth HARQ process ID and the sixth HARQ process ID; or the correspondence between the fourth side authorization, the fifth HARQ process ID and the sixth HARQ process ID.
  • the sixth HARQ process ID is the HARQ process ID determined by the first terminal for the fourth side authorization according to the preset algorithm or the HARQ process ID indicated by the network device as the fourth side authorization.
  • the updated correspondence relationship may also include the information of the resource to which the fourth side authorization belongs.
  • the updated correspondence relationship may also include the information of the resource to which the fourth side authorization belongs.
  • the first terminal may determine the fifth HARQ process ID associated with the fourth side row authorization in a manner similar to the foregoing manner 2.
  • the method further includes: the first terminal saves the corresponding relationship (denoted as the third corresponding relationship) associated with the fourth side line authorization, and the third corresponding relationship is: the fourth side line authorization and Correspondence between the fifth HARQ process ID; or between the fifth HARQ process ID and the sixth HARQ process ID; or, between the fourth side authorization, the fifth HARQ process ID and the sixth HARQ process ID Correspondence.
  • the saved correspondence relationship may also include the information of the resource to which the fourth side authorization belongs.
  • the saved correspondence relationship may also include the information of the resource to which the fourth side authorization belongs.
  • the first terminal deletes the corresponding relationship associated with the first side row authorization (for example, the foregoing first corresponding relationship).
  • the first terminal may use a preset algorithm to determine the fifth HARQ process ID associated with the fourth side authorization or the network device indicates the fifth HARQ associated with the fourth side authorization for the first terminal Process ID.
  • step 91 in the process of determining the third HARQ information associated with the fourth side authorization, in the scenario of preempting the second side authorization with the first side authorization, determine the first side authorization associated with the first side authorization.
  • the process of a HARQ information is similar, which can be understood by referring to the above, and will not be repeated.
  • the corresponding relationship may include the HARQ process ID associated with the side-line authorization that the first terminal can determine by itself. It may also be the HARQ information associated with the side-line authorization determined by the first terminal.
  • the above example provides the HARQ process ID associated with the side-line authorization determined by the first terminal in the corresponding relationship as an example. The method is illustrated as an example, but it is understandable that the HARQ process ID determined by the first terminal and associated with the side-line authorization included in the above corresponding relationship can also be replaced with the side-line authorization determined by the first terminal.
  • the associated HARQ information for example, the first HARQ process ID in the above-mentioned first correspondence can also be replaced with the first HARQ information.
  • the HARQ process ID determined by the first terminal for the side-line authorization according to the preset algorithm or the HARQ process ID indicated by the network device for the side-line authorization can be replaced with the HARQ process ID determined by the first terminal for the side-line authorization according to the preset algorithm HARQ information or HARQ information indicated by the network device for the side-line authorization.
  • the second HARQ process ID in the first correspondence can also be replaced with the HARQ information determined by the first terminal according to the preset algorithm for the first side-line authorization.
  • the network device is the HARQ information indicated by the first side line authorization.
  • the HARQ information associated with each side authorization may include one or more of the HARQ process ID, NDI, RV, and MCS.
  • the above-mentioned corresponding relationship may be maintained (for example, saved, updated, deleted) by the MAC entity, HARQ entity, and HARQ process of the first terminal.
  • the first HARQ information determined by the first terminal to be associated with the first side row authorization may be determined by the MAC entity, HARQ entity, and HARQ process of the first terminal.
  • the first terminal determines that the first side row authorization in the type 1CG5 resource needs to send data.
  • the small box in Figure 11 represents the side-line authorization
  • the number on the right of the small box is the HARQ process ID (pre) corresponding to the side-line authorization
  • the above number is the HARQ process ID (final) corresponding to the side-line authorization
  • “HARQ process ID (pre) represents the HARQ process ID determined by the first terminal according to a preset algorithm
  • HARQ process ID (end)” represents the HARQ process ID determined by the terminal itself.
  • the corresponding relationship stored in the first terminal may refer to (a) in FIG. 12.
  • the first terminal determines whether the number of HARQ processes currently being occupied is less than 16.
  • step 1003 If yes, go to step 1003, if no, end.
  • the number of HARQ processes currently being occupied is 4, that is, HARQ processes associated with HARQ process 0, HARQ process 1, HARQ process 2, and HARQ process 3 are occupied.
  • the first terminal selects the HARQ process ID corresponding to one HARQ process from among the unoccupied HARQ processes among the 16 HARQ processes as the HARQ process ID associated with the first side authorization.
  • the first terminal may select HARQ process 4 from HARQ process 4 to HARQ process 15 as the HARQ process ID associated with the first side row authorization.
  • the first terminal stores the corresponding relationship between the HARQ process ID (pre) and the HARQ process ID (end) associated with the first side authorization.
  • step 1004 the corresponding relationship stored in the first terminal is shown in (b) in FIG. 12.
  • the first terminal sends the HARQ information associated with the first side authorization to the second terminal, where the HARQ information includes the HARQ process ID (end), and sends data to the second terminal on the first side authorization.
  • the first terminal receives HARQ feedback for the HARQ process ID (end) associated with the first side authorization.
  • step 1007 is executed; if the HARQ feedback is NACK (for example, based on the example shown in FIG. 11, see FIG. 13, NACK is received at T1), step 1008 is executed.
  • the first terminal deletes the corresponding relationship between the HARQ process ID (pre) and the HARQ process ID (end) associated with the first side authorization.
  • FIG. 14 Exemplarily, based on the example shown in FIG. 12, reference may be made to FIG. 14 for deletion of the corresponding relationship.
  • the first terminal obtains a resource for retransmitting the foregoing data (recorded as a retransmission side authorization).
  • the first terminal may determine that the second side authorization in the type 1CG5 resource is the retransmission side authorization.
  • the first terminal determines the HARQ process ID associated with the retransmission side authorization as the HARQ process ID associated with the first side authorization (end).
  • the HARQ process ID (end) associated with the retransmission side authorization is HARQ process 4 (end).
  • the first terminal updates the corresponding relationship between the HARQ process ID (pre) and the HARQ process ID (end) associated with the first side authorization to the HARQ process ID (pre) and the HARQ process ID (pre) associated with the retransmission side authorization. Correspondence between HARQ process ID (end).
  • the first terminal sends the HARQ information associated with the retransmission side authorization to the second terminal, where the HARQ information includes the HARQ process ID (end) associated with the retransmission side authorization, and sends the HARQ information to the second terminal on the retransmission side authorization.
  • the second terminal retransmits the data.
  • one receiving terminal can communicate with multiple different sending terminals.
  • the data sent by the sending terminal is scheduled by the SCI, and the sending terminal informs the receiving terminal of the HARQ process ID used when sending the data through the HARQ process ID carried in the SCI. Different sending terminals may use the same HARQ process ID to communicate with the receiving terminal.
  • the HARQ process IDs in the SCI sent by different sending terminals are all the same. Since the receiving terminal thinks that the data transmitted on the same HARQ process ID corresponds to the same data (for example, the new transmission and retransmission of the same data), it is possible that different sending terminals use the same HARQ process ID to send data Putting them in the same HARQ buffer or soft buffer for soft combining and decoding will cause decoding errors.
  • an embodiment of the present application also provides a communication method, referring to FIG. 10A, which includes:
  • the receiving terminal receives the SCI.
  • the receiving terminal may receive the SCI from the transmitting terminal.
  • the SCI includes HARQ process ID, NDI, RV, source identifier (for example, Layer-1 source ID), and destination identifier (for example, Layer-1 destination ID) One or more of.
  • the source identifier may be used to identify a sending terminal of unicast or multicast or broadcast communication.
  • the destination identifier can be used to identify a receiving terminal of unicast or multicast or broadcast communication.
  • a unicast communication can be identified by the source ID and the destination ID (in this case, the source ID can be the ID of the sending terminal, and the destination ID can be the ID of the receiving terminal) or multicast communication (in this case, the source ID can be To send the terminal identifier, the destination identifier may be a group identifier, and the receiving terminal is all terminals in the group).
  • a broadcast communication may be identified by a destination identifier.
  • the destination identifier may be a broadcast service identifier.
  • the receiving terminals are all terminals that receive the broadcast service data.
  • the receiving terminal selects the HARQ process for the received SCI.
  • the receiving terminal can select a HARQ process to receive the SCI-scheduled data (for example, the new transmission and retransmission of the SCI-scheduled data are placed in the HARQ buffer or soft buffer corresponding to the HARQ process Decode after soft merging in).
  • the HARQ process used by the sending terminal to send data can be called the sending HARQ process.
  • the identification of the sending HARQ process can be called the sending HARQ process ID
  • the HARQ process used by the receiving terminal to receive data can be called the receiving The HARQ process, correspondingly, the identifier of the receiving HARQ process may be referred to as the receiving HARQ process ID.
  • the receiving terminal may select a HARQ process from the unoccupied HARQ process to receive the data scheduled by the SCI.
  • the HARQ process not occupied by the receiving terminal may include any one or several of the following situations:
  • the receiving terminal has not fed back the ACK corresponding to the HARQ process to the sending terminal.
  • the receiving terminal feeds back the NACK corresponding to the process to the sending terminal.
  • the receiving terminal has not yet fed back the feedback corresponding to the HARQ process to the sending terminal. For example, the receiving terminal failed to feed back to the sending terminal due to conflicts with other transmissions at the timing of the feedback to the sending terminal.
  • the number of times the receiving terminal receives the data associated with the HARQ process does not reach the maximum number of transmissions, for example, the number of times the receiving terminal receives one TB does not reach the maximum number of transmissions.
  • the receiving terminal does not receive the instruction for the last data transmission.
  • the transmission of the HARQ process has not reached the maximum transmission time, for example, the timer corresponding to the HARQ process has not expired. 1003A.
  • the receiving terminal saves the corresponding relationship associated with the received SCI.
  • the receiving terminal can store any one of the following correspondences:
  • the communication type (cast-type), the HARQ process ID in the SCI, the source identifier in the SCI, the destination identifier in the SCI, and the receiving HARQ process (for example, the receiving HARQ process ID).
  • the purpose identifiers used in unicast communication and multicast communication may be the same. This correspondence relationship can further distinguish the communication types.
  • the communication types include any of the following One or several types: unicast, multicast, broadcast.
  • the receiving terminal can find the corresponding HARQ process to process the received retransmitted data when receiving the retransmission of the data.
  • the sending terminal 1 uses the sending HARQ process 1 to send data 1 to the receiving terminal
  • the sending terminal 2 also uses the sending HARQ process 1 to send data 2 to the receiving terminal
  • the receiving terminal can use the receiving HARQ process 2 to receive the sending terminal.
  • the data 1 sent by the receiving HARQ process 3 is used to receive the data 2 sent by the sending terminal 2, then if the receiving terminal again receives the retransmission of the data 1 sent by the sending terminal 1 to the receiving terminal using the HARQ process 1, the receiving terminal uses the receiving terminal.
  • the HARQ process 2 receives the retransmission of the data 1 sent by the sending terminal 1, and performs soft-combination and decoding on the retransmission of the data 1 and the data 1.
  • the receiving terminal may delete the foregoing corresponding relationship when any one or several of the following conditions are met.
  • the receiving terminal successfully decodes the data corresponding to the HARQ process.
  • the receiving terminal transmits the decoded MAC PDU to the disassembly and demultiplexing entity.
  • the receiving terminal feeds back ACK to the sending terminal.
  • the receiving terminal does not feed back NACK to the sending terminal.
  • the number of times the receiving terminal receives the data associated with the HARQ process reaches the maximum number of transmissions, for example, the number of times the receiving terminal receives one TB reaches the maximum number of transmissions.
  • the receiving terminal receives an indication for indicating the last data transmission.
  • the receiving terminal receives an SCI, and the SCI contains an indication for indicating the last data transmission.
  • the indication is used to indicate that the transmission on the HARQ process is The last transmission.
  • the transmission of the HARQ process reaches the maximum transmission time, for example, the timer corresponding to the HARQ process times out.
  • the receiving terminal receives an SCI
  • the information contained in the SCI and the information in the stored correspondence are all the same, and the data scheduled by the SCI is newly transmitted data (for example, the NDI in the SCI indicates the information scheduled by the SCI
  • the corresponding relationship associated with the SCI may not be deleted, and the corresponding relationship may be directly used to receive the data scheduled by the SCI, or the corresponding relationship associated with the SCI may be deleted, and in the unoccupied HARQ process Select the HARQ process to receive the data scheduled by the SCI.
  • the embodiment of the present application provides a new method for clearing the cache.
  • the method includes:
  • the terminal determines that the uplink data transmission is complete.
  • step 1601 the terminal determines that the uplink data transmission is completed when the uplink data transmission reaches the maximum number of retransmissions, or the uplink data transmission reaches the maximum transmission time, or the configured grant timer (configuredGrantTimer) times out.
  • the configured grant timer ConfiguredGrantTimer
  • the terminal clears the HARQ buffer corresponding to the HARQ process used to transmit uplink data.
  • the method includes:
  • the terminal determines that the side-line data transmission is completed, and the side-line data transmission completion includes that the side-line data transmission is successful or the side-line data transmission reaches the maximum number of transmissions or the side-line data transmission reaches the maximum transmission time.
  • the terminal may maintain a HARQ buffer for each HARQ process.
  • the terminal clears the HARQ buffer corresponding to the HARQ process used to transmit side-line data.
  • the side-line data transmission is successful, including any one or several of the following situations:
  • the terminal does not receive the NACK for side-line data. For example, in a scenario where the first terminal performs multicast communication with other terminals, and the HARQ feedback is NACK only (after the sending terminal sends data to the receiving terminal If the receiving terminal correctly receives the data, the receiving terminal does not give feedback. If the receiving terminal fails to receive the data, the receiving terminal feeds back NACK to the sending terminal), the first terminal uses the HARQ process to send data to other terminals. A terminal does not receive the NACK at the time when the other terminals give feedback, and the first terminal thinks that all other terminals have correctly received the data.
  • the terminal receives an ACK for sideline data.
  • the first terminal uses the HARQ process to send data to other terminals, and the first terminal receives ACKs from other terminals, and the first terminal considers other terminals The data was received correctly
  • the terminal receives the ACK for the side-line data and does not receive the NACK for the side-line data.
  • the first terminal performs multicast communication with other terminals, and the HARQ feedback is ACK/NACK (After the sending terminal sends data to the receiving terminal, if the receiving terminal correctly receives the data, the receiving terminal feeds back an ACK to the sending terminal, and if the receiving terminal fails to receive the data, the receiving terminal feeds back NACK to the sending terminal), the first terminal Using the HARQ process to send data to other terminals, the first terminal only receives ACKs from other terminals, and the first terminal believes that other terminals have correctly received the data.
  • the methods shown in FIG. 16 and FIG. 17 can clear the HARQ buffer when the data transmission is completed, thereby saving buffer space.
  • each network element for example, a network device and a terminal, includes at least one of a hardware structure and a software module corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiment of the present application may divide the network device and the terminal into functional units according to the foregoing method examples.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 18 shows a schematic diagram of a possible structure of the communication device (denoted as the communication device 180) involved in the foregoing embodiment.
  • the communication device 180 includes a processing unit 1801 and a communication unit 1802.
  • a storage unit 1803 is further included.
  • the communication device 180 may be used to illustrate the structure of the terminal and the network device in the foregoing embodiment.
  • the processing unit 1801 is used to control and manage the actions of the terminal.
  • the processing unit 1801 is used to execute steps 901 to 901 in FIG. 9 903 (at this time, the terminal is the first terminal), 902 and 903 in Fig. 9 (at this time, the terminal is the second terminal), 1001 to 1011 in Fig. 10, 1001A to 1003A in Fig. 10A, and Fig. 16 1601 and 1602, 1701 and 1702 in FIG. 17, and/or actions performed by the terminal in other processes described in the embodiments of the present application.
  • the processing unit 1801 may communicate with other network entities through the communication unit 1802, for example, when the terminal is the first terminal, communicate with the second terminal in FIG. 9.
  • the storage unit 1803 is used to store program codes and data of the terminal.
  • the processing unit 1801 is used to control and manage the actions of the network device.
  • the processing unit 1801 is used to communicate with the network device through the communication unit 1802.
  • the first terminal sends configuration information used to configure the type of resource included in the first resource, and/or the action performed by the network device in other processes described in the embodiment of the present application.
  • the processing unit 1801 may communicate with other network entities through the communication unit 1802, for example, communicate with the first terminal.
  • the storage unit 1803 is used to store the program code and data of the network device.
  • the communication device 180 may be a device, a chip or a chip system.
  • the processing unit may be a processor; the communication unit may be a communication interface, a transceiver, or an input interface/output interface.
  • the transceiver may be a transceiver circuit.
  • the input interface/output interface may be an input circuit/output circuit.
  • the communication unit may be a communication interface, an input interface/output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit on the chip or a chip system.
  • the processing unit may be a processor, a processing circuit, a logic circuit, or the like.
  • the integrated unit in FIG. 18 is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the medium includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • Storage media for storing computer software products include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disks or optical disks, etc., which can store program codes Medium.
  • the embodiment of the present application also provides a schematic diagram of the hardware structure of a communication device (denoted as a communication device 190).
  • the communication device 190 includes a processor 1901, and optionally, a communication device connected to the processor 1901. ⁇ Memory 1902.
  • the processor 1901 can be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more programs for controlling the execution of the program of this application. integrated circuit.
  • the processor 1901 may also include multiple CPUs, and the processor 1901 may be a single-CPU processor or a multi-CPU processor.
  • the processor here may refer to one or more devices, circuits, or processing cores for processing data (for example, computer program instructions).
  • the memory 1902 may be a ROM or other types of static storage devices that can store static information and instructions, RAM, or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory).
  • read-only memory EEPROM
  • compact disc read-only memory, CD-ROM
  • optical disc storage including compact discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.
  • magnetic disks A storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, and the embodiment of the present application does not impose any limitation on this.
  • the memory 1902 may exist independently (at this time, the processor may be located outside the communication device, or may be located in the communication device), or may be integrated with the processor 1901. Wherein, the memory 1902 may contain computer program code.
  • the processor 1901 is configured to execute the computer program code stored in the memory 1902, so as to implement the method provided in the embodiment of the present application.
  • the communication device 190 further includes a transceiver 1903.
  • the processor 1901, the memory 1902, and the transceiver 1903 are connected by a bus.
  • the transceiver 1903 is used to communicate with other devices or communication networks.
  • the transceiver 1903 may include a transmitter and a receiver.
  • the device for implementing the receiving function in the transceiver 1903 can be regarded as a receiver, and the receiver is used to perform the receiving steps in the embodiment of the present application.
  • the device for implementing the sending function in the transceiver 1903 can be regarded as a transmitter, and the transmitter is used to perform the sending steps in the embodiment of the present application.
  • the schematic structural diagram shown in FIG. 19 may be used to illustrate the structure of the terminal and the network device in the foregoing embodiment involved in the foregoing embodiment.
  • the processor 1901 is used to control and manage the actions of the terminal.
  • the processor 1901 is used to execute steps 901 to 901 in FIG. 903 (at this time, the terminal is the first terminal), 902 and 903 in Fig. 9 (at this time, the terminal is the second terminal), 1001 to 1011 in Fig. 10, 1001A to 1003A in Fig. 10A, and Fig. 16 1601 and 1602, 1701 and 1702 in FIG. 17, and/or actions performed by the terminal in other processes described in the embodiments of the present application.
  • the processor 1901 may communicate with other network entities through the transceiver 1903, for example, when the terminal is the first terminal, it communicates with the second terminal in FIG. 9.
  • the memory 1902 is used to store program codes and data of the terminal.
  • the processor 1901 is used to control and manage the actions of the network device.
  • the processor 1901 is used to communicate to the network device through the transceiver 1903.
  • the first terminal sends configuration information used to configure the type of resources included in the first resource, and/or actions performed by the network device in other processes described in the embodiments of the present application.
  • the processor 1901 may communicate with other network entities through the transceiver 1903, for example, communicate with the first terminal.
  • the memory 1902 is used to store program codes and data of the network device.
  • the processor 1901 includes a logic circuit and at least one of an input interface and an output interface.
  • the output interface is used to execute the sending action in the corresponding method
  • the input interface is used to execute the receiving action in the corresponding method.
  • FIG. 20 The schematic structural diagram shown in FIG. 20 may be used to illustrate the structure of the terminal and the network device in the foregoing embodiment involved in the foregoing embodiment.
  • the processor 1901 is used to control and manage the actions of the terminal.
  • the processor 1901 is used to execute steps 901 to 901 in FIG. 9 903 (at this time, the terminal is the first terminal), 902 and 903 in Fig. 9 (at this time, the terminal is the second terminal), 1001 to 1011 in Fig. 10, 1001A to 1003A in Fig. 10A, and Fig. 16 1601 and 1602, 1701 and 1702 in FIG. 17, and/or actions performed by the terminal in other processes described in the embodiments of the present application.
  • the processor 1901 may communicate with other network entities through at least one of the input interface and the output interface, for example, when the terminal is the first terminal, it communicates with the second terminal in FIG. 9.
  • the memory 1902 is used to store program codes and data of the terminal.
  • the processor 1901 is used to control and manage the actions of the network device.
  • the processor 1901 is used to communicate with the network device through the transceiver 1903.
  • the first terminal sends configuration information used to configure the type of resource included in the first resource, and/or the action performed by the network device in other processes described in the embodiment of the present application.
  • the processor 1901 may communicate with other network entities through at least one of the input interface and the output interface, for example, communicate with the first terminal.
  • the memory 1902 is used to store program codes and data of the network device.
  • each step in the method provided in this embodiment can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the embodiment of the present application also provides a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to execute any of the above-mentioned methods.
  • the embodiments of the present application also provide a computer program product containing instructions, which when run on a computer, cause the computer to execute any of the above-mentioned methods.
  • An embodiment of the present application also provides a communication system, including: the foregoing multiple terminals (for example, a first terminal and a second terminal), or the foregoing terminal (for example, the first terminal) and a network device, or the foregoing multiple Terminal and network equipment.
  • a communication system including: the foregoing multiple terminals (for example, a first terminal and a second terminal), or the foregoing terminal (for example, the first terminal) and a network device, or the foregoing multiple Terminal and network equipment.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • a software program it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • Computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • computer instructions may be transmitted from a website, computer, server, or data center through a cable (such as Coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (such as infrared, wireless, microwave, etc.) transmission to another website site, computer, server or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or may include one or more data storage devices such as a server or a data center that can be integrated with the medium.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Landscapes

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

Abstract

本申请提供了一种通信方法及装置，该方法中，第一终端确定与第一侧行授权关联的第一HARQ信息，并通过侧行链路向第二终端发送第一HARQ信息。其中，第一HARQ信息包括：第一侧行授权关联的第一HARQ进程标识，第一侧行授权用于承载第一终端和第二终端之间的数据，该方法中，第一终端可以自行确定侧行授权关联的HARQ进程ID，该情况下，第一终端可以根据需求确定侧行授权关联的HARQ进程ID，而不受网络设备的影响。

Description

通信方法及装置 技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
车联网(vehicle to everything，V2X)是智能交通运输系统的关键技术，被认为是物联网体系中最有产业潜力、市场需求最明确的领域之一。车联网一般是指通过装载在车上的传感器、车载终端等提供车辆信息，实现车辆到车辆(vehicle to vehicle，V2V)，车辆到基础设施(vehicle to infrastructure，V2I)，车辆到网络(vehicle to network，V2N)以及车辆到行人(vehicle to pedestrian，V2P)之间的相互通信的通信网络。
V2X具有应用空间广、产业潜力大、社会效益强的特点，对促进汽车和信息通信产业创新发展，构建汽车和交通服务新模式新业态，推动无人驾驶、辅助驾驶、智能驾驶、网联驾驶、智能网联驾驶、自动驾驶、汽车共享等技术的创新和应用，以及提高交通效率和安全水平等都具有重要意义。
一般的，在V2X场景下，终端与其他终端之间进行直连通信的通信链路可以称之为侧行链路(sidelink，SL)或者边链路。针对SL的混合自动重传请求(hybrid automatic repeat request，HARQ)进程标识(ID)，目前并没有确定的方法。
发明内容
本申请实施例提供了一种通信方法及装置，用于确定SL的HARQ进程ID。
为达到上述目的，本申请实施例提供如下技术方案：
第一方面，提供了一种通信方法，包括：第一终端确定与第一侧行授权关联的第一HARQ信息，并通过侧行链路向第二终端发送第一HARQ信息。示例性的，第一侧行授权用于承载第一终端和第二终端之间的数据，第一HARQ信息包括：第一侧行授权关联的第一HARQ进程标识，侧行链路为第一终端和第二终端之间的无线直连通信链路。第一方面提供的方法，第一终端可以自行确定侧行授权关联的HARQ进程ID，该情况下，第一终端可以根据需求确定侧行授权关联的HARQ进程ID，而不受网络设备的影响。
在一种可能的实现方式中，第一HARQ信息还包括：用于指示对应的传输为新传或重传的新数据指示信息。
在一种可能的实现方式中，第一HARQ进程标识大于等于0小于N，N为第一终端在一个载波上最多支持的HARQ进程的个数，N为大于0的整数。该种可能的实现方式，可以节省SCI中HARQ进程标识所占的比特数。
在一种可能的实现方式中，第一终端确定与第一侧行授权关联的第一HARQ信息中的第一HARQ进程标识，包括：第一终端将第一终端在一个载波上最多支持的N个HARQ进程中的未被占用的一个HARQ进程的标识确定为第一HARQ进程标识；或者，在第一侧行授权抢占第二侧行授权的情况下，第一终端将第一终端确定的与第二侧行授权关联的HARQ进程标识确定为第一HARQ进程标识。
在一种可能的实现方式中，该方法还包括：第一终端保存第一侧行授权和第一 HARQ进程标识之间的对应关系；或者，第一终端保存第一HARQ进程标识和第二HARQ进程标识之间的对应关系；或者，第一终端保存第一侧行授权、第一HARQ进程标识和第二HARQ进程标识之间的对应关系；示例性的，第二HARQ进程标识为第一终端根据预设算法为第一侧行授权确定的HARQ进程标识或网络设备为第一侧行授权指示的HARQ进程标识。
在一种可能的实现方式中，该方法还包括：第一终端获取用于重传数据的第三侧行授权；第一终端将第一HARQ进程标识确定为第三侧行授权关联的HARQ进程标识；第一终端向第二终端发送第二HARQ信息，第二HARQ信息包括：第三侧行授权关联的第一HARQ进程标识。该种可能的实现方式，可以保证接收终端将同一个数据的新传和重传放到同一个缓存中进行处理，保证接收终端正确的解码数据。
在一种可能的实现方式中，第二HARQ信息还包括：用于指示对应的传输为重传的新数据指示信息。
在一种可能的实现方式中，第一终端获取用于重传数据的第三侧行授权，包括：第一终端确定用于重传数据的第三侧行授权；或者，第一终端向网络设备发送请求消息，请求消息用于请求重传数据的资源；请求消息包括第二HARQ进程标识，或者，传输请求消息的资源与第二HARQ进程标识关联；第一终端从网络设备接收请求响应，请求响应中包括用于指示第三侧行授权的信息。
在一种可能的实现方式中，第一终端确定用于重传数据的第三侧行授权，包括：第一终端从第一资源内选择用于重传数据的第三侧行授权，第一资源包括以下中的任一种或任几种类型的资源：侧行链路的资源；侧行链路的第一模式的资源；侧行链路的第二模式的资源；侧行链路的配置授权资源；侧行链路的第一类型配置授权资源；侧行链路的第二类型配置授权资源；侧行链路的动态授权资源；侧行链路的配置授权资源集合，配置授权资源集合包括一个或多个配置授权资源索引对应的配置授权资源。
在一种可能的实现方式中，该方法还包括：第一终端接收网络设备的配置信息，配置信息用于配置第一资源包括的资源的类型。该种可能的实现方式，可以使得第一终端确定第一资源，进而使得第一终端获知可以采用哪些资源进行数据重传。
在一种可能的实现方式中，第一侧行授权关联的第二HARQ进程标识与第三侧行授权关联的第四HARQ进程标识相同或不同，示例性的，第四HARQ进程标识为第一终端根据预设算法为第三侧行授权确定的HARQ进程标识或网络设备为第三侧行授权指示的HARQ进程标识。
在一种可能的实现方式中，该方法还包括：第一终端将第一侧行授权和第一HARQ进程标识之间的对应关系更新为：第三侧行授权和第一HARQ进程标识之间的对应关系；或者，第一终端将第一HARQ进程标识和第二HARQ进程标识之间的对应关系更新为：第一HARQ进程标识和第四HARQ进程标识之间的对应关系；或者，第一终端将第一侧行授权、第一HARQ进程标识和第二HARQ进程标识之间的对应关系更新为：第三侧行授权、第一HARQ进程标识和第四HARQ进程标识之间的对应关系；示例性的，第四HARQ进程标识为第一终端根据预设算法为第三侧行授权确定的HARQ进程标识或网络设备为第三侧行授权指示的HARQ进程标识。
在一种可能的实现方式中，该方法还包括：在第一HARQ进程标识对应的HARQ进 程结束的情况下，第一终端将第一侧行授权和第一HARQ进程标识之间的对应关系，或者，第一HARQ进程标识和第二HARQ进程标识之间的对应关系，或者，第一侧行授权、第一HARQ进程标识和第二HARQ进程标识之间的对应关系删除。该种可能的实现方式，及时的释放存储资源，可以提高存储资源的利用率，还可以用于标识已占用和未占用的HARQ进程。
在一种可能的实现方式中，第一HARQ进程标识对应的HARQ进程结束包括以下情况中的任意一种或多种：1)第一终端未接收到与第一HARQ进程标识对应的HARQ进程的反馈；2)第一终端接收到与第一HARQ进程标识对应的HARQ进程的肯定确认；3)第一终端仅接收到与第一HARQ进程标识对应的HARQ进程的肯定确认；4)第一终端向网络设备发送与第一HARQ进程标识对应的HARQ进程的肯定确认；5)与第一HARQ进程标识对应的HARQ进程关联的数据传输达到最大传输时间；6)与第一HARQ进程标识对应的HARQ进程关联的数据传输达到最大传输次数；7)第一终端释放第一HARQ进程标识对应的HARQ进程；8)第一终端清空第一HARQ进程标识对应的HARQ进程对应的HARQ缓存；9)其他侧行授权抢占了第一侧行授权；10)与第一HARQ进程标识对应的HARQ进程关联的数据传输完成或结束。
在一种可能的实现方式中，该方法还包括：在第四侧行授权抢占第一侧行授权的情况下，第一终端确定与第四侧行授权关联的第三HARQ信息，第三HARQ信息中包括：与第四侧行授权关联的第五HARQ进程标识。
在一种可能的实现方式中，该方法还包括：第一终端将第一侧行授权和第一HARQ进程标识之间的对应关系更新为：第四侧行授权和第五HARQ进程标识之间的对应关系；或者，第一终端将第一HARQ进程标识和第二HARQ进程标识之间的对应关系更新为：第五HARQ进程标识和第六HARQ进程标识之间的对应关系；或者，第一终端将第一侧行授权、第一HARQ进程标识和第二HARQ进程标识之间的对应关系更新为：第四侧行授权、第五HARQ进程标识和第六HARQ进程标识之间的对应关系；示例性的，第六HARQ进程标识为第一终端根据预设算法为第四侧行授权确定的HARQ进程标识或网络设备为第四侧行授权指示的HARQ进程标识。
在一种可能的实现方式中，第一侧行授权属于第二资源，第二资源包括以下中的任一种或任几种类型的资源：侧行链路的资源；侧行链路的第一模式的资源；侧行链路的第二模式的资源；侧行链路的配置授权资源；侧行链路的第一类型配置授权资源；侧行链路的第二类型配置授权资源；侧行链路的动态授权资源；侧行链路的配置授权资源集合，配置授权资源集合包括一个或多个配置授权资源索引对应的配置授权资源。
在一种可能的实现方式中，在第一终端为第一侧行授权确定第一HARQ信息之前，该方法还包括：第一终端确定在第一侧行授权上有数据需要发送。
第二方面，提供了一种通信方法，包括：网络设备生成用于配置第一资源包括的资源的类型的配置信息，并向第一终端发送配置信息。示例性的，第一资源用于第一终端和其他终端之间的数据的重传，第一终端和其他终端之间通过侧行链路通信，侧行链路为第一终端和其他终端之间的无线直连通信链路；示例性的，第一资源包括以下中的任一种或任几种类型的资源：侧行链路的资源；侧行链路的第一模式的资源；侧行链路的第二模式的资源；侧行链路的配置授权资源；侧行链路的第一类型配置授 权资源；侧行链路的第二类型配置授权资源；侧行链路的动态授权资源；侧行链路的配置授权资源集合，配置授权资源集合包括一个或多个配置授权资源索引对应的配置授权资源。第二方面提供的方法，可以为第一终端配置第一资源包含的资源的类型，从而使得第一终端确定第一资源，进而使得第一终端获知可以采用哪些资源进行数据重传。
在一种可能的实现方式中，第一资源具体用于第一终端和其他终端之间的承载在第二资源上的数据的重传；第二资源包括以下中的任一种或任几种类型的资源：侧行链路的资源；侧行链路的第一模式的资源；侧行链路的第二模式的资源；侧行链路的配置授权资源；侧行链路的第一类型配置授权资源；侧行链路的第二类型配置授权资源；侧行链路的动态授权资源；侧行链路的配置授权资源集合，配置授权资源集合包括一个或多个配置授权资源索引对应的配置授权资源。
第三方面，提供了一种通信方法，包括：第一终端确定与第一侧行授权关联的第一HARQ信息，示例性的，所述第一侧行授权用于承载所述第一终端和第二终端之间的数据，所述第一HARQ信息包括：所述第一侧行授权关联的HARQ进程标识；所述第一终端获取用于重传所述数据的第三侧行授权；所述第一终端确定与所述第三侧行授权关联的第二HARQ信息，所述第二HARQ信息包括：所述第三侧行授权关联的HARQ进程标识，所述第三侧行授权关联的HARQ进程标识与所述第一侧行授权关联的HARQ进程标识相同。第三方面提供的方法，可以保证接收终端将同一个数据的新传和重传放到同一个缓存中进行处理，保证接收终端正确的解码数据。
在一种可能的实现方式中，所述第一HARQ信息还包括：新数据指示信息，该新数据指示信息用于指示对应的传输为新传或重传；和/或，所述第二HARQ信息还包括：新数据指示信息，该新数据指示信息用于指示对应的传输为重传。
第四方面，提供了一种资源分配方法，包括：网络设备启动与第一终端的第二HARQ进程ID关联的第一定时器，所述第二HARQ进程ID为所述网络设备根据预设算法为所述第一终端的第一侧行授权确定的HARQ进程ID；在所述第一定时器超时的情况下，若所述网络设备未接收到针对所述第二HARQ进程ID对应的HARQ进程传输的侧行数据的肯定确认时，所述网络设备向所述第一终端发送资源指示信息，所述资源指示信息用于指示重传所述侧行数据的侧行链路资源。
第五方面，提供了一种清空HARQ缓存的方法，包括：终端确定上行数据传输完成；所述终端清空用于传输所述上行数据的HARQ进程对应的HARQ缓存。第五方面提供的方法，可以在数据传输完成时清空HARQ缓存，从而节约缓存空间。
第六方面，提供了一种清空HARQ缓存的方法，包括：终端确定侧行数据传输完成，所述侧行数据传输完成包括所述侧行数据传输成功或所述侧行数据传输达到最大传输次数或所述侧行数据传输达到最大传输时间；所述终端清空用于传输所述侧行数据的HARQ进程对应的HARQ缓存。第六方面提供的方法，可以在数据传输完成时清空HARQ缓存，从而节约缓存空间。
在一种可能的实现方式中，所述侧行数据传输成功，包括以下任一种或任几种情况：所述终端未接收到针对所述侧行数据的否定确认；所述终端接收到针对所述侧行数据的肯定确认；所述终端接收到针对所述侧行数据的肯定确认，且未接收到针对所 述侧行数据的否定确认。
第七方面，提供了一种通信装置，包括：处理单元和通信单元；处理单元，用于确定与第一侧行授权关联的第一HARQ信息，示例性的，第一侧行授权用于承载该装置和第二终端之间的数据，第一HARQ信息包括：第一侧行授权关联的第一HARQ进程标识；通信单元，用于通过侧行链路向第二终端发送第一HARQ信息，侧行链路为该装置和第二终端之间的无线直连通信链路。
在一种可能的实现方式中，第一HARQ信息还包括：新数据指示信息，该新数据指示信息用于指示对应的传输为新传或重传。
在一种可能的实现方式中，第一HARQ进程标识大于等于0小于N，N为该装置在一个载波上最多支持的HARQ进程的个数，N为大于0的整数。
在一种可能的实现方式中，处理单元，具体用于：将该装置在一个载波上最多支持的N个HARQ进程中的未被占用的一个HARQ进程的标识确定为第一HARQ进程标识；或者，在第一侧行授权抢占第二侧行授权的情况下，将该装置确定的与第二侧行授权关联的HARQ进程标识确定为第一HARQ进程标识。
在一种可能的实现方式中，处理单元，还用于：保存第一侧行授权和第一HARQ进程标识之间的对应关系；或者，保存第一HARQ进程标识和第二HARQ进程标识之间的对应关系；或者，保存第一侧行授权、第一HARQ进程标识和第二HARQ进程标识之间的对应关系；示例性的，第二HARQ进程标识为该装置根据预设算法为第一侧行授权确定的HARQ进程标识或网络设备为第一侧行授权指示的HARQ进程标识。
在一种可能的实现方式中，处理单元，还用于获取用于重传数据的第三侧行授权；处理单元，还用于将第一HARQ进程标识确定为第三侧行授权关联的HARQ进程标识；通信单元，还用于向第二终端发送第二HARQ信息，第二HARQ信息包括：第三侧行授权关联的第一HARQ进程标识。
在一种可能的实现方式中，第二HARQ信息还包括：新数据指示信息，该新数据指示信息用于指示对应的传输为重传。
在一种可能的实现方式中，处理单元，具体用于：确定用于重传数据的第三侧行授权；或者，通过通信单元向网络设备发送请求消息，请求消息用于请求重传数据的资源；请求消息包括第二HARQ进程标识，或者，传输请求消息的资源与第二HARQ进程标识关联；通过通信单元从网络设备接收请求响应，请求响应中包括用于指示第三侧行授权的信息。
在一种可能的实现方式中，处理单元，具体用于：从第一资源内选择用于重传数据的第三侧行授权，第一资源包括以下中的任一种或任几种类型的资源：侧行链路的资源；侧行链路的第一模式的资源；侧行链路的第二模式的资源；侧行链路的配置授权资源；侧行链路的第一类型配置授权资源；侧行链路的第二类型配置授权资源；侧行链路的动态授权资源；侧行链路的配置授权资源集合，配置授权资源集合包括一个或多个配置授权资源索引对应的配置授权资源。
在一种可能的实现方式中，通信单元，还用于接收网络设备的配置信息，配置信息用于配置第一资源包括的资源的类型。
在一种可能的实现方式中，第一侧行授权关联的第二HARQ进程标识与第三侧行授 权关联的第四HARQ进程标识相同或不同，示例性的，第四HARQ进程标识为该装置根据预设算法为第三侧行授权确定的HARQ进程标识或网络设备为第三侧行授权指示的HARQ进程标识。
在一种可能的实现方式中，处理单元，还用于：将第一侧行授权和第一HARQ进程标识之间的对应关系更新为：第三侧行授权和第一HARQ进程标识之间的对应关系；或者，将第一HARQ进程标识和第二HARQ进程标识之间的对应关系更新为：第一HARQ进程标识和第四HARQ进程标识之间的对应关系；或者，将第一侧行授权、第一HARQ进程标识和第二HARQ进程标识之间的对应关系更新为：第三侧行授权、第一HARQ进程标识和第四HARQ进程标识之间的对应关系；示例性的，第四HARQ进程标识为该装置根据预设算法为第三侧行授权确定的HARQ进程标识或网络设备为第三侧行授权指示的HARQ进程标识。
在一种可能的实现方式中，处理单元，还用于：在第一HARQ进程标识对应的HARQ进程结束的情况下，将第一侧行授权和第一HARQ进程标识之间的对应关系，或者，第一HARQ进程标识和第二HARQ进程标识之间的对应关系，或者，第一侧行授权、第一HARQ进程标识和第二HARQ进程标识之间的对应关系删除。
在一种可能的实现方式中，第一HARQ进程标识对应的HARQ进程结束包括以下情况中的任意一种或多种：1)该装置未接收到与第一HARQ进程标识对应的HARQ进程的反馈；2)该装置接收到与第一HARQ进程标识对应的HARQ进程的肯定确认；3)该装置仅接收到与第一HARQ进程标识对应的HARQ进程的肯定确认；4)该装置向网络设备发送与第一HARQ进程标识对应的HARQ进程的肯定确认；5)与第一HARQ进程标识对应的HARQ进程关联的数据传输达到最大传输时间；6)与第一HARQ进程标识对应的HARQ进程关联的数据传输达到最大传输次数；7)该装置释放第一HARQ进程标识对应的HARQ进程；8)该装置清空第一HARQ进程标识对应的HARQ进程对应的HARQ缓存；9)其他侧行授权抢占了第一侧行授权；10)与第一HARQ进程标识对应的HARQ进程关联的数据传输完成或结束。
在一种可能的实现方式中，处理单元，还用于：在第四侧行授权抢占第一侧行授权的情况下，确定与第四侧行授权关联的第三HARQ信息，第三HARQ信息中包括：与第四侧行授权关联的第五HARQ进程标识。
在一种可能的实现方式中，处理单元，还用于：将第一侧行授权和第一HARQ进程标识之间的对应关系更新为：第四侧行授权和第五HARQ进程标识之间的对应关系；或者，将第一HARQ进程标识和第二HARQ进程标识之间的对应关系更新为：第五HARQ进程标识和第六HARQ进程标识之间的对应关系；或者，将第一侧行授权、第一HARQ进程标识和第二HARQ进程标识之间的对应关系更新为：第四侧行授权、第五HARQ进程标识和第六HARQ进程标识之间的对应关系；示例性的，第六HARQ进程标识为该装置根据预设算法为第四侧行授权确定的HARQ进程标识或网络设备为第四侧行授权指示的HARQ进程标识。
在一种可能的实现方式中，第一侧行授权属于第二资源，第二资源包括以下中的任一种或任几种类型的资源：侧行链路的资源；侧行链路的第一模式的资源；侧行链路的第二模式的资源；侧行链路的配置授权资源；侧行链路的第一类型配置授权资源； 侧行链路的第二类型配置授权资源；侧行链路的动态授权资源；侧行链路的配置授权资源集合，配置授权资源集合包括一个或多个配置授权资源索引对应的配置授权资源。
在一种可能的实现方式中，处理单元，还用于：确定在第一侧行授权上有数据需要发送。
第八方面，提供了一种通信装置，包括：处理单元和通信单元；处理单元，用于生成配置信息，配置信息用于配置第一资源包括的资源的类型，第一资源用于第一终端和其他终端之间的数据的重传，第一终端和其他终端之间通过侧行链路通信，侧行链路为第一终端和其他终端之间的无线直连通信链路；通信单元，用于向第一终端发送配置信息；示例性的，第一资源包括以下中的任一种或任几种类型的资源：侧行链路的资源；侧行链路的第一模式的资源；侧行链路的第二模式的资源；侧行链路的配置授权资源；侧行链路的第一类型配置授权资源；侧行链路的第二类型配置授权资源；侧行链路的动态授权资源；侧行链路的配置授权资源集合，配置授权资源集合包括一个或多个配置授权资源索引对应的配置授权资源。
在一种可能的实现方式中，第一资源具体用于第一终端和其他终端之间的承载在第二资源上的数据的重传；第二资源包括以下中的任一种或任几种类型的资源：侧行链路的资源；侧行链路的第一模式的资源；侧行链路的第二模式的资源；侧行链路的配置授权资源；侧行链路的第一类型配置授权资源；侧行链路的第二类型配置授权资源；侧行链路的动态授权资源；侧行链路的配置授权资源集合，配置授权资源集合包括一个或多个配置授权资源索引对应的配置授权资源。
第九方面，提供了一种通信装置，包括：处理单元；所述处理单元，用于确定与第一侧行授权关联的第一HARQ信息，示例性的，所述第一侧行授权用于承载所述装置和第二终端之间的数据，所述第一HARQ信息包括：所述第一侧行授权关联的HARQ进程标识；所述处理单元，还用于获取用于重传所述数据的第三侧行授权；所述处理单元，还用于确定与所述第三侧行授权关联的第二HARQ信息，所述第二HARQ信息包括：所述第三侧行授权关联的HARQ进程标识，所述第三侧行授权关联的HARQ进程标识与所述第一侧行授权关联的HARQ进程标识相同。
在一种可能的实现方式中，所述第一HARQ信息还包括：新数据指示信息，该新数据指示信息用于指示对应的传输为新传或重传；和/或，所述第二HARQ信息还包括：新数据指示信息，该新数据指示信息用于指示对应的传输为重传。
第十方面，提供了一种资源分配装置，包括：处理单元和通信单元，所述处理单元，用于启动与第一终端的第二HARQ进程ID关联的第一定时器，所述第二HARQ进程ID为所述装置根据预设算法为所述第一终端的第一侧行授权确定的HARQ进程ID；在所述第一定时器超时的情况下，若所述装置未接收到针对所述第二HARQ进程ID对应的HARQ进程传输的侧行数据的肯定确认时，所述通信单元，用于向所述第一终端发送资源指示信息，所述资源指示信息用于指示重传所述侧行数据的侧行链路资源。
第十一方面，提供了一种清空HARQ缓存的装置，包括：处理单元，用于确定上行数据传输完成，并清空用于传输所述上行数据的HARQ进程对应的HARQ缓存。
第十二方面，提供了一种清空HARQ缓存的装置，包括：处理单元，用于确定侧行数据传输完成，并清空用于传输所述侧行数据的HARQ进程对应的HARQ缓存，所述侧 行数据传输完成包括所述侧行数据传输成功或所述侧行数据传输达到最大传输次数或所述侧行数据传输达到最大传输时间。
在一种可能的实现方式中，所述侧行数据传输成功，包括以下任一种或任几种：所述终端未接收到针对所述侧行数据的否定确认；所述终端接收到针对所述侧行数据的肯定确认；所述终端接收到针对所述侧行数据的肯定确认，且未接收到针对所述侧行数据的否定确认。
第十三方面，提供了一种通信装置，包括：处理器。处理器与存储器连接，存储器用于存储计算机执行指令，处理器执行存储器存储的计算机执行指令，从而实现第一方面至第六方面中任一方面提供的任意一种方法。示例性的，存储器和处理器可以集成在一起，也可以为独立的器件。若为后者，存储器可以位于通信装置内，也可以位于通信装置外。
在一种可能的实现方式中，处理器包括逻辑电路，还包括输入接口和输出接口中的至少一个。示例性的，输出接口用于执行相应方法中的发送的动作，输入接口用于执行相应方法中的接收的动作。
在一种可能的实现方式中，通信装置还包括通信接口和通信总线，处理器、存储器和通信接口通过通信总线连接。通信接口用于执行相应方法中的收发的动作。通信接口也可以称为收发器。可选的，通信接口包括发送器和接收器中的至少一种，该情况下，发送器用于执行相应方法中的发送的动作，接收器用于执行相应方法中的接收的动作。
在一种可能的实现方式中，通信装置以芯片的产品形态存在。
第十四方面，提供了一种通信系统，包括：上述第七方面提供的通信装置和第八方面提供的通信装置。
第十五方面，提供了一种计算机可读存储介质，包括指令，当该指令在计算机上运行时，使得计算机执行第一方面至第六方面中任一方面提供的任意一种方法。
第十六方面，提供了一种包含指令的计算机程序产品，当该指令在计算机上运行时，使得计算机执行第一方面至第六方面中任一方面提供的任意一种方法。
第七方面至第十六方面中的任一种实现方式所带来的技术效果可参见第一方面至第六方面中对应实现方式所带来的技术效果，此处不再赘述。
附图说明
图1为本申请实施例提供的一种通信场景示意图；
图2为本申请实施例提供的一种侧行授权的示意图；
图3为本申请实施例提供的一种并行HARQ进程的示意图；
图4为本申请实施例提供的一种上行授权及其对应的HARQ进程ID的示意图；
图5至图8为本申请实施例提供的一种多个SL传输资源中的侧行授权及其关联的HARQ进程ID的示意图；
图9和图10分别为本申请实施例提供的一种通信方法的流程图；
图10A为本申请实施例提供的一种通信方法的流程；
图10B为本申请实施例提供的发送终端和接收终端之间的数据传输示意图；
图11为本申请实施例提供的一种侧行授权及其对应的HARQ进程ID的示意图；
图12为本申请实施例提供的一种第一终端中存储的对应关系的示意图；
图13为本申请实施例提供的一种侧行授权及其对应的HARQ进程ID的示意图；
图14和图15分别为本申请实施例提供的一种第一终端中存储的对应关系的示意图；
图16和图17分别为本申请实施例提供的一种清空HARQ缓存的方法的流程图；
图18为本申请实施例提供的一种通信装置的组成示意图；
图19和图20分别为本申请实施例提供的一种通信装置的硬件结构示意图。
具体实施方式
在本申请的描述中，除非另有说明，“/”表示“或”的意思，例如，A/B可以表示A或B。本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。此外，“至少一个”是指一个或多个，“多个”是指两个或两个以上。“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
需要说明的是，本申请中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本申请实施例提供的方法可适用但不限于如下领域：设备到设备(device to device，D2D)、V2X、无人驾驶(unmanned driving)、自动驾驶(automated driving，ADS)、辅助驾驶(driver assistance，ADAS)、智能驾驶(intelligent driving)、网联驾驶(connected driving)、智能网联驾驶(intelligent network driving)、汽车共享(car sharing)等。
本申请涉及到的网元包括通信系统中的网络设备和终端。参见图1，本申请实施例提供的方法主要涉及终端和终端之间的通信，以及终端和网络设备之间的通信。
本申请实施例中的通信系统包括但不限于长期演进(long term evolution，LTE)系统、第五代(5th-generation，5G)系统、新无线(new radio，NR)系统，无线局域网(wireless local area networks，WLAN)系统以及未来演进系统或者多种通信融合系统。其中，5G系统可以为非独立组网(non-standalone，NSA)的5G系统或独立组网(standalone，SA)的5G系统。
本申请实施例中的网络设备为网络侧的一种用于发送信号，或者，接收信号，或者，发送信号和接收信号的实体。网络设备可以为部署在无线接入网(radio access network，RAN)中为终端提供无线通信功能的装置，例如可以为传输接收点(transmission reception point，TRP)、基站、各种形式的控制节点(例如，网络控制器、无线控制器(例如，云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器))等。具体的，网络设备可以为各种形式的宏基站，微基站(也称为小站)，中继站，接入点(access point，AP)等，也可以为基站的天线面板。所述控制节点可以连接多个基站，并为所述多个基站覆盖下的多个终端配置资源。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同。例如，LTE系统中可以称为演进型基站(evolved NodeB，eNB或eNodeB)，5G系统或NR系统中可以称为下一代基站节点(next generation node base  station，gNB)，本申请对基站的具体名称不作限定。网络设备还可以是未来演进的公共陆地移动网络(public land mobile network，PLMN)中的网络设备等。
本申请实施例中的终端是用户侧的一种用于接收信号，或者，发送信号，或者，接收信号和发送信号的实体。终端用于向用户提供语音服务和数据连通性服务中的一种或多种。终端还可以称为用户设备(user equipment，UE)、终端设备、接入终端、用户单元、用户站、移动站、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置。终端可以是V2X设备，例如，智能汽车(smart car或intelligent car)、数字汽车(digital car)、无人汽车(unmanned car或driverless car或pilotless car或automobile)、自动汽车(self-driving car或autonomous car)、纯电动汽车(pure EV或Battery EV)、混合动力汽车(hybrid electric vehicle，HEV)、增程式电动汽车(range extended EV，REEV)、插电式混合动力汽车(plug-in HEV，PHEV)、新能源汽车(new energy vehicle)、路边装置(road site unit，RSU)。终端也可以是D2D设备，例如，电表、水表等。终端还可以是移动站(mobile station，MS)、用户单元(subscriber unit)、无人机、物联网(internet of things，IoT)设备、WLAN中的站点(station，ST)、蜂窝电话(cellular phone)、智能电话(smart phone)、无绳电话、无线数据卡、平板型电脑、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)设备、膝上型电脑(laptop computer)、机器类型通信(machine type communication，MTC)终端、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备(也可以称为穿戴式智能设备)。终端还可以为下一代通信系统中的终端，例如，5G系统中的终端或者未来演进的PLMN中的终端，NR系统中的终端等。
为了使得本申请实施例更加的清楚，以下对与本申请实施例相关的概念和部分内容作简单介绍。
1、上行链路(uplink，UL)、下行链路(downlink，DL)、SL
终端向网络设备发送数据(即上行数据)的无线通信链路可以称为UL。网络设备向终端发送数据(即下行数据)的无线通信链路可以称为DL。UL接口和DL接口可以统称为Uu口，因此，UL和DL可以统称为Uu口链路。
终端和终端之间的直连通信的通信链路可以称为SL。SL也可以称为边链路。终端和终端之间传输的数据可以称为SL数据。
示例性的，本申请实施例中的数据可以理解为传输块(transport block，TB)或媒介接入控制(medium access control，MAC)协议数据单元(protocol data unit，PDU)。数据也可以称为数据包或报文。
2、SL的资源分配模式
两个终端中的发送终端所采用的SL传输资源可以通过以下方式A和方式B中的任意一种确定。
方式A、网络设备调度
网络设备调度SL传输资源的模式可以包括模式1(mode1)资源配置模式(NR中的名称)或者模式3(mode3)资源配置模式(LTE中的名称)。
其中，网络设备调度的SL传输资源有以下两种类型：
第一种：配置授权(configured grant，CG)资源
该情况下，发送终端的每次数据传输并不总是需要网络设备单独分配资源，网络设备在某次为发送终端分配资源之后，未来一段时间内，发送终端都可以使用上述分配的资源，特点是“一次分配，多次使用”。具体的，网络设备可以为发送终端配置一段周期性出现的时域资源。示例性的，参见图2，该段周期性出现的时域资源中第一次出现的时域资源为时隙1的符号4至符号9，周期为1个时隙。其中，每次出现的时域资源为一个SL的授权(下文中简称为侧行授权)，则可以理解的是，图2中示出了4个侧行授权，1个侧行授权对应1个侧行授权ID，则4个侧行授权对应的侧行授权ID分别为侧行授权0、侧行授权1、侧行授权2和侧行授权3。
CG资源可以包括类型1(type1)CG(SL configured grant type-1)资源、类型2(type2)CG(SL configured grant type-2)资源、免授权(SL grant free)资源、半静态调度(SL Semi-Persistent Scheduling，SL SPS)资源。type1CG资源可以是网络设备通过无线资源控制(radio resource control，RRC)信令直接配置给发送终端的SL传输资源，发送终端可以直接使用该CG资源传输数据，不需要额外的激活。type2CG资源可以是网络设备通过RRC信令定义SL传输资源的周期，再通过物理下行控制信道(physical downlink control channel，PDCCH)中的下行控制信息(downlink control information，DCI)激活该SL传输资源，发送终端不能直接使用该SL传输资源传输数据，激活之后才能使用。免授权资源可以是网络设备通过RRC信令直接配置给发送终端的SL传输资源，发送终端可以直接使用该SL传输资源传输数据，不需要额外的激活。半静态调度资源可以是网络设备通过RRC信令定义SL传输资源的周期，再通过PDCCH中的DCI激活该SL传输资源，发送终端不能直接使用该SL传输资源传输数据，激活之后才能使用。
目前，针对上行链路，一个载波上仅支持一个CG资源。针对SL，一个载波上可以支持多个CG资源，不同的CG资源可以对应不同的索引。示例性的，索引为1、2、3的CG资源可以分别记为CG1、CG2、CG3。
第二种：动态授权(dynamic grant，DG)资源
该情况下，发送终端的每次数据传输都需要网络设备单独分配资源，特点是“一次分配，一次使用”，比如，可以是网络设备通过DCI动态分配给发送终端的SL传输资源。DCI可以承载在PDCCH中。
其中，DG和CG主要的区别在于资源分配的灵活性和资源分配的开销。DG，网络设备需要为发送终端的每次数据传输分配授权，资源分配灵活，但是，资源分配开销较大。CG，网络设备的一次授权分配，发送终端可以多次使用，资源分配开销较小，但是，分配的资源相当长的时间内没有变化和调整，资源分配不灵活。DG一般使用物理信道(例如，PDCCH)来分配，分配比较迅速。CG一般使用高层信令(例如，RRC信令)或者高层信令(例如，RRC信令)加物理信道(例如，PDCCH)来配置，资源分配较慢。
方式B、发送终端自行确定
发送终端自行确定SL传输资源的模式可以包括模式2(mode2)资源配置模式(NR中的名称)或者模式4(mode4)资源配置模式(LTE中的名称)。
在方式B中，发送终端在网络设备通信覆盖范围内时，网络设备可以通过系统广播(system information block，SIB)消息或专用RRC信令为发送终端配置SL资源池，发送终端可以自主从SL资源池中获取SL传输资源来发送控制信号和/或数据信号给接收终端。发送终端在网络设备通信覆盖范围外时，发送终端可以自主从预配置的SL资源池中获取SL传输资源来发送控制信号和/或数据信号给接收终端。
在从SL资源池中获取SL传输资源时，发送终端可以感知或竞争SL传输资源。具体的，发送终端通过和其他终端竞争获得SL资源池中的合适的SL传输资源来发送控制信号和/或数据信号。其中，发送终端中待传输的V2X业务或数据的优先级越高，其竞争到SL资源池中的合适的SL传输资源的机会就越大。
在LTE V2X中，mode3和mode4不可以同时存在。在NR V2X中，mode1和mode2可以同时存在。
上述SL的资源可以分为多种类型，具体包括以下多种：
1)SL的第一模式的资源：网络设备调度的SL传输资源，可以包括：采用上述mode1资源配置模式配置的资源，或，采用上述mode3资源配置模式配置的资源。其中，采用上述mode1资源配置模式配置的资源或采用上述mode3资源配置模式配置的资源可以包括：SL的CG资源和/或SL的DG资源。
2)SL的第二模式的资源：终端需要自己选择或竞争或感知的SL传输资源，可以包括：采用上述mode2资源配置模式配置的资源，或，采用上述mode4资源配置模式配置的资源。
3)SL的第一类型CG资源：不需要激活就可以直接使用的CG资源，可以包括：上述type1CG资源，和/或，上述免授权资源。
4)SL的第二类型CG资源：终端不能直接使用，激活之后才能使用的CG资源，可以包括：上述type2CG资源，和/或，上述半静态调度资源。
5)SL的资源：上述SL的第一模式的资源，和/或，上述SL的第二模式的资源。
6)SL的CG资源：上述SL的第一类型CG资源，和/或，上述SL的第二类型CG资源。
7)SL的DG资源：网络设备通过DCI动态分配给终端的SL传输资源。
8)SL的CG资源集合：CG资源集合包括一个或多个CG资源索引对应的CG资源，例如，由CG1、CG2和CG3组成的资源集合。
需要说明的是，不同的CG资源集合为不同类型的资源。例如，CG资源集合1为一种类型的资源，CG资源集合2为另一种类型的资源。
3、HARQ
HARQ是一种结合前向纠错(或者说前向纠错码)(forward error correction，FEC)与自动重传请求(automatic repeat request，ARQ)方法的技术。
其中，FEC是指发送端发送的数据中包括前向纠错码或冗余信息，当接收端接收到数据后，通过校验(例如，循环冗余校验(cyclic redundancy check，CRC)校验)发现错误之后，能够通过前向纠错码或冗余信息进行纠正，这样发送端可以减少重传(即重新传输数据)的次数。
ARQ是指接收端通过校验(例如，CRC校验)判断接收到的数据的正确性，如果数 据接收正确，接收端发送肯定确认(acknowledgement，ACK)告知发送端，否则接收端发送否定确认(negative acknowledgement，NACK)告知发送端，发送端接收到NACK时，可以重传数据给接收端。ACK和NACK即HARQ反馈。
LTE V2X中由于仅支持广播业务，因此，不支持SL HARQ反馈。NR V2X中支持单播、组播和广播业务，支持SL HARQ反馈。
以下通过(a)至(c)三部分内容对与HARQ相关的内容具体进行介绍。
(a)HARQ进程(HARQ process)
HARQ使用停等协议(stop-and-wait protocol)来发送数据。在停等协议中，发送端发送一个传输块(transport block，TB)后，就停下来等待确认信息。接收端可以针对该TB反馈ACK或NACK。但是每次传输后发送端就停下来等待确认，会导致吞吐量很低。因此，可以使用多个并行的HARQ进程：当一个HARQ进程在等待确认时，发送端可以使用另一个HARQ进程来继续发送数据。示例性的，参见图3，终端采用第1个HARQ进程发送TB1，在T1时刻发送完TB1，在T2时刻接收TB1的HARQ反馈，在T1到T2这一时间段内，等待TB1的确认，在等待确认的这段时间内，可以采用第2个HARQ进程发送TB2，在T2时刻发送完TB2，在T3时刻接收TB2的HARQ反馈，在T2到T3这一时间段内，等待TB2的确认，在等待确认的这段时间内，可以采用第3个HARQ进程发送TB3。
需要说明的是，每个HARQ进程在一个传输时间间隔(transmission time interval，TTI)能处理一个TB，也能处理多个TB(例如，在空分复用的情况下)。
一般情况下，一个侧行授权关联一个HARQ进程。比较特殊的是，一个bundle内包括的多个侧行授权关联同一个HARQ进程，即一个bundle内包括的多个侧行授权上的传输(例如，上行传输，或，侧行传输)对应同一个HARQ进程。
示例性的，一个bundle内的传输可以理解为一个TB在一次新传之后，需要再进行一次或多次重传，在发送端将同一个TB的多次发送关联到同一个HARQ进程，对于接收端来说，可以将同一个HARQ进程的多次接收的数据放到同一个缓存(例如，HARQ缓存(buffer)或软缓存(soft buffer))中，进行软合并解码。
其中，一个HARQ进程通过一个HARQ进程ID来标识。
可选的，本申请实施例中的关于终端的HARQ进程的描述均是针对一个载波而言的。对于多载波的情况，每个载波上的情况与本申请文件中相同。
(b)接收端对新传数据和重传数据的处理机制
每个HARQ进程在接收端有对应的缓存(例如，HARQ buffer或soft buffer)，以便对接收到的数据进行软合并解码。
接收端接收到发送端采用一个HARQ进程发送的新传数据后，可以将接收到的新传数据放入该HARQ进程对应的缓存(例如，HARQ buffer或soft buffer)中，进行解码。若解码失败，再次接收到该新传数据的重传数据时，可以将接收到的重传数据和之前存储在缓存中的新传数据进行合并，放入缓存中，再次解码，这种方式可以称为软合并解码，相比于单独解码(即每次传输的数据都单独解码，不和之前的数据合并进行解码)，提高了解码成功的几率。同样，若解码仍然失败，可以继续重复上述过程，将新接收到的重传数据与缓存中的数据进行合并，并再次解码。
其中，发送端的重传数据和新传数据可以为同一个TB的同一个冗余版本 (redundancy version，RV)或不同的RV。
(c)上行传输中HARQ进程ID的确定机制
针对UL，一个载波上支持一个CG资源。一个CG资源上最多支持16个HARQ进程。针对CG资源，可以采用协议中规定的公式(具体可参见3GPP TS 38.321:"NR；Medium Access Control(MAC)；Protocol specification".中的第5.4.1节)(将该公式称为预设算法1)计算CG资源上的每个上行授权关联的HARQ进程ID，HARQ进程ID的最大范围为0至15，终端和网络设备均可以根据预设算法1计算出每个上行授权对应的HARQ进程ID。针对DG资源，网络设备可以在DCI中将每个上行授权关联的HARQ进程ID指示给终端。
示例性的，在子载波间隔(subcarrier spacing，SCS)为15KHZ的情况下，一个UL CG资源的起始系统帧号(system frame number，SFN)为5，起始时隙为时隙1，起始符号为符号4，一个上行授权占6个符号，周期为1个时隙，该CG资源可用的HARQ进程数为16，基于预设算法1进行计算，可以得出每个上行授权关联的HARQ进程ID，具体可参见图4。
针对SL，一个载波上同时存在多个CG资源，此时，可以通过以下方式C或方式D计算每个侧行授权关联的HARQ进程ID(以下内容中的HARQ进程均指SL HARQ进程，HARQ进程ID均指SL HARQ进程ID)。
方式C
针对每个CG资源，可以采用与预设算法1相类似的公式，计算CG资源中的每个侧行授权关联的HARQ进程ID。
采用方式C确定每个侧行授权关联的HARQ进程ID时，不同的CG资源上的侧行授权关联的HARQ进程ID可能是重叠的。
另外，SL的第一模式的资源中的每个侧行授权关联的HARQ进程ID可能是网络设备指示给终端的或者终端根据预设的规则(例如，上述预设算法1)计算的。SL的第二模式的资源中的每个侧行授权关联的HARQ进程ID可能是终端确定的。因此，SL的第一模式的资源和SL的第二模式的资源中的侧行授权关联的HARQ进程ID可能会重叠。
可选的，针对DG资源，网络设备可以确定HARQ进程ID，并通过DCI将该HARQ进程ID指示给终端。该HARQ进程ID可能与其他侧行授权关联的HARQ进程ID重叠。
不同资源(例如，不同的CG资源，或，第一模式的资源和第二模式的资源，或，DG资源和CG资源)上的侧行授权传输的数据可能为不同的数据，若不同资源上的侧行授权关联的HARQ进程ID相同，这就意味着，接收终端可能将不同的数据作软合并，导致解码出错。
方式D
采用预设算法2计算不同CG资源上的侧行授权关联的HARQ进程ID。预设算法2可以是在预设算法1的基础上增加一个偏移值(offset)，网络设备可以配置每个CG资源可用的HARQ进程数以及offset，从而使得不同的CG资源上的侧行授权关联的HARQ进程ID不同。例如，CG1可用的HARQ进程数为4，offset1＝0；CG2可用的HARQ进程数为8，offset2＝4；那么CG1可用的HARQ进程ID为0至3，CG2可用的HARQ进程ID为4至11，这样就把CG1和CG2的HARQ进程ID区分开了。
另外，可以通过其他方法使得SL的第一模式的资源上的侧行授权和SL的第二模式的资源上的侧行授权关联不同的HARQ进程ID。
综上，方式D的目的是要保证不同资源(例如，不同的CG资源，或，第一模式的资源 和第二模式的资源，或，DG资源和CG资源)上的侧行授权关联不同的HARQ进程ID。若全部资源上可用的HARQ进程ID的范围为0至M-1。M的值(示例性的，M＝24或M＝32)可能大于终端在一个载波上最多支持的HARQ进程的个数(记为N，示例性的，N＝8或N＝16)，该情况下，终端可以在M个HARQ进程ID中选择N个HARQ进程ID同时进行数据的传输。其中，终端在一个载波上最多支持的HARQ进程的个数可以理解为终端在一个载波上同时最多支持的HARQ进程的个数。
方式D这种计算HARQ进程ID的方法会存在以下几个问题。
问题1、SCI中HARQ进程ID所占的比特(bit)数较多。
需要说明的是，发送终端在发送数据时，可以在调度该数据的SL控制信息(sidelink control information，SCI)中携带发送终端所采用的HARQ进程对应的HARQ进程ID。该情况下，示例性的，如果网络设备为终端配置了8个CG资源，每个CG资源支持的HARQ进程数为2，终端为SL的第二模式的资源分配了16个HARQ进程，那么终端的HARQ进程ID的范围为0至31。SCI中HARQ进程ID需要占用5bit。若终端的HARQ进程ID范围更大，则需要占用更多的bit，将会增大SCI传输的负担。
问题2、具体包括以下3个和重传相关的问题。
1)重传时延不能保证。
需要说明的是，同一个数据的新传和重传采用的HARQ进程需要对应相同HARQ进程ID，以便接收终端对新传和重传的数据进行软合并。此时，方式D这种计算HARQ进程ID的方法，同一个数据的新传和重传只能在一个CG资源中的关联相同的HARQ进程ID的侧行授权上，无法保证重传时延。示例性的，参见图5，如果网络设备为终端配置了7个CG资源，每个CG资源支持的HARQ进程数为2，CG资源对应的HARQ进程ID为0-13。网络设备还为终端配置了一个DG资源，并指示了DG资源对应的HARQ进程ID为14。另外，SL的第二模式的资源对应的HARQ进程ID为16-31。图5至图8以及图11和图13中的小方块为侧行授权，小方块旁边的数字为该侧行授权对应的HARQ进程ID。若发送终端在HARQ进程0向接收终端新传一个数据，接收终端在T1向发送终端反馈HARQ进程0的NACK，那么发送终端也要在HARQ进程0重传这个数据，而HARQ进程0关联的侧行授权之间的时间间隔较长，会导致重传时延较大。
2)不同CG资源之间不能共享HARQ进程ID。
若为了满足一个业务的时延和可靠性要求，为这个业务配置了3个CG资源，那么这3个CG资源之间的HARQ进程ID应该共享，新传和重传也应该共享。但是，按照目前方式D计算HARQ进程ID的方法无法使得这3个CG资源之间的HARQ进程ID共享。
3)DG资源上传输的数据无法重传。
示例性的，参见图5中的HARQ进程14，DG资源关联的HARQ进程ID是单独的，因此，DG资源上传输的数据无法重传。发送终端只能向网络设备请求重传资源，时延较大。
问题3、可能会限制发送终端在某一时刻可用的HARQ进程数。
示例性的，参见图6，网络设备为发送终端分配了5个type1 CG，每个type1 CG支持的HARQ进程数为2，还为发送终端分配了2个type2 CG，每个type2 CG支持的HARQ进程数为2。若此时发送终端仅能用type2 CG传输数据，不能用type1 CG传输数据，那么发送终端此时只能用4个HARQ进程(即HARQ进程10至HARQ进程13)传输数据，限制了发送终端在该时刻可用的HARQ进程的数量，降低了数据的传输效率。
问题4、配置不合理，某些资源上上无法传输数据。
示例性的，参见图7，发送终端在HARQ进程10发送的数据，在T1时刻才接收到该数据的ACK。在HARQ进程11发送的数据，在T2时刻才接收到该数据的ACK，那么图中圈出的两个侧行授权(分别关联HARQ进程10和HARQ进程11)上无法传输数据，造成资源浪费。
问题5、存在资源浪费。
假设发送终端在一个载波上最多支持16个HARQ进程，一种情况下，当16个HARQ进程被占用之后，发送终端若接收到某个HARQ进程上传输的数据的HARQ反馈，则可以释放该HARQ进程，在其他HARQ进程ID关联的HARQ进程上传输数据。示例性的，参见图8，发送终端若接收到HARQ进程0上传输的数据的ACK，发送终端释放HARQ进程0关联的HARQ进程，开始HARQ进程13。此时，每个HARQ进程都有可能用于进行数据传输。发送终端和接收终端为每个HARQ进程ID维护一个缓存(例如，HARQ buffer或soft buffer)，此时，缓存的开销是32个HARQ进程的缓存开销。
另一种情况下，当16个HARQ进程被占用之后，发送终端若接收到某个HARQ进程上传输的数据的HARQ反馈，发送终端不释放该HARQ进程，只能继续在与之前的HARQ进程ID相同的HARQ进程上进行数据传输。此时，终端最多只会采用32个HARQ进程ID中的16个HARQ进程ID关联的HARQ进程上进行数据传输，则意味着除这16个HARQ进程ID之外的HARQ进程ID关联的侧行授权无法被使用，从而造成资源浪费。
为了解决上述问题，本申请实施例提供了一种通信方法，如图9所示，包括：
901、第一终端确定与第一侧行授权关联的第一HARQ信息。
示例性的，第一侧行授权用于承载第一终端和第二终端之间的数据。第一终端为两个终端中的发送终端，第二终端为两个终端中的接收终端。
可选的，第一侧行授权为第一终端获得的SL传输资源中的一个侧行授权。
可选的，第一侧行授权属于第二资源，第二资源包括以下中的任一种类型或任几种类型的资源(此时可以认为只有第二资源中的侧行授权才允许第一终端为其确定关联的HARQ信息)：
1)SL的资源。
2)SL的第一模式的资源。
3)SL的CG资源。
4)SL的第一类型CG资源。
5)SL的第二类型CG资源。
6)SL的DG资源。
7)SL的第二模式的资源。
8)SL的CG资源集合，CG资源集合包括一个或多个CG资源索引对应的CG资源。
示例性的，第二资源可以包括：SL的第二模式的资源，或者，第二资源可以包括：SL的第一类型CG资源和SL的第二模式的资源，或者，第二资源可以包括SL的某个CG资源集合和SL的第二模式的资源。
示例性的，第二资源包括的资源的类型可以是网络设备配置给第一终端的，也可以是第一终端自己确定的，也可以是预配置的。
若第二资源包括的资源的类型是网络设备配置给第一终端的，该方法还可以包括: 网络设备生成用于配置第二资源包括的资源的类型的配置信息，并向第一终端发送该配置信息。相应的，终端从网络设备接收该配置信息，并根据该配置信息确定第二资源。第二资源可以用于第一终端和其他终端(例如，上述第二终端)之间的数据的传输。
可选的，网络设备在为第一终端配置第二资源包括的资源的类型时，可以针对每个逻辑信道(logical channel，LCH)或逻辑信道组(logical channel group，LCG)。此时，一个LCH或LCG可以对应一个第二资源，该LCH或LCG上的数据采用属于第二资源的侧行授权进行传输时，第一终端为该侧行授权确定关联的HARQ信息。
若第二资源包括的资源的类型是预配置的，则第二资源包括的资源的类型可以是协议规定的，也可以是设备厂商在第一终端出厂前存储在第一终端中的，还可以是第一终端连网时网络设备预先配置在第一终端中的。
可选的，第一HARQ信息包括以下内容中的任一项或任几项：
1)与第一侧行授权关联的第一HARQ进程ID。
2)与第一侧行授权关联的新数据指示(new data indication，NDI),NDI用于指示对应的传输为新传还是重传。
3)与第一侧行授权关联的RV，RV用于指示对应的数据所采用的RV。
4)与第一侧行授权关联的调制与编码策略(modulation and coding scheme，MCS)，MCS用于指示对应的数据所采用的MCS。
针对第一HARQ进程ID，第一终端可以自行确定与第一侧行授权关联的第一HARQ进程ID。该情况下，第一HARQ进程ID与第二HARQ进程ID可以相同也可以不同。第二HARQ进程ID为第一终端根据预设算法为第一侧行授权确定的HARQ进程ID或网络设备为第一侧行授权指示的HARQ进程ID。第一终端也可以采用预设算法计算与第一侧行授权关联的第一HARQ进程ID或网络设备为第一终端指示第一侧行授权关联的第一HARQ进程ID，此时，第一HARQ进程ID与上述第二HARQ进程ID是相同的。本申请实施例中，第一终端采用预设算法计算与侧行授权关联的HARQ进程ID时，该预设算法为网络设备计算侧行授权关联的HARQ进程ID时所采用的算法，例如，上述预设算法1或预设算法2。
针对NDI，NDI可能占用1bit。示例性的，可以通过NDI的翻转来标识新传，通过NDI未翻转来标识重传；或者，通过NDI的翻转来标识重传，通过NDI未翻转来标识新传。示例性的，也可以通过NDI为1指示新传，通过NDI为0指示重传；或者，通过NDI为1指示重传，通过NDI为0指示新传。第一终端自行确定与第一侧行授权关联的NDI，即第一终端自行确定第一侧行授权用于新传还是重传。
针对RV，第一终端自行确定与第一侧行授权关联的RV，即第一终端自行确定该第一侧行授权上发送的数据的RV。
针对MCS，第一终端自行确定与第一侧行授权关联的MCS，即第一终端自行确定第一侧行授权上传输数据所用的MCS。
可选的，在步骤901之前，该方法还包括：第一终端确定在第一侧行授权上有数据需要发送。
可选的，当第一侧行授权对应的LCH或LCG上有缓存数据时，第一终端确定在第 一侧行授权上有数据需要发送。
可选的，当消息3(MSG3)的缓存中有要传输的MAC PDU时，第一终端确定在第一侧行授权上有数据需要发送。
可选的，复用和组装实体(Multiplexing and assembly entity)中有要传输的MAC PDU时，第一终端确定在第一侧行授权上有数据需要发送。
902、第一终端通过SL向第二终端发送第一HARQ信息，SL为第一终端和第二终端之间的无线直连通信链路。
示例性的，第一HARQ信息可以携带在SCI或其他消息中。
可选的，在步骤902之后，该方法还包括：
903、第一终端采用第一侧行授权向第二终端发送数据。
示例性的，该数据可以是上述携带第一HARQ信息的SCI调度的。
本申请实施例提供的方法，第一终端可以自行确定侧行授权关联的HARQ进程ID，该情况下，第一终端可以根据需求确定侧行授权关联的HARQ进程ID，而不受网络设备的影响。
第一终端自行确定侧行授权关联的HARQ进程ID的方案，一方面，可以解决上述问题3。具体的，终端可以为不同的侧行授权关联不同的HARQ进程ID，例如，针对某些业务，或者，针对某些LCH的数据传输，若发送终端在一段通信时间内仅能用type2CG资源传输数据，不能用type1CG资源传输数据，发送终端最多支持N个HARQ进程，在该段通信时间内，则可以将N个HARQ进程全部用于type2CG资源上的传输。从而保证了在任意时刻，不管终端正在使用哪种类型的资源进行传输，都可以支持N个HARQ进程，提高了终端的传输效率。
另一方面，可以解决上述问题4，基于图7所示的示例，发送终端可以为图中圈出的HARQ进程10关联的侧行授权和图中圈出的HARQ进程10之前的HARQ进程10关联的侧行授权关联不同的HARQ进程ID，即可避免问题4。HARQ进程11同理。
另一方面，可以解决上述问题5。发送终端和/或接收终端为N个HARQ进程ID各维护一个缓存，但是同一个HARQ进程ID关联的侧行授权可以是属于不同的SL传输资源(例如，不同的CG资源)的，因此，可以避免缓存资源和传输资源的浪费。
由于HARQ进程ID的确定方式不同会导致本申请其他方案也有所不同，因此，本申请通过以下第一种方式(第一终端自行确定与侧行授权关联的HARQ进程ID)和第二种方式(第一终端采用预设算法计算与侧行授权关联的HARQ进程ID或网络设备为第一终端指示侧行授权关联的HARQ进程ID)对本申请中HARQ进程ID的确定方式作进一步的说明，并对第一种方式和第二种方式下本申请的其他技术方案作详细阐述。
第一种方式：第一终端自行确定(或者说自行选择)与侧行授权关联的HARQ进程ID。
第一终端自行确定与侧行授权关联的HARQ进程ID是指第一终端独立的确定侧行授权关联的HARQ进程ID，不受网络设备的影响。也就是说，第一终端和网络设备采用不同的规则或算法确定侧行授权关联的HARQ进程ID。
以第一侧行授权为例，第一种方式可以应用于以下场景1至场景4。
场景1：第一侧行授权抢占第二侧行授权。
场景1具体可以包括以下场景1.1和场景1.2。
场景1.1：第一侧行授权关联的第二HARQ进程ID与第二侧行授权关联的第七HARQ进程ID相同。
示例性的，第二HARQ进程ID为第一终端采用预设算法计算的与第一侧行授权关联的HARQ进程ID或网络设备为第一终端指示的第一侧行授权关联的HARQ进程ID。第七HARQ进程ID为第一终端采用预设算法计算的与第二侧行授权关联的HARQ进程ID或网络设备为第一终端指示的第二侧行授权关联的HARQ进程ID。
在场景1.1下，可选的，第一侧行授权为DG资源，第二侧行授权为CG资源。在第二侧行授权关联的HARQ进程还被占用的情况下，若第一终端接收到配置第一侧行授权的信息、且第一侧行授权关联的第二HARQ进程ID与第二侧行授权关联的第七HARQ进程ID相同，则可以认为第一侧行授权抢占第二侧行授权。
场景1.2：第一侧行授权与第二侧行授权在时域上重叠(overlap)。
此处的重叠可以为部分重叠或全部重叠。
在场景1.2下，可选的，第一侧行授权为DG资源，第二侧行授权为CG资源。若第一终端接收到配置第一侧行授权的信息、且第一侧行授权与第二侧行授权在时域上重叠，则可以认为第一侧行授权抢占第二侧行授权。
在场景1.1和场景1.2中，可选的，第一终端在PDCCH上接收配置第一侧行授权的信息，且PDCCH中的DCI通过无线网络临时标识(radio network tempory identity，RNTI)加扰。
在场景1下，第一种方式具体可以通过以下方式1或方式2实现。
方式1：第一终端将与第二侧行授权关联的第八HARQ进程ID确定为第一HARQ进程ID，即第八HARQ进程ID与第一HARQ进程ID相同。
示例性的，第八HARQ进程ID为第一终端自行确定的与第二侧行授权关联的HARQ进程ID。
需要说明的是，第一终端在确定与第二侧行授权关联的第八HARQ进程ID之后，会保存与第二侧行授权关联的对应关系，该对应关系为：第二侧行授权与第八HARQ进程ID的对应关系，或，第八HARQ进程ID与第七HARQ进程ID之间的对应关系，或，第二侧行授权、第八HARQ进程ID和第七HARQ进程ID之间的对应关系。当第一终端采用方式1确定第一HARQ进程ID之后，第一终端还可以执行以下步骤11)：
11)第一终端将与第二侧行授权关联的对应关系更新为与第一侧行授权关联的对应关系。
示例性的，可以将第二侧行授权与第八HARQ进程ID的对应关系更新为：第一侧行授权与第一HARQ进程ID的对应关系；或者，将第八HARQ进程ID与第七HARQ进程ID之间的对应关系更新为：第一HARQ进程ID与第二HARQ进程ID之间的对应关系；或者，将第二侧行授权、第八HARQ进程ID和第七HARQ进程ID之间的对应关系更新为：第一侧行授权、第一HARQ进程ID和第二HARQ进程ID之间的对应关系。
示例性的，本申请实施例中的更新具体可以为将原对应关系修改为新的对应关系或删除原对应关系再保存新的对应关系。
另外，当与第二侧行授权关联的对应关系中还包括第二侧行授权所属的资源的信 息时，更新后的与第一侧行授权关联的对应关系中也可以包括第一侧行授权所属的资源的信息。
示例性的，本申请实施例中的一个侧行授权(例如，第二侧行授权或第一侧行授权)所属的资源为以下中的一种:
1)SL的资源。
2)SL的第一模式的资源。
3)SL的CG资源。
4)SL的第一类型CG资源。
5)SL的第二类型CG资源。
6)SL的DG资源。
7)SL的第二模式的资源。
8)SL的CG资源索引所指示的资源。
9)SL的CG资源集合，CG资源集合包括一个或多个CG资源索引对应的CG资源。
示例性的，不同的侧行授权可以属于不同的资源。
示例性的，若第二侧行授权属于CG1资源，第一侧行授权属于CG2资源，则与第二侧行授权关联的对应关系可以为：CG1+第二侧行授权
Figure PCTCN2019109769-appb-000001
第八HARQ进程ID，或者，CG1+第七HARQ进程ID
Figure PCTCN2019109769-appb-000002
第八HARQ进程ID，或者，CG1+第二侧行授权+第七HARQ进程ID
Figure PCTCN2019109769-appb-000003
第八HARQ进程ID。更新后的与第一侧行授权关联的对应关系可以为：CG2+第一侧行授权
Figure PCTCN2019109769-appb-000004
第一HARQ进程ID，或者，CG2+第二HARQ进程ID
Figure PCTCN2019109769-appb-000005
第一HARQ进程ID，或者，CG2+第一侧行授权+第二HARQ进程ID
Figure PCTCN2019109769-appb-000006
第一HARQ进程ID。本申请实施例中
Figure PCTCN2019109769-appb-000007
用于表示具有对应关系的两个参数，其中，
Figure PCTCN2019109769-appb-000008
之前的参数和
Figure PCTCN2019109769-appb-000009
之后的参数之间具有对应关系。
方式2：第一终端将未被占用的一个HARQ进程的标识确定为第一HARQ进程ID。
示例性的，第一终端将N个HARQ进程中未被占用的一个HARQ进程的标识确定为第一HARQ进程ID。
可选的，若N个HARQ进程都被占用，第一终端不能再为第一侧行授权选择HARQ进程ID。
示例性的，N个HARQ进程为第一终端在一个载波上最多支持的HARQ进程，N为大于0的整数。
示例性的，N可以为8、16或其他值，具体可参考相关通信协议中的相关规定。示例性的，若第一终端在一个载波上最多支持16个HARQ进程，示例性的，HARQ进程0至HARQ进程2以及HARQ进程6至HARQ进程15关联的HARQ进程均被占用，则第一终端可以在HARQ进程3至HARQ进程5中选择一个确定为第一HARQ进程ID。
示例性的，第一终端可以在未占用的HARQ进程对应的HARQ进程ID中选择最小或最大的ID值作为第一HARQ进程ID。当然，也可以根据一些其他规则进行选择，本申请不作限制。
可选的，第一HARQ进程ID为大于等于0小于N的整数，N为第一终端在一个载波上最多支持的HARQ进程的个数。该情况下，可以解决上述问题1，当N＝16时，SCI中仅需要4个bit指示HARQ进程ID，当N＝8时，SCI中仅需要3个bit指示HARQ进 程ID，节省了SCI中HARQ进程ID所占的bit数。
可选的，在本申请实施例中，一个HARQ进程被占用包括以下情况中的任意一种或多种：
1)与该HARQ进程关联的数据传输还未完成或未结束，例如，一种场景为：在不进行HARQ反馈的情况下，第一终端利用该HARQ进程向其他终端发送数据，还未达到盲重传或重复传输(repetition)的次数。
2)第一终端未接收到该HARQ进程的反馈，例如，一种场景为：第一终端利用该HARQ进程向其他终端发送数据，第一终端还在等待接收来自其他终端的反馈，或者，第一终端在其他终端进行反馈的时机未接收到反馈信息。
3)第一终端接收到该HARQ进程的NACK，例如，一种场景为：第一终端利用该HARQ进程向其他终端发送数据，且第一终端接收到来自其他终端的NACK。
4)第一终端未接收到该HARQ进程的ACK，例如，一种场景为：第一终端利用该HARQ进程向其他终端发送数据，第一终端未接收到来自其他终端的ACK，可能接收到了NACK，可能任何反馈信息都没有收到。
5)第一终端未向网络设备反馈该HARQ进程的ACK。
6)与该HARQ进程关联的数据传输未达到最大传输时间或最大传输次数。
7)第一终端未释放该HARQ进程。
8)第一终端未清空该HARQ进程对应的HARQ buffer。
9)第一终端保存了或未释放与该HARQ进程关联的对应关系。
示例性的，与一个HARQ进程关联的对应关系是指：与该HARQ进程关联的侧行授权和与该HARQ进程关联的第一终端自行确定的HARQ进程ID之间的对应关系，或者，与该HARQ进程关联的第一终端自行确定的HARQ进程ID和与该HARQ进程关联的第一终端根据预设算法确定的(或网络设备为第一终端指示的)HARQ进程ID之间的对应关系，或者，与该HARQ进程关联的侧行授权、与该HARQ进程关联的第一终端自行确定的HARQ进程ID和与该HARQ进程关联的第一终端根据预设算法确定的(或网络设备为第一终端指示的)HARQ进程ID之间的对应关系。
可选的，在本申请实施例中，一个HARQ进程未被占用包括以下情况中的任意一种或多种：
1)与该HARQ进程关联的数据传输完成或结束，例如，一种场景为：在不进行HARQ反馈的情况下，第一终端利用该HARQ进程向其他终端发送数据，达到了盲重传或repetition的次数。
2)第一终端未接收到该HARQ进程的反馈，例如，一种场景为：第一终端与其他终端进行组播通信的情况下，且HARQ反馈为NACK only(即发送终端向接收终端发送数据后，若接收终端正确接收了该数据，接收终端不进行反馈，若接收终端接收该数据失败，接收终端向发送终端反馈NACK)的情况下，第一终端利用该HARQ进程向其他终端发送数据，第一终端在其他终端进行反馈的时机未接收到反馈信息，第一终端认为其他终端都正确接收了该数据。
3)第一终端接收到了该HARQ进程的ACK，例如，一种场景为：第一终端利用该HARQ进程向其他终端发送数据，第一终端接收到了来自其他终端的ACK，第一终端认为其他终端正确接收了该数据。
可选的，第一终端接收到了该HARQ进程的ACK，可以理解为第一终端仅接收到了该HARQ进程的ACK。示例性的，第一终端与其他终端进行组播通信的情况下，且HARQ反馈为ACK/NACK(发送终端向接收终端发送数据后，若接收终端正确接收了该数据，接收终端向发送终端反馈ACK，若接收终端接收该数据失败，接收终端向发送终端反馈NACK)的情况下，第一终端利用该HARQ进程向其他终端发送数据，第一终端仅接收到来自其他终端的ACK，第一终端认为其他终端都正确接收了该数据。
4)第一终端向网络设备反馈了该HARQ进程的ACK。例如，一种场景为：第一终端利用该HARQ进程向其他终端发送数据，第一终端确定该HARQ进程对应的数据传输成功(例如，接收到来自其他终端的ACK，或，未接收到来自其他终端的NACK)之后，向网络设备反馈ACK。
5)与该HARQ进程关联的数据传输达到了最大传输时间或最大传输次数。
6)第一终端释放了该HARQ进程。
7)第一终端清空了该HARQ进程对应的HARQ buffer。
8)第一终端未保存或释放了与该HARQ进程关联的对应关系。当第一终端采用方式2确定第一HARQ进程ID之后，第一终端还可以执行以下步骤21)：
21)第一终端保存与第一侧行授权关联的对应关系(记为第一对应关系)。
第一对应关系可以为：第一侧行授权和第一HARQ进程ID的对应关系、第一HARQ进程ID和第二HARQ进程ID之间的对应关系，或者，第一侧行授权、第一HARQ进程ID和第二HARQ进程ID之间的对应关系。
可选的，第一终端保存的第一对应关系中可以包括第一侧行授权所属的资源的信息。
示例性的，若第一侧行授权属于CG资源，则第一对应关系可以为：CG+第一侧行授权
Figure PCTCN2019109769-appb-000010
第一HARQ进程ID，或者，CG+第二HARQ进程ID
Figure PCTCN2019109769-appb-000011
第一HARQ进程ID，或者，CG+第一侧行授权+第二HARQ进程ID
Figure PCTCN2019109769-appb-000012
第一HARQ进程ID。再例如，若第一侧行授权属于CG1资源，则第一对应关系可以为：CG1+第一侧行授权
Figure PCTCN2019109769-appb-000013
第一HARQ进程ID，或者，CG1+第二HARQ进程ID
Figure PCTCN2019109769-appb-000014
第一HARQ进程ID，或者，CG1+第一侧行授权+第二HARQ进程ID
Figure PCTCN2019109769-appb-000015
第一HARQ进程ID。
需要说明的是，终端在确定一个侧行授权(例如，第一侧行授权)关联的HARQ进程ID之后，可以直接保存与该侧行授权关联的对应关系，也可以在满足以下条件中的一个或多个后，保存与该侧行授权关联的对应关系。
1)HARQ反馈开启。例如，当网络设备配置或第一终端配置HARQ反馈开启时，第一终端自行确定一个侧行授权关联的HARQ进程ID，且第一终端利用该HARQ进程ID与其他终端通信，第一终端接收到来自其他终端的该HARQ进程ID对应的NACK时，第一终端可能需要向网络设备请求重传资源，此时第一终端需要知道该HARQ进程ID对应的网络设备所能识别的HARQ进程ID，第一终端才能利用网络设备所能识别的HARQ进程ID去请求重传资源，此时需要保存与该侧行授权关联的对应关系。
2)第一终端需要向网络设备请求重传资源。例如，第一终端自行确定一个侧行授权关联的HARQ进程ID，且第一终端利用该HARQ进程ID与其他终端通信，第一终端接收到来自其他终端的该HARQ进程ID对应的NACK时，第一终端可能需要向网络设备请求重传资源，此时第一终端需要知道该HARQ进程ID对应的网络设备所能识别的HARQ进程ID，第一终端才能利用网络设备所能识别的HARQ进程ID去请求重传资源，此时需要保存与该侧行授权关联的对应关系。
3)第一终端需要向网络设备反馈SL上的传输状态。第一终端自行确定一个侧行授权关联的HARQ进程ID，且第一终端利用该HARQ进程ID与其他终端通信，第一终端接收到来自其他终端的该HARQ进程ID对应的NACK时，第一终端可能需要向网络设备请求重传资源，此时第一终端需要知道该HARQ进程ID对应的网络设备所能识别的HARQ进程ID，第一终端才能利用网络设备所能识别的HARQ进程ID去告知网络设备该HARQ进程上的传输失败，且可能向网络设备请求重传资源，或者，第一终端接收到来自其他终端的该HARQ进程ID对应的NACK时，第一终端可能需要向网络设备请求重传资源，此时第一终端需要知道该HARQ进程ID对应的网络设备所能识别的HARQ进程ID，第一终端才能利用网络设备所能识别的HARQ进程ID去告知网络设备该HARQ进程上传输成功，此时需要保存与该侧行授权关联的对应关系。
可选的，针对不同的侧行授权，第一终端都可以保存相应的对应关系，第一终端最多可以保存N条针对N个侧行授权的对应关系。
当第一终端采用方式2确定第一HARQ进程ID之后，第一终端还可以删除上述与第二侧行授权关联的对应关系，及时的释放存储资源，可以提高存储资源的利用率。
在场景1下，可选的，第一HARQ信息中的NDI指示对应的传输为新传。
场景2：第一侧行授权关联的第二HARQ进程ID与第六侧行授权关联的第十一HARQ进程ID相同、且第六侧行授权关联的HARQ进程未被占用。
示例性的，第十一HARQ进程ID为第一终端采用预设算法计算的与第六侧行授权关联的HARQ进程ID或网络设备为第一终端指示的第六侧行授权关联的HARQ进程ID。
在场景2下，第一种方式具体可以通过上述方式1或方式2实现。在根据方式1或方式2确定第一HARQ进程ID之后的方法与场景1是类似的，只需要将相应方法中的第二侧行授权理解为第六侧行授权即可，不再赘述。
场景3：第一侧行授权上传输的数据为第五侧行授权上传输的数据的重传。
在场景3下，第一种方式具体包括：第一终端将第五侧行授权关联的第九HARQ进程ID确定为第一HARQ进程ID，即第九HARQ进程ID与第一HARQ进程ID相同。
该种可能的实现方式，可以保证接收终端将同一个数据的新传和重传放到同一个缓存中进行处理，保证接收终端正确的解码数据。
示例性的，第九HARQ进程ID为第一终端自行确定的与第五侧行授权关联的HARQ进程ID。
示例性的，若第一终端在第五侧行授权上向第二终端传输数据1，第五侧行授权与第九HARQ进程ID关联，第一终端在第一侧行授权上重传该数据1(例如，由于第一终端接收到第二终端针对数据1的NACK，或，第一终端对该数据1进行盲重传等)，第一终端将第五侧行授权关联的第九HARQ进程ID确定为第一HARQ进程ID。
在场景3下，需要说明的是，第一终端在确定与第五侧行授权关联的第九HARQ进程ID之后，可以存储与第五侧行授权关联的对应关系，该对应关系可以为：第五侧行授权与第九HARQ进程ID的对应关系，或，第九HARQ进程ID与第十HARQ进程ID之间的对应关系，或，第五侧行授权、第九HARQ进程ID和第十HARQ进程ID之间的对应关系。示例性的，第十HARQ进程ID为第一终端采用预设算法计算的与第五侧行授权关联的HARQ进程ID或网络设备为第一终端指示的第五侧行授权关联的HARQ进程ID。当第一终端确定第一HARQ进程ID之后，第一终端还可以执行以下步骤31)：
31)第一终端将与第五侧行授权关联的对应关系更新为与第一侧行授权关联的对应关系。
示例性的，可以将第五侧行授权与第九HARQ进程ID的对应关系更新为：第一侧行授权与第一HARQ进程ID的对应关系；或者，将第九HARQ进程ID与第十HARQ进程ID之间的对应关系更新为：第一HARQ进程ID与第二HARQ进程ID之间的对应关系；或者，将第五侧行授权、第九HARQ进程ID和第十HARQ进程ID之间的对应关系更新为：第一侧行授权、第一HARQ进程ID和第二HARQ进程ID之间的对应关系。
另外，当与第五侧行授权关联的对应关系中还包括第五侧行授权所属的资源的信息时，更新后的与第一侧行授权关联的对应关系中也可以包括第一侧行授权所属的资源的信息。具体和对与第二侧行授权关联的对应关系更新时是类似的，可参见上文进行理解，不再赘述。
在场景3下，可选的，第一HARQ信息中的NDI指示对应的传输为重传。
场景4：除场景1、场景2和场景3之外的其他场景。
在场景4下，第一种方式具体可以通过上述方式2实现。
在场景4下，可选的，第一终端保存上述第一对应关系，保存上述第一对应关系的过程可参见上文，在此不再赘述。
第二种方式：第一终端采用预设算法计算与侧行授权关联的HARQ进程ID或网络设备为第一终端指示侧行授权关联的HARQ进程ID。
以第一侧行授权为例，第二种方式可以适用于上述场景1、场景2和场景3。
在上述场景1、场景2和场景3中，第二种方式在具体实现时，第一终端可以采用预设算法计算与第一侧行授权关联的第一HARQ进程ID或网络设备为第一终端指示第一侧行授权关联的HARQ进程ID。
当第一终端采用上述第一种方式或第二种方式确定第一HARQ进程ID之后，可能发生以下事件1(第一HARQ进程ID对应的HARQ进程结束)、事件2(第一侧行授权上传输的数据需要重传)或事件3(第四侧行授权抢占第一侧行授权)，以下对不同事件下本申请提供的方案作详细阐述。
事件1：第一HARQ进程ID对应的HARQ进程结束
可选的，第一HARQ进程ID对应的HARQ进程结束包括以下情况中的任意一种或多种：
1)第一终端未接收到与第一HARQ进程ID对应的HARQ进程的反馈，例如，一种场景为：第一终端与其他终端进行组播通信的情况下，且HARQ反馈为NACK only(发送终端向接收终端发送数据后，若接收终端正确接收了该数据，接收终端不进行反馈； 若接收终端接收该数据失败，接收终端向发送终端反馈NACK)的情况下，第一终端利用该HARQ进程向其他终端发送数据，第一终端在其他终端进行反馈的时机未接收到反馈信息，第一终端认为其他终端都正确接收了该数据。
2)第一终端接收到与第一HARQ进程ID对应的HARQ进程的ACK，例如，一种场景为：第一终端利用该HARQ进程向其他终端发送数据，第一终端接收到了来自其他终端的ACK，第一终端认为其他终端正确接收了该数据。
3)第一终端仅接收到与第一HARQ进程ID对应的HARQ进程的ACK，示例性的，一种场景为：第一终端与其他终端进行组播通信的情况下，且HARQ反馈为ACK/NACK(发送终端向接收终端发送数据后，若接收终端正确接收了该数据，接收终端向发送终端反馈ACK，若接收终端接收该数据失败，接收终端向发送终端反馈NACK)的情况下，第一终端利用该HARQ进程向其他终端发送数据，第一终端仅接收到来自其他终端的ACK，第一终端认为其他终端都正确接收了该数据。
4)第一终端向网络设备发送与第一HARQ进程ID对应的HARQ进程的ACK；例如，一种场景为：第一终端利用该HARQ进程向其他终端发送数据，第一终端确定该HARQ进程对应的传输成功(例如，接收到来自其他终端的ACK，或，未接收到来自其他终端的NACK)之后，向网络设备反馈ACK。
5)与第一HARQ进程ID对应的HARQ进程关联的数据传输达到最大传输时间，例如，定时器超时。
6)与第一HARQ进程ID对应的HARQ进程关联的数据传输达到最大传输次数。
7)第一终端释放第一HARQ进程ID对应的HARQ进程。
8)第一终端清空第一HARQ进程ID对应的HARQ进程对应的HARQ缓存。
9)其他侧行授权抢占了第一侧行授权。
10)与该HARQ进程关联的数据传输完成或结束，例如，一种场景为：在不进行HARQ反馈的情况下，第一终端利用该HARQ进程向其他终端发送数据，达到了盲重传或repetition的次数。
其中，本申请实施例中，一个侧行授权抢占另一个侧行授权的情况与上述第一侧行授权抢占第二侧行授权的情况是类似的，具体可参见上文中的相关部分进行理解，不再赘述。
在事件1下，可选的，该方法还包括：
41)第一终端将上述第一对应关系删除。
需要说明的是，第一终端也可以不删除上述第一对应关系，该情况下，在后续需要保存或更新与第一HARQ进程ID关联的对应关系时在第一对应关系的基础上进行更新即可。
事件2：第一侧行授权上传输的数据需要重传。
在事件2下，可选的，该方法还包括以下步骤51)至步骤53)：
51)第一终端获取用于重传数据的第三侧行授权。
在一种情况下，在步骤51)之前，该方法还包括：
50)第一终端从第二终端接收针对第一HARQ进程ID关联的HARQ进程的NACK。也就是说，第一终端在确定上述数据未传输成功的情况下获取用于重传上述数据的第 三侧行授权。
另一种情况下，第一终端对第一侧行授权上传输的数据进行重传(例如，盲重传，repetition)，第一终端获取用于重传上述数据的第三侧行授权。
52)第一终端将第一HARQ进程ID确定为第三侧行授权关联的HARQ进程ID。
53)第一终端向第二终端发送第二HARQ信息，第二HARQ信息包括：第三侧行授权关联的第一HARQ进程ID。
可选的，第二HARQ信息还包括：NDI信息、RV和MCS中的一个或多个。示例性的，该NDI信息用于指示对应的传输为重传。RV和MCS的作用以及确定方法与第一HARQ信息中的这些信息是类似的，区别仅在于此处针对的为第三侧行授权，具体可参见上文进行理解，不再赘述。
需要说明的是，步骤51)至步骤53)所示的方案可以为一个独立的方案，具体可参见发明内容第三方面所示的部分，关于该部分内容的相关解释可参见步骤51)至步骤53)的解释，不再赘述。
步骤51)至步骤53)所示的方案可以解决上述问题2，具体的，一个CG资源中的侧行授权上传输的数据可以采用该CG资源中的侧行授权进行重传，一个CG资源中的侧行授权上传输的数据也可以采用另一个CG资源中的侧行授权进行重传，从而可以保证重传时延。不同CG资源之间也可以共享HARQ进程ID。另外，DG资源上传输的数据也可以采用CG资源中的侧行授权进行重传。
可选的，在步骤53)之后，该方法还包括以下步骤54)：
54)第一终端采用第三侧行授权向第二终端重传上述数据。
可选的，在步骤52)之后，若第一终端采用上述第一种方式确定第一HARQ进程ID，该方法还包括：
61)第一终端将上述第一对应关系更新为与第三侧行授权关联的对应关系。
示例性的，当第一对应关系为第一侧行授权和第一HARQ进程ID的对应关系时，将第一对应关系更新为：第三侧行授权和第一HARQ进程ID的对应关系。
当第一对应关系为第一HARQ进程ID和第二HARQ进程ID之间的对应关系时，将第一对应关系更新为：第一HARQ进程ID和第四HARQ进程ID之间的对应关系。
当第一对应关系为第一侧行授权、第一HARQ进程ID和第二HARQ进程ID之间的对应关系时，将第一对应关系更新为：第三侧行授权、第一HARQ进程ID和第四HARQ进程ID之间的对应关系。
示例性的，第四HARQ进程ID为第一终端根据预设算法为第三侧行授权确定的HARQ进程ID或网络设备为第三侧行授权指示的HARQ进程ID。
可选的，第一侧行授权关联的第二HARQ进程ID与第三侧行授权关联的第四HARQ进程ID相同或不同。
另外，当第一对应关系中还包括第一侧行授权所属的资源的信息时，更新后的与第三侧行授权关联的对应关系中也可以包括第三侧行授权所属的资源的信息。具体和对与第二侧行授权关联的对应关系更新时是类似的，可参见上文进行理解，不再赘述。
可选的，在步骤52)之后，若第一终端采用上述第二种方式确定第一HARQ进程ID，该方法还包括：
71)第一终端保存与第三侧行授权关联的对应关系(记为第二对应关系)。
第二对应关系为：第三侧行授权和第一HARQ进程ID的对应关系，或者，第一HARQ进程ID和第四HARQ进程ID之间的对应关系，或者，第三侧行授权、第一HARQ进程ID和第四HARQ进程ID之间的对应关系。
可选的，第一终端保存的第二对应关系中包括第三侧行授权所属的资源的信息，具体与保存第一对应关系时是类似的，可参见上文进行理解，不再赘述。
可选的，步骤51)在具体实现时可以通过以下方式(1)或方式(2)或方式(3)实现。具体采用哪种方式可以是网络设备配置给第一终端的，也可以是第一终端自己确定的。
方式(1)：第一终端确定用于重传数据的第三侧行授权。
可选的，方式(1)具体包括：第一终端从第一资源内选择用于重传数据的第三侧行授权。
示例性的，第一资源包括以下中的任一种或任几种类型的资源：
1)SL的资源。
2)SL的第一模式的资源。
3)SL的CG资源。
4)SL的第一类型CG资源。
5)SL的第二类型CG资源。
6)SL的DG资源。
7)SL的第二模式的资源。
8)SL的CG资源集合，CG资源集合包括一个或多个CG资源索引对应的CG资源。
示例性的，第一资源可以包括：SL的第二模式的资源，或者，第一资源可以包括：SL的第二类型CG资源和SL的第二模式的资源，或者，第一资源可以包括SL的CG资源集合和SL的第二模式的资源。
示例性的，第一资源包括的资源的类型可以是网络设备配置给第一终端的，也可以是第一终端自己确定的。若为前者，该方法还包括:网络设备生成配置信息并向第一终端发送配置信息，配置信息用于配置第一资源包括的资源的类型。相应的，终端从网络设备接收配置信息，根据配置信息确定第一资源包括的资源的类型，进而根据网络设备之前为第一终端配置的SL传输资源确定第一资源，并在第一资源中确定用于重传数据的第三侧行授权。示例性的，若网络设备之前为第一终端配置了SL的第一类型CG资源、SL的第二类型CG资源和SL的DG资源，配置信息为第一终端配置的第一资源包括的资源的类型为：SL的第一类型CG资源,则第一终端在网络设备为第一终端配置的SL的第一类型CG资源中确定用于重传数据的第三侧行授权。
在一种情况下，网络设备可以针对每个LCH或LCG配置第一资源包括的资源的类型。此时，只有第一侧行授权上传输的数据为该LCH或LCG的数据时，第一终端才可以在该第一资源中为第一侧行授权选择重传资源。例如，某些LCH的重传只能用type1CG，此时，为该LCH配置的第一资源包括的资源的类型可以为type1CG。再例如，为LCG配置的第一资源包括的资源的类型可以为一个CG资源集合(例如，CG资源集合1)。
在另一种情况下，网络设备也可以针对每个第二资源包括的资源的类型配置第一 资源包括的资源的类型。例如，第二资源包括的资源的类型可以为一个CG资源集合，第一资源包括的资源的类型也可以为一个CG资源集合，这两个CG资源集合可以相同也可以不同。CG资源集合可以是针对某个业务配置的。示例性的，第二资源可以为type2CG资源，第一资源可以为type2CG资源和DG资源。Type2CG资源上的侧行授权进行的传输，第一终端可以从type2CG资源和DG资源中确定用于重传数据的第三侧行授权。
在另一种情况下，网络设备可以不针对任何参数配置第一资源包括的资源的类型，直接为第一终端配置某一个或某几个资源类型，该某一个或某几个资源类型指示的资源集合(例如，一个CG资源集合，或由多种类型的资源组成的资源集合)中的侧行授权可以共享HARQ进程ID或者说互相可以用于重传。此时，可以认为第一资源和第二资源为同样的资源，即第一资源和第二资源均为该某一个或某几个资源类型指示的资源集合。
另外，也可以为第一终端配置一些其他条件，例如，由于Type1CG资源是在紧急情况下使用的，因此，可以配置DG资源和/或Type2CG资源上的传输是否能使用type1CG的资源做重传。针对DG资源和/或Type2CG资源上的传输是否能使用type1CG的资源做重传，可以是预配置的，或网络设备配置的，或协议定义好的，该配置可以是针对每个LCH或每个LCG或每个第二资源而配置的。再例如，可以配置mode1和mode2的资源是否能将对方的资源作为重传资源。针对mode1和mode2的资源是否能将对方的资源作为重传资源，可以是预配置的，或网络设备配置的，或协议定义好的，该配置也可以是针对每个LCH或每个LCG或每个第二资源而配置的。
可选的，方式(1)在具体实现时，第一终端在选择第三侧行授权时，可以考虑下列因素中的任一个或任多个：
1)侧行授权的大小，例如，根据侧行授权是否能够容纳第一侧行授权上传输的数据判断是否考虑将该侧行授权作为第三侧行授权，若该侧行授权能够容纳第一侧行授权上传输的数据，即，能够利用该侧行授权进行第一侧行授权上传输的数据的重传，可以考虑将该侧行授权作为第三侧行授权。
2)侧行授权上是否有数据传输，例如，根据侧行授权上本来是否有数据传输判断是否考虑将该侧行授权作为第三侧行授权，若侧行授权上本来没有数据传输，可以考虑将该侧行授权作为第三侧行授权。
3)侧行授权上传输数据的优先级和第一侧行授权上传输的数据的优先级，例如，根据侧行授权上本来将要传输的数据的优先级和第一侧行授权上传输的数据的优先级比较，判断是否考虑将该侧行授权作为第三侧行授权，若侧行授权上本来要传输的数据的优先级比第一侧行授权上传输的数据的优先级低，可以考虑将该侧行授权作为第三侧行授权。
可选的，优先级包括服务质量(quality of service，QoS)信息，或，近距包粒度优先级(proSe per packet priority，PPPP)值，或，MAC PDU中逻辑信道的优先级，或，MAC PDU中最高优先级的逻辑信道的优先级等。
示例性的，在比较逻辑信道的优先级时，可以根据两个数据所在的逻辑信道的优先级进行比较，也可以根据两个数据所在的最高优先级的逻辑信道的优先级进行比较。
4)侧行授权与第一侧行授权之间的时间间隔，例如，根据侧行授权与第一侧行授权之间的时间间隔长短，判断是否考虑将该侧行授权作为第三侧行授权，若侧行授权与第一侧行授权之间的时间间隔较短(例如，小于第一阈值)，可以考虑该侧行授权作为第三侧行授权。
示例性的，第一阈值可以是预配置的，或者是网络设备为第一终端配置的，或者是通信协议规定的，或者是网络设备按照一定规则确定的并告知该第一终端的，或者是第一终端在出厂时定义的，具体本申请不做限定。
另外，在确定第三侧行授权时，也可以综合考虑上述4个因素中的多个因素。例如，第一终端可以将与第一侧行授权之间的时间间隔最短、侧行授权上本来没有数据传输、且能够容纳第一侧行授权上传输的数据的侧行授权确定为第三侧行授权。再例如，第一终端可以将与第一侧行授权之间的时间间隔最短、侧行授权上本来要传输的数据的优先级低于第一侧行授权上传输的数据的优先级、且能够容纳第一侧行授权上传输的数据的侧行授权确定为第三侧行授权。
可选的，需要说明的是，若第三侧行授权上本来有要传输的数据，第一侧行授权上传输的数据的重传抢占了原本要在第三侧行授权上新传的数据的资源，第一终端可以为本来要在第三侧行授权上新传的数据请求重传资源，也可以将该新传的数据继续作为待传输的新传数据量，此时，终端向网络设备请求资源时，上报的缓存状态报告(buffer status report，BSR)中包含该待传输的新传的数据的大小。
可选的，为了保证高优先级和低优先级的业务都能传输，可以为一个CG资源或一个CG资源集合设置重传占该CG资源或该CG资源集合的比例阈值或次数阈值，在一段时间内，若超过这个比例阈值或次数阈值，该CG资源或该CG资源集合就不能再用于重传，使得不总是让高优先级业务的重传抢占低优先级业务的新传。
示例性的，比例阈值或次数阈值可以是预配置的，或者是网络设备为第一终端配置的，或者是通信协议规定的，或者是网络设备按照一定规则确定的并告知该第一终端的，或者是第一终端在出厂时定义的，具体本申请不做限定。
方式(2)：第一终端向网络设备请求第三侧行授权。
方式(2)在具体实现时可以包括以下步骤81)和步骤82)：
81)第一终端向网络设备发送请求消息，请求消息用于向网络设备请求重传资源，该重传资源用于重传第一侧行授权上传输的数据，请求消息包括第二HARQ进程ID和/或第一侧行授权所属的资源的信息，或者，传输请求消息的资源与第二HARQ进程ID和/或第一侧行授权所属的资源关联。相应的，网络设备从第一终端接收请求消息。
示例性的，第一终端可以根据与第一侧行授权关联的对应关系确定第一侧行授权关联的第二HARQ进程ID和/或第一侧行授权所属的资源的信息。
82)网络设备根据请求消息向第一终端发送请求响应，请求响应中包括用于重传第一侧行授权上传输的数据的第三侧行授权的信息。相应的，第一终端从网络设备接收请求响应，根据请求响应确定第三侧行授权。
方式(3)、网络设备自行为第一终端配置重传上述数据的第三侧行授权。
可选的，方式(3)具体可以包括：网络设备启动与第一终端的第二HARQ进程ID或第一侧行授权关联的第一定时器，在第一定时器超时的情况下，若网络设备未接收 到针对第一HARQ进程传输的侧行数据的ACK时，网络设备向第一终端发送资源指示信息，资源指示信息用于指示重传第一侧行授权上传输失败的数据的SL传输资源(例如，第三侧行授权)。
在方式(3)中，网络设备可以为第一终端或第一终端的每个HARQ进程或第一终端的每个HARQ进程ID或第一终端的每个侧行授权或第一终端的一个bundle内的每个侧行授权维护一个定时器。网络设备接收到该定时器对应的传输的反馈(例如，ACK，或，NACK)时，网络设备重启或启动该定时器。若定时器超时，网络设备还没有接收到第一终端发送的该定时器对应的传输的反馈(例如，ACK)，网络设备给第一终端发送一个重传资源，并重启该定时器。
可选的，该定时器的时长取决于发送终端发送数据到接收终端接收到数据的时间、接收终端给发送终端反馈的时间和发送终端向网络设备反馈的时间。例如：该定时器大于等于“发送终端发送数据到接收终端接收到数据的时间+接收终端给发送终端反馈的时间+发送终端向网络设备反馈的时间”。
方式(3)可以作为一个独立的方案实现，具体可以参见发明内容中的第四方面的部分，关于该部分的相关描述可参见此处，不再赘述。
对于一个数据，若发生了多次重传，则多次重传所采用的侧行授权的获取方式可以相同(例如，均通过上述方式(1)或方式(2)或方式(3)获取)，也可以不同(例如，一部分通过上述方式(1)获取，另一部分通过上述方式(2)获取)，本申请不作限制。
事件3：第四侧行授权抢占第一侧行授权
在事件3下，该方法还可以包括：
91)第一终端确定与第四侧行授权关联的第三HARQ信息，第三HARQ信息中包括：与第四侧行授权关联的第五HARQ进程ID。
步骤91)在具体实现时，在第一种可能的实现方式中，第一终端可以将第一HARQ进程ID确定为与第四侧行授权关联的第五HARQ进程ID。
在第一种可能的实现方式下，该方法还可以包括：第一终端将与第一侧行授权关联的对应关系更新为：第四侧行授权和第五HARQ进程ID的对应关系；或者，第五HARQ进程ID和第六HARQ进程ID之间的对应关系；或者，第四侧行授权、第五HARQ进程ID和第六HARQ进程ID之间的对应关系。
示例性的，第六HARQ进程ID为第一终端根据预设算法为第四侧行授权确定的HARQ进程ID或网络设备为第四侧行授权指示的HARQ进程ID。
在第一种可能的实现方式下，可选的，更新的对应关系也可以包括第四侧行授权所属的资源的信息。具体可参见上文进行理解，不再赘述。
在第二种可能的实现方式中，第一终端可以采用与上述方式2类似的方式确定与第四侧行授权关联的第五HARQ进程ID。
在第二种可能的实现方式下，该方法还包括：第一终端保存与第四侧行授权关联的对应关系(记为第三对应关系)，第三对应关系为：第四侧行授权和第五HARQ进程ID的对应关系；或者，第五HARQ进程ID和第六HARQ进程ID之间的对应关系；或者，第四侧行授权、第五HARQ进程ID和第六HARQ进程ID之间的对应关系。
在第二种可能的实现方式下，可选的，保存的对应关系也可以包括第四侧行授权所属的资源的信息。具体可参见上文进行理解，不再赘述。
在第二种可能的实现方式下，可选的，第一终端删除与第一侧行授权关联的对应关系(例如，上述第一对应关系)。
在第三种可能的实现方式中，第一终端可以采用预设算法确定与第四侧行授权关联的第五HARQ进程ID或网络设备为第一终端指示第四侧行授权关联的第五HARQ进程ID。
步骤91)的具体实现中，确定与第四侧行授权关联的第三HARQ信息的过程，与第一侧行授权抢占第二侧行授权的场景下，确定与第一侧行授权关联的第一HARQ信息的过程类似，可以参见上文进行理解，不再赘述。
本申请上述实施例中，需要说明的是，在保存与一个侧行授权关联的对应关系时，该对应关系中包括的可以为第一终端自行确定的与该侧行授权关联的HARQ进程ID，也可以为第一终端自行确定的与该侧行授权关联的HARQ信息，上文中以对应关系中包括的为第一终端自行确定的与侧行授权关联的HARQ进程ID为例对本申请实施例提供的方法作示例性说明的，但是可以理解的是，上述对应关系中包括的第一终端自行确定的与侧行授权关联的HARQ进程ID也可以替换为第一终端自行确定的与该侧行授权关联的HARQ信息，例如，上述第一对应关系中的第一HARQ进程ID也可以替换为第一HARQ信息。同理，第一终端根据预设算法为该侧行授权确定的HARQ进程ID或网络设备为该侧行授权指示的HARQ进程ID可以替换为第一终端根据预设算法为该侧行授权确定的HARQ信息或网络设备为该侧行授权指示的HARQ信息，例如，上述第一对应关系中的第二HARQ进程ID也可以替换为第一终端根据预设算法为第一侧行授权确定的HARQ信息或网络设备为第一侧行授权指示的HARQ信息。另外，每个侧行授权关联的HARQ信息中都可以包括HARQ进程ID、NDI、RV和MCS中的一个或多个。
可选的，本申请上述实施例中，可以是第一终端的MAC实体、HARQ实体、HARQ进程维护(例如，保存、更新、删除)上述对应关系。
可选的，本申请上述实施例中，第一终端确定与第一侧行授权关联的第一HARQ信息可以是第一终端的MAC实体、HARQ实体、HARQ进程确定的。
以下通过一个具体的示例，对上述实施例中提供的方法作示例性说明。该示例中，N＝16。如图10所示，该过程包括：
1001、参见图11，第一终端确定在类型1CG5资源中的第一个侧行授权需要发送数据。
其中，图11中的小方框代表侧行授权，小方框右边的数字为该侧行授权对应的HARQ进程ID(预)，上面的数字为该侧行授权对应的HARQ进程ID(终)。其中，“HARQ进程ID(预)表示第一终端根据预设算法确定的HARQ进程ID，“HARQ进程ID(终)”表示终端自行确定的HARQ进程ID”。
此时，第一终端中存储的对应关系可以参见图12中的(a)。
1002、第一终端确定当前正在被占用的HARQ进程数是否小于16。
若是，执行步骤1003，若否，结束。
示例性的，若为图11所示的场景，当前正在被占用的HARQ进程数为4，即HARQ 进程0、HARQ进程1、HARQ进程2和HARQ进程3关联的HARQ进程被占用。
1003、第一终端从16个HARQ进程中的未被占用的HARQ进程中选择一个HARQ进程对应的HARQ进程ID作为该第一个侧行授权关联的HARQ进程ID。
基于图11所示的示例，示例性的，第一终端可以从HARQ进程4至HARQ进程15中选择HARQ进程4作为该第一个侧行授权关联的HARQ进程ID。
1004、第一终端存储该第一个侧行授权关联的HARQ进程ID(预)与HARQ进程ID(终)之间的对应关系。
在步骤1004之后，第一终端中存储的对应关系参见图12中的(b)。
1005、第一终端向第二终端发送该第一个侧行授权关联的HARQ信息，该HARQ信息包含HARQ进程ID(终)，并在该第一个侧行授权上向第二终端发送数据。
1006、第一终端接收针对该第一个侧行授权关联的HARQ进程ID(终)的HARQ反馈。
若该HARQ反馈为ACK，执行步骤1007；若该HARQ反馈为NACK(例如，基于图11所示的示例，参见图13，在T1接收到NACK)，执行步骤1008。
1007、第一终端删除该第一个侧行授权关联的HARQ进程ID(预)与HARQ进程ID(终)之间的对应关系。
示例性的，基于图12所示的示例，对该对应关系的删除可参见图14。
1008、第一终端获取用于重传上述数据的资源(记为重传侧行授权)。
示例性的，参见图13，第一终端可以确定类型1CG5资源中的第二个侧行授权为重传侧行授权。
1009、第一终端将重传侧行授权关联的HARQ进程ID确定为该第一个侧行授权关联的HARQ进程ID(终)。
示例性的，基于图13所示的示例，重传侧行授权关联的HARQ进程ID(终)为HARQ进程4(终)。
1010、第一终端将该第一个侧行授权关联的HARQ进程ID(预)与HARQ进程ID(终)之间的对应关系更新为该重传侧行授权关联的HARQ进程ID(预)与HARQ进程ID(终)之间的对应关系。
示例性的，基于图13所示的示例，更新后的对应关系可参见图15。
1011、第一终端向第二终端发送该重传侧行授权关联的HARQ信息，该HARQ信息包含该重传侧行授权关联的HARQ进程ID(终)，并在该重传侧行授权上向第二终端重传数据。另外，针对接收终端而言，一个接收终端可以和多个不同的发送终端通信。发送终端发送的数据通过SCI调度，发送终端通过携带在SCI中的HARQ进程ID告知接收终端发送数据时所采用的HARQ进程ID。不同的发送终端可能使用相同的HARQ进程ID和该接收终端通信，此时，不同的发送终端发送的SCI中的HARQ进程ID均相同。由于接收终端认为同一个HARQ进程ID上传输的数据对应的为同一个数据(例如，同一个数据的新传和重传)，因此，可能将不同的发送终端采用相同的HARQ进程ID发送的数据放到同一个HARQ buffer或soft buffer中进行软合并后解码，会造成解码错误。为了解决该问题，本申请实施例还提供了一种通信方法，参见图10A，包括：
1001A、接收终端接收SCI。
示例性的，接收终端可以从发送终端接收SCI。
示例性的，SCI中包括HARQ进程ID、NDI、RV、源标识(例如，层1源标识(Layer-1 source ID))，目的标识(例如，层1目的标识(Layer-1 destination ID))中的一个或多个。
示例性的，源标识可以用来标识一个单播或组播或广播通信的发送终端。目的标识可以用来标识一个单播或组播或广播通信的接收终端。
示例性的，可以通过源标识和目的标识来标识一个单播通信(此时，源标识可以为发送终端的标识，目的标识可以为接收终端的标识)或组播通信(此时，源标识可以为发送终端的标识，目的标识可以为组标识，接收终端为组内的全部终端)。
示例性的，可以通过一个目的标识来标识一个广播通信，此时，目的标识可以为广播业务标识，此时，接收终端为接收该广播业务数据的所有的终端。
1002A、接收终端为接收到的SCI选择接收HARQ进程。
针对每个发送终端发送的SCI，接收终端可以选择一个HARQ进程去接收该SCI调度的数据(例如，将该SCI调度的数据的新传和重传放到该HARQ进程对应的HARQ buffer或soft buffer中进行软合并后解码)。为了区分，发送终端发送数据时所采用的HARQ进程可以称为发送HARQ进程，相应的，发送HARQ进程的标识可以称为发送HARQ进程ID，接收终端接收数据时所采用的HARQ进程可以称为接收HARQ进程，相应的，接收HARQ进程的标识可以称为接收HARQ进程ID。
可选的，对于一个SCI，该SCI调度一个新传数据时，接收终端可以从未占用的HARQ进程中选择一个HARQ进程去接收该SCI调度的数据。
示例性的，接收终端未占用HARQ进程可以包括以下任一种或任几种情况：
1)该HARQ进程对应的数据传输未完成或未结束。
2)该HARQ进程对应的数据解码未成功。
3)接收终端还未向发送终端反馈该HARQ进程对应的ACK。
4)接收终端向发送终端反馈了该进程对应的NACK。
5)接收终端还未向发送终端反馈该HARQ进程对应的反馈，例如，接收终端在向发送终端反馈的时机，由于和其他传输的冲突，未能向发送终端反馈。
6)接收终端接收到该HARQ进程关联的数据的次数未达到最大传输次数，例如，接收终端接收到一个TB的次数未达到最大传输次数。
7)接收终端未接收到用于指示最后一次数据传输的指示。
8)该HARQ进程的传输未达到最大传输时间，例如，该HARQ进程对应的定时器未超时。1003A、接收终端保存与接收到的SCI关联的对应关系。
需要说明的是，由于不同的发送终端发送的数据一般是不同的，因此，当一个发送终端发送了一个新传数据之后，若接收终端接收到调度该数据的重传数据的SCI时，需要采用与该重传数据对应的新传数据关联的HARQ进程去处理该重传数据，为了保证接收终端将同一个终端发送的新传数据和重传数据放到同一个HARQ buffer或soft buffer中进行软合并后解码，接收终端可以存储以下对应关系中的任意一个对应关系：
1)SCI与接收HARQ进程(例如，接收HARQ进程ID)之间的对应关系。
2)SCI中的发送HARQ进程ID与接收HARQ进程(例如，接收HARQ进程ID)之间的对应关系。
3)SCI中的发送HARQ进程ID、源标识与接收HARQ进程(例如，接收HARQ进程ID)之间的对应关系。该对应关系可以区分不同的发送终端采用的HARQ进程ID。
4)SCI中的发送HARQ进程ID、源标识、目的标识与接收HARQ进程(例如，接收HARQ进程ID)之间的对应关系。其中，对于一个发送终端来说，与不同的接收终端进行通信或通过不同的连接进行通信时或与不同的组进行通信时可能使用不同的源标识，同理，对于一个接收终端来说，也可以使用不同的目的标识与不同的发送终端或通过不同的连接或与不同的组进行通信，该情况下，该对应关系可以精确的指示源终端和目的终端。
5)通信类型(cast-type)、SCI中的HARQ进程ID、SCI中的源标识、SCI中的目的标识与接收HARQ进程(例如，接收HARQ进程ID)之间的对应关系。其中，接收终端与不同的发送终端分别进行单播、组播通信时，单播通信和组播通信所使用的目的标识可能是相同的，该对应关系可以进一步区分通信类型，通信类型包括以下任一种或任几种：单播、组播、广播。
在接收终端保存上述对应关系的情况下，接收终端可以在接收到数据的重传时，找到对应的HARQ进程去处理接收到的重传数据。示例性的，参见图10B，发送终端1采用发送HARQ进程1向接收终端发送数据1，发送终端2也采用发送HARQ进程1向接收终端发送数据2，接收终端可以采用接收HARQ进程2接收发送终端1发送的数据1，采用接收HARQ进程3接收发送终端2发送的数据2，那么若接收终端又接收到发送终端1采用HARQ进程1向接收终端发送的数据1的重传时，接收终端采用接收HARQ进程2接收发送终端1发送的数据1的重传，并对数据1和数据1的重传进行软合并后解码。
可选的，接收终端可以在满足下列条件中的任一项或任几项时，删除上述对应关系。
1)接收终端成功解码该HARQ进程对应的数据。
2)接收终端将解码的MAC PDU传送给解组装和解复用(disassembly and demultiplexing)实体。
3)接收终端向发送终端反馈ACK。
4)接收终端未向发送终端反馈NACK。
5)接收终端接收到该HARQ进程关联的数据的次数达到最大传输次数，例如，接收终端接收到一个TB的次数达到最大传输次数。
6)接收终端接收到用于指示最后一次数据传输的指示，例如，接收终端接收到一个SCI，SCI中包含用于指示最后一次数据传输的指示，该指示用于指示该HARQ进程上的传输为最后一次传输。
7)该HARQ进程的传输达到最大传输时间，例如，该HARQ进程对应的定时器超时。
另外，接收终端在接收到一个SCI、该SCI中包含的信息与存储的对应关系中的信息全部相同、且该SCI调度的数据为新传数据(例如，该SCI中的NDI指示该SCI调度的数据为新传数据)时，可以不删除与该SCI关联的对应关系，直接采用该对应关系接收 该SCI调度的数据，也可以删除与该SCI关联的对应关系，并在未占用的HARQ进程中选择HARQ进程，去接收该SCI调度的数据。
目前，NR UL清空HARQ缓存时，对于用于新传的上行授权，在未获得要传输的MAC PDU时，清空相应的HARQ缓存。
本申请实施例提供了一种新的清空缓存的方法。
针对UL，参见图16，该方法包括：
1601、终端确定上行数据传输完成。
步骤1601在具体实现时，终端在上行数据传输达到最大重传次数，或者，上行数据传输达到最大传输时间，或者，配置授权定时器(configuredGrantTimer)超时时，确定上行数据传输完成。关于配置授权定时器的相关描述可参见3GPP TS 38.321:"NR；Medium Access Control(MAC)；Protocol specification".中的第5.4节。
1602、终端清空用于传输上行数据的HARQ进程对应的HARQ缓存。
针对SL，参见图17，该方法包括：
1701、针对一个HARQ进程，终端确定侧行数据传输完成，侧行数据传输完成包括侧行数据传输成功或侧行数据传输达到最大传输次数或侧行数据传输达到最大传输时间。
可选的，终端可以为每个HARQ进程维护一个HARQ缓存。
1702、终端清空用于传输侧行数据的HARQ进程对应的HARQ缓存。
可选的，侧行数据传输成功，包括以下任一种或任几种情况：
1)终端未接收到针对侧行数据的NACK，例如，在一种场景下，第一终端与其他终端进行组播通信的情况下，且HARQ反馈为NACK only(发送终端向接收终端发送数据后，若接收终端正确接收了该数据，接收终端不进行反馈，若接收终端接收该数据失败，接收终端向发送终端反馈NACK)的情况下，第一终端利用该HARQ进程向其他终端发送数据，第一终端在其他终端进行反馈的时机未接收到NACK，第一终端认为其他终端都正确接收了该数据。
2)终端接收到针对侧行数据的ACK，例如，在一种场景下，第一终端利用该HARQ进程向其他终端发送数据，第一终端接收到了来自其他终端的ACK，第一终端认为其他终端正确接收了该数据
3)终端接收到针对侧行数据的ACK，且未接收到针对侧行数据的NACK，在一种场景下，第一终端与其他终端进行组播通信的情况下，且HARQ反馈为ACK/NACK(发送终端向接收终端发送数据后，若接收终端正确接收了该数据，接收终端向发送终端反馈ACK，若接收终端接收该数据失败，接收终端向发送终端反馈NACK)的情况下，第一终端利用该HARQ进程向其他终端发送数据，第一终端仅接收到来自其他终端的ACK，第一终端认为其他终端都正确接收了该数据。
图16和图17所示的方法，可以在数据传输完成时清空HARQ缓存，从而节约缓存空间。
上述主要从方法的角度对本申请实施例的方案进行了介绍。可以理解的是，各个网元，例如，网络设备和终端为了实现上述功能，其包含了执行各个功能相应的硬件结构和软件模块中的至少一个。本领域技术人员应该很容易意识到，结合本文中所公 开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对网络设备和终端进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
示例性的，图18示出了上述实施例中所涉及的通信装置(记为通信装置180)的一种可能的结构示意图，该通信装置180包括处理单元1801和通信单元1802。可选的，还包括存储单元1803。通信装置180可以用于示意上述实施例中的终端和网络设备的结构。
当图18所示的结构示意图用于示意上述实施例中所涉及的终端的结构时，处理单元1801用于对终端的动作进行控制管理，例如，处理单元1801用于执行图9中的901至903(此时，终端为第一终端)，图9中的902和903(此时，终端为第二终端)，图10中的1001至1011，图10A中的1001A至1003A，图16中的1601和1602，图17中的1701和1702，和/或本申请实施例中所描述的其他过程中的终端执行的动作。处理单元1801可以通过通信单元1802与其他网络实体通信，例如，当该终端为第一终端时，与图9中的第二终端通信。存储单元1803用于存储终端的程序代码和数据。
当图18所示的结构示意图用于示意上述实施例中所涉及的网络设备的结构时，处理单元1801用于对网络设备的动作进行控制管理，例如，处理单元1801用于通过通信单元1802向第一终端发送用于配置第一资源包含的资源的类型的配置信息，和/或本申请实施例中所描述的其他过程中的网络设备执行的动作。处理单元1801可以通过通信单元1802与其他网络实体通信，例如，与第一终端通信。存储单元1803用于存储网络设备的程序代码和数据。
示例性的，通信装置180可以为一个设备也可以为芯片或芯片系统。
当通信装置180为一个设备时，所述处理单元可以是处理器；所述通信单元可以是通信接口、收发器，或，输入接口/输出接口。可选地，所述收发器可以为收发电路。可选地，所述输入接口/输出接口可以为输入电路/输出电路。
当通信装置180为芯片或芯片系统时，所述通信单元可以是该芯片或芯片系统上的通信接口、输入接口/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。所述处理单元可以是处理器、处理电路或逻辑电路等。
图18中的集成的单元如果以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。存储计算机软 件产品的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本申请实施例还提供了一种通信装置(记为通信装置190)的硬件结构示意图，参见图19或图20，该通信装置190包括处理器1901，可选的，还包括与处理器1901连接的存储器1902。
处理器1901可以是一个通用中央处理器(central processing unit，CPU)、微处理器、特定应用集成电路(application-specific integrated circuit，ASIC)，或者一个或多个用于控制本申请方案程序执行的集成电路。处理器1901也可以包括多个CPU，并且处理器1901可以是一个单核(single-CPU)处理器，也可以是多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路或用于处理数据(例如计算机程序指令)的处理核。
存储器1902可以是ROM或可存储静态信息和指令的其他类型的静态存储设备、RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，本申请实施例对此不作任何限制。存储器1902可以是独立存在(此时，处理器可以位于通信装置外，也可以位于通信装置内)，也可以和处理器1901集成在一起。其中，存储器1902中可以包含计算机程序代码。处理器1901用于执行存储器1902中存储的计算机程序代码，从而实现本申请实施例提供的方法。
在第一种可能的实现方式中，参见图19，通信装置190还包括收发器1903。处理器1901、存储器1902和收发器1903通过总线相连接。收发器1903用于与其他设备或通信网络通信。可选的，收发器1903可以包括发射机和接收机。收发器1903中用于实现接收功能的器件可以视为接收机，接收机用于执行本申请实施例中的接收的步骤。收发器1903中用于实现发送功能的器件可以视为发射机，发射机用于执行本申请实施例中的发送的步骤。
基于第一种可能的实现方式，图19所示的结构示意图可以用于示意上述实施例中所涉及的上述实施例中的终端和网络设备的结构。
当图19所示的结构示意图用于示意上述实施例中所涉及的终端的结构时，处理器1901用于对终端的动作进行控制管理，例如，处理器1901用于执行图9中的901至903(此时，终端为第一终端)，图9中的902和903(此时，终端为第二终端)，图10中的1001至1011，图10A中的1001A至1003A，图16中的1601和1602，图17中的1701和1702，和/或本申请实施例中所描述的其他过程中的终端执行的动作。处理器1901可以通过收发器1903与其他网络实体通信，例如，当该终端为第一终端时，与图9中的第二终端通信。存储器1902用于存储终端的程序代码和数据。
当图19所示的结构示意图用于示意上述实施例中所涉及的网络设备的结构时，处理器1901用于对网络设备的动作进行控制管理，例如，处理器1901用于通过收发器 1903向第一终端发送用于配置第一资源包含的资源的类型的配置信息，和/或本申请实施例中所描述的其他过程中的网络设备执行的动作。处理器1901可以通过收发器1903与其他网络实体通信，例如，与第一终端通信。存储器1902用于存储网络设备的程序代码和数据。
在第二种可能的实现方式中，处理器1901包括逻辑电路以及输入接口和输出接口中的至少一个。示例性的，输出接口用于执行相应方法中的发送的动作，输入接口用于执行相应方法中的接收的动作。
基于第二种可能的实现方式，参见图20，图20所示的结构示意图可以用于示意上述实施例中所涉及的上述实施例中的终端和网络设备的结构。
当图20所示的结构示意图用于示意上述实施例中所涉及的终端的结构时，处理器1901用于对终端的动作进行控制管理，例如，处理器1901用于执行图9中的901至903(此时，终端为第一终端)，图9中的902和903(此时，终端为第二终端)，图10中的1001至1011，图10A中的1001A至1003A，图16中的1601和1602，图17中的1701和1702，和/或本申请实施例中所描述的其他过程中的终端执行的动作。处理器1901可以通过输入接口和输出接口中的至少一个与其他网络实体通信，例如，当该终端为第一终端时，与图9中的第二终端通信。存储器1902用于存储终端的程序代码和数据。
当图20所示的结构示意图用于示意上述实施例中所涉及的网络设备的结构时，处理器1901用于对网络设备的动作进行控制管理，例如，处理器1901用于通过收发器1903向第一终端发送用于配置第一资源包含的资源的类型的配置信息，和/或本申请实施例中所描述的其他过程中的网络设备执行的动作。处理器1901可以通过输入接口和输出接口中的至少一个与其他网络实体通信，例如，与第一终端通信。存储器1902用于存储网络设备的程序代码和数据。
在实现过程中，本实施例提供的方法中的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
本申请实施例还提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述任一方法。
本申请实施例还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述任一方法。
本申请实施例还提供了一种通信系统，包括：上述多个终端(例如，第一终端和第二终端)，或者，上述终端(例如，第一终端)和网络设备，或者，上述多个终端和网络设备。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输， 例如，计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看附图、公开内容、以及所附权利要求书，可理解并实现公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (29)

  1. 一种通信方法，其特征在于，包括：
    第一终端确定与第一侧行授权关联的第一混合自动重传请求HARQ信息，其中，所述第一侧行授权用于承载所述第一终端和第二终端之间的数据，所述第一HARQ信息包括：所述第一侧行授权关联的第一HARQ进程标识；
    所述第一终端通过侧行链路向所述第二终端发送所述第一HARQ信息，所述侧行链路为所述第一终端和所述第二终端之间的无线直连通信链路。
  2. 根据权利要求1所述的方法，其特征在于，所述第一HARQ信息还包括：新数据指示信息，该新数据指示信息用于指示对应的传输为新传或重传。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一HARQ进程标识大于等于0小于N，N为所述第一终端在一个载波上最多支持的HARQ进程的个数，N为大于0的整数。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述第一终端确定与所述第一侧行授权关联的所述第一HARQ信息中的所述第一HARQ进程标识，包括：
    所述第一终端将所述第一终端在一个载波上最多支持的N个HARQ进程中的未被占用的一个HARQ进程的标识确定为所述第一HARQ进程标识；或者，
    在所述第一侧行授权抢占第二侧行授权的情况下，所述第一终端将所述第一终端确定的与所述第二侧行授权关联的HARQ进程标识确定为所述第一HARQ进程标识。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述方法还包括：
    所述第一终端保存所述第一侧行授权和所述第一HARQ进程标识之间的对应关系；或者，
    所述第一终端保存所述第一HARQ进程标识和第二HARQ进程标识之间的对应关系；或者，
    所述第一终端保存所述第一侧行授权、所述第一HARQ进程标识和第二HARQ进程标识之间的对应关系；
    其中，所述第二HARQ进程标识为所述第一终端根据预设算法为所述第一侧行授权确定的HARQ进程标识或网络设备为所述第一侧行授权指示的HARQ进程标识。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述方法还包括：
    所述第一终端获取用于重传所述数据的第三侧行授权；
    所述第一终端将所述第一HARQ进程标识确定为所述第三侧行授权关联的HARQ进程标识；
    所述第一终端向所述第二终端发送第二HARQ信息，所述第二HARQ信息包括：所述第三侧行授权关联的所述第一HARQ进程标识。
  7. 根据权利要求6所述的方法，其特征在于，所述第二HARQ信息还包括：新数据指示信息，该新数据指示信息用于指示对应的传输为重传。
  8. 根据权利要求6或7所述的方法，其特征在于，所述第一终端获取用于重传所述数据的第三侧行授权，包括：
    所述第一终端确定用于重传所述数据的第三侧行授权；或者，
    所述第一终端向所述网络设备发送请求消息，所述请求消息用于请求重传所述数 据的资源；所述请求消息包括所述第二HARQ进程标识，或者，传输所述请求消息的资源与所述第二HARQ进程标识关联；所述第一终端从所述网络设备接收请求响应，所述请求响应中包括用于指示所述第三侧行授权的信息。
  9. 根据权利要求8所述的方法，其特征在于，所述第一终端确定用于重传所述数据的第三侧行授权，包括：
    所述第一终端从第一资源内选择用于重传所述数据的所述第三侧行授权，所述第一资源包括以下中的任一种或任几种类型的资源：
    所述侧行链路的资源；
    所述侧行链路的第一模式的资源；
    所述侧行链路的第二模式的资源；
    所述侧行链路的配置授权资源；
    所述侧行链路的第一类型配置授权资源；
    所述侧行链路的第二类型配置授权资源；
    所述侧行链路的动态授权资源；
    所述侧行链路的配置授权资源集合，所述配置授权资源集合包括一个或多个配置授权资源索引对应的配置授权资源。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述第一终端接收所述网络设备的配置信息，所述配置信息用于配置所述第一资源包括的资源的类型。
  11. 根据权利要求6-10任一项所述的方法，其特征在于，所述第一侧行授权关联的所述第二HARQ进程标识与所述第三侧行授权关联的第四HARQ进程标识相同或不同，其中，所述第四HARQ进程标识为所述第一终端根据所述预设算法为所述第三侧行授权确定的HARQ进程标识或所述网络设备为所述第三侧行授权指示的HARQ进程标识。
  12. 根据权利要求6-11任一项所述的方法，其特征在于，所述方法还包括：
    所述第一终端将所述第一侧行授权和所述第一HARQ进程标识之间的对应关系更新为：所述第三侧行授权和所述第一HARQ进程标识之间的对应关系；或者，
    所述第一终端将所述第一HARQ进程标识和所述第二HARQ进程标识之间的对应关系更新为：所述第一HARQ进程标识和第四HARQ进程标识之间的对应关系；或者，
    所述第一终端将所述第一侧行授权、所述第一HARQ进程标识和所述第二HARQ进程标识之间的对应关系更新为：所述第三侧行授权、所述第一HARQ进程标识和第四HARQ进程标识之间的对应关系；
    其中，所述第四HARQ进程标识为所述第一终端根据所述预设算法为所述第三侧行授权确定的HARQ进程标识或所述网络设备为所述第三侧行授权指示的HARQ进程标识。
  13. 根据权利要求5-12任一项所述的方法，其特征在于，所述方法还包括：
    在所述第一HARQ进程标识对应的HARQ进程结束的情况下，所述第一终端将所述第一侧行授权和所述第一HARQ进程标识之间的对应关系，或者，所述第一HARQ进程标识和所述第二HARQ进程标识之间的对应关系，或者，所述第一侧行授权、所述第一HARQ进程标识和所述第二HARQ进程标识之间的对应关系删除。
  14. 根据权利要求13所述的方法，其特征在于，所述第一HARQ进程标识对应的 HARQ进程结束包括以下情况中的任意一种或多种：
    1)所述第一终端未接收到与所述第一HARQ进程标识对应的HARQ进程的反馈；
    2)所述第一终端接收到与所述第一HARQ进程标识对应的HARQ进程的肯定确认；
    3)所述第一终端仅接收到与所述第一HARQ进程标识对应的HARQ进程的肯定确认；
    4)所述第一终端向所述网络设备发送与所述第一HARQ进程标识对应的HARQ进程的肯定确认；
    5)与所述第一HARQ进程标识对应的HARQ进程关联的数据传输达到最大传输时间；
    6)与所述第一HARQ进程标识对应的HARQ进程关联的数据传输达到最大传输次数；
    7)所述第一终端释放所述第一HARQ进程标识对应的HARQ进程；
    8)所述第一终端清空所述第一HARQ进程标识对应的HARQ进程对应的HARQ缓存；
    9)其他侧行授权抢占了所述第一侧行授权；
    10)与所述第一HARQ进程标识对应的HARQ进程关联的数据传输完成或结束。
  15. 根据权利要求1-5任一项所述的方法，其特征在于，所述方法还包括：
    在第四侧行授权抢占所述第一侧行授权的情况下，所述第一终端确定与所述第四侧行授权关联的第三HARQ信息，所述第三HARQ信息中包括：与所述第四侧行授权关联的第五HARQ进程标识。
  16. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    所述第一终端将所述第一侧行授权和所述第一HARQ进程标识之间的对应关系更新为：所述第四侧行授权和所述第五HARQ进程标识之间的对应关系；或者，
    所述第一终端将所述第一HARQ进程标识和所述第二HARQ进程标识之间的对应关系更新为：所述第五HARQ进程标识和第六HARQ进程标识之间的对应关系；或者，
    所述第一终端将所述第一侧行授权、所述第一HARQ进程标识和所述第二HARQ进程标识之间的对应关系更新为：所述第四侧行授权、所述第五HARQ进程标识和第六HARQ进程标识之间的对应关系；
    其中，所述第六HARQ进程标识为所述第一终端根据所述预设算法为所述第四侧行授权确定的HARQ进程标识或所述网络设备为所述第四侧行授权指示的HARQ进程标识。
  17. 根据权利要求1-16任一项所述的方法，其特征在于，所述第一侧行授权属于第二资源，所述第二资源包括以下中的任一种或任几种类型的资源：
    所述侧行链路的资源；
    所述侧行链路的第一模式的资源；
    所述侧行链路的第二模式的资源；
    所述侧行链路的配置授权资源；
    所述侧行链路的第一类型配置授权资源；
    所述侧行链路的第二类型配置授权资源；
    所述侧行链路的动态授权资源；
    所述侧行链路的配置授权资源集合，所述配置授权资源集合包括一个或多个配置授权资源索引对应的配置授权资源。
  18. 根据权利要求1-17任一项所述的方法，其特征在于，在所述第一终端为第一侧行授权确定第一HARQ信息之前，所述方法还包括：
    所述第一终端确定在所述第一侧行授权上有数据需要发送。
  19. 一种通信方法，其特征在于，包括：
    网络设备生成配置信息，所述配置信息用于配置第一资源包括的资源的类型，所述第一资源用于所述第一终端和其他终端之间的数据的重传，所述第一终端和所述其他终端之间通过侧行链路通信，所述侧行链路为所述第一终端和所述其他终端之间的无线直连通信链路；
    所述网络设备向所述第一终端发送所述配置信息；
    其中，所述第一资源包括以下中的任一种或任几种类型的资源：
    所述侧行链路的资源；
    所述侧行链路的第一模式的资源；
    所述侧行链路的第二模式的资源；
    所述侧行链路的配置授权资源；
    所述侧行链路的第一类型配置授权资源；
    所述侧行链路的第二类型配置授权资源；
    所述侧行链路的动态授权资源；
    所述侧行链路的配置授权资源集合，所述配置授权资源集合包括一个或多个配置授权资源索引对应的配置授权资源。
  20. 根据权利要求19所述的方法，其特征在于，所述第一资源具体用于所述第一终端和所述其他终端之间的承载在第二资源上的数据的重传；
    所述第二资源包括以下中的任一种或任几种类型的资源：
    所述侧行链路的资源；
    所述侧行链路的第一模式的资源；
    所述侧行链路的第二模式的资源；
    所述侧行链路的配置授权资源；
    所述侧行链路的第一类型配置授权资源；
    所述侧行链路的第二类型配置授权资源；
    所述侧行链路的动态授权资源；
    所述侧行链路的配置授权资源集合，所述配置授权资源集合包括一个或多个配置授权资源索引对应的配置授权资源。
  21. 一种通信装置，其特征在于，包括：用于执行如权利要求1-18任一项所述方法的功能单元，所述功能单元所执行的动作通过硬件实现或通过硬件执行相应的软件实现。
  22. 一种通信装置，其特征在于，包括：用于执行如权利要求19或20所述方法的功能单元，所述功能单元所执行的动作通过硬件实现或通过硬件执行相应的软件实现。
  23. 一种通信装置，其特征在于，包括：处理器；
    所述处理器与存储器连接，所述存储器用于存储计算机执行指令，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述装置实现如权利要求1-18任一项所述的方法。
  24. 一种通信装置，其特征在于，包括：处理器；
    所述处理器与存储器连接，所述存储器用于存储计算机执行指令，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述装置实现如权利要求19或20所述的方法。
  25. 一种通信系统，其特征在于，包括：终端和/或网络设备，所述终端用于实现如权利要求1-18任一项所述的方法，所述网络设备用于实现如权利要求19或20所述的方法。
  26. 一种计算机可读存储介质，其特征在于，包括指令，当所述指令在计算机上运行时，使得所述计算机执行如权利要求1-18任一项所述的方法。
  27. 一种计算机可读存储介质，其特征在于，包括指令，当所述指令在计算机上运行时，使得所述计算机执行如权利要求19或20所述的方法。
  28. 一种计算机程序产品，其特征在于，包括指令，当所述指令在计算机上运行时，使得所述计算机执行如权利要求1-18任一项所述的方法。
  29. 一种计算机程序产品，其特征在于，包括指令，当所述指令在计算机上运行时，使得所述计算机执行如权利要求19或20所述的方法。
PCT/CN2019/109769 2019-09-30 2019-09-30 通信方法及装置 WO2021062840A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
KR1020227014653A KR20220072870A (ko) 2019-09-30 2019-09-30 통신 방법 및 장치
BR112022005581A BR112022005581A2 (pt) 2019-09-30 2019-09-30 Método e aparelho de comunicação
PCT/CN2019/109769 WO2021062840A1 (zh) 2019-09-30 2019-09-30 通信方法及装置
EP19947645.8A EP4030840A4 (en) 2019-09-30 2019-09-30 METHOD AND COMMUNICATION DEVICE
CN201980099873.3A CN114375602A (zh) 2019-09-30 2019-09-30 通信方法及装置
US17/706,961 US20220217768A1 (en) 2019-09-30 2022-03-29 Communication Method and Apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/109769 WO2021062840A1 (zh) 2019-09-30 2019-09-30 通信方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/706,961 Continuation US20220217768A1 (en) 2019-09-30 2022-03-29 Communication Method and Apparatus

Publications (1)

Publication Number Publication Date
WO2021062840A1 true WO2021062840A1 (zh) 2021-04-08

Family

ID=75336711

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/109769 WO2021062840A1 (zh) 2019-09-30 2019-09-30 通信方法及装置

Country Status (6)

Country Link
US (1) US20220217768A1 (zh)
EP (1) EP4030840A4 (zh)
KR (1) KR20220072870A (zh)
CN (1) CN114375602A (zh)
BR (1) BR112022005581A2 (zh)
WO (1) WO2021062840A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115516954A (zh) * 2020-03-26 2022-12-23 上海诺基亚贝尔股份有限公司 调度释放反馈

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3051736A1 (en) * 2015-01-30 2016-08-03 Panasonic Intellectual Property Corporation of America Prioritization in the logical channel prioritization procedure for sidelink logical channels in ProSe direct communications
CN107534982A (zh) * 2015-04-10 2018-01-02 Lg电子株式会社 用于在无线通信系统中考虑优先权来发送/接收d2d信号的方法及设备
CN107615844A (zh) * 2015-04-17 2018-01-19 松下电器（美国）知识产权公司 在侧行链路控制时段期间的多邻近服务组通信

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11025374B2 (en) * 2017-08-04 2021-06-01 Samsung Electronics Co., Ltd. Methods and apparatus for resource allocation and feedback in vehicle to vehicle communication

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3051736A1 (en) * 2015-01-30 2016-08-03 Panasonic Intellectual Property Corporation of America Prioritization in the logical channel prioritization procedure for sidelink logical channels in ProSe direct communications
CN107534982A (zh) * 2015-04-10 2018-01-02 Lg电子株式会社 用于在无线通信系统中考虑优先权来发送/接收d2d信号的方法及设备
CN107615844A (zh) * 2015-04-17 2018-01-19 松下电器（美国）知识产权公司 在侧行链路控制时段期间的多邻近服务组通信

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP TS 38.321
LG ELECTRONICS INC.: "HARQ Retransmission for NR Sidelink Mode 1", 3GPP DRAFT; R2-1907204 HARQ RETRANSMISSION FOR SIDELINK MODE 1, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, USA; 20190513 - 20190517, 13 May 2019 (2019-05-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051730647 *
See also references of EP4030840A4

Also Published As

Publication number Publication date
CN114375602A (zh) 2022-04-19
KR20220072870A (ko) 2022-06-02
EP4030840A4 (en) 2022-10-05
EP4030840A1 (en) 2022-07-20
US20220217768A1 (en) 2022-07-07
BR112022005581A2 (pt) 2022-06-21

Similar Documents

Publication Publication Date Title
US11804940B2 (en) Resources selection for feedback based NR-V2X communication
JP7124261B2 (ja) 上りリンク送信のための方法及び装置
US20240023202A1 (en) Method and apparatus for initiating radio resource control (rrc) connection for vehicle-to-everything (v2x) communication
WO2021032067A1 (zh) 用于传输混合自动重传请求harq反馈信息的方法和装置
JP6940121B2 (ja) データ伝送方法、機器およびシステム
WO2020143731A1 (zh) 用于传输数据的方法、通信设备和网络设备
CN114097257A (zh) 用于nr车辆通信的sl harq缓冲区管理
CN114097193A (zh) 用于无线通信系统中配置侧链路数据承载的方法和装置
WO2021056568A1 (zh) 发送和接收侧行控制信息的方法、终端装置和系统
WO2021031912A1 (zh) 一种处理侧行链路资源的方法、装置及系统
CN110582067B (zh) 一种应答信息的发送和接收方法、通信设备及网络设备
CN113875178B (zh) 一种通信方法及装置
WO2021168659A1 (zh) 信息发送方法、信息接收方法、装置、设备及存储介质
WO2021052467A1 (zh) 通信方法及装置
US20220217768A1 (en) Communication Method and Apparatus
JP7352647B2 (ja) リソース割り当て方法ならびにデバイス、記憶媒体および端末
CN113517960B (zh) 通信方法及装置
WO2021031017A1 (zh) 配置侧行链路的传输资源的方法和通信装置
WO2020228557A1 (zh) 一种通信方法及相关设备
WO2021142706A1 (zh) 资源冲突的解决方法、装置、终端和存储介质
WO2021030955A1 (zh) 通信处理方法以及通信处理装置
CN112822715A (zh) 信息传输的方法及设备
WO2022082800A1 (zh) 处理侧行链路进程的方法及装置
WO2024066975A1 (zh) 一种通信方法及装置
WO2024007123A1 (zh) 侧行数据的重传方法、harq进程的选择方法以及装置

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: 19947645

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112022005581

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20227014653

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019947645

Country of ref document: EP

Effective date: 20220412

ENP Entry into the national phase

Ref document number: 112022005581

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20220324