SIDELINK DISCONTINUOUS RECEPTION CONFIGURATION

Information

  • Patent Application
  • 20230276364
  • Publication Number
    20230276364
  • Date Filed
    July 10, 2021
    2 years ago
  • Date Published
    August 31, 2023
    8 months ago
Abstract
Apparatuses, methods, and systems are disclosed for sidlink discontinuous reception configuration. One method (1000) includes accessing (1002) a sidelink discontinuous reception configuration. The sidelink discontinuous reception configuration corresponds to a quality of service class; an identifier of the quality of service class; at least on attribute of the quality of service class; or some combination thereof. The method (1000) includes performing (1004) sidelink communication based on the sidelink discontinuous reception configuration.
Description
FIELD

The subject matter disclosed herein relates generally to wireless communications and more particularly relates to sidelink discontinuous reception configuration.


BACKGROUND

In certain wireless communications networks, a configuration for sidelink discontinuous reception may be inefficient. A sidelink discontinuous reception configuration may be updated and/or provided to a user equipment.


BRIEF SUMMARY

Methods for sidelink discontinuous reception configuration are disclosed. Apparatuses and systems also perform the functions of the methods. One embodiment of a method includes accessing a sidelink discontinuous reception configuration. The sidelink discontinuous reception configuration corresponds to: a quality of service class; an identifier of the quality of service class; at least one attribute of the quality of service class; a range corresponding to the at least one attribute of the quality of service class; or some combination thereof. In some embodiments, the method includes performing sidelink communication based on the sidelink discontinuous reception configuration.


One apparatus for sidelink discontinuous reception configuration includes a processor that: accesses a sidelink discontinuous reception configuration, wherein the sidelink discontinuous reception configuration corresponds to: a quality of service class; an identifier of the quality of service class; at least one attribute of the quality of service class; a range corresponding to the at least one attribute of the quality of service class; or some combination thereof; and performs sidelink communication based on the sidelink discontinuous reception configuration.


Another embodiment of a method for sidelink discontinuous reception configuration includes determining, at a first user equipment, at least one parameter for a sidelink discontinuous reception configuration. In some embodiments, the method includes transmitting the at least one parameter for the sidelink discontinuous reception configuration to a second user equipment. In certain embodiments, the method includes receiving feedback from the second user equipment indicating acceptance of the at least one parameter for the sidelink discontinuous reception configuration.


Another apparatus for sidelink discontinuous reception configuration includes a first user equipment. In some embodiments, the apparatus includes a processor that determines at least one parameter for a sidelink discontinuous reception configuration. In various embodiments, the apparatus includes a transmitter that transmits the at least one parameter for the sidelink discontinuous reception configuration to a second user equipment. In certain embodiments, the apparatus includes a receiver that receives feedback from the second user equipment indicating acceptance of the at least one parameter for the sidelink discontinuous reception configuration.


Yet another embodiment of a method for sidelink discontinuous reception configuration includes accessing a sidelink discontinuous reception configuration. The sidelink discontinuous reception configuration includes a first offset for an on-duration, an on-duration timer, and a periodicity. In some embodiments, the method includes determining a second offset for the on-duration. In certain embodiments, the method includes transmitting data based on the sidelink discontinuous reception configuration and the second offset for the on-duration.


Yet another apparatus for sidelink discontinuous reception configuration includes a processor that: accesses a sidelink discontinuous reception configuration, wherein the sidelink discontinuous reception configuration comprises a first offset for an on-duration, an on-duration timer, and a periodicity; and determines a second offset for the on-duration. In various embodiments, the apparatus includes a transmitter that transmits data based on the sidelink discontinuous reception configuration and the second offset for the on-duration.


A further embodiment of a method for sidelink discontinuous reception configuration includes accessing a sidelink discontinuous reception configuration. The sidelink discontinuous reception configuration includes an offset for an on-duration, an on-duration timer, and a periodicity. In some embodiments, the method includes transmitting sidelink data, receiving the sidelink data, or a combination thereof. In certain embodiments, the method includes, in response to transmitting the sidelink data, receiving the sidelink data, or a combination thereof, starting a sidelink inactivity timer. In various embodiments, the method includes restarting the sidelink inactivity timer in response to: indicating a negative acknowledgement on a physical uplink control channel to request a retransmission grant to a base station; indicating an acknowledgement on the physical uplink control channel and in response to having a non-empty sidelink buffer to the base station; receiving hybrid automatic repeat request feedback on a physical sidelink feedback channel from a sidelink receiver user equipment; transmitting a sidelink scheduling request to a base station; transmitting a sidelink buffer status report to the base station; requesting a channel state information report on sidelink from a peer user equipment; receiving a request for a channel state information report on sidelink from a peer user equipment; receiving sidelink control information from the sidelink transmitter user equipment; receiving data from the sidelink transmitter user equipment; transmitting a physical sidelink feedback channel negative acknowledgement feedback to the sidelink transmitter user equipment; transmitting sidelink control information requesting sidelink physical sidelink feedback channel feedback; transmitting non-last sidelink control information while performing blind re-transmissions; transmitting non-last data while performing blind re-transmissions; a sync source using a value of a sidelink inactivity timer greater than a predetermined value; or some combination thereof.


A further apparatus for sidelink discontinuous reception configuration includes a processor that accesses a sidelink discontinuous reception configuration. The sidelink discontinuous reception configuration includes an offset for an on-duration, an on-duration timer, and a periodicity. In various embodiments, the apparatus includes a transmitter. In certain embodiments, the apparatus includes a receiver. The transmitter transmits sidelink data, the receiver receives the sidelink data, or a combination thereof. In response to the transmitter transmitting sidelink data, the receiver receiving the sidelink data, or a combination thereof, the processor starts a sidelink inactivity timer. The processor restarts the sidelink inactivity timer in response to: indicating a negative acknowledgement on a physical uplink control channel to request a retransmission grant to a base station; indicating an acknowledgement on the physical uplink control channel and in response to having a non-empty sidelink buffer to the base station; receiving hybrid automatic repeat request feedback on a physical sidelink feedback channel from a sidelink receiver user equipment; transmitting a sidelink scheduling request to a base station; transmitting a sidelink buffer status report to the base station; requesting a channel state information report on sidelink from a peer user equipment; receiving a request for a channel state information report on sidelink from a peer user equipment; receiving sidelink control information from the sidelink transmitter user equipment; receiving data from the sidelink transmitter user equipment; transmitting a physical sidelink feedback channel negative acknowledgement feedback to the sidelink transmitter user equipment; transmitting sidelink control information requesting sidelink physical sidelink feedback channel feedback; transmitting non-last sidelink control information while performing blind re-transmissions; transmitting non-last data while performing blind re-transmissions; a sync source using a value of a sidelink inactivity timer greater than a predetermined value; or some combination thereof.





BRIEF DESCRIPTION OF THE 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 sidelink discontinuous reception configuration;



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



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



FIG. 4 is a timing diagram illustrating one embodiment of a SL DRX configuration;



FIG. 5 is a timing diagram illustrating one embodiment of two SL DRX configurations corresponding to a first PQI range and a second PQI range;



FIG. 6 is a network communications diagram illustrating one embodiment of a negotiation of SL DRX configuration for unicast communication;



FIG. 7 is a network communications diagram illustrating one embodiment of a negotiation of SL DRX configuration for groupcast communication;



FIG. 8 is a network communications diagram illustrating one embodiment of Uu negotiation to align Uu and SL DRX;



FIG. 9 is a timing diagram illustrating one embodiment of SL DRX interplay with timers;



FIG. 10 is a flow chart diagram illustrating one embodiment of a method for sidelink discontinuous reception configuration;



FIG. 11 is a flow chart diagram illustrating another embodiment of a method for sidelink discontinuous reception configuration;



FIG. 12 is a flow chart diagram illustrating yet another embodiment of a method for sidelink discontinuous reception configuration; and



FIG. 13 is a flow chart diagram illustrating a further embodiment of a method for sidelink 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. 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 storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.


Certain 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, include 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 include disparate instructions stored in different locations which, when joined logically together, include 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 medium 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. 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 carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages 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 machine languages such as assembly languages. 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 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” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An 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 refer to “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 embodiments 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 an embodiment.


Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. 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 diagrams and/or schematic block diagrams block or blocks.


The code may also be stored in a storage 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 storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams 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 execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.


The schematic flowchart 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 flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code 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 Figures.


Although various arrow types and line types may be employed in the flowchart 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 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 diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.


The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.



FIG. 1 depicts an embodiment of a wireless communication system 100 for sidelink discontinuous reception configuration. In one embodiment, the wireless communication system 100 includes remote units 102 and network units 104. Even though a specific number of remote units 102 and network units 104 are depicted in FIG. 1, one of skill 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, 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), vehicle on-board computers, network devices (e.g., routers, switches, modems), aerial vehicles, drones, or the like. In some embodiments, the remote units 102 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device, or by other terminology used in the art. The remote units 102 may communicate directly with one or more of the network units 104 via UL communication signals. In certain embodiments, the remote units 102 may communicate directly with other remote units 102 via sidelink communication.


The network units 104 may be distributed over a geographic region. In certain embodiments, a network unit 104 may also be referred to and/or may include one or more of an access point, an access terminal, a base, a base station, a location server, a core network (“CN”), a radio network entity, 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 aerial server, a radio access node, an access point (“AP”), 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 operations, administration, and management (“OAM”), a session management function (“SMF”), a user plane function (“UPF”), an application function, an authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non-3GPP gateway function (“TNGF”), or by any other terminology used in the art. The network units 104 are generally part of a radio access network that includes one or more controllers communicably coupled to one or more corresponding network units 104. The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.


In one implementation, the wireless communication system 100 is compliant with NR protocols standardized in third generation partnership project (“3GPP”), wherein the network unit 104 transmits using an OFDM modulation scheme on the downlink (“DL”) and the remote units 102 transmit 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, 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 (“CDMA2000”), Bluetooth®, ZigBee, Sigfoxx, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.


The network units 104 may serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link. The network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and/or spatial domain.


In various embodiments, a remote unit 102 may access a sidelink discontinuous reception configuration. The sidelink discontinuous reception configuration corresponds to: a quality of service class; an identifier of the quality of service class; at least one attribute of the quality of service class; a range corresponding to the at least one attribute of the quality of service class; or some combination thereof. In some embodiments, the remote unit 102 may perform sidelink communication based on the sidelink discontinuous reception configuration. Accordingly, the remote unit 102 may be used for sidelink discontinuous reception configuration.


In certain embodiments, a remote unit 102 may determine, at a first user equipment, at least one parameter for a sidelink discontinuous reception configuration. In some embodiments, the remote unit 102 may transmit the at least one parameter for the sidelink discontinuous reception configuration to a second user equipment. In certain embodiments, the remote unit 102 may receive feedback from the second user equipment indicating acceptance of the at least one parameter for the sidelink discontinuous reception configuration. Accordingly, the remote unit 102 may be used for sidelink discontinuous reception configuration.


In various embodiments, a remote unit 102 may access a sidelink discontinuous reception configuration. The sidelink discontinuous reception configuration includes a first offset for an on-duration, an on-duration timer, and a periodicity. In some embodiments, the remote unit 102 may determine a second offset for the on-duration. In certain embodiments, the remote unit 102 may transmit data based on the sidelink discontinuous reception configuration and the second offset for the on-duration. Accordingly, the remote unit 102 may be used for sidelink discontinuous reception configuration.


In certain embodiments, a remote unit 102 may access a sidelink discontinuous reception configuration. The sidelink discontinuous reception configuration includes an offset for an on-duration, an on-duration timer, and a periodicity. In some embodiments, the remote unit 102 may transmit sidelink data, receive the sidelink data, or a combination thereof. In certain embodiments, the remote unit 102 may, in response to transmitting the sidelink data, receiving the sidelink data, or a combination thereof, start a sidelink inactivity timer. In various embodiments, the remote unit 102 may restart the sidelink inactivity timer in response to: indicating a negative acknowledgement on a physical uplink control channel to request a retransmission grant to a base station; indicating an acknowledgement on the physical uplink control channel and in response to having a non-empty sidelink buffer to the base station; receiving hybrid automatic repeat request feedback on a physical sidelink feedback channel from a sidelink receiver user equipment; transmitting a sidelink scheduling request to a base station; transmitting a sidelink buffer status report to the base station; requesting a channel state information report on sidelink from a peer user equipment; receiving a request for a channel state information report on sidelink from a peer user equipment; receiving sidelink control information from the sidelink transmitter user equipment; receiving data from the sidelink transmitter user equipment; transmitting a physical sidelink feedback channel negative acknowledgement feedback to the sidelink transmitter user equipment; transmitting sidelink control information requesting sidelink physical sidelink feedback channel feedback; transmitting non-last sidelink control information while performing blind re-transmissions; transmitting non-last data while performing blind re-transmissions; a sync source using a value of a sidelink inactivity timer greater than a predetermined value; or some combination thereof. Accordingly, the remote unit 102 may be used for sidelink discontinuous reception configuration.



FIG. 2 depicts one embodiment of an apparatus 200 that may be used for sidelink discontinuous reception configuration. The apparatus 200 includes one embodiment of the remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a 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 touchscreen. In certain embodiments, the 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.


The processor 202, in one embodiment, 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, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a 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.


The memory 204, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 204 includes volatile computer storage media. For example, the memory 204 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 204 includes non-volatile computer storage media. For example, the memory 204 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 204 includes both volatile and non-volatile 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.


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


The display 208, in one embodiment, may include any known electronically controllable display or display device. The display 208 may be designed to output visual, audible, and/or haptic signals. In some embodiments, the display 208 includes 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, or 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, a heads-up display, or the like. Further, the display 208 may be a component of a smart phone, a personal digital assistant, a television, a table 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 produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the display 208 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the display 208 may be integrated with the input device 206. For example, the input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, the display 208 may be located near the input device 206.


In some embodiments, the processor 202: accesses a sidelink discontinuous reception configuration, wherein the sidelink discontinuous reception configuration corresponds to: a quality of service class; an identifier of the quality of service class; at least one attribute of the quality of service class; a range corresponding to the at least one attribute of the quality of service class; or some combination thereof; and performs sidelink communication based on the sidelink discontinuous reception configuration.


In certain embodiments, the processor 202 determines at least one parameter for a sidelink discontinuous reception configuration. In various embodiments, the transmitter 210 transmits the at least one parameter for the sidelink discontinuous reception configuration to a second user equipment. In certain embodiments, the receiver 212 receives feedback from the second user equipment indicating acceptance of the at least one parameter for the sidelink discontinuous reception configuration.


In various embodiments, the processor 202: accesses a sidelink discontinuous reception configuration, wherein the sidelink discontinuous reception configuration comprises a first offset for an on-duration, an on-duration timer, and a periodicity; and determines a second offset for the on-duration. In various embodiments, the transmitter 210 transmits data based on the sidelink discontinuous reception configuration and the second offset for the on-duration.


In certain embodiments, the processor 202 accesses a sidelink discontinuous reception configuration. The sidelink discontinuous reception configuration includes an offset for an on-duration, an on-duration timer, and a periodicity. In various embodiments, the transmitter 210 transmits sidelink data, the receiver 212 receives the sidelink data, or a combination thereof. In response to the transmitter 210 transmitting sidelink data, the receiver 212 receiving the sidelink data, or a combination thereof, the processor 202 starts a sidelink inactivity timer. The processor 202 restarts the sidelink inactivity timer in response to: indicating a negative acknowledgement on a physical uplink control channel to request a retransmission grant to a base station; indicating an acknowledgement on the physical uplink control channel and in response to having a non-empty sidelink buffer to the base station; receiving hybrid automatic repeat request feedback on a physical sidelink feedback channel from a sidelink receiver user equipment; transmitting a sidelink scheduling request to a base station; transmitting a sidelink buffer status report to the base station; requesting a channel state information report on sidelink from a peer user equipment; receiving a request for a channel state information report on sidelink from a peer user equipment; receiving sidelink control information from the sidelink transmitter user equipment; receiving data from the sidelink transmitter user equipment; transmitting a physical sidelink feedback channel negative acknowledgement feedback to the sidelink transmitter user equipment; transmitting sidelink control information requesting sidelink physical sidelink feedback channel feedback; transmitting non-last sidelink control information while performing blind re-transmissions; transmitting non-last data while performing blind re-transmissions; a sync source using a value of a sidelink inactivity timer greater than a predetermined value; or some combination thereof.


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 the receiver 212 may be any suitable type of transmitters and receivers. In one embodiment, the transmitter 210 and the receiver 212 may be part of a transceiver.



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


In certain embodiments, a discontinuous reception (“DRX”) configuration may be brought to a vehicle to everything (“V2X”) layer (e.g., instead of at an access stratum layer). Such embodiments may cause a duplication of work (e.g., specification, implementation, and testing).


In some embodiments, a standard sidelink (“SL”) on-duration may be used. A standard SL on-duration may start at a known point in time and a SL user equipment (“UE”) may remain active until a known timer (e.g., on-duration-timer) is running. The standard SL on-duration may start at a fixed time offset (e.g., offset_std_On-duration) from Time_0 based on a synchronization source from global navigation satellite system (“GNSS”) or gNB directly or indirectly from sidelink synchronization signals (“SLSS”). The on-duration-timer may be restarted periodically with a periodicity. It should be noted that the term “active time” may refer to a time period where a SL UE transmits and receives data on a UE to UE interface (“PC5”) interface. This is different than a UE to network interface (“Uu”) interface active time which only refers to a time period in which a UE is monitoring physical downlink control channel (“PDCCH”). In various embodiments, a SL-DRX-configuration is defined as a combination of offset_std_On-duration, On-duration-timer, and periodicity as shown in FIG. 4, and may be: 1) known universally (e.g., by way of specification); 2) known per application and/or application type; 3) known per service and/or service type; 4) known per quality of service (“QoS”) class (e.g., QoS class identifier (“QCI”), performance quality index (“PQI”), etc.); 5) known per one or more attribute of a QoS class (e.g., QCI, PQI, etc.); and/or 6) known per range of one or more attribute of a QoS class (e.g., QCI, PQI, etc.).



FIG. 4 is a timing diagram 400 illustrating one embodiment of a SL DRX configuration. The timing diagram 400 illustrates timing from Time_0402 over time 404, an offset_std_On-duration 406, a periodicity 408, and an On-duration-timer 410.


In a first example, a first SL DRX configuration (e.g., SL-DRX-configuration_1) is for basic safety messages and a second SL DRX configuration (e.g., SL-DRX-configuration_2) is for advanced safety messages in V2X communication.


In a second example, a first SL DRX configuration (e.g., SL-DRX-configuration_1) is for vehicular communication and a second SL DRX configuration (e.g., SL-DRX-configuration_) is for public safety related communication.


In a third example, a first SL DRX configuration (e.g., SL-DRX-configuration_1) is for pedestrian (e.g., vulnerable road user (“VRU”)) and a second SL DRX configuration (e.g., SL-DRX-configuration_2) is vehicular messages in V2X communication.


In a fourth example, a first SL DRX configuration (e.g., SL-DRX-configuration_1) is for a first PQI range (e.g., x1 to y1) and a second SL DRX configuration (e.g., SL-DRX-configuration_2) is for a second PQI range (e.g., x2 to y2).


In a fifth example, a first SL DRX configuration (e.g., SL-DRX-configuration_1) is for a first QCI range (e.g., x1 to y1) and a second SL DRX configuration (e.g., SL-DRX-configuration_2) is for a second PQI range (e.g., x2 to y2).


In a sixth example, only one single SL DRX configuration (e.g., SL-DRX-configuration_1) is used for any kind of sidelink communication using DRX based power savings.



FIG. 5 is a timing diagram 500 illustrating one embodiment of two SL DRX configurations corresponding to a first PQI range and a second PQI range. The timing diagram 500 illustrates timing from Time_0502 over time 504 for a SL DRX configuration corresponding to a first PQI-range, an offset_std_On-duration 506, a periodicity 508, and an On-duration-timer 510. The timing diagram 500 also illustrates timing from the Time_0502 over time 516 for a SL DRX configuration corresponding to a second PQI-range, an offset_std_On-duration 518, a periodicity 520, and an On-duration-timer 522.


In various embodiments, not all SL DRX configuration parameters need to be unique across different (e.g., all) SL DRX configurations. Accordingly, in such embodiments, one or two of the parameters offset_std_On-duration, On-duration-timer, and periodicity may have a common value across different (e.g., all) SL DRX configurations. For different SL DRX configurations, it is sufficient to have just one or two parameters different across the different SL DRX configurations. For example, the On-duration-timer may be small (e.g., some milliseconds) for applications with a small periodical data. As another example, the On-duration-timer may be large (e.g., approaching infinity) for high latency sensitive applications—as long as the application remains live.


In certain embodiments, instead of fixed values for a SL DRX configuration in a specification, the values for the SL DRX configuration may be configurable and indicated to a UE using non-access stratum (“NAS”) or radio resource configuration (“RRC”) signaling where an application management function (“AMF”) or a gNB lets a SL UE know the SL DRX configuration for its geographical area like a radio access network (“RAN”) based notification area, UE's registration area (e.g., timing advance (“TA”) list), just cell areas, and/or just tracking areas. Preconfiguration of a SL DRX configuration may also be done.


In some embodiments, one or more SL DRX configurations between a pair of peer UEs in a unicast connection may be aligned. In such embodiments, one of the peer UEs may negotiate an On-duration start time (e.g., offset_common_On-duration) different from a offset_std_On-duration to align and/or overlap with one or more existing On-durations—so, a UE may request its peer UE to move the On-duration start time to a offset_common_On-duration. The negotiation may be done using PC5, NAS, or RRC signaling.



FIG. 6 is a network communications 600 diagram illustrating one embodiment of a negotiation of SL DRX configuration for unicast communication. The communications 600 are illustrated between a first SL UE 602 and a second SL UE 604. Each of the communications 600 may include one or more messages.


In a first communication 606, the first SL UE 602 transmits a SL DRX reconfiguration message (e.g., new offset_common_On-duration) to the second SL UE 604. In a second communication 608, the second SL UE 604 transmits a SL DRX reconfiguration complete message to the first SL UE 602. In a third communication 610, the new SL DRX configuration is applied to the first SL UE 602 and the second SL UE 604.


Specifically, as illustrated in FIG. 6, having started a unicast communication for a certain service according to its corresponding known SL DRX configuration, the first SL UE 602 aligns a SL DRX configuration with other SL DRX configurations to enable maximizing of its sleep time.


In some embodiments, alignment of On-durations between a group of UEs in a groupcast communication is used as shown in FIG. 7 where all group members at a moment communicate using one or more standard known SL DRX configurations. In such embodiments, one group member (e.g., a group leader) realizes opportunity for further power saving (e.g., realizes that there are more than one SL DRX configurations in use) and the group member requests that other group members (e.g., using a reconfiguration query) move to a different On-duration starting time called offset_common_On-duration. The reconfiguration query may be sent using a groupcast (“GC”) signaling (e.g., addressed to a layer 2 (“L2”) GC destination identifier (“ID”)). The offset_common_On-duration may be one of the offset_std_On-durations. In such embodiments, the group members may respond with a reconfiguration accept or a reconfiguration reject—that may be sent in a unicast (“UC”) manner to the initiating group member (e.g., to the group leader) or in a GC manner to the all group members. A reconfiguration reject sent by any member UE may lead to a negotiation failure or a new offset_common_On-duration may need to be negotiated. The initiating group member (e.g., the group leader) may announce actual reconfiguration of the SL DRX configurations.


In various embodiments, in a time-optimized implementation, group members (e.g., an initiating group member such as a group leader) announce reconfiguration of SL DRX configurations.


In certain embodiments, an offset_common_On-duration is advertised for each and/or any offset_std_On-duration relevant for communication relevant to a group—this helps a new group member to find the offset_common_On-duration. The offset_common_On-duration may be advertised by a group member (e.g., group leader) or by a roadside unit (“RSU”).


In some embodiments, a request and/or negotiation as shown in FIG. 8 may be done using NAS, RRC, or lower layer signaling. In various embodiments, if more than one UE triggers and/or sends a reconfiguration query: 1) the reconfiguration query that arrives later may be ignored by a group member; 2) a reconfiguration query from a UE with a smaller (or larger) member ID may be accepted; or 3) only a group leader can send a reconfiguration query.



FIG. 7 is a network communications 700 diagram illustrating one embodiment of a negotiation of SL DRX configuration for groupcast communication. The communications 700 are illustrated between a first SL UE 702, a second SL UE 704, a third SL UE 706, and an Nth SL UE 708. Each of the communications 700 may include one or more messages.


In a first communication 710, each of the first SL UE 702, the second SL UE 704, the third SL UE 706, and the Nth SL UE 708 group of UEs may follow a default SL DRX configuration. In a second communication 712, a third communication 714, and a fourth communication 716, the first SL UE 702 transmits a reconfiguration query message (e.g., new offset_common_On-duration) to the second SL UE 704, the third SL UE 706, and the Nth SL UE 708. In a fifth communication 718, a sixth communication 720, and a seventh communication 722, the second SL UE 704, the third SL UE 706, and the Nth SL UE 708 respectively transmit a reconfiguration accept message to the first SL UE 702. In an eighth communication 724, a ninth communication 726, and a tenth communication 728, the first SL UE 702 transmits a reconfiguration message (e.g., new offset_std_On-duration) to the second SL UE 704, the third SL UE 706, and the Nth SL UE 708. In an eleventh communication 730, the new SL DRX configuration is applied to the first SL UE 702, the second SL UE 704, the third SL UE 706, and the Nth SL UE 708.


In certain embodiments, an offset_common_On-duration is randomly picked from a set of offset values to facilitate proper resource utilization. The set of offset values may be configured, preconfigured, or specified. A possible configuration of the set of offset values may be achieved using RRC signaling, NAS signaling, or the set of offset values may be provided by the V2X layer.


In some embodiments, a SL DRX configuration is done in a manner similar to sidelink resource block (“SLRB”) configuration. This may be applicable for a unicast, a groupcast, and a broadcast connection. Further, this may be applicable to: 1) Mode 1: dedicated DRX configurations; and 2) Mode 2: broadcast DRX configurations (or pre-configured).


In various embodiments, a SL DRX configuration may be achieved by configuring resource pools such that SL resources are available only periodically. A UE may sleep in time periods where there are no SL resources available and may wake up on certain time occasions periodically if the SL resources again become available, to be able to use the SL resources for transmission and reception.


In certain embodiments, any reconfiguration of a SL resource may be done in advance and communicated to UEs accordingly. This may be done using: 1) a longer modification period—each modification period may contain more than one occasion of SL resources; or 2) the reconfiguration may only be carried out after ‘N’ modification periods. In some embodiments, SL resource pools may be given (e.g., by way of preconfiguration or specification). In such embodiments, the resource pools may not change or get reconfigured. The UE assumes that the transmission and reception time are according to known SL resource pool configurations and therefore may sleep if SL resources are not available.


One embodiment of a configuration of a resource pool using a sidelink resource pool information element (“IE”) is illustrated in Table 1.









TABLE 1





Sidelink Resource Pool IE

















-- ASNISTART










-- TAG-SL-RESOURCEPOOL-START










SL-ResourcePool-r16 ::=
SEQUENCE {



 sl-PSCCH-Config-r16
 SetupRelease { SL-PSCCH-Config-r16 }
      OPTIONAL,  --


Need M




 sl-PSSCH-Config-r16
 SetupRelease { SL-PSSCH-Config-r16 }
      OPTIONAL,  --


Need M




 sl-PSFCH-Config-r16
 SetupRelease { SL-PSFCH-Config-r16 }
      OPTIONAL,  --


Need M




  sl-offset_std_On-duration
    INTEGER (0..1024*5)










 OPTIONAL,


  sl-On-duration-timer
        ENUMERATED {ms2, ms20, ms200, infinite}



 OPTIONAL,


  sl-Periodicity
        ENUMERATED {one-fourth, half, one, two}



 OPTIONAL,









 sl-SyncAllowed-r16
SL-SyncAllowed-r16
  OPTIONAL, -- Need M








 sl-SubchannelSize-r16
 ENUMERATED {n10, n12, n15, n20, n25, n50, n75, n100}









OPTIONAL, -- Need M




 sl-TimeResource-r16
INTEGER (10..160)
  OPTIONAL, -- Need M


 sl-StartRB-Subchannel-r16
 INTEGER (0..265)
   OPTIONAL, -- Need


M




 sl-NumSubchannel-r16
INTEGER (1..27)
  OPTIONAL, -- Need M








 sl-Additional-MCS-Table-r16
    ENUMERATED { qam256, qam64LowSE, qam256-qam64LowSE }









OPTIONAL, -- Need M




 sl-ThreshS-RSSI-CBR-r16
INTEGER (0..45)
   OPTIONAL, -- Need


M




 sl-Time WindowSizeCBR-r16
 ENUMERATED {ms100, slot100}



OPTIONAL, -- Need M




 sl-Time WindowSizeCR-r16
 ENUMERATED {ms1000, slot1000}



OPTIONAL, -- Need M




 sl-PTRS-Config-r16
SL-PTRS-Config-r16
  OPTIONAL, -- Need M


 sl-UE-SelectedConfigRP-r16
 SL-UE-SelectedConfigRP-r16
      OPTIONAL,


Need M




 sl-RxParametersNcell-r16
SEQUENCE {



  sl-TDD-Configuration-r16
    TDD-UL-DL-ConfigCommon
      OPTIONAL, --


Need M




  sl-SyncConfigIndex-r16
INTEGER (0..15)









 }
              OPTIONAL, -- Need M


 sl-ZoneConfigMCR-List-r16
SEQUENCE (SIZE (16)) OF SL-ZoneConfigMCR-r16









OPTIONAL, -- Need M




 sl-FilterCoefficient-r16
 FilterCoefficient
OPTIONAL, -- Need M


sl-RB-Number-r16
INTEGER (10..275)
 OPTIONAL, -- Need M








 sl-PreemptionEnable-r16
  ENUMERATED {enabled, pl1, pl2, pl3, pl4, pl5, pl6, pl7, pl8}









OPTIONAL, -- Need R










sl-Priority Threshold-UL-URLLC-r16  INTEGER (1..9)
    OPTIONAL, --









Need M




sl-Priority Threshold-r16
 INTEGER (1..9)
OPTIONAL, -- Need M


sl-X-Overhead-r16
ENUMERATED {n0,n3, n6, n9}
    OPTIONAL, --


Need M




 sl-PowerControl-r16
SL-PowerControl-r16
   OPTIONAL, -- Need


M




sl-TxPercentageList-r16
SL-TxPercentageList-r16
OPTIONAL, -- Need M


sl-MinMaxMCS-List-r16
 SL-MinMaxMCS-List-r16
   OPTIONAL, -- Need


M




}









In some embodiments, a half-duplex (“HD”) issue may exist if multiple UEs buffering data for transmission attempt to transmit simultaneously at a start of a DRX On-duration.


In various embodiments, to avoid the HD issue, at least one re-transmission may be made for which a time of re-transmission is chosen randomly from a time window starting at an offset after a transmission has been made. The time window may be preconfigured, configured, or specified.


In certain embodiments, to avoid the HD issue, each member (e.g., in UC or GC) transmits in a round-robin fashion once an On-duration-timer is started. For example, a first member transmits in a first slot, a second member transmits in a second slot, and so forth. In such embodiments, at least one transmission is made by each member even if just to notify that there is no-data-available. The notification of no-data-available may be done using a medium access control (“MAC”) control element (“CE”), physical layer sidelink control information (“SCI”), or other signaling. Moreover, if a number of transmitters and/or transmitter members in a group is known from a higher layer for a groupcast then only transmitter UEs transmit in the round robin manner.


In some embodiments, a SL UE requests that a serving gNB align a Uu DRX cycle according to its SL DRX configuration. The SL UE sends UE assisted information (“UAI”) to the gNB, as shown in FIG. 8, signaling SL DRX configuration parameters (e.g., offset_std_On-duration, On-duration-timer, and periodicity) and: 1) the gNB may send back a Uu DRX configuration (e.g., RRCReconfiguration) that maximizes overlap of a Uu and a SL active time for the SL UE; 2) the gNB may send back a Uu DRX configuration (e.g., RRCReconfiguration) that does not necessarily maximize overlap of the Uu and the SL active time but rather attempts to average out system load and/or resource efficiency; or 3) the gNB may send back a Uu DRX configuration (e.g., RRCReconfiguration) that achieves a balance between the above two options.



FIG. 8 is a network communications 800 diagram illustrating one embodiment of Uu negotiation to align Uu and SL DRX. The communications 800 are illustrated between a UE 802 and a network 804. Each of the communications 800 may include one or more messages.


In a first communication 806, the UE 802 transmits UE assistance information (e.g., part of SL DRX configuration) to the network 804. In a second communication 808, the network 804 transmits an RRCReconfiguration message to the UE 802. The UE 802 applies the received Uu DRX configuration (e.g., RRCReconfiguration).


In various embodiments, a SL UE, upon transmitting or receiving data, may start and/or restart a SL inactivity timer (e.g., SL-inactivity-timer). If both the On-duration-timer (e.g., on duration timer) and the SL-inactivity-timer expire, the SL UE enters DRX sleep as shown in FIG. 9. The SL-inactivity-timer may also be started and/or restarted at one or more of the following occasions: 1) when indicating a negative acknowledgement (“NACK”) on a physical uplink control channel (“PUCCH”) to request a re-transmission grant; 2) when indicating an acknowledgement (“ACK”) on a PUCCH and having a non-empty SL buffer; 3) when it receives hybrid automatic repeat request (“HARQ”) feedback on a physical sidelink feedback channel (“PSFCH”); 4) when transmitting a SL scheduling request (“SR”) (“SL-SR”) and/or a SL buffer status report (“BSR”) (“SL-BSR”) to a gNB; 5) when requesting a channel state information (“CSI”) report on SL from a peer UE; 6) when having received a request for a CSI-report on SL from a peer UE; 7) when receiving SCI (e.g., PUCCH) which may contain a relevant source (“SRC”) layer 2 identifier (“L2ID”) and/or destination (“DST”) L2ID; 8) when receiving data (e.g., PSSCH); 9) when sending a PSFCH NACK feedback; 10) when transmitting SCI (e.g., PSCCH) requesting SL PSFCH feedback; 11) when transmitting non-last SCI (e.g., PSCCH) for blind re-transmissions; 12) when transmitting non-last data (e.g., PSSCH) for blind re-transmissions; and/or 13) a synchronization source uses an infinite (or very long) value of a SL-inactivity-timer.



FIG. 9 is a timing diagram 900 illustrating one embodiment of SL DRX interplay with timers. The timing diagram 900 illustrates a sleep time 902, a start 904 of an On-duration-timer, a time to wake-up 906, an event 908 triggering the start and/or restart of a SL-inactivity-timer, a start 910 of the SL-inactivity-timer, an expiration 912 of the On-duration-timer, and an expiration 914 of the SL-inactivity-timer.


In some embodiments, a resource pool configuration (e.g., from a network) and usage (e.g., from a UE) may be different for the following: 1) resource pool specific DRX: every resource pool has a configured SL DRX configuration—a SL UE chooses the SL DRX configuration according to its power saving needs and frequency of data transmission and/or reception for serving periodic applications; and 2) separate resource pools for vehicular traffic, for pedestrian UEs, for public safety, and/or for commercial SL UEs. In one example, a pedestrian (e.g., VRU) UE interested only in communicating with other pedestrian (e.g., VRU) UEs may use only a corresponding resource pool to receive and transmit messages. A vehicular UE may only transmit to pedestrian (e.g., VRU) UEs in that resource pool.



FIG. 10 is a flow chart diagram illustrating one embodiment of a method 1000 for sidelink discontinuous reception configuration. In some embodiments, the method 1000 is performed by an apparatus, such as the remote unit 102. In certain embodiments, the method 1000 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.


In various embodiments, the method 1000 includes accessing 1002 a sidelink discontinuous reception configuration. The sidelink discontinuous reception configuration corresponds to: a quality of service class; an identifier of the quality of service class; at least one attribute of the quality of service class; a range corresponding to the at least one attribute of the quality of service class; or some combination thereof. In some embodiments, the method 1000 includes performing 1004 sidelink communication based on the sidelink discontinuous reception configuration.


In certain embodiments, the sidelink discontinuous reception configuration comprises an offset from a fixed time reference for an on-duration, an on-duration timer, a periodicity, or some combination thereof. In some embodiments, the method 1000 further comprises receiving information indicating the offset for the on-duration, the on-duration timer, the periodicity, or some combination thereof.


In various embodiments, the information indicating the offset for the on-duration, the on-duration timer, the periodicity, or some combination thereof is received via non-access stratum signaling or radio resource control signaling. In one embodiment, the quality of service class comprises a quality of service class identifier for sidelink communication.



FIG. 11 is a flow chart diagram illustrating another embodiment of a method 1100 for sidelink discontinuous reception configuration. In some embodiments, the method 1100 is performed by an apparatus, such as the remote unit 102. In certain embodiments, the method 1100 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.


In various embodiments, the method 1100 includes determining 1102, at a first user equipment, at least one parameter for a sidelink discontinuous reception configuration. In some embodiments, the method 1100 includes transmitting 1104 the at least one parameter for the sidelink discontinuous reception configuration to a second user equipment. In certain embodiments, the method 1100 includes receiving 1106 feedback from the second user equipment indicating acceptance of the at least one parameter for the sidelink discontinuous reception configuration.


In certain embodiments, the method 1100 further comprises communicating with the second user equipment based on the sidelink discontinuous reception configuration. In some embodiments, the at least one parameter comprises an offset for an on-duration, an on-duration timer, a periodicity, or some combination thereof. In various embodiments, determining the at least one parameter for the sidelink discontinuous reception configuration comprises determining a change to the at least one parameter from a prior sidelink discontinuous reception configuration used by the first user equipment and the second user equipment.


In one embodiment, the at least one parameter for the sidelink discontinuous reception configuration is transmitted to the second user equipment using a sidelink interface, non-access stratum signaling, or sidelink radio resource control signaling. In certain embodiments, determining the at least one parameter for the sidelink discontinuous reception configuration is based on information received from a network device for the first user equipment to the network device discontinuous reception alignment or based on a time at which there is data available for transmission.



FIG. 12 is a flow chart diagram illustrating yet another embodiment of a method 1200 for sidelink discontinuous reception configuration. In some embodiments, the method 1200 is performed by an apparatus, such as the remote unit 102. In certain embodiments, the method 1200 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.


In various embodiments, the method 1200 includes accessing 1202 a sidelink discontinuous reception configuration. The sidelink discontinuous reception configuration includes a first offset for an on-duration, an on-duration timer, and a periodicity. In some embodiments, the method 1200 includes determining 1204 a second offset for the on-duration. In certain embodiments, the method 1200 includes transmitting 1206 data based on the sidelink discontinuous reception configuration and the second offset for the on-duration.


In certain embodiments, the data is transmitted at a time after the start of the on-duration timer that is offset by the second offset for the on-duration. In some embodiments, the method 1200 further comprises retransmitting the data at a second offset, wherein the second offset is randomly from a set of values. In various embodiments, the second offset for the on-duration is determined based on a number of user equipments transmitting data.



FIG. 13 is a flow chart diagram illustrating a further embodiment of a method 1300 for sidelink discontinuous reception configuration. In some embodiments, the method 1300 is performed by an apparatus, such as the remote unit 102. In certain embodiments, the method 1300 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.


In various embodiments, the method 1300 includes accessing 1302 a sidelink discontinuous reception configuration. The sidelink discontinuous reception configuration includes an offset for an on-duration, an on-duration timer, and a periodicity. In some embodiments, the method 1300 includes transmitting 1304 sidelink data, receiving the sidelink data, or a combination thereof. In certain embodiments, the method 1300 includes, in response to transmitting the sidelink data, receiving 1306 the sidelink data, or a combination thereof, starting a sidelink inactivity timer. In various embodiments, the method 1300 includes restarting 1308 the sidelink inactivity timer in response to: indicating a negative acknowledgement on a physical uplink control channel to request a retransmission grant to a base station; indicating an acknowledgement on the physical uplink control channel and in response to having a non-empty sidelink buffer to the base station; receiving hybrid automatic repeat request feedback on a physical sidelink feedback channel from a sidelink receiver user equipment; transmitting a sidelink scheduling request to a base station; transmitting a sidelink buffer status report to the base station; requesting a channel state information report on sidelink from a peer user equipment; receiving a request for a channel state information report on sidelink from a peer user equipment; receiving sidelink control information from the sidelink transmitter user equipment; receiving data from the sidelink transmitter user equipment; transmitting a physical sidelink feedback channel negative acknowledgement feedback to the sidelink transmitter user equipment; transmitting sidelink control information requesting sidelink physical sidelink feedback channel feedback; transmitting non-last sidelink control information while performing blind re-transmissions; transmitting non-last data while performing blind re-transmissions; a sync source using a value of a sidelink inactivity timer greater than a predetermined value; or some combination thereof.


In certain embodiments, the method 1300 further comprises, in response to the on-duration timer expiring and the sidelink inactivity timer expiring, entering a sleep mode.


In one embodiment, a method comprises: accessing a sidelink discontinuous reception configuration, wherein the sidelink discontinuous reception configuration corresponds to: a quality of service class; an identifier of the quality of service class; at least one attribute of the quality of service class; a range corresponding to the at least one attribute of the quality of service class; or some combination thereof; and performing sidelink communication based on the sidelink discontinuous reception configuration.


In certain embodiments, the sidelink discontinuous reception configuration comprises an offset from a fixed time reference for an on-duration, an on-duration timer, a periodicity, or some combination thereof.


In some embodiments, the method further comprises receiving information indicating the offset for the on-duration, the on-duration timer, the periodicity, or some combination thereof.


In various embodiments, the information indicating the offset for the on-duration, the on-duration timer, the periodicity, or some combination thereof is received via non-access stratum signaling or radio resource control signaling.


In one embodiment, the quality of service class comprises a quality of service class identifier for sidelink communication.


In one embodiment, an apparatus comprises: a processor that: accesses a sidelink discontinuous reception configuration, wherein the sidelink discontinuous reception configuration corresponds to: a quality of service class; an identifier of the quality of service class; at least one attribute of the quality of service class; a range corresponding to the at least one attribute of the quality of service class; or some combination thereof; and performs sidelink communication based on the sidelink discontinuous reception configuration.


In certain embodiments, the sidelink discontinuous reception configuration comprises an offset from a fixed time reference for an on-duration, an on-duration timer, a periodicity, or some combination thereof.


In some embodiments, the apparatus further comprises a receiver that receives information indicating the offset for the on-duration, the on-duration timer, the periodicity, or some combination thereof.


In various embodiments, the information indicating the offset for the on-duration, the on-duration timer, the periodicity, or some combination thereof is received via non-access stratum signaling or radio resource control signaling.


In one embodiment, the quality of service class comprises a quality of service class identifier for sidelink communication.


In one embodiment, a method comprises: determining, at a first user equipment, at least one parameter for a sidelink discontinuous reception configuration; transmitting the at least one parameter for the sidelink discontinuous reception configuration to a second user equipment; and receiving feedback from the second user equipment indicating acceptance of the at least one parameter for the sidelink discontinuous reception configuration.


In certain embodiments, the method further comprises communicating with the second user equipment based on the sidelink discontinuous reception configuration.


In some embodiments, the at least one parameter comprises an offset for an on-duration, an on-duration timer, a periodicity, or some combination thereof.


In various embodiments, determining the at least one parameter for the sidelink discontinuous reception configuration comprises determining a change to the at least one parameter from a prior sidelink discontinuous reception configuration used by the first user equipment and the second user equipment.


In one embodiment, the at least one parameter for the sidelink discontinuous reception configuration is transmitted to the second user equipment using a sidelink interface, non-access stratum signaling, or sidelink radio resource control signaling.


In certain embodiments, determining the at least one parameter for the sidelink discontinuous reception configuration is based on information received from a network device for the first user equipment to the network device discontinuous reception alignment or based on a time at which there is data available for transmission.


In one embodiment, an apparatus comprising a first user equipment. The apparatus further comprises: a processor that determines at least one parameter for a sidelink discontinuous reception configuration; a transmitter that transmits the at least one parameter for the sidelink discontinuous reception configuration to a second user equipment; and a receiver that receives feedback from the second user equipment indicating acceptance of the at least one parameter for the sidelink discontinuous reception configuration.


In certain embodiments, the transmitter and the receiver communicate with the second user equipment based on the sidelink discontinuous reception configuration.


In some embodiments, the at least one parameter comprises an offset for an on-duration, an on-duration timer, a periodicity, or some combination thereof.


In various embodiments, the processor determining the at least one parameter for the sidelink discontinuous reception configuration comprises the processor determining a change to the at least one parameter from a prior sidelink discontinuous reception configuration used by the first user equipment and the second user equipment.


In one embodiment, the at least one parameter for the sidelink discontinuous reception configuration is transmitted to the second user equipment using a sidelink interface, non-access stratum signaling, or sidelink radio resource control signaling.


In certain embodiments, the processor determining the at least one parameter for the sidelink discontinuous reception configuration is based on information received from a network device for the first user equipment to the network device discontinuous reception alignment or based on a time at which there is data available for transmission.


In one embodiment, a method comprises: accessing a sidelink discontinuous reception configuration, wherein the sidelink discontinuous reception configuration comprises a first offset for an on-duration, an on-duration timer, and a periodicity; determining a second offset for the on-duration; and transmitting data based on the sidelink discontinuous reception configuration and the second offset for the on-duration.


In certain embodiments, the data is transmitted at a time after the start of the on-duration timer that is offset by the second offset for the on-duration.


In some embodiments, the method further comprises retransmitting the data at a second offset, wherein the second offset is randomly from a set of values.


In various embodiments, the second offset for the on-duration is determined based on a number of user equipments transmitting data.


In one embodiment, an apparatus comprises: a processor that: accesses a sidelink discontinuous reception configuration, wherein the sidelink discontinuous reception configuration comprises a first offset for an on-duration, an on-duration timer, and a periodicity; and determines a second offset for the on-duration; and a transmitter that transmits data based on the sidelink discontinuous reception configuration and the second offset for the on-duration.


In certain embodiments, the data is transmitted at a time after the start of the on-duration timer that is offset by the second offset for the on-duration.


In some embodiments, the transmitter retransmits the data at a second offset, wherein the second offset is randomly from a set of values.


In various embodiments, the second offset for the on-duration is determined based on a number of user equipments transmitting data.


In one embodiment, a method comprises: accessing a sidelink discontinuous reception configuration, wherein the sidelink discontinuous reception configuration comprises an offset for an on-duration, an on-duration timer, and a periodicity; transmitting sidelink data, receiving the sidelink data, or a combination thereof; in response to transmitting the sidelink data, receiving the sidelink data, or a combination thereof, starting a sidelink inactivity timer; and restarting the sidelink inactivity timer in response to: indicating a negative acknowledgement on a physical uplink control channel to request a retransmission grant to a base station; indicating an acknowledgement on the physical uplink control channel and in response to having a non-empty is sidelink buffer to the base station; receiving hybrid automatic repeat request feedback on a physical sidelink feedback channel from a sidelink receiver user equipment; transmitting a sidelink scheduling request to a base station; transmitting a sidelink buffer status report to the base station; requesting a channel state information report on sidelink from a peer user equipment; receiving a request for a channel state information report on sidelink from a peer user equipment; receiving sidelink control information from the sidelink transmitter user equipment; receiving data from the sidelink transmitter user equipment; transmitting a physical sidelink feedback channel negative acknowledgement feedback to the sidelink transmitter user equipment; transmitting sidelink control information requesting sidelink physical sidelink feedback channel feedback; transmitting non-last sidelink control information while performing blind re-transmissions; transmitting non-last data while performing blind re-transmissions; a sync source using a value of a sidelink inactivity timer greater than a predetermined value; or some combination thereof.


In certain embodiments, the method further comprises, in response to the on-duration timer expiring and the sidelink inactivity timer expiring, entering a sleep mode.


In one embodiment, an apparatus comprises: a processor that accesses a sidelink discontinuous reception configuration, wherein the sidelink discontinuous reception configuration comprises an offset for an on-duration, an on-duration timer, and a periodicity; a transmitter; and a receiver, wherein the transmitter transmits sidelink data, the receiver receives the sidelink data, or a combination thereof wherein: in response to the transmitter transmitting sidelink data, the receiver receiving the sidelink data, or a combination thereof, the processor starts a sidelink inactivity timer; the processor restarts the sidelink inactivity timer in response to: indicating a negative acknowledgement on a physical uplink control channel to request a retransmission grant to a base station; indicating an acknowledgement on the physical uplink control channel and in response to having a non-empty sidelink buffer to the base station; receiving hybrid automatic repeat request feedback on a physical sidelink feedback channel from a sidelink receiver user equipment; transmitting a sidelink scheduling request to a base station; transmitting a sidelink buffer status report to the base station; requesting a channel state information report on sidelink from a peer user equipment; receiving a request for a channel state information report on sidelink from a peer user equipment; receiving sidelink control information from the sidelink transmitter user equipment; receiving data from the sidelink transmitter user equipment; transmitting a physical sidelink feedback channel negative acknowledgement feedback to the sidelink transmitter user equipment; transmitting sidelink control information requesting sidelink physical sidelink feedback channel feedback; transmitting non-last sidelink control information while performing blind re-transmissions; transmitting non-last data while performing blind re-transmissions; a sync source using a value of a sidelink inactivity timer greater than a predetermined value; or some combination thereof.


In certain embodiments, the processor, in response to the on-duration timer expiring and the sidelink inactivity timer expiring, enters a sleep mode.


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. An apparatus comprising: a processor that:accesses a sidelink discontinuous reception configuration, wherein the sidelink discontinuous reception configuration corresponds to: a quality of service class;an identifier of the quality of service class;at least one attribute of the quality of service class;or some combination thereof; andperforms sidelink communication based on the sidelink discontinuous reception configuration.
  • 2. The apparatus of claim 1, wherein the sidelink discontinuous reception configuration comprises an on-duration timer, a periodicity, or some combination thereof.
  • 3. The apparatus of claim 2, further comprising a receiver that receives information indicating the offset for the on-duration, the on-duration timer, the periodicity, or some combination thereof.
  • 4. The apparatus of claim 3, wherein the information indicating the offset for the on-duration, the on-duration timer, the periodicity, or some combination thereof is received via non-access stratum signaling or radio resource control signaling.
  • 5. The apparatus of claim 1, wherein the quality of service class comprises a quality of service class identifier for sidelink communication.
  • 6. An apparatus comprising a first user equipment, the apparatus further comprises: a processor that determines at least one parameter for a sidelink discontinuous reception configuration;a transmitter that transmits the at least one parameter for the sidelink discontinuous reception configuration to a second user equipment; anda receiver that receives feedback from the second user equipment indicating acceptance of the at least one parameter for the sidelink discontinuous reception configuration.
  • 7. The apparatus of claim 6, wherein the transmitter and the receiver communicate with the second user equipment based on the sidelink discontinuous reception configuration.
  • 8. The apparatus of claim 6, wherein the at least one parameter comprises an offset for an on-duration, an on-duration timer, a periodicity, or some combination thereof.
  • 9. The apparatus of claim 6, wherein the processor determining the at least one parameter for the sidelink discontinuous reception configuration comprises the processor determining a change to the at least one parameter from a prior sidelink discontinuous reception configuration used by the first user equipment and the second user equipment.
  • 10. The apparatus of claim 6, wherein the at least one parameter for the sidelink discontinuous reception configuration is transmitted to the second user equipment using a sidelink interface, non-access stratum signaling, or sidelink radio resource control signaling.
  • 11. The apparatus of claim 6, wherein the at least one parameter for the sidelink discontinuous reception configuration is determined based on discontinuous reception alignment information received from a network device.
  • 12. (canceled)
  • 13. (canceled)
  • 14. (canceled)
  • 15. (canceled)
  • 16. An apparatus comprising: a processor that accesses a sidelink discontinuous reception configuration, wherein the sidelink discontinuous reception configuration comprises an offset for an on-duration, an on-duration timer, and a periodicity;a transmitter; anda receiver, wherein the transmitter transmits sidelink data, the receiver receives the sidelink data, or a combination thereof;wherein:in response to the transmitter transmitting sidelink data, the receiver receiving the sidelink data, or a combination thereof, the processor starts a sidelink inactivity timer;the processor restarts the sidelink inactivity timer in response to: indicating a negative acknowledgement on a physical uplink control channel to request a retransmission grant to a base station;indicating an acknowledgement on the physical uplink control channel and in response to having a non-empty sidelink buffer to the base station;receiving hybrid automatic repeat request feedback on a physical sidelink feedback channel from a sidelink receiver user equipment;transmitting a sidelink scheduling request to a base station;transmitting a sidelink buffer status report to the base station;requesting a channel state information report on sidelink from a peer user equipment;receiving a request for a channel state information report on sidelink from a peer user equipment;receiving sidelink control information from the sidelink transmitter user equipment;receiving data from the sidelink transmitter user equipment;transmitting a physical sidelink feedback channel negative acknowledgement feedback to the sidelink transmitter user equipment;transmitting sidelink control information requesting sidelink physical sidelink feedback channel feedback;transmitting non-last sidelink control information while performing blind re-transmissions;transmitting non-last data while performing blind re-transmissions;a sync source using a value of a sidelink inactivity timer greater than a predetermined value;or some combination thereof.
  • 17. The apparatus of claim 16, wherein the processor, in response to the on-duration timer expiring and the sidelink inactivity timer expiring, enters a sleep mode.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Patent Application Ser. No. 63/051,184 entitled “APPARATUSES, METHODS, AND SYSTEMS FORA SIDELINK DRX MECHANISM-INTERACTION WITH UU DRX OPERATION” and filed on Jul. 13, 2020 for Joachim Loehr, U.S. Patent Application Ser. No. 63/051,207 entitled “APPARATUSES, METHODS, AND SYSTEMS FOR SIDELINK POWER SAVING USING A DRX MECHANISM AND MINIMIZING ENSUING HALF DUPLEX ISSUES” and filed on Jul. 13, 2020 for Prateek Basu Mallick, U.S. Patent Application Ser. No. 63/051,217 entitled “APPARATUSES, METHODS, AND SYSTEMS FOR SUPPORTING POWER SAVING FOR PC5 COMMUNICATIONS” and filed on Jul. 13, 2020 for Dimitrios Karampatsis, and U.S. Patent Application Ser. No. 63/051,233 entitled “APPARATUSES, METHODS, AND SYSTEMS FOR ENHANCEMENT FOR SL POWER SAVING” and filed on Jul. 13, 2020 for Karthikeyan Ganesan, all of which are incorporated herein by reference in their entirety.

PCT Information
Filing Document Filing Date Country Kind
PCT/IB2021/056209 7/10/2021 WO
Provisional Applications (4)
Number Date Country
63051184 Jul 2020 US
63051207 Jul 2020 US
63051217 Jul 2020 US
63051233 Jul 2020 US