A DRX method and device

Abstract

An embodiment of the present application provides a discontinuous reception DRX method and apparatus, which can ensure that the time domain position of the sidelink resources allocated by the network device to the terminal device at the transmitting end is within the sidelink DRX activation time of the terminal device at the receiving end, thereby avoiding the problem that the DRX mechanism in the sidelink communication cannot work or the sidelink resources are wasted. The method includes: a first terminal device sends a sidelink DRX parameter or indication information of a second terminal device to a network device, so that the network device determines a first time period based on the sidelink DRX parameter or indication information, and the first time period belongs to the sidelink DRX activation time of the second terminal device; the first terminal device receives the sidelink authority sent by the network device, and the sidelink authority is used to indicate the resources of the first terminal device to send PSCCH and / or PSSCH, and the time domain position of the resources is within the first time period; the first terminal device sends PSCCH and / or PSSCH based on the sidelink authority.

Description

[0001] This application claims the priority of the Chinese patent application filed with the China Patent Office on August 29, 2020, with application number 202010890908.X and application name “A SL DRX mechanism method”, and all the contents are incorporated by reference into this application; this application claims the priority of the Chinese patent application filed with the China Patent Office on October 16, 2020, with application number 202011112258.2 and application name “A non-continuous reception DRX method and device”, and all the contents are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a discontinuous reception (DRX) method and device. Background Art

[0003] In the new radio (NR) system specified by the 3rd generation partnership project (3GPP) protocol, when the terminal device and the network device communicate over the Uu port, a discontinuous reception (C-DRX or discontinuous reception, DRX) mechanism is introduced to save the power consumption of the terminal device. The DRX mechanism is to configure a DRX cycle or configure DRX for the terminal device in the radio resource control (RRC) connection state. The DRX mechanism can control the terminal device to monitor the physical downlink control channel (PDCCH) during the DRX activation time, and not to monitor the PDCCH during the DRX inactive time, so as to save the power consumption of the terminal device. In order to solve the power consumption problem of the terminal device in the sidelink communication, the DRX mechanism can be used in the sidelink communication. The DRX mechanism in the sidelink communication is similar to the DRX mechanism in the Uu port communication. In the sidelink communication, if the DRX mechanism is introduced, the terminal device at the receiving end only receives at least one of the physical sidelink control channel (PSCCH), physical sidelink shared channel (PSSCH), and sidelink control information (SCI) sent by the terminal device at the transmitting end during the DRX activation time. Summary of the invention

[0004] An embodiment of the present application provides a DRX method and apparatus to solve the problem that when the DRX mechanism is used in sidelink communication, if a network device allocates sidelink resources to a terminal device at the transmitting end, the time domain position of the sidelink resources may not be within the sidelink DRX activation time of the terminal device at the receiving end, thereby causing the DRX mechanism to fail to work in the sidelink communication or the sidelink resources to be wasted.

[0005] In a first aspect, the present application provides a DRX method, comprising: a first terminal device sends a sidelink discontinuous reception DRX parameter or indication information of a second terminal device to a network device, so that the network device determines a first time period based on the sidelink DRX parameter or the indication information; wherein the indication information is used to indicate the start and / or end of the first time period, the first time period belongs to the sidelink DRX activation time of the second terminal device, and the second terminal device is a device for sidelink communication with the first terminal device; the first terminal device receives a sidelink authority sent by the network device; wherein the sidelink authority is used to indicate the first terminal device to send resources of a physical sidelink control channel PSCCH and / or a physical sidelink shared channel PSSCH, and the time domain position of the resources is within the first time period; the first terminal device sends PSCCH and / or PSSCH based on the sidelink authority.

[0006] Based on the above technical solution, the first terminal device sends relevant information about the sidelink DRX activation time of the second terminal device to the network device, so that the network device can know the sidelink DRX activation time of the second terminal device, and further makes the time domain position of the resources indicated by the sidelink authority allocated by the network device to the first terminal device can be within the sidelink DRX activation time of the second terminal device, so that the second terminal device can receive PSCCH, PSSCH or SCI within the sidelink DRX activation time, thereby avoiding the problem that the DRX mechanism between the first terminal device and the second terminal device cannot work or the sidelink resources are wasted due to the time domain position of the resources indicated by the sidelink authority not being within the sidelink DRX activation time of the second terminal device.

[0007] In one possible design, the indication information is included in the uplink control information UCI, the media access control control unit MAC CE or the radio resource control RRC message; the side chain permission is included in the downlink control information DCI, MAC CE or the RRC message.

[0008] In one possible design, the first terminal device sends indication information to the network device, including: the first terminal device sends first indication information to the network device at the starting time of the first time period; wherein the first indication information is used to indicate the end time of the first time period; or, the first terminal device sends second indication information to the network device at the starting time of the first time period, and sends third indication information to the network device at the end time of the first time period; wherein the second indication information is used to indicate the beginning of the first time period, and the third indication information is used to indicate the end of the first time period.

[0009] In one possible design, the first time period belongs to the sidelink DRX activation time of the second terminal device, including: the first time period includes the sidelink DRX activation time of each of the second terminal devices; or, the first time period includes the intersection or union of the sidelink DRX activation times of at least two of the second terminal devices.

[0010] In one possible design, the first time period includes the intersection or union of the sidelink DRX activation times of at least two of the second terminal devices, including: the first time period includes any one or more combinations of the following: the earliest start time to the earliest end time of the sidelink DRX activation time of each of the second terminal devices; the earliest start time to the latest end time of the sidelink DRX activation time of each of the second terminal devices; the latest start time to the earliest end time of the sidelink DRX activation time of each of the second terminal devices; the latest start time to the latest end time of the sidelink DRX activation time of each of the second terminal devices; the start or end time of the sidelink DRX activation time of any of the second terminal devices to the start or end time of the sidelink DRX activation time of any of the second terminal devices.

[0011] In one possible design, if the first time period includes the side chain DRX activation time of each of the second terminal devices, the first terminal device receives the side chain rights sent by the network device, including: the first terminal device receives the side chain rights and device identification information sent by the network device, and determines the second terminal device corresponding to the side chain rights based on the device identification information.

[0012] In one possible design, the sidechain DRX activation time includes the running time of a DRX duration timer and a DRX deactivation timer, and the DRX deactivation timer is started or restarted when the first terminal device sends PSCCH and / or PSSCH; or, the DRX deactivation timer is started or restarted when the first terminal device receives HARQ feedback information of the second terminal device based on the PSCCH and / or PSSCH; or, the DRX deactivation timer is started or restarted when the first terminal device sends fourth indication information to the network device and the second terminal device; wherein the fourth indication information is used to indicate that the DRX deactivation timer is started or restarted.

[0013] In one possible design, the method also includes: the DRX deactivation timer is started or restarted when the first terminal device receives side link control information SCI and the information included in the SCI meets a preset condition; wherein the SCI includes any one or more of a source layer-1ID, a destination layer-1ID or a communication type cast type, and the cast type is used to indicate unicast communication, multicast communication or broadcast communication.

[0014] In one possible design, the SCI includes a source layer-1ID and a destination layer-1ID. When the destination layer-1ID is the same as the layer-1ID of the first terminal device and the sourcelayer-1ID is the same as the layer-1ID of the second terminal device, the first terminal device starts or restarts the DRX deactivation timer corresponding to the side link DRX between the first terminal device and the second terminal device; or, the SCI includes a source layer-1ID, a destination layer-1ID and a cast type. When the cast type indicates unicast communication, the destination layer-1ID is the same as the layer-1ID of the first terminal device and the source layer-1ID is the same as the layer-1ID of the second terminal device, the first terminal device starts or restarts the DRX deactivation timer corresponding to the side link DRX between the first terminal device and the second terminal device; or, the SCI includes a destination layer-1ID and a cast type. When the cast type is used to indicate multicast communication, the destination layer-1ID is the same as the destination of the multicast communication. When the layer-1ID is the same, the first terminal device starts or restarts the DRX deactivation timer corresponding to the sidelink DRX of the multicast communication.

[0015] In one possible design, the destination layer-1ID included in the SCI is the same as the layer-1ID of the first terminal device in any sidelink unicast communication, and the source layer-1ID included in the SCI is the same as the layer-1ID of the second terminal device corresponding to the first terminal device in the sidelink unicast communication, and the method also includes: the first terminal device cancels or restarts the DRX deactivation timer corresponding to the sidelink DRX between the first terminal device and the second terminal device; wherein, the first terminal device determines that the source layer-2ID of the media access control protocol data unit MAC PDU corresponding to the SCI is different from the layer-2ID of the second terminal device corresponding to the first terminal device in the sidelink unicast communication, or, the destination layer-2 ID of the MAC PDU corresponding to the SCI The layer-2ID is different from the layer-2ID of the first terminal device in the side-link unicast communication; or, the first terminal device configures the layer-2ID in the side-link unicast communication between the first terminal device and the second terminal device; wherein the layer-1ID corresponding to the layer-2ID is different from the layer-1ID corresponding to the layer-2ID configured by the first terminal device in the side-link unicast communication with other second terminal devices; or, the first terminal device configures the layer-2ID in the side-link unicast communication between the first terminal device and the second terminal device; wherein the layer-1ID corresponding to the layer-2ID is different from the layer-1ID corresponding to the layer-2ID in other side-link unicast communications, and the other side-link unicast communications are side-link unicast communications in which the terminal devices do not include the first terminal device.

[0016] In one possible design, the first terminal device receives the SCI or the fourth indication information and the MAC PDU corresponding to the SCI or the fourth indication information only includes non-data information, and the method also includes: the first terminal device determines that the MAC PDU corresponding to the SCI includes the first information but does not include the second information, and cancels or restarts the DRX deactivation timer corresponding to the sidelink DRX between the first terminal device and the second terminal device; wherein the first information includes any one or more of the following combinations: sidelink channel state information report, sidelink resource information in collaboration between terminal devices; the second information includes any one or more of the following combinations: sidelink control channel SCCH data, sidelink service channel STCH data, media access control control unit MAC CE other than the first information; or, the first information includes any one or more of the following combinations: sidelink channel state information report, sidelink resource information in collaboration between terminal devices, SCCH data, information other than STCH data; the second information includes STCH data.

[0017] In one possible design, the first terminal device receives a PSCCH, PSSCH or MAC PDU sent by the second terminal device and the SCI corresponding to the PSCCH, PSSCH or MAC PDU indicates at least two resources, or receives the SCI sent by the second terminal device and the SCI indicates at least two resources, and the method also includes: the first terminal device starts a sidelink HARQ timer or DRX retransmission timer corresponding to the sidelink DRX between the first terminal device and the second terminal device; wherein the priority indicated by the SCI is greater than the minimum value of the priority value range; the first terminal device does not start the sidelink HARQ timer or DRX retransmission timer corresponding to the sidelink DRX between the first terminal device and the second terminal device; wherein the priority indicated by the SCI is the minimum value of the priority value range.

[0018] In one possible design, the first terminal device receives a PSCCH, PSSCH or MAC PDU sent by the second terminal device and the SCI corresponding to the PSCCH, PSSCH or MAC PDU indicates at least two resources, or receives the SCI sent by the second terminal device and the SCI indicates at least two resources, and the method also includes: the first terminal device determines the start time of the sidelink HARQ timer or DRX retransmission timer corresponding to the sidelink DRX between the first terminal device and the second terminal device according to each of the at least two resources indicated by the SCI; wherein the resources include or indicate the SCI transmission timing.

[0019] In one possible design, after the first terminal device receives the side chain authority sent by the network device, the method also includes: if the first terminal device determines to discard the side chain authority, sending fifth indication information to the network device at the end time of the first time period or a time interval before the end time; wherein the fifth indication information is used to indicate that the first terminal device determines to discard the side chain authority and the end of the first time period; or, if the first terminal device determines to discard the side chain authority, sending sixth indication information to the network device; wherein the sixth indication information is used to indicate that the first terminal device determines to discard the side chain authority and the end time of the first time period or the time domain position of the side chain authority determined to be discarded or the time domain position of the previous side chain authority determined to be discarded.

[0020] Based on the above technical solution, the first terminal device sends relevant information of the discarded side chain authority to the network device after determining to discard the side chain authority, so that the network device can know whether the first terminal device and the second terminal device have started or restarted the DRX deactivation timer, and further makes the DRX deactivation timer maintained by the first terminal device and the second terminal device consistent with the state of the DRX deactivation timer maintained by the network device, thereby avoiding the problem that the time domain position of the resource indicated by the side chain authority subsequently sent by the network device to the first terminal device may not be within the side chain DRX activation time of the second terminal device, resulting in the DRX mechanism between the first terminal device and the second terminal device failing to work, or the side link resources being wasted. In a second aspect, the present application also provides a DRX method, including: a network device determines a first time period; wherein, the first time period belongs to the sidelink DRX activation time of a second terminal device, and the second terminal device is a device for sidelink communication with the first terminal device; the network device sends a sidelink authority to the first terminal device, so that the first terminal device sends a physical sidelink control channel PSCCH and / or a physical sidelink shared channel PSSCH based on the sidelink authority; wherein, the sidelink authority is used to indicate the resources for the first terminal device to send PSCCH and / or PSSCH, and the time domain position of the resources is within the first time period.

[0021] Based on the above technical solution, the network device obtains relevant information about the sidelink DRX activation time of the second terminal device, so that the network device can know the sidelink DRX activation time of the second terminal device, and further makes the time domain position of the resources indicated by the sidelink authority allocated by the network device to the first terminal device can be within the sidelink DRX activation time of the second terminal device, so that the second terminal device can receive PSCCH, PSSCH or SCI within the sidelink DRX activation time, thereby avoiding the problem that the DRX mechanism between the first terminal device and the second terminal device cannot work or the sidelink resources are wasted due to the time domain position of the resources indicated by the sidelink authority not being within the sidelink DRX activation time of the second terminal device.

[0022] In one possible design, the network device determines the first time period, including: the network device receives the sidelink DRX parameters of the second terminal device sent by the first terminal device or any one of the second terminal devices, and determines the first time period based on the sidelink DRX parameters; or, the network device determines the first time period based on the sidelink DRX parameters of the second terminal device configured by itself; or, the network device receives indication information sent by the first terminal device, and determines the first time period based on the indication information; wherein the indication information is used to indicate the start and / or end of the first time period.

[0023] In one possible design, the indication information is included in uplink control information UCI, media access control element MAC CE or radio resource control RRC message; the side chain permission is included in downlink control information DCI, MAC CE or RRC message.

[0024] In one possible design, the network device receives indication information sent by the first terminal device, including: the network device receives first indication information sent by the first terminal device at the starting time of the first time period; wherein the first indication information is used to indicate the end time of the first time period; or, the network device receives second indication information sent by the first terminal device at the starting time of the first time period and third indication information sent at the end time of the first time period; wherein the second indication information is used to indicate the beginning of the first time period, and the third indication information is used to indicate the end of the first time period.

[0025] In one possible design, the first time period belongs to the sidelink DRX activation time of the second terminal device, including: the first time period includes the sidelink DRX activation time of each of the second terminal devices; or, the first time period includes the intersection or union of the sidelink DRX activation times of at least two of the second terminal devices.

[0026] In one possible design, the first time period includes the intersection or union of the sidelink DRX activation times of at least two of the second terminal devices, including: the first time period includes any one or more combinations of the following: the earliest start time to the earliest end time of the sidelink DRX activation time of each of the second terminal devices; the earliest start time to the latest end time of the sidelink DRX activation time of each of the second terminal devices; the latest start time to the earliest end time of the sidelink DRX activation time of each of the second terminal devices; the latest start time to the latest end time of the sidelink DRX activation time of each of the second terminal devices; the start or end time of the sidelink DRX activation time of any of the second terminal devices to the start or end time of the sidelink DRX activation time of any of the second terminal devices.

[0027] In one possible design, if the first time period includes the side chain DRX activation time of each of the second terminal devices, the network device sends side chain permissions to the first terminal device, including: the network device sends side chain permissions and device identification information to the first terminal device, so that the first terminal device determines the second terminal device corresponding to the side chain permissions based on the device identification information.

[0028] In one possible design, the side chain DRX activation time includes the running time of a DRX duration timer and a DRX deactivation timer, and the DRX deactivation timer is started or restarted when the network device sends the side chain authority to the first terminal device; or, the DRX deactivation timer is started or restarted when the network device receives HARQ feedback information from the first terminal device based on the side chain authority; or, the DRX deactivation timer is started or restarted when the network device receives fourth indication information sent by the first terminal device; wherein the fourth indication information is used to indicate that the DRX deactivation timer is started or restarted.

[0029] In one possible design, after the network device sends the side chain authority to the first terminal device, the method also includes: the network device receives fifth indication information sent by the first terminal device at the end time of the first time period or at an interval before the end time; wherein the fifth indication information is used to indicate that the first terminal device determines to discard the side chain authority and the end of the first time period; or, the network device receives sixth indication information sent by the first terminal device; wherein the sixth indication information is used to indicate that the first terminal device determines to discard the side chain authority and the end time of the first time period or the time domain position of the side chain authority determined to be discarded or the time domain position of the previous side chain authority determined to be discarded.

[0030] Based on the above technical solution, the network device determines whether the first terminal device and the second terminal device have started or restarted the DRX deactivation timer by receiving the relevant information of the discarded side chain authority sent by the first terminal device after determining to discard the side chain authority, and further makes the DRX deactivation timer maintained by the first terminal device and the second terminal device consistent with the state of the DRX deactivation timer maintained by the network device, thereby avoiding the problem that the time domain position of the resource indicated by the side chain authority subsequently sent by the network device to the first terminal device may not be within the side chain DRX activation time of the second terminal device, resulting in the DRX mechanism between the first terminal device and the second terminal device failing to work, or the side link resources being wasted.

[0031] In a third aspect, the present application further provides a DRX device, which has the function of implementing the first aspect or any possible design method of the first aspect, and the function can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions, such as a first sending module, a receiving module, and a second sending module.

[0032] In a possible design, the first sending module is used to send a sidelink discontinuous reception DRX parameter or indication information of a second terminal device to a network device, so that the network device determines a first time period based on the sidelink DRX parameter or the indication information; wherein the indication information is used to indicate a start and / or end of the first time period, the first time period belongs to a sidelink DRX activation time of the second terminal device, and the second terminal device is a device that performs sidelink communication with the first terminal device;

[0033] In one possible design, the receiving module is used to receive a side chain permission sent by the network device; wherein the side chain permission is used to indicate that the first terminal device sends resources of a physical side chain control channel PSCCH and / or a physical side chain shared channel PSSCH, and the time domain position of the resources overlaps with the first time period;

[0034] In one possible design, the second sending module is used to send PSCCH and / or PSSCH based on the side chain authority.

[0035] In a fourth aspect, the present application further provides a DRX device, which has the function of implementing the above-mentioned second aspect or any possible design method of the second aspect, and the function can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions, such as a determination module and a sending module.

[0036] In one possible design, the determining module is used to determine a first time period; wherein the first time period belongs to a sidelink DRX activation time of a second terminal device, and the second terminal device is a device that performs sidelink communication with the first terminal device;

[0037] In one possible design, the sending module is used to send side chain permissions to the first terminal device, so that the first terminal device sends a physical side chain control channel PSCCH and / or a physical side chain shared channel PSSCH based on the side chain permissions; wherein the side chain permissions are used to indicate the resources for the first terminal device to send PSCCH and / or PSSCH, and the time domain position of the resources is within the first time period.

[0038] In a fifth aspect, the present application also provides a DRX device, which may include: at least one processor; and a memory and a communication interface communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the at least one processor executes the functions of the first aspect or any possible method in the design of the first aspect or the second aspect or any possible method in the design of the second aspect by executing the instructions stored in the memory.

[0039] In a sixth aspect, the present application also provides a computer-readable storage medium, which includes a computer program. When the computer program runs on a computer, the computer executes the above-mentioned first aspect or any possible method in the design of the first aspect or the above-mentioned second aspect or any possible method in the design of the second aspect.

[0040] In the seventh aspect, the present application also provides a program product, which, when running on a computer, enables the computer to execute the above-mentioned first aspect or any possible designed method of the first aspect or the above-mentioned second aspect or any possible designed method of the second aspect.

[0041] In the eighth aspect, the present application also provides a chip, which can be coupled to the memory of the DRX device, and is used to call a computer program stored in the memory and execute the above-mentioned first aspect or any possible designed method of the first aspect or the above-mentioned second aspect or any possible designed method of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 A schematic diagram of a DRX cycle applicable to an embodiment of the present application;

[0043] Figure 2 A state diagram of a DRX deactivation timer applicable to an embodiment of the present application;

[0044] Figure 3 A schematic diagram of a network architecture applicable to an embodiment of the present application;

[0045] Figure 4 A schematic diagram of a DRX method provided in an embodiment of the present application;

[0046] Figure 5a A schematic diagram of sending instruction information provided in an embodiment of the present application;

[0047] Figure 5b A schematic diagram of another embodiment of the present application for sending indication information;

[0048] Figure 5c A schematic diagram of another embodiment of the present application for sending indication information;

[0049] Figure 5d A schematic diagram of another embodiment of the present application for sending indication information;

[0050] Figure 5e A schematic diagram of a state maintenance method for a DRX deactivation timer provided in an embodiment of the present application;

[0051] Figure 5f A schematic diagram of a side chain DRX activation time provided in an embodiment of the present application;

[0052] Figure 5g A schematic diagram of another side chain DRX activation time provided in an embodiment of the present application;

[0053] Figure 5h A schematic diagram of another side chain DRX activation time provided in an embodiment of the present application;

[0054] Figure 5i A schematic diagram of sending fifth indication information provided in an embodiment of the present application;

[0055] Figure 5j A schematic diagram of another method for sending fifth indication information provided in an embodiment of the present application;

[0056] Figure 5k A schematic diagram of another method for maintaining the state of a DRX deactivation timer provided in an embodiment of the present application;

[0057] Figure 6 A structural diagram of a DRX device provided in an embodiment of the present application;

[0058] Figure 7 A schematic diagram of the structure of another DRX device provided in an embodiment of the present application;

[0059] Figure 8 A schematic diagram of the structure of another DRX device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0060] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

[0061] To facilitate understanding of the embodiments of the present application, the professional terms involved in the embodiments of the present application are explained below.

[0062] 1. Sidelink (SL) communication

[0063] In the embodiment of the present application, the sidelink may also be referred to as an edge link, or a side link, or a PC5 interface link, or a link between terminal devices. The sidelink communication is a wireless communication performed directly between two or more terminal devices. In this type of communication, two or more terminal devices that are geographically close to each other can communicate directly without passing through any network device. The data transmission in the sidelink communication is different from the typical cellular network communication. The typical cellular network communication is to send data to the network device, that is, uplink (UL) transmission, or to receive data from the network device, that is, downlink (DL) transmission. However, in the sidelink communication, the data is sent directly from the terminal device at the sending end to the terminal device at the receiving end through an air interface such as a PC5 interface without passing through any network device. For example, the sidelink communication is carried out between a pair of source addresses (source) and destination addresses (destination), wherein the terminal device at the sending end may be a terminal device that sends a signal, data, signaling or information, and correspondingly, the terminal device at the receiving end is a terminal device that receives the signal, data, signaling or information. The terminal device at the sending end may also be a terminal device that receives a signal, data, signaling or information sent by a terminal device (including the above-mentioned terminal device at the receiving end). In this case, it is also a terminal device at the receiving end. Correspondingly, the terminal device at the receiving end may also be a terminal device that sends a signal, data, signaling or information to a terminal device (including the above-mentioned terminal device at the sending end). In this case, it is also a terminal device at the sending end. The source is a source. The terminal device at the sending end of the sidelink communication identified by layer-2ID, the destination is the terminal device at the receiving end of the sidelink communication identified by destination layer-2ID, that is, the terminal device at the sending end refers to the source of the sidelink communication (or a medium access control (MAC) protocol data unit (PDU)), and the terminal device at the receiving end refers to the destination of the sidelink communication (or a MAC PDU). For sidelink unicast communication, the PC5-radio resource control (RRC) connection is a logical connection between a source and a destination. Since there is a one-to-one correspondence between the PC5-RRC connection and the PC5 unicast link, after the PC5 unicast link is established, the PC5-RRC connection corresponding to the PC5 unicast link is established.

[0064] In an embodiment of the present application, a MAC PDU of sidelink communication may include one or more of a MAC control element (CE), data of a sidelink control channel (SCCH), and data of a sidelink service channel (STCH). Among them, MAC CE includes a sidelink channel state information (SL-CSI) report MAC CE, and SL-CSI report refers to a terminal device providing sidelink channel state information to a peer terminal device. SL-CSI report MAC CE includes a channel quality indicator (CQI) and a rank indicator (RI). SL-CSI report MAC CE may be included in a MAC PDU of sidelink communication. SCCH is a sidelink channel used to transmit control information, and the control information includes PC5-RRC messages and PC5-S messages. STCH is a sidelink channel used to transmit user information or service information.

[0065] In the embodiment of the present application, the resources used for sidelink communication between terminal devices and terminal devices are called sidelink resources, which can also be simply referred to as resources, or transmission resources. Sidelink resources may include sidelink resources in the frequency domain and sidelink resources in the time domain. From the perspective of transmission type, sidelink resources may include sidelink transmission resources and sidelink reception resources. Among them, the sidelink transmission resources are used to send information, such as sending control information and / or data, and the sidelink reception resources are used to receive information, such as receiving control information and / or data.

[0066] At present, there are two methods for selecting sidelink resources. The first is that the network device allocates sidelink resources to the terminal device at the transmitting end. That is, the network device sends a sidelink grant (SL grant) to the terminal device at the transmitting end, and the SL grant is used to instruct the terminal device at the transmitting end to transmit the transmission resources of the physical sidelink control channel (PSCCH) and / or the physical sidelink shared channel (PSSCH). The second method is that the terminal device at the transmitting end autonomously selects the sidelink resources, that is, the terminal device at the transmitting end autonomously selects the SL grant. In the case where the terminal device at the transmitting end reserves the sidelink resources, the terminal device at the transmitting end can also send sidelink control information (SCI) to the terminal device at the receiving end, and the SCI carries information for indicating the reserved sidelink resources.

[0067] 2. Connected-discontinuous reception (C-DRX or DRX) mechanism

[0068] In the Uu port communication between the terminal device and the network device, the DRX mechanism is introduced to save power for the terminal device. The DRX mechanism is to configure a DRX cycle or configure DRX for the terminal device in the RRC connection state. Figure 1 As shown, it is a schematic diagram of a DRX cycle applicable to an embodiment of the present application. It can be seen from the figure that in the time domain, time is divided into continuous DRX cycles. The DRX cycle consists of "On Duration (wake-up period or wake-up time or activation period or duration)" and "Opportunity for DRX (sleep period or sleep time)". During the "On Duration" time, the terminal device monitors and receives the Physical Downlink Control Channel (PDCCH). During the "Opportunity for DRX" time, the terminal device does not receive PDCCH to save power consumption.

[0069] When a terminal device is configured with a DRX cycle or a DRX, the state of the terminal device can be divided into a DRX active state and a DRX non-active state (or sleep state). The terminal device is in the DRX active state during the active time, and in the DRX non-active state during the non-active time. When the terminal device is in the DRX active time, the terminal device will monitor and receive the PDCCH. If the terminal device is in the DRX non-active time, the terminal device will not monitor and receive the PDCCH, which can save power consumption.

[0070] When any of the following timers is running, the terminal device is in the DRX activation time:

[0071] DRX duration timer (drx-onDurationTimer);

[0072] DRX deactivation timer (drx-InactivityTimer);

[0073] DRX downlink retransmission timer (drx-RetransmissionTimerDL);

[0074] DRX uplink retransmission timer (drx-RetransmissionTimerUL);

[0075] Random access contention resolution timer (ra-ContentionResolutionTimer).

[0076] In addition, the DRX activation time also includes other situations, such as: the waiting period after the terminal device sends a scheduling request (SR) on the physical uplink control channel (PUCCH); the period when the terminal device has not received the PDCCH indicating a new transmission after successfully receiving the random access response (RAR) based on non-contention based random access.

[0077] At the beginning of the DRX cycle, the terminal device starts the timer drx-onDurationTimer, that is, enters the "OnDuration". When the timer starts running, it enters the DRX activation time. If during the operation of drx-onDurationTimer, the terminal device receives a PDCCH indicating new downlink or uplink data transmission, the terminal device will start or restart the timer drx-InactivityTimer, so that the terminal device is always in the DRX activation time. It can be understood that the length of time the terminal device is originally in the active state is the length of time of "On Duration". Running drx-InactivityTimer can extend the time the terminal device is in the active state until the drx-InactivityTimer timer times out, or the terminal device receives relevant media access control (MAC) control element (CE) signaling to stop the drx-onDurationTimer and the drx-InactivityTimer, for example, DRX Command MAC CE, the terminal device ends the activation time and enters the inactive time, that is, the terminal device enters the inactive state from the active state. It is easy to understand that the "On Duration" described here represents a time period, which is determined by the timer drx-onDurationTimer, and the length is equal to the size of the timer drx-onDurationTimer configured by the network device.

[0078] The drx-InactivityTimer is usually started or restarted in the first symbol after the PDCCH used to indicate new data transmission. Figure 2 , which is a state diagram of a DRX deactivation timer applicable to an embodiment of the present application, Figure 2 The PDCCH is used to schedule new physical downlink shared channel (PDSCH) transmissions.

[0079] As mentioned above, when the terminal device is in the DRX active state, it will continue to monitor the PDCCH. If the terminal device leaves the DRX active state and enters the DRX inactive state, it will not monitor the PDCCH. Therefore, running the drx-InactivityTimer during the "On Duration" period can keep the terminal device in the DRX active state for a longer time and continue to monitor the PDCCH until the drx-InactivityTimer stops running.

[0080] 3. Hybrid automatic repeat request (HARQ)

[0081] For downlink transmission, after the terminal device makes HARQ feedback for the downlink data, it can start a HARQ downlink timer (drx-HARQ-RTT-TimerDL) corresponding to the downlink HARQ process. The timer is used to indicate the minimum duration before the SCI for expected downlink HARQ retransmission or scheduling downlink HARQ retransmission. After the timer expires, if data decoding fails in the downlink HARQ process, the terminal device can start drx-RetransmissionTimerDL.

[0082] For example, if the terminal device receives a MAC PDU in the configured downlink allocation, the terminal device may start the drx-HARQ-RTT-TimerDL of the corresponding downlink HARQ process at the first symbol after the transmission carrying the downlink HARQ feedback ends, and stop the drx-RetransmissionTimerDL of the corresponding downlink HARQ process; or, if the terminal device receives a PDCCH indicating a downlink transmission, the terminal device may start the drx-HARQ-RTT-TimerDL of the corresponding downlink HARQ process at the first symbol after the transmission carrying the downlink HARQ feedback ends, and stop the drx-RetransmissionTimerDL of the corresponding downlink HARQ process; or, if the drx-HARQ-RTT-TimerDL times out and the data decoding of the corresponding downlink HARQ process fails, the terminal device may start the drx-RetransmissionTimerDL of the corresponding downlink HARQ process at the first symbol after the drx-HARQ-RTT-TimerDL times out.

[0083] 4. DRX Mechanism in Sidelink Communication

[0084] In order to solve the power consumption problem of terminal devices in sidelink communication, the DRX mechanism can be used in sidelink communication. The DRX mechanism in sidelink communication is similar to the DRX mechanism in Uu port communication. In sidelink communication, if the DRX mechanism is introduced between the terminal device at the transmitting end and the terminal device at the receiving end, the terminal device at the receiving end only receives at least one of the PSCCH, PSSCH, and SCI sent by the terminal device at the transmitting end during the DRX activation time.

[0085] When the DRX mechanism is used in the sidelink communication, if the network device allocates the sidelink resource to the terminal device at the transmitting end, since the network device does not know the sidelink DRX activation time between the terminal device at the transmitting end and the terminal device at the receiving end, the time domain position of the sidelink resource may not be within the sidelink DRX activation time between the terminal device at the transmitting end and the terminal device at the receiving end. If the terminal device at the transmitting end uses the sidelink resource to send at least one of PSCCH, PSSCH, and SCI, since the terminal device at the receiving end does not receive at least one of PSCCH, PSSCH, and SCI during the sidelink DRX inactive time, wherein the sidelink DRX inactive time is the time outside the sidelink DRX activation time, and SCI includes the first-level SCI, the second-level SCI, or the first-level SCI and the second-level SCI, the first-level SCI can be carried on the PSCCH, and the second-level SCI can be carried on the PSSCH. Therefore, the terminal device at the receiving end cannot receive at least one of PSCCH, PSSCH, and SCI. If, in order for the terminal device at the receiving end to receive at least one of PSCCH, PSSCH, and SCI, the terminal device at the receiving end must also receive at least one of PSCCH, PSSCH, and SCI during the sidelink DRX inactive time, the DRX mechanism will not work in the sidelink communication. If the terminal device at the transmitting end does not use the sidelink resource to send at least one of PSCCH, PSSCH, and SCI, the sidelink resource will be wasted.

[0086] 5. HARQ in Sidelink Communications

[0087] When the DRX mechanism is used in sidelink communication, the sidelink DRX activation time of the terminal device may include the running time of the sidelink DRX duration timer drx-onDurationTimerPC5, the sidelink DRX deactivation timer drx-InactivityTimerPC5 or the sidelink DRX retransmission timer drx-RetransmissionTimerPC5, and the terminal device may monitor PSCCH, PSSCH or SCI within the sidelink DRX activation time. Among them, the sidelink DRX can be the sidelink DRX of the terminal device at the receiving end, or the sidelink DRX between the terminal device at the transmitting end and the terminal device at the receiving end, or the sidelink DRX between a pair of source and destination, the source is the terminal device at the transmitting end identified by the source layer-1ID, and the destination is the terminal device at the receiving end identified by the destination layer-1ID, or the source is the terminal device at the transmitting end identified by the source layer-2ID, and the destination is the terminal device at the receiving end identified by the destination layer-2ID, wherein the layer-1ID is the 8LSB (least significant bits) of the layer-2ID, that is, the layer-1ID is the lower 8 bits of the layer-2ID, and it can be said that the source Layer-1 ID is the 8LSB of the source Layer-2 ID, and the destination Layer-1 ID is the 8LSB of the destination Layer-2 ID. PSCCH, PSSCH or SCI transmission is sent by the terminal device at the transmitting end to the terminal device at the receiving end, or, it is sent by the source to the destination.

[0088] The terminal device can determine the time domain and frequency domain resources of PSSCH transmission according to the time domain resource allocation domain and frequency domain resource allocation domain contained in SCI and the resources of PSCCH transmission, wherein the time domain resource allocation domain indicates N resources and the time slot offset of resources other than the first resource in the N resources, N can be 1 or 2 or 3, the time slot where the first resource is located is the time slot where SCI is located, the time slot offset of resources other than the first resource is the time slot offset relative to the first resource, and the frequency domain resource allocation domain indicates the number of continuous subchannels of each resource of the N resources and the starting subchannel index of resources other than the first resource. However, since the running time of drx-RetransmissionTimerPC5 is only related to the time domain position of the first resource, that is, the time domain position of resources other than the first resource may not be within the side chain DRX activation time of the terminal device, the terminal device cannot monitor the transmission on the N resources, resulting in the waste of resources other than the first resource.

[0089] 6. Inter-UE coordination

[0090] In the sidelink communication, the cooperation between the terminal devices includes the terminal device A sending information indicating a group of resources to the terminal device B, where the information indicating a group of resources may be referred to as sidelink resource information, and the sidelink resource information may be carried on the MAC CE, or the sidelink resource information may be included in the SCI, for example, in the second-level SCI, and the group of resources indicated by the sidelink resource information may be one or more of the following:

[0091] 1) Preferred resources for sidelink transmission by terminal device B. For example, terminal device A determines the preferred resources for sidelink transmission by terminal device B based on the detection result.

[0092] 2) Non-preferred resources for sidelink transmission by terminal device B. For example, terminal device A determines the non-preferred resources for sidelink transmission by terminal device B based on the detection result and / or potential resource conflict.

[0093] 3) Conflicting resources: For example, if terminal device A detects that the sidelink transmission resources to be used by terminal device B and terminal device C overlap, terminal device A detects conflicting resources.

[0094] When the DRX mechanism is used in the sidelink communication, if the network device allocates the sidelink resource to the terminal device at the transmitting end, since the network device does not know the sidelink DRX activation time of the terminal device at the receiving end, the time domain position of the sidelink resource may not be within the sidelink DRX activation time of the terminal device at the receiving end. If the terminal device at the transmitting end uses the sidelink resource to send at least one of PSCCH, PSSCH, and SCI, since the terminal device at the receiving end does not receive at least one of PSCCH, PSSCH, and SCI during the sidelink DRX inactive time, the terminal device at the receiving end cannot receive at least one of PSCCH, PSSCH, and SCI. If, in order for the terminal device at the receiving end to receive at least one of PSCCH, PSSCH, and SCI, the terminal device at the receiving end also needs to receive at least one of PSCCH, PSSCH, and SCI during the sidelink DRX inactive time, the DRX mechanism will not work in the sidelink communication. If the terminal device at the transmitting end does not use the sidelink resource to send at least one of PSCCH, PSSCH, and SCI, the sidelink resource will be wasted.

[0095] If SCI indicates N resources, the time domain positions of resources other than the first resource may not be within the sidelink DRX activation time of the terminal device at the receiving end, resulting in the terminal device being unable to monitor the transmission on the N resources, and resources other than the first resource being wasted.

[0096] From this, it can be seen that when the DRX mechanism is used in sidelink communications, if the network device allocates sidelink resources to the terminal device at the transmitting end, the time domain position of the sidelink resources may not be within the sidelink DRX activation time of the terminal device at the receiving end, resulting in the DRX mechanism failing to work in the sidelink communication or the sidelink resources being wasted.

[0097] In view of this, the terminal device and the network device in the embodiment of the present application determine the activation time of DRX through interaction, thereby avoiding the situation where the resources allocated by the base station are wasted.

[0098] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as the fourth generation (4G) communication system, the fifth generation (5G) communication system, the machine type communication (MTC) system, the device to device (D2D) system, the Internet of Things (IoT) system, the vehicle-to-everything (V2X) system, the narrow band Internet of Things (NB-IoT) system, and new communication systems emerging in the future communication development, as long as the communication entity in the communication system can configure the DRX parameters.

[0099] like Figure 3 As shown, it is a schematic diagram of a network architecture applicable to an embodiment of the present application, wherein the communication system includes a network device 301, a first terminal device 302, and multiple second terminal devices that perform sidelink communication with the first terminal device 302, wherein the first terminal device 302 is a terminal device at the transmitting end in the sidelink communication, the second terminal device is a terminal device at the receiving end in the sidelink communication, and the second terminal device includes a second terminal device a303 and a second terminal device b304. In the communication system, the first terminal device 302 and the second terminal device a303 within the coverage of the network device 301 can communicate with the network device 301 through the Uu interface, and the second terminal device b304 outside the coverage of the network device 301 cannot communicate with the network device 301 through the Uu interface. The first terminal device 302 can communicate with the second terminal device a303 and the second terminal device b304 through the PC5 interface.

[0100] The network device 301, for example, includes access network (AN) equipment and radio access network (RAN) equipment. Access network equipment, such as a base station (e.g., an access point), may refer to a device in an access network that communicates with a wireless terminal device through one or more cells at an air interface. The base station may be used to convert received air frames to and from Internet Protocol (IP) packets, and serve as a router between the terminal device and the rest of the access network, wherein the rest of the access network may include an IP network. The network device may also coordinate the attribute management of the air interface. For example, the network device may include an evolved base station (NodeB or eNB or e-NodeB, evolved Node B) in a long term evolution (LTE) system or long term evolution-advanced (LTE-A), or may also include a next generation node B (next generation node B, gNB) or a next generation evolved node B (next generation evolved nodeB, ng-eNB), en-gNB (enhanced next generation node B, gNB) in a fifth generation mobile communication technology (the 5th generation, 5G) new radio (new radio, NR) system: an enhanced next generation base station; it may also include a centralized unit (CU) and a distributed unit (DU) in a cloud access network (Cloud radio access network, Cloud RAN) system, or it may also include a relay device, which is not limited in the embodiments of the present application.

[0101] The first terminal device 302, the terminal device a303 and the terminal device b304 include devices that provide voice and / or data connectivity to the user, such as a handheld device with a wireless connection function, or a processing device connected to a wireless modem. The terminal device can communicate with the core network via a radio access network (RAN) and exchange voice and / or data with the RAN. The terminal device may include user equipment (UE), wireless terminal device, mobile terminal device, D2D communication terminal device, vehicle-to-everything (V2X) communication terminal device, machine-to-machine / machine-type communications (M2M / MTC) terminal device, Internet of Things (IoT) terminal device, subscriber unit, subscriber station, mobile station, remote station, access point (AP), remote terminal, access terminal, user terminal, user agent, or user device, etc. For example, it may include a mobile phone (or "cellular" phone), a computer with a mobile terminal device, a portable, pocket-sized, handheld, or computer-built-in mobile device, etc. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDA), and other devices. It also includes limited devices, such as devices with low power consumption, or devices with limited storage capacity, or devices with limited computing power, etc. For example, it includes information sensing devices such as barcodes, radio frequency identification (RFID), sensors, global positioning systems (GPS), laser scanners, etc.

[0102] As an example but not limitation, in the embodiments of the present application, the terminal device mentioned may also be a wearable device. Wearable devices may also be referred to as wearable smart devices or smart wearable devices, etc., which are a general term for the application of wearable technology to intelligently design and develop wearable devices for daily wear, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, etc., as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets, smart helmets, and smart jewelry for vital sign monitoring.

[0103] The various terminal devices introduced above, if located on a vehicle, such as placed in a vehicle or installed in a vehicle, can be considered as vehicle-mounted terminal devices, which are also called on-board units (OBU).

[0104] The above introduces the communication system to which the embodiment of the present application is applicable. Next, the DRX method provided by the embodiment of the present application is introduced in conjunction with the accompanying drawings.

[0105] It should be understood that the terms "system" and "network" in the embodiments of the present application can be used interchangeably. "At least one" refers to one or more, and "plurality" refers to 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 represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c.

[0106] Furthermore, unless otherwise specified, 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 order, timing, priority or importance of multiple objects. For example, the first priority criterion and the second priority criterion are only used to distinguish different criteria, and do not indicate the difference in the content, priority or importance of the two criteria.

[0107] In order to solve the first problem mentioned above, that is, how to avoid the situation where, if a network device allocates side link resources to a terminal device at the transmitting end, the time domain position of the side link resources may not be within the side link DRX activation time of the terminal device at the receiving end, resulting in the DRX mechanism failing to work or the side link resources being wasted, the embodiment of the present application provides the following solution of Embodiment 1, which is described in detail below.

[0108] Example 1

[0109] like Figure 4 As shown, the embodiment of the present application provides a DRX method that can be applied to Figure 3 The communication system shown. The method comprises:

[0110] S401, a first terminal device sends a sidelink DRX parameter or indication information of a second terminal device to a network device. Correspondingly, the network device receives the sidelink DRX parameter or indication information of the second terminal device sent by the first terminal device.

[0111] In some embodiments, the indication information is used to indicate the start, end, or start and end of the first time period, the first time period belongs to the sidelink DRX activation time of the second terminal device or the second terminal device is in the sidelink DRX activation state during the first time period; or, the indication information is used to indicate the start, end, or start and end of the sidelink DRX activation time or the sidelink DRX activation state of the second terminal device. The second terminal device is a device that performs sidelink communication with the first terminal device, and the number of the second terminal devices can be one or more, which is not specifically limited in the embodiments of the present application.

[0112] It should be noted that, in the embodiment of the present application, the side chain DRX activation time of the second terminal device can be understood as the side chain DRX activation time between the first terminal device and the second terminal device, and can also be understood as the side chain DRX activation time between a pair of source and destination, where the source is the first terminal device identified by source layer-1ID, and the destination is the second terminal device identified by destination layer-1ID, or the source is the first terminal device identified by source layer-2ID, and the destination is the second terminal device identified by destination layer-2ID. A first terminal device can correspond to at least one source, and a second terminal device can correspond to at least one destination.

[0113] It should be noted that in the embodiment of the present application, the terminal device within the sidelink DRX activation time is in the sidelink DRX activation state; the terminal device not within the sidelink DRX activation time is in the sidelink DRX inactive state, or the terminal device within the sidelink DRX inactive time is in the sidelink DRX inactive state.

[0114] In step 401, the first terminal device may inform the network device of the sidelink DRX activation time of the first time period or the second terminal device in two ways. The specific implementation of the two ways is described in detail below with reference to specific examples:

[0115] Method 1: The first terminal device may send the sidelink DRX parameters of the second terminal device to the network device, and correspondingly, the network device receives the sidelink DRX parameters of the second terminal device sent by the first terminal device. The network device may determine the first time period based on the sidelink DRX parameters, wherein the first time period belongs to the sidelink DRX activation time of the second terminal device, or the second terminal device is in an activated state during the first time period, and the second terminal is a device that performs sidelink communication with the first terminal device. The number of second terminal devices may be one or more, and the embodiments of the present application do not specifically limit this.

[0116] Alternatively, the first terminal device may send the sidelink DRX parameters of the second terminal device to the network device, and correspondingly, the network device receives the sidelink DRX parameters of the second terminal device sent by the first terminal device. The network device may determine the sidelink DRX activation time of the second terminal device based on the sidelink DRX parameters. The second terminal is a device that performs sidelink communication with the first terminal device. The number of second terminal devices may be one or more, which is not specifically limited in the embodiments of the present application.

[0117] It should be noted that, in the embodiment of the present application, the side chain DRX parameters may include any one or more combinations of the following:

[0118] drx-StartOffsetPC5, used to indicate the starting position of the sidelink DRX cycle, where the starting position of the sidelink DRX cycle includes one or more of the following combinations: starting subframe, time slot, symbol;

[0119] drx-SlotOffsetPC5, used to indicate the delay before starting drx-onDurationTimerPC5 at the start position of the sidelink DRX cycle, that is, the terminal device starts drx-onDudrationTimerPC5 after drx-SlotOffsetPC5 at the start position of the sidelink DRX cycle;

[0120] drx-onDudrationTimerPC5 is used to indicate the duration of the start of the side chain DRX cycle, that is, the "On Duration" of the DRXcycle. That is, "On Duration" represents a time period, which is determined by drx-onDurationTimerPC5. The length is equal to the size of drx-onDurationTimerPC5. At the start of the side chain DRX cycle, the terminal device will start drx-onDurationTimerPC5, that is, enter the "On Duration". When drx-onDurationTimerPC5 starts running, it enters the side chain DRX activation time;

[0121] drx-InactivityTimerPC5 is used to indicate the duration after a PSCCH, PSSCH, SCI or MAC PDU transmission, where the SCI includes a first-level SCI, a second-level SCI, or a first-level SCI and a second-level SCI, the first-level SCI can be carried on the PSCCH, the second-level SCI can be carried on the PSSCH, the PSSCH transmission can be a new transmission, and accordingly, the PSCCH or SCI is used to schedule the new transmission, or the PSSCH transmission can be a new transmission or a retransmission, and the PSCCH or SCI is used to schedule the new transmission or the retransmission. For example, if during the sidelink DRX activation time, the terminal device receives a PSCCH or SCI indicating new sidelink data transmission, the terminal device will start or restart drx-InactivityTimerPC5, so that the terminal device is always in the sidelink DRX activation time. It can be understood that the time length that the terminal device is originally in the sidelink DRX activation state is the time length of "On Duration". Running drx-InactivityTimerPC5 can extend the time that the terminal device is in the sidelink DRX activation state until drx-InactivityTimerPC5 times out, or the terminal device receives relevant MAC CE signaling to stop the drx-onDurationTimerPC5 and the drx-InactivityTimerPC5, for example, DRX Command PC5MACCE, the terminal device ends the sidelink DRX activation time and enters the sidelink DRX inactive time, that is, the terminal device enters the sidelink DRX inactive state from the sidelink DRX activation state;

[0122] drx-RetransmissionTimerPC5, used to indicate the maximum duration before receiving the SCI for side chain HARQ retransmission or scheduling side chain HARQ retransmission, where different side chain processes may correspond to different drx-RetransmissionTimerPC5;

[0123] drx-HARQ-RTT-TimerPC5, used to indicate the minimum duration before the SCI for which sidechain HARQ retransmission is expected or scheduled, where different sidechain processes may correspond to different drx-HARQ-RTT-TimerPC5;

[0124] For example, if the terminal device receives PSCCH, PSSCH, SCI or MAC PDU, the terminal device can start the drx-HARQ-RTT-TimerPC5 of the corresponding side chain process in the first symbol, time slot, subframe or micro-time slot after the transmission of the carrying side chain HARQ feedback is completed, or the terminal device can start the drx-HARQ-RTT-TimerPC5 of the corresponding side chain process in the first symbol, time slot, subframe or micro-time slot after the transmission of PSCCH, PSSCH, SCI or MAC PDU is completed. At this time, the drx-RetransmissionTimerPC5 of the corresponding side chain process may be stopped or the drx-RetransmissionTimerPC5 of the corresponding side chain process may not be stopped. The embodiments of the present application do not make specific limitations on this. If drx-HARQ-RTT-TimerPC5 times out and the data decoding of the corresponding side chain process fails, the terminal device may start drx-RetransmissionTimerPC5 of the corresponding side chain process in the first symbol, time slot, subframe or mini-time slot after drx-HARQ-RTT-TimerPC5 times out, that is, if the data decoding of the corresponding side chain process is successful, drx-RetransmissionTimerPC5 is not started;

[0125] Alternatively, if the terminal device receives PSCCH, PSSCH, SCI or MAC PDU, and the data decoding of the corresponding side chain process fails, the terminal device may start the drx-HARQ-RTT-TimerPC5 of the corresponding side chain process in the first symbol, time slot, subframe or micro-time slot after the transmission of the carrying side chain HARQ feedback ends. At this time, the drx-RetransmissionTimerPC5 of the corresponding side chain process may be stopped, or the drx-RetransmissionTimerPC5 of the corresponding side chain process may not be stopped. The embodiments of the present application do not specifically limit this. In other words, if the data decoding of the corresponding side chain process is successful, the drx-HARQ-RTT-TimerPC5 is not started. If the drx-HARQ-RTT-TimerPC5 times out, the terminal device may start the drx-RetransmissionTimerPC5 of the corresponding side chain process in the first symbol, time slot, subframe or micro-time slot after the drx-HARQ-RTT-TimerPC5 times out;

[0126] Alternatively, if the terminal device receives PSCCH, PSSCH, SCI or MAC PDU, and the sidechain HARQ feedback of the corresponding PSCCH, PSSCH, SCI or MAC PDU is NACK, the terminal device may start the drx-HARQ-RTT-TimerPC5 of the corresponding sidechain process in the first symbol, time slot, subframe or micro-time slot after the transmission of the carrying sidechain HARQ feedback ends. At this time, the drx-RetransmissionTimerPC5 of the corresponding sidechain process may be stopped or may not be stopped. The embodiments of the present application do not specifically limit this. That is to say, if the sidechain HARQ feedback of the corresponding PSCCH, PSSCH, SCI or MAC PDU is ACK, the drx-HARQ-RTT-TimerPC5 is not started. If drx-HARQ-RTT-TimerPC5 times out, the terminal device may start drx-RetransmissionTimerPC5 of the corresponding sidechain process in the first symbol, slot, subframe, or mini-slot after drx-HARQ-RTT-TimerPC5 times out;

[0127] Alternatively, if the terminal device receives PSCCH, PSSCH, SCI or MAC PDU, and the data decoding of the corresponding side chain process fails, the terminal device may start the drx-RetransmissionTimerPC5 of the corresponding side chain process at the first symbol, time slot, subframe or micro-time slot after the transmission of the carrying side chain HARQ feedback is completed, or, if the terminal device receives PSCCH, PSSCH, SCI or MAC PDU, the terminal device may start the drx-RetransmissionTimerPC5 of the corresponding side chain process at the first symbol, time slot, subframe or micro-time slot after the transmission of the PSCCH, PSSCH, SCI or MAC PDU is completed, and if the data decoding of the corresponding side chain process is successful, stop drx-RetransmissionTimerPC5;

[0128] Alternatively, if the terminal device receives PSCCH, PSSCH, SCI or MAC PDU, and the sidelink HARQ feedback of the corresponding PSCCH, PSSCH, SCI or MAC PDU is NACK, the terminal device can start the drx-RetransmissionTimerPC5 of the corresponding sidelink process in the first symbol, time slot, subframe or mini-slot after the transmission of the carrying sidelink HARQ feedback is completed, or, if the terminal device receives PSCCH, PSSCH, SCI or MAC PDU, the terminal device can start the drx-RetransmissionTimerPC5 of the corresponding sidelink process in the first symbol, time slot, subframe or mini-slot after the transmission of the PSCCH, PSSCH, SCI or MAC PDU is completed, and if the HARQ feedback of the corresponding PSCCH, PSSCH, SCI or MAC PDU is ACK, stop drx-RetransmissionTimerPC5.

[0129] It should be noted that, in the embodiment of the present application, the above-mentioned drx-StartOffsetPC5, drx-SlotOffsetPC5, drx-onDudrationTimerPC5, drx-InactivityTimerPC5, drx-RetransmissionTimerPC5 and drx-HARQ-RTT-TimerPC5 are only examples of the names of different sidechain DRX parameters, rather than limitations on the names of different sidechain DRX parameters.

[0130] It should be noted that in the embodiments of the present application, the various timers mentioned above, such as drx-onDudrationTimerPC5, drx-InactivityTimerPC5, drx-RetransmissionTimerPC5 and drx-HARQ-RTT-TimerPC5, once started, the timer will be in a running state until the timer stops or times out; otherwise, the timer is not in a running state. If the timer is not in a running state, the timer can be started. After the timer stops or times out, the timer is not in a running state until the timer is started. If the timer is in a running state, the timer can be restarted. The time length of the timer can be understood as the length of time the timer continues to run from the start or restart until the timeout. The value of the timer is its initial value at the time of startup or restart. The initial value of the timer can be the time length of the timer. The value of the timer is the time length of the timer at the time of startup or restart. It should be noted that, in the embodiments of the present application, the sidelink DRX parameters can be configured by the first terminal device, that is, by the terminal device at the transmitting end in the sidelink communication, or by the second terminal device, that is, by the terminal device at the receiving end in the sidelink communication. The party that configures the sidelink DRX parameters sends the sidelink DRX parameters to the other party in the sidelink communication. The sidelink DRX parameters can also be configured by the network device, and the network device sends the sidelink DRX parameters to the device performing the sidelink communication. The embodiments of the present application do not make specific limitations on this.

[0131] It should be noted that, in an embodiment of the present application, if the number of second terminal devices performing side link communication with the first terminal device is multiple or if the number of destinations performing side link communication with the source is multiple, where the source is a first terminal device identified by source layer-1ID or source layer-2ID, and the destination is a second terminal device identified by destination layer-1ID or destination layer-2ID, then in the above-mentioned first time period or the side link DRX activation time of the above-mentioned second terminal device, at least one second terminal device, a second terminal device with data to be transmitted, a destination or a destination with data to be transmitted is in the side link DRX activation time, and the above-mentioned first time period or the side link DRX activation time of the above-mentioned second terminal device may be a continuous period of time or may not be a continuous period of time, and the embodiment of the present application does not make any specific limitation on this.

[0132] The sidechain DRX activation time of the above-mentioned first time period or the above-mentioned second terminal device may include the sidechain DRX activation time of each specific second terminal device. For example, if there are three second terminal devices performing sidelink communication with the first terminal device, and the sidechain DRX activation times of the three second terminal devices are respectively the first sidechain DRX activation time, the second sidechain DRX activation time and the third sidechain DRX activation time, then the sidechain DRX activation time of the above-mentioned first time period or the above-mentioned second terminal device may include the first sidechain DRX activation time, the second sidechain DRX activation time and the third sidechain DRX activation time.

[0133] The sidelink DRX activation time of the above-mentioned first time period or the above-mentioned second terminal device may also include the intersection or union of the sidelink DRX activation times of at least two second terminal devices, for example, any one or more combinations of the following: the earliest start time of the sidelink DRX activation time of each second terminal device to the earliest end time of the sidelink DRX activation time of each second terminal device; the earliest start time of the sidelink DRX activation time of each second terminal device to the latest end time of the sidelink DRX activation time of each second terminal device; the latest start time of the sidelink DRX activation time of each second terminal device to the earliest end time of the sidelink DRX activation time of each second terminal device; the earliest time of the sidelink DRX activation time of each second terminal device to the latest end time of the sidelink DRX activation time of each second terminal device; the start time of the sidelink DRX activation time of each second terminal device to the latest end time of the sidelink DRX activation time of each second terminal device; the start or end time of the sidelink DRX activation time of any second terminal device to the start or end time of the sidelink DRX activation time of any second terminal device.

[0134] Exemplarily, if the number of second terminal devices conducting sidelink communication with the first terminal device is three, the sidelink DRX activation time of the first second terminal device is 11:25-11:30, the sidelink DRX activation time of the second second terminal device is 11:28-11:32, and the sidelink DRX activation time of the third second terminal device is 11:31-11:35, then the intersection or union of the sidelink DRX activation times of the at least two second terminal devices can be 11:25-11:30, or 11:25-11:35, or 11:30-11:31, or 11:31-11:35, or 11:28-11:35, or 11:25-11:28, or 11:28-11:30, or 11:31-11:32, or 11:32-11:35.

[0135] The above is just an example of the intersection or union of the side link DRX activation times of at least two second terminal devices. As long as the intersection or union overlaps with the side link DRX activation time of any second terminal device, as for the method of determining the intersection or union, the embodiment of the present application does not make any specific limitation on this.

[0136] The sidelink DRX activation time of the above-mentioned first time period or the above-mentioned second terminal device may also include the intersection or union of the sidelink DRX activation times of at least two second terminal devices to transmit data, for example, any one or more combinations of the following: the earliest start time of the sidelink DRX activation time of each second terminal device to transmit data to the earliest end time of the sidelink DRX activation time of each second terminal device to transmit data; the earliest start time of the sidelink DRX activation time of each second terminal device to transmit data to the latest end time of the sidelink DRX activation time of each second terminal device to transmit data; the latest start time of the sidelink DRX activation time of each second terminal device to transmit data to the earliest end time of the sidelink DRX activation time of each second terminal device to transmit data; the latest start time of the sidelink DRX activation time of each second terminal device to transmit data to the latest end time of the sidelink DRX activation time of each second terminal device to transmit data; the start or end time of the sidelink DRX activation time of any second terminal device to transmit data to the start or end time of the sidelink DRX activation time of any second terminal device to transmit data.

[0137] It should be noted that, in the embodiment of the present application, the side link DRX activation time of the above-mentioned first time period or the above-mentioned second terminal device can be understood as the side link DRX activation time of the destination to which data is to be transmitted, and the side link DRX activation time of any destination within this period does not change.

[0138] It should be noted that, in the embodiment of the present application, the second terminal device with data to be transmitted can be understood as the first terminal device having data to be sent to the second terminal device or any destination corresponding to the second terminal device. Specifically, the first terminal device or the MAC entity of the first terminal device may have available sidelink data of the logical channel of the second terminal device, or the sidelink data of the logical channel of the second terminal device may be provided to the first terminal device or the MAC entity of the first terminal device, or the sidelink data of the logical channel of the second terminal device may be used for the first terminal device or the MAC entity of the first terminal device, or the sidelink data of the logical channel of the second terminal device may be used for the first terminal device or the MAC entity of the first terminal device, or the sidelink data of the logical channel of the second terminal device may appear or exist in the first terminal device or the MAC entity of the first terminal device.

[0139] Optionally, when the situation of the data to be transmitted of the second terminal device changes, for example, the first terminal device sends the data to be transmitted to the second terminal device using the resources indicated by the side link permission sent by the network device, or a second terminal device that previously had no data to be transmitted now has data to be transmitted, the above-mentioned first time period or the side link DRX activation time of the above-mentioned second terminal device may change, and the network device needs to redefine the first time period or redefine the side link DRX activation time of the second terminal device.

[0140] It should be noted that, in the embodiment of the present application, the sidelink DRX activation time of the second terminal device may include the running time of drx-onDudrationTimerPC5 and drx-InactivityTimerPC5. For example, at the start time of the sidelink DRX cycle, the second terminal device starts drx-onDurationTimerPC5, that is, enters the "On Duration", drx-onDurationTimerPC5 starts running and enters the side chain DRX activation time. During the operation of drx-onDurationTimerPC5, the second terminal device starts or restarts drx-InactivityTimerPC5 to extend the side chain DRX activation time. Since the state of drx-InactivityTimerPC5 maintained by the second terminal device needs to be consistent with the state of drx-InactivityTimerPC5 maintained by the first terminal device and the network device, the first terminal device and the network device also need to start or restart drx-InactivityTimerPC5 during the operation of drx-onDurationTimerPC5. Among them, the first terminal device, the second terminal device and the network device can implicitly start or restart drx-InactivityTimerPC5, or explicitly start or restart drx-InactivityTimerPC5, and the embodiment of the present application does not make specific limitations on this.

[0141] Method 2: The first terminal device may send indication information to the network device, and correspondingly, the network device receives the indication information sent by the first terminal device. The network device may determine the first time period based on the indication information, wherein the indication information is used to indicate the start, end, or start and end of the first time period, the first time period belongs to the sidelink DRX activation time of the second terminal device, or the second terminal device is in the sidelink DRX activation state during the first time period, the second terminal is a device that performs sidelink communication with the first terminal device, and the number of second terminal devices may be one or more, which is not specifically limited in the embodiments of the present application.

[0142] Alternatively, the first terminal device may send indication information to the network device, and accordingly, the network device receives the indication information sent by the first terminal device. The network device may determine the sidelink DRX activation time of the second terminal device based on the indication information, or determine whether the second terminal device is in the sidelink DRX activation time, or determine whether the second terminal device is in the sidelink DRX inactive time, or determine the sidelink DRX state of the second terminal device, such as the second terminal device is in the sidelink DRX activation state or the sidelink DRX inactive state, wherein the indication information is used to indicate the start, end, or start and end of the sidelink DRX activation time or the sidelink DRX activation state of the second terminal device, or to indicate that the second terminal device is in the sidelink DRX activation time or the second terminal device is in the sidelink DRX inactive time or the sidelink DRX state of the second terminal device, such as the second terminal device is in the sidelink DRX activation state or the sidelink DRX inactive state, the second terminal is a device that performs sidelink communication with the first terminal device, the number of the second terminal devices may be one or more, and the embodiment of the present application does not make specific restrictions.

[0143] It should be noted that, in the embodiment of the present application, the indication information may be included in UCI, PUCCH, MAC CE, and radio resource control (RRC) messages.

[0144] It should be noted that, in an embodiment of the present application, before the first terminal device sends an indication message to the network device, the first terminal device needs to determine the sidelink DRX activation time of the first time period or the second terminal device, wherein if the number of second terminal devices performing sidelink communication with the first terminal device is multiple or if the number of destinations performing sidelink communication with the source is multiple, at least one second terminal device, a second terminal device with data to be transmitted, a destination or a destination with data to be transmitted is in the sidelink DRX activation time in the first time period or the second terminal device determined by the first terminal device. The sidelink DRX activation time of the first time period or the second terminal device determined by the first terminal device may be a continuous period of time or may not be a continuous period of time, and the embodiment of the present application does not make specific limitations on this.

[0145] The first time period determined by the first terminal device or the sidechain DRX activation time of the second terminal device may include the specific sidechain DRX activation time of each second terminal device. For example, if there are three second terminal devices performing sidelink communication with the first terminal device, and the sidechain DRX activation times of the three second terminal devices are respectively the first sidechain DRX activation time, the second sidechain DRX activation time and the third sidechain DRX activation time, then the first time period determined by the first terminal device or the sidechain DRX activation time of the second terminal device may include the first sidechain DRX activation time, the second sidechain DRX activation time and the third sidechain DRX activation time.

[0146] The first time period determined by the first terminal device or the sidelink DRX activation time of the second terminal device may also include the intersection or union of the sidelink DRX activation times of at least two second terminal devices, for example, any one or more combinations of the following: the earliest start time of the sidelink DRX activation time of each second terminal device to the earliest end time of the sidelink DRX activation time of each second terminal device; the earliest start time of the sidelink DRX activation time of each second terminal device to the latest end time of the sidelink DRX activation time of each second terminal device; the latest start time of the sidelink DRX activation time of each second terminal device to the earliest end time of the sidelink DRX activation time of each second terminal device; the latest start time of the sidelink DRX activation time of each second terminal device to the latest end time of the sidelink DRX activation time of each second terminal device; the start or end time of the sidelink DRX activation time of any second terminal device to the start or end time of the sidelink DRX activation time of any second terminal device.

[0147] Exemplarily, if the number of second terminal devices conducting sidelink communication with the first terminal device is three, the sidelink DRX activation time of the first second terminal device is 11:25-11:30, the sidelink DRX activation time of the second second terminal device is 11:28-11:32, and the sidelink DRX activation time of the third second terminal device is 11:31-11:35, then the intersection or union of the sidelink DRX activation times of the at least two second terminal devices can be 11:25-11:30, or 11:25-11:35, or 11:30-11:31, or 11:31-11:35, or 11:28-11:35, or 11:25-11:28, or 11:28-11:30, or 11:31-11:32, or 11:32-11:35.

[0148] The above is just an example of the intersection or union of the side link DRX activation times of at least two second terminal devices. As long as the intersection or union overlaps with the side link DRX activation time of any second terminal device, as for the method of determining the intersection or union, the embodiment of the present application does not make any specific limitation on this.

[0149] The first time period determined by the first terminal device or the sidelink DRX activation time of the second terminal device may also include the intersection or union of the sidelink DRX activation times of at least two second terminal devices to transmit data, for example, any one or more combinations of the following: the earliest start time of the sidelink DRX activation time of each second terminal device to transmit data to the earliest end time of the sidelink DRX activation time of each second terminal device to transmit data; the earliest start time of the sidelink DRX activation time of each second terminal device to transmit data to the latest end time of the sidelink DRX activation time of each second terminal device to transmit data; the latest start time of the sidelink DRX activation time of each second terminal device to transmit data to the earliest end time of the sidelink DRX activation time of each second terminal device to transmit data; the latest start time of the sidelink DRX activation time of each second terminal device to transmit data to the latest end time of the sidelink DRX activation time of each second terminal device to transmit data; the start or end time of the sidelink DRX activation time of any second terminal device to transmit data to the start or end time of the sidelink DRX activation time of any second terminal device to transmit data. This embodiment of the present application does not specifically limit this.

[0150] It should be noted that, in the embodiment of the present application, the first time period determined by the first terminal device or the side link DRX activation time of the second terminal device can be understood as the side link DRX activation time of the destination to which data is to be transmitted, and the side link DRX activation time of any destination does not change during this period.

[0151] Optionally, when the situation of the data to be transmitted of the second terminal device changes, for example, the first terminal device uses the resources indicated by the side chain permission sent by the network device to send the data to be transmitted to the second terminal device corresponding to the side chain permission, or a second terminal device that previously had no data to be transmitted now has data to be transmitted, the first time period determined by the above-mentioned first terminal device or the side chain DRX activation time of the second terminal device determined by the above-mentioned first terminal device may change, and the first terminal device needs to redetermine the first time period or redetermine the side chain DRX activation time of the second terminal device.

[0152] Exemplarily, the first terminal device may send indication information to the network device by any of the following methods, wherein the indication information may indicate the start, end, or start and end of the first time period, and may also indicate the end or start and end of the sidelink DRX activation time of the second terminal device, or indicate that the second terminal device is in the sidelink DRX activation time, or the second terminal device is in the sidelink DRX inactive time, or the sidelink DRX state of the second terminal device, such as the second terminal device is in the sidelink DRX activation state or the sidelink DRX inactive state:

[0153] (1) Figure 5a The first terminal device sends the first indication information to the network device, and correspondingly, the network device receives the first indication information from the first terminal device, wherein the first indication information is used to indicate the end time of the first time period. It should be noted that in the embodiment of the present application, the first time period belongs to the sidelink DRX activation time of the second terminal device, and the first time period and the sidelink DRX activation time of the second terminal device may completely overlap or may not completely overlap. Figure 5a The only case is the incomplete overlap.

[0154] It should be noted that, in the embodiment of the present application, the first terminal device may send the first indication information to the network device at the start time of the first time period or after the start time of the first time period or within the first time period. Optionally, if the end time of the first time period changes compared with the end time of the last reported first time period, the first terminal device may send the first indication information to the network device at any time within the first time period, or, if the end time of the first time period is earlier than the end time of the last reported first time period, the first terminal device may send the first indication information to the network device when the first time period changes, for example, when the first terminal device has no data to be sent to the second terminal device, the first time period will change, or, if the end time of the first time period is later than or equal to the end time of the last reported first time period, the first terminal device may send the first indication information to the network device at the end time of the last reported first time period or at a time interval before the end time of the last reported first time period.

[0155] It should be noted that, in an embodiment of the present application, the time of the interval before the end time can be determined based on the DCI sent by the network device to the first terminal device. Specifically, the DCI sent by the network device to the first terminal device contains a "Time gap" field, and the value m of the field indicates the index m+1 of the time slot offset table. The time slot offset table is a parameter configured by the network device, for example, timeGapFirstSidelinkTransmission or sl-DCI-ToSL-Trans. The table is used to indicate the time slot offset between receiving the DCI and the first sidelink transmission scheduled by the DCI, that is, the time slot offset between receiving the DCI and the first sidelink transmission indicated in the sidelink permission contained in the DCI. The specific form of the table may include one or more time slot offsets, and the order of the one or more time slot offsets implicitly indicates the index, for example, the first time slot offset corresponds to index 1, and the second time slot offset corresponds to index 2. The table can also explicitly indicate the index corresponding to each time slot offset. Assume that the time slot offset corresponding to index m+1 is represented by K SL Indicates that the time slot of the first sidelink transmission scheduled by this DCI is no earlier than The first sidelink time slot in the resource pool of DL is the start time of the downlink timeslot where the DCI is located, T TA is the timing advance (TA) value, T slot is the duration of the sidelink time slot. The time of the interval before the end time can be determined according to the time slot offset table, such as the time of the interval before the end time can be the minimum or maximum value in the time slot offset table, or the time of the interval before the end time is the end time of the first time slot, and the time slot of the first sidelink transmission scheduled by the DCI in the first time slot is no earlier than T DL , When the first sidelink time slot in the resource pool of the DCI is used, the time slot of the first sidelink transmission scheduled by the DCI in the first time slot is the last time slot before the end time, and the time slot of the first sidelink transmission scheduled by the DCI in the first time slot may be partially before the end time, partially after the end time, or all before the end time, or the start time of the first time slot satisfies no earlier than The first sidelink time slot in the resource pool is the last time slot before the end time, where T DL,第一时隙 is the start time of the first time slot, K SL,min / max This is the minimum or maximum value in the slot offset table.

[0156] Or, if Figure 5bThe first terminal device sends the first indication information to the network device, and correspondingly, the network device receives the first indication information from the first terminal device, wherein the first indication information is used to indicate the end time of the side chain DRX activation time of the second terminal device.

[0157] It should be noted that, in an embodiment of the present application, the first terminal device may send the first indication information to the network device at the start time of the sidelink DRX activation time of the second terminal device or after the start time or within the sidelink DRX activation time of the second terminal device. Optionally, if the end time of the sidelink DRX activation time changes compared with the end time of the last reported sidelink DRX activation time, the first terminal device may send the first indication information to the network device at any time within the sidelink DRX activation time, or, if the end time of the sidelink DRX activation time is earlier than the end time of the last reported sidelink DRX activation time, the first terminal device may send the first indication information to the network device when the sidelink DRX activation time changes, or, if the end time of the sidelink DRX activation time is later than or equal to the end time of the last reported sidelink DRX activation time, the first terminal device may send the first indication information to the network device at the end time of the last reported sidelink DRX activation time or at a time interval before the end time.

[0158] (2) Figure 5c According to the invention, the first terminal device sends second indication information to the network device at the start time of the first time period or after the start time or within the first time period, and sends third indication information to the network device at the end time of the first time period or at a time interval before the end time. Accordingly, the network device receives the second indication information and the third indication information from the first terminal device, wherein the second indication information is used to indicate that the first time period has started or has started or is within the first time period, and the third indication information is used to indicate that the first time period has ended or is about to end.

[0159] It should be noted that, in the embodiment of the present application, the first time period belongs to the sidelink DRX activation time of the second terminal device, and the first time period and the sidelink DRX activation time of the second terminal device may completely overlap or may not completely overlap. Figure 5c The only case is the incomplete overlap.

[0160] Or, if Figure 5dThe first terminal device sends second indication information to the network device at the start time of the side chain DRX activation time of the second terminal device or after the start time or during the side chain DRX activation time of the second terminal device, and sends third indication information to the network device at the end time of the side chain DRX activation time of the second terminal device or at a time interval before the end time. Correspondingly, the network device receives the second indication information and the third indication information from the first terminal device, wherein the second indication information is used to indicate that the side chain DRX activation time of the second terminal device has started, and the third indication information is used to indicate that the side chain DRX activation time of the second terminal device has ended or is about to end.

[0161] Exemplarily, the first terminal device may send an indication message to the network device, wherein the indication message may indicate the start and duration of the first time period or the side chain DRX activation time, or indicate the start and end times of the first time period or the side chain DRX activation time, or indicate the duration and end time of the first time period or the side chain DRX activation time, or indicate the duration of the first time period or the side chain DRX activation time.

[0162] It should be noted that, in the embodiment of the present application, the first terminal device can trigger a side chain buffer status report (buffer status or, if the end time of the first time period or the sidechain DRX activation time is earlier than the end time of the last reported first time period or the sidechain DRX activation time, the first terminal device may send the indication information to the network device at the first time period or the sidechain DRX activation time; or, if the end time of the first time period or the sidechain DRX activation time is later than or equal to the end time of the last reported first time period or the sidechain DRX activation time, the first terminal device may send the indication information to the network device at the end time of the last reported first time period or the sidechain DRX activation time or at an interval before the end time; or, the first terminal device sends the indication information to the network device at the start time of the first time period or the sidechain DRX activation time or after the start time.

[0163] It should be noted that, in the embodiment of the present application, the indication information sent by the first terminal device to the network device may also be a BSR for providing the network device with side chain data volume information. The side chain BSR may indicate the cache data of the logical channel group (LCG) of each destination corresponding to the first terminal device. If the cache size of at least one destination corresponding to the first terminal device changes from non-zero to zero, the side chain BSR is triggered, and the cache of the destination includes the cache of all LCGs of the destination.

[0164] Optionally, if the sidechain BSR is a truncated sidechain BSR, the truncated sidechain BSR is not sent or is canceled. If the destination is not within the sidechain DRX activation time, the sidechain BSR does not contain relevant information of the destination, such as destination index, LCG ID, cache size, etc. If the destination is not within the sidechain DRX activation time, the sidechain data of the destination does not trigger the sidechain BSR, that is, the destination corresponding to the sidechain data that triggers the sidechain BSR needs to be within the sidechain DRX activation time. If a sidechain BSR is triggered, the destination corresponding to the LCG included in the sidechain BSR needs to be within the sidechain DRX activation time. If a destination is not within the sidechain DRX activation time, the sidechain BSR does not contain the LCG of the destination. If a sidechain BSR is triggered and a destination corresponding to the LCG included in the sidechain BSR is not within the sidechain DRX activation time, the cache size of the LCG of the destination is 0.

[0165] It should be noted that, in an embodiment of the present application, the indication information sent by the first terminal device to the network device may also be information for indicating that the cache size of at least one destination changes from non-zero to zero, wherein the cache of the destination includes the caches of all LCGs of the destination. Based on the indication information, the network device can estimate which destination's data the first terminal device has transmitted using the resources indicated by the sidechain authority, thereby estimating the sidechain DRX activation time or sidechain DRX activation status of the destination.

[0166] It should be noted that, in the embodiment of the present application, step 401 is an optional step, and the first terminal device may send the sidechain DRX parameters or indication information of the second terminal device to the network device. The network device may determine the first time period or the sidechain DRX activation time based on the sidechain DRX parameters or indication information, and the first terminal device may not send the sidechain DRX parameters or indication information of the second terminal device to the network device. The network device may determine the first time period or the sidechain DRX activation time based on the sidechain DRX parameters of the second terminal device configured by itself, or the network device may determine the first time period or the sidechain DRX activation time based on the sidechain DRX parameters of the second terminal device sent by any second terminal device.

[0167] It should be noted that, in an embodiment of the present application, the first terminal device or the second terminal device or the network device can determine the end time of the side chain DRX activation time of the second terminal device according to drx-InactivityTimerPC5, such as the end time of the side chain DRX activation time is the timeout time of drx-InactivityTimerPC5, or the first terminal device or the second terminal device or the network device can determine whether a certain moment is within the side chain DRX activation time of the second terminal device according to the state of drx-InactivityTimerPC5, such as if the drx-InactivityTimerPC5 is running at a certain moment, then the moment is within the side chain DRX activation time of the second terminal device, or the first terminal device or the second terminal device or the network device can directly determine the side chain DRX activation time of the second terminal device without starting or restarting drx-InactivityTimerPC5, such as the start or restart time of drx-InactivityTimerPC5 plus the time length of drx-InactivityTimerPC5 is the end time of the side chain DRX activation time of the second terminal device.

[0168] S402, the network device sends a side chain permission to the first terminal device. Correspondingly, the first terminal device receives the side chain permission from the network device. The side chain permission is used to indicate, schedule or allocate resources for the first terminal device to send PSCCH, PSSCH or SCI.

[0169] In some embodiments, the side chain authority is used to indicate, schedule or allocate resources for the first terminal device to send PSCCH, PSSCH or SCI. Subsequently, taking the side chain authority used to indicate the resources for the first terminal device to send PSCCH, PSSCH or SCI as an example, the time domain position of the resources may be within the first time period or the side chain DRX activation time of the second terminal device, and the time domain position of the resources may not be within the first time period or the side chain DRX activation time of the second terminal device. The embodiments of the present application do not impose specific restrictions on this.

[0170] It should be noted that, in the embodiment of the present application, the side chain permission may be included in downlink control information (DCI), MAC CE or RRC message.

[0171] It should be noted that in an embodiment of the present application, the network device may also send device identification information to the first terminal device, wherein the device identification information is used to indicate the second terminal device corresponding to the above-mentioned side chain authority, that is, to indicate that the first terminal device can send PSCCH, PSSCH or SCI to the second terminal device indicated by the device identification information on the resources indicated by the above-mentioned side chain authority. Correspondingly, the first terminal device receives device identification information from the network device, and determines the second terminal device corresponding to the side chain authority based on the device identification information, and the first terminal device uses the resources indicated by the side chain authority to send PSCCH, PSSCH or SCI to the second terminal device, wherein the device identification information can be a destination ID, such as sl-destinationIdentity, used to identify a destination of a side link communication, sl-destinationIdentity can be a destination layer-2ID, or, the device identification information can be a destination index, such as destination Index, used to indicate the destination corresponding to any information element (IE) in the destination information list or resource request list sent by the first terminal device to the network device, the destination index corresponds to the order of the information element IE or entry corresponding to a destination in the list, such as destination index = 0 corresponds to the destination corresponding to the first IE or entry in the list, and destination index = 1 corresponds to the destination corresponding to the second IE or entry in the list.

[0172] It should be noted that in an embodiment of the present application, the device identification information may be included in the DCI, MAC CE or RRC message that sends the side chain permission.

[0173] It should be noted that in an embodiment of the present application, if some of the one or more second terminal devices communicating with the first terminal device apply sidechain DRX and some of the second terminal devices do not apply sidechain DRX, optionally, the network device can indicate the device identification information corresponding to the sidechain authority to both the second terminal devices applying sidechain DRX and the second terminal devices not applying sidechain DRX, and the first terminal device can use the resources indicated by the sidechain authority to send PSCCH, PSSCH or SCI to the second terminal device applying sidechain DRX corresponding to the sidechain authority indicated by the network device. Alternatively, the network device may indicate the device identification information corresponding to the side chain authority to the second terminal device that applies the side chain DRX, and not indicate the device identification information corresponding to the side chain authority to the second terminal device that does not apply the side chain DRX. For the second terminal device that applies the side chain DRX, the first terminal device may use the resources indicated by the side chain authority to send PSCCH, PSSCH or SCI to the second terminal device that applies the side chain DRX corresponding to the side chain authority indicated by the network device. For the second terminal device that does not apply the side chain DRX, the first terminal device may determine the second terminal device that does not apply the side chain DRX corresponding to the side chain authority, and use the resources indicated by the side chain authority to send PSCCH, PSSCH or SCI to the second terminal device that applies the side chain DRX corresponding to the side chain authority.

[0174] It should be noted that, in the embodiment of the present application, the device identification information may be included in the DCI for sending the side chain permission by any of the following methods:

[0175] (1) The DCI includes Xth indication information, wherein the Xth indication information is used to indicate whether the Yth domain exists or whether the Yth domain is valid, and the Yth domain indicates the device identification information of the second terminal device corresponding to the sidechain authority. If the Xth indication information indicates that the Yth domain exists or the Yth domain is valid, the first terminal device can use the resources indicated by the sidechain authority to send PSCCH, PSSCH or SCI to the second terminal device that applies sidechain DRX corresponding to the sidechain authority indicated by the Yth domain. If the Xth indication information indicates that the Yth domain does not exist or the Yth domain is invalid or the Yth domain can be ignored, the first terminal device determines the second terminal device that does not apply sidechain DRX corresponding to the sidechain authority, and uses the resources indicated by the sidechain authority to send PSCCH, PSSCH or SCI to the second terminal device that applies sidechain DRX corresponding to the sidechain authority.

[0176] (2) The DCI includes a Yth field, wherein the Yth field indicates the device identification information of the second terminal device corresponding to the sidechain authority. If the second terminal device indicated by the Yth field is a second terminal device applying sidechain DRX, the first terminal device can use the resources indicated by the sidechain authority to send PSCCH, PSSCH or SCI to the second terminal device applying sidechain DRX corresponding to the sidechain authority indicated by the Yth field. If the second terminal device indicated by the Yth field is a second terminal device not applying sidechain DRX, the first terminal device determines the second terminal device not applying sidechain DRX corresponding to the sidechain authority, and uses the resources indicated by the sidechain authority to send PSCCH, PSSCH or SCI to the second terminal device applying sidechain DRX corresponding to the sidechain authority.

[0177] It should be noted that, in an embodiment of the present application, the above-mentioned DCI containing the Xth field or the Yth field can use the first DCI format, and the DCI that does not contain the Xth field or the Yth field can use the second DCI format, for example, DCI format 3_0. When there is a terminal device that applies sidelink DRX among the second terminal devices that communicate with the first terminal device sidelink, the first terminal device monitors or receives the first DCI format. When there is no terminal device that applies sidelink DRX among the second terminal devices that communicate with the first terminal device sidelink, the first terminal device monitors or receives the second DCI format. The first terminal device can send indication information that a second terminal device applies sidelink DRX to the network device, so that the network device determines the second terminal device that applies sidelink DRX in the sidelink communication with the first terminal device.

[0178] S403. The first terminal device sends PSCCH, PSSCH or SCI based on the side chain authority.

[0179] In some embodiments, if a first terminal device receives device identification information from a network device, wherein the device identification information is used to indicate a second terminal device corresponding to a side chain authority, the first terminal device can determine the second terminal device corresponding to the side chain authority based on the device identification information, and use the resources indicated by the side chain authority to send PSCCH, PSSCH or SCI to the second terminal device corresponding to the side chain authority, wherein the time domain position of the resources indicated by the side chain authority is within a first time period, and the first time period belongs to the side chain DRX activation time of the second terminal device, or the time domain position of the resources indicated by the side chain authority is within the side chain DRX activation time of the second terminal device, so that the second terminal device can receive PSCCH, PSSCH or SCI within the side chain DRX activation time, thereby avoiding the problem that the DRX mechanism between the first terminal device and the second terminal device cannot work or the side link resources are wasted due to the time domain position of the resources indicated by the side chain authority not being within the side chain DRX activation time of the second terminal device.

[0180] In other embodiments, if the first terminal device does not receive the device identification information from the network device, wherein the device identification information is used to indicate the second terminal device corresponding to the side chain authority, the first terminal device can determine the second terminal device corresponding to the side chain authority by itself, and use the resources indicated by the side chain authority to send PSCCH, PSSCH or SCI to the second terminal device corresponding to the side chain authority, wherein the time domain position of the resources indicated by the side chain authority is within a first time period, and the first time period includes the side chain DRX activation time of the second terminal device, or the time domain position of the resources indicated by the side chain authority includes the side chain DRX activation time of the second terminal device, so that the second terminal device can receive PSCCH, PSSCH or SCI within the side chain DRX activation time, thereby avoiding the problem that the DRX mechanism between the first terminal device and the second terminal device cannot work, or the side link resources are wasted due to the time domain position of the resources indicated by the side chain authority not being within the side chain DRX activation time of the second terminal device.

[0181] In order to achieve reasonable control of the side chain DRX activation time, that is, to maintain or align the side chain DRX activation time of the network device, the terminal device at the transmitting end and the terminal device at the receiving end, the embodiments of the present application provide the following embodiments 2 and 3, which can be implemented in combination with the above-mentioned embodiment 1, as described in detail below.

[0182] Example 2

[0183] In this embodiment 2, the side chain DRX activation time of the second terminal device may include the running time of drx-onDudrationTimerPC5 and drx-InactivityTimerPC5. For example, at the start time of the DRX cycle, the second terminal device starts drx-onDurationTimerPC5, that is, enters "On Duration". When drx-onDurationTimerPC5 starts to run, it enters the side chain DRX activation time. During the running of drx-onDurationTimerPC5, the second terminal device starts or restarts drx-InactivityTimerPC5 to extend the side chain DRX activation time. Since the status of drx-InactivityTimerPC5 maintained by the second terminal device needs to be consistent with the status of drx-InactivityTimerPC5 maintained by the first terminal device and the network device, the first terminal device and the network device also need to start or restart drx-InactivityTimerPC5 during the running of drx-onDurationTimerPC5, wherein the first terminal device, the second terminal device and the network device can implicitly start or restart drx-InactivityTimerPC5.

[0184] Exemplarily, implicitly starting or restarting drx-InactivityTimerPC5 may include at least one of the following situations:

[0185] The first terminal device may start or restart drx-InactivityTimerPC5 after sending PSCCH, PSSCH, SCI or MAC PDU. The first terminal device may determine the time to start or restart drx-InactivityTimerPC5 according to the time domain position of PSCCH, PSSCH, SCI or MAC PDU transmission, such as starting drx-InactivityTimerPC5 in the first time slot or symbol after the end of PSCCH, PSSCH, SCI or MAC PDU transmission. SCI includes second-level SCI;

[0186] Alternatively, the first terminal device may start or restart drx-InactivityTimerPC5 after receiving HARQ feedback information corresponding to PSCCH, PSSCH, SCI or MAC PDU transmission sent by the second terminal device, wherein the HARQ feedback information includes positive acknowledgement (ACK) information or negative acknowledgement (NACK) information, and the first terminal device may determine the time to start or restart drx-InactivityTimerPC5 according to the time domain position of the HARQ feedback transmission, such as starting drx-InactivityTimerPC5 in the first time slot or symbol after the end of the HARQ feedback transmission. SCI includes a second-level SCI;

[0187] The second terminal device may start or restart drx-InactivityTimerPC5 after receiving the PSCCH, PSSCH, SCI or MAC PDU sent by the first terminal device. The second terminal device may determine the time to start or restart drx-InactivityTimerPC5 according to the time domain position of the PSCCH, PSSCH, SCI or MAC PDU transmission, such as starting drx-InactivityTimerPC5 in the first time slot or symbol after receiving the PSCCH, PSSCH, SCI or MAC PDU.

[0188] Alternatively, the second terminal device may start or restart drx-InactivityTimerPC5 after sending HARQ feedback information corresponding to PSCCH, PSSCH, SCI or MAC PDU transmission, wherein the HARQ feedback information includes ACK information or NACK information, and the second terminal device may determine the time to start or restart drx-InactivityTimerPC5 according to the time domain position of the HARQ feedback transmission, such as starting drx-InactivityTimerPC5 in the first time slot or symbol after the end of the HARQ feedback transmission. SCI includes a second-level SCI;

[0189] The network device can start or restart drx-InactivityTimerPC5 after sending the sidechain authority to the first terminal device, wherein the sidechain authority is used to indicate the resources for the first terminal device to send PSCCH, PSSCH or SCI transmission, and the resources indicated by the sidechain authority may include at least one sidechain transmission resource. The network device can determine the time to start or restart drx-InactivityTimerPC5 based on the time domain position of the PSCCH, PSSCH, SCI or MAC PDU transmission indicated by the sidechain authority, such as starting drx-InactivityTimerPC5 in the first time slot or symbol after the time domain position of the PSCCH, PSSCH, SCI or MAC PDU transmission resource indicated by the sidechain authority ends.

[0190] Alternatively, after the network device receives HARQ feedback information transmitted by PSCCH, PSSCH, SCI or MAC PDU indicating the side chain authority corresponding to the first terminal device, drx-InactivityTimerPC5 is started or restarted, wherein the HARQ feedback information includes ACK information or NACK information, and the network device can determine the time to start or restart drx-InactivityTimerPC5 according to the time domain position of the SLHARQ feedback transmission corresponding to the PSCCH, PSSCH, SCI or MAC PDU transmission, such as starting drx-InactivityTimerPC5 in the first time slot or symbol after the end of the SL HARQ feedback transmission corresponding to the PSCCH, PSSCH, SCI or MAC PDU transmission. SCI includes second-level SCI.

[0191] Example 3

[0192] In this embodiment 3, the side chain DRX activation time of the second terminal device may include the running time of drx-onDudrationTimerPC5 and drx-InactivityTimerPC5. For example, at the start time of the side chain DRX cycle, the second terminal device starts drx-onDurationTimerPC5, that is, enters "On Duration". When drx-onDurationTimerPC5 starts to run, it enters the side chain DRX activation time. During the running of drx-onDurationTimerPC5, the second terminal device starts or restarts drx-InactivityTimerPC5 to extend the side chain DRX activation time. Since the status of drx-InactivityTimerPC5 maintained by the second terminal device needs to be consistent with that of drx-InactivityTimerPC5 maintained by the first terminal device and the network device, the first terminal device and the network device also need to start or restart drx-InactivityTimerPC5 during the running of drx-onDurationTimerPC5. Among them, the first terminal device, the second terminal device and the network device can explicitly start or restart drx-InactivityTimerPC5.

[0193] Exemplarily, explicitly starting or restarting drx-InactivityTimerPC5 may include at least one of the following situations:

[0194] The first terminal device may send fourth indication information to the network device and the second terminal device, and the first terminal device starts or restarts drx-InactivityTimerPC5 after sending the fourth indication information, wherein the fourth indication information is used to instruct drx-InactivityTimerPC5 to start or restart;

[0195] The network device and the second terminal device start or restart drx-InactivityTimerPC5 after receiving the fourth indication information sent by the first terminal device, wherein the fourth indication information is used to instruct drx-InactivityTimerPC5 to start or restart.

[0196] It should be noted that, in an embodiment of the present application, when the first terminal device sends the fourth indication information to the second terminal device, the fourth indication information may be included in the SCI, such as using a field (a 1-bit field) in the SCI to indicate that drx-InactivityTimerPC5 is started or restarted. When the value in the field is 1, it indicates start or restart, and when it is 0, it indicates not start. Alternatively, the fourth indication information is transmitted via the PSSCH, that is, the PSSCH carries the fourth indication information.

[0197] It should be noted that, in the embodiment of the present application, when the first terminal device sends the fourth indication information to the network device and the second terminal device, the fourth indication information may also have any of the following functions:

[0198] (1) Instruct drx-InactivityTimerPC5 to start or restart;

[0199] (2) indicating the start or restart time of drx-InactivityTimerPC5, such as a time slot or symbol indicating the start or restart time of drx-InactivityTimerPC5;

[0200] When indicating the time slot of the start or restart moment of drx-InactivityTimerPC5, the SFN or DFN of the time slot and the index within the system frame number (SFN) or direct frame number (DFN) of the time slot may be indicated, or the subframe of the time slot and the index of the time slot within the subframe may be indicated, or the index of the time slot may be indicated, such as the index of the time slot on the sidelink or the index of the time slot in the sidelink resource pool. When indicating the symbol of the start or restart moment of drx-InactivityTimerPC5, the index of the symbol within the subframe or time slot and the subframe or time slot may be indicated. When indicating the subframe, the SFN or DFN of the subframe and the index within the SFN or DFN of the subframe may be indicated, or the index of the subframe may be indicated, such as the index of the subframe on the sidelink or the index of the subframe in the sidelink resource pool.

[0201] (3) indicating the timeout moment of drx-InactivityTimerPC5, such as a time slot or symbol indicating the timeout moment of drx-InactivityTimerPC5;

[0202] When indicating the time slot of the timeout moment of drx-InactivityTimerPC5, the SFN or DFN where the time slot is located and the index within the SFN or DFN where the time slot is located may be indicated, or the subframe where the time slot is located and the index of the time slot within the subframe may be indicated, or the index of the time slot may be indicated, such as the index of the time slot on the sidelink or the index of the time slot in the sidelink resource pool. When indicating the symbol of the timeout moment of drx-InactivityTimerPC5, the index of the symbol within the subframe or time slot may be indicated, and the subframe or time slot may be indicated. When indicating a subframe, the SFN or DFN where the subframe is located and the index within the SFN or DFN where the subframe is located may be indicated, or the index of the subframe may be indicated, such as the index of the subframe on the sidelink or the index of the subframe in the sidelink resource pool.

[0203] (4) indicating the end time of the sidelink DRX activation time, such as the time slot or symbol indicating the end time of the sidelink DRX activation time;

[0204] When indicating the time slot of the end moment of the sidelink DRX activation time, the SFN or DFN where the time slot is located and the index within the SFN or DFN where the time slot is located can be indicated, or the subframe where the time slot is located and the index of the time slot within the subframe can be indicated, or the index of the time slot is indicated, such as the index of the time slot on the sidelink or the index of the time slot in the sidelink resource pool. When indicating the symbol of the end moment of the sidelink DRX activation time, the index of the symbol in the subframe or time slot can be indicated, and the subframe or time slot can be indicated. When indicating a subframe, the SFN or DFN where the subframe is located and the index within the SFN or DFN where the subframe is located can be indicated, or the index of the subframe can be indicated, such as the index of the subframe on the sidelink or the index of the subframe in the sidelink resource pool.

[0205] It should be noted that, in the embodiment of the present application, when the first terminal device sends the fourth indication message to the network device, the fourth indication message may also have any of the following functions:

[0206] (1) Indicates the time domain location of the resource indicated by the side chain permission, which is the side chain permission corresponding to the start or restart time of drx-InactivityTimerPC5;

[0207] (2) Indicates the time domain position of downlink control information (DCI), which is used to schedule or contain the side chain permission corresponding to the start or restart time of drx-InactivityTimerPC5.

[0208] Optionally, when drx-InactivityTimerPC5 is started or restarted, or after drx-InactivityTimerPC5 is started or restarted, or the timeout moment of drx-InactivityTimerPC5, or the end moment of the sidelink DRX activation time of the second terminal device triggers the first terminal device to send fourth indication information to the network device and the second terminal device.

[0209] Optionally, when the first terminal device sends the fourth indication information to the network device, the fourth indication information may also indicate the second terminal device or destination corresponding to drx-InactivityTimerPC5, or the second terminal device or destination corresponding to the sidelink DRX activation time.

[0210] In the above-mentioned embodiments 1, 2 and 3, the second terminal device can start or restart the drx-InactivityTimerPC5, drx-HARQ-RTT-TimerPC5 or drx-RetransmissionTimerPC5 corresponding to the sidelink DRX of the second terminal device according to the information contained in the received SCI.

[0211] Exemplarily, the information included in the SCI may be a source layer-1ID and a destination layer-1ID. If the second terminal device receives an SCI (including a second-level SCI) that schedules a new transmission of the sidelink, and the source layer-1ID included in the SCI is the same as the layer-1ID of the first terminal device, and the destinationlayer-1ID included in the SCI is the same as the layer-1ID of the second terminal device, then the second terminal device starts or restarts the drx-InactivityTimerPC5, drx-HARQ-RTT-TimerPC5 or drx-RetransmissionTimerPC5 corresponding to the sidelink DRX between the first terminal device and the second terminal device. Among them, the source layer-1ID included in the SCI is the same as the layer-1ID of the first terminal device, which can also be understood as the source layer-1ID included in the SCI is the same as the 8LSB of the layer-2ID of the first terminal device. The destination layer-1ID included in the SCI is the same as the layer-1ID of the second terminal device, which can also be understood as the destination layer-1ID included in the SCI is the same as the 8LSB of the layer-2ID of the second terminal device.

[0212] Alternatively, the information included in the SCI may also be source layer-1ID, destination layer-1ID and communication type (cast type), wherein cast type is used to indicate whether the sidelink communication is unicast communication, multicast communication or broadcast communication. If the second terminal device receives an SCI (including a second-level SCI) that schedules a new transmission of the sidelink, and the cast type included in the SCI indicates that the sidelink communication is unicast communication, the source layer-1ID included in the SCI is the same as the layer-1ID of the first terminal device, and the destination layer-1ID included in the SCI is the same as the layer-1ID of the second terminal device, then the second terminal device starts or restarts the drx-InactivityTimerPC5, drx-HARQ-RTT-TimerPC5 or drx-RetransmissionTimerPC5 corresponding to the sidelink DRX between the first terminal device and the second terminal device.

[0213] Alternatively, the information included in the SCI may also be the destination layer-1ID and cast type. If the second terminal device receives an SCI (including a second-level SCI) that schedules a new transmission of the sidelink, and the casttype included in the SCI indicates that the sidelink communication is a multicast communication, and the destination layer-1ID included in the SCI is the same as the destination layer-1ID corresponding to the sidelink multicast communication, the second terminal device starts or restarts the drx-InactivityTimerPC5, drx-HARQ-RTT-TimerPC5 or drx-RetransmissionTimerPC5 corresponding to the sidelink DRX of the multicast communication.

[0214] It should be noted that, in the embodiment of the present application, the layer-1ID of the terminal device can be the source layer-1ID when the terminal device acts as a transmitter, and also the destination layer-1ID when the terminal device acts as a receiver. The layer-2ID of the terminal device can be the source layer-2ID when the terminal device acts as a transmitter, and also the destination layer-2ID when the terminal device acts as a receiver.

[0215] It should be noted that in an embodiment of the present application, the second terminal device can determine, based on the information contained in the received SCI, that the SCI is sent by the first terminal device to the second terminal device, or determine that the PSCCH, PSSCH or MAC PDU corresponding to the SCI is sent by the first terminal device to the second terminal device.

[0216] It should be noted that, in an embodiment of the present application, when the second terminal device conducts sidelink communication with multiple first terminal devices, and the layer-1ID corresponding to the multiple first terminal devices is the same, and the layer-1ID used by the second terminal device in the sidelink communication with each of the multiple first terminal devices is the same, if the source layer-1ID contained in the SCI received by the second terminal device is the same as the layer-1ID of the multiple first terminal devices, and the destination layer-1ID contained in the SCI is the same as the layer-1ID of the second terminal device, the second terminal device starts or restarts the drx-InactivityTimerPC5, drx-HARQ-RTT-TimerPC5 or drx-RetransmissionTimerPC5 corresponding to the sidelink DRX between the second terminal device and a certain first terminal device, the second terminal device will not be able to determine which first terminal device among the multiple first terminal devices conducting sidelink communication with the second terminal device is.

[0217] The present application can solve the above problems in two ways. The following describes the specific implementation of the two ways in detail with reference to specific examples:

[0218] Method 1: The second terminal device can respectively start or restart the drx-InactivityTimerPC5, drx-HARQ-RTT-TimerPC5 or drx-RetransmissionTimerPC5 corresponding to the sidelink DRX between the second terminal device and each of the multiple first terminal devices.

[0219] Optionally, if the second terminal device receives a newly transmitted SCI (including a second-level SCI) of the scheduling side link, the second terminal device will not stop drx-RetransmissionTimerPC5, and will restart drx-RetransmissionTimerPC5 when drx-HARQ-RTT-TimerPC5 times out and drx-RetransmissionTimerPC5 is running.

[0220] Method two, the second terminal device can start or restart the drx-InactivityTimerPC5 corresponding to the side link DRX between the second terminal device and one of the multiple first terminal devices, wherein the duration of the drx-InactivityTimerPC5 is the maximum value of the drx-InactivityTimerPC5 corresponding to the side link DRX between the second terminal device and the multiple first terminal devices;

[0221] Alternatively, the second terminal device may start or restart the drx-HARQ-RTT-TimerPC5 corresponding to the side link DRX between the second terminal device and one of the multiple first terminal devices, wherein the duration of the drx-HARQ-RTT-TimerPC5 is the minimum value of the drx-InactivityTimerPC5 corresponding to the side link DRX between the second terminal device and the multiple first terminal devices;

[0222] Alternatively, the second terminal device can start or restart the drx-RetransmissionTimerPC5 corresponding to the side link DRX between the second terminal device and one of the multiple first terminal devices, where the duration of drx-RetransmissionTimerPC5 is the maximum value of the drx-InactivityTimerPC5 corresponding to the side link DRX between the second terminal device and the multiple first terminal devices.

[0223] It should be noted that, in an embodiment of the present application, when the source layer-1ID and destination layer-1ID of multiple side-link unicast communications are the same, the SCI transmitted between the terminal device of the transmitting end (e.g., the first terminal device) and the terminal device of the receiving end (e.g., the second terminal device) in any side-link unicast communication may cause the terminal device of the receiving end in other side-link unicast communications to mistakenly start or restart the drx-InactivityTimerPC5, drx-HARQ-RTT-TimerPC5 or drx-RetransmissionTimerPC5 corresponding to the sidelink DRX between the terminal device of the corresponding transmitting end, thereby causing the sidelink DRX activation time of the terminal device of the receiving end maintained by the terminal device of the transmitting end in other side-link unicast communications to be different from the sidelink DRX activation time of the terminal device of the receiving end maintained by the terminal device of the receiving end, thereby causing power consumption of the receiving end to be wasted, or causing the receiving end to fail to receive the sidelink transmission from the transmitting end.

[0224] The present application embodiment can solve the above problems in four ways. The specific implementation of the four ways is described in detail below with reference to specific examples:

[0225] Method 1: If the second terminal device receives an SCI (including a second-level SCI) that schedules a new transmission on the sidelink, and the destination layer-1ID contained in the SCI is the same as the layer-1ID of the second terminal device in a sidelink unicast communication, and the source layer-1ID contained in the SCI is the same as the layer-1ID of the first terminal device corresponding to the second terminal device in the sidelink unicast communication, then the second terminal device can determine whether the source layer-2ID of the MAC PDU is the same as the layer-2ID of the first terminal device corresponding to the second terminal device in the sidelink unicast communication, or whether the destination of the MAC PDU is the same as the layer-2ID of the first terminal device corresponding to the second terminal device in the sidelink unicast communication, by decoding the MAC PDU corresponding to the SCI. Whether the layer-2ID is the same as the layer-2ID of the second terminal device in the sidelink unicast communication, if different, the second terminal device can start or restart the drx-InactivityTimerPC5, drx-HARQ-RTT-TimerPC5 or drx-RetransmissionTimerPC5 corresponding to the sidelink unicast communication according to the SCI (that is, when it is determined that it is not, the drx-InactivityTimerPC5, drx-HARQ-RTT-TimerPC5 or drx-RetransmissionTimerPC5 corresponding to the sidelink unicast communication has not been started or restarted) or after (that is, when it is determined that it is not, the sidelink has been started or restarted The second terminal device does not start or restart the drx-InactivityTimerPC5, drx-HARQ-RTT-TimerPC5 or drx-RetransmissionTimerPC5 corresponding to the side link unicast communication due to the SCI.

[0226] Method 2: if the second terminal device uses or is configured or activated sidelink DRX, it satisfies that the layer-1ID corresponding to the layer-2ID used or allocated by the second terminal device in different sidelink unicast communications between the second terminal device and multiple first terminal devices is different.

[0227] Exemplarily, the second terminal device may use or allocate layer-2ID in the process of establishing a PC5 unicast link with the first terminal device, such as the second terminal device may use or allocate layer-2ID when or before sending a PC5 unicast link establishment request message, or the second terminal device may use or allocate layer-2ID after receiving a PC5 unicast link establishment request message sent by the first terminal device, and make the layer-1ID corresponding to the layer-2ID different from the layer-1ID corresponding to the layer-2ID used or allocated by the second terminal device in other sidelink unicast communications.

[0228] It should be understood that in an embodiment of the present application, after the second terminal device establishes a PC5 unicast link with the first terminal device, the second terminal device may also update the layer-2ID and send the updated layer-2ID to the first terminal device during the PC5 unicast link identifier update process, so that the layer-1ID corresponding to the updated layer-2ID is different from the layer-1ID corresponding to the layer-2ID used or allocated by the second terminal device in other sidelink unicast communications.

[0229] Method three: if the second terminal device uses or is configured or activated sidelink DRX, the layer-1ID corresponding to the layer-2ID used or allocated by the second terminal device in any sidelink unicast communication is different from the layer-1ID corresponding to the layer-2ID in other sidelink unicast communications, wherein the second terminal device is not a terminal device in the other sidelink unicast communications.

[0230] It should be noted that, in an embodiment of the present application, the second terminal device can obtain the source layer-1ID and destination layer-1ID in other side-link unicast communications based on the SCI transmitted in other side-link unicast communications, and decode the MAC PDU corresponding to the SCI, thereby obtaining the source layer-2ID and destination layer-2ID in other side-link unicast communications, and can determine that the second terminal device is not a terminal device in the other side-link unicast communication based on the source layer-2ID and destination layer-2ID in the other side-link unicast communication.

[0231] Exemplarily, the second terminal device may use or allocate layer-2ID in the process of establishing a PC5 unicast link with the first terminal device, such as the second terminal device uses or allocates layer-2ID when or before sending a PC5 unicast link establishment request message, or the second terminal device uses or allocates layer-2ID after receiving a PC5 unicast link establishment request message sent by the first terminal device, so that the layer-1ID corresponding to the layer-2ID is different from the layer-1ID corresponding to the layer-2ID in other sidelink unicast communications.

[0232] It should be understood that in an embodiment of the present application, after the second terminal device establishes a PC5 unicast link with the first terminal device, the second terminal device may also update the layer-2ID and send the updated layer-2ID to the first terminal device during the PC5 unicast link identifier update process, so that the layer-1ID corresponding to the layer-2ID is different from the layer-1ID corresponding to the layer-2ID in other sidelink unicast communications.

[0233] Method four: The second terminal device can start or restart the drx-InactivityTimerPC5, drx-HARQ-RTT-TimerPC5 or drx-RetransmissionTimerPC5 corresponding to the sidelink DRX of the second terminal device according to the received destinationlayer-2ID and source layer-2ID corresponding to the sidelink transmission.

[0234] Exemplarily, if the second terminal device receives a sidelink transmission, and the source layer-2ID corresponding to the sidelink transmission is the same as the layer-2ID of the first terminal device, and the destination layer-2ID corresponding to the SL transmission is the same as the layer-2ID of the second terminal device, then the second terminal device starts or restarts the drx-InactivityTimerPC5, drx-HARQ-RTT-TimerPC5 or drx-RetransmissionTimerPC5 corresponding to the sidelink DRX between the first terminal device.

[0235] It should be understood that in an embodiment of the present application, if the sidelink transmission is a new transmission, the second terminal device only starts or restarts the drx-InactivityTimerPC5 corresponding to the sidelink DRX between the first terminal device; if the sidelink transmission is a retransmission, the second terminal device only starts or restarts the drx-InactivityTimerPC5, drx-HARQ-RTT-TimerPC5 or drx-RetransmissionTimerPC5 corresponding to the sidelink DRX between the first terminal device.

[0236] If the second terminal device receives an SCI (including a second-level SCI) for a newly transmitted scheduled sidelink, and the source layer-1ID contained in the SCI is the same as the source layer-1ID of the first terminal device, and the destination layer-1ID contained in the SCI is the same as the layer-1ID of the second terminal device, then the second terminal device starts or restarts the drx-InactivityTimerPC5, drx-HARQ-RTT-TimerPC5 or drx-RetransmissionTimerPC5 corresponding to the sidelink DRX between the second terminal device and the first terminal device if the MAC PDU corresponding to the SCI cannot be correctly decoded.

[0237] If the first terminal device sends an SCI to the second terminal device and receives a negative acknowledgement of the SCI from the second terminal device, the first terminal device does not start or restart the drx-InactivityTimerPC5, drx-HARQ-RTT-TimerPC5 or drx-RetransmissionTimerPC5 corresponding to the sidelink DRX between the first terminal device and the second terminal device due to the SCI.

[0238] It should be noted that in an embodiment of the present application, if the second terminal device receives an SCI indicating a new sidelink transmission from the first terminal device, or a fourth indication message, the second terminal device will start or restart drx-InactivityTimerPC5. However, if the MAC PDU corresponding to the SCI or the fourth indication message only contains non-data information, for example, only contains non-data information such as SL-CSI reporting or sidelink resource information in collaboration between terminal devices, and does not contain data information such as STCH data or SCCH data, it will cause the second terminal device to unnecessarily increase the sidelink activation time, thereby increasing the power consumption of the second terminal device.

[0239] The present application can solve the above problems in two ways. The following describes the specific implementation of the two ways in detail with reference to specific examples:

[0240] Method 1: If the first terminal device sends an SCI indicating a new sidelink transmission to the second terminal device, and the MAC PDU corresponding to the SCI contains the first information but not the second information, the second terminal device does not start or restart drx-InactivityTimerPC5.

[0241] Exemplarily, after receiving the SCI indicating a new sidelink transmission sent by the first terminal device, the second terminal device starts or restarts drx-InactivityTimerPC5. If the second terminal device decodes that the MAC PDU corresponding to the SCI contains the first information but not the second information, then before starting or restarting drx-InactivityTimerPC5 according to the SCI (i.e., when the MAC PDU corresponding to the SCI is decoded to contain the first information but not the second information, drx-InactivityTimerPC5 has not been started or restarted) or after (i.e., when the MAC PDU corresponding to the SCI is decoded to contain the first information but not the second information, drx-InactivityTimerPC5 has been started or restarted), the start or restart of drx-InactivityTimerPC5 is canceled, that is, the state of drx-InactivityTimerPC5 before receiving the SCI is maintained, or in other words, the SCI does not cause a state change of drx-InactivityTimerPC5.

[0242] Exemplarily, the first terminal device may include information used to indicate that the MAC PDU corresponding to the SCI contains the first information but not the second information in the SCI indicating a new sidelink transmission sent to the second terminal device, or include information used to indicate that the MAC PDU corresponding to the SCI contains the second information. After the second terminal device receives the SCI indicating a new sidelink transmission sent by the first terminal device, if the second terminal device determines based on the SCI that the MAC PDU corresponding to the SCI contains the first information but not the second information, the second terminal device does not start or restart drx-InactivityTimerPC5 after receiving the SCI; if the second terminal device determines based on the SCI that the MAC PDU corresponding to the SCI contains the second information, the second terminal device starts or restarts drx-InactivityTimerPC5 after receiving the SCI.

[0243] Exemplarily, the first terminal device may send fourth indication information to the second terminal device, or the first terminal device may send information for indicating not to start or restart drx-InactivityTimerPC5 to the second terminal device. The fourth indication information and the information for indicating not to start or restart drx-InactivityTimerPC5 may be included in the SCI or MAC CE. If the second terminal device determines that the SCI or MAC CE contains information for indicating not to start or restart drx-InactivityTimerPC5, the second terminal device determines that the MAC PDU corresponding to the SCI or MAC CE contains the first information but not the second information, and the second terminal device does not start or restart drx-InactivityTimerPC5 after receiving the SCI or MAC CE; if the second terminal device determines that the SCI or MAC CE contains the fourth indication information, the second terminal device determines that the MAC PDU corresponding to the SCI or MAC CE contains the second information, and the second terminal device starts or restarts drx-InactivityTimerPC5 after receiving the SCI or MAC CE.

[0244] Method 2: If the first terminal device sends an SCI indicating a new sidelink transmission to the second terminal device, and the MAC PDU corresponding to the SCI contains the first information but not the second information, the second terminal device starts the first timer, and the second terminal device monitors the PSCCH, PSSCH or SCI during the operation of the first timer, wherein the duration of the first timer is less than the duration of drx-InactivityTimerPC5.

[0245] It should be noted that, in the embodiment of the present application, the first information may be one or more of the following: SL-CSI reporting, side link resource information in the collaboration between terminal devices; the second information includes one or more of the following: SCCH data, STCH data, MAC CE other than the first information. Alternatively, the first information may be one or more of the following: SL-CSI reporting, side link resource information in the collaboration between terminal devices, SCCH data, information other than STCH data; the second information may be STCH data.

[0246] It should be noted that in an embodiment of the present application, the above two methods can be extended to the DRX of the Uu interface transmission between the second terminal device and the base station. For example, the first terminal device is replaced by the base station, the SCI is replaced by the DCI, and the SCI indicating the new transmission of the side link is replaced by the DCI indicating the new transmission. Then, the first information can be one or more of the following: data of the broadcast control channel (BCCH), data of the paging control channel (PCCH), data of the common control channel (CCCH), and data of the dedicated control channel (DCCH); the second information can be data of a dedicated traffic channel (DTCH).

[0247] The first terminal device in the above-mentioned embodiments 1, 2 and 3 can discard the side chain rights sent by the network device when a conflict occurs between the side link transmission and the uplink transmission. The side chain rights can be the side chain rights whose time domain positions of the resources indicated above are within the first time period, or can be the side chain rights whose time domain positions of the resources indicated above are not within the first time period. The embodiments of the present application do not make specific limitations on this.

[0248] It should be noted that, in the embodiment of the present application, the discarded side chain authority can also be understood as an unused side chain authority, which means that the first terminal device does not send PSCCH, PSSCH or SCI on the resources indicated by the side chain authority.

[0249] It should be noted that, in an embodiment of the present application, if the first terminal device discards or determines to discard a side chain permission sent by the network device, the network device will start or restart drx-InactivityTimerPC5, while the first terminal device and the second terminal device do not start or restart drx-InactivityTimerPC5, so that the states of drx-InactivityTimerPC5 maintained by the first terminal device and the second terminal device are inconsistent with the states of drx-InactivityTimerPC5 maintained by the network device. The time domain position of the resource indicated by the side chain permission subsequently sent by the network device to the first terminal device may not be within the side chain DRX activation time of the second terminal device. If the first terminal device uses the resource indicated by the side chain permission to send PSCCH, PSSCH or SCI, due to the second terminal device The terminal device does not receive PSCCH, PSSCH or SCI during the sidelink DRX inactive time. Therefore, the second terminal device cannot receive PSCCH, PSSCH or SCI. If the second terminal device is to receive PSCCH, PSSCH or SCI, the second terminal device must also receive PSCCH, PSSCH or SCI during the sidelink DRX inactive time, which will cause the DRX mechanism to fail to work. If the first terminal device does not use the resources indicated by the sidelink authority to send PSCCH, PSSCH or SCI, it will cause a waste of resources indicated by the sidelink authority. In view of this, the drx-InactivityTimerPC5 maintained by the first terminal device and the second terminal device can be made consistent with the state of drx-InactivityTimerPC5 maintained by the network device by any of the following methods:

[0250] (1) Figure 5e As shown, if the first terminal device discards or determines to discard a side chain permission sent by the network device, the first terminal device triggers the sending of the fifth indication information to the network device. Among them, the fifth indication information is used to indicate that the side chain DRX activation time of the second terminal device corresponding to the side chain permission has ended or is about to end. It can be understood that the fifth indication information can also indicate that the first terminal device has discarded or determined to discard the side chain permission. The side chain DRX activation time can be the side chain DRX activation time between the first terminal device and the second terminal device corresponding to the side chain permission, and can be determined by the first terminal device, the second terminal device corresponding to the side chain permission, or the first terminal device and the second terminal device corresponding to the side chain permission. Discarding the side chain permission will not cause the side chain DRX activation time to change or drx-InactivityTimerPC5 to start or restart.

[0251] It should be understood that in the embodiment of the present application, the first terminal device triggers the sending of indication information to the network device, which can be understood as the first terminal device triggering the sending of indication information, or the first terminal device triggering the reporting of indication information, or the first terminal device triggering the reporting of indication information, and the embodiment of the present application does not specifically limit this. After the first terminal device triggers the sending of indication information to the network device, when the first terminal device has uplink transmission resources, the indication information is sent to the network device. For example, the first terminal device triggers the sending of the fifth indication information to the network device, which can be understood as the first terminal device triggering the sending of the fifth indication information, or the first terminal device triggering the reporting of the fifth indication information, or the first terminal device triggering the reporting of the fifth indication information. After the first terminal device triggers the sending of the fifth indication information to the network device, when the first terminal device has uplink transmission resources, the fifth indication information is sent to the network device.

[0252] Optionally, in an embodiment of the present application, the first terminal device may trigger sending the fifth indication information to the network device after determining to discard the side link authority, or after discarding the side link authority, or after the time domain position of the resource indicated by the side link authority, or the end time of the time domain position of the first side link transmission indicated by the side link authority, or the first time slot or symbol after the end of the time domain position of the first side link transmission contained in the side link authority, or after determining to discard the side link authority, or after discarding the side link authority, or after an interval after the end of the time domain position of the first side link transmission contained in the side link authority, or the end time of the side link DRX activation time, or a time interval before the end time of the side link DRX activation time.

[0253] Optionally, in an embodiment of the present application, the first terminal device may determine the side chain DRX activation time according to the time domain position of the sent PSCCH, PSSCH or SCI, or drx-onDurationTimerPC5. For example, after the first terminal device sends PSCCH, PSSCH, SCI or MAC PDU to the second terminal device before or after discarding the side chain authority, the first terminal device starts or restarts drx-InactivityTimerPC5, then determines that the side chain DRX activation time includes the running time of drx-InactivityTimerPC5, and the end time of the side chain DRX activation time is later than or equal to the timeout time of drx-InactivityTimerPC5. If the first terminal device does not send PSCCH, PSSCH or SCI to the second terminal device during the running period of drx-onDurationTimerPC5, the end time of the side chain DRX activation time is the timeout time of drx-onDurationTimerPC5. The side chain DRX activation time is a continuous period of time.

[0254] For example, Figure 5f As shown, if the first terminal device uses the resources on the first side chain authority to send PSCCH, PSSCH, SCI or MAC PDU to the second terminal device before discarding the second side chain authority, the first terminal device starts or restarts drx-InactivityTimerPC5, determines that the side chain DRX activation time includes the running time of drx-InactivityTimerPC5, and the end time of the side chain DRX activation time is equal to the timeout time of drx-InactivityTimerPC5;

[0255] Or, if Figure 5g As shown, if the first terminal device uses the resources on the first side chain authority to send PSCCH, PSSCH, SCI or MAC PDU to the second terminal device before discarding the second side chain authority, and the first terminal device uses the resources on the third side chain authority to send PSCCH, PSSCH, SCI or MAC PDU to the second terminal device after discarding the second side chain authority, then the first terminal device starts or restarts drx-InactivityTimerPC5, determines that the side chain DRX activation time includes the running time of drx-InactivityTimerPC5, and the end time of the side chain DRX activation time is later than the timeout time of drx-InactivityTimerPC5;

[0256] Or, if Figure 5hAs shown, if the first terminal device does not use the resources on the first side chain authority to send PSCCH, PSSCH or SCI to the second terminal device during the operation of drx-onDurationTimerPC5, the end time of the side chain DRX activation time is determined to be the timeout time of drx-onDurationTimerPC5. Optionally, in an embodiment of the present application, when the first terminal device triggers the sending of the fifth indication information to the network device, it may also trigger the sending of the device identification information of the second terminal device corresponding to the determined discarded side chain permission to the network device, that is, the device identification information of the second terminal device whose side chain DRX activation time has ended, wherein the device identification information may be a destination ID, such as sl-destinationIdentity, used to identify a destination of a side link communication, sl-destinationIdentity may be a destination layer-2ID, or the device identification information may be a destination index, such as destination Index, used to indicate the destination corresponding to any IE or entry in the destination information list or the resource request list sent by the first terminal device to the network device, the destination index corresponds to the order of the information element IE or entry corresponding to a destination in the list, such as destination index = 0 corresponds to the destination corresponding to the first IE or entry in the list, and destination index = 1 corresponds to the destination corresponding to the second IE in the list. Optionally, in an embodiment of the present application, if the first terminal device uses or determines to use the resources indicated by another side chain permission to send PSCCH, PSSCH or SCI after the time domain position of the resource indicated by the discarded side chain permission and before the end time of the side chain DRX activation time or a time interval before the end time, the first terminal device can cancel the trigger to send the fifth indication information to the network device, that is, if the discarded side chain permission is followed by the last side chain permission for sending PSCCH, PSSCH or SCI to the second terminal device within the side chain DRX activation time, the first terminal device triggers the sending of the fifth indication information to the network device. The first terminal device can also cancel the trigger to send the device identification information of the second terminal device whose side chain DRX activation time ends to the network device.

[0257] It should be understood that, in the embodiment of the present application, the first terminal device cancels the triggering of sending the indication information to the network device, which can be understood as the first terminal device canceling the triggering of sending the indication information, or the first terminal device canceling the triggering of reporting the indication information, or the first terminal device canceling the reporting of the triggering of the indication information, and the embodiment of the present application does not make specific limitations on this. For example, the first terminal device cancels the triggering of sending the fifth indication information to the network device, which can be understood as the first terminal device canceling the triggering of sending the fifth indication information, or the first terminal device canceling the triggering of reporting the fifth indication information, or the first terminal device canceling the reporting of the triggering of the fifth indication information.

[0258] Optionally, in an embodiment of the present application, if before triggering the sending of the fifth indication information to the network device, the first terminal device uses the resources indicated by another sidelink permission to send PSCCH, PSSCH or SCI, or the first terminal device determines to use the resources indicated by another sidelink permission to send PSCCH, PSSCH or SCI, then the first terminal device can cancel the triggering of sending the fifth indication information to the network device. The first terminal device can also cancel the triggering of sending the device identification information of the second terminal device whose sidelink DRX activation time ends to the network device.

[0259] Optionally, in an embodiment of the present application, if the drx-onDurationTimerPC5 of the second terminal device is started or running before the fifth indication information is triggered to be sent to the network device, that is, the sidelink DRX activation time of the next cycle begins, then the first terminal device can cancel the trigger to send the fifth indication information to the network device. The first terminal device can also cancel the trigger to send the device identification information of the second terminal device that ends the sidelink DRX activation time to the network device.

[0260] For example, Figure 5iAs shown, if the first terminal device has no uplink resources when sending the fifth indication information to the network device, the first terminal device does not send the fifth indication information during the operation of the second drx-onDurationTimerPC5, and cancels the sending of the fifth indication information when drx-onDurationTimer PC5 is started or running. Optionally, in an embodiment of the present application, if the first terminal device uses the discarded side chain authority to send PSCCH, PSSCH or SCI to the second terminal, it will not cause the side chain DRX activation time to change, that is, the side chain DRX activation time determined by the network device is consistent with the side chain DRX activation time determined by the first terminal device, then the first terminal device does not trigger the sending of the fifth indication information to the network device. If the first terminal device uses the discarded side chain authority to send PSCCH, PSSCH or SCI to the second terminal, which will cause the side chain DRX activation time to change, that is, after discarding the side chain authority, the side chain DRX activation time determined by the network device is inconsistent with the side chain DRX activation time determined by the first terminal device, then the first terminal device sends the fifth indication information to the network device. For example, after the first terminal device sends PSCCH, PSSCH, SCI or MAC PDU to the second terminal device on the resource indicated by the first side chain authority before the discarded side chain authority, the end time of the first side chain DRX activation time is determined according to the PSCCH, PSSCH, SCI or MAC PDU transmission. If the first terminal device sends PSCCH, PSSCH, SCI or MAC PDU to the second terminal device on the resource indicated by the discarded side chain authority, the end time of the second side chain DRX activation time is determined according to the PSCCH, PSSCH, SCI or MAC PDU transmission. If the end time of the second side chain DRX activation time is equal to the end time of the first side chain DRX activation time, the first terminal device does not trigger the sending of the fifth indication information to the network device, and sends the device identification information of the second terminal device corresponding to the discarded side chain authority to the network device. If the end time of the second side chain DRX activation time is not equal to the end time of the first side chain DRX activation time, the first terminal device sends the fifth indication information to the network device.

[0261] For example, Figure 5jAs shown, if the time domain position of the resource indicated by the first side chain authority plus the time length of drx-InactivityTimerPC5 falls within the running period of drx-onDurationTimerPC5, then the end time of the side chain DRX activation time corresponding to the time domain position of the resource indicated by the first side chain authority is the timeout time of drx-onDurationTimerPC5, and the time domain position of the resource indicated by the discarded second side chain authority plus the time length of drx-InactivityTimerPC5 falls within the running period of drx-onDurationTimerPC5, then the end time of the side chain DRX activation time corresponding to the time domain position of the resource indicated by the discarded second side chain authority is the timeout time of drx-onDurationTimerPC5, then the first terminal device does not trigger sending the fifth indication information to the network device, and does not trigger sending the device identification information of the second terminal device corresponding to the second side chain authority determined to be discarded to the network device.

[0262] Optionally, in an embodiment of the present application, the fifth indication information may be included in a UCI, a MAC CE or an RRC message. It can be understood that the device identification information of the second terminal device corresponding to the side chain authority to be discarded may also be included in the UCI, the MAC CE or the RRC message. For example, a field in the MAC CE is used to indicate that the first terminal device determines to discard the side chain authority and the end of the DRX activation time of the side chain or the device identification information, or one or more bits in the MAC CE are used to indicate that the first terminal device determines to discard the side chain authority and the end of the DRX activation time of the side chain or the device identification information, or PUCCH or a physical uplink shared channel (PUSCH) or a physical random access channel (PRACH) is used to indicate that the first terminal device determines to discard the side chain authority and the end of the DRX activation time of the side chain or the device identification information, wherein the method for PRACH indication can be used by defining a PRACH resource, which is used to indicate that the first terminal device determines to discard the side chain authority and the end of the DRX activation time of the side chain or the device identification information.

[0263] (2) If the first terminal device discards or determines to discard a side chain permission sent by the network device, the first terminal device can trigger the sending of a sixth indication message to the network device, wherein the sixth indication message is used to indicate that the drx-InactivityTimerPC5 corresponding to the side chain permission has timed out or is about to time out. It is understandable that the sixth indication message can also indicate that the first terminal device has discarded or discarded the side chain permission.

[0264] Optionally, in an embodiment of the present application, the first terminal device may trigger sending the sixth indication information to the network device after determining to discard the side chain authority, or after discarding the side chain authority, or after the time domain position of the resource indicated by the side chain authority, or the end time of the time domain position of the first side link transmission indicated by the side chain authority, or the first time slot or symbol after the end of the time domain position of the first side link transmission contained in the side chain authority, or after determining to discard the side chain authority, or after discarding the side chain authority, or after an interval after the end of the time domain position of the first side link transmission contained in the side chain authority, or the drx-InactivityTimerPC5 timeout moment of the second terminal device, or the interval before the drx-InactivityTimerPC5 timeout moment.

[0265] Optionally, in an embodiment of the present application, the first terminal device can determine the running time or timeout moment of drx-InactivityTimerPC5 according to the time domain position of the sent PSCCH, PSSCH or SCI. For example, after the first terminal device sends PSCCH, PSSCH, SCI or MAC PDU to the second terminal device before the discarded side chain authority, the first terminal device starts or restarts drx-InactivityTimerPC5, and the running time or timeout moment of drx-InactivityTimerPC5 can be determined according to the duration of drx-InactivityTimerPC5.

[0266] Optionally, in an embodiment of the present application, when the first terminal device sends the sixth indication information to the network device, it may also send to the network device the device identification information of the second terminal device corresponding to the discarded side chain permission, that is, the device identification information of the second terminal device whose side chain DRX activation time ends, wherein the device identification information may be a destination ID, such as sl-destinationIdentity, used to identify a destination of a side link communication, sl-destinationIdentity may be a destination layer-2ID, or the device identification information may be a destination index, such as destination Index, used to indicate the destination corresponding to any IE or entry in the destination information list or the resource request list sent by the first terminal device to the network device, the destination index corresponds to the order of the information element IE or entry corresponding to a destination in the list, such as destination index = 0 corresponds to the destination corresponding to the first IE or entry in the list, and destination index = 1 corresponds to the destination corresponding to the second IE or entry in the list.

[0267] Optionally, in an embodiment of the present application, if the first terminal device uses or determines to use the resource indicated by another side chain permission to send PSCCH, PSSCH or SCI after the time domain position of the resource indicated by the discarded side chain permission and before the drx-InactivityTimerPC5 timeout moment or the moment of an interval before the timeout moment, the first terminal device cancels sending the sixth indication information to the network device, and sends the device identification information of the second terminal device indicating the end of the side chain DRX activation time to the network device. In other words, if the discarded side chain permission is followed by the last side chain permission for sending PSCCH, PSSCH or SCI to the second terminal device during the operation of drx-InactivityTimerPC5, the first terminal device sends the sixth indication information to the network device, or triggers sending the sixth indication information to the network device.

[0268] Optionally, in an embodiment of the present application, if the drx-onDurationTimerPC5 of the second terminal device is started or running before the sixth indication information is sent to the network device, that is, the side chain DRX activation time of the next cycle begins, the first terminal device cancels sending the sixth indication information to the network device, and sends the device identification information of the second terminal device corresponding to the discarded side chain authority to the network device.

[0269] Optionally, in an embodiment of the present application, if even if the first terminal device uses the discarded side chain authority to send PSCCH, PSSCH or SCI to the second terminal, it will not cause the side chain DRX activation time to change, that is, the side chain DRX activation time determined by the network device is consistent with the side chain DRX activation time determined by the first terminal device, then the first terminal device does not send the sixth indication information to the network device. For example, before the discarded side chain authority, after the first terminal device sends PSCCH, PSSCH, SCI or MAC PDU to the second terminal device on the resources indicated by the first side chain authority, the end time of the first side chain DRX activation time is determined according to the PSCCH, PSSCH, SCI or MAC PDU transmission. If the first terminal device sends PSCCH, PSSCH, SCI or MAC PDU to the second terminal device on the resources indicated by the discarded side chain authority, the end time of the second side chain DRX activation time is determined according to the PSCCH, PSSCH, SCI or MAC PDU transmission. If the end time of the second side chain DRX activation time is equal to the end time of the first side chain DRX activation time, the first terminal device does not send the sixth indication information to the network device, and sends the device identification information of the second terminal device corresponding to the discarded side chain authority to the network device. For example, the time domain position of the resource indicated by the first side chain authority plus the time length of drx-InactivityTimerPC5 falls within the running period of drx-onDurationTimerPC5, then the end time of the side chain DRX activation time corresponding to the time domain position of the resource indicated by the first side chain authority is drx-onDurationTimerPC5. ationTimerPC5 timeout moment, the time domain position of the resource indicated by the discarded side chain permission plus the time length of drx-InactivityTimerPC5 falls within the running period of drx-onDurationTimerPC5, then the end moment of the side chain DRX activation time corresponding to the time domain position of the resource indicated by the discarded side chain permission is the timeout moment of drx-onDurationTimerPC5, then the first terminal device does not send the sixth indication information to the network device, and sends the device identification information of the second terminal device corresponding to the discarded side chain permission to the network device.

[0270] (3) Figure 5kAs shown, if the first terminal device discards or determines to discard a side chain permission sent by the network device, it triggers the sending of the seventh indication information to the network device, wherein the seventh indication information is used to indicate the end time of the side chain DRX activation time of the second terminal device. It can be understood that the seventh indication information can also indicate that the first terminal device has discarded or discarded the side chain permission. The side chain DRX activation time can be the side chain DRX activation time between the first terminal device and the second terminal device corresponding to the side chain permission, and can be determined by the first terminal device, the second terminal device corresponding to the side chain permission, or the first terminal device and the second terminal device corresponding to the side chain permission. Discarding the side chain permission will not cause the side chain DRX activation time to change or the drx-InactivityTimerPC5 to start or restart.

[0271] Optionally, in an embodiment of the present application, when the first terminal device triggers the sending of the seventh indication information to the network device, it may also trigger the sending of device identification information of the second terminal device corresponding to the discarded side chain authority to the network device, that is, the device identification information of the second terminal device whose side chain DRX activation time ends.

[0272] Optionally, in an embodiment of the present application, the first terminal device may trigger sending the seventh indication information to the network device after determining to discard the side link authority, or after discarding the side link authority, or after the time domain position of the resource indicated by the side link authority, or the end time of the time domain position of the first side link transmission indicated by the side link authority, or the first time slot or symbol after the end of the time domain position of the first side link transmission contained in the side link authority, or after determining to discard the side link authority, or after discarding the side link authority, or at an interval after the end of the time domain position of the first side link transmission contained in the side link authority, or at an interval before the end of the side link DRX activation time.

[0273] Optionally, in an embodiment of the present application, if the first terminal device determines to discard the side chain permission or after discarding the side chain permission, when the first terminal device triggers sending a BSR to the network device, it can simultaneously trigger sending the seventh indication information to the network device and determine the device identification information of the second terminal device corresponding to the discarded side chain permission.

[0274] Optionally, in an embodiment of the present application, if the first terminal device determines to discard the side chain permission or after discarding the side chain permission, when the first terminal device triggers sending a BSR to the network device, it can simultaneously trigger sending the seventh indication information to the network device and determine the device identification information of the second terminal device corresponding to the discarded side chain permission.

[0275] In an embodiment of the present application, the first terminal device can determine the side chain DRX activation time according to the time domain position of the sent PSCCH, PSSCH or SCI, or drx-onDurationTimerPC5. For example, after the first terminal device sends PSCCH, PSSCH, SCI or MAC PDU to the second terminal device before or after the discarded side chain authority, the first terminal device starts or restarts drx-InactivityTimerPC5, and the side chain DRX activation time includes the drx-InactivityTimerPC5 running time, and the end time of the side chain DRX activation time is later than or equal to the drx-InactivityTimerPC5 timeout time. If the first terminal device does not send PSCCH, PSSCH or SCI to the second terminal device during the running of drx-onDurationTimerPC5, the end time of the side chain DRX activation time is the timeout time of drx-onDurationTimerPC5. The side chain DRX activation time here is a continuous period of time.

[0276] Optionally, in an embodiment of the present application, if the first terminal device uses or determines to use the resources indicated by another side chain permission to send PSCCH, PSSCH or SCI after the time domain position of the resource indicated by the discarded side chain permission and before the end time of the side chain DRX activation time or a time interval before the end time, the first terminal device cancels sending the seventh indication information to the network device, and sends the device identification information of the second terminal device indicating the end of the side chain DRX activation time to the network device. In other words, if the discarded side chain permission is followed by the last side chain permission for sending PSCCH, PSSCH or SCI to the second terminal device within the side chain DRX activation time, the first terminal device sends the seventh indication information to the network device, or triggers sending the seventh indication information to the network device.

[0277] Optionally, if the first terminal device sends PSCCH, PSSCH or SCI using another resource indicated by a side chain permission after the time domain position of the resource indicated by the discarded side chain permission and before triggering the sending of the seventh indication information to the network device and determining the device identification information of the second terminal device corresponding to the discarded side chain permission, the first terminal device can cancel the triggering of sending the seventh indication information to the network device. The first terminal device can also cancel the triggering of sending the device identification information of the second terminal device corresponding to the discarded side chain permission to the network device.

[0278] Optionally, if before triggering the sending of the seventh indication information to the network device to determine the device identification information of the second terminal device corresponding to the discarded side chain authority, the first terminal device uses the resources indicated by another side chain authority to send PSCCH, PSSCH or SCI, or the first terminal device determines to use the resources indicated by another side chain authority to send PSCCH, PSSCH or SCI, then the first terminal device can cancel the triggering of sending the seventh indication information to the network device. The first terminal device can also cancel the triggering of sending the device identification information of the second terminal device corresponding to the discarded side chain authority to the network device.

[0279] Optionally, in an embodiment of the present application, if the drx-onDurationTimerPC5 of the second terminal device is started or running before the triggering of sending the seventh indication information to the network device, that is, the side chain DRX activation time of the next cycle begins, then the first terminal device can cancel the triggering of sending the seventh indication information to the network device. The first terminal device can also cancel the triggering of sending the device identification information of the second terminal device corresponding to the discarded side chain authority to the network device.

[0280] Optionally, in an embodiment of the present application, if even if the first terminal device uses the discarded side chain authority to send PSCCH, PSSCH or SCI to the second terminal, it will not cause the side chain DRX activation time to change, that is, the side chain DRX activation time determined by the network device is consistent with the side chain DRX activation time determined by the first terminal device, then the first terminal device does not send the seventh indication information to the network device. If the first terminal device uses the discarded side chain authority to send PSCCH, PSSCH or SCI to the second terminal, which will cause the side chain DRX activation time to change, that is, after the side chain authority is discarded, the side chain DRX activation time determined by the network device is inconsistent with the side chain DRX activation time determined by the first terminal device, then the first terminal device sends the seventh indication information to the network device. For example, after the first terminal device sends PSCCH, PSSCH, SCI or MAC PDU to the second terminal device on the resources indicated by the first side chain authority before the discarded side chain authority, the end time of the first side chain DRX activation time is determined according to the PSCCH, PSSCH, SCI or MAC PDU transmission. If the first terminal device sends PSCCH, PSSCH, SCI or MAC PDU to the second terminal device on the resource indicated by the discarded side chain authority, the end time of the second side chain DRX activation time is determined according to the PSCCH, PSSCH, SCI or MAC PDU transmission. If the end time of the second side chain DRX activation time is equal to the end time of the first side chain DRX activation time, the first terminal device does not trigger the sending of the seventh indication information to the network device, and does not trigger the sending of the device identification information of the second terminal device corresponding to the discarded side chain authority to the network device.

[0281] Optionally, in an embodiment of the present application, when the first terminal device indicates the end time of the sidelink DRX activation time to the network device, it may indicate the last time slot or symbol before the end time of the sidelink DRX activation time, or it may indicate the first time slot or symbol after the end time of the sidelink DRX activation time, wherein, when indicating the first time slot after the end time of the sidelink DRX activation time, it may indicate the SFN or DFN where the time slot is located and the index within the SFN or DFN where the time slot is located, or it may indicate the subframe where the time slot is located and the index of the time slot within the subframe, or it may indicate the index of the time slot, such as indicating the index of the time slot on the sidelink or the index of the time slot in the sidelink resource pool, and when indicating the first symbol after the end time of the sidelink DRX activation time, it may indicate the index of the symbol within the subframe or time slot and indicate the subframe or time slot. When indicating a subframe, the SFN or DFN where the subframe is located and the index within the SFN or DFN where the subframe is located may be indicated, or the index of the subframe may be indicated, such as the index of the subframe on the sidelink or the index of the subframe in the sidelink resource pool.

[0282] Optionally, in an embodiment of the present application, the seventh indication information may be included in a UCI, a MAC CE or an RRC message. It can be understood that the device identification information of the second terminal device corresponding to the side chain authority to be discarded may also be included in the UCI, the MAC CE or the RRC message. For example, a field in the MAC CE is used to indicate that the first terminal device determines to discard the side chain authority and the end time of the side chain DRX activation time or the device identification information, or one or more bits in the MAC CE are used to indicate that the first terminal device determines to discard the side chain authority and the end time of the side chain DRX activation time or the device identification information, or PUCCH or PUSCH or PRACH is used to indicate that the first terminal device determines to discard the side chain authority and the end time of the side chain DRX activation time or the device identification information, wherein, using the method for PRACH indication, a PRACH resource can be defined, and the PRACH resource is used to indicate that the first terminal device determines to discard the side chain authority and the end time of the side chain DRX activation time or the device identification information. (4) If the first terminal device discards or determines to discard a side chain permission sent by the network device, the first terminal device can trigger sending an eighth indication message to the network device, where the eighth indication message is used to indicate the timeout moment of drx-InactivityTimerPC5 corresponding to the side chain permission.

[0283] Optionally, in an embodiment of the present application, the eighth indication information may also indicate that the first terminal device has discarded or discarded the side chain authority.

[0284] Optionally, in an embodiment of the present application, when the first terminal device sends the eighth indication information to the network device, it may also send to the network device the device identification information of the second terminal device corresponding to the discarded side chain authority, that is, the device identification information of the second terminal device whose side chain DRX activation time ends.

[0285] Optionally, in an embodiment of the present application, the first terminal device may trigger sending the eighth indication information to the network device after determining to discard the side link authority, or after discarding the side link authority, or after the time domain position of the resource indicated by the side link authority, or the end time of the time domain position of the first side link transmission indicated by the side link authority, or the first time slot or symbol after the end of the time domain position of the first side link transmission contained in the side link authority, or after determining to discard the side link authority, or after discarding the side link authority, or at a time interval after the end of the time domain position of the first side link transmission contained in the side link authority, or at a time interval before the end of the side link DRX activation time.

[0286] Optionally, in an embodiment of the present application, if the first terminal device determines to discard the side chain permission or after discarding the side chain permission, when the first terminal device sends a BSR to the network device, it can simultaneously send an eighth indication information and the device identification information of the second terminal device corresponding to the discarded side chain permission to the network device.

[0287] Optionally, in an embodiment of the present application, the first terminal device may determine the timeout moment of drx-InactivityTimerPC5 according to the time domain position of the sent PSCCH, PSSCH or SCI. For example, after the first terminal device sends PSCCH, PSSCH, SCI or MAC PDU to the second terminal device before or after the discarded side chain permission, the first terminal device starts or restarts drx-InactivityTimerPC5, and it times out after running for the duration of drx-InactityTimerPC5.

[0288] Optionally, in an embodiment of the present application, if the first terminal device uses or determines to use the resource indicated by another side chain permission to send PSCCH, PSSCH or SCI after the time domain position of the resource indicated by the discarded side chain permission and before the timeout moment of drx-InactivityTimerPC5 or the time interval before the timeout moment, the first terminal device cancels sending the eighth indication information to the network device. In other words, if the discarded side chain permission is followed by the last side chain permission used to send PSCCH, PSSCH or SCI to the second terminal device during the operation of drx-InactivityTimerPC5, the first terminal device sends the eighth indication information to the network device, or triggers sending the eighth indication information to the network device.

[0289] Optionally, if the first terminal device sends PSCCH, PSSCH or SCI using another resource indicated by a side chain permission after the time domain position of the resource indicated by the discarded side chain permission and before sending the eighth indication information to the network device and determining the device identification information of the second terminal device corresponding to the discarded side chain permission, the first terminal device cancels sending the eighth indication information to the network device and cancels determining the device identification information of the second terminal device corresponding to the discarded side chain permission.

[0290] Optionally, if before sending the eighth indication information to the network device to determine the device identification information of the second terminal device corresponding to the discarded side chain authority, the first terminal device uses the resources indicated by another side chain authority to send PSCCH, PSSCH or SCI, or the first terminal device determines to use the resources indicated by another side chain authority to send PSCCH, PSSCH or SCI, the first terminal device cancels sending the eighth indication information to the network device, and determines the device identification information of the second terminal device corresponding to the discarded side chain authority.

[0291] Optionally, in an embodiment of the present application, if the drx-onDurationTimerPC5 of the second terminal device is started or running before the eighth indication information is sent to the network device, that is, the side chain DRX activation time of the next cycle begins, the first terminal device cancels sending the eighth indication information to the network device, and determines the device identification information of the second terminal device corresponding to the discarded side chain authority.

[0292] Optionally, in an embodiment of the present application, if even if the first terminal device uses the discarded side chain authority to send PSCCH, PSSCH or SCI to the second terminal, it will not cause the side chain DRX activation time to change, that is, the side chain DRX activation time determined by the network device is consistent with the side chain DRX activation time determined by the first terminal device, then the first terminal device does not send the eighth indication information to the network device. If the first terminal device uses the discarded side chain authority to send PSCCH, PSSCH or SCI to the second terminal, which will cause the side chain DRX activation time to change, that is, after the side chain authority is discarded, the side chain DRX activation time determined by the network device is inconsistent with the side chain DRX activation time determined by the first terminal device, then the first terminal device sends the eighth indication information to the network device. For example, before the discarded side chain authority, after the first terminal device sends PSCCH, PSSCH, SCI or MAC PDU to the second terminal device on the resources indicated by the first side chain authority, the end time of the first side chain DRX activation time is determined according to the PSCCH, PSSCH, SCI or MAC PDU transmission. If the first terminal device sends PSCCH, PSSCH, SCI or MAC PDU to the second terminal device on the resource indicated by the discarded side chain authority, the end time of the second side chain DRX activation time is determined according to the PSCCH, PSSCH, SCI or MAC PDU transmission. If the end time of the second side chain DRX activation time is equal to the end time of the first side chain DRX activation time, the first terminal device does not send the eighth indication information to the network device, and determines the device identification information of the second terminal device corresponding to the discarded side chain authority. If the end time of the second side chain DRX activation time is not equal to the end time of the first side chain DRX activation time, the first terminal device sends the eighth indication information to the network device.

[0293] Optionally, in an embodiment of the present application, when the first terminal device indicates the timeout moment of drx-InactivityTimerPC5 to the network device, it may indicate the last time slot or symbol before the timeout moment of drx-InactivityTimerPC5, or, it may indicate the first time slot or symbol after the timeout moment of drx-InactivityTimerPC5, wherein, when indicating the first time slot after the timeout moment of drx-InactivityTimerPC5, it may indicate the SFN or DFN in which the time slot is located and the index within the SFN or DFN in which the time slot is located, or, it may indicate the subframe in which the time slot is located and the index of the time slot within the subframe, or, it may indicate the index of the time slot, such as indicating the index of the time slot on the sidelink or the index of the time slot in the sidelink resource pool, and when indicating the first symbol after the timeout moment of drx-InactivityTimerPC5, it may indicate the index of the symbol within the subframe or time slot and indicate the subframe or time slot. When indicating a subframe, the SFN or DFN where the subframe is located and the index within the SFN or DFN where the subframe is located may be indicated, or the index of the subframe may be indicated, such as the index of the subframe on the sidelink or the index of the subframe in the sidelink resource pool.

[0294] Optionally, in an embodiment of the present application, the eighth indication information may be included in a UCI, a MAC CE or an RRC message. It can be understood that the device identification information of the second terminal device corresponding to the side chain authority to be discarded may also be included in the UCI, the MAC CE or the RRC message. For example, a field in the MAC CE is used to indicate that the first terminal device determines to discard the side chain authority and the timeout moment of drx-InactivityTimerPC5 or the device identification information, or one or more bits in the MAC CE are used to indicate that the first terminal device determines to discard the side chain authority and the timeout moment of drx-InactivityTimerPC5 or the device identification information, or PUCCH or PUSCH or PRACH is used to indicate that the first terminal device determines to discard the side chain authority and the timeout moment of drx-InactivityTimerPC5 and / or the device identification information, wherein the method for PRACH indication can be used by defining a PRACH resource, which is used to indicate that the first terminal device determines to discard the side chain authority and the timeout moment of drx-InactivityTimerPC5 or the device identification information.

[0295] (5) If the first terminal device discards or determines to discard a side chain permission sent by the network device, ninth indication information is sent to the network device, wherein the ninth indication information is used to indicate the time domain location of the resource indicated by the side chain permission. It can be understood that the ninth indication information can also indicate that the first terminal device discards or determines to discard the side chain permission.

[0296] Optionally, in an embodiment of the present application, when the first terminal device indicates the time domain position of the resource indicated by the sidelink permission to the network device, it may indicate the time slot where the resource of the first sidelink transmission contained in the sidelink permission is located, wherein the SFN or DFN where the time slot is located and the index within the SFN or DFN where the time slot is located may be indicated, or the subframe where the time slot is located and the index of the time slot within the subframe may be indicated, or the index of the time slot may be indicated, such as indicating the index of the time slot on the sidelink or the index of the time slot in the sidelink resource pool and indicating the subframe or time slot. When indicating a subframe, the SFN or DFN where the subframe is located and the index within the SFN or DFN where the subframe is located may be indicated, or the index of the subframe may be indicated, such as indicating the index of the subframe on the sidelink or the index of the subframe in the sidelink resource pool.

[0297] Optionally, in an embodiment of the present application, when the first terminal device sends the ninth indication information to the network device, it may also send to the network device device identification information of the second terminal device corresponding to the discarded side chain authority.

[0298] Optionally, in an embodiment of the present application, when the first terminal device sends the ninth indication information to the network device, the first terminal device may also send the frequency domain position of the discarded side link authority to the network device, such as the lowest subchannel index or the lowest physical resource block (PRB) index of the resource of the first side link transmission included in the side link authority.

[0299] Optionally, in an embodiment of the present application, when the first terminal device sends the ninth indication information to the network device, the first terminal device may also send configuration index information of the discarded side chain permissions to the network device.

[0300] Optionally, in an embodiment of the present application, if there is only one side chain authority in the time domain position of the discarded side chain authority, when the first terminal device sends the ninth indication information to the network device, the first terminal device does not send the frequency domain position or configuration index information of the discarded side chain authority to the network device.

[0301] Optionally, in an embodiment of the present application, the first terminal device may determine the sidechain DRX activation time based on the time domain position of the sent PSCCH, PSSCH or SCI, or drx-onDurationTimerPC5. For example, after the first terminal device sends PSCCH, PSSCH, SCI or MAC PDU to the second terminal device before or after the discarded sidechain authority, the first terminal device starts or restarts drx-InactivityTimerPC5, and the sidechain DRX activation time includes the drx-InactivityTimerPC5 running time, and the end time of the sidechain DRX activation time is later than or equal to the drx-InactivityTimerPC5 timeout time. If the first terminal device does not send PSCCH, PSSCH or SCI to the second terminal device during the running of drx-onDurationTimerPC5, the end time of the sidechain DRX activation time is the timeout time of drx-onDurationTimerPC5. The sidechain DRX activation time here is a continuous period of time.

[0302] Optionally, in an embodiment of the present application, the first terminal device may trigger sending the ninth indication information to the network device after determining to discard the side link authority, or after discarding the side link authority, or after the time domain position of the resource indicated by the side link authority, or the end time of the time domain position of the first side link transmission contained in the side link authority, or the first time slot or symbol after the end of the time domain position of the first side link transmission contained in the side link authority, or after determining to discard the side link authority, or after discarding the side link authority, or at an interval after the end of the time domain position of the first side link transmission contained in the side link authority, or the end time of the side link DRX activation time, or at an interval before the end of the side link DRX activation time.

[0303] Optionally, in an embodiment of the present application, if the first terminal device determines to discard the side chain permission or after discarding the side chain permission, when the first terminal device triggers sending a cache status report BSR to the network device, it can simultaneously trigger sending the ninth indication information to the network device and determine the device identification information of the second terminal device corresponding to the discarded side chain permission.

[0304] Optionally, in an embodiment of the present application, if the first terminal device determines to discard the side chain permission or after discarding the side chain permission, when the first terminal device triggers sending a BSR to the network device, it can simultaneously trigger sending the ninth indication information to the network device and determine the device identification information of the second terminal device corresponding to the discarded side chain permission.

[0305] Optionally, if the first terminal device uses another resource indicated by a side chain permission to send PSCCH, PSSCH or SCI after determining the time domain position of the resource indicated by the discarded side chain permission and before triggering the sending of the ninth indication information to the network device and determining the device identification information of the second terminal device corresponding to the discarded side chain permission, the first terminal device cancels the triggering of sending the ninth indication information to the network device, and cancels the triggering of determining the device identification information of the second terminal device corresponding to the discarded side chain permission.

[0306] Optionally, if before triggering the sending of the ninth indication information to the network device to determine the device identification information of the second terminal device corresponding to the discarded side chain authority, the first terminal device uses the resources indicated by another side chain authority to send PSCCH, PSSCH or SCI, or the first terminal device determines to use the resources indicated by another side chain authority to send PSCCH, PSSCH or SCI, the first terminal device cancels sending the ninth indication information to the network device, and determines the device identification information of the second terminal device corresponding to the discarded side chain authority.

[0307] Optionally, in an embodiment of the present application, if before the ninth indication information is sent to the network device, the next cycle of the second terminal device's drx-onDurationTimerPC5 is started or running, that is, the side chain DRX activation time begins, the first terminal device cancels sending the ninth indication information to the network device, and determines the device identification information of the second terminal device corresponding to the discarded side chain authority.

[0308] Optionally, in an embodiment of the present application, if even if the first terminal device uses the discarded side chain authority to send PSCCH, PSSCH or SCI to the second terminal, it will not cause the side chain DRX activation time to change, that is, the side chain DRX activation time determined by the network device is consistent with the side chain DRX activation time determined by the first terminal device, then the first terminal device does not send the ninth indication information to the network device. If the first terminal device uses the discarded side chain authority to send PSCCH, PSSCH or SCI to the second terminal, which will cause the side chain DRX activation time to change, that is, after the side chain authority is discarded, the side chain DRX activation time determined by the network device is inconsistent with the side chain DRX activation time determined by the first terminal device, then the first terminal device sends the ninth indication information to the network device. For example, after the first terminal device sends PSCCH, PSSCH, SCI or MAC PDU to the second terminal device on the resources indicated by the first side chain authority before the discarded side chain authority, the end time of the first side chain DRX activation time is determined according to the PSCCH, PSSCH, SCI or MAC PDU transmission. If the first terminal device sends PSCCH, PSSCH, SCI or MAC PDU to the second terminal device on the resource indicated by the discarded side chain authority, the end time of the second side chain DRX activation time is determined according to the PSCCH, PSSCH, SCI or MAC PDU transmission. If the end time of the second side chain DRX activation time is equal to the end time of the first side chain DRX activation time, the first terminal device does not trigger the sending of the ninth indication information to the network device, and determines the device identification information of the second terminal device corresponding to the discarded side chain authority.

[0309] Optionally, in an embodiment of the present application, the ninth indication information and the device identification information of the second terminal device corresponding to the side chain authority to be discarded may be included in a UCI, a MAC CE or an RRC message, for example, a field in the MAC CE is used to indicate that the first terminal device determines to discard the side chain authority and the time domain position of the resource indicated by the side chain authority and / or the device identification information, or one or more bits in the MAC CE are used to indicate that the first terminal device determines to discard the side chain authority and the time domain position of the resource indicated by the side chain authority and / or the device identification information, or PUCCH or PUSCH or PRACH is used to indicate that the first terminal device determines to discard the side chain authority and the time domain position of the resource indicated by the side chain authority and / or the device identification information, wherein, using a method for PRACH indication, a PRACH resource can be defined, and the PRACH resource is used to indicate that the first terminal device determines to discard the side chain authority and the time domain position of the resource indicated by the side chain authority and / or the device identification information.

[0310] (6) If the first terminal device determines to discard a side link permission sent by the network device, the first terminal device may trigger sending a tenth indication message to the network device, wherein the tenth indication message is used to indicate the time slot where the DCI or PDCCH that schedules the side link permission is located, for example, it may indicate the SFN or DFN where the time slot is located and the index within the SFN or DFN where the time slot is located, or indicate the subframe where the time slot is located and the index of the time slot within the subframe, or indicate the index of the time slot, such as indicating the index of the time slot on the side link or the index of the time slot in the side link resource pool.

[0311] Optionally, in an embodiment of the present application, when the first terminal device sends the tenth indication information to the triggering network device, the first terminal device may also trigger the sending of device identification information of the second terminal device corresponding to the side chain authority determined to be discarded to the network device.

[0312] Optionally, in an embodiment of the present application, when the first terminal device triggers sending the tenth indication information to the network device, the first terminal device may also trigger sending the frequency domain position of the DCI or PDCCH that schedules the side link authority to the network device, such as the lowest subchannel index or the lowest PRB index of the resource for the first side link transmission included in the side link authority.

[0313] Optionally, in an embodiment of the present application, when the first terminal device triggers sending the tenth indication information to the network device, the first terminal device may also trigger sending a control channel element (CCE) index of the DCI or PDCCH that schedules the side chain authority to the network device.

[0314] Optionally, in an embodiment of the present application, when the first terminal device triggers sending the tenth indication information to the network device, the first terminal device may also trigger sending a "Timegap" domain of the DCI or PDCCH that schedules the side chain authority to the network device.

[0315] Optionally, in an embodiment of the present application, the first terminal device may determine the sidechain DRX activation time based on the time domain position of the sent PSCCH, PSSCH or SCI, or drx-onDurationTimerPC5. For example, after the first terminal device sends PSCCH, PSSCH, SCI or MAC PDU to the second terminal device before or after the discarded sidechain authority, the first terminal device starts or restarts drx-InactivityTimerPC5, and the sidechain DRX activation time includes the drx-InactivityTimerPC5 running time, and the end time of the sidechain DRX activation time is later than or equal to the drx-InactivityTimerPC5 timeout time. If the first terminal device does not send PSCCH, PSSCH or SCI to the second terminal device during the running of drx-onDurationTimerPC5, the end time of the sidechain DRX activation time is the timeout time of drx-onDurationTimerPC5. The sidechain DRX activation time here is a continuous period of time.

[0316] Optionally, in an embodiment of the present application, the network device may determine the side chain authority discarded by the first terminal device based on the DCI or PDCCH of the scheduled discarded side chain authority, and further determine the side chain DRX activation time.

[0317] (7) If the first terminal device discards or determines to discard a side chain permission sent by the network device, an eleventh indication information is sent to the network device, wherein the eleventh indication information is used to indicate the time domain position of the previous side chain permission of the discarded side chain permission. It can be understood that the eleventh indication information can also indicate that the first terminal device discards or discards the side chain permission.

[0318] Optionally, in an embodiment of the present application, the network device may obtain the end time of the side chain DRX activation time of the second terminal device corresponding to the side chain authority to be discarded based on the previous side chain authority to be discarded, such as the end time of the side chain DRX activation time is the time domain position of the resource indicated by the previous side chain authority plus the time length of drx-InactivityTimerPC5, or the end time of the side chain DRX activation time is the end time of the side chain DRX activation time of the second terminal device corresponding to the previous side chain authority.

[0319] (8) If the first terminal device determines to discard a side chain authority sent by the network device, it sends twelfth indication information to the network device, wherein the twelfth indication information is used to indicate the time domain position of the DCI or PDCCH of the previous side chain authority that schedules the side chain authority.

[0320] Optionally, in an embodiment of the present application, the network device may determine the previous side chain authority determined to be discarded by the first terminal device based on the DCI or PDCCH of the previous side chain authority determined to be discarded by the scheduling, and the network device may obtain the end time of the side chain DRX activation time of the second terminal device corresponding to the discarded side chain authority based on the previous side chain authority determined to be discarded, such as the end time of the side chain DRX activation time is the time domain position of the resource indicated by the previous side chain authority plus the time length of drx-InactivityTimerPC5, or the end time of the side chain DRX activation time is the end time of the side chain DRX activation time of the second terminal device corresponding to the previous side chain authority.

[0321] In order to solve the second problem mentioned above, that is, how to avoid the situation where, if the SCI indicates N resources, the time domain position of resources other than the first resource may not be within the side link DRX activation time of the terminal device at the receiving end, thereby causing the terminal device to be unable to monitor the transmission on the N resources, and resources other than the first resource are wasted, the embodiment of the present application provides a solution of the following embodiment 4, which can be implemented in combination with the above-mentioned embodiment 1 or embodiment 2 or embodiment 3, and is described in detail below.

[0322] Example 4

[0323] In some embodiments, the sidelink DRX activation time of the terminal device may include the time domain location of one or more resources indicated by the SCI, and each of the one or more resources may be a resource for SCI transmission, or each of the one or more resources may be a resource for PSCCH and PSSCH transmission, or each of the one or more resources may be a resource for PSCCH transmission.

[0324] Optionally, if the terminal device receives PSCCH, PSSCH, SCI or MAC PDU, and the data decoding of the corresponding sidelink process fails, the sidelink DRX activation time may include the time domain location of one or more resources indicated by SCI (corresponding to PSCCH, PSSCH or MAC PDU).

[0325] Optionally, when the SCI indicates more than one resource, the terminal device does not start the drx-HARQ-RTT-TimerPC5 of the corresponding side chain process. That is to say, when the SCI only indicates one resource, the terminal device starts the drx-HARQ-RTT-TimerPC5 of the corresponding side chain process. The specific start time is as described in Example 1, Example 2 or Example 3.

[0326] Optionally, when the SCI indicates more than one resource, the terminal device does not start the drx-RetransmissionTimerPC5 of the corresponding side chain process. That is to say, when the SCI only indicates one resource, the terminal device starts the drx-RetransmissionTimerPC5 of the corresponding side chain process. The specific start time is as described in Example 1, Example 2 or Example 3.

[0327] In other embodiments, the terminal device needs to monitor PSCCH, PSSCH or SCI at the time domain location where one or more resources indicated by SCI are located. That is, even if the time domain location where one or more resources indicated by SCI are located is not within the side link DRX activation time, the terminal device needs to monitor PSCCH, PSSCH or SCI at the time domain location where one or more resources indicated by SCI are located.

[0328] Optionally, if the terminal device receives PSCCH, PSSCH, SCI or MAC PDU, and the data decoding of the corresponding side link process fails, the terminal device needs to listen to PSCCH, PSSCH or SCI at the time domain location of one or more resources indicated by SCI (corresponding to PSCCH, PSSCH or MAC PDU).

[0329] Optionally, when the SCI indicates more than one resource, the terminal device does not start the drx-HARQ-RTT-TimerPC5 of the corresponding side link process. That is, when the SCI indicates only one resource, the terminal device starts the drx-HARQ-RTT-TimerPC5 of the corresponding side link process. The specific start time is as described in Example 1, Example 2 or Example 3.

[0330] Optionally, when the SCI indicates more than one resource, the terminal device does not start the drx-RetransmissionTimerPC5 of the corresponding side chain process. That is to say, when the SCI indicates only one resource, the terminal device starts the drx-RetransmissionTimerPC5 of the corresponding side chain process. The specific start time is as described in Example 1, Example 2 or Example 3.

[0331] In other embodiments, if the terminal device receives PSCCH, PSSCH, SCI or MAC PDU, if the SCI (corresponding to the PSCCH, PSSCH or MAC PDU) indicates more than one resource, the duration of the drx-HARQ-RTT-TimerPC5 of the corresponding side link process is the first duration, which is determined according to the time domain position of the resource indicated by the SCI, or the first duration is determined according to the offset of the resource indicated by the SCI relative to the time domain position of the SCI.

[0332] If the SCI (corresponding to PSCCH, PSSCH or MAC PDU) indicates only one resource, the duration of the drx-HARQ-RTT-TimerPC5 of the corresponding side chain process is the second duration, which can be determined by the terminal device of the transmitting end, or the terminal device of the receiving end, or the network device.

[0333] When the duration of drx-HARQ-RTT-TimerPC5 is the first duration, the first symbol, time slot or subframe after drx-HARQ-RTT-TimerPC5 times out is the time domain position of the second resource indicated by SCI, or the beginning of the time domain position of the second resource, or the time domain position of the third resource, or the beginning of the time domain position of the third resource.

[0334] If the SCI (corresponding to PSCCH, PSSCH or MAC PDU) indicates more than one resource, the duration of the drx-RetransmissionTimerPC5 of the corresponding sidelink process is 1 time slot, or the duration of drx-RetransmissionTimerPC5 is the time length of one resource indicated by the SCI.

[0335] If the SCI (corresponding to PSCCH, PSSCH or MAC PDU) indicates only one resource, the duration of the drx-RetransmissionTimerPC of the corresponding side chain process is the third duration, which can be determined by the terminal device of the transmitting end, or the terminal device of the receiving end, or the network device.

[0336] If the terminal device receives PSCCH, PSSCH, SCI or MAC PDU in the time domain position t0 time slot of the first resource indicated by SCI, if the SCI (corresponding to PSCCH, PSSCH or MAC PDU) indicates more than one resource, the drx-HARQ-RTT-TimerPC5 of the corresponding side chain process is started in the (t0+n1) time slot, and the drx-RetransmissionTimerPC5 of the corresponding side chain process is stopped. The duration of drx-HARQ-RTT-TimerPC5 is the first duration, which is equal to the time domain position (t0+t1) time slot of the second resource indicated by SCI minus the (t0+n1) time slot, and the (t0+n1) time slot is the time slot where the first resource is located. If the SCI received in the t0 time slot indicates more than two resources, and the terminal device does not receive PSCCH, PSSCH, SCI or MAC PDU in the time domain position of the second resource, the drx-HARQ-RTT-TimerPC5 of the corresponding side chain process is started in the (t0+n2) time slot, and the drx-RetransmissionTimerPC5 of the corresponding side chain process is stopped. The duration of drx-HARQ-RTT-TimerPC5 is the fourth duration, and the fourth duration is equal to the time domain position of the third resource indicated by the SCI (t0+t2) time slot minus the (t0+n2) time slot.

[0337] In other embodiments, if the terminal device receives PSCCH, PSSCH, SCI or MAC PDU, if the SCI (corresponding to the PSCCH, PSSCH or MAC PDU) indicates more than one resource, the drx-RetransmissionTimerPC5 of the corresponding sidelink process is started or restarted at the time domain location (time slot) where one or more resources indicated by the SCI are located. The duration of drx-RetransmissionTimerPC5 is 1 time slot, or the duration of drx-RetransmissionTimerPC5 is the time length of one resource indicated by the SCI.

[0338] Optionally, if the terminal device receives PSCCH, PSSCH, SCI or MAC PDU, the SCI (corresponding to PSCCH, PSSCH or MAC PDU) indicates more than one resource, and the data of the corresponding side chain process is not decoded successfully, drx-RetransmissionTimerPC5 starts or restarts at the time domain location (time slot) where one or more resources indicated by SCI are located.

[0339] If the terminal device receives PSCCH, PSSCH, SCI or MAC PDU, if the SCI (corresponding to the PSCCH, PSSCH or MAC PDU) indicates more than one resource, stop the drx-RetransmissionTimerPC5 of the corresponding side link process at the first symbol or time slot or subframe or mini-slot after the transmission of the side link HARQ feedback is completed, or stop the drx-RetransmissionTimerPC5 of the corresponding side link process at the first symbol or time slot or subframe or mini-slot after the transmission of the PSCCH, PSSCH, SCI or MAC PDU is completed.

[0340] In other embodiments, if the terminal device receives PSCCH, PSSCH, SCI or MAC PDU, if the SCI (corresponding to the PSCCH, PSSCH or MAC PDU) indicates more than one resource, and the terminal device has not received the SCI at the time domain position (time slot) of the second resource or the third resource indicated by the SCI, the terminal device still starts the drx-HARQ-RTT-TimerPC5 or drx-RetransmissionTimerPC5 of the corresponding side link process. The specific start time is as described in Example 1, Example 2 or Example 3, that is, the same as the terminal device receiving the SCI at the time domain position (time slot) of the second resource or the third resource indicated by the SCI.

[0341] It should be noted that in the embodiment of the present application, the terminal device may use the method in Embodiment 4 when determining whether the timer is started according to whether the SCI indicates more than one resource. For example, if one or more resources indicated by the SCI will not be preempted by other terminal devices, the terminal device adopts the method in Embodiment 4. In the case where whether the SCI indicates more than one resource is irrelevant to whether the timer is started, the method in Embodiment 1, Embodiment 2, or Embodiment 3 is used. For example, if one or more resources indicated by the SCI may be preempted by other terminal devices, the terminal device adopts the method in Embodiment 1, Embodiment 2, or Embodiment 3.

[0342] Exemplarily, the one or more resources indicated by the SCI will not be preempted by other terminal devices, which may include one or more of the following situations:

[0343] 1) Preemption is disabled;

[0344] 2) The priority indicated by the SCI is the minimum or maximum value of the priority value range;

[0345] 3) Pre-emption is enabled, and the priority indicated by the SCI is the minimum or maximum value of the priority range;

[0346] 4) The preemption threshold is the minimum or maximum value of the priority value range;

[0347] 5) Preemption is not enabled, and the preemption threshold is the minimum or maximum value of the priority range;

[0348] 6) The terminal device sending the SCI uses the resource allocation mode scheduled by the base station.

[0349] Optionally, when a priority with a smaller value is transmitted first, the priority indicated by SCI is the minimum value of the priority value range, and the preemption threshold is the minimum value of the priority value range; when a priority with a larger value is transmitted first, the priority indicated by SCI is the maximum value of the priority value range, and the preemption threshold is the maximum value of the priority value range.

[0350] Exemplarily, one or more resources indicated by the SCI may be preempted by other terminal devices, including one or more of the following situations:

[0351] 1) The priority indicated by the SCI is greater than the minimum value of the priority range;

[0352] 2) Pre-emption is enabled and the priority indicated by the SCI is greater than the minimum value of the priority range;

[0353] 3) The preemption threshold is greater than the minimum value of the priority range;

[0354] 4) Preemption is not enabled, and the preemption threshold is greater than the minimum value of the priority range;

[0355] 5) Preemption is enabled;

[0356] 6) The preemption threshold is greater than the minimum value of the priority value range, and the priority indicated by the SCI is greater than the minimum value of the priority value range;

[0357] 7) Preemption is not enabled, and the preemption threshold is greater than the minimum value of the priority value range, and the priority indicated by the SCI is greater than the minimum value of the priority value range, wherein the priority with a smaller value is transmitted first;

[0358] 8) The terminal device sending the SCI uses the resource allocation mode of autonomous resource selection.

[0359] Alternatively, the one or more resources indicated by the SCI may be preempted by other terminal devices and may also include one or more of the following situations:

[0360] 1) The priority indicated by the SCI is less than the maximum value of the priority value range;

[0361] 2) Pre-emption is enabled and the priority indicated by the SCI is less than the maximum value of the priority range;

[0362] 3) The preemption threshold is less than the maximum value of the priority value range;

[0363] 4) Preemption is not enabled, and the preemption threshold is less than the maximum value of the priority value range;

[0364] 5) Preemption is enabled;

[0365] 6) The preemption threshold is less than the maximum value of the priority value range, and the priority indicated by the SCI is less than the maximum value of the priority value range;

[0366] 7) Preemption is not enabled, and the preemption threshold is less than the maximum value of the priority value range, and the priority indicated by the SCI is less than the maximum value of the priority value range, wherein the priority with a larger value is transmitted first;

[0367] 8) The terminal device sending the SCI uses the resource allocation mode of autonomous resource selection.

[0368] Combination of the above Figure 4 to Figure 5b The method provided in the embodiment of the present application is described in detail. Figure 6 to Figure 8 The device provided in the embodiments of the present application is described in detail.

[0369] Based on the same technical concept, the embodiment of the present application further provides a DRX device 600, which may be a first terminal device, or a device 600 in the first terminal device, and the device 600 includes a method for performing the above Figure 4 Modules of the method shown. For example, see Figure 6 , the apparatus 600 may include:

[0370] The first sending module 601 is used to send a sidelink discontinuous reception DRX parameter or indication information of a second terminal device to a network device, so that the network device determines a first time period based on the sidelink DRX parameter or the indication information; wherein the indication information is used to indicate the start and / or end of the first time period, the first time period belongs to the sidelink DRX activation time of the second terminal device, and the second terminal device is a device that performs sidelink communication with the first terminal device;

[0371] A receiving module 602 is used to receive a side chain permission sent by the network device; wherein the side chain permission is used to indicate that the first terminal device sends resources of a physical side chain control channel PSCCH and / or a physical side chain shared channel PSSCH, and the time domain position of the resources overlaps with the first time period;

[0372] The second sending module 603 is used to send PSCCH and / or PSSCH based on the side chain authority.

[0373] In one possible design, the indication information is included in the uplink control information UCI, the media access control control unit MAC CE or the radio resource control RRC message; the side chain permission is included in the downlink control information DCI, MAC CE or the RRC message.

[0374] In a possible design, the first sending module 601 is specifically used to send the indication information to the network device:

[0375] Sending first indication information to the network device at the start time of the first time period; wherein the first indication information is used to indicate the end time of the first time period; or,

[0376] Sending second indication information to the network device at the beginning of the first time period, and sending third indication information to the network device at the end of the first time period; wherein the second indication information is used to indicate the beginning of the first time period, and the third indication information is used to indicate the end of the first time period.

[0377] In a possible design, the first time period belongs to the sidelink DRX activation time of the second terminal device, including:

[0378] The first period includes the sidelink DRX activation time of each of the second terminal devices; or,

[0379] The first time period includes the intersection or union of the sidelink DRX activation times of at least two of the second terminal devices.

[0380] In one possible design, the first time period includes an intersection or union of sidelink DRX activation times of at least two second terminal devices, including:

[0381] The first period includes any one or more of the following combinations:

[0382] The earliest starting time to the earliest ending time of the sidelink DRX activation time of each second terminal device;

[0383] The earliest starting time to the latest ending time of the sidelink DRX activation time of each second terminal device;

[0384] The latest start time and the earliest end time of the sidelink DRX activation time of each second terminal device;

[0385] The latest start time and the latest end time of the sidelink DRX activation time of each second terminal device;

[0386] The time when the side chain DRX activation time of any of the second terminal devices starts or ends to the time when the side chain DRX activation time of any of the second terminal devices starts or ends.

[0387] In a possible design, if the first time period includes the sidelink DRX activation time of each of the second terminal devices, the receiving module 602 is specifically used to:

[0388] Receive the side chain authority and device identification information sent by the network device, and determine the second terminal device corresponding to the side chain authority based on the device identification information.

[0389] In one possible design, the sidelink DRX activation time includes the running time of a DRX duration timer and a DRX deactivation timer, and the DRX deactivation timer is started or restarted when the first terminal device sends a PSCCH and / or a PSSCH; or,

[0390] The DRX deactivation timer is started or restarted when the first terminal device receives the HARQ feedback information of the second terminal device based on the PSCCH and / or PSSCH; or,

[0391] The DRX deactivation timer is started or restarted when the first terminal device sends fourth indication information to the network device and the second terminal device; wherein the fourth indication information is used to indicate that the DRX deactivation timer is started or restarted.

[0392] In one possible design, the DRX deactivation timer is started or restarted when the first terminal device receives side link control information SCI and the information included in the SCI meets a preset condition; wherein the SCI includes any one or more of a source layer-1ID, a destination layer-1ID or a communication type cast type, and the cast type is used to indicate unicast communication, multicast communication or broadcast communication.

[0393] In one possible design, the SCI includes a source layer-1ID and a destination layer-1ID, and when the destination layer-1ID is the same as the layer-1ID of the first terminal device, and the source layer-1ID is the same as the layer-1ID of the second terminal device, the first terminal device starts or restarts the DRX deactivation timer corresponding to the side link DRX between the first terminal device and the second terminal device; or,

[0394] The SCI includes a source layer-1ID, a destination layer-1ID and a cast type, and when the cast type indicates unicast communication, the destination layer-1ID is the same as the layer-1ID of the first terminal device, and the source layer-1ID is the same as the layer-1ID of the second terminal device, the first terminal device starts or restarts the DRX deactivation timer corresponding to the sidelink DRX between the first terminal device and the second terminal device; or,

[0395] The SCI includes a destination layer-1ID and a cast type. When the cast type is used to indicate multicast communication and the destination layer-1ID is the same as the destination layer-1ID of the multicast communication, the first terminal device starts or restarts the DRX deactivation timer corresponding to the sidelink DRX of the multicast communication.

[0396] In one possible design, a destination layer-1ID included in the SCI is the same as a layer-1ID of the first terminal device in any sidelink unicast communication, a source layer-1ID included in the SCI is the same as a layer-1ID of a second terminal device corresponding to the first terminal device in the sidelink unicast communication, and the apparatus further includes a processing module, the processing module being configured to:

[0397] Cancel start or restart the DRX deactivation timer corresponding to the sidelink DRX between the first terminal device and the second terminal device; wherein, the first terminal device determines that the source layer-2 ID of the media access control protocol data unit MAC PDU corresponding to the SCI is different from the layer-2ID of the second terminal device corresponding to the first terminal device in the sidelink unicast communication, or the destination layer-2 ID of the MAC PDU corresponding to the SCI is different from the layer-2ID of the first terminal device in the sidelink unicast communication; or,

[0398] Configuring a layer-2ID in a sidelink unicast communication between the first terminal device and the second terminal device; wherein the layer-1ID corresponding to the layer-2ID is different from the layer-1ID corresponding to the layer-2ID configured by the first terminal device in the sidelink unicast communication with the other second terminal device; or

[0399] Configure the layer-2ID in the sidelink unicast communication between the first terminal device and the second terminal device; wherein the layer-1ID corresponding to the layer-2ID is different from the layer-1ID corresponding to the layer-2ID in other sidelink unicast communications, and the other sidelink unicast communications are sidelink unicast communications in which the terminal devices do not include the first terminal device.

[0400] In one possible design, the first terminal device receives the SCI or the fourth indication information, and the MAC PDU corresponding to the SCI or the fourth indication information includes only non-data information, and the processing module is further used to:

[0401] Determine that the MAC PDU corresponding to the SCI includes the first information but does not include the second information, and cancel or restart the DRX deactivation timer corresponding to the sidelink DRX between the first terminal device and the second terminal device;

[0402] The first information includes any one or more of the following combinations: a sidelink channel state information report, and sidelink resource information in cooperation between terminal devices; the second information includes any one or more of the following combinations: data of a sidelink control channel SCCH, data of a sidelink service channel STCH, and a media access control control element MAC CE other than the first information; or,

[0403] The first information includes any one or more combinations of the following: sidelink channel state information report, sidelink resource information in collaboration between terminal devices, SCCH data, and information other than STCH data; the second information includes STCH data.

[0404] In one possible design, the first terminal device receives a PSCCH, a PSSCH, or a MAC PDU sent by the second terminal device, and the SCI corresponding to the PSCCH, the PSSCH, or the MAC PDU indicates at least two resources, or receives the SCI sent by the second terminal device and the SCI indicates at least two resources, and the processing module is further used to:

[0405] Start a sidechain HARQ timer or a DRX retransmission timer corresponding to the sidechain DRX between the first terminal device and the second terminal device; wherein the priority indicated by the SCI is greater than the minimum value of the priority value range;

[0406] The sidelink HARQ timer or DRX retransmission timer corresponding to the sidelink DRX between the first terminal device and the second terminal device is not started; wherein the priority indicated by the SCI is the minimum value of the priority value range.

[0407] In one possible design, if the first terminal device receives a PSCCH, a PSSCH, or a MAC PDU sent by the second terminal device and the SCI corresponding to the PSCCH, the PSSCH, or the MAC PDU indicates at least two resources, or receives the SCI sent by the second terminal device and the SCI indicates at least two resources, the processing module is further used to:

[0408] The start time of the sidelink HARQ timer or the DRX retransmission timer corresponding to the sidelink DRX between the first terminal device and the second terminal device is determined respectively according to each of the at least two resources indicated by the SCI; wherein the resource includes or indicates the SCI transmission timing.

[0409] In a possible design, the second sending module 603 is further configured to:

[0410] If it is determined to discard the side chain authority, fifth indication information is sent to the network device at the end time of the first time period or a time interval before the end time; wherein the fifth indication information is used to indicate that the first terminal device determines to discard the side chain authority and the end of the first time period; or,

[0411] If it is determined to discard the side chain authority, a sixth indication message is sent to the network device; wherein the sixth indication message is used to indicate that the first terminal device determines to discard the side chain authority and the end time of the first time period or the time domain position of the side chain authority determined to be discarded or the time domain position of the previous side chain authority of the side chain authority determined to be discarded.

[0412] Based on the same technical concept, the embodiment of the present application further provides a DRX device 700, which may be a network device, or a device 700 in a network device, and the device 700 includes a method for performing the above Figure 6 Modules of the method shown. For example, see Figure 7 , the apparatus 700 may include:

[0413] A determination module 701 is used to determine a first time period; wherein the first time period belongs to a sidelink DRX activation time of a second terminal device, and the second terminal device is a device that performs sidelink communication with the first terminal device;

[0414] The sending module 702 is used to send side chain permissions to the first terminal device so that the first terminal device sends a physical side chain control channel PSCCH and / or a physical side chain shared channel PSSCH based on the side chain permissions; wherein the side chain permissions are used to indicate the resources for the first terminal device to send PSCCH and / or PSSCH, and the time domain position of the resources is within the first time period.

[0415] In a possible design, the determining module 701 is specifically used for:

[0416] receiving a sidelink DRX parameter of the second terminal device sent by the first terminal device or any of the second terminal devices, and determining the first time period based on the sidelink DRX parameter; or,

[0417] Determine the first time period based on the sidelink DRX parameters of the second terminal device configured by itself; or,

[0418] Receive indication information sent by the first terminal device, and determine the first time period based on the indication information; wherein the indication information is used to indicate the start and / or end of the first time period.

[0419] In one possible design, the indication information is included in uplink control information UCI, media access control element MAC CE or radio resource control RRC message; the side chain permission is included in downlink control information DCI, MAC CE or RRC message.

[0420] In a possible design, the determining module 701, when receiving the indication information sent by the first terminal device, is specifically used to:

[0421] receiving first indication information sent by the first terminal device at the start time of the first time period; wherein the first indication information is used to indicate the end time of the first time period; or,

[0422] Receive second indication information sent by the first terminal device at the start time of the first time period and third indication information sent at the end time of the first time period; wherein the second indication information is used to indicate the start of the first time period, and the third indication information is used to indicate the end of the first time period.

[0423] In one possible design, the first time period belongs to the sidelink DRX activation time of the second terminal device, including:

[0424] The first period includes the sidelink DRX activation time of each of the second terminal devices; or,

[0425] The first time period includes the intersection or union of the sidelink DRX activation times of at least two of the second terminal devices.

[0426] In one possible design, the first time period includes an intersection or union of sidelink DRX activation times of at least two second terminal devices, including:

[0427] The first period includes any one or more of the following combinations:

[0428] The earliest starting time to the earliest ending time of the sidelink DRX activation time of each second terminal device;

[0429] The earliest starting time to the latest ending time of the sidelink DRX activation time of each second terminal device;

[0430] The latest start time and the earliest end time of the sidelink DRX activation time of each second terminal device;

[0431] The latest start time and the latest end time of the sidelink DRX activation time of each second terminal device;

[0432] The time when the side chain DRX activation time of any of the second terminal devices starts or ends to the time when the side chain DRX activation time of any of the second terminal devices starts or ends.

[0433] In a possible design, if the first time period includes the sidelink DRX activation time of each of the second terminal devices, the sending module 702 is specifically used to:

[0434] Send the side chain authority and device identification information to the first terminal device, so that the first terminal device determines the second terminal device corresponding to the side chain authority based on the device identification information.

[0435] In one possible design, the side chain DRX activation time includes the running time of a DRX duration timer and a DRX deactivation timer, and the DRX deactivation timer is started or restarted when the network device sends the side chain authority to the first terminal device; or,

[0436] The DRX deactivation timer is started or restarted when the network device receives HARQ feedback information from the first terminal device based on the side link authority; or,

[0437] The DRX deactivation timer is started or restarted when the network device receives fourth indication information sent by the first terminal device; wherein the fourth indication information is used to indicate that the DRX deactivation timer is started or restarted.

[0438] In one possible design, the apparatus 700 may further include: a receiving module;

[0439] The receiving module is used to receive fifth indication information sent by the first terminal device at the end time of the first time period or at a time interval before the end time; wherein the fifth indication information is used to indicate that the first terminal device determines to discard the side chain permission and the end of the first time period; or,

[0440] The network device receives the sixth indication information sent by the first terminal device; wherein the sixth indication information is used to instruct the first terminal device to determine to discard the side chain authority and the end time of the first time period or the time domain position of the side chain authority determined to be discarded or the time domain position of the previous side chain authority of the side chain authority determined to be discarded.

[0441] Based on the same technical concept, see Figure 8 The embodiment of the present application further provides a DRX device 800, including:

[0442] At least one processor 801; and a communication interface 803 communicatively connected to the at least one processor 801;

[0443] The at least one processor 801 executes the instructions stored in the memory 802 so that the device 800 performs Figure 4 The method shown.

[0444] Optionally, the memory 802 is located outside the device 800.

[0445] Optionally, the apparatus 800 includes the memory 802, the memory 802 is connected to the at least one processor 801, and the memory 802 stores instructions that can be executed by the at least one processor 801. Figure 8 The dashed lines indicate that memory 802 is optional for device 800 .

[0446] The processor 801 and the memory 802 may be coupled via an interface circuit or may be integrated together, which is not limited here.

[0447] The specific connection medium between the processor 801, the memory 802 and the communication interface 803 is not limited in the embodiment of the present application. Figure 8 In the embodiment, the processor 801, the memory 802 and the communication interface 803 are connected via a bus 804. Figure 8 The connections between the other components are shown in bold lines, which are only for illustration and are not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 8 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0448] It should be understood that the processor mentioned in the embodiments of the present application can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented by software, the processor can be a general-purpose processor implemented by reading software code stored in a memory.

[0449] Exemplarily, the processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0450] It should be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct memory bus random access memory (DR RAM).

[0451] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0452] It should be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0453] Based on the same technical concept, the embodiment of the present application also provides a computer-readable storage medium, including a program or an instruction, when the program or the instruction is executed on a computer, Figure 4 The method shown is executed.

[0454] Based on the same technical concept, the embodiment of the present application also provides a chip, which is coupled to a memory and is used to read and execute program instructions stored in the memory, so that Figure 4 The method shown is executed.

[0455] Based on the same technical concept, the embodiment of the present application also provides a computer program product, including instructions, which, when executed on a computer, enables Figure 4 The method shown is executed.

[0456] Based on the same technical concept, an embodiment of the present application also provides a communication system, including the first terminal device and network device mentioned above in the embodiment of the present application.

[0457] It should be understood that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0458] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, apparatuses, and computer program products involved in the embodiments. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0459] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0460] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

Claims

1. A DRX method, characterized in that: include: The first terminal device receives first sidelink control information SCI sent by the second terminal device; wherein the second terminal device is a device that performs sidelink communication with the first terminal device; If the first SCI indicates at least two resources, the first terminal device determines that the duration of the hybrid automatic repeat request HARQ round-trip time RTT timer of the sidelink process corresponding to the first SCI is a first duration; wherein the first duration is determined based on the time domain position of the resource indicated by the first SCI; If the first SCI indicates a resource, the first terminal device determines that the duration of the HARQ RTT timer is a second duration; wherein the second duration is configured by the second terminal device or network device.

2. The method according to claim 1, characterized in that The method further comprises: The first terminal device starts the HARQ RTT timer at a first time domain position; The first time domain position is the first symbol or time slot after the transmission of the carrying sidelink HARQ feedback is completed, and the sidelink HARQ feedback is feedback for the first SCI transmission or the physical sidelink control channel PSCCH, physical sidelink shared channel PSSCH or media access control protocol data unit MAC PDU transmission corresponding to the first SCI; or The first time domain position is the first symbol or time slot after the first SCI transmission or the PSCCH, PSSCH or MAC PDU transmission corresponding to the first SCI is completed.

3. The method according to claim 2, characterized in that The first symbol or time slot after the HARQ RTT timer starts and runs after the first duration is the time domain position of the second resource indicated by the first SCI; or, The first duration is equal to an offset of a time domain position of a second resource indicated by the first SCI relative to the first time domain position.

4. The method according to any one of claims 1 to 3, characterized in that: The time domain resource allocation field included in the first SCI indicates the quantity of resources indicated by the first SCI.

5. The method according to any one of claims 1 to 3, characterized in that: When the first SCI indicates at least two resources, the time domain resource allocation field included in the first SCI indicates a time slot offset of resources other than the first resource among the at least two resources relative to the first resource.

6. The method according to claim 2 or 3, characterized in that: After the HARQ RTT timer is started and runs for the first duration, it times out, and the method further includes: If the HARQ RTT timer times out and the first terminal device fails to successfully decode the data of the side link process, the first terminal device starts or restarts the DRX retransmission timer of the side link process in the first symbol or time slot after the HARQ RTT timer times out.

7. The method according to claim 6, characterized in that After the first terminal device starts or restarts the DRX retransmission timer of the side link process, the method further includes: The first terminal device monitors PSCCH, PSSCH or SCI during the operation of the DRX retransmission timer.

8. The method according to any one of claims 1 to 3, characterized in that: After the first terminal device receives the first sidelink control information SCI sent by the second terminal device, the method further includes: The first terminal device stops the DRX retransmission timer of the side chain process.

9. A DRX device, characterized in that: include: A receiving module, configured to receive first sidelink control information SCI sent by a second terminal device; wherein the second terminal device is a device that performs sidelink communication with the first terminal device; A first determination module, configured to, if the first SCI indicates at least two resources, determine by the first terminal device that the duration of a hybrid automatic repeat request HARQ round trip time RTT timer of a side link process corresponding to the first SCI is a first duration; wherein the first duration is determined based on a time domain position of the resource indicated by the first SCI; The second determination module is used to determine that if the first SCI indicates a resource, the first terminal device determines that the duration of the HARQRTT timer is a second duration; wherein the second duration is configured by the second terminal device or the network device.

10. A DRX device, characterized in that: The device comprises: at least one processor; and, A memory and a communication interface communicatively connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the at least one processor executes the method according to any one of claims 1 to 8 by executing the instructions stored in the memory.

11. A computer-readable storage medium, characterized in that: The method comprises a program or an instruction, and when the program or the instruction is run on a computer, the method according to any one of claims 1 to 8 is executed.

Images