Method and Device for Sidelink DRX Alignment

Abstract

Embodiments of the present application relate to a method and apparatus for sidelink DRX alignment. An exemplary method includes: obtaining configuration information indicating at least one DRX configuration of data, where the at least one DRX configuration is associated with a first resource pool; and transmitting or receiving the data based on the at least one DRX configuration indicated by the configuration information. Embodiments of the present application can minimize the power consumption of a UE and ensure data transmission between UEs.

Description

Technical Field

[0001] Embodiments of the present application generally relate to wireless communication technologies, and in particular, to methods and devices for sidelink (SL) discontinuous reception (DRX) alignment. Background Art

[0002] In the RAN#86 meeting, a sidelink enhancement work item was agreed upon. The need to enhance the sidelink has been identified. For vehicle-to-everything (V2X) and public safety, due to time constraints, service requirements and operation scenarios are not fully supported in Release 16 (R16).

[0003] Energy conservation enables user equipment (UE) with battery constraints to perform sidelink operations in a power-efficient manner. The NR sidelink in R16 is designed based on the assumption of "always on" when the UE operates the sidelink, for example, only focusing on UEs installed in vehicles with sufficient battery capacity. The energy conservation solution in Release 17 (R17) is needed for vulnerable road users (VRUs) in V2X use cases and UEs in public safety and commercial use cases where power consumption in the UE needs to be minimized.

[0004] Therefore, one goal of energy conservation in R17 is achieved by performing sidelink DRX. DRX refers to an operating mode for saving power consumption of the UE. For example, generally, in the DRX mode, the UE alternates between an active state and a dormant state (or an inactive state). The UE turns on the receiver only when it is in the active state to monitor and receive control information or data, and turns off the receiver when it is in the dormant state to stop receiving control information or data.

[0005] Alignment between sidelink UEs for DRX is important so that data is not lost at the receiving (Rx) UE and power consumption at the Rx UE can be minimized. Therefore, the industry expects an improved technology for sidelink DRX alignment between UEs communicating with each other. Summary of the Invention

[0006] Some embodiments of the present application at least provide a technical solution for sidelink DRX alignment.

[0007] According to some embodiments of the present application, a method for wireless communication performed by a UE may include: obtaining configuration information indicating at least one sidelink DRX configuration for data on a sidelink, wherein the at least one sidelink DRX configuration is associated with a first resource pool; and transmitting or receiving the data based on the at least one sidelink DRX configuration indicated by the configuration information.

[0008] According to some other embodiments of the present application, a method for wireless communication performed by a base station (BS) may include: transmitting configuration information indicating at least one sidelink DRX configuration for data on a sidelink, where the at least one sidelink DRX configuration is associated with a first resource pool.

[0009] Some embodiments of the present application also provide an apparatus, including: at least one non-transitory computer-readable medium storing computer-executable instructions; at least one receiver; at least one transmitter; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiver, and the at least one transmitter. The computer-executable instructions are programmed to implement any of the methods described above using the at least one receiver, the at least one transmitter, and the at least one processor.

[0010] Embodiments of the present application provide a technical solution for sidelink DRX alignment, such that data is not lost at the Rx UE, and power consumption at the Rx UE can be minimized. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] To describe the manner in which the advantages and features of the present application can be obtained, a description of the present application is presented by reference to specific embodiments of the present application illustrated in the accompanying drawings. These drawings only depict exemplary embodiments of the present application and should not be considered as limiting its scope.

[0012] Figure 1 is a schematic diagram illustrating an exemplary wireless communication system 100 according to some embodiments of the present application;

[0013] Figure 2 is a flowchart illustrating a method for sidelink DRX alignment according to some embodiments of the present application;

[0014] Figures 3(a) to 3(e) respectively illustrate exemplary instances of at least one sidelink DRX configuration according to some embodiments of the present application;

[0015] Figures 4(a) to 4(b) respectively illustrate exemplary instances of resource selection according to some embodiments of the present application; and

[0016] Figure 5 illustrates a simplified block diagram of an apparatus for sidelink DRX alignment according to some embodiments of the present application. DETAILED DESCRIPTION

[0017] The detailed description of the drawings is intended as a description of the presently preferred embodiments of the present application and is not intended to represent the only form in which the present application may be practiced. It is to be understood that the same or equivalent functions may be achieved by different embodiments that are intended to be covered within the spirit and scope of the present application.

[0018] Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the drawings. For the sake of promoting understanding, the embodiments are provided under a specific network architecture and new service scenarios (such as 3GPP 5G, 3GPP LTE Release 8, etc.). It is well understood by those skilled in the art that as the network architecture and new service scenarios evolve, the embodiments in the present application are also applicable to similar technical problems.

[0019] Figure 1 is a schematic diagram illustrating an exemplary wireless communication system 100 according to an embodiment of the present application.

[0020] As Figure 1 shown, the wireless communication system 100 includes at least one UE 101 and at least one BS 102. Specifically, for illustrative purposes, the wireless communication system 100 includes two UEs 101 (e.g., UE 101a and UE 101b) and one BS 102. Although a specific number of UEs 101 and BS 102 are depicted in Figure 1 it is contemplated that any number of UEs 101 and BS 102 may be included in the wireless communication system 100.

[0021] According to some embodiments of the present application, the UE 101 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including security cameras), an in-vehicle computer, a network device (e.g., a router, a switch, and a modem), etc. According to some embodiments of the present application, the UE 101 may include a portable wireless communication device, a smart phone, a cellular phone, a flip phone, a device with a subscriber identity module, a personal computer, a selective call receiver, or any other device capable of transmitting and receiving communication signals over a wireless network.

[0022] According to some embodiments of the present application, the UE 101 may include a power - sensitive vehicle UE (V - UE), a vulnerable road user (VRU), a public safety UE (PS - UE), and / or a commercial sidelink UE (CS - UE). In an embodiment of the present application, the VRU may include a pedestrian UE (P - UE), a cyclist UE, a wheelchair UE, or other UEs that require power saving compared to the V - UE. According to some embodiments of the present application, the UE 101 includes a wearable device, such as a smartwatch, a fitness band, an optical head - mounted display, etc. In addition, the UE 101 may be referred to as a subscriber unit, a mobile device, 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 described using other terms used in the art. The UE 101 may communicate directly with the BS 102 via the LTE or NR Uu interface.

[0023] According to Figure 1 some embodiments of, the UE 101a serves as a transmission (Tx) UE, and the UE 101b serves as an Rx UE. The UE 101a may exchange V2X messages with the UE 101b via a sidelink (e.g., the PC5 interface defined in 3GPP TS 23.303). The UE101a may transmit information or data to other UEs within the V2X communication system via sidelink unicast, sidelink multicast, or sidelink broadcast. For example, the UE 101a transmits data to the UE 101b in a sidelink unicast session. The UE 101a may transmit data to the UE 101b and other UEs ( Figure 1 not shown in) within the multicast group via a sidelink multicast transmission session. In addition, the UE 101a may transmit data to the UE 101b and other UEs ( Figure 1 not shown in) via a sidelink broadcast transmission session. In an embodiment of the present application, the UE 101a may be a V - UE, and the UE 101b may be a VRU (e.g., a P - UE or a cyclist UE) or a PS - UE or a CS - UE.

[0024] Alternatively, according to Figure 1 some other embodiments of, the UE 101b serves as a Tx UE and transmits V2X messages, and the UE 101a serves as an Rx UE and receives V2X messages from the UE 101b.

[0025] Figure 1In embodiments of the present application, both UE 101a and UE 101b can transmit information to BS 102 and receive control information from BS 102 via, for example, an LTE or NR Uu interface. BS 102 can be distributed over a geographical area. In certain embodiments of the present application, each of BS 102 can also be referred to as an access point, access terminal, base, basic unit, macro cell, Node B, evolved Node B (eNB), gNB, home Node B, relay node, or device, or described using other terms used in the art. BS 102 is generally part of a radio access network, which can include one or more controllers communicatively coupled to one or more corresponding BS 102.

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

[0027] In some embodiments of the present application, wireless communication system 100 is compatible with 5G NR of the 3GPP protocol, where BS102 transmits data using an OFDM modulation scheme on the downlink (DL), and UE 101 transmits data using a discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM) or cyclic prefix OFDM (CP-OFDM) scheme on the uplink (UL) or side link (SL). However, more generally, wireless communication system 100 can implement some other open or proprietary communication protocols, such as WiMAX and other protocols.

[0028] In some embodiments of the present application, BS 102 can communicate using other communication protocols, such as wireless communication protocols of the IEEE802.11 series. Further, in some embodiments of the present application, BS 102 can communicate on licensed spectrum, while in other embodiments BS 102 can communicate on unlicensed spectrum. The present application is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol. In still other embodiments of the present application, BS102 can communicate with UE 101 using the 3GPP 5G protocol.

[0029] In R17, power saving may be required for VRUs in V2X use cases and UEs in public safety and commercial use cases. In some embodiments of the present application, power saving in R17 can be achieved by performing sidelink DRX. DRX refers to an operating mode for saving the power consumption of a UE. For example, generally, in the DRX mode, the UE alternates between an active state and a dormant state (or an inactive state). The UE turns on the receiver only when it is in the active state to monitor and receive control information or data, and turns off the receiver when it is in the dormant state to stop receiving control information or data.

[0030] Alignment between sidelink UEs for DRX is important so that data at the Rx UE is not lost and the power consumption of the Rx UE can be minimized. In view of this, one of the working scopes in R17 is to specify a mechanism for aligning sidelink DRX wake-up times (or active times) between UEs that communicate with each other in a broadcast, multicast, or unicast manner. To specify the mechanism for DRX alignment, at least three problems need to be solved. For example, the first problem is how to align the sidelink DRX configurations of UEs that communicate with each other in a broadcast, multicast, or unicast manner, the second problem is how the UEs that communicate with each other know when to enable the sidelink DRX configuration and where to utilize the sidelink DRX configuration, and the third problem is what the behavior of the Tx UE is after receiving the sidelink DRX configuration.

[0031] Therefore, embodiments of the present application provide a technical solution for sidelink DRX alignment between UEs that communicate with each other in a broadcast, multicast, or unicast manner, so that data is not lost between the Tx UE and the Rx UE, and the power consumption at the Tx UE and the Rx UE can be minimized. More details about the embodiments of the present application will be described in the following text in conjunction with the drawings.

[0032] Figure 2 is a flowchart illustrating a method for sidelink DRX alignment according to some embodiments of the present application. Although the method is described at a system level by a UE and a BS (e.g., UE 101 and BS 102 as Figure 1 illustrated and shown), those skilled in the art can understand that the method implemented in the UE and the method implemented in the BS can be separately implemented and combined by other devices with similar functions.

[0033] In Figure 2 the exemplary method shown, in step 201, as Figure 1The BS 102 shown in [description] can transmit configuration information to the UE 101 (e.g., UE 101a and UE 101b). In step 202, the UE 101 can obtain the configuration information. According to some embodiments of the present application, obtaining the configuration information may include receiving the configuration information transmitted from the BS 102. In an embodiment of the present application, the configuration information may be broadcast in the system information block (SIB) of the BS 102. That is, the UE 101 can receive the configuration information in the SIB broadcast by the BS 102. In another embodiment of the present application, the configuration information may be transmitted via radio resource control (RRC) signaling. That is, the UE 101 can receive the configuration information through the RRC signaling transmitted from the BS 102. According to some other embodiments of the present application, step 201 may not be performed. In these embodiments, the configuration information may be pre-configured in the UE 101, for example, in the subscriber identity module (SIM), in the universal subscriber identity module (USIM), or in the memory of the UE 101. Therefore, obtaining the configuration information may refer to accessing the SIM, USIM, or the memory for obtaining the configuration information inside the UE.

[0034] The configuration information may indicate at least one sidelink DRX configuration for data on the sidelink. According to some embodiments of the present application, the data may be specific data. For example, the specific data may include at least one of the following data: vehicle-to-pedestrian (V2P) data, sidelink DRX-related data, power-sensitive related data, etc.

[0035] At least one sidelink DRX configuration may be associated with a first resource pool. According to some embodiments of the present application, the first resource pool may include at least one of the following: a transmission resource pool, a reception resource pool, and an exception resource pool, where the exception resource pool may be used for the handover process specified in the 3GPP standard document.

[0036] After receiving the configuration information, in step 204, the Tx UE (e.g., UE 101a) can transmit data based on at least one sidelink DRX configuration indicated by the configuration information. The Rx UE (e.g., UE 101b) can receive data based on at least one sidelink DRX configuration indicated by the configuration information.

[0037] According to some embodiments of the present application, each of the at least one sidelink DRX configurations may include at least one of the following parameters: the on-duration of the DRX; the off-duration of the DRX; the wake-up time of the DRX; one or more timers associated with the DRX; the DRX cycle; and the DRX offset value. The wake-up time may also be referred to as the active time.

[0038] In embodiments of the present application, one or more timers associated with sidelink DRX may include at least one of the following: a DRX on-duration timer (e.g., sl-drx-onDurationTimer as specified in 3GPP standard documents), a DRX inactivity timer (e.g., sl-drx-InactivityTimer as specified in 3GPP standard documents), and a DRX retransmission timer (e.g., sl-drx-RetransmissionTimer as specified in 3GPP standard documents).

[0039] In embodiments of the present application, when sidelink DRX is configured, the active time (or wake-up time) on the sidelink may include the time when one of the DRX on-duration timer for the sidelink (e.g., sl-drx-onDurationTimer as specified in 3GPP standard documents), the DRX inactivity timer for the sidelink (e.g., sl-drx-InactivityTimer as specified in 3GPP standard documents), and the DRX retransmission timer for the sidelink (e.g., sl-drx-RetransmissionTimer as specified in 3GPP standard documents) is running.

[0040] In some embodiments of the present application, at least one sidelink DRX configuration may include one sidelink DRX configuration. In these embodiments, the Tx resource pool for the Tx UE and the Rx resource pool for the Rx UE may be the same, and one sidelink DRX configuration may be associated with the Tx resource pool and the Rx resource pool.

[0041] For example, FIG. 3(a) illustrates an exemplary instance of at least one sidelink DRX configuration according to some embodiments of the present application. As shown in FIG. 3(a), the Tx resource pool for the Tx UE and the Rx resource pool for the Rx UE may be the same, and the first resource pool may be represented by resource pool 301 in FIG. 3(a), which may be a Tx resource pool or an Rx resource pool. The configuration information may indicate that one sidelink DRX configuration 302 is associated with resource pool 301. In embodiments of the present application, the sidelink DRX configuration 302 may include at least one of the following parameters: the on-duration of DRX; the off-duration of DRX (e.g., t2 as shown in FIG. 3(a)); the wake-up time of DRX (e.g., t1 as shown in FIG. 3(a)); one or more timers associated with DRX; the DRX cycle; and the DRX offset value.

[0042] Then, after receiving the configuration information, the Tx UE (e.g., UE 101a) may transmit data based on a sidelink DRX configuration 302. The Rx UE (e.g., UE 101b) may receive data based on a sidelink DRX configuration 303. For example, the Tx UE and the Rx UE may transmit and receive data during the on-duration t1 of DRX, and may not transmit or receive data during the off-duration t2 of DRX.

[0043] In some other embodiments of the present application, the configuration information may indicate that each of at least one sidelink DRX configuration is associated with one or more destination identifiers (IDs) or one or more sidelink radio bearers (RBs). Each of the one or more destination IDs may be associated with traffic having corresponding quality of service (QoS) requirements.

[0044] For example, FIG. 3(b) illustrates an exemplary instance of at least one sidelink DRX configuration according to some embodiments of the present application. As shown in FIG. 3(b), the Tx resource pool for the Tx UE and the Rx resource pool for the Rx UE may be the same, and the first resource pool may be represented by the resource pool 401 in FIG. 3(a), which may be a Tx resource pool or an Rx resource pool. The configuration information may indicate that three sidelink DRX configurations 401, 402, and 403 are associated with the resource pool 401. In an embodiment of the present application, each of the sidelink DRX configurations 402, 403, and 404 may include at least one of the following parameters: the on-duration of DRX; the off-duration of DRX (e.g., time t2, t4, or t6); the wake-up time of DRX (e.g., time t1, t3, or t5); one or more timers associated with DRX; the DRX cycle; and the DRX offset value. As shown in FIG. 3(b), the sidelink DRX configuration 402 may be associated with one destination ID (e.g., Dest#1) or one radio bearer (RB) (e.g., RB#1), the sidelink DRX configuration 403 may be associated with one destination ID (e.g., Dest#2) or one radio bearer (RB) (e.g., RB#2), and the sidelink DRX configuration 403 may be associated with one destination ID (e.g., Dest#3) or one radio bearer (RB) (e.g., RB#3).

[0045] Then, after receiving the configuration information, the Tx UE (e.g., UE 101a) and the Rx UE (e.g., UE 101b) may transmit and receive data based on at least one of the sidelink DRX configurations 402 to 404. For example, before transmitting data, the Tx UE may determine the destination ID or radio bearer associated with the data, and then transmit the data according to the sidelink DRX configuration associated with the destination ID or radio bearer.

[0046] In some other embodiments of the present application, the first resource pool may be a transmission resource pool, and at least one sidelink DRX configuration may include multiple sidelink DRX configurations. In these embodiments, after receiving the configuration information, in step 204, the Tx UE (e.g., UE 101a) may copy the data and transmit the copied data within the wake-up times of each of the multiple sidelink DRX configurations. In an embodiment of the present application, the above step 204 may be implemented through a resource selection process. For example, for data, resource selection is performed on the on-duration of each DRX and resources are reserved.

[0047] For example, FIG. 3(c) illustrates an exemplary instance of at least one sidelink DRX configuration according to some embodiments of the present application. As shown in FIG. 3(c), the first resource pool may be represented by resource pool 501 in FIG. 3(c), which may be a Tx resource pool. The configuration information may indicate that two sidelink DRX configurations 502 and 503 are associated with the resource pool 501. The sidelink DRX configuration 502 may be associated with a first Rx resource pool, and the sidelink DRX configuration 503 may be associated with a second Rx resource pool.

[0048] In an embodiment of the present application, each of the sidelink DRX configurations 502 and 503 may include at least one of the following parameters: the on-duration of the DRX; the off-duration of the DRX (e.g., times t2 and t4); the wake-up times of the DRX (e.g., times t1 and t3); one or more timers associated with the DRX; the DRX cycle; and the DRX offset value.

[0049] Then, after receiving the configuration information, the Tx UE (e.g., UE 101a) may copy the data to be transmitted and transmit the copied data at the wake-up times (e.g., times t1 and t3) of the sidelink DRX configurations 502 and 503.

[0050] In some other embodiments of the present application, at least one sidelink DRX configuration may indicate the time-frequency resources of the data. The time-frequency resources may be a part of the first resource pool. That is, at least one sidelink DRX configuration defines the on-duration of the first resource pool for transmitting and receiving specific data (e.g., V2P data, sidelink DRX-associated data, or power-sensitive-associated data). In these embodiments, after receiving the configuration information, in step 204, the Tx UE (e.g., UE 101a) and the Rx UE (e.g., UE 101b) may transmit and receive data on the time-frequency resources. In an embodiment of the present application, the time-frequency resources may be referred to as an Rx resource pool.

[0051] In embodiments of the present application, at least one sidelink DRX configuration may include at least one of the following parameters: a parameter indicating a bitmap (e.g., a new parameter sl-timeresoureceV2P similar to sl-timeresourece-r16 specified in 3GPP standard documents), the bitmap indicating time-domain resources within a first resource pool; a parameter indicating frequency-domain resources within the first resource pool (e.g., sl-StartRB-Subchannel-r16 and sl-NumSubchannel-r16 as specified in 3GPP standard documents); and a parameter indicating a resource selection window of the first resource pool (e.g., SL-SelectionWindowConfig as specified in 3GPP standard documents).

[0052] For example, FIG. 3(d) illustrates an exemplary instance of at least one sidelink DRX configuration according to some embodiments of the present application. As shown in FIG. 3(d), the first resource pool may be represented by resource pool 601 in FIG. 3(d), which may be a Tx resource pool. The configuration information may indicate that the sidelink DRX configuration 602 is associated with the resource pool 601. The sidelink DRX configuration 602 indicates time-frequency resources 603. As shown in FIG. 3(d), the time-frequency resources 603 are part of the resource pool 601.

[0053] Then, after receiving the configuration information, the Tx UE (e.g., UE 101a) and the Rx UE (e.g., UE 101b) may transmit and receive data on the time-frequency resources 603.

[0054] In some other embodiments of the present application, the BS may configure separate tx and rx resource pools for transmitting and receiving specific data (e.g., V2P data, sidelink DRX-associated data, or power-sensitive-associated data). In these embodiments, at least one sidelink DRX configuration indicates a second resource pool different from the first resource pool. When the Tx UE (e.g., UE101a) needs to transmit data (e.g., a transmission block), the Tx UE will first check whether it is specific data. In the case where the data to be transmitted is specific data, the Tx UE may select the second resource pool for transmitting the data. Correspondingly, the Rx UE (e.g., UE 101b) may receive the data on the second resource pool.

[0055] For example, FIG. 3(e) illustrates an exemplary instance of at least one sidelink DRX configuration according to some embodiments of the present application. As shown in FIG. 3(e), the first resource pool may be represented by resource pool 701 in FIG. 3(d). The configuration information may indicate that the sidelink DRX configuration 702 is associated with the resource pool 701. The sidelink DRX configuration 702 indicates a second resource pool 703 for specific data. In embodiments of the present application, both resource pools 701 and 703 are Tx resource pools. In another embodiment of the present application, both resource pools 701 and 703 are Rx resource pools.

[0056] Then, after receiving the configuration information, when a Tx UE (e.g., UE 101a) needs to transmit data, the Tx UE will first check whether it is specific data. In the case where the data to be transmitted is specific data, the Tx UE may select the resource pool 703 for transmitting the data. Correspondingly, an Rx UE (e.g., UE 101b) may receive the data on the resource pool 703.

[0057] In some other embodiments of the present application, UEs may communicate with each other in a multicast manner. That is, each UE may belong to a group that includes at least one UE. In these embodiments, the configuration information may indicate that each of at least one sidelink DRX configuration is associated with a group of UEs. Then, after receiving the configuration information, when a Tx UE (e.g., UE 101a) needs to transmit data, the Tx UE will first check the group to which it belongs, and then transmit the data based on the sidelink DRX configuration associated with the group. Similarly, an Rx UE (e.g., UE 101b) may receive the data based on the sidelink DRX configuration associated with the group to which the Rx UE belongs.

[0058] In some other embodiments of the present application, the configuration information may indicate a mapping relationship between at least one sidelink DRX configuration and at least one destination identifier (ID). That is, the BS may indicate to the UE which destination id's data will be configured with sidelink DRX. Then, after receiving the configuration information, when a Tx UE (e.g., UE 101a) needs to transmit data, the Tx UE will first check whether the data is related to the destination ID associated with the sidelink DRX configuration. In the case where the data is related to the destination ID associated with the sidelink DRX configuration, the Tx UE may transmit the data based on the sidelink DRX configuration associated with the destination ID.

[0059] In some other embodiments of the present application, the configuration information may indicate a mapping relationship between at least one sidelink DRX configuration and at least one sidelink radio bearer (SLRB). That is, the BS may indicate to the UE which SLRB(s)' data will be configured with sidelink DRX. Then, after receiving the configuration information, when the Tx UE (e.g., UE 101a) needs to transmit data, the Tx UE will first check whether the data is related to the SLRB associated with the sidelink DRX configuration. In the case where the data is related to the SLRB associated with the sidelink DRX configuration, the Tx UE may transmit the data based on the sidelink DRX configuration associated with the SLRB.

[0060] In the prior art, before transmitting data, the Tx UE (e.g., UE 101a) may perform a resource selection or reselection process to select a resource for transmitting the data. However, the existing resource selection or reselection process does not consider the sidelink DRX configuration.

[0061] In some embodiments of the present application, specific data configured with DRX is adopted. For the specific data configured with DRX, the Tx UE may trigger the resource selection or reselection process only during the wake-up time of the DRX. That is, in these embodiments, before performing the resource selection or resource reselection for transmitting data, the Tx UE may check whether the conditions are met in the media access control (MAC) of the Tx UE. The conditions may include: the data is the data configured with the sidelink DRX configuration (or specific data), and the Tx UE is in the wake-up time of the sidelink DRX configuration. Once the conditions are met, the UE may perform the resource selection or resource reselection for transmitting data.

[0062] According to an embodiment of the present application, the resource (re)selection process described in TS 38.321 may be changed. Specifically, the underlined (added) paragraphs in the following sections illustrate the changes to the resource (re)selection process described in TS 38.321.

[0063] 1> If the data is specific data associated with DRX, if the side - link DRX function is configured or re - configured by the upper layer, and if the UE is in the SL active time of DRX; 2> If the destination is related to the data transmission associated with the side - link DRX configuration (or specific data transmission), and the UE is in the active time (or wake - up time) of the side - link DRX configuration.

[0064] 2> Clear the configured sidelink authorization associated with the sidelink process (if available);

[0065] 2> Trigger TX resource (re)selection.

[0066] In some embodiments of the present application, for data associated with the sidelink DRX configuration (e.g., specific data), the Tx UE may determine the resources for transmitting the data based on the wake-up time (or active time) of the sidelink DRX configuration. In an embodiment of the present application, the Tx UE may select the resources for transmitting specific data only during the sidelink DRX wake-up time. In other words, the available resources for transmitting specific data are determined only during the sidelink DRX active time.

[0067] For example, FIG. 4(a) illustrates an exemplary instance of resource selection according to some embodiments of the present application. As shown in FIG. 4(a), the configuration information may indicate that the sidelink DRX configuration 801 is for the data. For example, the data may be specific data (e.g., V2P data, sidelink DRX associated data, or power-sensitive associated data). Then, at a specific time T0, the Tx UE may have data (e.g., TB) to transmit. When determining the available resources for transmitting the data, the Tx UE may determine the resources within the time interval [n + T1, n + T2] as the available resources for transmitting the data, where n is the time when the higher layer triggers the resource selection, or the time slot in which the higher layer provides parameters for this physical sidelink shared channel (PSSCH) / physical sidelink control channel (PSCCH) transmission.

[0068] T1 may be determined by the MAC layer of the Tx UE based on the wake-up time of the sidelink DRX configuration 801 (e.g., t1 as shown in FIG. 4(a)). As shown in FIG. 4(a), T0 is within the wake-up time t1 of the sidelink DRX configuration 801, and thus the Tx UE may determine T1 as T0. T2 may be determined based on the remaining packet delay budget and the wake-up time of the sidelink DRX configuration 801 (e.g., t1 as shown in FIG. 4(a)). For example, T2 may be the smaller of the above two values. Referring to FIG. 4(a), the remaining packet delay budget is greater than the wake-up time of the sidelink DRX configuration 801, and the Tx UE may determine T2 as the wake-up time of the sidelink DRX configuration 801.

[0069] FIG. 4(b) illustrates another exemplary instance of resource selection according to some embodiments of the present application. As shown in FIG. 4(b), the configuration information may indicate that the sidelink DRX configuration 901 is for the data. For example, the data may be specific data (e.g., V2P data, sidelink DRX associated data, or power-sensitive associated data). Then, at a specific time T0, the Tx UE has data (e.g., TB) to transmit. When determining the available resources for transmitting the data, the Tx UE may determine the resources within the time interval [n + T1, n + T2] as the available resources for transmitting the specific data, where n may refer to the number of subframes.

[0070] T1 can be determined by the MAC layer of the Tx UE based on the wake-up time of the sidelink DRX configuration 801 (e.g., t1 as shown in FIG. 4(b)). As shown in FIG. 4(b), T0 is before the wake-up time t1 of the sidelink DRX configuration 801. Thus, the Tx UE can determine T1 as the start point of the wake-up time t1. T2 can be determined based on the remaining packet delay budget and the wake-up time of the sidelink DRX configuration 801 (e.g., t1 as shown in FIG. 4(b)). For example, T2 can be the smaller of the above two values. Referring to FIG. 4(b), the remaining packet delay budget is less than the wake-up time t1 of the sidelink DRX configuration 801, and thus T2 can be determined as the remaining packet delay budget.

[0071] In some embodiments of the present application, during the logical channel prioritization (LCP) process, the Tx UE can select only destinations related to a specific data transmission. For example, during destination selection in LCP, when the UE is in the active time of DRX, the UE selects only destinations related to a specific data transmission. In these embodiments, during the logical channel prioritization (LCP) process, the Tx UE can select a destination when the destination is related to the data associated with the sidelink DRX configuration and the UE is in the wake-up time of the sidelink DRX configuration.

[0072] According to embodiments of the present application, the LCP process described in TS 38.321 can be changed. Specifically, the underlined (added) paragraphs in the following sections illustrate the changes to the LCP process described in TS 38.321.

[0073] · The MAC entity shall perform the following operations for each sidelink control information (SCI) corresponding to a new transmission:

[0074] 1> Select the destination of the logical channel or MAC CE (if any) with the highest priority among the logical channels and MAC CEs (if any) associated with the SL grant related to the SCI and associated with one of unicast, multicast, and broadcast that satisfy all of the following conditions:

[0075] 2> SL data is available for transmission; and

[0076] 2> In the presence of any logical channel with SBj > 0, SBj > 0; and

[0077] 2> When the SL grant is of the configured grant type 1, sl-configuredSLGrantType1Allowed (if configured) is set to true; and

[0078] Figure 5 Figure 1

[0079] Figure 5 Simplified block diagram of a device 500 for sidelink DRX alignment according to some embodiments of the present application. The device 500 can be a BS 102 or a UE 101 (e.g., UE 101a or UE 101b) as shown in Figure 2 .

[0080] Referring to ​ , the device 500 can include at least one non-transitory computer-readable medium 502, at least one receiving circuitry 504, at least one transmitting circuitry 506, and at least one processor 508. In some embodiments of the present application, the at least one receiving circuitry 504 and the at least one transmitting circuitry 506 are integrated into at least one transceiver. The at least one non-transitory computer-readable medium 502 can have computer-executable instructions stored therein. The at least one processor 508 can be coupled to the at least one non-transitory computer-readable medium 502, the at least one receiving circuitry 504, and the at least one transmitting circuitry 506. The computer-executable instructions can be programmed to implement a method using the at least one receiving circuitry 504, the at least one transmitting circuitry 506, and the at least one processor 508. The method can be a method according to an embodiment of the present application, e.g., the method shown in ​ .

[0081] The method according to an embodiment of the present application can also be implemented on a programmed processor. However, the controller, flowchart, and module can also be implemented on a general-purpose or special-purpose computer, a programmed microprocessor or microcontroller, and peripheral integrated circuit elements, integrated circuits, hardware electronic or logic circuits (e.g., discrete element circuits, programmable logic devices, etc.). Generally, any device on which a finite state machine capable of implementing the flowchart shown in the figures resides can be used to implement the processor functions of the present application. For example, embodiments of the present application provide a device for emotion recognition from speech, including a processor and a memory. The computer-programmable instructions for implementing the method for emotion recognition from speech are stored in the memory, and the processor is configured to execute the computer-programmable instructions to implement the method for emotion recognition from speech. The method can be the method as described above or other methods according to embodiments of the present application.

[0082] Alternative embodiments preferably implement the methods according to embodiments of the present application in a non - transitory computer - readable storage medium storing computer - programmable instructions. The instructions are preferably executed by a computer - executable component preferably integrated with a network security system. The non - transitory computer - readable storage medium can be stored on any suitable computer - readable medium, such as RAM, ROM, flash memory, EEPROM, optical storage devices (CD or DVD), hard disk drives, floppy disk drives, or any suitable device. The computer - executable component is preferably a processor, but the instructions can alternatively or additionally be executed by any suitable dedicated hardware device. For example, embodiments of the present application provide a non - transitory computer - readable storage medium having computer - programmable instructions stored therein. The computer - programmable instructions are configured to implement the method for emotion recognition from speech as stated above or other methods according to embodiments of the present application.

[0083] Although the present application has been described in terms of its specific embodiments, it will be apparent that many alternatives, modifications, and variations may be obvious to those skilled in the art. For example, the various components of the embodiments can be interchanged, added, or replaced in other embodiments. Additionally, all elements of each figure are not necessary for the operation of the disclosed embodiments. For example, one of ordinary skill in the art of the disclosed embodiments will be able to make and use the teachings of the present application by simply employing the elements of the independent technical solutions. Thus, the embodiments of the present application as described herein are intended to be illustrative rather than restrictive. Various changes can be made without departing from the spirit and scope of the present application.

Claims

1. A method for wireless communication performed by a user equipment (UE), comprising: Obtaining configuration information indicating at least one sidelink discontinuous reception (DRX) configuration for data on a sidelink, wherein the at least one sidelink DRX configuration is associated with a first resource pool; Transmitting the data at least in part based on the at least one sidelink DRX configuration or receiving the data at least in part based on the at least one sidelink DRX configuration indicated by the configuration information; And During a logical channel prioritization (LCP) process, selecting the destination if the destination is related to the data associated with the sidelink DRX configuration and the UE is in the wake-up time of the sidelink DRX configuration, wherein the destination is associated with traffic having corresponding quality of service (QoS) requirements.

2. The method according to claim 1, wherein the configuration information is pre-configured in the UE, broadcast in a system information block (SIB), or received via radio resource control (RRC) signaling, at least one of which.

3. The method according to claim 1, wherein each of the at least one sidelink DRX configurations includes at least one of the following parameters: On-duration; Off-duration; Wake-up time; One or more timers associated with DRX; DRX cycle; or DRX offset value.

4. The method according to claim 1, wherein the configuration information indicates that each of the at least one sidelink DRX configurations is associated with one or more destination identification IDs or one or more sidelink radio bearers.

5. The method according to claim 1, wherein the first resource pool is a transmission resource pool, wherein the at least one sidelink DRX configuration includes a plurality of sidelink DRX configurations, and the method further includes: Copying the data; And Transmitting the copied data during the wake-up time of each sidelink DRX configuration in the plurality of sidelink DRX configurations.

6. The method according to claim 1, wherein the at least one sidelink DRX configuration indicates the time-frequency resources of the data, wherein the time-frequency resources are part of the first resource pool, and the method further includes: Transmitting the data on the time-frequency resources or receiving the data on the time-frequency resources, one of which.

7. The method according to claim 6, wherein the at least one sidelink DRX configuration includes at least one of the following parameters: A first parameter indicating a bitmap that indicates time-domain resources within the first resource pool; A second parameter indicating frequency-domain resources within the first resource pool; or A third parameter indicating a resource selection window of the first resource pool.

8. The method according to claim 1, wherein the at least one sidelink DRX configuration indicates a second resource pool different from the first resource pool, and the method further includes: Transmitting the data on the second resource pool or receiving the data on the second resource pool, one of which.

9. The method according to claim 1, wherein the configuration information indicates a mapping relationship between the at least one sidelink DRX configuration and at least one destination identifier ID.

10. A device, comprising: a receiver; a transmitter; and a processor coupled to the receiver and the transmitter and configured to cause the device to: obtain configuration information indicating at least one sidelink discontinuous reception (DRX) configuration for data on a sidelink, the at least one sidelink DRX configuration being associated with a resource pool; and one of the following: transmit the data at least in part based on the at least one sidelink DRX configuration indicated by the configuration information; or receive the data at least in part based on the at least one sidelink DRX configuration indicated by the configuration information; and during a logical channel prioritization (LCP) process, select the destination if the destination is relevant to the data associated with the sidelink DRX configuration and the device is in the wake-up time of the sidelink DRX configuration, wherein the destination is associated with traffic having corresponding quality of service (QoS) requirements.

11. The device according to claim 10, wherein the configuration information is pre-configured in the device, broadcast in a system information block SIB, or received via radio resource control RRC signaling, at least one of the above.

12. The device according to claim 10, wherein: the at least one sidelink DRX configuration includes at least one of the following parameters: on-duration, off-duration, wake-up time, one or more timers associated with DRX, DRX cycle, or DRX offset value; and the configuration information indicates that the at least one sidelink DRX configuration is associated with one or more destination identifier IDs or one or more sidelink radio bearers.

13. The device according to claim 10, wherein the resource pool is a transmission resource pool, the at least one sidelink DRX configuration includes a plurality of sidelink DRX configurations, and the processor coupled to the receiver and the transmitter is configured to cause the device to: duplicate the data; and transmit the duplicated data at the wake-up time of each sidelink DRX configuration in the plurality of sidelink DRX configurations.

14. The device according to claim 10, wherein the at least one sidelink DRX configuration indicates the time-frequency resources of the data, the time-frequency resources being part of the resource pool, and the processor coupled to the receiver and the transmitter is configured to cause the device to perform one of the following: transmit the data on the time-frequency resources; or receive the data on the time-frequency resources.

15. The device according to claim 10, wherein the at least one sidelink DRX configuration includes at least one of the following parameters: a first parameter indicating a bitmap that indicates time-domain resources within the resource pool; a second parameter indicating frequency-domain resources within the resource pool; or a third parameter indicating a resource selection window of the resource pool.

Images