Sidelink transmission method and terminal

Abstract

The present application relates to a transmission method and terminal for a sidelink. The method includes: the terminal receives downlink information, the downlink information is used to indicate resource authorization for the sidelink; the terminal controls the state of a timer related to discontinuous reception DRX for the sidelink based on a first event. In an embodiment of the present application, based on event control, the state of a timer related to DRX for the sidelink can be optimized for DRX, thereby reducing the terminal energy consumption of the sidelink transmission.

Description

Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a sidelink transmission method and terminal. Background Art

[0002] Device to Device (D2D) communication is a transmission technology based on sidelink (SL). Different from the traditional cellular system where communication data is received or sent by base stations, the vehicle to everything (V2X) system uses terminal to terminal direct communication, so it has higher spectrum efficiency and lower transmission delay.

[0003] In the long-term evolution (LTE) system, discontinuous reception (DRX) is an energy-saving mechanism. In sideline transmission, how to optimize DRX to reduce terminal energy consumption is a problem that needs to be considered. Summary of the invention

[0004] The embodiments of the present application provide a sidelink transmission method and terminal, which can reduce the terminal energy consumption of sidelink transmission.

[0005] The embodiment of the present application provides a side link transmission method, including:

[0006] The terminal receives downlink information, where the downlink information is used to indicate resource authorization of the sidelink;

[0007] The terminal controls a state of a timer related to discontinuous reception (DRX) for the sidelink based on the first event.

[0008] An embodiment of the present application provides a terminal, including:

[0009] A receiving unit, configured to receive downlink information, where the downlink information is used to indicate resource authorization of a sidelink;

[0010] The processing unit is used to control the state of the timer related to discontinuous reception DRX for the side link based on the first event.

[0011] The embodiment of the present application provides a terminal, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the terminal device executes the above-mentioned side link transmission method.

[0012] An embodiment of the present application provides a chip for implementing the above-mentioned side link transmission method.

[0013] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned side link transmission method.

[0014] An embodiment of the present application provides a computer-readable storage medium for storing a computer program. When the computer program is executed by a device, the device executes the above-mentioned side link transmission method.

[0015] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above-mentioned side link transmission method.

[0016] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above-mentioned side link transmission method.

[0017] In the embodiment of the present application, based on event control of the state of the DRX-related timer for the side link, DRX can be optimized to reduce the terminal energy consumption of the side link transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 It is a schematic diagram of an application scenario according to an embodiment of the present application.

[0019] Figure 2 is a schematic diagram of mode A.

[0020] Figure 3 This is a schematic diagram of mode B.

[0021] Figure 4 It is a schematic flowchart of a side link transmission method according to an embodiment of the present application.

[0022] Figure 5 This is a schematic diagram of Example 1.

[0023] Figure 6 This is a schematic diagram of Example 2.

[0024] Figure 7 This is a schematic diagram of Example 3.

[0025] Figure 8 is a schematic diagram of Example 4.

[0026] Fig. 9 is a schematic block diagram of a terminal according to an embodiment of the present application.

[0027] Fig.10 It is a schematic block diagram of a communication device according to an embodiment of the present application.

[0028] Fig.11is a schematic block diagram of a chip according to an embodiment of the present application.

[0029] Fig.12 It is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0030] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0031] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0032] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle to vehicle (V2V) communication, or vehicle to everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0033] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.

[0034] Optionally, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

[0035] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0036] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0037] In the embodiments of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.).

[0038] In the embodiment of the present application, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0039] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology 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-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices 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 and smart jewelry for vital sign monitoring.

[0040] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (EvolutionalNode B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network, or a network device in an NTN network, etc.

[0041] As an example but not limitation, in an embodiment of the present application, the network device may have a mobile characteristic, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0042] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0043] Figure 1 A communication system 100 is exemplarily shown. The communication system includes a network device 110 and two terminal devices 120. Optionally, the communication system 100 may include multiple network devices 110, and each network device 110 may include other number of terminal devices 120 within its coverage area, which is not limited in the present embodiment.

[0044] Optionally, the communication system 100 may also include other network entities such as a mobility management entity (Mobility Management Entity, MME), an access and mobility management function (Access and Mobility Management Function, AMF), etc., which is not limited in the embodiments of the present application.

[0045] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment may be an evolutionary base station (evolutional node B, referred to as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), micro-micro base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB) in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

[0046] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1 Taking the communication system shown as an example, the communication equipment may include network equipment and terminal equipment with communication functions. The network equipment and terminal equipment may be specific equipment in the embodiments of the present application and will not be repeated here. The communication equipment may also include other equipment in the communication system, such as network controllers, mobile management entities and other network entities, which are not limited to the embodiments of the present application.

[0047] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0048] It should be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0049] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.

[0050] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application.

[0051] like Figure 2 and Figure 3 As shown, 3GPP includes the following transmission modes: mode A (mode-A) and mode B (mode-A).

[0052] Mode A: The transmission resources of the terminal are allocated by the base station, and the terminal sends data on the sidelink according to the resources allocated by the base station; the base station can allocate resources for a single transmission to the terminal, or allocate resources for semi-static transmission to the terminal.

[0053] Mode B: The terminal device selects a resource in the resource pool to transmit data. The terminal device can be an on-board terminal in the Internet of Vehicles.

[0054] In the process of 3GPP protocol evolution, D2D can include the following scenarios:

[0055] ProSe (Proximity based Service): In Rel-12 / 13, device-to-device communication is mainly targeted at ProSe scenarios and can be applied to public safety services.

[0056] Vehicle-to-everything (V2X): In Rel-14 / 15, the vehicle-to-everything system is mainly aimed at vehicle-to-vehicle communication scenarios, and is mainly aimed at relatively high-speed vehicle-to-vehicle and vehicle-to-human communication services.

[0057] Wearable devices (FeD2D): In Rel-14, FeD2D is mainly aimed at scenarios where wearable devices access the network through mobile phones, and is mainly aimed at scenarios with low mobile speeds and low power access.

[0058] Based on LTE V2X, NR V2X is not limited to broadcast scenarios, but is further expanded to unicast and multicast scenarios, and the application of V2X is studied in these scenarios.

[0059] Similar to LTE V2X, NR V2X will also define the above two resource authorization modes: mode-A / B. Furthermore, users may be in a mixed mode, that is, they can use mode-A to obtain resources and mode-B to obtain resources at the same time.

[0060] Different from LTE V2X, in addition to the feedback-free, UE-initiated Hybrid Automatic Repeat reQuest (HARQ) retransmission, NR V2X introduces feedback-based HARQ retransmission, which is not limited to unicast communication but also includes multicast communication.

[0061] The following is an introduction to DRX:

[0062] The user needs to perform DRX when receiving downlink to achieve power saving. Considering that the network can send resource grants for sidelinks to the user through the downlink, that is, the above-mentioned mode-A method, the question here is how to perform DRX for downlink reception for the "resource grants for sidelinks".

[0063] In LTE, the UE can be configured in mode-A and use DRX at the same time, but the network does not make special optimizations for DRX for "resource grant for sidelink", that is, the UE will decide whether to enter sleep mode to save power based on the Uu interface rather than the relevant parameters / timers of the sidelink. In NR, currently the UE cannot be configured in mode-A and use DRX at the same time.

[0064] The present application can be applied to NR. In a scenario where the UE can be configured as mode-A and use DRX at the same time, DRX is specially optimized for "resource authorization for the side link", and DRX-related parameters and timers for "resource authorization for the side link" are proposed.

[0065] Figure 4 is a schematic flow chart of a sidelink transmission method 200 according to an embodiment of the present application. The method can optionally be applied to Figures 1 to 3 The system shown in the figure is not limited thereto. The method includes at least part of the following contents.

[0066] S210. The terminal receives downlink information, where the downlink information is used to indicate resource authorization of a sidelink.

[0067] S220. The terminal controls a state of a timer related to discontinuous reception (DRX) for the sidelink based on the first event.

[0068] Optionally, in an embodiment of the present application, the downlink information is carried by a physical downlink control channel (Physical Downlink Control Channel, PDCCH).

[0069] Optionally, in an embodiment of the present application, the DRX-related timer includes a round-trip time (RTT) timer and / or a retransmission timer.

[0070] Optionally, in the embodiment of the present application, controlling the state of the DRX-related timer for the sidelink includes at least one of the following:

[0071] Starting the RTT timer for the side link;

[0072] When the RTT timer times out, a retransmission timer for the sidelink is started.

[0073] For example, if the timer related to DRX includes an RTT timer and a retransmission timer for the sidelink, the terminal may start the RTT timer for the sidelink based on the first event, and restart the retransmission timer for the sidelink when the RTT timer times out.

[0074] Optionally, in the embodiment of the present application, controlling a state of a DRX-related timer for the sidelink includes:

[0075] Start the retransmission timer for the sidelink.

[0076] For example, if the DRX-related timer includes a retransmission timer for the sidelink, the terminal may start the retransmission timer for the sidelink based on the first event.

[0077] Optionally, in the embodiment of the present application, controlling the state of a DRX-related timer for the sidelink further includes:

[0078] Stop the running retransmission timer of the sidelink.

[0079] For example, the transmission of the side link may be continuous. If there is a retransmission timer running on the side link, the terminal may first stop the running retransmission timer based on the first event, and then start the RTT timer for the side link. When the RTT timer times out, the retransmission timer for the side link is started again.

[0080] For another example, if there is no RTT timer for the sidelink, the terminal may restart the retransmission timer for the sidelink based on the first event.

[0081] In an embodiment of the present application, after the terminal starts the retransmission timer for the side link, during the operation of the retransmission timer, the terminal is in a DRX wake-up state and can monitor the downlink channel. For example, the terminal performs downlink PDCCH reception for a specific HARQ process of the side link. After the terminal obtains the resource authorization of the side link allocated by the network to the terminal, it can communicate with other terminals of the side link based on the resource authorization of the side link. In the case where the retransmission timer for the side link is not started, the terminal is in a DRX sleep state and does not monitor the downlink channel, which can achieve energy saving and power saving effects.

[0082] In an embodiment of the present application, after the terminal starts the RTT timer for the side link, the terminal does not need to monitor the downlink channel during the operation of the timer. For example, during the operation of the RTT timer, the terminal does not need to perform downlink PDCCH reception, or does not need to perform downlink PDCCH reception for a specific HARQ process of the side link.

[0083] Optionally, in the embodiment of the present application, the method further includes:

[0084] The terminal determines whether to start a retransmission timer for the sidelink based on the feedback information.

[0085] Optionally, in the embodiment of the present application, the terminal determines whether to start a retransmission timer for the sidelink based on the feedback information, including at least one of the following:

[0086] When the feedback information is confirmation (ACK) information, the retransmission timer for the side link is not started;

[0087] When the feedback information is non-acknowledgement (NACK) information, start a retransmission timer for the sidelink;

[0088] When receiving the feedback information, start a retransmission timer for the sidelink;

[0089] If the feedback information is not received, the retransmission timer for the sidelink is not started.

[0090] For example, the terminal may determine whether to start the retransmission timer for the side link based on the transmission status of the opposite end indicated by the received feedback information. If the feedback information received by the terminal is ACK information, it may indicate that the opposite end has successfully received the data sent by the terminal, and the retransmission timer for the side link may not be started. If the feedback information received by the terminal is NACK information, it may indicate that the opposite end has not successfully received the data sent by the terminal, and the retransmission timer for the side link may be started.

[0091] For another example, the terminal may determine whether to start the retransmission timer for the side link based on whether the feedback information is received. If the terminal does not receive the feedback information from the other end, it may indicate that the other end has successfully received the data sent by the terminal or the other end does not need to retransmit, and the retransmission timer for the side link may not be started. If the feedback information received by the terminal indicates that the other end has not successfully received the data sent by the terminal or the other end needs to retransmit, the retransmission timer for the side link may be started.

[0092] Optionally, in an embodiment of the present application, the first event includes:

[0093] The terminal receives a downlink resource including the downlink information, where the downlink resource may be a control channel or a data channel, such as a PDCCH or a PDSCH.

[0094] Optionally, the first event may include when the terminal receives a downlink resource including the downlink information.

[0095] For example, when the terminal receives the PDCCH, it may start a retransmission timer for the sidelink. For another example, when the terminal receives the PDCCH, it first starts an RTT timer for the sidelink, and when the RTT timer times out, it starts a retransmission timer for the sidelink.

[0096] Optionally, the first event may include after the terminal receives the downlink resource including the downlink information. After receiving the downlink resource including the downlink information means that the first event does not occur with the reception of the downlink resource, but there is a certain interval in timing. Exemplarily, the first event occurs in the first time unit after the terminal receives the downlink resource including the downlink information, or in a specific number of time units. For example, after receiving the downlink resource, in the next time slot, the next symbol, or a predetermined number of time slots or symbols in timing, the first event can control the state of the DRX-related timer for the side link.

[0097] For example, after receiving the PDCCH, the terminal may start a retransmission timer for the sidelink. For another example, after receiving the PDCCH, the terminal first starts an RTT timer for the sidelink, and when the RTT timer times out, starts a retransmission timer for the sidelink.

[0098] Optionally, in an embodiment of the present application, the first event includes:

[0099] The terminal sends a physical sidelink control channel (Physical Sidelink Control Channel, PSCCH) and / or a physical sidelink shared channel (Physical Sidelink Shared Channel, PSSCH).

[0100] Exemplarily, the first event may only include that the terminal sends a PSCCH and / or a PSSCH. The first event may also include both that the terminal receives the PDCCH and that the terminal sends a PSCCH and / or a PSSCH.

[0101] Optionally, the first event may include when the terminal sends a PSCCH and / or a PSSCH.

[0102] For example, when the terminal sends the PSCCH and / or the PSSCH, the retransmission timer for the sidelink may be started.

[0103] For another example, when the terminal sends PSCCH and / or PSSCH, the RTT timer for the side link is first started, and when the RTT timer times out, the retransmission timer for the side link is started.

[0104] For another example, when the terminal receives the PDCCH, it first starts the RTT timer for the side link, and when the RTT timer times out, it starts the retransmission timer for the side link. When the terminal sends the PSSCH, it restarts the RTT timer for the side link, and when the RTT timer times out, it restarts the retransmission timer for the side link.

[0105] Optionally, the first event may include after the terminal sends the PSCCH and / or the PSSCH. Exemplarily, the first time unit after the terminal sends the PSCCH and / or the PSSCH controls the state of the DRX-related timer for the sidelink.

[0106] For example, after sending the PSCCH and / or PSSCH, the terminal may start a retransmission timer for the sidelink.

[0107] For another example, after sending the PSCCH and / or PSSCH, the terminal first starts the RTT timer for the side link, and then starts the retransmission timer for the side link when the RTT timer times out.

[0108] For another example, after receiving the PDCCH, the terminal may start the retransmission timer for the sidelink. After sending the PSCCH, the terminal may restart the retransmission timer for the sidelink.

[0109] For another example, after receiving the PDCCH, the terminal first starts the RTT timer for the side link, and when the RTT timer times out, it starts the retransmission timer for the side link. After sending the PSSCH, the terminal restarts the RTT timer for the side link, and when the RTT timer times out, it restarts the retransmission timer for the side link.

[0110] Optionally, in an embodiment of the present application, the first event includes:

[0111] The terminal receives a Physical Sidelink Feedback Channel (PSFCH).

[0112] Exemplarily, the first event may only include the terminal receiving the PSFCH. The first event may also include both the terminal receiving the PDCCH and the terminal receiving the PSFCH. The first event may also include both the terminal receiving the PDCCH and the terminal sending the PSCCH and / or PSSCH, and the terminal receiving the PSFCH.

[0113] Optionally, the first event may include: when the terminal receives a PSFCH.

[0114] For example, when the terminal receives the PSFCH, it may start a retransmission timer for the sidelink.

[0115] For another example, when the terminal receives the PSFCH, it first starts the RTT timer for the side link, and when the RTT timer times out, it starts the retransmission timer for the side link.

[0116] For another example, after receiving the PDCCH, the terminal may start the retransmission timer for the sidelink. When the terminal sends the PSSCH, the terminal restarts the retransmission timer for the sidelink. When the terminal receives the PSFCH, the terminal restarts the retransmission timer for the sidelink again.

[0117] For another example, when the terminal receives the PDCCH, it first starts the RTT timer for the sidelink, and when the RTT timer times out, it starts the retransmission timer for the sidelink. After sending the PSSCH, the terminal restarts the RTT timer for the sidelink, and when the RTT timer times out, it starts the retransmission timer for the sidelink. When the terminal receives the PSFCH, it restarts the RTT timer for the sidelink again, and when the RTT timer times out, it starts the retransmission timer for the sidelink.

[0118] Optionally, the first event may include: after the terminal receives the PSFCH. Exemplarily, the state of the DRX-related timer for the sidelink is controlled in the first time unit after the terminal receives the PSFCH.

[0119] For example, after receiving the PSFCH, the terminal may start a retransmission timer for the sidelink.

[0120] For another example, after receiving the PSFCH, the terminal first starts the RTT timer for the side link, and then starts the retransmission timer for the side link when the RTT timer times out.

[0121] For another example, after receiving the PDCCH, the terminal may start the retransmission timer for the sidelink. After sending the PSSCH, the terminal may restart the retransmission timer for the sidelink. After receiving the PSFCH, the terminal may restart the retransmission timer for the sidelink again.

[0122] For another example, after receiving the PDCCH, the terminal first starts the RTT timer for the side link, and when the RTT timer times out, it starts the retransmission timer for the side link. After sending the PSSCH, the terminal restarts the RTT timer for the side link, and when the RTT timer times out, it starts the retransmission timer for the side link. After receiving the PSFCH, the terminal restarts the RTT timer for the side link again, and when the RTT timer times out, it starts the retransmission timer for the side link.

[0123] Optionally, in an embodiment of the present application, the first event includes:

[0124] The terminal sends a physical uplink control channel (Physical Uplink Control Channel, PUCCH).

[0125] Exemplarily, the first event may only include the terminal sending PUCCH. The first event may also include both the terminal receiving the PDCCH and the terminal sending PUCCH. The first event may also include both the terminal receiving the PDCCH and the terminal sending PSCCH and / or PSSCH and sending PUCCH. The first event may also include both the terminal receiving the PDCCH and the terminal sending PSCCH and / or PSSCH, and the terminal receiving PSFCH and the terminal sending PUCCH.

[0126] Optionally, the first event may include: when the terminal sends a PUCCH.

[0127] For example, when sending the PUCCH, the terminal may start a retransmission timer for the sidelink.

[0128] For another example, when sending the PUCCH, the terminal first starts the RTT timer for the side link, and then starts the retransmission timer for the side link when the RTT timer times out.

[0129] For another example, when the terminal receives the PDCCH, it may start the retransmission timer for the sidelink. When the terminal sends the PUCCH, it may restart the retransmission timer for the sidelink.

[0130] For another example, after receiving the PDCCH, the terminal may start the retransmission timer for the sidelink. When sending the PSSCH, the terminal restarts the retransmission timer for the sidelink. After receiving the PSFCH, the terminal restarts the retransmission timer for the sidelink again. When sending the PUCCH, the terminal restarts the retransmission timer for the sidelink.

[0131] Optionally, the first event may include: after the terminal sends the PUCCH. Exemplarily, the first time unit after the terminal sends the PUCCH controls the state of the DRX-related timer for the sidelink.

[0132] For example, after sending the PUCCH, the terminal may start a retransmission timer for the sidelink.

[0133] For another example, after sending the PUCCH, the terminal first starts the RTT timer for the side link, and then starts the retransmission timer for the side link when the RTT timer times out.

[0134] For another example, after receiving the PDCCH, the terminal may start the retransmission timer for the sidelink. After sending the PUCCH, the terminal may restart the retransmission timer for the sidelink.

[0135] For another example, after receiving the PDCCH, the terminal may start the retransmission timer for the sidelink. After sending the PSSCH, the terminal restarts the retransmission timer for the sidelink. After receiving the PSFCH, the terminal restarts the retransmission timer for the sidelink again. After sending the PUCCH, the terminal restarts the retransmission timer for the sidelink.

[0136] For another example, after receiving the PDCCH, the terminal first starts the RTT timer for the side link, and when the RTT timer times out, it starts the retransmission timer for the side link. After sending the PSSCH, the terminal restarts the RTT timer for the side link, and when the RTT timer times out, it starts the retransmission timer for the side link. After receiving the PSFCH, the terminal restarts the RTT timer for the side link again, and when the RTT timer times out, it starts the retransmission timer for the side link. After sending the PUCCH, the terminal restarts the RTT timer for the side link again, and when the RTT timer times out, it starts the retransmission timer for the side link.

[0137] Optionally, in the embodiment of the present application, the execution condition of the method includes at least one of the following:

[0138] PUCCH has been configured;

[0139] PUCCH is not configured;

[0140] PSFCH has been configured;

[0141] PSFCH is already used;

[0142] PSFCH is not configured;

[0143] PSFCH is not used.

[0144] Optionally, in the embodiment of the present application, the first event is associated with the execution condition of the method.

[0145] In the embodiment of the present application, different events may correspond to different execution conditions.

[0146] For example, when the event is that the terminal receives the PDCCH, the execution condition may include at least one of the following: the PUCCH is not configured; the PSFCH is not configured; and the PSFCH is not used.

[0147] For another example, after the event is that the terminal sends PSCCH and / or PSSCH, the execution condition may include at least one of the following: PUCCH is not configured; PSFCH is not configured; PSFCH is not used.

[0148] For another example, when the event is that the terminal receives the PSFCH, the execution condition may include at least one of the following: the PUCCH is not configured; the PSFCH is configured; and the PSFCH is used.

[0149] For another example, after the event is that the terminal sends PUCCH, the execution condition may include at least one of the following: PUCCH has been configured; PSFCH has been configured; PSFCH has been used; PSFCH has not been configured; PSFCH has not been used.

[0150] In the embodiment of the present application, the correspondence between multiple events and execution conditions can also be set respectively, and the event used to trigger the timer can be selected based on different execution conditions.

[0151] For example, when the event is that the terminal receives PDCCH, the corresponding execution condition is: PUCCH is not configured and PSFCH is not configured. When the event is that the terminal sends PSCCH and / or PSSCH, the corresponding execution condition is: PUCCH is configured and PSFCH is not configured. When the event is that the terminal receives PSFCH, the corresponding execution condition is: PUCCH is not configured and PSFCH is configured. When the event is that the terminal sends PUCCH, the corresponding execution condition is: PUCCH is configured and PSFCH is configured.

[0152] For another example, when the event is that the terminal receives PDCCH, the corresponding execution condition is: PUCCH is not configured, PSFCH is not configured, and PSFCH is not used. When the event is that the terminal sends PSCCH and / or PSSCH, the corresponding execution condition is: PUCCH is configured, PSFCH is not configured, and PSFCH is not used. When the event is that the terminal receives PSFCH, the corresponding execution condition is: PUCCH is not configured, PSFCH is configured, and PSFCH is used. When the event is that the terminal sends PUCCH, the corresponding execution condition is: PUCCH is configured, PSFCH is configured, and PSFCH is not used.

[0153] In the embodiment of the present application, the state of the timer related to DRX for the side link is controlled based on events, so that DRX can be optimized and the energy consumption of the terminal of the side transmission can be reduced. For example, if the terminal is configured as mode A and uses the DRX mechanism, after the terminal receives downlink information from the network, the state of the timer related to DRX for the side link can be controlled based on some events, thereby reducing the energy consumption of the terminal of the side transmission.

[0154] In an application example, the time point at which the timer is started in the embodiment of the present application may be the first time unit (symbol, time slot, etc.) after the event occurs. The event may be a transmission / reception behavior of a specific channel, such as PDCCH, PSCCH, PSSCH, PSFCH, PUCCH, etc. If the above channel contains one or more time units, the timer can be started at the first or last time unit of the channel.

[0155] The timer in the embodiment of the present application is described as follows:

[0156] RTT timer: During the running of this timer, the UE does not need to receive the downlink PDCCH, or does not need to receive the downlink PDCCH for a specific HARQ process of the side link.

[0157] Retransmission timer: During the running of the timer, the UE needs to perform downlink PDCCH reception, or needs to perform downlink PDCCH reception for a specific HARQ process of the side link.

[0158] Example 1: Start the timer based on PDCCH, see Figure 5 , examples may include:

[0159] 1. UE receives PDCCH;

[0160] 2. If the PDCCH indicates a sidelink resource grant, a DRX-related timer is started, for example:

[0161] a) starting the RTT timer for the sidelink; and / or

[0162] b) Start the retransmission timer (Re-Tx timer) for the sidelink.

[0163] Specifically, the timer start mode may include at least one of the following:

[0164] a) In the case where an RTT timer and a retransmission timer are included, the retransmission timer for the side link is stopped; when the RTT timer times out, the retransmission timer for the side link is started.

[0165] b) In the case of only including a retransmission timer, stopping the running retransmission timer for the side link and restarting the retransmission timer for the side link.

[0166] Optionally, whether to start the retransmission timer can be determined based on feedback information. One method includes: determining whether to start the retransmission timer for the side link based on whether the receiving end UE feeds back ACK. If ACK is fed back, the retransmission timer for the side link is not started, otherwise the retransmission timer for the side link is started. Another method includes: determining whether to start the retransmission timer for the side link based on whether the receiving end UE feeds back information. If information is fed back, the retransmission timer for the side link is started, otherwise the retransmission timer for the side link is not started.

[0167] Optionally, the scheme of this example can be used in at least one of the following situations.

[0168] a) PUCCH is not configured;

[0169] b) PSFCH is not configured;

[0170] c) PSFCH is not used.

[0171] Example 2: Start the timer based on PSCCH / PSSCH, see Figure 6 , the example may include.

[0172] 1. The UE receives the PDCCH.

[0173] 2. If the PDCCH indicates a resource grant for the sidelink, the UE sends the PSCCH / PSSCH according to the resource grant.

[0174] 3. After PSCCH / PSSCH transmission, start the DRX-related timer, for example:

[0175] a) starting the RTT timer for the sidelink; and / or

[0176] b) Start the retransmission timer for the sidelink.

[0177] Specifically, the description of the method of starting the timer can be seen in Example 1.

[0178] Optionally, for a description of determining whether to start a retransmission timer based on feedback information, see Example 1.

[0179] Optionally, the scheme of this example can be used in at least one of the following situations.

[0180] a) PUCCH is not configured;

[0181] b) PSFCH is not configured;

[0182] c) PSFCH is not used.

[0183] Example 3: Start the timer based on PSFCH, see Figure 7 , the example may include.

[0184] 1. The UE receives the PDCCH.

[0185] 2. If the PDCCH indicates a resource grant for the sidelink, the UE sends the PSCCH / PSSCH according to the resource grant.

[0186] 3. The UE receives the PSCCH / PSSCH and sends the corresponding PSFCH.

[0187] 4. After receiving PSFCH, start the DRX-related timer, for example:

[0188] a) starting the RTT timer for the sidelink; and / or

[0189] b) Start the retransmission timer for the sidelink.

[0190] Specifically, the description of the method of starting the timer can be seen in Example 1.

[0191] Optionally, for a description of determining whether to start a retransmission timer based on feedback information, see Example 1.

[0192] Optionally, the scheme of this example can be used in at least one of the following situations.

[0193] a) PUCCH is not configured;

[0194] b) PSFCH has been configured;

[0195] c) PSFCH is already in use.

[0196] Example 4: Start the timer based on PUCCH, see Figure 8 , the example may include.

[0197] 1. The UE receives the PDCCH.

[0198] 2. If the PDCCH indicates a resource grant for the sidelink, the UE sends the PSCCH / PSSCH according to the resource grant.

[0199] 3. The UE receives the PSCCH / PSSCH and sends the corresponding PSFCH.

[0200] 4. UE reports PUCCH.

[0201] 5. After PUCCH reporting, start the DRX-related timer, for example:

[0202] a) starting the RTT timer for the sidelink; and / or

[0203] b) starting a retransmission timer for the sidelink;

[0204] Specifically, the description of the method of starting the timer can be seen in Example 1.

[0205] Optionally, for a description of determining whether to start a retransmission timer based on feedback information, see Example 1.

[0206] Optionally, the scheme of this example can be used in at least one of the following situations.

[0207] a) PUCCH has been configured;

[0208] b) PSFCH has been configured;

[0209] c) PSFCH is already in use;

[0210] e) PSFCH is not configured;

[0211] f)PSFCH is not used.

[0212] In addition, the solutions of Examples 1 to 4 above can be combined with:

[0213] For example: the UE starts the RTT timer and / or the retransmission timer based on the event of Example 1. Then, the UE starts the RTT timer and / or the retransmission timer based on at least one event of Example 2, Example 3 or Example 4. The restarting method of the RTT timer and / or the retransmission timer may include: (1) if the RTT timer is running at this time, if it is necessary to start the RTT timer, restart the currently running RTT timer; if it is necessary to start the retransmission timer, wait for the current RTT timer to time out, and then start the retransmission timer. (2) if the retransmission timer is running at this time, if it is necessary to start the retransmission timer, restart the retransmission timer.

[0214] For another example, the UE starts the RTT timer and / or the retransmission timer based on the event of Example 2. Then, the UE starts the RTT timer and / or the retransmission timer based on at least one event of Example 1, Example 3, or Example 4. The restarting method of the RTT timer and / or the retransmission timer refers to the relevant description of the above examples.

[0215] For another example, the UE starts the RTT timer and / or the retransmission timer based on the event of Example 3. Then, the UE starts the RTT timer and / or the retransmission timer based on at least one event of Example 1, Example 2, or Example 4. The restarting method of the RTT timer and / or the retransmission timer refers to the relevant description of the above examples.

[0216] For another example, the UE starts the RTT timer and / or the retransmission timer based on the event of Example 4. Then, the UE starts the RTT timer and / or the retransmission timer based on at least one event of Example 1, Example 2, or Example 3. For the restarting method of the RTT timer and / or the retransmission timer, refer to the relevant description of the above examples.

[0217] The embodiment of the present application optimizes the sidelink power saving mechanism, and can achieve power saving effect in downlink reception when the network schedules sidelink resources.

[0218] Fig. 9 4 is a schematic block diagram of a terminal 400 according to an embodiment of the present application. The terminal 400 may include:

[0219] The receiving unit 410 is configured to receive downlink information, where the downlink information is used to indicate a resource grant of a sidelink;

[0220] The processing unit 420 is configured to control a state of a timer associated with discontinuous reception (DRX) for the sidelink based on the first event.

[0221] Optionally, in an embodiment of the present application, the downlink information is carried by a physical downlink control channel PDCCH.

[0222] Optionally, in an embodiment of the present application, the DRX-related timer includes a round-trip time RTT timer and / or a retransmission timer.

[0223] Optionally, in the embodiment of the present application, the processing unit is further configured to perform at least one of the following:

[0224] Starting the RTT timer for the side link;

[0225] When the RTT timer times out, a retransmission timer for the sidelink is started.

[0226] Optionally, in an embodiment of the present application, the processing unit is also used to start a retransmission timer for the side link.

[0227] Optionally, in an embodiment of the present application, the processing unit is further used to determine whether c starts a retransmission timer for the side link based on the feedback information.

[0228] Optionally, in the embodiment of the present application, the processing unit is further configured to perform at least one of the following:

[0229] In the case where the feedback information is confirmation ACK information, the retransmission timer for the side link is not started;

[0230] When the feedback information is non-acknowledgement (NACK) information, start a retransmission timer for the sidelink;

[0231] When receiving the feedback information, start a retransmission timer for the sidelink;

[0232] If the feedback information is not received, the retransmission timer for the sidelink is not started.

[0233] Optionally, in an embodiment of the present application, the processing unit is also used to stop the retransmission timer of the running side link.

[0234] Optionally, in an embodiment of the present application, the first event includes:

[0235] After the terminal receives the PDCCH including the downlink information.

[0236] Optionally, in an embodiment of the present application, the first event includes:

[0237] The terminal sends a physical sidelink control channel PSCCH and / or a physical sidelink shared channel PSSCH.

[0238] Optionally, in an embodiment of the present application, the first event includes:

[0239] After the terminal receives PSFCH.

[0240] Optionally, in an embodiment of the present application, the first event includes:

[0241] After the terminal sends PUCCH.

[0242] Optionally, in the embodiment of the present application, the execution condition of the processing unit of the terminal includes at least one of the following:

[0243] PUCCH has been configured;

[0244] PUCCH is not configured;

[0245] PSFCH has been configured;

[0246] PSFCH is already used;

[0247] PSFCH is not configured;

[0248] PSFCH is not used.

[0249] Optionally, in the embodiment of the present application, the first event is associated with an execution condition of the processing unit of the terminal.

[0250] The terminal 400 of the embodiment of the present application can implement the corresponding functions of the terminal in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (submodules, units or components, etc.) in the terminal 400 can be found in the corresponding description in the above-mentioned method 200 embodiment, which will not be repeated here. It should be noted that the functions described by the various modules (submodules, units or components, etc.) in the terminal 400 of the embodiment of the application can be implemented by different modules (submodules, units or components, etc.), or by the same module (submodule, unit or component, etc.).

[0251] Fig.10 6 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 includes a processor 610, and the processor 610 can call and run a computer program from a memory to enable the communication device 600 to implement the method in the embodiment of the present application.

[0252] Optionally, the communication device 600 may further include a memory 620. The processor 610 may call and run a computer program from the memory 620, so that the communication device 600 implements the method in the embodiment of the present application.

[0253] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0254] Optionally, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0255] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include an antenna, and the number of the antennas may be one or more.

[0256] Optionally, the communication device 600 may be a terminal of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the terminal in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0257] Fig.11 7 is a schematic structural diagram of a chip 700 according to an embodiment of the present application. The chip 700 includes a processor 710, and the processor 710 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0258] Optionally, the chip 700 may further include a memory 720. The processor 710 may call and run a computer program from the memory 720 to implement the method executed by the terminal in the embodiment of the present application.

[0259] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0260] Optionally, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0261] Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0262] Optionally, the chip can be applied to the terminal in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the terminal in the various methods in the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0263] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0264] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0265] The memory mentioned above 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 ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM) or a flash memory. The volatile memory may be a random access memory (RAM).

[0266] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0267] Fig.12 8 is a schematic block diagram of a communication system 800 according to an embodiment of the present application. The communication system 800 includes a terminal device 810, a terminal device 820 and a network device 830.

[0268] The terminal device 810 is used to receive downlink information, where the downlink information is used to indicate resource authorization for a side link; and to control a state of a DRX-related timer for the side link based on a first event.

[0269] The terminal device 820 can perform side communication with the terminal device 810.

[0270] The network device 830 may send the downlink information.

[0271] The terminal device 810 can be used to implement the corresponding functions implemented by the transmitting terminal in the above method, the terminal device 820 can be used to implement the corresponding functions implemented by the receiving terminal in the above method, and the network device 830 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, it will not be repeated here.

[0272] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, data center, etc. that contains one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0273] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0274] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

Claims

1. A sidelink transmission method, comprising: The terminal receives downlink information, where the downlink information is used to indicate resource authorization of the sidelink; The terminal controls a state of a timer related to discontinuous reception (DRX) for the sidelink based on a first event, The first event includes: The terminal receives a PDCCH including the downlink information, The terminal controls, based on the first event, a state of a timer related to the discontinuous reception (DRX) of the sidelink, including: A round trip time (RTT) timer for the sidelink is started at a next symbol in timing after receiving the PDCCH.

2. The method according to claim 1, wherein: The downlink information is carried by a physical downlink control channel PDCCH.

3. The method according to claim 1, wherein: The DRX-related timer also includes a retransmission timer.

4. The method according to any one of claims 1 to 3, wherein: Controlling a state of a DRX-related timer for the sidelink, including: When the RTT timer times out, a retransmission timer for the sidelink is started.

5. The method according to any one of claims 1 to 3, wherein: Controlling a state of a DRX-related timer for the sidelink, including: A retransmission timer for the sidelink is started.

6. The method according to claim 4, wherein: The method further comprises: The terminal determines whether to start a retransmission timer for the sidelink based on the feedback information.

7. The method according to claim 6, wherein: The terminal determines, based on the feedback information, whether to start a retransmission timer for the sidelink, including at least one of the following: In a case where the feedback information is confirmation ACK information, not starting a retransmission timer for the sidelink; When the feedback information is non-acknowledgement (NACK) information, start a retransmission timer for the sidelink; In case of receiving the feedback information, starting a retransmission timer for the sidelink; In case the feedback information is not received, the retransmission timer for the sidelink is not started.

8. The method according to claim 4, wherein: controlling a state of a DRX-related timer for the sidelink, further comprising: Stop the running retransmission timer of the sidelink.

9. The method according to any one of claims 1 to 3, wherein: The first event also includes: The terminal sends a physical sidelink control channel PSCCH and / or a physical sidelink shared channel PSSCH.

10. The method according to any one of claims 1 to 3, wherein: The first event also includes: The terminal receives a physical sidelink feedback channel PSFCH.

11. The method according to any one of claims 1 to 3, wherein: The first event includes: The terminal sends a physical uplink control channel PUCCH.

12. The method according to claim 1, wherein: The execution conditions of the method include at least one of the following: PUCCH has been configured; PUCCH is not configured; PSFCH has been configured; PSFCH is already used; PSFCH is not configured; PSFCH is not used.

13. The method according to any one of claims 1 to 3, wherein: The first event is associated with an execution condition of the method.

14. A terminal, comprising: A receiving unit, configured to receive downlink information, wherein the downlink information is used to indicate resource authorization of a sidelink; a processing unit, configured to control a state of a timer related to discontinuous reception DRX for the sidelink based on a first event, The first event includes: The terminal receives a PDCCH including the downlink information, The processing unit is also used for: A round trip time (RTT) timer for the sidelink is started at a next symbol in timing after receiving the PDCCH.

15. The terminal according to claim 14, wherein: The downlink information is carried by a physical downlink control channel PDCCH.

16. The terminal according to claim 14, wherein: The DRX-related timer also includes a retransmission timer.

17. The terminal according to any one of claims 14 to 16, wherein: The processing unit is also used for: When the RTT timer times out, a retransmission timer for the sidelink is started.

18. The terminal according to any one of claims 14 to 16, wherein: The processing unit is further configured to start a retransmission timer for the sidelink.

19. The terminal according to claim 17, wherein: The processing unit is further configured to determine whether to start a retransmission timer for the sidelink based on the feedback information.

20. The terminal according to claim 19, wherein: The processing unit is further configured to perform at least one of the following: In a case where the feedback information is confirmation ACK information, not starting a retransmission timer for the sidelink; When the feedback information is non-acknowledgement (NACK) information, start a retransmission timer for the sidelink; In case of receiving the feedback information, starting a retransmission timer for the sidelink; In case the feedback information is not received, the retransmission timer for the sidelink is not started.

21. The terminal according to claim 17, wherein: The processing unit is further configured to stop a retransmission timer of the side link that is in operation.

22. The terminal according to any one of claims 14 to 16, wherein: The first event includes: The terminal sends a physical sidelink control channel PSCCH and / or a physical sidelink shared channel PSSCH.

23. The terminal according to any one of claims 14 to 16, wherein: The first event includes: The terminal receives a physical sidelink feedback channel PSFCH.

24. The terminal according to any one of claims 14 to 16, wherein: The first event includes: The terminal sends a physical uplink control channel PUCCH.

25. The terminal according to claim 14, wherein: The execution condition of the processing unit of the terminal includes at least one of the following: PUCCH has been configured; PUCCH is not configured; PSFCH has been configured; PSFCH is already used; PSFCH is not configured; PSFCH is not used.

26. The terminal according to any one of claims 14 to 16, wherein: The first event is associated with an execution condition of a processing unit of the terminal.

27. A terminal, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 13.

28. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 13.

29. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 13.

30. A computer program product comprising computer program instructions for causing a computer to execute the method according to any one of claims 1 to 13.

Images