A communication method and device

By determining whether to start the DRX inactivation timer based on the received second side control information in the SL DRX environment, the problem of uncertain timer status before receiving channel status information is solved, and power saving and channel status are realized Efficient reception of information.

CN114980284BActive Publication Date: 2024-11-15HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110307529.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2021-02-24
Filing Date
2021-03-23
Publication Date
2024-11-15
Estimated Expiration
2041-03-23

AI Technical Summary

Technical Problem

In the SL DRX mechanism, there is uncertainty as to whether the UE starts or restarts the DRX inactivation timer before receiving the sideline CSI, resulting in confusion in device behavior, affecting the power saving and the reception efficiency of channel state information.

Method used

After sending the first side control information to the second terminal device, the second side control information is received within the first time period, and whether to start or restart the DRX inactivation timer is determined, ensuring that the channel status information is received during the monitoring of the PSCCH No longer monitoring time, save power and avoid confusion.

Benefits of technology

Effectively avoid unnecessary startup of DRX inactivated timer, saves power of terminal equipment, and clarify how the terminal equipment controls the DRX timer after triggering channel status information, avoids confusion in behavior, and improves the efficiency of receiving channel status information. .

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114980284B_ABST
    Figure CN114980284B_ABST
Patent Text Reader

Abstract

The present application relates to a communication method and device. A first terminal device configured with sidelink DRX sends first sidelink control information to a second terminal device, and the first sidelink control information is used to trigger the second terminal device to send sidelink channel status information. In a first time period after sending the first sidelink control information, the first terminal device receives second sidelink control information from the second terminal device, and the first time period is used to receive the sidelink channel status information. The first terminal device does not start the sidelink DRX inactive timer. The first time period itself is used to receive the sidelink channel status information, so the reception of the sidelink channel status information will not be affected if the first terminal device does not start the sidelink DRX inactive timer. And by not starting the timer, the power consumption of the first terminal device can be saved.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to a Chinese patent application filed with the State Intellectual Property Office of China on February 24, 2021, with application number 202110209310.4 and application name “A SL DRX inactivity timer startup method”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0004] If two adjacent user equipments (UE) want to communicate, they do not need to go through other network nodes, but can communicate directly, for example, the two UEs can communicate through a sidelink (SL). For two UEs communicating through SL, one UE can trigger the other UE to feedback sidelink channel state information (CSI) by sending a message.

[0005] For example, UE1 sends a message to UE2 to trigger UE2 to send sidelink CSI to UE1. For example, UE1 adopts the sidelink discontinuous reception (DRX) mechanism. In the sidelink DRX mechanism, UE1 will have a corresponding sleep time. So after sending the message, in order to receive the sidelink CSI from UE2, UE1 does not need to enter the sleep state, but continues to monitor the physical sidelink control channel (PSCCH). While UE1 is monitoring PSCCH, UE1 may also receive sidelink control information (SCI) from UE2. If SCI is received, whether the corresponding sidelink DRX timer of UE1 should be started (or restarted) or not is still unclear, which may cause confusion in UE1's behavior. Summary of the invention

[0006] The embodiments of the present application provide a communication method and device for providing an operation rule for a UE to avoid behavior confusion of the UE.

[0007] In a first aspect, a first communication method is provided, which can be executed by a terminal device, or by a larger device including the terminal device, or by a chip system or other functional module, which can implement the functions of the terminal device. For example, the terminal device is a first terminal device, and the first terminal device is configured with sidelink DRX. The method includes: sending first sidelink control information to a second terminal device, the first sidelink control information is used to trigger the second terminal device to send sidelink channel status information; receiving second sidelink control information from the second terminal device within a first time period after sending the first sidelink control information, the second sidelink control information is used to schedule MAC PDU, and the first time period is used to receive the sidelink channel status information; and not starting the sidelink DRX inactive timer.

[0008] In an embodiment of the present application, after the first terminal device sends the first side control information for triggering the side channel state information to the second terminal device, if the second side control information is received from the second terminal device within the first time period, the first terminal device may not start or restart the side DRX inactive timer. Because the first terminal device is in a state of listening to the PSCCH during the first time period, it is able to receive the side channel state information from the second terminal device, that is, the reception of the side channel state information will not be delayed. And because the first terminal device does not start or restart the side DRX inactive timer, the monitoring time (first time period) of the first terminal device for the side channel state information will not be extended, which can save power for the first terminal device. Moreover, the embodiment of the present application provides operating rules for the terminal device, so that the terminal device can clearly understand how to control the side DRX timer after triggering the side channel state information, thereby avoiding confusion in the behavior of the terminal device.

[0009] In combination with the first aspect, in a first optional implementation of the first aspect, the first time period satisfies: it is a time period during which the first terminal device monitors the sidewalk control information after sending the first sidewalk control information, and does not belong to the sidewalk DRX activation time of the first terminal device; or, the first time period satisfies: it is a time period during which the first terminal device monitors the sidewalk control information after sending the first sidewalk control information, and the sidewalk DRX duration timer and the sidewalk DRX inactivation timer of the first terminal device are not running; or, the first time period satisfies: it is a time period during which the first terminal device monitors the sidewalk control information after sending the first sidewalk control information, and the sidewalk DRX duration timer, the sidewalk DRX retransmission timer and the sidewalk DRX inactivation timer of the first terminal device are not running. The first time period may not belong to the sidewalk DRX activation time of the first terminal device, or the first time period may also belong to the sidewalk DRX activation time of the first terminal device, and the definition of the first time period is relatively flexible.

[0010] In combination with the first optional implementation manner of the first aspect, in the second optional implementation manner of the first aspect, the time period during which the first terminal device monitors the side control information after sending the first side control information is the time period during which the first timer runs, and the first timer is started by the first terminal device after sending the first side control information; or, the time period during which the first terminal device monitors the side control information after sending the first side control information is the time period during which the first terminal device expects to receive the side channel state information after sending the first side control information; or, the time period during which the first terminal device monitors the side control information after sending the first side control information is the time period during which the side channel state information report timer runs, and the side channel state information report timer is used to indicate the maximum duration until the side channel state information is sent. The time period during which the first terminal device monitors the side control information after sending the first side control information can be implemented in a variety of different ways, which is relatively flexible.

[0011] In combination with the first aspect or the first optional implementation manner of the first aspect or the second optional implementation manner of the first aspect, in the third optional implementation manner of the first aspect, the method also includes: sending first information to the second terminal device, the first information being used to indicate that the first terminal device does not start the sidelink DRX inactive timer within the first time period after sending the first sidelink control information; or, receiving first information from the second terminal device, the first information being used to indicate that the first terminal device does not start the sidelink DRX inactive timer within the first time period after sending the first sidelink control information; or, receiving first information from a network device, the first information being used to indicate that the first terminal device does not start the sidelink DRX inactive timer within the first time period after sending the first sidelink control information; or, the first sidelink control information is also used to indicate that the first terminal device does not start the sidelink DRX inactive timer within the first time period after sending the first sidelink control information. The first terminal device may not start the sidelink DRX inactive timer of the first terminal device by default within the first time period after sending the first sidelink control information to the second terminal device. Alternatively, whether the first terminal device starts the sidelink DRX inactive timer of the first terminal device within the first time period after sending the first sidelink control information to the second terminal device may be configured by the network device, or determined by the first UE itself, or configured by the second UE, which is more flexible.

[0012] In combination with the first aspect or any one of the first optional implementation manners to the third optional implementation manners of the first aspect, in a fourth optional implementation manner of the first aspect, the method further includes: sending second information to the second terminal device, the second information being used to indicate a first mode applied to the first time period, the first mode being a mode in which the second terminal device sends information to the first terminal device. The first mode includes: the second terminal device can send side channel state information to the first terminal device, and cannot send data to the first terminal device; or, the second terminal device can send side channel state information and / or data to the first terminal device; or, the second terminal device can send side channel state information to the first terminal device, or send side channel state information and data, and the side channel state information and the data are carried in the same MAC PDU. There may be multiple different implementations for the second terminal device to send a MAC PDU to the first terminal device within the first time period, or there may be multiple different implementations for the MAC PDU sent by the second terminal device to the first terminal device within the first time period. For example, one way is that the MAC PDU sent by the second terminal device to the first terminal device in the first time period can include the side channel state information but cannot include data. In this implementation mode, the second terminal device only needs to send the side channel state information to the first terminal device, which can reduce the sending time and improve the efficiency of the first terminal device in obtaining the side channel state information. If a transmission error requires retransmission, only the side channel state information needs to be retransmitted without retransmitting other information, which can save retransmission time. For example, another way is that the second terminal device can send the side channel state information and / or data to the first terminal device, and the side channel state information and data can be included in the same MAC PDU or in different MAC PDUs. In this implementation mode, the second terminal device can send the side channel state information to the first terminal device, and can also send data to the first terminal device, so that the first time period can be effectively utilized, so that the first terminal device can obtain more information in the first time period. Moreover, the side channel state information and data can be included in one MAC PDU or in different MAC PDUs, which is more flexible and can send more information. For example, in another way, the second terminal device can send the side channel state information to the first terminal device, or send the side channel state information and data to the first terminal device, but if data is to be sent, the side channel state information and data need to be included in the same MAC PDU.In this implementation, the second terminal device can send both the side channel state information and the data to the first terminal device, which can effectively utilize the first time period, so that the first terminal device can obtain more information within the first time period. Moreover, the side channel state information and data can be included in one MAC PDU, which can improve the transmission efficiency and the efficiency of the first terminal device in obtaining the side channel state information. Moreover, if retransmission is involved, only one MAC PDU needs to be retransmitted, which can also reduce the retransmission time.

[0013] In combination with the first aspect or any one of the first optional implementation manners to the fourth optional implementation manners of the first aspect, in the fifth optional implementation manner of the first aspect, the method further includes: receiving the MAC PDU from the second terminal device; in the event of a failure in decoding the MAC PDU, starting a second timer; during the operation of the second timer, monitoring the side control information to wait for the retransmitted MAC PDU. If the first terminal device fails to decode the MAC PDU, the first terminal device cannot obtain the information included in the MAC PDU, and the first terminal device may start the second timer to wait for the second terminal device to retransmit the MAC PDU. Through the retransmission mechanism, the success rate of the first terminal device in obtaining information can be improved.

[0014] In combination with the fifth optional implementation of the first aspect, in a sixth optional implementation of the first aspect, in the case of a failure in decoding the MAC PDU, starting the second timer includes: in the case of a failure in decoding the MAC PDU and the second side control information indicates that the MAC PDU includes side channel state information but does not include data, starting the second timer. For example, the first terminal device can start the second timer when the decoding of the MAC PDU fails, which can improve the success rate of the first terminal device in obtaining information. Alternatively, if the second side control information indicates that the MAC PDU includes side channel state information but does not include data, then if the first terminal device fails to decode the MAC PDU, the second timer can be started; and if the second side control information indicates that the MAC PDU includes side channel state information and data, or indicates that the MAC PDU does not include side channel state information (it may also indicate that it includes data or does not include data), then even if the first terminal device fails to decode the MAC PDU, the second timer may not be started, that is, it is not necessary to wait for the retransmission of the MAC PDU. If the second side control information indicates that the MAC PDU includes the side channel state information but does not include data, and the first terminal device does not decode the MAC PDU successfully, then since only the side channel state information needs to be retransmitted, the required retransmission time is not long, so the first terminal device can start the second timer to wait for retransmission. If the second side control information indicates that the MAC PDU includes the side channel state information and data, the retransmission process includes the retransmission of the side channel state information and the retransmission of the data, and the required retransmission time is longer, which results in a greater power consumption for the first terminal device, so the first terminal device does not need to wait for retransmission.

[0015] In combination with the fifth optional implementation of the first aspect or the sixth optional implementation of the first aspect, in the seventh optional implementation of the first aspect, starting the second timer includes: starting the second timer in the first time domain unit after the side data channel corresponding to the second side control information ends; or starting the second timer in the first time domain unit after the first feedback information is sent, and the first feedback information is feedback information corresponding to the MAC PDU sent to the second terminal device. The second timer can be started after the second side control information is sent, or it can be started after the first feedback information is sent. If it is started after the first feedback information is sent, the time for the first terminal device to monitor the side control information can be reduced, which can save the power consumption of the first terminal device.

[0016] In combination with the first aspect or any one of the first optional implementation manners to the fourth optional implementation manners of the first aspect, in the eighth optional implementation manner of the first aspect, the method further includes: receiving the MAC PDU from the second terminal device; in the case of a failure in decoding the MAC PDU, starting a third timer, the timing duration of the third timer being used to indicate the preparation time of the second terminal device before resending the MAC PDU; when the third timer times out, starting a second timer; during the operation of the second timer, monitoring the side control information to wait for the retransmitted MAC PDU. It takes a certain amount of time from the first terminal device sending the first feedback information to the second terminal device retransmitting the MAC PDU, that is, the second terminal device needs a certain amount of preparation time to retransmit the MAC PDU, and it is obvious that the first terminal device will not receive the retransmitted MAC PDU during the preparation time of the second terminal device. Therefore, the first terminal device can start the third timer, and during the operation time of the third timer, the first terminal device does not need to monitor the side control information to save the power consumption of the first terminal device.

[0017] In combination with the eighth optional implementation of the first aspect, in a ninth optional implementation of the first aspect, when decoding of the MAC PDU fails, starting a third timer includes: when decoding of the MAC PDU fails and the second sidelink control information indicates that the MAC PDU includes sidelink channel state information but does not include data, starting the third timer. For the technical effect of this implementation, reference may be made to the aforementioned implementation.

[0018] In combination with the eighth optional implementation of the first aspect or the ninth optional implementation of the first aspect, in the tenth optional implementation of the first aspect, starting the third timer includes: starting the third timer in the first time domain unit after the side data channel corresponding to the second side control information ends; or starting the third timer in the first time domain unit after the first feedback information is sent, and the first feedback information is feedback information corresponding to the MAC PDU sent to the second terminal device. The technical effect of this implementation can be referred to the aforementioned implementation.

[0019] In combination with any of the fifth optional implementation manners of the first aspect to the tenth optional implementation manners of the first aspect, in the eleventh optional implementation manner of the first aspect, the method further includes: when the sidelink channel state information report timer of the second terminal device times out, stopping the second timer; or, when a second duration after sending the first sidelink control information arrives, stopping the second timer, the second duration being used to wait for receiving the sidelink channel state information, and the timing duration of the sidelink channel state information report timer of the second terminal device is determined according to the second duration; or, when the duration for expecting to receive the sidelink channel state information after sending the first sidelink control information arrives, stopping the second timer. The first terminal device may not always wait for the retransmission of the MAC PDU. If the sidelink channel state information report timer times out, or the second duration arrives, or the maximum duration for the first terminal device to expect to receive the sidelink channel state information arrives, it may indicate that the second terminal device will no longer send the sidelink channel state information to the first terminal device, so the first terminal device does not need to wait in vain to save power consumption.

[0020] In combination with the first aspect or any one of the optional embodiments from the first optional embodiment to the fourth optional embodiment of the first aspect, in the twelfth optional embodiment of the first aspect, the method further includes: receiving the MAC PDU from the second terminal device; when the decoding of the MAC PDU fails and the second sideline control information indicates that the MAC PDU does not include the sideline channel status information, the second timer is not started, and the operation period of the second timer is used to monitor the sideline control information. If the second sideline control information indicates that the MAC PDU does not include the sideline channel status information, because the first terminal device actually mainly wants to receive the sideline channel status information, if the MAC PDU does not include the sideline channel status information, then the first terminal device does not need to wait for the retransmission of the MAC PDU, so there is no need to start the second timer.

[0021] In combination with the first aspect or any one of the first optional implementation manners to the twelfth optional implementation manners of the first aspect, in the thirteenth optional implementation manner of the first aspect, the method further includes: after sending the first side control information, starting a first timer, the timing duration of the first timer being the first time period. The first terminal device may determine the first time period through the first timer.

[0022] In combination with the first aspect or any one of the first optional implementation manners to the twelfth optional implementation manners of the first aspect, in the fourteenth optional implementation manner of the first aspect, the method further includes: after sending the first sideline control information, starting a fourth timer, the timing duration of the fourth timer is used to indicate the preparation time of the second terminal device before sending the sideline channel state information; when the fourth timer times out, starting the first timer, the timing duration of the first timer is the first time period. From the first terminal device sending the first sideline control information to the second terminal device sending the sideline channel state information, the second terminal device needs a certain preparation time. During this preparation time, the second terminal device will not send the sideline channel state information, and the first terminal device will not receive the sideline channel state information from the second terminal device. Therefore, after sending the first sideline control information, the first terminal device can start the fourth timer, and the timing duration of the fourth timer can indicate the preparation time of the second terminal device before sending the sideline channel state information. During the running time of the fourth timer, the first terminal device does not need to monitor the sideline control information. When the fourth timer times out, the first terminal device starts the first timer again to save the power consumption of the first terminal device.

[0023] In combination with the fourteenth optional implementation of the first aspect, in a fifteenth optional implementation of the first aspect, the method further includes: receiving third information from the second terminal device, the third information being used to indicate a timing duration of the fourth timer. The fourth timer may be configured by the second terminal device, and the second terminal device may indicate the timing duration of the fourth timer to the first terminal device, so that the first terminal device maintains the fourth timer.

[0024] In combination with the thirteenth optional implementation manner of the first aspect or the fourteenth optional implementation manner of the first aspect or the fifteenth optional implementation manner of the first aspect, in the sixteenth optional implementation manner of the first aspect, the running time of the first timer is the sidewalk DRX activation time of the first terminal device; or, the part of the running time of the first timer that does not overlap with the sidewalk DRX activation time of the first terminal device does not belong to the sidewalk DRX activation time of the first terminal device; or, during the running time of the first timer, the time during which the sidewalk DRX duration timer and / or the sidewalk DRX inactivation timer of the first terminal device is not running does not belong to the sidewalk DRX activation time of the first terminal device; or, during the running time of the first timer, the time during which one or more timers among the sidewalk DRX duration timer, the sidewalk DRX inactivation timer or the sidewalk DRX retransmission timer of the first terminal device is not running does not belong to the sidewalk DRX activation time of the first terminal device. The running time of the first timer can be the sidewalk DRX activation time of the first terminal device, or can also not belong to the sidewalk DRX activation time of the first terminal device, which is more flexible.

[0025] In combination with the thirteenth optional implementation of the first aspect or the fourteenth optional implementation of the first aspect or the fifteenth optional implementation of the first aspect or the sixteenth optional implementation of the first aspect, in the seventeenth optional implementation of the first aspect, the method further includes: receiving fourth information from a network device, the fourth information being used to indicate the timing duration of the first timer; or determining the timing duration of the first timer according to the CBR. The timing duration of the first timer may be configured by the network device, or may also be configured by the first terminal device. For example, the first terminal device may determine the timing duration of the first timer according to the CBR. When the value of the CBR remains unchanged, the longer the timing duration of the first timer, the more resources with lower interference can be selected when the second UE sends the sidelink channel state information, and the higher the sending success rate. The timing duration of the first timer is determined according to the CBR, so that a compromise can be made between the interference level of the resources selected by the second terminal device and the monitoring duration of the first terminal device, so as to improve the sending success rate of the second terminal device while saving the power consumption of the first terminal device as much as possible.

[0026] In combination with the seventeenth optional implementation of the first aspect, in the eighteenth optional implementation of the first aspect, determining the timing duration of the first timer according to the CBR includes: when the channel occupancy indicated by the CBR is greater than or equal to the first threshold, determining the timing duration of the first timer to be a duration greater than the second threshold; and / or, when the channel occupancy indicated by the CBR is less than the first threshold, determining the timing duration of the first timer to be a duration less than the third threshold. If the channel occupancy represented by the CBR is high, the timing duration of the first timer determined by the first terminal device can be longer, because at this time there may be greater channel competition and the channel state is not very good, and the first UE can wait for a longer time to receive the side channel state information to improve the success rate of receiving the side channel state information; for another example, if the channel occupancy represented by the CBR is low, the timing duration of the first timer determined by the first terminal device can be shorter, because at this time the channel state is better, and the first terminal device may be able to receive the side channel state information in a shorter time without taking too long, thereby saving power consumption of the first terminal device.

[0027] In combination with any of the thirteenth optional implementation manners of the first aspect to the eighteenth optional implementation manners of the first aspect, in the nineteenth optional implementation manner of the first aspect, the method further includes: receiving second feedback information from the second terminal device; if the second feedback information is used to indicate a failure to receive the first side data channel, stopping the first timer, the first side data channel being the side data channel scheduled by the first side control information. The first side control information may also schedule the first side data channel, so the first terminal device will also send the first side data channel to the second terminal device after sending the first side control information. The second terminal device needs to decode both the first side control information and the first side data channel. The second terminal device can send the side channel status information to the first terminal device only if both the first side control information and the first side data channel are successfully decoded. Whether the decoding of the first side control information or the first side data channel fails, it may cause the second terminal device to be unable to send the side channel status information to the first terminal device. After receiving the first side data channel, the second terminal device may send second feedback information to the first terminal device. If the second terminal device fails to decode the first side data channel (or fails to receive), the second feedback information is, for example, a negative response, indicating that the first side data channel fails to be received. If the second terminal device successfully decodes the first side data channel (or successfully receives), the second feedback information is, for example, a positive response, indicating that the first side data channel is successfully received. For the first terminal device, if the second feedback information is used to indicate that the first side data channel fails to be received, it indicates that the second terminal device cannot send the side channel status information to the first terminal device. Therefore, the first terminal device does not need to wait for receiving the side channel status information. The first terminal device may stop the first timer to save power consumption of the first terminal device.

[0028] In a second aspect, a second communication method is provided, which can be executed by a terminal device, or by a larger device including the terminal device, or by a chip system or other functional module, which can implement the functions of the terminal device. For example, the terminal device is a second terminal device. The method includes: receiving first sideline control information from a first terminal device, the first sideline control information is used to trigger the second terminal device to send sideline channel state information; sending second sideline control information to the first terminal device, the second sideline control information is used to schedule MAC PDU; and not starting the sideline DRX inactive timer.

[0029] In combination with the second aspect, in a first optional implementation of the second aspect, the method further includes: sending the MAC PDU to the first terminal device in a first manner applied to a first time period, the first time period being used for the first terminal device to wait for the sidelink channel state information. The first manner includes: being able to send sidelink channel state information to the first terminal device, and not being able to send data to the first terminal device; or, being able to send sidelink channel state information and / or data to the first terminal device; or, being able to send sidelink channel state information to the first terminal device, or sending sidelink channel state information and data, and the sidelink channel state information and the data are carried in one MAC PDU.

[0030] In combination with the second aspect or the first optional implementation of the second aspect, in the second optional implementation of the second aspect, the method also includes: receiving first information from the first terminal device, the first information being used to indicate that the first terminal device does not start the sidewalk DRX inactive timer within a first time period after sending the first sidewalk control information; or, receiving first information from a network device, the first information being used to indicate that the first terminal device does not start the sidewalk DRX inactive timer within the first time period after sending the first sidewalk control information; or, sending first information to the first terminal device, the first information being used to indicate that the first terminal device does not start the sidewalk DRX inactive timer within the first time period after sending the first sidewalk control information; or, the first sidewalk control information is also used to indicate that the first terminal device does not start the sidewalk DRX inactive timer within the first time period after sending the first sidewalk control information.

[0031] In combination with the first optional implementation of the second aspect or the second optional implementation of the second aspect, in the third optional implementation of the second aspect, the method also includes: selecting a target device for receiving the MAC PDU according to a first rule, the first rule including: the first time domain resource is located within the first time period after the target device triggers the second terminal device to send sidelink channel status information, or the first time domain information is located within the sidelink DRX activation time of the target device; wherein the first time domain resource is the time domain resource occupied by the second sidelink control information, or the time domain resource occupied by the sidelink control channel corresponding to the second sidelink control information, or the time domain resource occupied by the sidelink authorization information corresponding to the second sidelink control information.

[0032] In combination with the second aspect or any optional implementation manner from the first optional implementation manner to the third optional implementation manner of the second aspect, in a fourth optional implementation manner of the second aspect, the method further includes: receiving second information from the first terminal device, the second information being used to indicate the first method.

[0033] In combination with the second aspect or any optional implementation manner from the first optional implementation manner to the fourth optional implementation manner of the second aspect, in the fifth optional implementation manner of the second aspect, the method also includes: sending third information to the first terminal device, the third information being used to indicate the timing duration of a fourth timer, and the timing duration of the fourth timer being used to indicate the preparation time of the second terminal device before sending side channel status information.

[0034] Regarding the technical effects brought about by the second aspect or various optional implementations of the second aspect, reference may be made to the introduction to the technical effects of the first aspect or corresponding implementations.

[0035] In a third aspect, a third communication method is provided, which may be executed by a terminal device, or by a larger device including the terminal device, or by a chip system or other functional module, which chip system or functional module can realize the function of the terminal device. For example, the terminal device is a second terminal device. The method includes: receiving first sideline control information from a first terminal device, the first sideline control information is used to trigger the second terminal device to send sideline channel status information; sending second sideline control information to the first terminal device, the second sideline control information is used to schedule MAC PDU; sending the MAC PDU to the first terminal device in a first manner applied to a first time period, the first manner being a manner in which the second terminal device sends information to the first terminal device, and the first time period is used for the first terminal device to wait for the sideline channel status information.

[0036] In combination with the third aspect, in a first optional implementation of the third aspect, the first method includes: being able to send sidelink channel state information to the first terminal device, and being unable to send data to the first terminal device; or, being able to send sidelink channel state information and / or data to the first terminal device; or, being able to send sidelink channel state information to the first terminal device, or sending sidelink channel state information and data, and the sidelink channel state information and the data are carried in one MAC PDU.

[0037] In combination with the third aspect or the first optional implementation of the third aspect, in a second optional implementation of the third aspect, the method further includes: not starting a sidewalk DRX inactivity timer.

[0038] In combination with the third aspect or the first optional implementation manner of the third aspect or the second optional implementation manner of the third aspect, in the third optional implementation manner of the third aspect, the method also includes: receiving first information from the first terminal device, the first information being used to indicate that the first terminal device does not start the sidewalk DRX inactive timer within a first time period after sending the first sidewalk control information; or, receiving first information from a network device, the first information being used to indicate that the first terminal device does not start the sidewalk DRX inactive timer within the first time period after sending the first sidewalk control information; or, sending first information to the first terminal device, the first information being used to indicate that the first terminal device does not start the sidewalk DRX inactive timer within the first time period after sending the first sidewalk control information; or, the first sidewalk control information is also used to indicate that the first terminal device does not start the sidewalk DRX inactive timer within the first time period after sending the first sidewalk control information.

[0039] In combination with the second optional implementation of the third aspect or the third optional implementation of the third aspect, in the fourth optional implementation of the third aspect, the method also includes: selecting a target device for receiving the MAC PDU according to a first rule, the first rule including: a first time domain resource is located within the first time period after the target device triggers the second terminal device to send sidelink channel status information, or the first time domain information is located within the sidelink DRX activation time of the target device; wherein the first time domain resource is the time domain resource occupied by the second sidelink control information, or the time domain resource occupied by the sidelink control channel corresponding to the second sidelink control information, or the time domain resource occupied by the sidelink authorization information corresponding to the second sidelink control information.

[0040] In combination with the third aspect or any optional implementation manner from the first optional implementation manner of the third aspect to the fourth optional implementation manner of the third aspect, in the fifth optional implementation manner of the third aspect, the method also includes: receiving second information from the first terminal device, the second information being used to indicate the first mode.

[0041] In combination with the third aspect or any optional implementation manner from the first optional implementation manner of the third aspect to the fifth optional implementation manner of the third aspect, in the sixth optional implementation manner of the third aspect, the method also includes: sending third information to the first terminal device, the third information being used to indicate the timing duration of a fourth timer, and the timing duration of the fourth timer being used to indicate the preparation time of the second terminal device before sending side channel status information.

[0042] Regarding the technical effects brought about by the third aspect or various optional implementations of the third aspect, reference may be made to the introduction to the technical effects of the first aspect or corresponding implementations.

[0043] In a fourth aspect, a communication device is provided. The communication device may be the first terminal device described in any one of the first to third aspects. The communication device has the functions of the first terminal device. In an optional implementation, the communication device includes a baseband device and a radio frequency device. In another optional implementation, the communication device includes a processing unit (sometimes also referred to as a processing module) and a transceiver unit (sometimes also referred to as a transceiver module). The transceiver unit can implement a sending function and a receiving function. When the transceiver unit implements the sending function, it may be referred to as a sending unit (sometimes also referred to as a sending module), and when the transceiver unit implements the receiving function, it may be referred to as a receiving unit (sometimes also referred to as a receiving module). The sending unit and the receiving unit may be the same functional module, which is called a transceiver unit, and the functional module can implement a sending function and a receiving function; or, the sending unit and the receiving unit may be different functional modules, and the transceiver unit is a general term for these functional modules.

[0044] The transceiver unit (or the sending unit) is used to send first sideline control information to the second terminal device, and the first sideline control information is used to trigger the second terminal device to send sideline channel state information;

[0045] The transceiver unit (or the receiving unit) is configured to receive second sideline control information from the second terminal device within a first time period after sending the first sideline control information, wherein the second sideline control information is used to schedule the MAC PDU, and the first time period is used to receive the sideline channel state information;

[0046] The processing unit is used to not start the sidewalk DRX inactivity timer.

[0047] In an optional implementation, the communication device also includes a storage unit, and the processing unit is used to couple with the storage unit and execute the program or instructions in the storage unit, so that the communication device can perform the function of the first terminal device described in any one of the first to third aspects above.

[0048] In a fifth aspect, a communication device is provided. The communication device may be the second terminal device described in any one of the first to third aspects. The communication device has the functions of the second terminal device. In an optional implementation, the communication device includes a baseband device and a radio frequency device. In another optional implementation, the communication device includes a processing unit (sometimes also referred to as a processing module) and a transceiver unit (sometimes also referred to as a transceiver module). The implementation of the transceiver unit can refer to the introduction of the fourth aspect.

[0049] The transceiver unit (or the receiving unit) is used to receive first sideline control information from a first terminal device, where the first sideline control information is used to trigger the second terminal device to send sideline channel state information;

[0050] The transceiver unit (or the sending unit) is used to send second sideline control information to the first terminal device, where the second sideline control information is used to schedule a MAC PDU;

[0051] The processing unit is used to not start the sidewalk DRX inactivity timer.

[0052] or,

[0053] The transceiver unit (or the receiving unit) is used to receive first sideline control information from a first terminal device, where the first sideline control information is used to trigger the second terminal device to send sideline channel state information;

[0054] The transceiver unit (or the sending unit) is used to send second sideline control information to the first terminal device, where the second sideline control information is used to schedule a MAC PDU;

[0055] The transceiver unit (or the sending unit) is used to send the MAC PDU to the first terminal device in a first manner applied to a first time period, the first manner being a manner in which the second terminal device sends information to the first terminal device, and the first time period being used for the first terminal device to wait for the side channel status information.

[0056] In an optional implementation, the communication device also includes a storage unit, and the processing unit is used to couple with the storage unit and execute the program or instructions in the storage unit, so that the communication device can perform the function of the second terminal device described in any one of the first to third aspects above.

[0057] In a sixth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium is used to store a computer program or instruction, and when the computer-readable storage medium is executed, the method executed by the first terminal device or the second terminal device in the above aspects is implemented. Optionally, the method executed by the first terminal device or the second terminal device in any embodiment of the present application is implemented.

[0058] In a seventh aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the methods described in the above aspects to be implemented. Optionally, enables the method described in any embodiment of the present application to be implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] Figure 1A and Figure 1B Schematic diagrams of two application scenarios of the embodiments of the present application;

[0060] Figure 2 A flow chart of a communication method provided in an embodiment of the present application;

[0061] Figure 3 A schematic diagram of an operation mode of the first timer in an embodiment of the present application;

[0062] Figure 4 This is a schematic diagram of another operation mode of the first timer in an embodiment of the present application;

[0063] Figure 5 This is a schematic diagram of a second UE sending a MAC PDU to a first UE according to a first implementation manner in an embodiment of the present application;

[0064] Figure 6 This is a schematic diagram of a second UE sending a MAC PDU to a first UE according to a second implementation method in an embodiment of the present application;

[0065] Figure 7 This is a schematic diagram of a second UE sending a MAC PDU to a first UE according to a third implementation method in an embodiment of the present application;

[0066] Figure 8 A schematic block diagram of a communication device provided in an embodiment of the present application;

[0067] Fig. 9 A schematic block diagram of a terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0068] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0069] Below, some terms or concepts in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

[0070] In the embodiment of the present application, the terminal device is a device with wireless transceiver function, which can be a fixed device, a mobile device, a handheld device (such as a mobile phone), a wearable device, a vehicle-mounted device, or a wireless device built into the above device (for example, a communication module, a modem, or a chip system, etc.). The terminal device is used to connect people, objects, machines, etc., and can be widely used in various scenarios, such as but not limited to the following scenarios: cellular communication, device-to-device communication (device-to-device, D2D), vehicle to everything (vehicle to everything, V2X), machine-to-machine / machine-type communication (machine-to-machine / machine-type communications, M2M / MTC), Internet of Things (Internet of Things, IoT), virtual reality (virtual reality, VR), augmented reality (augmented reality, AR), industrial control (industrial control), self-driving, remote medical, smart grid (smart grid), smart furniture, smart office, smart wear, smart transportation, smart city (smart city), drones, robots and other scenarios of terminal devices. The terminal device may sometimes be referred to as user equipment (UE), terminal, access station, UE station, remote station, wireless communication device, or user device, etc. For ease of description, the terminal device is described by taking UE as an example in the embodiments of the present application.

[0071] The network device in the embodiment of the present application includes, for example, an access network device and / or a core network device. The access network device is a device with a wireless transceiver function, which is used to communicate with the terminal device. The access network device includes but is not limited to the base station (BTS, Node B, eNodeB / eNB, or gNodeB / gNB) in the above-mentioned communication system, a transmission reception point (TRP), a base station of the subsequent evolution of the third generation partnership project (3GPP), an access node in the wireless fidelity (Wi-Fi) system, a wireless relay node, a wireless backhaul node, etc. The base station can be: a macro base station, a micro base station, a micro-micro base station, a small station, a relay station, etc. Multiple base stations can support the same access technology mentioned above, or they can support the networks of different access technologies mentioned above. The base station may include one or more co-station or non-co-station transmission reception points. The network device may also be a wireless controller, a centralized unit (CU), and / or a distributed unit (DU) in a cloud radio access network (CRAN) scenario. The network device can also be a server, a wearable device, or a vehicle-mounted device. For example, the network device in the vehicle to everything (V2X) technology can be a road side unit (RSU). The following describes the access network device taking the base station as an example. The base station can communicate with the terminal device, or it can communicate with the terminal device through a relay station. The terminal device can communicate with multiple base stations in different access technologies. The core network device is used to implement functions such as mobility management, data processing, session management, policy and billing. The names of the devices that implement the core network functions in systems with different access technologies may be different, and the embodiments of the present application do not limit this. Taking the 5G system as an example, the core network device includes: access and mobility management function (AMF), session management function (SMF), policy control function (PCF) or user plane function (UPF), etc.

[0072] In the embodiment of the present application, the communication device for realizing the function of the network device may be a network device, or may be a device capable of supporting the network device to realize the function, such as a chip system, which may be installed in the network device. In the technical solution provided in the embodiment of the present application, the technical solution provided in the embodiment of the present application is described by taking the device for realizing the function of the network device as an example that the network device is used as the device.

[0073] Sidelink transmission is carried out between a pair of source and destination. The source can be identified by the source layer-2 ID, and the destination can be identified by the destination layer-2 ID. The source layer-2ID is used to identify the sender UE of the data in the sidelink communication, and the destination layer-2ID is used to identify the target UE of the data or the receiver UE of the data in the sidelink communication. The sender refers to the source of the sidelink communication (or a media access control (MAC) protocol data unit (PDU)), and the receiver refers to the destination of the sidelink communication (or a MAC PDU).

[0074] The source Layer-2 ID is assigned by the transmitting UE itself. For unicast, the destination Layer-2 ID depends on the peer UE of the sidelink communication, and the destination Layer-2 ID is the Layer-2 ID of the peer UE. It can be understood that the layer-2ID of the UE is the source layer-2ID when the UE acts as a transmitter, and it can also be the destination layer-2ID when the UE acts as a receiver. In the process of establishing a PC5 unicast link, Layer-2IDs are exchanged between two UEs and used for subsequent communications. The UE described below may refer to a UE identified by a Layer-2 ID, which is allocated the Layer-2 ID and uses the Layer-2 ID in sidelink communication.

[0075] For unicast, PC5-RRC connection is a logical connection between a source and destination pair. After the PC5 unicast link is established, the corresponding PC5 RRC connection is established. There is a one-to-one correspondence between PC5-RRC connection and PC5 unicast link.

[0076] In NR SL, SCI may include two levels of SCI, namely, 1st stage SCI and 2nd stage SCI. PSCCH carries 1st stage SCI, and PSSCH carries 2nd stage SCI and MAC PDU. 1st stage SCI may include information indicating the resources where PSSCH is located. UE can determine the resources of PSSCH according to the 1st stage SCI carried by PSCCH, and thus receive PSSCH on the corresponding resources.

[0077] In the embodiments of the present application, the number of nouns, unless otherwise specified, means "singular noun or plural noun", that is, "one or more". "At least one" means one or more, and "plural" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can 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 previous and next associated objects are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c means: 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.

[0078] The ordinal numbers such as "first" and "second" mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority or importance of the multiple objects. For example, the first side control information and the second side control information can be the same control information or different control information, and this name does not indicate the difference in content, information volume, sending order, sending time, priority or importance of the two control information. In addition, the numbering of the steps in the various embodiments introduced in the present application is only to distinguish different steps, and is not used to limit the order of the steps. For example, step S201 may occur before step S202, or may occur after S202, or may occur at the same time as S202.

[0079] In new radio (NR), when the UE is in the radio resource control (RRC) connected state, the DRX mechanism is defined to save unnecessary power consumption of the UE. DRX can control the UE to monitor the physical downlink control channel (PDCCH) in certain time periods and not monitor the PDCCH in other time periods, thereby reducing the power consumption of the UE.

[0080] In NR SL, SL DRX is also introduced to make UE more energy-efficient. In SL DRX, drx-onDuration Timer (onDurationTimer), drx-Inactivity Timer (InactivityTimer), drx-Hybrid Automatic Repeat Transmission Loopback Delay Timer (HARQ-RTT-Timer), and drx-Retransmission Timer (RetransmissionTimer) are introduced. In order to distinguish from the names of DRX timers on the Uu interface, the timers in the above SL DRX can be recorded as sl-DRX-OnDurationTimer, sl-DRX-InactivityTimer, sl-DRX-HARQ-RTT-Timer, and sl-DRX-RetransmissionTimer respectively. Among them, sl-DRX-OnDurationTimer is used to indicate a period of time at the beginning of the SL DRX cycle. For example, sl-DRX-OnDurationTimer can be started at the beginning of a SL DRX cycle. During the running time of sl-DRX-OnDurationTimer, the UE is in the sideline onduration time and will monitor the PSCCH. sl-DRX-InactivityTimer is used to indicate a period of time after an SCI indicating a new SL transmission. For example, when the UE is monitoring the PSCCH, if it receives an SCI indicating a new transmission, the UE starts or restarts the sl-DRX-InactivityTimer. sl-DRX-RetransmissionTimer is used to indicate the maximum time until an SCI indicating a retransmission of the SL is received, and sl-DRX-HARQ-RTT-Timer is used to indicate the minimum time before an SCI indicating a retransmission of the SL is expected to be received. For example, if the UE receives an SCI indicating data transmission, the UE starts the sl-drx-HARQ-RTT-Timer of the corresponding HARQ process in the first symbol after the transmission carrying the HARQ feedback ends, and stops the sl-drx-RetransmissionTimerDL of the corresponding HARQ process. The HARQ feedback refers to the HARQ information sent by the UE after receiving the data indicated by the SCI to indicate whether the data is received successfully. If the sl-drx-HARQ-RTT-Timer times out, if the data of the corresponding HARQ process is not decoded successfully, the UE starts the sl-drx-RetransmissionTimer of the corresponding HARQ process at the first symbol after the sl-drx-HARQ-RTT-Timer times out.

[0081] When SL DRX is configured or activated, the UE monitors PSCCH during the SL DRX active time (or SL active time), or the UE monitors PSCCH and the secondary SCI (2ndSCI) carried on the physical sidelink shared channel (PSSCH) during the SL DRX active time, or the UE monitors PSCCH and PSSCH during the SL DRX active time. SL DRX active time includes: the running time of one or more timers in sl-DRX-OnDurationTimer, sl-DRX-InactivityTimer or sl-DRX-RetransmissionTimer.

[0082] For two UEs communicating via SL, one UE can trigger the other UE to feedback SL CSI by sending a message. For example, UE1 sends a message to UE2 to trigger UE2 to send side CSI to UE1. For example, UE1 adopts the SL DRX mechanism, in which UE1 has a corresponding sleep time. So after sending the message, in order to receive SL CSI from the UE, UE1 does not need to enter the sleep state, but continues to monitor PSCCH. While UE1 is monitoring PSCCH, UE1 may also receive SCI from UE2. If SCI is received, there is no conclusion as to whether the corresponding side DRX timer of UE1 (such as sl-DRX-OnDurationTimer, sl-DRX-InactivityTimer or sl-DRX-RetransmissionTimer) should be started (or restarted) or not started. This may cause confusion in the behavior of UE1.

[0083] In view of this, a technical solution of an embodiment of the present application is provided. In an embodiment of the present application, after the first terminal device sends the first side control information for triggering the channel state information to the second terminal device, if the second side control information is received from the second terminal device within the first time period, the first terminal device may not start or restart the side DRX inactive timer. Because the first terminal device is in a listening state for the side control information within the first time period, it is able to receive the channel state information from the second terminal device, that is, the reception of the channel state information will not be delayed. And because the first terminal device does not start or restart the side DRX inactive timer, the listening time (or the first time period) of the first terminal device for the channel state information will not be extended, which can save the power of the first terminal device. Moreover, the embodiment of the present application provides an operating rule for the terminal device, so that the terminal device can clearly know how to control the side DRX timer after triggering the side channel state information, so as to avoid confusion in the behavior of the terminal device.

[0084] For reference Figure 1A , is a schematic diagram of an application scenario of an embodiment of the present application. Figure 1A In the example, the remote terminal device is connected to the relay terminal device, and the remote terminal device can communicate with the network device through the relay terminal device. Figure 1B , is a schematic diagram of another application scenario of the embodiment of the present application. Figure 1B In the process, the remote terminal device is connected to the relay terminal device, and the remote terminal device can communicate with the network device through the relay terminal device. Figure 1A and Figure 1B The difference is that Figure 1A In the case of a remote terminal device being within the coverage area (in-coverage), Figure 1B In the example, the remote terminal device is out of coverage. It should be noted that the technical solution of the embodiment of the present application is not limited to relay services, that is, relay services or non-relay services can be performed between two UEs. Figure 1A or Figure 1B It is only used to indicate the connection between UEs and whether the UE is covered by the network, etc., and does not indicate the service type of the UE.

[0085] Figure 1A or Figure 1B The network device in the example is an access network device, and the access network device is, for example, a base station. Among them, the access network device corresponds to different devices in different systems. For example, in a 4G system, it can correspond to an eNB, and in a 5G system, it corresponds to an access network device in 5G, such as a gNB. Of course, the technical solution provided in the embodiment of the present application can also be applied to future mobile communication systems, so Figure 1A or Figure 1BThe access network device in the embodiment of the present application may also correspond to a network device in a future mobile communication system. In the embodiment of the present application, the access network device is a base station as an example. In fact, referring to the introduction in the foregoing text, the access network device may also be a device such as an RSU.

[0086] The following is a description of the method provided by the embodiments of the present application in conjunction with the accompanying drawings. In the accompanying drawings corresponding to the various embodiments of the present application, all optional steps are indicated by dotted lines. The various embodiments of the present application can be applied to Figure 1A or Figure 1B The network architecture shown in FIG. 1 is a first UE described in each embodiment of the present application. Figure 1A or Figure 1B UE1 in the embodiment of the present application, the second UE described in each embodiment of the present application is, for example, Figure 1A or Figure 1B UE2 in; or, the second UE described in each embodiment of the present application is, for example, Figure 1A or Figure 1B UE1 in the embodiment of the present application, the first UE described in each embodiment of the present application is, for example, Figure 1A or Figure 1B UE2 in .

[0087] This application embodiment provides a communication method, see Figure 2 , which is a flow chart of the method.

[0088] S201. A first UE sends first sidelink control information to a second UE, and correspondingly, the second UE receives the first sidelink control information from the first UE. The first sidelink control information may trigger the second UE to send sidelink CSI, for example, the first sidelink control information may trigger the second UE to send sidelink CSI to the first UE.

[0089] The first UE is a peer UE of the second UE. There is a PC5-RRC connection between the first UE and the second UE, and the PC5-RRC connection corresponds to a source layer-2ID and a destination layer-2ID pair. The source layer-2ID is the layer 2ID of the first UE, and the destination layer-2ID is the layer 2ID of the second UE. Alternatively, the source layer-2ID is the layer 2ID of the second UE, and the destination layer-2ID is the layer 2ID of the first UE. The first UE is a SL CSI triggering UE, that is, a UE that triggers CSI (or, a UE that triggers the opposite end to send side CSI to itself), which can be understood as the first UE triggering CSI reporting (that is, the first UE triggers CSI reporting, which can be understood as the first UE triggering the opposite end UE (such as the second UE) to send side CSI to the first UE), and the triggering method is, for example, that the first UE sends the first side control information; the second UE is a SL CSI reporting UE, that is, a UE that is triggered to send side CSI (or, a UE that is triggered to send side CSI to the opposite end).

[0090] The sidelink CSI reporting (SL-CSI reporting) process is used for a UE to provide sidelink CSI to the opposite UE. For example, the first UE can send the first sidelink control information to the second UE to trigger the second UE to send the sidelink CSI to the first UE, and the second UE sends the sidelink CSI to the first UE. The first sidelink control information is, for example, SCI, or the first sidelink control information can be carried in SCI, and optionally, the SCI is, for example, a secondary SCI. If the value of the "CSI request" field in the secondary SCI is "1", it indicates sidelink SCI triggering, indicating that the SCI triggers the opposite UE to send sidelink CSI. Among them, the UE that sends the first sidelink control information (e.g., the first UE) can be called a CSI triggering UE (CSI triggering UE). In addition, the UE that triggers CSI (e.g., the first UE) can also be called a peer UE. In addition, the first UE may also send a message to the second UE, for example, the message is a PC5-RRC message, the PC5-RRC message is, for example, an RRC reconfiguration sidelink (RRCReconfigurationSidelink) message, or may be other PC5-RRC messages. The PC5-RRC message may carry a sidelink delay limit CSI report (sl-LatencyBound-CSI-Report), sl-LatencyBound-CSI-Report is used to indicate the delay requirement from the associated sidelink CSI triggering to the sidelink CSI reporting, or, sl-LatencyBound-CSI-Report is used to indicate the delay requirement from receiving the first sidelink control information to sending CSI to the first UE.

[0091] The first UE may send a sidelink CSI reference signal (sidelink CSI-RS) in the PSSCH corresponding to the first sidelink control information. After receiving the sidelink CSI-RS, the second UE may perform measurements based on the sidelink CSI-RS to obtain the sidelink CSI. In addition, after receiving the first sidelink control information and the PC5-RRC message, the second UE may send the sidelink CSI to the first UE within the latency requirement indicated by the sl-LatencyBound-CSI-Report configured by the first UE, for example, the sidelink CSI is carried in the sidelink CSI reporting media access control control element (SL CSI reporting MAC CE). The SL CSI reporting MAC CE may include a channel quality indicator (CQI) and a rank indicator (RI). In addition, the SLCSI reporting MAC CE may be included in the SL MAC PDU.

[0092] The UE may maintain a sidelink CSI report timer (sl-CSI-ReportTimer) for each source layer-2ID and destination layer-2ID pair associated with the UE. The sl-CSI-ReportTimer is used for the UE that needs to send sidelink CSI (e.g., the second UE) to follow the delay requirement indicated by the UE that triggers the sidelink CSI (e.g., the first UE). The timing duration of the sl-CSI-ReportTimer may be determined based on the delay indicated by the sl-LatencyBound-CSI-Report. For example, the timing duration of the sl-CSI-ReportTimer is equal to the delay indicated by the sl-LatencyBound-CSI-Report, which may be, for example, 50 slots, or may be other durations.

[0093] For example, the first UE and the second UE correspond to a source layer-2ID and destination layer-2ID pair. After the second UE receives the first sidelink control information from the first UE, it determines that SL-CSI reporting is triggered. If the sl-CSI-ReportTimer corresponding to the source layer-2ID and destination layer-2ID pair is not in a running state, the second UE starts the sl-CSI-ReportTimer. When the sl-CSI-ReportTimer times out, if the second UE has not sent the sidelink CSI, the second UE cancels the triggered SL-CSI reporting, that is, the second UE does not send the sidelink CSI to the first UE. If the sl-CSI-ReportTimer is running and there are SL resources that can accommodate the SL CSI reporting MAC CE and its subheader, the second UE can generate and send the Sidelink CSI Reporting MAC CE and stop the sl-CSI-ReportTimer.

[0094] Optionally, after sending the first sidelink control information, the first UE may start the first timer (or timer 1) without starting the fourth timer. The first timer may indicate the time for a UE to monitor the sidelink control information after triggering SL CSI reporting. The first UE may monitor the sidelink control information during the running time of the first timer to wait for receiving the sidelink CSI from the second UE. For example, the first UE may start the first timer in the first time domain unit after the PSCCH corresponding to the first sidelink control information (or the first sidelink control information itself, or the PSSCH corresponding to the first sidelink control information, or the HARQ feedback from the second UE for the SL transmission corresponding to the first sidelink control information). The SL transmission may refer to the transmission of the PSSCH, or to the transmission of the PSCCH and the PSSCH. The HARQ feedback of the SL transmission corresponding to the first sidelink control information means that the first sidelink control information may schedule the SL transmission, and the receiving end (e.g., the second UE) may send the HARQ feedback of the SL transmission after receiving the SL transmission to indicate whether the SL transmission is received successfully. The "time domain unit" described in the embodiment of the present application is, for example, an orthogonal frequency division multiplexing (OFDM) symbol, or a time slot, or a mini-slot, etc. In the embodiment of the present application, for SCI, the first time domain unit after the SCI may refer to the first time domain unit located in the time domain after the time domain position of the secondary SCI corresponding to the SCI. Wherein, the SCI is, for example, a primary SCI or a secondary SCI. If the SCI is a primary SCI, the secondary SCI corresponding to the SCI refers to the secondary SCI corresponding to the primary SCI, and if the SCI is a secondary SCI, the secondary SCI corresponding to the SCI is the SCI itself. If the SCI is a primary SCI and a secondary SCI, the secondary SCI corresponding to the SCI is the secondary SCI in the SCI. For a secondary SCI, the first time domain unit after the secondary SCI may refer to the first time domain unit located in the time domain after the last time domain unit where the secondary SCI is located. The first time domain unit after the SCI may refer to the first time domain unit located after the last time domain unit where the SCI is located in the time domain.

[0095] It should be noted that in the embodiments of the present application, there may be multiple monitoring behaviors of the first UE (for example, monitoring behaviors within the running time of the first timer, or monitoring behaviors within the first time period, etc.). For example, one monitoring behavior includes the first UE monitoring the side control information, wherein the monitoring side control information includes, for example, monitoring SCI, and the SCI may include a primary SCI and / or a secondary SCI; for another example, another monitoring behavior includes the first UE monitoring PSCCH; for another example, another monitoring behavior includes the first UE monitoring PSCCH and PSSCH. The first UE may select one of the above-mentioned monitoring behaviors to execute, and which one to select may be determined by the first UE, or configured by the second UE, or configured by the network device, or specified by the protocol, etc. In the embodiments of the present application, the first UE monitoring the side control information is taken as an example for description.

[0096] Or, optionally, after sending the first sidelink control information, the first UE may start a fourth timer (eg, called timer 4), and the timing duration of the fourth timer may indicate the preparation time of the second UE before sending the sidelink CSI. From the first UE sending the first sidelink control information to the second UE sending the sidelink CSI, the second UE needs a certain preparation time. During this preparation time, the second UE will not send the sidelink CSI, and the first UE will not receive the sidelink CSI from the second UE. Therefore, during this preparation time, the first UE can start the fourth timer, and the timing duration of the fourth timer can indicate the processing delay of the second UE. For example, the timing duration of the fourth timer may include one or more of the following: the time when the second UE decodes the PSSCH (or the first sidelink control information), the time when the second UE prepares to send the sidelink CSI, the reception and processing time of the physical sidelink feedback channel (PSFCH), the TX-RX / RX-TX switching time, and the minimum interval between the end of the last symbol of the PSSCH and the start of the first symbol of the corresponding PSFCH (for example, the sidelink minimum time interval PSFCH (sl-MinTimeGapPSFCH)). During the running time of the fourth timer, the first UE does not need to monitor the sidelink control information to save the power consumption of the first UE. When the fourth timer times out, the first UE restarts the first timer, and the first UE can monitor the side control information during the running time of the first timer to wait for receiving the side CSI from the second UE. For example, the first UE can start the fourth timer in the first time domain unit after the PSCCH corresponding to the first side control information (or the first side control information itself, or the PSSCH corresponding to the first side control information, or the HARQ feedback from the second UE for the SL transmission corresponding to the first side control information). For example, the timing duration of the fourth timer can be configured by the second UE, the second UE can send the third information to the first UE, the third information can indicate the timing duration of the fourth timer, and the first UE can know the timing duration of the fourth timer after receiving the third information from the second UE. The third information is included in the PC5-RRC message or MAC CE, for example. The timing duration of the fourth timer can also be configured by the first UE, or configured by the network device, or pre-configured. The first UE can send information indicating the timing duration of the fourth timer to the second UE. The timing duration of the first timer is configured by the first UE, for example, and the first UE can send information indicating the timing duration of the first timer to the second UE. Alternatively, the timing duration of the first timer may also be configured by the second UE, and the second UE sends information indicating the timing duration of the first timer to the first UE. Alternatively, the timing duration of the first timer may also be determined by the first UE and the second UE respectively.The following takes the configuration or determination of the timing duration of the first timer by the first UE as an example.

[0097] For example, if the first UE starts the fourth timer first and then starts the first timer, the first UE may configure the timing duration of the first timer to be the difference between the delay indicated by sl-LatencyBound-CSI-Report and the timing duration of the fourth timer. Alternatively, the first UE may configure the timing duration of the first timer to be equal to the delay indicated by sl-LatencyBound-CSI-Report. Alternatively, the first UE may obtain a channel busy ratio (CBR) and may determine the timing duration of the first timer based on the CBR (or determine the minimum timing duration of the first timer). For example, if the channel occupancy rate represented by the CBR is high (for example, the channel occupancy rate indicated by the CBR is greater than or equal to the first threshold), the timing duration of the first timer determined by the first UE may be longer (for example, the timing duration of the first timer is determined to be greater than the second threshold, or the minimum timing duration of the first timer is determined to be greater than the second threshold), because at this time the channel competition may be greater and the channel state is not very good, and the first UE may wait for a longer time to receive the sidelink CSI to improve the success rate of receiving the sidelink CSI; for another example, if the channel occupancy rate represented by the CBR is low (for example, the channel occupancy rate indicated by the CBR is less than the first threshold), the timing duration of the first timer determined by the first UE may be shorter (for example, the timing duration of the first timer is determined to be less than the third threshold, or the minimum timing duration of the first timer is determined to be less than the third threshold), because at this time the channel state is better, and the first UE may be able to receive the sidelink CSI in a shorter time without taking too long, thereby saving power consumption of the first UE. For example, the timing duration of the first timer may be proportional to or positively correlated with the CBR, or the timing duration of the first timer is not simply proportional to the CBR, but if the channel occupancy rate represented by the CBR is higher, the timing duration of the first timer may be longer. One or more of the first threshold, the second threshold, and the third threshold may be configured by the first UE, or by the network device, or pre-configured, or specified by a protocol, etc. The second threshold and the third threshold may be equal or unequal. When the value of the CBR remains unchanged, the longer the timing duration of the first timer, the more resources with lower interference the second UE can select when sending the side CSI, and the higher the sending success rate. The timing duration of the first timer is determined according to the CBR, so that a compromise can be made between the interference level of the resources selected by the second UE and the monitoring duration of the first UE, so as to improve the sending success rate of the second UE while saving the power consumption of the first UE as much as possible. For another example, the first UE may obtain a mapping relationship between a CBR range and a timing duration of a first timer, and determine the timing duration of the first timer according to the mapping relationship between the CBR range and the timing duration of the first timer and the obtained CBR.For example, the first UE determines that the timing duration of the first timer is the timing duration of the first timer corresponding to the CBR range where the obtained CBR is located. Alternatively, the first UE may obtain a mapping relationship between the CBR range and the minimum timing duration of the first timer, and the first UE may determine the minimum timing duration of the first timer based on the mapping relationship between the CBR range and the minimum timing duration of the first timer, and based on the obtained CBR. For example, the first UE determines that the minimum timing duration of the first timer is the minimum timing duration of the first timer corresponding to the CBR range where the obtained CBR is located. The mapping relationship between the CBR range and the timing duration of the first timer, or the mapping relationship between the CBR range and the minimum timing duration of the first timer, may be configured by a network device, or pre-configured, or specified by a protocol, etc. In the case where the first UE determines the minimum timing duration of the first timer, the first UE may determine the timing duration of the first timer, and the timing duration of the first timer is greater than or equal to the minimum timing duration of the first timer. Alternatively, the timing duration of the first timer or the minimum timing duration of the first timer may also be configured by the network device. For example, the network device may send a fourth message to the first UE and / or the second UE, and the fourth message may indicate the timing duration of the first timer (or, indicate the minimum timing duration of the first timer). After receiving the fourth message, the first UE and / or the second UE can obtain the timing duration of the first timer (or, obtain the minimum timing duration of the first timer). Optionally, the first UE sends information indicating the minimum timing duration of the first timer to the second UE. Alternatively, the second UE sends information indicating the minimum timing duration of the first timer to the first UE. In the case where the first UE and / or the second UE obtains the minimum timing duration of the first timer, the first UE determines the timing duration of the first timer, which is greater than or equal to the minimum timing duration of the first timer. The first UE sends information indicating the timing duration of the first timer to the second UE. Alternatively, the second UE sends information indicating the timing duration of the first timer to the first UE. The network device configures the timing duration of the first timer or the minimum timing duration of the first timer, so as to avoid as much as possible the situation that the second UE cannot select resources with less interference because the timing duration of the first timer is too short, or avoids as much as possible the situation that the second UE does not select resources within the running time of the first timer because the timing duration of the first timer is too short, or avoids as much as possible the situation that the network device of the second UE does not have time to schedule resources for the second UE to use within the timing duration of the first timer because the timing duration of the first timer is too short.

[0098] It should be noted that the network device described in the embodiment of the present application may be a network device serving the first UE or a network device serving the second UE. In addition, the network device serving the first UE and the network device serving the second UE may be the same network device or different network devices.

[0099] After the first UE starts the first timer, before the first timer times out, if the first UE receives the sidelink CSI from the second UE, or the first UE successfully decodes the MAC PDU including the sidelink CSI from the second UE, the first UE may stop running the first timer.

[0100] Alternatively, after the first UE starts the fourth timer, before the fourth timer expires, if the first UE receives sidelink CSI from the second UE, or the first UE successfully decodes the MAC PDU including the sidelink CSI from the second UE, the first UE may stop running the fourth timer.

[0101] Alternatively, the first sidelink control information will also schedule the corresponding PSSCH or MAC PDU. For example, the PSSCH is referred to as the first PSSCH, and the MAC PDU is referred to as the first MAC PDU. Then, when the first UE sends the first sidelink control information, it will also send the first PSSCH or the first MAC PDU to the second UE. The second UE needs to decode both the first sidelink control information and the first PSSCH (or the first MAC PDU). The second UE can send the sidelink CSI to the first UE only when both the first sidelink control information and the first PSSCH (or the first MAC PDU) are successfully decoded. Whether the decoding of the first sidelink control information or the first PSSCH (or the first MAC PDU) fails, the second UE may be unable to send the sidelink CSI to the first UE. After receiving the first sideline control information, the second UE may send second feedback information to the first UE. If the second UE fails to decode (or fails to receive) the first PSSCH (or the first MAC PDU), the second feedback information is, for example, a negative acknowledgement (NACK), used to indicate that the first PSSCH (or the first MAC PDU) has failed to be received. If the second UE successfully decodes (or successfully receives) the first PSSCH (or the first MAC PDU), the second feedback information is, for example, a positive acknowledgement (ACK), used to indicate that the first PSSCH (or the first MAC PDU) has been successfully received. For the first UE, after the first UE starts the first timer, before the first timer times out, if the second feedback information is used to indicate that the first PSSCH (or the first MAC PDU) has failed to be received, the first UE may stop the first timer. After the first UE starts the fourth timer, before the fourth timer times out, if the second feedback information is used to indicate that the first PSSCH (or the first MAC PDU) has failed to be received, the first UE may stop the fourth timer. Thus, the first UE will not start the first timer due to the timeout of the fourth timer. Because if the second feedback information indicates a failure to receive the first PSSCH (or the first MAC PDU), indicating that the second UE cannot send sidelink CSI to the first UE, the first UE does not need to wait to receive the sidelink CSI. The first UE can stop the first timer to save power consumption of the first UE.

[0102] For reference Figure 3, the first UE starts the first timer after sending the first side control information, and the first UE monitors the side control information during the running time of the first timer. For example, the first UE receives the second feedback information from the second UE during the running time of the first timer. If the second feedback information indicates that the reception of the first PSSCH (or the first MAC PDU) fails, the first UE stops the first timer. Since the second feedback information indicates that the reception of the first PSSCH fails, the first UE can optionally retransmit the first PSSCH (or the first MAC PDU). To retransmit the first PSSCH (or the first MAC PDU), the first UE also needs to send control information to the second UE to schedule the retransmitted first PSSCH (or the first MAC PDU). For example, the first UE sends the third side control information to the second UE, and the third side control information includes, for example, the primary SCI and / or the secondary SCI, and the third side control information can schedule the retransmitted first PSSCH (or the first MAC PDU). Optionally, because the first UE does not receive the side CSI from the second UE, the third side control information can also be used to trigger the second UE to send the side CSI to the first UE. Then, after sending the third sidelink control information, the first UE may restart the first timer to wait for receiving the sidelink CSI. For example, if the first UE receives the sidelink CSI from the second UE within the running time of the first timer, the first UE may stop the first timer.

[0103] You can refer to it again Figure 4 , the first UE starts the fourth timer after sending the first side control information, starts the first timer when the fourth timer times out, and the first UE monitors the side control information during the running time of the first timer. For example, the first UE receives the second feedback information from the second UE during the running time of the first timer. If the second feedback information indicates that the reception of the first PSSCH (or the first MAC PDU) fails, the first UE stops the first timer. Since the second feedback information indicates that the reception of the first PSSCH fails, the first UE can optionally retransmit the first PSSCH (or the first MAC PDU). For example, the first UE sends the third side control information to the second UE, and the third side control information can schedule the retransmission of the first PSSCH (or the first MAC PDU). Optionally, because the first UE has not received the side CSI from the second UE, the third side control information can also be used to trigger the second UE to send the side CSI to the first UE. Then, after sending the third side control information, in order to wait for the reception of the side CSI, the first UE can start the fourth timer again, and when the fourth timer times out, the first UE starts the first timer. For example, if the first UE receives the sidelink CSI from the second UE within the running time of the first timer, the first UE may stop the first timer.

[0104] in addition Figure 3 and Figure 4 The latency indicated by sl-LatencyBound-CSI-Report is also shown.

[0105] S202: The second UE sends second sidewalk control information to the first UE. Correspondingly, within a first time period after sending the first sidewalk control information, the first UE receives the second sidewalk control information from the second UE.

[0106] The second sidelink control information can be used to schedule a MAC PDU, which is a sidelink MAC PDU. The MAC PDU may be used to carry sidelink CSI and / or data. In other words, the MAC PDU scheduled by the second sidelink control information may carry the sidelink CSI required by the first UE (if this is the case, the second sidelink control information may be sent under the triggering of the first sidelink control information), or carry data (if this is the case, the second sidelink control information may not be sent under the triggering of the first sidelink control information, and it can be considered that the first sidelink control information and the second sidelink control information have no relationship), or carry sidelink CSI and data.

[0107] The second sidelink control information is used to schedule the MAC PDU, which can be understood as indicating that there is a transmission (such as a MAC PDU) on a sidelink shared channel (SL-SCH). Alternatively, the second control information can be used to schedule a transport block (TB), which can carry a MAC PDU.

[0108] The second sideline control information is, for example, SCI, or the second sideline control information is included in SCI. For example, the SCI includes a secondary SCI, or the SCI includes a primary SCI, or the SCI includes a primary SCI and a secondary SCI.

[0109] Take the second side control information being SCI as an example. The first UE receives the second side control information from the second UE. For example, the first UE receives an SCI, and the source layer-1ID and destination layer-1ID included in the SCI are consistent with the source and destination pair corresponding to the PC5-RRC connection between the first UE and the second UE. "Consistent" specifically means: the source layer-1ID included in the SCI is the 8 least significant bits (least significant bits, LSB) of the source layer-2ID of the second UE, and the destination layer-1ID included in the SCI is the 8 LSB of the destinationlayer-2ID (or source layer-2ID, or layer2-ID) of the first UE. The so-called 8 LSB refers to the lower 8 bits.

[0110] Alternatively, the first UE receives an SCI from the second UE, for example, the first UE receives an SCI, and the sidelink identification information corresponding to the SCI is consistent with the source and destination pair corresponding to the PC5-RRC connection between the first UE and the second UE. The sidelink identification information may include a cast type indicator, a source layer-1ID, and a destination layer-1ID. "Consistent" specifically means: the cast type indicator indicates that it is unicast, and the source layer-1ID included in the sidelink identification information is 8LSB of the source layer-2ID of the second UE, and the destination layer-1ID included in the sidelink identification information is 8LSB of the destination layer-2ID (or Source layer-2ID, or Layer2-ID) of the first UE.

[0111] The first time period can be used to wait for the sidewalk CSI, or the first time period can be used to receive the sidewalk CSI. It can be understood that the first UE expects to receive (or waits to receive) the sidewalk CSI in the first time period. That is, after the first UE sends the first sidewalk control information to the second UE, it needs to wait to receive the sidewalk CSI, so the first time period is set, and the first UE continues to monitor the sidewalk control information in the first time period to receive the sidewalk CSI. The first time period can be implemented in a variety of ways, as described below.

[0112] As a first optional implementation manner of the first time period, the first time period is a time period in which the first UE monitors the sidelink control information after sending the first sidelink control information, and it is considered that the first time period does not belong to the sidelink DRX activation time of the first UE.

[0113] As a second optional implementation of the first time period, the first time period is a time period during which the first UE monitors the sideline control information after sending the first sideline control information, and the first time period satisfies that neither the sl-DRX-InactivityTimer nor the sl-DRX-onDurationTimer of the first UE is running. In other words, the first time period is a time period during which the first UE monitors the sideline control information after sending the first sideline control information, and neither the sl-DRX-InactivityTimer nor the sl-DRX-onDurationTimer of the first UE is running. It can be understood that the time period that satisfies conditions 1 and 2 can be considered as the first time period. Condition 1 is that it is a time period during which the first UE monitors the sideline control information after sending the first sideline control information; condition 2 is that neither the sl-DRX-InactivityTimer nor the sl-DRX-onDurationTimer of the first UE is running. If the first time period adopts this implementation, the time period during which the first UE monitors the sideline control information after sending the first sideline control information may belong to the sideline DRX activation time of the first UE, or may not belong to the sideline DRX activation time of the first UE. If the time period in which the first UE monitors the sidelink control information after sending the first sidelink control information belongs to the sidelink DRX activation time of the first UE, then the time period in which the sl-DRX-InactivityTimer and / or sl-DRX-onDurationTimer of the first UE runs is considered not to belong to the first time period.

[0114] As a second optional implementation of the first time period, the first time period is a time period during which the first UE monitors the side control information after sending the first side control information, and the first time period satisfies that the sl-DRX-onDurationTimer, sl-DRX-InactivityTimer and sl-DRX-RetransmissionTimer of the first UE are not running. In other words, the first time period is: a time period during which the first UE monitors the side control information after sending the first side control information, and the sl-DRX-onDurationTimer, sl-DRX-InactivityTimer and sl-DRX-RetransmissionTimer of the first UE are not running. It can be understood that the time period that satisfies conditions 1 and 3 can be considered as the first time period. Condition 1 can refer to the introduction in the previous text; Condition 2 is that the sl-DRX-onDurationTimer, sl-DRX-InactivityTimer and sl-DRX-RetransmissionTimer of the first UE are not running. If the first time period adopts this implementation method, the time period during which the first UE monitors the sidelink control information after sending the first sidelink control information may belong to the sidelink DRX activation time of the first UE, or may not belong to the sidelink DRX activation time of the first UE. If the time period during which the first UE monitors the sidelink control information after sending the first sidelink control information belongs to the sidelink DRX activation time of the first UE, then if the time period during which one or more timers among sl-DRX-InactivityTimer, sl-DRX-onDurationTimer, or sl-DRX-RetransmissionTimer of the first UE are running, it is considered not to belong to the first time period.

[0115] As for which of the above methods is used to implement the first time period, it can be configured by the first UE or the second UE, or by a network device, or can be specified by a protocol, etc.

[0116] In the process of introducing the time mode of the first time period, the time period in which the first UE monitors the side control information after sending the first side control information is mentioned, for example, the time period is referred to as the second time period. The second time period can also be described as the time period in which the first UE receives the side control information after sending the first side control information. The description of the second time period can be understood as that after the first UE sends the first side control information, it monitors the side control information in order to receive the side CSI. The second time period can also be implemented in a variety of ways, which are introduced below by example.

[0117] As an optional implementation of the second time period, the second time period is, for example, a time period during which the first timer is running. For the first timer, reference may be made to the foregoing introduction.

[0118] As another optional implementation of the second time period, the second time period is, for example, a time period in which the first UE expects to receive (or, expects to monitor) the sidelink CSI after sending the first sidelink control information. For example, the maximum duration of the time period in which the first UE expects to receive the sidelink CSI after sending the first sidelink control information is the delay indicated by sl-LatencyBound-CSI-Report.

[0119] As another optional implementation of the second time period, the second time period is, for example, a time period in which sl-CSI-ReportTimer is running, and sl-CSI-ReportTimer may indicate the duration from when the second UE receives the first sidelink control information to when the second UE sends the sidelink CSI. sl-CSI-ReportTimer may be maintained in the second UE, and the first UE does not maintain sl-CSI-ReportTimer; or, sl-CSI-ReportTimer may be maintained in the second UE and the first UE, for example, after the first UE sends the first sidelink control information, it may also start sl-CSI-ReportTimer, for example, the first UE may start sl-CSI-ReportTimer at the same time as the first timer, or may start sl-CSI-ReportTimer at the same time as the fourth timer, or may start sl-CSI-ReportTimer at other times. Among them, for the second UE, the second UE sends the sidelink CSI to the first UE within the running time of sl-CSI-ReportTimer. For the first UE, sl-CSI-ReportTimer may indicate the maximum duration until the sidelink CSI is received, or in other words, sl-CSI-ReportTimer may indicate the maximum duration until the sidelink CSI is received. If sl-CSI-ReportTimer is maintained in the second UE, and the first UE does not maintain sl-CSI-ReportTimer, because the timing duration of the sl-CSI-ReportTimer of the second UE is determined according to the delay indicated by the sl-LatencyBound-CSI-Report of the second UE sent by the first UE to the second UE, although sl-CSI-ReportTimer is a timer maintained by the second UE, the running time of sl-CSI-ReportTimer can be estimated by the first UE. Alternatively, if both the first UE and the second UE maintain sl-CSI-ReportTimer, the first UE can determine the running time of the sl-CSI-ReportTimer of the first UE.

[0120] S203. The first UE does not start the sl-DRX-InactivityTimer of the first UE.

[0121] In an embodiment of the present application, if the first UE receives the second sidelink control information from the second UE within the first time period, the first UE does not start the sl-DRX-InactivityTimer. Since the first time period is already available for the first UE to receive the sidelink CSI, the first UE does not start the sl-DRX-InactivityTimer, and the reception of the sidelink CSI by the first UE will not be delayed. And since the first UE does not start the sl-DRX-InactivityTimer, the listening time of the first UE will not be extended (if the first UE starts the sl-DRX-InactivityTimer, the first UE needs to keep listening to the sidelink control information during the operation of the sl-DRX-InactivityTimer), thereby reducing the power consumption of the first UE.

[0122] For example, if the first UE receives second sidelink control information from the second UE within the first time period after sending the first sidelink control information to the second UE, the first UE may not start the sl-DRX-InactivityTimer of the first UE by default; or, whether the first UE starts the sl-DRX-InactivityTimer of the first UE within the first time period after sending the first sidelink control information to the second UE may also be configured by the network device, or determined by the first UE itself, or may also be configured by the second UE.

[0123] If the first UE determines it by itself, the first UE may inform the second UE of the determination result. For example, the first UE sends the first information to the second UE, and the first information may indicate that the first UE does not start the sl-DRX-InactivityTimer within the first time period after sending the message for triggering the second UE to send the side line CSI, or indicates that the first UE will start the sl-DRX-InactivityTimer within the first time period after sending the message for triggering the second UE to send the side line CSI (that is, if the SCI from the second UE is received, the first UE will start the sl-DRX-InactivityTimer). The first information is, for example, a message including the sl-LatencyBound-CSI-Report, or it may be other messages. Alternatively, if the first UE determines it by itself, the first UE may also inform the second UE of the determination result through the SCI. For example, the SCI may indicate that the first UE does not start the sl-DRX-InactivityTimer within the first time period after sending a message for triggering the second UE to send the sidelink CSI, or indicates that the first UE will start the sl-DRX-InactivityTimer within the first time period after sending a message for triggering the second UE to send the sidelink CSI. The SCI is, for example, the first sidelink control information (or the SCI including the first sidelink control information), or the SCI is, for example, other SCI except the first sidelink control information.

[0124] Alternatively, if determined by the second UE, the second UE may inform the first UE of the determination result. For example, the second UE sends first information to the first UE, and the first information may indicate that the first UE does not start the sl-DRX-InactivityTimer within the first time period after sending a message for triggering the second UE to send the sideline CSI, or indicates that the first UE will start the sl-DRX-InactivityTimer within the first time period after sending a message for triggering the second UE to send the sideline CSI. Alternatively, the second UE sends an SCI to the first UE, and the SCI may indicate that the first UE does not start the sl-DRX-InactivityTimer within the first time period after sending a message for triggering the second UE to send the sideline CSI, or indicates that the first UE will start the sl-DRX-InactivityTimer within the first time period after sending a message for triggering the second UE to send the sideline CSI. The SCI is, for example, the second sideline control information (or the SCI including the second sideline control information), or the SCI is, for example, other SCIs except the second sideline control information.

[0125] Optionally, the first information is, for example, a PC5-RRC message, or may also be a sidelink MAC control element (control element, CE), etc. The PC5-RRC message is, for example, an RRCReconfigurationSidelink message, or may also be other messages.

[0126] Alternatively, if determined by the network device, the network device may inform the first UE and / or the second UE of the determination result. Taking the process of the network device informing the first UE as an example, for example, the network device sends the first information to the first UE, and the first information may indicate that the first UE does not start the sl-DRX-InactivityTimer within the first time period after sending a message for triggering the second UE to send the sideline CSI, or indicates that the first UE will start the sl-DRX-InactivityTimer within the first time period after sending a message for triggering the second UE to send the sideline CSI. The first information at this time is, for example, included in the RRC message, or included in the MAC CE, or included in the downlink control information (downlink control information, DCI), or may also be included in other messages communicated between the network device and the UE.

[0127] If the first UE enters the sidewalk DRX activation time (if the first time period is also considered to belong to the sidewalk DRX activation time, then the sidewalk DRX activation time here does not include the first time period, but refers to the normal sidewalk DRX activation time), the first UE monitors the sidewalk control information. If the first UE monitors the sidewalk control information, the first UE can start the sl-DRX-InactivityTimer. That is, the first UE can start the sl-DRX-InactivityTimer according to the monitoring situation of the sidewalk control information during the normal sidewalk DRX activation time.

[0128] If the second UE also uses the sidelink DRX mechanism, optionally, the second UE may also control the corresponding timer in the same manner as the first UE. For example, if the second UE sends the second sidelink control information to the first UE within the first time period, the second UE may not start the sl-DRX-InactivityTimer of the second UE. This makes the sidelink DRX activation time of the first UE consistent with that of the second UE, which is conducive to communication between the first UE and the second UE. Alternatively, the second UE does not need to pay attention to the sl-DRX-InactivityTimer. For example, the sl-DRX-InactivityTimer of the second UE can be started or stopped in a normal manner, regardless of the first time period, or regardless of the first UE triggering the second UE to send the sidelink CSI.

[0129] Optionally, the embodiment of the present application may further include subsequent S204 to S209.

[0130] S204: The second UE sends a MAC PDU to the first UE within the first time period. The MAC PDU is, for example, a MAC PDU indicated by the second sideline control information. S203 may occur before S204, or S203 may occur after S204, or S203 and S204 may occur simultaneously.

[0131] There may be multiple different implementations of the second UE sending the MAC PDU to the first UE within the first time period, or in other words, there may be multiple different implementations of the MAC PDU sent by the second UE to the first UE within the first time period, which are described below with examples.

[0132] 1. A first implementation of a MAC PDU sent by the second UE to the first UE within a first time period, wherein the MAC PDU can include sidelink CSI but cannot include data, or the MAC PDU can include sidelink CSI but cannot include any information other than the sidelink CSI. Alternatively, the first implementation is described as the second UE can send sidelink CSI to the first UE but cannot send data to the first UE.

[0133] That is to say, in this implementation, the second UE can only send SL CSI reporting to the first UE in the first time period, but cannot send data to the first UE. It can be understood in reverse that in the first time period, the second UE cannot generate (or cannot send to the first UE) such a MAD PDU: there is no SL CSI reporting MAC CE in the MAC PDU (or, PSSCH) (it can be understood that the MAC PDU does not include side CSI), or the MAC PDU includes a non-zero MAC service data unit (service data unit, SDU). The so-called non-zero MAD SDU can be understood as including data. That is to say, the MAC PDU sent by the second UE to the first UE in the first time period needs to include the side CSI. If the side CSI is not included, the second UE cannot send the MAC PDU to the first UE. In addition, the MAC PDU sent by the second UE to the first UE in the first time period cannot include data. If data is included, even if the MAC PDU also includes the side CSI, the second UE cannot send the MAC PDU to the first UE. If the second UE sends the sidelink CSI to the first UE, the sidelink CSI is included in the SL CSI reporting MAC CE, for example, and the SL CSI reporting MAC CE may be included in the MAC PDU.

[0134] For reference Figure 5 , is a schematic diagram of a first UE receiving sidelink CSI in a first time period. Figure 5 The dashed box in represents the first time period. Figure 5 For example, the first time period does not belong to the sidewalk DRX activation time of the first UE, but the first time period overlaps with the sidewalk DRX activation time of the first UE. Figure 5 The area with diagonal lines in the middle represents the overlapping area of ​​the two. Figure 5 The latency indicated by sl-LatencyBound-CSI-Report is also shown. It can be seen that after the first UE triggers CSI to the second UE (for example, after the first UE sends the first side control information to the second UE), the first time period starts, and during the first time period, the first UE monitors the side control information. During the first time period, the first UE receives the side CSI from the second UE, but does not receive other information from the second UE.

[0135] For a corresponding newly transmitted SCI (for example, the second sidelink control information is the SCI, or the second sidelink control information is included in the SCI), the second UE selects a destination for the sidelink grant (SL grant) associated with the SCI, and the destination needs to satisfy that the PSCCH corresponding to the SCI (or, the SCI, or, the SL grant associated with the SCI) is temporally located within the time of monitoring the PSCCH and / or PSSCH after the destination triggers the SL CSI reporting of the second UE, and the second UE has the SL CSI reporting MAC CE of the destination (that is, the second UE needs to send sidelink CSI to the destination), or, the destination needs to satisfy that the PSCCH corresponding to the SCI (or, the SCI, or, the SL grant associated with the SCI) is within the sidelink DRX activation time of the destination. The SL grant associated with the SCI may refer to the SCI carried in the SL grant. The second UE may correspond to multiple logical channels, and different MAC PDUs include information from different logical channels. The second UE may need to send MAC PDU to multiple UEs (or multiple destinations), so the second UE needs to select the corresponding UE from these multiple UEs (or select the corresponding destination from these multiple destinations) to send the MAC PDU. For example, the second UE can make a selection according to the logical channel priority (LCP), and can give priority to sending the MAC PDU (or MAC CE) corresponding to the logical channel with a high priority. For the second sidelink control information, the second UE can select the destination corresponding to the MAC CE or logical channel with the highest priority from the MAC CEs and logical channels that meet the first rule. The first rule includes, for example, a first condition, and the first condition includes, for example: the first time domain resource is located in the first time period after the destination triggers the second UE to send the sidelink CSI (for example, the destination is the first UE, that is, the first time domain resource is located in the first time period after the first UE sends the first sidelink control information), or the first time domain information is located in the sidelink DRX activation time of the destination. The first time domain resource is the time domain resource occupied by the second sideline control information, or the time domain resource occupied by the PSCCH corresponding to the second sideline control information, or the time domain resource occupied by the SL grant corresponding to the second sideline control information.

[0136] Explaining the first condition in another way, the first condition includes: the PSCCH corresponding to the second sidelink control information (or the second sidelink control information itself, or the SL grant associated with the second sidelink control information) is within the sidelink DRX activation time of the destination corresponding to the MAC CE (including the SL CSI reporting MAC CE) or the logical channel, or the PSCCH corresponding to the second sidelink control information (or the second sidelink control information itself, or the SL grant associated with the second sidelink control information) monitors the PSCCH and / or PSSCH after the destination corresponding to the SL CSI reporting MAC CE triggers the SL CSI reporting of the second UE. In other words, the second UE sends the MAC PDU to the first UE as much as possible within the first time period after the first UE triggers the CSI, or sends the MAC PDU to the first UE within the sidelink DRX activation time of the first UE, so as to improve the first UE's success rate of receiving the MAC PDU.

[0137] If the first implementation manner is adopted, then if the first UE receives the sidelink CSI from the second UE, or the first UE successfully decodes the MAC PDU including the sidelink CSI from the second UE, the first UE may stop running the first timer.

[0138] In the first implementation, the second UE only needs to send the sidelink CSI to the first UE, which can reduce the sending time and improve the efficiency of the first UE in obtaining the sidelink CSI. If a transmission error requires retransmission, only the sidelink CSI needs to be retransmitted without retransmitting other information, which can save retransmission time.

[0139] 2. A second implementation of the MAC PDU sent by the second UE to the first UE within the first time period, the second UE can send sidelink CSI and / or data to the first UE, and the sidelink CSI and data can be included in the same MAC PDU or in different MAC PDUs. Alternatively, the second implementation is described as the second UE can send sidelink CSI and / or data to the first UE. The data, for example, includes data from a sidelink control channel (SCCH) and / or data from a sidelink traffic channel (STCH).

[0140] That is, in this implementation, the second UE may send sidelink CSI to the first UE without sending data within the first time period, or the second UE may send data to the first UE without sending sidelink CSI within the first time period, or the second UE may send sidelink CSI and data to the first UE within the first time period.

[0141] For reference Figure 6 , is a schematic diagram of a first UE receiving sidelink CSI in a first time period. Figure 6 The dashed box in represents the first time period. Figure 6 For example, the first time period does not belong to the sidewalk DRX activation time of the first UE, but the first time period overlaps with the sidewalk DRX activation time of the first UE. Figure 6 The area with diagonal lines in the middle represents the overlapping area of ​​the two. Figure 6 It also shows the latency indicated by sl-LatencyBound-CSI-Report. It can be seen that after the first UE triggers CSI to the second UE (for example, after the first UE sends the first sidelink control information to the second UE), the first time period starts, and during the first time period, the first UE monitors the sidelink control information. During the first time period, the first UE receives the sidelink CSI from the second UE and also receives data from the second UE. Figure 6 Take the example that data and sidelink CSI are included in different MAC PDUs.

[0142] For a corresponding newly transmitted SCI (for example, the second sidelink control information is the SCI, or the second sidelink control information is included in the SCI), the second UE selects a destination for the SL grant associated with the SCI, and the destination needs to satisfy that the PSCCH corresponding to the SCI (or, the SCI, or, the SL grant associated with the SCI) is temporally located within the time of monitoring the PSCCH and / or PSSCH after the destination triggers the SL CSI reporting of the second UE, or, the destination needs to satisfy that the PSCCH corresponding to the SCI (or, the SCI, or, the SL grant associated with the SCI) is within the sidelink DRX activation time of the destination. For example, the second UE can select a destination according to the LCP, and can give priority to sending a MAC PDU (or MAC CE) corresponding to a logical channel with a high priority. For the second sidelink control information, the second UE can select the destination corresponding to the MAC CE or logical channel with the highest priority from the MAC CEs and logical channels that meet the first rule. The first rule includes, for example, a second condition, and the second condition includes, for example: the first time domain resource is located in a first time period after the destination triggers the second UE to send the sidelink CSI, or the first time domain information is located in the sidelink DRX activation time of the destination. The first time domain resource is the time domain resource occupied by the second sidelink control information, or the time domain resource occupied by the PSCCH corresponding to the second sidelink control information, or the time domain resource occupied by the SL grant corresponding to the second sidelink control information.

[0143] Explaining the second condition in another way, the first condition includes: the PSCCH corresponding to the second sidelink control information (or the second sidelink control information itself, or the SL grant associated with the second sidelink control information) is within the sidelink DRX activation time of the destination corresponding to the MAC CE (including the SL CSI reporting MAC CE) or the logical channel, or the PSCCH corresponding to the second sidelink control information (or the second sidelink control information itself, or the SL grant associated with the second sidelink control information) monitors the PSCCH and / or PSSCH after the destination corresponding to the SL CSI reporting MAC CE triggers the SL CSI reporting of the second UE. In other words, the second UE sends the MAC PDU to the first UE as much as possible within the first time period after the first UE triggers the CSI, or sends the MAC PDU to the first UE within the sidelink DRX activation time of the first UE, so as to improve the first UE's success rate of receiving the MAC PDU.

[0144] If this implementation is adopted, if the first UE only receives data from the second UE but does not receive the sidelink SCI, and if the first timer has not timed out, the first UE does not stop the first timer, but keeps the first timer running to wait for receiving the sidelink SCI from the second UE. If the first UE receives the sidelink CSI from the second UE, or the first UE successfully decodes the MAC PDU including the sidelink CSI from the second UE, the first UE may stop running the first timer. For this, please refer to Figure 6 .

[0145] In the second implementation, the second UE can send both the sidelink CSI and the data to the first UE, which can effectively utilize the first time period so that the first UE can obtain more information in the first time period. Moreover, the sidelink CSI and data can be included in one MAC PDU or in different MAC PDUs. For example, if one MAC PDU is not enough to carry the sidelink CSI and all the data that the second UE needs to send, the second UE can send through multiple MAC PDUs, which is more flexible.

[0146] 3. A third implementation of the MAC PDU sent by the second UE to the first UE within the first time period, the second UE can send sidelink CSI to the first UE, or send sidelink CSI and data to the first UE, but if data is to be sent, the sidelink CSI and data need to be included in the same MAC PDU. Alternatively, the third implementation can also be described as the second UE can send sidelink CSI to the first UE, or send sidelink CSI and data, and if the sidelink CSI and data are sent, the sidelink CSI and data are carried in the same MAC PDU. The data, for example, includes data from the SCCH and / or data from the STCH.

[0147] That is, in this implementation, the second UE may send the sidelink CSI to the first UE without sending data in the first time period, or the second UE may send the sidelink CSI and data to the first UE in the first time period. However, if the sidelink CSI and data are to be sent to the first UE, the data needs to be included in the same MAC PDU as the sidelink CSI, or in other words, the data can only be sent through the MAC PDU including the sidelink CSI, but not through the MAC PDU not including the sidelink CSI.

[0148] For reference Figure 7 , is a schematic diagram of a first UE receiving sidelink CSI in a first time period. Figure 7 The dashed box in represents the first time period. Figure 7 For example, the first time period does not belong to the sidewalk DRX activation time of the first UE, but the first time period overlaps with the sidewalk DRX activation time of the first UE. Figure 7 The area with diagonal lines in the middle represents the overlapping area of ​​the two. Figure 7 The latency indicated by sl-LatencyBound-CSI-Report is also shown. It can be seen that after the first UE triggers CSI to the second UE (for example, after the first UE sends the first sidelink control information to the second UE), the first time period starts, and during the first time period, the first UE monitors PSCCH and / or PSSCH. During the first time period, the first UE receives the sidelink CSI from the second UE and also receives data from the second UE, and the data and the sidelink CSI are included in the same MAC PDU.

[0149] It should also be noted that after the first UE sends the first side control information, it can actually start the first timer immediately, that is, the first time period will start immediately, that is, the moment when the first side control information is sent and the start moment of the first time period can be the same moment. However, considering that the first UE may have a certain amount of processing time, Figure 5 , Figure 6 and Figure 7There is a certain delay between the completion of sending the first side control information and the start time of the first time period.

[0150] For a corresponding newly transmitted SCI (for example, the second sidelink control information is the SCI, or the second sidelink control information is included in the SCI), the second UE selects a destination for the SL grant associated with the SCI, and the destination needs to satisfy that the PSCCH corresponding to the SCI (or, the SCI, or, the SL grant associated with the SCI) is temporally located within the time of monitoring the PSCCH and / or PSSCH after the destination triggers the SL CSI reporting of the second UE, and the second UE has the SL CSI reporting MAC CE of the destination, or the destination needs to satisfy that the PSCCH corresponding to the SCI (or, the SCI, or, the SL grant associated with the SCI) is within the sidelink DRX activation time of the destination. For example, the second UE may select a destination according to the LCP, and may give priority to sending a MAC PDU (or MAC CE) corresponding to a logical channel with a high priority. For the second sidelink control information, the second UE may select a destination corresponding to a MAC CE or a logical channel with the highest priority from the MAC CEs and logical channels that satisfy the first rule. The first rule includes, for example, a third condition, and the third condition includes, for example: the first time domain resource is located in the first time period after the destination triggers the second UE to send the sidelink CSI, or the first time domain information is located in the sidelink DRX activation time of the destination. The first time domain resource is the time domain resource occupied by the second sidelink control information, or the time domain resource occupied by the PSCCH corresponding to the second sidelink control information, or the time domain resource occupied by the SL grant corresponding to the second sidelink control information.

[0151] Explaining the third condition in another way, the third condition includes: the PSCCH corresponding to the second sidelink control information (or the second sidelink control information itself, or the SL grant associated with the second sidelink control information) is within the sidelink DRX activation time of the destination corresponding to the MAC CE (including the SL CSI reporting MAC CE) or the logical channel, or the PSCCH corresponding to the second sidelink control information (or the second sidelink control information itself, or the SL grant associated with the second sidelink control information) monitors the PSCCH and / or PSSCH after the destination corresponding to the SL CSI reporting MAC CE triggers the SL CSI reporting of the second UE. In other words, the second UE sends a MAC PDU to the first UE as much as possible within the first time period after the first UE triggers the CSI, or sends a MAC PDU to the first UE within the sidelink DRX activation time of the first UE, so as to improve the first UE's success rate of receiving the MAC PDU.

[0152] If this implementation is adopted, if the first UE receives the sidelink CSI from the second UE, or the first UE successfully decodes the MAC PDU including the sidelink CSI from the second UE, the first UE may stop running the first timer.

[0153] In the third implementation, the second UE can send both the sidelink CSI and the data to the first UE, which can effectively utilize the first time period, so that the first UE can obtain more information in the first time period. Moreover, the sidelink CSI and the data can be included in one MAC PDU, which can improve the transmission efficiency and the efficiency of the first UE in obtaining the sidelink CSI. Moreover, if retransmission is involved, only one MAC PDU needs to be retransmitted, which can also reduce the retransmission time.

[0154] In S204, the second UE may send a MAC PDU to the first UE in accordance with one of the above three implementations, and the method used by the second UE is, for example, called the first method, and the first method is, for example, the first implementation, the second implementation, or the third implementation as described above. The first method may be determined by the second UE itself, or determined by the first UE and notified to the second UE, or may be configured by a network device, or may be specified by a protocol, etc.

[0155] If the first mode is determined by the second UE itself, then the second UE needs to inform the first UE after determining the first mode, so that the first UE can clearly understand the mode in which the second UE sends the MAC PDU, so as to correctly receive the MAC PDU from the second UE. For example, the second UE sends the second information to the first UE, and the second information may indicate the first mode. Alternatively, the second UE sends the SCI to the first UE, and the SCI may indicate the first mode. The SCI is, for example, the second side control information (or the SCI including the second side control information), or, the SCI is, for example, other SCI except the second side control information.

[0156] Alternatively, if the first mode is determined by the first UE, then the first UE needs to inform the second UE after determining the first mode, so that the second UE can send a MAC PDU to the first UE according to the first mode. For example, the first UE sends second information to the second UE, and the second information may indicate the first mode. Alternatively, the first UE sends SCI to the second UE, and the SCI may indicate the first mode. The SCI is, for example, the first side control information (or the SCI including the first side control information), or the SCI is, for example, other SCI except the first side control information.

[0157] Optionally, the first information is, for example, a PC5-RRC message, or may also be a MAC CE, etc. The PC5-RRC message is, for example, an RRCReconfigurationSidelink message, or may also be other messages.

[0158] Alternatively, if the first mode is determined by the network device, the network device needs to inform the first UE and / or the second UE after determining the first mode. Taking the network device informing the first UE as an example, for example, the network device sends second information to the first UE, and the second information may indicate the first mode. At this time, the second information is included in an RRC message, or in a MAC CE, or in a DCI, or in other messages communicated between the network device and the UE.

[0159] S205. The first UE decodes the MAC PDU.

[0160] The first UE receives the second sidelink control information and the MAC PDU, and decodes the MAC PDU according to the second sidelink control information.

[0161] S206: When the decoding of the MAC PDU fails, the first UE starts a second timer (or referred to as timer 2). The second timer is, for example, sl-DRX-RetransmissionTimer of the first UE, or may be a timer newly defined in the embodiment of the present application.

[0162] If the first UE fails to decode the MAC PDU, the first UE cannot obtain the information included in the MAC PDU (for example, the MAC PDU carries sidelink CSI and / or data), then the first UE can send first feedback information to the second UE, and the first feedback information, for example, indicates that the MAC PDU reception failed (for example, the first feedback information is a negative acknowledgment (NACK)). In addition to sending the first feedback information, the first UE can also start a second timer.

[0163] For example, the first UE may start the second timer when it fails to decode the MAC PDU. Alternatively, if the second sidelink control information indicates that the MAC PDU includes the sidelink CSI but does not include data, then the first UE may start the second timer if it fails to decode the MAC PDU; and if the second sidelink control information indicates that the MAC PDU includes the sidelink CSI and data, or indicates that the MAC PDU does not include the sidelink CSI (it may also indicate that it includes data or does not include data), then even if the first UE fails to decode the MAC PDU, it may not start the second timer, that is, it may not have to wait for the retransmission of the MAC PDU. The second sidelink control information may indicate the content included in the MAC PDU. If the second sidelink control information indicates that the MAC PDU includes the sidelink CSI but does not include data, and the first UE does not decode the MAC PDU successfully, then because only the sidelink CSI needs to be retransmitted, the required retransmission time is not long, so the first UE may start the second timer to wait for retransmission. If the second sidelink control information indicates that the MAC PDU includes the sidelink CSI and data, the first UE does not need to wait for retransmission, because the retransmission process includes the retransmission of the sidelink CSI and the retransmission of the data, and the required retransmission time is long, which causes a large power loss for the first UE. Alternatively, if the second sidelink control information indicates that the MAC PDU does not include the sidelink CSI, the first UE actually mainly wants to receive the sidelink CSI. If the MAC PDU does not include the sidelink CSI, the first UE does not need to wait for the retransmission of the MAC PDU.

[0164] For example, the first UE may start the second timer in the first time domain unit after the PSSCH corresponding to the second sideline control information ends. For another example, the first UE may start the second timer in the first time domain unit after the first feedback information is sent.

[0165] S207: During the running time of the second timer, the first UE monitors the sidelink control information to wait for the retransmission of the MAC PDU.

[0166] During the running time of the second timer, the first UE monitors the sidelink control information to wait for the retransmission of the MAC PDU. The running time of the second timer may belong to the sidelink DRX activation time of the first UE, or may not belong to the sidelink DRX activation time of the first UE. Before the second timer times out, if the first UE receives the retransmitted MAC PDU, the first UE may stop the second timer.

[0167] S208. In the case of a failure in decoding the MAC PDU, the first UE starts a third timer. The timing duration of the third timer may, for example, indicate the preparation time of the second UE before retransmitting (or resending) the MAC PDU. The third timer may, for example, be the sl-DRX-HARQ-RTT-Timer of the first UE, or may also be a newly defined timer in an embodiment of the present application.

[0168] That is to say, it takes a certain amount of time from the first UE sending the first feedback information to the second UE retransmitting the MAC PDU, that is, the second UE needs a certain amount of preparation time to retransmit the MAC PDU, and it is obvious that the first UE will not receive the retransmitted MAC PDU during the preparation time of the second UE. Therefore, the first UE can start the third timer. During the running time of the third timer, the first UE does not need to monitor the side control information to save the power consumption of the first UE. For example, the third timer can be started in the first time domain unit after the PSSCH corresponding to the second side control information ends. For another example, the first UE can start the third timer in the first time domain unit after sending the first feedback information.

[0169] For example, if the first UE fails to decode the MAC PDU, the third timer can be started. Alternatively, if the second sidelink control information indicates that the MAC PDU includes sidelink CSI but not data, then if the first UE fails to decode the MAC PDU, the third timer can be started; and if the second sidelink control information indicates that the MAC PDU includes sidelink CSI and data, or indicates that the MAC PDU does not include sidelink CSI (it may also indicate that it includes data or does not include data), then even if the first UE fails to decode the MAC PDU, the third timer may not be started, that is, it is not necessary to wait for the retransmission of the MAC PDU. For the reasons for such processing, please refer to the introduction of S206.

[0170] S209: When the third timer times out, the first UE starts the second timer, and then executes S207.

[0171] S206 and S208-S209 are two parallel solutions, and the first UE selects one of the solutions to execute. As for which solution to select, it can be determined by the first UE itself, or configured by the network device, or stipulated by the protocol.

[0172] Regardless of whether the first UE directly starts the second timer or starts the second timer when the third timer times out, if the sl-CSI-ReportTimer times out, the first UE may stop the second timer, wherein the sl-CSI-ReportTimer may be maintained in the first UE and the second UE, or maintained in the second UE, for which reference may be made to the foregoing description; or, when the second duration after the first UE triggers SL CSI reporting (for example, the first UE sends the first sideline control information) arrives, the first UE may stop the second timer; or, when the maximum duration for expecting to receive the sideline CSI after the first UE triggers SL CSI reporting (or, the duration for expecting to receive the sideline CSI after the first UE triggers SL CSI reporting) arrives, the first UE may stop the second timer. Wherein, the second duration is, for example, the delay indicated by sl-LatencyBound-CSI-Report, and the timing duration of sl-CSI-ReportTimer may be determined according to the delay indicated by sl-LatencyBound-CSI-Report. If the sl-CSI-ReportTimer times out, or the delay indicated by the sl-LatencyBound-CSI-Report is reached, or the maximum duration that the first UE expects to receive the sidelink CSI is reached, it may indicate that the second UE will no longer send the sidelink CSI to the first UE. Therefore, the first UE does not need to wait in vain to save power consumption.

[0173] In addition, the embodiments of the present application all take the first UE triggering the second UE to send the sidelink CSI as an example, but there is another situation, the first UE can also trigger the second UE to send resource information, if the first UE triggers the second UE to send resource information, then the behavior of the first UE and the second UE can also be applicable to the scheme provided by the embodiments of the present application, that is, the "sidelink CSI" mentioned above can also be replaced with "sidelink resource information". In addition, if the sidelink CSI is replaced with the sidelink resource information, the sl-CSI-ReportTimer can also be replaced with a timer related to the sidelink resource information, and / or, the sl-LatencyBound-CSI-Report can also be replaced with the delay indication information related to the sidelink resource information. For example, sl-LatencyBound-CSI-Report can be replaced with sl-LatencyBound-Resource-Report, and sl-LatencyBound-Resource-Report is used to indicate the delay requirement from the associated triggering of the sidelink resource information to the sending of the sidelink resource information. sl-CSI-ReportTimer can be replaced with a sidelink resource report timer (sl-Resource-ReportTimer) accordingly. sl-Resource-ReportTimer is used for the UE (e.g., the second UE) that needs to send sidelink resource information to follow the delay requirement indicated by the UE (e.g., the first UE) that triggers the sidelink resource information. The timing duration of sl-Resource-ReportTimer can be determined according to the delay indicated by sl-LatencyBound-Resource-Report. For example, the timing duration of sl-Resource-ReportTimer is equal to the delay indicated by sl-LatencyBound-Resource-Report, and the delay is, for example, 50 time slots (slots), or it can also be other durations.

[0174] The resource information is briefly introduced as follows. In the sidelink communication, inter-UE coordination includes UE1 (e.g., the second UE) sending information indicating a group of resources to UE2 (e.g., the first UE), and the information indicating a group of resources can be understood as the resource information. The group of resources can include one or more of the following (1), (2), and (3).

[0175] (1) Preferred resources for UE2 to perform SL transmission. For example, UE1 determines the preferred resources for UE2 to perform SL transmission based on the sensing result.

[0176] (2) Non-preferred resources for UE2 to perform SL transmission. For example, UE1 determines the non-preferred resources for UE2 to perform SL transmission based on sensing results and / or potential resource conflicts.

[0177] (3) Detection of conflicting resources: For example, if UE1 detects that the SL transmission resources to be used by UE2 and UE3 overlap, it is detected that a resource conflict has occurred.

[0178] The information indicating a group of resources may be carried in a MAC CE, or may be included in an SCI, such as a secondary SCI.

[0179] In an embodiment of the present application, if the first UE receives the second sidelink control information from the second UE within the first time period, the first UE may not start the sl-DRX-inactivityTimer of the first UE. Since the first UE does not start the sl-DRX-inactivityTimer, the first UE is prevented from monitoring the channel during the operation of the sl-DRX-inactivityTimer, thereby reducing the power consumption of the first UE. Therefore, the solution of the embodiment of the present application can reduce the problem of excessive increase in power consumption of the UE due to receiving SL CSI reporting after triggering SL CSI reporting.

[0180] Figure 8 A schematic diagram of the structure of a communication device 800 provided in an embodiment of the present application is given. The communication device 800 may be Figure 2 The first terminal device described in the embodiment shown is used to implement the method performed by the first terminal device in the above method embodiment. Alternatively, the communication device 800 may also be Figure 2 The second terminal device described in the embodiment shown is used to implement the method corresponding to the second terminal device in the above method embodiment. For specific functions, please refer to the description in the above method embodiment.

[0181] The communication device 800 includes one or more processors 801. The processor 801 may also be referred to as a processing unit, which may implement certain control functions. The processor 801 may be a general-purpose processor or a dedicated processor, etc. For example, it may include: a baseband processor, a central processing unit, an application processor, a modem processor, a graphics processor, an image signal processor, a digital signal processor, a video codec processor, a controller, a memory, and / or a neural network processor, etc. The baseband processor may be used to process communication protocols and communication data. The central processing unit may be used to control the communication device 800, execute software programs and / or process data. Different processors may be independent devices, or they may be integrated into one or more processors, for example, integrated into one or more dedicated integrated circuits.

[0182] Optionally, the communication device 800 includes one or more memories 802 for storing instructions 804, and the instructions 804 can be executed on the processor so that the communication device 800 performs the method described in the above method embodiment. Optionally, data can also be stored in the memory 802. The processor and the memory can be set separately or integrated together.

[0183] Optionally, the communication device 800 may include instructions 803 (sometimes also referred to as codes or programs), and the instructions 803 may be executed on the processor so that the communication device 800 executes the method described in the above embodiment. The processor 801 may store data.

[0184] Optionally, the communication device 800 may further include a transceiver 805 and an antenna 806. The transceiver 805 may be referred to as a transceiver unit, a transceiver, a transceiver circuit, a transceiver, an input / output interface, etc., and is used to implement the transceiver function of the communication device 800 through the antenna 806.

[0185] Optionally, the communication device 800 may also include one or more of the following components: a wireless communication module, an audio module, an external memory interface, an internal memory, a universal serial bus (USB) interface, a power management module, an antenna, a speaker, a microphone, an input / output module, a sensor module, a motor, a camera, or a display screen, etc. It is understood that in some embodiments, the communication device 800 may include more or fewer components, or some components may be integrated, or some components may be separated. These components may be implemented in hardware, software, or a combination of software and hardware.

[0186] The processor 801 and the transceiver 805 described in the embodiments of the present application may be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit (RFID), a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), or an electronic device, etc. The communication device described herein may be an independent device (e.g., an independent integrated circuit, a mobile phone, etc.), or may be a part of a larger device (e.g., a module that can be embedded in other devices). For details, please refer to the aforementioned description of the terminal device and the network device, which will not be repeated here.

[0187] The present application embodiment provides a terminal device, which can be used in the above embodiments (for the convenience of description, referred to as UE). The terminal device includes a Figure 2 The corresponding means, units and / or circuits of the first terminal device and / or the second terminal device functions described in the illustrated embodiments. For example, the terminal device includes a transceiver module to support the terminal device to implement the transceiver function, and a processing module to support the terminal device to process the signal.

[0188] Fig. 9 A schematic diagram of the structure of a terminal device provided in an embodiment of the present application is given.

[0189] The terminal device 900 can be applied to Figure 1A or Figure 1B In the network architecture shown in Figure 1, Fig. 9 Only the main components of the terminal device 900 are shown. Fig. 9 As shown, the terminal device 900 includes a processor, a memory, a control circuit, an antenna, and an input-output device. The processor is mainly used to process the communication protocol and communication data, and to control the entire terminal device 900, execute the software program, and process the data of the software program. The memory is mainly used to store the software program and data. The control circuit is mainly used for converting the baseband signal and the radio frequency signal and processing the radio frequency signal. The antenna is mainly used to send and receive radio frequency signals in the form of electromagnetic waves. The input-output device, such as a touch screen, a display screen, a microphone, a keyboard, etc., is mainly used to receive data input by the user and output data to the user.

[0190] Taking the terminal device 900 as a mobile phone as an example, when the terminal device 900 is turned on, the processor can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor performs baseband processing on the data to be sent, and outputs the baseband signal to the control circuit. The control circuit performs radio frequency processing on the baseband signal and then sends the radio frequency signal outward through the antenna in the form of electromagnetic waves. When data is sent to the terminal device 900, the control circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data.

[0191] Those skilled in the art will appreciate that for ease of description, Fig. 9 Only one memory and processor are shown. In some embodiments, the terminal device 900 may include multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, etc., which is not limited in the embodiments of the present invention.

[0192] As an optional implementation, the processor may include a baseband processor and a central processing unit. The baseband processor is mainly used to process the communication protocol and communication data, and the central processing unit is mainly used to control the entire terminal device 900, execute software programs, and process software program data. Fig. 9 The processor in the embodiment integrates the functions of the baseband processor and the central processing unit. It can be understood by those skilled in the art that the baseband processor and the central processing unit can also be independent processors, which are interconnected through technologies such as buses. The terminal device 900 may include multiple baseband processors to adapt to different network formats, and the terminal device 900 may include multiple central processing units to enhance its processing capabilities. The various components of the terminal device 900 may be connected through various buses. The baseband processor may also be described as a baseband processing circuit or a baseband processing chip. The central processing unit may also be described as a central processing circuit or a central processing chip. The function of processing the communication protocol and the communication data may be built into the processor, or may be stored in the storage unit in the form of a software program, and the processor executes the software program to implement the baseband processing function.

[0193] In one example, the antenna with transceiver functions and the control circuit can be regarded as the transceiver unit 910 of the terminal device 900, and the processor with processing function can be regarded as the processing unit 920 of the terminal device 900. Fig. 9As shown, the terminal device 900 includes a transceiver unit 910 and a processing unit 920. The transceiver unit may also be referred to as a transceiver, a transceiver, a transceiver device, etc. Optionally, the device used to implement the receiving function in the transceiver unit 910 may be regarded as a receiving unit, and the device used to implement the sending function in the transceiver unit 910 may be regarded as a sending unit, that is, the transceiver unit 910 includes a receiving unit and a sending unit. Exemplarily, the receiving unit may also be referred to as a receiver, a receiver, a receiving circuit, etc., and the sending unit may be referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

[0194] Those of ordinary skill in the art will appreciate that the units and steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0195] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the scheme of this embodiment.

[0196] If the functions are implemented in the form of software functional 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, 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, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned computer-readable storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, computer-readable media may include random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), universal serial bus flash disk, mobile hard disk, or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer. In addition, by way of example but not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), or direct rambus RAM (DR RAM).

[0197] The above is only a specific implementation of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the embodiments of the present application, which should be included in the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application should be based on the protection scope of the claims.

Claims

1. A communication method, applied to a first terminal device, It is characterized in that The first terminal device is configured with sidelink DRX, and the method includes: Sending first sidelink control information to a second terminal device, where the first sidelink control information is used to trigger the second terminal device to send sidelink channel state information; receiving second sideline control information from the second terminal device within a first time period after sending the first sideline control information, wherein the second sideline control information is used to schedule a MAC PDU, and the first time period is used to receive the sideline channel state information; The sidewalk DRX inactivity timer is not started.

2. The method according to claim 1, It is characterized in that The first time period satisfies: it is a time period during which the first terminal device monitors the sideline control information after sending the first sideline control information, and does not belong to the sideline DRX activation time of the first terminal device; or, The first time period satisfies: it is a time period during which the first terminal device monitors the sidewalk control information after sending the first sidewalk control information, and both the sidewalk DRX duration timer and the sidewalk DRX inactivation timer of the first terminal device are not running; or, The first time period satisfies: it is the time period for the first terminal device to monitor the sidelink control information after sending the first sidelink control information, and the sidelink DRX duration timer, the sidelink DRX retransmission timer and the sidelink DRX inactivation timer of the first terminal device are not running.

3. The method according to claim 2, It is characterized in that The time period during which the first terminal device monitors the side control information after sending the first side control information is the time period during which the first timer runs, and the first timer is started after the first terminal device sends the first side control information; or The time period during which the first terminal device monitors the sidelink control information after sending the first sidelink control information is the time period during which the first terminal device expects to receive the sidelink channel state information after sending the first sidelink control information; or, The time period during which the first terminal device monitors the side control information after sending the first side control information is the time period during which the side channel status information report timer runs. The side channel status information report timer is used to indicate the maximum duration until the side channel status information is sent.

4. The method according to any one of claims 1 to 3, It is characterized in that The method further comprises: Sending first information to the second terminal device, where the first information is used to instruct the first terminal device not to start the sidelink DRX inactivity timer within the first time period after sending the first sidelink control information; or, receiving first information from the second terminal device, where the first information is used to instruct the first terminal device not to start the sideline DRX inactivity timer within the first time period after sending the first sideline control information; or, receiving first information from a network device, where the first information is used to instruct the first terminal device not to start the sidelink DRX inactivity timer within the first time period after sending the first sidelink control information; or, The first sidelink control information is also used to instruct the first terminal device not to start the sidelink DRX inactivation timer within the first time period after sending the first sidelink control information.

5. The method according to any one of claims 1 to 3, It is characterized in that The method further comprises: Sending second information to the second terminal device, where the second information is used to indicate a first mode applied to the first time period, where the first mode is a mode in which the second terminal device sends information to the first terminal device, wherein the first mode includes: The second terminal device can send sidelink channel state information to the first terminal device, but cannot send data to the first terminal device; or, The second terminal device is capable of sending sidelink channel state information and / or data to the first terminal device; or, The second terminal device is capable of sending sidelink channel state information, or sending sidelink channel state information and data to the first terminal device, and the sidelink channel state information and the data are carried in the same MAC PDU.

6. The method according to any one of claims 1 to 3, It is characterized in that The method further comprises: receiving the MAC PDU from the second terminal device; In case of a failure in decoding the MAC PDU, starting a second timer; While the second timer is running, the sideline control information is monitored to wait for the retransmitted MAC PDU.

7. The method according to claim 6, It is characterized in that In case that decoding of the MAC PDU fails, starting a second timer includes: When decoding of the MAC PDU fails and the second sidelink control information indicates that the MAC PDU includes sidelink channel state information but does not include data, the second timer is started.

8. The method according to claim 6, It is characterized in that Starting the second timer includes: starting the second timer in the first time domain unit after the sidelink data channel corresponding to the second sidelink control information ends; or, The second timer is started in the first time domain unit after the first feedback information is sent, where the first feedback information is feedback information corresponding to the MAC PDU sent to the second terminal device.

9. The method according to any one of claims 1 to 3, It is characterized in that The method further comprises: receiving the MAC PDU from the second terminal device; In case of a failure in decoding the MAC PDU, starting a third timer, wherein the timing duration of the third timer is used to indicate a preparation time of the second terminal device before resending the MAC PDU; When the third timer times out, starting the second timer; While the second timer is running, the sideline control information is monitored to wait for the retransmitted MAC PDU.

10. The method according to claim 9, It is characterized in that In case that decoding of the MAC PDU fails, starting a third timer includes: When decoding of the MAC PDU fails and the second sidelink control information indicates that the MAC PDU includes sidelink channel state information but does not include data, the third timer is started.

11. The method according to claim 9, It is characterized in that Starting the third timer includes: starting the third timer in the first time domain unit after the sidelink data channel corresponding to the second sidelink control information ends; or, The third timer is started in the first time domain unit after the first feedback information is sent, where the first feedback information is feedback information corresponding to the MAC PDU sent to the second terminal device.

12. The method according to claim 6, It is characterized in that The method further comprises: When the sidelink channel state information reporting timer of the second terminal device times out, stopping the second timer; or, When a second time duration after sending the first sidelink control information arrives, stop the second timer, the second time duration is used to wait for receiving the sidelink channel state information, and the timing duration of the sidelink channel state information report timer of the second terminal device is determined according to the second time duration; or, When the expected duration for receiving the sidelink channel state information after sending the first sidelink control information arrives, the second timer is stopped.

13. The method according to any one of claims 1 to 3, It is characterized in that The method further comprises: receiving the MAC PDU from the second terminal device; When decoding of the MAC PDU fails and the second sidelink control information indicates that the MAC PDU does not include sidelink channel state information, the second timer is not started, and the running period of the second timer is used to monitor the sidelink control information.

14. The method according to any one of claims 1 to 3, 7, 8, 10, 11, and 12, It is characterized in that The method further comprises: After sending the first sidewalk control information, a first timer is started, and the timing duration of the first timer is the first time period.

15. The method according to any one of claims 1 to 3, 7, 8, 10, 11, and 12, It is characterized in that The method further comprises: After sending the first sidelink control information, starting a fourth timer, the timing duration of the fourth timer is used to indicate the preparation time of the second terminal device before sending the sidelink channel state information; When the fourth timer times out, the first timer is started, and the timing duration of the first timer is the first time period.

16. The method according to claim 15, It is characterized in that The method further comprises: Receive third information from the second terminal device, where the third information is used to indicate the timing duration of the fourth timer.

17. The method according to claim 14, It is characterized in that The running time of the first timer is the sidelink DRX activation time of the first terminal device; or, The portion of the running time of the first timer that does not overlap with the sidelink DRX activation time of the first terminal device does not belong to the sidelink DRX activation time of the first terminal device; or, During the running time of the first timer, the time during which the sidelink DRX duration timer and / or the sidelink DRX inactivation timer of the first terminal device is not running does not belong to the sidelink DRX activation time of the first terminal device; or, During the running time of the first timer, the time when one or more timers including the sidelink DRX duration timer, the sidelink DRX inactivation timer or the sidelink DRX retransmission timer of the first terminal device are not running does not belong to the sidelink DRX activation time of the first terminal device.

18. The method according to claim 14, It is characterized in that The method further comprises: receiving fourth information from a network device, where the fourth information is used to indicate a timing duration of the first timer; or, The timing duration of the first timer is determined according to the CBR.

19. The method according to claim 18, It is characterized in that Determining the timing duration of the first timer according to the CBR includes: When the channel occupancy indicated by the CBR is greater than or equal to a first threshold, determining the timing duration of the first timer to be a duration greater than a second threshold; and / or, When the channel occupancy indicated by the CBR is less than the first threshold, the timing duration of the first timer is determined to be less than a third threshold.

20. The method according to claim 14, It is characterized in that The method further comprises: receiving second feedback information from the second terminal device; If the second feedback information is used to indicate a reception failure of a first sidelink data channel, the first timer is stopped, where the first sidelink data channel is the sidelink data channel scheduled by the first sidelink control information.

21. A communication method, applied to a second terminal device, It is characterized in that include: Receiving first sideline control information from a first terminal device, where the first sideline control information is used to trigger the second terminal device to send sideline channel state information; Sending second sideline control information to the first terminal device, where the second sideline control information is used to schedule a MAC PDU; The sidewalk DRX inactivity timer is not started.

22. The method according to claim 21, It is characterized in that The method further comprises: The MAC PDU is sent to the first terminal device in a first manner applied to a first time period, the first time period being used for the first terminal device to wait for the sidelink channel state information, the first manner comprising: capable of sending sidelink channel state information to the first terminal device, but unable to send data to the first terminal device; or, capable of sending side channel state information and / or data to the first terminal device; or, It is capable of sending side channel status information, or sending side channel status information and data to the first terminal device, and the side channel status information and the data are carried in one MAC PDU.

23. The method according to claim 21 or 22, It is characterized in that The method further comprises: receiving first information from the first terminal device, where the first information is used to instruct the first terminal device not to start a sidewalk DRX inactivity timer within a first time period after sending the first sidewalk control information; or, receiving first information from a network device, where the first information is used to instruct the first terminal device not to start a sidewalk DRX inactivity timer within the first time period after sending the first sidewalk control information; or, Sending first information to the first terminal device, where the first information is used to instruct the first terminal device not to start a sidewalk DRX inactivity timer within a first time period after sending the first sidewalk control information; or, The first sidelink control information is also used to instruct the first terminal device not to start the sidelink DRX inactivity timer within a first time period after sending the first sidelink control information.

24. The method according to claim 22, It is characterized in that The method further comprises: A target device for receiving the MAC PDU is selected according to a first rule, wherein the first rule comprises: The first time domain resource is located within the first time period after the target device triggers the second terminal device to send sidelink channel status information, or the first time domain information is located within the sidelink DRX activation time of the target device; wherein, the first time domain resource is the time domain resource occupied by the second sidelink control information, or the time domain resource occupied by the sidelink control channel corresponding to the second sidelink control information, or the time domain resource occupied by the sidelink authorization information corresponding to the second sidelink control information.

25. The method according to any one of claims 21, 22 and 24, It is characterized in that The method further comprises: receiving second information from the first terminal device, where the second information is used to indicate a first mode, where the first mode includes: capable of sending sidelink channel state information to the first terminal device, but unable to send data to the first terminal device; or, capable of sending side channel state information and / or data to the first terminal device; or, It is capable of sending side channel status information, or sending side channel status information and data to the first terminal device, and the side channel status information and the data are carried in one MAC PDU.

26. The method according to any one of claims 21, 22 and 24, It is characterized in that The method further comprises: Sending third information to the first terminal device, the third information is used to indicate the timing duration of a fourth timer, and the timing duration of the fourth timer is used to indicate the preparation time of the second terminal device before sending the side channel state information.

27. A terminal device, It is characterized in that include: one or more processors; one or more memories; and one or more computer programs, wherein the one or more computer programs are stored in the one or more memories, and the one or more computer programs include instructions, which, when executed by one or more processors of the terminal device, cause the terminal device to execute the method as described in any one of claims 1 to 20, or cause the terminal device to execute the method as described in any one of claims 21 to 26.

28. A computer readable storage medium, It is characterized in that The computer-readable storage medium is used to store a computer program, and when the computer program is run on a computer, the computer is caused to execute the method according to any one of claims 1 to 20, or the computer is caused to execute the method according to any one of claims 21 to 26.

29. A chip, It is characterized in that The method comprises one or more processors and a communication interface, wherein the one or more processors are used to read instructions to execute the method according to any one of claims 1 to 20, or execute the method according to any one of claims 21 to 26.