CN116889092A

CN116889092A - Side link discontinuous reception configuration

Info

Publication number: CN116889092A
Application number: CN202180093994.4A
Authority: CN
Inventors: 约阿希姆·勒尔; 普拉泰克·巴苏马利克; 韩晶; 迪米特里额斯·卡拉姆帕特斯; 胡洁
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2021-02-24
Filing date: 2021-02-24
Publication date: 2023-10-13
Also published as: US20240196455A1; MX2023009765A; WO2022178713A1; EP4298861A1; CA3204558A1; AU2021430255A1; KR20230147630A

Abstract

Apparatus, methods, and systems for side link discontinuous reception configuration are disclosed. A method (800) includes initiating (802), by a first user equipment, a sidelink unicast establishment procedure with a second user equipment. The method (800) includes performing (804) side-link communication during a side-link unicast setup procedure using a predetermined side-link discontinuous reception configuration. The method (800) includes, in response to receiving the direct communication acceptance message, performing (806) side link communication based on a set of side link discontinuous reception configurations.

Description

Side link discontinuous reception configuration

Technical Field

The subject matter disclosed herein relates generally to wireless communications, and more particularly to side link discontinuous reception configurations.

Background

In some wireless communication networks, discontinuous reception may be used during side link communication. The user equipment may not be aware of the discontinuous reception configuration to be used for some side link communications.

Disclosure of Invention

The invention discloses a method for side link discontinuous reception configuration. The apparatus and system also perform the functions of the method. In one embodiment, a method includes initiating, by a first user device, a sidelink unicast establishment procedure with a second user device. In some embodiments, the method includes performing side-link communication during a side-link unicast setup procedure using a predetermined side-link discontinuous reception configuration. In various embodiments, a method includes performing side link communication based on a set of side link discontinuous reception configurations in response to receiving a direct communication accept message.

In one embodiment, an apparatus for side link discontinuous reception configuration includes a first user device. In some embodiments, an apparatus includes a processor to: initiating a side link unicast establishment process with the second user equipment; performing side link communication using a predetermined side link discontinuous reception configuration during a side link unicast setup procedure; and, in response to receiving the direct communication acceptance message, performing side link communication based on the set of side link discontinuous reception configurations.

In various embodiments, a method for side link discontinuous reception configuration includes receiving, at a second user device, information indicating initiation of a side link unicast setup procedure with a first user device. In some embodiments, the method includes performing side-link communication during a side-link unicast setup procedure using a predetermined side-link discontinuous reception configuration. In various embodiments, a method includes, in response to sending a direct communication accept message, performing side link communication based on a set of side link discontinuous reception configurations.

In some embodiments, an apparatus for side link discontinuous reception configuration includes a second user equipment. In some embodiments, the apparatus further comprises a receiver that receives information indicating initiation of a sidelink unicast setup procedure with the first user device. In various embodiments, the apparatus further comprises a processor that: performing side link communication using a predetermined side link discontinuous reception configuration during a side link unicast setup procedure; and, in response to sending the direct communication accept message, performing side link communication based on the set of side link discontinuous reception configurations.

Drawings

A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered limiting of scope, embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:

fig. 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for a side link discontinuous reception configuration;

FIG. 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for a side link discontinuous reception configuration;

fig. 3 is a schematic block diagram illustrating another embodiment of an apparatus that may be used for a side link discontinuous reception configuration;

FIG. 4 is a communication diagram illustrating one embodiment of a communication with a side link discontinuous reception configuration;

FIG. 5 is a communication diagram illustrating another embodiment of a communication having a side link discontinuous reception configuration;

FIG. 6 is a communication diagram illustrating a further embodiment of a communication having a side link discontinuous reception configuration;

FIG. 7 is a communication diagram illustrating yet another embodiment of a communication having a side link discontinuous reception configuration;

fig. 8 is a schematic flow chart diagram illustrating one embodiment of a method for side link discontinuous reception configuration; and

Fig. 9 is a schematic flow chart diagram illustrating another embodiment of a method for side link discontinuous reception configuration.

Detailed Description

As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method or program product. Thus, an embodiment may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," module, "or" system. Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code and/or program code, hereinafter referred to as code. The storage devices may be tangible, non-transitory, and/or non-transmitting. The storage device may not embody a signal. In a certain embodiment, the storage device only employs signals for the access code.

Some of the functional units described in this specification may be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very large scale integration ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

Modules may also be implemented in code and/or software for execution by various types of processors. The identified code module may, for instance, comprise one or more physical or logical blocks of executable code, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

Indeed, a code module may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer-readable storage devices. Where a module or portion of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device that stores code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system, apparatus or device, or any suitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or flash memory), a portable compact disc read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Code for performing operations of embodiments may be any number of rows and may be written in any combination including one or more of an object oriented programming language, such as Python, ruby, java, smalltalk, C ++, and a conventional procedural programming language, such as the "C" programming language, and/or a machine language, such as assembly language. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer, partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

Reference throughout this specification to "one embodiment," "an embodiment," or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases "in one embodiment," in an embodiment, "and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean" one or more but not all embodiments. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise. The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms "a," "an," and "the" also mean "one or more" unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that an embodiment may be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments.

Aspects of the embodiments are described below with reference to schematic flow chart diagrams and/or schematic block diagrams of methods, apparatuses, systems and program products according to the embodiments. It will be understood that each block of the schematic flow diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flow diagrams and/or schematic block diagrams, can be implemented by codes. The code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart and/or schematic block diagram block or blocks.

The code may further be stored in a storage device that is capable of directing a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or block diagram block or blocks.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which executes on the computer or other programmable apparatus provides processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The schematic flow chart diagrams and/or schematic block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flow diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).

It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated figure.

Although various arrow types and line types may be employed in the flow chart diagrams and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For example, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and code.

The description of the elements in each figure may refer to the elements of the preceding figures. Like reference numerals refer to like elements throughout, including alternative embodiments of like elements.

Fig. 1 depicts an embodiment of a wireless communication system 100 for a side link discontinuous reception configuration. In one embodiment, wireless communication system 100 includes a remote unit 102 and a network unit 104. Even though a particular number of remote units 102 and network units 104 are depicted in fig. 1, one skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in wireless communication system 100.

In one embodiment, the remote units 102 may include computing devices such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smart phones, smart televisions (e.g., televisions connected to the internet), set-top boxes, game consoles, security systems (including security cameras), on-board computers, network devices (e.g., routers, switches, modems), ioT devices, and the like. In some embodiments, remote unit 102 comprises a wearable device, such as a smart watch, a fitness band, an optical head mounted display, or the like. Further, remote unit 102 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user equipment ("UE"), user terminal, device, or other terminology used in the art. Remote units 102 may communicate directly with one or more network units 104 via uplink ("UL") communication signals and/or remote units 102 may communicate directly with other remote units 102 via side link communication.

Network elements 104 may be distributed over a geographic area. In some embodiments, network element 104 may also be referred to as and/or may include one or more of an access point, an access terminal, a base station, a node B, an evolved node B ("eNB"), a 5G node B ("gNB"), a home node B, a relay node, a device, a core network, an air server, a radio access node, an access point ("AP"), a new radio ("NR"), a network entity, an access and mobility management function ("AMF"), a unified data management ("UDM"), a unified data repository ("UDR"), a UDM/UDR, a policy control function ("PCF"), a radio access network ("RAN"), a network slice selection function ("NSSF"), an operation, administration and management ("OAM"), a session management function ("SMF"), a user plane function ("UPF"), an application function, an authentication server function ("AUSF"), a security anchor function ("SEAF"), a trusted non-3 GPP gateway function ("tnff"), or any other terminology used in the art. The network elements 104 are typically part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network elements 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks, such as the internet and public switched telephone networks. These and other elements of the radio access and core networks are not illustrated but are generally well known to those of ordinary skill in the art.

In one embodiment, the wireless communication system 100 conforms to the NR protocol standardized in the third Generation partnership project ("3 GPP"), wherein the network element 104 is in the downlinkThe transmission is performed using an OFDM modulation scheme on the ("DL") and the remote unit 102 transmits on the uplink ("UL") using a single carrier frequency division multiple access ("SC-FDMA") scheme or an orthogonal frequency division multiplexing ("OFDM") scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, such as, for example, wiMAX, institute of Electrical and electronics Engineers ("IEEE") 802.11 variants, global System for Mobile communications ("GSM"), general packet radio service ("GPRS"), universal Mobile telecommunications system ("UMTS"), long term evolution ("LTE") variants, code division multiple Access 2000 ("CDMA 2000")ZigBee, sigfoxx, and other protocols. The present disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

Network element 104 may serve a plurality of remote units 102 within a service area, such as a cell or cell sector, via wireless communication links. The network element 104 transmits DL communication signals to serve the remote units 102 in the time, frequency, and/or spatial domains.

In various embodiments, the remote unit 102 (e.g., the first user device) may initiate a sidelink unicast setup procedure with the second user device (e.g., the remote unit 102). In some embodiments, remote unit 102 may perform side-link communications during a side-link unicast setup procedure using a predetermined side-link discontinuous reception configuration. In various embodiments, remote unit 102 may perform side-link communication based on the set of side-link discontinuous reception configurations in response to receiving the direct communication accept message. Thus, remote unit 102 may be used in a side link discontinuous reception configuration.

In some embodiments, the remote unit 102 (e.g., the second user device) may receive information indicating that a sidelink unicast setup procedure with the first user device (e.g., the remote unit 102) is initiated. In some embodiments, remote unit 102 may perform side-link communications during a side-link unicast setup procedure using a predetermined side-link discontinuous reception configuration. In various embodiments, remote unit 102 may perform side-link communications based on a set of side-link discontinuous reception configurations in response to sending the direct communication accept message. Thus, remote unit 102 may be used in a side link discontinuous reception configuration.

Fig. 2 depicts one embodiment of an apparatus 200 that may be used for a side link discontinuous reception configuration. Apparatus 200 includes one embodiment of remote unit 102. In addition, remote unit 102 may include a processor 202, memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touch screen. In some embodiments, remote unit 102 may not include any input device 206 and/or display 208. In various embodiments, remote unit 102 may include one or more of processor 202, memory 204, transmitter 210, and receiver 212, and may not include input device 206 and/or display 208.

In one embodiment, processor 202 may include any known controller capable of executing computer-readable instructions and/or capable of performing logic operations. For example, the processor 202 may be a microcontroller, microprocessor, central processing unit ("CPU"), graphics processing unit ("GPU"), auxiliary processing unit, field programmable gate array ("FPGA"), or similar programmable controller. In some embodiments, processor 202 executes instructions stored in memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes a volatile computer storage medium. For example, memory 204 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and/or static RAM ("SRAM"). In some embodiments, memory 204 includes a non-volatile computer storage medium. For example, memory 204 may include a hard drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and nonvolatile computer storage media. In some embodiments, memory 204 also stores program codes and related data, such as an operating system or other controller algorithm operating on remote unit 102.

In one embodiment, input device 206 may include any known computer input device including a touchpad, buttons, keyboard, stylus, microphone, and the like. In some embodiments, the input device 206 may be integrated with the display 208, for example, as a touch screen or similar touch sensitive display. In some embodiments, the input device 206 includes a touch screen such that text may be entered using a virtual keyboard displayed on the touch screen and/or by handwriting on the touch screen. In some embodiments, the input device 206 includes two or more different devices such as a keyboard and a touchpad.

In one embodiment, the display 208 may comprise any known electronically controllable display or display device. The display 208 may be designed to output visual, audible, and/or tactile signals. In some embodiments, the display 208 comprises an electronic display capable of outputting visual data to a user. For example, the display 208 may include, but is not limited to, a liquid crystal display ("LCD"), a light emitting diode ("LED") display, an organic light emitting diode ("OLED") display, a projector, or similar display device capable of outputting images, text, and the like to a user. As another non-limiting example, the display 208 may include a wearable display such as a smart watch, smart glasses, head-up display, and the like. Further, the display 208 may be a component of a smart phone, personal digital assistant, television, desktop computer, notebook (laptop) computer, personal computer, vehicle dashboard, or the like.

In some embodiments, the display 208 includes one or more speakers for producing sound. For example, the display 208 may generate an audible alarm or notification (e.g., a beep or beep). In some embodiments, the display 208 includes one or more haptic devices for generating vibrations, motion, or other haptic feedback. In some embodiments, all or part of the display 208 may be integrated with the input device 206. For example, the input device 206 and the display 208 may form a touch screen or similar touch sensitive display. In other embodiments, the display 208 may be located near the input device 206.

In one embodiment, the processor 202 may: initiating a side link unicast establishment process with the second user equipment; performing side link communication using a predetermined side link discontinuous reception configuration during a side link unicast setup procedure; and in response to receiving the direct communication acceptance message, performing side link communication based on the set of side link discontinuous reception configurations.

In various embodiments, the receiver 212 may receive information indicating to initiate a sidelink unicast setup procedure with the first user device. In various embodiments, the processor 202 may: performing side link communication using a predetermined side link discontinuous reception configuration during a side link unicast setup procedure; and, in response to sending the direct communication accept message, performing side link communication based on the set of side link discontinuous reception configurations.

Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and receiver 212 may be any suitable type of transmitter and receiver. In one embodiment, the transmitter 210 and the receiver 212 may be part of a transceiver.

Fig. 3 depicts another embodiment of an apparatus 300 that may be used for a side link discontinuous reception configuration. The apparatus 300 comprises one embodiment of the network element 104. Further, the network element 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As can be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 can be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212, respectively, of the remote unit 102.

Although only one transmitter 310 and one receiver 312 are illustrated, the network element 104 may have any suitable number of transmitters 310 and receivers 312. The transmitter 310 and the receiver 312 may be any suitable type of transmitter and receiver. In one embodiment, the transmitter 310 and the receiver 312 may be part of a transceiver.

Although various embodiments are described herein, any embodiment described herein may be combined with other embodiments described herein as long as the features of the embodiments are not mutually exclusive. In some embodiments, it may not be clear which DRX configuration to use during the side link ("SL") unicast setup procedure and after the SL unicast link has been established until during the period of configuring the DRX configuration between peer UEs of the used SL unicast link. In such embodiments, the peers UE DRX ActiveTime may be aligned such that they are able to send and/or receive UE-to-UE interface ("PC 5") RRC messages during the SL RRCReconfiguration procedure for configuring DRX configurations.

In some embodiments, such as for NRUu operation, a drx-inactivatytimer timer may not be started for DL SPS transmissions. In various embodiments, a UE starts a drx-HARQ-RTT-TimerDL for a corresponding hybrid automatic repeat request ("HARQ") process in a first symbol after a corresponding transmission carrying DL HARQ feedback ends. Similar behavior may be used for grant transmission for UL configuration. In some embodiments, because the sidelink control information ("SCI") is sent with the PSSCH for SL transmissions over the PC5 interface, the UE may start an SLdrx-incaactyittmer timer for SL resources allocated by the sidelink ("SL") configuration grant ("CG"). In such embodiments, the receiver ("RX") UE may not be aware of the SL CG assignment. In various embodiments, starting the SLdrx-inactivity timer for SL CG transmissions may result in increased power consumption, as DRX ActiveTime may be unnecessarily extended.

In various embodiments, each SL logical channel ("LCH"), SL service, SL application, and/or SL destination may be associated with a preconfigured and/or fixed SL-DRX configuration (e.g., which may be defined as a combination of offset_std_on-duration, on-duration-timer, and/or periodicity). In some embodiments, SL On-duration is started at a fixed Time offset (e.g., offset_std_on-duration) from time_0, directly or indirectly from a side link synchronization signal ("SLSS"), based On a synchronization source from a global navigation satellite system ("GNSS"), gNB. In some embodiments, the On-duration-timer may be periodically restarted. It should be noted that the term SL "ActiveTime" may refer to a period of time in which the SL UE transmits and receives data and/or control over the PC5 interface.

In some embodiments, predefined public PC5 5G QoS indicators ("5 QI") ("PQI") and/or destination-specific SL DRX modes and/or configurations may facilitate SL data transmission for particular applications, services, destinations, and/or LCHs for synchronization between UEs of interest to the services and/or applications. In such embodiments, the TX side of the UE may need to know when the RX UE listens for data from a particular SL LCH and/or application, and the RX side of the UE may need to know when to monitor for SL data and/or control a particular SL LCH and/or application. In various embodiments, SL DRX mode and/or configuration may improve power consumption of the UE, as UEs interested in a particular SL service and/or application may only need to be active on the PC5 interface for a certain predetermined period of time (e.g., monitoring SCI and/or PSSCH). In some embodiments, two separate DRX modes and/or activetimes can be used for the sidelink UE (e.g., one DRX mode and/or ActiveTime defining when the SL UE (TX side) is allowed to transmit SL data and/or control to the peer UE over the PC5 interface and another separate DRX mode and/or ActiveTime defining when the same SL UE (RX UE) is to receive SL data and/or control from the peer UE). It should be noted that the embodiments described herein may be applied to different approaches (e.g., one common DRX mode and/or ActiveTime for each sidelink UE or two separate DRX modes and/or activetimes for each SL UE-one for the TX side and one for the RX side).

In some embodiments, a common, predefined, and/or preconfigured DRX configuration for PC5 control signaling may be used to specify a period of time (e.g., DRX ActiveTime) for exchanging PC5 control signaling (e.g., between unicast connected peer UEs (RX and/or TX UEs)). In such embodiments, control signaling may be used for PC5RRC signaling and/or PC5-S signaling. In some embodiments, PC5 control signaling is handled with respect to DRX behavior and/or configuration, similar to vehicle-to-all ("V2X") services (e.g., SL and/or V2X services may have associated DRX configurations). In an embodiment, the UE may have one or more DRX configurations associated with V2X services and/or QoS flows and one or more DRX configurations for PC5 control signaling. In some embodiments, PC5RRC signaling may be accomplished through a side link signaling radio bearer ("SRB") on the logical channel SCCH. In some embodiments, the common DRX configuration for SL SRBs may be predefined and/or preconfigured. In such embodiments, the predefined DRX configuration may be used to exchange signaling messages for establishing a PC5-RRC connection that is initiated after the corresponding unicast link has been established. Further, in such embodiments, the common DRX configuration may be derived by the SL UE based on the L2 destination ID. In some embodiments, the RX and TX UEs of the unicast link may receive and/or transmit PC5RRC messages associated with the PC5 unicast link using a common and/or preconfigured DRX configuration. In such embodiments, PC5RRC messages for a SL RRC reconfiguration procedure to configure a SL DRX configuration for use between RX and/or TX UEs of a unicast link (e.g., a pair of source and/or destination) may be sent and/or received within a DRX ActiveTime based on a predefined and/or preconfigured DRX configuration.

Fig. 4 is a communication diagram illustrating one embodiment of a communication 400 having a side link discontinuous reception configuration. Communication 400 includes messages sent between UE1 402 and UE2 404. Each of the communications 400 may include one or more messages.

In the first communication 406 sent from UEl 402 to UE2 404, UEl 402 sends an rrcrecon configuration sidelink message for DRX of UE2 404 to UE2 404. In a second communication 408 sent from UE2 404 to UE1 402, UE2 404 sends an rrcrecon configuration completesilink message to UE1 402. In a third communication 410 sent from UE2 404 to UE1 402, UE2 404 sends an rrcrecon configuration sip link message to UE1 402 for DRX of UE1 402. In a fourth communication 412 sent from UE1 402 to UE2 404, UE1 402 sends RRC ReconfigurationCompleteSidelink a message to UE2 404.

In various embodiments, the SL UE may use one predefined and/or preconfigured DRX configuration for transmission and/or reception of SL SRB0, SL SRB1, and SL SRB2 messages. In such embodiments, another predefined and/or preconfigured DRX configuration may be used for transmission and/or reception of SL SRB3 messages (e.g., PC5RRC signaling).

In some embodiments, a common, predefined and/or preconfigured DRX configuration may be used for transmission and/or reception of PC5-S messages until PC5-S security has been established. In such embodiments, during establishment of a unicast link (e.g., layer-2 link establishment procedure), the initiating UE (TX UE) transmits a direct communication request ("DCR") message to initiate the unicast link (e.g., layer-2 link establishment procedure). The DCR message may be transmitted according to a common, predefined, and/or preconfigured DRX configuration (e.g., the DCR message may be transmitted during DRX ActiveTime to ensure that the peer UE is able to receive the DCR message (e.g., the peer UE is in ActiveTime monitoring SCI and/or physical side link shared channel ("PSCCH")). In some embodiments, the common DRX configuration may be derived from the L2 destination ID. In various embodiments, to initiate unicast communications, one side chain SRB (e.g., SL-SRB 0) may be used to send a PC5-S message before PC5-S security has been established. In such an embodiment, one side link SRB (e.g., SL-SRB 1) may be used to send a PC5-S message to establish PC5-S security. Furthermore, in such an embodiment, one side chain SRB (e.g., SL-SRB 2) may be used to send the PC5-S message after PC5-S security has been established (e.g., it is protected). Furthermore, in such an embodiment, one side chain SRB (e.g., SL-SRB 3) may be used to send PC5-RRC signaling (e.g., which is protected and only transmitted after PC5-S security has been established). In some embodiments, a predefined and/or preconfigured DRX configuration may be used for transmission and/or reception of SL-SRB0 and SL-SRB1 during the unicast link setup procedure up to and including at least the security mode command message. In such embodiments, the same DRX configuration may be used for secure mode complete message transmission and/or reception. Further, in such embodiments, the security mode command message includes some QoS information (e.g., information about the PC5 QoS flow that originated the UE (TX UE) request). For each PC5 QoS flow, packet format information ("PFI"), corresponding PC5 QoS parameters (e.g., PQI and/or other parameters such as maximum flow bit rate ("MFBR") and/or guaranteed flow bit rate ("GFBR")) and/or may include an associated V2X service type. In various embodiments, in response to transmission and/or reception of the security mode command message, peer and/or receiver UEs of the unicast link may apply a predefined and/or preconfigured DRX configuration for the QoS flow (e.g., a PQI associated with the QoS flow-a common, predefined and/or preconfigured DRX configuration may be used for each PQI).

In some embodiments, common, predefined and/or preconfigured DRX configurations may be used to transmit and/or receive SL-SRB0, SL-SRB1 and SL-RB2 during the unicast link setup procedure up to and including transmitting and/or receiving direct communication acceptance ("DCA") messages. In one embodiment, common, preconfigured and/or known SL DRX configurations may be derived based on the L2 destination ID. In some embodiments, the DCA message includes QoS information (e.g., information about PC5 QoS flows requested by the initiating UE (TX UE) for each PC5 QoS flow, PFIs, corresponding PC5 QoS parameters (e.g., PQI and/or other parameters such as MFBR and/or GFBR), and/or associated V2X service types). In various embodiments, in response to transmission and/or reception of the DCA message, peer UEs of the unicast link may apply a predefined and/or preconfigured DRX configuration for QoS flows, e.g., qoS flows signaled within the DCA message (e.g., PQI associated with QoS flows—for each PQI, a predefined and/or preconfigured DRX configuration may be used). As described with respect to fig. 5, a predefined SL DRX configuration (e.g., derived based on the established QoS flows and/or the PQI of the SL RBs) may be used until the peer UE configures a different DRX configuration using the rrcr configuration sidelink procedure (e.g., until a rrcr configuration sidelink complete message is received).

Fig. 5 is a communication diagram illustrating another embodiment of a communication 500 having a side link discontinuous reception configuration. Communication 500 includes messages sent between UE1 502 and UE2 504. Each of the communications 500 may include one or more messages.

The UE2 504 may determine 506 a destination layer-2 ID for signaling reception. UE1 502 may have a V2X application layer that provides 508 application information for PCF unicast communications. In a first communication 510 transmitted from UE1 502 to UE2 504, UE1 502 transmits a DCR (e.g., broadcast or unicast) to UE2 504. In a second communication 512 sent between UE1 502 and UE2 504, a security setup message may be sent. In a third communication 514 sent from UE2 504 to UE1 502, UE2 504 sends a direct communication accept message (e.g., unicast) to UE1 502. In a fourth communication 516 transmitted between UE1 502 and UE2 504, V2X service data may be transmitted over a unicast link. It should be noted that the UE-oriented layer-2 link establishment occurs via the second communication 512, the third communication 514, and the fourth communication 516. Further, the first communication 510, the second communication 512, and the third communication 514 may be performed using common and/or pre-configured DRX configurations (e.g., DRX configurations that are not related to QoS and/or PQI).

In a fifth communication 518 sent from UE1 502 to UE2 504, UE1 502 sends an rrcrecon configuration sidelink message for DRX for UE2 504 to UE2 504. In a sixth communication 520 sent from UE2 504 to UE1 502, UE2 504 sends an rrcrecnonfigurationcompletesinlink message to UE1 502. In a seventh communication 522 sent from UE2 504 to UE1 502, UE2 504 sends an rrcrecon configuration sidelink message for DRX for UE1 502 to UE1 502. In an eighth communication 524 sent from UE1 502 to UE2 504, UE1 502 sends an rrcrecnonfigurationcompletesinlink message to UE2 504. It should be noted that DRX fine adjustment occurs via fifth communication 518, sixth communication 520, seventh communication 522, and eighth communication 524. Further, fourth communication 516, fifth communication 518, sixth communication 520, seventh communication 522, and eighth communication 524 may be performed using pre-configured DRX configurations associated with the PQI and/or QoS flows (e.g., qoS flows and/or PQI that signal a direct communication accept message (e.g., a set of DRX configurations) within third communication 514). In a ninth communication 526 transmitted between UE1 502 and UE2 504, V2X service data may be transmitted over the unicast link using a dedicated DRX configuration for the unicast link.

In some embodiments, the peer UEs may use a common, predefined, and/or preconfigured DRX configuration when establishing a unicast link (e.g., layer-2 link establishment procedure) between the peer UEs. In one embodiment, the pre-configured DRX configuration may be used for transmission and/or reception of DCR messages, security setup procedures, and/or DCA messages. In some embodiments, the preconfigured DRX configuration may be used by the peer UE after SL unicast setup (e.g., for transmission and/or reception of SL service data) until the peer UE configures a different DRX configuration using SL RRCReconfiguration procedure (e.g., until SL RRCReconfiguration completes reception of the message). In various embodiments, a predefined DRX configuration may be used for SL RRCReconfiguration procedures to configure and/or fine tune the DRX configuration between peer UEs for the PC5 unicast link. In some embodiments, the predefined and/or preconfigured DRX configuration may be based on the PQI of the service data. In some embodiments, a receiver (e.g., of a DCR) may anticipate which QoS flows, profiles, and/or PQI (e.g., services, service types, and/or applications and their messages, data, etc.) of the corresponding DRX configuration the receiver expects to receive and/or monitor. In various embodiments, to facilitate the receiver's knowledge of the intended PQI, a preconfigured list of V2X service identifier to PC5 QoS parameter mapping rules may be used. In some embodiments, the UE (e.g., transmitter and receiver) may be configured with default values for PC5 QoS parameters for particular services (e.g., identified by a public service ID ("PSID") and/or an intelligent transport system application identifier ("ITS-AID"). In some embodiments, default values may be used if the upper layer does not provide the corresponding PC5 QoS parameters. In various embodiments, the receiver of the potential DCR may be able to expect and monitor the transmission of certain PQI because the expected PSID and/or ITS-AID services may be known to the receiver and mapped to the default QoS. As can be appreciated, the ability of the receiver UE to anticipate and/or monitor PQI may not be limited to unicast communications, but may be used by potential receivers of multicast or broadcast communications.

Fig. 6 is a communication diagram illustrating a further embodiment of a communication 600 having a side link discontinuous reception configuration. Communication 600 includes messages sent between UE1 602 and UE2 604. Each of communications 600 may include one or more messages.

The UE2 604 may determine a destination layer-2 id 606 for signaling reception. UE1 602 may have a V2X application layer that provides 608 application information for PCF unicast communications. In a first communication 610 transmitted from UE1 602 to UE2 604, UE1 602 transmits a DCR (e.g., broadcast or unicast) to UE2 604. In a second communication 612 sent between UE1 602 and UE2 604, a security setup message may be sent. In a third communication 614 sent from UE2 604 to UE1 602, UE2 604 sends a direct communication accept message (e.g., unicast) to UE1 602. In a fourth communication 616 sent between UE1 602 and UE2 604, V2X service data may be sent over a unicast link. It should be noted that the UE-oriented layer-2 link establishment occurs via the second communication 612, the third communication 614, and the fourth communication 616.

In a fifth communication 618 sent from UE1 602 to UE2 604, UE1 602 sends an rrcrecon configuration sidelink message for DRX for UE2 604 to UE2 604. In a sixth communication 620 sent from UE2 604 to UE1 602, UE2 604 sends an rrcrecconfiguration sidelink message to UE1 602. In a seventh communication 622 transmitted from UE2 604 to UE1 602, UE2 604 transmits an rrcrecon configuration sidelink message for DRX for UE1 602 to UE1 602. In an eighth communication 624 sent from UE1 602 to UE2 604, UE1 602 sends an rrcrecnonfigurationcompletesinlink message to UE2 604. It should be noted that DRX fine adjustment occurs via fifth communication 618, sixth communication 620, seventh communication 622, and eighth communication 624. Also, the first communication 610, the second communication 612, the third communication 614, the fourth communication 616, the fifth communication 618, the sixth communication 620, the seventh communication 622, and the eighth communication 624 may be performed using a pre-configured DRX configuration (e.g., a DRX configuration that is not related to QoS and/or PQI). In a ninth communication 626 transmitted between UE1 602 and UE2 604, V2X service data may be transmitted over the unicast link using a dedicated DRX configuration for the unicast link.

In some embodiments, the period of time after the SL unicast link has been established until each pair of source and/or destination between the RX and TX UEs configures the SL DRX configuration (e.g., by means of the SL RRCReconfiguration procedure) may be considered DRX ActiveTime (e.g., no DRX applied). In some embodiments, the PC5 RRC message may be used to configure DRX configuration between RX and TX UEs for a unicast transmission, which may be sent on SRB3, which may be transmitted at any point in time. In various embodiments, in response to having sent the rrcrecon configuration completeidelink message, the UE configures DRX configured between peer UEs for transmission and/or reception of PC5 control signaling (e.g., PC5 RRC signaling and/or PC5-S signaling).

In some embodiments, a pre-configured and/or predefined DRX configuration may be used for transmission and/or reception of SL logical channels with logical channel priority equal to 1. In various embodiments, the SL SRB with the highest logical channel priority is the SL SRB with the logical channel priority set to 1. In some embodiments, preconfigured and/or predefined DRX configurations may be used for SL SRBs.

In various embodiments, PC5 RRC signaling may be sent and/or received within DRX ActiveTime configured for unicast links. In some embodiments, the unicast communication link establishes V2X services between peer UEs over the PC5 interface. In some embodiments, the V2X service running in the UE uses a PC5 unicast link (e.g., a PC5-RRC connection) as a logical link established between a pair of UEs to communicate between the pair of UEs. In various embodiments, a UE may have multiple PC5-RRC connections (e.g., unicast connections with one or more UEs and/or source and destination L2ID pairs for different services). In these embodiments, the UE may use multiple DRX configurations concurrently (e.g., one DRX configuration per unicast link or one DRX configuration per V2X service, PQI, and/or destination ID). Also, in such embodiments, PC5 RRC signaling for a PC5-RRC connection (e.g., unicast link) is transmitted and/or received according to any DRX configuration used by the UE for the corresponding PC5 unicast link.

Fig. 7 is a communication diagram illustrating yet another embodiment of a communication 700 having a side link discontinuous reception configuration. The communication 700 includes messages sent between UE1 702 and UE2 704. Each of communications 700 may include one or more messages. The UEs 702 and 704 may have multiple application layer IDs, resulting in potentially multiple PC5 links.

Specifically, UE1 702 includes an application layer ID1 706 and an application layer ID3 708. Also, the application layer ID1 706 includes V2X service a 710 and V2X service B712. Also, the application layer ID3 708 includes V2X service C714. UE2 704 includes an application layer ID2 716 and an application layer ID4 718. Also, the application layer ID2 716 includes V2X service a 720 and V2X service B722. Also, the application layer ID4 718 includes V2X service C724. PC5 unicast link 1 726 includes PC5QoS flow 1 728 and PC5QoS flow 2 730. Also, PC5 unicast link 2 732 includes PC5QoS flow 3 734 and PC5QoS flow 4 736.

In various embodiments, the unicast link may be between the same pair of UEs (e.g., different applications may be launched to initiate such unicast links). In some embodiments, to receive and/or transmit PC5 RRC signaling for PC5 unicast link 1 726, UE1 702 and UE2 704 may use any of the DRX configurations (e.g., DRX ActiveTime) configured for PC5 unicast link 1 726 (e.g., one DRX configuration may exist for each QoS flow of PC5 unicast link 1 726).

In some embodiments, a field in the SCI indicates whether the RX UE should start an SLdrx-inactivity timer in response to receipt of the SCI, e.g., the UE is in DRX activity time and the SLdrx-inactivity timer is running. In such an embodiment, the SCI indicates whether the SLdrx-activity timer should be started, because the RX UE does not know whether the SL resources are allocated by a SL configured grant allocation (e.g., SL CG allocated by the gNB (mode 1)) or by a dynamic grant allocation. It should be noted that for SL CG resources, the SLdrx-inactivity timer should not be started (e.g., similar to the Uu interface where Drx-inactivity is not started for SL semi-persistent scheduling ("SPS") transmissions). In Uu, DRX-inactivityTimer cannot be started for DL SPS (e.g., CG) transmissions. In various embodiments, drx-HARQ-RTT-TimerDL may be initiated after transmission of DL HARQ feedback (e.g., sent on a physical uplink control channel ("PUCCH").

In some embodiments, if a MAC protocol data unit ("PDU") is received in a configured downlink assignment, 1) starting drx-HARQ-RTT-TimerDL for a corresponding HARQ process in a first symbol after the end of the corresponding transmission carrying DL HARQ feedback; and 2) stop drx-retransmission timerdl for the corresponding HARQ process.

In some embodiments, information regarding whether to start an SLdrx-activity timer and/or a physical side link shared channel ("PSSCH") in response to receipt of the SCI is carried within the level 1 SCI. In such an embodiment, one of the reserved bits in the level 1 SCI may be used to carry this information.

In various embodiments, the SCI may indicate whether the SL resource is a SL CG resource or a dynamically allocated SL resource. In one embodiment, the RX UE may start an SLdrx-activity timer in response to receiving the SCI indicating the dynamically allocated SL resource. In response to receiving the SCI indicating that the corresponding SL resource (e.g., PSSCH) is dynamically allocated, the UE starts an SLdrx-inactivity timer. One embodiment of SCI (e.g., SCI format 1-a) is shown in table 1.

Table 1: SCI Format 1-A

/>

In some embodiments, the UE does not start an SLdrx-activity timer (e.g., the resource reservation period is set to a value other than 0) in response to receiving the SCI indicating reserved resources. In some embodiments, such as for mode 2, a resource reservation period within the sci may be used to indicate SL resources for more than one transport block ("TB") (e.g., multiple MAC PDU transmissions). In such an embodiment, the SCI indicates reserved SL resources for multiple subsequent TBs, and the RX UE may not start the SL-connectivity timer. In such an embodiment, the receiving UE may treat the time slot indicated in the SCI as reserved resources for further transmission as discontinuous reception ("DRX") ActiveTime. Also, in such embodiments, the peer transmitter ("TX") UE may treat the slots and/or subframes indicated within the SCI as DRX active times (e.g., TX UE is enabled to transmit in those side slots).

Fig. 8 is a schematic flow chart diagram illustrating one embodiment of a method 800 for side link discontinuous reception configuration. In some embodiments, the method 800 is performed by a device, such as the remote unit 102. In some embodiments, method 800 may be performed by a processor executing program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or the like.

The method 800 may include initiating 802, by a first user equipment, a sidelink unicast establishment procedure with a second user equipment. In some embodiments, method 800 includes performing 804 side-link communications during a side-link unicast setup procedure using a predetermined side-link discontinuous reception configuration. In various embodiments, method 800 includes performing 806 side-link communication based on a set of side-link discontinuous reception configurations in response to receiving the direct communication accept message.

In some embodiments, the predetermined side link discontinuous reception configuration is based on the destination identifier. In some embodiments, the set of side link discontinuous reception configurations is associated with a service identifier, a PC5 quality of service parameter, a PC5 5G quality of service identifier, quality of service flow information, or a combination thereof.

In various embodiments, the set of side link discontinuous reception configurations corresponds to: quality of service class; attributes of quality of service class; a range of attributes for the quality of service class; or some combination thereof. In one embodiment, the quality of service class is indicated by a quality of service class identifier, a PC5 quality of service parameter, and a PC5 5G quality of service identifier, or a combination thereof.

Fig. 9 is a schematic flow chart diagram illustrating another embodiment of a method 900 for side link discontinuous reception configuration. In some embodiments, the method 900 is performed by a device, such as the remote unit 102. In some embodiments, method 900 may be performed by a processor executing program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or the like.

The method 900 may include receiving 902, at a second user device, information indicating initiation of a sidelink unicast establishment procedure with a first user device. In some embodiments, method 900 includes performing 904 side-link communications during a side-link unicast setup procedure using a predetermined side-link discontinuous reception configuration. In various embodiments, method 900 includes performing side-link communication based on a set of side-link discontinuous reception configurations in response to sending the direct communication accept message 906.

In one embodiment, a method includes: initiating a side link unicast establishment process with the second user equipment by the first user equipment; performing side link communication using a predetermined side link discontinuous reception configuration during a side link unicast setup procedure; and in response to receiving the direct communication acceptance message, performing side link communication based on the set of side link discontinuous reception configurations.

In some embodiments, the predetermined side link discontinuous reception configuration is based on the destination identifier.

In some embodiments, the set of side link discontinuous reception configurations is associated with a service identifier, a PC5 quality of service parameter, a PC5 5G quality of service identifier, quality of service flow information, or a combination thereof.

In various embodiments, the set of side link discontinuous reception configurations corresponds to: quality of service class; attributes of quality of service class; a range of attributes for the quality of service class; or some combination thereof.

In one embodiment, the quality of service class is indicated by a quality of service class identifier, a PC5 quality of service parameter, and a PC5 5G quality of service identifier, or a combination thereof.

In one embodiment, an apparatus includes a first user device. The apparatus further comprises: a processor that: initiating a side link unicast establishment process with the second user equipment; performing side link communication using a predetermined side link discontinuous reception configuration during a side link unicast setup procedure; and in response to receiving the direct communication acceptance message, performing side link communication based on the set of side link discontinuous reception configurations.

In one embodiment, a method includes: receiving, at the second user equipment, information indicating initiation of a sidelink unicast establishment procedure with the first user equipment; performing side link communication using a predetermined side link discontinuous reception configuration during a side link unicast setup procedure; and in response to sending the direct communication acceptance message, performing side link communication based on the set of side link discontinuous reception configurations.

In various embodiments, the set of side link discontinuous reception configurations corresponds to: quality of service class; attributes of quality of service class; a range of attributes for the quality of service class; or a combination thereof.

In one embodiment, an apparatus includes a second user device. The apparatus further comprises: a receiver that receives information indicating initiation of a sidelink unicast establishment procedure with the first user equipment; and a processor that: performing side link communication using a predetermined side link discontinuous reception configuration during a side link unicast setup procedure; and in response to sending the direct communication accept message, performing side link communication based on the set of side link discontinuous reception configurations.

Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1. A method, comprising:

initiating a side link unicast establishment process with the second user equipment by the first user equipment;

performing side link communication using a predetermined side link discontinuous reception configuration during the side link unicast setup procedure; and

side link communication is performed based on the set of side link discontinuous reception configurations in response to receiving the direct communication accept message.

2. The method of claim 1, wherein the predetermined side link discontinuous reception configuration is based on a destination identifier.

3. The method of claim 1, wherein the set of side link discontinuous reception configurations is associated with a service identifier, a PC5 quality of service parameter, a PC5 5G quality of service identifier, quality of service flow information, or a combination thereof.

4. The method of claim 1, wherein the set of side link discontinuous reception configurations corresponds to:

quality of service class;

attributes of the quality of service class;

a range of attributes of the quality of service class; or (b)

Some combination thereof.

5. The method of claim 4, wherein the quality of service class is indicated by a quality of service class identifier, a PC5 quality of service parameter, and a PC5 5G quality of service identifier, or a combination thereof.

6. An apparatus comprising a first user device, the apparatus further comprising:

a processor, the processor:

initiating a side link unicast establishment process with the second user equipment;

performing side link communication using a predetermined side link discontinuous reception configuration during the side link unicast setup procedure; and is also provided with

In response to receiving the direct communication acceptance message, side link communication is performed based on the set of side link discontinuous reception configurations.

7. The apparatus of claim 6, wherein the predetermined side link discontinuous reception configuration is based on a destination identifier.

8. The apparatus of claim 6, wherein the set of side-chain discontinuous reception configurations is associated with a service identifier, a PC5 quality of service parameter, a PC5 5G quality of service identifier, quality of service flow information, or a combination thereof.

9. The apparatus of claim 6, wherein the set of side link discontinuous reception configurations corresponds to:

quality of service class;

attributes of the quality of service class;

a range of attributes of the quality of service class; or (b)

Some combination thereof.

10. The apparatus of claim 9, wherein the quality of service class is indicated by a quality of service class identifier, a PC5 quality of service parameter, and a PC5 5G quality of service identifier, or a combination thereof.

11. A method, comprising:

receiving, at the second user equipment, information indicating initiation of a sidelink unicast establishment procedure with the first user equipment;

side link communication is performed based on the set of side link discontinuous reception configurations in response to sending the direct communication accept message.

12. The method of claim 11, wherein the predetermined side link discontinuous reception configuration is based on a destination identifier.

13. The method of claim 11, wherein the set of side link discontinuous reception configurations is associated with a service identifier, a PC5 quality of service parameter, a PC5 5G quality of service identifier, quality of service flow information, or a combination thereof.

14. The method of claim 11, wherein the set of side link discontinuous reception configurations corresponds to:

quality of service class;

attributes of the quality of service class;

a range of attributes of the quality of service class; or (b)

Some combination thereof.

15. The method of claim 14, wherein the quality of service class is indicated by a quality of service class identifier, a PC5 quality of service parameter, and a PC5 5G quality of service identifier, or a combination thereof.

16. An apparatus comprising a second user equipment, the apparatus further comprising:

a receiver that receives information indicating initiation of a sidelink unicast establishment procedure with a first user equipment; and

a processor, the processor:

17. The apparatus of claim 16, wherein the predetermined side link discontinuous reception configuration is based on a destination identifier.

18. The apparatus of claim 16, wherein the set of side-chain discontinuous reception configurations is associated with a service identifier, a PC5 quality of service parameter, a PC5 5G quality of service identifier, quality of service flow information, or a combination thereof.

19. The apparatus of claim 16, wherein the set of side link discontinuous reception configurations corresponds to:

quality of service class;

attributes of the quality of service class;

a range of attributes of the quality of service class; or (b)

Some combination thereof.

20. The apparatus of claim 19, wherein the quality of service class is indicated by a quality of service class identifier, a PC5 quality of service parameter, and a PC5 5G quality of service identifier, or a combination thereof.