WO2022188692A1 - 一种旁链路drx配置的确定方法及通信装置 - Google Patents

一种旁链路drx配置的确定方法及通信装置 Download PDF

Info

Publication number
WO2022188692A1
WO2022188692A1 PCT/CN2022/079105 CN2022079105W WO2022188692A1 WO 2022188692 A1 WO2022188692 A1 WO 2022188692A1 CN 2022079105 W CN2022079105 W CN 2022079105W WO 2022188692 A1 WO2022188692 A1 WO 2022188692A1
Authority
WO
WIPO (PCT)
Prior art keywords
drx
configuration
sidelink
configurations
drx configuration
Prior art date
Application number
PCT/CN2022/079105
Other languages
English (en)
French (fr)
Inventor
才宇
徐海博
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2023555156A priority Critical patent/JP2024510581A/ja
Priority to CN202280020452.9A priority patent/CN117413548A/zh
Priority to EP22766218.6A priority patent/EP4297444A1/en
Priority to BR112023018228A priority patent/BR112023018228A2/pt
Publication of WO2022188692A1 publication Critical patent/WO2022188692A1/zh
Priority to US18/463,015 priority patent/US20230422344A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/188—Time-out mechanisms
    • H04L1/1883—Time-out mechanisms using multiple timers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
    • H04W52/028—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof switching on or off only a part of the equipment circuit blocks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
    • H04L1/0017—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • 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.
  • LTE Long Term Evolution
  • 3GPP 3rd Generation Partnership Project
  • SL sidelink
  • DRX sidelink discontinuous reception
  • the present application provides a method and a communication device for determining a sidelink DRX configuration, so as to select an appropriate sidelink DRX configuration for use, thereby improving the communication efficiency between terminals.
  • an embodiment of the present application provides a method for determining a sidelink DRX configuration, and the method may be executed by a terminal or a module applied in the terminal.
  • the method includes: determining at least two PQIs or sidelink QoS profiles corresponding to services of the terminal; determining at least two sidelink DRX configurations corresponding to the at least two PQIs or sidelink QoS profiles, wherein each sidelink The channel DRX configuration indicates one or more sidelink DRX parameters; according to the at least two sidelink DRX configurations, the used sidelink DRX configuration is determined.
  • the used sidelink DRX configuration is a first sidelink DRX configuration
  • the first sidelink DRX configuration is one of the at least two sidelink DRX configurations.
  • one sidelink DRX configuration is selected and used from at least two sidelink DRX configurations. Since only one sidelink DRX configuration is used, energy consumption of the terminal can be reduced.
  • the value of the first parameter configured by the first sidelink DRX is the minimum value or the maximum value among the values of the first parameter configured by the at least two sidelink DRXs;
  • the first parameter is any 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- The value of RetransmissionTimer, the value of SL DRX cycle, the value of sl-DRX-startOffset, and the value of sl-DRX-slotOffset.
  • the value of the first parameter of multiple sidelink DRX configurations in the at least two sidelink DRX configurations is a minimum value or a maximum value
  • the multiple sidelink DRX configurations are In the link DRX configuration
  • the value of the second parameter of multiple sidelink DRX configurations in the channel DRX configuration is the smallest or the largest, then it is determined that one sidelink DRX configuration in the multiple sidelink DRX configurations is the first sidelink DRX configuration .
  • the value of the first parameter of multiple sidelink DRX configurations in the at least two sidelink DRX configurations is a minimum value or a maximum value
  • the link DRX configuration the side link DRX configuration that is ranked most forward or last in the side link DRX configuration list is used as the first side link DRX configuration.
  • the value of the first parameter of multiple sidelink DRX configurations in the at least two sidelink DRX configurations is a minimum value or a maximum value
  • the sidelink DRX configuration with the smallest or largest value of the corresponding PQI in the link DRX configuration is used as the first sidelink DRX configuration.
  • the value of the first parameter of multiple sidelink DRX configurations in the at least two sidelink DRX configurations is a minimum value or a maximum value
  • the sidelink DRX configuration with the smallest or largest index of the corresponding PQI in the link DRX configuration is used as the first sidelink DRX configuration; or, selecting the sidelink QoS profile corresponding to the multiple sidelink DRX configurations.
  • the sidelink DRX configuration with the smallest or largest index is used as the first sidelink DRX configuration.
  • the first sidelink DRX configuration is determined according to at least one of the following parameters: the ordering of at least two sidelink DRX configurations in the sidelink DRX configuration list respectively; The values of the PQIs corresponding to the link DRX configurations respectively; the indices of the sidelink QoS profiles corresponding to the at least two sidelink DRX configurations respectively; or the indices of the PQIs corresponding to the at least two sidelink DRX configurations respectively.
  • the first sidelink DRX configuration is generated according to the at least two sidelink DRX configurations, and values of parameters in the first sidelink DRX configuration come from the at least two sidelink DRX configurations One or more of the sidelink DRX configurations in the sidelink DRX configuration.
  • one sidelink DRX configuration is generated and used according to at least two sidelink DRX configurations. Since only one sidelink DRX configuration is used, the energy consumption of the terminal can be reduced. And since the used sidelink DRX configuration is regenerated, the flexibility of selecting the sidelink DRX configuration can be increased.
  • the value of the first parameter included in the first sidelink DRX configuration is the minimum value among the values of the first parameters included in the at least two sidelink DRX configurations respectively, or maximum value.
  • the used sidelink DRX configuration is the at least two sidelink DRX configurations.
  • At least two sidelink DRX configurations are used as the used sidelink DRX configurations. Since multiple sidelink DRX configurations are used, the sidelink activation time of the terminal can be increased, thereby increasing the number of sidelinks between terminals. The success rate of communication can improve the communication efficiency.
  • each sidelink DRX configuration in the at least two sidelink DRX configurations includes 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 activation time corresponding to the terminal includes one of the following running times or the union of multiple running times: the sl- The running time of the DRX-onDurationTimer, the running time of the sl-DRX-inactivityTimer corresponding to each sidelink DRX configuration, or the running time of the sl-DRX-RetransmissionTimer corresponding to each sidelink DRX configuration.
  • each sidelink DRX configuration in the at least two sidelink DRX configurations includes 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 activation time corresponding to the terminal includes one of the following running times or the union of multiple running times: the sl- The running time of the DRX-onDurationTimer, the running time of the first sl-DRX-inactivityTimer corresponding to the second sidelink DRX configuration, or the running time of the first sl-DRX-RetransmissionTimer corresponding to the third sidelink DRX configuration;
  • the second sidelink DRX configuration and the third sidelink DRX configuration are each one of the at least two sidelink DRX configurations.
  • the value of the first sl-DRX-inactivityTimer is the minimum value or the maximum value among the values of the sl-DRX-inactivityTimer corresponding to the at least two sidelink DRX configurations respectively; and /or, the value of the first sl-DRX-RetransmissionTimer is the minimum value or the maximum value among the values of the sl-DRX-RetransmissionTimer corresponding to the at least two sidelink DRX configurations respectively.
  • an embodiment of the present application provides a method for determining a sidelink DRX configuration, and the method may be performed by a terminal or a module applied in the terminal.
  • the method includes: acquiring configuration information, the configuration information including indices of PQIs corresponding to at least one sidelink DRX configuration respectively; The first sidelink DRX configuration corresponding to the index of the first PQI.
  • the terminal can determine the SL DRX configuration corresponding to each PQI. Moreover, since the PQI index corresponding to each sidelink DRX configuration is carried in the configuration information instead of carrying the PQI, signaling overhead and storage overhead can be reduced.
  • the first PQI corresponding to the terminal is determined; and the index of the first PQI is determined according to the first PQI.
  • the index of the PQI is a value of the standard PQI; or, the index of the PQI is an index of a sidelink QoS template including the standard PQI.
  • the PQI is a standard PQI
  • at least one non-standard PQI is obtained; wherein, each non-standard PQI corresponds to one indication information, and the indication information is used to indicate that the non-standard PQI corresponds to the non-standard PQI.
  • the index of the PQI is an index of a sidelink QoS template containing the non-standard PQI; or, the index of the PQI is a sidelink RB configuration
  • the index of the non-standard PQI contained in; or, the index of the PQI is the index of the side-link RB configuration corresponding to the side-link QoS template containing the non-standard PQI and the non-standard PQI in the side-link RB configuration to represent the index in .
  • an embodiment of the present application provides a method for determining a sidelink DRX configuration, and the method may be performed by a terminal or a module applied in the terminal.
  • the method includes: acquiring configuration information, the configuration information including an index of a sidelink QoS profile corresponding to at least one sidelink DRX configuration respectively; according to the index of the first sidelink QoS profile, and the at least one sidelink DRX configuration
  • the indexes of the corresponding side-link QoS profiles are respectively used to determine the first side-link DRX configuration corresponding to the indexes of the first side-link QoS profiles.
  • the terminal can determine the SL DRX configuration corresponding to each sidelink QoS profile. Moreover, since the index of the sidelink QoS profile corresponding to each sidelink DRX configuration is carried in the configuration information instead of the sidelink QoS profile, signaling overhead and storage overhead can be reduced.
  • a first side link QoS profile corresponding to the terminal is determined; and an index of the first side link QoS profile is determined according to the first side link QoS profile.
  • the index of the sidelink QoS template is represented by the order of the sidelink QoS template in the sidelink QoS template corresponding to the sidelink RB configuration list; or, the sidelink QoS template
  • the index of the road QoS template is represented by the index of the sidelink RB configuration corresponding to the sidelink QoS template and the order of the sidelink QoS template in the sidelink QoS template corresponding to the sidelink RB configuration.
  • an embodiment of the present application provides a method for determining a sidelink DRX configuration, and the method may be performed by a terminal or a module applied in the terminal.
  • the method includes: acquiring configuration information, the configuration information including indexes of sidelink RB configurations corresponding to at least one sidelink DRX configuration respectively, each sidelink RB configuration corresponding to at least one PQI; according to the first PQI and the at least one The indexes of the sidelink RB configurations corresponding to the sidelink DRX configurations respectively are determined, and the first sidelink DRX configuration corresponding to the index of the first PQI is determined.
  • the terminal can determine the SL DRX configuration corresponding to each PQI. Moreover, since the index of the sidelink RB configuration corresponding to each sidelink DRX configuration is carried in the configuration information, instead of carrying the sidelink RB configuration, signaling overhead and storage overhead can be reduced.
  • an index of the first sidelink RB configuration corresponding to the first PQI is determined; according to the index of the first sidelink RB configuration, and the at least one sidelink DRX configuration corresponding respectively
  • the index of the sidelink RB configuration is to determine the first sidelink DRX configuration corresponding to the index of the first sidelink RB configuration.
  • the index of the first sidelink RB configuration is represented by an order of the first sidelink RB configuration in the sidelink RB configuration list.
  • an embodiment of the present application provides a method for determining a sidelink DRX configuration, and the method may be executed by a terminal or a module applied in the terminal.
  • the method includes: acquiring configuration information, the configuration information including indexes of sidelink RB configurations corresponding to at least one sidelink DRX configuration respectively, each sidelink RB configuration corresponding to at least one sidelink QoS profile;
  • the link QoS profile and the indexes of the sidelink RB profiles corresponding to the at least one sidelink DRX profile respectively determine the first sidelink DRX profile corresponding to the first sidelink QoS profile.
  • the terminal can determine the SL DRX configuration corresponding to each sidelink QoS profile. Moreover, since the index of the sidelink RB configuration corresponding to each sidelink DRX configuration is carried in the configuration information, instead of carrying the sidelink RB configuration, signaling overhead and storage overhead can be reduced.
  • an index of the first sidelink RB configuration corresponding to the first sidelink QoS profile is determined; according to the indexes of the sidelink RB configuration corresponding to the at least one sidelink DRX configuration, respectively, and the index of the first sidelink RB configuration, to determine the first sidelink DRX configuration corresponding to the index of the first sidelink RB configuration.
  • the index of the first sidelink RB configuration is represented by an order of the first sidelink RB configuration in the sidelink RB configuration list.
  • an embodiment of the present application provides a communication device, including a processor and an interface circuit, where the interface circuit is configured to receive signals from other communication devices other than the communication device and transmit to the processor or transfer signals from the processor
  • the processor sends the signal of the processor to other communication devices other than the communication device, and the processor is used for implementing any of the implementation methods in the first aspect to the fifth aspect above through a logic circuit or executing code instructions.
  • an embodiment of the present application provides a communication device, including a processor coupled to a memory, where the processor is configured to call a program stored in the memory to execute any implementation method in the first to fifth aspects above .
  • the memory may be located within the device or external to the device.
  • the processor can be one or more.
  • an embodiment of the present application provides a communication device, including a processor and a memory; the memory stores computer instructions, and when the communication device runs, the processor executes the computer instructions stored in the memory, so that the communication device Any implementation method in the above-mentioned first to fifth aspects is performed.
  • an embodiment of the present application provides a communication device, where the device may be a terminal or a module applied in the terminal.
  • the apparatus has the function of implementing any of the implementation methods of the first aspect to the fifth aspect above. This function can be implemented by hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an embodiment of the present application provides a communication apparatus, including a module for implementing any of the implementation methods in the first aspect to the fifth aspect.
  • an embodiment of the present application provides a terminal, configured to execute any implementation method in the foregoing first aspect to the fifth aspect.
  • embodiments of the present application further provide a computer program product, where the computer program product includes a computer program, and when the computer program is executed by a processor, implements any of the foregoing implementation methods in the first to fifth aspects.
  • an embodiment of the present application further provides a computer-readable storage medium, where a computer program or instruction is stored in the storage medium, and when the computer program or instruction is executed by a processor, the above-mentioned first to fifth aspects are implemented Any implementation method in the aspect.
  • FIG. 1 is a schematic structural diagram of a communication system to which an embodiment of the present application is applied;
  • Figure 2 is a schematic diagram of the running time of sl-DRX-OnDurationTimer
  • Figure 3 is a schematic diagram of the running time of sl-DRX-InactivityTimer
  • Figure 4 is a schematic diagram of the running time of sl-DRX-RetransmissionTimer
  • Fig. 5 is the running time schematic diagram of sl-DRX-HARQ-RTT-Timer
  • FIG. 6 is a schematic diagram of a method for determining an SL DRX configuration provided by an embodiment of the present application
  • FIG. 7 is a schematic diagram of a method for determining an SL DRX configuration provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of the running time of sl-DRX-OnDurationTimer corresponding to different SL DRX configurations
  • FIG. 9 is a schematic diagram of the running time of sl-DRX-InactivityTimer and sl-DRX-OnDurationTimer corresponding to different SL DRX configurations;
  • Figure 10 is a schematic diagram of the running time of sl-DRX-RetransmissionTimer and sl-DRX-OnDurationTimer corresponding to different SL DRX configurations;
  • FIG. 11 is a schematic diagram of a method for determining an SL DRX configuration provided by an embodiment of the present application.
  • FIG. 12 is a schematic diagram of the running time of sl-DRX-OnDurationTimer corresponding to different SL DRX configurations and the running time of the first sl-DRX-InactivityTimer;
  • FIG. 13 is a schematic diagram of the running time of the sl-DRX-OnDurationTimer corresponding to different SL DRX configurations and the running time of the first sl-DRX-RetransmissionTimer;
  • Figure 14 is a schematic diagram of the running time of sl-DRX-OnDurationTimer and the running time of sl-DRX-InactivityTimer corresponding to different SL DRX configurations;
  • Figure 15 is a schematic diagram of the running time of sl-DRX-OnDurationTimer and the running time of sl-DRX-InactivityTimer corresponding to different SL DRX configurations;
  • 16 is a schematic diagram of a method for determining an SL DRX configuration provided by an embodiment of the present application
  • 17 is a schematic diagram of a method for determining an SL DRX configuration provided by an embodiment of the present application.
  • FIG. 18(a) is a schematic diagram of a method for determining a DRX configuration provided by an embodiment of the present application
  • FIG. 18(b) is a schematic diagram of a method for determining a DRX configuration provided by an embodiment of the present application.
  • FIG. 19 is a schematic diagram of a communication device according to an embodiment of the present application.
  • FIG. 20 is a schematic diagram of a communication apparatus provided by an embodiment of the present application.
  • FIG. 1 is a schematic structural diagram of a communication system to which an embodiment of the present application is applied.
  • the communication system 1000 includes a radio access network 100 and a core network 200 .
  • the communication system 1000 may further include the Internet 300 .
  • the radio access network 100 may include at least one radio access network device (such as 110a and 110b in FIG. 1 ), and may also include at least one terminal (such as 120a-120j in FIG. 1 ).
  • the terminal is connected to the wireless access network device in a wireless way, and the wireless access network device is connected to the core network in a wireless or wired way.
  • the core network device and the radio access network device can be independent and different physical devices, or the functions of the core network device and the logical functions of the radio access network device can be integrated on the same physical device, or they can be one physical device. It integrates the functions of some core network equipment and some functions of the wireless access network equipment. Terminals and terminals and wireless access network devices and wireless access network devices may be connected to each other in a wired or wireless manner.
  • FIG. 1 is just a schematic diagram, and the communication system may also include other network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in FIG. 1 .
  • the radio access network equipment can be a base station (base station), an evolved base station (evolved NodeB, eNodeB), a transmission reception point (transmission reception point, TRP), the next generation in the fifth generation (5th generation, 5G) mobile communication system Base station (next generation NodeB, gNB), next generation base station in 6th generation (6G) mobile communication system, base station in future mobile communication system or access node in wireless fidelity (WiFi) system It can also be a module or unit that completes some functions of the base station, for example, it can be a centralized unit (central unit, CU), or it can be a distributed unit (distributed unit, DU).
  • the radio access network device may be a macro base station (110a in FIG.
  • a base station is used as an example of a radio access network device for description.
  • a terminal may also be referred to as terminal equipment, user equipment (UE), mobile station, mobile terminal, and the like.
  • Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things ( internet of things, IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc.
  • Terminals can be mobile phones, tablet computers, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc.
  • the embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal.
  • sidelink (sidelink, SL) communication may be performed between terminals.
  • Different terminals may correspond to the same serving cell, or may correspond to different serving cells.
  • Base stations and terminals can be fixed or mobile. Base stations and terminals can be deployed on land, including indoor or outdoor, hand-held or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of the present application do not limit the application scenarios of the base station and the terminal.
  • the helicopter or drone 120i in FIG. 1 may be configured as a mobile base station, for those terminals 120j accessing the radio access network 100 through 120i, the terminal 120i is Base station; but for base station 110a, 120i is a terminal, that is, communication between 110a and 120i is performed through a wireless air interface protocol.
  • the communication between 110a and 120i may also be performed through an interface protocol between the base station and the base station.
  • both the base station and the terminal may be collectively referred to as communication devices, 110a and 110b in FIG. 1 may be referred to as communication devices with base station functions, and 120a-120j in FIG. 1 may be referred to as communication devices with terminal functions.
  • sidelink communication is also called SL communication, sidelink communication, bypass communication, sidelink communication or sidelink communication.
  • Sidelink communication refers to direct communication between two adjacent terminals without going through any network nodes.
  • Sidelink communication using new radio (NR) technology may be referred to as NR sidelink communication.
  • the source terminal is also called the terminal on the sending side, and the destination terminal is also called the terminal on the receiving side.
  • the source terminal can be identified by the source layer-2 ID, and the target terminal can be identified by the destination layer-2 ID.
  • the terminal on the sending side refers to the source of the sidelink communication (or a media access control (MAC) protocol data unit (PDU)), and the terminal on the receiving side refers to the sidelink communication (or a media access control (MAC) protocol data unit, PDU) source. a MAC PDU) destination.
  • MAC media access control
  • the Layer-2 ID of the terminal is the source layer-2 ID
  • the Layer-2 ID of the terminal on the receiving side is the destination layer-2 ID
  • the Layer-2 ID of the terminal on the sending side is the source layer-2 ID
  • source layer-2 ID can also be referred to as source ID
  • destination layer-2 ID can also be referred to as destination ID
  • the source Layer-2 ID is allocated by the terminal on the sending side itself.
  • the destination Layer-2 ID depends on the terminal on the receiving side.
  • PC5 unicast link In the establishment process of PC5 unicast link (PC5 unicast link), Layer-2 ID is exchanged between two terminals and used for subsequent communication.
  • the terminal described later may refer to a terminal identified by a Layer-2 ID, the terminal is allocated the Layer-2 ID, and uses the Layer-2 ID in sidelink communication.
  • a PC5-RRC connection is a logical connection between the source and destination pair. After the PC5 unicast link (PC5 unicast link) is established, the corresponding PC5 RRC connection is established. There is a one-to-one correspondence between PC5-RRC connections and PC5 unicast links.
  • the terminal on the sending side or the receiving side can determine a destination Layer- 2 IDs.
  • the terminal on the sending side or the receiving side can use the mapping relationship between the V2X/D2D service and the destination layer-2 ID, and the current V2X/D2D Business, determine the destination Layer-2 ID.
  • the terminal on the sending or receiving side can determine the destination Layer-2 ID according to the mapping relationship between the V2X/D2D service and the destination layer-2 ID, as well as the current V2X/D2D service.
  • SL DRX is introduced in NR SL.
  • SL DRX the following four types of timers (Timers) are currently introduced: Sidelink DRX Duration Timer (sl-DRX-OnDurationTimer), Sidelink DRX Inactivity Timer (sl-DRX-InactivityTimer) , Sidelink DRX Hybrid Automatic Repeat Request Loopback Delay Timer (sl-DRX-HARQ-RTT-Timer) and Sidelink DRX Retransmission Timer (sl-DRX-RetransmissionTimer).
  • HARQ is the abbreviation of hybrid automatic repeat request (Hybrid Automatic Repeat Request)
  • RTT is the abbreviation of round trip time (loopback delay).
  • sl-DRX-OnDurationTimer is used to indicate a period of time after the start position of one SL DRX cycle.
  • sl-DRX-InactivityTimer is used to indicate a period of time after a newly transmitted sidelink control information (SCI) indicating the SL.
  • sl-DRX-RetransmissionTimer is used to indicate the maximum time until an SCI indicating SL retransmission is received.
  • the sl-DRX-HARQ-RTT-Timer is used to indicate the minimum time until an SCI indicating SL retransmission is expected to be received.
  • the terminal monitors the PSCCH, or monitors the PSCCH and the pysical sidelink share channel (PSSCH), or monitors the PSCCH and PSSCH within the SL active time (SL active time).
  • PSSCH pysical sidelink share channel
  • the second-level SCI it does not monitor the time outside the SL activation time, so the power consumption of the terminal can be saved.
  • monitoring the secondary SCI on the PSCCH and the PSSCH can also be understood as monitoring the SCI
  • the SCI includes a primary SCI and a secondary SCI
  • the primary SCI is carried on the PSCCH
  • the secondary SCI is carried on the PSSCH.
  • the SL activation time includes any one of the following running times or a union of multiple running times: the running time of sl-DRX-OnDurationTimer, the running time of sl-DRX-InactivityTimer, or the running time of sl-DRX-RetransmissionTimer. That is, the SL activation time includes any of the following:
  • Figure 2 is a schematic diagram of the running time of sl-DRX-OnDurationTimer.
  • the sl-DRX-OnDurationTimer is periodically started and stopped, and the sl-DRX-OnDurationTimer keeps running for a period of time within each SL DRX cycle.
  • the SL activation time includes the running time of the sl-DRX-OnDurationTimer. Taking FIG. 2 as an example, the SL activation time includes the duration between T1 and T2, and the duration between T3 and T4.
  • FIG. 3 is a schematic diagram of the running time of sl-DRX-InactivityTimer.
  • the sl-DRX-InactivityTimer is started after receiving the SCI indicating a new transmission.
  • the terminal receives an SCI indicating a new transmission at time T5 in the running time of sl-DRX-OnDurationTimer, the terminal parses the SCI, and learns that the SCI indicates a new transmission, then the terminal starts sl-DRX- InactivityTimer, and the running duration of this sl-DRX-InactivityTimer may be indicated by the SL DRX configuration.
  • the running duration of the sl-DRX-InactivityTimer includes the duration between T6 and T7.
  • the running time of sl-DRX-InactivityTimer and the running time of sl-DRX-OnDurationTimer may overlap.
  • the SL activation time includes the running time of sl-DRX-OnDurationTimer and the running time of sl-DRX-InactivityTimer. Taking FIG. 3 as an example, the SL activation time includes the duration between T1 and T7, and the duration between T3 and T4.
  • FIG. 4 is a schematic diagram of the running time of sl-DRX-RetransmissionTimer.
  • sl-DRX-RetransmissionTimer is started at time T6.
  • the T6 time can be the timeout time of the s1-DRX-HARQ-RTT-Timer, or the first symbol after the PSSCH scheduled by the SCI ends, or the first symbol after the HARQ feedback for the data scheduled by the SCI ends, Wherein, the SCI here indicates new transmission or retransmission.
  • the runtime of the sl-DRX-RetransmissionTimer may be indicated by the SL DRX configuration. In the example of FIG.
  • the running duration of sl-DRX-RetransmissionTimer includes the duration between T6 and T7. It can be seen that the running time of sl-DRX-RetransmissionTimer and the running time of sl-DRX-OnDurationTimer may overlap.
  • the SL activation time includes the running time of sl-DRX-OnDurationTimer and the running time of sl-DRX-RetransmissionTimer. Taking FIG. 4 as an example, the SL activation time includes the duration between T1 and T7, and the duration between T3 and T4.
  • FIG. 5 is a schematic diagram of the running time of sl-DRX-HARQ-RTT-Timer.
  • the sl-DRX-HARQ-RTT-Timer is started at time T6.
  • the time T6 may be the first symbol after the PSSCH scheduled by the SCI ends, or the first symbol after the HARQ feedback for the data scheduled by the SCI ends, where the SCI here indicates new transmission or retransmission.
  • the runtime of the sl-DRX-HARQ-RTT-Timer may be indicated by the SL DRX configuration.
  • the running duration of the sl-DRX-HARQ-RTT-Timer includes the duration between T6 and T7.
  • the running time of sl-DRX-HARQ-RTT-Timer is included in the running time of sl-DRX-OnDurationTimer.
  • the SL activation time includes the running time of the sl-DRX-OnDurationTimer. Taking FIG. 5 as an example, the SL activation time includes the duration between T1 and T2, and the duration between T3 and T4.
  • the SL DRX configuration may also be referred to as the DRX configuration for short.
  • An SL DRX configuration may include at least 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 the side link DRX start offset (sl-DRX-startOffset), the value of the side link DRX cycle (SL DRX cycle), the side link DRX time slot offset (sl-DRX- slotOffset) value.
  • the value of sl-DRX-OnDurationTimer indicates the duration of sl-DRX-OnDurationTimer
  • the value of sl-DRX-InactivityTime indicates the duration of sl-DRX-InactivityTime
  • the value of sl-DRX-HARQ-RTT-Timer The duration of sl-DRX-HARQ-RTT-Timer is indicated
  • the value of sl-DRX-RetransmissionTimer indicates the duration of sl-DRX-RetransmissionTimer.
  • the value of sl-DRX-startOffset indicates the start subframe of the SL DRX cycle, that is, the subframe started by sl-DRX-OnDurationTimer.
  • the value of sl-DRX-SlotOffset indicates the time slot delay before the start of sl-DRX-OnDurationTimer.
  • the terminal can monitor or send SL control information (such as SCI) according to the SL DRX configuration.
  • SL control information such as SCI
  • SL quality of service quality of service, QoS
  • profile profile
  • the SL QoS profile can also be abbreviated as QoS profile.
  • An SL QoS profile includes one or more of the following: PC5 interface 5G QoS identifier (PC5 5G QoS identifier, PQI), guaranteed flow bit rate (GFBR), maximum flow bit rate (maximum flow bit rate, MFBR) , PC5 link aggregate maximum bit rate (PC5link aggregate maximum bit rate, PC5Link-AMBR) or distance (range).
  • PC5 interface 5G QoS identifier PC5 5G QoS identifier, PQI
  • GFBR guaranteed flow bit rate
  • maximum flow bit rate maximum flow bit rate
  • MFBR maximum flow bit rate
  • PC5 link aggregate maximum bit rate PC5link aggregate maximum bit rate
  • PC5Link-AMBR PC5 link aggregate maximum bit rate
  • PQI is used to indicate one or more of the following PC5QoS parameters: resource type (resource type), priority level (priority level), packet delay budget (packet delay budget, PDB), packet error rate (packet error rate) rate, PER), sliding window (averaging window), or maximum data burst volume (MDBV).
  • resource type can be guaranteed bit rate (guaranteed bit rate, GBR), delay critical GBR (Delay critical GBR) or non-GBR (Non-GBR).
  • the PQI can be a standard PQI or a non-standard PQI. Among them, the standard PQI is indicated by an integer.
  • the parameters indicated by the PQI, some parameters in the parameters indicated by the PQI, the parameters indicated by the SL QoS profile, or some parameters in the parameters indicated by the SL QoS profile may be collectively referred to as QoS parameter groups. Therefore, it can also be understood that a QoS parameter group corresponds to a PQI, or corresponds to an SL QoS profile. In this embodiment of the present application, when a QoS parameter group includes a parameter indicated by a PQI, the QoS parameter group may also be referred to as a PQI. When 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.
  • the SL RB configuration may also be referred to as the RB configuration for short.
  • the terminal may obtain the SL RB configuration from the signaling including the SL RB configuration sent by the base station, or preconfigure the SL RB configuration for the terminal.
  • Each SL RB configuration includes an index of the SL RB configuration, and indication information for indicating whether it is a default SL RB.
  • each SL RB configuration may also include a QoS flow or an SL QoS profile mapped to the SL RB.
  • the SL RB configuration configured for the terminal can be expressed in the form of an SL RB list (such as sl-RadioBearerToAddModList or sl-RadioBearerPreConfigList).
  • An SL RB list contains one or more SL RB configurations (such as SL-RadioBearerConfig) .
  • One SL RB configuration can correspond to one or more SL QoS profiles, one SL QoS profile corresponds to one SL RB configuration, and different SL QoS profiles can correspond to the same SL RB configuration, or can correspond to different SL RB configurations.
  • SL RB configurations respectively SL RB configuration 1 to SL RB configuration M, where M is a positive integer, where:
  • 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;
  • SL RB configuration M corresponds to SL QoS profile K-2, SL QoS profile K-1 and SL QoS profile K.
  • One SL DRX configuration can correspond to one or more sets of QoS parameters, one set of QoS parameters corresponds to one SL DRX configuration, and different QoS parameter groups can correspond to the same SL DRX configuration, or can correspond to different SL DRX configurations.
  • a set of QoS parameters includes one or more of the following: SL QoS profile, PQI, resource type, priority level, PDB, PER, averaging window, MDBV, GFBR, MFBR, PC5Link-AMBR, range.
  • the QoS parameter group is PQI or SL QoS profile as an example for description.
  • the configured SL DRX configuration is related to the SL QoS profile.
  • N SL DRX configurations respectively SL DRX configuration 1 to SL DRX configuration N, where N is a positive integer, where:
  • 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 DRX configuration N corresponds to SL QoS profile L-1 and SL QoS profile L.
  • the configured SL DRX configuration is related to the PQI.
  • N SL DRX configurations respectively SL DRX configuration 1 to SL DRX configuration N, where N is a positive integer, where:
  • SL DRX configuration 1 corresponds to PQI 1 and PQI 2;
  • SL DRX configuration 2 corresponds to PQI 3;
  • SL DRX configuration N corresponds to PQIL-1 and PQIL.
  • the QoS parameter groups corresponding to different services can be different, and the same service can correspond to multiple different QoS parameter groups , so a destination Layer-2 ID can correspond to multiple sets of QoS parameters.
  • different QoS parameter groups may correspond to different SL DRX configurations, so one destination Layer-2 ID can correspond to multiple SL DRX configurations.
  • services performed by different terminals correspond to the same destination Layer-2 ID, or, different terminals of a group correspond to the same destination Layer-2 ID, and a destination Layer-2 ID can be Corresponds to multiple SL DRX configurations, so different terminals can correspond to multiple SL DRX configurations for the same destination Layer-2 ID.
  • the SL activation time between different terminals may not be aligned, resulting in abnormal communication between terminals.
  • the terminal on the transmitting side sends sidelink data information or sidelink control information to the terminal on the receiving side outside the SL activation time maintained by the terminal on the receiving side, the terminal on the receiving side cannot receive the sidelink data information or sidelink control information.
  • the terminal when configuring the SL DRX configuration for the terminal based on the granularity of the QoS parameter group (for example, SL QoS profile or PQI), the terminal needs to be configured with the corresponding relationship between the SL DRX configuration and the QoS parameter group. Due to the large number of QoS parameter groups, the content of each group of QoS parameters is also relatively large, resulting in a large signaling overhead.
  • the QoS parameter group for example, SL QoS profile or PQI
  • Embodiments 1 to 4 provide different solutions corresponding to the following Embodiments 1 to 4, respectively.
  • FIG. 6 is a schematic diagram of a method for determining an SL DRX configuration provided by an embodiment of the present application, comprising the following steps:
  • Step 601 the terminal determines at least two QoS parameter groups corresponding to the service of the terminal.
  • each service corresponds to one or more QoS parameter groups.
  • the correspondence between the service of the terminal and the QoS parameter group may be configured by the core network element, or pre-configured, or configured by the base station.
  • the multiple services correspond to the same destination Layer-2 ID (destination Layer-2 ID).
  • the at least two QoS parameter groups corresponding to the service of the terminal can also be understood as at least two QoS parameter groups corresponding to the destination Layer-2 ID.
  • Step 602 the terminal determines at least two SL DRX configurations corresponding to at least two QoS parameter groups, wherein each SL DRX configuration indicates one or more SL DRX parameters.
  • the terminal may determine at least two SL DRX configurations corresponding to at least two QoS parameter groups according to the correspondence between the QoS parameter groups and the SL DRX configurations.
  • the corresponding relationship between the QoS parameter group and the SL DRX configuration may be configured by the base station, or pre-configured, or configured by the core network element.
  • Different terminals can determine at least two SL DRX configurations corresponding to the same destination Layer-2 ID, so 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 terminal on the sending side and the terminal on the receiving side, so at least two SL DRXs corresponding to the same service are configured on the terminal on the sending side and the receiving side. can be the same between the terminals.
  • Step 603 the terminal determines a first SLDRX configuration according to at least two SLDRX configurations, and the first SDL DRX configuration is used as the used SDL DRX configuration.
  • the terminal can also determine the running time of the timer corresponding to the first SLDRX configuration according to the first SLDRX configuration.
  • the timer here includes one or more of sl-DRX-onDurationTimer, sl-DRX-inactivityTimer, sl-DRX-HARQ-RTT-Timer or sl-DRX-RetransmissionTimer. Determining the running time of the timer includes determining the timing duration, start time, restart time, timeout time or stop time of the timer.
  • the terminal maintains a set of SL DRX timers for the destination Layer-2 ID corresponding to the service of the terminal, that is, the timer corresponding to the first SL DRX configuration.
  • the terminal determines the SL activation time corresponding to the destination Layer-2 ID according to the running time of the timer corresponding to the first SL DRX configuration.
  • the SL activation time corresponding to the destination Layer-2 ID includes any one of the following running times or the union of multiple running times: the running time of the sl-DRX-OnDurationTimer corresponding to the first SL DRX configuration, the first SL DRX Configure the running time of the corresponding sl-DRX-InactivityTimer or the running time of the sl-DRX-RetransmissionTimer corresponding to the first SL DRX configuration.
  • the terminal can determine the running time of the timer corresponding to the first SL DRX configuration according to the first SL DRX configuration and the SCI corresponding to the destination Layer-2 ID.
  • the SCI corresponding to the destination Layer-2 ID refers to: the destination Layer-1 ID included in the SCI is the lower 8 bits (Least significant bits, 8LSB) of the destination Layer-2 ID.
  • the terminal on the sending side sends the SCI corresponding to the destination Layer-2 ID to the terminal on the receiving side
  • the terminal on the receiving side receives the SCI corresponding to the destination Layer-2 ID sent by the terminal on the transmitting side, it starts the sl-DRX-inactivityTimer corresponding to the first SL DRX configuration and the sl corresponding to the first SL DRX configuration.
  • the above-mentioned terminal may be either a terminal on the transmitting side or a terminal on the receiving side. That is, the terminal on the sending side and the terminal on the receiving side select an identical SL DRX configuration (ie, the first SL DRX configuration) from at least two SL DRX configurations corresponding to the destination Layer-2 ID according to the same method, so that the The terminal and the terminal on the receiving side can align the SL activation time, which can ensure correct communication.
  • an identical SL DRX configuration ie, the first SL DRX configuration
  • the terminal and the terminal on the receiving side can align the SL activation time, which can ensure correct communication.
  • the terminal determines the mode of the first SL DRX configuration according to the at least two SL DRX configurations, including but not limited to the following method 1 and method 2.
  • the terminal selects one SL DRX configuration from the at least two SL DRX configurations as the first SL DRX configuration.
  • the first SL DRX configuration is one of the at least two SL DRX configurations.
  • the method 1 may include the following methods 1.1 to 1.6.
  • Method 1.1 according to the first parameter in the at least two SL DRX configurations, determine one SL DRX configuration in the at least two SL DRX configurations, as the first SL DRX configuration
  • the first parameter is any 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, and the value of sl-DRX-slotOffset.
  • the determined first SL DRX configuration is the SL DRX configuration with the largest value of the first parameter in the at least two SL DRX configurations.
  • the value of the first parameter as the value of sl-DRX-OnDurationTimer as an example, compare the values of sl-DRX-OnDurationTimer in at least two SL DRX configurations, and select the SL with the largest value of sl-DRX-OnDurationTimer.
  • DRX configuration as the first SL DRX configuration.
  • the determined first SL DRX configuration is the SL DRX configuration with the smallest value of the first parameter in the at least two SL DRX configurations.
  • the first parameter compares the values of the SL DRX cycle in at least two SL DRX configurations, and selects the SL DRX configuration with the smallest value of the SL DRX cycle as the first SL DRX configuration.
  • SL DRX configuration is the SL DRX configuration with the smallest value of the first parameter in the at least two SL DRX configurations.
  • the selected methods may include the following methods A to D.
  • Method A determine the first SL DRX configuration
  • the SL DRX configuration that is at the top or the bottom in the SL DRX configuration list among the multiple SL DRX configurations is selected as the first SL DRX configuration. That is, in the case where the value of the first parameter of multiple SL DRX configurations in at least two SL DRX configurations is the minimum value or the maximum value, select the multiple SL DRX configurations to be ranked the most in the SL DRX configuration list.
  • the front or rearmost SL DRX configuration as the first SL DRX configuration.
  • Method B according to the value of the PQI corresponding to the multiple SL DRX configurations, determine the first SL DRX configuration
  • the values 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 value is selected as the first SL DRX configuration. That is, when the value of the first parameter of multiple SL DRX configurations in at least two SL DRX configurations is the minimum value or the maximum value, select the minimum or maximum value of the corresponding PQI in the multiple SL DRX configurations.
  • the SL DRX configuration as the first SL DRX configuration.
  • sl-DRX-OnDurationTimer first compare the values of sl-DRX-OnDurationTimer in the above at least two SL DRX configurations, and select the SL DRX configuration with the largest value of sl-DRX-OnDurationTimer, for example, the result is SL DRX configuration 2 and SL DRX configuration If the value of sl-DRX-OnDurationTimer of 3 is the same and is the largest, the values of the PQIs corresponding to SL DRX configuration 2 and SL DRX configuration 3 are further compared.
  • SL DRX configuration 2 corresponds to PQI 3
  • SL DRX configuration 3 corresponds to PQI 6 and PQI 7, and the value of PQI 4 is the smallest, and the value of PQI 7 is the largest. If the SL DRX configuration corresponding to the PQI with the smallest value is selected as the first SL DRX configuration, then PQI 4 is selected as the first SL DRX configuration. If the SL DRX configuration corresponding to the PQI with the largest value is selected as the first SL DRX configuration, then PQI 7 is selected as the first SL DRX configuration.
  • Method C according to the index of the SL QoS profile corresponding to the multiple SL DRX configurations, determine the first SL DRX configuration
  • the indexes of the SL QoS profiles corresponding to the above multiple SL DRX configurations compare the indexes of the SL QoS profiles corresponding to the above multiple SL DRX configurations, and select the SL DRX configuration corresponding to the SL QoS profile with the smallest or largest index as the first SL DRX configuration. That is, in the case where the values of the first parameters of multiple SL DRX configurations in at least two SL DRX configurations are the minimum value or the maximum value, the index of the corresponding SL QoS profile in the multiple SL DRX configurations is selected to be the minimum or the maximum value. The largest SL DRX configuration, as the first SL DRX configuration.
  • sl-DRX-OnDurationTimer first compare the values of sl-DRX-OnDurationTimer in the above at least two SL DRX configurations, and select the SL DRX configuration with the largest value of sl-DRX-OnDurationTimer, for example, the result is SL DRX configuration 2 and SL DRX configuration If the value of sl-DRX-OnDurationTimer of 3 is the same and is the largest, then further compare the indices of the SL QoS profiles corresponding to SL DRX configuration 2 and SL DRX configuration 3 respectively.
  • 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 SL QoS profile 3, SL QoS profile 4, SL QoS profile 5.
  • the indices of 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, then 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, then the SL QoS profile 7 is selected as the first SL DRX configuration.
  • Method D according to the index of the PQI corresponding to the multiple SL DRX configurations, determine the first SL DRX configuration
  • the indexes 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, when the value of the first parameter of multiple SL DRX configurations in at least two SL DRX configurations is the minimum value or the maximum value, select the one with the smallest or largest index of the corresponding PQI in the multiple SL DRX configurations.
  • SL DRX configuration as the first SL DRX configuration.
  • sl-DRX-OnDurationTimer first compare the values of sl-DRX-OnDurationTimer in the above at least two SL DRX configurations, and select the SL DRX configuration with the largest value of sl-DRX-OnDurationTimer, for example, the result is SL DRX configuration 2 and SL DRX configuration If the value of sl-DRX-OnDurationTimer of 3 is the same and is the largest, then further compare the indices of the PQIs corresponding to SL DRX configuration 2 and SL DRX configuration 3 respectively.
  • SL DRX configuration 2 corresponds to PQI 3
  • SL DRX configuration 3 corresponds to PQI 6 and PQI 7
  • the indices of PQI 3, PQI 4, PQI 5, PQI 6, and PQI 7 are 3, 4, and 5, respectively. , 6, 7.
  • PQI 3 is selected as the first SL DRX configuration.
  • PQI 7 is selected as the first SL DRX configuration.
  • Method 1.2 determine one SL DRX configuration in the at least two SL DRX configurations, as the first SL DRX configuration
  • the value of the first parameter of multiple SL DRX configurations is the minimum value or the maximum value in at least two SL DRX configurations
  • the value of the parameter is the smallest or the largest, then it is determined that the SL DRX configuration is the first SL DRX configuration; or, when there are multiple SL DRX configurations in the second parameter of the multiple SL DRX configurations, the value of the second parameter is the smallest or largest, then it is determined that multiple One of the SL DRX configurations is the first SL DRX configuration.
  • determine an SL DRX configuration according to the determined value of the second parameter in the plurality of SL DRX configurations, determine an SL DRX configuration, wherein the value of the second parameter of the determined one SL DRX configuration is the maximum value or the minimum value. If more than one SL DRX configuration is determined by using the first parameter and the second parameter, other parameters, such as the third parameter, can be used to further filter the SL DRX configuration until one SL DRX configuration is selected.
  • the order of use of parameters in the used SL DRX configuration is not limited.
  • the first parameter, the second parameter, and the third parameter are different from each other, and the first parameter, the second parameter, and the third parameter are all one of the following parameters: the value of sl DRX cycle, the value of sl-DRX-onDurationTimer Value, value of sl-DRX-inactivityTimer, value of sl-DRX-RetransmissionTimer, value of sl-DRX-HARQ-RTT-Timer, value of sl-DRX-startOffset, value of sl-DRX-slotOffset value.
  • Method 1.3 according to the ordering of the at least two SL DRX configurations in the SL DRX configuration list, determine the first SL DRX configuration
  • the SL DRX configuration in the SL DRX configuration list is SL DRX configuration 1, SL DRX configuration 2, SL DRX configuration 3, ... in order, then finally SL DRX configuration 1 is selected as the first SL DRX configuration.
  • Method 1.4 according to the value of the PQI corresponding to the at least two SL DRX configurations, determine the first SL DRX configuration
  • the values of the PQIs corresponding to the at least two SL DRX configurations are compared, and the SL DRX configuration corresponding to the PQI with the smallest or largest value is selected as the first SL DRX configuration.
  • SL DRX configuration 1 corresponds to PQI 1 and PQI 2
  • SL DRX configuration 2 corresponds to PQI 3
  • SL DRX configuration 3 corresponds to PQI 6 and PQI 7, and the value of PQI 4 is the smallest, and the value of PQI 7 is the smallest. maximum value. If the SL DRX configuration corresponding to the PQI with the smallest value is selected as the first SL DRX configuration, then PQI 4 is selected as the first SL DRX configuration. If the SL DRX configuration corresponding to the PQI with the largest value is selected as the first SL DRX configuration, then PQI 7 is selected as the first SL DRX configuration.
  • Method 1.5 according to the index of the SL QoS profile corresponding to the at least two SL DRX configurations, determine the first SL DRX configuration
  • the indexes 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.
  • 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 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.7.
  • SL QoS profile 1 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, then the SL QoS profile 7 is selected as the first SL DRX configuration.
  • Method 1.6 according to the index of the PQI corresponding to the at least two SL DRX configurations, determine the first SL DRX configuration
  • the indexes of the PQIs corresponding to the at least two 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.
  • SL DRX configuration 1 corresponds to PQI 1 and PQI 2
  • SL DRX configuration 2 corresponds to PQI 3
  • SL DRX configuration 3 corresponds to PQI 6 and PQI 7, and PQI 1, PQI 2, PQI 3, and PQI 4
  • the indices of , PQI 5, PQI 6, and PQI 7 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, then PQI 1 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, then PQI 7 is selected as the first SL DRX configuration.
  • Method 2 generating a first SL DRX configuration according to the at least two SL DRX configurations
  • the first SL DRX configuration is generated according to at least two SL DRX configurations, and the values of the parameters in the first SL DRX configuration come from one or more SL DRX configurations in the at least two SL DRX configurations.
  • the first SL DRX configuration is generated according to the maximum value or the minimum value of each parameter in the at least two SL DRX configurations. That is, the value of the first parameter included in the first SL DRX configuration is the minimum value or the maximum value among the values of the first parameter included in the at least two SL DRX configurations respectively.
  • the value of the SL DRX cycle, the value of sl-DRX-HARQ-RTT-Timer, the value of sl-DRX-startOffset, and the value of sl-DRX-slotOffset in the generated first SL DRX configuration are the minimum values in 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 all The maximum value of the at least two DRX configurations.
  • the terminal on the sending side and the terminal on the receiving side use the same method to determine one SL DRX configuration from at least two SL DRX configurations, so that the The terminal and the terminal on the receiving side use the same SL DRX configuration, so the SL activation time between the terminal on the transmitting side and the terminal on the receiving side can be aligned.
  • the above steps 602 and 603 may also be replaced by: determining a first QoS parameter group according to the at least two QoS parameter groups, and determining that the DRX configuration corresponding to the first QoS parameter group is the first DRX configuration.
  • the first QoS parameter group (that is, the first PQI) may be the PQI with the smallest or largest value among the multiple PQIs, or the PQI with the smallest or largest index among the multiple PQIs .
  • the first QoS parameter group (that is, the first SL QoS profile) may be the SL QoS profile with the smallest or largest index among the multiple SL QoS profiles.
  • FIG. 7 is a schematic diagram of a method for determining an SL DRX configuration provided by an embodiment of the present application, comprising the following steps:
  • Steps 701 to 702 are the same as the foregoing steps 601 to 602, and reference may be made to the foregoing description.
  • Step 703 the terminal determines at least two SL DRX configurations as used SL DRX configurations, wherein the SL activation time corresponding to the service of the terminal includes the following one running time or the union of multiple running times: the at least two SL DRX configurations The running time of the corresponding sl-DRX-OnDurationTimer, the running time of the sl-DRX-InactivityTimer corresponding to the at least two SL DRX configurations respectively, or the running time of the sl-DRX-RetransmissionTimer corresponding to the at least two SL DRX configurations respectively.
  • the terminal may determine, according to the at least two SLDRX configurations, the running times of the timers corresponding to the at least two SLDRX configurations respectively.
  • the timer here includes one or more of sl-DRX-onDurationTimer, sl-DRX-inactivityTimer, sl-DRX-HARQ-RTT-Timer or sl-DRX-RetransmissionTimer. Determining the running time of the timer includes determining the timing duration, start time, restart time, timeout time or stop time of the timer.
  • the terminal maintains the multiple sets of SL DRX timers for the destination Layer-2 ID corresponding to the service of the terminal. According to the running time of each set of SL DRX timers, the SL activation time corresponding to the destination Layer-2 ID can be determined.
  • the SL activation time corresponding to the destination Layer-2 ID may also be referred to as the SL activation time corresponding to the service of the terminal.
  • FIG. 8 is a schematic diagram of the running time of sl-DRX-OnDurationTimer corresponding to different SL DRX configurations.
  • FIG. 8 exemplarily shows the running time of sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1 and the running time of sl-DRX-OnDurationTimer corresponding to SL DRX configuration 2.
  • SL DRX configuration 1 includes SL DRX cycle 1
  • SL DRX configuration 2 includes SL DRX cycle 2.
  • the running time of sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1 includes the duration between T1 and T2, and the duration between T5 and T6.
  • the running time of sl-DRX-OnDurationTimer corresponding to SL DRX configuration 2 includes the duration between T3 and T4, and the duration between T7 and T8.
  • the SL activation time corresponding to the destination Layer-2 ID includes the duration between T1 and T2, the duration between T3 and T4, the duration between T5 and T6, and the duration between T7 and T8.
  • FIG. 9 is a schematic diagram of the running time of sl-DRX-InactivityTimer and sl-DRX-OnDurationTimer corresponding to different SL DRX configurations.
  • FIG. 9 exemplarily shows the running time of sl-DRX-InactivityTimer and sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1 and the running time of sl-DRX-InactivityTimer corresponding to SL DRX configuration 2.
  • the running time of sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1 includes the duration between T1 and T4.
  • the running time of sl-DRX-InactivityTimer corresponding to SL DRX configuration 1 includes the duration between T3 and T5.
  • the running time of sl-DRX-InactivityTimer corresponding to SL DRX configuration 2 includes the duration between T3 and T4.
  • the SL activation time corresponding to the destination Layer-2 ID includes the duration between T3 and T5, the duration between T3 and T4, and the duration between T1 and T4, that is, the SL activation time corresponding to the destination Layer-2 ID includes T1 The duration between T5.
  • FIG. 10 is a schematic diagram of the running time of sl-DRX-RetransmissionTimer and sl-DRX-OnDurationTimer corresponding to different SL DRX configurations.
  • FIG. 10 exemplarily shows the running time of sl-DRX-RetransmissionTimer and sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1 and the running time of sl-DRX-RetransmissionTimer corresponding to SL DRX configuration 2.
  • the running time of sl-DRX-RetransmissionTimer corresponding to SL DRX configuration 1 includes the duration between T3 and T5.
  • the running time of sl-DRX-RetransmissionTimer corresponding to SL DRX configuration 2 includes the duration between T3 and T4.
  • the SL activation time corresponding to the destination Layer-2 ID includes the duration between T3 and T5, the duration between T3 and T4, and the duration between T1 and T4, that is, the SL activation time corresponding to the destination Layer-2 ID includes T1 The duration between T5.
  • the above-mentioned terminal may be either a terminal on the transmitting side or a terminal on the receiving side. That is, the terminal on the sending side and the terminal on the receiving side determine the running time of the timers corresponding to the at least two SL DRX configurations according to the at least two SL DRX configurations corresponding to the services of the terminal according to the same method, so that the The terminal and the terminal on the receiving side can align the SL activation time between the terminal on the sending side and the terminal on the receiving side, which can ensure correct communication.
  • the terminal may determine the running time of the sl-DRX-onDurationTimer corresponding to the SL DRX configuration according to the value of the parameter indicated by each SL DRX configuration.
  • the sl-DRX-onDurationTimer corresponding to each SL DRX configuration runs periodically.
  • the terminal can determine the running time of the timers corresponding to the at least two SL DRX configurations according to the at least two SL DRX configurations and the SCI corresponding to the destination Layer-2 ID.
  • the meaning of the SCI corresponding to the destination Layer-2 ID may refer to the foregoing description.
  • the terminal on the sending side sends the SCI corresponding to the destination Layer-2 ID to the terminal on the receiving side, the sl-DRX-inactivityTimer corresponding to each SL DRX configuration and the sl-DRX- One or more of the sl-DRX-RetransmissionTimers corresponding to the HARQ-RTT-Timer or each SL DRX configuration respectively.
  • the terminal on the receiving side After the terminal on the receiving side receives the SCI corresponding to the destination Layer-2 ID sent by the terminal on the transmitting side, it starts the sl-DRX-inactivityTimer corresponding to each SL DRX configuration and the sl corresponding to each SL DRX configuration respectively.
  • the destination Layer-2 ID is the same, but the SL QoS profile/PQI corresponding to the transmitted data is different, the starting method of the timer corresponding to each SL DRX configuration is the same.
  • the multiple data sent by the terminal on the sending side corresponding to the destination Layer-2 ID may correspond to different SL QoS profiles/PQIs.
  • the terminal on the sending side and the terminal on the receiving side maintain a set of SL DRX timers for each SL DRX configuration corresponding to the service of the terminal, respectively,
  • the terminal on the sending side and the terminal on the receiving side use the same at least two SL DRX configurations, maintain the same timer, and use the same SL DRX timer activation method, so that the terminal on the sending side and the terminal on the receiving side can be aligned.
  • SL activation time in between.
  • FIG. 11 is a schematic diagram of a method for determining an SL DRX configuration provided by an embodiment of the application, comprising the following steps:
  • Steps 1101 to 1102 are the same as the aforementioned steps 601 to 602, and reference may be made to the aforementioned description.
  • Step 1103 the terminal determines at least two SL DRX configurations as used SL DRX configurations, wherein the SL activation time corresponding to the service of the terminal includes the following one running time or the union of multiple running times: the at least two SL DRX configurations The running time of the corresponding sl-DRX-OnDurationTimer, the running time of the first sl-DRX-InactivityTimer corresponding to the second SL DRX configuration, or the running time of the first sl-DRX-RetransmissionTimer corresponding to the third SL DRX configuration.
  • the second SL DRX configuration and the third SL DRX configuration are respectively one of at least two SL DRX configurations, and the second SL DRX configuration and the third SL DRX configuration may be the same or different.
  • the terminal determines the running time of the sl-DRX-onDurationTimer corresponding to the at least two SL DRX configurations respectively, and determines the first sl-DRX-inactivityTimer corresponding to the second SL DRX configuration, The running time of one or more of the first sl-DRX-RetransmissionTimers corresponding to the third SL DRX configuration.
  • the running time of the first sl-DRX-HARQ-RTT-Timer corresponding to the fourth SL DRX configuration is also determined.
  • the fourth SL DRX configuration is one of at least two SL DRX configurations, and the fourth SL DRX configuration may be the same as the second SL DRX configuration or the third SL DRX configuration, or may be the same as the second SL DRX configuration and the third SL DRX configuration Configurations are different.
  • the first sl-DRX-inactivityTimer is one of the sl-DRX-inactivityTimers corresponding to the at least two SL DRX configurations, for example, the sl-DRX-inactivityTimer with the smallest value or the sl-DRX-inactivityTimer with the largest value .
  • the first sl-DRX-HARQ-RTT-Timer is one of the sl-DRX-HARQ-RTT-Timers corresponding to the at least two SL DRX configurations, for example, the sl-DRX-HARQ-RTT-Timer with the smallest value Or sl-DRX-HARQ-RTT-Timer with the largest value.
  • the first sl-DRX-RetransmissionTimer is one of the sl-DRX-RetransmissionTimers corresponding to the at least two SL DRX configurations, for example, the sl-DRX-RetransmissionTimer with the smallest value or the sl-DRX-RetransmissionTimer with the largest value.
  • the terminal maintains multiple sl-DRX-onDurationTimers, one sl-DRX-inactivityTimer, one sl-DRX-HARQ-RTT-Timer and one sl-DRX- RetransmissionTimer.
  • the terminal determines the destination Layer according to the running time of the sl-DRX-onDurationTimer corresponding to the at least two SL DRX configurations, and the running time of one or more of the first sl-DRX-inactivityTimer or the first sl-DRX-RetransmissionTimer -2
  • the SL activation time corresponding to the ID is also called the SL activation time corresponding to the service of the terminal.
  • FIG. 12 is a schematic diagram of the running time of the sl-DRX-OnDurationTimer corresponding to different SL DRX configurations and the running time of the first sl-DRX-InactivityTimer.
  • FIG. 12 exemplarily shows the running time of the sl-DRX-OnDurationTimer corresponding to the SL DRX configuration 1, the running time of the sl-DRX-OnDurationTimer corresponding to the SL DRX configuration 2, and the running time of the first sl-DRX-InactivityTimer.
  • the first sl-DRX-InactivityTimer corresponds to SL DRX configuration 1, SL DRX configuration 2, or other SL DRX configurations.
  • the running time of sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1 includes the duration between T1 and T3, and the duration between T6 and T7.
  • the running time of sl-DRX-OnDurationTimer corresponding to SL DRX configuration 2 includes the duration between T4 and T5, and the duration between T8 and T9.
  • the first sl-DRX-InactivityTimer includes the duration between T2 and T3. Therefore, the SL activation time corresponding to the destination Layer-2 ID includes the duration between T1 and T3, the duration between T4 and T5, the duration between T6 and T7, and the duration between T8 and T9.
  • FIG. 13 is a schematic diagram of the running time of the sl-DRX-OnDurationTimer corresponding to different SL DRX configurations and the running time of the first sl-DRX-RetransmissionTimer.
  • FIG. 13 exemplarily shows the running time of the sl-DRX-OnDurationTimer corresponding to the SL DRX configuration 1, the running time of the sl-DRX-OnDurationTimer corresponding to the SL DRX configuration 2, and the running time of the first sl-DRX-RetransmissionTimer.
  • the first sl-DRX-RetransmissionTimer corresponds to SL DRX configuration 1, SL DRX configuration 2, or other SL DRX configurations.
  • the running time of sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1 includes the duration between T1 and T3, and the duration between T6 and T7.
  • the running time of sl-DRX-OnDurationTimer corresponding to SL DRX configuration 2 includes the duration between T4 and T5, and the duration between T8 and T9.
  • the first sl-DRX-RetransmissionTimer includes the duration between T2 and T3. Therefore, the SL activation time corresponding to the destination Layer-2 ID includes the duration between T1 and T3, the duration between T4 and T5, the duration between T6 and T7, and the duration between T8 and T9.
  • the above step 1102 may specifically be: the terminal determines the first sl-DRX-inactivityTimer, the first sl-DRX according to the at least two SL DRX configurations and the SCI corresponding to the destination Layer-2 ID - the runtime of one or more of the HARQ-RTT-Timer or the first sl-DRX-RetransmissionTimer.
  • the meaning of the SCI corresponding to the destination Layer-2 ID may refer to the foregoing description.
  • the first sl-DRX-inactivityTimer For example, after the terminal on the transmitting side sends the SCI corresponding to the destination Layer-2 ID to the terminal on the receiving side, the first sl-DRX-inactivityTimer, the first sl-DRX-HARQ-RTT-Timer or the first sl-DRX-inactivityTimer is started. One or more of DRX-RetransmissionTimer.
  • the terminal on the receiving side receives the SCI corresponding to the destination Layer-2 ID sent by the terminal on the transmitting side, it starts the first sl-DRX-inactivityTimer, the first sl-DRX-HARQ-RTT-Timer or the first sl-DRX-inactivityTimer.
  • One or more of the sl-DRX-RetransmissionTimers One or more of the sl-DRX-RetransmissionTimers.
  • the above-mentioned terminal may be either a terminal on the transmitting side or a terminal on the receiving side. That is, the terminal on the sending side and the terminal on the receiving side determine the running time of the sl-DRX-onDurationTimer corresponding to the at least two SL DRX configurations according to the at least two SL DRX configurations corresponding to the service of the terminal according to the same method, and a The runtime of sl-DRX-inactivityTimer, one sl-DRX-HARQ-RTT-Timer and one sl-DRX-RetransmissionTimer. Therefore, the terminal on the sending side and the terminal on the receiving side can align the SL activation time, which can ensure correct communication.
  • the terminal on the transmitting side and the terminal on the receiving side maintain the sl-DRX-onDurationTimer corresponding to each DL DRX configuration, and maintain a set of sl-DRX- InactivityTimer, sl-DRX-HARQ-RTT-Timer or sl-DRX-RetransmissionTimer, the terminal on the transmitting side and the terminal on the receiving side use the same at least two SL DRX configurations, maintain the same timer, and use the same SL DRX timing Therefore, the SL activation time between the terminal on the transmitting side and the terminal on the receiving side can be aligned. Also, since only one set of sl-DRX-InactivityTimer, sl-DRX-HARQ-RTT-Timer or sl-DRX-RetransmissionTimer is maintained, the complexity can be reduced.
  • the fourth embodiment is the same as the second embodiment: both the terminal on the transmitting side and the terminal on the receiving side use at least two SL DRX configurations corresponding to the services of the terminal, each SL DRX configuration corresponds to a set of SL DRX timers, and Terminal services, maintain each set of SL DRX timers.
  • the service of the terminal corresponds to the same destination Layer-2 ID, so it can also be called maintaining each set of SL DRX timers for one destination Layer-2 ID.
  • an SL activation time can be determined according to the running time of each set of SL DRX timers.
  • An SL activation time includes one of the following running times or the union of multiple running times: the running time of sl-DRX-OnDurationTimer in a set of SL DRX timers, the running time of sl-DRX-InactivityTimer in the set of SL DRX timers The time or the runtime of the sl-DRX-RetransmissionTimer in this set of SL DRX timers.
  • Each SL activation time is the SL activation time corresponding to one or more SL QoS profiles/PQIs, that is, the SL activation time has a corresponding relationship with the SL QoS profile/PQI.
  • the one or more SL QoS profiles/PQIs are one or more SL QoS profiles/PQIs corresponding to the SL DRX configuration corresponding to the SL activation time.
  • the terminal on the sending side sends the destination Layer-2 ID and the SCI corresponding to the SL QoS profile/PQI respectively at the SL activation time corresponding to one or more SL QoS profiles/PQIs.
  • the terminal on the receiving side receives the SCI corresponding to the destination Layer-2 ID at the SL activation time corresponding to one or more SL QoS profiles/PQIs, or the terminal on the receiving side receives the SL activation time corresponding to one or more SL QoS profiles/PQIs Receive the destination Layer-2 ID and the SCI corresponding to the SL QoS profile/PQI respectively.
  • the destination Layer-2 ID and the SCI corresponding to the SL QoS profile/PQI refer to: the destination Layer-1 ID included in the SCI is the lower 8 bits (Least significant bits, 8LSB) of the destination Layer-2 ID, and the SCI schedules
  • the SL QoS profile/PQI of the data is the SL QoS profile/PQI.
  • the SL activation time of the terminal includes the SL activation time corresponding to one or more SL QoS profiles/PQIs.
  • At least two SL DRX configurations corresponding to destination Layer-2 IDs determined by different terminals are the same. For example, if the service corresponding to the destination Layer-2 ID is the same among different terminals, then at least two SL DRX configurations corresponding to the QoS parameter group of the service corresponding to the destination Layer-2 ID are the same. Therefore, the service corresponding to the destination Layer-2 ID may be the same between the terminal on the sending side and the terminal on the receiving side. At least two SL DRX configurations corresponding to the destination Layer-2 ID may be the same between the terminal on the sending side and the terminal on the receiving side.
  • At least two SL DRX configurations corresponding to destination Layer-2 IDs determined by different terminals are different. For example, if the service corresponding to the destination Layer-2 ID is different between different terminals, at least two SL DRX configurations corresponding to the QoS parameter group of the service corresponding to the destination Layer-2 ID are different. If the service corresponding to the destination Layer-2 ID is the service of interest to the terminal corresponding to the destination Layer-2 ID, since the services that different terminals are interested in may be different, the service corresponding to the destination Layer-2 ID can be between different terminals. different. Therefore, the service corresponding to the destination Layer-2 ID may be different between the terminal on the sending side and the terminal on the receiving side. At least two SL DRX configurations corresponding to the destination Layer-2 ID may be different between the terminal on the sending side and the terminal on the receiving side.
  • the terminal on the sending side sends an SCI corresponding to the destination Layer-2 ID, and the SCI contains data corresponding to the data scheduled by the SCI for indicating one or more SL QoS Indication information of profile/PQI.
  • the terminal on the sending side determines the DRX configuration corresponding to the SL QoS profile/PQI, and determines one or more of the sl-DRX-inactivityTimer, sl-DRX-HARQ-RTT-Timer or sl-DRX-RetransmissionTimer corresponding to the DRX configuration running time.
  • the terminal on the receiving side After receiving the SCI, the terminal on the receiving side obtains the SL QoS profile/PQI in the SCI, determines the DRX configuration corresponding to the SL QoS profile/PQI, and determines the sl-DRX-inactivityTimer, sl-DRX-HARQ corresponding to the DRX configuration - Runtime of one or more of RTT-Timer or sl-DRX-RetransmissionTimer.
  • Figure 14 is a schematic diagram of the running time of sl-DRX-OnDurationTimer and the running time of sl-DRX-InactivityTimer corresponding to different SL DRX configurations.
  • Figure 14 exemplarily shows the running time of sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1, the running time of sl-DRX-InactivityTimer corresponding to SL DRX configuration 1, and the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 2 and the runtime of the sl-DRX-InactivityTimer corresponding to SL DRX configuration 2.
  • SL DRX configuration 1 corresponds to SL QoS profile 1
  • SL DRX configuration 2 corresponds to SL QoS profile 2.
  • the terminal at the sending end sends the SCI 1 corresponding to the destination Layer-2 ID at the SL activation time corresponding to the SL QoS profile 1
  • the SCI 1 contains the indication information of the SL QoS profile 1
  • the terminal at the receiving end obtains To the instruction information for indicating SL QoS profile 1 in SCI 1, according to the instruction information, determine that the data scheduled by SCI 1 corresponds to SL QoS profile 1, then determine SL DRX configuration 1 corresponding to SL QoS profile 1, and then start sl-DRX -InactivityTimer, and according to the sl-DRX-InactivityTimer in SL DRX configuration 1, determine the running duration of the sl-DRX-InactivityTimer that is started.
  • the SL activation time corresponding to SL QoS profile1 includes the duration between T1 and T3, and T2
  • the duration between T4 that is, the SL activation time corresponding to SL QoS profile 1 includes the duration between T1 and T4.
  • the SCI 2 contains the indication information for the SL QoS profile 2
  • the The terminal obtains the indication information of SL QoS profile 2 in SCI 2, determines according to the indication information that SCI 2 scheduling is data corresponding to SL QoS profile 2, then determines SL DRX configuration 2 corresponding to SL QoS profile 2, and then starts sl-DRX- InactivityTimer, and according to the sl-DRX-InactivityTimer in SL DRX configuration 2, determine the running duration of the sl-DRX-InactivityTimer that is started.
  • the SL activation time corresponding to SL QoS profile 2 includes the duration between T5 and T7, and T6
  • the duration between T7 that is, the SL activation time corresponding to SL QoS profile 2 includes the duration between T5 and T7.
  • the SL activation time corresponding to the destination Layer-2 ID includes the duration between T1 and T3, and the duration between T5 and T7.
  • the terminal on the sending side sends the SCI corresponding to the destination Layer-2 ID, and the SCI contains one or more SL QoS profiles/PQIs corresponding to the data scheduled by the SCI
  • SDAP service data adaptation protocol
  • MAC medium access control
  • Each layer from the service data adaptation protocol (SDAP) layer of the terminal on the side to the medium access control (MAC) layer needs to indicate or mark the corresponding SL QoS profile/ PQI.
  • Data corresponding to the same SL QoS profile/PQI can be multiplexed into the same MAC protocol data unit (PDU), and data corresponding to different SL QoS profiles/PQIs can be multiplexed into different MAC PDUs.
  • PDU MAC protocol data unit
  • the terminal on the sending side sends the SCI corresponding to the destination Layer-2 ID, and the SCI does not contain the SL QoS profile/PQI corresponding to the data scheduled by the SCI.
  • the terminal on the receiving side determines the sl-DRX-inactivityTimer, sl-DRX-HARQ-RTT-Timer or sl-DRX-RetransmissionTimer corresponding to each SL DRX configuration.
  • One or more running times that is, the terminal on the receiving side determines the SL activation time corresponding to the destination Layer-2 ID for all SL DRX configurations corresponding to the SL activation time.
  • FIG. 15 is a schematic diagram of the running time of sl-DRX-OnDurationTimer and the running time of sl-DRX-InactivityTimer corresponding to different SL DRX configurations.
  • Figure 15 exemplarily shows the running time of sl-DRX-OnDurationTimer corresponding to SL DRX configuration 1, the running time of sl-DRX-InactivityTimer corresponding to SL DRX configuration 1, and the sl-DRX-OnDurationTimer corresponding to SL DRX configuration 2 and the runtime of the sl-DRX-InactivityTimer corresponding to SL DRX configuration 2.
  • the running time of the sl-DRX-OnDurationTimer corresponding to the SL DRX configuration 2 is the same as the running time of the sl-DRX-OnDurationTimer corresponding to the DRX configuration 1.
  • SL DRX configuration 1 corresponds to SL QoS profile 1
  • SL DRX configuration 2 corresponds to SL QoS profile 2.
  • the terminal at the sending end when the terminal at the sending end sends the destination Layer-2 ID and the SCI 1 corresponding to the SL QoS profile 1 at the SL activation time corresponding to the SL QoS profile 1, and the SCI 1 does not contain an indicator for indicating the SL QoS profile 1, the terminal at the receiving end starts one sl-DRX-InactivityTimer according to the duration of sl-DRX-InactivityTimer in SL DRX configuration 1, and starts another sl-DRX-InactivityTimer according to the duration of sl-DRX-InactivityTimer in SL DRX configuration 2 sl-DRX-InactivityTimer.
  • the SL activation time corresponding to SL QoS profile 1 includes the duration between T1 and T3, and the duration between T2 and T4, that is, the SL activation time corresponding to SL QoS profile 1 includes the duration between T1 and T4.
  • the SL activation time corresponding to the SL QoS profile 2 includes the duration between T1 and T3, and the duration between T2 and T3, that is, the SL activation time corresponding to the SL QoS profile 2 includes the duration between T1 and T3.
  • the SL activation time corresponding to the destination Layer-2 ID includes the duration between T1 and T3, the duration between T2 and T4, and the duration between T2 and T3, that is, the SL activation time corresponding to the destination Layer-2 ID includes The duration between T1 and T4.
  • Embodiments 5 to 9 provide different solutions corresponding to the following Embodiments 5 to 9, respectively.
  • This solution is based on the granularity of the SL QoS profile, and configures the SL DRX configuration for the terminal.
  • 16 is a schematic diagram of a method for determining an SL DRX configuration provided by an embodiment of the application, comprising the following steps:
  • Step 1601 the terminal obtains configuration information, where the configuration information includes an index of the SL QoS profile corresponding to at least one SL DRX configuration respectively.
  • the configuration information may be pre-configured, configured by a base station, configured by a core network element, or pre-defined by a protocol.
  • the above configuration information indicates the following correspondence:
  • DRX configuration 2 corresponding to the index of SL QoS profile 3, the index of SL QoS profile 4, the index of SL QoS profile 5, and the index of SL QoS profile 6;
  • the configuration information includes an index list of SL QoS profiles corresponding to at least one SL DRX configuration respectively.
  • the above configuration information indicates the following correspondence:
  • the index corresponding to the SL QoS profile starts at 3 and has a length of 2; that is, the index corresponding to the SL QoS profile for DRX configuration 1 is 3 and 4;
  • the index corresponding to the SL QoS profile starts at 7 and has a length of 1; that is, the index corresponding to the SL QoS profile for DRX configuration 2 is 7;
  • the index corresponding to the SL QoS profile starts at 10 and has a length of 3; that is, the indices corresponding to the SL QoS profile in DRX configuration 3 are 10, 11, and 12.
  • the configuration information includes the start and length of the index of the SL QoS profile corresponding to at least one SL DRX configuration respectively.
  • the start value and the length value may be indicated by two indication information, for example, indication information 1 is used to indicate the index start value, and indication information 2 is used to indicate the index length value.
  • indication information 1 is used to indicate the index start value
  • indication information 2 is used to indicate the index length value.
  • the starting value and the length value can also be indicated by an indication information, which is used to indicate a value that is jointly encoded by the starting value and the length value, and this value is referred to herein as the starting and length joint value, Also known as start and length indicator value (SLIV).
  • SLIV start and length indicator value
  • the start value is denoted as S
  • the length value is denoted as L
  • S is an integer greater than or equal to 0 and less than N
  • L is an integer greater than 0 and less than or equal to (N-S).
  • the configuration information also indicates the at least one SL DRX configuration, that is, the configuration information configures at least one SL DRX configuration on the one hand, and also configures each SL in the at least one SL DRX configuration on the other hand.
  • the index of the SL QoS profile corresponding to the DRX configuration is not limited to the DRX configuration.
  • the configuration information does not configure the at least one SL DRX configuration, but configures the at least one SL DRX configuration independently through another configuration information. That is, at least one SL DRX configuration is configured by one configuration information, and the index of the SL QoS profile corresponding to each SL DRX configuration in the at least one SL DRX configuration is configured by another configuration information.
  • Step 1602 the terminal determines the first SL DRX configuration corresponding to the index of the first SL QoS profile according to the index of the first SL QoS profile and the index of the SL QoS profile corresponding to at least one SL DRX configuration respectively.
  • the terminal can determine the SL DRX configuration corresponding to each SL QoS profile. For example, the terminal first determines the first SL QoS profile corresponding to the terminal or the service of the terminal, and determines the index of the first SL QoS profile, and then configures the corresponding SL QoS according to the index of the first SL QoS profile and at least one SL DRX respectively
  • the index of the profile can determine the first SL DRX configuration corresponding to the index of the first SL QoS profile, and the first SL DRX configuration is the SL DRX configuration corresponding to the first SL QoS profile.
  • the index of the SL QoS profile is represented by the ordering of the SL QoS profile in the SL QoS profiles corresponding to all SL RB configurations.
  • the index of the SL QoS profile is determined according to the order of the SL RB configurations in the SL RB list and the order of the SL QoS profiles in the SL QoS profile list contained in the SL RB configuration.
  • the index of the SL QoS profile can first be in the order of the SL QoS profiles in the SL QoS profile list included in an SL RB configuration, and then the SL QoS profiles can be numbered in the order of the SL RB configurations in the SL RB list.
  • the numbering can start with any integer greater than or equal to 0.
  • the number can be incremented by 1.
  • the SL RB configurations in the SL RB list are SL RB configuration 1, SL RB configuration 2, SL RB configuration 3 in sequence, and so on.
  • the SL QoS profiles corresponding to SL RB configuration 1 are numbered from 1 to N1 according to their order in the SL QoS profile list, and the SL QoS profiles corresponding to SL RB configuration 2 are numbered N1+ according to their order in the SL QoS profile list.
  • the SL QoS profiles corresponding to SL RB configuration 3 are sequentially numbered N2+1 to N3 according to their order in the SL QoS profile list, and so on.
  • the index of the SL QoS profile is 1,...,N1,N1+1,N1+2,...,N2,N2+1,...,N3,... .
  • the above configuration information indicates the following correspondence:
  • 1, 2, ..., 7 are the indexes of each SL QoS profile.
  • the index of the SL QoS profile is represented by the index of the SL RB configuration corresponding to the SL QoS profile and the ordering of the SL QoS profile in the SL QoS profile corresponding to the SL RB configuration.
  • the SL QoS profiles are numbered in sequence according to the order of the SL QoS profiles in the SL QoS profile list included in the SL RB configuration. The numbering can start with any integer greater than or equal to 0. The number can be incremented by 1.
  • the SL QoS profiles corresponding to SL RB configuration 1 are sequentially numbered from 1 to N1 according to their order in the SL QoS profile list, and the SL QoS profiles corresponding to SL RB configuration 2 are sequentially numbered according to their order in the SL QoS profile list. 1 to N2, the SL QoS profiles corresponding to SL RB configuration 3 are sequentially numbered 1 to N3 according to their order in the SL QoS profile list, and so on.
  • 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.
  • the above configuration information indicates the following correspondence:
  • ((X), (Y, Z)) represents the index of the SL QoS profile
  • X is the index of the SL RB configuration
  • Y and Z are the indexes of each SL QoS profile in the SL RB configuration.
  • (1) in ((1), (1, 2)) represents the SL RB configuration with an index of 1, that is, SL RB configuration 1.
  • (1, 2) in ((1), (1, 2)) represents the SL QoS profiles with indices 1 and 2 corresponding to SL RB configuration 1, and
  • (1) in ((1), (3, 4)) ) represents the SL RB configuration with index 1, that is, SL RB configuration 1.
  • (3, 4) in ((1), (3, 4)) represents the SL QoS profiles with indices 3 and 4 corresponding to SL RB configuration 1
  • (2) in ((2), (1, 3)) ) represents the SL RB configuration with index 2, that is, SL RB configuration 2.
  • (1, 3) in ((2), (1, 3)) represents the SL QoS profiles with indices 1 and 3 corresponding to SL RB configuration 2.
  • the above configuration information indicates the following correspondence:
  • (X, Y) represents the index of the SL QoS profile
  • X is the index of the SL RB configuration
  • Y is the index of the SL QoS profile in the SL RB configuration.
  • the index of each SL QoS profile corresponding to the SL RB configuration can be carried in each SL RB configuration, so that when the terminal receives the SL RB configuration and the SL QoS profile corresponding to the SL RB configuration, it can know the SL QoS profile.
  • One way is to carry the index of the SL QoS profile in the SL QoS profile corresponding to the SL RB configuration.
  • the indexes of each SL QoS profile corresponding to different SL RB configurations are different.
  • the SL QoS profile indicated by the index of the SL QoS profile in the configuration information can be known.
  • the index of each SL QoS profile corresponding to the SL RB configuration in the SL RB configuration can be carried in each SL RB configuration, so that the terminal receives the SL RB configuration and the SL QoS profile corresponding to the SL RB configuration.
  • the corresponding relationship between the index of the SL QoS profile in the SL RB configuration and the SL QoS profile can be known.
  • One way is to carry the index of the SL QoS profile in the SL RB configuration in the SL QoS profile corresponding to the SL RB configuration.
  • the indices of the SL QoS profiles corresponding to different SL RB configurations in the SL RB configurations may be the same.
  • the index of the SL QoS profile is represented by the index of the SL RB configuration corresponding to the SL QoS profile and the index of the SL QoS profile in the SL RB configuration. Subsequently, through the configuration information in the above step 1601, the SL QoS profile indicated by the index of the SL QoS profile in the configuration information can be known.
  • the index of the SL QoS profile corresponding to each SL DRX configuration is carried in the configuration information instead of the SL QoS profile, which can reduce signaling overhead and storage overhead.
  • This solution is based on the granularity of PQI, and configures the SL DRX configuration for the terminal.
  • 17 is a schematic diagram of a method for determining an SL DRX configuration provided by an embodiment of the application, comprising the following steps:
  • Step 1701 the terminal acquires configuration information, where the configuration information includes an index of a PQI corresponding to at least one SLDRX configuration respectively.
  • the configuration information may be pre-configured, configured by a base station, configured by a core network element, or pre-defined by a protocol.
  • the above configuration information indicates the following correspondence:
  • the configuration information also indicates the at least one SL DRX configuration, that is, the configuration information configures at least one SL DRX configuration on the one hand, and also configures each SL in the at least one SL DRX configuration on the other hand.
  • the index of the PQI corresponding to the DRX configuration is not limited to the DRX configuration.
  • the configuration information does not configure the at least one SL DRX configuration, but configures the at least one SL DRX configuration independently through another configuration information. That is, at least one SLDRX configuration is configured through one configuration information, and the index of the PQI corresponding to each SLDRX configuration in the at least one SDL DRX configuration is configured through another configuration information.
  • Step 1702 the terminal determines the first SL DRX configuration corresponding to the index of the first PQI according to the index of the first PQI and the index of the PQI corresponding to the at least one SL DRX configuration respectively.
  • the terminal can determine the SL DRX configuration corresponding to each PQI. For example, the terminal first determines the first PQI corresponding to the terminal or the service of the terminal, and determines the index of the first PQI, and then according to the index of the first PQI and the index of the PQI corresponding to at least one SL DRX configuration, the first PQI can be determined.
  • the SL DRX configuration corresponding to the index of the PQI is the first SL DRX configuration corresponding to the first PQI.
  • the PQI here may be a standard PQI or a non-standard PQI.
  • the value of the standard PQI can be used as the index of the standard PQI.
  • the index of the standard PQI is the index of the SL QoS profile containing the standard PQI, and the index of the SL QoS profile is as described in the fifth embodiment.
  • the index of the non-standard PQI is the index of the SL QoS profile including the non-standard PQI, and the index of the SL QoS profile is as described in the fifth embodiment.
  • the index of a non-standard PQI can also be represented by any of the following methods:
  • the index of the non-standard PQI is the SL QoS profile containing the non-standard PQI, which is represented by the ordering in the SL QoS profile corresponding to all SL RB configurations.
  • the SL RB configurations in the SL RB list are SL RB configuration 1, SL RB configuration 2, SL RB configuration 3, and so on.
  • the SL QoS profiles corresponding to SL RB configuration 1 are numbered from 1 to N1 according to their order in the SL QoS profile list, and the SL QoS profiles corresponding to SL RB configuration 2 are numbered N1+ according to their order in the SL QoS profile list. 1 to N2, the SL QoS profiles corresponding to SL RB configuration 3 are sequentially numbered N2+1 to N3 according to their order in the SL QoS profile list, and so on.
  • the index of the SL QoS profile is 1,...,N1,N1+1,N1+2,...,N2,N2+1,...,N3,... .
  • the index of the non-standard PQI included in the SL QoS profile with index i is i, and the value of i is 1, 2, 3, . . .
  • the above configuration information indicates the following correspondence:
  • 1, 2, ..., 7 are the indices of each non-standard PQI.
  • the index of the non-standard PQI is represented by the index of the SL RB configuration corresponding to the SL QoS profile containing the non-standard PQI and the ordering of the SL QoS profile in the SL QoS profile corresponding to the SL RB configuration.
  • the SL QoS profiles corresponding to SL RB configuration 1 are sequentially numbered from 1 to N1 according to their order in the SL QoS profile list, and the SL QoS profiles corresponding to SL RB configuration 2 are sequentially numbered according to their order in the SL QoS profile list. 1 to N2, the SL QoS profiles corresponding to SL RB configuration 3 are sequentially numbered 1 to N3 according to their order in the SL QoS profile list, and so on.
  • 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.
  • the index of the non-standard PQI included in the SL QoS profile whose index is i is i
  • the value of i is 1, 2, 3, . . .
  • the above configuration information indicates the following correspondence:
  • (X, Y) represents the index of the non-standard PQI
  • X is the index of the SL RB configuration
  • Y is the index of the non-standard PQI in the SL RB configuration.
  • the index of the non-standard PQI is the non-standard PQI index included in the SL RB configuration.
  • One way is to include the index of the non-standard PQI in the non-standard PQI. That is, an index is added to the non-standard PQI.
  • the value of the index may coincide with the value of the standard PQI, or may not coincide with the values of all the standard PQIs. If the index of the non-standard PQI coincides with the value of a certain standard PQI, the above configuration information also needs to indicate whether it is a standard PQI or a non-standard PQI, or the standard PQI and the non-standard PQI should be separately indicated.
  • a field "PqiIndex" is added to the non-standard PQI to indicate the index of the non-standard PQI.
  • the index of the non-standard PQI is represented by the index of the SL RB configuration corresponding to the SL QoS profile containing the non-standard PQI and the index of the non-standard PQI in the SL RB configuration.
  • the index of the non-standard PQI in the SL RB configuration may be carried in each SL RB configuration.
  • One way is to include the index of the non-standard PQI in the SL RB configuration in the non-standard PQI.
  • the value of the index of the non-standard PQI may coincide with the value of the standard PQI, or may not coincide with the values of all standard PQIs. If the index of the non-standard PQI coincides with the value of a certain standard PQI, the above configuration information also needs to indicate whether it is a standard PQI or a non-standard PQI, or the standard PQI and the non-standard PQI should be separately indicated.
  • the index of the PQI corresponding to each SL DRX configuration is carried in the configuration information, which can reduce signaling overhead and storage overhead.
  • Figure 18(a) is a schematic diagram of a method for determining a DRX configuration provided by an embodiment of the present application, including the following steps:
  • Step 1801a the terminal acquires configuration information, where the configuration information includes standard PQIs corresponding to at least one SL DRX configuration respectively.
  • Step 1802a the terminal determines the first standard PQI corresponding to the first non-standard PQI according to the indication information corresponding to the first non-standard PQI.
  • the indication information is used to indicate the first standard PQI corresponding to the same SL DRX configuration as the first non-standard PQI. That is, the indication information indicates the first standard PQI, and the first standard PQI and the first non-standard PQI correspond to the same SL DRX configuration.
  • Step 1803a the terminal determines the first SL DRX configuration corresponding to the first standard PQI according to the first standard PQI and the standard PQI corresponding to at least one SL DRX configuration, and the first SL DRX configuration is also the SL corresponding to the first non-standard PQI. DRX configuration.
  • the standard PQI and the non-standard PQI corresponding to the same SL DRX configuration are associated, so that the SL DRX configuration corresponding to the non-standard PQI can be determined.
  • the SL DRX configuration corresponding to the non-standard PQI is the same as the SL DRX configuration corresponding to a certain standard PQI, then an indication information may be corresponding to the non-standard PQI, and in specific implementation, the non-standard PQI may be added with this Instructions.
  • the indication information is used to indicate the standard PQI that uses the same SL DRX configuration as the non-standard PQI. Therefore, it is not necessary to configure the mapping relationship between the non-standard PQI and the SL DRX configuration through configuration information, which can reduce signaling overhead and storage overhead.
  • sl-Non-StandardizedPQI-r16 represents the information contained in the non-standard PQI
  • the SameDRXstandardizedPQI is added to the sl-Non-StandardizedPQI-r16 to indicate a standard PQI
  • the SL DRX configuration corresponding to the standard PQI is the same as the non-standard PQI.
  • the SL DRX configuration corresponding to the PQI is the same.
  • the SL DRX configuration corresponding to a non-standard PQI is the same as the SL DRX corresponding to a certain standard PQI, instead of using additional configuration information to configure the mapping relationship between the non-standard PQI and the SL DRX configuration, thereby reducing signaling overhead and storage overhead.
  • Non-standard PQI corresponds to the default (default) SL DRX configuration, or the common (common) SL DRX configuration.
  • the default SL DRX configuration or common SL DRX configuration can be sent by the base station or pre-configured.
  • the default SL DRX configuration or common SL DRX configuration may or may not be dedicated to non-standard PQI.
  • the default SL DRX configuration corresponding to non-standard PQI can be the same as the default SL DRX configuration or common SL DRX configuration for unicast, broadcast or multicast, or the common SL DRX configuration corresponding to non-standard PQI can be the same as unicast, broadcast or group
  • the default SL DRX configuration or common SL DRX configuration for broadcast is the same.
  • the non-standard PQI corresponds to the same default SL DRX configuration or common SL DRX configuration, thereby reducing signaling overhead and storage overhead.
  • Figure 18(b) is a schematic diagram of a method for determining a DRX configuration provided by an embodiment of the present application, including the following steps:
  • Step 1801b the terminal obtains configuration information, the configuration information includes an index of the SL RB configuration corresponding to at least one SL DRX configuration, wherein each SL RB configuration corresponds to one or more SL QoS profiles, or each SL RB configuration corresponds to one or multiple PQIs.
  • the configuration information may be pre-configured, configured by a base station, configured by a core network element, or pre-defined by a protocol.
  • the above configuration information indicates the following correspondence:
  • DRX configuration 2 corresponding 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;
  • the configuration information also indicates the at least one SL DRX configuration, that is, the configuration information configures at least one SL DRX configuration on the one hand, and also configures each SL in the at least one SL DRX configuration on the other hand.
  • the index of the PQI corresponding to the DRX configuration is not limited to the DRX configuration.
  • the configuration information does not configure the at least one SL DRX configuration, but configures the at least one SL DRX configuration independently through another configuration information. That is, at least one SLDRX configuration is configured through one configuration information, and the index of the PQI corresponding to each SLDRX configuration in the at least one SDL DRX configuration is configured through another configuration information.
  • the SL RB configuration may be pre-configured, base station configuration, core network element configuration or protocol predefined.
  • the SL RB configuration may be configured through the configuration information in the above step 1801, or may be configured independently through other configuration information.
  • Step 1802b the terminal determines the first SL DRX configuration corresponding to the first SL QoS profile according to the first SL QoS profile and the index of the SL RB configuration corresponding to the at least one SL DRX configuration; or the terminal determines the first SL DRX configuration corresponding to the first SL QoS profile;
  • the indexes of the SL DRX configurations corresponding to the SL DRX configurations respectively determine the first SL DRX configuration corresponding to the first PQI.
  • the terminal can determine the SL DRX configuration corresponding to each SL QoS profile. For example, for the first SL QoS profile corresponding to the terminal or the service of the terminal, the terminal first determines the first SL RB configuration corresponding to the first SL QoS profile, and then determines the index of the first SL RB configuration, and then according to the first SL RB configuration The index of the configuration, and the index of the SL RB configuration corresponding to at least one SL DRX configuration respectively, can determine the SL DRX configuration corresponding to the index of the first SL RB configuration, and the SL DRX configuration is the first SL corresponding to the first SL QoS profile. DRX configuration.
  • the terminal first determines the first SL RB configuration corresponding to the first PQI, then determines the index of the first SL RB configuration, and then determines the index of the first SL RB configuration according to the index of the first SL RB configuration.
  • the SL DRX configuration corresponding to the index of the first SL DRX configuration can be determined, and the SL DRX configuration is the first SL DRX configuration corresponding to the first PQI.
  • the terminal may also determine the first SL DRX configuration corresponding to the index of the first SL RB configuration according to the index of the SL RB configuration corresponding to the at least one SL DRX configuration, and the index of the first SL RB configuration.
  • the terminal can determine the index of the first SL RB configuration, and then according to the index of the first SL RB configuration and the index of the SL RB configuration corresponding to at least one SL DRX configuration respectively, can determine the index corresponding to the first SL RB configuration The first SL DRX configuration.
  • the index of the SL RB configuration can be represented by the ordering of the SL RB configuration in all SL RB configurations.
  • the index of the SL RB configuration may be the index of the SL RB configuration contained in the SL RB configuration.
  • SL RB configuration 1 corresponds to SL QoS profile 1, SL QoS profile 2;
  • SL RB configuration 2 corresponds to SL QoS profile 3, 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.
  • 1, 2, 3, and 4 are the indices of SL RB configuration 1, SL RB configuration 2, SL RB configuration 3, and SL RB configuration 4, respectively, then the configuration information is used to indicate: DRX configuration 1 corresponds to SL RB configuration 1 and SL RB configuration 2, so DRX configuration 1 corresponds to SL QoS profile 1, SL QoS profile 2, SL QoS profile 3 and SL QoS profile 4, DRX configuration 2 corresponds to SL RB configuration 3 and SL RB configuration 4, so DRX configuration 2 corresponds to SL QoS profile 5, SL QoS profile 6 and SL QoS profile 7.
  • the SL DRX configuration and the SL RB configuration are in a one-to-one correspondence between the SL DRX configuration in the SL DRX configuration list and the SL RB configuration in the SL RB configuration list, that is, in the SL RB list
  • the SL RB configuration is SL RB configuration 1, SL RB configuration 2, SL RB configuration 3, and so on.
  • the SL DRX configurations in the SL DRX configuration list are SL DRX configuration 1, SL DRX configuration 2, SL DRX configuration 3, and so on.
  • SL DRX configuration 1 corresponds to SL RB configuration 1
  • SL DRX configuration 2 corresponds to SL RB configuration 2
  • the terminal can determine that DRX configuration 1 corresponds to SL QoS profile 1 and SL QoS. profile 2
  • DRX configuration 2 corresponds to SL QoS profile 3 and SL QoS profile 4.
  • the SL QoS profile/PQI corresponding to the SL DRX configuration is the corresponding SL QoS profile/PQI configured for one or more SL RBs
  • an implementation method is to configure a corresponding SL QoS profile/PQI if necessary.
  • SL DRX configuration you need to meet the SL RB configuration corresponding to the SL QoS profile/PQI.
  • the SL QoS profile/PQI corresponds to a default (default) SL DRX configuration, or a common (common) SL DRX configuration.
  • the default SL DRX configuration or the common SL DRX configuration is the default SL DRX configuration or the common SL DRX configuration for unicast, broadcast or multicast.
  • the SL QoS profile/PQI corresponding to each SL DRX configuration can be represented by the index in the above embodiment, or represented 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, it is represented 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, it is represented by the SL QoS profile/PQI.
  • the index of the SL RB configuration corresponding to each SL DRX configuration is carried in the configuration information, which can reduce signaling overhead and storage overhead.
  • the terminal can determine the corresponding first SL RB configuration according to the first SL QoS profile or the first PQI, and then determine the first SL DRX configuration corresponding to the first SL RB configuration, and 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.
  • This solution is based on the granularity of the SL QoS profile, and configures the SL DRX configuration for the terminal.
  • the terminal acquires configuration information, where the configuration information indicates (or includes) SL DRX configurations corresponding to at least one SL QoS profile respectively.
  • the configuration information indicates (or includes) the corresponding relationship between at least one SL QoS profile and the SL DRX configuration.
  • the configuration information may be pre-configured, configured by a base station, configured by a core network element, or pre-defined by a protocol.
  • the above configuration information indicates the following correspondence:
  • SL QoS profile 3 corresponding SL DRX profile 3.
  • the configuration information also indicates the at least one SL QoS profile, that is, the configuration information configures the at least one SL QoS profile on the one hand, and also configures the SL corresponding to the at least one SL QoS profile on the other hand.
  • DRX configuration the configuration information configures the at least one SL QoS profile on the one hand, and also configures the SL corresponding to the at least one SL QoS profile on the other hand.
  • the configuration information includes one or more SL-QoS-Profiles, wherein each SL-QoS-Profile includes one or more of PQI, GFBR, MFBR, Range, and includes SL DRX configuration, SL-QoS-Profile
  • the indication is as follows.
  • SL DRX is configured as an enumerated type (ENUMERATED).
  • 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 sl-DRX-InactivityTimer is parentheses one of the.
  • the value in parentheses is an integer multiple of 1ms, ms0 means 0, ms1 means 1ms, ms2 means 2ms, and so on.
  • spare is an idle value, which can also be understood as an unused value.
  • 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 SL DRX cycle is one of the parentheses.
  • the unit of the value in parentheses is ms
  • ms10 means 10ms
  • ms20 means 20ms
  • spare is an idle value, which can also be understood as an unused value.
  • the SL DRX is configured to select the type (CHOICE).
  • sl-DRX-OnDurationTimer is CHOICE ⁇ subMilliSeconds,milliSeconds ⁇ .
  • subMilliSeconds is an integer type (INTEGER)
  • INTEGER integer type
  • the value range is 1 to 31
  • the unit is 1/32ms, that is, 1 means 1/32ms, 2 means 2/32ms, and so on.
  • milliSeconds is an enumeration type, the value range is ⁇ 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 ⁇ , the unit is ms, ms1 means 1ms, ms2 means 2ms, and so on. spare is an idle value, which can also be understood as an unused value.
  • carrying at least one SL QoS profile corresponding to the SL DRX configuration in the configuration information can reduce signaling overhead and storage overhead compared to carrying the SL QoS profile in each SL DRX configuration.
  • This solution is based on the granularity of the SL QoS profile, and configures the SL DRX configuration for the terminal.
  • a schematic diagram of a method for determining an SL DRX configuration provided in Embodiment 11 of the present application includes the following steps: the terminal obtains configuration information, where the configuration information includes an index of the SL DRX configuration corresponding to at least one SL QoS profile, or may also be referred to as The configuration information includes the correspondence between at least one SL QoS profile and the SL DRX configuration index.
  • the configuration information may be pre-configured, configured by a base station, configured by a core network element, or pre-defined by a protocol.
  • the above configuration information indicates the following correspondence:
  • the index of the corresponding SL DRX configuration is 3;
  • the index of the corresponding SL DRX configuration is 1;
  • the index of the corresponding SL DRX configuration is 3.
  • the configuration information also indicates the at least one SL QoS profile, that is, the configuration information configures the at least one SL QoS profile on the one hand, and also configures the SL corresponding to the at least one SL QoS profile on the other hand. Index of the DRX configuration.
  • the configuration information also indicates the at least one SL DRX configuration, that is, the configuration information configures the at least one SL DRX configuration on the one hand, and also configures the SL DRX corresponding to the at least one SL QoS profile on the other hand.
  • the configured index indicates the at least one SL DRX configuration, that is, the configuration information configures the at least one SL DRX configuration on the one hand, and also configures the SL DRX corresponding to the at least one SL QoS profile on the other hand.
  • the configuration information does not configure the at least one SL DRX configuration, but configures the at least one SL DRX configuration independently through another configuration information. That is, at least one SL DRX configuration is configured through one configuration information, and at least one SL DRX configuration index corresponding to the SL QoS profile is configured through another configuration information.
  • Step 1X02 the terminal determines the first SL DRX configuration corresponding to the first SL QoS profile according to the first SL QoS profile and the index of the SL DRX configuration corresponding to at least one SL QoS profile respectively.
  • the terminal determines the first SL DRX configuration index corresponding to the first SL QoS profile according to the first SL QoS profile and the index of the SL DRX configuration corresponding to the at least one SL QoS profile respectively, and then the terminal determines that the first SL QoS profile corresponds to
  • the first SL DRX configuration to index is the SL DRX configuration of the first SL DRX configuration index.
  • the terminal can determine the SL DRX configuration corresponding to the terminal or the service of the terminal. For example, the terminal first determines the first SL QoS profile corresponding to the terminal or the service of the terminal, and then determines the SL DRX configuration corresponding to the first SL QoS profile according to the first SL QoS profile.
  • the index of the SL DRX configuration is represented by the ordering of the SL DRX configuration in the SL DRX configuration list.
  • the SL DRX configuration in the SL DRX configuration list is SL DRX configuration 1, SL DRX configuration 2, SL DRX configuration 3, ..., SL DRX configuration N in sequence.
  • the indexes of the SL DRX configuration are 1, 2, 3, ..., N in sequence.
  • the above configuration information indicates the following correspondence:
  • 1, 2, and 3 are the indexes of each SL DRX configuration.
  • the configuration information also indicates the at least one SL QoS profile, that is, the configuration information configures the at least one SL QoS profile on the one hand, and also configures the SL corresponding to the at least one SL QoS profile on the other hand. Index of the DRX configuration.
  • the configuration information contains one or more SL-QoS-Profiles, wherein each SL-QoS-Profile contains one or more of PQI, GFBR, MFBR, Range, and contains an index of SL DRX configuration, SL-QoS -Profile is indicated as follows.
  • carrying the index of the SL DRX configuration corresponding to at least one SL QoS profile in the configuration information can reduce signaling overhead and storage overhead compared to carrying the SL QoS profile in each SL DRX configuration.
  • the solution of the eleventh embodiment may be used in combination with other embodiments.
  • the corresponding relationship between the standard PQI and the SL DRX configuration may also be configured through configuration information. If the PQI corresponding to the sidelink unicast communication is the standard PQI, both the terminal on the transmitting side and the terminal on the receiving side determine the same SL DRX configuration according to the configuration information. If the PQI corresponding to the sidelink unicast communication is a non-standard PQI, the SL DRX configuration can be determined by the terminal on one side, and the indication information used to indicate the SL DRX configuration is sent to the terminal on the opposite side.
  • the SL DRX configuration can be determined by the terminal on one side, and the indication information used to indicate the SL DRX configuration is sent to the opposite terminal.
  • the corresponding relationship between the SL QoS profile/PQI and the value range of the SL DRX parameter can also be configured through configuration information.
  • the value range of the SL DRX parameter includes, for example, the value range of sl-DRX-OnDurationTimer is 2ms to 10ms, and the value range of sl-DRX-InactivityTimer is 0ms to 8ms.
  • the terminal on one side determines the SL DRX configuration according to the QoS profile/PQI corresponding to the sidelink unicast communication, wherein the value of the SL DRX parameter included in the determined SL DRX configuration is the value of the SL DRX parameter corresponding to the QoS profile/PQI within the range.
  • the terminal sends the indication information for indicating the SL DRX configuration to the opposite terminal.
  • the QoS profile/PQI can be represented by the index of the QoS profile/PQI described in the fifth embodiment to the ninth embodiment.
  • the relationship between the above-mentioned Embodiments 1 to 4 and the above-mentioned Embodiments 5 to 9 is: through the above-mentioned Embodiments 5 to 9, the corresponding relationship between the SL DRX configuration and the QoS profile/PQI can be configured for the terminal. Correspondence can be used. For example, for a destination Layer-2 ID, there is only one service corresponding to the destination Layer-2 ID on the terminal, and the service corresponds to a QoS profile/PQI, then the terminal can determine the QoS profile/PQI and the above-mentioned corresponding relationship according to the above. The SL DRX configuration corresponding to the QoS profile/PQI is used by subsequent terminals.
  • the terminal can determine multiple services corresponding to the destination Layer-2 ID.
  • QoS profile/PQI so that the terminal determines at least two SL DRX configurations according to the multiple QoS profiles/PQIs and the above-mentioned corresponding relationship, and then the terminal can determine the at least two SL DRX configurations by any method in the above-mentioned Embodiments 1 to 4
  • the SL DRX configuration used in the configuration is described in the configuration.
  • method 1 if there are multiple PQIs associated with a destination Layer-2 ID, two methods can be considered. In method 1, first select a target PQI from multiple PQIs associated with the destination Layer-2 ID, for example, select the PQI with the smallest priority and/or the smallest PDB, and then select the SL DRX configuration corresponding to the target PQI as the used PQI.
  • the SL DRX configuration can also be referred to as applying the SL DRX configuration corresponding to the target PQI to the destination Layer-2 ID.
  • the second mode first determine multiple SL DRX configurations corresponding to the multiple PQIs according to the multiple PQIs associated with the destination Layer-2 ID, and then select a target SLDRX configuration from the multiple SL DRX configurations, such as the selected target SLDRX configuration.
  • the configuration is the SL DRX configuration with the smallest SL DRX period among the multiple SL DRX configurations.
  • the base station and the terminal include corresponding hardware structures and/or software modules for performing each function.
  • the units and method steps of each example described in conjunction with the embodiments disclosed in the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software-driven hardware depends on the specific application scenarios and design constraints of the technical solution.
  • FIG. 19 and FIG. 20 are schematic structural diagrams of possible communication apparatuses provided by embodiments of the present application. These communication apparatuses can be used to implement the functions of the terminal or the base station in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.
  • the communication device may be one of the terminals 120a to 120j shown in FIG. 1 , the base station 110a or 110b shown in FIG. 1 , or a terminal or base station modules (eg chips).
  • the communication device 1900 includes a processing unit 1910 and a transceiver unit 920 .
  • the communication apparatus 1900 is used to implement the functions of the terminal in the first embodiment to the ninth 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 sidelinks corresponding to the at least two PQIs or sidelink QoS profiles Each sidelink DRX configuration indicates one or more sidelink DRX parameters; according to the at least two sidelink DRX configurations, the used sidelink DRX configuration is determined.
  • the used sidelink DRX configuration is a first sidelink DRX configuration
  • the first sidelink DRX configuration is one of the at least two sidelink DRX configurations.
  • the value of the first parameter configured by the first sidelink DRX is the minimum value or the maximum value among the values of the first parameter configured by the at least two sidelink DRXs;
  • the first parameter is any 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- The value of RetransmissionTimer, the value of SL DRX cycle, the value of sl-DRX-startOffset, and the value of sl-DRX-slotOffset.
  • the processing unit 1910 is configured to determine that the sidelink DRX configuration is the first sidelink DRX configuration; or, When the value of the second parameter of the multiple sidelink DRX configurations in the multiple sidelink DRX configurations is the smallest or the largest, the processing unit 1910 is configured to determine one sidelink in the multiple sidelink DRX configurations
  • the channel DRX configuration is the first sidelink DRX configuration.
  • the processing unit 1910 uses In selecting the plurality of sidelink DRX configurations, the sidelink DRX configuration that is ranked first or last in the sidelink DRX configuration list is used as the first sidelink DRX configuration.
  • the processing unit 1910 uses and selecting the sidelink DRX configuration with the smallest or largest value of the corresponding PQI among the plurality of sidelink DRX configurations as the first sidelink DRX configuration.
  • the processing unit 1910 uses for selecting the sidelink DRX configuration with the smallest or largest index of the corresponding PQI among the multiple sidelink DRX configurations as the first sidelink DRX configuration; or, selecting the corresponding sidelink DRX configuration among the multiple sidelink DRX configurations
  • the sidelink DRX configuration with the smallest or largest index of the sidelink QoS profile is used as the first sidelink DRX configuration.
  • the first sidelink DRX configuration is determined according to at least one of the following parameters: the ordering of at least two sidelink DRX configurations in the sidelink DRX configuration list respectively; The values of the PQIs corresponding to the link DRX configurations respectively; the indices of the sidelink QoS profiles corresponding to the at least two sidelink DRX configurations respectively; or the indices of the PQIs corresponding to the at least two sidelink DRX configurations respectively.
  • the first sidelink DRX configuration is generated according to the at least two sidelink DRX configurations, and values of parameters in the first sidelink DRX configuration come from the at least two sidelink DRX configurations One or more of the sidelink DRX configurations in the sidelink DRX configuration.
  • the value of the first parameter included in the first sidelink DRX configuration is the minimum value among the values of the first parameters included in the at least two sidelink DRX configurations respectively, or maximum value.
  • the used sidelink DRX configuration is the at least two sidelink DRX configurations.
  • each sidelink DRX configuration in the at least two sidelink DRX configurations includes 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 activation time corresponding to the terminal includes one of the following running times or the union of multiple running times: the sl- The running time of the DRX-onDurationTimer, the running time of the sl-DRX-inactivityTimer corresponding to each sidelink DRX configuration, or the running time of the sl-DRX-RetransmissionTimer corresponding to each sidelink DRX configuration.
  • each sidelink DRX configuration in the at least two sidelink DRX configurations includes 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 activation time corresponding to the terminal includes one of the following running times or the union of multiple running times: the sl- The running time of the DRX-onDurationTimer, the running time of the first sl-DRX-inactivityTimer corresponding to the second sidelink DRX configuration, or the running time of the first sl-DRX-RetransmissionTimer corresponding to the third sidelink DRX configuration;
  • the second sidelink DRX configuration and the third sidelink DRX configuration are each one of the at least two sidelink DRX configurations.
  • the value of the first sl-DRX-inactivityTimer is the minimum value or the maximum value among the values of the sl-DRX-inactivityTimer corresponding to the at least two sidelink DRX configurations respectively; and /or, the value of the first sl-DRX-RetransmissionTimer is the minimum value or the maximum value among the values of the sl-DRX-RetransmissionTimer corresponding to the at least two sidelink DRX configurations respectively.
  • 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 respectively; according to the index of the first PQI, and the at least one sidelink The PQI indices corresponding to the DRX configurations respectively, and the first sidelink DRX configuration corresponding to the first PQI index is determined.
  • the processing unit 1910 is configured to determine the first PQI corresponding to the terminal; and determine the index of the first PQI according to the first PQI.
  • the index of the PQI is a value of the standard PQI; or, the index of the PQI is an index of a sidelink QoS template including the standard PQI.
  • the processing unit 1910 is configured to acquire at least one non-standard PQI; wherein, each non-standard PQI corresponds to an indication information, and the indication information is used to indicate The non-standard PQI corresponds to a standard PQI of the same sidelink DRX configuration; or, each non-standard PQI corresponds to a default sidelink DRX configuration; or, each non-standard PQI corresponds to a common sidelink DRX configuration.
  • the index of the PQI is an index of a sidelink QoS template containing the non-standard PQI; or, the index of the PQI is a sidelink RB configuration
  • the index of the non-standard PQI contained in; or, the index of the PQI is the index of the side-link RB configuration corresponding to the side-link QoS template containing the non-standard PQI and the non-standard PQI in the side-link RB configuration to represent the index in .
  • the processing unit 1910 is configured to acquire configuration information, where the configuration information includes an index of a sidelink QoS template corresponding to at least one sidelink DRX configuration respectively; according to the index of the first sidelink QoS template , and the indexes of the sidelink QoS profiles corresponding to the at least one sidelink DRX configuration respectively, to determine the first sidelink DRX configuration corresponding to the index of the first sidelink QoS profile.
  • the processing unit 1910 is configured to determine a first sidelink QoS template corresponding to the terminal; and determine an index of the first sidelink QoS template according to the first sidelink QoS template.
  • the index of the sidelink QoS template is represented by the order of the sidelink QoS template in the sidelink QoS template corresponding to the sidelink RB configuration list; or, the sidelink QoS template
  • the index of the road QoS template is represented by the index of the sidelink RB configuration corresponding to the sidelink QoS template and the order of the sidelink QoS template in the sidelink QoS template corresponding to the sidelink RB configuration.
  • the processing unit 1910 is configured to acquire configuration information, where the configuration information includes indexes of sidelink RB configurations corresponding to at least one sidelink DRX configuration respectively, and each sidelink RB configuration corresponds to at least one sidelink RB configuration.
  • PQI Determine a first sidelink DRX configuration corresponding to the first PQI according to the first PQI and an index of the sidelink RB configuration corresponding to the at least one sidelink DRX configuration.
  • the processing unit 1910 is configured to determine an index of the first sidelink RB configuration corresponding to the first PQI; according to the index of the first sidelink RB configuration, and the at least one sidelink The indices of the sidelink RB configurations corresponding to the respective DRX configurations of the paths are determined, and the first sidelink DRX configuration corresponding to the index of the first sidelink RB configuration is determined.
  • the index of the first sidelink RB configuration is represented by an order of the first sidelink RB configuration in the sidelink RB configuration list.
  • the processing unit 1910 is configured to acquire configuration information, where the configuration information includes indexes of sidelink RB configurations corresponding to at least one sidelink DRX configuration respectively, and each sidelink RB configuration corresponds to at least one A sidelink QoS profile; according to the first sidelink QoS profile and the index of the sidelink RB configuration corresponding to the at least one sidelink DRX profile respectively, determine the first sidelink corresponding to the first sidelink QoS profile DRX configuration.
  • the processing unit 1910 is configured to determine the index of the first sidelink RB configuration corresponding to the first sidelink QoS profile; according to the at least one sidelink DRX configuration, the corresponding sidelinks
  • the index of the channel RB configuration and the index of the first sidelink RB configuration determine the first sidelink DRX configuration corresponding to the index of the first sidelink RB configuration.
  • the index of the first sidelink RB configuration is represented by an order of the first sidelink RB configuration in the sidelink RB configuration list.
  • the communication apparatus 2000 includes a processor 2010 and an interface circuit 2020 .
  • the processor 2010 and the interface circuit 2020 are coupled to each other.
  • the interface circuit 2020 can be a transceiver or an input-output interface.
  • the communication apparatus 2000 may further include a memory 2030 for storing instructions executed by the processor 2010 or input data required by the processor 2010 to run the instructions or data generated after the processor 2010 runs the instructions.
  • the processor 2010 is used to implement the functions of the above-mentioned processing unit 1910
  • the interface circuit 2020 is used to implement the functions of the above-mentioned transceiver unit 1920 .
  • the terminal chip When the above communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the first embodiment to the eleventh embodiment. and functions of the terminal in other embodiments.
  • the terminal chip receives information from other modules (such as radio frequency modules or antennas) in the terminal, and the information is sent to the terminal by the base station; or, the terminal chip sends information to other modules in the terminal (such as radio frequency modules or antennas), the information is The information is sent by the terminal to the base station.
  • the processor in the embodiments of the present application may be a central processing unit (Central Processing Unit, CPU), and may also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application-specific integrated circuits (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • a general-purpose processor may be a microprocessor or any conventional processor.
  • the method steps in the embodiments of the present application may be implemented in a hardware manner, or may be implemented in a manner in which a processor executes software instructions.
  • Software instructions may be composed of corresponding software modules, and software modules may be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory memory, registers, hard disk, removable hard disk, CD-ROM or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor, such that the processor can read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and storage medium may reside in an ASIC.
  • the ASIC may be located in the base station or in the terminal.
  • the processor and the storage medium may also exist in the base station or terminal as discrete components.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer programs or instructions.
  • the processes or functions described in the embodiments of the present application are executed in whole or in part.
  • the computer may be a general purpose computer, special purpose computer, computer network, base station, user equipment, or other programmable apparatus.
  • the computer program or instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instructions may be downloaded from a website site, computer, A server or data center transmits by wire or wireless to another website site, computer, server or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server, data center, or the like that integrates one or more available media.
  • the usable media may be magnetic media, such as floppy disks, hard disks, magnetic tapes; optical media, such as digital video discs; and semiconductor media, such as solid-state drives.
  • the computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media, volatile and non-volatile.
  • “at least one” means one or more, and “plurality” means two or more.
  • “And/or”, which describes the association relationship of the associated objects, indicates that there can be three kinds of relationships, for example, A and/or B, which can indicate: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the related objects are a kind of "or” relationship; in the formula of this application, the character "/” indicates that the related objects are a kind of "division" Relationship.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种旁链路DRX配置的确定方法及通信装置。该方法包括：确定终端的业务确定对应的至少两个PQI或旁链路QoS模板，然后确定该至少两个PQI或旁链路QoS模板对应的至少两个旁链路DRX配置，进而根据该至少两个旁链路DRX配置，确定使用的旁链路DRX配置。如此可以实现确定合适的旁链路DRX配置进行使用，有助于提升终端之间的通信效率。并且当发送侧的终端和接收侧的终端都使用该方法确定使用的旁链路DRX配置，则发送侧的终端和接收侧的终端将使用相同的旁链路DRX配置，因而可以对齐发送侧的终端与接收侧的终端之间的旁链路激活时间。

Description

一种旁链路DRX配置的确定方法及通信装置
本申请要求在2021年3月9日提交中华人民共和国知识产权局、申请号为202110252910.9、发明名称为“一种UE2NW relay的通信方法方法、UE及网络设备”的中国专利申请和在2021年3月31日提交中华人民共和国知识产权局、申请号为202110351627.1、发明名称为“一种旁链路DRX配置的确定方法及通信装置”的中国专利申请和在2021年9月23日提交中华人民共和国知识产权局、申请号为202111116713.0、发明名称为“一种旁链路DRX配置的确定方法及通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术领域，尤其涉及一种旁链路DRX配置的确定方法及通信装置。
背景技术
从长期演进(long term evolution，LTE)开始，第三代合作伙伴计划(3rd generation partnership project，3GPP)一直在制定旁链路(sidelink，SL)标准，用于实现在各种应用场景中的终端与终端之间直接通信。
终端之间在通信时，需要确定使用的旁链路非连续接收(discontinuous reception，DRX)配置，以实现基于旁链路DRX配置确定终端的旁链路激活时间。
然而，目前还没有很好的确定旁链路DRX配置的方法。
发明内容
本申请提供一种旁链路DRX配置的确定方法及通信装置，用以实现选择合适的旁链路DRX配置进行使用，从而提升终端之间的通信效率。
第一方面，本申请实施例提供一种旁链路DRX配置的确定方法，该方法可以由终端或应用于终端中的模块来执行。该方法包括：确定终端的业务对应的至少两个PQI或旁链路QoS模板；确定该至少两个PQI或旁链路QoS模板对应的至少两个旁链路DRX配置，其中，每个旁链路DRX配置指示了一个或多个旁链路DRX参数；根据该至少两个旁链路DRX配置，确定使用的旁链路DRX配置。
基于上述方案，确定终端的业务确定对应的至少两个PQI或旁链路QoS模板，然后确定该至少两个PQI或旁链路QoS模板对应的至少两个旁链路DRX配置，进而根据该至少两个旁链路DRX配置，确定使用的旁链路DRX配置。如此可以实现确定合适的旁链路DRX配置进行使用，有助于提升终端之间的通信效率。并且当发送侧的终端和接收侧的终端都使用该方法确定使用的旁链路DRX配置，则发送侧的终端和接收侧的终端将使用相同的旁链路DRX配置，因而可以对齐发送侧的终端与接收侧的终端之间的旁链路激活时间。
在一种可能的实现方法中，该使用的旁链路DRX配置为第一旁链路DRX配置，该第一旁链路DRX配置为该至少两个旁链路DRX配置中的一个。
基于上述方案，从至少两个旁链路DRX配置中选择一个旁链路DRX配置来使用，由于仅使用一个旁链路DRX配置，因此可以减少终端能耗。
在一种可能的实现方法中，该第一旁链路DRX配置的第一参数的取值，是该至少两个旁链路DRX配置的第一参数的取值中的最小值或最大值；其中，该第一参数是以下参数中的任意一种：sl-DRX-OnDurationTimer的取值、sl-DRX-InactivityTimer的取值、sl-DRX-HARQ-RTT-Timer的取值、sl-DRX-RetransmissionTimer的取值、SL DRX cycle的取值、sl-DRX-startOffset的取值、sl-DRX-slotOffset的取值。
在一种可能的实现方法中，在该至少两个旁链路DRX配置中有多个旁链路DRX配置的第一参数的取值为最小值或最大值的情况下，当该多个旁链路DRX配置中仅有一个旁链路DRX配置的第二参数的取值最小或最大，则确定该旁链路DRX配置为该第一旁链路DRX配置；或者，当该多个旁链路DRX配置中有多个旁链路DRX配置的第二参数的取值最小或最大，则确定该多个旁链路DRX配置中的一个旁链路DRX配置为该第一旁链路DRX配置。
在一种可能的实现方法中，在该至少两个旁链路DRX配置中有多个旁链路DRX配置的第一参数的取值为最小值或最大值的情况下，选择该多个旁链路DRX配置中在旁链路DRX配置列表中排序最靠前或最靠后的旁链路DRX配置，作为该第一旁链路DRX配置。
在一种可能的实现方法中，在该至少两个旁链路DRX配置中有多个旁链路DRX配置的第一参数的取值为最小值或最大值的情况下，选择该多个旁链路DRX配置中对应的PQI的取值最小或最大的旁链路DRX配置，作为该第一旁链路DRX配置。
在一种可能的实现方法中，在该至少两个旁链路DRX配置中有多个旁链路DRX配置的第一参数的取值为最小值或最大值的情况下，选择该多个旁链路DRX配置中对应的PQI的索引最小或最大的旁链路DRX配置，作为该第一旁链路DRX配置；或者，选择该多个旁链路DRX配置中对应的旁链路QoS模板的索引最小或最大的旁链路DRX配置，作为该第一旁链路DRX配置。
在一种可能的实现方法中，根据以下至少一种参数，确定该第一旁链路DRX配置：至少两个旁链路DRX配置分别在旁链路DRX配置列表中的排序；至少两个旁链路DRX配置分别对应的PQI的取值；至少两个旁链路DRX配置分别对应的旁链路QoS模板的索引；或者，至少两个旁链路DRX配置分别对应的PQI的索引。
在一种可能的实现方法中，该第一旁链路DRX配置是根据该至少两个旁链路DRX配置生成的，该第一旁链路DRX配置中的参数的取值来自该至少两个旁链路DRX配置中的一个或多个旁链路DRX配置。
基于上述方案，根据至少两个旁链路DRX配置生成一个旁链路DRX配置来使用，由于仅使用一个旁链路DRX配置，因此可以减少终端能耗。并且由于使用的旁链路DRX配置是重新生成的，因而可以增加选择旁链路DRX配置的灵活性。
在一种可能的实现方法中，该第一旁链路DRX配置包含的第一参数的取值，是该至少两个旁链路DRX配置分别包含的第一参数的取值中的最小值或最大值。
在一种可能的实现方法中，该使用的旁链路DRX配置，为该至少两个旁链路DRX配置。
基于上述方案，将至少两个旁链路DRX配置均作为使用的旁链路DRX配置，由于使 用多个旁链路DRX配置，因此可以增加终端的旁链路激活时间，从而可以增加终端之间通信的成功率，从而可以提升通信效率。
在一种可能的实现方法中，该至少两个旁链路DRX配置中的每个旁链路DRX配置包括以下一个或多个定时器的时长：sl-DRX-onDurationTimer、sl-DRX-inactivityTimer、sl-DRX-HARQ-RTT-Timer或sl-DRX-RetransmissionTimer；该终端对应的旁链路激活时间包括以下一个运行时间或多个运行时间的并集：每个旁链路DRX配置对应的sl-DRX-onDurationTimer的运行时间、每个旁链路DRX配置对应的sl-DRX-inactivityTimer的运行时间或每个旁链路DRX配置对应的sl-DRX-RetransmissionTimer的运行时间。
在一种可能的实现方法中，该至少两个旁链路DRX配置中的每个旁链路DRX配置包括以下一个或多个定时器的时长：sl-DRX-onDurationTimer、sl-DRX-inactivityTimer、sl-DRX-HARQ-RTT-Timer或sl-DRX-RetransmissionTimer；该终端对应的旁链路激活时间包括以下一个运行时间或多个运行时间的并集：每个旁链路DRX配置对应的sl-DRX-onDurationTimer的运行时间、第二旁链路DRX配置对应的第一sl-DRX-inactivityTimer的运行时间或第三旁链路DRX配置对应的第一sl-DRX-RetransmissionTimer的运行时间；其中，该第二旁链路DRX配置和该第三旁链路DRX配置分别是该至少两个旁链路DRX配置中的一个。
在一种可能的实现方法中，该第一sl-DRX-inactivityTimer的取值是该至少两个旁链路DRX配置分别对应的sl-DRX-inactivityTimer的取值中的最小值或最大值；和/或，该第一sl-DRX-RetransmissionTimer的取值是该至少两个旁链路DRX配置分别对应的sl-DRX-RetransmissionTimer的取值中的最小值或最大值。
第二方面，本申请实施例提供一种旁链路DRX配置的确定方法，该方法可以由终端或应用于终端中的模块来执行。该方法包括：获取配置信息，该配置信息包括至少一个旁链路DRX配置分别对应的PQI的索引；根据第一PQI的索引，以及该至少一个旁链路DRX配置分别对应的PQI的索引，确定该第一PQI的索引对应的第一旁链路DRX配置。
基于上述方案，终端可以确定每个PQI对应的SL DRX配置。并且，由于在配置信息中携带各个旁链路DRX配置分别对应的PQI的索引，而不是携带PQI，可以减少信令开销及存储开销。
在一种可能的实现方法中，确定终端对应的第一PQI；根据该第一PQI，确定该第一PQI的索引。
在一种可能的实现方法中，在该PQI是标准PQI的情况下，该PQI的索引是标准PQI的取值；或者，该PQI的索引是包含该标准PQI的旁链路QoS模板的索引。
在一种可能的实现方法中，在该PQI是标准PQI的情况下，获取至少一个非标准PQI；其中，每个非标准PQI对应一个指示信息，该指示信息用于指示与该非标准PQI对应相同旁链路DRX配置的标准PQI；或者，每个非标准PQI对应一个默认旁链路DRX配置；或者，每个非标准PQI对应一个公共旁链路DRX配置。
在一种可能的实现方法中，在该PQI是非标准PQI的情况下，该PQI的索引是包含该非标准PQI的旁链路QoS模板的索引；或者，该PQI的索引是旁链路RB配置中包含的该非标准PQI的索引；或者，该PQI的索引是使用包含该非标准PQI的旁链路QoS模板对应的旁链路RB配置的索引以及该非标准PQI在该旁链路RB配置中的索引来表示。
第三方面，本申请实施例提供一种旁链路DRX配置的确定方法，该方法可以由终端或应用于终端中的模块来执行。该方法包括：获取配置信息，该配置信息包括至少一个旁链路DRX配置分别对应的旁链路QoS模板的索引；根据第一旁链路QoS模板的索引，以及该至少一个旁链路DRX配置分别对应的旁链路QoS模板的索引，确定该第一旁链路QoS模板的索引对应的第一旁链路DRX配置。
基于上述方案，终端可以确定每个旁链路QoS模板对应的SL DRX配置。并且，由于在配置信息中携带各个旁链路DRX配置分别对应的旁链路QoS模板的索引，而不是携带旁链路QoS模板，可以减少信令开销及存储开销。
在一种可能的实现方法中，确定终端对应的第一旁链路QoS模板；根据该第一旁链路QoS模板，确定该第一旁链路QoS模板的索引。
在一种可能的实现方法中，该旁链路QoS模板的索引是使用该旁链路QoS模板在旁链路RB配置列表对应的旁链路QoS模板中的排序来表示；或者，该旁链路QoS模板的索引是使用该旁链路QoS模板对应的旁链路RB配置的索引，以及该旁链路QoS模板在该旁链路RB配置对应的旁链路QoS模板中的排序来表示。
第四方面，本申请实施例提供一种旁链路DRX配置的确定方法，该方法可以由终端或应用于终端中的模块来执行。该方法包括：获取配置信息，该配置信息包括至少一个旁链路DRX配置分别对应的旁链路RB配置的索引，每个旁链路RB配置对应至少一个PQI；根据第一PQI以及该至少一个旁链路DRX配置分别对应的旁链路RB配置的索引，确定该第一PQI的索引对应的第一旁链路DRX配置。
基于上述方案，终端可以确定每个PQI对应的SL DRX配置。并且，由于在配置信息中携带各个旁链路DRX配置分别对应的旁链路RB配置的索引，而不是携带旁链路RB配置，可以减少信令开销及存储开销。
在一种可能的实现方法中，确定该第一PQI对应的第一旁链路RB配置的索引；根据该第一旁链路RB配置的索引，以及该至少一个旁链路DRX配置分别对应的旁链路RB配置的索引，确定该第一旁链路RB配置的索引对应的该第一旁链路DRX配置。
在一种可能的实现方法中，该第一旁链路RB配置的索引是使用该第一旁链路RB配置在旁链路RB配置列表中的排序来表示。
第五方面，本申请实施例提供一种旁链路DRX配置的确定方法，该方法可以由终端或应用于终端中的模块来执行。该方法包括：获取配置信息，该配置信息包括至少一个旁链路DRX配置分别对应的旁链路RB配置的索引，每个旁链路RB配置对应至少一个旁链路QoS模板；根据第一旁链路QoS模板以及该至少一个旁链路DRX配置分别对应的旁链路RB配置的索引，确定该第一旁链路QoS模板对应的第一旁链路DRX配置。
基于上述方案，终端可以确定每个旁链路QoS模板对应的SL DRX配置。并且，由于在配置信息中携带各个旁链路DRX配置分别对应的旁链路RB配置的索引，而不是携带旁链路RB配置，可以减少信令开销及存储开销。
在一种可能的实现方法中，确定该第一旁链路QoS模板对应的第一旁链路RB配置的索引；根据该至少一个旁链路DRX配置分别对应的旁链路RB配置的索引，以及该第一旁链路RB配置的索引，确定该第一旁链路RB配置的索引对应的该第一旁链路DRX配置。
在一种可能的实现方法中，该第一旁链路RB配置的索引是使用该第一旁链路RB配置 在旁链路RB配置列表中的排序来表示。
第六方面，本申请实施例提供一种通信装置，包括处理器和接口电路，该接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至该处理器或将来自该处理器的信号发送给该通信装置之外的其它通信装置，该处理器通过逻辑电路或执行代码指令用于实现上述第一方面至第五方面中的任意实现方法。
第七方面，本申请实施例提供一种通信装置，包括与存储器耦合的处理器，该处理器用于调用所述存储器中存储的程序，以执行上述第一方面至第五方面中的任意实现方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器可以是一个或多个。
第八方面，本申请实施例提供一种通信装置，包括处理器和存储器；该存储器存储有计算机指令，当该通信装置运行时，该处理器执行该存储器存储的计算机指令，以使该通信装置执行上述第一方面至第五方面中的任意实现方法。
第九方面，本申请实施例提供一种通信装置，该装置可以是终端或应用于终端中的模块。该装置具有实现上述第一方面至第五方面的任意实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十方面，本申请实施例提供一种通信装置，包括用于执行上述第一方面至第五方面中的任意实现方法的模块。
第十一方面，本申请实施例提供一种终端，用于执行上述第一方面至第五方面中的任意实现方法。
第十二方面，本申请实施例还提供一种计算机程序产品，该计算机程序产品包括计算机程序，当计算机程序被处理器运行时，实现上述第一方面至第五方面中的任意实现方法。
第十三方面，本申请实施例还提供一种计算机可读存储介质，该存储介质中存储有计算机程序或指令，当该计算机程序或指令被处理器执行时，实现上述第一方面至第五方面中的任意实现方法。
附图说明
图1为本申请实施例应用的通信系统的架构示意图；
图2为sl-DRX-OnDurationTimer的运行时间示意图；
图3为sl-DRX-InactivityTimer的运行时间示意图；
图4为sl-DRX-RetransmissionTimer的运行时间示意图；
图5为sl-DRX-HARQ-RTT-Timer的运行时间示意图；
图6为本申请实施例提供的一种SL DRX配置的确定方法示意图；
图7为本申请实施例提供的一种SL DRX配置的确定方法示意图；
图8为不同SL DRX配置对应的sl-DRX-OnDurationTimer的运行时间示意图；
图9为不同SL DRX配置对应的sl-DRX-InactivityTimer及sl-DRX-OnDurationTimer的运行时间示意图；
图10为不同SL DRX配置对应的sl-DRX-RetransmissionTimer及sl-DRX-OnDurationTimer的运行时间示意图；
图11为本申请实施例提供的一种SL DRX配置的确定方法示意图；
图12为不同SL DRX配置对应的sl-DRX-OnDurationTimer的运行时间以及第一sl-DRX-InactivityTimer的运行时间示意图；
图13为不同SL DRX配置对应的sl-DRX-OnDurationTimer的运行时间以及第一sl-DRX-RetransmissionTimer的运行时间示意图；
图14为不同SL DRX配置对应的sl-DRX-OnDurationTimer的运行时间以及sl-DRX-InactivityTimer的运行时间示意图；
图15为不同SL DRX配置对应的sl-DRX-OnDurationTimer的运行时间以及sl-DRX-InactivityTimer的运行时间示意图；
图16为本申请实施例提供的一种SL DRX配置的确定方法示意图；
图17为本申请实施例提供的一种SL DRX配置的确定方法示意图；
图18(a)为本申请实施例提供的一种DRX配置的确定方法示意图；
图18(b)为本申请实施例提供的一种DRX配置的确定方法示意图；
图19为本申请实施例提供的一种通信装置示意图；
图20为本申请实施例提供的一种通信装置示意图。
具体实施方式
图1为本申请实施例应用的通信系统的架构示意图。如图1所示，该通信系统1000包括无线接入网100和核心网200，可选的，通信系统1000还可以包括互联网300。其中，无线接入网100可以包括至少一个无线接入网设备(如图1中的110a和110b)，还可以包括至少一个终端(如图1中的120a-120j)。终端通过无线的方式与无线接入网设备相连，无线接入网设备通过无线或有线方式与核心网连接。核心网设备与无线接入网设备可以是独立的不同的物理设备，也可以是将核心网设备的功能与无线接入网设备的逻辑功能集成在同一个物理设备上，还可以是一个物理设备上集成了部分核心网设备的功能和部分的无线接入网设备的功能。终端和终端之间以及无线接入网设备和无线接入网设备之间可以通过有线或无线的方式相互连接。图1只是示意图，该通信系统中还可以包括其它网络设备，如还可以包括无线中继设备和无线回传设备，在图1中未画出。
无线接入网设备可以是基站(base station)、演进型基站(evolved NodeB，eNodeB)、发送接收点(transmission reception point，TRP)、第五代(5th generation，5G)移动通信系统中的下一代基站(next generation NodeB，gNB)、第六代(6th generation，6G)移动通信系统中的下一代基站、未来移动通信系统中的基站或无线保真(wireless fidelity，WiFi)系统中的接入节点等；也可以是完成基站部分功能的模块或单元，例如，可以是集中式单元(central unit，CU)，也可以是分布式单元(distributed unit，DU)。无线接入网设备可以是宏基站(如图1中的110a)，也可以是微基站或室内站(如图1中的110b)，还可以是中继节点或施主节点等。本申请的实施例对无线接入网设备所采用的具体技术和具体设备形态不做限定。在本申请的实施例中，以基站作为无线接入网设备的一个举例进行描述。
终端也可以称为终端设备、用户设备(user equipment，UE)、移动台、移动终端等。终端可以广泛应用于各种场景，例如，设备到设备(device-to-device，D2D)、车物(vehicle to everything，V2X)通信、机器类通信(machine-type communication，MTC)、物联网(internet  of things，IOT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、智慧城市等。终端可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、车辆、无人机、直升机、飞机、轮船、机器人、机械臂、智能家居设备等。本申请的实施例对终端所采用的具体技术和具体设备形态不做限定。
本申请实施例中，终端与终端之间可以进行旁链路(sidelink，SL)通信。不同的终端可以对应相同的服务小区，也可以对应不同的服务小区。
基站和终端可以是固定位置的，也可以是可移动的。基站和终端可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和人造卫星上。本申请的实施例对基站和终端的应用场景不做限定。
基站和终端的角色可以是相对的，例如，图1中的直升机或无人机120i可以被配置成移动基站，对于那些通过120i接入到无线接入网100的终端120j来说，终端120i是基站；但对于基站110a来说，120i是终端，即110a与120i之间是通过无线空口协议进行通信的。当然，110a与120i之间也可以是通过基站与基站之间的接口协议进行通信的，此时，相对于110a来说，120i也是基站。因此，基站和终端都可以统一称为通信装置，图1中的110a和110b可以称为具有基站功能的通信装置，图1中的120a-120j可以称为具有终端功能的通信装置。
为便于理解，下面先对本申请的实施例涉及的一些名词或术语进行解释说明。
一、sidelink通信
其中，sidelink通信也称为SL通信、旁链路通信、旁路通信、侧行通信或侧行链路通信。
sidelink通信是指邻近的两个终端之间直接通信，不需要通过任何网络节点。使用新无线(new radio，NR)技术的sidelink通信可以称为NR sidelink通信。
sidelink通信是在源(source)终端和destination(目的)终端之间进行的。源终端也称为发送侧的终端，目的终端也称为接收侧的终端。源终端可以用源层2标识(source layer-2 ID)进行标识，目标终端可以用目的层2标识(destination layer-2 ID)进行标识。发送侧的终端指的是sidelink通信(或者是一个媒体接入控制(media access control，MAC)协议数据单元(protocol data unit，PDU))的source，接收侧的终端指的是sidelink通信(或者是一个MAC PDU)的destination。
当一个终端作为发送侧的终端，则该终端的Layer-2 ID是source layer-2 ID，接收侧的终端的Layer-2 ID是destination layer-2 ID。当一个终端作为接收侧的终端，则该终端的Layer-2 ID是destination layer-2 ID，发送侧的终端的Layer-2 ID是source layer-2 ID。
需要说明的是，在实际应用中，source layer-2 ID也可以简称为source ID，destination layer-2 ID也可以简称为destination ID。
其中，source Layer-2 ID是由发送侧的终端自己分配的。
对于sidelink单播通信，destination Layer-2 ID取决于接收侧的终端。在PC5单播链路(PC5unicast link)的建立流程中，两个终端之间交换Layer-2 ID，并且用于后来的通信。后文所描述的终端，可以是指使用Layer-2 ID标识的终端，该终端分配了该Layer-2 ID，并且在sidelink通信中使用该Layer-2 ID。PC5-RRC连接(PC5-RRC connection)是在一个source 和destination对(the source and destination pair)之间的逻辑连接。在PC5单播链路(PC5 unicast link)建立后，对应的PC5 RRC连接就建立了。PC5-RRC连接和PC5单播链路之间是一一对应的。
对于sidelink组播通信，当发送侧或接收侧的终端的V2X/D2D应用层可以提供组标识信息(group identifier information)，则发送侧或接收侧的终端可以根据该组标识信息确定一个destination Layer-2 ID。当发送侧或接收侧的终端的V2X/D2D应用层没有提供组标识信息，则发送侧或接收侧的终端可以根据V2X/D2D业务与destination layer-2 ID的映射关系，以及当前的V2X/D2D业务，确定destination Layer-2 ID。
对于sidelink广播通信，发送侧或接收侧的终端可以根据V2X/D2D业务与destination layer-2 ID的映射关系，以及当前的V2X/D2D业务，确定destination Layer-2 ID。
二、SL DRX
为了节省终端功耗，在NR SL中，引入SL DRX。在SL DRX中，目前引入了以下4种类型的定时器(Timer)：旁链路DRX持续时间定时器(sl-DRX-OnDurationTimer)、旁链路DRX非激活定时器(sl-DRX-InactivityTimer)、旁链路DRX混合自动重传请求环回时延定时器(sl-DRX-HARQ-RTT-Timer)以及旁链路DRX重传定时器(sl-DRX-RetransmissionTimer)。其中，HARQ是hybrid automatic repeat request(混合自动重传请求)的缩写，RTT是round trip time(环回时延)的缩写。
其中，sl-DRX-OnDurationTimer用于指示在一个SL DRX周期的起始位置后的一段时间。sl-DRX-InactivityTimer用于指示在一个指示SL新传的旁链路控制信息(sidelink control information，SCI)后的一段时间。sl-DRX-RetransmissionTimer用于指示直到接收到一个指示SL重传的SCI的最长时间。sl-DRX-HARQ-RTT-Timer用于指示期望接收到一个指示SL重传的SCI之前的最短时间。
终端在配置或激活了SL DRX的情况下，在SL激活时间(SL active time)内监听PSCCH，或监听PSCCH和物理侧行链路共享信道(pysical sidelink share channel，PSSCH)，或监听PSCCH和PSSCH上的二级SCI，在SL激活时间之外的时间不监听，因此可以节省终端的功耗。其中，监听PSCCH和PSSCH上的二级SCI也可以理解为监听SCI，该SCI包括一级SCI和二级SCI，该一级SCI承载于PSCCH，该二级SCI承载于PSSCH。
其中，SL激活时间包括以下任一个运行时间或多个运行时间的并集：sl-DRX-OnDurationTimer的运行时间、sl-DRX-InactivityTimer的运行时间或sl-DRX-RetransmissionTimer的运行时间。也即，SL激活时间包括以下任一种：
1)sl-DRX-OnDurationTimer的运行时间；
2)sl-DRX-InactivityTimer的运行时间；
3)sl-DRX-RetransmissionTimer的运行时间；
4)sl-DRX-OnDurationTimer的运行时间和sl-DRX-InactivityTimer的运行时间的并集；
5)sl-DRX-InactivityTimer的运行时间和sl-DRX-RetransmissionTimer的运行时间的并集；
6)sl-DRX-OnDurationTimer的运行时间和sl-DRX-RetransmissionTimer的运行时间的并集；
7)sl-DRX-OnDurationTimer的运行时间、sl-DRX-InactivityTimer的运行时间和sl-DRX-RetransmissionTimer的运行时间的并集。
下面结合附图来描述上述不同的定时器的运行时间。
图2为sl-DRX-OnDurationTimer的运行时间示意图。sl-DRX-OnDurationTimer是周期性地开启和停止的，在每个SL DRX周期内的一段时长内，sl-DRX-OnDurationTimer保持运行。其中，SL激活时间包括sl-DRX-OnDurationTimer的运行时间。以图2为例，SL激活时间包括T1至T2之间的时长，以及T3至T4之间的时长。
图3为sl-DRX-InactivityTimer的运行时间示意图。sl-DRX-InactivityTimer是在收到用于指示新传的SCI之后开启的。图3中，终端在sl-DRX-OnDurationTimer的运行时间内的T5时刻收到一个指示新传的SCI，终端解析该SCI，获知该SCI是指示新传，则终端在T6时刻启动sl-DRX-InactivityTimer，且该sl-DRX-InactivityTimer的运行时长可以由SL DRX配置来指示。图3的示例中，sl-DRX-InactivityTimer的运行时长包括T6与T7之间的时长。可以看出，sl-DRX-InactivityTimer的运行时间与sl-DRX-OnDurationTimer的运行时间可以存在重叠。其中，SL激活时间包括sl-DRX-OnDurationTimer的运行时间以及sl-DRX-InactivityTimer的运行时间。以图3为例，SL激活时间包括T1至T7之间的时长，以及T3至T4之间的时长。
图4为sl-DRX-RetransmissionTimer的运行时间示意图。图4的示例中，sl-DRX-RetransmissionTimer是在T6时刻开启的。该T6时刻可以是sl-DRX-HARQ-RTT-Timer的超时时刻，或是SCI调度的PSSCH结束后的第一个符号，或是针对SCI调度的数据的HARQ反馈结束后的第一个符号，其中，这里的SCI指示新传或重传。该sl-DRX-RetransmissionTimer的运行时长可以由SL DRX配置来指示。图4的示例中，sl-DRX-RetransmissionTimer的运行时长包括T6与T7之间的时长。可以看出，sl-DRX-RetransmissionTimer的运行时间与sl-DRX-OnDurationTimer的运行时间可以存在重叠。其中，SL激活时间包括sl-DRX-OnDurationTimer的运行时间以及sl-DRX-RetransmissionTimer的运行时间。以图4为例，SL激活时间包括T1至T7之间的时长，以及T3至T4之间的时长。
图5为sl-DRX-HARQ-RTT-Timer的运行时间示意图。图5的示例中，sl-DRX-HARQ-RTT-Timer是在T6时刻开启的。该T6时刻可以是SCI调度的PSSCH结束后的第一个符号，或是针对SCI调度的数据的HARQ反馈结束后的第一个符号，其中，这里的SCI指示新传或重传。该sl-DRX-HARQ-RTT-Timer的运行时长可以由SL DRX配置来指示。图5的示例中，sl-DRX-HARQ-RTT-Timer的运行时长包括T6与T7之间的时长。可以看出，sl-DRX-HARQ-RTT-Timer的运行时间是包含于sl-DRX-OnDurationTimer的运行时间的。其中，SL激活时间包括sl-DRX-OnDurationTimer的运行时间。以图5为例，SL激活时间包括T1至T2之间的时长，以及T3至T4之间的时长。
三、SL DRX配置
在实际应用中，SL DRX配置也可以简称为DRX配置。
一个SL DRX配置可以包括以下参数中的至少一种：sl-DRX-OnDurationTimer的取值、sl-DRX-InactivityTimer的取值、sl-DRX-HARQ-RTT-Timer的取值、 sl-DRX-RetransmissionTimer的取值、旁链路DRX起始偏移(sl-DRX-startOffset)的取值、旁链路DRX周期(SL DRX cycle)的取值、旁链路DRX时隙偏移(sl-DRX-slotOffset)的取值。
其中，sl-DRX-OnDurationTimer的取值指示了sl-DRX-OnDurationTimer的时长，sl-DRX-InactivityTime的取值指示了sl-DRX-InactivityTime的时长，sl-DRX-HARQ-RTT-Timer的取值指示了sl-DRX-HARQ-RTT-Timer的时长，sl-DRX-RetransmissionTimer的取值指示了sl-DRX-RetransmissionTimer的时长。sl-DRX-startOffset的取值指示了SL DRX cycle的起始子帧，即sl-DRX-OnDurationTimer启动的子帧。sl-DRX-SlotOffset的取值指示了sl-DRX-OnDurationTimer开始前的时隙延迟。
终端可以根据SL DRX配置，监听或发送SL控制信息(如SCI)。
四、SL服务质量(quality of service，QoS)模板(profile)
在实际应用中，SL QoS profile也可以简称为QoS profile。
一个SL QoS profile包括以下一个或多个：PC5接口5G QoS标识(PC5 5G QoS identifier，PQI)、保证流量比特率(guaranteed flow bit rate，GFBR)、最大流量比特率(maximum flow bit rate，MFBR)、PC5链路聚合最大比特率(PC5link aggregate maximum bit rate，PC5Link-AMBR)或距离(range)。其中，距离的值指示PC5通信中的PC5QoS参数适用的距离，即，当接收侧的终端与发送侧的终端之间的距离超出了SL QoS profile指示的距离(range)时，PC5通信是尽力而为的。
其中，PQI用于指示以下PC5QoS参数中的一个或多个：资源类型(resource type)、优先级量级(priority level)、包时延预算(packet delay budget，PDB)、包错误率(packet error rate，PER)、滑动窗口(averaging window)或最大数据突发量(maximum data burst volume，MDBV)。其中，resource type可以是保证比特速率(guaranteed bit rate，GBR),延时关键GBR(Delay critical GBR)或非GBR(Non-GBR))。
PQI可以是标准PQI或非标准PQI。其中，标准PQI使用整数来指示。
本申请实施例中，PQI指示的参数、PQI指示的参数中的部分参数、SL QoS profile指示的参数或SL QoS profile指示的参数中的部分参数，可以统称为QoS参数组。因此，也可以理解为一个QoS参数组对应一个PQI，或对应一个SL QoS profile。本申请实施例中，当一个QoS参数组包括PQI指示的参数，则该QoS参数组也可以称为是一个PQI。当一个QoS参数组包括SL QoS profile指示的参数，则该QoS参数组也可以称为是一个SL QoS profile。
五、SL无线承载(radio bearer，RB)配置
在实际应用中，SL RB配置也可以简称为RB配置。
比如，终端可以从基站发送的包含SL RB配置的信令中获取SL RB配置，或者为终端预配置SL RB配置。
每个SL RB配置包括该SL RB配置的索引、用于指示是否为默认SL RB的指示信息，可选的，每个SL RB配置还可以包含映射到该SL RB的QoS flow或SL QoS profile。
可选的，为终端配置的SL RB配置可以是以SL RB列表(如sl-RadioBearerToAddModList 或sl-RadioBearerPreConfigList)的形式来表示，一个SL RB列表包含一个或多个SL RB配置(如SL-RadioBearerConfig)。
六、SL RB配置与SL QoS profile的关系
一个SL RB配置可以对应一个或多个SL QoS profile，一个SL QoS profile对应一个SL RB配置，不同的SL QoS profile可以对应相同的SL RB配置，也可以对应不同的SL RB配置。
示例1
例如，有M个SL RB配置，分别为SL RB配置1至SL RB配置M，M为正整数，其中：
SL RB配置1对应SL QoS profile 1，SL QoS profile 2和SL QoS profile 3；
SL RB配置2对应SL QoS profile 4和SL QoS profile 5；
……
SL RB配置M对应SL QoS profile K-2，SL QoS profile K-1和SL QoS profile K。
七、SL DRX配置与QoS参数组的关系
一个SL DRX配置可以对应一组或多组QoS参数，一组QoS参数对应一个SL DRX配置，不同的QoS参数组可以对应相同的SL DRX配置，也可以对应不同的SL DRX配置。其中，一组QoS参数包括以下中的一种或多种：SL QoS profile、PQI、resource type、priority level、PDB、PER、averaging window、MDBV、GFBR、MFBR、PC5Link-AMBR、range。本申请实施例中以QoS参数组为PQI或SL QoS profile为例进行说明。
示例2
当以SL QoS profile的粒度为终端配置SL DRX配置，则配置的SL DRX配置与SL QoS profile有关。例如，N个SL DRX配置，分别为SL DRX配置1至SL DRX配置N，N为正整数，其中：
SL DRX配置1对应SL QoS profile 1和SL QoS profile 2；
SL DRX配置2对应SL QoS profile 3；
……
SL DRX配置N对应SL QoS profile L-1和SL QoS profile L。
示例3
当以PQI的粒度为终端配置SL DRX配置，则配置的SL DRX配置与PQI有关。例如，N个SL DRX配置，分别为SL DRX配置1至SL DRX配置N，N为正整数，其中：
SL DRX配置1对应PQI 1和PQI 2；
SL DRX配置2对应PQI 3；
……
SL DRX配置N对应PQI L-1和PQI L。
八、destination Layer-2 ID、终端的业务与SL DRX配置的关系
在不同终端之间进行的不同业务可以使用同一个用于sidelink组播/广播通信的 destination Layer-2 ID，不同业务对应的QoS参数组可以不同，同一个业务可以对应多个不同的QoS参数组，因此一个destination Layer-2 ID可以对应多组QoS参数。并且，不同的QoS参数组可能对应不同的SL DRX配置，从而一个destination Layer-2 ID可以对应多个SL DRX配置。
目前，对于sidelink组播/广播通信的SL DRX配置，有以下两个问题需要解决：
第一，在sidelink组播/广播通信中，不同终端进行的业务对应相同的destination Layer-2 ID，或，一个组的不同终端对应相同的destination Layer-2 ID，而一个destination Layer-2 ID可以对应多个SL DRX配置，因此不同终端针对相同的destination Layer-2 ID均可以对应多个SL DRX配置。当进行相同业务的不同终端使用不同的SL DRX配置，将可能导致不同终端之间的SL激活时间无法对齐，进而导致终端之间通信异常。例如，如果发送侧的终端在接收侧的终端维护的SL激活时间之外向接收侧的终端发送sidelink数据信息或sidelink控制信息，则接收侧的终端接收不到该sidelink数据信息或sidelink控制信息。
第二，在为终端基于QoS参数组(例如，SL QoS profile或PQI)的粒度配置SL DRX配置时，需要向终端配置SL DRX配置与QoS参数组之间的对应关系。由于QoS参数组的数量很多，每组QoS参数的内容也比较多，从而导致信令开销较大。
为解决上述第一个问题，本申请实施例提供以下实施例一至实施例四分别对应的不同解决方案。
实施例一
图6为本申请实施例提供的一种SL DRX配置的确定方法示意图，包括以下步骤：
步骤601，终端确定终端的业务对应的至少两个QoS参数组。
其中，每个业务对应一个或多个QoS参数组。终端的业务与QoS参数组的对应关系可以是核心网网元配置的，或是预配置的，或者是基站配置的。
其中，当该终端的业务的数量为多个时，则该多个业务对应相同的目的层2标识(destination Layer-2 ID)。该终端的业务对应的至少两个QoS参数组，也可以理解为是destination Layer-2 ID对应的至少两个QoS参数组。
步骤602，终端确定至少两个QoS参数组对应的至少两个SL DRX配置，其中，每个SL DRX配置指示了一个或多个SL DRX参数。
终端可以根据QoS参数组与SL DRX配置之间的对应关系，确定至少两个QoS参数组对应的至少两个SL DRX配置。其中，QoS参数组与SL DRX配置之间的对应关系可以是基站配置的，或是预配置的，或者是核心网网元配置的。
不同终端可以确定同一个destination Layer-2 ID对应的至少两个SL DRX配置，因此不同终端确定的至少两个SL DRX配置是相同的。也可以理解为，destination Layer-2 ID对应的业务在发送侧的终端和接收侧的终端之间可以是相同的，因此相同的业务对应的至少两个SL DRX配置在发送侧的终端和接收侧的终端之间可以是相同的。
步骤603，终端根据至少两个SL DRX配置，确定第一SL DRX配置，该第一SL DRX配置作为使用的SL DRX配置。
进一步地，，终端还可以根据该第一SL DRX配置，确定该第一SL DRX配置对应的定 时器的运行时间。这里的定时器，包括sl-DRX-onDurationTimer、sl-DRX-inactivityTimer、sl-DRX-HARQ-RTT-Timer或sl-DRX-RetransmissionTimer中的一个或多个。确定定时器的运行时间包括确定定时器的定时时长、启动时间、重启时间、超时时间或停止时间。
终端针对终端的业务对应的destination Layer-2 ID，维护一套SL DRX定时器，即，该第一SL DRX配置对应的定时器。终端根据该第一SL DRX配置对应的定时器的运行时间确定该destination Layer-2 ID对应的SL激活时间。例如，该destination Layer-2 ID对应的SL激活时间包括以下任一个运行时间或多个运行时间的并集：该第一SL DRX配置对应的sl-DRX-OnDurationTimer的运行时间、该第一SL DRX配置对应的sl-DRX-InactivityTimer的运行时间或该第一SL DRX配置对应的sl-DRX-RetransmissionTimer的运行时间。
作为一种实现方法，终端可以根据该第一SL DRX配置，以及与该destination Layer-2 ID对应的SCI，确定该第一SL DRX配置对应的定时器的运行时间。其中，该destination Layer-2 ID对应的SCI是指：SCI中包含的destination Layer-1ID是该destination Layer-2 ID的低8位(Least significant bits，8LSB)。比如，当发送侧的终端向接收侧的终端发送与该destination Layer-2 ID对应的SCI之后，启动第一SL DRX配置对应的sl-DRX-inactivityTimer、第一SL DRX配置对应的sl-DRX-HARQ-RTT-Timer或第一SL DRX配置对应的sl-DRX-RetransmissionTimer中的一个或多个。再比如，当接收侧的终端接收到发送侧的终端发送的与该destination Layer-2 ID对应的SCI之后，启动第一SL DRX配置对应的sl-DRX-inactivityTimer、第一SL DRX配置对应的sl-DRX-HARQ-RTT-Timer或第一SL DRX配置对应的sl-DRX-RetransmissionTimer中的一个或多个。
上述终端既可以是发送侧的终端，也可以是接收侧的终端。也即发送侧的终端和接收侧的终端按照相同的方法，从destination Layer-2 ID对应的至少两个SL DRX配置选择一个相同的SL DRX配置(即第一SL DRX配置)，从而发送侧的终端和接收侧的终端可以对齐SL激活时间，可以保障正确通信。
其中，上述步骤603中，终端根据该至少两个SL DRX配置确定第一SL DRX配置的方式，包括但不限于以下方法1和方法2。
方法1，终端从该至少两个SL DRX配置中选择一个SL DRX配置，作为第一SL DRX配置。
也即，第一SL DRX配置是该至少两个SL DRX配置中的一个。
具体的，该方法1可以包括以下方法1.1到方法1.6。
方法1.1，根据至少两个SL DRX配置中的第一参数，确定至少两个SL DRX配置中的一个SL DRX配置，作为第一SL DRX配置
其中，第一参数是以下参数中的任意一种：sl-DRX-OnDurationTimer的取值、sl-DRX-InactivityTimer的取值、sl-DRX-HARQ-RTT-Timer的取值、sl-DRX-RetransmissionTimer的取值、sl-DRX-startOffset的取值、SL DRX cycle的取值、sl-DRX-slotOffset的取值。
比如，确定的第一SL DRX配置为至少两个SL DRX配置中的第一参数的取值最大的SL DRX配置。示例性地，以第一参数是sl-DRX-OnDurationTimer的取值为例，比较至少两个SL DRX配置中的sl-DRX-OnDurationTimer的取值，选择sl-DRX-OnDurationTimer的取值最大的SL DRX配置，作为第一SL DRX配置。
再比如，确定的第一SL DRX配置为至少两个SL DRX配置中的第一参数的取值最小的SL DRX配置。示例性地，以第一参数是SL DRX cycle的取值为例，比较至少两个SL DRX配置中的SL DRX cycle的取值，选择SL DRX cycle的取值最小的SL DRX配置，作为第一SL DRX配置。
需要说明的是，如果有两个或两个以上的SL DRX配置的第一参数的取值相同，且取值是最小或最大的，则可以进一步从选择出来的多个SL DRX配置中再选择一个SL DRX配置，作为第一SL DRX配置。其中，选择的方法可以包括以下方法A至方法D。
方法A，根据该多个SL DRX配置在SL DRX配置列表中的排序，确定第一SL DRX配置
比如，选择该多个SL DRX配置中的在SL DRX配置列表中排在最靠前或最靠后的SL DRX配置，作为第一SL DRX配置。也即，在至少两个SL DRX配置中有多个SL DRX配置的第一参数的取值为最小值或最大值的情况下，选择多个SL DRX配置中在SL DRX配置列表中排序最靠前或最靠后的SL DRX配置，作为第一SL DRX配置。
示例性地，先比较上述至少两个SL DRX配置中的sl-DRX-OnDurationTimer的取值，选择sl-DRX-OnDurationTimer的取值最大的SL DRX配置，比如结果是SL DRX配置2和SL DRX配置3的sl-DRX-OnDurationTimer的取值相同，且最大，则进一步比较SL DRX配置2与SL DRX配置3在SL DRX配置列表中的排列顺序。比如SL DRX配置2排在前面，则最终选择SL DRX配置2作为第一SL DRX配置。
方法B，根据该多个SL DRX配置对应的PQI的取值，确定第一SL DRX配置
比如，比较该多个SL DRX配置对应的PQI的取值，选择取值最小或最大的PQI对应的SL DRX配置，作为第一SL DRX配置。也即，在至少两个SL DRX配置中有多个SL DRX配置的第一参数的取值为最小值或最大值的情况下，选择多个SL DRX配置中对应的PQI的取值最小或最大的SL DRX配置，作为第一SL DRX配置。
示例性地，先比较上述至少两个SL DRX配置中的sl-DRX-OnDurationTimer的取值，选择sl-DRX-OnDurationTimer的取值最大的SL DRX配置，比如结果是SL DRX配置2和SL DRX配置3的sl-DRX-OnDurationTimer的取值相同，且最大，则进一步比较SL DRX配置2与SL DRX配置3分别对应的PQI的取值。比如SL DRX配置2对应PQI 3、PQI 4和PQI 5，SL DRX配置3对应PQI 6和PQI 7，且PQI 4的取值最小，PQI 7的取值最大。假如选择取值最小的PQI对应的SL DRX配置作为第一SL DRX配置，则选择PQI 4作为第一SL DRX配置。假如选择取值最大的PQI对应的SL DRX配置作为第一SL DRX配置，则选择PQI 7作为第一SL DRX配置。
方法C，根据该多个SL DRX配置对应的SL QoS profile的索引，确定第一SL DRX配置
比如，比较上述多个SL DRX配置对应的SL QoS profile的索引，选择索引最小或最大的SL QoS profile对应的SL DRX配置，作为第一SL DRX配置。也即，在至少两个SL DRX配置中有多个SL DRX配置的第一参数的取值为最小值或最大值的情况下，选择多个SL DRX配置中对应的SL QoS profile的索引最小或最大的SL DRX配置，作为第一SL DRX配置。
示例性地，先比较上述至少两个SL DRX配置中的sl-DRX-OnDurationTimer的取值， 选择sl-DRX-OnDurationTimer的取值最大的SL DRX配置，比如结果是SL DRX配置2和SL DRX配置3的sl-DRX-OnDurationTimer的取值相同，且最大，则进一步比较SL DRX配置2与SL DRX配置3分别对应的SL QoS profile的索引。比如SL DRX配置2对应SL QoS profile 3、SL QoS profile 4和SL QoS profile 5，SL DRX配置3对应SL QoS profile 6和SL QoS profile 7，且SL QoS profile 3、SL QoS profile 4、SL QoS profile 5、SL QoS profile 6、SL QoS profile 7的索引分别为3、4、5、6、7。假如选择索引最小的SL QoS profile对应的SL DRX配置作为第一SL DRX配置，则选择SL QoS profile 3作为第一SL DRX配置。假如选择索引最大的SL QoS profile对应的SL DRX配置作为第一SL DRX配置，则选择SL QoS profile 7作为第一SL DRX配置。
方法D，根据该多个SL DRX配置对应的PQI的索引，确定第一SL DRX配置
比如，比较该多个SL DRX配置对应的PQI的索引，选择索引最小或最大的PQI对应的SL DRX配置，作为第一SL DRX配置。也即，在至少两个SL DRX配置中有多个SL DRX配置的第一参数的取值为最小值或最大值的情况下，选择多个SL DRX配置中对应的PQI的索引最小或最大的SL DRX配置，作为第一SL DRX配置。
示例性地，先比较上述至少两个SL DRX配置中的sl-DRX-OnDurationTimer的取值，选择sl-DRX-OnDurationTimer的取值最大的SL DRX配置，比如结果是SL DRX配置2和SL DRX配置3的sl-DRX-OnDurationTimer的取值相同，且最大，则进一步比较SL DRX配置2与SL DRX配置3分别对应的PQI的索引。比如SL DRX配置2对应PQI 3、PQI 4和PQI 5，SL DRX配置3对应PQI 6和PQI 7，且PQI 3、PQI 4、PQI 5、PQI 6、PQI 7的索引分别为3、4、5、6、7。假如选择索引最小的PQI对应的SL DRX配置作为第一SL DRX配置，则选择PQI 3作为第一SL DRX配置。假如选择索引最大的PQI对应的SL DRX配置作为第一SL DRX配置，则选择PQI 7作为第一SL DRX配置。
方法1.2，根据至少两个SL DRX配置中的多个参数，确定至少两个SL DRX配置中的一个SL DRX配置，作为第一SL DRX配置
也即，在至少两个SL DRX配置中有多个SL DRX配置的第一参数的取值为最小值或最大值的情况下，当多个SL DRX配置中仅有一个SL DRX配置的第二参数的取值最小或最大，则确定SL DRX配置为第一SL DRX配置；或者，当多个SL DRX配置中有多个SL DRX配置的第二参数的取值最小或最大，则确定多个SL DRX配置中的一个SL DRX配置为第一SL DRX配置。
具体地，先根据至少两个SL DRX配置中的第一参数的取值，确定多个SL DRX配置，其中，确定的多个SL DRX配置的第一参数的取值相同，例如，该第一参数的取值是多个SL DRX配置中该参数的最大值或最小值。接着，再根据确定的多个SL DRX配置中的第二参数的取值，确定一个SL DRX配置，其中，确定的一个SL DRX配置的该第二参数的取值是最大值或最小值。如果用第一参数和第二参数，确定出一个以上的SL DRX配置，则可以继续使用其它参数，如第三参数，进一步筛选SL DRX配置，直至选出一个SL DRX配置。
其中，对使用的SL DRX配置中的参数的使用顺序不做限定。其中，第一参数、第二参数、第三参数互不相同，且第一参数、第二参数、第三参数均为以下参数中的一个：sl DRX cycle的取值、sl-DRX-onDurationTimer的取值、sl-DRX-inactivityTimer的取值、 sl-DRX-RetransmissionTimer的取值、sl-DRX-HARQ-RTT-Timer的取值、sl-DRX-startOffset的取值、sl-DRX-slotOffset的取值。
方法1.3，根据该至少两个SL DRX配置在SL DRX配置列表中的排序，确定第一SL DRX配置
比如，选择在SL DRX配置列表中排在最靠前或最靠后的SL DRX配置，作为第一SL DRX配置。
比如，SL DRX配置列表中的SL DRX配置按照排列顺序依次为SL DRX配置1，SL DRX配置2，SL DRX配置3，……，则最终选择SL DRX配置1作为第一SL DRX配置。
方法1.4，根据该至少两个SL DRX配置对应的PQI的取值，确定第一SL DRX配置
比如，比较该至少两个SL DRX配置对应的PQI的取值，选择取值最小或最大的PQI对应的SL DRX配置，作为第一SL DRX配置。
比如，SL DRX配置1对应PQI 1和PQI 2，SL DRX配置2对应PQI 3、PQI 4和PQI 5，SL DRX配置3对应PQI 6和PQI 7，且PQI 4的取值最小，PQI 7的取值最大。假如选择取值最小的PQI对应的SL DRX配置作为第一SL DRX配置，则选择PQI 4作为第一SL DRX配置。假如选择取值最大的PQI对应的SL DRX配置作为第一SL DRX配置，则选择PQI 7作为第一SL DRX配置。
方法1.5，根据该至少两个SL DRX配置对应的SL QoS profile的索引，确定第一SL DRX配置
比如，比较至少两个SL DRX配置对应的SL QoS profile的索引，选择索引最小或最大的SL QoS profile对应的SL DRX配置，作为第一SL DRX配置。
比如，SL DRX配置1对应SL QoS profile 1和SL QoS profile 2，SL DRX配置2对应SL QoS profile 3、SL QoS profile 4和SL QoS profile 5，SL DRX配置3对应SL QoS profile 6和SL QoS profile 7，且SL QoS profile 1、SL QoS profile 2、SL QoS profile 3、SL QoS profile4、SL QoS profile 5、SL QoS profile 6、SL QoS profile 7的索引分别为1、2、3、4、5、6、7。假如选择索引最小的SL QoS profile对应的SL DRX配置作为第一SL DRX配置，则选择SL QoS profile 1作为第一SL DRX配置。假如选择索引最大的SL QoS profile对应的SL DRX配置作为第一SL DRX配置，则选择SL QoS profile 7作为第一SL DRX配置。
方法1.6，根据该至少两个SL DRX配置对应的PQI的索引，确定第一SL DRX配置
比如，比较该至少两个SL DRX配置对应的PQI的索引，选择索引最小或最大的PQI对应的SL DRX配置，作为第一SL DRX配置。
比如，SL DRX配置1对应PQI 1和PQI 2，SL DRX配置2对应PQI 3、PQI 4和PQI 5，SL DRX配置3对应PQI 6和PQI 7，且PQI 1、PQI 2、PQI 3、PQI 4、PQI 5、PQI 6、PQI 7的索引分别为1、2、3、4、5、6、7。假如选择索引最小的PQI对应的SL DRX配置作为第一SL DRX配置，则选择PQI 1作为第一SL DRX配置。假如选择索引最大的PQI对应的SL DRX配置作为第一SL DRX配置，则选择PQI 7作为第一SL DRX配置。
方法2，根据该至少两个SL DRX配置生成第一SL DRX配置
也即，第一SL DRX配置是根据至少两个SL DRX配置生成的，第一SL DRX配置中的参数的取值来自至少两个SL DRX配置中的一个或多个SL DRX配置。
比如，根据该至少两个SL DRX配置中的每个参数的最大值或最小值，生成第一SL DRX 配置。也即，第一SL DRX配置包含的第一参数的取值，是至少两个SL DRX配置分别包含的第一参数的取值中的最小值或最大值。示例性地，生成的第一SL DRX配置中的SL DRX cycle的取值、sl-DRX-HARQ-RTT-Timer的取值、sl-DRX-startOffset的取值、sl-DRX-slotOffset的取值均为该至少两个DRX配置中的最小值，生成的第一SL DRX配置中的sl-DRX-onDurationTimer的取值、sl-DRX-inactivityTimer的取值、sl-DRX-RetransmissionTimer的取值均为该至少两个DRX配置中的最大值。
基于上述方案，在终端的业务对应至少两个SL DRX配置的情况下，发送侧的终端和接收侧的终端使用相同的方法，从至少两个SL DRX配置确定一个SL DRX配置，从而发送侧的终端和接收侧的终端使用相同的SL DRX配置，因而可以对齐发送侧的终端与接收侧的终端之间的SL激活时间。
作为一种实现方法，上述步骤602及步骤603也可以替换为：根据该至少两个QoS参数组确定第一QoS参数组，并确定该第一QoS参数组对应的DRX配置为第一DRX配置。其中，以QoS参数组为PQI为例，则第一QoS参数组(也即第一PQI)可以是多个PQI中取值最小或最大的PQI，或者是多个PQI中索引最小或最大的PQI。以QoS参数组为SL QoS profile为例，则第一QoS参数组(也即第一SL QoS profile)可以是多个SL QoS profile中索引最小或最大的SL QoS profile。
实施例二
图7为本申请实施例提供的一种SL DRX配置的确定方法示意图，包括以下步骤：
步骤701至步骤702，同前述步骤601至步骤602，可参考前述描述。
步骤703，终端确定至少两个SL DRX配置，作为使用的SL DRX配置，其中，终端的业务对应的SL激活时间包括以下一个运行时间或多个运行时间的并集：该至少两个SL DRX配置分别对应的sl-DRX-OnDurationTimer的运行时间、该至少两个SL DRX配置分别对应的sl-DRX-InactivityTimer的运行时间或该至少两个SL DRX配置分别对应的sl-DRX-RetransmissionTimer的运行时间。
终端可以根据该至少两个SL DRX配置，确定该至少两个SL DRX配置分别对应的定时器的运行时间。这里的定时器，包括sl-DRX-onDurationTimer、sl-DRX-inactivityTimer、sl-DRX-HARQ-RTT-Timer或sl-DRX-RetransmissionTimer中的一个或多个。确定定时器的运行时间包括确定定时器的定时时长、启动时间、重启时间、超时时间或停止时间。
终端针对终端的业务对应的destination Layer-2 ID，维护该多套SL DRX定时器。根据每套SL DRX定时器的运行时间，可以确定destination Layer-2 ID对应的SL激活时间。destination Layer-2 ID对应的SL激活时间也可以称为终端的业务对应的SL激活时间。
图8为不同SL DRX配置对应的sl-DRX-OnDurationTimer的运行时间示意图。图8示例性地，给出了SL DRX配置1对应的sl-DRX-OnDurationTimer的运行时间和SL DRX配置2对应的sl-DRX-OnDurationTimer的运行时间。其中，SL DRX配置1包含SL DRX周期1，SL DRX配置2包含SL DRX周期2。基于图8的示例，SL DRX配置1对应的sl-DRX-OnDurationTimer的运行时间包括T1至T2之间的时长，以及T5至T6之间的时长。SL DRX配置2对应的sl-DRX-OnDurationTimer的运行时间包括T3至T4之间的时长，以及T7至T8之间的时长。destination Layer-2 ID对应的SL激活时间包括T1至T2之间的时 长，T3至T4之间的时长，T5至T6之间的时长，以及T7至T8之间的时长。
图9为不同SL DRX配置对应的sl-DRX-InactivityTimer及sl-DRX-OnDurationTimer的运行时间示意图。图9示例性地，给出了SL DRX配置1对应的sl-DRX-InactivityTimer及sl-DRX-OnDurationTimer的运行时间和SL DRX配置2对应的sl-DRX-InactivityTimer的运行时间。基于图9的示例，SL DRX配置1对应的sl-DRX-OnDurationTimer的运行时间包括T1至T4之间的时长。SL DRX配置1对应的sl-DRX-InactivityTimer运行时间包括T3至T5之间的时长。SL DRX配置2对应的sl-DRX-InactivityTimer运行时间包括T3至T4之间的时长。destination Layer-2 ID对应的SL激活时间包括T3至T5之间的时长，T3至T4之间的时长，以及T1至T4之间的时长，也即destination Layer-2 ID对应的SL激活时间包括T1至T5之间的时长。
图10为不同SL DRX配置对应的sl-DRX-RetransmissionTimer及sl-DRX-OnDurationTimer的运行时间示意图。图10示例性地，给出了SL DRX配置1对应的sl-DRX-RetransmissionTimer及sl-DRX-OnDurationTimer的运行时间和SL DRX配置2对应的sl-DRX-RetransmissionTimer的运行时间。基于图10的示例，SL DRX配置1对应的sl-DRX-RetransmissionTimer运行时间包括T3至T5之间的时长。SL DRX配置2对应的sl-DRX-RetransmissionTimer运行时间包括T3至T4之间的时长。destination Layer-2 ID对应的SL激活时间包括T3至T5之间的时长，T3至T4之间的时长，以及T1至T4之间的时长，也即destination Layer-2 ID对应的SL激活时间包括T1至T5之间的时长。
上述终端既可以是发送侧的终端，也可以是接收侧的终端。也即发送侧的终端和接收侧的终端按照相同的方法，根据终端的业务对应的至少两个SL DRX配置，确定该至少两个SL DRX配置分别对应的定时器的运行时间，从而发送侧的终端和接收侧的终端可以对齐发送侧的终端与接收侧的终端之间的SL激活时间，可以保障正确通信。
需要说明的是，对于每个SL DRX配置对应的sl-DRX-onDurationTimer，终端可以根据每个SL DRX配置指示的参数的值，确定该SL DRX配置对应的sl-DRX-onDurationTimer的运行时间。其中，每个SL DRX配置对应的sl-DRX-onDurationTimer都是周期性地运行。
作为一种实现方法，终端可以根据该至少两个SL DRX配置，以及与destination Layer-2 ID对应的SCI，确定该至少两个SL DRX配置对应的定时器的运行时间。其中，该destination Layer-2 ID对应的SCI的含义可以参考前述描述。比如，当发送侧的终端向接收侧的终端发送与该destination Layer-2 ID对应的SCI之后，启动各个SL DRX配置分别对应的sl-DRX-inactivityTimer、各个SL DRX配置分别对应的sl-DRX-HARQ-RTT-Timer或各个SL DRX配置分别对应的sl-DRX-RetransmissionTimer中的一个或多个。再比如，当接收侧的终端接收到发送侧的终端发送的与该destination Layer-2 ID对应的SCI之后，启动各个SL DRX配置分别对应的sl-DRX-inactivityTimer、各个SL DRX配置分别对应的sl-DRX-HARQ-RTT-Timer或各个SL DRX配置分别对应的sl-DRX-RetransmissionTimer中的一个或多个。
因此，当destination Layer-2 ID相同，但传输的数据对应的SL QoS profile/PQI不同，则各个SL DRX配置对应的定时器的启动方法是相同的。在destination Layer-2 ID对应的SL激活时间内，发送侧的终端发送的与该destination Layer-2 ID对应的多个数据，可以对应不同的SL QoS profile/PQI。
基于上述方案，在终端的业务对应至少两个SL DRX配置的情况下，发送侧的终端和接收侧的终端分别针对该终端的业务对应的每个SL DRX配置都维护一套SL DRX定时器，发送侧的终端和接收侧的终端使用相同的至少两个SL DRX配置，维护相同的定时器，且采用相同的SL DRX定时器的激活方法，因而可以对齐发送侧的终端与接收侧的终端之间的SL激活时间。
实施例三
图11为本申请实施例提供的一种SL DRX配置的确定方法示意图，包括以下步骤：
步骤1101至步骤1102，同前述步骤601至步骤602，可参考前述描述。
该步骤的具体实现方法可以参考前述步骤601的实现，不再赘述。
步骤1103，终端确定至少两个SL DRX配置，作为使用的SL DRX配置，其中，终端的业务对应的SL激活时间包括以下一个运行时间或多个运行时间的并集：该至少两个SL DRX配置分别对应的sl-DRX-OnDurationTimer的运行时间、第二SL DRX配置对应的第一sl-DRX-InactivityTimer的运行时间或第三SL DRX配置对应的第一sl-DRX-RetransmissionTimer的运行时间。
其中，第二SL DRX配置和第三SL DRX配置分别是至少两个SL DRX配置中的一个，第二SL DRX配置与第三SL DRX配置可以相同，也可以不同。
具体地，终端根据该至少两个SL DRX配置，确定该至少两个SL DRX配置分别对应的sl-DRX-onDurationTimer的运行时间，以及确定第二SL DRX配置对应的第一sl-DRX-inactivityTimer、第三SL DRX配置对应的第一sl-DRX-RetransmissionTimer中的一个或多个的运行时间。可选的，还确定第四SL DRX配置对应的第一sl-DRX-HARQ-RTT-Timer的运行时间。该第四SL DRX配置是至少两个SL DRX配置中的一个，第四SL DRX配置可以与第二SL DRX配置或第三SL DRX配置相同，也可以与第二SL DRX配置和第三SL DRX配置均不同。
其中，第一sl-DRX-inactivityTimer是该至少两个SL DRX配置分别对应的sl-DRX-inactivityTimer中的一个，比如是取值最小的sl-DRX-inactivityTimer或取值最大的sl-DRX-inactivityTimer。第一sl-DRX-HARQ-RTT-Timer是该至少两个SL DRX配置分别对应的sl-DRX-HARQ-RTT-Timer中的一个，比如是取值最小的sl-DRX-HARQ-RTT-Timer或取值最大的sl-DRX-HARQ-RTT-Timer。第一sl-DRX-RetransmissionTimer是该至少两个SL DRX配置分别对应的sl-DRX-RetransmissionTimer中的一个，比如是取值最小的sl-DRX-RetransmissionTimer或取值最大的sl-DRX-RetransmissionTimer。
也即，终端针对终端的业务对应的destination Layer-2 ID，维护多个sl-DRX-onDurationTimer，以及维护一个sl-DRX-inactivityTimer、一个sl-DRX-HARQ-RTT-Timer以及一个sl-DRX-RetransmissionTimer。终端根据该至少两个SL DRX配置分别对应的sl-DRX-onDurationTimer的运行时间，以及第一sl-DRX-inactivityTimer或第一sl-DRX-RetransmissionTimer中的一个或多个的运行时间确定该destination Layer-2 ID对应的SL激活时间。该destination Layer-2 ID对应的SL激活时间也称为终端的业务对应的SL激活时间。
不同SL DRX配置对应的sl-DRX-OnDurationTimer的运行时间的示例，可以参考图8 所示的示意图及相关描述。
图12为不同SL DRX配置对应的sl-DRX-OnDurationTimer的运行时间以及第一sl-DRX-InactivityTimer的运行时间示意图。图12示例性地，给出了SL DRX配置1对应的sl-DRX-OnDurationTimer的运行时间、SL DRX配置2对应的sl-DRX-OnDurationTimer的运行时间以及第一sl-DRX-InactivityTimer的运行时间。该示例中，第一sl-DRX-InactivityTimer对应SL DRX配置1、SL DRX配置2或其它SL DRX配置。以下以第一sl-DRX-InactivityTimer对应SL DRX配置1为例进行说明。基于图12的示例，SL DRX配置1对应的sl-DRX-OnDurationTimer运行时间包括T1至T3之间的时长，以及T6至T7之间的时长。SL DRX配置2对应的sl-DRX-OnDurationTimer运行时间包括T4至T5之间的时长，以及T8至T9之间的时长。第一sl-DRX-InactivityTimer包括T2至T3之间的时长。因此，destination Layer-2 ID对应的SL激活时间包括T1至T3之间的时长，T4至T5之间的时长，T6至T7之间的时长，以及T8至T9之间的时长。
图13为不同SL DRX配置对应的sl-DRX-OnDurationTimer的运行时间以及第一sl-DRX-RetransmissionTimer的运行时间示意图。图13示例性地，给出了SL DRX配置1对应的sl-DRX-OnDurationTimer的运行时间、SL DRX配置2对应的sl-DRX-OnDurationTimer的运行时间以及第一sl-DRX-RetransmissionTimer的运行时间。该示例中，第一sl-DRX-RetransmissionTimer对应SL DRX配置1、SL DRX配置2或其它SL DRX配置。以下以第一sl-DRX-RetransmissionTimer对应SL DRX配置1为例进行说明。基于图13的示例，SL DRX配置1对应的sl-DRX-OnDurationTimer运行时间包括T1至T3之间的时长，以及T6至T7之间的时长。SL DRX配置2对应的sl-DRX-OnDurationTimer运行时间包括T4至T5之间的时长，以及T8至T9之间的时长。第一sl-DRX-RetransmissionTimer包括T2至T3之间的时长。因此，destination Layer-2 ID对应的SL激活时间包括T1至T3之间的时长，T4至T5之间的时长，T6至T7之间的时长，以及T8至T9之间的时长。
作为一种实现方法，上述步骤1102，具体可以是：终端根据该至少两个SL DRX配置，以及与该destination Layer-2 ID对应的SCI，确定第一sl-DRX-inactivityTimer、第一sl-DRX-HARQ-RTT-Timer或第一sl-DRX-RetransmissionTimer中的一个或多个的运行时间。其中，该destination Layer-2 ID对应的SCI的含义可以参考前述描述。比如，当发送侧的终端向接收侧的终端发送与该destination Layer-2 ID对应的SCI之后，启动第一sl-DRX-inactivityTimer、第一sl-DRX-HARQ-RTT-Timer或第一sl-DRX-RetransmissionTimer中的一个或多个。再比如，当接收侧的终端接收到发送侧的终端发送的与该destination Layer-2 ID对应的SCI之后，启动第一sl-DRX-inactivityTimer、第一sl-DRX-HARQ-RTT-Timer或第一sl-DRX-RetransmissionTimer中的一个或多个。
上述终端既可以是发送侧的终端，也可以是接收侧的终端。也即发送侧的终端和接收侧的终端按照相同的方法，根据终端的业务对应的至少两个SL DRX配置，确定该至少两个SL DRX配置对应的sl-DRX-onDurationTimer的运行时间，以及一个sl-DRX-inactivityTimer、一个sl-DRX-HARQ-RTT-Timer和一个sl-DRX-RetransmissionTimer的运行时间。从而发送侧的终端和接收侧的终端可以对齐SL激活时间，可以保障正确通信。
基于上述方案，在终端的业务对应至少两个SL DRX配置的情况下，发送侧的终端和接收侧的终端维护每个DL DRX配置对应的sl-DRX-onDurationTimer，以及维护一套 sl-DRX-InactivityTimer、sl-DRX-HARQ-RTT-Timer或sl-DRX-RetransmissionTimer，发送侧的终端和接收侧的终端使用相同的至少两个SL DRX配置，维护相同的定时器，且采用相同的SL DRX定时器的激活方法，因而可以对齐发送侧的终端与接收侧的终端之间的SL激活时间。并且，由于只维护一套sl-DRX-InactivityTimer、sl-DRX-HARQ-RTT-Timer或sl-DRX-RetransmissionTimer，因而可以减少复杂度。
实施例四
该实施例四与实施例二相同的是：发送侧的终端和接收侧的终端都使用终端的业务对应的至少两个SL DRX配置，每个SL DRX配置对应一套SL DRX定时器，且针对终端的业务，维护每套SL DRX定时器。终端的业务对应同一个destination Layer-2 ID，因此也可以称为针对一个destination Layer-2 ID，维护每套SL DRX定时器
该实施例四与实施例二不同的是：该实施例四中，根据每套SL DRX定时器的运行时间，可以确定一个SL激活时间。一个SL 激活时间包括以下一个运行时间或多个运行时间的并集：一套SL DRX定时器中的sl-DRX-OnDurationTimer的运行时间、该套SL DRX定时器中的sl-DRX-InactivityTimer的运行时间或该套SL DRX定时器中的sl-DRX-RetransmissionTimer的运行时间。每个SL激活时间为一个或多个SL QoS profile/PQI对应的SL激活时间，也即SL激活时间是与SL QoS profile/PQI具有对应关系的。其中，该一个或多个SL QoS profile/PQI为该SL激活时间对应的SL DRX配置所对应的一个或多个SL QoS profile/PQI。发送侧的终端在一个或多个SL QoS profile/PQI对应的SL激活时间分别发送该destination Layer-2 ID和该SL QoS profile/PQI对应的SCI。接收侧的终端在一个或多个SL QoS profile/PQI对应的SL激活时间接收该destination Layer-2 ID对应的SCI，或者接收侧的终端在一个或多个SL QoS profile/PQI对应的SL激活时间分别接收该destination Layer-2 ID和该SL QoS profile/PQI对应的SCI。该destination Layer-2 ID和该SL QoS profile/PQI对应的SCI是指：SCI中包含的destination Layer-1ID是该destination Layer-2 ID的低8位(Least significant bits，8LSB)，并且该SCI调度的数据的SL QoS profile/PQI为该SL QoS profile/PQI。在该实施例四中，终端的SL激活时间包括一个或多个SL QoS profile/PQI对应的SL激活时间。
作为一种实现方法，不同终端确定的destination Layer-2 ID对应的至少两个SL DRX配置是相同的。例如，destination Layer-2 ID对应的业务在不同终端之间是相同的，则该destination Layer-2 ID对应的业务的QoS参数组对应的至少两个SL DRX配置是相同的。因此，destination Layer-2 ID对应的业务在发送侧的终端和接收侧的终端之间可以是相同的。destination Layer-2 ID对应的至少两个SL DRX配置在发送侧的终端和接收侧的终端之间可以是相同的。
作为另一种实现方法，不同终端确定的destination Layer-2 ID对应的至少两个SL DRX配置是不同的。例如，destination Layer-2 ID对应的业务在不同终端之间是不同的，则该destination Layer-2 ID对应的业务的QoS参数组对应的至少两个SL DRX配置是不同的。若destination Layer-2 ID对应的业务，是该destination Layer-2 ID对应的终端感兴趣业务，由于不同终端感兴趣的业务可以不同，则destination Layer-2 ID对应的业务在不同终端之间可以是不同的。因此，destination Layer-2 ID对应的业务在发送侧的终端和接收侧的终端之间可 以是不同的。destination Layer-2 ID对应的至少两个SL DRX配置在发送侧的终端和接收侧的终端之间可以是不同的。
作为一种实现方法，在一个SL激活时间内，发送侧的终端发送与该destination Layer-2 ID对应的SCI，该SCI中包含与该SCI调度的数据对应的用于指示一个或多个SL QoS profile/PQI的指示信息。发送侧的终端确定与该SL QoS profile/PQI对应的DRX配置，并确定该DRX配置对应的sl-DRX-inactivityTimer、sl-DRX-HARQ-RTT-Timer或sl-DRX-RetransmissionTimer中的一个或多个的运行时间。接收侧的终端收到SCI后，获取SCI中的SL QoS profile/PQI，确定与该SL QoS profile/PQI对应的DRX配置，并确定该DRX配置对应的sl-DRX-inactivityTimer、sl-DRX-HARQ-RTT-Timer或sl-DRX-RetransmissionTimer中的一个或多个的运行时间。
不同SL DRX配置对应的sl-DRX-OnDurationTimer的运行时间的示例，可以参考图8所示的示意图及相关描述。
图14为不同SL DRX配置对应的sl-DRX-OnDurationTimer的运行时间以及sl-DRX-InactivityTimer的运行时间示意图。图14示例性地，给出了SL DRX配置1对应的sl-DRX-OnDurationTimer的运行时间、SL DRX配置1对应的sl-DRX-InactivityTimer的运行时间、SL DRX配置2对应的sl-DRX-OnDurationTimer的运行时间以及SL DRX配置2对应的sl-DRX-InactivityTimer的运行时间。SL DRX配置1对应SL QoS profile 1，SL DRX配置2对应SL QoS profile 2。基于图14的示例，当发送端的终端在SL QoS profile 1对应的SL激活时间发送该destination Layer-2 ID对应的SCI 1，则该SCI 1中包含SL QoS profile 1的指示信息，接收端的终端获取到SCI 1中的用于指示SL QoS profile 1的指示信息，根据该指示信息确定SCI 1调度的数据对应SL QoS profile 1，则确定SL QoS profile 1对应的SL DRX配置1，进而启动sl-DRX-InactivityTimer，并根据SL DRX配置1中的sl-DRX-InactivityTimer，确定启动的sl-DRX-InactivityTimer的运行时长，因此，SL QoS profile1对应的SL激活时间包括T1至T3之间的时长，以及T2至T4之间的时长，也即SL QoS profile 1对应的SL激活时间包括T1至T4之间的时长。基于图14的示例，当发送端的终端在SL QoS profile 2对应的SL激活时间发送该destination Layer-2 ID对应的SCI 2，则该SCI 2中包含用于SL QoS profile 2的指示信息，接收端的终端获取到SCI 2中的SL QoS profile 2的指示信息，根据该指示信息确定SCI 2调度是数据对应SL QoS profile 2，则确定SL QoS profile 2对应的SL DRX配置2，进而启动sl-DRX-InactivityTimer，并根据SL DRX配置2中的sl-DRX-InactivityTimer，确定启动的sl-DRX-InactivityTimer的运行时长，因此，SL QoS profile 2对应的SL激活时间包括T5至T7之间的时长，以及T6至T7之间的时长，也即SL QoS profile 2对应的SL激活时间包括T5至T7之间的时长。该destination Layer-2 ID对应的SL激活时间包括T1至T3之间的时长，以及T5至T7之间的时长。
为了满足“在一个SL激活时间内，发送侧的终端发送与该destination Layer-2 ID对应的SCI，该SCI中包含与该SCI调度的数据对应的一个或多个SL QoS profile/PQI”，发送侧的终端的服务数据适配协议(service data adaptation protocol，SDAP)层到媒体接入控制(medium access control，MAC)层的每一层，需要指示或标记每个数据包对应的SL QoS profile/PQI。对应相同SL QoS profile/PQI的数据可以复用到同一个MAC协议数据单元(protocol data unit，PDU)中，对应不同SL QoS profile/PQI的数据复用到不同的MAC PDU 中。需要说明的是，对于destination Layer-2 ID相同，但携带的SL QoS profile/PQI不同的SCI，会导致该SL QoS profile/PQI对应的SL DRX定时器状态改变，而不会导致其他SL QoS profile/PQI对应的SL DRX定时器状态改变。
作为另一种实现方法，发送侧的终端发送与该destination Layer-2 ID对应的SCI，该SCI中不包含该SCI调度的数据对应的SL QoS profile/PQI。接收侧的终端根据收到的与destination Layer-2 ID对应的SCI后，确定每个SL DRX配置对应的sl-DRX-inactivityTimer、sl-DRX-HARQ-RTT-Timer或sl-DRX-RetransmissionTimer中的一个或多个的运行时间，也即接收侧的终端确定destination Layer-2 ID对应的SL激活时间为所有SL DRX配置对应的SL激活时间。
图15为不同SL DRX配置对应的sl-DRX-OnDurationTimer的运行时间以及sl-DRX-InactivityTimer的运行时间示意图。图15示例性地，给出了SL DRX配置1对应的sl-DRX-OnDurationTimer的运行时间、SL DRX配置1对应的sl-DRX-InactivityTimer的运行时间、SL DRX配置2对应的sl-DRX-OnDurationTimer的运行时间以及SL DRX配置2对应的sl-DRX-InactivityTimer的运行时间。其中，SL DRX配置2对应的sl-DRX-OnDurationTimer的运行时间与DRX配置1对应的sl-DRX-OnDurationTimer的运行时间相同。SL DRX配置1对应SL QoS profile 1，SL DRX配置2对应SL QoS profile 2。基于图15的示例，当发送端的终端在SL QoS profile 1对应的SL激活时间发送该destination Layer-2 ID和SL QoS profile 1对应的SCI 1，且该SCI 1中不包含用于指示SL QoS profile 1的指示信息，接收端的终端根据SL DRX配置1中的sl-DRX-InactivityTimer的时长，启动一个sl-DRX-InactivityTimer，以及根据SL DRX配置2中的sl-DRX-InactivityTimer的时长，启动另一个sl-DRX-InactivityTimer。因此，SL QoS profile 1对应的SL激活时间包括T1至T3之间的时长，以及T2至T4之间的时长，也即SL QoS profile 1对应的SL激活时间包括T1至T4之间的时长。SL QoS profile 2对应的SL激活时间包括T1至T3之间的时长，以及T2至T3之间的时长，也即SL QoS profile 2对应的SL激活时间包括T1至T3之间的时长。该destination Layer-2 ID对应的SL激活时间包括T1至T3之间的时长，T2至T4之间的时长，T2至T3之间的时长，也即该destination Layer-2 ID对应的SL激活时间包括T1至T4之间的时长。
为解决上述第二个问题，本申请实施例提供以下实施例五至实施例九分别对应的不同解决方案。
实施例五
该方案是基于SL QoS profile的粒度，为终端配置SL DRX配置。
图16为本申请实施例提供的一种SL DRX配置的确定方法示意图，包括以下步骤：
步骤1601，终端获取配置信息，该配置信息包括至少一个SL DRX配置分别对应的SL QoS profile的索引。
该配置信息可以是预配置的，基站配置的，核心网网元配置的或协议预定义的。
例如，在上述配置信息指示了如下对应关系：
DRX配置1，对应SL QoS profile 1的索引，SL QoS profile 2的索引；
DRX配置2，对应SL QoS profile 3的索引，SL QoS profile 4的索引，SL QoS profile 5 的索引，SL QoS profile 6的索引；
DRX配置3，对应SL QoS profile 7的索引。
即配置信息包括至少一个SL DRX配置分别对应的SL QoS profile的索引列表。
又如，在上述配置信息指示了如下对应关系：
DRX配置1，对应SL QoS profile的索引的起始为3，长度为2；即，DRX配置1对应SL QoS profile的索引为3、4；
DRX配置2，对应SL QoS profile的索引的起始为7，长度为1；即，DRX配置2对应SL QoS profile的索引为7；
DRX配置3，对应SL QoS profile的索引的起始为10，长度为3；即，DRX配置3对应SL QoS profile的索引为10、11、12。
即配置信息包括至少一个SL DRX配置分别对应的SL QoS profile的索引的起始和长度。其中，起始的值和长度的值可以分别用两个指示信息指示，例如，指示信息1用于指示索引起始值，指示信息2用于指示索引长度值。起始的值和长度的值也可以用一个指示信息指示，该指示信息用于指示起始的值和长度的值联合编码成的一个值，本文将该值称为起始和长度联合值，也可以称为起始和长度指示值(start and length indicator value，SLIV)。假设SL QoS profile索引总数为N，将起始值记为S，将长度值记为L，起始和长度联合值记为M。如果(L-1)小于等于N/2，则M＝N*(L-1)+S，否则，也就是(L-1)大于N/2，则M＝N*(N-L+1)+(N-1-S)。其中，S为大于等于0且小于N的整数，L为大于0且小于等于(N-S)的整数。
作为一种实现方法，该配置信息还指示了该至少一个SL DRX配置，也即该配置信息一方面配置了至少一个SL DRX配置，另一方面还配置了该至少一个SL DRX配置中每个SL DRX配置对应的SL QoS profile的索引。
作为另一种实现方法，该配置信息没有配置该至少一个SL DRX配置，而是通过另一个配置信息单独配置该至少一个SL DRX配置。也即通过一个配置信息配置至少一个SL DRX配置，通过另一个配置信息配置该至少一个SL DRX配置中每个SL DRX配置对应的SL QoS profile的索引。
步骤1602，终端根据第一SL QoS profile的索引，以及至少一个SL DRX配置分别对应的SL QoS profile的索引，确定第一SL QoS profile的索引对应的第一SL DRX配置。
基于上述方案，终端可以确定每个SL QoS profile对应的SL DRX配置。比如，终端先确定终端或终端的业务对应的第一SL QoS profile，以及确定该第一SL QoS profile的索引，然后根据第一SL QoS profile的索引，以及至少一个SL DRX配置分别对应的SL QoS profile的索引，可以确定第一SL QoS profile的索引对应的第一SL DRX配置，该第一SL DRX配置即为第一SL QoS profile对应的SL DRX配置。
作为一种实现方法，SL QoS profile的索引是用该SL QoS profile在所有SL RB配置对应的SL QoS profile中的排序来表示。SL QoS profile的索引根据SL RB列表中SL RB配置的顺序，以及SL RB配置包含的SL QoS profile列表中SL QoS profile的顺序确定。SL QoS profile的索引可以先按一个SL RB配置包含的SL QoS profile列表中SL QoS profile的顺序，再按SL RB列表中SL RB配置的顺序依次对SL QoS profile编号。编号可以从任意一个大于或等于0的整数开始。编号可以以1递增。例如，SL RB列表中的SL RB配置按顺序依 次为SL RB配置1、SL RB配置2、SL RB配置3，以此类推。SL RB配置1对应的SL QoS profile按其在SL QoS profile列表中的顺序依次编号为1～N1，SL RB配置2对应的SL QoS profile按其在SL QoS profile列表中的顺序依次编号为N1+1～N2，SL RB配置3对应的SL QoS profile按其在SL QoS profile列表中的顺序依次编号为N2+1～N3，以此类推。则SL QoS profile的索引依次为1，……，N1，N1+1，N1+2，……，N2，N2+1，……，N3，……。比如，在上述配置信息指示了如下对应关系：
DRX配置1，对应1，3；
DRX配置2，对应2，4，6，7；
DRX配置3，对应5。
其中，1，2，……，7为各个SL QoS profile的索引。
作为一种实现方法，SL QoS profile的索引是用该SL QoS profile对应的SL RB配置的索引以及该SL QoS profile在该SL RB配置对应的SL QoS profile中的排序来表示。按该SL QoS profile在该SL RB配置包含的SL QoS profile列表中的顺序依次对SL QoS profile编号。编号可以从任意一个大于或等于0的整数开始。编号可以以1递增。例如，SL RB配置1对应的SL QoS profile按其在SL QoS profile列表中的顺序依次编号为1～N1，SL RB配置2对应的SL QoS profile按其在SL QoS profile列表中的顺序依次编号为1～N2，SL RB配置3对应的SL QoS profile按其在SL QoS profile列表中的顺序依次编号为1～N3，以此类推。SL RB配置1为索引为1的SL RB配置。SL RB配置2为索引为2的SL RB配置。SL RB配置3为索引为3的SL RB配置。比如，在上述配置信息指示了如下对应关系：
DRX配置1，对应((1)，(1，2))；
DRX配置2，对应((1)，(3，4))；
DRX配置3，对应((2)，(1，3))。
其中，((X)，(Y，Z))代表SL QoS profile的索引，X是SL RB配置的索引，Y和Z是各个SL QoS profile的在该SL RB配置中的索引。((1)，(1，2))中的(1)表示索引为1的SL RB配置，即SL RB配置1。((1)，(1，2))中的(1，2)表示SL RB配置1对应的索引为1和2的SL QoS profile，((1)，(3，4))中的(1)表示索引为1的SL RB配置，即SL RB配置1。((1)，(3，4))中的(3，4)表示SL RB配置1对应的索引为3和4的SL QoS profile，((2)，(1，3))中的(2)表示索引为2的SL RB配置，即SL RB配置2。((2)，(1，3))中的(1，3)表示SL RB配置2对应的索引为1和3的SL QoS profile。
又如，在上述配置信息指示了如下对应关系：
DRX配置1，对应(1，1)，(1，2)；
DRX配置2，对应(1，3)，(1，4)，(2，2)；
DRX配置3，对应(2，1)，(2，3)。
其中，(X，Y)代表SL QoS profile的索引，X是SL RB配置的索引，Y是SL QoS profile在该SL RB配置中的索引。
作为一种实现方法，可以在各个SL RB配置中携带该SL RB配置对应的各个SL QoS profile的索引，从而终端接收到SL RB配置及该SL RB配置对应的SL QoS profile时，可以获知SL QoS profile的索引与SL QoS profile之间的对应关系。一种方式是在SL RB配置对应的SL QoS profile中携带该SL QoS profile的索引。不同SL RB配置对应的各个SL QoS  profile的索引均不相同。后续，通过上述步骤1601的配置信息，可以获知配置信息中的SL QoS profile的索引所指示的SL QoS profile。
作为一种实现方法，可以在各个SL RB配置中携带该SL RB配置对应的各个SL QoS profile在该SL RB配置中的索引，从而终端接收到SL RB配置及该SL RB配置对应的SL QoS profile时，可以获知SL QoS profile在该SL RB配置中的索引与SL QoS profile之间的对应关系。一种方式是在SL RB配置对应的SL QoS profile中携带该SL QoS profile在该SL RB配置中的索引。不同SL RB配置对应的SL QoS profile在SL RB配置中的索引可以相同。SL QoS profile的索引是用该SL QoS profile对应的SL RB配置的索引以及该SL QoS profile在该SL RB配置中的索引来表示。后续，通过上述步骤1601的配置信息，可以获知配置信息中的SL QoS profile的索引所指示的SL QoS profile。
基于上述方案，在配置信息中携带各个SL DRX配置分别对应的SL QoS profile的索引，而不是携带SL QoS profile，可以减少信令开销及存储开销。
实施例六
该方案是基于PQI的粒度，为终端配置SL DRX配置。
图17为本申请实施例提供的一种SL DRX配置的确定方法示意图，包括以下步骤：
步骤1701，终端获取配置信息，该配置信息包括至少一个SL DRX配置分别对应的PQI的索引。
该配置信息可以是预配置的，基站配置的，核心网网元配置的或协议预定义的。
例如，在上述配置信息指示了如下对应关系：
DRX配置1，对应PQI 1的索引，PQI 2的索引；
DRX配置2，对应PQI 3的索引，PQI 4的索引，PQI 5的索引，PQI 6的索引；
DRX配置3，对应PQI 7的索引。
作为一种实现方法，该配置信息还指示了该至少一个SL DRX配置，也即该配置信息一方面配置了至少一个SL DRX配置，另一方面还配置了该至少一个SL DRX配置中每个SL DRX配置对应的PQI的索引。
作为另一种实现方法，该配置信息没有配置该至少一个SL DRX配置，而是通过另一个配置信息单独配置该至少一个SL DRX配置。也即通过一个配置信息配置至少一个SL DRX配置，通过另一个配置信息配置该至少一个SL DRX配置中每个SL DRX配置对应的PQI的索引。
步骤1702，终端根据第一PQI的索引，以及至少一个SL DRX配置分别对应的PQI的索引，确定第一PQI的索引对应的第一SL DRX配置。
基于上述方案，终端可以确定每个PQI对应的SL DRX配置。比如，终端先确定终端或终端的业务对应的第一PQI，并确定该第一PQI的索引，然后根据第一PQI的索引，以及至少一个SL DRX配置分别对应的PQI的索引，可以确定第一PQI的索引对应的SL DRX配置，该SL DRX配置即为第一PQI对应的第一SL DRX配置。
其中，这里的PQI可以是标准PQI或非标准PQI。
针对标准PQI，可以用该标准PQI的取值作为该标准PQI的索引。或者，标准PQI的索引为包含该标准PQI的SL QoS profile的索引，SL QoS profile的索引如实施例五中所述。
针对非标准PQI，非标准PQI的索引为包含该非标准PQI的SL QoS profile的索引，SL QoS profile的索引如实施例五中所述。或者，还可以用以下任一方法来表示非标准PQI的索引：
方法A，非标准PQI的索引为包含该非标准PQI的SL QoS profile，在所有SL RB配置对应的SL QoS profile中的排序来表示。
例如，SL RB列表中的SL RB配置按顺序依次为SL RB配置1、SL RB配置2、SL RB配置3，以此类推。SL RB配置1对应的SL QoS profile按其在SL QoS profile列表中的顺序依次编号为1～N1，SL RB配置2对应的SL QoS profile按其在SL QoS profile列表中的顺序依次编号为N1+1～N2，SL RB配置3对应的SL QoS profile按其在SL QoS profile列表中的顺序依次编号为N2+1～N3，以此类推。则SL QoS profile的索引依次为1，……，N1，N1+1，N1+2，……，N2，N2+1，……，N3，……。并且，索引为i的SL QoS profile包含的非标准PQI的索引为i，i取值为1，2，3，……。
比如，在上述配置信息指示了如下对应关系：
DRX配置1，对应1，3；
DRX配置2，对应2，4，6；
DRX配置3，对应5，7。
其中，1，2，……，7为各个非标准PQI的索引。
方法B，非标准PQI的索引是用包含该非标准PQI的SL QoS profile对应的SL RB配置的索引以及该SL QoS profile在该SL RB配置对应的SL QoS profile中的排序来表示。
例如，SL RB配置1对应的SL QoS profile按其在SL QoS profile列表中的顺序依次编号为1～N1，SL RB配置2对应的SL QoS profile按其在SL QoS profile列表中的顺序依次编号为1～N2，SL RB配置3对应的SL QoS profile按其在SL QoS profile列表中的顺序依次编号为1～N3，以此类推。SL RB配置1为索引为1的SL RB配置。SL RB配置2为索引为2的SL RB配置。SL RB配置3为索引为3的SL RB配置。并且，在一个SL RB配置中索引为i的SL QoS profile包含的非标准PQI的索引为i，i取值为1，2，3，……。
比如，在上述配置信息指示了如下对应关系：
DRX配置1，对应(1，1)，(1，2)；
DRX配置2，对应(1，3)，(1，4)，(2，2)；
DRX配置3，对应(2，1)，(2，3)。
其中，(X，Y)代表非标准PQI的索引，X是SL RB配置的索引，Y是非标准PQI在该SL RB配置中的索引。
方法C，非标准PQI的索引为SL RB配置中包含的该非标准PQI索引。一种方式是在非标准PQI中包含该非标准PQI的索引。也即，在非标准PQI中增加一个索引。
其中，索引的值可以与标准PQI的值重合，也可以与所有标准PQI的值都不重合。如果非标准PQI的索引与某个标准PQI的值重合，则在上述配置信息中还需要指示是标准PQI还是非标准PQI，或者是将标准PQI和非标准PQI分开单独进行指示。
示例性地，在非标准PQI中增加字段“PqiIndex”，用于表示非标准PQI的索引。
Figure PCTCN2022079105-appb-000001
Figure PCTCN2022079105-appb-000002
方法D，非标准PQI的索引是用包含该非标准PQI的SL QoS profile对应的SL RB配置的索引以及该非标准PQI在该SL RB配置中的索引来表示。
可以在各个SL RB配置中携带非标准PQI在该SL RB配置中的索引。一种方式是在非标准PQI中包含该非标准PQI在该SL RB配置中的索引。其中，非标准PQI的索引的值可以与标准PQI的值重合，也可以与所有标准PQI的值都不重合。如果非标准PQI的索引与某个标准PQI的值重合，则在上述配置信息中还需要指示是标准PQI还是非标准PQI，或者是将标准PQI和非标准PQI分开单独进行指示。
基于上述方案，在配置信息中携带各个SL DRX配置分别对应的PQI的索引，而不是携带PQI，可以减少信令开销及存储开销。
实施例七
图18(a)为本申请实施例提供的一种确定DRX配置的确定方法示意图，包括以下步骤：
步骤1801a，终端获取配置信息，该配置信息包括至少一个SL DRX配置分别对应的标准PQI。
步骤1802a，终端根据第一非标准PQI对应的指示信息，确定与第一非标准PQI对应的第一标准PQI。
其中，该指示信息用于指示与第一非标准PQI对应相同SL DRX配置的第一标准PQI。也即，该指示信息指示了第一标准PQI，该第一标准PQI与第一非标准PQI对应相同的SL DRX配置。
步骤1803a，终端根据第一标准PQI，以及至少一个SL DRX配置分别对应的标准PQI，确定第一标准PQI对应的第一SL DRX配置，该第一SL DRX配置也是第一非标准PQI对应的SL DRX配置。
基于上述方案，通过指示信息，将对应相同SL DRX配置的标准PQI和非标准PQI进行关联，从而可以确定非标准PQI对应的SL DRX配置。
该实施例中，非标准PQI对应的SL DRX配置与某一个标准PQI对应的SL DRX配置相同，则可以为该非标准PQI对应一个指示信息，在具体实现中，可以在非标准PQI中增加该指示信息。该指示信息用于指示与该非标准PQI使用相同SL DRX配置的标准PQI。从而不需要通过配置信息来配置非标准PQI与SL DRX配置之间的映射关系，可以减少信令开销和存储开销。
示例性地，sl-Non-StandardizedPQI-r16表示非标准PQI包含的信息，在 sl-Non-StandardizedPQI-r16中增加SameDRXstandardizedPQI，用于指示一个标准PQI，该标准PQI对应的SL DRX配置与该非标准PQI对应的SL DRX配置相同。
Figure PCTCN2022079105-appb-000003
基于上述方案，非标准PQI对应的SL DRX配置与某一个标准PQI对应的SL DRX相同，替代了使用额外的配置信息来配置非标准PQI与SL DRX配置之间的映射关系，从而减少信令开销和存储开销。
实施例八
非标准PQI对应默认(default)SL DRX配置，或者公共(common)SL DRX配置。default SL DRX配置或common SL DRX配置可以是基站发送的，或者是预配置的。该default SL DRX配置或common SL DRX配置可以是专用于非标准PQI的，也可以不是专用的。例如，非标准PQI对应的default SL DRX配置可以与单播、广播或组播的default SL DRX配置或common SL DRX配置相同，或者非标准PQI对应的common SL DRX配置可以与单播、广播或组播的default SL DRX配置或common SL DRX配置相同。
基于上述方案，非标准PQI对应同一个default SL DRX配置或者common SL DRX配置，从而减少信令开销和存储开销。
实施例九
图18(b)为本申请实施例提供的一种确定DRX配置的确定方法示意图，包括以下步骤：
步骤1801b，终端获取配置信息，该配置信息包括至少一个SL DRX配置分别对应的SL RB配置的索引，其中，每个SL RB配置对应一个或多个SL QoS profile，或者每个SL RB配置对应一个或多个PQI。
该配置信息可以是预配置的，基站配置的，核心网网元配置的或协议预定义的。
例如，在上述配置信息指示了如下对应关系：
DRX配置1，对应SL RB配置1的索引，SL RB配置2的索引；
DRX配置2，对应SL RB配置3的索引，SL RB配置4的索引，SL RB配置5的索引，SL RB配置6的索引；
DRX配置3，对应SL RB配置7的索引。
作为一种实现方法，该配置信息还指示了该至少一个SL DRX配置，也即该配置信息一方面配置了至少一个SL DRX配置，另一方面还配置了该至少一个SL DRX配置中每个 SL DRX配置对应的PQI的索引。
作为另一种实现方法，该配置信息没有配置该至少一个SL DRX配置，而是通过另一个配置信息单独配置该至少一个SL DRX配置。也即通过一个配置信息配置至少一个SL DRX配置，通过另一个配置信息配置该至少一个SL DRX配置中每个SL DRX配置对应的PQI的索引。
其中，SL RB配置可以是预配置，基站配置，核心网网元配置或协议预定义的。SL RB配置可以是通过上述步骤1801的配置信息进行配置，也可以是通过其它配置信息单独配置的。
步骤1802b，终端根据第一SL QoS profile，以及至少一个SL DRX配置分别对应的SL RB配置的索引，确定第一SL QoS profile对应的第一SL DRX配置；或者终端根据第一PQI，以及至少一个SL DRX配置分别对应的SL RB配置的索引，确定第一PQI对应的第一SL DRX配置。
基于上述方案，终端可以确定每个SL QoS profile对应的SL DRX配置。比如，针对终端或终端的业务对应的第一SL QoS profile，终端先确定该第一SL QoS profile对应的第一SL RB配置，然后确定该第一SL RB配置的索引，然后根据第一SL RB配置的索引，以及至少一个SL DRX配置分别对应的SL RB配置的索引，可以确定第一SL RB配置的索引对应的SL DRX配置，该SL DRX配置即为第一SL QoS profile对应的第一SL DRX配置。再比如，针对终端或终端的业务对应的第一PQI，终端先确定该第一PQI对应的第一SL RB配置，然后确定该第一SL RB配置的索引，然后根据第一SL RB配置的索引，以及至少一个SL DRX配置分别对应的SL RB配置的索引，可以确定第一SL RB配置的索引对应的SL DRX配置，该SL DRX配置即为第一PQI对应的第一SL DRX配置。
或者，终端也可以根据至少一个SL DRX配置分别对应的SL RB配置的索引，以及第一SL RB配置的索引，确定第一SL RB配置的索引对应的第一SL DRX配置。
基于上述方案，终端可以确定该第一SL RB配置的索引，然后根据第一SL RB配置的索引以及至少一个SL DRX配置分别对应的SL RB配置的索引，可以确定第一SL RB配置的索引对应的第一SL DRX配置。
其中，SL RB配置的索引可以用该SL RB配置在所有SL RB配置中的排序来表示。或者，SL RB配置的索引可以是该SL RB配置中包含的SL RB配置的索引。
下面结合一个示例来说明。
SL RB配置1对应SL QoS profile 1，SL QoS profile 2；
SL RB配置2对应SL QoS profile 3，SL QoS profile 4；
SL RB配置3对应SL QoS profile 5；
SL RB配置4对应SL QoS profile 6，SL QoS profile 7。
比如，当上述配置信息指示了如下对应关系：
DRX配置1，对应1，2；
DRX配置2，对应3，4。
其中，1，2，3，4分别为SL RB配置1，SL RB配置2，SL RB配置3，SL RB配置4的索引，则该配置信息用于指示：DRX配置1对应SL RB配置1和SL RB配置2，因此DRX配置1对应SL QoS profile 1，SL QoS profile 2，SL QoS profile 3和SL QoS profile 4， DRX配置2对应SL RB配置3和SL RB配置4，因此DRX配置2对应SL QoS profile 5，SL QoS profile 6和SL QoS profile 7。
作为一种实现方法，如果SL DRX配置与SL RB配置是按照SL DRX配置在SL DRX配置列表中的顺序和SL RB配置在SL RB配置列表中的顺序一一对应，也即，SL RB列表中的SL RB配置按顺序依次为SL RB配置1、SL RB配置2、SL RB配置3，以此类推。SL DRX配置列表中的SL DRX配置按顺序依次为SL DRX配置1、SL DRX配置2、SL DRX配置3，以此类推。则SL DRX配置1对应SL RB配置1，SL DRX配置2对应SL RB配置2，以此类推，则不需要通过上述配置信息来配置各个SL DRX配置对应的SL RB配置。以上述示例为例，比如终端被配置了上述SL RB配置与SL QoS profile的对应关系，以及被配置了DRX配置1和DRX配置2，则终端可以确定DRX配置1对应SL QoS profile 1和SL QoS profile 2，DRX配置2对应SL QoS profile 3和SL QoS profile 4。
上述实施例中，由于对应SL DRX配置的SL QoS profile/PQI为一个或多个SL RB配置对应的SL QoS profile/PQI，因此，一种实现方式是若需要配置一个SL QoS profile/PQI对应的SL DRX配置，则需要满足有对应该SL QoS profile/PQI的SL RB配置。
另一种实现方式是若一个SL QoS profile/PQI没有对应的SL RB配置，则该SL QoS profile/PQI对应默认(default)SL DRX配置，或者公共(common)SL DRX配置。例如，该default SL DRX配置或common SL DRX配置为单播、广播或组播的default SL DRX配置或common SL DRX配置。
另一种实现方式是每个SL DRX配置对应的SL QoS profile/PQI可以用上述实施例中的索引表示，或者用SL QoS profile/PQI表示。如果SL DRX配置对应的SL QoS profile/PQI是SL RB配置中的SL QoS profile/PQI，则用上述实施例中的索引表示。如果SL DRX配置对应的SL QoS profile/PQI不是任何一个SL RB配置中的SL QoS profile/PQI，则用SL QoS profile/PQI表示。
基于上述方案，在配置信息中携带各个SL DRX配置分别对应的SL RB配置的索引，而不是携带SL QoS profile，可以减少信令开销及存储开销。
作为另一种实现方法，当SL DRX配置与SL RB配置之间是一一对应关系，且该对应关系是预配置在终端上的，则可以不需要执行上述步骤1801b。该情形下，终端可以根据第一SL QoS profile或第一PQI，确定相应的第一SL RB配置，然后再确定第一SL RB配置对应的第一SL DRX配置，该第一SL DRX配置即为第一SL QoS profile对应的SL DRX配置或第一PQI对应的SL DRX配置。
实施例十
该方案是基于SL QoS profile的粒度，为终端配置SL DRX配置。
本申请实施例一提供的一种SL DRX配置的确定方法示意图，包括以下步骤：
终端获取配置信息，该配置信息指示(或者包括)至少一个SL QoS profile分别对应的SL DRX配置。或者又可以称为，该配置信息指示(或者包括)至少一个SL QoS profile与SL DRX配置的对应关系。
该配置信息可以是预配置的，基站配置的，核心网网元配置的或协议预定义的。
例如，在上述配置信息指示了如下对应关系：
SL QoS profile 1，对应的SL DRX配置1；
SL QoS profile 2，对应的SL DRX配置2；
SL QoS profile 3，对应的SL DRX配置3。
作为一种实现方法，该配置信息还指示了该至少一个SL QoS profile，也即该配置信息一方面配置了至少一个SL QoS profile，另一方面还配置了该至少一个SL QoS profile分别对应的SL DRX配置。
例如，配置信息包含一个或多个SL-QoS-Profile，其中，每个SL-QoS-Profile包含PQI、GFBR、MFBR、Range中的一个或多个，并包含SL DRX配置，SL-QoS-Profile示意如下。
Figure PCTCN2022079105-appb-000004
作为一种实现方法，SL DRX配置为枚举类型(ENUMERATED)。例如，SL DRX配置包括sl-DRX-InactivityTimer的情况下，sl-DRX-InactivityTimer为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}，即，sl-DRX-InactivityTimer的取值为括号中的一个。其中，括号中的值为1ms的整数倍，ms0表示0，ms1表示1ms，ms2表示2ms，以此类推。spare为闲置的取值，也可以理解为不用的取值。
又如，SL DRX配置包括SL DRX cycle的情况下，SL DRX cycle为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}，即，SL DRX cycle的取值为括号中的一个。其中，括号中的值的单位为ms，ms10表示10ms，ms20表示20ms，以此类推。spare为闲置的取值，也可以理解为不用的取值。
作为一种实现方法，SL DRX配置为选择类型(CHOICE)。例如，SL DRX配置包括sl-DRX-OnDurationTimer的情况下，sl-DRX-OnDurationTimer为CHOICE{subMilliSeconds,milliSeconds}。其中，subMilliSeconds为整数类型(INTEGER)，取值范围为1至31，单位为1/32ms，即1表示1/32ms，2表示2/32ms，以此类推。milliSeconds为枚举类型，取值范围例如为{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}，单位为ms，ms1表示1ms，ms2表示2ms，以此类推。spare为闲置的取值，也可以理解为不用的取值。
基于上述方案，在配置信息中携带至少一个SL QoS profile分别对应的SL DRX配置，相比于在每个SL DRX配置中携带SL QoS profile，可以减少信令开销及存储开销。
在不冲突的情况下，该实施例十的方案可以和其他实施例组合使用。
实施例十一
该方案是基于SL QoS profile的粒度，为终端配置SL DRX配置。
本申请实施例十一提供的一种SL DRX配置的确定方法示意图，包括以下步骤：终端获取配置信息，该配置信息包括至少一个SL QoS profile分别对应的SL DRX配置的索引，或者又可以称为该配置信息包括至少一个SL QoS profile与SL DRX配置索引的对应关系。
该配置信息可以是预配置的，基站配置的，核心网网元配置的或协议预定义的。
例如，在上述配置信息指示了如下对应关系：
SL QoS profile 1，对应的SL DRX配置的索引为3；
SL QoS profile 2，对应的SL DRX配置的索引为1；
SL QoS profile 3，对应的SL DRX配置的索引为3。
作为一种实现方法，该配置信息还指示了该至少一个SL QoS profile，也即该配置信息一方面配置了至少一个SL QoS profile，另一方面还配置了该至少一个SL QoS profile分别对应的SL DRX配置的索引。
作为一种实现方法，该配置信息还指示了该至少一个SL DRX配置，也即该配置信息一方面配置了至少一个SL DRX配置，另一方面还配置了至少一个SL QoS profile分别对应的SL DRX配置的索引。
作为另一种实现方法，该配置信息没有配置该至少一个SL DRX配置，而是通过另一个配置信息单独配置该至少一个SL DRX配置。也即通过一个配置信息配置至少一个SL DRX配置，通过另一个配置信息配置至少一个SL QoS profile分别对应的SL DRX配置的索引。
步骤1X02，终端根据第一SL QoS profile，以及至少一个SL QoS profile分别对应的SL DRX配置的索引，确定第一SL QoS profile对应的第一SL DRX配置。
具体的，终端根据第一SL QoS profile，以及至少一个SL QoS profile分别对应的SL DRX配置的索引，确定第一SL QoS profile对应的第一SL DRX配置索引，进而终端确定第一SL QoS profile对应的第一SL DRX配置为索引是第一SL DRX配置索引的SL DRX配置。
基于上述方案，终端可以确定终端或终端的业务对应的SL DRX配置。比如，终端先确定终端或终端的业务对应的第一SL QoS profile，然后根据第一SL QoS profile确定第一SL QoS profile对应的SL DRX配置。
作为一种实现方法，SL DRX配置的索引是用该SL DRX配置在SL DRX配置列表中的排序来表示。例如，SL DRX配置列表中的SL DRX配置按顺序依次为SL DRX配置1、SL DRX配置2、SL DRX配置3，……，SL DRX配置N。则SL DRX配置的索引依次为1，2，3，……，N。比如，在上述配置信息指示了如下对应关系：
SL QoS profile 1，对应3；
SL QoS profile 2，对应1；
SL QoS profile 3，对应3。
其中，1，2，3为各个SL DRX配置的索引。
作为一种实现方法，该配置信息还指示了该至少一个SL QoS profile，也即该配置信息一方面配置了至少一个SL QoS profile，另一方面还配置了该至少一个SL QoS profile分别对应的SL DRX配置的索引。
例如，配置信息包含一个或多个SL-QoS-Profile，其中，每个SL-QoS-Profile包含PQI、GFBR、MFBR、Range中的一个或多个，并包含SL DRX配置的索引，SL-QoS-Profile示意如下。
Figure PCTCN2022079105-appb-000005
基于上述方案，在配置信息中携带至少一个SL QoS profile分别对应的SL DRX配置的索引，相比于在每个SL DRX配置中携带SL QoS profile，可以减少信令开销及存储开销。
在不冲突的情况下，该实施例十一的方案可以和其他实施例组合使用。需要说明的是，在一种实现方法中，还可以通过配置信息配置标准PQI与SL DRX配置的对应关系。若sidelink单播通信对应的PQI是标准PQI，则发送侧的终端和接收侧的终端均根据该配置信息确定出相同的SL DRX配置。若sidelink单播通信对应的PQI是非标准PQI，则可以由一侧终端确定SL DRX配置，并且将用于指示该SL DRX配置的指示信息发送给对侧终端。若sidelink单播通信对应的PQI包括标准PQI和非标准PQI，则可以由一侧终端确定SL DRX配置，并且将用于指示该SL DRX配置的指示信息发送给对侧终端。
在一种实现方法中，还可以通过配置信息配置SL QoS profile/PQI与SL DRX参数的取值范围的对应关系。例如SL DRX参数的取值范围例如包括：sl-DRX-OnDurationTimer的取值范围为2ms至10ms，sl-DRX-InactivityTimer的取值范围为0ms至8ms。一侧终端根据sidelink单播通信对应的QoS profile/PQI，确定SL DRX配置，其中，确定的该SL DRX配置包含的SL DRX参数的取值在该QoS profile/PQI对应的SL DRX参数的取值范围内。该终端将用于指示该SL DRX配置的指示信息发送给对侧终端。在该SL DRX配置信息中，QoS profile/PQI可以用上述实施例五至实施例九中描述的QoS profile/PQI的索引来表示。
需要说明的是，上述实施例一至四，与上述实施例五至九的关系是：通过上述实施例五至九，可以实现为终端配置SL DRX配置与QoS profile/PQI之间的对应关系，后续可以使用对应关系。比如，针对一个destination Layer-2 ID，终端上仅有对应该destination Layer-2 ID的一个业务，该业务对应一个QoS profile/PQI，则终端可以根据上述该QoS profile/PQI以及上述对应关系，确定该QoS profile/PQI对应的SL DRX配置，后续终端使用该SL DRX配置。再比如，针对一个destination Layer-2 ID，终端上有对应该destination Layer-2 ID的多 个业务，每个业务对应一个QoS profile/PQI，则终端可以确定该destination Layer-2 ID对应的多个QoS profile/PQI，从而终端根据该多个QoS profile/PQI以及上述对应关系，确定至少两个SL DRX配置，进而终端可以再通过上述实施例一至四中的任一方法确定该至少两个SL DRX配置中使用的SL DRX配置。
作为一种实现方法，如果有多个PQI关联一个destination Layer-2 ID，可以考虑两种方式。方式一中，首先从该destination Layer-2 ID关联的多个PQI中选择一个目标PQI，例如，选择优先级最小和/或PDB最小的PQI，然后选择目标PQI对应的SL DRX配置，作为使用的SL DRX配置，也可以称为将目标PQI对应的SL DRX配置应用到该destination Layer-2 ID。方式二中，首先根据该destination Layer-2 ID关联的多个PQI确定该多个PQI对应的多个SL DRX配置，然后从该多个SL DRX配置中选择一个目标SLDRX配置，例如选择的目标SLDRX配置是多个SL DRX配置中SL DRX周期最小的SL DRX配置。
可以理解的是，为了实现上述实施例中功能，基站和终端包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及方法步骤，本申请能够以硬件或硬件和计算机软件相结合的形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用场景和设计约束条件。
图19和图20为本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可以用于实现上述方法实施例中终端或基站的功能，因此也能实现上述方法实施例所具备的有益效果。在本申请的实施例中，该通信装置可以是如图1所示的终端120a至120j中的一个，也可以是如图1所示的基站110a或110b，还可以是应用于终端或基站的模块(如芯片)。
如图19所示，通信装置1900包括处理单元1910和收发单元920。通信装置1900用于实现上述实施例一至实施例九中终端的功能。
在第一个实施例中：处理单元1910，用于确定终端的业务对应的至少两个PQI或旁链路QoS模板；确定该至少两个PQI或旁链路QoS模板对应的至少两个旁链路DRX配置，其中，每个旁链路DRX配置指示了一个或多个旁链路DRX参数；根据该至少两个旁链路DRX配置，确定使用的旁链路DRX配置。
在一种可能的实现方法中，该使用的旁链路DRX配置为第一旁链路DRX配置，该第一旁链路DRX配置为该至少两个旁链路DRX配置中的一个。
在一种可能的实现方法中，该第一旁链路DRX配置的第一参数的取值，是该至少两个旁链路DRX配置的第一参数的取值中的最小值或最大值；其中，该第一参数是以下参数中的任意一种：sl-DRX-OnDurationTimer的取值、sl-DRX-InactivityTimer的取值、sl-DRX-HARQ-RTT-Timer的取值、sl-DRX-RetransmissionTimer的取值、SL DRX cycle的取值、sl-DRX-startOffset的取值、sl-DRX-slotOffset的取值。
在一种可能的实现方法中，在该至少两个旁链路DRX配置中有多个旁链路DRX配置的第一参数的取值为最小值或最大值的情况下，当该多个旁链路DRX配置中仅有一个旁链 路DRX配置的第二参数的取值最小或最大，则处理单元1910，用于确定该旁链路DRX配置为该第一旁链路DRX配置；或者，当该多个旁链路DRX配置中有多个旁链路DRX配置的第二参数的取值最小或最大，则处理单元1910，用于确定该多个旁链路DRX配置中的一个旁链路DRX配置为该第一旁链路DRX配置。
在一种可能的实现方法中，在该至少两个旁链路DRX配置中有多个旁链路DRX配置的第一参数的取值为最小值或最大值的情况下，处理单元1910，用于选择该多个旁链路DRX配置中在旁链路DRX配置列表中排序最靠前或最靠后的旁链路DRX配置，作为该第一旁链路DRX配置。
在一种可能的实现方法中，在该至少两个旁链路DRX配置中有多个旁链路DRX配置的第一参数的取值为最小值或最大值的情况下，处理单元1910，用于选择该多个旁链路DRX配置中对应的PQI的取值最小或最大的旁链路DRX配置，作为该第一旁链路DRX配置。
在一种可能的实现方法中，在该至少两个旁链路DRX配置中有多个旁链路DRX配置的第一参数的取值为最小值或最大值的情况下，处理单元1910，用于选择该多个旁链路DRX配置中对应的PQI的索引最小或最大的旁链路DRX配置，作为该第一旁链路DRX配置；或者，选择该多个旁链路DRX配置中对应的旁链路QoS模板的索引最小或最大的旁链路DRX配置，作为该第一旁链路DRX配置。
在一种可能的实现方法中，根据以下至少一种参数，确定该第一旁链路DRX配置：至少两个旁链路DRX配置分别在旁链路DRX配置列表中的排序；至少两个旁链路DRX配置分别对应的PQI的取值；至少两个旁链路DRX配置分别对应的旁链路QoS模板的索引；或者，至少两个旁链路DRX配置分别对应的PQI的索引。
在一种可能的实现方法中，该第一旁链路DRX配置是根据该至少两个旁链路DRX配置生成的，该第一旁链路DRX配置中的参数的取值来自该至少两个旁链路DRX配置中的一个或多个旁链路DRX配置。
在一种可能的实现方法中，该第一旁链路DRX配置包含的第一参数的取值，是该至少两个旁链路DRX配置分别包含的第一参数的取值中的最小值或最大值。
在一种可能的实现方法中，该使用的旁链路DRX配置，为该至少两个旁链路DRX配置。
在一种可能的实现方法中，该至少两个旁链路DRX配置中的每个旁链路DRX配置包括以下一个或多个定时器的时长：sl-DRX-onDurationTimer、sl-DRX-inactivityTimer、sl-DRX-HARQ-RTT-Timer或sl-DRX-RetransmissionTimer；该终端对应的旁链路激活时间包括以下一个运行时间或多个运行时间的并集：每个旁链路DRX配置对应的sl-DRX-onDurationTimer的运行时间、每个旁链路DRX配置对应的sl-DRX-inactivityTimer的运行时间或每个旁链路DRX配置对应的sl-DRX-RetransmissionTimer的运行时间。
在一种可能的实现方法中，该至少两个旁链路DRX配置中的每个旁链路DRX配置包括以下一个或多个定时器的时长：sl-DRX-onDurationTimer、sl-DRX-inactivityTimer、sl-DRX-HARQ-RTT-Timer或sl-DRX-RetransmissionTimer；该终端对应的旁链路激活时间包括以下一个运行时间或多个运行时间的并集：每个旁链路DRX配置对应的sl-DRX-onDurationTimer的运行时间、第二旁链路DRX配置对应的第一sl-DRX-inactivityTimer的运行时间或第三旁链路DRX配置对应的第一 sl-DRX-RetransmissionTimer的运行时间；其中，该第二旁链路DRX配置和该第三旁链路DRX配置分别是该至少两个旁链路DRX配置中的一个。
在一种可能的实现方法中，该第一sl-DRX-inactivityTimer的取值是该至少两个旁链路DRX配置分别对应的sl-DRX-inactivityTimer的取值中的最小值或最大值；和/或，该第一sl-DRX-RetransmissionTimer的取值是该至少两个旁链路DRX配置分别对应的sl-DRX-RetransmissionTimer的取值中的最小值或最大值。
在第二个实施例中，处理单元1910，用于获取配置信息，该配置信息包括至少一个旁链路DRX配置分别对应的PQI的索引；根据第一PQI的索引，以及该至少一个旁链路DRX配置分别对应的PQI的索引，确定该第一PQI的索引对应的第一旁链路DRX配置。
在一种可能的实现方法中，处理单元1910，用于确定终端对应的第一PQI；根据该第一PQI，确定该第一PQI的索引。
在一种可能的实现方法中，在该PQI是标准PQI的情况下，该PQI的索引是标准PQI的取值；或者，该PQI的索引是包含该标准PQI的旁链路QoS模板的索引。
在一种可能的实现方法中，在该PQI是标准PQI的情况下，处理单元1910，用于获取至少一个非标准PQI；其中，每个非标准PQI对应一个指示信息，该指示信息用于指示与该非标准PQI对应相同旁链路DRX配置的标准PQI；或者，每个非标准PQI对应一个默认旁链路DRX配置；或者，每个非标准PQI对应一个公共旁链路DRX配置。
在一种可能的实现方法中，在该PQI是非标准PQI的情况下，该PQI的索引是包含该非标准PQI的旁链路QoS模板的索引；或者，该PQI的索引是旁链路RB配置中包含的该非标准PQI的索引；或者，该PQI的索引是使用包含该非标准PQI的旁链路QoS模板对应的旁链路RB配置的索引以及该非标准PQI在该旁链路RB配置中的索引来表示。
在第三个实施例中，处理单元1910，用于获取配置信息，该配置信息包括至少一个旁链路DRX配置分别对应的旁链路QoS模板的索引；根据第一旁链路QoS模板的索引，以及该至少一个旁链路DRX配置分别对应的旁链路QoS模板的索引，确定该第一旁链路QoS模板的索引对应的第一旁链路DRX配置。
在一种可能的实现方法中，处理单元1910，用于确定终端对应的第一旁链路QoS模板；根据该第一旁链路QoS模板，确定该第一旁链路QoS模板的索引。
在一种可能的实现方法中，该旁链路QoS模板的索引是使用该旁链路QoS模板在旁链路RB配置列表对应的旁链路QoS模板中的排序来表示；或者，该旁链路QoS模板的索引是使用该旁链路QoS模板对应的旁链路RB配置的索引，以及该旁链路QoS模板在该旁链路RB配置对应的旁链路QoS模板中的排序来表示。
在第四个实施例中，处理单元1910，用于获取配置信息，该配置信息包括至少一个旁链路DRX配置分别对应的旁链路RB配置的索引，每个旁链路RB配置对应至少一个PQI；根据第一PQI，以及该至少一个旁链路DRX配置分别对应的旁链路RB配置的索引，确定该第一PQI对应的第一旁链路DRX配置。
在一种可能的实现方法中，处理单元1910，用于确定该第一PQI对应的第一旁链路RB配置的索引；根据该第一旁链路RB配置的索引，以及该至少一个旁链路DRX配置分别对应的旁链路RB配置的索引，确定该第一旁链路RB配置的索引对应的该第一旁链路DRX配置。
在一种可能的实现方法中，该第一旁链路RB配置的索引是使用该第一旁链路RB配置在旁链路RB配置列表中的排序来表示。
在第五个实施例中，处理单元1910，用于获取配置信息，该配置信息包括至少一个旁链路DRX配置分别对应的旁链路RB配置的索引，每个旁链路RB配置对应至少一个旁链路QoS模板；根据第一旁链路QoS模板以及该至少一个旁链路DRX配置分别对应的旁链路RB配置的索引，确定该第一旁链路QoS模板对应的第一旁链路DRX配置。
在一种可能的实现方法中，处理单元1910，用于确定该第一旁链路QoS模板对应的第一旁链路RB配置的索引；根据该至少一个旁链路DRX配置分别对应的旁链路RB配置的索引，以及该第一旁链路RB配置的索引，确定该第一旁链路RB配置的索引对应的该第一旁链路DRX配置。
在一种可能的实现方法中，该第一旁链路RB配置的索引是使用该第一旁链路RB配置在旁链路RB配置列表中的排序来表示。
有关上述处理单元1910和收发单元1920更详细的描述可以直接参考实施例一至实施例九中相关描述直接得到，这里不加赘述。
如图20所示，通信装置2000包括处理器2010和接口电路2020。处理器2010和接口电路2020之间相互耦合。可以理解的是，接口电路2020可以为收发器或输入输出接口。可选的，通信装置2000还可以包括存储器2030，用于存储处理器2010执行的指令或存储处理器2010运行指令所需要的输入数据或存储处理器2010运行指令后产生的数据。
当通信装置2000用于实现实施例一至实施例十一时，处理器2010用于实现上述处理单元1910的功能，接口电路2020用于实现上述收发单元1920的功能。
当上述通信装置为应用于终端的芯片时，该终端芯片实现上述实施例一至实施例十一中终端的功能。以及其他实施例中终端的功能。该终端芯片从终端中的其它模块(如射频模块或天线)接收信息，该信息是基站发送给终端的；或者，该终端芯片向终端中的其它模块(如射频模块或天线)发送信息，该信息是终端发送给基站的。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其它通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法步骤可以通过硬件的方式来实现，也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器、闪存、只读存储器、可编程只读存储器、可擦除可编程只读存储器、电可擦除可编程只读存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于基站或终端中。当然，处理器和存储介质也可以作为分立组件存在于基站或终端中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。 当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、基站、用户设备或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序或指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字视频光盘；还可以是半导体介质，例如，固态硬盘。该计算机可读存储介质可以是易失性或非易失性存储介质，或可包括易失性和非易失性两种类型的存储介质。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式中，字符“/”，表示前后关联对象是一种“相除”的关系。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。

Claims (17)

  1. 一种旁链路非连续接收DRX配置的确定方法，其特征在于，包括：
    确定终端的业务对应的至少两个PQI或旁链路服务质量QoS模板；
    确定所述至少两个PQI或旁链路QoS模板对应的至少两个旁链路DRX配置，其中，每个旁链路DRX配置指示了一个或多个旁链路DRX参数；
    根据所述至少两个旁链路DRX配置，确定使用的旁链路DRX配置。
  2. 如权利要求1所述的方法，其特征在于，所述使用的旁链路DRX配置为第一旁链路DRX配置，所述第一旁链路DRX配置为所述至少两个旁链路DRX配置中的一个。
  3. 如权利要求2所述的方法，其特征在于，所述第一旁链路DRX配置的第一参数的取值，是所述至少两个旁链路DRX配置的第一参数的取值中的最小值或最大值；
    其中，所述第一参数是以下参数中的任意一种：旁链路DRX持续时间定时器sl-DRX-OnDurationTimer的取值、旁链路DRX非激活定时器sl-DRX-InactivityTimer的取值、旁链路DRX混合自动重传请求环回时延定时器sl-DRX-HARQ-RTT-Timer的取值、旁链路DRX重传定时器sl-DRX-RetransmissionTimer的取值、旁链路DRX周期SL DRX cycle的取值、旁链路DRX起始偏移sl-DRX-startOffset的取值、旁链路DRX时隙偏移sl-DRX-slotOffset的取值。
  4. 如权利要求3所述的方法，其特征在于，在所述至少两个旁链路DRX配置中有多个旁链路DRX配置的第一参数的取值为最小值或最大值的情况下，
    当所述多个旁链路DRX配置中仅有一个旁链路DRX配置的第二参数的取值最小或最大，则确定所述旁链路DRX配置为所述第一旁链路DRX配置；或者，
    当所述多个旁链路DRX配置中有多个旁链路DRX配置的第二参数的取值最小或最大，则确定所述多个旁链路DRX配置中的一个旁链路DRX配置为所述第一旁链路DRX配置。
  5. 如权利要求3所述的方法，其特征在于，在所述至少两个旁链路DRX配置中有多个旁链路DRX配置的第一参数的取值为最小值或最大值的情况下，
    选择所述多个旁链路DRX配置中在旁链路DRX配置列表中排序最靠前或最靠后的旁链路DRX配置，作为所述第一旁链路DRX配置。
  6. 如权利要求3所述的方法，其特征在于，在所述至少两个旁链路DRX配置中有多个旁链路DRX配置的第一参数的取值为最小值或最大值的情况下，
    选择所述多个旁链路DRX配置中对应的PQI的取值最小或最大的旁链路DRX配置，作为所述第一旁链路DRX配置。
  7. 如权利要求3所述的方法，其特征在于，在所述至少两个旁链路DRX配置中有多个旁链路DRX配置的第一参数的取值为最小值或最大值的情况下，
    选择所述多个旁链路DRX配置中对应的PQI的索引最小或最大的旁链路DRX配置，作为所述第一旁链路DRX配置；或者，
    选择所述多个旁链路DRX配置中对应的旁链路QoS模板的索引最小或最大的旁链路DRX配置，作为所述第一旁链路DRX配置。
  8. 如权利要求2所述的方法，其特征在于，根据以下至少一种参数，确定所述第一旁链路DRX配置：
    所述至少两个旁链路DRX配置分别在旁链路DRX配置列表中的排序；
    所述至少两个旁链路DRX配置分别对应的PQI的取值；
    所述至少两个旁链路DRX配置分别对应的旁链路QoS模板的索引；或者，
    所述至少两个旁链路DRX配置分别对应的PQI的索引。
  9. 如权利要求1所述的方法，其特征在于，
    所述第一旁链路DRX配置是根据所述至少两个旁链路DRX配置生成的，所述第一旁链路DRX配置中的参数的取值来自所述至少两个旁链路DRX配置中的一个或多个旁链路DRX配置。
  10. 如权利要求9所述的方法，其特征在于，所述第一旁链路DRX配置包含的第一参数的取值，是所述至少两个旁链路DRX配置分别包含的第一参数的取值中的最小值或最大值。
  11. 如权利要求1所述的方法，其特征在于，
    所述使用的旁链路DRX配置，为所述至少两个旁链路DRX配置。
  12. 如权利要求11所述的方法，其特征在于，所述至少两个旁链路DRX配置中的每个旁链路DRX配置包括以下一个或多个定时器的时长：sl-DRX-onDurationTimer、sl-DRX-inactivityTimer、sl-DRX-HARQ-RTT-Timer或sl-DRX-RetransmissionTimer；
    所述终端对应的旁链路激活时间包括以下一个运行时间或多个运行时间的并集：每个旁链路DRX配置对应的sl-DRX-onDurationTimer的运行时间、每个旁链路DRX配置对应的sl-DRX-inactivityTimer的运行时间或每个旁链路DRX配置对应的sl-DRX-RetransmissionTimer的运行时间。
  13. 如权利要求11所述的方法，其特征在于，所述至少两个旁链路DRX配置中的每个旁链路DRX配置包括以下一个或多个定时器的时长：sl-DRX-onDurationTimer、sl-DRX-inactivityTimer、sl-DRX-HARQ-RTT-Timer或sl-DRX-RetransmissionTimer；
    所述终端对应的旁链路激活时间包括以下一个运行时间或多个运行时间的并集：每个旁链路DRX配置对应的sl-DRX-onDurationTimer的运行时间、第二旁链路DRX配置对应的第一sl-DRX-inactivityTimer的运行时间或第三旁链路DRX配置对应的第一sl-DRX-RetransmissionTimer的运行时间；
    其中，所述第二旁链路DRX配置和所述第三旁链路DRX配置分别是所述至少两个旁链路DRX配置中的一个。
  14. 如权利要求13所述的方法，其特征在于，
    所述第一sl-DRX-inactivityTimer的取值是所述至少两个旁链路DRX配置分别对应的sl-DRX-inactivityTimer的取值中的最小值或最大值；和/或，
    所述第一sl-DRX-RetransmissionTimer的取值是所述至少两个旁链路DRX配置分别对应的sl-DRX-RetransmissionTimer的取值中的最小值或最大值。
  15. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1至14中任一项所述的方法。
  16. 一种计算机程序产品，其特征在于，包括计算机程序，当所述计算机程序被处理器执行时，实现如权利要求1至14中任一项所述的方法。
  17. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序或指令，当所述计算机程序或指令被处理器执行时，实现如权利要求1至14中任一项所述的方法。
PCT/CN2022/079105 2021-03-09 2022-03-03 一种旁链路drx配置的确定方法及通信装置 WO2022188692A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
JP2023555156A JP2024510581A (ja) 2021-03-09 2022-03-03 サイドリンクｄｒｘ構成を決定する方法及び通信機器
CN202280020452.9A CN117413548A (zh) 2021-03-09 2022-03-03 一种旁链路drx配置的确定方法及通信装置
EP22766218.6A EP4297444A1 (en) 2021-03-09 2022-03-03 Method for determining sidelink drx configuration, and communication apparatus
BR112023018228A BR112023018228A2 (pt) 2021-03-09 2022-03-03 Método para determinar configuração de drx de enlace lateral e aparelho de comunicação
US18/463,015 US20230422344A1 (en) 2021-03-09 2023-09-07 Method for determining sidelink drx configuration and communication apparatus

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
CN202110252910.9 2021-03-09
CN202110252910 2021-03-09
CN202110351627 2021-03-31
CN202110351627.1 2021-03-31
CN202111116713.0 2021-09-23
CN202111116713.0A CN115052271A (zh) 2021-03-09 2021-09-23 一种旁链路drx配置的确定方法及通信装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/463,015 Continuation US20230422344A1 (en) 2021-03-09 2023-09-07 Method for determining sidelink drx configuration and communication apparatus

Publications (1)

Publication Number Publication Date
WO2022188692A1 true WO2022188692A1 (zh) 2022-09-15

Family

ID=83156302

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/079105 WO2022188692A1 (zh) 2021-03-09 2022-03-03 一种旁链路drx配置的确定方法及通信装置

Country Status (6)

Country Link
US (1) US20230422344A1 (zh)
EP (1) EP4297444A1 (zh)
JP (1) JP2024510581A (zh)
CN (2) CN115052271A (zh)
BR (1) BR112023018228A2 (zh)
WO (1) WO2022188692A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020168080A1 (en) * 2019-02-13 2020-08-20 Convida Wireless, Llc Apparatus, system, method, and computer-readable medium for connection-oriented vehicle-to-x (vtx) communication in 5g
CN111818659A (zh) * 2019-07-24 2020-10-23 维沃移动通信有限公司 sidelink信息发送方法、接收方法、终端和控制节点
WO2021029672A1 (ko) * 2019-08-12 2021-02-18 엘지전자 주식회사 무선통신시스템에서 사이드링크 drx에 관련된 ue의 동작 방법 및 장치

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020168080A1 (en) * 2019-02-13 2020-08-20 Convida Wireless, Llc Apparatus, system, method, and computer-readable medium for connection-oriented vehicle-to-x (vtx) communication in 5g
CN111818659A (zh) * 2019-07-24 2020-10-23 维沃移动通信有限公司 sidelink信息发送方法、接收方法、终端和控制节点
WO2021029672A1 (ko) * 2019-08-12 2021-02-18 엘지전자 주식회사 무선통신시스템에서 사이드링크 drx에 관련된 ue의 동작 방법 및 장치

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
INTERDIGITAL INC.: "Procedures for Handling the DRX Configuration", 3GPP DRAFT; R2-2100515, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20210101, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051973673 *
LG ELECTRONICS INC.: "Discussion on Sidelink DRX", 3GPP DRAFT; R2-2100637, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20210125 - 20210205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051973761 *
VIVO: "Left issues on SL DRX", 3GPP DRAFT; R2-2105352, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20210519 - 20210527, 11 May 2021 (2021-05-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052006987 *

Also Published As

Publication number Publication date
US20230422344A1 (en) 2023-12-28
BR112023018228A2 (pt) 2023-11-28
CN115052271A (zh) 2022-09-13
EP4297444A1 (en) 2023-12-27
JP2024510581A (ja) 2024-03-08
CN117413548A (zh) 2024-01-16

Similar Documents

Publication Publication Date Title
KR102224214B1 (ko) 사이드링크 데이터 복제를 위한 방법 및 디바이스
WO2021089020A1 (zh) 一种侧行链路信道状态信息报告的发送方法、装置及系统
EP3399684A1 (en) Data transmission method, user equipment, and base station
WO2016164084A1 (en) Resolving concurrent communications at a relay user equipment (ue)
WO2021180098A1 (zh) 无线通信方法和通信装置
KR20130019386A (ko) 하이브리드형 스테이션별 및 플로우별 업링크 할당들을 수행하기 위한 방법 및 장치
US20210297195A1 (en) Method and Device for Facilitating HARQ Transmission
WO2020259363A1 (zh) 用于无线通信的电子设备和方法、计算机可读存储介质
WO2018165987A1 (zh) 上行传输方法、装置、终端设备、接入网设备及系统
WO2020088224A1 (zh) 一种数据传输、确定发送功率的方法及设备
WO2021036910A1 (zh) 数据传输方法及装置
TW202029681A (zh) 用於harq傳輸之方法及通訊裝置
WO2020119753A1 (zh) 一种参数配置方法及装置
WO2022188692A1 (zh) 一种旁链路drx配置的确定方法及通信装置
CN114451017A (zh) 一种激活和释放非动态调度传输的方法及装置
WO2021228163A1 (zh) 确定资源的方法、装置及系统
US20210376968A1 (en) Feedback method and apparatus
WO2023134619A1 (zh) Harq-ack信息反馈方法和装置
WO2024027615A1 (zh) 一种通信方法，通信装置及通信系统
WO2022179496A1 (en) Terminal device, network node, and methods therein for drx configuration
WO2023207631A1 (zh) 一种通信方法及通信装置
WO2022247739A1 (zh) 一种数据传输方法和相关装置
WO2024067172A1 (zh) 一种数据传输的方法和装置
WO2023001075A1 (zh) 一种通信方法及装置
WO2021228182A1 (zh) Pdsch传输方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22766218

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023555156

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 202280020452.9

Country of ref document: CN

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112023018228

Country of ref document: BR

WWE Wipo information: entry into national phase

Ref document number: 2022766218

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022766218

Country of ref document: EP

Effective date: 20230919

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 11202306590W

Country of ref document: SG

ENP Entry into the national phase

Ref document number: 112023018228

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20230908