METHOD FOR DETERMINING SIDELINK DRX CONFIGURATION AND COMMUNICATION DEVICE - Patent application

Abstract

The present application provides a method and a communication device for determining a sidelink DRX configuration. The method includes the steps of determining at least two PQIs or sidelink QoS profiles corresponding to a service of a terminal, then determining at least two sidelink DRX configurations corresponding to the at least two PQIs or sidelink QoS profiles, and then determining a sidelink DRX configuration to use based on the at least two sidelink DRX configurations. In this way, a suitable sidelink DRX configuration can be determined for use, which helps to improve the efficiency of communication between terminals. Also, when a transmitting terminal and a receiving terminal each determine a sidelink DRX configuration to use according to the method, both the transmitting terminal and the receiving terminal use the same sidelink DRX configuration. Therefore, the sidelink active times of the transmitting terminal and the receiving terminal can be aligned.

Description

[Technical Field]

[0001] [Related Applications] This application claims priority to Chinese Patent Application No. 202110252910.9, filed with the State Intellectual Property Office of China on March 9, 2021, and entitled "UE2NW RELAY COMMUNICATION METHOD, UE, AND NETWORK DEVICE," and claims priority to Chinese Patent Application No. 202110351627.1, filed with the State Intellectual Property Office of China on March 31, 2021, and entitled "METHOD FOR DETERMINING SIDELINK DRX CONFIGURATION AND COMMUNICATION APPARATUS," and claims priority to Chinese Patent Application No. 202111116713.0, filed with the State Intellectual Property Office of China on September 23, 2021, and entitled "METHOD FOR DETERMINING SIDELINK DRX CONFIGURATION AND COMMUNICATION APPARATUS," each of which is incorporated herein by reference in its entirety.

[0002] [Technical field] The present application relates to the field of wireless communication technologies, and in particular to a method and a communication device for determining a sidelink DRX configuration. [Background technology]

[0003] The 3rd Generation Partnership Project (3GPP) has been developing sidelink (SL) standards since the Long Term Evolution (LTE) era to implement direct communication between terminals in various application scenarios.

[0004] During communication between terminals, it is necessary to determine a sidelink discontinuous reception (DRX) configuration to use, and determine the sidelink active time of the terminal based on the sidelink DRX configuration.

[0005] However, currently there is no good method for determining the sidelink DRX configuration. Summary of the Invention

[0006] The present application provides a method and a communication device for determining a sidelink DRX configuration to improve the efficiency of communication between terminals by selecting an appropriate sidelink DRX configuration to use.

[0007] According to a first aspect, an embodiment of the present application provides a method for determining a sidelink DRX configuration, the method may be performed by a terminal or a module used within the terminal, the method comprising: determining at least two PQIs or sidelink QoS profiles corresponding to the services of the terminal; determining at least two sidelink DRX configurations corresponding to the at least two PQIs or sidelink QoS profiles, each sidelink DRX configuration indicating one or more sidelink DRX parameters; determining a sidelink DRX configuration to use based on the at least two sidelink DRX configurations; Includes:

[0008] According to this solution, The at least two PQIs or sidelink QoS profiles corresponding to the services of the terminal are determined; Then, at least two sidelink DRX configurations corresponding to the at least two PQIs or sidelink QoS profiles are determined; Next, a sidelink DRX configuration to use is determined based on the at least two sidelink DRX configurations. In this way, an appropriate sidelink DRX configuration can be determined for use, which helps improve the efficiency of communication between terminals. Furthermore, once the transmitting terminal and the receiving terminal each determine a sidelink DRX configuration to use according to this method, both the transmitting terminal and the receiving terminal use the same sidelink DRX configuration. Therefore, the sidelink active times of the transmitting terminal and the receiving terminal can be aligned.

[0009] In a possible implementation, the sidelink DRX configuration to use is a first sidelink DRX configuration, which is one of the at least two sidelink DRX configurations.

[0010] According to this solution, one sidelink DRX configuration is selected for use from the at least two sidelink DRX configurations, and since only one sidelink DRX configuration is used, power consumption of the terminal can be reduced.

[0011] In a possible implementation, the value of a first parameter in the first sidelink DRX configuration is the minimum or maximum value of the values of the first parameter in the at least two sidelink DRX configurations, where the first parameter is one of the following parameters: the value of sl-DRX-OnDurationTimer, the value of sl-DRX-InactivityTimer, the value of sl-DRX-HARQ-RTT-Timer, the value of sl-DRX-RetransmissionTimer, the value of SLDRXcycle, the value of sl-DRX-startOffset, or the value of sl-DRX-slotOffset.

[0012] In a possible implementation, when the values of the first parameter in the plurality of sidelink DRX configurations in the at least two sidelink DRX configurations are the minimum or maximum value, the sidelink DRX configuration is determined to be the first sidelink DRX configuration when a value of the second parameter in only one sidelink DRX configuration among the plurality of sidelink DRX configurations is the smallest or largest value, or When a value of a second parameter in a plurality of sidelink DRX configurations among the plurality of sidelink DRX configurations is the minimum or maximum value, one of the plurality of sidelink DRX configurations is determined to be the first sidelink DRX configuration.

[0013] In a possible implementation, if the values of the first parameter in the plurality of sidelink DRX configurations in the at least two sidelink DRX configurations are the minimum or maximum value, The sidelink DRX configuration located at the top or bottom of the sidelink DRX configuration list is selected as the first sidelink DRX configuration from the plurality of sidelink DRX configurations.

[0014] In a possible implementation, if the values of the first parameter in the plurality of sidelink DRX configurations in the at least two sidelink DRX configurations are the minimum or maximum value, The sidelink DRX configuration corresponding to the PQI with the smallest or largest value is selected as the first sidelink DRX configuration from the plurality of sidelink DRX configurations.

[0015] In a possible implementation, if the values of the first parameter in the plurality of sidelink DRX configurations in the at least two sidelink DRX configurations are the minimum or maximum value, a sidelink DRX configuration corresponding to a PQI with a smallest or largest index is selected as the first sidelink DRX configuration from the plurality of sidelink DRX configurations; or The sidelink DRX configuration corresponding to the sidelink QoS profile with the smallest or largest index is selected as the first sidelink DRX configuration from the plurality of sidelink DRX configurations.

[0016] In a possible implementation, the first sidelink DRX configuration is determined based on at least one of the following parameters: - separate positions of the at least two sidelink DRX configurations in a sidelink DRX configuration list; PQI values respectively corresponding to the at least two sidelink DRX configurations; indices of sidelink QoS profiles respectively corresponding to the at least two sidelink DRX configurations; or an index of a PQI corresponding to each of the at least two sidelink DRX configurations;

[0017] In a possible implementation, the first sidelink DRX configuration is generated based on the at least two sidelink DRX configurations, and values of parameters in the first sidelink DRX configuration are derived from one or more of the at least two sidelink DRX configurations.

[0018] According to this solution, one sidelink DRX configuration is generated for use based on the at least two sidelink DRX configurations. Since only one sidelink DRX configuration is used, power consumption of the terminal can be reduced. Furthermore, since the sidelink DRX configuration to be used is regenerated, flexibility in selecting the sidelink DRX configuration can be increased.

[0019] In a possible implementation, the value of the first parameter included in the first sidelink DRX configuration is the minimum or maximum value of the values of the first parameter included in each of the at least two sidelink DRX configurations.

[0020] In a possible implementation, the sidelink DRX configuration to use is the at least two sidelink DRX configurations.

[0021] According to this solution, at least two sidelink DRX configurations can all function as sidelink DRX configurations to be used. Using multiple sidelink DRX configurations can increase the sidelink active time of terminals, thereby increasing the success rate of communication between terminals and improving communication efficiency.

[0022] In a possible implementation, each of the at least two sidelink DRX configurations comprises a duration of one or more of the following timers: sl-DRX-onDurationTimer, sl-DRX-inactivityTimer, sl-DRX-HARQ-RTT-Timer, or sl-DRX-RetransmissionTimer. The sidelink active time corresponding to the terminal comprises one or a union of the following execution times: execution time of the sl-DRX-onDurationTimer corresponding to each sidelink DRX configuration, execution time of the sl-DRX-inactivityTimer corresponding to each sidelink DRX configuration, or execution time of the sl-DRX-RetransmissionTimer corresponding to each sidelink DRX configuration.

[0023] In a possible implementation, each of the at least two sidelink DRX configurations comprises a duration of one or more of the following timers: sl-DRX-onDurationTimer, sl-DRX-inactivityTimer, sl-DRX-HARQ-RTT-Timer, or sl-DRX-RetransmissionTimer. The sidelink active time corresponding to the terminal comprises one or a union of the following execution times: an execution time of the sl-DRX-onDurationTimer corresponding to each sidelink DRX configuration, an execution time of a first sl-DRX-inactivityTimer corresponding to a second sidelink DRX configuration, or an execution time of a first sl-DRX-RetransmissionTimer corresponding to a third sidelink DRX configuration. The second sidelink DRX configuration and the third sidelink DRX configuration are different ones of the at least two sidelink DRX configurations.

[0024] In a possible implementation, the first sl-DRX-inactivityTimer value is the minimum or maximum value of the sl-DRX-inactivityTimer values respectively corresponding to the at least two sidelink DRX configurations; and / or The value of the first sl-DRX-RetransmissionTimer is the minimum or maximum value of the sl-DRX-RetransmissionTimer values corresponding to the at least two sidelink DRX configurations, respectively.

[0025] According to a second aspect, an embodiment of the present application provides a method for determining a sidelink DRX configuration, the method may be performed by a terminal or a module used within the terminal, the method comprising: obtaining configuration information, the configuration information including an index of a PQI corresponding to at least one sidelink DRX configuration; determining a first sidelink DRX configuration corresponding to the index of the first PQI based on an index of the first PQI and an index of the PQI corresponding to at least one sidelink DRX configuration; Includes:

[0026] According to this solution, a terminal can determine a SL DRX configuration corresponding to each PQI, and the configuration information does not carry the PQI but carries the index of the PQI corresponding to each sidelink DRX configuration, thereby reducing signaling overhead and storage overhead.

[0027] In a possible implementation, the method comprises: determining the first PQI corresponding to the terminal; determining an index of the first PQI based on the first PQI; Includes:

[0028] In a possible implementation, if the PQI is a normalized PQI, the index of the PQI is the value of the normalized PQI; or The index of the PQI is the index of the sidelink QoS profile that includes the normalized PQI.

[0029] In a possible implementation, if the PQI is a standardized PQI, at least one non-standardized PQI is obtained, each non-standardized PQI corresponding to one indication, the indication indicating a standardized PQI corresponding to the same sidelink DRX configuration as the non-standardized PQI, or Each non-standardized PQI corresponds to one default sidelink DRX configuration, or Each non-standardized PQI corresponds to one common sidelink DRX configuration.

[0030] In a possible implementation, if the PQI is a non-standardized PQI, the index of the PQI is the index of a sidelink QoS profile that includes the non-standardized PQI, or The index of the PQI is the index of the non-standardized PQI included in the sidelink RB configuration, or The index of the PQI is indicated by the index of a sidelink RB configuration corresponding to a sidelink QoS profile including the non-standardized PQI and the index of the non-standardized PQI in the sidelink RB configuration.

[0031] According to a third aspect, an embodiment of the present application provides a method for determining a sidelink DRX configuration, the method may be performed by a terminal or a module used within the terminal, the method comprising: obtaining configuration information, the configuration information including an index of a sidelink QoS profile corresponding to at least one sidelink DRX configuration; determining a first sidelink DRX configuration corresponding to the first sidelink QoS profile index based on an index of a first sidelink QoS profile and an index of the sidelink QoS profile corresponding to at least one sidelink DRX configuration; Includes.

[0032] According to this solution, the terminal can determine the SL DRX configuration corresponding to each sidelink QoS profile, and the configuration information does not carry the sidelink QoS profile but carries the index of the sidelink QoS profile corresponding to each sidelink DRX configuration, thereby reducing signaling overhead and storage overhead.

[0033] In a possible implementation, the method comprises: determining the first sidelink QoS profile corresponding to the terminal; determining an index of the first sidelink QoS profile based on the first sidelink QoS profile; Includes.

[0034] In a possible implementation, the index of the sidelink QoS profile is indicated by the position of the sidelink QoS profile within a sidelink RB configuration list corresponding to the sidelink QoS profile, or The index of the sidelink QoS profile is indicated by the index of the sidelink RB configuration corresponding to the sidelink QoS profile and the position of the sidelink QoS profile within the sidelink RB configuration corresponding to the sidelink QoS profile.

[0035] According to a fourth aspect, an embodiment of the present application provides a method for determining a sidelink DRX configuration, the method may be performed by a terminal or a module used within the terminal, the method comprising: acquiring configuration information, the configuration information including an index of a side RB configuration corresponding to at least one sidelink DRX configuration, each side RB configuration corresponding to at least one PQI; determining a first sidelink DRX configuration corresponding to the index of the first PQI based on a first PQI and an index of the sidelink RB configuration corresponding to at least one sidelink DRX configuration; Includes.

[0036] According to this solution, a terminal can determine an SL DRX configuration corresponding to each PQI, and the configuration information does not transmit a sidelink RB configuration but transmits an index of a sidelink RB configuration corresponding to each sidelink RB configuration, thereby reducing signaling overhead and storage overhead.

[0037] In a possible implementation, the method comprises: determining an index of a first sidelink RB configuration corresponding to the first PQI; determining the first sidelink DRX configuration corresponding to the index of the first sidelink RB configuration based on an index of the first sidelink RB configuration and an index of the sidelink RB configuration corresponding to the at least one sidelink DRX configuration; Includes.

[0038] In a possible implementation, the index of the first sidelink RB configuration is indicated by the position of the first sidelink RB configuration in the sidelink RB configuration list.

[0039] According to a fifth aspect, an embodiment of the present application provides a method for determining a sidelink DRX configuration, the method may be performed by a terminal or a module used within the terminal, the method comprising: acquiring configuration information, the configuration information including an index of a side RB configuration corresponding to at least one sidelink DRX configuration, each side RB configuration corresponding to at least one sidelink QoS profile; determining a first sidelink DRX configuration corresponding to the index of the first sidelink QoS profile based on a first sidelink QoS profile and an index of the sidelink RB configuration corresponding to at least one sidelink DRX configuration; Includes.

[0040] According to this solution, a terminal can determine an SL DRX configuration corresponding to each sidelink QoS profile, and the configuration information does not transmit the sidelink RB configuration but transmits an index of the sidelink RB configuration corresponding to each sidelink RB configuration, thereby reducing signaling overhead and storage overhead.

[0041] In a possible implementation, the method comprises: determining an index of a first sidelink RB configuration corresponding to the first sidelink QoS profile; determining the first sidelink DRX configuration corresponding to the index of the first sidelink RB configuration based on an index of the first sidelink RB configuration and an index of the sidelink RB configuration corresponding to the at least one sidelink DRX configuration; Includes.

[0042] In a possible implementation, the index of the first sidelink RB configuration is indicated by the position of the first sidelink RB configuration in the sidelink RB configuration list.

[0043] According to a sixth aspect, an embodiment of the present application provides a communication device including a processor and an interface circuit, the interface circuit configured to receive a signal from a communication device other than the communication device and transmit the signal to the processor, or transmit a signal from the processor to a communication device other than the communication device, the processor configured to implement the method of any of the first to fifth aspects by using logic circuits or by executing code instructions.

[0044] According to a seventh aspect, an embodiment of the present application provides a communications device including a processor coupled to a memory, the processor configured to invoke a program stored in the memory and execute a method according to any of the implementations of the first to fifth aspects. The memory may be located internal or external to the device. Furthermore, there may be one or more processors.

[0045] According to an eighth aspect, an embodiment of the present application provides a communications device including a processor and a memory, the memory storing computer instructions, and when the communications device is operating, the processor executes the computer instructions stored in the memory, thereby causing the communications device to perform a method according to any one of the first to fifth aspects.

[0046] According to a ninth aspect, an embodiment of the present application provides a communication device. The device may be a terminal or a module used in a terminal. The function has a function for performing a method in any of the implementations of the first to fifth aspects. The function may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the function.

[0047] According to a tenth aspect, an embodiment of the present application provides a communication device including a module configured to perform a method in any implementation of the first to fifth aspects.

[0048] According to an eleventh aspect, an embodiment of the present application provides a terminal configured to perform a method in an implementation of any of the first to fifth aspects.

[0049] According to a twelfth aspect, an embodiment of the present application further provides a computer program product, the computer program product including a computer program that, when executed by a processor, performs a method according to any one of the implementations of the first to fifth aspects.

[0050] According to a thirteenth aspect, an embodiment of the present application further provides a computer-readable storage medium, the storage medium storing a computer program or instructions, which, when executed by a processor, performs a method according to any one of the first to fifth aspects. [Brief explanation of the drawings]

[0051] [Figure 1] 1 is a schematic diagram of the architecture of a communication system to which embodiments of the present application are applied;

[0052] [Figure 2] FIG. 10 is a schematic diagram of the execution time of sl-DRX-OnDurationTimer.

[0053] [Figure 3] FIG. 10 is a schematic diagram of the execution time of the sl-DRX-InactivityTimer.

[0054] [Figure 4] FIG. 10 is a schematic diagram of the execution time of the sl-DRX-RetransmissionTimer.

[0055] [Figure 5] FIG. 10 is a schematic diagram of the execution time of the sl-DRX-HARQ-RTT-Timer.

[0056] [Figure 6] FIG. 2 is a schematic diagram of a method for determining a SL DRX configuration according to an embodiment configuration of the present application;

[0057] [Figure 7] FIG. 2 is a schematic diagram of a method for determining a SL DRX configuration according to an embodiment configuration of the present application;

[0058] [Figure 8] FIG. 10 is a schematic diagram of the execution times of sl-DRX-OnDurationTimers corresponding to different SL DRX configurations.

[0059] [Figure 9] FIG. 10 is a schematic diagram of the execution times of the sl-DRX-InactivityTimers and the sl-DRX-OnDurationTimer corresponding to different SL DRX configurations.

[0060] [Figure 10] 10 is a schematic diagram of the execution times of the sl-DRX-RetransmissionTimers and the sl-DRX-OnDurationTimer corresponding to different SL DRX configurations. FIG.

[0061] [Figure 11] FIG. 2 is a schematic diagram of a method for determining a SL DRX configuration according to an embodiment configuration of the present application;

[0062] [Figure 12] FIG. 10 is a schematic diagram of the execution times of the sl-DRX-OnDurationTimers and the first sl-DRX-InactivityTimer corresponding to different SL DRX configurations.

[0063] [Figure 13] 10 is a schematic diagram of the execution times of the sl-DRX-OnDurationTimers and the sl-DRX-RetransmissionTimer corresponding to different SL DRX configurations. FIG.

[0064] [Figure 14] FIG. 10 is a schematic diagram of the execution times of the sl-DRX-OnDurationTimer and sl-DRX-InactivityTimer corresponding to different SL DRX configurations.

[0065] [Figure 15] FIG. 10 is a schematic diagram of the execution times of the sl-DRX-OnDurationTimer and sl-DRX-InactivityTimer corresponding to different SL DRX configurations.

[0066] [Figure 16] FIG. 2 is a schematic diagram of a method for determining a SL DRX configuration according to an embodiment configuration of the present application;

[0067] [Figure 17] FIG. 2 is a schematic diagram of a method for determining a SL DRX configuration according to an embodiment configuration of the present application;

[0068] [Figure 18A] 1 is a schematic diagram of a method for determining a DRX configuration according to an embodiment configuration of the present application;

[0069] [Figure 18B] 1 is a schematic diagram of a method for determining a DRX configuration according to an embodiment configuration of the present application;

[0070] [Figure 19] 1 is a schematic diagram of a communication device according to an embodiment of the present application;

[0071] [Figure 20] 1 is a schematic diagram of a communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0072] FIG. 1 is a schematic diagram of the architecture of a communication system to which an embodiment of the present application is applied. As shown in FIG. 1, the communication system 1000 includes a radio access network 100 and a core network 200. Optionally, the communication system 1000 may further include the Internet 300. The radio access network 100 includes at least one radio access network device (e.g., 110a and 110b in FIG. 1) and may further include at least one terminal (e.g., 120a to 120j in FIG. 1). The terminal is wirelessly connected to the radio access network device, and the radio access network device is wirelessly or wiredly connected to the core network device. The core network device and the radio access network device may be separate physical devices, or the functions of the core network device and the logical functions of the radio access network device may be integrated into the same physical device, or some functions of the core network device and some functions of the radio access network device may be integrated into one physical device. The connection between the terminal and the radio access network device may be wired or wireless. FIG. 1 is merely a schematic diagram. The communication system may further include other network devices, for example, a wireless relay device and a wireless backhaul device, which are not shown in FIG.

[0073] The radio access network device may be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a fifth generation (5G) mobile communication system, a next generation NodeB in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a wireless fidelity (Wi-Fi) system, or may be a module or unit implementing part of the functions of a base station, such as a central unit (CU) or a distributed unit (DU). The radio access network device may be a macro base station (e.g., 110a in FIG. 1 ), a micro base station, or an indoor base station (e.g., 110b in FIG. 1 ), or may be a relay node, a donor node, or the like. The specific technology and the specific device type used by the radio access network device are not limited to the embodiments of this application. In the embodiment of the present application, an example in which a base station functions as a radio access network device will be described.

[0074] A terminal may also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely applied to various scenarios such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart clothing, smart transportation, and smart city. Terminals may be mobile phones, tablet computers, computers with wireless transceiver capabilities, wearable devices, vehicles, unmanned aerial vehicles, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The specific technology and specific device type used in the terminal are not limited to the embodiments of this application.

[0075] In embodiments of the present application, sidelink (SL) communication may be performed between terminals, where different terminals may correspond to the same serving cell or different serving cells.

[0076] The base station and the terminal may be located at a fixed position or may be mobile. The base station and the terminal may be deployed on the ground, including indoor or outdoor devices, handheld devices, or vehicle-mounted devices, or may be deployed on water, or may be deployed on airborne aircraft, balloons, and satellites. The application scenarios of the base station and the terminal are not limited in the embodiments of the present application.

[0077] The roles of a base station and a terminal may be relative. For example, if the helicopter or unmanned aerial vehicle 120i in FIG. 1 is configured as a mobile base station and the terminal 120j accesses the wireless access network 100 through 120i, the terminal 120i is a base station. However, from the perspective of the base station 110a, 120i is a terminal. Specifically, communication between 110a and 120i is performed according to a radio-air interface protocol. Of course, communication between 110a and 120i may alternatively be performed according to a protocol for the interface between base stations. In this case, from the perspective of 110a, 120i is also a base station. Therefore, both the base station and the terminal may be collectively referred to as communication equipment. 110a and 110b in FIG. 1 may be referred to as communication equipment having base station functionality, and 120a to 120j in FIG. 1 may be referred to as communication equipment having terminal functionality.

[0078] For ease of understanding, the following will first explain and describe some nouns or terms used in the examples of this application.

[0079] 1. Sidelink communication

[0080] Sidelink communication is also called SL communication, sidelink communication, sidelink communication, sidelink communication, sidelink communication.

[0081] Sidelink communication means that two adjacent devices communicate directly without the need for a network node. Sidelink communication using new radio (NR) technology is sometimes called NR sidelink communication.

[0082] Sidelink communication is between a source terminal and a destination terminal. The source terminal is sometimes called the transmitting terminal, and the destination terminal is sometimes called the receiving terminal. The source terminal can be identified using a source layer-2 identifier (source layer-2 ID), and the destination terminal can be identified using a destination layer-2 ID. The transmitting terminal is the source of the sidelink communication (or media access control (MAC) protocol data unit (PDU)), and the receiving terminal is the destination of the sidelink communication (or MAC PDU).

[0083] When a terminal acts as a transmitting terminal, the Layer-2 ID of the terminal is the source layer-2 ID, and the Layer-2 ID of the receiving terminal is the destination layer-2 ID.When a terminal acts as a transmitting terminal, the Layer-2 ID of the terminal is the source layer-2 ID, and the Layer-2 ID of the receiving terminal is the destination layer-2 ID.

[0084] In actual applications, the source layer-2 ID is sometimes abbreviated to source ID, and the destination layer-2 ID is sometimes abbreviated to destination ID.

[0085] The source layer-2 ID is assigned by the sending terminal.

[0086] For sidelink unicast communication, the destination layer-2 ID depends on the receiving terminal. In the process of establishing a PC5 unicast link, Layer-2 IDs are exchanged between two terminals and used for subsequent communication. The terminals mentioned below can be terminals identified using Layer-2 IDs. A Layer-2 ID is assigned to the terminal and used in sidelink communication. A PC5-RRC connection is a logical connection between a source and destination pair. After a PC5 unicast link is established, a corresponding PC5-RRC connection is established. There is a one-to-one correspondence between a PC5-RRC connection and a PC5 unicast link.

[0087] In sidelink multicast communication, if the V2X / D2D application layer of the transmitting or receiving terminal provides group identifier information, the transmitting or receiving terminal can determine the destination layer-2 ID based on the group identifier information. If the V2X / D2D application layer of the transmitting or receiving terminal does not provide group identifier information, the transmitting or receiving terminal can determine the destination layer-2 ID based on the current V2X / D2D service and the mapping relationship between the V2X / D2D service and the destination layer-2 ID.

[0088] In sidelink broadcast communication, the transmitting or receiving terminal can determine the destination layer-2 ID based on the current V2X / D2D service and the mapping relationship between the V2X / D2D service and the destination layer-2 ID.

[0089] 2.SL DRX

[0090] To reduce terminal power consumption, SL DRX was introduced in NR SL. SL DRX currently includes four timers: the sidelink DRX on-duration timer (sl-DRX-OnDurationTimer), the sidelink DRX inactivity timer (sl-DRX-InactivityTimer), the sidelink DRX hybrid automatic repeat request round-trip time timer (sl-DRX-HARQ-RTT-Timer), and the sidelink DRX retransmission timer (sl-DRX-RetransmissionTimer). HARQ stands for hybrid automatic repeat request, and RTT stands for round-trip time.

[0091] The sl-DRX-OnDurationTimer indicates the period generated after the start of an SL DRX cycle. The sl-DRX-InactivityTimer indicates the period generated after a sidelink control information (SCI) indicating a new SL transmission. The sl-DRX-RetransmissionTimer indicates the maximum period generated until an SCI indicating an SL retransmission is received. The sl-DRX-HARQ-RTT-Timer indicates the minimum period generated until an SCI indicating an SL retransmission is expected to be received.

[0092] When SL DRX is configured or activated, the terminal monitors the PSCCH during the SL active time, or monitors the PSCCH and the physical sidelink shared channel (PSSCH) during the SL active time, or monitors the PSCCH and the second stage SCI of the PSCH during the SL active time, and does not perform monitoring outside the SL active time. This reduces the power consumption of the terminal. Monitoring the second stage SCI on the PSCCH and PSCH can also be understood as monitoring the SCI. The SCI includes the first stage SCI and the second stage SCI, where the first stage SCI is transmitted on the PSCCH and the second stage SCI is transmitted on the PSCH.

[0093] The SL active time includes any one or union of the following execution times: the execution time of the sl-DRX-OnDurationTimer, the execution time of the sl-DRX-InactivityTimer, or the execution time of the sl-DRX-RetransmissionTimer. Specifically, the SL active time includes any of the following: Description of the embodiment (1) sl-DRX-OnDurationTimer execution time; (2) sl-DRX-InactivityTimer execution time; (3) sl-DRX-RetransmissionTimer execution time; (4) the union of the execution time of sl-DRX-OnDurationTimer and the execution time of sl-DRX-InactivityTimer; (5) The union of the execution time of sl-DRX-InactivityTimer and sl-DRX-RetransmissionTimer; (6) the union of the execution time of the sl-DRX-OnDurationTimer and the execution time of the sl-DRX-RetransmissionTimer; or (7) The union of the execution time of the sl-DRX-OnDurationTimer, the execution time of the sl-DRX-InactivityTimer, and the execution time of the sl-DRX-RetransmissionTimer.

[0094] The execution times of the above different timers will be explained below with reference to the accompanying drawings.

[0095] Figure 2 is a schematic diagram of the execution time of the sl-DRX-OnDurationTimer. The sl-DRX-OnDurationTimer is started and stopped periodically. The sl-DRX-OnDurationTimer continues to run within the period of each SL DRX cycle. The SL active time includes the execution time of the sl-DRX-OnDurationTimer. Figure 2 is used as an example. The SL active time includes the period between T1 and T2 and the period between T3 and T4.

[0096] FIG. 3 is a schematic diagram of the execution time of the sl-DRX-InactivityTimer. The sl-DRX-InactivityTimer is started after receiving an SCI indicating a new transmission. In FIG. 3, the terminal receives an SCI indicating a new transmission at time T5 within the execution time of the sl-DRX-OnDurationTimer. The terminal analyzes the SCI and learns that the SCI indicates a new transmission. In this case, the terminal starts the sl-DRX-InactivityTimer at time T6, and the execution time of the sl-DRX-InactivityTimer may be indicated by the SL DRX configuration. In the example of FIG. 3, the execution time of the sl-DRX-InactivityTimer includes the period between T6 and T7. It can be seen that the execution time of the sl-DRX-InactivityTimer and the execution time of the sl-DRX-OnDurationTimer may overlap. The SL active time includes the execution time of the sl-DRX-OnDurationTimer and the execution time of the sl-DRX-InactivityTimer. FIG. 3 is used as an example. The SL active time includes the period between T1 and T7 and the period between T3 and T4.

[0097] FIG. 4 is a schematic diagram of the execution time of the sl-DRX-RetransmissionTimer. In the example of FIG. 4, the sl-DRX-RetransmissionTimer is started at time T6. Time T6 may be the timeout time of the sl-DRX-HARQ-RTT-Timer, the first symbol generated after the end of the PSSCH scheduled by the SCI, or the first symbol generated after the end of the HARQ feedback of the data scheduled by the SCI, where the SCI indicates a new transmission or a retransmission. The execution time of the sl-DRX-RetransmissionTimer may be indicated by the SL DRX configuration. In the example of FIG. 4, the execution time of the sl-DRX-RetransmissionTimer includes the period between T6 and T7. It can be seen that the execution time of the sl-DRX-RetransmissionTimer and the execution time of the sl-DRX-OnDurationTimer may overlap. The SL active time includes the execution time of the sl-DRX-OnDurationTimer and the execution time of the sl-DRX-RetransmissionTimer. FIG. 4 is used as an example. The SL active time includes the period between T1 and T7 and the period between T3 and T4.

[0098] FIG. 5 is a schematic diagram of the execution time of the sl-DRX-HARQ-RTT-Timer. In the example of FIG. 5, the sl-DRX-HARQ-RTT-Timer is started at time T6. Time T6 may be the first symbol generated after the end of the PSSCH scheduled by the SCI or the first symbol generated after the end of the HARQ feedback of the data scheduled by the SCI, where the SCI indicates a new transmission or a retransmission. The execution time of the sl-DRX-HARQ-RTT-Timer may be indicated by the SL DRX configuration. In the example of FIG. 5, the execution time of the sl-DRX-HARQ-RTT-Timer includes the period between T6 and T7. It can be seen that the execution time of the sl-DRX-HARQ-RTT-Timer is included in the execution time of the sl-DRX-OnDurationTimer. The SL active time includes the execution time of the sl-DRX-OnDurationTimer. FIG. 5 is used as an example. The SL active time includes the period between T1 and T2 and the period between T3 and T4.

[0099] 3.SL DRX configuration

[0100] In practical applications, the SL DRX configuration is sometimes called the DRX configuration for short.

[0101] The SL DRX configuration may include at least one of the following parameters: a value of the sl-DRX-OnDurationTimer, a value of the sl-DRX-InactivityTimer, a value of the sl-DRX-HARQ-RTT-Timer, a value of the sl-DRX-RetransmissionTimer, a value of the sidelink DRX start offset (sl-DRX-startOffset), a value of the sidelink DRX cycle (SL DRX cycle), or a value of the sidelink DRX slot offset (sl-DRX-slotOffset).

[0102] The value of sl-DRX-OnDurationTimer indicates the duration of the sl-DRX-OnDurationTimer, the value of sl-DRX-InactivityTimer indicates the duration of the sl-DRX-InactivityTimer, the value of sl-DRX-HARQ-RTT-Timer indicates the duration of the sl-DRX-HARQ-RTT-Timer and the value of sl-DRX-RetransmissionTimer indicates the duration of the sl-DRX-RetransmissionTimer. The value of sl-DRX-startOffset indicates the subframe in which the SL DRX cycle starts, i.e. the subframe in which the sl-DRX-OnDurationTimer starts. The value of sl-DRX-SlotOffset indicates the slot delay generated before the sl-DRX-OnDurationTimer starts.

[0103] The terminal may monitor or transmit SL control information (eg, SCI) based on the SL DRX configuration.

[0104] 4.SL Quality of Service (QoS) Profile

[0105] In actual applications, the SL QoS profile is sometimes abbreviated to QoS profile.

[0106] The SL QoS profile includes one or more of a PC5 interface 5G QoS identifier (PQI), a guaranteed flow bit rate (GFBR), a maximum flow bit rate (MFBR), a PC5 link aggregate maximum bit rate (PC5 Link-AMBR), or a distance (range). The distance value indicates the distance to which the PC5 QoS parameters of the PC5 communication apply. Specifically, if the distance between the receiving terminal and the transmitting terminal exceeds the distance (range) indicated by the SL QoS profile, the PC5 communication becomes best effort.

[0107] The PQI indicates one or more of the following PC5 QoS parameters: resource type, priority level, packet delay budget (PDB), and packet error rate (PER), averaging window, or maximum data burst volume (MDBV). Resource type can be guaranteed bit rate (GBR), delay critical GBR, or non-GBR.

[0108] The PQI may be a standardized PQI or a non-standardized PQI. The standardized PQI is represented by an integer.

[0109] In the embodiments of the present application, parameters indicated by a PQI, some parameters among the parameters indicated by a PQI, parameters indicated by an SL QoS profile, or some parameters among the parameters indicated by an SL QoS profile may be collectively referred to as a QoS parameter group. Therefore, it can be understood that one QoS parameter group corresponds to one PQI or one SL QoS profile. In the embodiments of the present application, if a QoS parameter group includes parameters indicated by a PQI, the QoS parameter group may also be referred to as a PQI. If a QoS parameter group includes parameters indicated by an SL QoS profile, the QoS parameter group may also be referred to as an SL QoS profile.

[0110] 5. SL Radio Bearer (RB) Configuration

[0111] In practical applications, the SL RB configuration is sometimes called the RB configuration for short.

[0112] For example, the terminal may obtain the SL RB configuration from signaling sent by the base station and including the SL RB configuration, or the SL RB configuration is pre-configured for the terminal.

[0113] Each SL RB configuration includes an index of the SL RB configuration and an indication of whether the SL RB is the default SL RB. Optionally, each SL RB configuration may further include a QoS flow or an SL QoS profile mapped to the SL RB.

[0114] Optionally, the SL RB configuration configured in the terminal may be indicated in the form of an SL RB list (e.g., sl-RadioBearerToAddModList or sl-RadioBearerPreConfigList). One SL RB list includes one or more SL RB configurations (e.g., SL-RadioBearerConfig).

[0115] 6. Relationship between SL RB configuration and SL QoS profile

[0116] One SL RB configuration may correspond to one or more SL QoS profiles, and one SL QoS profile corresponds to one SL RB configuration. Different SL QoS profiles may correspond to the same SL RB configuration or different SL RB configurations.

[0117] <Example 1>

[0118] For example, there are M SL RB configurations from SL RB configuration 1 to SL RB configuration M, where M is a positive integer.

[0119] SL RB configuration 1 corresponds to SL QoS profile 1, SL QoS profile 2, and SL QoS profile 3. SL RB configuration 2 corresponds to SL QoS profile 4 and SL QoS profile 5. ...and The SL RB configuration M corresponds to the SL QoS profile K-2, the SL QoS profile K-1, and the SL QoS profile K.

[0120] 7. Relationship between SL DRX configuration and QoS parameter group

[0121] One SL DRX configuration corresponds to one or more QoS parameter groups, one QoS parameter group corresponds to one SL DRX configuration, and different QoS parameter groups may correspond to the same SL DRX configuration or different SL DRX configurations. One QoS parameter group includes one or more of the following: SL QoS profile, PQI, resource type, priority level, PDB, PER, averaging window, MDBV, GFBR, MFBR, PC5 Link-AMBR, or range. In this embodiment of the present application, an example will be described in which the QoS parameter group is a PQI or an SL QoS profile.

[0122] <Example 2>

[0123] When an SL DRX configuration is configured in a terminal with the granularity of an SL QoS profile, the configured SL DRX configuration is associated with the SL QoS profile. For example, there are N SL DRX configurations, from SL DRX configuration 1 to SL DRX configuration N, where N is a positive integer.

[0124] SL DRX configuration 1 corresponds to SL QoS profile 1 and SL QoS profile 2. SL DRX configuration 2 corresponds to SL QoS profile 3. ...and The SL DRX configuration N corresponds to the SL QoS profile L-1 and the SL QoS profile L.

[0125] <Example 3>

[0126] If an SL DRX configuration is configured in a terminal with the granularity of the PQI, the SL DRX configuration is associated with the PQI. For example, there are N SL DRX configurations, from SL DRX configuration 1 to SL DRX configuration N, where N is a positive integer.

[0127] SL DRX configuration 1 corresponds to PQI1 and PQI2. SL DRX configuration 2 corresponds to PQI3. ...and SL DRX configuration N corresponds to PQI L-1 and PQI L.

[0128] 8. Relationship between destination layer-2 ID, terminal service, and SL DRX configuration

[0129] Different services executed between different terminals can use the same destination layer-2 ID used for sidelink multicast / broadcast communication. Different services may correspond to different QoS parameter groups, and the same service may correspond to multiple different QoS parameter groups. Therefore, one destination layer-2 ID can correspond to multiple QoS parameter groups. Furthermore, different QoS parameter groups may correspond to different SL DRX configurations. Therefore, one destination layer-2 ID can correspond to multiple SL DRX configurations.

[0130] Currently, the SL DRX configuration for sidelink multicast / broadcast communication needs to solve the following two problems:

[0131] First, in sidelink multicast / broadcast communication, services executed by different terminals may correspond to the same destination layer-2 ID, or different terminals in a group may correspond to the same destination layer-2 ID, and one destination layer-2 ID may correspond to multiple SL DRX configurations. Therefore, different terminals may correspond to multiple SL DRX configurations for the same destination layer-2 ID. If different terminals executing the same service use different SL DRX configurations, the SL active times of the different terminals may not be synchronized, which may cause communication errors between the terminals. For example, if a transmitting terminal transmits sidelink data information or sidelink control information to a receiving terminal at a time other than the SL active time maintained by the receiving terminal, the receiving terminal cannot receive the sidelink data information or sidelink control information.

[0132] Second, when an SL DRX configuration is configured for a terminal at the granularity of a QoS parameter group (e.g., an SL QoS profile or PQI), the correspondence between the SL DRX configuration and the QoS parameter group needs to be configured for the terminal, which results in a large signaling overhead since there are a large number of QoS parameter groups and each QoS parameter group also contains a large amount of content.

[0133] To solve the first problem, the embodiments of the present application provide different solutions corresponding to Embodiments 1 to 4, respectively.

[0134] Embodiment 1 6 is a schematic diagram of a method for determining a SL DRX configuration according to an embodiment of the present application. The method includes the following steps:

[0135] Step 601: A terminal determines at least two QoS parameter groups corresponding to the terminal's services.

[0136] Each service corresponds to one or more QoS parameter groups. The correspondence between the services and the QoS parameter groups of the terminal may be configured by a core network element, may be pre-configured, or may be configured by a base station.

[0137] If there are multiple services of a terminal, the multiple services correspond to the same destination Layer-2 identifier (destination Layer-2 ID), and the at least two QoS parameter groups corresponding to the services of the terminal can also be understood as at least two QoS parameter groups corresponding to the destination layer-2 ID.

[0138] Step 602: The terminal determines at least two SL DRX configurations corresponding to at least two QoS parameter groups, where each SL DRX configuration indicates one or more SL DRX parameters.

[0139] The terminal can determine at least two SL DRX configurations corresponding to the at least two QoS parameter groups based on the correspondence between the QoS parameter groups and the SL DRX configurations. The correspondence between the QoS parameter groups and the SL DRX configurations may be configured by the base station, may be pre-configured, or may be configured by a core network element.

[0140] Different terminals may determine at least two SL DRX configurations corresponding to the same destination layer-2 ID. Therefore, the at least two SL DRX configurations determined by different terminals are the same. It can also be understood that the service corresponding to the destination layer-2 ID may be the same between the transmitting terminal and the receiving terminal. Therefore, the at least two SL DRX configurations corresponding to the same service may be the same between the transmitting terminal and the receiving terminal.

[0141] Step 603: The terminal determines a first SL DRX configuration based on the at least two SL DRX configurations, and the first SL DRX configuration serves as the SL DRX configuration for use.

[0142] Furthermore, the terminal may further determine, based on the first SL DRX configuration, a running time of a timer corresponding to the first SL DRX configuration, where the timer includes one or more of an sl-DRX-onDurationTimer, an sl-DRX-inactivityTimer, an sl-DRX-HARQ-RTT-Timer, or an sl-DRX-RetransmissionTimer. Determining the running time of the timer includes determining a timing period, a start time, a restart time, a timeout time, or a stop time of the timer.

[0143] The terminal maintains a set of SL DRX timers for a destination layer-2 ID corresponding to a service of the terminal, i.e., timers corresponding to the first SL DRX configuration. The terminal determines the SL active time corresponding to the destination layer-2 ID based on the execution times of the timers corresponding to the first SL DRX configuration. For example, the SL active time corresponding to the destination layer-2 ID includes any one or a union of the following execution times: the execution time of the sl-DRX-OnDurationTimer corresponding to the first SL DRX configuration, the execution time of the sl-DRX-InactivityTimer corresponding to the first SL DRX configuration, or the execution time of the sl-DRX-RetransmissionTimer corresponding to the first SL DRX configuration.

[0144] In implementation, the terminal can determine the execution time of the timer corresponding to the first SL DRX configuration based on the first SL DRX configuration and the SCI corresponding to the destination layer-2 ID. The SCI corresponding to the destination layer-2 ID means that the destination layer-1 ID included in the SCI is the 8 least significant bits (8 LSBs) of the destination layer-2 ID. For example, after transmitting the SCI corresponding to the destination layer-2 ID to the receiving terminal, the transmitting terminal starts one or more of the sl-DRX-inactivity-Timer corresponding to the first SL DRX configuration, the sl-DRX-HARQ-RTT-Timer corresponding to the first SL DRX configuration, or the sl-DRX-Retransmission-Timer corresponding to the first SL DRX configuration. For example, after receiving an SCI corresponding to the destination layer-2 ID transmitted by the transmitting terminal, the receiving terminal starts one or more of the following: an sl-DRX-inactivityTimer corresponding to the first SL DRX configuration, an sl-DRX-HARQ-RTT-Timer corresponding to the first SL DRX configuration, and an sl-DRX-RetransmissionTimer corresponding to the first SL DRX configuration.

[0145] The above terminal may be a transmitting terminal or a receiving terminal. Specifically, the transmitting terminal and the receiving terminal select the same SL DRX configuration (i.e., the first SL DRX configuration) from at least two SL DRX configurations corresponding to the destination layer-2 ID using the same method. This allows the SL active times of the transmitting terminal and the receiving terminal to be aligned, ensuring correct communication.

[0146] In step 603, the method by which the terminal determines the first SL DRX configuration based on the at least two SL DRX configurations includes, but is not limited to, the following method 1 and method 2.

[0147] Method 1: The terminal selects one SL DRX configuration from at least two SL DRX configurations as a first SL DRX configuration.

[0148] That is, the first SL DRX configuration is one of at least two SL DRX configurations.

[0149] Specifically, Method 1 can include the following Methods 1.1 to 1.6.

[0150] Method 1.1: Determine one of the at least two SL DRX configurations as a first SL DRX configuration based on a first parameter among the at least two SL DRX configurations.

[0151] The first parameter is one of the following parameters: the value of sl-DRX-OnDurationTimer, the value of sl-DRX-InactivityTimer, the value of sl-DRX-HARQ-RTT-Timer, the value of sl-DRX-RetransmissionTimer, the value of sl-DRX-startOffset, the value of SL DRX cycle, or the value of sl-DRX-slotOffset.

[0152] For example, the determined first SL DRX configuration is the SL DRX configuration with the largest value of the first parameter among at least two SL DRX configurations. For example, the first parameter is the value of sl-DRX-OnDurationTimer. The values of sl-DRX-OnDurationTimer of the at least two SL DRX configurations are compared, and then the SL DRX configuration with the largest value of sl-DRX-OnDurationTimer is selected as the first SL DRX configuration.

[0153] In another example, the determined first SL DRX configuration is the SL DRX configuration having the smallest value of a first parameter among at least two SL DRX configurations. For example, the first parameter is the value of the SL DRX cycle. The values of the SL DRX cycle among the at least two SL DRX configurations are compared, and then the SL DRX configuration having the smallest value of the SL DRX cycle is selected as the first SL DRX configuration.

[0154] If two or more SL DRX configurations have the same first parameter value, and this value is the minimum or maximum, another SL DRX configuration may be selected as the first SL DRX configuration from the multiple selected SL DRX configurations. Selection methods include the following methods A to D.

[0155] Method A: Determine a first SL DRX configuration based on the positions of multiple SL DRX configurations in the SL DRX configuration list.

[0156] For example, the SL DRX configuration located at the beginning or end of the SL DRX configuration list is selected as the first SL DRX configuration from among the multiple SL DRX configurations. If the values of the first parameter in at least two of the multiple SL DRX configurations are the minimum or maximum value, the SL DRX configuration located at the beginning or end of the SL DRX configuration list is selected as the first SL DRX configuration from among the multiple SL DRX configurations.

[0157] For example, first, the values of sl-DRX-OnDurationTimer in at least two SL DRX configurations are compared, and then the SL DRX configuration with the largest value of sl-DRX-OnDurationTimer is selected. For example, as a result, the value of sl-DRX-OnDurationTimer in SL DRX configuration 2 is the same as that in SL DRX configuration 3, and this value is the largest. In this case, the positions of SL DRX configuration 2 and SL DRX configuration 3 in the SL DRX configuration list are further compared. For example, if SL DRX configuration 2 is located first, SL DRX configuration 2 is finally selected as the first SL DRX configuration.

[0158] Method B: Determine the first SL DRX configuration based on PQI values corresponding to multiple SL DRX configurations.

[0159] For example, the PQI values corresponding to the multiple SL DRX configurations are compared, and the SL DRX configuration corresponding to the PQI with the minimum or maximum value is selected as the first SL DRX configuration. That is, if the values of the first parameter in at least two SL DRX configurations are the minimum or maximum value in the multiple SL DRX configurations, the SL DRX configuration corresponding to the PQI with the minimum or maximum value is selected as the first SL DRX configuration from among the multiple SL DRX configurations.

[0160] For example, first, the values of sl-DRX-OnDurationTimer among at least two SL DRX configurations are compared, and then the SL DRX configuration with the largest value of sl-DRX-OnDurationTimer is selected. As a result, for example, the value of sl-DRX-OnDurationTimer in SL DRX configuration 2 is the same as that in SL DRX configuration 3, and this value is the largest. In this case, the PQI values corresponding to SL DRX configuration 2 and SL DRX configuration 3 are further compared. For example, SL DRX configuration 2 corresponds to PQI3, PQI4, and PQI5, while SL DRX configuration 3 corresponds to PQI6 and PQI7, with PQI4 having the smallest value and PQI7 having the largest value. If the SL DRX configuration corresponding to the smallest PQI is selected as the first SL DRX configuration, PQI4 is selected as the first SL DRX configuration. If the SL DRX configuration corresponding to the maximum PQI is selected as the first SL DRX configuration, PQI7 is selected as the first SL DRX configuration.

[0161] Method C: Determine a first SL DRX configuration based on the indexes of SL QoS profiles corresponding to multiple SL DRX configurations.

[0162] For example, the indexes of the SL QoS profiles corresponding to the multiple SL DRX configurations are compared, and then the SL DRX configuration corresponding to the SL QoS profile with the smallest or largest index is selected as the first SL DRX configuration. That is, if the values of the first parameter in the multiple SL DRX configurations in at least two SL DRX configurations are the smallest or largest value, the SL DRX configuration corresponding to the SL QoS profile with the smallest or largest index is selected as the first SL DRX configuration from among the multiple SL DRX configurations.

[0163] For example, first, the values of sl-DRX-OnDurationTimer in at least two SL DRX configurations are compared, and then the SL DRX configuration with the largest value of sl-DRX-OnDurationTimer is selected. As a result, for example, the value of sl-DRX-OnDurationTimer in SL DRX configuration 2 is the same as that in SL DRX configuration 3, and this value is the largest. In this case, the indices of the SL QoS profiles corresponding to SL DRX configuration 2 and SL DRX configuration 3 separately are further compared. For example, SL DRX configuration 2 corresponds to SL QoS profile 3, SL QoS profile 4, and SL QoS profile 5, SL DRX configuration 3 corresponds to SL QoS profile 6 and SL QoS profile 7, and the indices of SL QoS profile 3, SL QoS profile 4, SL QoS profile 5, SL QoS profile 6, and SL QoS profile 7 are 3, 4, 5, 6, and 7, respectively. If the SL DRX configuration corresponding to the SL QoS profile with the smallest index is selected as the first SL DRX configuration, SL QoS profile 3 is selected as the first SL DRX configuration. If the SL DRX configuration corresponding to the SL QoS profile with the largest index is selected as the first SL DRX configuration, SL QoS profile 7 is selected as the first SL DRX configuration.

[0164] Method D: Determine the first SL DRX configuration based on the indexes of the PQIs corresponding to the multiple SL DRX configurations.

[0165] For example, the indices of the PQIs corresponding to the multiple SL DRX configurations are compared, and the SL DRX configuration corresponding to the PQI with the smallest or largest index is selected as the first SL DRX configuration. That is, if the values of the first parameter in at least two of the multiple SL DRX configurations are the smallest or largest value, the SL DRX configuration corresponding to the PQI with the smallest or largest index is selected as the first SL DRX configuration from among the multiple SL DRX configurations.

[0166] For example, first, the values of sl-DRX-OnDurationTimer in at least two SL DRX configurations are compared, and then the SL DRX configuration with the largest value of sl-DRX-OnDurationTimer is selected. As a result, for example, the value of sl-DRX-OnDurationTimer in SL DRX configuration 2 is the same as that in SL DRX configuration 3, and this value is the largest. In this case, the PQI indices corresponding to SL DRX configuration 2 and SL DRX configuration 3 are further compared. For example, SL DRX configuration 2 corresponds to PQI3, PQI4, and PQI5, and SL DRX configuration 3 corresponds to PQI6 and PQI7, with the indices of PQI3, PQI4, PQI5, PQI6, and PQI7 being 3, 4, 5, 6, and 7, respectively. If the SL DRX configuration corresponding to the PQI with the smallest index is selected as the first SL DRX configuration, PQI3 is selected as the first SL DRX configuration. If the SL DRX configuration corresponding to the PQI with the largest index is selected as the first SL DRX configuration, PQI7 is selected as the first SL DRX configuration.

[0167] Method 1.2: Determine one of the at least two SL DRX configurations as a first SL DRX configuration based on a plurality of parameters in the at least two SL DRX configurations.

[0168] Specifically, when the value of the first parameter in a plurality of SL DRX configurations in at least two SL DRX configurations is the minimum value or the maximum value, When the value of the second parameter in only one SL DRX configuration among the multiple SL DRX configurations is the smallest or largest, the SL DRX configuration is determined to be the first SL DRX configuration; or When the value of the second parameter in the plurality of SL DRX configurations is the minimum or maximum value, one of the plurality of SL DRX configurations is determined as the first SL DRX configuration.

[0169] Specifically, first, multiple SL DRX configurations are determined based on values of a first parameter among at least two SL DRX configurations, where the values of the first parameter among the multiple determined SL DRX configurations are the same, for example, the value of the first parameter is the maximum or minimum value of a parameter among the multiple SL DRX configurations. Then, one SL DRX configuration is determined based on values of a second parameter among the multiple determined SL DRX configurations, where the value of the second parameter among the determined SL DRX configurations is the maximum or minimum value. If more than one SL DRX configuration is determined using the first parameter and the second parameter, another parameter, for example, a third parameter, can be used to further select an SL DRX configuration until one SL DRX configuration is selected.

[0170] The order of using the parameters of the SL DRX configuration to be used is not limited. The first parameter, the second parameter, and the third parameter are different from each other. The first parameter, the second parameter, and the third parameter are each one of the following parameters: the value of slDRX cycle, the value of sl-DRX-onDurationTimer, the value of sl-DRX-inactivityTimer, the value of sl-DRX-RetransmissionTimer, the value of sl-DRX-HARQ-RTT-Timer, or the value of sl-DRX-startOffset and the value of sl-DRX-slotOffset.

[0171] Method 1.3: Determine a first SL DRX configuration based on the positions of at least two SL DRX configurations in the SL DRX configuration list.

[0172] For example, the SL DRX configuration located first or last in the SL DRX configuration list is selected as the first SL DRX configuration.

[0173] For example, the SL DRX configurations in the SL DRX configuration list are in the order of SL DRX configuration 1, SL DRX configuration 2, SL DRX configuration 3, ... In this case, SL DRX configuration 1 is finally selected as the first SL DRX configuration.

[0174] Method 1.4: Determine a first SL DRX configuration based on PQI values corresponding to at least two SL DRX configurations.

[0175] For example, the PQI values corresponding to at least two SL DRX configurations are compared, and then the SL DRX configuration corresponding to the PQI with the smallest or largest value is selected as the first SL DRX configuration.

[0176] For example, SL DRX configuration 1 corresponds to PQI1 and PQI2, SL DRX configuration 2 corresponds to PQI3, PQI4, and PQI5, and SL DRX configuration 3 corresponds to PQI6 and PQI7, with PQI4 having the smallest value and PQI7 having the largest value. If the SL DRX configuration corresponding to the smallest PQI is selected as the first SL DRX configuration, PQI4 is selected as the first SL DRX configuration. If the SL DRX configuration corresponding to the largest PQI is selected as the first SL DRX configuration, PQI7 is selected as the first SL DRX configuration.

[0177] Method 1.5: Determine a first SL DRX configuration based on the indexes of SL QoS profiles corresponding to at least two SL DRX configurations.

[0178] For example, the indices of the SL QoS profiles corresponding to at least two SL DRX configurations are compared, and the SL DRX configuration corresponding to the SL QoS profile with the smallest or largest index is selected as the first SL DRX configuration.

[0179] For example, SL DRX configuration 1 corresponds to SL QoS profile 1 and SL QoS profile 2, SL DRX configuration 2 corresponds to SL QoS profile 3, SL QoS profile 4, and SL QoS profile 5, SL DRX configuration 3 corresponds to SL QoS profile 6 and SL QoS profile 7, and the indices of SL QoS profile 1, SL QoS profile 2, SL QoS profile 3, SL QoS profile 4, SL QoS profile 5, SL QoS profile 6, and SL QoS profile 7 are 1, 2, 3, 4, 5, 6, and 7, respectively. When the SL DRX configuration corresponding to the SL QoS profile with the smallest index is selected as the first SL DRX configuration, SL QoS profile 1 is selected as the first SL DRX configuration. When the SL DRX configuration corresponding to the SL QoS profile with the largest index is selected as the first SL DRX configuration, SL QoS profile 7 is selected as the first SL DRX configuration.

[0180] Method 1.6: Determine a first SL DRX configuration based on the indices of the PQIs corresponding to at least two SL DRX configurations.

[0181] For example, the indexes of the PQIs corresponding to at least two SL DRX configurations are compared, and then the SL DRX configuration corresponding to the PQI with the smallest or largest index is selected as the first SL DRX configuration.

[0182] For example, SL DRX configuration 1 corresponds to PQI1 and PQI2, SL DRX configuration 2 corresponds to PQI3, PQI4, and PQI5, SL DRX configuration 3 corresponds to PQI6 and PQI7, and the indices of PQI1, PQI2, PQI3, PQI4, PQI5, PQI6, and PQI7 are 1, 2, 3, 4, 5, 6, and 7, respectively. If the SL DRX configuration corresponding to the PQI with the smallest index is selected as the first SL DRX configuration, PQI1 is selected as the first SL DRX configuration. If the SL DRX configuration corresponding to the PQI with the largest index is selected as the first SL DRX configuration, PQI7 is selected as the first SL DRX configuration.

[0183] Method 2: Generating a first SL DRX configuration based on at least two SL DRX configurations.

[0184] That is, the first SL DRX configuration is generated based on the at least two SL DRX configurations, and the values of the parameters in the first SL DRX configuration are derived from one or more of the at least two SL DRX configurations.

[0185] For example, the first SL DRX configuration is generated based on the maximum or minimum value of each parameter of at least two SL DRX configurations. That is, the value of the first parameter included in the first SL DRX configuration is the maximum or minimum value among the values of the first parameter included in each of the at least two SL DRX configurations. For example, the values of SL DRX cycle, sl-DRX-HARQ-RTT-Timer, sl-DRX-startOffset, and sl-DRX-slotOffset in the generated first SL DRX configuration are each the minimum values among the at least two DRX configurations, and the values of sl-DRX-onDurationTimer, sl-DRX-inactivityTimer, and sl-DRX-RetransmissionTimer in the generated first SL DRX configuration are each the maximum values among the at least two DRX configurations.

[0186] According to this solution, when the terminal service supports at least two SL DRX configurations, the transmitting terminal and the receiving terminal determine one SL DRX configuration from the at least two SL DRX configurations by the same method, and therefore the transmitting terminal and the receiving terminal use the same SL DRX configuration, so that the SL active times of the transmitting terminal and the receiving terminal can be aligned.

[0187] In an implementation, steps 602 and 603 may alternatively be replaced by steps of determining a first QoS parameter group based on at least two QoS parameter groups and determining an SL DRX configuration corresponding to the first QoS parameter group as the first SL DRX configuration. For example, the QoS parameter group is a PQI. In this case, the first QoS parameter group (i.e., the first PQI) may be a PQI having the smallest or largest value among the multiple PQIs, or a PQI having the smallest or largest index among the multiple PQIs. For example, the QoS parameter group is a SL QoS profile. In this case, the first QoS parameter group (i.e., the first SL QoS profile) may be an SL QoS profile having the smallest or largest index among the multiple SL QoS profiles.

[0188] Embodiment 2 7 is a schematic diagram of a method for determining a SL DRX configuration according to an embodiment of the present application. The method includes the following steps:

[0189] Steps 701 and 702 are the same as steps 601 and 602. For details, see the above description.

[0190] Step 703: The terminal determines at least two SL DRX configurations as SL DRX configurations to use, and the SL active time corresponding to the terminal's service includes one or a union of the following multiple execution times: execution times of sl-DRX-OnDurationTimers each corresponding to the at least two SL DRX configurations, execution times of sl-DRX-InactivityTimers each corresponding to the at least two SL DRX configurations, or execution times of sl-DRX-RetransmissionTimers each corresponding to the at least two SL DRX configurations.

[0191] The terminal may determine, based on the at least two SL DRX configurations, running times of timers corresponding to the at least two SL DRX configurations, where the timers include one or more of an sl-DRX-onDurationTimer, an sl-DRX-inactivityTimer, an sl-DRX-HARQ-RTT-Timer, or an sl-DRX-RetransmissionTimer. Determining the running times of the timers includes determining a timing period, a start time, a restart time, a timeout time, or a stop time of the timers.

[0192] The terminal maintains multiple sets of SL DRX timers for destination layer-2 IDs corresponding to the terminal's services. The SL active time corresponding to the destination layer-2 ID can be determined based on the execution time of each set of SL DRX timers. The SL active time corresponding to the destination layer-2 ID may also be referred to as the SL active time corresponding to the terminal's services.

[0193] FIG. 8 is a schematic diagram of the execution times of the sl-DRX-OnDurationTimers corresponding to different SL DRX configurations. For example, FIG. 8 shows the execution times of the sl-DRX-OnDurationTimers corresponding to SL DRX configuration 1 and SL DRX configuration 2. SL DRX configuration 1 includes SL DRX cycle 1, and SL DRX configuration 2 includes SL DRX cycle 2. Based on the example in FIG. 8, the execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1 includes the period between T1 and T2 and the period between T5 and T6. The execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 2 includes the period between T3 and T4 and the period between T7 and T8. The SL active time corresponding to the destination layer-2 ID includes the period between T1 and T2, the period between T3 and T4, the period between T5 and T6, and the period between T7 and T8.

[0194] FIG. 9 is a schematic diagram of the execution times of the sl-DRX-InactivityTimers and the sl-DRX-OnDurationTimer corresponding to different SL DRX configurations. For example, FIG. 9 shows the execution times of the sl-DRX-InactivityTimer and sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1 and the execution time of the sl-DRX-InactivityTimer corresponding to SL DRX configuration 2. Based on the example of FIG. 9, the execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1 includes the period from T1 to T4. The execution time of the sl-DRX-InactivityTimer corresponding to SL DRX configuration 1 includes the period from T3 to T5. The execution time of the sl-DRX-InactivityTimer corresponding to SL DRX configuration 2 includes the period from T3 to T4. The SL active time corresponding to the destination layer-2 ID includes the period from T3 to T5, the period from T3 to T4, and the period from T1 to T4. That is, the SL active time corresponding to the destination layer-2 ID includes the period from T1 to T5.

[0195] FIG. 10 is a schematic diagram of the execution times of the sl-DRX-RetransmissionTimers and the sl-DRX-OnDurationTimer corresponding to different SL DRX configurations. For example, FIG. 10 shows the execution times of the sl-DRX-RetransmissionTimer and the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1 and the execution time of the sl-DRX-RetransmissionTimer corresponding to SL DRX configuration 2. Based on the example of FIG. 10, the execution time of the sl-DRX-RetransmissionTimer corresponding to SL DRX configuration 1 includes the period from T3 to T5. The execution time of the sl-DRX-RetransmissionTimer corresponding to SL DRX configuration 2 includes the period from T3 to T4. The execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1 includes the period from T1 to T4. The SL active time corresponding to the destination layer-2 ID includes the periods between T3 and T5, between T3 and T4, and between T1 and T4. That is, the SL active time corresponding to the destination layer-2 ID includes the periods T1 to T5.

[0196] The terminal may be a transmitting terminal or a receiving terminal. Specifically, the transmitting terminal and the receiving terminal determine the execution times of the timers corresponding to the at least two SL DRX configurations in the same manner based on the at least two SL DRX configurations corresponding to the terminal services. This allows the transmitting terminal and the receiving terminal to align their SL active times and ensure correct communication.

[0197] Note that for the sl-DRX-onDurationTimer corresponding to each SL DRX configuration, the terminal may determine the execution time of the sl-DRX-onDurationTimer corresponding to the SL DRX configuration based on the parameter values indicated by each SL DRX configuration. The sl-DRX-onDurationTimer corresponding to each SL DRX configuration is executed periodically.

[0198] In this implementation, the terminal may determine the execution times of the timers corresponding to the at least two SL DRX configurations based on the at least two SL DRX configurations and the SCI corresponding to the destination layer-2 ID. For the meaning of the SCI corresponding to the destination layer-2 ID, see the above description. For example, after transmitting the SCI corresponding to the destination layer-2 ID to the receiving terminal, the transmitting terminal starts one or more of the sl-DRX-inactivityTimer corresponding to each SL DRX configuration, the sl-DRX-HARQ-RTT-Timer corresponding to each SL DRX configuration, or the sl-DRX-RetransmissionTimer corresponding to each SL DRX configuration. As another example, after receiving the SCI transmitted from the transmitting terminal and corresponding to the destination layer-2 ID, the receiving terminal starts one or more of the sl-DRX-inactivityTimer corresponding to each SL DRX configuration, the sl-DRX-HARQ-RTT-Timer corresponding to each SL DRX configuration, or the sl-DRX-RetransmissionTimer corresponding to each SL DRX configuration.

[0199] Therefore, if the destination layer-2 ID is the same but the transmitted data corresponds to different SL QoS profiles / PQIs, the method of starting the timer corresponding to the SL DRX configuration is the same. There are cases where multiple data transmitted from the transmitting terminal and corresponding to a destination layer-2 ID correspond to different SL QoS profiles / PQIs within the SL active time corresponding to the destination layer-2 ID.

[0200] According to the above solution, when a terminal service supports at least two SL DRX configurations, the transmitting terminal and the receiving terminal maintain separate sets of SL DRX timers for each SL DRX configuration corresponding to the terminal service, and the transmitting terminal and the receiving terminal use at least two identical SL DRX configurations, maintain the same timers, and use the same SL DRX timer activity method, thereby aligning the SL active times of the transmitting terminal and the receiving terminal.

[0201] Embodiment 3 11 is a schematic diagram of a method for determining a SL DRX configuration according to an embodiment of the present application. The method includes the following steps:

[0202] Steps 1101 and 1102 are the same as steps 601 and 602. For details, see the above description.

[0203] For the specific implementation of this step, please refer to the implementation of step 601. The details will not be described again here.

[0204] Step 1103: The terminal determines at least two SL DRX configurations as SL DRX configurations to use, and the SL active time corresponding to the terminal's service includes one or a union of the following multiple execution times: execution times of sl-DRX-OnDurationTimers corresponding to the at least two SL DRX configurations, respectively, an execution time of a first sl-DRX-InactivityTimer corresponding to a second SL DRX configuration, or an execution time of a first sl-DRX-RetransmissionTimer corresponding to a third SL DRX configuration.

[0205] The second SL DRX configuration and the third SL DRX configuration are different ones of at least two SL DRX configurations. The second SL DRX configuration and the third SL DRX configuration may be the same or different.

[0206] Specifically, the terminal determines, based on the at least two SL DRX configurations, execution times of the sl-DRX-onDurationTimers corresponding to the at least two SL DRX configurations, and determines one or more execution times of a first sl-DRX-inactivityTimer corresponding to the second SL DRX configuration or a first sl-DRX-RetransmissionTimer corresponding to the third SL DRX configuration. Optionally, the terminal further determines an execution time of a first sl-DRX-HARQ-RTT-Timer corresponding to a fourth SL DRX configuration. The fourth SL DRX configuration is one of the at least two SL DRX configurations. The fourth SL DRX configuration may be the same as the second SL DRX configuration or the third SL DRX configuration, or may be different from both the second SL DRX configuration and the third SL DRX configuration.

[0207] The first sl-DRX-inactivity-Timer is one of the sl-DRX-inactivity-Timers corresponding to at least two SL DRX configurations, each of which corresponds to one of the SL DRX configurations, e.g., the minimum sl-DRX-inactivity-Timer or the maximum sl-DRX-inactivity-Timer. The first sl-DRX-HARQ-RTT-Timer is one of the sl-DRX-HARQ-RTT-Timers corresponding to at least two SL DRX configurations, each of which corresponds to one of the SL DRX configurations, e.g., the minimum sl-DRX-HARQ-RTT-Timer or the maximum sl-DRX-HARQ-RTT-Timer. The first sl-DRX-Retransmission-Timer is one of the sl-DRX-Retransmission-Timers corresponding to at least two SL DRX configurations, each of which corresponds to one of the SL DRX configurations, e.g., the minimum sl-DRX-Retransmission-Timer or the maximum sl-DRX-Retransmission-Timer.

[0208] That is, for a destination layer-2 ID corresponding to the UE's service, the UE maintains multiple sl-DRX-onDurationTimers, including one sl-DRX-inactivityTimer, one sl-DRX-HARQ-RTT-Timer, and one sl-DRX-RetransmissionTimer. The UE determines the SL active time corresponding to the destination layer-2 ID based on the execution times of the sl-DRX-onDurationTimers corresponding to at least two SL DRX configurations and the execution times of one or more first sl-DRX-inactivityTimers or first sl-DRX-RetransmissionTimers. The SL active time corresponding to the destination layer-2 ID is also referred to as the SL active time corresponding to the UE's service.

[0209] For examples of the execution times of the sl-DRX-OnDurationTimers corresponding to different SL DRX configurations, see the schematic diagram in FIG. 8 and the associated discussion.

[0210] FIG. 12 is a schematic diagram of the execution times of the sl-DRX-OnDurationTimers corresponding to different SL DRX configurations and the execution time of the first sl-DRX-InactivityTimer. For example, FIG. 12 shows the execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1, the execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 2, and the execution time of the first sl-DRX-InactivityTimer. In this example, the first sl-DRX-InactivityTimer corresponds to SL DRX configuration 1, SL DRX configuration 2, or another SL DRX configuration. The following description uses an example in which the first sl-DRX-InactivityTimer corresponds to SL DRX configuration 1. Based on the example of FIG. 12, the execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1 includes the period between T1 and T3 and the period between T6 and T7. The execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 2 includes the period between T4 and T5 and the period between T8 and T9. The execution time of the first sl-DRX-InactivityTimer includes the period between T2 and T3. Therefore, the SL active time corresponding to the destination layer-2 ID includes the periods between T1 and T3, T4 and T5, T6 and T7, and T8 and T9.

[0211] FIG. 13 is a schematic diagram of the execution times of the sl-DRX-OnDurationTimers and the sl-DRX-RetransmissionTimer corresponding to different SL DRX configurations. For example, FIG. 13 shows the execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1, the execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 2, and the execution time of the first sl-DRX-RetransmissionTimer. In this example, the first sl-DRX-RetransmissionTimer corresponds to SL DRX configuration 1, SL DRX configuration 2, or another SL DRX configuration. The following description uses an example in which the first sl-DRX-RetransmissionTimer corresponds to SL DRX configuration 1. Based on the example of FIG. 13, the execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1 includes the period between T1 and T3 and the period between T6 and T7. The execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 2 includes the period between T4 and T5 and the period between T8 and T9. The execution time of the first sl-DRX-RetransmissionTimer includes the period between T2 and T3. Therefore, the SL active time corresponding to the destination layer-2 ID includes the periods between T1 and T3, T4 and T5, T6 and T7, and T8 and T9.

[0212] In implementation, step 1102 may specifically involve the terminal determining, based on at least two SL DRX configurations and an SCI corresponding to a destination layer-2 ID, an execution time for one or more of the first sl-DRX-inactivity-timer, the first sl-DRX-HARQ-RTT-timer, or the first sl-DRX-retransmission-timer. For the meaning of the SCI corresponding to the destination layer-2 ID, see the above description. For example, after sending an SCI corresponding to the destination layer-2 ID to the receiving terminal, the transmitting terminal starts one or more of the first sl-DRX-inactivity-timer, the first sl-DRX-HARQ-RTT-timer, or the first sl-DRX-retransmission-timer. For example, after receiving an SCI transmitted from a transmitting terminal and corresponding to a destination layer-2 ID, the receiving terminal starts one or more of the first sl-DRX-inactivityTimer, the first sl-DRX-HARQ-RTT-Timer, and the first sl-DRX-RetransmissionTimer.

[0213] The above terminal may be a transmitting terminal or a receiving terminal. Specifically, the transmitting terminal and the receiving terminal determine, based on at least two SL DRX configurations corresponding to the terminal's services, the execution times of the sl-DRX-onDurationTimer, one sl-DRX-inactivityTimer, one sl-DRX-HARQ-RTT-Timer, and one sl-DRX-RetransmissionTimer corresponding to the at least two SL DRX configurations, using the same method. This makes it possible to align the SL active times of the transmitting terminal and the receiving terminal, thereby ensuring correct communication.

[0214] According to the above solution, if a terminal service supports at least two SL DRX configurations, the transmitting terminal and the receiving terminal maintain an sl-DRX-onDurationTimer corresponding to each DL DRX configuration, and one sl-DRX-InactivityTimer, one sl-DRX-HARQ-RTT-Timer, or one sl-DRX-RetransmissionTimer. The transmitting terminal and the receiving terminal use at least two identical SL DRX configurations, maintain the same timers, and use the same SL DRX timer activity method. This allows the SL active times of the transmitting terminal and the receiving terminal to be aligned. Furthermore, since only one sl-DRX-InactivityTimer, sl-DRX-HARQ-RTT-Timer, or sl-DRX-RetransmissionTimer is maintained, complexity can be reduced.

[0215] Embodiment 4 The fourth embodiment is similar to the second embodiment in that both the transmitting terminal and the receiving terminal use at least two SL DRX configurations corresponding to the terminal services, each SL DRX configuration corresponding to a set of SL DRX timers, and each set of SL DRX timers is maintained for the terminal services. The terminal services correspond to the same destination layer-2 ID. Therefore, in other words, each set of SL DRX timers may be maintained for one destination layer-2 ID.

[0216] The fourth embodiment differs from the second embodiment in that the fourth embodiment can determine the SL active time based on the execution time of each set of SL DRX timers. The SL active time includes any one or a union of the following execution times: the execution time of the sl-DRX-OnDurationTimer in the set of SL DRX timers, the execution time of the sl-DRX-InactivityTimer in the set of SL DRX timers, or the execution time of the sl-DRX-RetransmissionTimer in the set of SL DRX timers. Each SL active time corresponds to one or more SL QoS profiles / PQIs. That is, there is a correspondence between the SL active time and the SL QoS profile / PQIs. One or more SL QoS profiles / PQIs correspond to the SL DRX configuration corresponding to the SL active time. The transmitting terminal separately transmits SCIs corresponding to both the destination layer-2 ID and the SL QoS profile / PQI during the SL active time corresponding to one or more SL QoS profiles / PQIs. The receiving terminal receives an SCI corresponding to a destination layer-2 ID during an SL active time corresponding to one or more SL QoS profile / PQIs, or the receiving terminal receives an SCI corresponding to both a destination layer-2 ID and an SL QoS profile / PQI during an SL active time corresponding to one or more SL QoS profile / PQIs. An SCI corresponding to both a destination layer-2 ID and an SL QoS profile / PQI means that the destination layer-1 ID included in the SCI is the 8 least significant bits (8 LSBs) of the destination layer-2 ID, and that the SL QoS profile / PQI of the data scheduled by the SCI is the SL QoS profile / PQI. In embodiment 4, the SL active time of the terminal includes SL active times corresponding to one or more SL QoS profile / PQIs.

[0217] In implementation, at least two SL DRX configurations corresponding to a destination layer-2 ID and determined by different terminals are the same. For example, if the service corresponding to a destination layer-2 ID is the same between different terminals, the QoS parameter group of the service corresponding to the destination layer-2 ID corresponds to at least two identical SL DRX configurations. Therefore, the service corresponding to the destination layer-2 ID may be the same between the transmitting terminal and the receiving terminal. At least two SL DRX configurations corresponding to the destination layer-2 ID may be the same between the transmitting terminal and the receiving terminal.

[0218] In another implementation, at least two SL DRX configurations corresponding to a destination layer-2 ID and determined by different terminals are different. For example, if the service corresponding to a destination layer-2 ID is different between different terminals, the QoS parameter group within the service corresponding to the destination layer-2 ID corresponds to at least two different SL DRX configurations. If the service corresponding to the destination layer-2 ID is a service corresponding to the destination layer-2 ID and of interest to the terminals, the service corresponding to the destination layer-2 ID may be different between different terminals because different terminals are interested in different services. Therefore, the service corresponding to the destination layer-2 ID may be different between the transmitting terminal and the receiving terminal. At least two SL DRX configurations corresponding to the destination layer-2 ID may be different between the transmitting terminal and the receiving terminal.

[0219] In this implementation, the transmitting terminal transmits an SCI corresponding to a destination layer-2 ID during the SL active time, and the SCI includes indication information indicating one or more SL QoS profiles / PQIs corresponding to the data scheduled by the SCI. The transmitting terminal determines a DRX configuration corresponding to the SL QoS profile / PQI and determines the execution times of one or more of the sl-DRX-inactivityTimer, sl-DRX-HARQ-RTT-Timer, or sl-DRX-RetransmissionTimer corresponding to the DRX configuration. After receiving the SCI, the receiving terminal obtains the SL QoS profile / PQI in the SCI, determines the DRX configuration corresponding to the SL QoS profile / PQI, and determines the execution times of one or more of the sl-DRX-inactivityTimer, sl-DRX-HARQ-RTT-Timer, or sl-DRX-RetransmissionTimer corresponding to the DRX configuration.

[0220] For examples of the execution times of the sl-DRX-OnDurationTimers corresponding to different SL DRX configurations, see the schematic diagram in FIG. 8 and the associated discussion.

[0221] 14 is a schematic diagram of the execution times of the sl-DRX-OnDurationTimer and the sl-DRX-InactivityTimer corresponding to different SL DRX configurations. For example, FIG. 14 shows the execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1, the execution time of the sl-DRX-InactivityTimer corresponding to SL DRX configuration 1, the execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 2, and the execution time of the sl-DRX-InactivityTimer corresponding to SL DRX configuration 2. SL DRX configuration 1 corresponds to SL QoS profile 1, and SL DRX configuration 2 corresponds to SL QoS profile 2. In the example of FIG. 14, when the transmitting terminal transmits SCI1 corresponding to the destination layer-2 ID during the SL active time corresponding to SL QoS profile 1, SCI1 includes an indication of SL QoS profile 1. The receiving terminal acquires the indication information included in SCI1 and indicating SL QoS profile1, and determines, based on the indication information, that the data scheduled by SCI1 corresponds to SL QoS profile1, and determines SL DRX configuration 1 corresponding to SL QoS profile1. Furthermore, the receiving terminal starts the sl-DRX-InactivityTimer, and determines the execution time of the started sl-DRX-InactivityTimer based on the sl-DRX-InactivityTimer of SL DRX configuration 1. In this case, the SL active time corresponding to SL QoS profile1 includes the periods T1 to T3 and T2 to T4. In other words, the SL active time corresponding to SL QoS profile1 includes the periods T1 to T4. In the example of FIG. 14, when the transmitting terminal transmits SCI2 corresponding to the destination layer-2 ID during the SL active time corresponding to SL QoS profile2, SCI2 includes the indication information of SL QoS profile2.The receiving terminal acquires the instruction information for SL QoS profile 2 from SCI2, and based on that instruction information, determines that the data scheduled by SCI2 corresponds to SL QoS profile 2, and determines SL DRX configuration 2 that corresponds to SL QoS profile 2. Furthermore, it starts the sl-DRX-InactivityTimer, and determines the execution time of the started sl-DRX-InactivityTimer based on the sl-DRX-InactivityTimer for SL DRX configuration 2. In this case, the SL active time corresponding to SL QoS profile 2 includes the periods T5 to T7 and T6 to T7. In other words, the SL active time corresponding to SL QoS profile 2 includes the periods T5 to T7. The SL active time corresponding to the destination layer-2 ID includes the periods between T1 and T3 and between T5 and T7.

[0222] To satisfy the requirement that "a transmitting terminal transmits an SCI corresponding to a destination layer-2 ID during an SL active time, where the SCI includes one or more SL QoS profiles / PQIs corresponding to data scheduled by the SCI," Each layer in the transmitting terminal, from the Service Data Adaptation Protocol (SDAP) layer to the Media Access Control (MAC) layer, needs to indicate or mark the SL QoS profile / PQI corresponding to each data packet. Data corresponding to the same SL QoS profile / PQI may be multiplexed into the same MAC protocol data unit (PDU), and data corresponding to different SL QoS profiles / PQIs are multiplexed into different MAC PDUs. Note that for SCIs with the same destination layer-2 ID but carrying different SL QoS profiles / PQIs, the state of the SL DRX timer corresponding to the SL QoS profile / PQI changes, but the state of the SL DRX timer corresponding to another SL QoS profile / PQI does not change.

[0223] In another implementation, the transmitting terminal transmits an SCI corresponding to a destination layer-2 ID, but the SCI does not include an SL QoS profile / PQI corresponding to data scheduled by the SCI. The receiving terminal determines the execution times of one or more of the sl-DRX-inactivityTimer, sl-DRX-HARQ-RTT-Timer, or sl-DRX-RetransmissionTimer corresponding to each SL DRX configuration based on the received SCI corresponding to the destination layer-2 ID. Specifically, the receiving terminal determines that the SL active time corresponding to the destination layer-2 ID includes the SL active times corresponding to all SL DRX configurations.

[0224] 15 is a schematic diagram of the execution times of the sl-DRX-OnDurationTimer and the sl-DRX-InactivityTimer corresponding to different SL DRX configurations. For example, Fig. 15 shows the execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1, the execution time of the sl-DRX-InactivityTimer corresponding to SL DRX configuration 1, the execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 2, and the execution time of the sl-DRX-InactivityTimer corresponding to SL DRX configuration 2. The execution time of the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 2 is the same as the execution time of the sl-DRX-OnDurationTimer corresponding to DRX configuration 1. SL DRX configuration 1 corresponds to SL QoS profile 1, and SL DRX configuration 2 corresponds to SL QoS profile 2. Based on the example of FIG. 15, the transmitting terminal transmits SCI1 corresponding to the destination layer-2 ID and SL QoS profile1 during the SL active time corresponding to SL QoS profile1. If SCI1 does not include indication information indicating SL QoS profile1, the receiving terminal starts one sl-DRX-InactivityTimer based on the period of the sl-DRX-InactivityTimer for SL DRX configuration 1, and starts the other sl-DRX-InactivityTimer based on the period of the sl-DRX-InactivityTimer for SL DRX configuration 2. In this case, the SL active time corresponding to SL QoS profile1 includes the periods T1 to T3 and T2 to T4. In other words, the SL active time corresponding to SL QoS profile1 includes the periods T1 to T4. The SL active time corresponding to SL QoS profile2 includes the periods T1 to T3 and T2 to T3. In other words, the SL active time corresponding to SL QoS profile2 includes the periods T1 to T3. The SL active time corresponding to the destination layer-2 ID includes the period between T1 and T3, the period between T2 and T4, and the period between T2 and T3.That is, the SL active time corresponding to the destination layer-2 ID includes the period from T1 to T4.

[0225] To solve the second problem, the embodiments of the present application provide different solutions corresponding to Embodiments 5 to 9, respectively.

[0226] Embodiment 5 In this solution, the SL DRX configuration is configured for the terminal at the granularity of the SL QoS profile.

[0227] 16 is a schematic diagram of a method for determining a SL DRX configuration according to an embodiment of the present application. The method includes the following steps:

[0228] Step 1601: A terminal obtains configuration information, where the configuration information includes an index of an SL QoS profile corresponding to at least one SL DRX configuration.

[0229] The configuration information may be pre-configured, configured by the base station, configured by a core network element, or pre-defined in a protocol.

[0230] For example, the configuration information indicates the following correspondence: DRX configuration 1 corresponds to the index of SL QoS profile1 and the index of SL QoS profile2; DRX configuration 2 corresponds to the index of SL QoS profile3, the index of SL QoS profile4, the index of SL QoS profile5 and the index of SL QoS profile6; DRX configuration 3 corresponds to SL QoS profile 7.

[0231] In other words, the configuration information includes a list of indices of SL QoS profiles corresponding to at least one SL DRX configuration.

[0232] In another example, the configuration information indicates the following correspondence: The beginning of the index of the SL QoS profile corresponding to DRX configuration 1 is 3, and the length of the index of the SL QoS profile is 2, that is, the indexes of the SL QoS profile corresponding to DRX configuration 1 are 3 and 4; The beginning of the index of the SL QoS profile corresponding to the DRX configuration 2 is 7, and the length of the index of the SL QoS profile is 1, that is, the index of the SL QoS profile corresponding to the DRX configuration 2 is 7; The index of the SL QoS profile corresponding to DRX configuration 3 starts with 10 and the length of the index of the SL QoS profile is 3; that is, the indexes of the SL QoS profile corresponding to DRX configuration 3 are 10, 11, and 12.

[0233] That is, the configuration information includes the start and length of the index of the SL QoS profile corresponding to at least one SL DRX configuration. The start value and length value can each be indicated by two pieces of indication information. For example, indication 1 indicates the start value of the index, and indication 2 indicates the length value of the index. Alternatively, the start value and length value can be indicated by one indication information. The indication information indicates a value obtained by jointly encoding the start value and the length value. In this specification, the value may be referred to as a joint start and length value or a start and length indicator value (SLIV). The total number of indexes of the SL QoS profile is N, the start value is denoted as S, the length value is denoted as L, and the joint start and length value is denoted as M. If (L-1) is less than or equal to N / 2, M = N × (L-1) + S, or if (L-1) is greater than N / 2, M = N × (N-L+1) + (N-1-S). Here, S is an integer equal to or greater than 0 and less than N, and L is an integer equal to or greater than 0 and less than (N−S).

[0234] In the implementation, the configuration information further indicates at least one SL DRX configuration, specifically, the configuration information is used to configure the at least one SL DRX configuration and further configure an index of an SL QoS profile corresponding to each SL DRX configuration in the at least one SL DRX configuration.

[0235] In another implementation, instead of configuring at least one SL DRX configuration using configuration information, at least one SL DRX configuration is configured individually using separate configuration information, i.e., at least one SL DRX configuration is configured using one piece of configuration information, and an index of an SL QoS profile corresponding to each SL DRX configuration in the at least one SL DRX configuration is configured using separate configuration information.

[0236] Step 1602: The terminal determines, based on the index of the first SL QoS profile and the index of the SL QoS profile corresponding to at least one SL DRX configuration, the first SL DRX configuration corresponding to the index of the first SL QoS profile.

[0237] According to the above solution, the terminal can determine an SL DRX configuration corresponding to each SL QoS profile. For example, the terminal first determines a first SL QoS profile corresponding to the terminal or the terminal's service and determines an index of the first SL QoS profile. Next, the terminal determines a first SL DRX configuration corresponding to the index of the first SL QoS profile based on the index of the first SL QoS profile and the index of the SL QoS profile corresponding to at least one SL DRX configuration. The first SL DRX configuration is the SL DRX configuration corresponding to the first SL QoS profile.

[0238] In this implementation, the index of an SL QoS profile is indicated by its position among the SL QoS profiles corresponding to all SL RB configurations. The index of an SL QoS profile is determined based on the position of the SL RB configuration in the SL RB list and the position of the SL QoS profile in the SL QoS profile list included in the SL RB configuration. The index of an SL QoS profile can be obtained by consecutively numbering the SL QoS profile based first on the position of the SL QoS profile in the SL QoS profile list included in the SL RB configuration, and then on the position of the SL RB configuration in the SL RB list. The numbering may start with an integer equal to or greater than 0. The numbering may be incremented by 1. For example, the SL RB configurations in the SL RB list are ordered as SL RB configuration 1, SL RB configuration 2, and SL RB configuration 3. The remaining SL QoS profiles may be deduced similarly. The SL QoS profile corresponding to SL RB configuration 1 is consecutively numbered from 1 to N1 based on the position of the SL QoS profile in the SL QoS profile list. The SL QoS profiles corresponding to SL RB configuration 2 are consecutively numbered from N1+1 to N2 based on the position of the SL QoS profile in the SL QoS profile list. The SL QoS profiles corresponding to SL RB configuration 3 are consecutively numbered from N2+1 to N3 based on the position of the SL QoS profile in the SL QoS profile list. The rest may be deduced similarly. The indices of the SL QoS profiles are, in order, 1, ..., N1, N1+1, N1+2, ..., N2, N2+1, ..., N3, ... For example, the configuration information indicates the following correspondence: DRX configuration 1 corresponds to 1 and 3; DRX configuration 2 corresponds to 2, 4, 6, and 7; DRX configuration 3 corresponds to 5.

[0239] where 1, 2, ..., and 7 are the indices of the SL QoS profiles.

[0240] In this implementation, the index of an SL QoS profile is indicated by the index of the SL RB configuration corresponding to the SL QoS profile and the position of the SL QoS profile within the SL QoS profile corresponding to the SL RB configuration. The SL QoS profiles are numbered consecutively based on the position of the SL QoS profile in the SL QoS profile list included in the SL RB configuration. The numbering may start with an integer equal to or greater than 0. The numbering may increment by 1. For example, the SL QoS profiles corresponding to SL RB configuration 1 are numbered consecutively from 1 to N1 based on the position of the SL QoS profile in the SL QoS profile list. The SL QoS profiles corresponding to SL RB configuration 2 are numbered consecutively from 1 to N2 based on the position of the SL QoS profile in the SL QoS profile list. The SL QoS profiles corresponding to SL RB configuration 3 are numbered consecutively from 1 to N3 based on the position of the SL QoS profile in the SL QoS profile list. The rest may be deduced similarly. SL RB configuration 1 is the SL RB configuration with an index of 1. SL RB configuration 2 is the SL RB configuration with index 2. SL RB configuration 3 is the SL RB configuration with index 3. For example, the configuration information indicates the following correspondence: DRX configuration 1 corresponds to ((1),(1,2)); DRX configuration 2 corresponds to ((1),(3,4)); DRX configuration 3 corresponds to ((2),(1,3)).

[0241] Here, ((X),(Y,Z)) represent the index of the SL QoS profile, X is the index of the SL RB configuration, and Y and Z are the indexes of the SL QoS profile in the SL RB configuration. The (1) in ((1),(1,2)) indicates the SL RB configuration with index 1, i.e., SL RB configuration 1. The (1,2) in ((1),(1,2)) indicates the SL QoS profile with indexes 1 and 2 corresponding to SL RB configuration 1. The (1) in ((1),(3,4)) indicates the SL RB configuration with index 1, i.e., SL RB configuration 1. The (3,4) in ((1),(3,4)) indicates the SL QoS profile with indexes 3 and 4 corresponding to SL RB configuration 1. The (2) in ((2),(1,3)) indicates the SL RB configuration with index 2, i.e., SL RB configuration 2. The (1,3) in ((2),(1,3)) indicates the SL QoS profile corresponding to the SL RB configuration 2, with indexes 1 and 3.

[0242] In another example, the configuration information indicates the following correspondence: DRX configuration 1 corresponds to (1,1) and (1,2); DRX configuration 2 corresponds to (1,3), (1,4) and (2,2); DRX configuration 3 corresponds to (2,1) and (2,3).

[0243] Here, (X, Y) represents the index of the SL QoS profile, X is the index of the SL RB configuration, and Y is the index of the SL QoS profile in the SL RB configuration.

[0244] In implementation, the SL RB configuration may hold an index of the SL QoS profile corresponding to the SL RB configuration. In this case, when the UE receives the SL RB configuration and the SL QoS profile corresponding to the SL RB configuration, the UE may obtain the correspondence between the SL QoS profile and the SL QoS profile index. In one method, the SL QoS profile corresponding to the SL RB configuration is transmitted. Different SL RB configurations correspond to different SL QoS profile indexes. Then, the UE may use the configuration information in step 1601 to obtain the SL QoS profile indicated by the SL QoS profile index in the configuration information.

[0245] In implementation, the SL RB configuration may retain an index of an SL QoS profile corresponding to the SL RB configuration. In this case, when the terminal receives the SL RB configuration and the SL QoS profile corresponding to the SL RB configuration, the terminal may obtain the correspondence between the SL QoS profile and the index of the SL QoS profile in the SL RB configuration. In one method, the index of the SL QoS profile in the SL RB configuration is transmitted in the SL QoS profile corresponding to the SL RB configuration. SL QoS profiles corresponding to different SL RB configurations may have the same index in the SL RB configuration. The index of the SL QoS profile is indicated by the index of the SL RB configuration corresponding to the SL QoS profile and the position of the SL QoS profile in the SL RB configuration. Then, the terminal may use the configuration information of step 1601 to obtain the SL QoS profile indicated by the index of the SL QoS profile in the configuration information.

[0246] According to the above solution, the configuration information does not transmit the SL QoS profile, but transmits the index of the SL QoS profile corresponding to each SL DRX configuration, thereby reducing signaling overhead and storage overhead.

[0247] Embodiment 6 In this solution, the SL DRX configuration is configured for the terminal at the granularity of PQI.

[0248] 17 is a schematic diagram of a method for determining a SL DRX configuration according to an embodiment of the present application. The method includes the following steps:

[0249] Step 1701: A terminal obtains configuration information, where the configuration information includes an index of a PQI corresponding to at least one SL DRX configuration.

[0250] The configuration information may be pre-configured, configured by the base station, configured by a core network element, or pre-defined in a protocol.

[0251] For example, the configuration information indicates the following correspondence: DRX configuration 1 corresponds to the index of PQI1 and the index of PQI2; DRX configuration 2 corresponds to an index of PQI3, an index of PQI4, an index of PQI5 and an index of PQI6; DRX configuration 3 corresponds to an index of PQI7.

[0252] In implementation, the configuration information further indicates at least one SL DRX configuration, specifically, the configuration information is used to configure the at least one SL DRX configuration, and further configure an index of a PQI corresponding to each SL DRX configuration in the at least one SL DRX configuration.

[0253] In another implementation, instead of configuring the at least one SL DRX configuration using configuration information, separate configuration information is used to configure the at least one SL DRX configuration individually, i.e., one piece of configuration information is used to configure the at least one SL DRX configuration, and separate configuration information is used to configure an index of a PQI corresponding to each SL DRX configuration in the at least one SL DRX configuration.

[0254] Step 1702: The terminal determines a first SL DRX configuration corresponding to the index of the first PQI based on the index of the first PQI and the index of the PQI corresponding to the at least one SL DRX configuration.

[0255] According to the above solution, the terminal can determine an SL DRX configuration corresponding to each PQI. For example, the terminal first determines a first PQI corresponding to the terminal or the terminal's service and determines an index of the first PQI. Then, the terminal may determine an SL DRX configuration corresponding to the index of the first PQI based on the index of the first PQI and the index of a PQI corresponding to at least one SL DRX configuration. The SL DRX configuration is the first SL DRX configuration corresponding to the first PQI.

[0256] Here, the PQI may be a standardized PQI or a non-standardized PQI.

[0257] In the case of the standardized PQI, the value of the standardized PQI can be used as the index of the standardized PQI. Alternatively, the index of the standardized PQI is the index of the SL QoS profile including the standardized PQI, and the index of the SL QoS profile will be described in embodiment 5.

[0258] In the case of a non-standardized PQI, the index of the non-standardized PQI is the index of the SL QoS profile including the non-standardized PQI, and the index of the SL QoS profile will be described in embodiment 5. In addition, the index of the non-standardized PQI can be indicated in one of the following ways:

[0259] Method A: The index of the non-standardized PQI is indicated by the position of the SL QoS profile including the non-standardized PQI among the SL QoS profiles corresponding to all SL RB configurations.

[0260] For example, the SL RB configurations in the SL RB list are in the order SL RB configuration 1, SL RB configuration 2, SL RB configuration 3. The rest may be deduced similarly. The SL QoS profiles corresponding to SL RB configuration 1 are consecutively numbered from 1 to N1 based on the position of the SL QoS profile in the SL QoS profile list. The SL QoS profiles corresponding to SL RB configuration 2 are consecutively numbered from N1+1 to N2 based on the position of the SL QoS profile in the SL QoS profile list. The SL QoS profiles corresponding to SL RB configuration 3 are consecutively numbered from N2+1 to N3 based on the position of the SL QoS profile in the SL QoS profile list. The rest may be deduced similarly. The indices of the SL QoS profiles are, in order, 1, ..., N1, N1+1, N1+2, ..., N2, N2+1, ..., N3, ... Furthermore, the index of the non-standardized PQI included in the SL QoS profile with index i is i, and the value of i is 1, 2, 3, . . .

[0261] For example, the configuration information indicates the following correspondence: DRX configuration 1 corresponds to 1 and 3; DRX configuration 2 corresponds to 2, 4, and 6; DRX configuration 3 corresponds to 5 and 7.

[0262] where 1, 2, ..., and 7 are the indices of the non-normalized PQI.

[0263] Method B: The index of the non-standardized PQI is indicated by the index of the SL RB configuration corresponding to the SL QoS profile including the non-standardized PQI and the position of the SL QoS profile within the SL QoS profile corresponding to the SL RB configuration.

[0264] For example, the SL QoS profiles corresponding to SL RB configuration 1 are numbered consecutively from 1 to N1 based on the position of the SL QoS profile in the SL QoS profile list. The SL QoS profiles corresponding to SL RB configuration 2 are numbered consecutively from 1 to N2 based on the position of the SL QoS profile in the SL QoS profile list. The SL QoS profiles corresponding to SL RB configuration 3 are numbered consecutively from 1 to N3 based on the position of the SL QoS profile in the SL QoS profile list. The rest may be deduced similarly. SL RB configuration 1 is the SL RB configuration with index 1. SL RB configuration 2 is the SL RB configuration with index 2. SL RB configuration 3 is the SL RB configuration with index 3. Furthermore, the index of the non-normalized PQI included in the SL QoS profile with index i in the SL RB configuration is i, where the value of i is 1, 2, 3, ...

[0265] For example, the configuration information indicates the following correspondence: DRX configuration 1 corresponds to (1,1) and (1,2); DRX configuration 2 corresponds to (1,3), (1,4) and (2,2); DRX configuration 3 corresponds to (2,1) and (2,3).

[0266] Here, (X, Y) represents the index of the non-standardized PQI, X is the index of the SL RB configuration, and Y is the index of the non-standardized PQI in the SL RB configuration.

[0267] Method C: The index of the non-standard PQI is the index of the non-standard PQI included in the SL RB configuration. In one method, the index of the non-standard PQI is included in the non-standard PQI. In other words, the index is added to the non-standard PQI.

[0268] The index value may overlap with the standardized PQI value or may not overlap with all standardized PQI values. If the index of a non-standardized PQI overlaps with a specific standardized PQI value, the configuration information must further indicate whether the PQI is a standardized PQI or a non-standardized PQI, or the standardized PQI and the non-standardized PQI must be indicated separately.

[0269] For example, a "PqiIndex" field is added to the non-standardized PQI to indicate the index of the non-standardized PQI.

number

[0270] Method D: The index of the non-standard PQI is indicated by the index of the SL RB configuration corresponding to the SL QoS profile including the non-standard PQI and the index of the non-standard PQI in the SL RB configuration.

[0271] The index of the non-standard PQI of the SL RB configuration may be transmitted in the SL RB configuration. In one method, the index of the non-standard PQI of the SL RB configuration is included in the non-standard PQI. The value of the index of the non-standard PQI may overlap with the value of the standardized PQI, or may not overlap with all the values of the standardized PQI. If the index of the non-standardized PQI overlaps with the value of a specific standardized PQI, it is necessary to further indicate in the configuration information whether the PQI is a standardized PQI or a non-standardized PQI, or to indicate the standardized PQI and the non-standardized PQI separately.

[0272] According to the above solution, the configuration information does not carry the PQI, but carries the index of the PQI corresponding to each SL DRX configuration, which can reduce signaling overhead and storage overhead.

[0273] Embodiment 7 18A is a schematic diagram of a method for determining a DRX configuration according to an embodiment of the present application. The method includes the following steps:

[0274] Step 1801a: A terminal obtains configuration information, where the configuration information includes a normalized PQI corresponding to at least one SL DRX configuration.

[0275] Step 1802a: The terminal determines a first standardized PQI corresponding to the first non-standardized PQI according to the indication information corresponding to the first non-standardized PQI.

[0276] The indication information indicates a first standardized PQI that corresponds to the same SL DRX configuration as the first non-standardized PQI, i.e., the indication information indicates the first standardized PQI, and the first standardized PQI and the first non-standardized PQI correspond to the same SL DRX configuration.

[0277] Step 1803a: The terminal determines, based on the first standardized PQI and the standardized PQI corresponding to the at least one SL DRX configuration, a first SL DRX configuration corresponding to the first standardized PQI, where the first SL DRX configuration is also an SL DRX configuration corresponding to the first non-standardized PQI.

[0278] According to the above solution, the standardized PQI and the non-standardized PQI corresponding to the same SL DRX configuration are associated with each other using the indication information, so that the SL DRX configuration corresponding to the non-standardized PQI can be determined.

[0279] In this embodiment, if the SL DRX configuration corresponding to a non-standardized PQI is the same as the SL DRX configuration corresponding to a specific standardized PQI, the non-standardized PQI may correspond to one piece of indication information. In a specific embodiment, indication information may be added to the non-standardized PQI. The indication information indicates that the standardized PQI uses the same SL DRX configuration as the non-standardized PQI. In this way, no configuration information is required to configure the mapping relationship between the non-standardized PQI and the SL DRX configuration, thereby reducing signaling overhead and storage overhead.

[0280] For example, sl-Non-StandardizedPQI-r16 indicates the information contained in a non-standardized PQI, and SameDRXstandardizedPQI is added to sl-Non-StandardizedPQI-r16 to indicate a standardized PQI. The SL DRX configuration corresponding to a standardized PQI is the same as the SL DRX configuration corresponding to a non-standardized PQI.

number

[0281] According to the above solution, instead of configuring the mapping relationship between the non-standardized PQI and the SL DRX configuration using additional configuration information, the SL DRX configuration corresponding to the non-standardized PQI is made the same as the SL DRX configuration corresponding to the standardized PQI, thereby reducing signaling overhead and storage overhead.

[0282] Embodiment 8 A non-standardized PQI corresponds to a default SL DRX configuration or a common SL DRX configuration. The default SL DRX configuration or the common SL DRX configuration may be transmitted by the base station or may be pre-configured. The default SL DRX configuration or the common SL DRX configuration may or may not be dedicated to a non-standardized PQI. For example, the default SL DRX configuration corresponding to a non-standardized PQI may be the same as the default SL DRX configuration or the common SL DRX configuration for unicast, broadcast, or multicast, or the common SL DRX configuration corresponding to a non-standardized PQI may be the same as the default SL DRX configuration or the common SL DRX configuration for unicast, broadcast, or multicast.

[0283] According to this solution, the non-standardized PQIs correspond to the same default SL DRX configuration or common SL DRX configuration, thereby reducing the signaling overhead and storage overhead.

[0284] Embodiment 9 18B is a schematic diagram of a method for determining a DRX configuration according to an embodiment of the present application. The method includes the following steps:

[0285] Step 1801b: The terminal obtains configuration information, where the configuration information includes an index of an SL RB configuration corresponding to at least one SL DRX configuration, and each SL RB configuration corresponds to one or more SL QoS profiles, or each SL RB configuration corresponds to one or more PQIs.

[0286] The configuration information may be pre-configured, configured by the base station, configured by a core network element, or pre-defined in a protocol.

[0287] For example, the configuration information indicates the following correspondence: DRX configuration 1 corresponds to the index of SL RB configuration 1 and the index of SL RB configuration 2; DRX configuration 2 corresponds to the index of SL RB configuration 3, the index of SL RB configuration 4, the index of SL RB configuration 5, and the index of SL RB configuration 6; DRX configuration 3 corresponds to the index of SL RB configuration 7.

[0288] In implementation, the configuration information further indicates at least one SL DRX configuration, specifically, the configuration information is used to configure the at least one SL DRX configuration, and further configure an index of a PQI corresponding to each SL DRX configuration in the at least one SL DRX configuration.

[0289] In another implementation, instead of configuring the at least one SL DRX configuration using configuration information, separate configuration information is used to configure the at least one SL DRX configuration individually, i.e., one piece of configuration information is used to configure the at least one SL DRX configuration, and separate configuration information is used to configure an index of a PQI corresponding to each SL DRX configuration in the at least one SL DRX configuration.

[0290] The SL RB configuration may be pre-configured, configured by the base station, configured by a core network element, or pre-defined in a protocol. The SL RB configuration may be configured using the configuration information in step 1801b, or may be configured separately using other configuration information.

[0291] Step 1802b: The terminal determines a first SL DRX configuration corresponding to the first SL QoS profile based on the first SL QoS profile and an index of an SL RB configuration corresponding to the at least one SL DRX configuration, or determines a first SL DRX configuration corresponding to the first PQI based on the first PQI and an index of an SL RB configuration corresponding to the at least one SL DRX configuration.

[0292] According to the above solution, the terminal can determine an SL DRX configuration corresponding to each SL QoS profile. For example, for a first SL QoS profile corresponding to the terminal or a terminal service, the terminal first determines a first SL RB configuration corresponding to the first SL QoS profile and determines an index of the first SL RB configuration. Next, the terminal may determine an SL DRX configuration corresponding to the index of the first SL RB configuration based on the index of the first SL RB configuration and an index of an SL RB configuration corresponding to at least one SL DRX configuration. The SL DRX configuration is the first SL DRX configuration corresponding to the first SL QoS profile. In another example, for a first PQI corresponding to the terminal or a terminal service, the terminal first determines a first SL RB configuration corresponding to the first PQI and determines an index of the first SL RB configuration. Next, the terminal may determine an SL DRX configuration corresponding to the index of the first SL RB configuration based on the index of the first SL RB configuration and an index of an SL RB configuration corresponding to at least one SL DRX configuration. The SL DRX configuration is a first SL DRX configuration corresponding to a first PQI.

[0293] Alternatively, the terminal may determine the first SL DRX configuration corresponding to the index of the first SL RB configuration based on the index of the first SL RB configuration and the index of the SL RB configuration corresponding to at least one SL DRX configuration.

[0294] According to this solution, the terminal determines an index of a first SL RB configuration, and then, based on the index of the first SL RB configuration and the index of an SL RB configuration corresponding to at least one SL DRX configuration, can determine a first SL DRX configuration corresponding to the index of the first SL RB configuration.

[0295] The index of the SL RB configuration may be indicated by the position of the SL RB configuration in all SL RB configurations. Alternatively, the index of the SL RB configuration may be the index of the SL RB configuration included in the SL RB configuration.

[0296] The following provides an explanation with reference to an example.

[0297] SL RB configuration 1 corresponds to SL QoS profile 1 and SL QoS profile 2; SL RB configuration 2 corresponds to SL QoS profile 3 and SL QoS profile 4; SL RB configuration 3 corresponds to SL QoS profile 5; SL RB configuration 4 corresponds to SL QoS profile 6 and SL QoS profile 7.

[0298] For example, the configuration information indicates the following correspondence: DRX configuration 1 corresponds to 1 and 2; DRX configuration 2 corresponds to 3 and 4.

[0299] Here, 1, 2, 3, and 4 are indexes of SL RB configuration 1, SL RB configuration 2, SL RB configuration 3, and SL RB configuration 4, respectively. In this case, the configuration information indicates that DRX configuration 1 corresponds to SL RB configuration 1 and SL RB configuration 2, and therefore DRX configuration 1 corresponds to SL QoS profile 1, SL QoS profile 2, SL QoS profile 3, and SL QoS profile 4. Also, it indicates that DRX configuration 2 corresponds to SL RB configuration 3 and SL RB configuration 4, and therefore DRX configuration 2 corresponds to SL QoS profile 5, SL QoS profile 6, and SL QoS profile 7.

[0300] In implementation, there may be a one-to-one correspondence between the SL DRX configurations and the SL RB configurations based on the positions of the SL DRX configurations in the SL DRX configuration list and the positions of the SL RB configurations in the SL RB list. That is, the SL RB configurations in the SL RB list are in the order of SL RB configuration 1, SL RB configuration 2, and SL RB configuration 3. The rest may be estimated in a similar manner. The SL DRX configurations in the SL DRX configuration list are in the order of SL DRX configuration 1, SL DRX configuration 2, and SL DRX configuration 3. The rest may be estimated in a similar manner. In this case, SL DRX configuration 1 corresponds to SL RB configuration 1, and SL DRX configuration 2 corresponds to SL RB configuration 2. The rest may be estimated in a similar manner. This eliminates the need for configuration information to configure the SL RB configuration corresponding to each SL DRX configuration. The above example is used as an example. For example, if a terminal is configured with a correspondence relationship between SL RB configurations and SL QoS profiles, and DRX configuration 1 and DRX configuration 2 are configured, the terminal may determine that DRX configuration 1 corresponds to SL QoS profile 1 and SL QoS profile 2, and that DRX configuration 2 corresponds to SL QoS profile 3 and SL QoS profile 4.

[0301] In the above embodiment, the SL QoS profile / PQI corresponding to the SL DRX configuration is the SL QoS profile / PQI of one or more SL RB configurations. Therefore, in implementation, when an SL DRX configuration corresponding to an SL QoS profile / PQI needs to be configured, the SL RB configuration corresponding to the SL QoS profile / PQI needs to be satisfied.

[0302] In another implementation, if an SL QoS profile / PQI does not have a corresponding SL RB configuration, the SL QoS profile / PQI corresponds to a default SL DRX configuration or a common SL DRX configuration, for example, the default SL DRX configuration or the common SL DRX configuration is a default SL DRX configuration or a common SL DRX configuration for unicast, broadcast, or multicast.

[0303] In another implementation, the SL QoS profile / PQI corresponding to each SL DRX configuration may be indicated by the index in the above embodiment or by the SL QoS profile / PQI. If the SL QoS profile / PQI corresponding to the SL DRX configuration is the SL QoS profile / PQI in the SL RB configuration, the SL QoS profile / PQI is indicated by the index in the above embodiment. If the SL QoS profile / PQI corresponding to the SL DRX configuration is not the SL QoS profile / PQI in any SL RB configuration, the SL QoS profile / PQI is indicated by the SL QoS profile / PQI.

[0304] According to the above solution, the configuration information does not transmit the SL QoS profile, but transmits the index of the SL RB configuration corresponding to each SL DRX configuration, thereby reducing signaling overhead and storage overhead.

[0305] In another embodiment, if the SL DRX configuration and the SL RB configuration have a one-to-one correspondence and the correspondence is pre-configured in the terminal, step 1801b may not be performed. In this case, the terminal may determine a corresponding first SL RB configuration based on a first SL QoS profile or a first PQI, and then determine a first SL DRX configuration corresponding to the first SL RB configuration. The first SL DRX configuration is the SL DRX configuration corresponding to the first SL QoS profile or the SL DRX configuration corresponding to the first PQI.

[0306] Embodiment 10 In this solution, the SL DRX configuration is configured for the terminal at the granularity of the SL QoS profile.

[0307] In a schematic diagram of a method for determining an SL DRX configuration according to a tenth embodiment of the present application, the method includes the following steps:

[0308] The terminal obtains configuration information, where the configuration information indicates (or includes) an SL DRX configuration corresponding to at least one SL QoS profile. In other words, the configuration information indicates (or includes) a correspondence between at least one SL QoS profile and an SL DRX configuration.

[0309] The configuration information may be pre-configured, configured by the base station, configured by a core network element, or pre-defined in a protocol.

[0310] For example, the configuration information indicates the following correspondence: SL QoS profile1 corresponds to SL DRX configuration 1; SL QoS profile2 corresponds to SL DRX configuration 2; SL QoS profile 3 corresponds to SL DRX configuration 3.

[0311] In an implementation, the configuration information further indicates at least one SL QoS profile. Specifically, the configuration information is used to configure at least one SL QoS profile, and an SL DRX configuration corresponding to the at least one SL QoS profile is further configured.

[0312] For example, the configuration information includes one or more SL-QoS-Profiles, each of which includes one or more of PQI, GFBR, MFBR, or range, and includes an SL DRX configuration. An SL-QoS-Profile is denoted as follows:

number

[0313] In implementation, the SL DRX configuration is of enumerated type (ENUMERATED). For example, if the SL DRX configuration includes the sl-DRX-InactivityTimer, the sl-DRX-InactivityTimer is ENUMERATED{ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}. That is, the value of the sl-DRX-InactivityTimer is one of the values in parentheses. The value in parentheses is an integer multiple of 1 ms. where ms0 denotes 0, ms1 denotes 1 ms, ms2 denotes 2 ms, and the rest may be estimated similarly. Here, spare is an idle value, or can be understood as an unused value.

[0314] As another example, if the SL DRX configuration includes an SL DRX cycle, the SL DRX cycle is ENUMERATED{ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256, ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}. That is, the value of the SL DRX cycle is one of the values in parentheses. The unit of the value in parentheses is ms. Here, ms10 indicates 10 ms and ms20 indicates 20 ms. The rest may be estimated similarly. Here, spare can be understood as an idle or unused value.

[0315] In implementation, the SL DRX configuration is a choice type (CHOICE). For example, if the SL DRX configuration includes sl-DRX-OnDurationTimer, sl-DRX-OnDurationTimer is CHOICE{subMilliSeconds, milliSeconds}. Here, subMilliSeconds is an integer type (INTEGER) with a value range of 1 to 31, and the unit is 1 / 32 ms. That is, 1 indicates 1 / 32 ms, 2 indicates 2 / 32 ms, and so on. The rest may be estimated similarly. Here, milliSeconds is an enumeration type, with a range of values, e.g., {ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}, in ms. Here, ms1 indicates 1 ms and ms2 indicates 2 ms. The rest can be estimated similarly. Here, spare is an idle value, or can be understood as an unused value.

[0316] According to the above solution, compared to the method of transmitting an SL QoS profile in each SL DRX configuration, in this method, the configuration information transmits an SL DRX configuration corresponding to at least one SL QoS profile, thereby reducing signaling overhead and storage overhead.

[0317] The solution of the tenth embodiment may be used in conjunction with the solutions of the other embodiments, provided that no contradiction arises.

[0318] Embodiment 11 In this solution, the SL DRX configuration is configured for the terminal at the granularity of the SL QoS profile.

[0319] In a schematic diagram of a method for determining a SL DRX configuration according to an eleventh embodiment of the present application, the method includes the following steps:

[0320] Step 1X01: A terminal acquires configuration information, where the configuration information includes an SL DRX configuration corresponding to at least one SL QoS profile, or in other words, the configuration information includes a correspondence between at least one SL QoS profile and an SL DRX configuration.

[0321] The configuration information may be pre-configured, configured by the base station, configured by a core network element, or pre-defined in a protocol.

[0322] For example, the configuration information indicates the following correspondence: The index of the SL DRX configuration corresponding to SL QoS profile1 is 3; The index of the SL DRX configuration corresponding to SL QoS profile2 is 1; The index of the SL DRX configuration corresponding to SL QoS profile 3 is 3.

[0323] In an implementation, the configuration information further indicates at least one SL QoS profile. Specifically, the configuration information is used to configure the at least one SL QoS profile, and further to configure an index of an SL DRX configuration corresponding to the at least one SL QoS profile.

[0324] In implementation, the configuration information further indicates at least one SL DRX configuration, specifically, the configuration information is used to configure at least one SL DRX configuration, and further configures an index of the SL DRX configuration corresponding to at least one SL QoS profile.

[0325] In another implementation, instead of configuring the at least one SL DRX configuration using configuration information, the at least one SL DRX configuration is configured individually using separate configuration information, i.e., the at least one SL DRX configuration is configured using one piece of configuration information, and an index of the SL DRX configuration corresponding to the at least one SL QoS profile is configured using separate configuration information.

[0326] Step 1X02: The terminal determines a first SL DRX configuration corresponding to the first SL QoS profile based on the first SL QoS profile and an index of the SL DRX configuration corresponding to the at least one SL QoS profile.

[0327] Specifically, the terminal determines an index of the first SL DRX configuration corresponding to the first SL QoS profile based on the first SL QoS profile and an index of the SL DRX configuration corresponding to at least one SL QoS profile, and then determines that the first SL DRX configuration corresponding to the first SL QoS profile is an SL DRX configuration indexed by the index of the first SL DRX configuration.

[0328] According to the above solution, the terminal can determine an SL DRX configuration corresponding to the terminal or the service of the terminal device. For example, the terminal first determines a first SL QoS profile corresponding to the terminal or the service of the terminal, and then determines an SL DRX configuration corresponding to the first SL QoS profile based on the first SL QoS profile.

[0329] In implementation, the index of the SL DRX configuration is indicated by the position of the SL DRX configuration in the SL DRX configuration list. For example, the SL DRX configurations in the SL DRX configuration list are, in order, SL DRX configuration 1, SL DRX configuration 2, SL DRX configuration 3, ..., and SL DRX configuration N. The rest may be deduced similarly. In this case, the indices of the SL DRX configurations are in the order 1, 2, 3, ..., and N. For example, the configuration information indicates the following correspondence: SL QoS profile1 corresponds to 3; SL QoS profile2 corresponds to 1; SL QoS profile3 corresponds to 3.

[0330] where 1, 2, and 3 are the indices of the SL DRX configurations.

[0331] In an implementation, the configuration information further indicates at least one SL QoS profile. Specifically, the configuration information is used to configure the at least one SL QoS profile, and further to configure an index of an SL DRX configuration corresponding to the at least one SL QoS profile.

[0332] For example, the configuration information includes one or more SL-QoS-Profiles, each of which includes one or more of PQI, GFBR, MFBR, or range, and includes an index of the SL DRX configuration. The SL-QoS-Profiles are denoted as follows:

number

[0333] According to the above solution, compared to the method of transmitting an SL QoS profile in each SL DRX configuration, in this method, the configuration information transmits an index of an SL DRX configuration corresponding to at least one SL QoS profile, thereby reducing signaling overhead and storage overhead.

[0334] If no contradiction occurs, the solution of embodiment 11 may be used in combination with the solutions of other embodiments. In implementation, the correspondence between the standardized PQI and the SL DRX configuration may be further configured using configuration information. If the PQI corresponding to the sidelink unicast communication is a standardized PQI, both the transmitting terminal and the receiving terminal determine the same SL DRX configuration based on the configuration information. If the PQI corresponding to the sidelink unicast communication is a non-standardized PQI, one terminal may determine the SL DRX configuration and transmit indication information indicating the SL DRX configuration to the other terminal. If the PQI corresponding to the sidelink unicast communication includes a standardized PQI and a non-standardized PQI, one terminal may determine the SL DRX configuration and transmit indication information indicating the SL DRX configuration to the other terminal.

[0335] In implementation, the correspondence between the SL QoS profile / PQI and the value range of the SL DRX parameters can be further configured using configuration information. For example, the value range of the SL DRX parameters includes, for example, a value range of 2 ms to 10 ms for the sl-DRX-OnDurationTimer and a value range of 0 ms to 8 ms for the sl-DRX-InactivityTimer. One terminal determines an SL DRX configuration based on the QoS profile / PQI corresponding to sidelink unicast communication, and the values of the SL DRX parameters included in the determined SL DRX configuration are within the value range of the SL DRX parameters corresponding to the QoS profile / PQI. The terminal transmits indication information indicating the SL DRX configuration to the other terminal. In the information regarding the SL DRX configuration, the QoS profile / PQI may be indicated by the index of the QoS profile / PQI described in the fifth to ninth embodiments.

[0336] The relationship between embodiments 1 to 4 and embodiments 5 to 9 is that the correspondence between SL DRX configurations and QoS profiles / PQIs may be configured in the terminal using embodiments 5 to 9, and the correspondence may be used later. For example, for a destination layer-2 ID, the terminal has only one service corresponding to the destination layer-2 ID, and the service corresponds to one QoS profile / PQI. In this case, the terminal can determine the SL DRX configuration corresponding to the QoS profile / PQI based on the QoS profile / PQI and its correspondence. The terminal then uses the SL DRX configuration. In another example, for a destination layer-2 ID, the terminal has multiple services corresponding to the destination layer-2 ID, and each service corresponds to one QoS profile / PQI. In this case, the terminal can determine multiple QoS profiles / PQIs corresponding to the destination layer-2 ID, and then the terminal determines at least two SL DRX configurations based on the multiple QoS profiles / PQIs and their correspondence. Furthermore, the terminal can use the method of any one of the first to fourth embodiments to determine the SL DRX configuration to use from among at least two SL DRX configurations.

[0337] In implementation, when multiple PQIs are associated with one destination layer-2 ID, two methods can be considered. In method 1, first, one target PQI is selected from the multiple PQIs associated with the destination layer-2 ID. For example, the PQI with the lowest priority and / or the smallest PDB is selected. Then, the SL DRX configuration corresponding to the target PQI is selected as the SL DRX configuration to be used. In other words, the SL DRX configuration corresponding to the target PQI is used for the destination layer-2 ID. In method 2, first, multiple SL DRX configurations corresponding to the multiple PQIs are determined based on the multiple PQIs associated with the destination layer-2 ID, and then one target SL DRX configuration is selected from the multiple SL DRX configurations. For example, the selected target SL DRX configuration is the SL DRX configuration with the smallest SL DRX cycle among the multiple SL DRX configurations.

[0338] It can be understood that to realize the functions in the above embodiments, the base station and the terminal include corresponding hardware structures and / or software modules for performing the functions. Those skilled in the art should easily recognize that the present application can be implemented using hardware or a combination of hardware and computer software, in combination with the example units and method steps described in the embodiments disclosed herein. Whether the functions are performed using hardware or hardware driven by computer software depends on the specific application scenario and design constraints of the technical solution.

[0339] 19 and 20 are schematic diagrams of possible communication device structures according to embodiments of the present application. The communication device may be configured to implement the functions of a terminal or a base station in the above-described method embodiments. Thus, the beneficial effects of the above-described method embodiments can also be achieved. In this embodiment of the present application, the communication device may be any one of the terminals 120a to 120j shown in FIG. 1, or may be the base station 110a or 110b shown in FIG. 1, or may be a module (e.g., a chip) used in a terminal or a base station.

[0340] 19, the communication device 1900 includes a processing unit 1910 and a transceiver unit 1920. The communication device 1900 is configured to implement the functions of the terminals in the first to ninth embodiments.

[0341] In a first embodiment, the processing unit 1910 is configured to: determine at least two PQIs or sidelink QoS profiles corresponding to services of the terminal; determine at least two sidelink DRX configurations corresponding to the at least two PQIs or sidelink QoS profiles, each sidelink DRX configuration indicating one or more sidelink DRX parameters; and determine a sidelink DRX configuration to use based on the at least two sidelink DRX configurations.

[0342] In a possible implementation, the sidelink DRX configuration to use is a first sidelink DRX configuration, which is one of the at least two sidelink DRX configurations.

[0343] In a possible implementation, the value of the first parameter in the first sidelink DRX configuration is the minimum or maximum value of the values of the first parameter in the at least two sidelink DRX configurations, where the first parameter is one of the following parameters: the value of sl-DRX-OnDurationTimer, the value of sl-DRX-InactivityTimer, the value of sl-DRX-HARQ-RTT-Timer, the value of sl-DRX-RetransmissionTimer, the value of SLDRX cycle, the value of sl-DRX-startOffset, or the value of sl-DRX-slotOffset.

[0344] In a possible implementation, if the values of the first parameter in the plurality of sidelink DRX configurations in at least two sidelink DRX configurations are the minimum or maximum value, The processing unit 1910 is configured to determine a sidelink DRX configuration as the first sidelink DRX configuration when a value of the second parameter in only one sidelink DRX configuration among the plurality of sidelink DRX configurations is the smallest or largest value, or to determine one of the plurality of sidelink DRX configurations as the first sidelink DRX configuration when a value of the second parameter in multiple sidelink DRX configurations among the plurality of sidelink DRX configurations is the smallest or largest value.

[0345] In a possible implementation, the processing unit 1910 is configured to select a sidelink DRX configuration located at the beginning or end of the sidelink DRX configuration list as the first sidelink DRX configuration from the plurality of sidelink DRX configurations if the values of the first parameter in the plurality of sidelink DRX configurations in at least two sidelink DRX configurations are the smallest or largest value.

[0346] In a possible implementation, if the values of the first parameter in the plurality of sidelink DRX configurations in at least two sidelink DRX configurations are the smallest or largest value, the processing unit 1910 is configured to select the sidelink DRX configuration corresponding to the PQI having the smallest or largest value as the first sidelink DRX configuration from the plurality of sidelink DRX configurations.

[0347] In a possible implementation, if the value of the first parameter in the plurality of sidelink DRX configurations in at least two sidelink DRX configurations is the smallest or largest value, the processing unit 1910 is configured to select the sidelink DRX configuration corresponding to the PQI with the smallest or largest index as the first sidelink DRX configuration from the plurality of sidelink DRX configurations, or to select the sidelink DRX configuration corresponding to the sidelink QoS profile with the smallest or largest index as the first sidelink DRX configuration from the plurality of sidelink DRX configurations.

[0348] In a possible implementation, the first sidelink DRX configuration is determined based on at least one of the following parameters: distinct positions of the at least two sidelink DRX configurations in a sidelink DRX configuration list, values of PQIs corresponding to the at least two sidelink DRX configurations, indices of sidelink QoS profiles corresponding to the at least two sidelink DRX configurations, or indices of PQIs corresponding to the at least two sidelink DRX configurations.

[0349] In a possible implementation, the first sidelink DRX configuration is generated based on at least two sidelink DRX configurations, and values of parameters in the first sidelink DRX configuration are derived from one or more of the at least two sidelink DRX configurations.

[0350] In a possible implementation, the value of the first parameter included in the first sidelink DRX configuration is the minimum or maximum value of the values of the first parameter included in each of the at least two sidelink DRX configurations.

[0351] In a possible implementation, the sidelink DRX configurations to use are at least two sidelink DRX configurations.

[0352] In a possible implementation, each of the at least two sidelink DRX configurations comprises the duration of one or more of the following timers: sl-DRX-onDurationTimer, sl-DRX-inactivityTimer, sl-DRX-HARQ-RTT-Timer, or sl-DRX-RetransmissionTimer. The sidelink active time corresponding to a terminal comprises one or the union of the following execution times: the execution time of the sl-DRX-onDurationTimer corresponding to each sidelink DRX configuration, the execution time of the sl-DRX-inactivityTimer corresponding to each sidelink DRX configuration, or the execution time of the sl-DRX-RetransmissionTimer corresponding to each sidelink DRX configuration.

[0353] In a possible implementation, each of the at least two sidelink DRX configurations comprises a duration of one or more of the following timers: sl-DRX-onDurationTimer, sl-DRX-inactivityTimer, sl-DRX-HARQ-RTT-Timer, or sl-DRX-RetransmissionTimer. The sidelink active time corresponding to the terminal comprises one or a union of the following execution times: an execution time of the sl-DRX-onDurationTimer corresponding to each sidelink DRX configuration, an execution time of a first sl-DRX-inactivityTimer corresponding to the second sidelink DRX configuration, or an execution time of a first sl-DRX-RetransmissionTimer corresponding to the third sidelink DRX configuration. The second and third sidelink DRX configurations are different ones of the at least two sidelink DRX configurations.

[0354] In a possible implementation, the first sl-DRX-inactivityTimer value is the minimum or maximum of the sl-DRX-inactivityTimer values corresponding to at least two sidelink DRX configurations, respectively, and / or the first sl-DRX-RetransmissionTimer value is the minimum or maximum of the sl-DRX-RetransmissionTimer values corresponding to at least two sidelink DRX configurations, respectively.

[0355] In the second embodiment, the processing unit 1910 is configured to acquire configuration information, where the configuration information includes an index of a PQI corresponding to at least one sidelink DRX configuration, and to determine a first sidelink DRX configuration corresponding to the index of the first PQI based on the index of the first PQI and the index of the PQI corresponding to the at least one sidelink DRX configuration.

[0356] In a possible implementation, the processing unit 1910 is configured to determine a first PQI corresponding to the terminal, and determine an index of the first PQI based on the first PQI.

[0357] In a possible implementation, if the PQI is a standardized PQI, the index of the PQI is the value of the standardized PQI, or the index of the PQI is the index of the sidelink QoS profile that includes the standardized PQI.

[0358] In a possible implementation, if the PQI is a standardized PQI, the processing unit 1910 is configured to obtain at least one non-standardized PQI, each non-standardized PQI corresponding to one indication information, where the indication information indicates a standardized PQI corresponding to the same sidelink DRX configuration as the non-standardized PQI, or each non-standardized PQI corresponds to one default sidelink DRX configuration, or each non-standardized PQI corresponds to one common sidelink DRX configuration.

[0359] In a possible implementation, if the PQI is a non-standardized PQI, the index of the PQI is the index of the sidelink QoS profile including the non-standardized PQI, or the index of the PQI is the index of the non-standardized PQI included in the sidelink RB configuration, or the index of the PQI is indicated by the index of the sidelink RB configuration corresponding to the sidelink QoS profile including the non-standardized PQI and the index of the non-standardized PQI in the sidelink RB configuration.

[0360] In the third embodiment, the processing unit 1910 is configured to acquire configuration information, the configuration information including an index of a sidelink QoS profile corresponding to at least one sidelink DRX configuration, and to determine a first sidelink DRX configuration corresponding to the index of the first sidelink QoS profile based on the index of the first sidelink QoS profile and the index of the sidelink QoS profile corresponding to the at least one sidelink DRX configuration.

[0361] In a possible implementation, the processing unit 1910 is configured to determine a first sidelink QoS profile corresponding to the terminal and to determine an index of the first sidelink QoS profile based on the first sidelink QoS profile.

[0362] In a possible implementation, the index of a sidelink QoS profile is indicated by the position of the sidelink QoS profile in the sidelink QoS profile list corresponding to the sidelink RB configuration, or the index of a sidelink QoS profile is indicated by the index of the sidelink RB configuration corresponding to the sidelink QoS profile and the position of the sidelink QoS profile in the sidelink QoS profile list corresponding to the sidelink RB configuration.

[0363] In the fourth embodiment, the processing unit 1910 is configured to acquire configuration information, the configuration information including indices of side RB configurations corresponding to at least one sidelink DRX configuration, each side RB configuration corresponding to at least one PQI, and determine a first sidelink DRX configuration corresponding to the index of the first PQI based on the first PQI and the indices of the sidelink RB configurations corresponding to the at least one sidelink DRX configuration.

[0364] In a possible implementation, the processing unit 1910 is configured to determine an index of a first sidelink RB configuration corresponding to the first PQI, and to determine the first sidelink DRX configuration corresponding to the index of the first sidelink RB configuration based on the index of the first sidelink RB configuration and the index of a sidelink RB configuration corresponding to at least one sidelink DRX configuration.

[0365] In a possible implementation, the index of the first sidelink RB configuration is indicated by the position of the first sidelink RB configuration in the sidelink RB configuration list.

[0366] In the fifth embodiment, the processing unit 1910 The method is configured to acquire configuration information, the configuration information including indices of side RB configurations corresponding to at least one sidelink DRX configuration, each side RB configuration corresponding to at least one sidelink QoS profile, and determine a first sidelink DRX configuration corresponding to the index of the first sidelink QoS profile based on the first sidelink QoS profile and the indices of the sidelink RB configurations corresponding to the at least one sidelink DRX configuration.

[0367] In a possible implementation, the processing unit 1910 is configured to determine an index of a first sidelink RB configuration corresponding to the first sidelink QoS profile, and to determine the first sidelink DRX configuration corresponding to the index of the first sidelink RB configuration based on the index of the first sidelink RB configuration and the index of a sidelink RB configuration corresponding to at least one sidelink DRX configuration.

[0368] In a possible implementation, the index of the first sidelink RB configuration is indicated by the position of the first sidelink RB configuration in the sidelink RB configuration list.

[0369] For further detailed descriptions of the processing unit 1910 and the transceiver unit 1920, please refer to the relevant descriptions in Embodiments 1 to 9. The details will not be described again here.

[0370] 20 , the communication device 2000 includes a processor 2010 and an interface circuit 2020. The processor 2010 and the interface circuit 2020 are coupled to each other. It can be understood that the interface circuit 2020 may be a transceiver or an input / output interface. Optionally, the communication device 2000 may further include a memory 2030 configured to store instructions to be executed by the processor 2010, or to store input data required for the processor 2010 to execute the instructions, or to store data generated after the processor 2010 executes the instructions.

[0371] When the communication device 2000 is configured to implement embodiments 1 to 11, the processor 2010 is configured to implement the functions of the processing unit 1910, and the interface circuit 2020 is configured to implement the functions of the transceiver unit 1920.

[0372] When the communication device is a chip used in a terminal, the chip in the terminal implements the functions of the terminal in embodiments 1 to 11 and the functions of the terminal in other embodiments. The chip in the terminal receives information from another module in the terminal (e.g., a radio frequency module or an antenna), and the information is transmitted to the terminal by the base station. Alternatively, the chip in the terminal transmits information to another module in the terminal (e.g., a radio frequency module or an antenna), and the information is transmitted by the terminal to the base station.

[0373] It should be understood that the processor in the embodiments of the present application may be a Central Processing Unit (CPU), or may be another general-purpose processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic element, a transistor logic element, a hardware component, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0374] The steps of the method in the embodiments of the present application may be implemented using hardware or by a processor executing software instructions. The software instructions may include corresponding software modules. The software modules may be stored in random access memory, flash memory, read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage medium well known in the art. For example, the storage medium may be coupled to the processor such that the processor can read information from and write information to the storage medium. Of course, the storage medium may be components of the processor. The processor and the storage medium may be located in an ASIC. Furthermore, the ASIC may be located in a base station or a terminal. Of course, the processor and the storage medium may alternatively reside in separate components within the base station or terminal.

[0375] All or part of the above-described embodiments may be implemented using software, hardware, firmware, or any combination thereof. When software is used to implement an embodiment, all or part of the embodiment may be implemented in the form of a computer program product. The computer program product includes one or more computer program instructions. When the computer program instructions are loaded and executed on a computer, all or part of the procedures or functions of the embodiments of the present application are performed. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a base station, user equipment, or another programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer program or instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center via a wired or wireless manner. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device such as a server or data center that integrates one or more available media. The usable medium may be a magnetic medium such as a floppy disk, hard disk, or magnetic tape, or an optical medium such as a digital video disk, or a semiconductor medium such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include two types of storage media: volatile and non-volatile storage media.

[0376] In the embodiments of the present application, unless otherwise specified or there is no logical contradiction, the terms and / or descriptions between different embodiments are consistent and can be mutually referenced, and the technical features in different embodiments can be combined based on their internal logical relationships to form a new embodiment.

[0377] In this application, "at least one" means one or more, and "multiple" means two or more. The term "and / or" describes an association relationship between associated objects and indicates that three relationships may exist. For example, A and / or B may indicate three cases: only A is present, A and both are present, and only B is present, where A and B may be singular or plural. In descriptions in the text of this application, the character " / " typically indicates an "or" relationship between associated objects. In formulas of this application, the character " / " represents a "divide by" relationship between related objects.

[0378] It should be further understood that various numbers in the embodiments of the present application are distinguished merely for ease of description and are not used to limit the scope of the embodiments of the present application. The sequence numbers of the above processes do not mean the execution sequence, and the execution sequence of the processes should be determined based on the function and internal logic of the processes.

Claims

1. 1. A method for determining a sidelink discontinuous reception (DRX) configuration, comprising: determining at least two PQIs or sidelink Quality of Service (QoS) profiles corresponding to destination layer-2 IDs; determining at least two sidelink DRX configurations corresponding to the at least two PQIs or sidelink QoS profiles, each sidelink DRX configuration indicating one or more sidelink DRX parameters; determining a sidelink DRX configuration for the destination layer-2 ID based on the at least two sidelink DRX configurations; A method comprising:

2. 2. The method of claim 1, wherein the determined sidelink DRX configuration for the destination layer-2 ID is a first sidelink DRX configuration, and the first sidelink DRX configuration is one of the at least two sidelink DRX configurations.

3. a value of a first parameter in the first sidelink DRX configuration is a minimum value or a maximum value among values of the first parameter in the at least two sidelink DRX configurations; 3. The method of claim 2, wherein the first parameter is any one of the following parameters: a value of a sidelink DRX on-duration timer (sl-DRX-OnDurationTimer), a value of a sidelink DRX inactivity timer (sl-DRX-InactivityTimer), a value of a sidelink DRX hybrid automatic repeat request round-trip time timer (sl-DRX-HARQ-RTT-Timer), a value of a sidelink DRX retransmission timer (sl-DRX-RetransmissionTimer), a value of a sidelink DRX cycle (SL DRX cycle), a value of a sidelink DRX start offset (sl-DRX-startOffset), or a value of a sidelink DRX slot offset (sl-DRX-slotOffset).

4. when a value of the first parameter in a plurality of sidelink DRX configurations in the at least two sidelink DRX configurations is a minimum value or a maximum value, the first sidelink DRX configuration is determined by a second parameter in addition to the first parameter; determining the sidelink DRX configuration according to the second parameter as the first sidelink DRX configuration when a value of the second parameter in only one sidelink DRX configuration among the plurality of sidelink DRX configurations is the smallest or largest; or determining one of the plurality of sidelink DRX configurations as the first sidelink DRX configuration when a value of a second parameter in the plurality of sidelink DRX configurations is the smallest or largest; the second parameter is one of the following parameters: a value of a sidelink DRX on-duration timer (sl-DRX-OnDurationTimer), a value of a sidelink DRX inactivity timer (sl-DRX-InactivityTimer), a value of a sidelink DRX hybrid automatic repeat request round-trip time timer (sl-DRX-HARQ-RTT-Timer), a value of a sidelink DRX retransmission timer (sl-DRX-RetransmissionTimer), a value of a sidelink DRX cycle (SL DRX cycle), a value of a sidelink DRX start offset (sl-DRX-startOffset), or a value of a sidelink DRX slot offset (sl-DRX-slotOffset); the second parameter is different from the first parameter; The method of claim 3.

5. when values of the first parameter in the plurality of sidelink DRX configurations in the at least two sidelink DRX configurations are the minimum value or the maximum value, 4. The method of claim 3, wherein a sidelink DRX configuration located at the top or the bottom of a sidelink DRX configuration list is selected as the first sidelink DRX configuration from the plurality of sidelink DRX configurations.

6. when values of the first parameter in the plurality of sidelink DRX configurations in the at least two sidelink DRX configurations are the minimum value or the maximum value, 4. The method of claim 3, further comprising selecting a sidelink DRX configuration corresponding to a PQI having a minimum or maximum value as the first sidelink DRX configuration from the plurality of sidelink DRX configurations.

7. when values of the first parameter in the plurality of sidelink DRX configurations in the at least two sidelink DRX configurations are the minimum value or the maximum value, selecting a sidelink DRX configuration corresponding to a PQI with a smallest or largest index as the first sidelink DRX configuration from the plurality of sidelink DRX configurations, or selecting a sidelink DRX configuration corresponding to a sidelink QoS profile with a smallest or largest index as the first sidelink DRX configuration from the plurality of sidelink DRX configurations. The method of claim 3.

8. The first sidelink DRX configuration is determined based on at least one of the following parameters: - separate positions of the at least two sidelink DRX configurations in a sidelink DRX configuration list. PQI values respectively corresponding to the at least two sidelink DRX configurations; indices of sidelink QoS profiles respectively corresponding to the at least two sidelink DRX configurations; or 3. The method of claim 2, wherein an index of a PQI corresponding to each of the at least two sidelink DRX configurations is selected.

9. The method described in claim 1, wherein the sidelink DRX configuration determined for the destination layer-2 ID is a first sidelink DRX configuration, the first sidelink DRX configuration is generated based on the at least two sidelink DRX configurations, and values of parameters in the first sidelink DRX configuration are derived from one or more of the at least two sidelink DRX configurations.

10. 10. The method of claim 9, wherein a value of the first parameter included in the first sidelink DRX configuration is the minimum or maximum value of values of the first parameter included in each of the at least two sidelink DRX configurations.

11. each of the at least two sidelink DRX configurations comprising the duration of one or more of the following timers: sl-DRX-onDurationTimer, sl-DRX-inactivityTimer, sl-DRX-HARQ-RTT-Timer, or sl-DRX-RetransmissionTimer; The sidelink active time corresponding to the terminal comprises one or the union of the following execution times: an execution time of the sl-DRX-onDurationTimer corresponding to each sidelink DRX configuration, an execution time of the sl-DRX-inactivityTimer corresponding to each sidelink DRX configuration, or an execution time of the sl-DRX-RetransmissionTimer corresponding to each sidelink DRX configuration.

10. The method of claim 9.

12. each of the at least two sidelink DRX configurations comprising the duration of one or more of the following timers: sl-DRX-onDurationTimer, sl-DRX-inactivityTimer, sl-DRX-HARQ-RTT-Timer, or sl-DRX-RetransmissionTimer; the sidelink active time corresponding to the terminal comprises one or a union of the following execution times: execution time of the sl-DRX-onDurationTimer corresponding to each sidelink DRX configuration, execution time of a first sl-DRX-inactivityTimer corresponding to a second sidelink DRX configuration, or execution time of a first sl-DRX-RetransmissionTimer corresponding to a third sidelink DRX configuration; 10. The method of claim 9, wherein the second sidelink DRX configuration and the third sidelink DRX configuration are different ones of the at least two sidelink DRX configurations.

13. the first sl-DRX-inactivityTimer value is the minimum or maximum value of the sl-DRX-inactivityTimer values respectively corresponding to the at least two sidelink DRX configurations; and / or 13. The method of claim 12, wherein the first sl-DRX-RetransmissionTimer value is the minimum or maximum value of the sl-DRX-RetransmissionTimer values corresponding to the at least two sidelink DRX configurations, respectively.

14. 14. A communications device comprising a processor and an interface circuit, the interface circuit configured to receive signals from a communications device other than the communications device and to transmit the signals to the processor, or to transmit signals from the processor to a communications device other than the communications device, the processor configured to perform a method according to any one of claims 1 to 13 by means of logic circuits or by executing code instructions.

15. A computer-readable storage medium having stored thereon a computer program or instructions which, when executed by a processor, perform the method of any one of claims 1 to 13.

Images