Configuration of communications with multimedia traffic and time division duplex resources

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may obtain a configuration for an external configuration grant (CG) or semi-persistent scheduling (SPS) cycle, where a communication time within the external CG or SPS cycle is a multiple of a time division duplex (TDD) periodicity and is based at least in part on multimedia traffic periodicity. The UE may transmit or receive communications at the communication time. Numerous other aspects are described.

Description

[0001] Cross - Reference to Related Applications

[0002] This patent application claims priority to Provisional Patent Application No. 63 / 383,140, filed on November 10, 2022, entitled "CONFIGURATIONS FOR COMMUNICATIONS WITH MULTIMEDIA TRAFFIC AND TIME DIVISION DUPLEX RESOURCES", and Non - Provisional Patent Application No. 18 / 505,634, filed on November 9, 2023, entitled "CONFIGURATIONS FOR COMMUNICATIONS WITH MULTIMEDIA TRAFFIC AND TIME DIVISION DUPLEX RESOURCES", which patent applications have been assigned to the assignee of this patent application. The disclosure of the prior provisional application is considered part of this patent application and is incorporated herein by reference in its entirety. Technical Field

[0003] Aspects of the present disclosure generally relate to wireless communication and relate to techniques and apparatus for configuring communications using multimedia traffic and time - division duplex resources. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ multiple access techniques capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access techniques include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single - Carrier Frequency Division Multiple Access (SC - FDMA) systems, Time Division - Synchronous Code Division Multiple Access (TD - SCDMA) systems, and Long Term Evolution (LTE). LTE / Advanced LTE is an enhanced collection of Universal Mobile Telecommunications System (UMTS) mobile standards promulgated by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more base stations that support communication for a User Equipment (UE) or multiple UEs. The UE may communicate with the base station via downlink communication and uplink communication. "Downlink" (or "DL") refers to the communication link from the base station to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the base station.

[0006] The above multi-access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at the urban, national, regional, and / or global levels. New Radio (NR) (which may be referred to as 5G) is an enhanced set of LTE mobile standards promulgated by 3GPP. NR is designed to improve spectral efficiency, reduce costs, enhance services, utilize new spectrums, and better integrate with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink, CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, Multiple Input Multiple Output (MIMO) antenna technology, and carrier aggregation, so as to better support mobile broadband Internet access. With the continuous increase in the demand for mobile broadband access, further improvements in LTE, NR, and other radio access technologies are still useful. SUMMARY OF THE INVENTION

[0007] Some aspects described herein relate to a method of wireless communication performed by a User Equipment (UE). The method may include: obtaining a configuration for an external Configuration Grant (CG) or Semi-Persistent Scheduling (SPS) cycle, wherein the communication time within the external CG or SPS cycle is a multiple of a Time Division Duplex (TDD) periodicity and is at least partially based on a multimedia service periodicity. The method may include: transmitting or receiving communication during the communication time.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include: transmitting a configuration for an external CG or SPS cycle, wherein the communication time within the external CG or SPS cycle is a multiple of a TDD periodicity and is at least partially based on a multimedia service periodicity. The method may include: transmitting or receiving communication during the communication time.

[0009] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include: receiving a configuration for the periodicity of a communication time, the communication time being divisible by a TDD periodicity or being a multiple of a TDD periodicity and being at least partially based on a multimedia service periodicity. The method may include: transmitting or receiving communication during the communication time.

[0010] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include: transmitting a configuration for the periodicity of a communication time, the communication time being divisible by a TDD periodicity or being a multiple of a TDD periodicity and being at least partially based on a multimedia service periodicity. The method may include: transmitting or receiving communication during the communication time.

[0011] Some aspects described herein relate to a UE for wireless communication. The user equipment may include: a memory; and one or more processors coupled to the memory. The one or more processors may be configured to obtain a configuration for an external CG or SPS cycle, wherein the communication time within the external CG or SPS cycle is a multiple of the TDD periodicity and is at least partially based on the multimedia traffic periodicity. The one or more processors may be configured to transmit or receive communication at the communication time.

[0012] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit a configuration for an external CG or SPS cycle, wherein the communication time within the external CG or SPS cycle is a multiple of the TDD periodicity and is at least partially based on the multimedia traffic periodicity. The one or more processors may be configured to transmit or receive communication at the communication time.

[0013] Some aspects described herein relate to a UE for wireless communication. The user equipment may include: a memory; and one or more processors coupled to the memory. The one or more processors may be configured to receive a configuration for the periodicity of the communication time, the communication time being divisible by the TDD periodicity or being a multiple of the TDD periodicity and being at least partially based on the multimedia traffic periodicity. The one or more processors may be configured to transmit or receive communication at the communication time.

[0014] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit a configuration for the periodicity of the communication time, the communication time being divisible by the TDD periodicity or being a multiple of the TDD periodicity and being at least partially based on the multimedia traffic periodicity. The one or more processors may be configured to transmit or receive communication at the communication time.

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to obtain a configuration for an external CG or SPS cycle, wherein the communication time within the external CG or SPS cycle is a multiple of the TDD periodicity and is at least partially based on the multimedia traffic periodicity. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit or receive communication at the communication time.

[0016] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, can cause the network entity to send a configuration for an external CG or SPS cycle, wherein a communication time within the external CG or SPS cycle is a multiple of a TDD periodicity and is at least partially based on a multimedia service periodicity. The set of instructions, when executed by one or more processors of the network entity, can cause the network entity to send or receive communication at the communication time.

[0017] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, can cause the UE to receive a configuration for a periodicity of a communication time, the communication time being divisible by a TDD periodicity or being a multiple of a TDD periodicity and being at least partially based on a multimedia service periodicity. The set of instructions, when executed by one or more processors of the UE, can cause the UE to send or receive communication at the communication time.

[0018] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, can cause the network entity to send a configuration for a periodicity of a communication time, the communication time being divisible by a TDD periodicity or being a multiple of a TDD periodicity and being at least partially based on a multimedia service periodicity. The set of instructions, when executed by one or more processors of the network entity, can cause the network entity to send or receive communication at the communication time.

[0019] Some aspects described herein relate to an apparatus for wireless communication. The apparatus can include means for obtaining a configuration for an external CG or SPS cycle, wherein a communication time within the external CG or SPS cycle is a multiple of a TDD periodicity and is at least partially based on a multimedia service periodicity. The apparatus can include means for sending or receiving communication at the communication time.

[0020] Some aspects described herein relate to an apparatus for wireless communication. The apparatus can include means for sending a configuration for an external CG or SPS cycle, wherein a communication time within the external CG or SPS cycle is a multiple of a TDD periodicity and is at least partially based on a multimedia service periodicity. The apparatus can include means for sending or receiving communication at the communication time.

[0021] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a periodic configuration for a communication time that is divisible by or a multiple of a TDD period and is at least partially based on a multimedia service period. The apparatus may include means for transmitting or receiving a communication at the communication time.

[0022] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting a periodic configuration for a communication time that is divisible by or a multiple of a TDD period and is at least partially based on a multimedia service period. The apparatus may include means for transmitting or receiving a communication at the communication time.

[0023] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, UEs, base stations, network entities, wireless communication devices, and / or processing systems as fully described herein with reference to the figures and the specification and illustrated in the figures and the specification.

[0024] The features and technical advantages of examples in accordance with the present disclosure have been outlined rather broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both as to their organization and operation methods, as well as associated advantages, will be better understood by considering the following description in conjunction with the accompanying figures. Each of the figures provided in the figures is for purposes of illustration and description and not as a definition of the limits of the claims.

[0025] Although aspects are described herein by way of illustration of some examples, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects can be implemented via an integrated chip implementation or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features can include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals can include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] To enable a more particular understanding of the above-described features of the present disclosure, a more specific description may be obtained by reference to aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered limiting of its scope, as the specification may admit other equally effective aspects. Like reference numerals in different drawings may identify the same or similar elements.

[0027] Figure 1 is a diagram illustrating an example of a wireless network in accordance with the present disclosure.

[0028] Figure 2 is a diagram illustrating an example of a network entity communicating with a user equipment (UE) in a wireless network in accordance with the present disclosure.

[0029] Figure 3 is a diagram illustrating an example of a decomposed base station in accordance with the present disclosure.

[0030] Figure 4 is a diagram illustrating an example of a discontinuous reception (DRX) cycle in accordance with the present disclosure.

[0031] Figure 5 is a diagram illustrating an example of downlink semi-persistent scheduling (SPS) communication and an example of uplink configured grant (CG) communication in accordance with the present disclosure.

[0032] Figure 6It is a diagram illustrating an example in which CG or SPS communication is periodically misaligned with a multimedia service according to the present disclosure.

[0033] Figure 7 It is a diagram illustrating an example in which CG or SPS communication is aligned with both a multimedia service periodically and a time division duplex (TDD) mode according to the present disclosure.

[0034] Figure 8 It is a diagram illustrating an example of CG type 1 with a TDD mode according to the present disclosure.

[0035] Figure 9 It is a diagram illustrating an example associated with a communication time using a multimedia service periodically and a TDD mode according to the present disclosure.

[0036] Figure 10A and Figure 10B It is a diagram illustrating an example in which CG or SPS communication is aligned with both a multimedia service periodically and a TDD mode according to the present disclosure.

[0037] Figure 11 It is a diagram illustrating an example of CG type 2 with a TDD mode according to the present disclosure.

[0038] Figure 12 It is a diagram illustrating an example of an external CG or SPS cycle for a TDD mode according to the present disclosure.

[0039] Figure 13 It is a diagram illustrating an example of extending an external CG or SPS cycle according to the present disclosure.

[0040] Figures 14A to 14E It is a table illustrating an example of a sub-optimal configuration for CG or SPS according to the present disclosure.

[0041] Figure 15 It is a diagram illustrating an example process, such as performed by a UE, according to the present disclosure.

[0042] Figure 16 It is a diagram illustrating an example process, such as performed by a network entity, according to the present disclosure.

[0043] Figure 17 It is a diagram illustrating an example process, such as performed by a UE, according to the present disclosure.

[0044] Figure 18 It is a diagram illustrating an example process, such as performed by a network entity, according to the present disclosure.

[0045] Figure 19 It is a diagram of an example apparatus for wireless communication according to the present disclosure.

[0046] Figure 20 FIG. Figure 20 is a diagram of an example apparatus for wireless communication in accordance with the present disclosure. DETAILED DESCRIPTION

[0047] Aspects of the present disclosure are described more fully hereinafter with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art. Those skilled in the art will understand that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the present disclosure. For example, any number of the aspects set forth herein may be used to implement an apparatus or practice a method. In addition, the scope of the present disclosure is intended to cover such apparatus or methods practiced using other structures, functionality, or a combination of structures and functionality in addition to or different from the aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0048] Several aspects of a telecommunications system will now be presented with reference to various apparatuses and techniques. These apparatuses and techniques will be described in the following detailed description and illustrated in the drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0049] Although terms that are generally associated with 5G or new radio (NR) radio access technology (RAT) may be used herein to describe aspects, aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RAT (e.g., 6G).

[0050] Figure 1FIG. is an illustration of an example of a wireless network 100 in accordance with the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, and so on. The wireless network 100 may include a UE 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e). The wireless network 100 may also include one or more network entities, such as base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d) and / or other network entities. The base station 110 is a network entity that communicates with the UE 120. The base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of the base station 110 and / or the base station subsystem serving that coverage area, depending on the context in which the term is used.

[0051] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs 120 having a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 having a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 associated with the femto cell (e.g., UEs 120 in a Closed Subscriber Group (CSG)). The base station 110 for a macro cell may be referred to as a macro base station. The base station 110 for a pico cell may be referred to as a pico base station. The base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 the example shown, BS110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS110c may be a femto base station for femto cell 102c. A base station may support one or more (e.g., three) cells.

[0052] In some examples, the cell may not necessarily be fixed, and the geographical area of the cell may move according to the location of the moving base station 110 (e.g., mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or interconnected to one or more other base stations 110 or network entities in the wireless network 100 using any suitable transport network via various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0053] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more of their components. For example, in some aspects, the "base station" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non RT) RIC, or a combination thereof. The network entity may be configured to utilize a protocol stack physically or logically distributed between two or more nodes (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, the term "base station" or "network entity" may refer to a single device configured to perform one or more functions (such as those described herein in connection with base station 110). In some aspects, the term "base station" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of several different devices (which may be located at the same geographical location or different geographical locations) may be configured to perform at least a part of a function, or repeat the execution of at least a part of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one base station function among base station functions, rather than another base station function. In this way, a single device may include more than one base station.

[0054] The wireless network 100 may include one or more relay stations. A relay station is a network entity capable of receiving a transmission of data from an upstream station (e.g., a network entity or UE 120) and transmitting the data to a downstream station (e.g., UE 120 or network entity). A relay station may be a UE 120 capable of relaying transmissions for other UEs 120. In Figure 1In the example shown, BS110d (e.g., a relay base station) can communicate with BS110a (e.g., a macro base station) and UE 120d to facilitate communication between BS110a and UE 120d. A base station 110 that performs relay communication may be referred to as a relay station, a relay base station, a relay, etc.

[0055] The wireless network 100 can be a heterogeneous network that has network entities including different types of BSs, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmission power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmission power level (e.g., 5 watts to 40 watts), while pico base stations, femto base stations, and relay base stations may have lower transmission power levels (e.g., 0.1 watt to 2 watts).

[0056] The network controller 130 can be coupled to or communicate with a set of network entities and can provide coordination and control for these network entities. The network controller 130 can communicate with the base stations 110 via a backhaul communication link. The network entities can also communicate directly with each other or indirectly via wireless or wired backhaul communication links.

[0057] UEs 120 can be dispersed throughout the wireless network 100, and each UE 120 can be stationary or mobile. The UE 120 can include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. The UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, a superbook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0058] Some UEs 120 may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. The MTC UE and / or eMTC UE may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with network entities, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices and / or may be implemented as narrowband IoT (NB-IoT) devices. Some UEs 120 may be considered customer premise equipment. The UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and / or memory components. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0059] Generally, any number of wireless networks 100 may be deployed in a given geographical area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. The RAT may be referred to as a radio technology, an air interface, etc. The frequency may be referred to as a carrier, a frequency channel, etc. Each frequency in a given geographical area may support a single RAT to avoid interference between wireless networks of different RATs. In some cases, an NR or 5G RAT network may be deployed.

[0060] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., communicate with each other without using a network entity as an intermediary). For example, the UE 120 may use peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, or vehicle-to-pedestrian (V2P) protocol), and / or a mesh network to communicate. In such examples, the UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the base station 110.

[0061] Devices of the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, channels, etc. according to frequency or wavelength. For example, devices of the wireless network 100 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency bands have been identified as Frequency Range Designation FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is usually (interchangeably) referred to as the "sub-6 GHz" band. Regarding FR2, a similar naming issue sometimes occurs, which is usually (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0062] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified operating frequency bands for these mid-band frequencies as Frequency Range Designation FR3 (7.125 GHz - 24.25 GHz). Bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the characteristics of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating frequency bands have been identified as Frequency Range Designation FR4a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0063] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" etc. is used in this article, this term can generally represent frequencies that can be below 6 GHz, can be within FR1, or can include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" etc. is used in this article, this term can generally represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or can be within the EHF band. Considering that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the technologies described in this article are applicable to those modified frequency ranges.

[0064] In some aspects, a UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may obtain a configuration for an external configuration grant (CG) or semi-persistent scheduling (SPS) cycle, where the communication time within the external CG or SPS cycle is a multiple of a time-division duplex (TDD) periodicity and is at least partially based on a multimedia traffic periodicity. The communication manager 140 may send or receive communications during the communication time.

[0065] In some aspects, the communication manager 140 may receive a configuration for the periodicity of a communication time that is divisible by or is a multiple of a TDD periodicity and is at least partially based on a multimedia traffic periodicity. The communication manager 140 may send or receive communications during the communication time. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0066] In some aspects, a network entity (e.g., base station 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a configuration for an external CG or SPS cycle, where the communication time within the external CG or SPS cycle is a multiple of a TDD periodicity and is at least partially based on a multimedia traffic periodicity. The communication manager 150 may send or receive communications during the communication time.

[0067] In some aspects, the communication manager 150 may send a configuration for the periodicity of a communication time that is divisible by or is a multiple of a TDD periodicity and is at least partially based on a multimedia traffic periodicity; and send or receive communications during the communication time. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0068] As indicated above, Figure 1 is provided as an example. Other examples may be different from the examples described with respect to Figure 1 the examples described.

[0069] Figure 2 is a diagram illustrating example 200 of communication between a network entity (e.g., base station 110) and a UE 120 in a wireless network 100 in accordance with the present disclosure. The base station 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0070] At base station 110, transmit processor 220 may receive data destined for UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCSs) for UE 120 at least in part based on one or more channel quality indicators (CQIs) received from UE 120. Base station 110 may process (e.g., encode and modulate) data for UE 120 at least in part based on the MCS selected for UE 120, and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signal (CRS) or demodulation reference signal (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). If applicable, transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, overhead symbols, and / or reference symbols, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232. Each modem 232 may process the corresponding output symbol stream (e.g., for OFDM) using the corresponding modulator component to obtain an output sample stream. Each modem 232 may also process the output sample stream (e.g., convert to analog, amplify, filter, and / or up-convert) using the corresponding modulator component to obtain a downlink signal. Modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).

[0071] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use the demodulator component to further process the input samples (e.g., for OFDM) to obtain the received symbols. The MIMO detector 256 may obtain the received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide the detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide the decoded data for the UE 120 to the data sink 260, and may provide the decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine reference signal received power (RSRP) parameters, received signal strength indicator (RSSI) parameters, reference signal received quality (RSRQ) parameters, and / or CQI parameters, etc. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0072] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with network entities via the communication unit 294.

[0073] One or more antennas (e.g., antennas 234a through 234t and / or antennas 252a through 252r) may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc., or may be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, one or more sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), one or more sets of coplanar antenna elements, one or more sets of non-coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmit and / or receive components (such as Figure 2 one or more components) of

[0074] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-coded by the TX MIMO processor 266 when applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network entity. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and / or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., the controller / processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to Figures 4 to 20 ).

[0075] At the network entity (e.g., the base station 110), the uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., the demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 when applicable, and further processed by the receive processor 238 to obtain the decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network entity may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network entity may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communication. In some examples, the modem 232 of the network entity may include a modulator and a demodulator. In some examples, the network entity includes a transceiver. The transceiver may include any combination of the antenna 234, the modem 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and / or the TX MIMO processor 230. The transceiver may be used by a processor (e.g., the controller / processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to Figures 4 to 20 ).

[0076] As described in more detail elsewhere herein, a controller / processor of a network entity (e.g., controller / processor 240 of base station 110), a controller / processor 280 of UE 120, and / or Figure 2 any other component of may perform one or more techniques associated with configuring communications using multimedia periodicity and TDD mode. For example, controller / processor 240 of base station 110, controller / processor 280 of UE 120, and / or Figure 2 any other component of may execute or direct, for example Figure 15 process 1500 of, Figure 16 process 1600 of, Figure 17 process 1700 of, Figure 18 process 1800 of, and / or operations of other processes as described herein. Memories 242 and 282 may store data and program code for the network entity and UE 120, respectively. In some examples, memories 242 and / or 282 may include non-transitory computer-readable media storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, when executed (e.g., directly executed, or after compilation, conversion, and / or interpretation) by one or more processors of the network entity and / or UE 120, the one or more instructions may cause the one or more processors, UE 120, and / or network entity to execute or direct, for example Figure 15 process 1500 of, Figure 16 process 1600 of, Figure 17 process 1700 of, Figure 18 process 1800 of, and / or operations of other processes described herein. In some examples, executing the instructions may include running the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions, etc.

[0077] In some aspects, a UE (e.g., UE 120) includes components for obtaining a configuration for an external CG or SPS cycle, where communication time within the external CG or SPS cycle is a multiple of TDD periodicity and is at least partially based on multimedia traffic periodicity; and / or components for sending or receiving communications during the communication time. Components for a UE to perform the operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0078] In some aspects, the UE includes components for receiving a configuration of a periodicity for a communication time that is divisible by or is a multiple of the TDD periodicity and is at least partially based on a multimedia service periodicity; and / or components for transmitting or receiving communications at the communication time.

[0079] In some aspects, a network entity (e.g., base station 110) includes components for transmitting a configuration for an external CG or SPS cycle, where the communication time within the external CG or SPS cycle is a multiple of the TDD periodicity and is at least partially based on a multimedia service periodicity; and / or components for transmitting or receiving communications at the communication time. In some aspects, the components for the network entity to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0080] In some aspects, the network entity includes components for transmitting a configuration of a periodicity for a communication time that is divisible by or is a multiple of the TDD periodicity and is at least partially based on a multimedia service periodicity; and / or components for transmitting or receiving communications at the communication time.

[0081] Although Figure 2 the blocks in are illustrated as different components, the functions described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functions described for transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0082] As indicated above, Figure 2 is provided as an example. Other examples may be different from the example described with respect to Figure 2 the example.

[0083] Figure 3 is a diagram illustrating an example of a decomposed base station 300 according to the present disclosure.

[0084] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, radio access network (RAN) nodes, core network nodes, network elements, or network equipment (such as a base station, or one or more units (or one or more components) that perform base station functionality) can be implemented in a centralized architecture or a split architecture. For example, a BS (such as Node B, evolved Node B (eNB), NR BS, 5G NB, access point (AP), TRP, or cell, etc.) can be implemented as a centralized base station (also referred to as a stand-alone BS or a monolithic BS) or a split base station.

[0085] A centralized base station can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A split base station can be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. A DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit (e.g., virtual central unit (VCU), virtual distributed unit (VDU), or virtual radio unit (VRU)).

[0086] The operation of the base station type or the network design can consider the aggregation characteristics of the base station functionality. For example, a split base station can be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as cloud radio access network (C-RAN)). The split can include distributing functions across two or more units at various physical locations, as well as virtually distributing the functions of at least one unit, which can achieve flexibility in network design. The various units of a split base station or a split RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0087] The architecture of the split base station 300 may include one or more CUs 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 through one or more split base station units (such as the near-RTRIC 325 via the E2 link, or the non-RT RIC 315 associated with the Service Management and Orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via a corresponding midhaul link (such as the F1 interface). The DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. The fronthaul link, midhaul link, and backhaul link may generally be referred to as "communication links". The RU 340 may communicate with the corresponding UE 120 via one or more RF access links. In some aspects, the UE 120 may be served simultaneously by multiple RUs 340. The DU 330 and RU 340 may also be referred to as "O-RAN DU (O-DU)" and "O-RAN RU (O-RU)", respectively. A network entity may include a CU, a DU, an RU, or any combination of a CU, a DU, and an RU. A network entity may include a split base station or one or more components of a split base station, such as a CU, a DU, an RU, or any combination of a CU, a DU, and an RU. A network entity may also include one or more of the following: a TRP, a relay station, a passive device, a Smart Reflecting Surface (IRS), or other components that may provide a network interface for or serve a UE, a mobile station, a sensor / actuator, or other wireless device.

[0088] Each of the units (e.g., CU 310, DU 330, RU 340, as well as the near-RTRIC 325, non-RT RIC 315, and SMO framework 305) may include one or more interfaces or be coupled to one or more interfaces, which are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or the associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, these units may include a wired interface that is configured to receive or transmit signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), which is configured to receive or transmit signals to one or more of the other units on a wireless transmission medium, or both.

[0089] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented using an interface configured to signal with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some embodiments, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface such as the E1 interface. As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0090] The DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of the following, at least in part, according to a functional split (such as the functional split defined by 3GPP): Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high Physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, the DU 330 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to signal with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0091] Lower layer functionality may be implemented by one or more RUs 340. In some deployments, the RUs 340 controlled by the DU 330 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.) or both, at least in part based on a functional split (such as a lower layer functional split). In such an architecture, the RUs 340 may be implemented to handle over-the-air (OTA) communication with one or more UEs 120. In some embodiments, the real-time and non-real-time aspects of the control plane and user plane communication with the RUs 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0092] The SMO framework 305 can be configured to support the RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, and these dedicated physical resources can be managed via operation and maintenance interfaces (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 390) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, the CU 310, DU 330, RU 340, and near RT RIC 325. In some specific implementations, the SMO framework 305 can communicate with the hardware aspect of the 4G RAN (such as the Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 can communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0093] The non-RT RIC 315 can be configured to include logical functions that can enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near RT RIC 325 (such as via the A1 interface). The near RT RIC 325 can be configured to include logical functions that can enable near-real-time control and optimization of RAN elements and resources through interfaces (such as via the E2 interface) via data collection and actions, and this interface connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB to the near RT RIC 325.

[0094] In some specific implementations, to generate the AI / ML models to be deployed in the near RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information can be utilized by the near RT RIC 325 and can be received from non-network data sources or from network functions at the SMO framework 305 or at the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions via the SMO framework 305 (such as reconfiguration via O1) or via creating RAN management policies (such as A1 policies).

[0095] As indicated above, Figure 3 is provided as an example. Other examples may be different from the examples described with respect to Figure 3 description.

[0096] Figure 4 is a diagram illustrating Example 400 of a discontinuous reception (DRX) cycle according to the present disclosure. Example 400 shows a DRX cycle associated with an extended reality (XR) traffic burst between an edge server 402 (via a network entity 404) and a UE (such as an XR device 406).

[0097] Some UEs (including devices for XR) may require low-latency traffic to and from an edge server or a cloud environment. An XR device can be an augmented reality (AR) glasses device, a virtual reality (VR) glasses device, a gaming device, an educational device, an industrial device, or other devices providing AR and / or VR. In one or more examples, a UE such as an XR device may operate using battery power. The consumption of battery power can be reduced by restricting the amount of active time of the UE's processing resources for computing and power consumption.

[0098] In one or more examples, an XR device 406 (e.g., UE 120) may communicate with an edge server 402 (e.g., edge server 160) or a cloud environment via a network entity 404 (e.g., base station 110). By offloading some computations to the edge server 402, the XR device 406 may save processing resources. In one scenario, the XR device 406 may share the computation of an application with the edge server 402 on the other side of the network entity 404. The edge server 402 may render video frames (such as intra-coded (I) frames and predicted (P) frames), encode the video frames, align the video frames with user pose information, and perform other related computations. However, this means that there may be more traffic between the XR device 406 and the edge server 402, which will cause the XR device 406 to consume more power and signaling resources. XR downlink traffic (e.g., video frames) may have a periodic pattern corresponding to the frame rate of the transmitted video data (e.g., H.264 / H.265 encoded video).

[0099] The XR device 406 may have a limited battery capacity while being expected to have a smart phone's battery life (e.g., all-day usage). Even if the XR device 406 is connected to a smart phone and uses the same smart phone battery, battery power is still an issue. The power consumption of the XR device may be limited and may result in an uncomfortable user experience and / or a short battery life. The power consumption may be reduced by restricting the amount of active time of the processing resources of the XR device 406 for computations and power consumption. Thus, some wireless communication systems may support a DRX mode for the XR device 406 or other UEs.

[0100] According to one or more examples, a UE such as the XR device 406 may use the DRX mode to save power. A UE in the DRX mode may transition between a sleep state for power saving and an active state for data transmission and reception. In one or more examples, a UE in the sleep state may turn off the radio component and one or more other components or functions of the UE. Turning off or disconnecting the radio component may include removing power from the radio component such that the radio component does not fully operate or does not operate at full power. In one or more examples, the UE may wake up to the active state by turning on the radio component and one or more other components or functions of the UE. Other components may include, for example, buffers, timers, memories, and / or processors. The functions of the UE may include, for example, communication, application operation, and / or configuration. Turning on or connecting the radio component may include providing power to the radio component such that the radio component fully operates (e.g., all applications or functions have sufficient power to execute) and / or operates at full power. As used herein, the active state for data transmission and reception may be referred to as the DRX "on duration".

[0101] A service (e.g., an XR service) may have multiple data streams. The XR stream may include some control information. In an example, such a service may involve periodic data bursts that have a certain time jitter when they arrive. The jitter time may include variations in the arrival time caused by the environment, changes in the propagation time, or changes in time introduced by radio components or processors. Additionally, the packet size and the number of packets for a burst may vary for different bursts. Additionally, multiple service streams can be used for the downlink with different periodicities. Therefore, configuring multiple DRX cycles with different periodicities for multiple streams can enable the UE to sleep for less time, which consumes power. Being in an active state consumes power.

[0102] A UE (such as the XR device 406) in DRX mode can transition between a sleep state for power saving and an active state for data transmission and reception. UEs using different DRX cycles (different periods) can have inconsistent cycle durations within the DRX period. Such inconsistent cycle durations can provide a DRX on-duration aligned with the periodicity of the downlink traffic to the UE. For low-latency applications, the DRX cycle and the start offset of the DRX cycle will be aligned with the downlink traffic arrival time.

[0103] For example, a UE such as the XR device 406 can serve a user and enter a short sleep state within the DRX cycle and between video frames. The XR device 406 and the edge server 402 can attempt to align the uplink DRX cycle and the downlink DRX cycle as part of connected DRX (C-DRX), which is the DRX operation when the XR device 406 is in the RRC connected state. However, there is a DRX multimedia timing mismatch that prevents such alignment and the successful use of C-DRX.

[0104] Example 400 shows the arrival 405 of downlink traffic bursts of an XR service on the top timeline, and the arrival of the downlink traffic bursts may include several downlink traffic bursts 410 sent according to a periodic pattern. Example 400 also shows a DRX configuration 415 of a DRX cycle with a periodic on-duration at the on-duration timing 420 on the bottom timeline. The downlink traffic bursts 410 may include, for example, XR downlink traffic with a periodic pattern corresponding to the frame rate of the transmitted data (e.g., video after H.264 / H.265 encoding). The update rate of the XR service can be, for example, 120 Hertz (Hz) or 60 Hz, resulting in downlink traffic burst arrival periodicities of 8.333 milliseconds (ms) or 16.667 ms, respectively. The DRX configuration 415 may have on-duration timings 415-a to 415-d corresponding to the downlink traffic bursts 410-a to 410-d, respectively.

[0105] The DRX configuration may have one millisecond as the finest granularity of the DRX cycle, and the start of the on-duration may be aligned with the millisecond time boundary (shown by the arrow below the bottom timeline). That is, each on-duration occasion 420 of the DRX cycle is aligned with a millisecond integer value rather than a fraction of a millisecond. This may result in a partial millisecond difference between the start of the DRX on-duration and the start of the downlink traffic burst of the XR service. The start of each downlink traffic burst 410 is shown by a dashed line. There may be multiple partial millisecond differences between the start of the downlink traffic burst and the start of the DRX on-duration. For example, the dashed line for the start of downlink traffic burst 410-b is not aligned with the start of on-duration occasion 420-b. These partial millisecond differences may compound with each on-duration of the DRX cycle, causing the DRX cycle to be misaligned with the XR service periodicity. For example, the start of the downlink traffic burst (dashed line) may drift (the difference increases) to the middle of the DRX on-duration occasion, as shown by the dashed line of traffic burst 410-c passing through the middle of on-duration occasion 420-c. This results in an increase in latency and power consumption.

[0106] As indicated above, Figure 4 is provided as an example. Other examples may be different from the example described for Figure 4 is different.

[0107] Figure 5 FIG. 500 illustrates an example of downlink SPS communication and FIG. 510 illustrates an example of uplink CG communication in accordance with the present disclosure. SPS communication may include periodic downlink communication configured for a UE such that a network node does not need to (e.g., directly or via one or more network nodes) send separate downlink control information (DCI) to schedule each downlink communication, thereby saving signaling overhead. CG communication may include periodic uplink communication configured for a UE such that a network node does not need to (e.g., directly or via one or more network nodes) send separate DCI to schedule each uplink communication, thereby saving signaling overhead.

[0108] In addition to the DRX-on duration, CG communication and SPS communication may also be periodically misaligned with XR services. As shown in Example 500, the UE may be configured with an SPS configuration for SPS communication. For example, the UE may receive the SPS configuration via an RRC message sent by a network node (e.g., sent directly to the UE or via one or more network nodes). The SPS configuration may indicate the resource allocation associated with SPS downlink communication (e.g., in the time domain, frequency domain, spatial domain, and / or code domain) and the periodicity with which the resource allocation is repeated, such that the scheduled SPS opportunity 505 for the UE repeats periodically. The SPS configuration may also configure for the UE a hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback resource to send HARQ-ACK feedback for the SPS physical downlink shared channel (PDSCH) communication received in the SPS opportunity 505. For example, the SPS configuration may indicate a PDSCH-to-HARQ feedback timing value, which may be referred to as a K1 value in a wireless communication standard (e.g., a 3GPP standard).

[0109] The network node may send an SPS activation DCI to the UE (e.g., directly or via one or more network nodes) to activate the SPS configuration for the UE. The network node may indicate communication parameters, such as MCS, resource block (RB) allocation, and / or antenna port, in the SPS activation DCI for the SPS PDSCH communication to be sent in the scheduled SPS opportunity 505. The UE may start monitoring the scheduled SPS opportunity 505 at least partially based on receiving the SPS activation DCI. For example, starting from the next scheduled SPS opportunity 505 after receiving the SPS activation DCI, the UE may monitor the scheduled SPS opportunity 505 to decode the PDSCH communication using the communication parameters indicated in the SPS activation DCI. The UE may prohibit monitoring the configured SPS opportunity 505 before receiving the SPS activation DCI.

[0110] The network node may send an SPS reactivation DCI to the UE (e.g., directly or via one or more network nodes) to change the communication parameters for the SPS PDSCH communication. At least partially based on receiving the SPS reactivation DCI, the UE may start monitoring the scheduled SPS opportunity 505 using the communication parameters indicated in the SPS reactivation DCI. For example, starting from the next scheduled SPS opportunity 505 after receiving the SPS reactivation DCI, the UE may monitor the scheduled SPS opportunity 505 to decode the PDSCH communication based on the communication parameters indicated in the SPS reactivation DCI.

[0111] In some cases, such as when there is no downlink traffic to be sent to the UE, the network node may send an SPS cancellation DCI to the UE (e.g., directly or via one or more network nodes) to temporarily cancel or deactivate one or more subsequent SPS occasions 505 for the UE. The SPS cancellation DCI may deactivate only a subsequent single SPS occasion 505 or subsequent N SPS occasions 505 (where N is an integer). The SPS occasion 505 after one or more (e.g., N) SPS occasions 505 after the SPS cancellation DCI may remain active. At least partially based on receiving the SPS cancellation DCI, the UE may refrain from monitoring one or more (e.g., N) SPS occasions 505 after receiving the SPS cancellation DCI. As shown in example 500, the SPS cancellation DCI cancels one subsequent SPS occasion 505 for the UE. After the SPS occasion 505 (or N SPS occasions) after receiving the SPS cancellation DCI, the UE may automatically resume monitoring scheduled SPS occasions 505.

[0112] The network node may send an SPS release DCI to the UE (e.g., directly or via one or more network nodes) to deactivate the SPS configuration for the UE. The UE may stop monitoring scheduled SPS occasions 505 at least partially based on receiving the SPS release DCI. For example, the UE may refrain from monitoring any scheduled SPS occasions 505 until the UE receives another SPS activation DCI. However, while the SPS cancellation DCI may deactivate only a subsequent single SPS occasion 505 or subsequent N SPS occasions 505, the SPS release DCI deactivates all subsequent SPS occasions 505 for a given SPS configuration for the UE until that given SPS configuration is reactivated by a new SPS activation DCI.

[0113] As shown in example 510, the UE may be configured with a CG configuration for CG communication. For example, the UE may receive the CG configuration via an RRC message sent by a network node (e.g., sent directly to the UE or via one or more network nodes). The CG configuration may indicate resource allocation associated with CG uplink communication (e.g., in the time domain, frequency domain, spatial domain, and / or code domain) and the periodicity with which the resource allocation is repeated, such that scheduled CG occasions 515 for the UE occur periodically. In some examples, the CG configuration may identify a resource pool or resource pools available for the UE for uplink transmission. The CG configuration may configure contention-free CG communication (e.g., where resources are dedicated for the UE to transmit uplink communication) or contention-based CG communication (e.g., where the UE contends for access to the channel in a configured resource allocation, such as by using a channel access procedure or a channel sensing procedure).

[0114] A network node may send a CG activation DCI to a UE (e.g., directly or via one or more network nodes) to activate a CG configuration for the UE. The network node may indicate communication parameters, such as MCS, RB allocation, and / or antenna ports, in the CG activation DCI for CG physical uplink shared channel (PUSCH) communication to be sent in the scheduled CG occasion 515. The UE may start transmitting in the CG occasion 515 at least partially based on receiving the CG activation DCI. For example, starting from the next scheduled CG occasion 515 after receiving the CG activation DCI, the UE may transmit PUSCH communication in the scheduled CG occasion 515 using the communication parameters indicated in the CG activation DCI. The UE may prohibit transmitting in the configured CG occasion 515 before receiving the CG activation DCI.

[0115] A network node may send a CG reactivation DCI to a UE (e.g., directly or via one or more network nodes) to change the communication parameters for CG PUSCH communication. At least partially based on receiving the CG reactivation DCI, the UE may start transmitting in the scheduled CG occasion 515 using the communication parameters indicated in the CG reactivation DCI. For example, starting from the next scheduled CG occasion 515 after receiving the CG reactivation DCI, the UE may transmit PUSCH communication in the scheduled CG occasion 515 at least partially based on the communication parameters indicated in the CG reactivation DCI.

[0116] In some cases, such as when the network node needs to override the scheduled CG communication for higher-priority communication, the network node may send a CG cancellation DCI to the UE (e.g., directly or via one or more network nodes) to temporarily cancel or deactivate one or more subsequent CG occasions 515 for the UE. The CG cancellation DCI may deactivate only one subsequent CG occasion 515 or N subsequent CG occasions 515 (where N is an integer). The CG occasion 515 after one or more (e.g., N) CG occasions 515 after the CG cancellation DCI may remain active. At least partially based on receiving the CG cancellation DCI, the UE may prohibit transmitting in one or more (e.g., N) CG occasions 515 after receiving the CG cancellation DCI. As shown in example 510, the CG cancellation DCI cancels one subsequent CG occasion 515 for the UE. After the CG occasion 515 (or N CG occasions) after receiving the CG cancellation DCI, the UE may automatically resume transmitting in the scheduled CG occasion 515.

[0117] A network node may send a CG release DCI to a UE (e.g., directly or via one or more network nodes) to deactivate the CG configuration for the UE. The UE may stop transmitting in the scheduled CG occasion 515 at least partially based on receiving the CG release DCI. For example, the UE may prohibit transmitting in any scheduled CG occasion 515 until the UE receives another CG activation DCI. However, the CG cancellation DCI may deactivate only the subsequent one CG occasion 515 or the subsequent N CG occasions 515, and the CG release DCI deactivates all subsequent CG occasions 515 of a given CG configuration for the UE until the given CG configuration is reactivated by a new CG activation DCI.

[0118] As indicated above, Figure 5 is provided as an example. Other examples may be different from the examples described with respect to Figure 5 the examples.

[0119] Figure 6 FIG. 600 is a diagram illustrating an example 600 in which the CG or SPS communication according to the present disclosure is not aligned with the multimedia service periodically. There may be multiple partial millisecond differences between the start of the downlink service burst and the start of the CG occasion or the SPS occasion. These partial millisecond differences may be compounded with each CG occasion or SPS occasion to misalign the CG occasion or SPS occasion with the XR service periodicity. This also results in increased latency and power consumption.

[0120] Example 600 shows a two-level CG / SPS cycle for XR service alignment. The outer CG or SPS cycle supports a consistent CG / SPS cycle. The outer CG or SPS cycle may include multiple inner CG or SPS cycles, and the multiple inner CG or SPS cycles may be inconsistent. For example, for an XR service at 120 frames per second (fps) (assuming subcarrier spacing (SCS)=15 kHz, frequency division duplex (FDD) and no D / U slot restriction), the outer CG or SPS cycle may be 25 ms (indicated by an RRC message). An integer multiple of the XR periodicity (i.e., 8.333 ms) may be aligned with the CG or SPS periodicity (8.333×3 = 25). Ideally, the number of inner cycles may be defined as the numerator of the XR periodic rational number (e.g., 120 fps = 25 / 3 ms). In example 600, the inner CG or SPS cycles=(9,8,8) ms (e.g., in the RRC message, CG / SPS timeDomainOffset={0 ms,9 ms,17 ms}). The set of integer inner cycles may align the outer cycle with the XR service periodicity. Ideally, the number of inner cycles may be defined as the denominator of the XR periodic rational number (e.g., 120 fps = 25 / 3 ms).

[0121] The rational periodicity can be configured by any control message such as RRC signaling, MAC-CE signaling, or DCI signaling. The rational periodicity can be indicated as one of the values defined by a wireless communication standard such as 3GPP or otherwise fixed (e.g., 120 fps = 25 / 3 ms, 60 = 50 / 3 ms, 30 = 25 / 3 ms).

[0122] Although some solutions for aligning CG or SPS with the XR service periodicity may have been proposed, none of these solutions take into account the actual TDD mode. The TDD mode can be a time slot pattern of uplink resources (uplink time slots or U), downlink resources (downlink time slots or D), and / or special resources (S), where these resources can be guard time slots, flexible resources that can be either uplink time slots or downlink time slots. For example, the TDD mode can be DDDSU. The UE receives downlink communication in the D time slot, receives uplink communication (e.g., especially CG PUSCH communication) in the U time slot, and receives uplink or downlink communication in the S time slot. Without considering the TDD mode for uplink and downlink resources when aligning with the multimedia (e.g., XR) service periodicity, it cannot be guaranteed that CG or SPS communication (and other types of communication or timing) is placed on appropriate (e.g., granted) U / D resources. This misalignment with the TDD mode may result in conflicts or loss of some communication, thus wasting power, processing resources, and signaling resources.

[0123] As indicated above, Figure 6 is provided as an example. Other examples may be different from the example described for Figure 6 is different from the example described above.

[0124] Figure 7 is a diagram illustrating Example 700 that aligns CG or SPS communication with both the multimedia service periodicity and the TDD mode according to the present disclosure.

[0125] According to various aspects described herein, the UE and the network may align CG or SPS communications with multimedia traffic both periodically and with appropriate (e.g., granted) uplink resources and / or downlink resources of a TDD mode configured for the UE. For example, TDD mode alignment for CG type 1 (RRC only) may place CG or sounding reference signal (SRS) communication times on U resources or D resources of the TDD mode, respectively. The UE may be configured to use internal CG or SPS cycles that are only multiples of the TDD periodicity. The sum of the internal CG or SPS cycles may be equal to the external CG or SPS cycle such that CG or SPS communications may be aligned with XR periodicity. In some aspects, the UE may be configured to use multiple time domain offset (e.g., timeDomainOffset) values for CG or SPS communications on U or D resources of the TDD mode within the external CG or SPS cycle that is closest to and after an XR burst transmission.

[0126] In an example with an XR traffic of 120 fps, SCS = 30 kHz, and TDD mode = DDDSU (2.5 ms), and assuming the PUSCH preparation time of the UE is 0, there may be a configuration of an external CG or SPS cycle for 25 ms = 50 time slots = 50x14 symbols and internal CG or SPS cycles of (7.5, 7.5, 10) ms = (15, 15, 20) time slots = (15x14, 15x14, 20x14) symbols. In the case of 7.5 ms + 7.5 ms + 10 ms = 25 ms, there is no timing drift. Another configuration with RRC parameters for periodicity or time domain offset for CG type 1, for example, may include an external CG or SPS cycle with a periodicity of 25 ms and a time domain offset equal to (2 ms, 9.5 ms, 17 ms) = (4, 19, 34) time slots = (4x14, 19x14, 34x14) symbols. Due to the TDD mode (e.g., DDDSU) with a periodicity of 2.5 ms, U resources may be available only at {2 ms, 4.5 ms, 7 ms, 9.5 ms, 12 ms, 14.5 ms, 17 ms, 19.5 ms, 22 ms, 24.5 ms, 25 + 2 ms,...}. The XR uplink timing may be (0 ms, 8.333 ms, 16.666 ms), while the CG uplink resource timing is (2 ms, 9.5 ms, 17 ms, 27 ms). That is, the U time slots in the TDD mode may be available at 2 ms, 4.5 ms, 7 ms, 9.5 ms, 12 ms, 14.5 ms, 17 ms, 19.5 ms, 22 ms, 24.5 ms, and 25 + 2 ms. The UE may use communication times closer to the periodic multimedia traffic at 2 ms (instead of 0 ms), 9.5 ms (instead of 9 ms), 17 ms, and 27 ms (instead of 25 ms).

[0127] As indicated above, Figure 7 is provided as an example. Other examples may be different from the example Figure 7 described.

[0128] Figure 8 is a diagram illustrating Example 800 of CG Type 1 with a TDD mode according to the present disclosure.

[0129] Example 800 shows a U-slot 802 granted by CG Type 1 with a TDD mode having DDDSU. In some aspects, an external CG or an internal CG or SPS cycle of an SPS cycle may be set to have a communication time aligned with the U-slot 802 granted by CG Type 1. The internal CG or SPS cycle may be a multiple of the TDD period (e.g., 2.5 ms). These U-slots 802 may also be closest to and after the XR uplink traffic opportunity.

[0130] In some aspects, a time domain offset 804 may be set to be aligned with the U-slot 802 granted by CG Type 1. For example, in the case of a period of 25 ms, the time domain offset 804 may be 2 ms, 9.5 ms, and 17 ms.

[0131] As indicated above, Figure 8 is provided as an example. Other examples may be different from the example Figure 8 described.

[0132] Figure 9 is a diagram illustrating Example 900 according to the present disclosure associated with communication time using multimedia service periodicity and a TDD mode. As Figure 9 shown, a network entity 910 (e.g., base station 110) and a UE 920 (e.g., UE 120) may communicate with each other over a wireless network (e.g., wireless network 100).

[0133] As shown by reference numeral 925, the network entity 910 may send a configuration for an external CG or an SPS cycle, where the communication time within the external CG or SPS cycle is a multiple of the TDD period and is at least partially based on the multimedia service periodicity.

[0134] As shown by reference numeral 930, the UE 920 may select a communication time at least partially based on the configuration. For example, the UE 920 may select a communication time aligned with the multimedia service periodicity, the TDD period, and the granted resources (within a reasonable distance for quality communication) of the TDD mode. The granted resources may be U-slots or D-slots of CG Type 1, CG Type 2, or SPS.

[0135] As shown by reference numeral 935, UE 920 and network entity 910 may communicate during a communication time. This may include: UE 920 sending a communication during a communication time aligned with a granted (or scheduled) U time slot in TDD mode, as shown in example 800 of Figure 8 or receiving a communication during a communication time aligned with a granted or scheduled D time slot in TDD mode.

[0136] By aligning the communication time with the multimedia periodicity and the TDD periodicity, UE 920 and network entity 910 may not lose communication due to misalignment. By aligning the communication time with the resources in TDD mode, UE 920 and network entity 910 may further avoid losing communication due to resource mismatch. This improves communication and saves power, processing resources, and signaling resources.

[0137] As indicated above, Figure 9 is provided as an example. Other examples may be different from the example described for Figure 9 Description of the example.

[0138] Figure 10A and Figure 10B are diagrams illustrating example 1000 of aligning CG or SPS communication with both multimedia service periodicity and TDD mode according to the present disclosure.

[0139] In some aspects, the UE and the network entity may use TDD mode alignment for CG type 2 (RRC and DCI), and place the CG or SPS communication time on the U resource or D resource of the TDD mode respectively. The DCI may dynamically set the start time of the CG or SPS. The CG type 2 or SPS configuration may have periodic parameters (for example, rrc-ConfiguredUplinkGrant may be allowed only for CG type 1). In some aspects, the configuration may further include a time domain offset information element (IE) for SPS or CG type 2. The time domain offset IE (for example, timeDomainOffset IE) or a set of time domain offset IEs may define the time domain offset between the start time indicated by the DCI and the next CG or SPS communication time within the periodicity. The UE may establish a time domain offset to place the CG or SPS communication time on the granted U or D time slot of the TDD mode. If necessary, network entity 910 may provide a difference (for example, ΔMCS, ΔfrequencyDomainAllocation, ΔtimeDomainAllocation) for each resource of multiple time domain offsets.

[0140] In Figure 10AIn Example 1000 with 120fps XR service, SCS = 30kHz, and TDD mode = DDDSU (2.5ms), and assuming the PUSCH preparation time of the UE is 0, there can be a configuration of an external CG or SPS cycle for 25ms = 50 time slots = 50x14 symbols and an internal CG or SPS cycle for (7.5, 7.5, 10)ms = (15, 15, 20) time slots = (15x14, 15x14, 20x14) symbols. Another configuration with RRC parameters for the periodicity or time domain offset of CG type 2, for example, can include a periodicity of the external CG or SPS cycle equal to 25ms and a time domain offset equal to (0ms, 7.5ms, 15ms) = (0, 15, 30) time slots = (0x14, 15x14, 30x14) symbols. The DCI can be associated with a configured scheduling radio network temporary identifier (CS-RNTI), and can grant the initial PUSCH (starting time) at 2ms. A time domain offset value equal to 0 can indicate the initial PUSCH communication (not explicitly signaled in the RRC message).

[0141] In some aspects, the network entity can introduce a set of multiple inconsistent periodicities (e.g., multiple periodicity) for SPS or CG type 2. In the current standard, the periodicity of CG or SPS can be configured with a single consistent value. By defining the periodicity of CG or SPS using a set of multiple inconsistent values (e.g., a sequence), the CG or SPS configuration can be aligned with the multimedia periodicity. In Figure 10B Example 1002, the set of periodicities can be configured with the same value as the set of internal cycles. Thus, the periodicity for expecting the arrival of a multimedia burst at 120Hz can be (7.5, 7.5, 10)ms = (15, 15, 20) time slots = (15x14, 15x14, 20x14) symbols.

[0142] In some aspects, the network entity can introduce a new IE that can configure a set of associated CG or SPS configurations for SPS or CG type 2. In this case, a single DCI with CS-RNTI can activate / deactivate all associated CG or SPS configurations together with the current CG or SPS configuration. In Figure 10A Example, the first CG configuration has a time domain offset equal to 0ms, the second CG configuration has a time domain offset equal to 7.5ms, and the third CG configuration has a time domain offset equal to 15ms. This configuration can be associated with the RRC message. Thus, a single DCI with CS-RNTI can grant the initial PUSCH (e.g., starting time) at 2ms and can activate all three CG configurations.

[0143] As indicated above, Figure 10A and Figure 10B are provided as examples. Other examples can be found in the Figure 10A and Figure 10B The examples described are different.

[0144] Figure 11 is a diagram illustrating example 1100 of CG type 2 with TDD mode according to the present disclosure.

[0145] Example 1100 shows U slots 1102 granted by CG type 2 of TDD mode with DDDSU. In some aspects, the inner CG or SPS cycle of the outer CG or SPS cycle can be set to have a communication time aligned with the U slots 1102 granted by CG type 2. The inner CG or SPS cycle can be a multiple of the TDD periodicity (e.g., 2.5ms). These U slots 1102 can also be closest to the XR uplink service opportunity and located after the XR uplink service opportunity.

[0146] In some aspects, the time domain offset 1104 may be set to align with the U slot 1102 granted by CG type 2. For example, in the case of a periodicity of 25 ms, the time domain offset 1104 may be 7.5 ms and 15 ms after the start time indicated by the DCI.

[0147] As indicated above, Figure 11 are provided as examples. Other examples can be found in the Figure 11 The examples described are different.

[0148] Figure 12 is a diagram illustrating an example 1200 of an outer CG or SPS cycle for TDD mode according to the present disclosure.

[0149] Example 1200 shows the granted U slots in TDD mode (TDD periodicity is 2ms) of DDDU. In some scenarios, the outer CG or SPS cycle may not be aligned with the TDD periodicity. For example, the sum of the inner CG or SPS cycle may be 8ms+8ms+10ms=26ms, which is not aligned with the 25ms of the outer CG or SPS cycle.

[0150] As indicated above, Figure 12 are provided as examples. Other examples can be found in the Figure 12 The examples described are different.

[0151] Figure 13 is a diagram illustrating an example 1300 of an extended outer CG or SPS loop according to the present disclosure.

[0152] In some aspects, the external CG or SPS cycle can be extended to be periodically aligned with TDD and aligned with resources in the TDD pattern. For example, the external CG or SPS cycle can be extended to 50 ms, which is a multiple of both XR periodicity and TDD periodicity. The communication time can also be aligned with the granted resources of the TDD pattern.

[0153] As indicated above, Figure 13 is provided as an example. Other examples may be different from the example described with respect to Figure 13 description.

[0154] In some aspects, a network entity can select an optimal CG or SPS configuration (e.g., periodicity, time domain offset) for the combination of multimedia services and the TDD pattern. This selection can be at least partially based on an algorithm having the following steps. First, find the minimum value of n for which 'n * XR periodicity' divided by the TDD periodicity is satisfied. Second, set the external cycle (periodicity) = n * XR periodicity. Third, calculate the next XR burst arrival time in sequence based on its initial burst arrival time and periodicity. Fourth, find the earliest available downlink (e.g., SPS) or uplink (e.g., CG) resource in the TDD pattern after the XR burst arrival time of the third step. Fifth, save the resource timing of the third step in a set of internal cycles (timeDomainOffset). Sixth, steps 2 to 5 can be repeated until all CG / SPS resources within the external cycle are allocated. Seventh, the internal cycle (timeDomainOffset) of the fifth step can provide the optimal CG / SPS configuration.

[0155] In some aspects, if a network entity has information about the burst arrival of multimedia traffic, the network entity can find the optimal CG / SPS resources by running the proposed algorithm and configuring the optimal configuration for the UE. Time-Sensitive Communication Assistance Information (TSCAI) can indicate the burst arrival time from the application function to the network entity. Enhanced TSCAI (eTSCAI) can indicate the multimedia traffic pattern - periodicity (Hz or fps of the XR rhythm), size, and / or burst arrival time per flow. However, the UE may know the uplink traffic pattern better than the server, and the UE can directly indicate the burst arrival time of the uplink traffic at least partially based on the 5G system time. Since the 5G system time is synchronized between the network entity and the UE, the UE can convert the uplink traffic timing of a multimedia (e.g., XR) application into the 5G system time. The UE can provide the burst arrival time of the uplink traffic to the network entity. In some aspects, UE Assistance Information (UAI) can indicate the periodicity (Hz or fps of the XR rhythm), size (e.g., average value, minimum / maximum value, variance), and burst arrival time (e.g., μs from a certain 5G system reference time or a specific time slot / subframe / slot start) of the uplink multimedia traffic flow. Since the uplink traffic can include multiple flows, the traffic pattern can be notified for each flow. Additionally, a new RRC or MAC CE (instead of UAI) can be introduced to indicate the uplink traffic pattern.

[0156] In some aspects, the UE can request a relative shift of the current CG / SPS resources for the uplink traffic with respect to the UAI or MAC CE. In the opposite direction, the network entity can request a relative shift of the uplink traffic from the UE.

[0157] In some aspects, the UE can utilize the UAI to provide the traffic pattern of the downlink traffic. The burst arrival time can also be indicated at least partially based on the 5G system time (e.g., μs from a certain 5G system reference time or a specific time slot / subframe / slot start). Additionally, a new RRC message or MAC CE (instead of UAI) can be introduced to indicate the downlink traffic pattern.

[0158] Figures 14A to 14E is a table illustrating Examples 1400 to 1440 of suboptimal configurations for CG or SPS according to the present disclosure.

[0159] In some aspects, if the network entity does not know the burst arrival of the uplink traffic, the network entity can configure a suboptimal configuration for the UE, and the use of this suboptimal configuration is generally independent of the burst arrival time. The UE can request the network entity (e.g., via MAC CE or DCI) to shift the CG / SPS resources. For such a suboptimal configuration, any time shift value of the CG / SPS can be tolerable.

[0160] Figures 14A to 14E The CG configuration can generally support multimedia services without accurate information about the service arrival time. The CG configuration can be adopted in 5G commercial networks. In some aspects, to minimize the average latency, the network entity can evenly place smaller values in the middle of the inner loop sets grouped by subsets. In some aspects, larger inner loops can be placed in front of the subsets to ensure that multimedia burst services arrive before the CG / SPS resources.

[0161] Figure 14A Example 1400 can be used for FDD (e.g., non-TDD) and SCS of 15 kHz. Figure 14B Example 1410 can be used for TDD-DDDSU (2.5 ms) and SCS of 30 kHz. Figure 14C Example 1420 can be used for TDD-DDSU (2 ms) and SCS of 30 kHz. Figure 14D Example 1430 can be used for TDD-DDDSU (0.625 ms) and SCS of 120 kHz. Figure 14E Example 1440 can be used for TDD-DDDU (0.5 ms) and SCS of 120 kHz.

[0162] As indicated above, Figures 14A to 14E is provided as an example. Other examples can be different from the examples described regarding Figures 14A to 14E Description.

[0163] In some aspects, the network entity can optimize the starting time slot for CG type 1 (e.g., via RRC). The optimal SPS / CG resources can be at least partially based on the starting time slot position of the external CG or SPS loop or the TDD mode. The network entity can configure multiple sets of external CG or SPS loops for the UE. The UE can select a preferred external CG or SPS loop from the list. The network entity can configure multiple sets of CG / SPS for multimedia services for each time slot within the external loop or TDD mode. The UE can send a feedback message (e.g., via UAI) indicating the set that is preferred for uplink multimedia services. The network entity can configure the selected set of CG / SPS for the UE.

[0164] In some aspects, a network entity may optimize the starting time slot for CG type 2 (e.g., via RRC and DCI). The network may have a representative set of timedomainoffset that can cover all possible starting time slots in the TDD mode. However, some complex TDD modes do not allow a single set of timedomainoffset, and this set may vary according to the starting time slot position of the TDD mode. In addition, if the network wants to optimize the CG / SPS resources according to the starting time slot position in the TDD mode, multiple sets of timedomainoffset may be defined for each possible time slot in the TDD mode. In some aspects, the network entity may configure a set of timedomainoffset for CG / SPS for each time slot in the TDD mode. The UE may select one of these sets at least partially based on the starting time slot granted by DCI with CS-RNTI. For example, in the case of SPS of SU in TDD mode = D 1 D 2 D 3 In the case of SPS of SU, the network entity may define an optimal set (or multiple periodic optimal sets) of multiple timedomainoffset for each of the time slots D 1 、D 2 、D 3 、S in the TDD mode respectively. The network entity may activate the first starting time slot for the SPS resources using DCI with CS-RNTI. Based on the starting time slot position in the TDD mode, the UE may utilize a specific set of timedomainoffset from the defined set.

[0165] In some aspects, the network entity may configure multiple CG / SPS configurations with different CG / SPS resource patterns (e.g., multiple timedomainoffset or periodicity). The HARQ process number field of the DCI with CS-RNTI may indicate an appropriate CG / SPS configuration index (ConfiguredGrantConfigIndex or sps-ConfigIndex), and this CG / SPS configuration index may indicate an optimal CG / SPS resource pattern (e.g., multiple timedomainoffset or periodicity) according to the starting point of CG / SPS. For example, the network entity may have different CG / SPS configurations for each of the time slots D 1 、D 2 、D 3 、S in the TDD mode, and select one of the time slots with its index at least partially based on the starting time slot position in the TDD mode.

[0166] In some aspects, the UL / DL time slots may be aligned for CG / SPS. The formula for the enhanced CG / SPS option can provide symbol or time slot timing that can be aligned periodically with multimedia. However, these formulas cannot consider the UL / DL time slots in the TDD mode, and the resource timing may not indicate the UL / DL resources in the TDD mode. In some aspects, the network entity may use a second formula that realigns the positions of the first CG / SPS formula to specific UL / DL positions in the TDD mode. For example, the network entity may find the final CG / SPS resource for the next available UL / DL time slot in the TDD mode. The network entity may implicitly (e.g., implicitly align the final CG / SPS time slot assignment with the current TDD UL / DL configuration mode) or explicitly (e.g., define the available UL / DL resource pattern for SPS / CG in an RRC message and align the final CG / SPS time slot assignment accordingly) define the available UL / DL time slots for CG / SPS.

[0167] In some aspects, the network entity may align the final CG / SPS time slot allocation with the TDD UL / DL configuration mode of the RRC message. The network entity may add a second formula or statement based on the current TDD UL / DL configuration mode, which assigns the final CG / SPS time slot allocation to the next available UL / DL time slot. In some aspects, the network entity may explicitly define the available UL / DL resource pattern for SPS / CG in the RRC message and align the final CG / SPS time slot allocation. The network entity may define an additional new IE that aligns the CG / SPS resources with the UL / DL mode of the TDD system. In some aspects that are periodically associated with the CG / SPS TDD resource pattern, the network entity may define the TDD resource pattern periodicity for CG / SPS transmission. For example, for the TDD mode of DDDSU, cgTddPatternPeriodicity = 2.5 ms, spsTddPatternPeriodicity = 2.5 ms, and the sum of the dl-UL-TransmissionPeriodicity of mode 1 and mode 2 may be indicated in TDD-UL-DL-ConfigCommon. dl-UL-TransmissionPeriodicity may be enumerated as {ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10}. In some aspects that are associated with the CG / SPS TDD resource bitmap, the network entity may define the TDD resource bitmap to indicate which time slots are available for CG / SPS transmission. For example, for the TDD mode of DDDSU, cgBitmap =

[00001] and spsBitmap =

[11110] . The network entity may add a second formula or statement based on the proposed message, which assigns the final CG / SPS time slot allocation to the next available UL / DL time slot.

[0168] In some aspects, the alignment with the TDD mode and multimedia service periodicity may be extended to other resources, such as DRX, channel state information (CSI) reference signal (CSI-RS), CSI interference management (CSI-IM) resources, SRS, scheduling request (SR), CSI report (e.g., periodic, semi-persistent), buffer status report (BSR), physical downlink control channel (PDCCH) monitoring (search space), physical uplink control channel (PUCCH) resources, synchronization signal block (SSB), SSB-based measurement timing configuration (SMTC), random access channel (RACH) process, cross-link interference (CLI) RSSI, RSSI-based measurement timing configuration (RMTC), paging message, and / or system information block (SIB), etc.

[0169] In some aspects associated with CSI-RS and SRS, a UE may align CSI-RS or SRS with multimedia traffic periodicity and TDD mode. For example, for enhanced SRS, the UE may use a two-level CG / SPS configuration (e.g., inner loop and outer loop), a conditional CG / SPS formula using the multimedia traffic rhythm, and / or a MAC CE command for shift offset to align the SRS with multimedia traffic. At least in part based on the previous aspects described herein, the UE may establish SRS periodicity and an offset on uplink resources to be placed in TDD mode. In some aspects, at least in part based on the previous aspects described herein, the UE may establish CSI-RS periodicity and an offset on downlink resources to be placed in TDD mode.

[0170] The previous aspects described herein may be applied to enhanced DRX. In some aspects, the UE may adjust the DRX offset value such that the DRX on-duration always starts from a downlink time slot. The UE does not wake up on an uplink time slot because it is expected that the UE will start with DCI in the downlink time slot. To keep the UE longer, the UE may adjust the DRX offset (inner loop) to start on a downlink time slot. In some aspects, the UE may adjust the DRX offset value such that the DRX on-duration may start from a specific radio resource timing (e.g., CSI-RS or SRS). Additionally, if some resources (e.g., SRS, CSI-RS) are to be used when the UE wakes up (e.g., to update beamforming or channel state), the DRX offset may be adjusted according to the timing of the relevant resources.

[0171] In some aspects associated with CG / SPS and enhanced connected mode DRX (CDRX), the UE may adjust the CG / SPS offset value from which the CG / SPS resources start within the DRX on-duration. If the CG / SPS resources are placed in the middle of the UE's inactive state, the UE must wake up during the sleep mode and send / receive the CG / SPS resources. To save power consumption, it would be better to allow the UE to remain in the sleep mode until the DRX on-duration starts by setting the CG / SPS resources before the on-duration starts or equivalently at the start of the on-duration. At least for UL scheduling, the UE may skip PDCCH monitoring in the CG occasion.

[0172] If the periodicity between CG / SPS and DRX cycles is different (e.g., DL XR service (DRX) = 60 Hz, pose (CG / SPS) = 90 Hz), the network entity may define the CG / SPS for a 90 Hz pose aligned with the 60 Hz DL XR service. In some aspects, the UE may align resource timing in multiple XR streams, introduce the least common multiple of the XR streams for a common external cycle (periodicity), and define multiple offsets for each XR stream within this common external cycle (periodicity). Even when the periodicities are different, the network entity may define specific resource timing aligned with both the DL stream (DL XR service) and the UL stream (CG / SPS). By defining a common external cycle, the network entity may define the resource timing of two XR streams. In an example where stream #1: DL XR service (DRX) = 60 Hz (50 / 3 ms) and stream #2: pose (CG / SPS) = 90 Hz (100 / 9 ms), the common external cycle may be the least common multiple of the external cycles of the two streams (50 ms, 100 ms) = 100 ms. The network entity may define 100 ms as the periodicity for both DRX and CG / SPS. The offset values for stream #1 and stream #2 may be defined within the common external cycle (periodicity) of 100 ms. For stream #1, there are 6 offset values within the common external cycle (periodicity) of 100 ms. For stream #2, there are 9 offset values within the common external cycle (periodicity) of 100 ms. For these 6 and 9 offset values, any fine timing adjustment is possible. The network entity may define the resource timing of stream #1 and stream #2 within the 100 ms common periodicity.

[0173] In some aspects, to define the resource timing of multiple radio resources with different periodicities, the network entity may define the least common multiple of their external cycles as the common external cycle (periodicity), and these include: 1) multiple XR stream periodicities (e.g., DRX, CG / SPS), 2) periodic radio resources (e.g., CSI-RS, SRS: 20 ms or 40 ms), and / or 3) TDD mode periodicities (e.g., DDDSU: 2.5 ms, DDDU: 2 ms). The various aspects described herein may support DRX for multiple XR streams.

[0174] The various aspects described herein align the CG / SPS transmission communication time with the multimedia service, thereby improving downlink / uplink scheduling, power consumption, and system performance.

[0175] Figure 15 is a diagram illustrating an example process 1500 performed, for example, by a UE in accordance with the present disclosure. Example process 1500 is an example of operations performed by a UE (e.g., UE 120, UE 920) related to configuring communication for a multimedia service and TDD resources.

[0176] As Figure 15 shown, in some aspects, process 1500 may include: obtaining a configuration for an external CG or SPS cycle, where the communication time within the external CG or SPS cycle is a multiple of the TDD period and is at least partially based on the multimedia service period (block 1510). For example, a UE (e.g., using the communication manager 1908 and / or the configuration component 1910 depicted in Figure 19 ) may obtain a configuration for an external CG or SPS cycle, where the communication time within the external CG or SPS cycle is a multiple of the TDD period and is at least partially based on the multimedia service period, as described above.

[0177] As Figure 15 further shown, in some aspects, process 1500 may include: transmitting or receiving a communication at the communication time (block 1520). For example, a UE (e.g., using the communication manager 1908, the receiving component 1902, and / or the transmitting component 1904 depicted in Figure 19 ) may transmit or receive a communication at the communication time, as described above.

[0178] Process 1500 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0179] In a first aspect, the communication time is at least partially based on the TDD pattern of resources granted by CG type 1 or CG type 2.

[0180] In a second aspect, alone or in combination with the first aspect, obtaining the configuration includes: receiving the configuration or obtaining the configuration from stored configuration information.

[0181] In a third aspect, alone or in combination with one or more of the first and second aspects, the communication time is at least partially based on an internal CG or SPS cycle configured for the external CG or SPS cycle, and where the sum of the internal CG or SPS cycles is equal to the external CG or SPS cycle.

[0182] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the communication time is at least partially based on a time domain offset value configured for the external CG or SPS cycle.

[0183] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the time domain offset value is aligned with the uplink or downlink resources closest to the multimedia service burst.

[0184] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the time domain offset value is aligned with an uplink or downlink resource that is after and closest to the multimedia service burst.

[0185] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the external CG or SPS cycle is for CG type 2, and wherein the method includes: receiving an information element that indicates the time domain offset value for the external CG or SPS cycle.

[0186] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the external CG or SPS cycle is for CG type 1.

[0187] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the external CG or SPS cycle is for CG type 2, and wherein the method includes: receiving DCI that indicates a start time of the external CG or SPS cycle.

[0188] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the DCI indicates different values for determining a time domain offset value for the communication time within the external CG or SPS cycle, indicates a periodic set for the multimedia service burst, or indicates a set of associated CG or SPS configurations.

[0189] In an eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, process 1500 includes: extending a length of the external CG or SPS cycle to align with the TDD periodicity.

[0190] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, extending the length of the external CG or SPS cycle includes: extending the external CG or SPS cycle to a least common multiple of the external CG or SPS cycle and the TDD periodicity.

[0191] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, process 1500 includes: receiving an indication of a set of multiple external CG or SPS cycles, each external CG or SPS cycle having a pattern of communication time; selecting the external CG or SPS cycle from the set of multiple external CG or SPS cycles based at least in part on one or more of an external cycle start time slot or a TDD pattern; and transmitting an indication of the selected external CG or SPS cycle.

[0192] In a fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, process 1500 includes: receiving an indication of a set of time domain value offsets for the external CG or SPS cycle for each time slot in the TDD mode; selecting a set of time domain offset values for the external CG or SPS cycle for the time slots in the TDD mode that correspond to the starting time slot or configuration index indicated by the DCI; and transmitting an indication of the selected set of time domain offset values.

[0193] In a fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, process 1500 includes: aligning the communication time with the time slots allocated according to the current TDD mode.

[0194] In a sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, process 1500 includes: receiving an indication of the TDD mode, and aligning the communication time with the time slots allocated according to the TDD mode.

[0195] Although Figure 15 illustrative example boxes of process 1500 are shown, in some aspects, process 1500 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner compared to those depicted in Figure 15 . Additionally or alternatively, two or more of the boxes of process 1500 may be performed in parallel.

[0196] Figure 16 is a diagram illustrating an example process 1600, such as may be performed by a network entity, in accordance with the present disclosure. Example process 1600 is one in which a network entity (e.g., base station 110, network entity 910) performs operations associated with configuring communication for multimedia services and TDD resources.

[0197] As Figure 16 shown, in some aspects, process 1600 may include: transmitting a configuration for an external CG or SPS cycle, where the communication time within the external CG or SPS cycle is a multiple of the TDD periodicity and is at least partially based on the multimedia service periodicity (block 1610). For example, a network entity (e.g., using the communication manager 2008 and / or the transmitting component 2004 depicted in Figure 20 ) may transmit a configuration for an external CG or SPS cycle, where the communication time within the external CG or SPS cycle is a multiple of the TDD periodicity and is at least partially based on the multimedia service periodicity, as described above.

[0198] As Figure 16 further shown, in some aspects, process 1600 may include: transmitting or receiving communication at the communication time (block 1620). For example, a network entity (e.g., usingFigure 20 The communication manager 2008 and / or the transmitting component 2004 depicted in [description] can send or receive communications during the communication time, as described above.

[0199] Process 1600 can include additional aspects, such as any individual aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0200] In a first aspect, the communication time is at least partially based on the TDD mode of resources granted by CG type 1 or CG type 2.

[0201] In a second aspect, either alone or in combination with the first aspect, the communication time is at least partially based on an internal CG or SPS cycle configured for the external CG or SPS cycle, and wherein the sum of the internal CG or SPS cycles is equal to the external CG or SPS cycle.

[0202] In a third aspect, either alone or in combination with one or more of the first and second aspects, the communication time is at least partially based on a time domain offset value configured for the external CG or SPS cycle.

[0203] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the time domain offset value is aligned with the uplink or downlink resources closest to the multimedia service burst.

[0204] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the time domain offset value is aligned with the uplink or downlink resources that are located after and closest to the multimedia service burst.

[0205] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the external CG or SPS cycle is for CG type 2, and process 1600 includes: transmitting an IE that indicates the time domain offset value for the external CG or SPS cycle.

[0206] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the external CG or SPS cycle is for CG type 1.

[0207] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the external CG or SPS cycle is for CG type 2, and wherein the method includes: transmitting a DCI that indicates the start time of the external CG or SPS cycle.

[0208] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the DCI indicates different values for determining a time domain offset value for the communication time within the external CG or SPS cycle, indicates a periodic set of multimedia service bursts, or indicates a set of associated CG or SPS configurations.

[0209] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, process 1600 includes: extending the length of the external CG or SPS cycle to align with the TDD periodicity.

[0210] In an eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, extending the length of the external CG or SPS cycle includes: extending the external CG or SPS cycle to a common multiple of the external CG or SPS cycle and the TDD periodicity.

[0211] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, process 1600 includes: selecting the communication time at least in part based on having information about the arrival time of the initial multimedia service burst or at least in part based on a request associated with a relative shift.

[0212] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, process 1600 includes: selecting a pre-configured communication time pattern in the external CG or SPS cycle as the configuration at least in part based on not having information about the arrival time of the initial multimedia service burst.

[0213] In a fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, process 1600 includes: sending an indication of a set of multiple external CG or SPS cycles, each external CG or SPS cycle having a pattern of communication time; receiving an indication of the selected external CG or SPS cycle; and generating the configuration at least in part based on the selected external CG or SPS cycle.

[0214] In a fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, process 1600 includes: sending an indication of a set of time domain value offsets of the external CG or SPS cycle for each time slot in the TDD mode; receiving an indication of the selected set of time domain offset values; and generating the configuration at least in part based on the selected set of time domain offset values.

[0215] In a sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, process 1600 includes: sending an indication of the TDD mode for aligning the communication time with the time slots of the TDD mode.

[0216] Although Figure 16 example boxes of process 1600 are shown, in some aspects, process 1600 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner compared to those depicted in Figure 16 . Additionally or alternatively, two or more of the boxes of process 1600 may be executed in parallel.

[0217] Figure 17 is a diagram illustrating an example process 1700 performed, for example, by a UE in accordance with the present disclosure. Example process 1700 is an example of operations performed by a UE (e.g., UE 120, UE 920) associated with configuring communications for multimedia services and TDD resources.

[0218] As Figure 17 shown, in some aspects, process 1700 may include: receiving a periodic configuration for a communication time that is divisible by or is a multiple of a TDD period and is at least partially based on a multimedia service period (block 1710). For example, a UE (e.g., using the communication manager 1908 and / or the receiving component 1902 depicted in Figure 19 ) may receive a periodic configuration for a communication time that is divisible by or is a multiple of a TDD period and is at least partially based on a multimedia service period, as described above.

[0219] As Figure 17 further shown, in some aspects, process 1700 may include: transmitting or receiving a communication at the communication time (block 1720). For example, a UE (e.g., using the communication manager 1908 and / or the transmitting component 1904 depicted in Figure 19 ) may transmit or receive a communication at the communication time, as described above.

[0220] Process 1700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0221] In a first aspect, the communication time is at least partially based on a TDD pattern of the granted resources.

[0222] In a second aspect, alone or in combination with the first aspect, the communication time has a DRX cycle.

[0223] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1700 includes: adjusting a DRX offset value such that a DRX on-duration is aligned with a downlink time slot of a TDD pattern.

[0224] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 1700 includes: adjusting a DRX offset value such that a DRX on-duration is aligned with a specific radio resource timing.

[0225] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 1700 includes: adjusting a DRX offset value such that a DRX on-duration is aligned with an external configured grant or a semi-persistent scheduling cycle.

[0226] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the communication is CSI-RS or CSI-IM resource.

[0227] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 1700 includes: aligning the periodicity and offset of the CSI-RS with a downlink time slot of a TDD mode.

[0228] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the communication is SRS.

[0229] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 1700 includes: aligning the SRS with an uplink time slot of a TDD mode.

[0230] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the communication is a scheduling request.

[0231] In an eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the communication is a channel state information report or a buffer status report.

[0232] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the communication is sent in a physical uplink channel resource or received in a physical downlink channel resource.

[0233] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the communication is SSB.

[0234] In a fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, the communication is a random access channel message.

[0235] In a fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the communication is a CLI measurement resource.

[0236] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the communication is a signal strength or signal quality measurement resource.

[0237] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the communication is a paging message.

[0238] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the communication is a system information block.

[0239] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, process 1700 includes: aligning resource timing in a plurality of multimedia traffic flows based at least in part on a common multiple number of multimedia traffic flows for a common outer loop.

[0240] Although Figure 17 illustrates example blocks of process 1700, in some aspects, process 1700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner compared to those depicted in Figure 17 . Additionally or alternatively, two or more blocks of process 1700 may be executed in parallel.

[0241] Figure 18 is a diagram illustrating an example process 1800 performed, for example, by a network entity in accordance with the present disclosure. Example process 1800 is one in which a network entity (e.g., base station 110, network entity 910) performs operations associated with configuring communication for multimedia traffic and TDD resources.

[0242] As Figure 18 shown, in some aspects, process 1800 may include: transmitting a periodic configuration for a communication time that is divisible by or is a multiple of a TDD period and is at least partially based on a multimedia traffic period (block 1810). For example, a network entity (e.g., using the communication manager 2008 and / or the transmitting component 2004 depicted in Figure 20 ) may transmit a periodic configuration for a communication time that is divisible by or is a multiple of a TDD period and is at least partially based on a multimedia traffic period, as described above.

[0243] As Figure 18 further shown, in some aspects, process 1800 may include: transmitting or receiving a communication at the communication time (block 1820). For example, a network entity (e.g., using the communication manager 2008 and / or the transmitting component 2004 depicted in Figure 20 ) may transmit or receive a communication at the communication time, as described above.

[0244] The process 1800 may include additional aspects, such as any individual aspect or any combination of aspects described below and / or in combination with one or more other process descriptions described elsewhere herein.

[0245] In a first aspect, the communication time is at least partially based on the TDD mode of the granted resources.

[0246] In a second aspect, either alone or in combination with the first aspect, the communication time has a DRX cycle.

[0247] In a third aspect, either alone or in combination with one or more of the first and second aspects, the process 1800 includes: adjusting the DRX offset value such that the DRX on duration is aligned with the downlink time slots of the TDD mode.

[0248] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the process 1800 includes: adjusting the DRX offset value such that the DRX on duration is aligned with a specific radio resource timing.

[0249] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the process 1800 includes: adjusting the DRX offset value such that the DRX on duration is aligned with an external configured grant or semi-persistent scheduling cycle.

[0250] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the communication is CSI-RS or CSI-IM resources.

[0251] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the process 1800 includes: aligning the periodicity and offset of the CSI-RS with the downlink time slots of the TDD mode.

[0252] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the communication is SRS.

[0253] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the process 1800 includes: aligning the SRS with the uplink time slots of the TDD mode.

[0254] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the communication is a scheduling request.

[0255] In an eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the communication is a CSI report or a buffer status report.

[0256] In a twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the communication is sent in a physical uplink channel resource or received in a physical downlink channel resource.

[0257] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the communication is an SSB.

[0258] In a fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, the communication is a random access channel message.

[0259] In a fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, the communication is CLI measurement resources.

[0260] In a sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, the communication is signal strength or signal quality measurement resources.

[0261] In a seventeenth aspect, either alone or in combination with one or more of the first to sixteenth aspects, the communication is a paging message.

[0262] In an eighteenth aspect, either alone or in combination with one or more of the first to seventeenth aspects, the communication is an SIB.

[0263] In a nineteenth aspect, either alone or in combination with one or more of the first to eighteenth aspects, process 1800 includes: aligning resource timings in a plurality of multimedia traffic flows based at least in part on a common multiple number of multimedia traffic flows for a common outer loop.

[0264] Although Figure 18 example boxes of process 1800 are shown, in some aspects, process 1800 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner compared to those depicted in Figure 18 Two or more boxes of process 1800 may be executed in parallel additionally or alternatively.

[0265] Figure 19FIG. 0 is a diagram of an example apparatus 1900 for wireless communication in accordance with the present disclosure. The apparatus 1900 may be a UE (e.g., UE 20, UE 920), or the UE may include the apparatus 1900. In some aspects, the apparatus 1900 includes a receiving component 1902 and a transmitting component 1904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1900 may communicate with another apparatus 1906 (such as a UE, a base station, or another wireless communication device) using the receiving component 1902 and the transmitting component 1904. As further shown, the apparatus 1900 may include a communication manager 1908. The communication manager 1908 may control and / or otherwise manage one or more operations of the receiving component 1902 and / or the transmitting component 1904. In some aspects, the communication manager 1908 may include one or more antennas, modems, controllers / processors, memories, or combinations thereof of the UE described in conjunction with Figure 2 The communication manager 1908 may be or be similar to Figure 1 and Figure 2 The communication manager 140 depicted in. For example, in some aspects, the communication manager 1908 may be configured to perform one or more of the functions described as being performed by the communication manager 140. In some aspects, the communication manager 1908 may include the receiving component 1902 and / or the transmitting component 1904. The communication manager 1908 may include a configuration component 1910 and / or a selection component 1912, etc.

[0266] In some aspects, the apparatus 1900 may be configured to perform one or more operations described herein in conjunction with Figures 1 to 14E Additionally or alternatively, the apparatus 1900 may be configured to perform one or more processes described herein, such as Figure 15 The process 1500 of Figure 17 The process 17 of Figure 19 or combinations thereof. In some aspects, Figure 2 The apparatus 1900 shown and / or one or more components may include one or more components of the UE described in conjunction with Figure 19 Additionally or alternatively, Figure 2 One or more components shown may be implemented within one or more components described in conjunction with

[0267] The receiving component 1902 can receive communications from the device 1906, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1902 can provide the received communications to one or more other components of the device 1900. In some aspects, the receiving component 1902 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and can provide the processed signals to one or more other components of the device 1900. In some aspects, the receiving component 1902 can include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the UE described in conjunction with Figure 2 The one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the UE described in conjunction with

[0268] The transmitting component 1904 can send communications to the device 1906, such as reference signals, control information, data communications, or combinations thereof. In some aspects, one or more other components of the device 1900 can generate communications and can provide the generated communications to the transmitting component 1904 for transmission to the device 1906. In some aspects, the transmitting component 1904 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.), and can send the processed signals to the device 1906. In some aspects, the transmitting component 1904 can include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE described in conjunction with Figure 2 The one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE described in conjunction with

[0269] In some aspects, the configuration component 1910 can obtain a configuration for an external CG or SPS cycle, where the communication time within the external CG or SPS cycle is a multiple of the TDD periodicity and is at least partially based on the multimedia service periodicity. The transmitting component 1904 can send or receive communications at the communication time.

[0270] The configuration component 1910 can extend the length of the external CG or SPS cycle to align with the TDD periodicity. The receiving component 1902 can receive an indication of a set of multiple external CG or SPS cycles, each external CG or SPS cycle having a pattern of communication times.

[0271] The selection component 1912 may select the external CG or SPS cycle from the set of multiple external CG or SPS cycles based at least in part on one or more of an external loop start time slot or a TDD mode. The sending component 1904 may send an indication of the selected external CG or SPS cycle. The receiving component 1902 may receive an indication of a set of time domain value offsets of the external CG or SPS cycle for each time slot in the TDD mode.

[0272] The selection component 1912 may select a set of time domain offset values for the time slots in the TDD mode for the external CG or SPS cycle, where the time slots correspond to a start time slot or a configuration index indicated by DCI. The sending component 1904 may send an indication of the selected set of time domain offset values. The selection component 1912 may align the communication time with the time slots allocated according to the current TDD mode.

[0273] The receiving component 1902 may receive an indication of the TDD mode. The selection component 1912 may align the communication time with the time slots allocated according to the TDD mode.

[0274] In some aspects, the receiving component 1902 may receive a configuration for the periodicity of the communication time, which is divisible by or is a multiple of the TDD periodicity and is at least in part based on the multimedia service periodicity. The sending component 1904 may send or receive communication at the communication time.

[0275] The selection component 1912 may adjust the DRX offset value such that the DRX on duration is aligned with the downlink time slots of the TDD mode. The selection component 1912 may adjust the DRX offset value such that the DRX on duration is aligned with a specific radio resource timing. The selection component 1912 may adjust the DRX offset value such that the DRX on duration is aligned with a configured grant or a semi-persistent scheduling cycle. The selection component 1912 may align the periodicity and offset of the CSI-RS with the downlink time slots of the TDD mode. The selection component 1912 may align the SRS with the uplink time slots of the TDD mode. The selection component 1912 may align the resource timing in multiple multimedia service flows based at least in part on a common multiple number of multimedia service flows for the external cycle.

[0276] Figure 19 The number and arrangement of the components shown are provided as an example. In fact, there may be additional components, fewer components, different components, or components arranged in a different manner compared to Figure 19 those shown. Additionally, Figure 19 two or more of the components shown may be implemented within a single component, or Figure 19 the single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 19The set of components (one or more components) shown can perform one or more functions described as being performed by Figure 19 another set of components shown.

[0277] Figure 20 is a diagram of an example apparatus 2000 for wireless communication in accordance with the present disclosure. The apparatus 2000 can be a network entity (e.g., base station 110, network entity 910), or a network entity can include the apparatus 2000. In some aspects, the apparatus 2000 includes a receiving component 2002 and a transmitting component 2004 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 2000 can use the receiving component 2002 and the transmitting component 2004 to communicate with another apparatus 2006 (such as a UE, a base station, or another wireless communication device). As further shown, the apparatus 2000 can include a communication manager 2008. The communication manager 2008 can control and / or otherwise manage one or more operations of the receiving component 2002 and / or the transmitting component 2004. In some aspects, the communication manager 2008 can include one or more antennas, modems, controllers / processors, memories, or combinations thereof of the network entity described in conjunction with Figure 2 The communication manager 2008 can be or be similar to Figure 1 and Figure 2 the communication manager 150 depicted in

[0278] In some aspects, the apparatus 2000 can be configured to perform one or more operations described herein in conjunction with Figures 1 to 14E Additionally or alternatively, the apparatus 2000 can be configured to perform one or more processes described herein, such as Figure 16 process 1600 of Figure 18 process 1800 of Figure 20 or combinations thereof. In some aspects, Figure 2 the apparatus 2000 and / or one or more components shown can include one or more components of the network entity described in conjunction with Figure 20 Additionally or alternatively, Figure 2implemented within one or more of the described components. Additionally or alternatively, one or more of the components in the set of components may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the functions or operations of the component.

[0279] The receiving component 2002 may receive communications from the device 2006, such as reference signals, control information, data communications, or combinations thereof. The receiving component 2002 may provide the received communications to one or more other components of the device 2000. In some aspects, the receiving component 2002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signals to one or more other components of the device 2000. In some aspects, the receiving component 2002 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controller / processors, memories, or combinations thereof of the network entity described in conjunction with Figure 2 the description.

[0280] The transmitting component 2004 may transmit communications to the device 2006, such as reference signals, control information, data communications, or combinations thereof. In some aspects, one or more other components of the device 2000 may generate communications and may provide the generated communications to the transmitting component 2004 for transmission to the device 2006. In some aspects, the transmitting component 2004 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.), and may transmit the processed signals to the device 2006. In some aspects, the transmitting component 2004 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controller / processors, memories, or combinations thereof of the network entity described in conjunction with Figure 2 the description. In some aspects, the transmitting component 2004 may be co-located with the receiving component 2002 in a transceiver.

[0281] In some aspects, the transmitting component 2004 may transmit a configuration for an external CG or SPS cycle, where the communication time within the external CG or SPS cycle is a multiple of the TDD period and is at least partially based on the multimedia service period. The transmitting component 2004 may transmit or receive communications at the communication time.

[0282] The configuration component 2010 can extend the length of the external CG or SPS cycle to align with the TDD periodicity. The selection component 2012 can select the communication time at least partially based on having information about the arrival time of the initial multimedia service burst or at least partially based on a request associated with a relative shift. The selection component 2012 can select a preconfigured communication time pattern in the external CG or SPS cycle as the configuration at least partially based on not having information about the arrival time of the initial multimedia service burst.

[0283] The sending component 2004 can send an indication of a set of multiple external CG or SPS cycles, each external CG or SPS cycle having a pattern of communication time. The receiving component 2002 can receive an indication of the selected external CG or SPS cycle. The configuration component 2010 can generate the configuration at least partially based on the selected external CG or SPS cycle.

[0284] The sending component 2004 can send an indication of a set of time domain value offsets of the external CG or SPS cycle for each time slot in the TDD mode. The receiving component 2002 can receive an indication of the selected set of time domain offset values.

[0285] The configuration component 2010 can generate the configuration at least partially based on the selected set of time domain offset values. The sending component 2004 can send an indication of the TDD mode for aligning the communication time with the time slots of the TDD mode.

[0286] In some aspects, the sending component 2004 can send a configuration for the periodicity of the communication time, which is divisible by the TDD periodicity or is a multiple of the TDD periodicity and at least partially based on the multimedia service periodicity. The sending component 2004 can send or receive communication at the communication time.

[0287] The configuration component 2010 can adjust the DRX offset value such that the DRX on duration is aligned with the downlink time slots of the TDD mode. The configuration component 2010 can adjust the DRX offset value such that the DRX on duration is aligned with a specific radio resource timing. The configuration component 2010 can adjust the DRX offset value such that the DRX on duration is aligned with a configured grant or semi-persistent scheduling cycle. The configuration component 2010 can align the periodicity and offset of the CSI-RS with the downlink time slots of the TDD mode. The configuration component 2010 can align the SRS with the uplink time slots of the TDD mode. The configuration component 2010 can align the resource timing in multiple multimedia service flows at least partially based on a common multiple number of multimedia service flows for a common external cycle.

[0288] Figure 20 The number and arrangement of the components shown are provided as an example. In fact, there may beFigure 20 those shown compared to additional components, fewer components, different components, or components arranged in a different manner. Additionally, Figure 20 two or more of the components shown may be implemented within a single component, or Figure 20 a single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 20 a collection of the component(s) shown may perform one or more functions described as being performed by Figure 20 another collection of the components shown.

[0289] An overview of some aspects of the present disclosure is provided below:

[0290] Aspect 1: A method of wireless communication performed by a UE, the method comprising: obtaining a configuration for an external configured grant (CG) or semi-persistent scheduling (SPS) cycle, wherein communication time within the external CG or SPS cycle is a multiple of a time division duplex (TDD) period and is at least partially based on a multimedia traffic period; and transmitting or receiving communication during the communication time.

[0291] Aspect 2: The method according to aspect 1, wherein the communication time is at least partially based on a TDD pattern of resources granted by CG type 1 or CG type 2.

[0292] Aspect 3: The method according to any one of aspects 1 to 2, wherein obtaining the configuration comprises: receiving the configuration or obtaining the configuration from stored configuration information.

[0293] Aspect 4: The method according to any one of aspects 1 to 3, wherein the communication time is at least partially based on an internal CG or SPS cycle configured for the external CG or SPS cycle, and wherein a sum of the internal CG or SPS cycles is equal to the external CG or SPS cycle.

[0294] Aspect 5: The method according to any one of aspects 1 to 4, wherein the communication time is at least partially based on a time domain offset value configured for the external CG or SPS cycle.

[0295] Aspect 6: The method according to aspect 5, wherein the time domain offset value is aligned with an uplink or downlink resource closest to a multimedia traffic burst.

[0296] Aspect 7: The method according to aspect 5, wherein the time domain offset value is aligned with an uplink or downlink resource located after and closest to the multimedia traffic burst.

[0297] Aspect 8: The method according to aspect 5, wherein the external CG or SPS cycle is for CG type 2, and wherein the method comprises: receiving an information element indicating the time domain offset value for the external CG or SPS cycle.

[0298] Aspect 9: The method according to any one of aspects 1 to 8, wherein the external CG or SPS cycle is for CG type 1.

[0299] Aspect 10: The method according to any one of aspects 1 to 9, wherein the external CG or SPS cycle is for CG type 2, and wherein the method comprises: receiving downlink control information (DCI) indicating a start time of the external CG or SPS cycle.

[0300] Aspect 11: The method according to aspect 10, wherein the DCI indicates different values for determining a time domain offset value for a communication time within the external CG or SPS cycle, indicates a periodic set for a multimedia service burst, or indicates a set of associated CG or SPS configurations.

[0301] Aspect 12: The method according to any one of aspects 1 to 11, the method further comprising: extending a length of the external CG or SPS cycle to align with the TDD periodicity.

[0302] Aspect 13: The method according to aspect 12, wherein extending the length of the external CG or SPS cycle comprises: extending the external CG or SPS cycle to a least common multiple of the external CG or SPS cycle and the TDD periodicity.

[0303] Aspect 14: The method according to any one of aspects 1 to 13, the method further comprising: receiving an indication of a set of multiple external CG or SPS cycles, each external CG or SPS cycle having a pattern of communication time; selecting the external CG or SPS cycle from the set of multiple external CG or SPS cycles at least partially based on one or more of an external cycle start time slot or a TDD pattern; and sending an indication of the selected external CG or SPS cycle.

[0304] Aspect 15: The method according to any one of aspects 1 to 14, the method further comprising: receiving an indication of a set of time domain value offsets of the external CG or SPS cycle for each time slot in a TDD pattern; selecting a set of time domain offset values for the external CG or SPS cycle for time slots in the TDD pattern, the time slots corresponding to a start time slot or a configuration index indicated by downlink control information; and sending an indication of the selected set of time domain offset values.

[0305] Aspect 16: The method according to any one of Aspects 1 to 15, the method further comprising: aligning the communication time with a time slot allocated according to a current TDD mode.

[0306] Aspect 17: The method according to any one of Aspects 1 to 16, the method further comprising: receiving an indication of a TDD mode; and aligning the communication time with a time slot allocated according to the TDD mode.

[0307] Aspect 18: A method for wireless communication performed by a network entity, the method comprising: sending a configuration for an external configured grant (CG) or semi-persistent scheduling (SPS) cycle, wherein a communication time within the external CG or SPS cycle is a multiple of a time division duplex (TDD) period and is at least partially based on a multimedia service period; and sending or receiving communication at the communication time.

[0308] Aspect 19: The method according to Aspect 18, wherein the communication time is at least partially based on a TDD mode of resources granted by CG type 1 or CG type 2.

[0309] Aspect 20: The method according to any one of Aspects 18 to 19, wherein the communication time is at least partially based on an internal CG or SPS cycle configured for the external CG or SPS cycle, and wherein a sum of the internal CG or SPS cycles is equal to the external CG or SPS cycle.

[0310] Aspect 21: The method according to any one of Aspects 18 to 20, wherein the communication time is at least partially based on a time domain offset value configured for the external CG or SPS cycle.

[0311] Aspect 22: The method according to Aspect 21, wherein the time domain offset value is aligned with an uplink or downlink resource closest to a multimedia service burst.

[0312] Aspect 23: The method according to Aspect 21, wherein the time domain offset value is aligned with an uplink or downlink resource that is located after and closest to the multimedia service burst.

[0313] Aspect 24: The method according to Aspect 21, wherein the external CG or SPS cycle is for CG type 2, and wherein the method comprises: sending an information element indicating the time domain offset value for the external CG or SPS cycle.

[0314] Aspect 25: The method according to any one of Aspects 18 to 24, wherein the external CG or SPS cycle is for CG type 1.

[0315] Aspect 26: The method according to any one of aspects 18 to 25, wherein the external CG or SPS cycle is for CG type 2, and wherein the method comprises: transmitting downlink control information (DCI), the downlink control information (DCI) indicating a start time of the external CG or SPS cycle.

[0316] Aspect 27: The method according to aspect 26, wherein the DCI indicates different values for determining a time domain offset value for the communication time within the external CG or SPS cycle, indicates a periodic set for a multimedia service burst, or indicates a set of associated CG or SPS configurations.

[0317] Aspect 28: The method according to any one of aspects 18 to 27, the method further comprising: extending a length of the external CG or SPS cycle to align with a TDD periodicity.

[0318] Aspect 29: The method according to aspect 28, wherein extending the length of the external CG or SPS cycle comprises: extending the external CG or SPS cycle to a least common multiple of the external CG or SPS cycle and the TDD periodicity.

[0319] Aspect 30: The method according to any one of aspects 18 to 29, the method further comprising: selecting the communication time at least in part based on having information about an arrival time of an initial multimedia service burst or at least in part based on a request associated with a relative shift.

[0320] Aspect 31: The method according to any one of aspects 18 to 30, the method further comprising: selecting a preconfigured communication time pattern in the external CG or SPS cycle as the configuration at least in part based on not having information about an arrival time of an initial multimedia service burst.

[0321] Aspect 32: The method according to any one of aspects 18 to 31, the method further comprising: transmitting an indication of a set of a plurality of external CG or SPS cycles, each external CG or SPS cycle having a pattern of communication time; receiving an indication of a selected external CG or SPS cycle; and generating the configuration at least in part based on the selected external CG or SPS cycle.

[0322] Aspect 33: The method according to any one of aspects 18 to 32, the method further comprising: transmitting an indication of a set of time domain value offsets of the external CG or SPS cycle for each time slot in a TDD mode; receiving an indication of a selected set of time domain offset values; and generating the configuration at least in part based on the selected set of time domain offset values.

[0323] Aspect 34: The method according to any one of aspects 18 to 33, the method further comprising: sending an indication of a TDD mode for aligning a communication time with time slots of the TDD mode.

[0324] Aspect 35: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a periodic configuration for a communication time, the communication time being divisible by a time division duplex (TDD) period or being a multiple of a time division duplex (TDD) period and at least partially based on a multimedia service period; and transmitting or receiving communication at the communication time.

[0325] Aspect 36: The method according to aspect 35, wherein the communication time is at least partially based on a TDD mode of granted resources.

[0326] Aspect 37: The method according to any one of aspects 35 to 36, wherein the communication time has a discontinuous reception (DRX) cycle.

[0327] Aspect 38: The method according to aspect 37, the method further comprising: adjusting a DRX offset value such that a DRX on duration is aligned with a downlink time slot of a TDD mode.

[0328] Aspect 39: The method according to aspect 37, the method further comprising: adjusting a DRX offset value such that a DRX on duration is aligned with a specific radio resource timing.

[0329] Aspect 40: The method according to aspect 37, the method further comprising: adjusting a DRX offset value such that a DRX on duration is aligned with an external configured grant or semi-persistent scheduling cycle.

[0330] Aspect 41: The method according to any one of aspects 35 to 40, wherein the communication is a channel state information (CSI) reference signal (CSI-RS) or a CSI interference measurement resource.

[0331] Aspect 42: The method according to aspect 41, the method further comprising: aligning a period and an offset of the CSI-RS with a downlink time slot of a TDD mode.

[0332] Aspect 43: The method according to any one of aspects 35 to 42, wherein the communication is a sounding reference signal (SRS).

[0333] Aspect 44: The method according to aspect 43, the method further comprising: aligning the SRS with an uplink time slot of a TDD mode.

[0334] Aspect 45: The method according to any one of aspects 35 to 44, wherein the communication is a scheduling request.

[0335] Aspect 46: The method according to any one of aspects 35 to 45, wherein the communication is a channel state information report or a buffer status report.

[0336] Aspect 47: The method according to any one of aspects 35 to 46, wherein the communication is sent in a physical uplink channel resource or received in a physical downlink channel resource.

[0337] Aspect 48: The method according to any one of aspects 35 to 47, wherein the communication is a synchronization signal block (SSB).

[0338] Aspect 49: The method according to any one of aspects 35 to 48, wherein the communication is a random access channel message.

[0339] Aspect 50: The method according to any one of aspects 35 to 49, wherein the communication is a cross-link interference measurement resource.

[0340] Aspect 51: The method according to any one of aspects 35 to 50, wherein the communication is a signal strength or signal quality measurement resource.

[0341] Aspect 52: The method according to any one of aspects 35 to 51, wherein the communication is a paging message.

[0342] Aspect 53: The method according to any one of aspects 35 to 52, wherein the communication is a system information block.

[0343] Aspect 54: The method according to any one of aspects 35 to 53, the method further comprising: aligning resource timings in a plurality of multimedia traffic flows at least in part based on a common multiple number of multimedia traffic flows for a common external cycle.

[0344] Aspect 55: A method of wireless communication performed by a network entity, the method comprising: transmitting a periodic configuration for a communication time that is divisible by a time division duplex (TDD) period or is a multiple of a time division duplex (TDD) period and at least in part based on a multimedia traffic period; and transmitting or receiving communication at the communication time.

[0345] Aspect 56: The method according to aspect 55, wherein the communication time is at least in part based on a TDD pattern of the granted resources.

[0346] Aspect 57: The method according to any one of aspects 55 to 56, wherein the communication time has a discontinuous reception (DRX) cycle.

[0347] Aspect 58: The method according to aspect 57, the method further comprising: adjusting the DRX offset value such that the DRX on-duration is aligned with the downlink time slots of the TDD mode.

[0348] Aspect 59: The method according to aspect 57, the method further comprising: adjusting the DRX offset value such that the DRX on-duration is aligned with a specific radio resource timing.

[0349] Aspect 60: The method according to aspect 57, the method further comprising: adjusting the DRX offset value such that the DRX on-duration is aligned with an external configured grant or semi-persistent scheduling cycle.

[0350] Aspect 61: The method according to any one of aspects 55 to 60, wherein the communication is a channel state information (CSI) reference signal (CSI-RS) or a CSI interference measurement resource.

[0351] Aspect 62: The method according to aspect 61, the method further comprising: aligning the periodicity and offset of the CSI-RS with the downlink time slots of the TDD mode.

[0352] Aspect 63: The method according to any one of aspects 55 to 62, wherein the communication is a sounding reference signal (SRS).

[0353] Aspect 64: The method according to aspect 63, the method further comprising: aligning the SRS with the uplink time slots of the TDD mode.

[0354] Aspect 65: The method according to any one of aspects 55 to 64, wherein the communication is a scheduling request.

[0355] Aspect 66: The method according to any one of aspects 55 to 65, wherein the communication is a channel state information report or a buffer status report.

[0356] Aspect 67: The method according to any one of aspects 55 to 66, wherein the communication is sent in a physical uplink channel resource or received in a physical downlink channel resource.

[0357] Aspect 68: The method according to any one of aspects 55 to 67, wherein the communication is a synchronization signal block (SSB).

[0358] Aspect 69: The method according to any one of aspects 55 to 68, wherein the communication is a random access channel message.

[0359] Aspect 70: The method according to any one of aspects 55 to 69, wherein the communication is a cross-link interference measurement resource.

[0360] Aspect 71: The method according to any one of Aspects 55 to 70, wherein the communication is a signal strength or signal quality measurement resource.

[0361] Aspect 72: The method according to any one of Aspects 55 to 71, wherein the communication is a paging message.

[0362] Aspect 73: The method according to any one of Aspects 55 to 72, wherein the communication is a system information block.

[0363] Aspect 74: The method according to any one of Aspects 55 to 73, the method further comprising: aligning resource timings in a plurality of multimedia traffic flows based at least in part on a common multiple number of multimedia traffic flows for a common outer loop.

[0364] Aspect 75: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of Aspects 1 to 74.

[0365] Aspect 76: A device for wireless communication, the device comprising: a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of Aspects 1 to 74.

[0366] Aspect 77: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of Aspects 1 to 74.

[0367] Aspect 78: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of Aspects 1 to 74.

[0368] Aspect 79: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of Aspects 1 to 74.

[0369] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure, or may be obtained from practice of the aspects.

[0370] As used herein, the term "component" is intended to be broadly construed as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, "software" shall be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, and / or functions, and the like. As used herein, a "processor" is implemented by hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by different forms of hardware and / or combinations of hardware and software. The actual specific control hardware or software code used to implement these systems and / or methods does not limit the various aspects. Accordingly, the operation and behavior of the systems and / or methods are not described herein with reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed at least in part based on the description herein to implement the systems and / or methods.

[0371] As used herein, depending on the context, "meeting a threshold" can mean that a value is greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, and the like.

[0372] Although specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. Many of these features can be combined in ways that are not specifically recited in the claims and / or not disclosed in the specification. The disclosure of the various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, the phrase referring to "at least one of" a list of items refers to any combination of those items (which includes a single member). By way of example, "at least one of a, b, or c" is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiple identical elements (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).

[0373] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Additionally, as used herein, the article "a" is intended to include one or more items and may be used interchangeably with "one or more." Further, as used herein, the article "the" is intended to include one or more items mentioned in connection with the article "the" and may be used interchangeably with "one or more." Additionally, as used herein, the terms "set" and "group" are intended to include one or more items and may be used interchangeably with "one or more." If only one item is intended to be referred to, the phrase "only one" or similar language will be used. Additionally, as used herein, the terms "has," "owns," "possesses," etc. are intended to be open-ended terms that do not limit the elements they modify (e.g., an element that "has" A may also have B). Additionally, the phrase "based on" is intended to mean "at least partially based on" unless otherwise explicitly stated. Additionally, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless otherwise clearly stated (e.g., if used in conjunction with "either" or "only one").

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a periodic configuration for a communication time, the communication time being a factor of a time division duplex (TDD) periodicity, wherein the communication time is at least partially based on a multimedia service periodicity; and transmitting or receiving communication during the communication time.

2. The method according to claim 1, wherein the communication time is at least partially based on a TDD pattern of the granted resources.

3. The method according to claim 1, wherein the communication time has a discontinuous reception (DRX) cycle.

4. The method according to claim 3, the method further comprising: adjusting a DRX offset value such that a DRX on duration is aligned with a downlink time slot of a TDD pattern.

5. The method according to claim 3, the method further comprising: adjusting a DRX offset value such that a DRX on duration is aligned with a configured grant or semi-persistent scheduling cycle.

6. The method according to claim 1, wherein the communication is a channel state information (CSI) reference signal (CSI-RS) or a CSI interference measurement resource, the method further comprising: aligning the periodicity and offset of the CSI-RS with a downlink time slot of a TDD pattern associated with the TDD periodicity.

7. The method according to claim 1, wherein the communication is a sounding reference signal (SRS), the method further comprising: aligning the SRS with an uplink time slot of a TDD pattern associated with the TDD periodicity.

8. The method according to claim 1, wherein the communication is at least one of the following: a scheduling request, a channel state information report, a buffer status report, a synchronization signal block (SSB), a random access channel message, a cross-link interference measurement resource, a signal strength or signal quality measurement resource, a paging message, or a system information block.

9. The method according to claim 1, wherein the communication is transmitted in a physical uplink channel resource or received in a physical downlink channel resource.

10. The method according to claim 1, the method further comprising: aligning resource timing in multiple multimedia service flows at least partially based on a common multiple number of multimedia service flows for a common external cycle.

11. The method according to claim 1, wherein the one or more communications are configured grant communications or semi-persistent scheduling communications, wherein the configuration indicates that the one or more communication times are included in the next available time slot in a TDD pattern associated with the TDD periodicity.

12. The method according to claim 1, wherein the multimedia service periodicity is a rational number.

13. A method of wireless communication performed by a network entity, the method comprising: transmitting a periodic configuration for a communication time, the communication time being a factor of a time division duplex (TDD) periodicity, wherein the communication time is at least partially based on a multimedia service periodicity; and transmitting or receiving communication during the communication time.

14. The method according to claim 13, wherein the communication time is at least partially based on a TDD pattern of the granted resources.

15. The method according to claim 13, wherein the communication time has a discontinuous reception (DRX) cycle.

16. The method according to claim 13, wherein the communication is a channel state information (CSI) reference signal (CSI-RS) or a CSI interference measurement resource, and the method further comprises: aligning the periodicity and offset of the CSI-RS with the downlink time slots of the TDD pattern.

17. The method according to claim 13, wherein the communication is a sounding reference signal (SRS), and the method further comprises: aligning the SRS with the uplink time slots of the TDD pattern.

18. The method according to claim 13, wherein the multimedia service periodicity is a rational number.

19. A user equipment (UE) for wireless communication, the user equipment (UE) comprises: one or more memories; and one or more processors, the one or more processors being coupled to the one or more memories, the one or more processors being configured to: receive a configuration for the periodicity of a communication time, the communication time being divisible by a time division duplex (TDD) periodicity or being a multiple of the time division duplex (TDD) periodicity, wherein the communication time is at least partially based on a multimedia service periodicity; and transmit or receive a communication during the communication time.

20. The UE according to claim 19, wherein the communication time is at least partially based on a TDD pattern of the granted resources.

21. The UE according to claim 19, wherein the communication is a channel state information (CSI) reference signal (CSI-RS) or a CSI interference measurement resource, and wherein the one or more processors are further configured to align the periodicity and offset of the CSI-RS with the downlink time slots of the TDD pattern.

22. The UE according to claim 19, wherein the communication is a sounding reference signal (SRS), and wherein the one or more processors are configured to align the SRS with the uplink time slots of the TDD pattern.

23. The UE according to claim 19, wherein the communication is at least one of the following: a scheduling request, a channel state information report, a buffer status report, a synchronization signal block (SSB), a random access channel message, a cross-link interference measurement resource, a signal strength or signal quality measurement resource, a paging message, or a system information block.

24. The UE according to claim 19, wherein, in order to transmit or receive the communication, the one or more processors are configured to: transmit the one or more communications in a physical uplink channel resource; or receive the one or more communications in a physical downlink channel resource.

25. The UE according to claim 19, wherein the one or more processors are configured to align the resource timing in a plurality of multimedia service flows at least partially based on a common multiple number of multimedia service flows for a common external cycle.

26. The UE according to claim 19, wherein the one or more communications are configured grant communications or semi-persistent scheduled communications, and wherein the configuration indicates that the one or more communication times are included in the next available time slot in the TDD mode associated with the TDD periodicity.

27. The UE according to claim 19, wherein the multimedia traffic periodicity is a rational number.

28. A network entity for wireless communication, the network entity comprising: one or more memories; and one or more processors, the one or more processors being coupled to the one or more memories and configured to: transmit a configuration for the periodicity of communication times, the communication times being a factor of a time division duplex (TDD) periodicity, wherein the communication times are at least partially based on a multimedia traffic periodicity; and transmit or receive communications at the communication times.

29. The network entity according to claim 28, wherein the communication times are at least partially based on the TDD mode of the granted resources.

30. The network entity according to claim 28, wherein the one or more processors are configured to align resource timing in a plurality of multimedia traffic flows at least partially based on a common multiple number of multimedia traffic flows for a common external cycle.

Images