US20230276527A1 - Discontinuous reception configuration parameters for communication - Google Patents

Discontinuous reception configuration parameters for communication Download PDF

Info

Publication number
US20230276527A1
US20230276527A1 US18/016,119 US202118016119A US2023276527A1 US 20230276527 A1 US20230276527 A1 US 20230276527A1 US 202118016119 A US202118016119 A US 202118016119A US 2023276527 A1 US2023276527 A1 US 2023276527A1
Authority
US
United States
Prior art keywords
discontinuous reception
radio interface
over
communication
configuration parameters
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
US18/016,119
Other languages
English (en)
Inventor
Dimitrios Karampatsis
Karthikeyan Ganesan
Prateek Basu Mallick
Joachim Loehr
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lenovo Singapore Pte Ltd
Original Assignee
Lenovo Singapore Pte Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo Singapore Pte Ltd filed Critical Lenovo Singapore Pte Ltd
Priority to US18/016,119 priority Critical patent/US20230276527A1/en
Assigned to LENOVO (SINGAPORE) PTE. LTD. reassignment LENOVO (SINGAPORE) PTE. LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KARAMPATSIS, DIMITRIOS, BASU MALLICK, PRATEEK, LOEHR, JOACHIM, GANESAN, KARTHIKEYAN
Publication of US20230276527A1 publication Critical patent/US20230276527A1/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0235—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a power saving command
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0245—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal according to signal strength
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/25—Control channels or signalling for resource management between terminals via a wireless link, e.g. sidelink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/40—Resource management for direct mode communication, e.g. D2D or sidelink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/188—Time-out mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the subject matter disclosed herein relates generally to wireless communications and more particularly relates to discontinuous reception configuration parameters for communication.
  • discontinuous reception may be used.
  • the devices in the network may be configured in a variety of ways.
  • One embodiment of a method includes receiving, at a first user equipment and over a first radio interface, discontinuous reception configuration parameters for communication over a second radio interface. In some embodiments, the method includes receiving quality of service requirements for transmission over the second radio interface. In certain embodiments, the method includes determining discontinuous reception communication parameters based on the discontinuous reception configuration parameters and based on the quality of service requirements. In various embodiments, the method includes transmitting and receiving communications over the second radio interface based on the discontinuous reception communication parameters.
  • One apparatus for discontinuous reception configuration parameters for communication includes a first user equipment.
  • the apparatus includes a receiver that: receives, over a first radio interface, discontinuous reception configuration parameters for communication over a second radio interface; and receives quality of service requirements for transmission over the second radio interface.
  • the apparatus includes a processor that determines discontinuous reception communication parameters based on the discontinuous reception configuration parameters and based on the quality of service requirements.
  • the apparatus includes a transmitter. The transmitter transmits communications and the receiver receives communications over the second radio interface based on the discontinuous reception communication parameters.
  • a method for discontinuous reception configuration parameters for communication includes receiving, at a policy control function and over a first radio interface, a policy association request for a corresponding user equipment.
  • the method includes obtaining a subscription profile for the user equipment.
  • the subscription profile includes a default discontinuous reception configuration for a second radio interface.
  • the method includes determining configuration information for communications over the second radio interface for the first user equipment.
  • the method includes transmitting the configuration information to the user equipment via non-access stratum control plane signaling over the first radio interface.
  • the apparatus includes a receiver that receives, over a first radio interface, a policy association request for a corresponding user equipment.
  • the apparatus includes a processor that: obtains a subscription profile for the user equipment, wherein the subscription profile includes a default discontinuous reception configuration for a second radio interface; and determines configuration information for communications over the second radio interface for the first user equipment.
  • the apparatus includes a transmitter that transmits the configuration information to the user equipment via non-access stratum control plane signaling over the first radio interface.
  • FIG. 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for discontinuous reception configuration parameters for communication
  • FIG. 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for discontinuous reception configuration parameters for communication;
  • FIG. 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for discontinuous reception configuration parameters for communication
  • FIG. 4 is a timing diagram illustrating one embodiment of a system for transmitting a message over a PC5 interface based on a DRX configuration
  • FIG. 5 is a schematic block diagram illustrating one embodiment of a system for extending DRX to support a required QoS
  • FIG. 6 is a network communications diagram illustrating one embodiment of a DRX configuration via NAS (e.g., AMF based);
  • NAS e.g., AMF based
  • FIG. 7 is a network communications diagram illustrating another embodiment of a DRX configuration between UEs for unicast sidelink communication over PC5;
  • FIG. 8 is a network communications diagram illustrating one embodiment of a DRX configuration via NAS (e.g., PCF based);
  • NAS e.g., PCF based
  • FIG. 9 is a network communications diagram illustrating one embodiment of a DRX configuration via a relay UE (e.g., RSU);
  • a relay UE e.g., RSU
  • FIG. 10 is a flow chart diagram illustrating one embodiment of a method for discontinuous reception configuration parameters for communication.
  • FIG. 11 is a flow chart diagram illustrating another embodiment of a method for discontinuous reception configuration parameters for communication.
  • 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.
  • modules 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.
  • VLSI very-large-scale integration
  • 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.
  • 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.
  • 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.
  • the software portions are stored on one or more computer readable storage devices.
  • 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.
  • a storage device 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.
  • 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.
  • 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).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider an Internet Service Provider
  • 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.
  • 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).
  • FIG. 1 depicts an embodiment of a wireless communication system 100 for discontinuous reception configuration parameters for communication.
  • 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 .
  • 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.
  • the remote units 102 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like.
  • 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.
  • 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
  • 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.
  • 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.
  • 3GPP third generation partnership project
  • SC-FDMA single-carrier frequency division multiple access
  • OFDM orthogonal frequency division multiplexing
  • 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.
  • WiMAX institute of electrical and electronics engineers
  • IEEE institute of electrical and electronics engineers
  • GSM global system for mobile communications
  • GPRS general packet radio service
  • UMTS universal mobile telecommunications system
  • LTE long term evolution
  • CDMA2000 code division multiple access 2000
  • Bluetooth® ZigBee
  • ZigBee ZigBee
  • Sigfoxx among other protocols.
  • 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.
  • a remote unit 102 may receive, at a first user equipment and over a first radio interface, discontinuous reception configuration parameters for communication over a second radio interface. In some embodiments, the remote unit 102 may receive quality of service requirements for transmission over the second radio interface. In certain embodiments, the remote unit 102 may determine discontinuous reception communication parameters based on the discontinuous reception configuration parameters and based on the quality of service requirements. In various embodiments, the remote unit 102 may transmit and receive communications over the second radio interface based on the discontinuous reception communication parameters. Accordingly, the remote unit 102 may be used for discontinuous reception configuration parameters for communication.
  • a network unit 104 may receive, at a policy control function and over a first radio interface, a policy association request for a corresponding user equipment.
  • the network unit 104 may obtain a subscription profile for the user equipment.
  • the subscription profile includes a default discontinuous reception configuration for a second radio interface.
  • the network unit 104 may determine configuration information for communications over the second radio interface for the first user equipment.
  • the network unit 104 may transmit the configuration information to the user equipment via non-access stratum control plane signaling over the first radio interface. Accordingly, the network unit 104 may be used for discontinuous reception configuration parameters for communication.
  • FIG. 2 depicts one embodiment of an apparatus 200 that may be used for discontinuous reception configuration parameters for communication.
  • the apparatus 200 includes one embodiment of the remote unit 102 .
  • 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 .
  • the input device 206 and the display 208 are combined into a single device, such as a touchscreen.
  • the remote unit 102 may not include any input device 206 and/or display 208 .
  • 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 may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations.
  • 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.
  • 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.
  • the memory 204 includes volatile computer storage media.
  • the memory 204 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”).
  • the memory 204 includes non-volatile computer storage media.
  • the memory 204 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device.
  • the memory 204 includes both volatile and non-volatile computer storage media.
  • 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 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like.
  • the input device 206 may be integrated with the display 208 , for example, as a touchscreen or similar touch-sensitive display.
  • 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.
  • the input device 206 includes two or more different devices, such as a keyboard and a touch panel.
  • the display 208 may include any known electronically controllable display or display device.
  • the display 208 may be designed to output visual, audible, and/or haptic signals.
  • the display 208 includes an electronic display capable of outputting visual data to a user.
  • 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.
  • the display 208 may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like.
  • 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.
  • the display 208 includes one or more speakers for producing sound.
  • the display 208 may produce an audible alert or notification (e.g., a beep or chime).
  • the display 208 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback.
  • all or portions of the display 208 may be integrated with the input device 206 .
  • the input device 206 and display 208 may form a touchscreen or similar touch-sensitive display.
  • the display 208 may be located near the input device 206 .
  • the receiver 210 receives, over a first radio interface, discontinuous reception configuration parameters for communication over a second radio interface; and receives quality of service requirements for transmission over the second radio interface.
  • the processor 202 determines discontinuous reception communication parameters based on the discontinuous reception configuration parameters and based on the quality of service requirements.
  • the transmitter 212 transmits communications and the receiver 210 receives communications over the second radio interface based on the discontinuous reception communication parameters.
  • 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.
  • 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 discontinuous reception configuration parameters for communication.
  • the apparatus 300 includes one embodiment of the network unit 104 .
  • 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 .
  • 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.
  • the receiver 312 receives, over a first radio interface, a policy association request for a corresponding user equipment.
  • the processor 302 obtains a subscription profile for the user equipment, wherein the subscription profile includes a default discontinuous reception configuration for a second radio interface; and determines configuration information for communications over the second radio interface for the first user equipment.
  • the transmitter 310 transmits the configuration information to the user equipment via non-access stratum control plane signaling over the first radio interface.
  • sidelink communication over a user equipment (“UE”) to UE interface (“PC5”) interface for pedestrians may support sidelink communication with power efficiency.
  • UE user equipment
  • PC5 UE interface
  • a vehicle to everything (“V2X”) UE transmits a message for sidelink communication over PC5 at a constant rate.
  • V2X vehicle to everything
  • CAM cooperative awareness message
  • This constant operation may reduce the power efficiency of the UE.
  • V2X UEs e.g., cars or roadside units (“RSUs”)
  • RSUs roadside units
  • pedestrian UEs e.g., smartphones, smart watches
  • battery capacity or radio resources available e.g., smartphones, smart watches
  • a V2X pedestrian UE applies discontinuous reception (“DRX”) over PC5 in a manner to increase power efficiency.
  • DRX discontinuous reception
  • DRX synchronization is carried out between V2X UEs running the same application and/or service to increase power efficiency.
  • eNB and/or gNB are used for a base station but may be replaceable by any other radio access node (e.g., base station (“BS”), eNB, gNB, access point (“AP”), new radio (“NR”), and so forth).
  • BS base station
  • eNB evolved node
  • gNB access point
  • NR new radio
  • certain embodiments described herein may be described in the context of NR V2X. However, embodiments herein may be applicable to any mobile communication systems supporting sidelink Communication over a PC5 interface. Moreover, any of the embodiments described herein may be combined together.
  • a UE may be configured with DRX to use for sidelink communication over PC5.
  • a UE receives a DRX configuration for sidelink communication over PC5 via non-access stratum (“NAS”) signaling from an application management function (“AMF”) or policy control function (“PCF”).
  • applications may provide synchronization parameters that assist a UE (e.g., V2X layer) to identify required DRX parameters.
  • a UE receives a DRX configuration from a UE acting as a DRX synchronization function (e.g., an RSU UE).
  • the UE applies the DRX for transmitting and/or receiving V2X messages as shown in FIG. 4 .
  • the UE configures an “Active Time” and an “Inactive Time” for sidelink communication over PC5 based on the received DRX configuration. Further, when the UE is in the “Inactive Time,” the UE enters into a “sleep” state and does not transmit or listen for sidelink communication messages over PC5. Moreover, when the UE is in the “Active Time,” the UE may transmit data provided by a V2X application layer or listen for sidelink communication messages over PC5. If the V2X application provides the data during a UE inactive state, the UE buffers the data and transmits it during the Active Time period.
  • a UE may apply the same DRX configuration for communication over a UE to network interface (“Uu”) and a PC5 interface.
  • Uu network interface
  • PC5 interface a PC5 interface
  • FIG. 4 is a timing diagram 400 illustrating one embodiment of a system for transmitting a message over a PC5 interface based on a DRX configuration.
  • the timing diagram 400 illustrates timing of communications of an application layer 402 compared to a UE state 404 based on DRX. While the UE state 404 is in an inactive period 406 , the application layer 402 transmits data 408 and includes a first time period from 410 to 412 . Moreover, a second time period 414 (e.g., 1 sec) may be between each data 408 transmission.
  • the UE state 404 may have an active time 416 as illustrated.
  • a UE receives a DRX configuration to use for sidelink communication over PC5 from an AMF or PCF via NAS signaling.
  • an AMF determines that a DRX configuration for sidelink communication over PC5 is required to be provided to a UE based on a UE subscription. More specifically, the AMF determines, by receiving from a unified data repository (“UDR”), the UE subscription that includes information indicating whether the UE is authorized to perform sidelink communication over PC5 as a pedestrian UE.
  • the DRX configuration that is provided to the UE may be based on a pre-configuration at the AMF.
  • the pre-configuration may be carried out by a network operator based on a knowledge of quality of service (“QoS”) requirements of applications providing pedestrian services.
  • QoS quality of service
  • V2X applications may require sidelink communications over PC5 for a V2X service (e.g., identified by a provider service identifier (“PSID”) or intelligent transports systems application identifier (“ITS-AID”) with specific QoS requirements. For example, low latency and high guaranteed bit rate (“GBR”) requirements.
  • PSID provider service identifier
  • ITS-AID intelligent transports systems application identifier
  • GBR guaranteed bit rate
  • a DRX configuration provided by an AMF may not be adequate to sustain the low latency and/or high GBR.
  • a UE may add an offset in a configured DRX to extend the “Active Time” for transmitting the data according to the low latency and/or high GBR requirements of the application. This is shown in FIG. 5 .
  • FIG. 5 is a schematic block diagram 500 illustrating one embodiment of a system for extending DRX to support a required QoS.
  • a UE state 502 (e.g., based on DRX to support low latency QoS) includes a repetition of an active time 504 followed by an offset 506 , followed by an inactive period 508 .
  • FIG. 6 is a network communications 600 diagram illustrating one embodiment of a DRX configuration via NAS (e.g., AMF based).
  • the network communications 600 are made between a UE 602 (e.g., pedestrian UE), an AMF 604 , and a unified data management (“UDM”) and/or UDR (“UDM/UDR”) 606 .
  • Each of the illustrated network communications 600 may include one or more messages.
  • the UE 602 transmits a message to register to a 3GPP network using standard authentication procedures by sending a registration request to the AMF 604 .
  • the UE 602 includes an indication in the registration request that the UE 602 is V2X capable.
  • the AMF 604 performs 610 an authentication server function (“AUSF”) selection, authentication, and security.
  • AUSF authentication server function
  • the AMF 604 receives a subscription profile from the UDR/UDM 606 .
  • the UDM/UDR 606 contains 614 the subscription profile that may include information indicating that the UE 602 is authorized for V2X communication over PC5 as a pedestrian UE.
  • the AMF 604 determines 616 from the subscription provide that the UE 602 is authorized for V2X communication over PC5 as a pedestrian UE.
  • the AMF 604 determines 618 the DRX configuration required over PC5. Further, the AMF 604 ensures that all UEs registered on the same traffic area receive the same DRX configuration.
  • the AMF 604 In a third communication 620 transmitted from the AMF 604 to the UE 602 , the AMF 604 provides the DRX configuration over PC5 in a registration accept message sent to the UE 602 .
  • the UE 602 determines 622 an Active Time and an Inactive Time.
  • the UE 602 transmits and/or listens for sidelink communications over PC5 only during the Active Time.
  • an access stratum (“AS”) layer of the UE 602 configures the Active Time and the Inactive Time for PC5.
  • the AS layer in the UE 602 does not transmit or monitor for V2X messages during the Inactive Time. This may apply to broadcast, groupcast, and unicast transmissions.
  • the AS layer of the UE 602 may notify 624 higher layers about at which time interval a V2X message may be transmitted. Moreover, an application in the UE 602 requests 626 to send a message over sidelink communication over PC5 with specific QoS requirements. Further, the UE 602 determines 628 that the configured DRX cannot support the QoS requirements and determines an additional offset in the configured DRX to support the required QoS. The UE 602 applies 630 the DRX for all sidelink communications over PC5 for any V2X service. Once the UE 602 determines the DRX required, the UE 602 may exchange the DRX with other UEs that are using the same V2X application and V2X service via unicast signaling.
  • a UE may determine that a different DRX configuration is required when two UEs exchange QoS requirements during sidelink communications over PC5 over a unicast link. This is illustrated in FIG. 7 .
  • FIG. 7 is a network communications 700 diagram illustrating another embodiment of a DRX configuration between UEs for unicast sidelink communication over PC5.
  • the network communications 700 are made between a first UE 702 (e.g., pedestrian UE) and a second UE 704 (e.g., pedestrian UE).
  • Each of the illustrated network communications 700 may include one or more messages.
  • a first communication 706 transmitted between the first UE 702 and the second UE 704 based on a received DRX configuration the first UE 702 and the second UE 704 determine an Active Time and an Inactive Time.
  • the first UE 702 and the second UE 704 transmit and/or listen for sidelink communications over PC5 only during the Active Time.
  • the AS layer of each UE may notify higher layers of the Active Time and the Inactive Time used.
  • a third communication 710 transmitted between the first UE 702 and the second UE 704 if the first UE 702 needs to establish a unicast session over PC5 with the second UE 704 , the first UE 702 establishes the unicast connection during the Active Time period.
  • both the first UE 702 and the second UE 704 determine the QoS requirements and associated DRX configuration.
  • Both the first UE 702 and the second UE 704 use 712 the negotiated DRX. If the unicast session ends, the first UE 702 and the second UE 704 fallback to a default DRX.
  • a DRX configuration is provided via NAS from a PCF.
  • the PCF provides a default DRX over PC5 for V2X services that are used by pedestrian UEs within a provisioned V2X configuration information.
  • the V2X configuration information may include: 1) a mapping of a V2X service for pedestrian UEs (e.g., identified by a PSID or ITS-AID) to a default DRX configuration; 2) a mapping of DRX configuration per QoS requirement (e.g., QoS class, packet delay budget (“PDB”), etc.)—in one embodiment there may be a default DRX configuration and an additional offset per QoS requirement; and/or 3) a mapping of DRX configuration per cast type (e.g., broadcast, unicast, groupcast).
  • QoS requirement e.g., QoS class, packet delay budget (“PDB”), etc.
  • a UE uses a DRX configuration within a V2X configuration to determine the DRX. If the application has specific QoS requirements, the UE determines an additional offset based on the received DRX configuration.
  • a procedure to provide a UE with a DRX configuration from a PCF is shown in FIG. 8 .
  • FIG. 8 is a network communications 800 diagram illustrating one embodiment of a DRX configuration via NAS (e.g., PCF based).
  • the network communications 800 are made between a first UE 802 (e.g., pedestrian UE), a second UE 804 (e.g., pedestrian UE), a RAN 806 , an AMF 808 , a UDM/UDR 810 , and a PCF 812 .
  • Each of the illustrated network communications 800 may include one or more messages.
  • the first UE 802 and the second UE 804 register to the 3GPP network using standard authentication procedures by sending a registration request.
  • the first UE 802 and the second UE 804 include an indication in the registration request that the first UE 802 and the second UE 804 are V2X capable.
  • the AMF 808 performs 818 an AUSF selection, authentication, and security.
  • a third communication 820 transmitted between the AMF 808 and the UDM/UDR 810 during the registration procedure the AMF 808 receives a subscription profile from the UDR/UDM 810 .
  • the UDM/UDR 810 contains 822 the subscription profile that may include information indicating that the UEs are authorized for V2X communication over PC5 as pedestrian UEs.
  • the AMF 808 determines 824 from the subscription provide that the UEs are authorized for V2X communication over PC5 as pedestrian UEs and selects the PCF 812 .
  • the AMF 808 In a fourth communication 826 transmitted between the AMF 808 and the PCF 812 , the AMF 808 establishes a UE policy association with the PCF 812 including a V2X capability indication.
  • the AMF 808 completes registration with the UEs with a registration accept message.
  • the PCF 812 determines 832 the V2X configuration based on subscription information provided by the UDM/UDR 810 .
  • the PCF 812 includes in the V2X configuration a DRX configuration for sidelink communication over PC5.
  • the PCF 812 In a seventh communication 834 transmitted from the PCF 812 to the first UE 802 and/or in an eighth communication 836 transmitted from the PCF 812 to the second UE 804 , the PCF 812 provides the V2X configuration to the UEs using a UE policy delivery via a transparent UE configuration update.
  • the first UE 802 and the second UE 806 determine 838 an Active Time and an Inactive Time.
  • the first UE 802 and the second UE 806 transmit and/or listen for V2X messages over PC5 for specific V2X services used by pedestrians (e.g., according to the DRX configuration over PC5) only during the Active Time.
  • an application's message periodicity and QoS requirements are provided from upper layers to a V2X layer of a UE.
  • the V2X layer determines the best DRX configuration based on each application's requirements and the DRX configuration received as described in the first embodiment.
  • DRX over PC5 is synchronized via sidelink communications over PC5 with a UE that supports DRX configuration synchronization of one or more V2X services (e.g., this UE as a ‘DRX sync’ UE and/or a relay UE).
  • the DRX sync UE may be an RSU supporting sidelink communications over PC5 and/or Uu.
  • the DRX sync UE advertises via broadcast signaling the V2X services that it supports (e.g., supports for V2X communication for pedestrian service identified by the PSID or ITS-AID).
  • a UE may also additionally broadcast that DRX synchronization is supported for one or more V2X services.
  • UEs that are interested in services advertised by a DRX sync UE establish a unicast connection using DRX synchronization information based on a UEs active V2X services.
  • a relay UE or DRX sync UE periodically broadcasts a DRX configuration to be used per service type for the pedestrian UE and the pedestrian UE may broadcast messages to other pedestrian UEs using the DRX configuration.
  • a DRX sync UE maintains the same DRX configuration for all UEs that are interested in services the DRX sync UE advertises and updates the DRX configuration to all UEs based on QoS requirements of each UE that has established a unicast connection with the DRX sync UE.
  • FIG. 9 is a network communications 900 diagram illustrating one embodiment of a DRX configuration via a relay UE (e.g., RSU).
  • the network communications 900 are made between a first UE 902 (e.g., pedestrian UE), a second UE 904 (e.g., pedestrian UE), and a relay UE 906 (e.g., DRX sync UE).
  • Each of the illustrated network communications 900 may include one or more messages.
  • the relay UE 906 acting as a DRX sync UE, advertises support for DRX synchronization for one or more V2X services via broadcast signaling to the first UE 902 and the second UE 904 .
  • the first UE 902 determines 912 , based on a ‘Destination Layer-2 ID’ of the first communication 908 , to establish a unicast connection with the PC5 based RSU.
  • the first UE 902 sends a direct communication request to the relay UE 906 including source user information, and/or V2X services requested (e.g., within V2X service information).
  • a security association is established between the first UE 902 and the relay UE 906 (e.g., RSU based PC5).
  • the first UE 902 provides its QoS requirements.
  • the first UE 902 may provide its current DRX configuration.
  • the relay UE 906 may determine a DRX configuration required and update the first UE 902 .
  • a fourth communication 918 transmitted from the relay UE 906 to the first UE 902 once the security association is complete the relay UE 906 sends a direct communication accept message.
  • the second UE 904 establishes 920 a unicast connection with the relay UE 906 via steps 912 through 918 .
  • the relay UE 906 determines 922 that DRX configuration has changed, the relay UE updates all UEs with the new DRX configuration for the services.
  • the relay UE 906 initiates transmission of a link modification request to all UEs that have a unicast connection and provides an updated DRX configuration (e.g., V2X service information, DRX information).
  • a link modification request e.g., V2X service information, DRX information.
  • the first UE 902 sends a link modification acknowledgement.
  • the UEs apply 928 , 930 the configured DRX for all V2X communication corresponding to the V2X services advertised by the relay UE 906 .
  • FIG. 10 is a flow chart diagram illustrating one embodiment of a method 1000 for discontinuous reception configuration parameters for communication.
  • the method 1000 is performed by an apparatus, such as the remote unit 102 .
  • 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.
  • the method 1000 includes receiving 1002 , at a first user equipment and over a first radio interface, discontinuous reception configuration parameters for communication over a second radio interface. In some embodiments, the method 1000 includes receiving 1004 quality of service requirements for transmission over the second radio interface. In certain embodiments, the method 1000 includes determining 1006 discontinuous reception communication parameters based on the discontinuous reception configuration parameters and based on the quality of service requirements. In various embodiments, the method 1000 includes transmitting 1008 and receiving communications over the second radio interface based on the discontinuous reception communication parameters.
  • receiving the discontinuous reception configuration parameters comprises receiving the discontinuous reception configuration parameters from a policy control function.
  • determining the discontinuous reception communication parameters based on the discontinuous reception configuration parameters and based on the quality of service requirements comprises determining an offset to the discontinuous reception configuration parameters to meet the quality of service requirements.
  • determining an offset is based on a mapping of an offset parameter to the quality of service requirements included within the discontinuous reception configuration parameters.
  • receiving the quality of service requirements for transmission over the second radio interface comprises receiving the quality of service requirements from a second user equipment.
  • determining the discontinuous reception communication parameters based on the discontinuous reception parameters comprises determining an active time and an inactive time.
  • the inactive time comprises a time in which the first user equipment is in a sleep state and does not transmit sidelink communication messages over the second radio interface and does not listen for sidelink communication messages over the second radio interface.
  • receiving the discontinuous reception configuration parameters comprises receiving a default discontinuous reception configuration.
  • the user equipment uses default discontinuous reception configuration parameters to fallback to a default discontinuous reception communication.
  • the default discontinuous reception configuration comprises a mapping of configuration per vehicle to everything service type.
  • the default discontinuous reception configuration comprises a mapping of discontinuous reception configuration parameters per quality of service requirement.
  • the default discontinuous reception configuration comprises a mapping of discontinuous reception configuration parameters per groupcast, broadcast, or unicast transmission over the second radio interface.
  • transmitting and receiving communications over the second radio interface comprises transmitting and receiving communications with the second user equipment via a PC5 interface.
  • transmissions over the first radio interface comprise communication with a mobile core network via a Uu interface.
  • FIG. 11 is a flow chart diagram illustrating one embodiment of a method 1100 for discontinuous reception configuration parameters for communication.
  • the method 1100 is performed by an apparatus, such as the network unit 104 .
  • 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.
  • the method 1100 includes receiving 1102 , at a policy control function and over a first radio interface, a policy association request for a corresponding user equipment.
  • the method 1100 includes obtaining 1104 a subscription profile for the user equipment.
  • the subscription profile includes a default discontinuous reception configuration for a second radio interface.
  • the method 1100 includes determining 1106 configuration information for communications over the second radio interface for the first user equipment.
  • the method 1100 includes transmitting 1108 the configuration information to the user equipment via non-access stratum control plane signaling over the first radio interface.
  • a method comprises: receiving, at a first user equipment and over a first radio interface, discontinuous reception configuration parameters for communication over a second radio interface; receiving quality of service requirements for transmission over the second radio interface; determining discontinuous reception communication parameters based on the discontinuous reception configuration parameters and based on the quality of service requirements; and transmitting and receiving communications over the second radio interface based on the discontinuous reception communication parameters.
  • receiving the discontinuous reception configuration parameters comprises receiving the discontinuous reception configuration parameters from a policy control function.
  • determining the discontinuous reception communication parameters based on the discontinuous reception configuration parameters and based on the quality of service requirements comprises determining an offset to the discontinuous reception configuration parameters to meet the quality of service requirements.
  • determining an offset is based on a mapping of an offset parameter to the quality of service requirements included within the discontinuous reception configuration parameters.
  • receiving the quality of service requirements for transmission over the second radio interface comprises receiving the quality of service requirements from a second user equipment.
  • determining the discontinuous reception communication parameters based on the discontinuous reception parameters comprises determining an active time and an inactive time.
  • the inactive time comprises a time in which the first user equipment is in a sleep state and does not transmit sidelink communication messages over the second radio interface and does not listen for sidelink communication messages over the second radio interface.
  • receiving the discontinuous reception configuration parameters comprises receiving a default discontinuous reception configuration.
  • the user equipment uses default discontinuous reception configuration parameters to fallback to a default discontinuous reception communication.
  • the default discontinuous reception configuration comprises a mapping of configuration per vehicle to everything service type.
  • the default discontinuous reception configuration comprises a mapping of discontinuous reception configuration parameters per quality of service requirement.
  • the default discontinuous reception configuration comprises a mapping of discontinuous reception configuration parameters per groupcast, broadcast, or unicast transmission over the second radio interface.
  • transmitting and receiving communications over the second radio interface comprises transmitting and receiving communications with the second user equipment via a PC5 interface.
  • transmissions over the first radio interface comprise communication with a mobile core network via a Uu interface.
  • an apparatus comprising a first use equipment.
  • the apparatus further comprises: a receiver that: receives, over a first radio interface, discontinuous reception configuration parameters for communication over a second radio interface; and receives quality of service requirements for transmission over the second radio interface; a processor that determines discontinuous reception communication parameters based on the discontinuous reception configuration parameters and based on the quality of service requirements; and a transmitter; wherein the transmitter transmits communications and the receiver receives communications over the second radio interface based on the discontinuous reception communication parameters.
  • the receiver receiving the discontinuous reception configuration parameters comprises the receiver receiving the discontinuous reception configuration parameters from a policy control function.
  • the processor determining the discontinuous reception communication parameters based on the discontinuous reception configuration parameters and based on the quality of service requirements comprises the processor determining an offset to the discontinuous reception configuration parameters to meet the quality of service requirements.
  • the processor determines an offset is based on a mapping of an offset parameter to the quality of service requirements included within the discontinuous reception configuration parameters.
  • the receiver receiving the quality of service requirements for transmission over the second radio interface comprises the receiver receiving the quality of service requirements from a second user equipment.
  • the processor determining the discontinuous reception communication parameters based on the discontinuous reception parameters comprises the processor determining an active time and an inactive time.
  • the inactive time comprises a time in which the first user equipment is in a sleep state and does not transmit sidelink communication messages over the second radio interface and does not listen for sidelink communication messages over the second radio interface.
  • the receiver receiving the discontinuous reception configuration parameters comprises the receiver receiving a default discontinuous reception configuration.
  • the user equipment uses default discontinuous reception configuration parameters to fallback to a default discontinuous reception communication.
  • the default discontinuous reception configuration comprises a mapping of configuration per vehicle to everything service type.
  • the default discontinuous reception configuration comprises a mapping of discontinuous reception configuration parameters per quality of service requirement.
  • the default discontinuous reception configuration comprises a mapping of discontinuous reception configuration parameters per groupcast, broadcast, or unicast transmission over the second radio interface.
  • the transmitter transmits communications and the receiver receives communications over the second radio interface the transmitter transmits communications and the receiver receives communications with the second user equipment via a PC5 interface.
  • transmissions over the first radio interface comprise communication with a mobile core network via a Uu interface.
  • a method comprises: receiving, at a policy control function and over a first radio interface, a policy association request for a corresponding user equipment; obtaining a subscription profile for the user equipment, wherein the subscription profile comprises a default discontinuous reception configuration for a second radio interface; determining configuration information for communications over the second radio interface for the first user equipment; and transmitting the configuration information to the user equipment via non-access stratum control plane signaling over the first radio interface.
  • an apparatus comprising a policy and control function.
  • the apparatus further comprises: a receiver that receives, over a first radio interface, a policy association request for a corresponding user equipment; a processor that: obtains a subscription profile for the user equipment, wherein the subscription profile comprises a default discontinuous reception configuration for a second radio interface; and determines configuration information for communications over the second radio interface for the first user equipment; and a transmitter that transmits the configuration information to the user equipment via non-access stratum control plane signaling over the first radio interface.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Databases & Information Systems (AREA)
  • Input Circuits Of Receivers And Coupling Of Receivers And Audio Equipment (AREA)
  • Measuring Pulse, Heart Rate, Blood Pressure Or Blood Flow (AREA)
US18/016,119 2020-07-13 2021-07-10 Discontinuous reception configuration parameters for communication Pending US20230276527A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/016,119 US20230276527A1 (en) 2020-07-13 2021-07-10 Discontinuous reception configuration parameters for communication

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US202063051233P 2020-07-13 2020-07-13
US202063051207P 2020-07-13 2020-07-13
US202063051184P 2020-07-13 2020-07-13
US202063051217P 2020-07-13 2020-07-13
PCT/IB2021/056211 WO2022013700A1 (en) 2020-07-13 2021-07-10 Discontinuous reception configuration parameters for communication
US18/016,119 US20230276527A1 (en) 2020-07-13 2021-07-10 Discontinuous reception configuration parameters for communication

Publications (1)

Publication Number Publication Date
US20230276527A1 true US20230276527A1 (en) 2023-08-31

Family

ID=76959021

Family Applications (4)

Application Number Title Priority Date Filing Date
US18/016,119 Pending US20230276527A1 (en) 2020-07-13 2021-07-10 Discontinuous reception configuration parameters for communication
US18/016,052 Pending US20230276364A1 (en) 2020-07-13 2021-07-10 Sidelink discontinuous reception configuration
US18/016,151 Pending US20230262738A1 (en) 2020-07-13 2021-07-10 Indication of a request for sidelink resources
US18/016,147 Pending US20230262601A1 (en) 2020-07-13 2021-07-12 Radio resource configuration for power saving

Family Applications After (3)

Application Number Title Priority Date Filing Date
US18/016,052 Pending US20230276364A1 (en) 2020-07-13 2021-07-10 Sidelink discontinuous reception configuration
US18/016,151 Pending US20230262738A1 (en) 2020-07-13 2021-07-10 Indication of a request for sidelink resources
US18/016,147 Pending US20230262601A1 (en) 2020-07-13 2021-07-12 Radio resource configuration for power saving

Country Status (10)

Country Link
US (4) US20230276527A1 (ko)
EP (4) EP4179795A2 (ko)
JP (2) JP2023534266A (ko)
KR (2) KR20230038199A (ko)
CN (4) CN115804240A (ko)
AU (1) AU2021307585A1 (ko)
BR (3) BR112023000651A2 (ko)
CA (2) CA3182835A1 (ko)
MX (2) MX2023000592A (ko)
WO (4) WO2022013700A1 (ko)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4133803A1 (en) * 2020-04-08 2023-02-15 IDAC Holdings, Inc. Nr v2x sidelink power saving for unicast and/or groupcast
WO2022077395A1 (zh) * 2020-10-15 2022-04-21 Oppo广东移动通信有限公司 侧行链路的传输方法和终端
WO2022086271A1 (ko) * 2020-10-22 2022-04-28 엘지전자 주식회사 Nr v2x에서 단말-간 조정 메시지를 송수신하는 방법 및 장치
US20220225297A1 (en) * 2021-01-13 2022-07-14 Qualcomm Incorporated Techniques for sidelink control signaling
US20220295408A1 (en) * 2021-03-15 2022-09-15 Qualcomm Incorporated Power saving in sidelink
US11889497B2 (en) * 2021-07-28 2024-01-30 Qualcomm Incorporated Scheduling sidelink communications
US11576122B1 (en) * 2021-08-05 2023-02-07 Qualcomm Incorporated Sidelink discontinuous reception (DRX) support indication and detection
US20230073478A1 (en) * 2021-09-06 2023-03-09 Qualcomm Incorporated Discontinuous reception (drx) configuration for sidelink communications by a user equipment (ue)
WO2024087762A1 (en) * 2023-07-24 2024-05-02 Lenovo (Beijing) Limited Sl wus resource (pre) configuration

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2641448A1 (en) * 2010-11-15 2013-09-25 BlackBerry Limited Managing communications across a wireless network
WO2016089294A1 (en) * 2014-12-02 2016-06-09 Telefonaktiebolaget Lm Ericsson (Publ) Wake-up for d2d communication
US10390303B2 (en) * 2016-05-24 2019-08-20 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatus for configuring a discontinuous reception mode in a wireless network
CN109479189B (zh) * 2016-07-21 2022-04-05 三星电子株式会社 设备到设备(d2d)通信中通过侧链路发现用户设备(ue)的***和方法
CN108307486A (zh) * 2016-08-11 2018-07-20 索尼公司 用于网络控制端和网络节点的电子设备和方法
WO2018175760A1 (en) * 2017-03-24 2018-09-27 Intel Corporation Wake up signal for machine type communication and narrowband-internet-of-things devices
WO2018199652A1 (ko) * 2017-04-26 2018-11-01 엘지전자 주식회사 무선 통신 시스템에서 wake up 신호를 수신하는 방법 및 장치
WO2020060890A1 (en) * 2018-09-17 2020-03-26 Apple Inc. Systems, methods, and devices for signaling for power saving
CN110574443B (zh) * 2019-07-29 2022-09-09 北京小米移动软件有限公司 直连通信方法、装置及存储介质

Also Published As

Publication number Publication date
JP2023535892A (ja) 2023-08-22
EP4179669A2 (en) 2023-05-17
CA3182840A1 (en) 2022-01-20
EP4179794A1 (en) 2023-05-17
US20230276364A1 (en) 2023-08-31
MX2023000592A (es) 2023-02-13
EP4179836A2 (en) 2023-05-17
AU2021307585A1 (en) 2023-03-09
JP2023534266A (ja) 2023-08-08
BR112023000610A2 (pt) 2023-01-31
WO2022013700A1 (en) 2022-01-20
CA3182835A1 (en) 2022-01-20
CN115769638A (zh) 2023-03-07
CN115769663A (zh) 2023-03-07
KR20230038192A (ko) 2023-03-17
US20230262738A1 (en) 2023-08-17
WO2022013699A3 (en) 2022-02-24
CN115804240A (zh) 2023-03-14
BR112023000651A2 (pt) 2023-01-31
WO2022013717A2 (en) 2022-01-20
WO2022013698A2 (en) 2022-01-20
BR112023000507A2 (pt) 2023-01-31
US20230262601A1 (en) 2023-08-17
MX2023000591A (es) 2023-02-13
KR20230038199A (ko) 2023-03-17
EP4179795A2 (en) 2023-05-17
WO2022013699A2 (en) 2022-01-20
CN115918007A (zh) 2023-04-04
WO2022013698A3 (en) 2022-02-24
WO2022013717A3 (en) 2022-02-24

Similar Documents

Publication Publication Date Title
US20230276527A1 (en) Discontinuous reception configuration parameters for communication
US20230156584A1 (en) Target network slice information for target network slices
WO2022184277A1 (en) Traffic communication pattern mapping
US20230299897A1 (en) Configuring a sidelink hybrid automatic repeat request
US20240147235A1 (en) Network slice admission control
US20240232708A1 (en) Model training using federated learning
WO2023061616A1 (en) Relaying data volume information
US20240147427A1 (en) Paging occasion monitoring
US20230276285A1 (en) Disabling analytics information of a network analytics function
US20240237089A1 (en) Allowing connectivity between a uav and a uav-c
WO2022178713A1 (en) Sidelink discontinuous reception configuration
US20230300729A1 (en) User equipment radio capabilities
WO2022208363A1 (en) Including a serving cell identity in a discovery message
WO2023078576A1 (en) Multi-access protocol data unit session access type usage
WO2023072419A1 (en) Communicating and storing aerial system security information
WO2022018587A1 (en) Radio resource control inactive state sidelink communications
WO2023057078A1 (en) Coordinating dual registration
WO2023156915A1 (en) Configuring quality of experience measurements
EP4381715A1 (en) Domain name system determination

Legal Events

Date Code Title Description
AS Assignment

Owner name: LENOVO (SINGAPORE) PTE. LTD., SINGAPORE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KARAMPATSIS, DIMITRIOS;GANESAN, KARTHIKEYAN;BASU MALLICK, PRATEEK;AND OTHERS;SIGNING DATES FROM 20230103 TO 20230202;REEL/FRAME:062620/0119

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION