WO2022129390A1 - Procédés de mise à jour automatique d'autorisation configurée et de synchronisation de planification semi-persistante pour des services xr - Google Patents

Procédés de mise à jour automatique d'autorisation configurée et de synchronisation de planification semi-persistante pour des services xr Download PDF

Info

Publication number
WO2022129390A1
WO2022129390A1 PCT/EP2021/086281 EP2021086281W WO2022129390A1 WO 2022129390 A1 WO2022129390 A1 WO 2022129390A1 EP 2021086281 W EP2021086281 W EP 2021086281W WO 2022129390 A1 WO2022129390 A1 WO 2022129390A1
Authority
WO
WIPO (PCT)
Prior art keywords
start times
dci
transmission resources
application data
network node
Prior art date
Application number
PCT/EP2021/086281
Other languages
English (en)
Inventor
Du Ho KANG
Jose Luis Pradas
Xingqin LIN
Original Assignee
Ericsson
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 Ericsson filed Critical Ericsson
Publication of WO2022129390A1 publication Critical patent/WO2022129390A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • 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/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • 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/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • 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
    • 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/0078—Timing of allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • 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

Definitions

  • the present invention generally relates to wireless communication networks, and more specifically to techniques for reducing communication latency or delay for applications (e.g., extended reality (XR) and cloud gaming) needing guaranteed low latency.
  • applications e.g., extended reality (XR) and cloud gaming
  • NR New Radio
  • 3GPP Third-Generation Partnership Project
  • eMBB enhanced mobile broadband
  • MTC machine type communications
  • URLLC ultra-reliable low latency communications
  • D2D side-link device-to-device
  • FIG. 1 illustrates an exemplary high-level view of the 5G network architecture, consisting of a Next Generation RAN (NG-RAN) 199 and a 5G Core (5GC) 198.
  • NG-RAN 199 can include a set of gNodeB’s (gNBs) connected to the 5GC via one or more NG interfaces, such as gNBs 100, 150 connected via interfaces 102, 152, respectively.
  • the gNBs can be connected to each other via one or more Xn interfaces, such as Xn interface 140 between gNBs 100 and 150.
  • each of the gNBs can support frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.
  • FDD frequency division duplexing
  • TDD time division duplexing
  • NG-RAN 199 is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL).
  • RNL Radio Network Layer
  • TNL Transport Network Layer
  • the TNL For each NG-RAN interface (NG, Xn, Fl), the TNL provides services for user plane transport and signaling transport.
  • the NG RAN logical nodes shown in Figure 1 include a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU).
  • gNB 100 includes gNB-CU 110 and gNB-DUs 120 and 130.
  • CUs e.g., gNB-CU 110
  • CUs are logical nodes that host higher-layer protocols and perform various gNB functions such controlling the operation of DUs.
  • Each DU is a logical node that hosts lower-layer protocols and can include, depending on the functional split, various subsets of the gNB functions.
  • each of the CUs and DUs can include various circuitry needed to perform their respective functions, including processing circuitry, transceiver circuitry (e.g., for communication), and power supply circuitry.
  • central unit and “centralized unit” are used interchangeably herein, as are the terms “distributed unit” and “decentralized unit.”
  • a gNB-CU connects to gNB-DUs over respective Fl logical interfaces, such as interfaces 122 and 132 shown in Figure 1.
  • the gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB. In other words, the Fl interface is not visible beyond gNB-CU.
  • FIG. 2 shows a high-level view of an exemplary 5G network architecture, including a Next Generation Radio Access Network (NG-RAN) 299 and a 5G Core (5GC) 298.
  • NG-RAN 299 can include gNBs 210 e.g., 210a, b) and ng-eNBs 220 (e.g., 220a, b) that are interconnected with each other via respective Xn interfaces.
  • gNBs 210 e.g., 210a, b
  • ng-eNBs 220 e.g., 220a, b
  • the gNBs and ng-eNBs are also connected via the NG interfaces to 5GC 298, more specifically to the Access and Mobility Management Function (AMF, e.g., 230a, b) via respective NG-C interfaces and to the User Plane Function (UPF, e.g., 240a, b) via respective NG-U interfaces.
  • AMFs 230a, b can communicate with one or more policy control functions (PCFs, e.g., 250a, b) and network exposure functions (NEFs, e.g., 260a, b).
  • PCFs policy control functions
  • NEFs network exposure functions
  • Each of the gNBs 210 can support the NR radio interface including frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.
  • Each of ng-eNBs 220 can support the fourth-generation (4G) Long-Term Evolution (LTE) radio interface. Unlike conventional LTE eNBs, however, ng-eNBs 220 connect to the 5GC via the NG interface.
  • Each of the gNBs and ng-eNBs can serve a geographic coverage area including one more cells, such as cells 21 la-b and 221a-b shown in Figure 2.
  • a UE 205 can communicate with the gNB or ng-eNB serving that particular cell via the NR or LTE radio interface, respectively.
  • Figure 2 shows gNBs and ng-eNBs separately, it is also possible that a single NG-RAN node provides both types of functionality.
  • 5G/NR technology shares many similarities with LTE.
  • NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in the DL and both CP-OFDM and DFT-spread OFDM (DFT-S-OFDM) in the UL.
  • CP-OFDM Cyclic Prefix Orthogonal Frequency Division Multiplexing
  • DFT-S-OFDM DFT-S-OFDM
  • time domain NR DL and UL physical resources are organized into equal-sized 1-ms subframes. A subframe is further divided into multiple slots of equal duration, with each slot including multiple OFDM-based symbols.
  • time-frequency resources can be configured much more flexibly for an NR cell than for an LTE cell.
  • NR networks In addition to providing coverage via cells, NR networks also provide coverage via “beams.”
  • a downlink (DL, i.e., network to UE) “beam” is a coverage area of a network-transmitted reference signal (RS) that may be measured/monitored by a UE.
  • RS network-transmitted reference signal
  • Figure 3 shows an exemplary configuration of NR user plane (UP) and control plane (CP) protocol stacks between a UE (310), a gNB (320), and an AMF (320), such as those shown in Figures 1-2.
  • the Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP) layers between the UE and the gNB are common to UP and CP.
  • the PDCP layer provides ciphering/deciphering, integrity protection, sequence numbering, reordering, and duplicate detection for both CP and UP.
  • PDCP provides header compression and retransmission for UP data.
  • IP Internet protocol
  • SDU service data units
  • PDU protocol data units
  • the RLC layer transfers PDCP PDUs to the MAC through logical channels (LCH).
  • LCH logical channels
  • RLC provides error detection/correction, concatenation, segmentation/reassembly, sequence numbering, reordering of data transferred to/from the upper layers. If RLC receives a discard indication from associated with a PDCP PDU, it will discard the corresponding RLC SDU (or any segment thereof) if it has not been sent to lower layers.
  • the MAC layer provides mapping between LCHs and PHY transport channels, LCH prioritization, multiplexing into or demultiplexing from transport blocks (TBs), hybrid ARQ (HARQ) error correction, and dynamic scheduling (on gNB side).
  • the PHY layer provides transport channel services to the MAC layer and handles transfer over the NR radio interface, e.g., via modulation, coding, antenna mapping, and beam forming.
  • the Service Data Adaptation Protocol (SDAP) layer handles quality-of-service (QoS). This includes mapping between QoS flows and Data Radio Bearers (DRBs) and marking QoS flow identifiers (QFI) in UL and DL packets.
  • QoS quality-of-service
  • DRBs Data Radio Bearers
  • QFI QoS flow identifiers
  • the non-access stratum (NAS) layer is between UE and AMF and handles UE/gNB authentication, mobility management, and security control.
  • the RRC layer sits below NAS in the UE but terminates in the gNB rather than the AMF.
  • RRC controls communications between UE and gNB at the radio interface as well as the mobility of a UE between cells in the NG-RAN.
  • RRC also broadcasts system information (SI) and performs establishment, configuration, maintenance, and release of DRBs and Signaling Radio Bearers (SRBs) and used by UEs.
  • SI system information
  • SRBs Signaling Radio Bearers
  • RRC controls addition, modification, and release of carrier aggregation (CA) and dual -connectivity (DC) configurations for UEs.
  • CA carrier aggregation
  • DC dual -connectivity
  • RRC also performs various security functions such as key management.
  • RRC IDLE After a UE is powered ON it will be in the RRCJCDLE state until an RRC connection is established with the network, at which time the UE will transition to RRC CONNECTED state (e.g., where data transfer can occur). The UE returns to RRC IDLE after the connection with the network is released.
  • RRC IDLE state the UE’s radio is active on a discontinuous reception (DRX) schedule configured by upper layers.
  • DRX active periods also referred to as “DRX On durations”
  • an RRC IDLE UE receives SI broadcast in the cell where the UE is camping, performs measurements of neighbor cells to support cell reselection, and monitors a paging channel on PDCCH for pages from 5GC via gNB.
  • NR RRC includes an RRC_INACTIVE state in which a UE is known (e.g., via UE context) by the serving gNB.
  • RRC INACTIVE has some properties similar to a “suspended” condition used in LTE.
  • Extended Reality (XR) and Cloud Gaming are important 5G media applications under consideration in the industry.
  • XR is an umbrella term that refers to all real-and-virtual combined environments and human-machine interactions generated by computer technology and wearables.
  • XR includes Augmented Reality (AR), Mixed Reality (MR), and Virtual Reality (VR), as well as various other types that span or sit between these examples.
  • AR Augmented Reality
  • MR Mixed Reality
  • VR Virtual Reality
  • the term “XR” also refers to cloud gaming and related applications.
  • Video is an important component of most XR applications and is typically associated with a video frame rate (also referred to as “frame refresh rate”).
  • frame refresh rate also referred to as “frame refresh rate”.
  • the inter-arrival time of video frames is the reciprocal of the frame refresh rate.
  • Typical frame refresh rates are 30, 60, 90, and 120 Hz, with the specific rate being dependent on application needs and the capabilities of the video source and destination (e.g., VR headset).
  • frame refresh rates are independent of the communication network (e.g., 5G/NR) used for video transport can cause various problems, issues, and/or difficulties, particularly for XR applications that require very low latency.
  • 5G/NR communication network
  • Embodiments of the present disclosure provide specific improvements to communication between user equipment (UE) and network nodes in a wireless network, such as by providing, enabling, and/or facilitating solutions to overcome exemplary problems summarized above and described in more detail below.
  • UE user equipment
  • Embodiments include methods e.g., procedures) for a UE configured to transmit and receive application data in a wireless network.
  • These exemplary methods can include receiving, from the wireless network, an allocation of a plurality of transmission resources having respective periodic start times.
  • the allocation of the transmission resources comprises one of the following:
  • CG type-1 configured grant
  • UL uplink
  • SPS semi-persistent scheduling
  • These exemplary methods can also include determining modified start times for the respective transmission resources based on the periodic start times and one or more parameters associated with periodically arriving application data.
  • the duration between successive arrivals of the application data can be a non-integer multiple of the duration between successive start times of the allocated transmission resources.
  • the modified start times can be better aligned with the arrivals of the application data, thereby reducing application latency.
  • These exemplary methods can also include transmitting (i.e., to the wireless network) or receiving (i.e., from the wireless network) the periodically arriving application data using the allocated transmission resources at the respective modified start times.
  • the allocation includes the one or more parameters associated with the periodically arriving application data.
  • the one or more parameters include a video frame rate, such as 30 Hz, 60 Hz, 90 Hz, or 120 Hz.
  • determining the modified start times can include calculating respective numbers of transmission timeslots based on a function of the video frame rate and respective indices associated with the respective transmission resources; and adding the respective numbers of transmission timeslots to the periodic start times to obtain the modified start times.
  • the one or more parameters can include an offset increment parameter and a modulo parameter representing a number of consecutive allocated transmission resources over which a same timing offset is applied.
  • determining the modified start times can include determining respective offset scaling factors based on the modulo parameter and respective indices associated with the respective transmission resources; calculating respective numbers of transmission timeslots based on a function of the offset increment parameter and the respective offset scaling factors; and adding the respective numbers of transmission timeslots to the periodic start times to obtain the modified start times.
  • these exemplary methods can also include receiving first downlink control information (DCI) activating the allocation; determining the periodic start times based on a first timing offset included in the first DCI; and subsequently receiving second DCI updating the allocation.
  • DCI downlink control information
  • the modified start times can be determined for all periodic start times after the second DCI and based on a second timing offset included in the second DCI.
  • receiving the first DCI can include validating one or more bit fields of the first DCI against bit field patterns representative of an activation.
  • receiving the second DCI can include validating one or more bit fields of the second DCI against bit field patterns representative of an update.
  • receiving the second DCI can include validating one or more bit fields of the second DCI against bit field patterns representative of an activation. In such case, the second DCI can indicate an update based on the first DCI indicating an activation and the UE not receiving an intervening DCI indicating a deactivation.
  • receiving the first DCI can include receiving a DCI of a first format corresponding to an activation.
  • receiving the second DCI can include receiving a DCI of a second format corresponding to an update.
  • inventions include exemplary methods (e.g., procedures) for a network node configured to transmit and receive application data with a UE in a wireless network.
  • These exemplary methods can include transmitting, to the UE, an allocation of a plurality of transmission resources having respective periodic start times.
  • the allocation of the plurality of transmission resources comprises one of the following:
  • These exemplary methods can also include determining modified start times for the respective transmission resources based on the periodic start times and one or more parameters associated with periodically arriving application data.
  • the duration between successive arrivals of the application data can be a non-integer multiple of the duration between successive start times of the allocated transmission resources.
  • the modified start times can be better aligned with the arrivals of the application data, thereby reducing application latency.
  • These exemplary methods can also include transmitting (i.e., to the UE) or receiving (i.e., from the UE) the periodically arriving application data using the allocated transmission resources at the respective modified start times.
  • the allocation includes the one or more parameters associated with the periodic arrivals of the application data.
  • the one or more parameters include a video frame rate, such as 30 Hz, 60 Hz, 90 Hz, or 120 Hz.
  • determining the modified start times can include calculating respective numbers of transmission timeslots based on a function of the video frame rate and respective indices associated with the respective transmission resources; and adding the respective numbers of transmission timeslots to the periodic start times to obtain the modified start times.
  • the one or more parameters can include an offset increment parameter and a modulo parameter representing a number of consecutive allocated transmission resources over which a same timing offset is applied.
  • determining the modified start times can include determining respective offset scaling factors based on the modulo parameter and respective indices associated with the respective transmission resources; calculating respective numbers of transmission timeslots based on a function of the offset increment parameter and the respective offset scaling factors; and adding the respective numbers of transmission timeslots to the periodic start times to obtain the modified start times.
  • these exemplary methods can also include transmitting first DCI activating the allocation.
  • the first DCI can include a first timing offset associated with the periodic start times.
  • these exemplary methods can also include subsequently transmitting a second DCI updating the allocation.
  • the second DCI can include a second timing offset associated with the modified start times.
  • transmitting first DCI can include setting one or more bit fields of the first DCI to bit field patterns representative of an activation.
  • transmitting second DCI can include setting one or more bit fields of the second DCI to bit field patterns representative of an update.
  • transmitting second DCI can include setting one or more bit fields of the second DCI to bit field patterns representative of an activation. In such case, the second DCI indicates an update based on the first DCI indicating an activation and the network node not transmitting an intervening DCI indicating a deactivation.
  • transmitting first DCI can include transmitting a DCI of a first format corresponding to an activation.
  • transmitting second DCI can include transmitting a DCI of a second format corresponding to an update.
  • UEs e.g., wireless devices
  • network nodes e.g., base stations, eNBs, gNBs, ng-eNBs, etc., or components thereof
  • Other embodiments include non-transitory, computer-readable media storing program instructions that, when executed by processing circuitry, configure such UEs or network nodes to perform operations corresponding to any of the exemplary methods described herein.
  • embodiments described herein provide flexible and efficient techniques to update timing of the first symbol of each SPS/CG occasion to match an application (e.g., video) traffic periodicity that is not an integer multiple of the transmission slot length, thereby reducing or eliminating excess UL or DL transmission latency without requiring frequent signaling to update SPS/CG parameters.
  • embodiments can avoid unnecessary and/or aggressive CG over-provisioning by allocating grants that better match application traffic arrival in the time domain. This can result in reduced application transmission latency and improved quality of experience (QoE), including for XR applications.
  • QoE quality of experience
  • Figures 1-2 illustrate two high-level views of an exemplary 5G/NR network architecture.
  • Figure 3 shows an exemplary configuration of NR user plane (UP) and control plane (CP) protocol stacks.
  • UP user plane
  • CP control plane
  • Figure 4 illustrates a comparison of various characteristics or requirements between Extended Reality (XR) and other 5G applications.
  • Figure 5 shows an example of frame latency measured over a radio access network (RAN, e.g., NG-RAN).
  • RAN radio access network
  • Figure 6 shows exemplary cumulative distribution functions (CDFs) for the number of transport blocks (TBs) on the NR PHY required to deliver video frames of various sizes.
  • CDFs cumulative distribution functions
  • Figure 7 shows a comparison of arrival times between XR, voice-over-IP (VoIP), and web browsing traffic.
  • VoIP voice-over-IP
  • Figure 8 is a table illustrating timing misalignment between periodic transmission resource allocations and arrival times of periodic application traffic, such as video frames.
  • Figure 9 is a table illustrating improved timing alignment between periodic transmission resource allocations and arrival times of periodic application traffic, according to various embodiments of the present disclosure.
  • FIG 10 shows a flow diagram of an exemplary method for a user equipment (UE, e.g., wireless device), according to various embodiments of the present disclosure.
  • UE user equipment
  • Figure 11 shows a flow diagram of an exemplary method for a network node (e.g., base station, eNB, gNB, ng-eNB, efc.), according to various embodiments of the present disclosure.
  • a network node e.g., base station, eNB, gNB, ng-eNB, efc.
  • Figure 12 shows a block diagram of an exemplary wireless device or UE, according to various embodiments of the present disclosure.
  • Figure 13 shows a block diagram of an exemplary network node according to various embodiments of the present disclosure.
  • Figure 14 shows a block diagram of an exemplary network configured to provide over- the-top (OTT) data services between a host computer and a UE, according to various embodiments of the present disclosure.
  • OTT over-the-top
  • Radio Node can be either a radio access node or a wireless device.”
  • Node can be a network node or a wireless device.
  • Radio Access Node As used herein, a “radio access node” (or equivalently “radio network node,” “radio access network node,” or “RAN node”) can be any node in a radio access network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals.
  • RAN radio access network
  • a radio access node examples include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a 3GPP Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP LTE network), base station distributed components (e.g., CU and DU), a high-power or macro base station, a low-power base station (e.g., micro, pico, femto, or home base station, or the like), an integrated access backhaul (IAB) node, a transmission point, a remote radio unit (RRU or RRH), and a relay node.
  • a base station e.g., a New Radio (NR) base station (gNB) in a 3GPP Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP LTE network
  • base station distributed components e.g., CU and DU
  • a “core network node” is any type of node in a core network.
  • Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), a Packet Data Network Gateway (P-GW), an access and mobility management function (AMF), a session management function (AMF), a user plane function (UPF), a Service Capability Exposure Function (SCEF), or the like.
  • MME Mobility Management Entity
  • SGW serving gateway
  • P-GW Packet Data Network Gateway
  • AMF access and mobility management function
  • AMF access and mobility management function
  • AMF AMF
  • UPF user plane function
  • SCEF Service Capability Exposure Function
  • Wireless Device As used herein, a “wireless device” (or “WD” for short) is any type of device that has access to (i.e., is served by) a cellular communications network by communicate wirelessly with network nodes and/or other wireless devices. Communicating wirelessly can involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • wireless device examples include, but are not limited to, smart phones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop- embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer-premise equipment (CPE), mobile-type communication (MTC) devices, Internet-of-Things (loT) devices, vehicle-mounted wireless terminal devices, etc.
  • the term “wireless device” is used interchangeably herein with the term “user equipment” (or “UE” for short).
  • Network Node is any node that is either part of the radio access network (e.g., a radio access node or equivalent name discussed above) or of the core network (e.g., a core network node discussed above) of a cellular communications network.
  • a network node is equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the cellular communications network, to enable and/or provide wireless access to the wireless device, and/or to perform other functions (e.g., administration) in the cellular communications network.
  • typical video frame refresh rates are 30, 60, 90, and 120 Hz, with the particular value being determined based on application needs and the capabilities of the video source and destination (e.g., VR headset).
  • the fact that frame refresh rates are independent of the communication network (e.g., 5G/NR) used for video transport can cause various problems, issues, and/or difficulties, particularly for XR applications that require very low latency. This is discussed in more detail below, after a brief introduction to NR PHY characteristics.
  • NR DL and UL physical resources are organized into equal-sized 1-ms subframes.
  • a subframe is further divided into multiple slots of equal duration, with each slot including multiple OFDM-based symbols.
  • An NR slot can include 14 OFDM symbols for normal cyclic prefix and 12 symbols for extended cyclic prefix.
  • a resource block (RB) consists of a group of 12 contiguous OFDM subcarriers for a duration of a 12- or 14-symbol slot.
  • a resource element (RE) corresponds to one OFDM subcarrier during one OFDM symbol interval.
  • a UE can be configured with up to four carrier bandwidth parts (BWPs) in the DL with a single DL BWP being active at a given time.
  • BWPs carrier bandwidth parts
  • a UE can be configured with up to four BWPs in the UL with a single UL BWP being active at a given time.
  • the UE can be configured with up to four additional BWPs in the supplementary UL, with a single supplementary UL BWP being active at a given time.
  • Common RBs are numbered from 0 to the end of the carrier bandwidth.
  • Each BWP configured for a UE has a common reference of CRBO, such that a configured BWP may start at a CRB greater than zero.
  • CRBO can be identified by one of the following parameters provided by the network, as further defined in 3GPP TS 38.211 section 4.4:
  • PCell e.g., PCell or PSCell
  • a UE can be configured with a narrow BWP (e.g., 10 MHz) and a wide BWP (e.g., 100 MHz), each starting at a particular CRB, but only one BWP can be active for the UE at a given point in time.
  • BWP narrow BWP
  • 100 MHz wide BWP
  • PRBs are defined and numbered in the frequency domain from 0 to “1 , where i is the index of the particular BWP for the carrier.
  • 3 GPP Release 17 includes a study item (SI) on XR Evaluations for NR.
  • SI study item
  • the main objectives are to identify the traffic model for each application of interest and the evaluation methodology and the key performance indicators of interest for relevant deployment scenarios, and to carry out performance evaluations accordingly in order to investigate possible standardization enhancements in potential follow-up SI or work item (WI).
  • Figure 4 illustrates a high-level comparison of various characteristics requirements for XR and other 5G applications.
  • Figure 4 shows a comparison of latency, reliability, and bitrate requirements for URLLC, streaming, and EC-based XR.
  • URLLC services have extreme requirements of 1-ms latency and of 10' 5
  • EC-based XR can have relaxed requirements of 5-10 ms latency and 10' 4 reliability.
  • XR services can require a much higher bite rate than either URLLC or streaming, (e.g., due to codec inefficiency).
  • XR traffic can also be very dynamic, e.g., due to eye/viewport tracking.
  • XR requires bounded latency but not necessarily ultra-low latency.
  • the end-to-end latency budget needs to be distributed over several components including application processing latency, transport latency, radio link latency, etc.
  • TTIs transmission time intervals
  • mini-slots targeting ultra-low latency may not be effective.
  • Figure 5 shows an example of frame latency measured over a radio access network (RAN, e.g., NG-RAN), excluding latencies of application and core network (CN, e.g., 5GC).
  • RAN radio access network
  • CN core network
  • FIG. 5 shows an example of frame latency measured over a radio access network (RAN, e.g., NG-RAN), excluding latencies of application and core network (CN, e.g., 5GC).
  • RAN radio access network
  • CN core network
  • XR applications typically require high data rates. This is due to both high frame refresh rates and large video frame sizes that may range from tens to hundreds of kilobytes (kB). As a concrete example, a frame size of 100 kB and a frame refresh rate of 120 Hz can lead to a data rate requirement of 95.8 Mb/s.
  • Figure 6 shows exemplary cumulative distribution functions (CDFs) for the number of transport blocks (TBs) on the NR PHY required to deliver a video frame of size ranging from 20 to 300 kB.
  • CDFs cumulative distribution functions
  • Figure 6 shows that for video frames of size 200 kB, the median number of TBs is 5 but in ⁇ 5% of the cases, 15 or more TBs are required to deliver a 200-kB video frame.
  • a 1-ms TTI and 100-MHz carrier bandwidth is assumed in Figure 6.
  • Figure 7 shows a comparison of arrival times between XR, voice-over-IP (VoIP), and web browsing traffic.
  • XR traffic arrival time is quasi-periodic and largely predictable. This is similar to VoIP but different than web browsing, in which arrival is very unpredictable.
  • the size of XR traffic e.g., video frames
  • XR traffic data size varies across arrivals due to dynamics of contents and human motion. As such, XR traffic shares some characteristics with web browsing traffic.
  • UL and DL data transmissions can take place with or without an explicit grant or assignment of resources by the network (e.g., gNB).
  • the network e.g., gNB
  • UL transmissions are usually referred to as being “granted” by the network (i.e., “UL grant”)
  • DL transmissions are usually referred to as taking place on resources that are “assigned” by the network (i.e., “DL assignment”).
  • DCI downlink control information
  • a transmission without an explicit grant/assignment is typically configured to occur with a defined periodicity.
  • the UE Given a periodic and/or recurring UL grant and/or DL assignment, the UE can then initiate a data transmission and/or receive data according to a predefined configuration.
  • Such transmissions can be referred to as semi-persistent scheduling (SPS, for DL), configured grant (CG, for UL), or grant-free transmissions.
  • Type-1 are configured via RRC signaling only, while for Type-2, some parameters are preconfigured via RRC signaling and some PHY parameters are dynamically indicated via DCI that also activates/deactivates the grant.
  • the RRC configuration of a UL configured grant includes various parameters, including a configuredGrantTimer value used for controlling operation of hybrid ARQ (HARQ) processes in the UL via a controlled grant timer (“CG timer”) in the UE.
  • CG timer controlled grant timer
  • a related feature is Autonomous Uplink (AUL), which can support autonomous HARQ retransmissions using an UL CG.
  • AUL Autonomous Uplink
  • Configuration of SPS includes periodicity of the assignment, resource allocation in time and frequency, and modulation and coding scheme (MCS) in SPS occasions, among others.
  • MCS modulation and coding scheme
  • XR Low-latency high-bandwidth applications, such as XR, require timely allocation of large amounts of radio resource in time/frequency domains.
  • frame arrival of XR traffic is expected to be relatively periodic, as illustrated in Figure 7. Therefore, it is expected that the SPS/CG resource allocations will be used for at least part of XR data transmissions, such as periodic UL buffer status reports (BSR) report and initial UL/DL data transmissions.
  • BSR periodic UL buffer status reports
  • the NR MAC specification 3GPP TS 38.321 (), defines the timing of the first symbol of granted resources in a type-2 UL CG as follows. After an UL grant is configured for a CG Type 2, the MAC entity shall consider sequentially that the N' h (N > 0) UL grant occurs in the symbol for which:
  • 3GPP TS 38.321 defines the timing of the first symbol of granted resources in a type-1 UL CG as follows. After an UL grant is configured for a CG Type 1, the MAC entity shall consider sequentially that the N' h UL grant (N > 0) occurs in the symbol for which:
  • timeReferenceSFN x numberOfSlotsPerFrame x numberOfSymbolsPerSlot + timeDomainOffset x numberOfSymbolsPerSlot + S + N x periodicity modulo (1024 x numberOfSlotsPerFrame x numberOfSymbolsPerSlot), where all terms have the same meanings as discussed above for UL CG type-2.
  • 3GPP TS 38.321 defines the timing of the first symbol of assigned resources in an SPS assignment as follows. After a DL assignment is configured for SPS, the MAC entity shall consider sequentially that the N' h DL assignment occurs in the slot for which:
  • periodicityExt was introduced to support finer granularities than “periodicity”, and is defined in 3GPP TS 38.331 as follows:
  • typical video frame refresh rates are multiples of 30 Hz, e.g., 30, 60, 90, 120, etc. These produce frame arrivals spaced by the reciprocal of the refresh rates, which are not aligned with the NR PHY slot and symbol timing.
  • Figure 8 is a table illustrating this example in more detail for three different periodicities: 33, 34, and 35 symbols. These periodicities are preferred choices for 60 Hz frame refresh rate. Note that a single slot with 0.5-ms duration grant is allocated for BSR and initial data transmission. The entries below the respective dashed lines indicate grants that cause more than 2-ms extra delay for a video frame due to the non-divisible arrival period of -16.667 ms. In this example, periodicity of 33 symbols will make an early start of CG. However, after fifth periodic grant, the frame arrives after the end of granted slot , i.e., at 66.667 ms.
  • embodiments of the present disclosure provide flexible and efficient techniques to update the timing of the first symbol of each SPS/CG occasion to match an application (e.g., video) traffic periodicity that is not an integer multiple of the transmission slot length, in order to reduce accumulated extra latency.
  • Some of these techniques introduce a new automatic offset update element into the calculations for SPS/CG timing (discussed above), as well as RRC signaling of relevant parameters for the automatic offset.
  • Other of these techniques introduce fast DCI signaling of SPS/CG timing updates.
  • Embodiments of the present disclosure provide various benefits and/or advantages. For example, these techniques do not require frequent MAC control element (CE), RRC, or DCI signaling to update SPS/CG parameters. Also, these techniques can avoid unnecessary and/or aggressive SPS/CG over-provisioning by allocating grants that better matches application traffic arrival in the time domain. Furthermore, these techniques can avoid accumulated latency due to the non-integer relationship between application frame rate and NR slot/symbol timing, as shown in Figure 8.
  • CE MAC control element
  • RRC Radio Resource Control element
  • DCI DCI signaling
  • Embodiments of the present disclosure can be divided into various groups to facilitate the following description. However, this grouping of embodiments is not intended to preclude the use of embodiments from different groups together and/or in a complementary manner. Also, features of embodiments from different groups may be combined unless expressly stated to the contrary or their combination would be technically infeasible and/or inoperable.
  • a first group of embodiments apply a technique of moving the occurrence (e.g., symbol) of the Nth CG to a different point in time, with automatic time shifting based on RRC signaled parameters. For example, a slot offset can be increased in proportion to the index, N, of the grant occasion.
  • the equation given above for the timing of the first symbol of granted resources in a type-2 UL CG can be modified as follows.
  • nxXR_slot_offset x numberOfSymbolsPerSlot shifts the start timing of the first symbol of Nth CG occurrence.
  • the term “XR slot offsef ’ represents the number of slots to be shifted for each increment of n.
  • the network can signal both traffic cg offset and XR slot offset to a UE, and let the UE automatically shift the CG timing based on UE determination of n.
  • These two signaled parameters provide flexibility for the network to decide how often and how much time shifting to apply to reduce the amount of excess latency associated with the CG.
  • the improvement between the “old equation” (conventional approach in 3GPP TS 38.321) and the “new equation” (embodiment of the first group) is visible starting at grant number 4.
  • the equation given above for the timing of the first symbol of granted resources in a type-1 UL CG can be modified as follows. After an UL grant is configured for a CG Type 1, the MAC entity shall consider sequentially that the N' h (N > 0) UL grant occurs in the symbol for which:
  • the equation given above for the timing of the first symbol of granted resources in an SPS assignment can be modified as follows. After a DL assignment is configured for SPS, the MAC entity shall consider sequentially that the N' h DL assignment occurs in the slot for which:
  • a second group of embodiments apply a technique of moving the occurrence (e.g., symbol) of the Nth CG to a different point in time based on information related to an application frame refresh rate (e.g., parameter “fps”, representing the numbers of frame per second).
  • the parameter “fps” can be signaled via RRC and can be equal to 30, 60, 90, and 120 for frame refresh rates of 30 Hz, 60 Hz, 90 Hz, and 120 Hz, respectively.
  • the network can signal one value from an enumerated set of frame refresh rates or an index to a particular value within an enumerated set (e.g., index “00” for 30 Hz, “01” for 60 Hz, etc.).
  • the equation given above for the timing of the first symbol of granted resources in a type-2 UL CG can be modified as follows. After an UL grant is configured for a CG Type 2, the MAC entity shall consider sequentially that the N' h (N > 0) UL grant occurs in the symbol for which:
  • the equation given above for the timing of the first symbol of granted resources in a type-1 UL CG can be modified as follows. After an UL grant is configured for a CG Type 1, the MAC entity shall consider sequentially that the N' h (N > 0) UL grant occurs in the symbol for which:
  • the equation given above for the timing of the first symbol of granted resources in an SPS assignment can be modified as follows. After a DL assignment is configured for SPS, the MAC entity shall consider sequentially that the N' h DL assignment occurs in the slot for which:
  • the start time of the first allocation for SPS or CG type 2 is indicated by DCI and is denoted as t 0 .
  • the N-th (N>1) assignment or grant is at time t_0 + (N-1)*T, where T denotes the periodicity of the SPS/CG type 2.
  • the network conventionally must send a first DCI deactivating the SPS or CG type 2, and then send a second DCI re-activating SPS/CG type 2 with a new start time (to) of the first allocation after the second DCI. This process must be repeated for every timing change.
  • a third group of embodiments include a technique for updating the start time of SPS/CG type 2 by DCI without the need to deactivate the SPS/CG type 2 and/or change the existing grant timing.
  • a new PDCCH validation is introduced for SPS/CG type 2 “update”, in addition to the existing PDCCH validations for activation and deactivation.
  • PDCCH validation is used to avoid various problems cause by mistaken activation or deactivation of an SPS or CG type 2. For example, if an SPS or CG type 2 configuration is activated by mistake, the UE may try to use the recurring allocation for a long time, which can cause problems (e.g., interference) with respect to other traffic in a cell.
  • problems e.g., interference
  • the UE in addition to verifying that a DCI is addressed to the appropriate UE identifier (e.g., RNTI), the UE must also validate the DCI contents in comparison with specific bit field values. The validation for activation or deactivation is achieved only if all relevant bit fields for the DCI are set according to specific values corresponding to those respective actions.
  • a PDCCH validation for “update” is achieved if all fields for a DCI format are set according to a certain pattern, which is different from the existing patterns used for PDCCH validation of the DCI format for activation and deactivation.
  • the UE can change the timings of transmission opportunities for the activated SPS/CG type 2 (and, optionally, other values such as frequency domain resource allocation) according to other contents of the update DCI.
  • the UE can set the start time of the first transmission opportunity for SPS/CG type 2 after the update validation based on the value of a DCI field denoted “t_0_new”, such that the Nth (N > 1) transmission opportunity afterwards occurs at time t_0_new + (N-1)*T.
  • the existing PDCCH validation for “activation” can be reused for “update”. Specifically, a UE activates an SPS/CG type 2 configuration based on a first DCI for “activation”. While the configuration is not released, the UE receives another PDCCH validation for a second “activation” DCI, which the UE will interpret as an update to the timing of subsequent transmission opportunities within the SPS/CG type 2. In some embodiments, the second “activation” DCI can also update various other values such as frequency domain resource allocation, etc.
  • the UE the UE can set the start time of the first transmission opportunity for SPS/CG type 2 after the second DCI validation based on the value of a DCI field denoted “t_0_new”, such that the Nth (N > 1) transmission opportunity afterwards occurs at time t_0_new + (N-1)*T.
  • a new DCI format can be used for SPS/CG type 2 “update”.
  • the new DCI format can update the timings of transmission opportunities for SPS/CG type 2 in a similar manner as discussed above.
  • Figures 10-11 show exemplary methods (e.g., procedures) for a UE and a network node, respectively.
  • various features of the operations described below correspond to various embodiments described above.
  • the exemplary methods shown in Figures 10-11 can be used cooperatively to provide various benefits, advantages, and/or solutions to problems described herein.
  • Figures 10-11 show specific blocks in particular orders, the operations of the exemplary methods can be performed in different orders than shown and can be combined and/or divided into blocks having different functionality than shown. Optional blocks or operations are indicated by dashed lines.
  • Figure 10 shows an exemplary method (e.g., procedure) for a UE configured to transmit and receive application data in a wireless network, according to various embodiments of the present disclosure.
  • the exemplary method can be performed by a UE (e.g., wireless device, loT device, etc.) such as described elsewhere herein.
  • a UE e.g., wireless device, loT device, etc.
  • the exemplary method can include the operations of block 1010, where the UE can receive, from a network node of the wireless network, an allocation of a plurality of transmission resources having respective periodic start times.
  • the allocation of the plurality of transmission resources comprises one of the following:
  • CG type-1 configured grant
  • UL uplink
  • SPS semi-persistent scheduling
  • the exemplary method can also include the operations of block 1050, where the UE can determine modified start times for the respective transmission resources based on the periodic start times and one or more parameters associated with periodically arriving application data.
  • the duration between successive arrivals of the application data can be a non-integer multiple of the duration between successive start times of the allocated transmission resources, such as discussed above.
  • the modified start times can be better aligned with the arrivals of the application data, thereby reducing application latency as illustrated in Figure 9.
  • the exemplary method can also include the operations of block 1060, where the UE can transmit (i.e., to the wireless network) or receive (i.e., from the wireless network) the periodically arriving application data using the allocated transmission resources at the respective modified start times.
  • the allocation includes the one or more parameters associated with the periodically arriving application data.
  • the one or more parameters include a video frame rate, such as 30 Hz, 60 Hz, 90 Hz, or 120 Hz.
  • determining the modified start times in block 1050 can include the operations of sub-blocks 1051-1052.
  • the UE can calculate respective numbers of transmission timeslots based on a function of the video frame rate and respective indices associated with the respective transmission resources.
  • the UE can add the respective numbers of transmission timeslots to the periodic start times to obtain the modified start times.
  • An exemplary equation for calculations in sub-blocks 1051-1052 was discussed above.
  • the one or more parameters can include an offset increment parameter and a modulo parameter representing a number of consecutive allocated transmission resources over which a same timing offset is applied. Examples include XR slot offset and traffic cg offset parameters, respectively, that were discussed above.
  • determining the modified start times in block 1050 can include the operations of sub-blocks 1053- 1054.
  • the UE can determine respective offset scaling factors based on the modulo parameter and respective indices associated with the respective transmission resources.
  • the UE can calculate respective numbers of transmission timeslots based on a function of the offset increment parameter and the respective offset scaling factors.
  • the determining operations can also include sub-block 1052, discussed above. An exemplary equation for calculations in sub-blocks 1052-1054 was discussed above.
  • the exemplary method can also include the operations of blocks 1020-1040.
  • the UE can receive first downlink control information (DCI) activating the allocation.
  • DCI downlink control information
  • the UE can determine the periodic start times based on a first timing offset included in the first DCI.
  • the UE can subsequently receive second DCI updating the allocation.
  • the modified start times are determined (e.g., in block 1050) for all periodic start times after the second DCI and are based on a second timing offset included in the second DCI.
  • receiving first DCI can include the operations of sub-block 1021, where the UE can validate one or more bit fields of the first DCI against bit field patterns representative of an activation.
  • receiving second DCI e.g., in block 1040
  • receiving second DCI can include the operations of sub-block 1041, where the UE can validate one or more bit fields of the second DCI against bit field patterns representative of an update.
  • receiving second DCI e.g., in block 1040
  • receiving second DCI can include the operations of sub-block 1042, where the UE can validate one or more bit fields of the second DCI against bit field patterns representative of an activation.
  • the second DCI indicates an update based on the first DCI indicating an activation and the UE not receiving an intervening DCI indicating a deactivation.
  • receiving first DCI can include the operations of sub-block 1022, where the UE can receive a DCI of a first format corresponding to an activation.
  • receiving the second DCI e.g., in block 1040
  • receiving the UE can include the operations of sub-block 1043, where the UE can receive a DCI of a second format corresponding to an update.
  • Figure 11 shows an exemplary method (e.g., procedure) for a network node configured to transmit and receive application data with a UE in a wireless network, according to various embodiments of the present disclosure.
  • the exemplary method can be performed by a network node (e.g., base station, eNB, gNB, ng-eNB, etc., or component thereof) in a wireless network (e.g., E-UTRAN, NG-RAN), such as described elsewhere herein.
  • a network node e.g., base station, eNB, gNB, ng-eNB, etc., or component thereof
  • a wireless network e.g., E-UTRAN, NG-RAN
  • the exemplary method can include the operations of block 1110, where the network node can transmit, to a UE, an allocation of a plurality of transmission resources having respective periodic start times.
  • the allocation of the plurality of transmission resources comprises one of the following:
  • the exemplary method can also include the operations of block 1140, where the network node can determine modified start times for the respective transmission resources based on the periodic start times and one or more parameters associated with periodically arriving application data.
  • the duration between successive arrivals of the application data can be a noninteger multiple of the duration between successive start times of the allocated transmission resources, such as discussed above.
  • the modified start times can be better aligned with the arrivals of the application data, thereby reducing application latency as illustrated in Figure 9.
  • the exemplary method can also include the operations of block 1150, where the network node can transmit (i.e., to the UE) or receive (i.e., from the UE) the periodically arriving application data using the allocated transmission resources at the respective modified start times.
  • the allocation includes the one or more parameters associated with the periodically arriving application data.
  • the one or more parameters include a video frame rate, such as 30 Hz, 60 Hz, 90 Hz, or 120 Hz.
  • determining the modified start times in block 1140 can include the operations of sub-blocks 1141-1142.
  • the network node can calculate respective numbers of transmission timeslots based on a function of the video frame rate and respective indices associated with the respective transmission resources.
  • the network node can add the respective numbers of transmission timeslots to the periodic start times to obtain the modified start times. These calculations can correspond to UE calculations in sub-blocks 1051- 1052, such that the network node and the UE can determine compatible modified start times.
  • the one or more parameters can include an offset increment parameter and a modulo parameter representing a number of consecutive allocated transmission resources over which a same timing offset is applied. Examples include XR slot offset and traffic cg offset parameters, respectively, that were discussed above.
  • determining the modified start times in block 1140 can include the operations of sub-blocks 1143- 1144.
  • the network node can determine respective offset scaling factors based on the modulo parameter and respective indices associated with the respective transmission resources.
  • the network node can calculate respective numbers of transmission timeslots based on a function of the offset increment parameter and the respective offset scaling factors.
  • the determining operation can also include sub-block 1142, discussed above. These calculations can correspond to UE calculations in sub-blocks 1052-1054, such that the network node and the UE can determine compatible modified start times.
  • the exemplary method can also include the operations of blocks 1120-1130.
  • the network node can transmit first DCI activating the allocation.
  • the first DCI can include a first timing offset associated with the periodic start times.
  • the network node can subsequently transmit second DCI updating the allocation.
  • the second DCI can include a second timing offset associated with the modified start times.
  • transmitting first DCI can include the operations of sub-block 1121, where the network node can set one or more bit fields of the first DCI to bit field patterns representative of an activation.
  • transmitting second DCI can include the operations of sub-block 1131, where the network node can set one or more bit fields of the second DCI to bit field patterns representative of an update.
  • transmitting second DCI e.g., in block 1130
  • transmitting second DCI can include the operations of subblock 1132, where the network node can set one or more bit fields of the second DCI to bit field patterns representative of an activation.
  • the second DCI indicates an update based on the first DCI indicating an activation and the network node not transmitting an intervening DCI indicating a deactivation.
  • transmitting first DCI can include the operations of sub-block 1122, where the network node can transmit a DCI of a first format corresponding to an activation.
  • transmitting second DCI can include the operations of sub-block 1133, where the network node can transmit a DCI of a second format corresponding to an update.
  • FIG 12 shows a block diagram of an exemplary wireless device or user equipment (UE) 1200 (hereinafter referred to as “UE 1200”) according to various embodiments of the present disclosure, including those described above with reference to other figures.
  • UE 1200 can be configured by execution of instructions, stored on a computer-readable medium, to perform operations corresponding to one or more of the exemplary methods described herein.
  • UE 1200 can include a processor 1210 (also referred to as “processing circuitry”) that can be operably connected to a program memory 1220 and/or a data memory 1230 via a bus 1270 that can comprise parallel address and data buses, serial ports, or other methods and/or structures known to those of ordinary skill in the art.
  • Program memory 1220 can store software code, programs, and/or instructions (collectively shown as computer program product (CPP) 1221 in Figure 12) that, when executed by processor 1210, can configure and/or facilitate UE 1200 to perform various operations, including operations corresponding to various exemplary methods described herein.
  • CPP computer program product
  • execution of such instructions can configure and/or facilitate UE 1200 to communicate using one or more wired or wireless communication protocols, including one or more wireless communication protocols standardized by 3GPP, 3GPP2, or IEEE, such as those commonly known as 5G/NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, IxRTT, CDMA2000, 802.11 WiFi, HDMI, USB, Firewire, etc., or any other current or future protocols that can be utilized in conjunction with radio transceiver 1240, user interface 1250, and/or control interface 1260.
  • 3GPP 3GPP2
  • IEEE such as those commonly known as 5G/NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, IxRTT, CDMA2000, 802.11 WiFi, HDMI, USB, Firewire, etc., or any other current or future protocols that can be utilized in conjunction with radio transceiver 1240, user interface 1250, and/or control interface 1260.
  • processor 1210 can execute program code stored in program memory 1220 that corresponds to MAC, RLC, PDCP, SDAP, RRC, and NAS layer protocols standardized by 3GPP (e.g., for NR and/or LTE).
  • processor 1210 can execute program code stored in program memory 1220 that, together with radio transceiver 1240, implements corresponding PHY layer protocols, such as Orthogonal Frequency Division Multiplexing (OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single-Carrier Frequency Division Multiple Access (SC-FDMA).
  • processor 1210 can execute program code stored in program memory 1220 that, together with radio transceiver 1240, implements device-to-device (D2D) communications with other compatible devices and/or UEs.
  • D2D device-to-device
  • Program memory 1220 can also include software code executed by processor 1210 to control the functions of UE 1200, including configuring and controlling various components such as radio transceiver 1240, user interface 1250, and/or control interface 1260.
  • Program memory 1220 can also comprise one or more application programs and/or modules comprising computerexecutable instructions embodying any of the exemplary methods described herein.
  • Such software code can be specified or written using any known or future developed programming language, such as e.g., Java, C++, C, Objective C, HTML, XHTML, machine code, and Assembler, as long as the desired functionality, e.g., as defined by the implemented method steps, is preserved.
  • program memory 1220 can comprise an external storage arrangement (not shown) remote from UE 1200, from which the instructions can be downloaded into program memory 1220 located within or removably coupled to UE 1200, so as to enable execution of such instructions.
  • Data memory 1230 can include memory area for processor 1210 to store variables used in protocols, configuration, control, and other functions of UE 1200, including operations corresponding to, or comprising, any of the exemplary methods described herein.
  • program memory 1220 and/or data memory 1230 can include non-volatile memory (e.g., flash memory), volatile memory (e.g., static or dynamic RAM), or a combination thereof.
  • data memory 1230 can comprise a memory slot by which removable memory cards in one or more formats (e.g., SD Card, Memory Stick, Compact Flash, etc.) can be inserted and removed.
  • processor 1210 can include multiple individual processors (including, e.g., multi-core processors), each of which implements a portion of the functionality described above. In such cases, multiple individual processors can be commonly connected to program memory 1220 and data memory 1230 or individually connected to multiple individual program memories and or data memories. More generally, persons of ordinary skill in the art will recognize that various protocols and other functions of UE 1200 can be implemented in many different computer arrangements comprising different combinations of hardware and software including, but not limited to, application processors, signal processors, general-purpose processors, multi-core processors, ASICs, fixed and/or programmable digital circuitry, analog baseband circuitry, radio-frequency circuitry, software, firmware, and middleware.
  • Radio transceiver 1240 can include radio-frequency transmitter and/or receiver functionality that facilitates the UE 1200 to communicate with other equipment supporting like wireless communication standards and/or protocols.
  • the radio transceiver 1240 includes one or more transmitters and one or more receivers that enable UE 1200 to communicate according to various protocols and/or methods proposed for standardization by 3GPP and/or other standards bodies.
  • such functionality can operate cooperatively with processor 1210 to implement a PHY layer based on OFDM, OFDMA, and/or SC-FDMA technologies, such as described herein with respect to other figures.
  • radio transceiver 1240 includes one or more transmitters and one or more receivers that can facilitate the UE 1200 to communicate with various LTE, LTE- Advanced (LTE- A), and/or NR networks according to standards promulgated by 3 GPP.
  • the radio transceiver 1240 includes circuitry, firmware, etc. necessary for the UE 1200 to communicate with various NR, NR-U, LTE, LTE- A, LTE-LAA, UMTS, and/or GSM/EDGE networks, also according to 3GPP standards.
  • radio transceiver 1240 can include circuitry supporting D2D communications between UE 1200 and other compatible devices.
  • radio transceiver 1240 includes circuitry, firmware, etc. necessary for the UE 1200 to communicate with various CDMA2000 networks, according to 3GPP2 standards.
  • the radio transceiver 1240 can be capable of communicating using radio technologies that operate in unlicensed frequency bands, such as IEEE 802.11 WiFi that operates using frequencies in the regions of 2.4, 5.6, and/or 60 GHz.
  • radio transceiver 1240 can include a transceiver that is capable of wired communication, such as by using IEEE 802.3 Ethernet technology. Functionality specific to each of these embodiments can be coupled with and/or controlled by other circuitry in the UE 1200, such as the processor 1210 executing program code stored in program memory 1220 in conjunction with, and/or supported by, data memory 1230.
  • User interface 1250 can take various forms depending on the embodiment of UE 1200 or can be absent from UE 1200 entirely.
  • user interface 1250 can comprise a microphone, a loudspeaker, slidable buttons, depressible buttons, a display, a touchscreen display, a mechanical or virtual keypad, a mechanical or virtual keyboard, and/or any other user-interface features commonly found on mobile phones.
  • the UE 1200 can comprise a tablet computing device including a larger touchscreen display.
  • one or more of the mechanical features of the user interface 1250 can be replaced by comparable or functionally equivalent virtual user interface features (e.g., virtual keypad, virtual buttons, etc.) implemented using the touchscreen display, as familiar to persons of ordinary skill in the art.
  • the UE 1200 can be a digital computing device, such as a laptop computer, desktop computer, workstation, etc. that comprises a mechanical keyboard that can be integrated, detached, or detachable depending on the specific embodiment.
  • a digital computing device can also comprise a touch screen display.
  • Many embodiments of the UE 1200 having a touch screen display can receive user inputs, such as inputs related to exemplary methods described herein or otherwise known to persons of ordinary skill.
  • UE 1200 can include an orientation sensor, which can be used in various ways by features and functions of UE 1200.
  • the UE 1200 can use outputs of the orientation sensor to determine when a user has changed the physical orientation of the UE 1200’ s touch screen display.
  • An indication signal from the orientation sensor can be available to any application program executing on the UE 1200, such that an application program can change the orientation of a screen display e.g., from portrait to landscape) automatically when the indication signal indicates an approximate 90-degree change in physical orientation of the device.
  • the application program can maintain the screen display in a manner that is readable by the user, regardless of the physical orientation of the device.
  • the output of the orientation sensor can be used in conjunction with various embodiments of the present disclosure.
  • a control interface 1260 of the UE 1200 can take various forms depending on the particular embodiment of UE 1200 and of the particular interface requirements of other devices that the UE 1200 is intended to communicate with and/or control.
  • the control interface 1260 can comprise an RS-232 interface, a USB interface, an HDMI interface, a Bluetooth interface, an IEEE (“Firewire”) interface, an I 2 C interface, a PCMCIA interface, or the like.
  • control interface 1260 can comprise an IEEE 802.3 Ethernet interface such as described above.
  • the control interface 1260 can comprise analog interface circuitry including, for example, one or more digital-to-analog converters (DACs) and/or analog-to-digital converters (ADCs).
  • DACs digital-to-analog converters
  • ADCs analog-to-digital converters
  • the UE 1200 can comprise more functionality than is shown in Figure 12 including, for example, a video and/or still-image camera, microphone, media player and/or recorder, etc.
  • radio transceiver 1240 can include circuitry necessary to communicate using additional radio-frequency communication standards including Bluetooth, GPS, and/or others.
  • the processor 1210 can execute software code stored in the program memory 1220 to control such additional functionality. For example, directional velocity and/or position estimates output from a GPS receiver can be available to any application program executing on the UE 1200, including any program code corresponding to and/or embodying any embodiments (e.g., of methods) described herein.
  • FIG. 13 shows a block diagram of an exemplary network node 1300 according to various embodiments of the present disclosure, including those described above with reference to other figures.
  • exemplary network node 1300 can be configured by execution of instructions, stored on a computer-readable medium, to perform operations corresponding to one or more of the exemplary methods described herein.
  • network node 1300 can comprise a base station, eNB, gNB, or one or more components thereof.
  • network node 1300 can be configured as a central unit (CU) and one or more distributed units (DUs) according to NR gNB architectures specified by 3GPP. More generally, the functionally of network node 1300 can be distributed across various physical devices and/or functional units, modules, etc.
  • CU central unit
  • DUs distributed units
  • Network node 1300 can include processor 1310 (also referred to as “processing circuitry”) that is operably connected to program memory 1320 and data memory 1330 via bus 1370, which can include parallel address and data buses, serial ports, or other methods and/or structures known to those of ordinary skill in the art.
  • processor 1310 also referred to as “processing circuitry”
  • bus 1370 can include parallel address and data buses, serial ports, or other methods and/or structures known to those of ordinary skill in the art.
  • Program memory 1320 can store software code, programs, and/or instructions (collectively shown as computer program product (CPP) 1321 in Figure 13) that, when executed by processor 1310, can configure and/or facilitate network node 1300 to perform various operations, including operations corresponding to various exemplary methods described herein.
  • CPP computer program product
  • program memory 1320 can also include software code executed by processor 1310 that can configure and/or facilitate network node 1300 to communicate with one or more other UEs or network nodes using other protocols or protocol layers, such as one or more of the PHY, MAC, RLC, PDCP, SDAP, RRC, and NAS layer protocols standardized by 3 GPP for LTE, LTE-A, and/or NR, or any other higher-layer protocols utilized in conjunction with radio network interface 1340 and/or core network interface 1350.
  • core network interface 1350 can comprise the SI or NG interface and radio network interface 1340 can comprise the Uu interface, as standardized by 3 GPP.
  • Program memory 1320 can also comprise software code executed by processor 1310 to control the functions of network node 1300, including configuring and controlling various components such as radio network interface 1340 and core network interface 1350.
  • Data memory 1330 can comprise memory area for processor 1310 to store variables used in protocols, configuration, control, and other functions of network node 1300.
  • program memory 1320 and data memory 1330 can comprise non-volatile memory (e.g., flash memory, hard disk, etc.), volatile memory (c.g, static or dynamic RAM), network-based (e.g., “cloud”) storage, or a combination thereof.
  • processor 1310 can include multiple individual processors (not shown), each of which implements a portion of the functionality described above. In such case, multiple individual processors may be commonly connected to program memory 1320 and data memory 1330 or individually connected to multiple individual program memories and/or data memories.
  • network node 1300 may be implemented in many different combinations of hardware and software including, but not limited to, application processors, signal processors, general-purpose processors, multi-core processors, ASICs, fixed digital circuitry, programmable digital circuitry, analog baseband circuitry, radio-frequency circuitry, software, firmware, and middleware.
  • Radio network interface 1340 can comprise transmitters, receivers, signal processors, ASICs, antennas, beamforming units, and other circuitry that enables network node 1300 to communicate with other equipment such as, in some embodiments, a plurality of compatible user equipment (UE). In some embodiments, interface 1340 can also enable network node 1300 to communicate with compatible satellites of a satellite communication network. In some embodiments, radio network interface 1340 can comprise various protocols or protocol layers, such as the PHY, MAC, RLC, PDCP, and/or RRC layer protocols standardized by 3GPP for LTE, LTE-A, LTE-LAA, NR, NR-U, etc. improvements thereto such as described herein above; or any other higher-layer protocols utilized in conjunction with radio network interface 1340.
  • protocols or protocol layers such as the PHY, MAC, RLC, PDCP, and/or RRC layer protocols standardized by 3GPP for LTE, LTE-A, LTE-LAA, NR, NR-U, etc. improvements there
  • the radio network interface 1340 can comprise a PHY layer based on OFDM, OFDMA, and/or SC-FDMA technologies.
  • the functionality of such a PHY layer can be provided cooperatively by radio network interface 1340 and processor 1310 (including program code in memory 1320).
  • Core network interface 1350 can comprise transmitters, receivers, and other circuitry that enables network node 1300 to communicate with other equipment in a core network such as, in some embodiments, circuit-switched (CS) and/or packet-switched Core (PS) networks.
  • core network interface 1350 can comprise the SI interface standardized by 3GPP.
  • core network interface 1350 can comprise the NG interface standardized by 3GPP.
  • core network interface 1350 can comprise one or more interfaces to one or more AMFs, SMFs, SGWs, MMEs, SGSNs, GGSNs, and other physical devices that comprise functionality found in GERAN, UTRAN, EPC, 5GC, and CDMA2000 core networks that are known to persons of ordinary skill in the art. In some embodiments, these one or more interfaces may be multiplexed together on a single physical interface.
  • lower layers of core network interface 1350 can comprise one or more of asynchronous transfer mode (ATM), Internet Protocol (IP)-over-Ethernet, SDH over optical fiber, T1/E1/PDH over a copper wire, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art.
  • ATM asynchronous transfer mode
  • IP Internet Protocol
  • SDH over optical fiber
  • T1/E1/PDH over a copper wire
  • microwave radio or other wired or wireless transmission technologies known to those of ordinary skill in the art.
  • network node 1300 can include hardware and/or software that configures and/or facilitates network node 1300 to communicate with other network nodes in a RAN, such as with other eNBs, gNBs, ng-eNBs, en-gNBs, IAB nodes, etc.
  • Such hardware and/or software can be part of radio network interface 1340 and/or core network interface 1350, or it can be a separate functional unit (not shown).
  • such hardware and/or software can configure and/or facilitate network node 1300 to communicate with other RAN nodes via the X2 or Xn interfaces, as standardized by 3 GPP.
  • OA&M interface 1360 can comprise transmitters, receivers, and other circuitry that enables network node 1300 to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of network node 1300 or other network equipment operably connected thereto.
  • Lower layers of OA&M interface 1360 can comprise one or more of asynchronous transfer mode (ATM), Internet Protocol (IP)-over- Ethernet, SDH over optical fiber, T1/E1/PDH over a copper wire, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art.
  • ATM asynchronous transfer mode
  • IP Internet Protocol
  • SDH over optical fiber
  • T1/E1/PDH over optical fiber
  • T1/E1/PDH over a copper wire, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art.
  • one or more of radio network interface 1340, core network interface 1350, and OA&M interface 1360 may be multiplexed together on a single physical interface, such as the examples listed above.
  • FIG 14 is a block diagram of an exemplary communication network configured to provide over-the-top (OTT) data services between a host computer and a user equipment (UE), according to one or more embodiments of the present disclosure.
  • UE 1410 can communicate with radio access network (RAN) 1430 over radio interface 1420, which can be based on protocols described above including, e.g., LTE, LTE-A, and 5G/NR.
  • RAN radio access network
  • UE 1410 can be configured and/or arranged as shown in other figures discussed above.
  • RAN 1430 can include one or more network nodes (e.g., base stations, eNBs, gNBs, controllers, etc.) operable in licensed spectrum bands, as well one or more network nodes operable in unlicensed spectrum (using, e.g., LAA or NR-U technology), such as a 2.4-GHz band and/or a 5-GHz band.
  • network nodes comprising RAN 1430 can cooperatively operate using licensed and unlicensed spectrum.
  • RAN 1430 can include, or be capable of communication with, one or more satellites comprising a satellite access network.
  • RAN 1430 can further communicate with core network 1440 according to various protocols and interfaces described above.
  • one or more apparatus e.g., base stations, eNBs, gNBs, etc.
  • RAN 1430 and core network 1440 can be configured and/or arranged as shown in other figures discussed above.
  • eNBs comprising an evolved UTRAN (E-UTRAN) 1430 can communicate with an evolved packet core (EPC) network 1440 via an SI interface.
  • EPC evolved packet core
  • gNBs and ng-eNBs comprising an NG-RAN 1430 can communicate with a 5GC network 1430 via an NG interface.
  • Core network 1440 can further communicate with an external packet data network, illustrated in Figure 14 as Internet 1450, according to various protocols and interfaces known to persons of ordinary skill in the art. Many other devices and/or networks can also connect to and communicate via Internet 1450, such as exemplary host computer 1460.
  • host computer 1460 can communicate with UE 1410 using Internet 1450, core network 1440, and RAN 1430 as intermediaries.
  • Host computer 1460 can be a server (e.g., an application server) under ownership and/or control of a service provider.
  • Host computer 1460 can be operated by the OTT service provider or by another entity on the service provider’s behalf.
  • host computer 1460 can provide an over-the-top (OTT) packet data service to UE 1410 using facilities of core network 1440 and RAN 1430, which can be unaware of the routing of an outgoing/incoming communication to/from host computer 1460.
  • host computer 1460 can be unaware of routing of a transmission from the host computer to the UE, e.g., the routing of the transmission through RAN 1430.
  • OTT services can be provided using the exemplary configuration shown in Figure 14 including, e.g., streaming (unidirectional) audio and/or video from host computer to UE, interactive (bidirectional) audio and/or video between host computer and UE, interactive messaging or social communication, interactive virtual or augmented reality, cloud gaming, etc.
  • the exemplary network shown in Figure 14 can also include measurement procedures and/or sensors that monitor network performance metrics including data rate, latency and other factors that are improved by embodiments disclosed herein.
  • the exemplary network can also include functionality for reconfiguring the link between the endpoints (e.g., host computer and UE) in response to variations in the measurement results.
  • Such procedures and functionalities are known and practiced; if the network hides or abstracts the radio interface from the OTT service provider, measurements can be facilitated by proprietary signaling between the UE and the host computer.
  • Embodiments described herein provide flexible and efficient techniques to update the timing of the first symbol of each SPS/CG occasion to match an application (e.g., video) traffic periodicity that is not an integer multiple of the transmission slot length, thereby reducing or eliminating accumulated latency.
  • Embodiments can reduce and/or eliminate excess UL or DL transmission latency without requiring frequent signaling to update SPS/CG parameters.
  • embodiments can avoid unnecessary and/or aggressive CG over-provisioning by allocating grants that better match application traffic arrival in the time domain. This can result in reduced application transmission latency and improved quality of experience (QoE), including for XR applications.
  • QoE quality of experience
  • NR UEs e.g., UE 1410
  • gNBs e.g., gNBs comprising RAN 1430
  • these improvements can increase the use of OTT data services - including XR applications - by providing better QoE to OTT service providers and end users. Consequently, this increases the benefits and/or value of such data services to end users and OTT service providers.
  • the term unit can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • device and/or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor.
  • functionality of a device or apparatus can be implemented by any combination of hardware and software.
  • a device or apparatus can also be regarded as an assembly of multiple devices and/or apparatuses, whether functionally in cooperation with or independently of each other.
  • devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.
  • Embodiments of the techniques and apparatus described herein also include, but are not limited to, the following enumerated examples:
  • a method for a user equipment (UE) configured to transmit and receive application data in a wireless network, the method comprising: receiving, from the wireless network, an allocation of a plurality of transmission resources having respective periodic start times; determining modified start times for the respective transmission resources based on the periodic start times and one or more parameters associated with periodic arrivals of application data for transmission or reception; and transmitting or receiving the periodically arriving application data using the allocated transmission resources at the respective modified start times.
  • UE user equipment
  • the one or more parameters include a video frame rate
  • determining the modified start times for the respective transmission resources comprises: calculating respective numbers of transmission timeslots based on a function of the video frame rate and respective indices associated with the respective transmission resources; and adding the respective numbers of transmission timeslots to the periodic start times to obtain the modified start times.
  • the video frame rate is one of the following: 30 Hz, 60 Hz, 90 Hz, or 120 Hz.
  • A6 The method of embodiment Al, further comprising: receiving first downlink control information (DCI) activating the allocation; determining the periodic start times based on a first timing offset included in the first DCI; and subsequently receiving a second DCI updating the allocation, wherein the modified start times are determined for all periodic start times after the second DCI and based on a second timing offset included in the second DCI.
  • DCI downlink control information
  • receiving the first DCI comprises validating one or more bit fields of the first DCI against bit field patterns representative of an activation.
  • receiving the second DCI comprises validating one or more bit fields of the second DCI against bit field patterns representative of an update.
  • receiving the second DCI comprises validating one or more bit fields of the second DCI against bit field patterns representative of an activation; and the second DCI indicates an update based on the first DCI indicating an activation without receiving an intervening DCI indicating a deactivation.
  • receiving the first DCI comprises receiving a DCI of a first format corresponding to an activation; and receiving the second DCI comprises receiving a DCI of a second format corresponding to an update.
  • Al l The method of any of embodiments A1-A10, wherein the allocation of the plurality of transmission resources comprises one of the following: a type-1 configured grant (CG) for uplink (UL) transmission by the UE; a type-2 CG for UL transmission by the UE; or a semi-persistent scheduling (SPS) assignment for downlink (DL) reception by the UE.
  • CG type-1 configured grant
  • SPS semi-persistent scheduling
  • A12 The method of any of embodiments Al-Al l, wherein the duration between successive arrivals of the application data is a non-integer multiple of the duration between successive start times of the allocated transmission resources.
  • a method for a network node configured to transmit and receive application data with a user equipment (UE) in a wireless network, the method comprising: transmitting, to the UE, an allocation of a plurality of transmission resources having respective periodic start times; determining modified start times for the respective transmission resources based on the periodic start times and one or more parameters associated with periodic arrivals of application data for transmission or reception; and transmitting or receiving the periodically arriving application data using the allocated transmission resources at the respective modified start times.
  • UE user equipment
  • the one or more parameters include a video frame rate
  • determining the modified start times for the respective transmission resources comprises: calculating respective numbers of transmission timeslots based on a function of the video frame rate and respective indices associated with the respective transmission resources; and adding the respective numbers of transmission timeslots to the periodic start times to obtain the modified start times.
  • invention B6 further comprising: transmitting first downlink control information (DCI) activating the allocation, wherein the first DCI includes a first timing offset associated with the periodic start times; and subsequently transmitting a second DCI updating the allocation, wherein the second DCI includes a second timing offset associated with the modified start times.
  • DCI downlink control information
  • transmitting the second DCI comprises setting one or more bit fields of the second DCI to bit field patterns representative of an update.
  • transmitting the second DCI comprises setting one or more bit fields of the second DCI to bit field patterns representative of an activation; and the second DCI indicates an update based on the first DCI indicating an activation without transmitting an intervening DCI indicating a deactivation.
  • Bl 1.
  • the allocation of the plurality of transmission resources comprises one of the following: a type-1 configured grant (CG) for uplink (UL) transmission by the UE; a type-2 CG for UL transmission by the UE; or a semi-persistent scheduling (SPS) assignment for downlink (DL) reception by the UE.
  • CG type-1 configured grant
  • SPS semi-persistent scheduling
  • a user equipment configured to transmit and receive application data in a wireless network
  • the UE comprising: radio transceiver circuitry configured to communicate with a network node in the wireless network; and processing circuitry operatively coupled to the radio transceiver circuitry, whereby the processing circuitry and the radio transceiver circuitry are configured to perform operations corresponding to any of the methods of embodiments A1-A12.
  • a user equipment (UE) configured to transmit and receive application data in a wireless network, the UE being further configured to perform operations corresponding to any of the methods of embodiments A1-A12. C3.
  • a non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to transmit and receive application data in a wireless network, configure the UE to perform operations corresponding to any of the methods of embodiments A1-A12.
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry of a user equipment (UE) configured to operate in a wireless network according to periodic discontinuous reception (DRX) cycles comprising periodic DRX on durations, configure the UE to perform operations corresponding to any of the methods of embodiments A1-A12.
  • UE user equipment
  • DRX periodic discontinuous reception
  • a network node configured to transmit and receive application data with a user equipment (UE) in a wireless network, the network node comprising: radio network interface circuitry configured to communicate with the UE; and processing circuitry operatively coupled to the radio network interface circuitry, whereby the processing circuitry and the radio network interface circuitry are configured to perform operations corresponding to any of the methods of embodiments Bl- B12.
  • UE user equipment
  • a network node configured to transmit and receive application data with a user equipment (UE) in a wireless network, the network node being further configured to perform operations corresponding to any of the methods of embodiments B1-B12.
  • UE user equipment
  • a non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of network node configured to transmit and receive application data with a user equipment (UE) in a wireless network, configure the network node to perform operations corresponding to any of the methods of embodiments B1-B12.
  • UE user equipment
  • a computer program product comprising computer-executable instructions that, when executed by processing circuitry of a network node configured to transmit and receive application data with a user equipment (UE) in a wireless network, configure the network node to perform operations corresponding to any of the methods of embodiments B1-B12.
  • UE user equipment

Landscapes

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

Abstract

Certains modes de réalisation concernent des procédés permettant à un équipement d'utilisateur (UE) de recevoir et de transmettre des données d'utilisateur dans un réseau sans fil. De tels procédés consistent à recevoir, à partir d'un nœud de réseau du réseau sans fil, une attribution d'une pluralité de ressources de transmission possédant des temps de démarrage périodiques respectifs. De tels procédés consistent à déterminer des temps de démarrage modifiés relatifs aux ressources de transmission respectives sur la base des temps de démarrage périodiques et d'un ou plusieurs paramètres associés à des données d'application arrivant périodiquement. De tels procédés consistent à transmettre ou à recevoir des données d'application arrivant périodiquement à l'aide des ressources de transmission attribuées aux temps de démarrage modifiés respectifs. D'autres modes de réalisation comprennent des procédés complémentaires pour un nœud de réseau, ainsi que des UE et des nœuds de réseau configurés pour exécuter de tels procédés.
PCT/EP2021/086281 2020-12-17 2021-12-16 Procédés de mise à jour automatique d'autorisation configurée et de synchronisation de planification semi-persistante pour des services xr WO2022129390A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063126824P 2020-12-17 2020-12-17
US63/126,824 2020-12-17

Publications (1)

Publication Number Publication Date
WO2022129390A1 true WO2022129390A1 (fr) 2022-06-23

Family

ID=80111979

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2021/086281 WO2022129390A1 (fr) 2020-12-17 2021-12-16 Procédés de mise à jour automatique d'autorisation configurée et de synchronisation de planification semi-persistante pour des services xr

Country Status (1)

Country Link
WO (1) WO2022129390A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180288746A1 (en) * 2017-04-03 2018-10-04 Huawei Technologies Co., Ltd. Methods and Systems for Resource Configuration of Wireless Communication Systems
US20200092908A1 (en) * 2018-09-19 2020-03-19 Qualcomm Incorporated Sps for signaling with non-integer periodicities

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180288746A1 (en) * 2017-04-03 2018-10-04 Huawei Technologies Co., Ltd. Methods and Systems for Resource Configuration of Wireless Communication Systems
US20200092908A1 (en) * 2018-09-19 2020-03-19 Qualcomm Incorporated Sps for signaling with non-integer periodicities

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ALCARDO ALEX BARAKABITZE ET AL: "QoE Management of Multimedia Streaming Services in Future Networks: A Tutorial and Survey", ARXIV.ORG, CORNELL UNIVERSITY LIBRARY, 201 OLIN LIBRARY CORNELL UNIVERSITY ITHACA, NY 14853, 28 December 2019 (2019-12-28), XP081567539, DOI: 10.1109/COMST.2019.2958784 *

Similar Documents

Publication Publication Date Title
US11917635B2 (en) Network node, user equipment (UE), and associated methods for scheduling of the UE by the network node
US11528637B2 (en) Method and apparatus for wireless communication
CN113287360B (zh) 用于nr用户设备的选择性跨时隙调度
WO2022075912A1 (fr) Temporisateur de rejet de pdcp de groupe pour des services à faible latence
WO2020225031A1 (fr) Découverte et récupération à partir d'une réception de signal de réveil (wus) manqué
WO2018166048A1 (fr) Procédé, dispositif, et système de configuration de direction de transmission
US20210314981A1 (en) Communication system
US20230413178A1 (en) Methods for Discontinuous Reception (DRX) in Conjunction with Guaranteed Low-Latency Services
US20220167266A1 (en) NR User Equipment (UE) Power Savings Reporting and Configuration
JP2022520829A (ja) リミテッドバッファレートマッチングの制約に対する補正
WO2020030801A1 (fr) Ressources temporelles pour des canaux de liaison montante
US20230388066A1 (en) Direct Current (DC) Location Reporting for Intra-Band Uplink Carrier Aggregation (CA)
US20230319607A1 (en) Inter-Cell Group Messages for User Equipment Operating in Multi-Connectivity
EP4315689A1 (fr) Procédés et appareil pour processus harq désactivés
WO2021262071A1 (fr) Demande de répétition automatique (arq) hybride (harq) améliorée pour un réseau sans fil
US20230097818A1 (en) Selective Transmission or Reception for Reducing UE Energy Consumption
WO2022129390A1 (fr) Procédés de mise à jour automatique d'autorisation configurée et de synchronisation de planification semi-persistante pour des services xr
WO2021167518A1 (fr) Structure de trame pour communication sans fil
US20240187143A1 (en) Logical Channel Prioritization within Configured Grants
US20240114367A1 (en) Mobility Measurement Reporting for XR Services

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: 21840537

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: 21840537

Country of ref document: EP

Kind code of ref document: A1