Method and apparatus for sidelink communications

Abstract

The present application relates to an apparatus and a method for sidelink (SL) communication. According to an embodiment of the present application, the method may include: acquiring, by a remote device, a plurality of SL DRX configurations for SL communication; determining, by the remote device, one or more SL DRX configurations from the plurality of SL DRX configurations for a medium access control (MAC) layer of the remote device; and transmitting SL data from the remote device based on an active time derived in each of the one or more SL DRX configurations when there is SL data associated with DRX at the remote device. The embodiment of the present application determines three kinds of granularity for SL DRX configurations for broadcast communication and groupcast communication, and proposes a method for determining SL DRX configurations for the three kinds of granularity.

Description

[Technical Field]

[0001] FIELD Embodiments of the present application generally relate to wireless communication technologies, and more particularly, to methods and apparatus for sidelink (SL) communication. [Background technology]

[0002] Discontinuous reception (DRX) refers to an operating mode for reducing the power consumption of a user equipment (UE). For example, in DRX mode, a UE typically alternates between an active state and a sleep state (or inactive state). When the UE is in the active state, it turns on its receiver to monitor and receive control information or data, and when the UE is in the sleep state, it turns off its receiver and stops receiving control information or data.

[0003] At the RAN#86 meeting, a sidelink enhancement work item was agreed upon. This sidelink enhancement work item introduced SL DRX and specified a mechanism to align SL DRX between UEs. At RAN2#113e, it was agreed that for groupcast and broadcast communications in sidelink, SL DRX configuration requires finer granularity compared to the cast type.

[0004] In consideration of this, it needs to be discussed how to determine the granularity of the SL DRX configuration for groupcast communication and broadcast communication, and how to determine the SL DRX configuration for different types of granularity. Summary of the Invention [Problem to be solved by the invention]

[0005] The embodiments of the present application provide a technical solution for SL communication, which proposes at least three types of granularity of SL DRX configuration for broadcast communication and groupcast communication, and also proposes how to determine the SL DRX configuration taking into account the three types of granularity. [Means for solving the problem]

[0006] According to some embodiments of the present application, a method for wireless communication may include: obtaining, by a remote device, a plurality of SL DRX configurations for SL communication; determining, by the remote device, one or more SL DRX configurations from the plurality of SL DRX configurations for a medium access control (MAC) layer of the remote device; and, if there is SL data associated with DRX at the remote device, transmitting SL data from the remote device based on an active time derived in each of the one or more SL DRX configurations.

[0007] In some embodiments of the present application, the multiple SL DRX configurations are configured based on a Layer 2 (L2) destination ID, and determining the one or more SL DRX configurations for the MAC layer includes, at the MAC layer, determining the one or more SL DRX configurations for the MAC layer to be the multiple SL DRX configurations.

[0008] In some embodiments of the present application, transmitting the SL data further includes selecting an L2 destination ID during a Logical Channel Prioritization (LCP) procedure, where the SL DRX configurations associated with the L2 destination IDs of the one or more SL DRX configurations are within an active time. In some embodiments, the first configuration information is predefined per resource pool, the first configuration information is preconfigured per resource pool for the first UE, or the first configuration information is configured per resource pool for the first UE via higher layer signaling.

[0009] In some embodiments of the present application, multiple SL DRX configurations are configured based on Quality of Service (QoS) related parameters.

[0010] In one embodiment of the present application, determining one or more SL DRX configurations for the MAC layer includes, for each logical channel, determining, in a radio resource control (RRC) layer of the remote device, at least one SL DRX configuration from a plurality of SL DRX configurations based on a mapping relationship between QoS-related parameters and sidelink radio bearers (SLRBs) and a mapping relationship between the SLRBs and the logical channels.

[0011] In another embodiment of the present application, determining one or more SL DRX configurations for the MAC layer further includes, for each logical channel, determining, at the RRC layer, one SL DRX configuration from at least one SL DRX configuration based on a predefined rule.

[0012] In yet another embodiment of the present application, transmitting SL data further includes selecting one or more logical channels during an LCP procedure, wherein an SL DRX configuration associated with each logical channel of the one or more logical channels is within an active time.

[0013] In yet another embodiment of the present application, determining one or more SL DRX configurations for the MAC layer includes, for each L2 destination ID, determining, at an RRC layer of the remote device, at least one SL DRX configuration from a plurality of SL DRX configurations based on a mapping relationship between a QoS-related parameter and the L2 destination ID.

[0014] In yet another embodiment of the present application, determining one or more SL DRX configurations for the MAC layer further includes, for each L2 destination ID, determining, at the RRC layer, one SL DRX configuration from the at least one SL DRX configuration based on a predefined rule.

[0015] In yet another embodiment of the present application, transmitting SL data further includes selecting an L2 destination ID during an LCP procedure, where an SL DRX configuration associated with the L2 destination ID of one or more SL DRX configurations is within an active time.

[0016] In yet another embodiment of the present application, determining one or more SL DRX configurations for the MAC layer includes indicating, in an RRC layer of the remote device, a mapping relationship between QoS-related parameters and the SL DRX configurations for the MAC layer of the remote device.

[0017] In yet another embodiment of the present application, transmitting SL data further includes obtaining one or more packets of SL data, each of the one or more packets being labeled with a QoS-related parameter, and selecting, during an LCP procedure, one or more logical channels each including a packet, the SL DRX configurations associated with the packets of the one or more SL DRX configurations being within an active time.

[0018] In some embodiments of the present application, multiple SL DRX configurations are configured based on SLRBs, radio link control (RLC) bearers, or logical channels (LCHs).

[0019] In one embodiment of the present application, determining one or more SL DRX configurations for the MAC layer includes determining, at the MAC layer, the one or more SL DRX configurations for the MAC layer to be multiple SL DRX configurations.

[0020] In another embodiment of the present application, transmitting the SL data further includes selecting one or more logical channels during an LCP procedure, wherein an SL DRX configuration associated with each logical channel of the one or more logical channels is within an active time.

[0021] In yet another embodiment of the present application, determining one or more SL DRX configurations for the MAC layer further includes, for each L2 destination ID, determining one SL DRX configuration from at least one SL DRX configuration associated with the corresponding L2 destination ID of the plurality of SL DRX configurations based on a predefined rule.

[0022] In yet another embodiment of the present application, transmitting SL data further includes selecting an L2 destination ID during an LCP procedure, where an SL DRX configuration associated with the L2 destination ID of one or more SL DRX configurations is within an active time.

[0023] According to some embodiments of the present application, a method for wireless communication may include obtaining, by a remote device, a plurality of SL DRX configurations for SL communication; determining, by the remote device, one or more SL DRX configurations from the plurality of SL DRX configurations for a MAC layer of the remote device; and receiving SL data based on an active time derived in each of the one or more SL DRX configurations.

[0024] In some embodiments of the present application, the multiple SL DRX configurations are configured based on an L2 destination ID, and determining the one or more SL DRX configurations for the MAC layer includes, at the MAC layer, determining the one or more SL DRX configurations for the MAC layer to be the multiple SL DRX configurations.

[0025] In some embodiments of the present application, receiving SL data further includes monitoring sidelink control information (SCI) when an SL DRX configuration associated with an L2 destination ID of one or more SL DRX configurations is within an active time.

[0026] In some embodiments of the present application, multiple SL DRX configurations are configured based on QoS-related parameters.

[0027] In one embodiment of the present application, determining one or more SL DRX configurations for the MAC layer includes, for each logical channel, determining, in an RRC layer of the remote device, at least one SL DRX configuration from a plurality of SL DRX configurations based on a mapping relationship between a QoS-related parameter and an SLRB and a mapping relationship between the SLRB and the logical channel.

[0028] In another embodiment of the present application, determining one or more SL DRX configurations for the MAC layer further includes, for each logical channel, determining, at the RRC layer, one SL DRX configuration from at least one SL DRX configuration based on a predefined rule.

[0029] In yet another embodiment of the present application, receiving SL data further includes monitoring the SCI when an SL DRX configuration associated with a logical channel of the one or more SL DRX configurations is within an active time.

[0030] In yet another embodiment of the present application, determining one or more SL DRX configurations for the MAC layer includes, for each L2 destination ID, determining, at an RRC layer of the remote device, at least one SL DRX configuration from a plurality of SL DRX configurations based on a mapping relationship between a QoS-related parameter and the L2 destination ID.

[0031] In yet another embodiment of the present application, determining one or more SL DRX configurations for the MAC layer further includes, for each L2 destination ID, determining, at the RRC layer, one SL DRX configuration from the at least one SL DRX configuration based on a predefined rule.

[0032] In yet another embodiment of the present application, receiving SL data further includes monitoring an SCI for an L2 destination ID when an SL DRX configuration associated with the L2 destination ID of one or more SL DRX configurations is within an active time.

[0033] In yet another embodiment of the present application, determining one or more SL DRX configurations for the MAC layer includes indicating, in an RRC layer of the remote device, a mapping relationship between QoS-related parameters and the SL DRX configurations for the MAC layer of the remote device.

[0034] In yet another embodiment of the present application, receiving SL data further includes monitoring sidelink control information (SCI) when an SL DRX configuration associated with a QoS-related parameter of the one or more SL DRX configurations is within an active time.

[0035] In some embodiments of the present application, multiple SL DRX configurations are configured based on SLRBs, radio link control (RLC) bearers, or LCHs.

[0036] In one embodiment of the present application, determining one or more SL DRX configurations for the MAC layer includes determining, at the MAC layer, the one or more SL DRX configurations for the MAC layer to be multiple SL DRX configurations.

[0037] In another embodiment of the present application, receiving SL data further includes monitoring sidelink control information (SCI) when an SL DRX configuration associated with an SLRB, an RLC bearer, or an LCH of one or more SL DRX configurations is within an active time.

[0038] In yet another embodiment of the present application, determining one or more SL DRX configurations for the MAC layer further includes, for each L2 destination ID, determining one SL DRX configuration from at least one SL DRX configuration associated with the corresponding L2 destination ID of the plurality of SL DRX configurations based on a predefined rule.

[0039] In yet another embodiment of the present application, receiving SL data further includes monitoring sidelink control information (SCI) when an SL DRX configuration associated with an L2 destination ID of one or more SL DRX configurations is within an active time.

[0040] Some embodiments of the present application also provide an apparatus, comprising: at least one non-transitory computer-readable medium having computer-executable instructions stored thereon; at least one receiving circuit; at least one transmitting circuit; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiving circuit, and the at least one transmitting circuit, wherein the computer-executable instructions are programmed to implement any method as described above in conjunction with the at least one receiving circuit, the at least one transmitting circuit, and the at least one processor.

[0041] To explain the manner in which the advantages and features of the present application may be achieved, the present application will be described by reference to specific embodiments thereof that are illustrated in the accompanying drawings. These drawings depict only exemplary embodiments of the present application and are therefore not to be considered limiting of its scope. [Brief explanation of the drawings]

[0042] [Figure 1] FIG. 1 is a schematic diagram illustrating an example wireless communication system according to some embodiments of the present application. [Figure 2] 1 illustrates an exemplary mapping relationship between an L2 destination ID, a PC5 QoS indicator (PQI), and an SLRB according to some embodiments of the present application. [Figure 3] 1 is a flowchart illustrating an example method for SL DRX configuration according to some embodiments of the present application. [Figure 4] FIG. 1 is a simplified block diagram of an example apparatus for SL DRX configuration according to some embodiments of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0043] The detailed description of the accompanying drawings is intended as an illustration of the presently preferred embodiment of the present application and is not intended to represent the only form in which the present application may be practiced. It should be understood that the same or equivalent function may be accomplished by different embodiments that are intended to be encompassed within the spirit and scope of the present application.

[0044] Reference will now be made in detail to several embodiments of the present application, examples of which are illustrated in the accompanying drawings. For ease of understanding, the embodiments are provided under specific network architectures and new service scenarios, such as 3rd Generation Partnership Project (3GPP (registered trademark, hereinafter the same)) 5G (i.e., NR), 3GPP Long Term Evolution (LTE) Release 8, etc. Those skilled in the art will be well aware that with the development of network architectures and new service scenarios, the embodiments of the present application can also be applied to similar technical problems. Furthermore, the terms used in the present application may be changed, but this should not affect the principles of the present application.

[0045] FIG. 1 is a schematic diagram illustrating an example wireless communication system 100 in accordance with some embodiments of the present application.

[0046] 1, the wireless communication system 100 includes at least one base station (BS) 101 and at least one UE 102. In particular, the wireless communication system 100 includes one BS 101 and two UEs 102 (e.g., UE 102a and UE 102b) for illustrative purposes. Although a particular number of BSs 101 and UEs 102 are depicted in FIG. 1, it is contemplated that any number of BSs 101 and UEs 102 may be included in the wireless communication system 100.

[0047] The wireless communication system 100 is compatible with any type of network capable of transmitting and receiving wireless communication signals. For example, the wireless communication system 100 may be compatible with a wireless communication network, a cellular network, a time division multiple access (TDMA)-based network, a code division multiple access (CDMA)-based network, an orthogonal frequency division multiple access (OFDMA)-based network, an LTE network, a 3GPP-based network, a 3GPP 5G network, a satellite communication network, a high altitude platform network, and / or other communication networks.

[0048] The BS 101 may also be referred to as an access point, access terminal, base, macrocell, Node B, evolved Node B (eNB), gNB, Home Node B, relay node, or device, or may be described using other terms used in the art. The BS 101 is generally part of a wireless access network, which may include a controller communicatively coupled to the BS 101.

[0049] According to some embodiments of the present application, the UEs 102 may include vehicle UEs (VUEs) and / or power-saving UEs (also referred to as power sensitive UEs). The power-saving UEs may include power-sensitive vulnerable road users (VRUs), public safety UEs (PS-UEs), and / or commercial sidelink UEs (CS-UEs). In one embodiment of the present application, the VRUs may include pedestrian UEs (P-UEs), bicycle UEs, wheelchair UEs, or other UEs that require power savings compared to VUEs. In one embodiment of the present application, the UE 102a may be a power-saving UE, and the UE 102b may be a VUE.

[0050] According to some other embodiments of the present application, the UE 102 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart television (e.g., a television connected to the Internet), a set-top box, a gaming console, a security system (including security cameras), an in-vehicle computer, a network device (e.g., a router, a switch, and a modem), or the like.

[0051] According to some other embodiments of the present application, the UE 102 may include a portable wireless line communication device, a smartphone, a mobile phone, a flip phone, a device with a subscriber identity module, a personal computer, a selective call receiver, or any other device capable of sending and receiving communication signals over a wireless network.

[0052] According to some other embodiments of the present application, the UE 102 may include a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, or the like.

[0053] Furthermore, the UE 102 may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or may be described using other terms used in the art.

[0054] Both UE 102a and UE 102b in the embodiment of FIG. 1 may transmit information to and receive control information from BS 101, for example, over an LTE or New Radio (NR) Uu interface.

[0055] According to some embodiments of FIG. 1 , the UE 102a may function as a transmitting (Tx) UE, and the UE 102b may function as a receiving (Rx) UE. The UE 102a may transmit messages to the UE 102b over a sidelink, such as a PC5 interface defined in 3GPP TS 23.303. The UE 102a may transmit information or data to other UEs in the wireless communication system 100 via sidelink unicast, sidelink groupcast, or sidelink broadcast. For example, the UE 102a may transmit data to the UE 102b in a sidelink unicast session. The UE 102a may transmit data to the UE 102b and other UEs in a groupcast group (not shown in FIG. 1 ) via a sidelink groupcast transmission session. The UE 102a may also transmit data to the UE 102b and other UEs (not shown in FIG. 1 ) via a sidelink broadcast transmission session.

[0056] According to some other embodiments of FIG. 1, the UE 102b may function as a transmitting (Tx) UE and transmit messages, and the UE 102a may function as a receiving (Rx) UE and receive messages from the UE 102b.

[0057] In RAN2#113e, the SL DRX configuration granularity for sidelink communications, e.g., broadcast or groupcast communications, was discussed. It was agreed that the SL DRX configuration requires finer granularity compared to the cast type, e.g., broadcast or groupcast. Then, how to determine the SL DRX configuration for sidelink communications for different granularities needs to be resolved.

[0058] In consideration of this, an embodiment of the present application provides a technical solution for SL communication, which determines three types of granularity for SL DRX configuration, including an SL DRX configuration configured per L2 destination ID, an SL DRX configuration configured per QoS-related parameter, and an SL DRX configuration configured per SLRB, or RLC bearer, or LCH.

[0059] In addition, the SL DRX procedure is processed by the MAC layer of the UE. However, SL DRX configurations under some types of granularity cannot be directly used by the MAC layer. For example, for SL DRX configurations configured for each QoS-related parameter, because the QoS-related parameters are not configured for the MAC layer, the MAC layer cannot maintain the SL DRX configuration configured for each QoS-related parameter and therefore cannot determine the active time of each SL DRX configuration. From the perspective of the Tx UE, the MAC layer cannot transmit data based on the active time of the SL DRX configuration. In consideration of this, embodiments of the present application also propose solutions regarding methods for determining the SL DRX configuration to be used by the MAC layer for three types of granularity.

[0060] Furthermore, the embodiments of the present application also propose solutions regarding how to select a destination ID (or "destination") or LCH under three kinds of granularity.

[0061] Details of the embodiments of the present application are illustrated in the following text in conjunction with the accompanying drawings.

[0062] According to some embodiments of the present application, a MAC layer of a UE (e.g., a Tx UE or an Rx UE) has one or more L2 destination IDs, and each L2 destination ID may be associated with a service. In some embodiments of the present application, a service may have one or more QoS-related parameters. The QoS-related parameter may refer to a QoS flow, a QoS profile, or any QoS parameter within a QoS profile. In some other embodiments of the present application, a service may have one or more QoS flows. Each QoS flow is associated with a QoS profile and a QoS flow indicator (QFI). Each QoS profile has a set of QoS parameters, such as a PQI, a priority, a packet delay budget (PDB), a packet error rate (PER), etc. Thus, each L2 destination ID may be associated with one or more QoS parameters, one or more QoS flows, or one or more QoS profiles. A mapping relationship between one or more QoS parameters (or one or more QoS flows, or one or more QoS profiles) and the L2 destination ID may be received from a higher layer of the UE (i.e., a layer higher than the AS layer). In one embodiment of the present application, the upper layer may be a Vehicle-to-Everything (V2X) layer.

[0063] In addition, each L2 destination ID may also be associated with one or more SLRB configurations. Each SLRB configuration may include a mapping relationship between QoS flows (each QoS flow is associated with one set of QoS parameters) and a corresponding SLRB, and a radio link control (RLC) bearer configuration including a logical channel configuration. In other words, each SLRB may be associated with one or more QoS flows and a corresponding RLC bearer. Each RLC bearer may be associated with a corresponding LCH. As a result, each SLRB may be associated with a corresponding LCH.

[0064] FIG. 2 illustrates an exemplary mapping relationship between an L2 destination ID, a PQI, and an SLRB according to some embodiments of the present application.

[0065] Referring to FIG. 2, it is assumed that the MAC layer of the UE has two L2 destination IDs, for example, L2 destination id#1 and L2 destination id#2.

[0066] Each L2 destination ID may be associated with one or more QoS-related parameters, e.g., PQI#1, PQI#2, etc., as shown in Figure 2. The mapping relationship between one or more PQIs and the L2 destination IDs may be received from the V2X layer of the UE. For example, the V2X layer may indicate to the MAC layer that L2 destination id#1 is associated with PQI#1 through PQI#N1, and L2 destination id#2 is associated with PQI#1 through PQI#N2, where N1 and N2 are integers greater than 0, and N1 may be the same as or different from N2.

[0067] Those skilled in the art will understand that "#1", "#2", ..., "#N1" are PQI indexes for L2 destination ID#1, but are not PQI values. Similarly, "#1", "#2", ..., "#N2" are PQI indexes for L2 destination ID#1, but are not PQI values. In addition, for different L2 destination IDs, the same PQI index may refer to the same PQI or different PQIs. For example, for L2 destination id#1 and L2 destination id#2, "PQI#1" may refer to the same PQI or two different PQIs. The same principle may also be applicable to the following indexes for SLRB configuration and RLC bearer configuration:

[0068] Each L2 destination ID may be associated with one or more SLRB configurations, for example, L2 destination id#1 is associated with SLRB config#1 to SLRB config#M1, L2 destination id#2 is associated with SLRB config#1 to SLRB config#M2, where M1 and M2 are integers greater than 0, and M1 may be the same as or different from M2.

[0069] Each SLRB configuration may include a relationship between one or more PQIs, the corresponding SLRB, and the corresponding RLC bearer configuration. For example, for L2 destination ID#1, SLRB config#1 may include RLC bearer config#1, SLRB config#2 may include RLC bearer config#2, ... SLRB config#M1 may include RLC bearer config#M1. For L2 destination ID#2, SLRB config#1 may include RLC bearer config#1, SLRB config#2 may include RLC bearer config#2, ... SLRB config#M1 may include RLC bearer config#M2. In other words, each SLRB is associated with a corresponding RLC bearer.

[0070] Each RLC bearer configuration may include an LCH configuration (not shown in FIG. 2). For example, RLC bearer config#2 may include LCH config#2 (not shown in FIG. 2). That is, each RLC bearer is associated with a corresponding logical channel. As a result, each SLRB may be associated with a corresponding LCH.

[0071] Although a particular number of L2 destination IDs are depicted in Figure 2, it is contemplated that any number of L2 destination IDs may be included in the MAC layer in some other embodiments of the present application. In addition, although the PQI is depicted in Figure 2 to illustrate a mapping relationship, it is contemplated that the PQI may be replaced by any other QoS parameter within a QoS profile, or may be replaced by a QoS flow, or may be replaced by a QoS profile in some other embodiments of the present application.

[0072] FIG. 3 is a flowchart illustrating a method for SL DRX configuration according to some embodiments of the present application. Although the method is illustrated at a system level with two remote devices, e.g., a Tx UE and an Rx UE, those skilled in the art will understand that the method implemented in the Tx UE and the method implemented in the Rx UE may be separately implemented and incorporated by other devices having similar functionality. In some embodiments of the present application, the Tx UE or the Rx UE performs sidelink communication in a broadcast or groupcast manner. For example, the Tx UE may be the UE 102a as shown in FIG. 1, and the Rx UE may be the UE 102b as shown in FIG. 1.

[0073] In the exemplary method shown in FIG. 3, in step 301, a Tx UE may obtain multiple SL DRX configurations for SL communication.

[0074] According to some embodiments of the present application, multiple SL DRX configurations may be pre-configured in the Tx UE, for example, in a subscriber identity module (SIM), a universal subscriber identity module (USIM), or in a memory of the Tx UE. Thus, obtaining multiple SL DRX configurations may refer to accessing a SIM, a USIM, or a memory to obtain multiple SL DRX configurations in the Tx UE.

[0075] According to some other embodiments of the present application, the BS 101, as shown in FIG. 1, may transmit multiple SL DRX configurations to the UEs 102 (e.g., the Tx UE 102a and the Rx UE 102b). The Tx UEs may then obtain the multiple SL DRX configurations from the BS. In one embodiment of the present application, the BS 101 may broadcast the multiple SL DRX configurations in at least one SIB. The Tx UEs may then receive the multiple SL DRX configurations in the at least one SIB broadcast by the BS 101. In another embodiment of the present application, the BS 101 may configure the multiple SL DRX configurations via at least one RRC signaling. The Tx UEs may then receive the multiple SL DRX configurations via at least one RRC signaling.

[0076] The same operation may also be performed by the Rx UE. That is, in step 302, the Rx UE may also acquire multiple SL DRX configurations for SL communication. Similarly, the Rx UE may acquire multiple SL DRX configurations through pre-configuration (e.g., multiple SL DRX configurations are pre-configured in the Rx UE). Otherwise, the Rx UE may acquire multiple SL DRX configurations in at least one SIB broadcast by BS 101 or may acquire multiple SL DRX configurations via at least one RRC signaling transmitted from BS 101.

[0077] According to some embodiments of the present application, each of the plurality of SL DRX configurations may include at least one parameter of a DRX on duration, a DRX off duration, a DRX wake-up time, a set of SL DRX timers associated with the DRX, a DRX cycle, and a DRX offset value.

[0078] In one embodiment of the present application, the set of SL DRX timers associated with DRX may include at least one of an on-duration timer, an inactivity timer, a hybrid automatic repeat request (HARQ) round-trip time (RTT) timer, a HARQ retransmission timer, and any other timers associated with DRX specified in a 3GPP standard document.

[0079] The multiple SL DRX configurations can be configured based on one of three types of granularity: Multiple SL DRX configurations are configured based on an L2 destination ID. This type of granularity is also referred to as "SL DRX configuration configured per L2 destination ID," and is expressed as "an SL DRX configuration configured per L2 destination ID," or "each of multiple SL DRX configurations configured per L2 destination ID." With this type of granularity, each L2 destination ID can be associated with one DRX configuration among the multiple SL DRX configurations. In other words, one DRX configuration among the multiple SL DRX configurations can be associated with one or more L2 destination IDs. In one embodiment, multiple L2 destination IDs or a group of L2 destination IDs may be configured with one SL DRX configuration, and all other L2 destination IDs that are not explicitly configured with an SL DRX configuration may be configured with the default SL DRX configuration. The multiple SL DRX configurations are configured based on a QoS-related parameter. The QoS-related parameter may refer to a QoS flow, a QoS profile, or any one of the QoS parameters in the QoS profile. This type of granularity is also referred to as an "SL DRX configuration configured for each QoS-related parameter," and expressed as "an SL DRX configuration configured for each QoS-related parameter," or "each of the multiple SL DRX configurations is configured for each QoS-related parameter," etc. With this type of granularity, each QoS-related parameter (e.g., a QoS flow, a QoS profile, or any QoS parameter in the QoS profile) may be associated with one DRX configuration of the multiple SL DRX configurations. In other words, one DRX configuration of the multiple SL DRX configurations may be associated with one or more QoS-related parameters. In one embodiment, multiple QoS-related parameters or groups of QoS-related parameters may be configured in one SL DRX configuration, and all other QoS-related parameters that are not explicitly configured in an SL DRX configuration may be configured in the default SL DRX configuration. Multiple SL DRX configurations are configured based on SLRBs, RLC bearers, or LCHs. This type of granularity is also referred to as "SL DRX configuration configured per SLRB, RLC bearer, or LCH," expressed as "an SL DRX configuration configured per SLRB, RLC bearer, or LCH," or "each of multiple SL DRX configurations configured per SLRB, RLC bearer, or LCH." With this type of granularity, each SLRB, RLC bearer, or LCH may be associated with one DRX configuration among the multiple SL DRX configurations. In other words, one DRX configuration among the multiple SL DRX configurations may be associated with one or more SLRBs, one or more RLC bearers, or one or more LCHs. In one embodiment, multiple SLRBs, RLC bearers, or LCHs or a group of SLRBs, RLC bearers, or LCHs may be configured with one SL DRX configuration, and all other SLRBs, RLC bearers, or LCHs that are not explicitly configured with an SL DRX configuration may be configured with the default SL DRX configuration.

[0080] After obtaining the multiple SL DRX configurations, the Tx UE may determine one or more SL DRX configurations from the multiple SL DRX configurations for the Tx UE's MAC layer in step 303. Similarly, after obtaining the multiple SL DRX configurations, the Rx UE may determine one or more SL DRX configurations from the multiple SL DRX configurations for the Rx UE's MAC layer in step 304. The Tx UE and the Rx UE may each determine one or more SL DRX configurations for their MAC layers using the same method.

[0081] Then, in step 305, if there is SL data associated with the DRX of the Tx UE, the Tx UE may transmit the SL data from the Tx UE based on the active time derived in each of the one or more SL DRX configurations. The Tx UE may transmit the SL data to one or more other UEs, including the Rx UE, via a broadcast or groupcast manner. In step 306, the Rx UE may receive the SL data based on the active time derived in each of the one or more SL DRX configurations.

[0082] Embodiment I According to some embodiments of the present application, multiple SL DRX configurations may be configured based on an L2 destination ID. That is, each L2 destination ID may be associated with one SL DRX configuration among multiple SL DRX configurations. In such embodiments, all of the multiple SL DRX configurations may be used for the MAC layer of a UE (e.g., a Tx UE or an Rx UE).

[0083] As a result, for a Tx UE, determining one or more SL DRX configurations for the MAC layer in step 303 may include the MAC layer of the Tx UE determining the one or more SL DRX configurations for the MAC layer to be multiple SL DRX configurations. Each L2 destination ID may be associated with one SL DRX configuration of the multiple SL DRX configurations. Then, for each L2 destination ID, the MAC layer of the Tx UE may maintain a set of SL DRX timers for the SL DRX configuration configured for the L2 destination ID.

[0084] In some embodiments of the present application, the set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, and any other timers specified in a 3GPP standard document.

[0085] For example, it is assumed that the multiple SL DRX configurations include two SL DRX configurations (e.g., SL DRX configuration #1 and SL DRX configuration #2), where SL DRX configuration #1 is configured for L2 destination id #1 and SL DRX configuration #2 is configured for L2 destination id #2. After obtaining the two SL DRX configurations, the MAC layer of the UE (e.g., a Tx UE or an Rx UE) may determine the two SL DRX configurations for the MAC layer. For L2 destination id #1, the MAC layer of the UE may maintain a first set of SL DRX timers (including at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, etc.). For L2 destination id #2, the MAC layer of the UE may maintain a second set of SL DRX timers (including at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, etc.).

[0086] In step 305, after determining one or more SL DRX configurations, transmitting the SL data may further include the MAC layer of the Tx UE selecting an L2 destination ID during an LCP procedure, where the SL DRX configuration associated with the L2 destination ID of the one or more SL DRX configurations is in an active time. As an example, an SL DRX configuration being in an active time may refer to at least one timer (if any) of the SL DRX configuration for the L2 destination ID being running, e.g., an on-duration timer, an inactivity timer, and an HARQ retransmission timer being running. As another example, an SL DRX configuration being in an active time may refer to the SL DRX configuration being in one or more time ranges or time periods defined as SL DRX active times in 3GPP standard documents.

[0087] The procedure for selecting an L2 destination ID may be performed as follows: First, the Tx UE may select an LCH with the highest priority among the LCHs that meet the conditions as specified in the 3GPP standard document for LCP. Since one or more LCHs may be associated with an L2 destination ID, the Tx UE may determine the L2 destination ID associated with the selected LCH based on a mapping relationship between the destination ID and one or more LCHs.

[0088] After determining the L2 destination ID, the Tx UE may determine whether the SL DRX configuration associated with the L2 destination ID is within an active time. The SL DRX configuration being within an active time may refer to the SL DRX configuration being in one or more time ranges or time periods defined as SL DRX active times, or at least one SL DRX timer of a set of SL DRX timers (including an on-duration timer, an inactivity timer, and an HARQ retransmission timer) of the SL DRX configuration being running, e.g., the on-duration timer being running. In other words, the Tx UE may check the active time condition, or whether at least one SL DRX timer of the set of SL DRX timers associated with the L2 destination ID is running. If the active time condition is met or at least one SL DRX timer of the set of SL DRX timers associated with the L2 destination ID is running, the SL DRX configuration associated with the L2 destination ID is within the active time, and therefore the L2 destination ID is selected by the Tx UE for transmission, and then all LCHs associated with the L2 destination ID may be selected for transmission.

[0089] If the active time condition is not met or none of the SL DRX timers associated with the L2 destination ID are running, the SL DRX configuration associated with the L2 destination ID is not within the active time, and therefore the L2 destination ID cannot be selected. The Tx UE may select another LCH with the highest priority from the remaining LCHs and perform the above procedure until the L2 destination ID is selected.

[0090] The Rx UE may perform the same operations in step 304 as those performed by the Tx UE in step 303. That is, the MAC layer of the Rx UE may determine one or more SL DRX configurations for the MAC layer to be multiple SL DRX configurations. For each L2 destination ID, the MAC layer of the Rx UE may maintain a set of SL DRX timers for the SL DRX configurations configured for the L2 destination ID.

[0091] In step 306, the Rx UE may receive SL data based on an active time derived in each of the one or more SL DRX configurations. In some embodiments of the present application, receiving SL data may further include monitoring SCI when an SL DRX configuration associated with an L2 destination ID of the one or more SL DRX configurations is within the active time. An SL DRX configuration being within the active time may refer to at least one SL DRX timer of a set of SL DRX timers of the SL DRX configuration being running (e.g., at least one of an on-duration timer, an inactivity timer, and a HARQ retransmission timer is running), or the SL DRX configuration being within one or more time ranges or time periods defined as SL DRX active times. In other words, the Rx UE monitors SCI for an L2 destination ID when at least one SL DRX timer of a set of SL DRX timers of the SL DRX configuration associated with the L2 destination ID is running. In one embodiment of the present application, the Rx UE wakes up to monitor SCI during the active times of all of the one or more SL DRX configurations.

[0092] Embodiment II According to some embodiments of the present application, multiple SL DRX configurations may be configured based on QoS-related parameters. As mentioned above, each QoS flow is associated with a QoS profile. Each QoS profile has a set of QoS parameters including PQI, PDB, PER, etc. Therefore, a QoS-related parameter herein may refer to a QoS flow, a QoS profile, or any QoS parameter (e.g., PQI) within a QoS profile. That is, in embodiment II, each QoS-related parameter may be associated with an SL DRX configuration, which may refer to one of: each QoS flow being associated with an SL DRX configuration; each QoS profile being associated with an SL DRX configuration; or each QoS parameter (e.g., PQI) within a QoS profile being associated with an SL DRX configuration. In such embodiments, multiple SL DRX configurations cannot be directly used for the MAC layer of a UE (e.g., a Tx UE or an Rx UE).

[0093] Embodiment II-1 In embodiment II-1, after receiving multiple SL DRX configurations configured based on the QoS-related parameters, in step 303, the RRC layer of the Tx UE may determine one or more SL DRX configurations for the MAC layer, which includes that for each logical channel of the Tx UE, the RRC layer of the Tx UE may determine (or derive) at least one SL DRX configuration from the multiple SL DRX configurations based on the mapping relationship between the QoS-related parameters and the SLRBs and the mapping relationship between the SLRBs and the logical channels.

[0094] As shown in FIG. 2, at least one QoS-related parameter may be mapped to one SLRB, and this mapping relationship may be included in an SLRB configuration. In addition, each SLRB configuration may also include an RLC bearer configuration, which may include an LCH configuration. As a result, each SLRB may correspond to or be associated with an LCH. That is, based on the SLRB configuration, the RRC layer determines that each LCH may be associated with at least one QoS-related parameter, and at least one SL DRX configuration configured for the at least one QoS-related parameter may be used for the corresponding LCH. In some embodiments of the present application, the SLRB configuration may be obtained by pre-configuration in the Tx UE or in at least one SIB transmitted by the BS.

[0095] After determining at least one SL DRX configuration for each LCH, the RRC layer may indicate the at least one SL DRX configuration for each LCH to the MAC layer. Then, for each LCH, the MAC layer of the Tx UE may maintain at least one set of SL DRX timers. In some embodiments of the present application, the set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, and any other timers specified in 3GPP standard documents.

[0096] For example, it is assumed that the multiple SL DRX configurations include three SL DRX configurations (e.g., SL DRX configuration #1, SL DRX configuration #2, and SL DRX configuration #3), where SL DRX configuration #1 is configured for QoS-related parameter #1, SL DRX configuration #2 is configured for QoS parameter #2, and SL DRX configuration #3 is configured for QoS parameter #3. It is further assumed that QoS-related parameter #1 and QoS-related parameter #2 are mapped to SLRB #1, SLRB #1 is mapped to LCH #1 based on the SLRB configuration for SLRB #1, QoS-related parameter #3 is mapped to SLRB #2, and SLRB #1 is mapped to LCH #2 based on the SLRB configuration for SLRB #2. Then, after obtaining the three SL DRX configurations, the RRC layer of the Tx UE may determine SL DRX configuration #1 and SL DRX configuration #2 for LCH #1 and SL DRX configuration #3 for LCH #2, and instruct the same to the MAC layer of the Tx UE. After receiving the above information, for LCH#1, the MAC layer of the UE may maintain a first set of SL DRX timers for SL DRX configuration#1 and a second set of SL DRX timers for SL DRX configuration#2, and for LCH#2, the MAC layer may maintain a third set of SL DRX timers for SL DRX configuration#3. Each set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, etc.

[0097] In step 305, after determining one or more SL DRX configurations, transmitting the SL data may further include the MAC layer of the Tx UE selecting one or more LCHs during the LCP procedure, where an SL DRX configuration associated with each logical channel of the one or more logical channels is within the active time. The procedure for selecting one or more LCHs may be performed as follows: First, the Tx UE selects an LCH with the highest priority from all LCHs whose SL DRX configurations are within the active time, and then the Tx UE may determine an L2 destination ID associated with the LCH based on a mapping relationship between the destination ID and the one or more LCHs. After determining the L2 destination ID, the Tx UE may select one or more LCHs associated with the L2 destination ID whose SL DRX configuration is within the active time. An SL DRX configuration being within an active time may refer to at least one SL DRX timer of the set of SL DRX timers of the SL DRX configuration being running (e.g., at least one of the on-duration timer, the inactivity timer, and the HARQ retransmission timer is running), or the SL DRX configuration being within one or more time ranges or time periods defined as the SL DRX active time.

[0098] In step 304, the Rx UE may perform the same operations as those performed by the Tx UE in step 303. That is, in step 304, after receiving the multiple SL DRX configurations configured based on the QoS-related parameters, the RRC layer of the Rx UE may determine one or more SL DRX configurations for the MAC layer, which includes: for each logical channel of the RRC layer of the Rx UE, the RRC layer of the Rx UE may determine (derive) at least one SL DRX configuration from the multiple SL DRX configurations based on the mapping relationship between the QoS-related parameters and the SLRBs and the mapping relationship between the SLRBs and the logical channels.

[0099] After determining at least one SL DRX configuration for each LCH, the RRC layer of the Rx UE may indicate the at least one SL DRX configuration for each LCH to the MAC layer of the Rx UE. Then, for each LCH, the MAC layer of the Rx UE may maintain at least one set of SL DRX timers. In some embodiments of the present application, the set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, and any other timers specified in 3GPP standard documents.

[0100] In step 306, the Rx UE may receive SL data based on an active time derived for each of the one or more SL DRX configurations. In some embodiments of the present application, receiving SL data further includes monitoring SCI when an SL DRX configuration associated with an LCH of the one or more SL DRX configurations is in active time. An SL DRX configuration being in active time may refer to at least one SL DRX timer of a set of SL DRX timers of the SL DRX configuration being running (e.g., at least one of an on-duration timer, an inactivity timer, and a HARQ retransmission timer is running), or the SL DRX configuration being within one or more time ranges or time periods defined as SL DRX active times. In other words, the Rx UE monitors SCI when at least one SL DRX timer of a set of SL DRX timers of the SL DRX configuration associated with an LCH is running. In one embodiment of the present application, the Rx UE wakes up to monitor SCI during the active times of all of the one or more SL DRX configurations.

[0101] Embodiment II-2 In embodiment II-1, the RRC layer of the Tx UE may determine at least one SL DRX for each LCH. In embodiment II-2, after determining at least one SL DRX for each LCH based on the method of embodiment II-1, the RRC layer of the Tx UE may further determine one SL DRX configuration from the at least one SL DRX configuration for each LCH based on a predefined rule in step 303. The predefined rule may define how to combine the at least one SL DRX configuration for each LCH or how to select one SL DRX configuration from the at least one SL DRX configuration for each logical channel.

[0102] In one embodiment of the present application, the SL DRX configuration having the minimum periodicity of at least one SL DRX configuration may be derived as the final SL DRX configuration for the LCH. In another embodiment of the present application, the SL DRX period of the SL DRX configuration using the minimum periodicity of at least one SL DRX configuration may be derived as the final SL DRX configuration for the LCH. In yet another embodiment of the present application, the SL DRX timer of the SL DRX configuration using the maximum value of at least one SL DRX configuration may be derived as the final SL DRX configuration for the LCH. It is contemplated that any other predefined rule may be used to determine the final SL DRX configuration for the LCH.

[0103] After determining at least one SL DRX configuration for each LCH, the RRC layer may indicate one SL DRX configuration for each LCH to the MAC layer. Then, for each LCH, the MAC layer of the Tx UE may maintain one set of SL DRX timers. In some embodiments of the present application, the set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, and any other timers specified in 3GPP standard documents.

[0104] For example, it is assumed that the RRC layer of the Tx UE determines SL DRX configuration #1 and SL DRX configuration #2 for LCH #1 and SL DRX configuration #3 for LCH #2 based on the method in embodiment II-1, and then, for LCH #1, the RRC layer of the Tx UE may further determine SL DRX configuration #1 for LCH #1 based on a predefined rule. The RRC layer of the Tx UE may instruct the MAC layer of the Tx UE of SL DRX configuration #1 for LCH #1 and SL DRX configuration #3 for LCH #2. After receiving the above information, for LCH #1, the MAC layer of the Tx UE may maintain a first set of SL DRX timers for SL DRX configuration #1 and a third set of SL DRX timers for SL DRX configuration #3 for LCH #2. Each set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, etc.

[0105] In step 305, after determining the one or more SL DRX configurations, transmitting the SL data may further include: the MAC layer of the Tx UE selecting one or more LCHs during the LCP procedure, and an SL DRX configuration associated with each logical channel of the one or more logical channels is within an active time. The procedure for selecting one or more LCHs in embodiment II-2 may be the same as the procedure performed in embodiment II-1.

[0106] In step 304, the Rx UE may perform the same operation as that performed by the Tx UE in step 303. That is, after determining at least one SL DRX for each LCH based on the method in embodiment II-1, the RRC layer of the Rx UE may further determine one SL DRX configuration from the at least one SL DRX configuration for each LCH based on a predefined rule in step 304. The predefined rule used by the Rx UE may be the same as that used by the Tx UE.

[0107] After determining one SL DRX configuration for each LCH, the RRC layer of the Rx UE may indicate one SL DRX configuration for each LCH to the MAC layer of the Rx UE. Then, for each LCH, the MAC layer of the Rx UE may maintain one set of SL DRX timers. In some embodiments of the present application, the set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, and any other timers specified in 3GPP standard documents.

[0108] In step 306, the Rx UE may receive SL data based on an active time derived for each of the one or more SL DRX configurations. In some embodiments of the present application, receiving SL data further includes monitoring SCI when an SL DRX configuration associated with an LCH of the one or more SL DRX configurations is in active time. An SL DRX configuration being in active time may refer to at least one SL DRX timer of a set of SL DRX timers of the SL DRX configuration being running (e.g., at least one of an on-duration timer, an inactivity timer, and a HARQ retransmission timer is running), or the SL DRX configuration being within one or more time ranges or time periods defined as SL DRX active times. In other words, the Rx UE monitors SCI when at least one SL DRX timer of a set of SL DRX timers of the SL DRX configuration associated with an LCH is running. In one embodiment of the present application, the Rx UE wakes up to monitor SCI during the active times of all of the one or more SL DRX configurations.

[0109] Embodiment II-3 In embodiment II-3, after receiving the multiple SL DRX configurations configured based on the QoS-related parameters, in step 303, the RRC layer of the Tx UE may determine one or more SL DRX configurations for the MAC layer, including: For each L2 destination ID of the Tx UE, the RRC layer of the Tx UE may determine (derive) at least one SL DRX configuration from the multiple SL DRX configurations based on the mapping relationship between the PQI and the L2 destination ID.

[0110] At least one QoS-related parameter may be mapped to one destination ID, as depicted in Figure 2. In some embodiments of the present application, the mapping relationship between the QoS-related parameter and the destination ID may be obtained by higher layer signaling, for example, signaling from a V2X layer.

[0111] After determining at least one SL DRX configuration for each L2 destination ID, the RRC layer may indicate the at least one SL DRX configuration for each L2 destination ID to the MAC layer. Then, for each L2 destination ID, the MAC layer of the Tx UE may maintain at least one set of SL DRX timers. In some embodiments of the present application, the set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, and any other timers specified in a 3GPP standard document.

[0112] For example, it is assumed that the multiple SL DRX configurations include three SL DRX configurations (e.g., SL DRX configuration #1, SL DRX configuration #2, and SL DRX configuration #3), where SL DRX configuration #1 is configured for QoS-related parameter #1, SL DRX configuration #2 is configured for QoS parameter #2, and SL DRX configuration #3 is configured for QoS parameter #3. It is further assumed that QoS-related parameter #1 and QoS-related parameter #2 are mapped to L2 destination id #1, and QoS-related parameter #3 is mapped to L2 destination id #2. Then, after obtaining the three SL DRX configurations, the RRC layer of the Tx UE may determine SL DRX configuration #1 and SL DRX configuration #2 for L2 destination id #1 and SL DRX configuration #3 for L2 destination id #2, and instruct the same to the MAC layer of the Tx UE. After receiving the above information, for L2 destination id#1, the MAC layer of the Tx UE may maintain a first set of SL DRX timers for SL DRX configuration #1 and a second set of SL DRX timers for SL DRX configuration #2. For L2 destination id#2, the MAC layer may maintain a third set of SL DRX timers for SL DRX configuration #3. Each set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, etc.

[0113] In step 305, after determining the one or more SL DRX configurations, transmitting the SL data may further include: the MAC layer of the Tx UE selecting an L2 destination ID during an LCP procedure, and an SL DRX configuration associated with the L2 destination ID of the one or more SL DRX configurations is within an active time. The procedure for selecting an L2 destination ID may be the same as the procedure performed in embodiment I.

[0114] In step 304, the Rx UE may perform the same operations as those performed by the Tx UE in step 303. That is, in step 304, after receiving the multiple SL DRX configurations configured based on the QoS-related parameters, the RRC layer of the Rx UE may determine one or more SL DRX configurations for the MAC layer, which includes: For each L2 destination ID of the Rx UE, the RRC layer of the Rx UE may determine (derive) at least one SL DRX configuration from the multiple SL DRX configurations based on the mapping relationship between the QoS-related parameters and the L2 destination ID.

[0115] After determining at least one SL DRX configuration for each L2 destination ID, the RRC layer of the Rx UE may indicate the at least one SL DRX configuration for each L2 destination ID to the MAC layer of the Rx UE. Then, for each L2 destination ID, the MAC layer of the Rx UE may maintain at least one set of SL DRX timers. In some embodiments of the present application, the set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, and any other timers specified in a 3GPP standard document.

[0116] In step 306, the Rx UE may receive SL data based on an active time derived in each of the one or more SL DRX configurations. In some embodiments of the present application, receiving SL data may further include monitoring SCI when an SL DRX configuration associated with an L2 destination ID of the one or more SL DRX configurations is within the active time. An SL DRX configuration being within the active time may refer to at least one SL DRX timer of a set of SL DRX timers of the SL DRX configuration being running (e.g., at least one of an on-duration timer, an inactivity timer, and a HARQ retransmission timer is running), or the SL DRX configuration being within one or more time ranges or time periods defined as SL DRX active times. In other words, the Rx UE monitors SCI when at least one SL DRX timer of a set of SL DRX timers of the SL DRX configuration associated with the L2 destination ID is running. In one embodiment of the present application, the Rx UE wakes up to monitor SCI during the active times of all of the one or more SL DRX configurations.

[0117] Embodiment II-4 In embodiment II-3, the RRC layer of the Tx UE may determine at least one SL DRX for each L2 destination ID. In embodiment II-4, after determining at least one SL DRX for each L2 destination ID based on the method of embodiment II-3, in step 303, the RRC layer of the Tx UE may further determine one SL DRX configuration from the at least one SL DRX configuration for each L2 destination ID based on a predefined rule. The predefined rule may define how to combine the at least one SL DRX configuration for each L2 destination ID or how to select one SL DRX configuration from the at least one SL DRX configuration for each L2 destination ID.

[0118] In one embodiment of the present application, the SL DRX configuration having the minimum periodicity of at least one SL DRX configuration may be derived as the final SL DRX configuration for the L2 destination ID. In another embodiment of the present application, the SL DRX period of the SL DRX configuration using the minimum periodicity of the at least one SL DRX configuration may be derived as the final SL DRX configuration for the L2 destination ID. In yet another embodiment of the present application, the SL DRX timer of the SL DRX configuration using the maximum value of the at least one SL DRX configuration may be derived as the final SL DRX configuration for the L2 destination ID. It is contemplated that any other predefined rule may be used to determine the final SL DRX configuration for the L2 destination ID.

[0119] After determining at least one SL DRX configuration for each L2 destination ID, the RRC layer may indicate one SL DRX configuration for each L2 destination ID to the MAC layer. Then, for each L2 destination ID, the MAC layer of the Tx UE may maintain one set of SL DRX timers. In some embodiments of the present application, the set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, and any other timers specified in 3GPP standard documents.

[0120] For example, it is assumed that the RRC layer of the Tx UE determines SL DRX configuration #1 and SL DRX configuration #2 for L2 destination ID #1 and SL DRX configuration #3 for L2 destination ID #2 based on the method in embodiment II-3, and then, for L2 destination ID #1, the RRC layer of the Tx UE may further determine SL DRX configuration #1 for L2 destination ID #1 based on a predefined rule. The RRC layer of the Tx UE may instruct the MAC layer of the Tx UE of SL DRX configuration #1 for L2 destination ID #1 and SL DRX configuration #3 for L2 destination ID #2. After receiving the above information, for L2 destination ID #1, the MAC layer of the Tx UE may maintain a first set of SL DRX timers for SL DRX configuration #1 and a third set of SL DRX timers for SL DRX configuration #3 for L2 destination ID #2. Each set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, and the like.

[0121] In step 305, after determining the one or more SL DRX configurations, transmitting the SL data may further include: the MAC layer of the Tx UE selecting an L2 destination ID during an LCP procedure, and the SL DRX configurations associated with the L2 destination IDs of the one or more SL DRX configurations are within an active time. The procedure for selecting an L2 destination ID in embodiment II-4 may be the same as the procedure performed in embodiment II-3.

[0122] In step 304, the Rx UE may perform the same operation as that performed by the Tx UE in step 303. That is, after determining at least one SL DRX for each L2 destination ID based on the method in embodiment II-3, the RRC layer of the Rx UE may further determine one SL DRX configuration from the at least one SL DRX configuration for each L2 destination ID based on a predefined rule in step 304. The predefined rule used by the Rx UE may be the same as the route used by the Tx UE.

[0123] After determining one SL DRX configuration for each L2 destination ID, the RRC layer of the Rx UE may indicate one SL DRX configuration for each L2 destination ID to the MAC layer of the Rx UE. Then, for each L2 destination ID, the MAC layer of the Rx UE may maintain one set of SL DRX timers. In some embodiments of the present application, the set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, and any other timers specified in 3GPP standard documents.

[0124] In step 306, the Rx UE may receive SL data based on an active time derived in each of the one or more SL DRX configurations. In some embodiments of the present application, receiving SL data may further include monitoring SCI when an SL DRX configuration associated with an L2 destination ID of the one or more SL DRX configurations is within the active time. An SL DRX configuration being within the active time may refer to at least one SL DRX timer of a set of SL DRX timers of the SL DRX configuration being running (e.g., at least one of an on-duration timer, an inactivity timer, and a HARQ retransmission timer is running), or the SL DRX configuration being within one or more time ranges or time periods defined as SL DRX active times. In other words, the Rx UE monitors SCI when at least one SL DRX timer of a set of SL DRX timers of the SL DRX configuration associated with the L2 destination ID is running. In one embodiment of the present application, the Rx UE wakes up to monitor SCI during the active times of all of the one or more SL DRX configurations.

[0125] Embodiment II-5 In embodiment II-5, after receiving multiple SL DRX configurations configured based on the QoS-related parameters, in step 303, the RRC layer of the Tx UE may determine one or more SL DRX configurations for the MAC layer, which may include: The RRC layer of the Tx UE may indicate a mapping relationship between the QoS-related parameters and the SL DRX configurations to the MAC layer.

[0126] After receiving the mapping relationship between the QoS-related parameters and the SL DRX configuration, for each QoS-related parameter, the MAC layer of the Tx UE may maintain a set of SL DRX timers. In some embodiments of the present application, the set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, and any other timers specified in a 3GPP standard document.

[0127] For example, it is assumed that the multiple SL DRX configurations include three SL DRX configurations (e.g., SL DRX configuration #1, SL DRX configuration #2, and SL DRX configuration #3), where SL DRX configuration #1 is configured for QoS-related parameter #1, SL DRX configuration #2 is configured for QoS-related parameter #2, and SL DRX configuration #3 is configured for QoS-related parameter #3. Then, after receiving the three SL DRX configurations, the RRC layer may indicate the mapping relationships between the three SL DRX configurations and the three QoS-related parameters to the MAC layer of the Tx UE.

[0128] After receiving the above information, for QoS-related parameter #1, the MAC layer of the UE may maintain a first set of SL DRX timers for SL DRX configuration #1, for QoS-related parameter #2, the MAC layer of the UE may maintain a second set of SL DRX timers for SL DRX configuration #2, and for QoS-related parameter #3, the MAC layer may maintain a third set of SL DRX timers for SL DRX configuration #3. Each set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, etc.

[0129] In embodiment II-5, to distinguish packets having different QoS-related parameters, each packet in a logical channel is labeled with a corresponding QoS-related parameter. In one embodiment of the present application, labeling the packet may include adding the corresponding QoS-related parameter in a header of the packet. In another embodiment of the present application, labeling the packet may be achieved by an implementation of the UE, for example, by internal shingling within the UE.

[0130] In step 305, after determining the one or more SL DRX configurations, transmitting the SL data may further include: a MAC layer of the Tx UE obtaining one or more packets of the SL data, each of the one or more packets being labeled with a QoS-related parameter; the MAC layer of the Tx UE selecting one or more LCHs during execution of an LCP procedure, each LCH of the one or more LCHs containing a packet, and the SL DRX configurations associated with the packets of the one or more SL DRX configurations being within an active time.

[0131] Whether the SL DRX configuration associated with a packet is within the active time may be determined based on a QoS-related parameter labeled with the packet, i.e., since each packet is labeled with a QoS-related parameter, if the SL DRX configuration set for the QoS-related parameter is within the active time, it may be determined that the SL DRX configuration associated with the packet labeled with the QoS-related parameter is within the active time.

[0132] The procedure for selecting one or more LCHs may be performed as follows: First, the Tx UE selects an LCH with the highest priority from all LCHs containing packets whose associated SL DRX configurations are in the active time; then, the Tx UE may determine an L2 destination ID associated with the LCH based on a mapping relationship between the destination ID and one or more LCHs. After determining the L2 destination ID, the Tx UE may select one or more LCHs associated with the L2 destination IDs containing packets whose associated SL DRX configurations are in the active time. An SL DRX configuration being in the active time may refer to at least one SL DRX timer of a set of SL DRX timers of the SL DRX configuration being running (e.g., at least one of an on-duration timer, an inactivity timer, and a HARQ retransmission timer is running), or the SL DRX configuration being within one or more time ranges or time periods defined as SL DRX active times.

[0133] In step 304, the Rx UE may perform the same operations as those performed by the Tx UE in step 303. That is, in step 304, after receiving multiple SL DRX configurations configured based on the QoS-related parameters, the RRC layer of the Rx UE may determine one or more SL DRX configurations for the MAC layer, which may include: The RRC layer of the Rx UE may indicate a mapping relationship between the QoS-related parameters and the SL DRX configurations to the MAC layer.

[0134] After receiving the mapping relationship between the QoS-related parameters and the SL DRX configuration, for each QoS-related parameter, the MAC layer of the Rx UE may maintain a set of SL DRX timers. In some embodiments of the present application, the set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, and any other timers specified in a 3GPP standard document.

[0135] In step 306, the Rx UE may receive SL data based on an active time derived in each of the one or more SL DRX configurations. In some embodiments of the present application, receiving SL data may further include monitoring SCI when an SL DRX configuration associated with a QoS-related parameter of the one or more SL DRX configurations is in the active time. An SL DRX configuration being in the active time may refer to at least one SL DRX timer of a set of SL DRX timers of the SL DRX configuration being running (e.g., at least one of an on-duration timer, an inactivity timer, and a HARQ retransmission timer is running), or the SL DRX configuration being within one or more time ranges or time periods defined as SL DRX active times. In other words, the Rx UE monitors SCI when at least one SL DRX timer of a set of SL DRX timers of the SL DRX configuration associated with the QoS-related parameter is running. In one embodiment of the present application, the Rx UE wakes up to monitor SCI during the active times of all of the one or more SL DRX configurations.

[0136] Embodiment III According to some embodiments of the present application, multiple SL DRX configurations may be configured based on an SLRB, an RLC bearer, or an LCH. That is, each SLRB, RLC bearer, or LCH may be associated with one SL DRX configuration among multiple SL DRX configurations. In embodiment III, an SLRB may be associated with an RLC bearer, and an RLC bearer may be associated with an LCH, so that an SL DRX configuration configured for an SLRB may be considered to be configured for an RLC bearer or an LCH, and vice versa.

[0137] Embodiment III-1 In embodiment III-1, all of the multiple SL DRX configurations may be used for the MAC layer of a UE (eg, a Tx UE or an Rx UE).

[0138] As a result, for a Tx UE, determining one or more SL DRX configurations for the MAC layer in step 303 may include the MAC layer of the Tx UE determining the one or more SL DRX configurations for the MAC layer to be multiple SL DRX configurations. Each SLRB, RLC bearer, or LCH may be associated with one SL DRX configuration of the multiple SL DRX configurations. Then, for each SLRB, RLC bearer, or LCH, the MAC layer of the Tx UE may maintain a set of SL DRX timers for the SL DRX configuration configured for the SLRB, RLC bearer, or LCH.

[0139] In some embodiments of the present application, the set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, and any other timers specified in a 3GPP standard document.

[0140] For example, it is assumed that the multiple SL DRX configurations include two SL DRX configurations (e.g., SL DRX configuration #1 and SL DRX configuration #2), where SL DRX configuration #1 is configured for SLRB #1, RLC bearer #1, or LCH #1, and SL DRX configuration #2 is configured for SLRB #2, RLC bearer #2, or LCH #2. After obtaining the two SL DRX configurations, the MAC layer of the UE (e.g., Tx UE or Rx UE) may determine the two SL DRX configurations for the MAC layer. For SLRB #1, RLC bearer #1, or LCH #1, the MAC layer of the UE may maintain a first set of SL DRX timers (including at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, etc.). For SLRB#1, RLC bearer#1, or LCH#1, the MAC layer of the UE may maintain a second set of SL DRX timers (including at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, etc.).

[0141] In step 305, after determining one or more SL DRX configurations, transmitting SL data may further include: a MAC layer of the Tx UE selecting one or more LCHs during an LCP procedure, and an SL DRX configuration associated with each LCH of the one or more LCHs being within an active time. The procedure for selecting one or more LCHs may be the same as in embodiment II-1.

[0142] The Rx UE may perform the same operations in step 304 as those performed by the Tx UE in step 303. That is, the MAC layer of the Rx UE may determine one or more SL DRX configurations for the MAC layer to be multiple SL DRX configurations. For each SLRB, RLC bearer, or LCH, the MAC layer of the Rx UE may maintain a set of SL DRX timers for the SL DRX configurations configured for the SLRB, RLC bearer, or LCH.

[0143] In step 306, the Rx UE may receive SL data based on an active time derived for each of the one or more SL DRX configurations. In some embodiments of the present application, receiving SL data may further include monitoring SCI when an SL DRX configuration associated with an SLRB, an RLC bearer, or an LCH or an LCH of the one or more SL DRX configurations is within the active time. An SL DRX configuration being within the active time may refer to at least one SL DRX timer of a set of SL DRX timers of the SL DRX configuration being running, or the SL DRX configuration being within one or more time ranges or time periods defined as SL DRX active times. In other words, the Rx UE monitors SCI when at least one SL DRX timer of a set of SL DRX timers of an SL DRX configuration associated with an SLRB, an RLC bearer, or an LCH is running. In one embodiment of the present application, the Rx UE wakes up to monitor SCI during the active times of all of the one or more SL DRX configurations.

[0144] Embodiment III-2 In embodiment III-2, after receiving multiple SL DRX configurations configured based on SLRBs, RLC bearers, or LCHs, in step 303, the RRC layer of the Tx UE may determine one or more SL DRX configurations for the MAC layer, including: For each L2 destination ID, the RRC layer of the Tx UE may determine (or derive) one SL DRX configuration from at least one SL DRX configuration associated with the corresponding L2 destination ID of the multiple SL DRX configurations based on a predefined rule. The specific procedure may be as follows:

[0145] First, as illustrated in Figure 2, at least one SLRB, RLC bearer, or LCH is mapped to an L2 destination ID, and therefore the RRC layer may determine that at least one SL DRX configuration configured for the at least one SLRB, RLC bearer, or LCH can be used for the corresponding L2 destination ID. As a result, for each L2 destination ID, the RRC layer may determine at least one SL DRX configuration.

[0146] After determining at least one SL DRX configuration for each L2 destination ID, the RRC layer of the Tx UE may further determine one SL DRX configuration from the at least one SL DRX configuration for each L2 destination ID based on a predefined rule, where the predefined rule may define how to combine the at least one SL DRX configuration for each L2 destination ID or how to select one SL DRX configuration from the at least one SL DRX configuration for each L2 destination ID.

[0147] In one embodiment of the present application, the SL DRX configuration having the minimum periodicity of at least one SL DRX configuration may be derived as the final SL DRX configuration for the L2 destination ID. In another embodiment of the present application, the SL DRX period of the SL DRX configuration using the minimum periodicity of the at least one SL DRX configuration may be derived as the final SL DRX configuration for the L2 destination ID. In yet another embodiment of the present application, the SL DRX timer of the SL DRX configuration using the maximum value of the at least one SL DRX configuration may be derived as the final SL DRX configuration for the L2 destination ID. It is contemplated that any other predefined rule may be used to determine the final SL DRX configuration for the L2 destination ID.

[0148] After determining at least one SL DRX configuration for each L2 destination ID, the RRC layer may indicate one SL DRX configuration for each L2 destination ID to the MAC layer. Then, for each L2 destination ID, the MAC layer of the Tx UE may maintain one set of SL DRX timers. In some embodiments of the present application, the set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, and any other timers specified in 3GPP standard documents.

[0149] In step 305, after determining the one or more SL DRX configurations, transmitting the SL data may further include: the MAC layer of the Tx UE selecting an L2 destination ID during an LCP procedure, and the SL DRX configurations associated with the L2 destination IDs of the one or more SL DRX configurations are within an active time. The procedure for selecting an L2 destination ID in embodiment III-2 may be the same as the procedure performed in embodiment I.

[0150] In step 304, the Rx UE may perform the same operations as those performed by the Tx UE in step 303. That is, for each L2 destination ID, the RRC layer of the Rx UE may determine one SL DRX configuration from at least one SL DRX configuration of multiple SL DRX configurations associated with the corresponding L2 destination ID based on a predefined rule. The predefined rule used by the Rx UE may be the same as the route used by the Tx UE.

[0151] After determining one SL DRX configuration for each L2 destination ID, the RRC layer of the Rx UE may indicate one SL DRX configuration for each L2 destination ID to the MAC layer of the Rx UE. Then, for each L2 destination ID, the MAC layer of the Rx UE may maintain one set of SL DRX timers. In some embodiments of the present application, the set of SL DRX timers may include at least one of an on-duration timer, an inactivity timer, a HARQ RTT timer, a HARQ retransmission timer, and any other timers specified in 3GPP standard documents.

[0152] In step 306, the Rx UE may receive SL data based on an active time derived for each of the one or more SL DRX configurations. In some embodiments of the present application, receiving SL data may further include monitoring SCI when an SL DRX configuration associated with an L2 destination ID of the one or more SL DRX configurations is within the active time. An SL DRX configuration being within the active time may refer to at least one SL DRX timer of a set of SL DRX timers of the SL DRX configuration being running, or the SL DRX configuration being within one or more time ranges or time periods defined as SL DRX active times. In other words, the Rx UE monitors SCI when at least one SL DRX timer of a set of SL DRX timers of the SL DRX configuration associated with the L2 destination ID is running. In one embodiment of the present application, the Rx UE wakes up to monitor SCI during the active times of all of the one or more SL DRX configurations.

[0153] 4 is a simplified block diagram of an example apparatus 400 for SL communication according to some embodiments of the present application. The apparatus 400 may include a UE (e.g., a Tx UE 102a or an Rx UE 102b) or a BS 101 as shown in FIG.

[0154] 4 , the apparatus 400 may include at least one non-transitory computer-readable medium 402, at least one receiving circuit 404, at least one transmitting circuit 406, and at least one processor 408. In some embodiments of the present application, the at least one receiving circuit 404 and the at least one transmitting circuit 406 may be integrated into at least one transceiver. The at least one non-transitory computer-readable medium 402 may have computer-executable instructions stored thereon. The at least one processor 408 may be coupled to the at least one non-transitory computer-readable medium 402, the at least one receiving circuit 404, and the at least one transmitting circuit 406. While shown coupled to each other via the at least one processor 408 in the example of FIG. 4 , the at least one receiving circuit 404, the at least one transmitting circuit 406, the at least one non-transitory computer-readable medium 402, and the at least one processor 408 may be coupled to each other in various arrangements. For example, the at least one receiving circuit 404, the at least one transmitting circuit 406, the at least one non-transitory computer-readable medium 402, and the at least one processor 408 may be coupled to one another via one or more local buses (not shown for simplicity). Computer-executable instructions stored on the at least one non-transitory computer-readable medium 402 may be programmed to perform a method using the at least one receiving circuit 404, the at least one transmitting circuit 406, and the at least one processor 408. The method may include acts or steps such as those shown in FIG.

[0155] The methods according to the embodiments of the present application may be implemented on a programmed processor. However, the controller, flowcharts, and modules may also be implemented in hardware electronic or logical circuits, such as a general-purpose or special-purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, integrated circuits, discrete element circuits, programmable logic devices, or the like. In general, any device on which a finite state machine capable of implementing the flowcharts shown in the figures exists may be used to implement the processor functions of the present application. For example, one embodiment of the present application provides an apparatus for SL communication, comprising a processor and a memory. Computer programmable instructions for implementing the method for SL communication are stored in the memory, and the processor is configured to execute the computer programmable instructions to implement the method for SL communication. The method may be the method described above or another method according to the embodiments of the present application.

[0156] An alternative embodiment preferably implements a method according to an embodiment of the present application on a non-transitory computer-readable storage medium storing computer-programmable instructions. The instructions are preferably executed by a computer-executable component integrated with the network security system. The non-transitory computer-readable storage medium may be stored in any suitable computer-readable medium, such as RAM, ROM, flash memory, EEPROM, an optical storage device (CD or DVD), a hard drive, a floppy drive, or any suitable device. The computer-executable component is preferably a processor, although the instructions may alternatively or additionally be executed by any suitable dedicated hardware device. For example, one embodiment of the present application provides a non-transitory computer-readable storage medium on which computer-programmable instructions are stored. The computer-programmable instructions are configured to implement a method for SL communication as described above or other methods according to an embodiment of the present application.

[0157] While the present application has been described with specific embodiments thereof, it may be apparent that many alternatives, modifications, and variations will be apparent to those skilled in the art. For example, various components of the embodiments may be interchanged, added, or substituted in other embodiments. Also, not all elements in each figure are necessary for the operation of the disclosed embodiments. For example, one skilled in the art can make and use the teachings of the present application by simply employing the elements of the independent claims. Accordingly, the embodiments of the present application described herein are intended to be illustrative, not limiting. Various modifications may be made without departing from the spirit and scope of the present application. [Explanation of symbols]

[0158] 100 Wireless Communication System 101 Base station (BS) 102UE 102a UE 102b UE 400 equipment 402 Non-transitory computer-readable medium 404 receiving circuit 406 Transmission Circuit 408 processors

Claims

1. 1. A user equipment (UE) for wireless communications, comprising: at least one memory; at least one processor coupled to said at least one memory; and wherein the at least one processor causes the UE to: obtaining a plurality of sidelink (SL) discontinuous reception (DRX) configurations for sidelink (SL) communication, the plurality of SL DRX configurations being configured based on a layer 2 (L2) destination identity (ID); selecting one or more SL DRX configurations from the plurality of SL DRX configurations for a medium access control (MAC) layer of the UE; and When there is SL data associated with DRX in the UE, transmitting the SL data from the UE based on an active time derived in each of the one or more SL DRX configurations; the active time is determined based on a SL DRX configuration; an SL DRX period of an SL DRX configuration using a minimum periodicity is selected as the SL DRX configuration for the L2 destination ID; or An SL DRX timer of an SL DRX configuration using the maximum value of at least one SL DRX configuration is selected as the SL DRX configuration for the L2 destination ID. At least one of the UE.

2. The UE of claim 1 , wherein the plurality of SL DRX configurations are configured based on a quality of service (QoS) related parameter.

3. The at least one processor, in the UE, 3. The UE of claim 2, configured to cause a radio resource control (RRC) layer of the UE to determine, for each logical channel, at least one SL DRX configuration from the plurality of SL DRX configurations based on a mapping relationship between a QoS-related parameter and a sidelink radio bearer (SLRB) and a mapping relationship between the SLRB and the logical channel, thereby causing the MAC layer to determine the one or more SL DRX configurations.

4. The at least one processor further comprising:

4. The UE of claim 3, configured to cause the RRC layer to determine, for each logical channel, one or more SL DRX configurations for the MAC layer by determining, in the RRC layer, one SL DRX configuration from the at least one SL DRX configuration based on a predefined rule.

5. The at least one processor further comprising:

5. The UE of claim 3 or 4, configured to transmit the SL data by selecting one or more logical channels during a Logical Channel Prioritization (LCP) procedure, wherein an SL DRX configuration associated with each logical channel of the one or more logical channels is within the active time.

6. The at least one processor, in the UE, 3. The UE of claim 2, configured to cause an RRC layer of the UE to determine, for each L2 destination ID, the one or more SL DRX configurations for the MAC layer by determining at least one SL DRX configuration from the plurality of SL DRX configurations based on a mapping relationship between a QoS-related parameter and an L2 destination ID.

7. The at least one processor further comprising:

7. The UE of claim 6, configured to cause the RRC layer to determine, for each L2 destination ID, one or more SL DRX configurations for the MAC layer by determining, in the RRC layer, one SL DRX configuration from the at least one SL DRX configuration based on a predefined rule.

8. The at least one processor further comprising:

8. The UE of claim 6 or 7, configured to transmit the SL data by selecting an L2 destination ID during an LCP procedure, wherein an SL DRX configuration associated with the L2 destination ID of the one or more SL DRX configurations is within the active time.

9. 1. A user equipment (UE) for wireless communications, comprising: at least one memory; at least one processor coupled to said at least one memory; and wherein the at least one processor causes the UE to: obtaining a plurality of sidelink (SL) discontinuous reception (DRX) configurations for sidelink (SL) communication, the plurality of SL DRX configurations being configured based on a layer 2 (L2) destination identity (ID); selecting one or more SL DRX configurations from the plurality of SL DRX configurations for a medium access control (MAC) layer of the UE; and receiving SL data based on an active time derived in each of the one or more SL DRX configurations; the active time is determined based on a SL DRX configuration; an SL DRX period of an SL DRX configuration using a minimum periodicity is selected as the SL DRX configuration for the L2 destination ID; or An SL DRX timer of an SL DRX configuration using the maximum value of at least one SL DRX configuration is selected as the SL DRX configuration for the L2 destination ID. At least one of the UE.

10. A method for wireless communications performed by a user equipment (UE), comprising: obtaining a plurality of sidelink (SL) discontinuous reception (DRX) configurations for sidelink (SL) communication, the plurality of SL DRX configurations being configured based on a layer 2 (L2) destination identity (ID); selecting one or more SL DRX configurations from the plurality of SL DRX configurations for a Medium Access Control (MAC) layer of the UE; If there is SL data associated with DRX in the UE, transmitting the SL data from the UE based on an active time derived in each of the one or more SL DRX configurations; wherein the active time is determined based on a SL DRX configuration; an SL DRX period of an SL DRX configuration using a minimum periodicity is selected as the SL DRX configuration for the L2 destination ID; or An SL DRX timer of an SL DRX configuration using the maximum value of at least one SL DRX configuration is selected as the SL DRX configuration for the L2 destination ID. The method is at least one of:

11. A method for wireless communications performed by a user equipment (UE), comprising: obtaining a plurality of sidelink (SL) discontinuous reception (DRX) configurations for sidelink (SL) communication, the plurality of SL DRX configurations being configured based on a layer 2 (L2) destination identity (ID); selecting one or more SL DRX configurations from the plurality of SL DRX configurations for a Medium Access Control (MAC) layer of the UE; receiving SL data based on an active time derived in each of the one or more SL DRX configurations; wherein the active time is determined based on a SL DRX configuration; an SL DRX period of an SL DRX configuration using a minimum periodicity is selected as the SL DRX configuration for the L2 destination ID; or An SL DRX timer of an SL DRX configuration using the maximum value of at least one SL DRX configuration is selected as the SL DRX configuration for the L2 destination ID. The method is at least one of:

12. A processor for wireless communication by a user equipment (UE), comprising: The processor causes the UE to: obtaining a plurality of sidelink (SL) discontinuous reception (DRX) configurations for sidelink (SL) communication, the plurality of SL DRX configurations being configured based on a layer 2 (L2) destination identity (ID); selecting one or more SL DRX configurations from the plurality of SL DRX configurations for a medium access control (MAC) layer of the UE; and When there is SL data associated with DRX in the UE, transmitting the SL data from the UE based on an active time derived in each of the one or more SL DRX configurations; the active time is determined based on a SL DRX configuration; an SL DRX period of an SL DRX configuration using a minimum periodicity is selected as the SL DRX configuration for the L2 destination ID; or An SL DRX timer of an SL DRX configuration using the maximum value of at least one SL DRX configuration is selected as the SL DRX configuration for the L2 destination ID. a processor, which is at least one of:

13. A processor for wireless communication by a user equipment (UE), comprising: The processor causes the UE to: obtaining a plurality of sidelink (SL) discontinuous reception (DRX) configurations for sidelink (SL) communication, the plurality of SL DRX configurations being configured based on a layer 2 (L2) destination identity (ID); selecting one or more SL DRX configurations from the plurality of SL DRX configurations for a medium access control (MAC) layer of the UE; and receiving SL data based on an active time derived in each of the one or more SL DRX configurations; the active time is determined based on a SL DRX configuration; an SL DRX period of an SL DRX configuration using a minimum periodicity is selected as the SL DRX configuration for the L2 destination ID; or An SL DRX timer of an SL DRX configuration using the maximum value of at least one SL DRX configuration is selected as the SL DRX configuration for the L2 destination ID. a processor, which is at least one of:

Images