CN115918007A

CN115918007A - Indication of a request for side link resources

Info

Publication number: CN115918007A
Application number: CN202180049673.4A
Authority: CN
Inventors: 约阿希姆·勒尔; 普拉泰克·巴苏马利克; 凯斯基延·盖内森; 拉维·库奇波特拉
Original assignee: Lenovo Singapore Pte Ltd
Current assignee: Lenovo Singapore Pte Ltd
Priority date: 2020-07-13
Filing date: 2021-07-10
Publication date: 2023-04-04
Also published as: WO2022013698A3; JP2023534266A; MX2023000592A; MX2023000591A; CA3182840A1; WO2022013698A2; US20230276364A1; CA3182835A1; WO2022013717A3; WO2022013700A1; KR20230038192A; BR112023000507A2; JP2023535892A; KR20230038199A; EP4179795A2; WO2022013717A2; CN115769638A; US20230262601A1; CN115769663A; BR112023000651A2

Abstract

Apparatus, methods, and systems for indicating a request for resources of a contralateral link are disclosed. A method (500) includes receiving (502) a hybrid automatic repeat request feedback message over a first radio interface. The method (500) comprises transmitting (504) a negative acknowledgement on a physical uplink control channel of the second radio interface in response to determining that the hybrid automatic repeat request feedback message indicates unsuccessful decoding of the corresponding transport block. The negative acknowledgement indicates a request for sidelink resources on the first radio interface. The method (500) includes starting (506) a timer in response to transmitting a negative acknowledgement.

Description

Indication of a request for side link resources

Cross Reference to Related Applications

The present application claims U.S. patent application Ser. Nos. 63/Ding,207, US patent application Ser. Nos. 207, US patent application Ser. No. 2020, US patent application Ser. No. 13/D, US patent application Ser. No. 13/051,184 entitled "APPATATATUSES, METHOD AND SYSTEM FOR SIDE DRX MECHANISM-INTERACTION WITH UU DRX OPERATION" filed by Joachim Loehr on 13.2020, US patent application Ser. No. 63/051,184 entitled "APPATEAS, METHOD AND SYSTEM FOR SIGTRANS POWER SAVING USING A DRX MECHANISM AND MINIMINIZHIZINING HALF DUPLISES filed on 13.7.2020 by Joachim Loehr on 13.2020,2020,2020, U.S. patent application Ser. Nos. 63/051,217 to METHOD, AND SYSTEM FOR SUPPORTING POWER AND PC5 COMMUNICATIONS (an apparatus, method, AND system FOR POWER SAVING to support PC5 COMMUNICATIONS), AND U.S. patent application Ser. No. 63/051,233 entitled" APPARATUS, METHOD, AND SYSTEM FOR ENHANCEMENT FOR SL POWER SAVING (an apparatus, method, AND system FOR enhancing SL POWER SAVING) "filed on 13.7.2020, of Karthikeyan Ganesan, priority, all of which are incorporated herein by reference in their entirety.

Technical Field

The subject matter disclosed herein relates generally to wireless communications, and more particularly to indication of a request for sidelink resources.

Background

In some wireless communication networks, power and other resources may be inefficiently used. For example, sidelink resources may be statically used for sidelink transmissions.

Disclosure of Invention

A method for indicating a request for link resources is disclosed. The apparatus and system also perform the functions of the method. One embodiment of a method includes receiving a hybrid automatic repeat request feedback message over a first radio interface. In some embodiments, the method includes transmitting a negative acknowledgement on a physical uplink control channel of the second radio interface in response to determining that the hybrid automatic repeat request feedback message indicates unsuccessful decoding of the corresponding transport block. The negative acknowledgement indicates a request for sidelink resources on the first radio interface. In some embodiments, the method includes starting a timer in response to transmitting the negative acknowledgement.

An apparatus for indicating a request for contralateral link resources includes a receiver that receives a hybrid automatic repeat request feedback message over a first radio interface. In various embodiments, the apparatus includes a transmitter to transmit a negative acknowledgement on a physical uplink control channel of the second radio interface in response to determining that the hybrid automatic repeat request feedback message indicates unsuccessful decoding of the corresponding transport block. The negative acknowledgement indicates a request for sidelink resources on the first radio interface. In some embodiments, an apparatus includes a processor that starts a timer in response to transmitting a negative acknowledgement.

One embodiment of a method for providing assistance information includes determining a change in a discontinuous reception configuration applied over a first radio interface. In some embodiments, the method comprises triggering transmission of assistance information on the second radio interface in response to determining the change in the discontinuous reception configuration. In some embodiments, the method comprises transmitting the assistance information on the second radio interface in response to triggering transmission of the assistance information on the second radio interface.

An apparatus for providing auxiliary information includes a processor that: determining a change in a discontinuous reception configuration applied on a first radio interface; and, in response to determining the change in the discontinuous reception configuration, triggering transmission of assistance information on the second radio interface. In various embodiments, the apparatus includes a transmitter to transmit the aiding information on the second radio interface in response to triggering transmission of the aiding information on the second radio interface.

One embodiment of a method for receiving assistance information includes receiving assistance information corresponding to a first radio interface on a second radio interface. In some embodiments, a method includes determining discontinuous reception configuration information for a second radio interface based on assistance information corresponding to a first radio interface. In some embodiments, the method comprises transmitting discontinuous reception configuration information on a second radio interface.

An apparatus for receiving assistance information includes a receiver that receives assistance information corresponding to a first radio interface on a second radio interface. In various embodiments, an apparatus includes a processor that determines discontinuous reception configuration information for a second radio interface based on assistance information corresponding to a first radio interface. In some embodiments, the apparatus comprises a transmitter to transmit discontinuous reception configuration information on the second radio interface.

One embodiment of a method for sidelink resource determination includes receiving a sidelink grant. In some embodiments, the method includes determining whether side link resources allocated by the sidelink route grant are within a discontinuous reception active time associated with the sidelink logical channel. In some embodiments, the method includes, in response to determining that the sidelink resources allocated by the sidelink licenses are within a discontinuous reception activity time associated with the sidelink logical channel, using the sidelink logical channel in a logical channel prioritization procedure, a destination selection procedure, or a combination thereof.

An apparatus for sidelink resource determination includes a receiver that receives a sidelink grant. In various embodiments, an apparatus includes a processor that: determining whether sidelink resources allocated by sidelink grants are within a discontinuous reception activity time associated with a sidelink logical channel; and, in response to determining that the side link resources allocated by the sidelink route grant are within a discontinuous reception activity time associated with the sidelink logical channel, using the side link logical channel in a logical channel prioritization procedure, a destination selection procedure, or a combination thereof.

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 to be limiting of scope, the 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 indicating a request for contralateral link resources;

FIG. 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to indicate a request for sidelink resources;

FIG. 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to receive assistance information;

FIG. 4 is a schematic block diagram illustrating one embodiment of a system with communications indicating a request for contralateral link resources;

figure 5 is a flow diagram illustrating one embodiment of a method for indicating a request for contralateral link resources;

FIG. 6 is a flow diagram illustrating one embodiment of a method for providing assistance information;

FIG. 7 is a flow diagram illustrating one embodiment of a method for receiving assistance information; and

FIG. 8 is a flow diagram illustrating one embodiment of a method for side link resource determination.

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. Accordingly, embodiments 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 that store machine-readable code, computer-readable code, and/or program code, referred to hereinafter as code. The storage device may be tangible, non-transitory, and/or non-transmissive. The storage device may not embody the signal. In a certain embodiment, the storage device only employs signals for access codes.

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. An identified module of code 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 module of code 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 portions of a module are implemented in software, the software portions are 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 storing the code. A 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.

The code for performing the operations of an embodiment may be any number of lines and may be written in any combination including an object oriented programming language such as Python, ruby, java, smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or the like, and/or one or more programming languages, such as an 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 and 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 in the 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" unless expressly specified otherwise. The terms "include," "have," 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" and "an" 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, and so forth. 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 charts and/or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that each block of the schematic flow chart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flow chart diagrams and/or schematic block diagrams, can be implemented by code. The code can 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 also be stored in a memory device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the memory device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart and/or schematic 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 charts and/or schematic block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flow chart 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 diagram blocks, they are understood not to limit the scope of the corresponding embodiment. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, 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 elements of previous figures. Like numbers refer to like elements throughout, including alternative embodiments of the same elements.

Fig. 1 depicts an embodiment of a wireless communication system 100 for indicating a request for contralateral link resources. In one embodiment, wireless communication system 100 includes a remote unit 102 and a network unit 104. Although a particular number of remote units 102 and network units 104 are depicted in fig. 1, those skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

In one embodiment, remote unit 102 may include a computing device such as a desktop computer, laptop computer, personal digital assistant ("PDA"), tablet computer, smart phone, smart television (e.g., television connected to the internet), set-top box, game console, security system (including security camera), on-board computer, networking device (e.g., router, switch, modem), airborne vehicle, drone, or the like. In some embodiments, remote unit 102 includes a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, and the like. Moreover, remote unit 102 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, UE, user terminal, device, or other terminology used in the art. Remote unit 102 may communicate directly with one or more network elements 104 via UL communication signals. In some embodiments, remote units 102 may communicate directly with other remote units 102 via sidelink communications.

The network elements 104 may be distributed over a geographic area. In certain embodiments, the network element 104 may also be referred to and/or may include an access point, access terminal, base station, location server, core network ("CN"), radio network entity, node-B, evolved node-B ("eNB"), 5G node-B ("gNB"), home node-B, relay node, device, core network, over-the-air server, radio access node, access point ("AP"), new radio ("NR"), network entity, access and mobility management function ("AMF"), unified data management ("UDM"), unified data repository ("UDR"), UDM/UDR, policy control function ("PCF"), radio access network ("RAN"), network slice selection function ("NSSF"), operation, administration and management ("OAM"), session management function ("SMF"), user plane function ("UPF"), application function, authentication server function ("AUSF"), secure anchor function ("SEAF"), trusted non-3 GPP gateway function ("TNGF"), or any other term 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 networks are 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, as well as other 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"), where the network unit 104 transmits on the downlink ("DL") using an OFDM modulation scheme and the remote unit 102 uses a single OFDM modulation schemeA carrier frequency division multiple access ("SC-FDMA") scheme or an orthogonal frequency division multiplexing ("OFDM") scheme is transmitted on the uplink ("UL"). More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocols, such as WiMAX, an institute of electrical and electronics engineers ("IEEE") 802.11 variant, global system for mobile communications ("GSM"), general packet radio service ("GPRS"), universal mobile telecommunications system ("UMTS"), long term evolution ("LTE") variant, code division multiple access 2000 ("CDMA 2000"), "CDMA mobile telecommunications system (" UMTS "), and/or the like,

ZigBee, sigfoxx, and other protocols. The present disclosure is not intended to be limited to implementation by any particular wireless communication system architecture or protocol.

Network element 104 may serve multiple remote units 102 within a service area (e.g., a cell or cell sector) via wireless communication links. The network unit 104 transmits DL communication signals in the time, frequency, and/or spatial domains to serve the remote units 102.

In various embodiments, the remote unit 102 may receive the hybrid automatic repeat request feedback message over the first radio interface. In some embodiments, the remote unit 102 may transmit a negative acknowledgement on a physical uplink control channel of the second radio interface in response to determining that the hybrid automatic repeat request feedback message indicates unsuccessful decoding of the corresponding transport block. The negative acknowledgement indicates a request for sidelink resources on the first radio interface. In some embodiments, the remote unit 102 may start a timer in response to transmitting a negative acknowledgement. Thus, remote unit 102 may be used to indicate a request for sidelink resources.

In some embodiments, the remote unit 102 may determine a change in the discontinuous reception configuration applied over the first radio interface. In some embodiments, the remote unit 102 may trigger transmission of assistance information on the second radio interface in response to determining the change in the discontinuous reception configuration. In some embodiments, the remote unit 102 may transmit the aiding information on the second radio interface in response to triggering transmission of the aiding information on the second radio interface. Thus, remote unit 102 may be used to provide assistance information.

In various embodiments, the network element 104 may receive assistance information corresponding to the first radio interface on the second radio interface. In some embodiments, the network unit 104 may determine discontinuous reception configuration information for the second radio interface based on the assistance information corresponding to the first radio interface. In some embodiments, the network element 104 may transmit discontinuous reception configuration information on the second radio interface. Thus, the network element 104 may be used to receive assistance information.

In some embodiments, the remote unit 102 may receive a sidelink grant. In some embodiments, the remote unit 102 may determine whether the sidelink resources allocated by the sidelink grants are within a discontinuous reception activity time associated with the sidelink logical channel. In some embodiments, the method includes, in response to determining that the sidelink resources allocated by the sidelink licenses are within a discontinuous reception activity time associated with the sidelink logical channel, using the sidelink logical channel in a logical channel prioritization procedure, a destination selection procedure, or a combination thereof. Thus, the remote unit 102 may be used for sidelink resource determination.

Fig. 2 depicts one embodiment of an apparatus 200 that may be used to indicate a request for sidelink resources. The apparatus 200 includes one embodiment of the remote unit 102. In addition, remote unit 102 may include a processor 202, memory 204, input device 206, display 208, transmitter 210, and 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, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and/or the display 208.

In one embodiment, processor 202 may include any known controller capable of executing computer readable instructions and/or capable of performing logical 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, the processor 202 executes instructions stored in the 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 volatile computer storage media. For example, the memory 204 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and/or static RAM ("SRAM"). In some embodiments, memory 204 includes non-volatile computer storage media. 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, the memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit 102.

In one embodiment, input device 206 may comprise any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, and the like. In some embodiments, the input device 206 may be integrated with the display 208 (e.g., 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 touch panel.

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, 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, display 208 may include a wearable display such as a smart watch, smart glasses, heads-up display, and the like. Further, the display 208 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

In certain 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., beep or ring). In some embodiments, the display 208 includes one or more haptic devices for generating vibrations, motions, 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 some embodiments, the receiver 212 receives the hybrid automatic repeat request feedback message over the first radio interface. In various embodiments, the transmitter 210 transmits a negative acknowledgement on a physical uplink control channel of the second radio interface in response to determining that the hybrid automatic repeat request feedback message indicates unsuccessful decoding of the corresponding transport block. The negative acknowledgement indicates a request for sidelink resources on the first radio interface. In some embodiments, processor 202 starts a timer in response to transmitting a negative acknowledgement.

In some embodiments, processor 202: determining a change in a discontinuous reception configuration applied on a first radio interface; and, in response to determining the change in the discontinuous reception configuration, triggering transmission of assistance information on the second radio interface. In various embodiments, the transmitter 210 transmits the assistance information on the second radio interface in response to triggering transmission of the assistance information on the second radio interface.

In various embodiments, receiver 212 receives side link grants. In various embodiments, processor 202: determining whether sidelink resources allocated by sidelink grants are within a discontinuous reception activity time associated with a sidelink logical channel; and, in response to determining that the side link resources allocated by the side link grant are within the discontinuous reception active time associated with the side link logical channel, using the side link logical channel in a logical channel prioritization procedure, a destination selection procedure, or a combination thereof.

Although only one transmitter 210 and one receiver 212 are illustrated, 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 receiver 212 may be part of a transceiver.

Fig. 3 depicts one embodiment of an apparatus 300 that may be used to receive assistance information. The apparatus 300 includes 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, memory 304, input device 306, display 308, transmitter 310, and receiver 312 may be substantially similar to the processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212, respectively, of the remote unit 102.

In some embodiments, the receiver 312 receives assistance information corresponding to the first radio interface on the second radio interface. In various embodiments, processor 302 determines discontinuous reception configuration information for the second radio interface based on assistance information corresponding to the first radio interface. In some embodiments, the apparatus comprises a transmitter to transmit discontinuous reception configuration information on a second radio interface.

In certain embodiments, sidelink ("SL") data transmission and/or reception activity (e.g., also referred to herein as SL discontinuous reception ("DRX")) may not be coordinated with DRX operation on the interface between the UE and base station ("Uu") interfaces. In such embodiments, a transmitter ("TX") user equipment ("UE") (e.g., using mode 1 resource allocation) may be in a sleep mode (e.g., DRX) on the Uu interface (e.g., without monitoring a physical downlink control channel ("PDCCH")), although the UE is expected to receive sidelink ("SL") resource allocation over the gNB for SL data transmission on the UE-to-UE interface ("PC 5") interface.

In some embodiments, if SL data transmission and/or reception activity on the PC5 interface is not aligned with DRX operation on the Uu interface, the active time on the Uu interface may be unnecessarily extended, resulting in some increased battery power consumption.

In various embodiments, the TX UE may always be in active time on the Uu interface to be ready to receive some SL downlink control information ("DCI"). However, such embodiments may result in poor battery life, which may be undesirable for pedestrian-vehicle-to-all ("V2X") UEs.

In some embodiments, each SL logical channel ("LCH"), SL service, SL application, and/or SL destination may be associated with a pre-configured and/or fixed SL-DRX-configuration defined as a combination of parameters (e.g., offset _ std _ On-duration, on-duration-timer, and periodicity). In such embodiments, the SL On duration begins at a fixed Time offset (e.g., offset _ std _ On-duration) from the first Time (e.g., time _ 0) based On a synchronization source from a global navigation satellite system ("GNSS"), gNB, directly or indirectly from a sidelink synchronization signal ("SLSS"). The on-duration-timer may be periodically restarted. It should be noted that the term "SL active time" may refer to a time period for the SL UE to transmit and receive data on the PC5 interface. Also, the term "SL transmit and/or receive window" as used herein may be interchanged with the term SL DRX configuration. It refers to the time period during which the sidelink UE is "awake and/or active" on the PC5 interface to transmit and receive data. The SL transmit and/or receive window may facilitate SL data transmission for a particular application, service, destination, and/or LCH synchronized between UEs interested in such service and/or application. The TX side of the UE may need to know when to receive ("RX") the UE is "listening" to data for a particular SL LCH and/or application (e.g., transmit window), and the RX side of the UE needs to know when to monitor SL data for a particular SL LCH and/or application (e.g., receive window). The SL transmit and/or receive window may improve the power consumption of the UE because a UE interested in a particular SL service and/or application needs to be "active" only on the PC5 interface (e.g., for sidelink control information ("SCI") and/or physical sidelink shared channel ("psch") monitoring) for a certain predefined period of time.

In a first embodiment, there may be an interaction between SL data transmission and UU DRX state and/or timer. In such embodiments, DRX related timers and/or states used to control DRX activity time on the Uu interface may be updated based on SL data and/or control transmissions and/or receptions on the PC5 interface. To ensure that the UE is active time on the Uu interface and if SL data transmission and/or reception occurs on the PC5 interface monitoring the physical downlink control channel ("PDCCH") for SL grants, some linkage between the active time on the Uu interface and sidelink data activity on the PC5 interface may be used. In certain embodiments of the first embodiment, the UE enters an active time on the Uu interface monitoring the PDCCH in response to having transmitted a negative acknowledgement ("NACK") to the gNB on the PUCCH triggered by receiving the NACK from the RX UE on a physical sidelink feedback channel ("PSFCH"). To receive the SL grant for retransmission, the UE may be in DRX active time and may monitor for PDCCH (e.g., in mode 1) after a NACK has been sent on PUCCH for SL transmission. It should be noted that the UE may not be active immediately after a NACK has been sent on PUCCH in ActiveTime, but may be active after some predefined offset similar to DRX operation on the Uu interface. As can be appreciated, various embodiments may exist that facilitate the UE being in DRX active time when NACK for SL resources has been sent on PUCCH. In some embodiments of the first embodiment, the UE behavior when a NACK for SL resource allocation has been sent on PUCCH follows at least one of: 1) Starting or restarting drx-inactivity timer in the first symbol after PUCCH transmission ends (e.g., NACK); 2) Starting drx-retransmission timerdl for a corresponding hybrid automatic repeat request ("HARQ") process in a first symbol after transmitting a NACK on PUCCH; and/or 3) initiate a new drx-timer (e.g., drx-retransmission timersl) on Uu related to SL transmission and/or reception in response to the transmitted PUCCH (e.g., NACK). When drx-retransmission timersl is running, the UE is in active time and monitors PDCCH for SL DCI.

In a second embodiment, the DRX cycle (e.g., transmit and/or receive window) for the PC5 interface may be aligned with the DRX active time for Uu (e.g., for mode 1).

In a second embodiment, the UE provides information to the gNB about SL receive and/or transmit windows for the PC5 interface to allow the gNB to align the UU DRX configuration and/or active time of the UE based on the received information. To facilitate the UE being in DRX active time and monitoring PDCCH for SL DCI while the UE is receiving and/or transmitting SL data on the PC5 interface, some coordination between the period of time the UE is active (e.g., transmitting and/or receiving) on the PC5 interface and the UE's Uu DRX setting and/or configuration may be used. In some embodiments of the second embodiment, the UE reports to the gNB timing information within UE assistance information ("UAI") or sidelink assistance information ("SAI") indicating when the UE is active (e.g., transmitting and/or receiving SL data) on the PC5 interface. The timing information may be "SL transmit and/or receive window" or PC5DRX pattern information as described herein. The UE informs the gNB about PC5 reception and/or transmission window information whenever there is a change in PC5 transmission and/or reception activity (e.g., the UE triggers transmission of UAI and/or SAI information). The information reported by the UE to the gNB may be: 1) TX UE reports multiple SL DRX configurations and/or "transmit and/or receive window information" to the gNB, e.g., each SL destination and/or service reports a SL DRX configuration; 2) TX UE reports to the gNB SL DRX configurations and/or "SL receive and/or transmit windows" that are overlapping and/or supersets (e.g., created from the overlap of all configured SL DRX cycles); and/or 3) the TX UE only reports the SL DRX cycles for mode 1LCH to the gNB and does not report or use them for superset calculations for mode 2 LCH.

In various embodiments, in response to receipt of PC5DRX information provided by the TX UE, the gNB may configure the UE's Uu DRX cycle based on a superset of the reported SL DRX cycles such that it matches the SL DRX cycle. In some embodiments, the gNB may configure SL-specific DRX configurations for TX UEs on the Uu interface (e.g., in addition to legacy DRX configurations for DL and/or UL data on the Uu interface). TX UE may monitor SL DCI only during times when the UE is only active according to the SL DRX configuration (e.g., to reduce power consumption) and Uu-related DCI during times when the UE is also active in DRX according to legacy DRX configuration, timers, and/or rules.

In a third embodiment, there may be an active time on the Uu interface (e.g., the active time is triggered by the UE only) triggered by a SL scheduling request ("SR") and/or a buffer status report ("BSR") sent on the Uu interface.

In some of the third embodiments, the UE enters DRX active time based on SL related UL transmissions (e.g., SL SR and/or BSR) sent on the Uu interface. In various embodiments of the third embodiment, the UE enters DRX active time on the Uu interface in response to having sent a SL related resource request (e.g., such as a SL SR and/or BSR on PUCCH or a SL related acknowledgement ("ACK") and/or NACK). To be able to receive SL DCI after a request for SL resources has been sent on the Uu interface, the UE may be in DRX active time (e.g., whenever there is new SL data in the UE and the UE requests resources for PC 5) and the UE may enter active time and monitor for SL DCI.

In some of the third embodiments, a new DRX timer may be started when a request for SL resources has been sent on the Uu interface. While the new DRX timer is running, the UE considers itself to be in DRX active time. The new DRX timer may have different behavior if the UE sends an SR on PUCCH to request resources for UL data (e.g., UL shared channel ("SCH") resources) and if the UE sends (e.g., SL) an SR and/or BSR to request resources for the PC5 interface (e.g., PSCCH resources). In some embodiments of the third embodiment, the UE is in an active time for the Uu interface in response to having sent an ACK on PUCCH for SL data transmission (e.g., a packet delay budget ("PDB") associated with a transport block ("TB") and/or an ACK that has been received on PSFCH is expired). In various embodiments of the third embodiment, the UE considers itself to be active time after having sent an ACK on PUCCH for SL data transmission only if the UE has SL data available for transmission in its buffer. As can be appreciated, the UE may not be active time immediately after an ACK for the SL data transmission has been sent on the PUCCH, but may be active time after some predefined offset. In some of the third embodiments, the UE may enter an active time and monitor for SL DCI after the SL BSR has been sent on a physical uplink shared channel ("PUSCH") and/or after uplink assistance information ("UAI") including information for SL semi-persistent scheduling ("SPS") has been provided. In various ones of the third embodiment, the TX UE may delay transmission of the SL SR such that the SL SR is transmitted if the UE is active time on the Uu interface to save power.

One implementation of the third example is illustrated in table 1.

TABLE 1

In some embodiments of the third embodiment, transmission of a SL BSR medium access control ("MAC") control element ("CE") indicating a zero buffer status (e.g., no SL data available for transmission) sent on the Uu interface may trigger the UE to stop monitoring PDCCH for SL DCI on the Uu interface. If the UE is not required to be in DRX active time for other reasons (e.g., the Uu related DRX timer, such as DRX-inactivity timer, is running), the UE may enter sleep mode. In various ones of the third embodiment, new SL-related control information may be used that indicates to the gNB that no SL data is available for transmission (e.g., within a predefined time period or until some new indication of SL data becomes available for transmission). In response to having provided such information to the gNB, the TX UE stops monitoring PDCCH for SL DCI (e.g., for a predefined time period).

In some embodiments, DRX active time on the Uu interface may be guided by sidelink and/or V2X related activity on the PC5 interface (e.g., sidelink and/or V2X related signaling on the Uu interface). For example, if the UE does not establish a Uu data radio bearer ("DRB"), the UE may only be in DRX active time to receive PDCCH for SL DCI (e.g., sending NACK for SL transmission on PUCCH already and/or sending SL BSR on PUSCH or triggered by SL BSR in response to SR already being sent on PUCCH). Even if there is no Uu DRB established, the UE may be configured with some DRX configurations (e.g., long DRX cycle with short OnDuration).

In a fourth embodiment, there may be separate search spaces and drxActiveTime for Uu DCI and SL DCI.

In some embodiments, a UE using resource allocation mode 1 may be configured with separate search spaces for Uu DCI and SL DCI. In various embodiments, the UE may have two separate active times on the Uu interface (e.g., one for Uu-related data activity, also referred to as Uu active time, and one for SL-related activity, referred to as SL active time). While the UE is in Uu active time, the UE monitors PDCCH in Uu DCI related search spaces, while the UE is in SL active time, the UE monitors PDCCH in SL related search spaces for SL DCI on Uu interface. Separating the search spaces for Uu DCI and SL DCI may again achieve power savings. In various embodiments, the Uu and SL active times on the Uu interface may overlap, resulting in a situation where the UE monitors the PDCCH on both the Uu-related search space (e.g., or null) and the SL-related search space (e.g., null). In some embodiments, the DRX active time of the UE may be controlled by separate timers (e.g., uu related DRX timers, such as an duration timer or a DRX inactivity timer, and SL related DRX timers).

In a fifth embodiment, a logical channel prioritization ("LCP") procedure (e.g., destination selection) may consider the DRX configuration of the receiving UE on the PC5 interface to ensure that the receiving UE is active and ready to receive data transmitted on the allocated resources. In one embodiment of the fifth embodiment, the UE considers the SL LCH for LCP procedure and/or destination selection when receiving a SL grant (SL DCI) if the SL DCI allocated SL resources fall within the transmit and/or receive window associated with the SL LCH. If the UE has SL data for SL LCH x in its buffer when receiving the SL grant and the active time associated with SL LCH x does not overlap with SL resources (e.g., allocated by the SL grant), the UE may override SL LCH x for the LCP (e.g., destination selection).

In a sixth embodiment, the UE transmits an SR (e.g., triggered by the SL BSR) no earlier than a predefined time (e.g., x ms) before the start of a corresponding "transmit and/or receive window" on the PC5 interface to facilitate the assignment of SL resources by the gbb in response to receipt of the SL SR within the "transmit and/or receive window". Even though the internal SR trigger may occur at any point in time (e.g., based on SL data arrival), the UE may delay transmission of the SR such that SR transmission does not occur earlier than a predefined time before the start of the corresponding "SL transmission and/or reception window".

Figure 4 is a schematic block diagram illustrating one embodiment of a system 400 with communications for indicating a request for contralateral link resources. System 400 includes a gNB 402, a first UE 404, and a second UE 406. As can be appreciated, any communication in the system 400 can include one or more messages.

In a first communication 408 transmitted from the second UE406 to the first UE 404, the second UE406 transmits a hybrid automatic repeat request feedback message to the first UE 404 over a first radio interface (e.g., a PC5 interface).

In a second communication 410 transmitted from the first UE 404 to the gNB 406, the first UE 404 transmits a negative determination to the gNB 406 on a physical uplink control channel of a second radio interface (e.g., the Uu interface) in response to determining that the hybrid automatic repeat request feedback message indicates unsuccessful decoding of the corresponding transport block. The negative acknowledgement indicates a request for sidelink resources on the first radio interface.

The first UE 404 starts 412 a timer in response to transmitting a negative acknowledgement.

In a third communication 414 transmitted from the gNB 406 to the first UE 404, the gNB 406 transmits downlink control information to the first UE 404 on a physical downlink control channel of the second radio interface.

The first UE 404 monitors 416 a physical downlink control channel on the second radio interface for downlink control information while the timer is running.

Figure 5 is a flow diagram illustrating one embodiment of a method 500 for indicating a request for sidelink resources. In some embodiments, the method 500 is performed by an apparatus, such as the remote unit 102. In certain embodiments, the method 500 may be performed by a processor executing program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or the like.

In various embodiments, method 500 includes receiving 502 a hybrid automatic repeat request feedback message over a first radio interface. In some embodiments, the method 500 includes, in response to determining that the hybrid automatic repeat request feedback message indicates unsuccessful decoding of the corresponding transport block, transmitting 504 a negative acknowledgement on a physical uplink control channel of the second radio interface. The negative acknowledgement indicates a request for sidelink resources on the first radio interface. In some embodiments, the method 500 includes starting 506 a timer in response to transmitting the negative acknowledgement.

In certain embodiments, the method 500 further comprises monitoring a physical downlink control channel on the second radio interface for downlink control information while the timer is running. In some embodiments, the downlink control information comprises sidelink downlink control information.

In various embodiments, the hybrid automatic repeat request feedback message is received over the first radio interface on a physical sidelink feedback channel. In one embodiment, the timer comprises a discontinuous reception retransmission sidelink timer.

FIG. 6 is a flow diagram illustrating one embodiment of a method 600 for providing assistance information. In some embodiments, method 600 is performed by an apparatus, such as remote unit 102. In certain embodiments, the method 600 may be performed by a processor executing program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or the like.

In various embodiments, the method 600 includes determining 602 a change in a discontinuous reception configuration applied over a first radio interface. In some embodiments, the method 600 includes, in response to determining the change in the discontinuous reception configuration, triggering 604 transmission of assistance information on the second radio interface. In certain embodiments, the method 600 includes, in response to triggering transmission of the assistance information on the second radio interface, transmitting 606 the assistance information on the second radio interface.

In certain embodiments, the assistance information comprises a plurality of side link discontinuous reception configurations for the first radio interface, transmit window information, receive window information, or a combination thereof. In some embodiments, the method 600 further comprises receiving discontinuous reception configuration information for the second radio interface in response to transmitting the assistance information. In various embodiments, the discontinuous reception configuration information is determined based on the assistance information.

Fig. 7 is a flow diagram illustrating one embodiment of a method 700 for receiving assistance information. In some embodiments, method 700 is performed by an apparatus, such as network element 104. In certain embodiments, method 700 may be performed by a processor executing program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or the like.

In various embodiments, method 700 includes receiving 702 assistance information corresponding to a first radio interface on a second radio interface. In some embodiments, method 700 includes determining 704 discontinuous reception configuration information for a second radio interface based on assistance information corresponding to a first radio interface. In certain embodiments, the method 700 includes transmitting 706 discontinuous reception configuration information on the second radio interface.

In certain embodiments, the assistance information comprises a plurality of side link discontinuous reception configurations for the first radio interface, transmit window information, receive window information, or a combination thereof.

Fig. 8 is a flow diagram illustrating one embodiment of a method 800 for side link resource determination. In some embodiments, the method 800 is performed by an apparatus, such as the remote unit 102. In certain embodiments, the 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.

In various embodiments, method 800 includes receiving 802 a side link grant. In some embodiments, method 800 includes determining 804 whether the sidelink resources allocated by the sidelink licenses are within a discontinuous reception active time associated with the sidelink logical channel. In some embodiments, method 800 includes, in response to determining that the sidelink resources allocated by the sidelink licenses are within a discontinuous reception activity time associated with the sidelink logical channel, using 806 the sidelink logical channel in a logical channel prioritization procedure, a destination selection procedure, or a combination thereof.

In some embodiments, method 800 further includes determining whether sidelink data is in a buffer for a sidelink logical channel. In some embodiments, method 800 further includes, in response to determining that sidelink data is in the buffer for the sidelink logical channel, determining whether resources allocated by the sidelink grants overlap with discontinuous reception activity times associated with the sidelink logical channel.

In various embodiments, method 800 further comprises, in response to determining that the resources allocated by the sidelink admission do not overlap with the discontinuous reception activity time associated with the sidelink logical channel, not selecting the sidelink logical channel as part of a logical channel prioritization procedure, a destination selection procedure, or a combination thereof. In one embodiment, the method 800 further includes, in response to determining that the resources allocated by the sidelink licenses overlap with discontinuous reception activity times associated with the sidelink logical channel, selecting the sidelink logical channel as part of a logical channel prioritization procedure, a destination selection procedure, or a combination thereof.

In one embodiment, a method comprises: receiving a hybrid automatic repeat request feedback message over a first radio interface; transmitting a negative acknowledgement on a physical uplink control channel of the second radio interface in response to determining that the hybrid automatic repeat request feedback message indicates unsuccessful decoding of the corresponding transport block, wherein the negative acknowledgement indicates a request for sidelink resources on the first radio interface; and starting a timer in response to transmitting the negative acknowledgement.

In some embodiments, the method further comprises monitoring a physical downlink control channel on the second radio interface for downlink control information while the timer is running.

In some embodiments, the downlink control information comprises sidelink downlink control information.

In various embodiments, the hybrid automatic repeat request feedback message is received over a physical sidelink feedback channel over a first radio interface.

In one embodiment, the timer comprises a discontinuous reception retransmission sidelink timer.

In one embodiment, an apparatus comprises: a receiver that receives a hybrid automatic repeat request feedback message over a first radio interface; a transmitter to transmit a negative acknowledgement on a physical uplink control channel of the second radio interface in response to determining that the hybrid automatic repeat request feedback message indicates unsuccessful decoding of the corresponding transport block, wherein the negative acknowledgement indicates a request for sidelink resources on the first radio interface; and a processor that starts a timer in response to transmitting a negative acknowledgement.

In certain embodiments, the processor monitors a physical downlink control channel on the second radio interface for downlink control information while the timer is running.

In one embodiment, a method comprises: determining a change in a discontinuous reception configuration applied on a first radio interface; triggering transmission of assistance information on a second radio interface in response to determining the change in the discontinuous reception configuration; and transmitting the assistance information on the second radio interface in response to triggering the transmission of the assistance information on the second radio interface.

In some embodiments, the method further comprises receiving discontinuous reception configuration information for the second radio interface in response to transmitting the assistance information.

In various embodiments, the discontinuous reception configuration information is determined based on the assistance information.

In one embodiment, an apparatus comprises: a processor, the processor: determining a change in a discontinuous reception configuration applied on a first radio interface; and, in response to determining the change in the discontinuous reception configuration, triggering transmission of assistance information on the second radio interface; and transmitting the assistance information on the second radio interface in response to triggering transmission of the assistance information on the second radio interface.

In some embodiments, the apparatus further comprises a receiver that receives discontinuous reception configuration information for the second radio interface in response to transmitting the assistance information.

In one embodiment, a method comprises: receiving assistance information corresponding to the first radio interface on the second radio interface; determining discontinuous reception configuration information for a second radio interface based on assistance information corresponding to a first radio interface; and transmitting discontinuous reception configuration information on the second radio interface.

In one embodiment, an apparatus comprises: a receiver that receives assistance information corresponding to the first radio interface on the second radio interface; a processor that determines discontinuous reception configuration information for a second radio interface based on assistance information corresponding to a first radio interface; and a transmitter that transmits discontinuous reception configuration information on the second radio interface.

In one embodiment, a method comprises: receiving a sidelink grant; determining whether sidelink resources allocated by sidelink grants are within a discontinuous reception activity time associated with a sidelink logical channel; and in response to determining that the side link resources allocated by the side link grant are within discontinuous reception active times associated with the side link logical channel, using the side link logical channel in a logical channel prioritization procedure, a destination selection procedure, or a combination thereof.

In some embodiments, the method further comprises determining whether sidelink data is in a buffer for a sidelink logical channel.

In some embodiments, the method further comprises, in response to determining that sidelink data is in the buffer for the sidelink logical channel, determining whether resources allocated by the sidelink grants overlap with discontinuous reception activity times associated with the sidelink logical channel.

In various embodiments, the method further comprises, in response to determining that the resources allocated by the sidelink grants do not overlap with discontinuous reception activity times associated with the sidelink logical channel, not selecting the sidelink logical channel as part of the logical channel prioritization procedure, the destination selection procedure, or a combination thereof.

In one embodiment, the method further comprises, in response to determining that the resources allocated by the sidelink admission overlap with the discontinuous reception activity time associated with the sidelink logical channel, selecting the sidelink logical channel as part of a logical channel prioritization procedure, a destination selection procedure, or a combination thereof.

In one embodiment, an apparatus comprises: a receiver that receives a sidelink grant; and a processor, the processor: determining whether sidelink resources allocated by sidelink grants are within a discontinuous reception activity time associated with a sidelink logical channel; and in response to determining that the side link resources allocated by the side link grant are within discontinuous reception active times associated with the side link logical channel, using the side link logical channel in a logical channel prioritization procedure, a destination selection procedure, or a combination thereof.

In some embodiments, the processor determines whether sidelink data is in a buffer for a sidelink logical channel.

In some embodiments, the processor determines whether resources allocated by the sidelink grant overlap with a discontinuous reception activity time associated with the sidelink logical channel in response to determining that sidelink data is in a buffer for the sidelink logical channel.

In various embodiments, the processor, in response to determining that the resources allocated by the sidelink route grant do not overlap with the discontinuous reception activity time associated with the sidelink logical channel, does not select the sidelink logical channel as part of a logical channel prioritization procedure, a destination selection procedure, or a combination thereof.

In one embodiment, the processor selects the sidelink logical channel as part of a logical channel prioritization procedure, a destination selection procedure, or a combination thereof, in response to determining that resources allocated by the sidelink licenses overlap with discontinuous reception activity times associated with the sidelink logical channel.

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:

receiving a hybrid automatic repeat request feedback message over a first radio interface;

in response to determining that the hybrid automatic repeat request feedback message indicates unsuccessful decoding of a corresponding transport block, transmitting a negative acknowledgement on a physical uplink control channel of a second radio interface, wherein the negative acknowledgement indicates a request for sidelink resources on the first radio interface; and

starting a timer in response to transmitting the negative acknowledgement.

2. The method of claim 1, further comprising monitoring a physical downlink control channel on the second radio interface for downlink control information while the timer is running.

3. The method of claim 2, wherein the downlink control information comprises sidelink downlink control information.

4. An apparatus, comprising:

a receiver to receive a hybrid automatic repeat request feedback message over a first radio interface;

a transmitter to transmit a negative acknowledgement on a physical uplink control channel of a second radio interface in response to determining that the hybrid automatic repeat request feedback message indicates unsuccessful decoding of a corresponding transport block, wherein the negative acknowledgement indicates a request for sidelink resources on the first radio interface; and

a processor that starts a timer in response to transmitting the negative acknowledgement.

5. The apparatus of claim 4, wherein the processor monitors a physical downlink control channel on the second radio interface for downlink control information while the timer is running.

6. The apparatus of claim 5, wherein the downlink control information comprises sidelink downlink control information.

7. The apparatus of claim 4, wherein the timer comprises a discontinuous reception retransmission sidelink timer.

8. An apparatus, comprising:

a receiver to receive assistance information corresponding to a first radio interface on a second radio interface;

a processor that determines discontinuous reception configuration information for the second radio interface based on the assistance information corresponding to the first radio interface; and

a transmitter that transmits the discontinuous reception configuration information on the second radio interface.

9. The apparatus of claim 8, wherein the assistance information comprises a plurality of side link discontinuous reception configurations, transmit window information, receive window information, or a combination thereof for the first radio interface.

10. A method, comprising:

receiving a side link grant;

determining whether sidelink resources allocated by said sidelink grants are within a discontinuous reception activity time associated with a sidelink logical channel; and

in response to determining that the sidelink resources allocated by the sidelink grants are within the discontinuous reception active time associated with the sidelink logical channel, using the sidelink logical channel in a logical channel prioritization procedure, a destination selection procedure, or a combination thereof.

11. An apparatus, comprising:

a receiver that receives a side link grant; and

a processor that:

determining whether side link resources allocated by the sidelink grants are within a discontinuous reception active time associated with a sidelink logical channel; and is

12. The apparatus of claim 11, wherein the processor determines whether sidelink data is in a buffer for the sidelink logical channel.

13. The apparatus of claim 12, wherein the processor determines whether resources allocated by the sidelink grant overlap with the discontinuous reception activity time associated with the sidelink logical channel in response to determining sidelink data is in the buffer for the sidelink logical channel.

14. The apparatus of claim 13, wherein the processor does not select the sidelink logical channel as part of the logical channel prioritization procedure, the destination selection procedure, or the combination thereof, in response to determining that resources allocated by the sidelink grant do not overlap with the discontinuous reception activity time associated with the sidelink logical channel.

15. The apparatus of claim 13, wherein the processor selects the sidelink logical channel as part of the logical channel prioritization procedure, the destination selection procedure, or the combination thereof, in response to determining that resources allocated by the sidelink grant overlap the discontinuous reception activity time associated with the sidelink logical channel.