WO2023066175A1

WO2023066175A1 - Sidelink communication method and communication apparatus

Info

Publication number: WO2023066175A1
Application number: PCT/CN2022/125583
Authority: WO
Inventors: 李翔宇; 彭文杰
Original assignee: 华为技术有限公司
Priority date: 2021-10-21
Filing date: 2022-10-17
Publication date: 2023-04-27
Also published as: CN116017667A

Abstract

The present application provides a sidelink communication method. A sending terminal indicates, to a receiving terminal, a threshold value of the number of retransmission times of data of a sidelink between the sending terminal and the receiving terminal and/or a threshold value of the number of starting times of a retransmission scheduling timer. During a data transmission process, the receiving terminal and the sending terminal determine whether the number of retransmission times of data reaches the threshold value of the number of retransmission times, or whether the current number of starting times of the retransmission scheduling timer of a sidelink process associated with SCI corresponding to the transmitted data reaches the threshold value of the number of starting times. When the threshold value of the number of retransmission times or the threshold value of the number of starting times is reached, neither the sending terminal nor the receiving terminal starts the corresponding retransmission scheduling timers, otherwise both the sending terminal and the receiving terminal start the corresponding retransmission scheduling timers, thereby realizing the synchronization of starting or not starting the retransmission scheduling timers. Therefore, the power consumption and the reduction in the communication quality of a sidelink that are caused by asynchronous starting of retransmission scheduling timers are avoided.

Description

Method and device for sidelink communication

This application claims priority to a Chinese patent application with application number 202111228885.7 and titled "Method and communication device for sidelink communication" filed with the State Intellectual Property Office of China on October 21, 2021, the entire contents of which are incorporated by reference incorporated in this application.

technical field

The present application relates to the field of sidelink communication, and more specifically, to a sidelink communication method and communication device.

Background technique

In a wireless communication system, user equipment (user equipment, UE) can communicate directly with the UE without the aid of network equipment. A link between UEs is called a sidelink (sidelink, SL). Unicast, multicast, and broadcast are supported on the sidelink. Among them, the unicast and multicast communication of the sidelink supports hybrid automatic repeat request (HARQ) feedback, and a physical sidelink feedback channel (PSFCH) is introduced to transmit HARQ feedback. For a transmission, SL HARQ feedback also supports enabled and disabled, that is, if this transmission supports SL HARQ feedback, it is SL HARQ feedback enabled; if this transmission does not support SL HARQ feedback, it is SL HARQ feedback disabled. Known sidelink control information (sidelink control information, SCI) includes a first-level SCI (ie, the first stage SCI) and a second-level SCI (ie, the second stage SCI). Wherein, whether the SL HARQ feedback of one transmission is enabled or disabled is specifically indicated by the second-level SCI.

In addition, unicast communication and multicast communication support sidelink discontinuous reception retransmission scheduling timer (sidelinkdrx retransmission timer). In sidelink transmission that does not support HARQ feedback, there is no PSFCH transmission, or in other words, the receiving terminal does not give feedback to the transmitting terminal on whether the data is decoded successfully. This mechanism may cause the sending terminal and the receiving terminal to start asynchronously for the sidelink discontinuous reception retransmission scheduling timer. For example, in some cases, the sending terminal starts the sidelink discontinuous reception retransmission scheduling timer, but the receiving terminal does not start the sidelink discontinuous reception retransmission scheduling timer. In other cases, the sending terminal does not start the sidelink retransmission discontinuous reception scheduling timer, but the receiving terminal starts the sidelink discontinuous reception retransmission scheduling timer.

Due to the asynchronous start of the sidelink discontinuous reception retransmission scheduling timer between the sending terminal and the receiving terminal of the sidelink communication, it will bring some adverse effects, for example, affecting the power saving effect of the receiving terminal, Or greatly affect the quality of the sidelink communication.

Contents of the invention

This application provides a sidelink communication method, which can realize the synchronization of the sidelink retransmission scheduling timers of the sending terminal and the receiving terminal of the sidelink communication, thereby avoiding The problem of waste of power consumption caused by timer asynchronization or degradation of SL communication quality.

In a first aspect, a method for sidelink communication is provided, the method comprising:

The first terminal device sends the first information to the second terminal device, the first information is used to indicate the retransmission times threshold of the first sidelink data and/or the start times threshold of the retransmission scheduling timer, the first sidelink the link is a communication link between the first terminal device and the second terminal device;

The first terminal device sends sidelink control information SCI to the second terminal device through the first sidelink, where the SCI includes the identifier of the first sidelink process;

The first terminal device processes the retransmission scheduling timer or the retransmission waiting timer corresponding to the first sidelink process according to the first information.

In this technical solution, the sending terminal (that is, the first terminal) of the sidelink communication sends the first information to the receiving terminal (that is, the second terminal), so that the first terminal and the second terminal are pre-aligned with the first sidelink The retransmission times threshold of the data on the path (that is, the communication link between the first terminal and the second terminal) and/or the start times threshold of the retransmission scheduling timer. Subsequently, the first terminal and the second terminal may, according to the first information, the number of retransmission times of the data on the first sidelink reach the retransmission times threshold, and/or the number of starts of the retransmission scheduling timer associated with the SCI reaches In the case of the start times threshold, both the first terminal and the second terminal start the retransmission scheduling timer after the retransmission waiting timer of the corresponding sidelink process expires, or, when sending (for the first terminal) Or start the retransmission waiting timer after receiving (for the second terminal) the SCI. In this way, the synchronization between the first terminal and the second terminal for starting or not starting the retransmission scheduling timer is realized.

On the basis of starting or not starting the retransmission scheduling timer to achieve synchronization, it is possible to avoid some adverse effects caused by asynchrony between the first terminal and the second terminal due to the starting or not starting of the retransmission scheduling timer.

For example, in a scenario where the first terminal does not start the retransmission scheduling timer, but the second terminal starts the retransmission scheduling timer, the power consumption caused by the second terminal meaninglessly starting and running the retransmission scheduling timer can be avoided.

For another example, it is also possible to avoid the scenario where the first terminal starts the retransmission scheduling timer and schedules newly transmitted data within the running time of the retransmission scheduling timer, but the second terminal does not start the retransmission scheduling timer. The terminal may not be able to receive the newly transmitted data sent by the first terminal, resulting in a problem that communication quality of the SL is degraded.

With reference to the first aspect, in some implementation manners of the first aspect, the first terminal device processes the retransmission scheduling timer corresponding to the first sidelink process according to the first information, including:

According to the first information, if the first terminal device determines that the first condition is satisfied, after the retransmission wait timer corresponding to the first side link process expires, it does not start the retransmission corresponding to the first side link process dispatch timer; or,

According to the first information, if the first terminal device determines that the first condition is not met, after the retransmission wait timer corresponding to the first side link process expires, start the retransmission corresponding to the first side link process schedule timer,

Among them, the first condition includes at least one of the following:

The current number of retransmissions of data scheduled by the SCI reaches the retransmission threshold; or,

The current start times of the retransmission scheduling timer corresponding to the first sidelink process corresponding to the SCI reaches the start times threshold.

In this implementation, the first terminal does not start the retransmission scheduling timer if the first condition is met according to the first information, and on the contrary, starts the retransmission scheduling timer if the first condition is not met The timer can realize the synchronization between the first terminal and the second terminal for starting or not starting the retransmission scheduling timer.

With reference to the first aspect, in some implementation manners of the first aspect, the first terminal device processes the retransmission waiting timer corresponding to the first sidelink process according to the first information, including:

After the first terminal device determines that the first condition is met according to the first information, after sending the SCI, it does not start the retransmission waiting timer corresponding to the first sidelink process; or,

If the first terminal device determines that the first condition is not met according to the first information, after sending the SCI, start a retransmission waiting timer corresponding to the first sidelink process;

Among them, the first condition includes at least one of the following:

In this implementation, the first terminal does not start the retransmission waiting timer corresponding to the first sidelink process after sending the SCI if the first condition is met according to the first information; or, in If the first condition is not satisfied, after sending the SCI, the first terminal starts a retransmission waiting timer corresponding to the first sidelink process. By controlling whether to start or not to start the retransmission waiting timer, the first terminal and the second terminal can realize the synchronization of starting or not starting the retransmission scheduling timer.

With reference to the first aspect, in some implementations of the first aspect, the first information is for the first sidelink process, where the first terminal device includes multiple sidelink processes, and the first sidelink process The road process is a side link process in the plurality of side link processes.

In combination with the first aspect, in some implementations of the first aspect, the method further includes:

The first terminal device sends the first information to the access network device.

The first terminal device receives first information from the access network equipment.

In a second aspect, a method for sidelink communication is provided, and the method includes:

The second terminal device receives first information from the first terminal device, the first information is used to indicate the retransmission times threshold of the first sidelink data and/or the start times threshold of the retransmission scheduling timer, the first the sidelink is a communication link between the first terminal device and the second terminal device;

The second terminal device receives the sidelink control information SCI from the first terminal device through the first sidelink, and the SCI includes the identifier of the first sidelink process;

The second terminal device processes the retransmission scheduling timer or the retransmission waiting timer corresponding to the second sidelink process according to the first information, the second sidelink process is used to process the data scheduled by the SCI, the first A sidelink process is associated with the second sidelink process.

With reference to the second aspect, in some implementation manners of the second aspect, the second terminal device processes the retransmission scheduling timer corresponding to the second sidelink process according to the first information, including:

According to the first information, if the second terminal device determines that the first condition is satisfied, after the retransmission waiting timer corresponding to the second side link process expires, the second terminal device does not start the second side link process the corresponding retransmission scheduling timer; or,

According to the first information, if the second terminal device determines that the first condition is not met, after the retransmission waiting timer corresponding to the second sidelink process expires, start the second sidelink process The corresponding retransmission scheduling timer;

Among them, the first condition includes at least one of the following:

The current start times of the retransmission scheduling timer corresponding to the second sidelink process corresponding to the SCI reaches the start times threshold.

With reference to the second aspect, in some implementation manners of the second aspect, the second terminal device processes the retransmission waiting timer corresponding to the second sidelink process according to the first information, including:

If the second terminal device determines that the first condition is met according to the first information, after receiving the SCI, it does not start the retransmission waiting timer corresponding to the second sidelink process; or,

If the second terminal device determines that the first condition is not met according to the first information, after receiving the SCI, start the retransmission waiting timer corresponding to the second sidelink process;

Among them, the first condition includes at least one of the following:

With reference to the second aspect, in some implementation manners of the second aspect, the first information is for the first sidelink process.

The solutions in the second aspect are methods on the receiving terminal side corresponding to the solutions in the first aspect. Regarding the beneficial technical effects of the solutions in the second aspect, you can refer to the description of the corresponding solutions in the first aspect, and will not repeat them here.

In a third aspect, a method for sidelink communication is provided, and the method includes:

acquiring a first sidelink resource by the first terminal device;

The first terminal device determines a destination address, the destination address corresponds to the second terminal device, and the time domain of the first sidelink resource overlaps or partially overlaps with the activation time of the destination address,

Wherein, the activation time does not include the first duration, and the first duration is the running duration of the retransmission scheduling timer of the sidelink process of the destination address that does not support HARQ feedback, or,

The running time of the persistent timer of the destination address, the running time of the inactive timer, the running time of the retransmission scheduling timer of the sidelink process supporting HARQ feedback, or the first terminal device expects to receive the channel state information CSI report The duration of the period belongs to the activation time;

The first terminal device performs sidelink communication with the second terminal device according to the activation time.

In this technical solution, the first terminal does not consider the running time of the retransmission scheduling timer corresponding to the sidelink process that does not support HARQ feedback within the activation time, which prevents the first terminal from running the retransmission scheduling timer. The second terminal does not run the retransmission scheduling timer, which causes the problem that the first terminal cannot receive the newly transmitted data sent to the second terminal within the retransmission scheduling timer, which can improve the quality of SL communication.

With reference to the third aspect, in some implementations of the third aspect, within the running duration of the retransmission scheduling timer of the sidelink process that does not support HARQ feedback, if the first timer is in the running state, the The activation time includes the running duration of the first timer, where the first timer includes a persistence timer, an inactive timer, or a retransmission scheduling timer of a third sidelink process that supports HARQ feedback; or,

Within the running time of the retransmission scheduling timer of the sidelink process that does not support HARQ feedback, the first terminal device is in the state of expecting to receive the CSI report, and the activation time includes the first terminal device expecting to receive the CSI report The length of the report.

In combination with the third aspect, in some implementations of the third aspect, the method further includes:

the first terminal device acquires the second sidelink resource;

Wherein, the second sidelink resource is unavailable under the following circumstances:

The time domain of the second sidelink resource and the running duration of the persistent timer of any destination address, the running duration of the inactive timer, and the running of the retransmission scheduling timer of the sidelink process supporting HARQ feedback there is no overlap between the time duration or the time duration during which the first terminal device expects to receive the CSI report,

Wherein, the unavailable second side link resource includes that the second side link resource cannot be used for side link transmission, or the second side link resource cannot be used for side link The initial pass.

In a fourth aspect, a method for sidelink communication is provided, the method comprising:

The first terminal device sends sidelink control information SCI to the second terminal device, where the SCI includes the identifier of the first sidelink process;

The first terminal device determines whether the first sidelink process supports hybrid automatic repeat request (HARQ) feedback;

If the first sidelink process does not support HARQ feedback, the first terminal device does not start the retransmission waiting timer or retransmission scheduling timer corresponding to the first sidelink process;

If the first sidelink process supports HARQ feedback, the first terminal device starts a retransmission waiting timer or a retransmission scheduling timer corresponding to the first sidelink process.

In this technical solution, for a sidelink process that does not support HARQ feedback, the first terminal does not run the retransmission scheduling timer corresponding to the sidelink process, which can avoid retransmissions caused by the first terminal and the second terminal. The adverse effects caused by the asynchronous start (or operation) of the scheduling timer.

For example, it can avoid the problem that the second terminal may not receive the newly transmitted data sent by the first terminal because the first terminal does not run the retransmission scheduling timer, but the second terminal runs the retransmission scheduling timer, thereby improving SL communication quality.

In addition, power consumption caused by unnecessary running of the retransmission scheduling timer of the sidelink process that does not support HARQ feedback by the second terminal can also be avoided.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, in the case that the first sidelink process does not support HARQ feedback, the first terminal device does not start the restart corresponding to the first sidelink process Transmission waiting timer or retransmission scheduling timer, including:

When the first sidelink process does not support HARQ feedback, the first terminal device does not start the first sidelink process corresponding The retransmission scheduling timer of ; or,

If the first sidelink process does not support HARQ feedback, the first terminal device does not start the retransmission waiting timer corresponding to the first sidelink process after sending the SCI.

In this implementation, when the first sidelink process does not support HARQ feedback, after the retransmission waiting timer corresponding to the first sidelink process expires, the first terminal does not enable the first sidelink The retransmission scheduling timer corresponding to the uplink process; or, after sending the SCI, the retransmission waiting timer corresponding to the first side link process is not started. In these manners, the synchronization with the non-start of the retransmission scheduling timer with the second terminal can be realized.

With reference to the fourth aspect, in some implementations of the fourth aspect, when the first sidelink process supports HARQ feedback, the first terminal device starts retransmission waiting corresponding to the first sidelink process Timers or retransmission scheduling timers, including:

When the first sidelink process supports HARQ feedback, the first terminal device starts the retransmission corresponding to the first sidelink process when the retransmission waiting timer corresponding to the first sidelink process expires. pass scheduling timer; or,

In the case that the first sidelink process supports HARQ feedback, after sending the SCI, the first terminal device starts a retransmission waiting timer corresponding to the first sidelink process.

In this implementation, when the first side link process supports HARQ feedback, after the retransmission waiting timer corresponding to the first side link process expires, the first terminal starts the first side link process A corresponding retransmission scheduling timer; or, after sending the SCI, start a retransmission waiting timer corresponding to the first sidelink process. In these manners, synchronization with the start of the retransmission scheduling timer by the second terminal can be achieved.

In a fifth aspect, a method for sidelink communication is provided, the method comprising:

The second terminal device receives sidelink control information SCI from the first terminal device, where the SCI includes the identifier of the first sidelink process;

The second terminal device judges whether the second sidelink process supports Hybrid Automatic Repeat Request (HARQ) feedback, the second sidelink process is used to process SCI scheduled data, the second sidelink process and the first sidelink process One side uplink process association;

If the first sidelink process does not support HARQ feedback, the second terminal device does not start the retransmission waiting timer or retransmission scheduling timer corresponding to the first sidelink process; or,

If the first sidelink process supports HARQ feedback, the second terminal device starts a retransmission waiting timer or a retransmission scheduling timer corresponding to the first sidelink process.

With reference to the fifth aspect, in some implementations of the fifth aspect, if the first sidelink process does not support HARQ feedback, the second terminal device does not start retransmission waiting corresponding to the first sidelink process Timers or retransmission scheduling timers, including:

When the first sidelink process does not support HARQ feedback, the second terminal device does not Start a retransmission scheduling timer corresponding to the first sidelink process; or,

If the first sidelink process does not support HARQ feedback, the second terminal device does not start the retransmission waiting timer corresponding to the first sidelink process after receiving the SCI.

With reference to the fifth aspect, in some implementations of the fifth aspect, when the first sidelink process supports HARQ feedback, the second terminal device starts retransmission waiting corresponding to the first sidelink process Timers or retransmission scheduling timers, including:

When the first side link process supports HARQ feedback, the second terminal device starts the second terminal device when the retransmission waiting timer corresponding to the first side link process expires and fails to decode the data scheduled by the SCI. A retransmission scheduling timer corresponding to a downlink process; or,

In the case that the first sidelink process supports HARQ feedback, after receiving the SCI, the second terminal device starts a retransmission waiting timer corresponding to the first sidelink process.

The solutions in the fifth aspect are methods on the receiving terminal side corresponding to the solutions in the fourth aspect. Regarding the beneficial technical effects of the solutions in the fifth aspect, you can refer to the description of the corresponding solutions in the fourth aspect, and will not repeat them here.

In a sixth aspect, a communication device is provided, and the communication device has a function of implementing the method in the first aspect, the third aspect, or the fourth aspect, or any possible implementation manner of any one of these aspects. The functions described above may be implemented by hardware, or may be implemented by executing corresponding software on the hardware. The hardware or software includes one or more units corresponding to the above functions.

In a seventh aspect, a communication device is provided, and the communication device has a function of implementing the method in the second aspect or the fifth aspect, or any possible implementation manner of any one of these aspects. The functions described above may be implemented by hardware, or may be implemented by executing corresponding software on the hardware. The hardware or software includes one or more units corresponding to the above functions.

In an eighth aspect, a communication device is provided, including a processor and a memory. Optionally, a transceiver may also be included. Wherein, the memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory, and control the transceiver to send and receive signals, so that the communication device performs the first aspect, the third aspect or the fourth aspect, or these aspects A method in any possible implementation of any aspect.

Exemplarily, the communication device is a sending terminal for sidelink communication.

In a ninth aspect, a communication device is provided, including a processor and a memory. Optionally, a transceiver may also be included. Wherein, the memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory, and control the transceiver to send and receive signals, so that the communication device performs the second aspect or the fifth aspect, or any of these aspects A method in any possible implementation of an aspect.

Exemplarily, the communication device is a receiving terminal for sidelink communication.

In a tenth aspect, a communication device is provided, including a processor and a communication interface, the communication interface is used to receive data and/or information, and transmit the received data and/or information to the processor, and the processing The processor processes the data and/or information, and the communication interface is also used to output the data and/or information processed by the processor, so that as in the first aspect, the third aspect or the fourth aspect, or in these aspects A method in any possible implementation of any aspect is performed.

In an eleventh aspect, a communication device is provided, including a processor and a communication interface, the communication interface is used to receive data and/or information, and transmit the received data and/or information to the processor, the The processor processes the data and/or information, and the communication interface is also used to output the data and/or information processed by the processor, so that as in the second aspect or the fifth aspect, or any of these aspects A method in any possible implementation of is executed.

In a twelfth aspect, a computer-readable storage medium is provided, wherein computer instructions are stored in the computer-readable storage medium, and when the computer instructions are run on a computer, as in the first aspect, the third aspect or the fourth aspect, Or a method in any possible implementation of any of these aspects is performed.

In a thirteenth aspect, there is provided a computer-readable storage medium, wherein computer instructions are stored in the computer-readable storage medium, and when the computer instructions are run on a computer, such as in the second aspect or the fifth aspect, or in these aspects A method in any possible implementation of any aspect is performed.

In a fourteenth aspect, a computer program product is provided, the computer program product includes computer program code, when the computer program code is run on a computer, such as in the first aspect, the third aspect or the fourth aspect, or these A method in any possible implementation of any of the aspects is performed.

In a fifteenth aspect, there is provided a computer program product, the computer program product comprising computer program code, when the computer program code is run on a computer, such that as in the second aspect or the fifth aspect, or any of these aspects A method in any possible implementation of an aspect is performed.

A sixteenth aspect provides a wireless communication system, including the communication device according to the sixth aspect, and/or the communication device according to the seventh aspect.

Description of drawings

FIG. 1 is a schematic diagram of a communication scenario applicable to the technical solution of the present application.

Figure 2 is a schematic diagram of the transmission of SL HARQ feedback enabled.

Fig. 3 is a schematic diagram of the transmission of SL HARQ feedback disabled.

Figure 4 shows a possible situation of the transmission of SL HARQ feedback disabled.

Figure 5 shows another possible situation of the transmission of SL HARQ feedback disabled.

Fig. 6 is a schematic flowchart of a sidelink communication method provided by the present application.

FIG. 7 is a schematic diagram of another method for sidelink communication provided by the present application.

Figure 8 is a schematic diagram of the SL LCP process.

(a) of FIG. 9 is an example of the activation time corresponding to the destination address.

(b) of FIG. 9 is another example of the activation time corresponding to the destination address.

FIG. 10 is a schematic flowchart of another method for sidelink communication provided by the present application.

(a) of FIG. 11 is a schematic process for the sending terminal to process the timer corresponding to the sidelink process.

(b) of FIG. 11 is another schematic process for the sending terminal to process the timer corresponding to the sidelink process.

(a) of FIG. 12 is a schematic process for the receiving terminal to process the timer corresponding to the sidelink process.

(b) of FIG. 12 is another schematic process for the receiving terminal to process the timer corresponding to the sidelink process.

Fig. 13 is a schematic block diagram of a communication device provided in this application.

FIG. 14 is a schematic structural diagram of a communication device provided in the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

The technical solution of the present application can be applied to various wireless communication systems, including but not limited to long term evolution (long term evolution, LTE) system, new radio interface (new radio, NR) system and next generation wireless local area network system, etc.

In order to support direct communication between terminals, side link (sidelink, SL) communication is introduced. In SL communication, SL transmission is addressed through the source identifier and destination identifier of the medium access control (MAC) layer. In related technologies, multiple logical channels may be established between terminals performing SL communication for data transmission. After the terminal obtains the SL grant, it selects a logical channel to send data through a logical channel priority (logical channel prioritization, LCP) selection method.

In sidelink communication, in order to save power consumption of the terminal, the terminal configuration can be configured with discontinuous reception (DRX), hereinafter referred to as SL DRX. SL DRX means that the UE monitors the SCI (including first stage SCI and second stage SCI) within the specified active time, and does not need to monitor the SCI during the inactive time, and turns off the receiver to save power consumption.

The following introduces several timers related to SL DRX and their respective functions.

Sidelink drx on-duration timer (sidelink drx on-duration timer): It is used to define the duration of SL DRX activation time at the beginning of a cycle. It should be noted that the persistent timer runs periodically, and the persistent timer is started at the beginning of each SL DRX cycle. The UE needs to monitor the SCI during the activation time. .

Sidelink drx inactivity timer (sidelink drx inactivity timer): Whenever the UE is scheduled to transmit data, the UE will start the inactivity timer. The inactivity timer specifies how long the UE remains active after receiving an SCI indicating a new transmission. That is, whenever the UE has new data to be scheduled, the inactivity timer will be restarted once.

Additionally, unicast, multicast, and broadcast are supported on the sidelink. Among them, sidelink-drx-HARQ round-trip time timer (SL drx HARQ RTT timer) and sidelink discontinuous reception retransmission scheduling timing for unicast and multicast communication The sidelink retransmission timer is used for retransmission control.

Sidelink discontinuous reception retransmission scheduling timer: used to define the maximum duration of the UE until receiving data retransmission. Wherein, during the running time of the retransmission scheduling timer, the UE is in active time.

Sidelink discontinuous reception retransmission waiting timer: used to define the minimum duration before the UE expects to receive retransmission scheduling, and can also be considered as the waiting time between the UE receiving data and receiving the data retransmission of the data .

In the current communication standard, both the sending terminal and the receiving terminal maintain the SL HARQ RTT timer and the SL retransmission timer based on the sidelink process (ie, per sidelink process). Each SL process will be configured with an SL HARQ RTT timer and an SL retransmission timer.

Regarding the functions of SL HARQ RTT timer and SL retransmission timer, the following will explain whether the sidelink transmission supports HARQ feedback.

It can be understood that since this application relates to sidelink communication, the prefix of "sidelink discontinuous reception" in the names of the above timers is omitted in this article, for example, the sidelink discontinuous reception is continuously timed The device is referred to as the persistence timer, the sidelink discontinuous reception inactive timer is referred to as the active timer, and the sidelink discontinuous reception retransmission waiting timer is referred to as the HARQ RTT timer or the retransmission waiting timer. The sidelink discontinuous reception retransmission scheduling timer is referred to as retransmission timer or retransmission scheduling timer for short, and will not be described repeatedly below.

Referring to FIG. 1 , FIG. 1 is a schematic diagram of a communication scenario applicable to the technical solution of the present application. As shown in Figure 1, the technical solution of the present application is applicable to the scenario where UE performs sidelink (sidelink) communication based on SL DRX. The sending terminal of the sidelink communication can work in mode 1 (that is, mode 1), can also work in mode 2 (that is, mode 2), and can be in the radio resource control (radio resource control, RRC) connected state, RRC non-connected Active state, RRC idle state, or out of coverage (OOC) state. The communication between the sending terminal and the receiving terminal may be unicast communication or multicast communication.

In the above communication scenario, the access network device provides the configuration of the SL resource pool for the sending terminal. If the sending terminal works in mode1, the access network device can schedule SL resources for the sending terminal through downlink control information (DCI), or provide SL configuration authorization for the sending terminal through radio resource control (radio resource control, RRC) configuration (SL configured grant).

The sending terminal can work in mode1 or mode2. After obtaining SL authorization, the sending terminal uses SL resources to send data to the receiving terminal.

This application mainly involves terminals and access network equipment.

Terminal, also known as user equipment (UE), mobile station (mobile station, MS), mobile terminal (mobile terminal, MT), terminal equipment, etc., is a device that provides voice and/or data connectivity to users . In this application, a terminal particularly refers to a device capable of sidelink communication, for example, a vehicle-mounted terminal, or a handheld terminal capable of V2X communication.

Alternatively, in this application, the transmitting end of the sidelink communication is also referred to as the transmitting terminal, the transmitting UE (i.e. TX UE), the transmitting end UE, UE1 or the first terminal, and the receiving end is referred to as the receiving terminal, receiving UE (that is, the RX UE), the receiving end UE, UE2 or the second terminal.

An access network device refers to a node (or device) of a radio access network (radio access network, RAN) that connects a terminal to a wireless network, and may also be called a base station.

The unicast and multicast communication of the sidelink supports hybrid automatic repeat request (HARQ) feedback, and a physical sidelink feedback channel (PSFCH) is introduced to transmit HARQ feedback, that is, HARQ feedback is sent on PSFCH resources. For a transmission, SL HARQ feedback also supports enabled and disabled, that is, if this transmission supports SL HARQ feedback, it is SL HARQ feedback enabled; if this transmission does not support SL HARQ feedback, it is SL HARQ feedback disabled.

As mentioned above, both unicast communication and multicast communication of the sidelink link support SL HARQ RTT timer and SL retransmission timer. On the TX UE side and the RX UE side, SL HARQ RTT timer and SL retransmission timer are maintained per SL process.

See Fig. 2, Fig. 2 is a schematic diagram of the transmission of SL HARQ feedback enabled. As shown in Figure 2, for the transmission of SL HARQ feedback enabled, the RX UE will start the SL HARQ RTT timer at the symbol/slot (for example, the first symbol/slot) after the PSFCH transmission ends. If the PSFCH transmission is given low priority due to priority issues and no PSFCH is sent, the RX UE will still start the SL HARQ RTT timer at the symbol/slot (for example, the first symbol/slot) after the PSFCH resource ends. When the SL HARQ RTT timer times out, if the data of the corresponding SL process is not successfully decoded, for example, the PSFCH feedback is a negative acknowledgment (NACK), the RX UE will be in the symbol/slot after the SL HARQ RTT timer times out (for example , start the corresponding SL retransmission timer at the first symbol/slot).

The TX UE starts the HARQ RTT timer at the symbol/slot (for example, the first symbol/slot) after receiving PSFCH or PSFCH resources. When the HARQ RTT timer times out, and the HARQ feedback is NACK or no HARQ feedback is received, the TX UE will start the corresponding SL retransmission timer at the corresponding symbol/slot (for example, the first symbol/slot).

The following describes the transmission of SL HARQ feedback disabled in combination with FIG. 3 .

See Figure 3, which is a schematic diagram of the transmission of SL HARQ feedback disabled. Considering that SL HARQ feedback disabled cannot perform PSFCH transmission, one possible situation is that the RX UE starts the HARQ RTT timer at the symbol/slot (for example, the first symbol/slot) after receiving the SCI. When the HARQ RTT timer times out, if the data corresponding to the SL process is not successfully decoded, the RX UE will start the corresponding SL retransmission timer at the symbol/slot (for example, the first symbol/slot) after the SL HARQ RTT timer times out.

For the TX UE, start the HARQ RTT timer at the symbol/slot (for example, the first symbol/slot) after sending the SCI. When the HARQ RTT timer times out, because the TX UE cannot know whether the RX UE has successfully decoded the data scheduled by the SCI, the TX UE determines whether to start the corresponding SL retransmission timer based on the implementation. For example, if the TX UE thinks that it needs to continue to retransmit the data to the RX UE, then the retransmission timer will be started later. If the TX UE thinks that it is not necessary to continue to retransmit the data to the RX UE, the retransmission timer will not be started subsequently.

From the transmission situation of SL HARQ feedback disabled introduced in Figure 3, it can be found that for the transmission of SL HARQ feedback disabled, there may be a problem that the start of the retransmission timer on the TX UE side and the RX UE side is not synchronized, and this will cause some disadvantages The influence will be described in detail below in conjunction with Fig. 4 and Fig. 5 .

Referring to Figure 4, Figure 4 shows a possible situation of the transmission of SL HARQ feedback disabled. As shown in Figure 4, for SL DRX, if the RX UE does not successfully decode the data scheduled by SCI, after the SL HARQ RTT timer expires, the RX UE will start the SL retransmission timer in anticipation of receiving the retransmission of the data from the TX UE. However, TX UE does not need to continue to retransmit the data scheduled by SCI based on the implementation (for example, TX UE believes that RX UE has successfully decoded the data), then after SL HARQ RTT timer expires, TX UE will not start SL retransmission timer . Therefore, the TX UE does not run the SL retransmission timer and the RX UE runs the SL retransmission timer. This situation will increase the power consumption of RX UE and affect the power saving effect of RX UE.

Referring to Figure 5, Figure 5 shows another possible situation of the transmission of SL HARQ feedback disabled. As shown in Figure 5, the RX UE successfully decodes the data scheduled by SCI. After the SL HARQ RTT timer expires, the RX UE does not start the SL retransmission timer. Based on the implementation, the TX UE believes that it needs to continue to retransmit the data scheduled by SCI (for example, it believes that the RX UE has not successfully decoded the data), then after the SL HARQ RTT timer expires, the TX UE will start the SL retransmission timer. In this case, if the TX UE schedules the newly transmitted data (for example, the newly transmitted data of other SL process) within the running time of the SL retransmission timer, the RX UE may not be able to receive the newly transmitted data (for example, the retransmission timer runs When the RX UE does not have other active time timers running), the RX UE may not receive the newly transmitted data, and cannot start the inactivity timer or retransmission timer of the newly transmitted data, resulting in failure to receive Subsequent retransmission corresponding to the newly transmitted data. It can be seen that this situation will greatly affect the quality of sidelink communication.

This application provides some solutions for the adverse effects caused by the asynchronous start or non-start of the SL retransmission timer between the TX UE and the RX UE during the above-mentioned SL HARQ feedback disabled transmission.

The technical solutions provided by this application are introduced below.

Herein, the first terminal device and the second terminal device may be terminal devices, or chips installed in the terminal device, or devices, components or combinations thereof that can realize corresponding functions in the terminal device. In the following embodiments, description is made by taking the first terminal device and the second terminal device as terminal devices as an example.

This application provides three different solutions to realize the synchronization of starting or not starting the retransmission scheduling timer of the TX UE and the RX UE. It can be understood that, on the basis of realizing the synchronization of starting or not starting the retransmission scheduling timer, the above-mentioned problems caused by the starting or not starting of the retransmission scheduling timer out of synchronization can also be avoided.

plan 1

The TX UE and the RX UE pre-align the threshold of the number of retransmissions of the first side link or the threshold of the number of times of starting the retransmission scheduling timer, where the first side link refers to the communication link between the TX UE and the RX UE .

Alternatively, the number of retransmissions of the first sidelink may also be the number of transmissions of the first sidelink, and the transmission of the first sidelink includes initial transmission and retransmission.

Referring to FIG. 6 , FIG. 6 is a schematic flowchart of a sidelink communication method provided by the present application.

210. The first terminal sends the first information to the second terminal, and the second terminal receives the first information from the first terminal.

Wherein, the first information is used to indicate the retransmission times threshold of the first sidelink data and/or the start times threshold of the retransmission scheduling timer. The first sidelink is the communication link between the first terminal and the second terminal.

It is known that the first terminal needs to determine the destination address before sending the first information.

Optionally, the destination address may correspond to a unicast connection or a multicast group.

In unicast communication, when the TXUE sends data, it will send the source address (or source identifier) and destination address (or destination identifier) along with the data. Among them, the source address is allocated by the TX UE itself, and the destination address is the address allocated by the RX UE for the unicast connection.

If it is unicast communication, in step 210, the destination address of the first message sent by the TX UE corresponds to one RX UE. Correspondingly, the first information indicates the threshold of retransmission times of the sidelink data between the TX UE and the RX UE and/or the threshold of the number of times of starting the retransmission scheduling timer.

In the multicast communication, the creation of the multicast group corresponding to the multicast communication is completed at the upper layer (specifically, the layer above the access layer, for example, the PC5-S layer or the V2X layer). In multicast communication, when TX UE sends data, it will send the source address and destination address along with the data. The source address is allocated by TX UE itself, and the destination address is the address obtained by converting the multicast group ID.

If it is multicast communication, in step 210, the destination address of the TX UE sending the first information corresponds to a multicast group, or in other words, there are multiple second terminals. Therefore, the first information may correspond to the sidelink between the first terminal and any one of the multiple second terminals. Wherein, the threshold value of retransmission times indicated by the first information is the threshold value of the retransmission times of data on the sidelink link between the TX UE and an RX UE in the multicast group, or the threshold value of the number of times of starting is the threshold value of the number of retransmission times between the TX UE and the group The threshold value of the number of times the retransmission scheduling timer of the sidelink process associated with the SCI associated with the sidelink communication data of the RX UE in the broadcast group is started.

Exemplarily, the first information may be a value, and the value may be the number of HARQ retransmissions (selected number of HARQ retransmission) determined by resource selection or resource reselection when the first terminal is in mode2 or the number of HARQ retransmissions- 1 or the HARQ retransmission times +1.

Exemplarily, the first information is carried in the SL MAC CE, and the SL MAC CE is identified by a special SL logical channel identifier (logical channel identifier, LCID).

Optionally, the granularity of the first information may be based on a sidelink process (that is, per SL process), or in other words, the first information corresponding to different sidelink processes may be different. For example, the first terminal includes multiple sidelink processes, and for each sidelink process, the first information may be different.

Optionally, step 220 is included.

220. The access network device sends the first information to the first terminal, or the first terminal sends the first information to the access network device.

Exemplarily, the first information exchanged between the access network device and the first terminal is carried in RRC dedicated signaling.

Exemplarily, the first information is carried in a MAC CE, and the MAC CE is identified by a dedicated LCID.

Optionally, the granularity of the first information may be based on the UE (that is, per UE), the destination address (that is, per destination) or the HARQ process of the Uu interface (that is, Uu HARQ process). Likewise, the destination address can correspond to a unicast connection or a multicast group.

It should be noted that if the granularity of the first information is based on the Uu HARQ process (also directly referred to as the HARQ process), the TX UE needs to allocate an SL process to establish a mapping relationship with the Uu HARQ process, where the TX UE allocates The SL process is used to process the data of the first sidelink. In other words, if the first information received by the TX UE from the access network device is Uu HARQ process granularity, the TX UE will convert to per SL process granularity.

As an example of implementation, when the TX UE is in the RRC connection state, step 220 is performed.

As another implementation example, when the TX UE is configured to be in mode1, step 220 is performed.

230. The first terminal sends the SCI to the second terminal, and the second terminal receives the SCI from the first terminal.

Wherein, the SCI includes the identifier of the first sidelink process of the first terminal (for example, sidelink process identifier, SL process ID), wherein, the first sidelink process is allocated by the first terminal for processing the first terminal A sidelink process for the first sidelink data between the second terminal and the second terminal.

240. The first terminal processes a retransmission scheduling timer or a retransmission waiting timer corresponding to the first sidelink process according to the first information. The second terminal processes the retransmission scheduling timer or the retransmission waiting timer corresponding to the second sidelink process according to the first information.

Wherein, the second sidelink process is a sidelink process allocated by the second terminal for processing data scheduled by the SCI (specifically, the SCI received in step 230).

It should be understood that the first sidelink process is a sidelink process on the first terminal side, and is one of one or more sidelink processes on the first terminal side. The second sidelink process is a sidelink process on the second terminal side, and is one of one or more sidelink processes on the second terminal side. The first sidelink process is associated with the second sidelink process. Optionally, "association" may also be replaced with "correspondence" or "has a mapping relationship".

The process of processing the timer by the first terminal and the second terminal in step 230 will be described in detail below.

(1) The TX UE processes the timer corresponding to the first sidelink process.

In one implementation, the TX UE may process the retransmission scheduling timer corresponding to the first sidelink process, as follows:

The TX UE does not start the retransmission scheduling timing corresponding to the first side link process after the retransmission waiting timer corresponding to the first side link process expires after determining that the first condition is met according to the first information device; or,

According to the first information, if the TX UE determines that the first condition is not met, after the retransmission waiting timer corresponding to the first side link process expires, start the retransmission scheduling timing corresponding to the first side link process device,

Among them, the first condition includes at least one of the following:

It should be understood that, for the TX UE, the SCI mentioned in the first condition refers to the SCI sent by the TX UE in step 230.

In another implementation, the TX UE can handle the retransmission waiting timer corresponding to the first sidelink process, as follows:

The TX UE does not start the retransmission waiting timer corresponding to the first side link process after sending the SCI according to the first information, if it determines that the first condition is met; or,

The TX UE starts the retransmission waiting timer corresponding to the first side link after sending the SCI according to the first information, if it determines that the first condition is not met;

Among them, the first condition includes at least one of the following:

Exemplarily, the TX UE starts or does not start the retransmission waiting timer corresponding to the first sidelink process at a symbol (symbol) or a time slot (slot) after sending the SCI. For example, the symbol may be the first symbol after the SCI is sent, or the time slot may be the first time slot after the SCI is sent.

For the RX UE, the SCI mentioned in the first condition refers to the SCI received by the RX UE in step 230.

(2) The RX UE processes the timer corresponding to the second sidelink process.

In one implementation, the RX UE may process the retransmission scheduling timer corresponding to the second sidelink process, as follows:

The RX UE does not start the retransmission scheduling timing corresponding to the second side link process after the retransmission waiting timer corresponding to the second side link process expires after determining that the first condition is met according to the first information device; or,

According to the first information, if the RX UE determines that the first condition is not met, after the retransmission waiting timer corresponding to the second side link process expires, start the retransmission scheduling timing corresponding to the second side link process device,

Among them, the first condition includes at least one of the following:

The current start times of the retransmission scheduling timer of the second sidelink process corresponding to the SCI reaches the start times threshold.

In another implementation, the RX UE can handle the retransmission waiting timer corresponding to the second sidelink process, as follows:

The RX UE does not start the retransmission waiting timer corresponding to the second sidelink process after receiving the SCI when it determines that the first condition is met according to the first information; or,

According to the first information, if the RX UE determines that the first condition is not met, after receiving the SCI, it starts the retransmission waiting timer corresponding to the second sidelink process,

Among them, the first condition includes at least one of the following:

It can be understood that, the RX UE receives the SCI, the SCI contains the identifier of the first side link process, and the RX UE allocates the second side link process to process the data scheduled by the SCI, that is, the second side link process Associated with the first sidelink process. Therefore, for the RX UE, the SCI corresponds to the second sidelink process.

Exemplarily, the RX UE starts or does not start the retransmission waiting timer corresponding to the second sidelink process at a symbol (symbol) or a time slot (slot) after receiving the SCI. For example, the symbol may be the first symbol after receiving the SCI, or the slot may be the first slot after receiving the SCI.

Optionally, the TX UE or the RX UE, according to the first information, determines that the number of retransmissions of the data scheduled by the SCI reaches the threshold of the number of retransmissions indicated by the first information, and/or, the sidelink process corresponding to the SCI corresponds to The current number of starts of the retransmission scheduling timer reaches the start times threshold, or in other words, the TX UE or the RX UE determines that the current transmission of the data scheduled by the SCI is the last transmission (or the last retransmission) according to the first information. In the case of transmission), the TX UE or RX UE clears the HARQ buffer of the corresponding sidelink process. Specifically, the TX UE clears the HARQ buffer of the first side link process, and the RX UE clears the HARQ buffer of the second side link process.

In addition, optionally, if the first condition is met, if the access network device (for example, gNB) continues to schedule the retransmission of the first sidelink process of the TX UE, the TX UE will ignore the sidelink Authorization (SL grant).

It can be seen that in scheme 1, the TX UE and the RX UE pre-align the threshold of the number of retransmissions of the SL data and/or the threshold of the number of times the retransmission scheduling timer is started, and when the number of retransmissions of the data scheduled by the SCI reaches the TX The threshold of the retransmission times of the first side link between the UE and the RX UE, or the current start times of the retransmission scheduling timer of the side link process corresponding to the SCI reaches the start times threshold of the retransmission scheduling timer In this case, the TX UE and the RX UE do not start the retransmission scheduling timer after the retransmission waiting timer of the corresponding sidelink process expires, or do not start the retransmission waiting timer after sending or receiving the SCI. The number of retransmission times of the data scheduled by the SCI does not reach the threshold of the first sidelink data retransmission times, or the current start times of the retransmission scheduling timer of the sidelink process corresponding to the SCI does not reach the start times In the case of the threshold value, both the TX UE and the RX UE start the retransmission scheduling timer after the retransmission waiting timer of the corresponding sidelink process expires, or both start the retransmission waiting timer after sending or receiving the SCI. It can be found that the TX UE and the RX UE can achieve synchronization for starting or not starting the retransmission scheduling timer.

On the basis of starting or not starting the retransmission scheduling timer to achieve synchronization, it can avoid some problems caused by the asynchrony between the TX UE and the RX UE due to the starting or not starting of the retransmission scheduling timer.

For example, adopting scheme 1 can avoid the power consumption caused by the RX UE meaninglessly starting and running the retransmission scheduling timer in the scenario where the TX UE does not start the retransmission scheduling timer and the RX UE starts the retransmission scheduling timer.

In addition, using scheme 1, it can also avoid the scenario where the TX UE starts the retransmission scheduling timer and schedules new data transmission within the running time of the retransmission scheduling timer, while the RX UE does not start the retransmission scheduling timer. The UE may not be able to receive the newly transmitted data sent by the TX UE, which affects the communication quality of the SL.

Scenario 2

The TX UE will not support the running time of the retransmission scheduling timer corresponding to the sidelink process that does not support HARQ feedback as the activation time of the destination address. In other words, the activation time corresponding to the destination address determined by the TX UE does not include the running time of the retransmission scheduling timer corresponding to the sidelink process that does not support HARQ feedback.

Referring to FIG. 7 , FIG. 7 is a schematic diagram of another method for sidelink communication provided by the present application.

310. The TX UE acquires the first sidelink resource.

320. The TX UE determines the destination address, where the destination address corresponds to the RX UE, and the time domain of the first sidelink resource overlaps or partially overlaps with the activation time of the destination address.

Wherein, the activation time does not include the first duration, and the first duration is the running duration of the retransmission scheduling timer of the sidelink process of the destination address that does not support HARQ feedback; or,

The first duration is not part of the activation time; or,

The running time of the persistent timer of the destination address, the running time of the inactive timer, the running time of the retransmission scheduling timer corresponding to the sidelink process that supports HARQ feedback, or the time that the TX UE expects to receive the CSI report belongs to the active time ;or,

The activation time does not include the running time of the persistent timer, the running time of the inactive timer, the running time of the retransmission scheduling timer corresponding to the sidelink process supporting HARQ feedback, or the time the TX UE expects to receive the CSI report is active time.

Optionally, the length of time that the TX UE expects to receive the CSI report can also be implemented by a timer, for example, configure the second timer, when the TX UE expects to receive the CSI report, start the second timer, and run the second timer During the duration, the TX UE is in the state of waiting to receive the CSI report.

330. The TX UE performs sidelink communication with the RX UE according to the activation time.

Optionally, when the TX UE works in mode1 or mode2, scheme 2 is applicable.

In mode1, the TX UE obtains the SL authorization from the access network device, and then determines the destination address and LCH(s) of the transmission through the SL logical channel priority (logical channel prioritization, LCP) process for the SL authorization.

In mode2, the TX UE first obtains the SL authorization through resource selection (or resource reselection), and then determines the transmission destination address and LCH(s) through the SLLCP process for the SL authorization.

It can be seen that in mode1 or mode2, TX UE is involved in the SL LCP process. When the TX UE determines the destination address through the SL LCP process, the running time of the retransmission scheduling timer corresponding to the sidelink process that does not support HARQ feedback will not be considered in the activation time corresponding to the destination address.

It should be understood that when the TX UE is newly transmitting data, it needs to execute the SL LCP process, which will be described below with reference to FIG. 8 .

Referring to Fig. 8, Fig. 8 is the schematic diagram of SLL LCP process.

As shown in Figure 8, the SL LCP process includes two steps: TX UE selects the destination address (destination) and selects the logical channel LCH(s), as follows respectively step1 and step2:

step1: TX UE selects the destination address.

The TX UE selects the destination address corresponding to the LCH(s) or MAC CE with the highest priority and satisfying the second condition among the LCH(s) or MAC CE associated with unicast, multicast or broadcast.

Exemplarily, the second condition may include one or more of the following:

There is valid SL transmission data, SB _j is greater than 0, SL-CG type1 is allowed (if the SL grant is configured grant type1), etc.

step2: TX UE selects LCH(s).

The TX UE selects the LCH(s) associated with the destination address selected in step1 and which satisfies the third condition.

Exemplarily, the third condition may include one or more of the following:

There is valid SL transmission data, SL-CG type1 is allowed (if SL grant is configured grant type1), and the HARQ feedback enable/disable attribute corresponding to the LCH selected in step1 is the same, etc.

It can be seen from the above SL LCP process that the LCH will first be configured as HARQ feedback enabled or disabled. When SL grant is not configured with PSFCH (that is, SL HARQ feedback cannot be supported), TX UE can only select LCHs with HARQ feedback disabled when selecting LCHs; when SL grant is configured with PSFCH, TX UE first selects the destination to determine the highest priority When selecting LCHs later, only the LCHs with the same HARQ feedback enabled/disabled attribute and the HARQ feedback enabled/disabled attribute of the highest priority LCH determined in the selected destination can be selected. That is to say, if the LCH with the highest priority determined by the destination is HARQ feedback enabled, only the LCHs with HARQ feedback enabled can be selected in the future; if the LCH with the highest priority determined by the destination is HARQ feedback disabled, then only LCHs with HARQ feedback disabled can be selected. Therefore, through the SL LCP process, it is finally determined whether the transmitted transport block (transport block, TB) is HARQ feedback enabled or HARQ feedback disabled.

Considering the state (i.e., running or not running) of the retransmission scheduling timer of the TX UE and the RX UE if not synchronized (e.g., the TX UE is running the retransmission scheduling timer while the RX UE is not running), if the TX UE is retransmitting If the newly transmitted data is scheduled within the transmission scheduling timer, the RX UE may not receive the newly transmitted data, which will greatly reduce the communication quality of SL.

Before sending data, the TX UE acquires the first sidelink resource (ie, SL grant). Optionally, the TX UE may acquire the first side link resource based on the scheduling of the access network device, or the TX UE may acquire the first side link resource through sensing and/or resource selection in mode2. Further, the TX UE selects the destination address. When the TX UE selects the destination address through the SL LCP process, the time domain of the first side link resource needs to overlap or partially overlap with the activation time of the destination address. In addition, the activation time does not include the running time of the SL retransmission timer of the SL process of the HARQ feedback disabled SL process of the destination address, that is, the activation time does not include the retransmission scheduling timer corresponding to the side link process of the destination address that does not support HARQ feedback In other words, the running time of the retransmission scheduling timer of the SL process of the destination address that does not support HARQ feedback does not belong to the activation time.

Alternatively, it can also be said that the activation time of the destination address includes the running time of the persistent timer (that is, SL on-duration timer) of the destination address, the running time of the inactive timer (that is, SL inactivity timer), and the support for HARQ The running time of the retransmission scheduling timer corresponding to the feedback sidelink process (that is, the SL retransmission timer of the SL process with HARQ feedback enabled) or the length of time that the RX UE expects to receive the channel state information (CSI) report.

It should be noted that the activation time does not include the running time of the retransmission scheduling timer corresponding to the sidelink process of the destination address that does not support HARQ feedback (for example, the first sidelink process). Within the running duration of the retransmission scheduling timer corresponding to the first sidelink process supporting HARQ feedback, if the first timer is in the running state, the activation time corresponding to the destination address includes the running duration of the first timer.

Optionally, the first timer includes a persistence timer, an inactivity timer, or a retransmission scheduling timer corresponding to a third sidelink process that supports HARQ feedback.

Referring to (a) and (b) of FIG. 9, (a) and (b) of FIG. 9 are schematic explanatory diagrams of the activation time corresponding to the destination address.

As shown in (a) of FIG. 9, (a) of FIG. 9 is an example of the activation time corresponding to the destination address.

The TX UE determines the destination address. The destination address corresponds to the sidelink process 1 that does not support HARQ feedback. If the running time T1 of the retransmission scheduling timer corresponding to the sidelink process 1 overlaps with the running time of the first timer, then The running duration T1 of the retransmission scheduling timer corresponding to the sidelink process 1 still belongs to the activation time.

As shown in (b) of FIG. 9, (b) of FIG. 9 is another example of the activation time corresponding to the destination address.

The TX UE determines the destination address. The destination address corresponds to the sidelink process 1 that does not support HARQ feedback. If the running time T1 of the retransmission scheduling timer corresponding to the sidelink process 1 and the running time T2 of the first timer exist Partially overlapping, the overlapping duration is T3. According to solution 2 proposed in this application, the running time T1 of the retransmission scheduling timer corresponding to the sidelink process 1 that does not support HARQ feedback does not belong to the activation time, but because the first timer is in the In the running state, therefore, T3 belongs to the activation time, and the time length corresponding to (T1-T3) within the running time T1 of the retransmission scheduling timer corresponding to the sidelink process 1 does not belong to the activation time.

In addition, within the running duration of the retransmission scheduling timer of the sidelink process that does not support HARQ feedback, if the TX UE is in the state of expecting to receive the CSI report, the activation time includes the duration of the TX UE expecting to receive the CSI report.

Optionally, the TX UE obtains the second side link resource, if the time domain of the second side link resource is compatible with the running time of the persistent timer of any destination address, the running time of the inactive timer, and supports HARQ feedback If there is no overlap between the running duration of the retransmission scheduling timer corresponding to the sidelink process or the duration that the TX UE expects to receive the CSI report, the second sidelink resource is unavailable.

Exemplarily, if the second side link resource is unavailable, the second side link resource needs to be ignored (ignored), or the second side link resource can only be used for SL retransmission. In other words, the unavailable second side link resource indicates that the second side link resource cannot be used for SL transmission or cannot be used for SL new transmission.

Optionally, the TX UE obtains the third side link resource, if the time domain of the third side link resource is compatible with the running time of the persistent timer of any destination address, the running time of the inactive timer, and supports HARQ feedback There is no overlap between the running duration of the retransmission scheduling timer corresponding to the sidelink process or the duration that the TX UE expects to receive the CSI report, but the third sidelink resource and the sidelink resource that does not support HARQ feedback If the running time of the retransmission scheduling timer corresponding to the link overlaps, the second side link resource can only be used for SL retransmission.

As mentioned above, in the above implementation of scheme 2, when the TX UE determines the destination address through the SL LCP process, the running time of the retransmission scheduling timer corresponding to the sidelink process that does not support HARQ feedback is not used as the destination address corresponding activation time.

Optionally, as another implementation, the method for the TX UE to determine the activation time corresponding to the destination address in the SL LCP can also be applied to the resource selection (or resource reselection) process of the TX UE. That is, when the TX UE performs resource selection (resource reselection), the running time of the retransmission scheduling timer corresponding to the sidelink process that does not support HARQ feedback is not used as the activation time of the destination address. In other words, the activation time determined by the TX UE for resource selection (resource reselection) does not include the running time of the retransmission scheduling timer corresponding to the sidelink process that does not support HARQ feedback. It can be understood that the resources include initial transmission resources and/or retransmission resources.

In solution 2, the TX UE will not support the HARQ feedback sidelink process corresponding to the running time of the retransmission scheduling timer regardless of the activation time, which prevents the TX UE from running the retransmission scheduling timer, while the RX UE does not Run the retransmission scheduling timer, resulting in the problem that the TX UE can not receive the newly transmitted data sent to the RX UE within the retransmission scheduling timer, which can improve the quality of SL communication.

Option 3

For sidelink processes that do not support HARQ feedback, TX UE and RX UE do not start the retransmission scheduling timer.

Considering that both the sidelink process that supports HARQ feedback and the sidelink process that does not support HARQ feedback may both support the retransmission waiting timer, on this basis, scheme 3 proposes that according to whether a sidelink process supports HARQ feedback to determine whether to start the retransmission scheduling timer corresponding to the sidelink process.

Referring to FIG. 10 , FIG. 10 is a schematic flowchart of another method for sidelink communication provided by the present application.

510. The TX UE sends an SCI to the RX UE, where the SCI includes the identifier of the first sidelink process.

520. The TX UE processes the retransmission scheduling timer or the retransmission waiting timer of the first sidelink process according to whether the first sidelink process supports HARQ feedback.

The RX UE processes the retransmission scheduling timer or the retransmission waiting timer of the second sidelink process according to whether the second sidelink process supports HARQ feedback.

Wherein, the second sidelink process is used to process data scheduled by the SCI. The second sidelink process is associated with the first sidelink process.

Step 520 will be described below for the TX UE and the RX UE respectively.

(1)TX UE

An implementation manner is shown in (a) of FIG. 11 , and (a) of FIG. 11 is a schematic process for the sending terminal to process the timer corresponding to the sidelink process.

The TX UE sends SCI, and the SCI includes the identifier of the first sidelink process. Optionally, if the first side link process supports HARQ feedback, the TX UE receives the HARQ feedback from the RX UE for whether the data scheduled by the SCI is successfully decoded, or, when the TX UE does not receive the HARQ feedback, The TX UE starts the retransmission waiting timer corresponding to the first sidelink process at the symbol or time slot after the PSFCH transmission ends (or after the PSFCH resource ends). When the retransmission waiting timer expires, the TX UE judges whether the first side link process supports HARQ feedback.

If the first side link process supports HARQ feedback, the TX UE starts the retransmission scheduling timer corresponding to the first side link process. Specifically, when the TX UE receives the HARQ feedback for the SCI scheduled data from the RX UE as NACK or the TX UE does not receive the HARQ feedback, the TX UE starts the retransmission scheduling timing corresponding to the first sidelink process device.

If the first side link process does not support HARQ feedback, the TX UE does not start the retransmission scheduling timer corresponding to the first side link process.

In particular, when the TX UE receives the HARQ feedback from the RX UE as an acknowledgment (acknowledgment, ACK), the TX UE does not start the retransmission corresponding to the first sidelink process after the retransmission waiting timer expires. The scheduling timer is transmitted instead of judging whether the first sidelink process supports HARQ feedback.

It should be understood that the steps corresponding to the dotted boxes in (a) of FIG. 11 represent optional situations.

Another implementation is shown in (b) of FIG. 11 . (b) of FIG. 11 is another schematic process for the sending terminal to process the timer corresponding to the sidelink process.

The TX UE sends SCI, and the SCI includes the identifier of the first sidelink process. After the TX UE sends the SCI, it judges whether the first sidelink process supports HARQ feedback.

If the first side link process supports HARQ feedback, the TX UE starts the retransmission waiting timer corresponding to the first side link process; if the first side link process does not support HARQ feedback, the TX UE does not start the first side link process The retransmission waiting timer corresponding to the uplink process.

(2) RX UE

An implementation manner is shown in (a) of FIG. 12 , and (a) of FIG. 12 is a schematic process for the receiving terminal to process the timer corresponding to the sidelink process.

The RX UE receives the SCI, and the SCI includes the identifier of the first sidelink process. Optionally, if the second sidelink process supports HARQ feedback, the RX UE sends to the TX UE the HARQ feedback for whether the data scheduled by the SCI is successfully decoded. The retransmission waiting timer corresponding to the second sidelink process is started at the symbol or time slot after the PSFCH transmission ends (or after the PSFCH resource ends). When the retransmission waiting timer expires and the data scheduled by the SCI is not successfully decoded, the TX UE determines whether the second side link process supports HARQ feedback.

If the second sidelink supports HARQ feedback, the RX UE starts the retransmission scheduling timer corresponding to the second sidelink. Specifically, when the RX UE fails to decode the data scheduled by the SCI (that is, the HARQ feedback sent by the RX UE is specifically NACK) or the RX UE does not send the HARQ feedback, the RX UE starts the second sidelink process corresponding to Retransmission scheduling timer.

If the second sidelink does not support HARQ feedback, the RX UE does not start the retransmission scheduling timer corresponding to the second sidelink.

In particular, when the HARQ feedback sent by the RX UE to the TX UE is ACK, the RX UE does not start the retransmission scheduling timer corresponding to the first sidelink process after the retransmission waiting timer expires, and no longer Determine whether the second sidelink process supports HARQ feedback.

Likewise, the steps corresponding to the dotted boxes in (a) of FIG. 12 represent optional situations.

Another implementation is shown in (b) of FIG. 12 . (b) of FIG. 12 is another schematic process for the receiving terminal to process the timer corresponding to the sidelink process.

The RX UE receives the SCI, and the SCI includes the identifier of the first sidelink process. After receiving the SCI, the RX UE determines whether the second sidelink process supports HARQ feedback.

If the second side link process supports HARQ feedback, the RX UE starts the retransmission waiting timer of the second side link process; if the second side link process does not support HARQ feedback, the RX UE does not start the second side link process The retransmission waiting timer corresponding to the link process.

In the above scheme 3, for the sidelink process that does not support HARQ feedback, TX UE and RX UE do not run the retransmission scheduling timer corresponding to the sidelink process, which can avoid retransmission due to TX UE and RX UE The start (or operation) of the scheduling timer is not synchronized, which may cause the RX UE to fail to receive the newly transmitted data sent by the TX UE, which can improve the communication quality of SL. In addition, it can also avoid the power consumption caused by the RX UE meaninglessly running the retransmission scheduling timer of the sidelink process that does not support HARQ feedback.

The sidelink communication method provided by the present application has been described in detail above, and the communication device provided by the present application will be introduced below.

Referring to FIG. 13 , FIG. 13 is a schematic block diagram of a communication device provided by the present application. As shown in FIG. 13 , the communication device 1000 includes a processing unit 1100 , a receiving unit 1200 and a sending unit 1300 .

Optionally, the communication device 1000 may correspond to the sending terminal in this embodiment of the present application.

In some solutions, each unit of the communication device 1000 is used to realize the following functions:

The sending unit 1300 is configured to send first information to the second terminal device, where the first information is used to indicate the retransmission times threshold of the first sidelink data and/or the start times threshold of the retransmission scheduling timer, The first sidelink is a communication link between the communication device and the second terminal device;

And, sending sidelink control information SCI to the second terminal device through the first sidelink, where the SCI includes the identifier of the first sidelink process

The processing unit 1100 is configured to process a retransmission scheduling timer or a retransmission waiting timer corresponding to the first sidelink process according to the first information.

Optionally, in one embodiment, the processing unit 1100 is specifically configured to:

According to the first information, when it is determined that the first condition is met, after the retransmission waiting timer corresponding to the first sidelink process expires, the first sidelink process is not started the corresponding retransmission scheduling timer; or,

According to the first information, if it is determined that the first condition is not met, after the retransmission waiting timer corresponding to the first sidelink process expires, start the first sidelink The retransmission scheduling timer corresponding to the road process,

Wherein, the first condition includes at least one of the following:

The current retransmission times of the data scheduled by the SCI reaches the retransmission times threshold; or,

According to the first information, when it is determined that the first condition is met, after sending the SCI, do not start the retransmission waiting timer corresponding to the first sidelink process; or,

According to the first information, when it is determined that the first condition is not met, after sending the SCI, start a retransmission waiting timer corresponding to the first sidelink process;

Wherein, the first condition includes at least one of the following:

Optionally, in an embodiment, the first information is for the first sidelink process, wherein the first terminal device includes multiple sidelink processes, and the first side The uplink process is a sidelink process in the plurality of sidelink processes.

Optionally, in an embodiment, the sending unit 1300 is further configured to send the first information to the access network device.

Optionally, in an embodiment, the receiving unit 1200 is further configured to receive the first information from the access network device.

In other solutions, each unit of the communication device 1000 is used to realize the following functions:

The processing unit 1100 is used for:

obtaining a first sidelink resource;

And, determine a destination address, the destination address corresponds to the second terminal device, and the time domain of the first sidelink resource overlaps or partially overlaps with the activation time of the destination address,

The running time of the persistent timer of the destination address, the running time of the inactive timer, the running time of the retransmission scheduling timer of the sidelink process supporting HARQ feedback, or the communication device expects to receive the channel state information CSI report The duration of the period belongs to the activation time;

Perform sidelink communication with the second terminal device based on the activation time.

Optionally, in an embodiment, within the running time of the retransmission scheduling timer of the sidelink process that does not support HARQ feedback, if the first timer is in the running state, the activation time includes the The running duration of the first timer, where the first timer includes a persistence timer, an inactivity timer, or a retransmission scheduling timer of a third sidelink process that supports HARQ feedback; or,

During the running time of the retransmission scheduling timer of the sidelink process that does not support HARQ feedback, the first terminal device is in the state of expecting to receive the CSI report, and the activation time includes the first terminal device expecting The duration of receiving the CSI report.

Optionally, in an embodiment, the processing unit 1100 is further configured to acquire a second sidelink resource;

The time domain of the second sidelink resource and the running duration of the persistent timer of any destination address, the running duration of the inactive timer, and the running of the retransmission scheduling timer of the sidelink process supporting HARQ feedback There is no overlap between the duration or the duration during which the first terminal device expects to receive the CSI report,

A sending unit 1300, configured to send sidelink control information SCI to the second terminal device, where the SCI includes the identifier of the first sidelink process;

A processing unit 1100, configured to determine whether the first sidelink process supports hybrid automatic repeat request (HARQ) feedback;

And, if the first sidelink process does not support HARQ feedback, do not start the retransmission waiting timer or retransmission scheduling timer corresponding to the first sidelink process;

If the first sidelink process supports HARQ feedback, start a retransmission waiting timer or a retransmission scheduling timer corresponding to the first sidelink process.

If the first sidelink process does not support HARQ feedback, if the retransmission waiting timer corresponding to the first sidelink process times out, do not start the first sidelink The retransmission scheduling timer corresponding to the process; or,

If the first sidelink process does not support HARQ feedback, after sending the SCI, the retransmission waiting timer corresponding to the first sidelink process is not started.

When the first side link process supports HARQ feedback, the first terminal device starts the first side link process when the retransmission waiting timer corresponding to the first side link process expires. The retransmission scheduling timer corresponding to the sidelink process; or,

If the first side link process supports HARQ feedback, the first terminal device starts a retransmission waiting timer corresponding to the first side link process after sending the SCI.

Optionally, the communication device 1000 may correspond to the receiving terminal in this embodiment of the present application.

The receiving unit 1200 is configured to receive first information from the first terminal device, where the first information is used to indicate the retransmission times threshold of the data of the first sidelink and/or the start times of the retransmission scheduling timer a threshold, the first sidelink being a communication link between the first terminal device and the second terminal device;

And, receiving sidelink control information SCI from the second terminal device through the first sidelink, where the SCI includes the identifier of the first sidelink process;

The processing unit 1100 is configured to process a retransmission scheduling timer or a retransmission waiting timer corresponding to a second sidelink process according to the first information, and the second sidelink process is used to process the SCI For scheduled data, the first sidelink process is associated with the second sidelink process.

Optionally, in one embodiment, the processing unit 100 is specifically configured to:

According to the first information, when it is determined that the first condition is met, after the retransmission wait timer corresponding to the second sidelink process expires, the second sidelink process is not started The corresponding retransmission scheduling timer; or,

According to the first information, when it is determined that the first condition is not met, after the retransmission waiting timer corresponding to the second sidelink process expires, start the second sidelink process The corresponding retransmission scheduling timer;

Wherein, the first condition includes at least one of the following:

According to the first information, when it is determined that the first condition is met, after receiving the SCI, do not start the retransmission waiting timer corresponding to the second sidelink process; or,

According to the first information, when it is determined that the first condition is not met, after receiving the SCI, start a retransmission waiting timer corresponding to the second sidelink process;

Wherein, the first condition includes at least one of the following:

Optionally, in an embodiment, the first information is for the first sidelink process.

The receiving unit 1200 is configured to receive sidelink control information SCI from the first terminal device, where the SCI includes the identifier of the first sidelink process;

The processing unit 1100 is configured to determine whether a second sidelink process supports hybrid automatic repeat request (HARQ) feedback, the second sidelink process is used to process the data scheduled by the SCI, and the second sidelink process an on-road process is associated with the first side-link process;

And, if the first sidelink process does not support HARQ feedback, do not start the retransmission waiting timer or retransmission scheduling timer corresponding to the first sidelink process; or,

In the case that the first side link process does not support HARQ feedback, in the case that the retransmission waiting timer corresponding to the first side link process expires and the data scheduled by the SCI is not successfully decoded , not starting the retransmission scheduling timer corresponding to the first sidelink process; or,

If the first sidelink process does not support HARQ feedback, the receiving unit 1200 does not start the retransmission waiting timer corresponding to the first sidelink process after receiving the SCI.

In the case where the first sidelink process supports HARQ feedback, when the retransmission waiting timer corresponding to the first sidelink process times out and the data scheduled by the SCI is not successfully decoded, Start a retransmission scheduling timer corresponding to the first sidelink process; or,

If the first sidelink process supports HARQ feedback, the receiving unit 1200 starts a retransmission waiting timer corresponding to the first sidelink process after receiving the SCI.

In each of the above implementation manners, the receiving unit 1200 and the sending unit 1300 may also be integrated into a transceiver unit, which has the functions of receiving and sending at the same time, which is not limited here.

In each embodiment where the communication device 1000 corresponds to the sending terminal (or the first terminal), the processing unit 1100 is configured to perform processing and/or operations implemented internally by the sending terminal except for the actions of sending and receiving. The receiving unit 1200 is configured to perform the receiving action of the sending terminal, and the sending unit 1300 is configured to perform the sending action of the sending terminal.

For example, in FIG. 6 , the processing unit 1100 is configured to perform step 240 . The sending unit 1300 is configured to perform the sending operation in step 210 or step 230 . Optionally, the sending unit 1300 is configured to perform the operation of sending the first information to the access network device in step 220 . Optionally, the receiving unit 1200 is configured to perform the operation of receiving the first information from the access network device in step 220 .

For another example, in FIG. 7 , the processing unit 1100 is configured to execute step 310 and step 320 . The sending unit 1300 is configured to perform the sending operation involved in step 330 , and the receiving unit 1200 is configured to perform the receiving operation involved in step 330 .

For another example, in FIG. 10 , the processing unit 1100 is configured to execute step 520 . The sending unit 1300 is configured to execute step 510 .

In each embodiment where the communication device 1000 corresponds to a receiving terminal (or a second terminal), the processing unit 1100 is configured to perform processing and/or operations implemented internally by the receiving terminal except for the actions of sending and receiving. The receiving unit 1200 is configured to perform the receiving action of the receiving terminal, and the sending unit 1300 is configured to perform the sending action of the receiving terminal.

For example, in FIG. 6 , the processing unit 1100 is configured to perform step 240 . The receiving unit 1200 is configured to perform the receiving operation in step 210 or step 230 .

For another example, in FIG. 10 , the processing unit 1100 is configured to execute step 520 . The receiving unit 1200 is configured to execute step 510 .

Referring to FIG. 14 , FIG. 14 is a schematic structural diagram of a communication device provided by the present application. As shown in FIG. 14 , the communication device 10 includes: one or more processors 11 , one or more memories 12 and one or more communication interfaces 13 . The processor 11 is used to control the communication interface 13 to send and receive signals, the memory 12 is used to store a computer program, and the processor 11 is used to call and run the computer program from the memory 12, so that the communication device 10 executes the method described in each method embodiment of the present application. Processing performed by the sending terminal or the receiving terminal.

For example, the processor 11 may have the functions of the processing unit 1100 shown in FIG. 13 , and the communication interface 13 may have the functions of the receiving unit 1200 and/or the sending unit 1300 shown in FIG. 13 . Specifically, the processor 11 may be used to perform processing or operations performed internally by the communication device, and the communication interface 13 is used to perform sending and/or receiving operations of the communication device.

In an implementation manner, the communication device 10 may be the sending terminal in the method embodiment. In this implementation manner, the communication interface 13 may be a transceiver of the sending terminal. Transceivers may include receivers and/or transmitters. Optionally, the processor 11 may be a baseband device of the sending terminal, and the communication interface 13 may be a radio frequency device.

In another implementation, the communication device 10 may be a chip (or chip system) installed in the sending terminal. In this implementation manner, the communication interface 13 may be an interface circuit or an input/output interface.

In an implementation manner, the communication device 10 may be the receiving terminal in the method embodiment. In this implementation manner, the communication interface 13 may be a transceiver of the receiving terminal. Transceivers may include receivers and/or transmitters. Optionally, the processor 11 may be a baseband device of the receiving terminal, and the communication interface 13 may be a radio frequency device.

In another implementation, the communication device 10 may be a chip (or chip system) installed in a receiving terminal. In this implementation manner, the communication interface 13 may be an interface circuit or an input/output interface.

Wherein, the dotted box behind the device (for example, processor, memory or communication interface) in FIG. 14 indicates that there may be more than one device.

Optionally, the memory and the processor in the foregoing apparatus embodiments may be physically independent units, or the memory and the processor may also be integrated together, which is not limited herein.

In addition, the present application also provides a computer-readable storage medium, where computer instructions are stored in the computer-readable storage medium, and when the computer instructions are run on the computer, the operations performed by the sending terminal in each method embodiment of the present application are and/or processing is performed.

The present application also provides a computer-readable storage medium, where computer instructions are stored in the computer-readable storage medium, and when the computer instructions are run on the computer, the operations performed by the receiving terminal in each method embodiment of the present application and/or or processing is performed.

In addition, the present application also provides a computer program product. The computer program product includes computer program codes or instructions. When the computer program codes or instructions are run on the computer, the operations performed by the sending terminal in each method embodiment of the present application and/or or processing is performed.

The present application also provides a computer program product. The computer program product includes computer program codes or instructions. When the computer program codes or instructions are run on the computer, the operations and/or processing performed by the receiving terminal in each method embodiment of the present application are be executed.

In addition, the present application also provides a chip, the chip includes a processor, the memory for storing computer programs is set independently of the chip, and the processor is used for executing the computer programs stored in the memory, so that the terminal equipment installed with the chip Execute the operations and/or processing performed by the sending terminal in any one method embodiment.

Further, the chip may further include a communication interface. The communication interface may be an input/output interface, or an interface circuit or the like. Further, the chip may further include the memory.

The present application also provides a chip, the chip includes a processor, a memory for storing computer programs is provided independently of the chip, and the processor is used for executing the computer programs stored in the memory, so that the terminal device installed with the chip executes any Operations and/or processing performed by a receiving terminal in a method embodiment.

Optionally, there may be one or more processors, one or more memories, and one or more memories.

In addition, the present application also provides a communication device (for example, it may be a chip or a chip system), including a processor and a communication interface, the communication interface is used to receive (or be referred to as input) data and/or information, and will receive The received data and/or information are transmitted to the processor, and the processor processes the data and/or information, and the communication interface is also used to output (or be referred to as output) the data and/or processed by the processor or information, so that the operation and/or processing performed by the sending terminal in any method embodiment is performed.

The present application also provides a communication device (for example, it may be a chip or a chip system), including a processor and a communication interface, the communication interface is used to receive (or be referred to as input) data and/or information, and the received The data and/or information are transmitted to the processor, and the processor processes the data and/or information, and the communication interface is also used to output (or be referred to as output) the data and/or information processed by the processor , so that the operation and/or processing performed by the receiving terminal in any one method embodiment is performed.

In addition, the present application also provides a communication device, including at least one processor, the at least one processor is coupled to at least one memory, and the at least one processor is configured to execute computer programs or instructions stored in the at least one memory, The communication device is made to perform the operation and/or processing performed by the sending terminal in any one method embodiment.

The present application also provides a communication device, including at least one processor, the at least one processor is coupled to at least one memory, and the at least one processor is used to execute the computer program or instruction stored in the at least one memory, so that the The above communication device executes the operation and/or processing performed by the receiving terminal in any one method embodiment.

In addition, the present application also provides a communication device, including a processor and a memory. Optionally, a transceiver may also be included. Wherein, the memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory, and control the transceiver to send and receive signals, so that the communication device performs the operation and/or processing performed by the sending terminal in any method embodiment .

The present application also provides a communication device, including a processor and a memory. Optionally, a transceiver may also be included. Wherein, the memory is used to store the computer program, and the processor is used to call and run the computer program stored in the memory, and control the transceiver to send and receive signals, so that the communication device performs the operation and/or processing performed by the receiving terminal in any method embodiment .

In addition, the present application also provides a wireless communication system, including the sending terminal and the receiving terminal in the method embodiments of the present application. Optionally, the wireless communication system further includes radio access network equipment.

The memory in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory can be random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, many forms of RAM are available such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM ) and direct memory bus random access memory (direct rambus RAM, DRRAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

The methods provided in the foregoing embodiments may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product may comprise one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.

In order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, numbers such as "first" and "second" are used to distinguish the same or similar items with basically the same function and effect. For example, the first sidelink procedure and the second sidelink procedure are only for distinguishing the two sidelink procedures. Those skilled in the art can understand that numbers such as "first" and "second" do not limit the quantity, and words such as "first" and "second" are not necessarily different.

In the embodiment of this application, "and/or" describes the association relationship of associated objects, indicating that there may be three relationships, for example, A and/or B, which may mean: A exists alone, A and B exist at the same time, and B exists alone , where A and B can be singular or plural. The character "/" generally indicates that the contextual objects are an "or" relationship. "At least one item(s)" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural item(s). For example, at least one item (unit) of a, b, or c may represent: a, b, c; a and b; a and c; b and c; or a and b and c. Where a, b, c can be single or multiple.

Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.

If the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims

A method for sidelink communication, comprising:

The first terminal device sends first information to the second terminal device, where the first information is used to indicate the retransmission times threshold of the first sidelink data and/or the start times threshold of the retransmission scheduling timer, the said The first sidelink is a communication link between the first terminal device and the second terminal device;

The first terminal device sends sidelink control information SCI to the second terminal device through the first sidelink, where the SCI includes an identifier of a first sidelink process;

The first terminal device processes a retransmission scheduling timer or a retransmission waiting timer corresponding to the first sidelink process according to the first information.
The method according to claim 1, wherein the first terminal device processes the retransmission scheduling timer corresponding to the first sidelink process according to the first information, including:

When the first terminal device determines that the first condition is met according to the first information, after the retransmission waiting timer corresponding to the first sidelink process expires, the first terminal device does not start the second A retransmission scheduling timer corresponding to a downlink process; or,

If the first terminal device determines that the first condition is not met according to the first information, after the retransmission waiting timer corresponding to the first sidelink process expires, start the The retransmission scheduling timer corresponding to the first sidelink process,

Wherein, the first condition includes at least one of the following:

The current retransmission times of the data scheduled by the SCI reaches the retransmission times threshold; or,

The current start times of the retransmission scheduling timer corresponding to the first sidelink process corresponding to the SCI reaches the start times threshold.
The method according to claim 1, wherein the first terminal device processes the retransmission waiting timer corresponding to the first sidelink process according to the first information, including:

After the first terminal device determines that the first condition is met according to the first information, after sending the SCI, not starting the retransmission waiting timer corresponding to the first sidelink process; or ,

After the first terminal device determines that the first condition is not met according to the first information, after sending the SCI, start a retransmission waiting timer corresponding to the first sidelink process ;

Wherein, the first condition includes at least one of the following:

The current retransmission times of the data scheduled by the SCI reaches the retransmission times threshold; or,

The current start times of the retransmission scheduling timer corresponding to the first sidelink process corresponding to the SCI reaches the start times threshold.
The method according to any one of claims 1-3, wherein the first information is for the first sidelink process, wherein the first terminal device includes a plurality of sidelink processes A link process, the first side link process is a side link process in the plurality of side link processes.
The method according to any one of claims 1-4, further comprising:

The first terminal device sends the first information to the access network device.
The method according to any one of claims 1-4, further comprising:

The first terminal device receives the first information from an access network device.
A method for sidelink communication, comprising:

The second terminal device receives first information from the first terminal device, where the first information is used to indicate the retransmission times threshold of the first sidelink data and/or the start times threshold of the retransmission scheduling timer, The first sidelink is a communication link between the first terminal device and the second terminal device;

The second terminal device receives sidelink control information SCI from the first terminal device through the first sidelink, and the SCI includes an identifier of a first sidelink process;

The second terminal device processes the retransmission scheduling timer or the retransmission waiting timer corresponding to the second sidelink process according to the first information, and the second sidelink process is used to process the SCI For scheduled data, the first sidelink process is associated with the second sidelink process.
The method according to claim 7, wherein the second terminal device processes the retransmission scheduling timer corresponding to the second sidelink process according to the first information, including:

When the second terminal device determines that the first condition is met according to the first information, after the retransmission wait timer corresponding to the second sidelink process expires, the second terminal device does not start the second sidelink process. The retransmission scheduling timer corresponding to the two sidelink processes; or,

In a case where the second terminal device determines that the first condition is not met according to the first information, after the retransmission waiting timer corresponding to the second sidelink process expires, start the second The retransmission scheduling timer corresponding to the two uplink processes;

Wherein, the first condition includes at least one of the following:

The current retransmission times of the data scheduled by the SCI reaches the retransmission times threshold; or,

The current start times of the retransmission scheduling timer corresponding to the second sidelink process corresponding to the SCI reaches the start times threshold.
The method according to claim 7, wherein the second terminal device processes the retransmission waiting timer corresponding to the second sidelink process according to the first information, including:

The second terminal device does not start the retransmission waiting timer corresponding to the second sidelink process after receiving the SCI when the second terminal device determines that the first condition is met according to the first information; or ,

If the second terminal device determines that the first condition is not met according to the first information, after receiving the SCI, start a retransmission waiting timer corresponding to the second sidelink process ;

Wherein, the first condition includes at least one of the following:

The current retransmission times of the data scheduled by the SCI reaches the retransmission times threshold; or,

The current start times of the retransmission scheduling timer corresponding to the second sidelink process corresponding to the SCI reaches the start times threshold.
The method according to any one of claims 7-9, wherein the first information is for the first sidelink process.
A method for sidelink communication, comprising:

acquiring a first sidelink resource by the first terminal device;

The first terminal device determines a destination address, the destination address corresponds to the second terminal device, and the time domain of the first sidelink resource overlaps or partially overlaps with the activation time of the destination address,

Wherein, the activation time does not include the first duration, and the first duration is the running duration of the retransmission scheduling timer of the sidelink process of the destination address that does not support hybrid automatic repeat request HARQ feedback, or,

The running time of the persistent timer of the destination address, the running time of the inactive timer, the running time of the retransmission scheduling timer of the sidelink process supporting HARQ feedback, or the channel state information that the first terminal device expects to receive The duration of the CSI report belongs to the activation time;

The first terminal device performs sidelink communication with the second terminal device according to the activation time.
The method according to claim 11, wherein within the running time of the retransmission scheduling timer of the side link process that does not support HARQ feedback, if the first timer is in the running state, the activation time Including the running duration of the first timer, where the first timer includes a persistence timer, an inactivity timer, or a retransmission scheduling timer of a third sidelink process that supports HARQ feedback; or,

During the running time of the retransmission scheduling timer of the sidelink process that does not support HARQ feedback, the first terminal device is in the state of expecting to receive the CSI report, and the activation time includes the first terminal device expecting The duration of receiving the CSI report.
The method according to claim 11 or 12, further comprising:

The first terminal device acquires a second sidelink resource;

Wherein, the second sidelink resource is unavailable under the following circumstances:

The time domain of the second sidelink resource and the running duration of the persistent timer of any destination address, the running duration of the inactive timer, and the running of the retransmission scheduling timer of the sidelink process supporting HARQ feedback There is no overlap between the duration or the duration during which the first terminal device expects to receive the CSI report,

Wherein, the unavailable second side link resource includes that the second side link resource cannot be used for side link transmission, or the second side link resource cannot be used for side link The initial pass.
A terminal device, characterized in that it includes:

A sending unit, configured to send first information to the second terminal device, where the first information is used to indicate the retransmission times threshold of the first sidelink data and/or the start times threshold of the retransmission scheduling timer, the said first sidelink is a communication link between said terminal device and said second terminal device;

And, sending sidelink control information SCI to the second terminal device through the first sidelink, where the SCI includes the identifier of the first sidelink process;

A processing unit, configured to process a retransmission scheduling timer or a retransmission waiting timer corresponding to the first sidelink process according to the first information.
The terminal device according to claim 14, wherein the processing unit is specifically configured to:

According to the first information, when it is determined that the first condition is met, after the retransmission waiting timer corresponding to the first sidelink process expires, the first sidelink process is not started the corresponding retransmission scheduling timer; or,

According to the first information, if it is determined that the first condition is not met, after the retransmission waiting timer corresponding to the first sidelink process expires, start the first sidelink The retransmission scheduling timer corresponding to the road process,

Wherein, the first condition includes at least one of the following:

The current retransmission times of the data scheduled by the SCI reaches the retransmission times threshold; or,

The current start times of the retransmission scheduling timer corresponding to the first sidelink process corresponding to the SCI reaches the start times threshold.
The terminal device according to claim 14, wherein the processing unit is specifically configured to:

According to the first information, when it is determined that the first condition is met, after sending the SCI, do not start the retransmission waiting timer corresponding to the first sidelink process; or,

According to the first information, when it is determined that the first condition is not met, after sending the SCI, start a retransmission waiting timer corresponding to the first sidelink process;

Wherein, the first condition includes at least one of the following:

The current retransmission times of the data scheduled by the SCI reaches the retransmission times threshold; or,

The current start times of the retransmission scheduling timer corresponding to the first sidelink process corresponding to the SCI reaches the start times threshold.
The terminal device according to any one of claims 14-16, wherein the first information is for the first sidelink process, wherein the first terminal device includes multiple sidelink processes An uplink process, where the first sidelink process is one of the multiple sidelink processes.
The terminal device according to any one of claims 14-17, wherein the sending unit is further configured to:

Send the first information to the access network device.
The terminal device according to any one of claims 14-17, wherein the terminal device further comprises:

A receiving unit, configured to receive the first information from the access network device.
A terminal device, characterized in that it includes:

A receiving unit, configured to receive first information from the first terminal device, where the first information is used to indicate the retransmission times threshold of the first sidelink data and/or the start times threshold of the retransmission scheduling timer , the first sidelink is a communication link between the first terminal device and the terminal device;

And, receiving sidelink control information SCI from the first terminal device through the first sidelink, where the SCI includes the identifier of the first sidelink process;

A processing unit, configured to process a retransmission scheduling timer or a retransmission waiting timer corresponding to a second sidelink process according to the first information, and the second sidelink process is used to process the SCI scheduling For data, the first sidelink process is associated with the second sidelink process.
The terminal device according to claim 20, wherein the processing unit is specifically used for:

According to the first information, when it is determined that the first condition is met, after the retransmission wait timer corresponding to the second sidelink process expires, the second sidelink process is not started The corresponding retransmission scheduling timer; or,

According to the first information, when it is determined that the first condition is not met, after the retransmission waiting timer corresponding to the second sidelink process expires, start the second sidelink process The corresponding retransmission scheduling timer;

Wherein, the first condition includes at least one of the following:

The current retransmission times of the data scheduled by the SCI reaches the retransmission times threshold; or,

The current start times of the retransmission scheduling timer corresponding to the second sidelink process corresponding to the SCI reaches the start times threshold.
The terminal device according to claim 20, wherein the processing unit is specifically used for:

According to the first information, when it is determined that the first condition is met, after receiving the SCI, do not start the retransmission waiting timer corresponding to the second sidelink process; or,

According to the first information, when it is determined that the first condition is not met, after receiving the SCI, start a retransmission waiting timer corresponding to the second sidelink process;

Wherein, the first condition includes at least one of the following:

The current retransmission times of the data scheduled by the SCI reaches the retransmission times threshold; or,

The current start times of the retransmission scheduling timer corresponding to the second sidelink process corresponding to the SCI reaches the start times threshold.
The terminal device according to any one of claims 20-22, wherein the first information is for the first sidelink process.
A terminal device, characterized in that it includes:

a processing unit, configured to obtain a first sidelink resource;

And, determine a destination address, the destination address corresponds to the second terminal device, and the time domain of the first sidelink resource overlaps or partially overlaps with the activation time of the destination address,

Wherein, the activation time does not include the first duration, and the first duration is the running duration of the retransmission scheduling timer of the sidelink process of the destination address that does not support HARQ feedback, or,

The running time of the persistent timer of the destination address, the running time of the inactive timer, the running time of the retransmission scheduling timer of the sidelink process supporting HARQ feedback, or the channel state information that the first terminal device expects to receive The duration of the CSI report belongs to the activation time;

And, according to the activation time, control the sending unit and/or the receiving unit to perform sidelink communication with the second terminal device.
A communication device, characterized in that it includes at least one processor, the at least one processor is coupled to at least one memory, and the at least one processor is configured to execute a computer program or instructions stored in the at least one memory, so that The communication device executes the method according to any one of claims 1-13.
A chip, characterized in that it includes a processor and a communication interface, the communication interface is used to receive data and/or information, and transmit the received data and/or information to the processor, and the processor processes Said data and/or information to perform the method according to any one of claims 1-13.
A computer-readable storage medium, characterized in that computer instructions are stored in the computer-readable storage medium, and when the computer instructions are run on a computer, the method according to any one of claims 1-13 is executed accomplish.
A computer program product, characterized in that the computer program product includes computer program code, and when the computer program code is run on a computer, the method according to any one of claims 1-13 is realized.