[go: up one dir, main page]

WO2022041036A1 - Mise à jour de flux de trafic à l'aide d'un message de temps de cycle de réception discontinue - Google Patents

Mise à jour de flux de trafic à l'aide d'un message de temps de cycle de réception discontinue Download PDF

Info

Publication number
WO2022041036A1
WO2022041036A1 PCT/CN2020/111726 CN2020111726W WO2022041036A1 WO 2022041036 A1 WO2022041036 A1 WO 2022041036A1 CN 2020111726 W CN2020111726 W CN 2020111726W WO 2022041036 A1 WO2022041036 A1 WO 2022041036A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
pdb
drx
base station
cycle time
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.)
Ceased
Application number
PCT/CN2020/111726
Other languages
English (en)
Inventor
Nan Zhang
Yongjun XU
Wenkai YAO
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.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
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 Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2020/111726 priority Critical patent/WO2022041036A1/fr
Publication of WO2022041036A1 publication Critical patent/WO2022041036A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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
    • 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
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
    • 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 technology discussed below relates generally to wireless communication systems, and more particularly, to updating one or more traffic flows associated with a user equipment (UE) using a discontinuous reception (DRX) cycle time message.
  • UE user equipment
  • DRX discontinuous reception
  • a user equipment may utilize one or more resources on which to receive broadcast communications from the base station when the UE is in a discontinuous reception (DRX) idle mode.
  • DRX is a method used in mobile communication to conserve the battery of the UE.
  • the UE and the network negotiate phases in which data transfer occurs. During other times the UE turns its receiver off and enters a low power state, e.g., a DRX idle mode.
  • An improvement in DRX power saving usually leads to a potential increase in the packet delay.
  • Packet delay budget defines the upper limit of the delay experienced by a packet between the UE and a core network node, for example, when a UE is in a DRX idle mode.
  • a method for wireless communication by a base station includes receiving a message from a user equipment (UE) requesting a discontinuous reception (DRX) cycle time.
  • the method also includes generating DRX updating information based on the DRX cycle time.
  • the method further includes transmitting the DRX updating information to a core network node for updating one or more traffic flows associated with the UE.
  • the method includes receiving a packet delay budget (PDB) message from the core network node for the one or more traffic flows associated with the UE based on the DRX updating information.
  • PDB packet delay budget
  • a base station includes a transceiver for wirelessly communicating with a user equipment (UE) .
  • the base station also includes a memory.
  • the base station further includes a processor coupled to the transceiver and the memory.
  • the processor and the memory are configured to receive a message from the UE requesting a discontinuous reception (DRX) cycle time.
  • the processor and the memory are also configured to generate DRX updating information based on the DRX cycle time.
  • the processor and the memory are further configured to transmit the DRX updating information to a core network node for updating one or more traffic flows associated with the UE.
  • the processor and the memory are configured to receive a packet delay budget (PDB) message from the core network node for the one or more traffic flows associated with the UE based on the DRX updating information.
  • PDB packet delay budget
  • a non-transitory, processor-readable storage medium, having instructions stored thereon is disclosed.
  • the instructions When the instructions are executed by a processing circuit, the instructions cause the processing circuit to receive a message from a user equipment (UE) requesting a discontinuous reception (DRX) cycle time.
  • the instructions When the instructions are executed by a processing circuit, the instructions also cause the processing circuit to generate DRX updating information based on the DRX cycle time.
  • the instructions further cause the processing circuit to transmit the DRX updating information to a core network node for updating one or more traffic flows associated with the UE.
  • the instructions When the instructions are executed by a processing circuit, in addition, the instructions cause the processing circuit to receive a packet delay budget (PDB) message from the core network node for the one or more traffic flows associated with the UE based on the DRX updating information.
  • PDB packet delay budget
  • a base station includes a means for receiving a message from a user equipment (UE) requesting a discontinuous reception (DRX) cycle time.
  • the base station also includes a means for generating DRX updating information based on the DRX cycle time.
  • the base station further includes a means for transmitting the DRX updating information to a core network node for updating one or more traffic flows associated with the UE.
  • the base station includes a means for receiving a packet delay budget (PDB) message from the core network node for the one or more traffic flows associated with the UE based on the DRX updating information.
  • PDB packet delay budget
  • a method for wireless communication by a core network node includes receiving discontinuous reception (DRX) updating information from a base station.
  • the DRX updating information is based on a requested DRX cycle time for one or more traffic flows associated with a user equipment (UE) .
  • the method also includes generating a packet delay budget (PDB) message based on the DRX updating information.
  • the method further includes transmitting the PDB message to the base station for updating the one or more traffic flows associated with the UE.
  • DRX discontinuous reception
  • UE user equipment
  • PDB packet delay budget
  • a core network node includes a network interface.
  • the core network node also includes a memory.
  • the core network node further includes a processor coupled to the network interface and the memory.
  • the processor and the memory are configured to receive discontinuous reception (DRX) updating information from a base station.
  • the DRX updating information is based on a requested DRX cycle time for one or more traffic flows associated with a user equipment (UE) .
  • the processor and the memory are also configured to generate a packet delay budget (PDB) message based on the DRX updating information.
  • the processor and the memory are further configured to transmit the PDB message to the base station for updating the one or more traffic flows associated with the UE.
  • PDB packet delay budget
  • a non-transitory, processor-readable storage medium, having instructions stored thereon is disclosed.
  • the instructions When the instructions are executed by a processing circuit, the instructions cause the processing circuit to receive discontinuous reception (DRX) updating information from a base station.
  • the DRX updating information is based on a requested DRX cycle time for one or more traffic flows associated with a user equipment (UE) .
  • the instructions When the instructions are executed by a processing circuit, the instructions also cause the processing circuit to generate a packet delay budget (PDB) message based on the DRX updating information.
  • the instructions When the instructions are executed by a processing circuit, the instructions further cause the processing circuit to transmit the PDB message to the base station for updating the one or more traffic flows associated with the UE.
  • PDB packet delay budget
  • a core network node includes a means for receiving discontinuous reception (DRX) updating information from a base station.
  • the DRX updating information is based on a requested DRX cycle time for one or more traffic flows associated with a user equipment (UE) .
  • the core network node also includes a means for generating a packet delay budget (PDB) message based on the DRX updating information.
  • the core network node further includes a means for transmitting the PDB message to the base station for updating the one or more traffic flows associated with the UE.
  • PDB packet delay budget
  • a method for wireless communication by a user equipment includes transmitting a message to a base station.
  • the message requests a discontinuous reception (DRX) cycle time for one or more traffic flows associated with the UE.
  • the method also includes receiving a packet delay budget (PDB) message for the one or more traffic flow associated with the UE.
  • the PDB message is based on generated DRX updating information derived from the DRX cycle time.
  • a user equipment includes a transceiver for wirelessly communicating with a base station.
  • the UE also includes a memory.
  • the UE also includes a processor coupled to the transceiver and the memory.
  • the processor and the memory are configured to transmit a message to the base station.
  • the message requests a discontinuous reception (DRX) cycle time for one or more traffic flows associated with the UE.
  • the processor and the memory are also configured to receive a packet delay budget (PDB) message for the one or more traffic flow associated with the UE.
  • the PDB message is based on generated DRX updating information derived from the DRX cycle time.
  • a non-transitory, processor-readable storage medium, having instructions stored thereon is disclosed.
  • the instructions When the instructions are executed by a processing circuit, the instructions cause the processing circuit to transmit a message to a base station.
  • the message requests a discontinuous reception (DRX) cycle time for one or more traffic flows associated with the UE.
  • DRX discontinuous reception
  • a user equipment includes a means for transmitting a message to a base station.
  • the message requests a discontinuous reception (DRX) cycle time for one or more traffic flows associated with the UE.
  • the UE also includes a means for receiving a packet delay budget (PDB) message for the one or more traffic flow associated with the UE.
  • the PDB message is based on generated DRX updating information derived from the DRX cycle time.
  • FIG. 1 is a diagram illustrating an example of a wireless communication system.
  • FIG. 2 is a conceptual illustration of an example of a radio access network.
  • FIG. 3 is a block diagram illustrating an example of a 5G wireless communication system (5GS) .
  • FIG. 4 is a diagram illustrating an example of a frame structure for use in a radio access network according to some aspects
  • FIG. 5 is a conceptual illustration of an example wireless communication system for updating one or more traffic flows associated with a user equipment (UE) using a discontinuous reception (DRX) cycle time message in accordance with some aspects of the disclosure.
  • UE user equipment
  • DRX discontinuous reception
  • FIG. 6 is a block diagram conceptually illustrating an example hardware implementation for a base station in accordance with some aspects of the disclosure.
  • FIG. 7 is a flow chart illustrating an example method performed at a base station for updating one or more traffic flows associated with a UE using a DRX cycle time message in accordance with some aspects of the disclosure.
  • FIG. 8 is a block diagram conceptually illustrating an example hardware implementation for a core network node in accordance with some aspects of the disclosure.
  • FIG. 9 is a flow chart illustrating an example method performed at a core network node for updating one or more traffic flows associated with a UE using a DRX cycle time message in accordance with some aspects of the disclosure.
  • FIG. 10 is a block diagram conceptually illustrating an example hardware implementation for a UE in accordance with some aspects of the disclosure.
  • FIG. 11 is a flow chart illustrating an example method performed at a UE for updating one or more traffic flows associated with a UE using a DRX cycle time message in accordance with some aspects of the disclosure.
  • NG-RAN radio resource scheduling and UE local data transmission adaptive configurations e.g., audio/video bit rates
  • Implementations may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations.
  • devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described embodiments.
  • transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (for example, hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor (s) , interleaver, adders/summers, etc. ) .
  • innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, or the like of varying sizes, shapes, and constitution.
  • the various concepts presented throughout this disclosure may be implemented across a broad variety of telecommunication systems, network architectures, and communication standards.
  • the wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106.
  • the UE 106 may be enabled to carry out data communication with an external data network 110, such as (but not limited to) the Internet.
  • the RAN 104 may implement any suitable wireless communication technology or technologies to provide radio access to the UE 106.
  • the RAN 104 may operate according to 3rd Generation Partnership Project (3GPP) New Radio (NR) specifications, often referred to as 5G.
  • 3GPP 3rd Generation Partnership Project
  • NR New Radio
  • the RAN 104 may operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, often referred to as Long-Term Evolution (LTE) .
  • eUTRAN Evolved Universal Terrestrial Radio Access Network
  • LTE Long-Term Evolution
  • the 3GPP refers to this hybrid RAN as a next-generation RAN, or NG-RAN.
  • NG-RAN next-generation RAN
  • the RAN 104 includes a plurality of base stations 108 (e.g., a RAN entity, RAN node, or the like) .
  • a base station is a network element in a radio access network responsible for radio transmission and reception in one or more cells to or from a UE.
  • a base station may variously be referred to by those skilled in the art as a base transceiver station (BTS) , a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , an access point (AP) , a Node B (NB) , an eNode B (eNB) , a gNode B (gNB) , or some other suitable terminology.
  • BTS basic service set
  • ESS extended service set
  • AP access point
  • NB Node B
  • eNB eNode B
  • gNB gNode B
  • the radio access network 104 is further illustrated supporting wireless communication for multiple mobile apparatuses.
  • a mobile apparatus may be referred to as user equipment (UE) in 3GPP standards, but may also be referred to by those skilled in the art as a mobile station (MS) , a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT) , a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology.
  • a UE may be an apparatus that provides a user with access to network services.
  • a “mobile” apparatus need not necessarily have a capability to move and may be stationary.
  • the term mobile apparatus or mobile device broadly refers to a diverse array of devices and technologies.
  • UEs may include a number of hardware structural components sized, shaped, and arranged to help in communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. electrically coupled to each other.
  • a mobile apparatus examples include a mobile, a cellular (cell) phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal computer (PC) , a notebook, a netbook, a smartbook, a tablet, a personal digital assistant (PDA) , and a broad array of embedded systems, e.g., corresponding to an “Internet of Things” (IoT) .
  • IoT Internet of Things
  • a mobile apparatus may additionally be an automotive or other transportation vehicle, a remote sensor or actuator, a robot or robotics device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-copter, a quad-copter, a remote control device, a consumer and/or wearable device, such as eyewear, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., MP3 player) , a camera, a game console, etc.
  • GPS global positioning system
  • a mobile apparatus may additionally be a digital home or smart home device such as a home audio, video, and/or multimedia device, an appliance, a vending machine, intelligent lighting, a home security system, a smart meter, etc.
  • a mobile apparatus may additionally be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device controlling electric power (e.g., a smart grid) , lighting, water, etc.; an industrial automation and enterprise device; a logistics controller; agricultural equipment; military defense equipment, vehicles, aircraft, ships, and weaponry, etc.
  • a mobile apparatus may provide for connected medicine or telemedicine support, i.e., health care at a distance.
  • Telehealth devices may include telehealth monitoring devices and telehealth administration devices, whose communication may be given preferential treatment or prioritized access over other types of information, e.g., in terms of prioritized access for transport of critical service data, and/or relevant QoS for transport of critical service data.
  • Wireless communication between a RAN 104 and a UE 106 may be described as utilizing an air interface.
  • Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) may be referred to as downlink (DL) transmission.
  • DL downlink
  • the term downlink may refer to a point-to-multipoint transmission originating at a scheduling entity (described further below; e.g., base station 108) .
  • Another way to describe this scheme may be to use the term broadcast channel multiplexing.
  • Uplink Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as uplink (UL) transmissions.
  • UL uplink
  • the term uplink may refer to a point-to-point transmission originating at a scheduled entity (described further below; e.g., UE 106) .
  • a scheduling entity e.g., a base station 108 allocates resources for communication among some or all devices and equipment within its service area or cell.
  • the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, UEs 106, which may be scheduled entities, may utilize resources allocated by the scheduling entity 108.
  • Base stations 108 are not the only entities that may function as scheduling entities. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs) .
  • a scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities 106.
  • the scheduling entity 108 is a node or device responsible for scheduling traffic in a wireless communication network, including the downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108.
  • the scheduled entity 106 is a node or device that receives downlink control information 114, including but not limited to scheduling information (e.g., a grant) , synchronization or timing information, or other control information from another entity in the wireless communication network such as the scheduling entity 108.
  • the uplink and/or downlink control information and/or traffic information may be time-divided into frames, subframes, slots, and/or symbols.
  • a symbol may refer to a unit of time that, in an orthogonal frequency division multiplexed (OFDM) waveform, carries one resource element (RE) per sub-carrier.
  • a slot may carry 7 or 14 OFDM symbols.
  • a subframe may refer to a duration of 1ms. Multiple subframes or slots may be grouped together to form a single frame or radio frame.
  • OFDM orthogonal frequency division multiplexed
  • a slot may carry 7 or 14 OFDM symbols.
  • a subframe may refer to a duration of 1ms. Multiple subframes or slots may be grouped together to form a single frame or radio frame.
  • these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and various time divisions of the waveform may have any suitable duration.
  • base stations 108 may include a backhaul interface for communication with a backhaul portion 120 of the wireless communication system.
  • the backhaul 120 may provide a link between a base station 108 and the core network 102.
  • a backhaul network may provide interconnection between the respective base stations 108.
  • Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, or the like using any suitable transport network.
  • the core network 102 may be a part of the wireless communication system 100, and may be independent of the radio access technology used in the RAN 104.
  • the core network 102 may be configured according to 5G standards (e.g., 5GC) .
  • the core network 102 may be configured according to a 4G evolved packet core (EPC) , or any other suitable standard or configuration.
  • 5G standards e.g., 5GC
  • EPC 4G evolved packet core
  • the 5GS 200 may be the same wireless communication system 100 described above and illustrated in FIG. 1.
  • the 5GS 200 includes a user equipment (UE) 202, a NR-RAN 204, and a core network 206.
  • the UE 202 may be enabled to carry out data communication with an external data network 214, such as (but not limited to) the Internet or an Ethernet network.
  • the core network 206 may include, for example, an access and mobility management function (AMF) 208, a session management function (SMF) 210, and a user plane function (UPF) 212.
  • the AMF 208 and SMF 210 employ control plane (e.g., Non Access Stratum (NAS) ) signaling to perform various functions related to mobility management and session management for the UE 202.
  • control plane e.g., Non Access Stratum (NAS)
  • NAS Non Access Stratum
  • the AMF 208 provides connectivity, mobility management and authentication of the UE 202
  • the SMF 210 provides session management of the UE 202 (e.g., processes signaling related to protocol data unit (PDU) sessions between the UE 202 and the external DN 214) .
  • the UPF 212 provides user plane connectivity to route 5G (NR) packets to/from the UE 202 via the NR-RAN 204.
  • NR 5G
  • the core network 206 may further include other functions, such as a policy control function (PCF) 216, authentication server function (AUSF) 218, unified data management (UDM) 220, network slice selection function (NSSF) 222, and other functions (not illustrated, for simplicity) .
  • the PCF 216 provides policy information (e.g., rules) for control plane functions, such as network slicing, roaming, and mobility management.
  • policy information e.g., rules
  • control plane functions such as network slicing, roaming, and mobility management.
  • QoS 5G quality of service
  • the AUSF 218 performs authentication of UEs 202.
  • the UDM 220 facilitates generation of authentication and key agreement (AKA) credentials, performs user identification and manages subscription information and UE context.
  • AKA authentication and key agreement
  • the NSSF 222 redirects traffic to a network slice.
  • Network slices may be defined, for example, for different classes of subscribers or use cases, such as smart home, Internet of Things (IoT) , connected car, smart energy grid, etc.
  • IoT Internet of Things
  • Each use case may receive a unique set of optimized resources and network topology (e.g., a network slice) to meet the connectivity, speed, power, and capacity requirements of the use case.
  • the UE 202 may transmit a registration request and PDU session establishment request to the 5G core network 206 via the NR-RAN 204.
  • the AMF 208 and SMF 210 may process the registration request and PDU session establishment request and establish a data network session (DNS) between the UE 202 and the external DN 214 via the UPF 212.
  • DNS may include one or more sessions (e.g., data sessions or data flows) and may be served by multiple UPFs 212 (only one of which is shown for convenience) . Examples of data flows include, but are not limited to, IP flows, Ethernet flows and unstructured data flows.
  • the RAN 300 may be the same as the RAN 104 described above and illustrated in FIG. 1 and/or the NR-RAN 204 described above and illustrated in FIG. 2.
  • the geographic area covered by the RAN 300 may be divided into cellular regions (cells) that can be uniquely identified by a user equipment (UE) based on an identification broadcasted from one access point or base station.
  • FIG. 3 illustrates macrocells 302, 304, and 306, and a small cell 308, each of which may include one or more sectors (not shown) .
  • a sector is a sub-area of a cell. All sectors within one cell are served by the same base station.
  • a radio link within a sector can be identified by a single logical identification belonging to that sector.
  • the multiple sectors within a cell can be formed by groups of antennas with each antenna responsible for communication with UEs in a portion of the cell.
  • FIG. 3 two base stations 310 and 312 are shown in cells 302 and 304; and a third base station 314 is shown controlling a remote radio head (RRH) 316 in cell 306. That is, a base station can have an integrated antenna or can be connected to an antenna or RRH by feeder cables.
  • the cells 302, 304, and 306 may be referred to as macrocells, as the base stations 310, 312, and 314 support cells having a large size.
  • a base station 318 is shown in the small cell 308 (e.g., a microcell, picocell, femtocell, home base station, home Node B, home eNode B, etc.
  • the cell 308 may be referred to as a small cell, as the base station 318 supports a cell having a relatively small size.
  • Cell sizing can be done according to system design as well as component constraints.
  • the radio access network 300 may include any number of wireless base stations and cells. Further, a relay node may be deployed to extend the size or coverage area of a given cell.
  • the base stations 310, 312, 314, 318 provide wireless access points to a core network for any number of mobile apparatuses. In some examples, the base stations 310, 312, 314, and/or 318 may be the same as the base station/scheduling entity 108 described above and illustrated in FIG. 1.
  • the cells may include UEs that may be in communication with one or more sectors of each cell.
  • each base station 310, 312, 314, and 318 may be configured to provide an access point to a core network (e.g., as illustrated in FIG. 1 and/or 2) for all the UEs in the respective cells.
  • UEs 322 and 324 may be in communication with base station 310;
  • UEs 326 and 328 may be in communication with base station 412;
  • UEs 330 and 332 may be in communication with base station 314 by way of RRH 316; and
  • UE 334 may be in communication with base station 318.
  • the UEs 322, 324, 326, 328, 330, 332, 334, 338, 340, and/or 342 may be the same as the UE/scheduled entity 106 described above and illustrated in FIG. 1 and/or the UE 202 described above and illustrated in FIG. 2.
  • an unmanned aerial vehicle (UAV) 320 which may be a drone or quadcopter, can be a mobile network node and may be configured to function as a UE.
  • the UAV 320 may operate within cell 302 by communicating with base station 310.
  • the ability for a UE to communicate while moving, independent of its location, is referred to as mobility.
  • the various physical channels between the UE and the radio access network are generally set up, maintained, and released under the control of the AMF 208, illustrated in FIG. 2.
  • a RAN 300 may utilize DL-based mobility or UL-based mobility to enable mobility and handovers (i.e., the transfer of a UE’s connection from one radio channel to another) .
  • a UE may monitor various parameters of the signal from its serving cell as well as various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more of the neighboring cells.
  • the UE may undertake a handoff or handover from the serving cell to the neighboring (target) cell.
  • UE 324 illustrated as a vehicle, although any suitable form of UE may be used
  • the UE 324 may transmit a reporting message to its serving base station 310 indicating this condition.
  • the UE 324 may receive a handover command, and the UE may undergo a handover to the cell 306.
  • UL reference signals from each UE may be utilized by the network to select a serving cell for each UE.
  • the base stations 310, 312, and 314/316 may broadcast unified synchronization signals (e.g., unified Primary Synchronization Signals (PSSs) , unified Secondary Synchronization Signals (SSSs) and unified Physical Broadcast Channels (PBCH) ) .
  • PSSs Primary Synchronization Signals
  • SSSs unified Secondary Synchronization Signals
  • PBCH Physical Broadcast Channels
  • the UEs 322, 324, 326, 328, 330, and 332 may receive the unified synchronization signals, derive the carrier frequency and slot timing from the synchronization signals, and in response to deriving timing, transmit an uplink pilot or reference signal.
  • the uplink pilot signal transmitted by a UE may be concurrently received by two or more cells (e.g., base stations 310 and 314/316) within the radio access network 300.
  • Each of the cells may measure a strength of the pilot signal, and the radio access network (e.g., one or more of the base stations 310 and 314/316 and/or a central node within the core network) may determine a serving cell for the UE 324.
  • the radio access network e.g., one or more of the base stations 310 and 314/316 and/or a central node within the core network
  • the network may continue to monitor the uplink pilot signal transmitted by the UE 324.
  • the network 300 may handover the UE 324 from the serving cell to the neighboring cell, with or without informing the UE 324.
  • the synchronization signal transmitted by the base stations 310, 312, and 314/316 may be unified, the synchronization signal may not identify a particular cell, but rather may identify a zone of multiple cells operating on the same frequency and/or with the same timing.
  • the use of zones in 5G networks or other next generation communication networks enables the uplink-based mobility framework and improves the efficiency of both the UE and the network, since the number of mobility messages that need to be exchanged between the UE and the network may be reduced.
  • the air interface in the radio access network 300 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum.
  • Licensed spectrum provides for exclusive use of a portion of the spectrum, generally by virtue of a mobile network operator purchasing a license from a government regulatory body.
  • Unlicensed spectrum provides for shared use of a portion of the spectrum without need for a government-granted license. While compliance with some technical rules is generally still required to access unlicensed spectrum, generally, any operator or device may gain access.
  • Shared spectrum may fall between licensed and unlicensed spectrum, wherein technical rules or limitations may be required to access the spectrum, but the spectrum may still be shared by multiple operators and/or multiple RATs.
  • the holder of a license for a portion of licensed spectrum may provide licensed shared access (LSA) to share that spectrum with other parties, e.g., with suitable licensee-determined conditions to gain access.
  • LSA licensed shared access
  • the air interface in the radio access network 300 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of the various devices.
  • 5G NR specifications provide multiple access for UL transmissions from UEs 322 and 324 to base station 310, and for multiplexing for DL transmissions from base station 310 to one or more UEs 322 and 324, utilizing orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) .
  • OFDM orthogonal frequency division multiplexing
  • CP cyclic prefix
  • 5G NR specifications provide support for discrete Fourier transform-spread-OFDM (DFT-s-OFDM) with a CP (also referred to as single-carrier FDMA (SC-FDMA) ) .
  • DFT-s-OFDM discrete Fourier transform-spread-OFDM
  • SC-FDMA single-carrier FDMA
  • multiplexing and multiple access are not limited to the above schemes, and may be provided utilizing time division multiple access (TDMA) , code division multiple access (CDMA) , frequency division multiple access (FDMA) , sparse code multiple access (SCMA) , resource spread multiple access (RSMA) , or other suitable multiple access schemes.
  • multiplexing DL transmissions from the base station 310 to UEs 322 and 324 may be provided utilizing time division multiplexing (TDM) , code division multiplexing (CDM) , frequency division multiplexing (FDM) , orthogonal frequency division multiplexing (OFDM) , sparse code multiplexing (SCM) , or other suitable multiplexing schemes.
  • the air interface in the radio access network 300 may further utilize one or more duplexing algorithms.
  • Duplex refers to a point-to-point communication link where both endpoints can communicate with one another in both directions.
  • Full duplex means both endpoints can simultaneously communicate with one another.
  • Half duplex means only one endpoint can send information to the other at a time.
  • a full duplex channel generally relies on physical isolation of a transmitter and receiver, and suitable interference cancellation technologies.
  • Full duplex emulation is frequently implemented for wireless links by utilizing frequency division duplex (FDD) or time division duplex (TDD) .
  • FDD frequency division duplex
  • TDD time division duplex
  • transmissions in different directions operate at different carrier frequencies.
  • TDD transmissions in different directions on a given channel are separated from one another using time division multiplexing. That is, at some times the channel is dedicated for transmissions in one direction, while at other times the channel is dedicated for transmissions in the other direction, where the direction may change very rapidly, e.g.,
  • FIG. 4 an expanded view of an exemplary DL subframe 402 is illustrated, showing an OFDM resource grid.
  • time is in the horizontal direction with units of OFDM symbols; and frequency is in the vertical direction with units of subcarriers.
  • the resource grid 404 may be used to schematically represent time–frequency resources for a given antenna port. That is, in a multiple-input-multiple-output (MIMO) implementation with multiple antenna ports available, a corresponding multiple number of resource grids 404 may be available for communication.
  • the resource grid 404 is divided into multiple resource elements (REs) 406.
  • An RE which is 1 subcarrier ⁇ 1 symbol, is the smallest discrete part of the time–frequency grid, and contains a single complex value representing data from a physical channel or signal.
  • each RE may represent one or more bits of information.
  • a block of REs may be referred to as a physical resource block (PRB) or a resource block (RB) 408, which contains any suitable number of consecutive subcarriers in the frequency domain.
  • an RB may include 12 subcarriers, a number independent of the numerology used.
  • an RB may include any suitable number of consecutive OFDM symbols in the time domain.
  • Scheduling of UEs typically involves scheduling one or more resource elements 406 within one or more sub-bands.
  • a UE generally utilizes only a subset of the resource grid 404.
  • an RB may be the smallest unit of resources that can be allocated to a UE.
  • the RB 408 is shown as occupying less than the entire bandwidth of the subframe 402, with some subcarriers illustrated above and below the RB 408.
  • the subframe 402 may have a bandwidth corresponding to any number of one or more RBs 408.
  • the RB 408 is shown as occupying less than the entire duration of the subframe 402, although this is merely one possible example.
  • Each 1 ms subframe 402 may consist of one or multiple adjacent slots.
  • one subframe 402 includes four slots 410, as an illustrative example.
  • a slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length.
  • CP cyclic prefix
  • a slot may include 7 or 14 OFDM symbols with a nominal CP.
  • Additional examples may include mini-slots, sometimes referred to as shortened transmission time intervals (TTIs) , having a shorter duration (e.g., one to three OFDM symbols) .
  • TTIs shortened transmission time intervals
  • These mini-slots or shortened transmission time intervals (TTIs) may in some cases be transmitted occupying resources scheduled for ongoing slot transmissions for the same or for different UEs. Any number of resource blocks may be utilized within a subframe or slot.
  • An expanded view of one of the slots 410 illustrates the slot 410 including a control region 412 and a data region 414.
  • the control region 412 may carry control channels
  • the data region 414 may carry data channels.
  • a slot may contain all DL, all UL, or at least one DL portion and at least one UL portion.
  • the structure illustrated in FIG. 4 is merely exemplary in nature, and different slot structures may be utilized, and may include one or more of each of the control region (s) and data region (s) .
  • the slot 410 may be utilized for broadcast or unicast communication.
  • a broadcast, multicast, or groupcast communication may refer to a point-to-multipoint transmission by one device (e.g., a base station, UE, or other similar device) to other devices.
  • a broadcast communication is delivered to all devices, whereas a multicast communication is delivered to multiple intended recipient devices.
  • a unicast communication may refer to a point-to-point transmission by a one device to a single other device.
  • the scheduling entity may allocate one or more REs 406 (e.g., within the control region 412) to carry DL control information including one or more DL control channels, such as a physical downlink control channel (PDCCH) , to one or more scheduled entities (e.g., UEs) .
  • the PDCCH carries downlink control information (DCI) including but not limited to power control commands (e.g., one or more open loop power control parameters and/or one or more closed loop power control parameters) , scheduling information, a grant, and/or an assignment of REs for DL and UL transmissions.
  • DCI downlink control information
  • the PDCCH may further carry HARQ feedback transmissions such as an acknowledgment (ACK) or negative acknowledgment (NACK) .
  • HARQ is a technique well-known to those of ordinary skill in the art, wherein the integrity of packet transmissions may be checked at the receiving side for accuracy, e.g., utilizing any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC) . If the integrity of the transmission is confirmed, an ACK may be transmitted, whereas if not confirmed, a NACK may be transmitted. In response to a NACK, the transmitting device may send a HARQ retransmission, which may implement chase combining, incremental redundancy, etc.
  • the base station may further allocate one or more REs 406 (e.g., in the control region 412 or the data region 414) to carry other DL signals, such as a demodulation reference signal (DMRS) ; a phase-tracking reference signal (PT-RS) ; a channel state information (CSI) reference signal (CSI-RS) ; a primary synchronization signal (PSS) ; and a secondary synchronization signal (SSS) .
  • DMRS demodulation reference signal
  • PT-RS phase-tracking reference signal
  • CSI-RS channel state information reference signal
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • a UE may utilize the PSS and SSS to achieve radio frame, subframe, slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identity (PCI) of the cell.
  • PCI physical cell identity
  • the synchronization signals PSS and SSS may be transmitted in a synchronization signal block (SSB) .
  • the PBCH may further include a master information block (MIB) that includes various system information, along with parameters for decoding a system information block (SIB) .
  • the SIB may be, for example, a SystemInformationType 1 (SIB1) that may include various additional system information.
  • system information transmitted in the MIB may include, but are not limited to, a subcarrier spacing, system frame number, a configuration of a PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0) , and a search space for SIB1.
  • Examples of additional system information transmitted in the SIB1 may include, but are not limited to, a random access search space, downlink configuration information, and uplink configuration information.
  • the MIB and SIB1 together provide the minimum system information (SI) for initial access.
  • the scheduled entity may utilize one or more REs 406 to carry UL control information (UCI) including one or more UL control channels, such as a physical uplink control channel (PUCCH) , to the scheduling entity.
  • UCI may include a variety of packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions.
  • uplink reference signals may include a sounding reference signal (SRS) and an uplink DMRS.
  • the UCI may include a scheduling request (SR) , i.e., request for the scheduling entity to schedule uplink transmissions.
  • SR scheduling request
  • the scheduling entity may transmit downlink control information (DCI) that may schedule resources for uplink packet transmissions.
  • DCI may also include HARQ feedback, channel state feedback (CSF) , such as a CSI report, or any other suitable UCI.
  • CSF channel state feedback
  • one or more REs 406 may be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, such as, for a DL transmission, a physical downlink shared channel (PDSCH) ; or for an UL transmission, a physical uplink shared channel (PUSCH) .
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • one or more REs 406 within the data region 314 may be configured to carry other signals, such as one or more SIBs and DMRSs.
  • the control region 412 of the slot 410 may include a physical sidelink control channel (PSCCH) including sidelink control information (SCI) transmitted by an initiating (transmitting) sidelink device (e.g., V2X or other sidelink device) towards a set of one or more other receiving sidelink devices.
  • the data region 414 of the slot 410 may include a physical sidelink shared channel (PSSCH) including sidelink data traffic transmitted by the initiating (transmitting) sidelink device within resources reserved over the sidelink carrier by the transmitting sidelink device via the SCI.
  • PSSCH physical sidelink shared channel
  • Other information may further be transmitted over various REs 406 within slot 410.
  • HARQ feedback information may be transmitted in a physical sidelink feedback channel (PSFCH) within the slot 410 from the receiving sidelink device to the transmitting sidelink device.
  • PSFCH physical sidelink feedback channel
  • one or more reference signals such as a sidelink SSB and/or a sidelink CSI-RS, may be transmitted within the slot 410.
  • Transport channels carry blocks of information called transport blocks (TB) .
  • TBS transport block size
  • MCS modulation and coding scheme
  • channels or carriers described herein are not necessarily all of the channels or carriers that may be utilized between a scheduling entity and scheduled entities, and those of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those illustrated, such as other traffic, control, and feedback channels.
  • a user equipment may utilize one or more resources on which to receive broadcast communications from the base station when the UE is in a discontinuous reception (DRX) idle mode.
  • DRX is a method used in mobile communication to conserve the battery of the UE.
  • the UE and the network negotiate phases in which data transfer occurs. During other times the UE turns its receiver off and enters a low power state, e.g., a DRX idle mode.
  • An improvement in DRX power saving usually leads to a potential increase in the packet delay.
  • Packet delay budget defines the upper limit of the delay experienced by a packet between the UE and a core network node, for example, when a UE is in a DRX idle mode.
  • packet delay budget (PDB) message may be used to control 5GC and NG-RAN packet transmission delay.
  • 5GC packet delay may be predicted and, in NR, 1ms may be sufficient to cover the delay by the 5GC allowing the NG-RAN to use the 1ms parameter to schedule radio resources.
  • the 5GC may determine a PDB value of 1ms and transmit that PDB value to the NG-RAN.
  • RRC radio resource control
  • DBR delay budget report
  • the UE may request a C-DRX cycle change from the UE to the NG-RAN, for example, when the UE is entering into a DRX idle mode.
  • the NG-RAN may provide the UE with a new C-DRX cycle after receiving the message.
  • the PDB message and the DBR message may be separate requests from the 5GC and the UE.
  • the PDB message is not provided to the UE and the DBR message is not provide to the 5GC.
  • the UE may not be aware of the DBR message and the 5GC may not be aware of the PDB message.
  • the C-DRX cycle and PDB value may not be aligned resulting in suboptimal NG-RAN radio resource scheduling and suboptimal UE data transmission adaptive configuration (e.g., audio/video rates) .
  • a UE may generate a message requesting a discontinuous reception (DRX) cycle time for one or more traffic flows associated with the UE.
  • the UE may transmit the message to the base station and the base station may generate DRX updating information based on the DRX cycle time provided in the message.
  • the base station may transmit the DRX updating information to a core network node (e.g., a user plane function) and the core network node may generate a packet delay budget (PDB) message containing a PDB value based on the DRX updating information.
  • PDB packet delay budget
  • the core network node may set the PDB value to be equal to the DRX cycle time.
  • the core network node may transmit the PDB message to the base station for updating the one or more traffic flows associated with the UE.
  • the base station may transmit the PDB message to the UE for updating the one or more traffic flows associated with the UE.
  • the UE may update one or more traffic flows based on the PDB message. For example, the UE may update both the first cycle time of the first traffic flow and the second cycle time of the second traffic flow according to the PDB value.
  • the base station may schedule one or more radio resources based on the PDB message.
  • the UE and the base station may communication with each other using the one or more radio resources.
  • FIG. 5 is a conceptual illustration of an example wireless communication system 500 for updating one or more traffic flows associated with a user equipment (UE) using a discontinuous reception (DRX) cycle time message in accordance with some aspects of the disclosure.
  • the wireless communication system 500 includes a user equipment (UE) 502, a base station 504, and a core network node 506.
  • the UE 502 may correspond, for example, to any of the UEs or scheduled entities illustrated in FIGs. 1, 2, and/or 3.
  • the base station 504 may correspond, for example, to any of the base stations (e.g., gNB, eNB, etc. ) or scheduling entities illustrated in FIGs. 1, 2, and/or 3.
  • the core network node 506 may include a user plane function UPF, such as UPF 212 illustrated in FIG. 2.
  • the UE 502 may generate a message requesting a discontinuous reception (DRX) cycle time for one or more traffic flows associated with the UE 502.
  • the UE 502 may be utilizing a first traffic flow with a first cycle time of 100ms and a second traffic flow with a second cycle time of 20ms.
  • the UE 502 may determine to utilize a DRX cycle time of 50ms.
  • the UE 502 may generate a message requesting a DRX cycle time of 50ms to update the first cycle time and the second cycle time to a cycle time of 50ms.
  • the one or more traffic flows associated with the UE 502 include one or more Quality of Service (QoS) flows associated with the UE 502.
  • QoS Quality of Service
  • the UE 502 may transmit the message to the base station 504. For example, after generating the message requesting the DRX cycle time for the first traffic flow and the second traffic flow, the UE 502 may transmit the message to the base station 504 for updating the first traffic flow and the second traffic flow according to the DRX cycle time.
  • the message may include a radio resource control (RRC) delay budget report (DBR) message.
  • RRC radio resource control
  • DBR delay budget report
  • the base station 504 may generate DRX updating information based on the DRX cycle time. For example, the UE 502 may transmit the message requesting a DRX cycle time for one or more traffic flows associated with the UE 502. In response to receiving the message, the base station 504 may generate DRX updating information based on the DRX cycle time requested by the UE 502. In some aspects, the base station 504 may generate DRX updating information based on the DRX cycle time for the first traffic flow and the second traffic flow.
  • the base station 504 may transmit the DRX updating information to the core network node 506. For example, after generating the DRX updating information based on the DRX cycle time requested by the UE 502, the base station 504 may transmit the DRX updating information to the core network node 506. In some aspects, the DRX updating information may be used to update a cycle time for the first traffic flow and the second traffic flow.
  • the core network node 506 may generate a packet delay budget (PDB) message based on the DRX updating information.
  • generating the PDB message based on the DRX updating information may include setting a PDB value equal to the requested DRX cycle time.
  • a UE may request a DRX cycle time of 50ms.
  • the core network node 506 may set a PDB value to 50ms so that the PDB value is equal to the requested DRX cycle time.
  • the core network node 506 may transmit the PDB message to the base station 504 for updating the one or more traffic flows associated with the UE 502. For example, after generating the PDB message based on the DRX updating information, the core network node 506 may transmit the PDB message to the base station for updating the first cycle time of the first traffic flow and the second cycle time of the second traffic flow according to the PDB value provided in the PDB message.
  • the base station 504 may transmit the PDB message to the UE 502 for updating the one or more traffic flows associated with the UE 502. For example, after receiving the PDB message from the core network node 506, the base station 504 may transmit the PDB message to the UE for updating the first cycle time of the first traffic flow and the second cycle time of the second traffic flow according to the PDB value provided in the PDB message.
  • the UE 502 may update one or more traffic flows based on the PDB message. In some aspects, the UE 502 may update both the first cycle time of the first traffic flow and the second cycle time of the second traffic flow according to the PDB value.
  • the UE 502 may update both the first cycle time of the first traffic flow and the second cycle time of the second traffic flow according to the PDB value so that the first cycle time and the second cycle time are both 50ms.
  • the base station 504 may schedule one or more radio resources for communication with the UE 502 based on the PDB message.
  • the UE 502 and the base station 504 may communicate with each other using the one or more radio resources.
  • system 500 including the UE 502, the base station 504, and the core network node 506 may implement any one or more procedures described herein in addition to the procedure described herein with respect to FIG. 5.
  • the system 500 including the UE 502, the base station 504, and the core network node 506 may implement any one or more procedures described herein with respect to any one or more of FIGS. 1-4 and 6-11.
  • FIG. 6 is a block diagram conceptually illustrating an example hardware implementation for a base station 600 in accordance with some aspects of the disclosure.
  • the base station 600 may be a base station (e.g., gNB or eNB) , RAN entity, or other scheduling entity as illustrated in any one or more of FIGS. 1-5.
  • the base station 600 may be implemented with a processing system 614 that includes one or more processors 604.
  • processors 604 include microprocessors, microcontrollers, digital signal processors (DSPs) , field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • DSPs digital signal processors
  • FPGAs field programmable gate arrays
  • PLDs programmable logic devices
  • state machines gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • the base station 600 may be configured to perform any one or more of the functions described herein. That is, the processor 604, as utilized in the base station 600, may be used to implement any one or more of the processes and procedures described and illustrated in FIGS. 5 and 7-11.
  • the processing system 614 may be implemented with a bus architecture, represented generally by the bus 602.
  • the bus 602 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 614 and the overall design constraints.
  • the bus 602 communicatively couples together various circuits including one or more processors (represented generally by the processor 604) , a memory 605, and computer-readable media (represented generally by the computer-readable medium 606) .
  • the bus 602 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.
  • a bus interface 608 provides an interface between the bus 602 and a transceiver 610.
  • the transceiver 610 may provide a communication interface or means for wirelessly communicating with various other apparatus over a transmission medium.
  • a user interface 612 for example, keypad, display, speaker, microphone, joystick
  • a user interface 612 is optional, and may be omitted in some examples.
  • the processor 604 is responsible for managing the bus 602 and general processing, including the execution of software stored on the computer-readable medium 606.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the software when executed by the processor 604, causes the processing system 614 to perform the various functions described below for any particular apparatus.
  • the computer-readable medium 606 and the memory 605 may also be used for storing data that is manipulated by the processor 604 when executing software.
  • the computer-readable medium 606 may be a non-transitory computer-readable medium.
  • a non-transitory computer-readable medium includes, by way of example, a magnetic storage device (for example, hard disk, floppy disk, magnetic strip) , an optical disk (for example, a compact disc (CD) or a digital versatile disc (DVD) ) , a smart card, a flash memory device (for example, a card, a stick, or a key drive) , a random access memory (RAM) , a read only memory (ROM) , a programmable ROM (PROM) , an erasable PROM (EPROM) , an electrically erasable PROM (EEPROM) , a register, a removable disk, and any other suitable medium for storing software or instructions that may be accessed and read by a computer.
  • a magnetic storage device for example, hard disk, floppy disk, magnetic strip
  • an optical disk for example, a compact disc (CD) or a digital versatile disc
  • the computer-readable medium 606 may reside in the processing system 614, external to the processing system 614, or distributed across multiple entities including the processing system 614.
  • the computer-readable medium 606 may be embodied in a computer program product.
  • a computer program product may include a computer-readable medium in packaging materials.
  • the processor 604 may include circuitry configured for various functions.
  • the processor 604 may include a receiving circuit 640 configured to perform various functions, including, for example, receiving a message from a UE requesting a DRX cycle time.
  • the receiving circuit 640 may also be configured to perform various functions, including, for example, receiving a packet delay budget (PDB) message from a core network node for the one or more traffic flows associated with the UE based on DRX updating information.
  • the receiving circuit 640 may further be configured to execute receiving instructions 650 (receiving software) stored in the computer-readable medium 606 to implement one or more of the functions described herein.
  • the processor 604 may include a generating circuit 642 configured to perform various functions, including, for example, generating DRX updating information based on the DRX cycle time.
  • the generating circuit 642 may further be configured to execute generating instructions 652 (generating software) stored in the computer-readable medium 606 to implement one or more of the functions described herein.
  • the processor 604 may include a transmitting circuit 644 configured to perform various functions, including, for example, transmitting DRX updating information to a core network node for updating one or more traffic flows associated with the UE.
  • the transmitting circuit 644 may also be configured to perform various functions, including, for example, transmitting the PDB message to the UE for updating the one or more traffic flows.
  • the transmitting circuit 644 may further be configured to execute transmitting instructions 654 (transmitting software) stored in the computer-readable medium 606 to implement one or more of the functions described herein.
  • the processor 604 may include a scheduling circuit 646 configured to perform various functions, including, for example, scheduling one or more radio resources based on the PDB message (e.g., according to the PDB value) .
  • the scheduling circuit 646 may further be configured to execute scheduling instructions 654 (scheduling software) stored in the computer-readable medium 606 to implement one or more of the functions described herein.
  • circuitry included in the processor 604 is merely provided as an example, and other means for carrying out the described functions may be included within various aspects of the present disclosure, including but not limited to the instructions stored in the computer-readable storage medium 606, or any other suitable apparatus or means described in any one of the FIGS. 1-5 and 7-11 and utilizing, for example, the processes or algorithms described herein.
  • FIG. 7 is a flow chart illustrating an example method 700 performed at a base station for updating one or more traffic flows associated with a user equipment (UE) using a discontinuous reception (DRX) cycle time message in accordance with some aspects of the disclosure.
  • UE user equipment
  • DRX discontinuous reception
  • the method may be performed by the base station 600, as described above and illustrated in FIG. 6, by a processor or processing system, or by any suitable means for carrying out the described functions.
  • the base station may receive a message from a UE requesting a DRX cycle time. For example, after generating the message requesting the DRX cycle time for one or more traffic flows (e.g., a first traffic flow and a second traffic flow) , a base station may receive a message from a UE for updating the one or more traffic flows according to the DRX cycle time.
  • the message may include a radio resource control (RRC) delay budget report (DBR) message.
  • RRC radio resource control
  • DBR delay budget report
  • the base station may generate DRX updating information based on the DRX cycle time. For example, the base station may receive the message requesting a DRX cycle time for one or more traffic flows associated with the UE. In response to receiving the message, the base station may generate DRX updating information based on the DRX cycle time requested by the UE. In some aspects, the base station may generate DRX updating information based on the DRX cycle time for the first cycle traffic flow and the second cycle traffic flow.
  • the base station may transmit the DRX updating information to a core network node for updating one or more traffic flows associated with the UE. For example, after generating the DRX updating information based on the DRX cycle time requested by the UE, the base station may transmit the DRX updating information to the core network node.
  • the DRX updating information may be used to update a cycle time for the first traffic flow and the second traffic flow.
  • the core network node may include a user plane function (UPF) .
  • UPF user plane function
  • the base station may receive a packet delay budget (PDB) message from the core network node for the one or more traffic flows associated with the UE based on the DRX updating information. For example, after generating the PDB message based on the DRX updating information, the core network node may transmit the PDB message to the base station for updating the first cycle time of the first traffic flow and the second cycle time of the second traffic flow according to the PDB value provided in the PDB message.
  • the base station may schedule one or more radio resources based on the PDB message.
  • the base station may communicate with a UE using the one or more radio resources.
  • FIG. 8 is a block diagram conceptually illustrating an example hardware implementation for a core network node in accordance with some aspects of the disclosure.
  • the core network node may be a user plane function such as UPF 212 illustrated in FIG. 2.
  • an element, or any portion of an element, or any combination of elements may be implemented with a processing system 814 that includes one or more processors 804.
  • the processing system 814 may be substantially the same as the processing system 614 illustrated in FIG. 6, including a bus interface 808, a bus 802, memory 805, a processor 804, and a computer-readable medium 806.
  • the core network node 800 may include an optional user interface 812 and a network interface 810. That is, the processor 804, as utilized in a core network node 800, may be used to implement any one or more of the processes described below.
  • the processor 804 may include circuitry configured for various functions.
  • the processor may include a receiving circuit 840 configured to perform various functions, including, for example, receiving discontinuous reception (DRX) updating information from a base station, wherein the DRX updating information is based on a requested DRX cycle time for one or more traffic flows associated with a user equipment (UE) .
  • the receiving circuit 840 may further be configured to execute receiving instructions 850 (receiving software) stored in the computer-readable medium 806 to implement one or more of the functions described herein.
  • the processor 804 may include a generating circuit 842 configured to perform various functions, including, for example, generating a packet delay budget (PDB) message based on the DRX updating information.
  • the generating circuit 842 may further be configured to execute generating instructions 852 (generating software) stored in the computer-readable medium 806 to implement one or more of the functions described herein.
  • the processor 804 may include a transmitting circuit 844 configured to perform various functions, including, for example, transmitting the PDB message to the base station for updating the one or more traffic flows associated with the UE.
  • the transmitting circuit 844 may also be configured to perform various functions, including, for example, transmitting the PDB message to the base station for reception by the UE to update the one or more traffic flows associated with the UE.
  • the transmitting circuit 844 may further be configured to execute transmitting instructions 854 (transmitting software) stored in the computer-readable medium 806 to implement one or more of the functions described herein.
  • circuitry included in the processor 804 is merely provided as an example, and other means for carrying out the described functions may be included within various aspects of the present disclosure, including but not limited to the instructions stored in the computer-readable storage medium 806, or any other suitable apparatus or means described in any one of the FIGS. 1-7 and 9-11 and utilizing, for example, the processes or algorithms described herein.
  • FIG. 9 is a flow chart illustrating an example method 900 performed at a core network node for updating one or more traffic flows associated with a user equipment (UE) using a discontinuous reception (DRX) cycle time message in accordance with some aspects of the disclosure.
  • UE user equipment
  • DRX discontinuous reception
  • the method 900 may be carried out by the core network node 800 illustrated in FIG. 8.
  • the method 900 may be carried out by a user plane function (UPF) such as UPF 212 illustrated in FIG. 2.
  • UPF user plane function
  • the core network node may receive discontinuous reception (DRX) updating information from a base station.
  • the DRX updating information may be based on a requested DRX cycle time for one or more traffic flows associated with a UE.
  • the base station may transmit the DRX updating information to the core network node.
  • the DRX updating information may be used to update a cycle time for the first traffic flow and the second traffic flow.
  • the core network node may include a user plane function (UPF) .
  • UPF user plane function
  • the core network node may generate a packet delay budget (PDB) message based on the DRX updating information.
  • the base station may transmit the DRX updating information that based on a DRX cycle time for one or more traffic flows associated with the UE.
  • the core network node may generate a PDB message that is based on the DRX updating information.
  • generating the PDB message based on the DRX updating information may include setting a PDB value equal to the requested DRX cycle time.
  • a UE may request a DRX cycle time of 50ms.
  • the core network node may set a PDB value to 50ms so that the PDB value is equal to the requested DRX cycle time.
  • the core network node 800 may transmit the PDB message to the base station for updating the one or more traffic flows associated with the UE. For example, after generating the PDB message based on the DRX updating information, the core network node may transmit the PDB message to the base station for updating the first cycle time of the first traffic flow and the second cycle time of the second traffic flow according to the PDB value provided in the PDB message.
  • FIG. 10 is a block diagram conceptually illustrating an example hardware implementation for a user equipment (UE) 1000 in accordance with some aspects of the disclosure.
  • the UE 1000 may be illustrated in any one or more of FIGS. 1-9 and 11.
  • the UE 1000 may be implemented with a processing system 1014 that includes one or more processors 1004.
  • processors 1004 include microprocessors, microcontrollers, digital signal processors (DSPs) , field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • DSPs digital signal processors
  • FPGAs field programmable gate arrays
  • PLDs programmable logic devices
  • state machines gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • the UE 1000 may be configured to perform any one or more of the functions described herein. That is, the processor 1004, as utilized in the base station 1000, may be used to implement any one or more of the processes and procedures described and illustrated in FIGS. 1-9 and 11.
  • the processing system 1014 may be implemented with a bus architecture, represented generally by the bus 1002.
  • the bus 1002 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 1014 and the overall design constraints.
  • the bus 1002 communicatively couples together various circuits including one or more processors (represented generally by the processor 1004) , a memory 1005, and computer-readable media (represented generally by the computer-readable medium 1006) .
  • the bus 1002 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.
  • a bus interface 1008 provides an interface between the bus 1002 and a transceiver 1010.
  • the transceiver 1010 may provide a communication interface or means for wirelessly communicating with various other apparatus over a transmission medium.
  • a user interface 1012 for example, keypad, display, speaker, microphone, joystick
  • keypad for example, keypad, display, speaker, microphone, joystick
  • the processor 1004 may include circuitry configured for various functions.
  • the processor 1004 may include a transmitting circuit 1040 configured to perform various functions, including, for example, transmitting a message to a base station, the message requesting a discontinuous reception (DRX) cycle time for one or more traffic flows associated with the UE.
  • the transmitting circuit 1040 may further be configured to execute transmitting instructions 1050 (transmitting software) stored in the computer-readable medium 1006 to implement one or more of the functions described herein.
  • the processor 1004 may include a receiving circuit 1042 configured to perform various functions, including, for example, receiving a packet delay budget (PDB) message for the one or more traffic flow associated with the UE, wherein the PDB message is based on generated DRX updating information derived from the DRX cycle time.
  • the receiving circuit 1042 may further be configured to execute receiving instructions 1052 (receiving software) stored in the computer-readable medium 1006 to implement one or more of the functions described herein.
  • the processor 1004 may include a updating circuit 1044 configured to perform various functions, including, for example, updating the one or more traffic flows based on the PDB message.
  • the updating circuit 1044 may further be configured to execute updating instructions 1054 (updating software) stored in the computer-readable medium 1006 to implement one or more of the functions described herein.
  • circuitry included in the processor 1004 is merely provided as an example, and other means for carrying out the described functions may be included within various aspects of the present disclosure, including but not limited to the instructions stored in the computer-readable storage medium 1006, or any other suitable apparatus or means described in any one of the FIGS. 1-9 and 11 and utilizing, for example, the processes or algorithms described herein.
  • FIG. 11 is a flow chart illustrating an example method 1100 performed at a user equipment (UE) for updating one or more traffic flows associated with a user equipment (UE) using a discontinuous reception (DRX) cycle time message in accordance with some aspects of the disclosure.
  • UE user equipment
  • DRX discontinuous reception
  • the UE may transmit a message to a base station.
  • the message may request a DRX cycle time for one or more traffic flows associated with the UE.
  • the UE may be utilizing a first traffic flow with a first cycle time of 100ms and a second traffic flow with a second cycle time of 20ms.
  • the UE may determine to utilize a DRX cycle time of 50ms.
  • the UE may generate a message requesting a DRX cycle time of 50ms to update the first cycle time and the second cycle time to a cycle time of 50ms.
  • the one or more traffic flows associated with the UE include one or more Quality of Service (QoS) flows associated with the UE.
  • QoS Quality of Service
  • the UE may transmit the message to the base station for updating the first traffic flow and the second traffic flow according to the DRX cycle time.
  • the message may include a radio resource control (RRC) delay budget report (DBR) message.
  • RRC radio resource control
  • DBR delay budget report
  • the UE may generate receive a packet delay budget (PDB) message that is based on generated DRX updating information derived from the DRX cycle time. For example, the UE may transmit the message requesting a DRX cycle time for one or more traffic flows associated with the UE.
  • the base station may generate DRX updating information based on the DRX cycle time requested by the UE.
  • the base station may generate DRX updating information based on the DRX cycle time for the first cycle traffic flow and the second cycle traffic flow.
  • the UE may update the one or more traffic flows based on the PDB message.
  • the UE may update both the first cycle time of the first traffic flow and the second cycle time of the second traffic flow according to the PDB value.
  • the UE may update both the first cycle time of the first traffic flow and the second cycle time of the second traffic flow according to the PDB value so that the first cycle time and the second cycle time are both 50ms.
  • a or b may include a only, b only, or a combination of a and b.
  • a phrase referring to “at least one of” or “one or more of” a list of items refers to any combination of those items, including single members.
  • “at least one of: a, b, or c” is intended to cover the examples of: a only, b only, c only, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a and b and c.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente divulgation concerne des techniques permettant de mettre à jour un ou plusieurs flux de trafic associés à un équipement utilisateur (UE) à l'aide d'un message de temps de cycle de réception discontinue (DRX). Une station de base reçoit un message d'un équipement utilisateur (UE) demandant un temps de cycle DRX. La station de base génère des informations de mise à jour DRX d'après le temps de cycle DRX. La station de base transmet les informations de mise à jour DRX à un nœud de réseau central pour mettre à jour un ou plusieurs flux de trafic associés à l'UE. La station de base reçoit un message de budget de retard de paquet (PDB) du nœud de réseau central pour le(s) flux de trafic associé(s) à l'UE d'après les informations de mise à jour DRX. La station de base transmet le message PDB À l'UE pour mettre à jour le(s) flux de trafic.
PCT/CN2020/111726 2020-08-27 2020-08-27 Mise à jour de flux de trafic à l'aide d'un message de temps de cycle de réception discontinue Ceased WO2022041036A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/111726 WO2022041036A1 (fr) 2020-08-27 2020-08-27 Mise à jour de flux de trafic à l'aide d'un message de temps de cycle de réception discontinue

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/111726 WO2022041036A1 (fr) 2020-08-27 2020-08-27 Mise à jour de flux de trafic à l'aide d'un message de temps de cycle de réception discontinue

Publications (1)

Publication Number Publication Date
WO2022041036A1 true WO2022041036A1 (fr) 2022-03-03

Family

ID=80352298

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/111726 Ceased WO2022041036A1 (fr) 2020-08-27 2020-08-27 Mise à jour de flux de trafic à l'aide d'un message de temps de cycle de réception discontinue

Country Status (1)

Country Link
WO (1) WO2022041036A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025231251A1 (fr) * 2024-05-02 2025-11-06 Verizon Patent And Licensing Inc. Déploiement de fonctionnalités dans un réseau mobile sans dépendance de station de base

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016010467A1 (fr) * 2014-07-17 2016-01-21 Telefonaktiebolaget L M Ericsson (Publ) Procédé et élément de réseau pour programmer un dispositif de communication
CN109891927A (zh) * 2016-11-04 2019-06-14 瑞典爱立信有限公司 用于空口延迟调节的机制
US20200107339A1 (en) * 2018-09-28 2020-04-02 Qualcomm Incorporated Delay budget for low latency communications

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016010467A1 (fr) * 2014-07-17 2016-01-21 Telefonaktiebolaget L M Ericsson (Publ) Procédé et élément de réseau pour programmer un dispositif de communication
CN109891927A (zh) * 2016-11-04 2019-06-14 瑞典爱立信有限公司 用于空口延迟调节的机制
US20200107339A1 (en) * 2018-09-28 2020-04-02 Qualcomm Incorporated Delay budget for low latency communications

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "KI#1， New Sol: negotiate a PC5 DRX for Unicast communication", 3GPP TSG-WG SA2 MEETING #140E E-MEETING，S2-2005400, 13 August 2020 (2020-08-13), XP051920228 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025231251A1 (fr) * 2024-05-02 2025-11-06 Verizon Patent And Licensing Inc. Déploiement de fonctionnalités dans un réseau mobile sans dépendance de station de base

Similar Documents

Publication Publication Date Title
US11985557B2 (en) Signaling for conditional primary secondary cell addition/change configuration
US12323343B2 (en) Enablement of simultaneous beam update across component carriers
EP4183089A1 (fr) Planification de parties de largeur de bande actives
US11825373B2 (en) Reference measurement timing selection for wireless communication mobility
US12010508B2 (en) Peer-to-peer link security setup for relay connection to mobile network
US12171001B2 (en) Determining transmission preparation time for wireless communication on at least one carrier
US11838917B2 (en) Cross-carrier downlink control information scheduling
US11805477B2 (en) Method to reduce recovery time from out-of-service event in dual receive (DR) or dual sim dual access (DSDA) capable user equipment
US11818724B2 (en) Communication after change in bandwidth part
US20230239847A1 (en) Wireless communication using multiple active bandwidth parts
US20240114373A1 (en) Cell activation procedures
EP4559121A1 (fr) Gestion de conflit de porteuses composantes au niveau d'un dispositif de communication sans fil avec de multiples abonnements
US20240276389A1 (en) Power control parameters for wireless communication
WO2022041036A1 (fr) Mise à jour de flux de trafic à l'aide d'un message de temps de cycle de réception discontinue
WO2024156076A1 (fr) Commutation de groupe de cellules pour mobilité déclenchée par une couche inférieure
WO2024098182A9 (fr) Prach déclenché pour une cellule candidate
WO2024092600A1 (fr) Procédures de transfert intercellulaire de couche 1 et de couche 2
WO2024092603A1 (fr) Procédures de transfert de couche 1/couche 2
WO2023010271A1 (fr) Préférence de connectivité de réseau d'équipement utilisateur
WO2024073180A1 (fr) Procédures d'activation de cellule
WO2024036595A1 (fr) Sélection de ressource d'accès aléatoire

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20950708

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20950708

Country of ref document: EP

Kind code of ref document: A1