System and method for vehicle-to-everything sidelink communication

Abstract

In some embodiments, the method includes: determining a sidelink discontinuous reception configuration using sidelink discontinuous reception configuration information by a first wireless communication device, and communicating with a second communication device based on the sidelink discontinuous reception configuration by the first wireless communication device.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications and, more particularly, to systems and methods for V2X communications indicating potential sidelink time slots. Background Art

[0002] Sidelink (SL) communication is wireless radio communication directly between two or more user equipment devices (hereinafter referred to as "UE"). In this type of communication, two or more UEs that are geographically close to each other can communicate directly without going through an eNode or base station (hereinafter referred to as "BS") or a core network. Therefore, data transmission in SL communication is different from typical cellular network communications that send data to a BS (i.e., uplink transmission) or receive data from a BS (i.e., downlink transmission). In SL communication, data is transmitted directly from a source UE to a target UE over a unified air interface (e.g., a PC5 interface) without going through a BS.

[0003] In network coverage, all UEs are within the network coverage of the BS. In partial network coverage, at least one UE is within the network coverage and at least one other UE is outside the network coverage. Outside network coverage, all UEs are outside the network coverage. Summary of the invention

[0004] The example embodiments disclosed herein are intended to solve problems associated with one or more problems presented in the prior art, as well as to provide additional features that will become apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. According to various embodiments, example systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example, not by way of limitation, and it will be apparent to those of ordinary skill in the art who read this disclosure that various modifications to the disclosed embodiments may be made while remaining within the scope of this disclosure.

[0005] In some arrangements, a user equipment (UE) determines a sidelink (SL) discontinuous reception (DRX) configuration information and communicates with a peer UE based on the SL DRX configuration.

[0006] In some arrangements, the peer UE receives a SL DRX configuration from another UE and sends a SL DRX configuration response to the other UE. The SL DRX configuration response includes one of a DRX adjustment request (which indicates that the number of packet losses exceeds a threshold) or a packet loss indication.

[0007] The above and other aspects and their embodiments are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Various example embodiments of the present solution are described in detail below with reference to the accompanying drawings or drawings. The drawings are provided for illustrative purposes only and depict only example embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered as limiting the breadth, scope or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.

[0009] Figure 1A is a diagram illustrating an example wireless communication network according to various arrangements.

[0010] Figure 1B is a diagram illustrating a block diagram of an example wireless communication system for transmitting and receiving downlink, uplink and / or sidelink communication signals according to various arrangements.

[0011] Figure 2 Example scenarios of sidelink communications according to various arrangements are shown.

[0012] Figure 3 is a flow chart illustrating an example process for determining a sidelink discontinuous reception configuration according to various arrangements.

[0013] Figure 4 is a flow chart illustrating an example process for determining a sidelink discontinuous reception configuration according to various arrangements.

[0014] Figure 5 is a flow chart illustrating an example method for determining a sidelink discontinuous reception configuration of a wireless communication device in a multicast according to various arrangements.

[0015] Figure 6 is a flow chart illustrating an example method for sidelink communications between a first wireless communication device and a second wireless communication device according to various arrangements.

[0016] Fig. 7A is a flow chart illustrating an example wireless communication method for a sidelink discontinuous reception configuration according to various arrangements.

[0017] Figure 7B is a flow chart illustrating an example wireless communication method for a sidelink discontinuous reception configuration according to various arrangements.

[0018] Figure 7C is a flow chart illustrating an example wireless communication method for triggering transmission resource re-selection according to various arrangements.

[0019] Fig. 8A A block diagram of an example base station is shown according to various arrangements.

[0020] Figure 8B A block diagram of an example user equipment is shown according to various arrangements. DETAILED DESCRIPTION

[0021] Various example embodiments of the present solution are described below with reference to the accompanying drawings to enable a person of ordinary skill in the art to make and use the present solution. As will be apparent to a person of ordinary skill in the art, after reading the present disclosure, various changes or modifications to the examples described herein may be made without departing from the scope of the present solution. Therefore, the present solution is not limited to the example embodiments and applications described and illustrated herein. In addition, the specific order or hierarchy of steps in the methods disclosed herein are merely example methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes may be rearranged while remaining within the scope of the present solution. Therefore, a person of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or actions in an example order, and unless otherwise expressly stated, the present solution is not limited to the specific order or hierarchy presented.

[0022] refer to Figure 1A , an example wireless communication network 100 is shown. The wireless communication network 100 shows group communication within a cellular network. In a wireless communication system, network-side communication nodes or base stations (BS) may include next-generation Node Bs (gNBs), E-utran Node Bs (also known as evolved Node Bs, eNodeBs, or eNBs), micro-micro stations, femto-micro stations, transmit / receive points (TRPs), access points (APs), and the like. Terminal-side nodes or user equipment (UEs) may include long-range communication systems, such as, for example, mobile devices, smart phones, personal digital assistants (PDAs), tablet computers, laptop computers, or short-range communication systems, such as, for example, wearable devices, vehicles with vehicle communication systems, and the like. In Figure 1A In the embodiment of the present disclosure, the network side and terminal side communication nodes are represented by BS 102 and UE 104a or 104b, respectively, and in the embodiments of the present disclosure below. In some embodiments, BS 102 and UE 104a / 104b are sometimes referred to as "wireless communication nodes" and "wireless communication devices", respectively. Such communication nodes / devices can perform wireless and / or wired communications.

[0023] exist Figure 1AIn the illustrated embodiment, BS 102 may define a cell 101 in which UE 104a-b is located. UE 104a may include a vehicle moving within the coverage of cell 101. UE 104a may communicate with BS 102 via communication channel 103a. Similarly, UE 104b may communicate with BS 102 via communication channel 103b. In addition, UE 104a-b may communicate with each other via communication channel 105. The communication channel between UE and BS (e.g., 103a-b) may be through an interface (such as a Uu interface), which is also referred to as a universal mobile telecommunications system (UMTS) air interface. The communication channel between UEs (e.g., 105) may be through a PC5 interface, which is introduced to address high mobile speed and high density applications, such as, for example, vehicle-to-vehicle (V2V) communication, vehicle-to-pedestrian (V2P) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-network (V2N) communication, etc. In some instances, this automotive network communication mode may be collectively referred to as vehicle-to-everything (V2X) communication. It should be understood that the communication channel between UEs may be used in device-to-device (D2D) communication while remaining within the scope of the present disclosure. BS 102 is connected to a core network (CN) 108 via an external interface 107 (e.g., an Iu interface).

[0024] Figure 1B A block diagram of an example wireless communication system 150 for transmitting and receiving downlink, uplink, and sidelink (SL) communication signals according to some embodiments of the present disclosure is shown. The system 150 may include components and elements configured to support known or conventional operating features that do not require detailed description herein. In one embodiment, as described above, the system 150 may be configured to transmit and receive downlink, uplink, and sidelink (SL) communication signals in a manner such as Figure 1A The wireless communication network 100 may be used to send and receive data symbols in a wireless communication environment.

[0025] like Figure 1AAs described, the system 150 generally includes a BS 102 and UEs 104a-b. The BS 102 includes a BS transceiver module 110, a BS antenna 112, a BS memory module 116, a BS processor module 114, and a network communication module 118, each of which is coupled and interconnected to each other via a data communication bus 120 as needed. The UE 104a includes a UE transceiver module 130a, a UE antenna 132a, a UE memory module 134a, and a UE processor module 136a, each of which is coupled and interconnected to each other via a data communication bus 140a as needed. Similarly, the UE 104b includes a UE transceiver module 130b, a UE antenna 132b, a UE memory module 134b, and a UE processor module 136b, each of which is coupled and interconnected to each other via a data communication bus 140b as needed. The BS 102 communicates with the UEs 104a-b via one or more of the communication channels 150, which may be any wireless channel or other medium known in the art suitable for data transmission as described herein.

[0026] As will be appreciated by those skilled in the art, system 150 may also include Figure 1B Modules of any number outside the modules shown. It will be appreciated by those skilled in the art that the various illustrative blocks, modules, circuits and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware or any actual combination thereof. In order to clearly illustrate this interchangeability and compatibility of hardware, firmware and software, various illustrative components, blocks, modules, circuits and steps are generally described according to their functions. Whether this function is implemented as hardware, firmware or software depends on the specific application and design constraints imposed on the entire system. Personnel familiar with the concepts described herein can implement this function in a suitable manner for each specific application, but this implementation decision should not be interpreted as limiting the scope of the present disclosure.

[0027] The wireless transmission from the antenna of one of UE 104a-b to the antenna of BS 102 is referred to as uplink transmission, and the wireless transmission from the antenna of BS 102 to the antenna of one of UE 104a-b is referred to as downlink transmission. According to some embodiments, each of UE transceiver modules 130a-b may be referred to as an uplink transceiver or UE transceiver in this article. The uplink transceiver may include a transmitter and a receiver circuit, each of which is coupled to a corresponding antenna 132a-b. The duplex switch may alternately couple the uplink transmitter or receiver to the uplink antenna in a time duplex manner. Similarly, the BS transceiver module 110 may be referred to as a downlink transceiver or BS transceiver in this article. The downlink transceiver may include an RF transmitter and a receiver circuit, each of which is coupled to an antenna 112. The downlink duplex switch may alternately couple the downlink transmitter or receiver to the antenna 112 in a time duplex manner. The operations of the transceivers 110 and 130a-b are coordinated in time such that at the same time that the downlink transmitter is coupled to the antenna 112, the uplink receiver is coupled to the antenna 132a-b to receive the transmission via the wireless communication channel 150. In some embodiments, the UE 104a-b may use the UE transceivers 130a-b via the respective antennas 132a-b to communicate with the BS 102 via the wireless communication channel 150. The wireless communication channel 150 may be any wireless channel or other medium known in the art suitable for downlink (DL) and / or uplink (UL) transmission of data as described herein. The UEs 104a-b may communicate with each other via the wireless communication channel 170. The wireless communication channel 170 may be any wireless channel or other medium known in the art suitable for SL transmission of data as described herein.

[0028] Each of the UE transceivers 130a-b and the BS transceiver 110 are configured to communicate via a wireless data communication channel 150 and cooperate with an appropriately configured antenna arrangement that can support a specific wireless communication protocol and modulation scheme. In some embodiments, the UE transceivers 130a-b and the BS transceiver 110 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to application to specific standards and associated protocols. Instead, the UE transceivers 130a-b and the BS transceiver 110 can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0029] The processor modules 136a-b and 114 may each be implemented or realized by a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which are designed to perform the functions described herein. In this manner, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.

[0030] In addition, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be directly embodied in hardware, in firmware, in software modules executed by the processor modules 114 and 136a-b, respectively, or in any practical combination thereof. The memory modules 116 and 134a-b may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. In this regard, the memory modules 116 and 134a-b may be coupled to the processor modules 114 and 136a-b, respectively, so that the processor modules 114 and 136a-b may read information from the memory modules 116 and 134a-b, respectively, and write information to the memory modules 116 and 134a-b, respectively. The memory modules 116 and 134a-b may also be integrated into their respective processor modules 114 and 136a-b. In some embodiments, memory modules 116 and 134a-b may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions to be executed by processor modules 114 and 136a-b, respectively. Memory modules 116 and 134a-b may also each include a non-volatile memory for storing instructions to be executed by processor modules 114 and 136a-b, respectively.

[0031] The network interface 118 generally represents the hardware, software, firmware, processing logic and / or other components of the BS 102 that enable bidirectional communication between the BS transceiver 110 and other network components and communication nodes configured to communicate with the BS 102. For example, the network interface 118 can be configured to support Internet or WiMAX services. In a typical deployment, but not limited to, the network interface 118 provides an 802.3 Ethernet interface so that the BS transceiver 110 can communicate with a conventional Ethernet-based computer network. In this way, the network interface 118 may include a physical interface for connecting to a computer network (e.g., a mobile switching center (MSC)). The term "configured for" or "configured to" as used herein with respect to a specified operation or function refers to a device, component, circuit, structure, machine, signal, etc. that is physically constructed, programmed, formatted and / or arranged to perform a specified operation or function. The network interface 118 can allow the BS 102 to communicate with other BSs or a core network via a wired or wireless connection.

[0032] In some embodiments, each of UEs 104a-b may operate in a hybrid communication network in which the UE communicates with BS 102 and with other UEs (e.g., between 104a and 104b). As described in further detail below, UEs 104a-b support SL communications with other UEs and downlink / uplink communications between BS 102 and UEs 104a-b. Typically, SL communications allow UEs 104a-b to establish direct communication links with each other or with other UEs from different cells without requiring BS 102 to relay data between UEs.

[0033] With the technological advancement and development of the automation industry, the scenarios of V2X communication are further diversified and require higher performance. These advanced V2X services include vehicle platooning, extended sensors, advanced driving (semi-automatic driving and fully automatic driving), and remote driving. The expected performance requirements may include supporting data packets between 50 and 12,000 bytes, enabling transmission rates between 2 and 50 messages per second, enabling maximum end-to-end latency between 3 and 500 milliseconds, supporting reliability between 90 and 99.999%, enabling data rates between 0.5 and 1000Mbps, and supporting a transmission range between 50 and 1000 meters.

[0034] Figure 2 is a diagram illustrating an example system 200 for SL communication according to various arrangements. Figure 2 As shown, BS 210 (such as, Figure 1A BS 102) broadcasts a signal which is received by the first UE 220, the second UE 230 and the third UE 240. Figure 2In the figure, UE 220 and 230 are shown as vehicles with a vehicle communication network, and UE 240 is shown as a mobile device. As shown in SL, UE 220-240 can communicate with each other via an air interface (i.e., direct transmission) without being forwarded by base station 210 and the core network. This type of V2X communication is called PC5-based V2X communication or V2X SL communication, and is one of the ways to implement the V2X standard from the 3rd Generation Partnership Project (3GPP) V2X communication research.

[0035] Various identifiers can be used for New Radio (NR) SL communications. The first identifier is the source layer-2 identifier (ID), which identifies the sender of data in NR SL communications. The source layer-2ID is 24 bits long and is divided into two bit strings in the medium access control (MAC) layer. The first bit string is the least significant bit (LSB) part of the source layer-2ID, which is 8 bits long and is forwarded to the physical layer of the sender. This bit string identifies the source of the expected data in the edge control information and is used to filter packets at the physical layer of the receiver. The second bit string is the most significant bit (MSB) part of the source layer-2ID, which is 16 bits long and is carried in the MAC header. This bit string is used to filter packets at the MAC layer of the receiver.

[0036] The second identifier is the destination layer-2ID, which identifies the data destination in NR SL communication. For NR SL communication, the destination layer-2ID is 24 bits long and is split into two bit strings in the MAC layer. The first bit string is the LSB part of the destination layer-2ID, which is 16 bits long and is forwarded to the physical layer of the sender. This bit string identifies the destination of the expected data in the SL control information and is used to filter packets at the physical layer of the receiver. The second bit string is the MSB part of the destination layer-2ID, which is 8 bits long and is carried in the MAC header. This bit string is used to filter packets at the MAC layer of the receiver.

[0037] The third identifier is a PC5 link identifier, which uniquely identifies a PC5 unicast link in the UE during the lifetime of the PC5 unicast link, as specified in TS 23.287

[40] . The PC5 link identifier is used to indicate a PC5 unicast link for which a SL Radio Link Failure (RLF) statement is made and whose PC5-RRC (Radio Resource Control) connection is released.

[0038] In order for SL communication between UEs to work effectively, correctly configured SL discontinuous reception (DRX) is very important. Once the first UE determines the SL DRX configuration, the first UE can communicate with the second UE based on the SL DRX configuration. The SL DRX configuration can be determined according to several embodiments.

[0039] In a first embodiment, the BS considers PO alignment when configuring SL DRX. By definition, the UE monitors one paging occasion (PO) per DRX cycle. PO is a set of physical downlink control channel (PDCCH) monitoring opportunities and may consist of multiple time slots (e.g., subframes or orthogonal frequency division multiplexing (OFDM) symbols) in which paging downlink control information (DCI) may be sent. The BS may indicate whether to align with PO when configuring the SL DRX of an RRC idle state UE. If the UE receives information indicating SL DRX alignment, the SL on duration of the UE is the same as the paging occasion.

[0040] Figure 3 300 is a flow chart illustrating an example process 300 for determining a SL DRX configuration according to various arrangements. At 310, BS 301 determines whether to align POs when configuring SL DRX of an RRC idle state UE. At 310, BS 301 sends SL DRX configuration information to UE 302. The SL DRX configuration information includes a SL DRX alignment indication. The SL DRX configuration information is signaled in SystemInformationBlockType1 (SIB1). At 330, UE 302 receives the SL DRX configuration information. At 340, the UE determines the SL DRX configuration based on the SL DRX configuration information and DL DRX parameters, including Ns (which is the number of POs in a paging frame (PF)), nAndPagingFrameOffset (which is a PF parameter), and the length of the default DRX cycle. The system frame number (SFN) of the PF can be determined according to the following formula:

[0041]

[0042]

[0043] Where T is the DRX cycle of the UE, N is the total number of paging frames in T, and N s It can also be the number of DRX on occasions of the DRX on frame, PF offset is the offset value used for PF determination, and UE ID Equal to 5G-S-TMSI mod 1024. N and PF offset The value of is derived from the parameter nAndPagingFrameOffset, while T is the length of the default DRX cycle.

[0044] Since the SL DRX alignment indication is received, the UE assumes that no DRX is used for PO. The SL DRX alignment indication indicates that the UE's SL on duration is the same as the PO determined by the UE based on the DL DRX parameters. If DRX is not activated, the UE must continuously monitor the information. DRX enables sleep or "off", so no DRX means that the UE is not allowed to sleep. In addition, after the UE receives the SL DRX configuration information, the UE can notify the peer UE of the UE's own SL DRX configuration. The peer UE also needs to know the PO, so at 350, the UE sends the PO to the peer UE, which can be done in one of two ways. First, the SL DRX configuration can include not only the above-mentioned received DL DRX parameters (e.g., Ns, nAndPagingFrameOffset, and the length of the default DRX cycle), but also the UE's own UE ID (i.e., 5G-S-TMSI mod 1024). Second, the SL DRX configuration may include T, PF offset 、DRX offset (given by formula 1) and i S (given by Formula 2) one or more.

[0045] In the second embodiment, the BS configures the SL DRX mode for the UE without considering the alignment, because the alignment is situational and depends on the UE capabilities, which means that the alignment may not be optimal for some UEs. In this embodiment, the BS configures the SL DRX mode for the UE according to the configuration of the SL resource pool. The BS determines the SL DRX configuration information, which includes slot offset and the length of the default DRX cycle. The SL DRX configuration information is signaled in SIB1. The UE receives the SL DRX configuration information and determines the SL DRX on-duration according to one of the following formulas:

[0046] (Slot index +Slot offset ) mod T=UE ID mod T (3)

[0047] Where T is the UE's SL DRX cycle, slot offset is the offset used for PF determination, UE ID 5G-S-Temporary Mobile Subscriber Identity (TMSI) mod 1024, destination ID mod 1024 or source ID one of mod1024;

[0048] (Slot index +Slotoffset ) mod T = Destination ID mod T (4)

[0049] or

[0050] (Slot index +Slot offset ) mod T=Source ID mod T (5)

[0051] Where T is the UE's SL DRX period, and slot offset is the offset used for PF determination. For formulas 4 and 5, if the UE involves multiple PC5 links, the UE can configure different SL DRX configurations for different PC5 links. Different PC5 links can be associated with different Source ID and Destination ID In addition, once the UE receives the SL DRX configuration information, the UE can notify the peer UE of its own SL DRX configuration, including Slot offset and the length of the default DRX cycle. The UE notifies the peer UE of the SL DRX configuration via a PC5 RRC message or a PC5 broadcast message.

[0052] In the third embodiment, the BS configures SL DRX configuration information for the UE and signals the information in SIB1. The SL DRX configuration information includes Ns, nAndDRXFrameOffset and the length of the default SL DRX cycle. The UE receives the SL DRX configuration information and determines the SL DRX on-duration. The SFN of the SL DRX on-duration frame is determined according to the following formula:

[0053]

[0054] And indicates the time slot of the frame Index It is determined according to the following formula:

[0055]

[0056] Where T is the SL DRX cycle of the UE, N is the number of total SL DRX frames in T, and N S is the number of DRX on occasions of the DRX on frame, F offset It is the offset used to determine the DRX start frame. ID 5G-S-TMSI mod 1024, Destination ID mod 1024, SourceID mod 1024, Destination ID or Source ID One. N and F offset The value of is derived from the parameter nAndDRXFrameOffset. T is the length of the default SL DRX cycle. S It can be a fixed number, such as the total number of time slots in a frame. In addition, once the UE receives the SL DRX configuration information, the UE can notify the peer UE of the UE's own SL DRX configuration, and include Ns, nAndDRXFrameOffset and the length of the default SL DRX cycle. The UE notifies the peer UE of the SL DRX configuration via a PC5 RRC message or a PC5 broadcast message.

[0057] In the fourth embodiment, the BS configures SL DRX configuration information for the UE and signals the information in SIB1. The SL DRX configuration information includes DRXFrameOffset and the length of the default SL DRX cycle. The UE receives the SL DRX configuration information and determines the SL DRX on duration. The SFN of the SL DRX duration frame is determined by one of the following formulas:

[0058] (SFN+F offset ) mod T=UE ID mod T (8)

[0059] Slot Index , which indicates the time slot of the frame, is determined by the following formula:

[0060] Slot Index =UE ID mod N (9)

[0061] Where T is the UE's SL DRX cycle, F offset is the offset used for PF determination, N is the fixed total number of time slots in the frame, and UE ID 5G-S-TMSI mod 1024, Destination ID mod 1024, Source ID mod 1024, Destination ID or Source ID If the UE involves multiple PC5 links, the UE can configure different SL DRX configurations for different PC5 links. Different PC5 links can be associated with different Source ID and Destination IDIn addition, once the UE receives the SL DRX configuration information, the UE may notify the peer UE of the UE's own SL DRX configuration, including the DRXFrameOffset and the length of the default SL DRX cycle. The UE may also include the UE's own UE ID (For example, 5G-S-TMSImod 1024). The UE notifies the peer UE of the SL DRX configuration via a PC5 RRC message or a PC5 broadcast message.

[0062] In a fifth embodiment, SL DRX is configured based on a bitmap including a SL resource pool. Figure 4 4 is a flow chart illustrating an example process 400 for determining a SL DRX configuration according to various arrangements. At 410, BS 410 sends SL resource pool configuration information to UE 402, which is received by UE 402 at 420. The SL resource pool configuration includes a period (T), an offset, and a UE ID. ID At 430, UE 402 uses the received SL DRX configuration information to determine the logical time slots of the SL DRX on-duration. At 440, UE 402 maps the logical time slots to specific SL resources based on the bitmap. The mapping may be based on the following formula:

[0063] (Slot Index +Slot Offset ) mod T=UE ID mod T (10)

[0064] If the period is 10 units, the calculated Slot Index is 1, 11, 21, and the corresponding SL resource pools are 1, 11, 21. The time slots corresponding to each bitmap are the time slots in which the UE SL DRX is turned on. In contrast to the previous embodiment, the time slot pools are discontinuous because the bitmaps are mapped to those of the SL resource pools. If the calculated time slot index is 2, in this embodiment, the time slot index is actually 3 (for example, 1, 3). Different bitmaps lead to different configurations. In this way, different T values ​​and offset values ​​can be configured based on different receiving resource pools. In addition, a unified (i.e., aligned) T and offset can be configured. If the relationship between T and the period of the resource pool is not an integer multiple, the start position alignment may cause problems that complicate the determination of the SL DRX configuration. Therefore, the relationship between T and the period of the resource pool should only be considered when the relationship between T and the period of the resource pool is an integer multiple.

[0065] For sidelink multicast or broadcast connections (as opposed to the unicast connections of the first to fifth embodiments), the simplest way for a UE with energy saving requirements is not to monitor multicast or broadcast messages, but to send multicast and broadcast messages. Because multicast messages support feedback, even if the UE does not need to monitor multicast messages, the UE at least needs to monitor feedback messages. If the UE is configured with SL DRX, the RTT timer of the relevant process can be started after the multicast message is sent. However, considering that the location of the acknowledgment (ACK) feedback resource is fixed, the RTT timer is not required. Therefore, if the reception scenarios of broadcast and multicast are not considered, SL DRX is not required.

[0066] However, if multicast and broadcast messages are considered with the goal of energy saving, three solutions are possible. In the first solution, the UE sends its own SL DRX configuration to the peer UE via PC5 broadcast message. In the second solution, the UE determines multiple sets of SL DRX configurations corresponding to different lists of destination identifiers. These SL DRX configurations include one or more periods (i.e., T), Slot Offset 、F Offset Or at least one of DRXFrameOffset, inactivity timer, different retransmission timers. In a third solution, the UE determines multiple sets of SL DRX configurations based on different SL quality of service (QoS). SL QoS includes one of packet delay budget (PDB), priority level, reliability level, QoS-FLOWIDENTITY, SL-PC5 QoS identifier (PQI) or packet error rate level. In other words, different SL QoS can be associated with different groups of SL DRX configurations. In particular, different SL QoS can be associated with different inactivity timers, different retransmission timers or with different DRX cycles. Alternatively, different SL QoS can be associated with the same RTT timer.

[0067] Figure 5 5 is a flow chart illustrating an example method 500 for determining SL DRX configuration of UEs in multicast according to various arrangements. At 510, BS 501 determines SL DRX configurations based on different SL QoS or corresponding to different Destination ID At 520, BS 501 sends multiple sets of SL DRX configuration information to UE 502, which is received by UE 502 at 530. At 540, UE 502 notifies peer UE 503 of the corresponding Destination ID , which is received by peer UE 503 at 550. Figure 5As shown, the peer UE may be a single UE or may be a plurality of UEs such that the transmission of information by UE 502 at 540 is accomplished via a SL multicast or broadcast message.

[0068] If the SL DRX configuration of the UE is determined or predetermined by the network side (i.e., by the BS), the simplest configuration method is through the UE. After the UE determines its own SL DRX configuration, the UE notifies the peer UE, and the peer UE can select transmission resources based on the SL DRX of the original UE. For UEs in unicast communication, the UE can notify the peer UE of the UE's SL DRX configuration through a PC5 RRC message. After obtaining the SL DRX configuration of the receiving UE, the transmitter UE can select transmission resources based on the SL DRX mode of the peer UE.

[0069] In the first mode (i.e., Mode 1), the UE sends the SL DRX configuration information of the peer UE to the serving BS so that the serving BS can allocate appropriate resources to the receiving UE according to the DRX configuration of the received UE. Specifically, the UE can report this SL DRX information per destination ID through SL UE information. In the second mode (i.e., Mode 2), the UE considers the SL DRX configuration of the receiver UE when selecting resources.

[0070] If after obtaining the SL DRX configuration of the peer UE, the peer UE determines that the available resources will cause the data or channel state information (CSI) MAC control element (CE) to time out and the SL DRX configuration is not suitable. In response, the peer UE has two options for the SL DRX configuration response. First, the UE triggers a DRX adjustment request, which indicates the preferred increment of the long DRX cycle length for the current DRX configuration and can be sent via a PC5 RRC message or a SL MAC CE. The DRX adjustment request may be triggered when the number of packet losses exceeds a threshold. If the SL DRX configuration is configured per destination ID, the number of packet losses can be calculated per destination ID. The threshold is received before the SL DRX configuration response is transmitted. Second, the UE sends an indication of packet loss due to timeout of the current DRX configuration. When per Destination ID due to the SL DRX configuration ID The indication is sent when the number of packet losses exceeds the threshold. If the value of the threshold is set to 1, the indication is sent once a single timeout packet loss occurs. The indication information can be carried by the SL MAC CE or PC5 RRC transmission and either only indicates that a packet loss has occurred, or directly carries the number of packet losses or the level of packet loss.

[0071] Prior to sending the SL DRX Configuration Response, the peer UE determines that at least one of three conditions is met. First, the peer UE determines that the delay requirement of the data in the logical channel or SL MAC CE is not met due to the SL DRX configuration. Second, the peer UE determines that the transmission with the selected SL grant cannot meet the delay requirement of the data in the logical channel according to the associated priority due to the SL DRX configuration. Third, the peer UE determines that the transmission of the pending SL MAC CE with the sidelink grant cannot meet the delay requirement associated with the SL MAC CE due to the SLDRX configuration.

[0072] In some embodiments, the peer UE maintains a packet loss number counter. If the peer UE determines that the transmission with the selected SL grant cannot meet the delay requirements of the data in the logical channel due to the SL DRX configuration, and the packet loss number counter has not reached a threshold, the peer UE adds one to the packet loss number counter. If the packet loss number counter reaches the threshold, the peer UE sends a SL DRX configuration response, which may be a DRX adjustment request or an indication of a timeout packet loss due to the current DRX configuration. If the UE receives an updated SL DRX configuration from the peer UE, the peer UE reinitializes the packet loss number counter to zero, or sets the packet loss number counter to 0 or 1.

[0073] For an embodiment, the peer UE receives a SL DRX configuration from the UE.The peer UE may also trigger transmission resource reselection if the peer UE determines that at least transmission with the selected SL grant cannot meet the delay requirements of data in the logical channel according to the associated priority level due to the received SL DRX configuration.

[0074] Figure 6 6 is a flow chart illustrating an example method 600 for SL communication between a first UE 601 and a second UE 602 according to various arrangements. At 610, the first UE 601 sends a SL DRX configuration to the second UE 602, which is received by the UE 602 at 620. At 630, the second UE receives a number of packet losses (or per Destination ID At 640, the second UE 602 sends a DRX adjustment request to the first UE 601, indicating that the number of packet losses exceeds the threshold received at 630. At 650, the second UE 602 sends an indication of packet loss to the first UE. At 660, the first UE receives the SL configuration response (from 640 or 650).

[0075] Fig. 7A1 is a flow chart illustrating an example wireless communication method 700 for SL DRX configuration according to various arrangements. Figure 5 The method 700 may be performed by a BS. The method 700 starts at step 701, where the BS determines whether to align the PO of a connected wireless communication device (eg, UE). Then, at step 702, the BS indicates SL DRX configuration information to the UE.

[0076] Figure 7B 1 is a flow chart illustrating an example wireless communication method 710 for SL DRX configuration according to various arrangements. Figure 6 The method 710 may be performed by a first UE. The method 710 starts at step 711, where the first UE receives SL DRX configuration information from a BS. At step 712, the first UE determines a SL DRX configuration using the SL DRX configuration information. Then, at step 713, the UE communicates with a second UE based on the SL DRX configuration.

[0077] Figure 7C is a flow chart illustrating an example wireless communication method 720 for triggering transmission resource reselection according to various arrangements. Referring to FIGS. 1-6 , the method 720 may be performed by a second UE. The method 720 begins at step 721 , where the second UE receives a SL DRX configuration from a first UE. At step 722 , the peer UE determines that at least one transmission with a selected UL grant cannot meet a delay requirement for data in a logical channel according to an associated priority level due to the SL DRX configuration. Then, at step 713 , the second UE triggers transmission resource reselection.

[0078] Fig. 8A A block diagram of an example BS 802 is shown in accordance with some embodiments of the present disclosure. Figure 8B FIG1 is a block diagram of an example UE 801 according to some embodiments of the present disclosure. Figure 8B , UE 801 (eg, wireless communication device, terminal, mobile device, mobile user, etc.) is an example implementation of a UE described herein, and BS 802 is an example implementation of a BS described herein.

[0079] BS 802 and UE 801 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In an illustrative embodiment, as described above, BS 802 and UE 801 may be used to communicate (e.g., send and receive) data symbols in a wireless communication environment. For example, BS 802 may be a BS (e.g., gNB, eNB, etc.), a server, a node, or any suitable computing device for implementing various network functions.

[0080] BS 802 includes a transceiver module 810, an antenna 812, a processor module 814, a memory module 816, and a network communication module 818. Modules 810, 812, 814, 816, and 818 are operably coupled to and interconnected with each other via a data communication bus 820. UE 801 includes a UE transceiver module 830, a UE antenna 832, a UE memory module 834, and a UE processor module 836. Modules 830, 832, 834, and 836 are operably coupled to and interconnected with each other via a data communication bus 840. BS 802 communicates with UE 801 or another BS via a communication channel, which may be any wireless channel or other medium suitable for data transmission as described herein.

[0081] As will be understood by those skilled in the art, BS 802 and UE 801 may also include Fig. 8A and Figure 8B . The various illustrative blocks, modules, circuits and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware or any actual combination thereof. In order to illustrate this interchangeability and compatibility of hardware, firmware and software, various illustrative components, blocks, modules, circuits and steps are usually described according to their functions. Whether this function is implemented as hardware, firmware or software can depend on the specific application and design constraints imposed on the whole system. The embodiments described herein can be implemented in a suitable manner for each specific application, but any implementation decision should not be interpreted as limiting the scope of the present disclosure.

[0082] According to some embodiments, the UE transceiver 830 includes a radio frequency (RF) transmitter and an RF receiver, each including a circuit coupled to an antenna 832. A duplex switch (not shown) can alternately couple the RF transmitter or receiver to the antenna in a time duplex manner. Similarly, according to some embodiments, the transceiver 810 includes an RF transmitter and an RF receiver, each having a circuit coupled to an antenna 812 or an antenna of another BS. The duplex switch can alternately couple the RF transmitter or receiver to the antenna 812 in a time duplex manner. The operation of the two transceiver modules 810 and 830 can be coordinated in time so that while the transmitter is coupled to the antenna 812, the receiver circuit is coupled to the antenna 832 for receiving transmissions via a wireless transmission link. In some embodiments, there is tight time synchronization with a minimum guard time between changes in duplex direction.

[0083] The UE transceiver 830 and the transceiver 810 are configured to communicate via a wireless data communication link and cooperate with an appropriately configured RF antenna arrangement 812 / 832 capable of supporting a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 830 and the transceiver 810 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to application to specific standards and associated protocols. Instead, the UE transceiver 830 and the BS transceiver 810 can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0084] The transceiver 810 and the transceiver of another BS (such as but not limited to the transceiver 810) are configured to communicate via a wireless data communication link and cooperate with an appropriately configured RF antenna arrangement capable of supporting a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, the transceiver 810 and the transceiver of another BS are configured to support industry standards such as LTE and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to the application of specific standards and associated protocols. On the contrary, the transceiver 810 and the transceiver of another BS can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0085] According to various embodiments, BS 802 may be a BS such as, but not limited to, an eNB, a serving eNB, a target eNB, a femtocell or a microcell. BS 802 may be a RN, a DeNB or a gNB. In some embodiments, UE 801 may be embodied in various types of user equipment, such as a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, a wearable computing device, etc. Processor modules 814 and 836 may be implemented or implemented with a general-purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, a discrete gate or transistor logic, a discrete hardware component or any combination thereof, which are designed to perform the functions described herein. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a digital signal processor core, or any other such configuration.

[0086] In addition, the methods or algorithms disclosed herein may be directly embodied in hardware, in firmware, in software modules executed by processor modules 814 and 836, respectively, or in any practical combination thereof. Memory modules 816 and 834 may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 816 and 834 may be coupled to processor modules 814 and 836, respectively, so that processor modules 814 and 836 can read information from and write information to memory modules 816 and 834, respectively. Memory modules 816 and 834 may also be integrated into their respective processor modules 814 and 836. In some embodiments, memory modules 816 and 834 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions to be executed by processor modules 814 and 836, respectively. The memory modules 816 and 834 may also each include non-volatile memory for storing instructions to be executed by the processor modules 814 and 836, respectively.

[0087] The network communication module 818 generally represents the hardware, software, firmware, processing logic and / or other components of the BS 802, which enables bidirectional communication between the transceiver 810 and other network components and communication nodes that communicate with the BS 802. For example, the network communication module 818 can be configured to support Internet or WiMAX traffic. In deployment, but not limited to, the network communication module 818 provides an 802.3 Ethernet interface so that the transceiver 810 can communicate with a conventional Ethernet-based computer network. In this way, the network communication module 818 may include a physical interface for connecting to a computer network (e.g., a mobile switching center (MSC)). In some embodiments, the network communication module 818 includes a fiber optic transmission connection configured to connect the BS 802 to the core network. The terms "configured for", "configured to" and their variants as used herein with respect to a specified operation or function refer to a device, component, circuit, structure, machine, signal, etc. that is physically constructed, programmed, formatted and / or arranged to perform a specified operation or function.

[0088] Although various embodiments of the present solution have been described above, it should be understood that they are presented only by way of example rather than by way of limitation. Similarly, various figures may depict example architectures or configurations, which are provided to enable those of ordinary skill in the art to understand the example features and functions of the present solution. However, these personnel will understand that the present solution is not limited to the example architectures or configurations shown, but may be implemented using various alternative architectures and configurations. In addition, as will be understood by those of ordinary skill in the art, one or more features of an embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above-mentioned illustrative embodiments.

[0089] It should also be understood that any reference to an element using names such as "first", "second" etc. herein does not generally limit the quantity or order of these elements. On the contrary, these names can be used as a convenient means of distinguishing two or more elements or element instances in this article. Therefore, reference to a first element and a second element does not mean that only two elements can be used, or that the first element must be located before the second element in some way.

[0090] In addition, those of ordinary skill in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0091] Those of ordinary skill in the art will further understand that any of the various illustrative logic blocks, modules, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of the two), firmware, various forms of programs or design codes containing instructions (which, for convenience, may be referred to herein as "software" or "software modules"), or any combination of these technologies. In order to clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functions. Whether such functionality is implemented as hardware, firmware, software, or a combination of these technologies depends on the specific application and design constraints imposed on the entire system. Those skilled in the art may implement the described functionality in various ways for each specific application, but such implementation decisions will not result in a departure from the scope of the present disclosure.

[0092] In addition, it will be understood by those of ordinary skill in the art that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented or performed within an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, or any combination thereof. The logic blocks, modules, and circuits may also include antennas and / or transceivers to communicate with various components within a network or within a device. The general-purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration to perform the functions described herein.

[0093] If implemented in software, the function can be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, and communication media include any media that can enable a computer program or code to be transferred from one place to another. The storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or any other medium that can be used to store desired program codes in the form of instructions or data structures and can be accessed by a computer.

[0094] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. In addition, for the purpose of discussion, various modules are described as discrete modules; however, it will be apparent to one of ordinary skill in the art that two or more modules can be combined to form a single module that performs the associated functions according to an embodiment of the present solution.

[0095] In addition, memory or other storage and communication components can be used in the embodiments of the present solution. It should be understood that, for the purpose of clarity, the above description has described the embodiments of the present solution with reference to different functional units and processors. However, it is apparent that any appropriate functional distribution between different functional units, processing logic elements or domains can be used without departing from the present solution. For example, the functions shown as being performed by a separate processing logic element or controller can be performed by the same processing logic element or controller. Therefore, reference to a specific functional unit is only a reference to a suitable device for providing the described function, rather than an indication of a strict logical or physical structure or organization.

[0096] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the broadest scope consistent with the novel features and principles disclosed herein, as described in the following claims.

Claims

1. A wireless communication method, comprising: determining, by the first wireless communication device, a sidelink (SL) discontinuous reception (DRX) configuration information received from a base station, the SL DRX configuration information comprising one or more DRX parameters; The first wireless communication device communicates with a second communication device based on the SL DRX configuration, Wherein, determining the SL DRX configuration includes: determining the SL DRX on-duration time using the one or more DRX parameters, wherein determining the SL DRX on-duration time includes: determining a time slot index of a time slot indicating a DRX on-time based on the one or more DRX parameters and an identifier, wherein the identifier is determined based on a destination identifier.

2. The method according to claim 1, further comprising: receiving, by the first wireless communication device, downlink (DL) DRX configuration information and the SL DRX configuration information from a base station, wherein the DL DRX configuration information includes one or more DL DRX parameters; The SL DRX configuration is determined by the first wireless communication device using the DL DRX parameters and the SL DRX parameters, wherein The SL DRX configuration information includes a SL DRX alignment indication, and The DL DRX parameters include one or more of the number of paging occasions (PO) of a paging frame (PF), paging frame parameters, and a length of a default DRX cycle.

3. The method according to claim 2, wherein: The SL DRX alignment indication indicates that no DRX is used for the PO determined by the first wireless communication device using the DL DRX parameters.

4. The method according to claim 2, wherein: The SL DRX alignment indication indicates that the SL On-Duration of the first wireless communication device is the same as the PO determined by the first wireless communication device using the DL DRX parameters.

5. The method according to claim 2, further comprising notifying the second communication device of the SL DRX configuration by the first wireless communication device in the following manner: The first wireless communication device sends one or more of the DL DRX parameters and an identifier identifying the first communication device to the second communication device; or The first wireless communication device sends one or more of the DRX cycle of the first wireless communication device, the offset for determining the PF, the DRX offset and the index of the PO to the second communication device.

6. The method according to claim 1, further comprising: The first wireless communication device receives the SL DRX configuration information from a base station, wherein the SL DRX configuration information includes a time slot offset and a length of a default DRX cycle; The SL DRX configuration is determined by the first wireless communication device using the SL DRX configuration information, wherein Determining the SL DRX configuration includes determining a SL DRX On-Duration using the slot offset, a length of a DRX cycle, and an identifier determined based on one of: Temporary Mobile Subscriber Identity (TMSI), the destination identifier, or Source identifier.

7. The method according to claim 6, further comprising: One or more of the time slot offset and the length of the default DRX cycle are sent by the first wireless communication device to the second communication device.

8. The method according to claim 1, further comprising: The second communication device is informed of the SL DRX configuration by the first wireless communication device sending one or more of the DRX parameters to the second communication device by the first wireless communication device.

9. The method according to claim 1, further comprising: The first wireless communication device receives the SL DRX configuration information from a base station, where the SL DRX configuration information includes one or more DRX parameters; The SL DRX configuration is determined by the first wireless communication device using the DRX parameters, wherein The DRX parameters include one or more of a DRX frame offset and a length of a default DRX cycle; Determining the SL DRX configuration includes: determining the SL DRX on-duration time using the DRX parameters; Determining the SL DRX on-duration includes determining the time slot index of the time slot indicating the DRX on-opportunity according to the DRX parameter and an identifier determined based on one of the following: Temporary Mobile Subscriber Identity (TMSI), the destination identifier, or Source identifier.

10. The method according to claim 9, further comprising: The second communication device is informed of the SL DRX configuration by the first wireless communication device sending one or more of the DRX parameters and the identifier to the second communication device by the first wireless communication device.

11. The method according to claim 1, wherein: Determining the SL DRX configuration includes: The first wireless communication device receives SL resource pool configuration information from a base station, Determine a logical time slot of the SL DRX on-duration using the SL DRX configuration information; and The logical time slot is mapped to the SL resources in the SL resource pool using a bitmap, wherein the bitmap includes: a mapping of the logical time slot to the resources in the SL resource pool.

12. The method according to claim 1, wherein: The second communication device includes a plurality of second communication devices, and the method further includes: notifying the second communication devices, by the first wireless communication device, of a same set of the SL DRX configurations via an SL multicast or broadcast message.

13. The method according to claim 1, further comprising one of the following: Determining a plurality of sets of the SL DRX configurations based on different SL quality of service (QoS), wherein the SL QoS comprises one of: a packet delay budget (PDB), a priority level, a reliability level, a QoS-FLOWIDENTITY, a SL-PC5 QoS identifier (PQI), or a packet error rate level A plurality of sets of the SL DRX configurations are determined corresponding to different destination identifier lists, wherein the SL DRX configurations include one or more of a DRX frame offset, a length of a default DRX cycle, an inactivity timer, or a retransmission timer.

14. The method according to claim 13, further comprising receiving, by the first wireless communication device, a plurality of sets of the SL DRX configuration information from a base station, and each of the QoS corresponds to one of the plurality of sets of the SL DRX configuration information, wherein The SL DRX configuration includes one or more of a DRX frame offset, a length of a default DRX cycle, an inactivity timer, or a retransmission timer.

15. A wireless communication device, comprising at least one processor and a memory, wherein the at least one memory is configured to read a code from the memory and implement the method according to any one of claims 1 to 14.

16. A computer program product comprising computer readable program medium code stored thereon, which, when executed by at least one processor, causes the at least one processor to implement the method of any one of claims 1-14.

17. A wireless communication method for side link (SL) communication between a first wireless communication device and a second wireless communication device, comprising: Receiving, by the second wireless communication device, a SL discontinuous reception (DRX) configuration from the first wireless communication device; The SL DRX configuration is determined in the following manner: determining the SL DRX on-duration time using one or more DRX parameters in the SL DRX configuration information from the base station, wherein determining the SL DRX on-duration time includes: determining a time slot index of a time slot indicating a DRX on-time based on the one or more DRX parameters and an identifier, and the identifier is determined based on a destination identifier.

18. A wireless communication device comprising at least one processor and a memory, wherein the at least one memory is configured to read code from the memory and implement the method of claim 17.

19. A computer program product comprising computer readable program medium code stored thereon, which, when executed by at least one processor, causes the at least one processor to implement the method of claim 17.

Images