Power control for burst communication
In wireless communication, the UE that receives burst metadata optimizes power state transition by using the power control instructions of the network entity, solving the problems of power waste and communication interruption in wireless communication, and achieving more efficient power management and communication efficiency.
Patent Information
- Application Number
- CN202380036738.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-04-21
- Filing Date
- 2023-04-24
- Publication Date
- 2024-12-06
AI Technical Summary
In wireless communication, user equipment (UE) may waste power resources while waiting for the inactive timer to expire, and reducing the timer length to save power may lead to premature entry of low power states, resulting in communication interruption or delay.
By receiving burst metadata associated with burst transmission, the network entity sends power control indications to trigger the transition of the UE from one communication state to another, avoiding excessive power hold and premature power saving state transitions.
Effectively save power resources, avoid communication interruptions and delays, optimize UE's power management, and improve communication efficiency.
Smart Images

Figure CN119096607A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 364,162, entitled “POWER CONTROL FOR BURST COMMUNICATIONS,” filed on May 4, 2022, and U.S. Non-Provisional Patent Application No. 18 / 304,740, entitled “POWER CONTROL FOR BURST COMMUNICATIONS,” filed on April 21, 2023, and assigned to the assignee of this application. The disclosures of these prior applications are considered part of and incorporated by reference into this patent application. Technical Field
[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for power control for bursty communications. Background Art
[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies 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 / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).
[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).
[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using 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. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention
[0007] In burst communications, such as for extended reality (XR) services or augmented reality (AR) services, application data units (ADUs) may be grouped into burst transmissions. For example, a single burst transmission may correspond to a video frame, and the ADU may correspond to a slice of the video frame. Similarly, packet data units (PDUs) may be grouped into a set of PDUs that are sent in a burst transmission. A user equipment (UE) may transition from a first communication state to a second communication state having a power different from that of the first communication state to reduce utilization of power resources. For example, a UE may transition from a discontinuous reception (DRX) on duration or active mode to a DRX off duration or sleep / inactive mode.
[0008] To switch between communication states, the network entity and / or the UE may use a timer to determine whether to remain in a particular state or transition to a different state. For example, in DRX communication, the UE may transition from a DRX on duration to a DRX off duration after an inactivity timer expires. However, in some cases, the UE may waste power resources while waiting for a timer such as an inactivity timer to expire. The length of the timer may be reduced to save power (e.g., by allowing the UE to enter a lower power state more quickly), but this may cause the UE to enter a lower power state prematurely (e.g., when the network entity has additional control information or data to send to the UE).
[0009] Some aspects described herein use burst metadata to provide burst awareness. For example, a first network entity (e.g., a base station) may receive a burst end indication associated with burst metadata accompanying a burst transmission of one or more packets from a second network entity (e.g., a core network entity, such as an application server (AS) or a user plane function (UPF), etc.). In this case, the first network entity may determine when the burst transmission will end, and may send a power control indication to trigger a transition from a first communication state (e.g., a DRX on duration) to a second communication state (e.g., a DRX off duration). Based at least in part on receiving the power control indication, the UE may transition from the first communication state to the second communication state. In this way, the UE avoids remaining in the first communication state for an excessively long period of time, thereby saving power resources. In addition, by transitioning based at least in part on receiving the power control indication, the UE avoids transitioning to a power saving state too early, thereby avoiding interrupting communication during the DRX off duration or excessive delays associated with delaying communication until the next DRX on duration.
[0010] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a burst transmission including one or more packets. The method may include transitioning from a first communication state to a second communication state based at least in part on receiving a power control indication triggered by a burst end indication associated with burst metadata accompanying the burst transmission, wherein the power of the second communication state is different from the power of the first communication state.
[0011] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include receiving a burst end indication associated with burst metadata accompanying a burst transmission of one or more packets, identifying an end of the burst transmission of the one or more packets. The method may include sending a power control indication in conjunction with the burst transmission of the one or more packets to indicate a transition from a first communication state to a second communication state, wherein a power of the second communication state is different from a power of the first communication state.
[0012] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a burst transmission including one or more packets. The one or more processors may be configured to transition from a first communication state to a second communication state based at least in part on receiving a power control indication triggered by a burst end indication associated with burst metadata accompanying the burst transmission, wherein the power of the second communication state is different from the power of the first communication state.
[0013] 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 receive a burst end indication associated with burst metadata accompanying a burst transmission of one or more packets, identifying the end of the burst transmission of one or more packets. The one or more processors may be configured to: send a power control indication in conjunction with the burst transmission of the one or more packets to indicate a transition from a first communication state to a second communication state, wherein the power of the second communication state is different from the power of the first communication state.
[0014] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a burst transmission including one or more packets. The instruction set, when executed by one or more processors of the UE, may cause the UE to transition from a first communication state to a second communication state based at least in part on receiving a power control indication triggered by a burst end indication associated with burst metadata accompanying the burst transmission, wherein the power of the second communication state is different from the power of the first communication state.
[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to receive a burst end indication associated with burst metadata accompanying a burst transmission of one or more packets, identifying an end of the burst transmission of the one or more packets. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send a power control indication in conjunction with the burst transmission of the one or more packets to indicate a transition from a first communication state to a second communication state, wherein a power of the second communication state is different from a power of the first communication state.
[0016] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a burst transmission, the burst transmission including one or more packets. The apparatus may include means for: transitioning from a first communication state to a second communication state based at least in part on receiving a power control indication triggered by a burst end indication associated with burst metadata accompanying the burst transmission, wherein a power of the second communication state is different from a power of the first communication state.
[0017] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a burst end indication associated with burst metadata accompanying a burst transmission of one or more packets, identifying an end of the burst transmission of the one or more packets. The apparatus may include means for transmitting a power control indication in conjunction with the burst transmission of the one or more packets to indicate a transition from a first communication state to a second communication state, wherein a power of the second communication state is different from a power of the first communication state.
[0018] 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 receive application data for transmission to a UE via another network entity. The one or more processors may be configured to transmit the application data with a burst end indication, the burst end indication being associated with burst metadata accompanying a burst transmission of one or more packets of the application data, identifying an end of the burst transmission of the one or more packets.
[0019] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include receiving application data for transmission to a UE via another network entity. The method may include transmitting the application data with a burst end indication associated with burst metadata accompanying a burst transmission of one or more packets of the application data, identifying an end of the burst transmission of the one or more packets.
[0020] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to receive application data for transmission to a UE via another network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to transmit the application data with a burst end indication, the burst end indication being associated with burst metadata accompanying a burst transmission of one or more packets of the application data, identifying an end of the burst transmission of the one or more packets.
[0021] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving application data for transmission to a UE via another apparatus. The apparatus may include means for transmitting the application data with a burst end indication associated with burst metadata accompanying a burst transmission of one or more packets of the application data, identifying an end of the burst transmission of the one or more packets.
[0022] The various aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.
[0023] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.
[0024] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology 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 integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various 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. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may 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 various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.
[0026] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.
[0027] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.
[0028] Figure 3 is a diagram illustrating an example of an open radio access network (O-RAN) architecture according to the present disclosure.
[0029] Figure 4 is a diagram illustrating an example of physical channels and reference signals in a wireless network according to the present disclosure.
[0030] Figure 5 is a diagram illustrating an example of a discontinuous reception (DRX) configuration according to the present disclosure.
[0031] Figure 6 is a diagram illustrating an example of a protocol stack for a network entity and a UE according to the present disclosure.
[0032] Figure 7 is a diagram illustrating an example associated with power control for burst communication according to the present disclosure.
[0033] Figures 8 to 10 is a diagram illustrating an example process associated with power control for bursty communications according to the present disclosure.
[0034] Figure 11 to Figure 12 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION
[0035] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of protection of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method implemented using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.
[0036] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0037] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).
[0038] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to 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, as well as other examples. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).
[0039] In some examples, the network node 110 is or includes a network node (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 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, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.
[0040] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 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 a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. The network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of the cells may move according to the location of the mobile network node 110 (e.g., a mobile network node).
[0041] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC) or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations 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 node" may refer to one of the base station functions, but not another base station function. In this way, a single device may include more than one base station.
[0042] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown, a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communications between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.
[0043] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).
[0044] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link. In some aspects, the network controller 130 may be, or may include, a CU or a core network device.
[0045] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station and / or a subscriber unit. 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 device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, 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, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node and / or any other suitable device configured to communicate via a wireless or wired medium.
[0046] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.
[0047] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.
[0048] 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., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.
[0049] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).
[0050] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.
[0051] In view of the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as frequencies that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that the term "millimeter wave" or the like, if used herein, can be broadly referred to as 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. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.
[0052] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, communication manager 140 may: receive a burst transmission including one or more packets; and transition from a first communication state to a second communication state based at least in part on receiving a power control indication triggered by a burst end indication associated with burst metadata accompanying the burst transmission, wherein a power of the second communication state is different from a power of the first communication state. Additionally or alternatively, communication manager 140 may perform one or more other operations described herein.
[0053] In some aspects, a network entity (e.g., a network node 110 or a core network device) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may: receive a burst end indication associated with burst metadata accompanying a burst transmission of one or more packets, identifying the end of the burst transmission of the one or more packets; and send a power control indication in conjunction with the burst transmission of the one or more packets to indicate a transition from a first communication state to a second communication state, wherein the power of the second communication state is different from the power of the first communication state. Additionally or alternatively, the communication manager 150 may receive application data for transmission to a UE via another network entity; and may send the application data with a burst end indication associated with burst metadata accompanying a burst transmission of one or more packets of the application data, identifying the end of the burst transmission of the one or more packets. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.
[0054] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Different than described.
[0055] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 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). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.
[0056] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., code and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, 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 to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).
[0057] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 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 to 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 a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide 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 a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.
[0058] 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 the network node 110 via the communication unit 294.
[0059] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or 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, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.
[0060] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a 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-decoded by a TX MIMO processor 266, where applicable, further processed by a modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. 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 an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 7 to 12 ) any aspects of any of the methods described herein.
[0061] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain 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 provide the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions described herein (e.g., reference 20). Figures 7 to 12 ) any aspects of any of the methods described herein.
[0062] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in the may perform one or more techniques associated with power control for bursty communications, as described in more detail elsewhere herein. In some aspects, the network entity described herein is a network node 110, is included in a network node 110, or includes Figure 2 One or more components of the network node 110 shown. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 8 The process of 800 Fig. 9 The process of 900 Fig.10 1000 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example Figure 8 The process of 800 Fig. 9 The process of 900 Fig.10 The process 1000 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.
[0063] In some aspects, the UE 120 includes: means for receiving a burst transmission, the burst transmission including one or more packets; and / or means for the following operations: transitioning from a first communication state to a second communication state based at least in part on receiving a power control indication triggered by a burst end indication associated with burst metadata accompanying the burst transmission, wherein the power of the second communication state is different from the power of the first communication state. The means for the UE 120 to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.
[0064] In some aspects, a network entity (e.g., network node 110 or a core network entity) includes: a component for receiving a burst end indication, the burst end indication associated with burst metadata accompanying a burst transmission of one or more packets, identifying the end of the burst transmission of the one or more packets; and / or a component for the following operations: sending a power control indication in conjunction with the burst transmission of the one or more packets to indicate a transition from a first communication state to a second communication state, wherein the power of the second communication state is different from the power of the first communication state. Additionally or alternatively, the network entity may receive application data for transmission to a UE via another network entity; and may send the application data with a burst end indication, the burst end indication associated with burst metadata accompanying the burst transmission of one or more packets of the application data, identifying the end of the burst transmission of the one or more packets. In some aspects, means for a network entity to perform operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.
[0065] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality 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 functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.
[0066] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Different than described.
[0067] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).
[0068] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack 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 examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.
[0069] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may 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 a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Various units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.
[0070] Figure 3 3 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. The DU 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served by multiple RUs 340 simultaneously.
[0071] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, and the wireless interface being configured to receive signals or send signals to one or more of the other units via a wireless transmission medium, or both.
[0072] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, 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 unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.
[0073] Each 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 a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to a functional split (such as a functional split defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) coding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.
[0074] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional splits (e.g., functional splits defined by 3GPP) such as lower layer functional splits, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.
[0075] The SMO framework 305 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.
[0076] The non-RT RIC 315 may be configured to include logic functions that 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 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.
[0077] In some implementations, in order to generate an AI / ML model 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 may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or 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 through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).
[0078] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Different than described.
[0079] Figure 4 4 is a diagram illustrating an example 400 of physical channels and reference signals in a wireless network according to the present disclosure. Figure 4 As shown, the downlink channel and the downlink reference signal may carry information from the network entity 402 to the UE 120 , and the uplink channel and the uplink reference signal may carry information from the UE 120 to the network entity 402 .
[0080] As shown, the downlink channel may include a physical downlink control channel (PDCCH) carrying downlink control information (DCI), a physical downlink shared channel (PDSCH) carrying downlink data, or a physical broadcast channel (PBCH) carrying system information, etc. PDSCH communication may be scheduled via PDCCH communication. As further shown, the uplink channel may include a physical uplink control channel (PUCCH) carrying uplink control information (UCI), a physical uplink shared channel (PUSCH) carrying uplink data, or a PRACH for initial network access, etc. UE 120 may send an acknowledgement (ACK) or negative acknowledgement (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in the UCI on the PUCCH and / or PUSCH.
[0081] As further shown, the downlink reference signal may include a synchronization signal block (SSB), a channel state information (CSI) reference signal (CSI-RS), a DMRS, a positioning reference signal (PRS), or a phase tracking reference signal (PTRS), etc. As also shown in the figure, the uplink reference signal may include a sounding reference signal (SRS), a DMRS, or a PTRS, etc.
[0082] The SSB may carry information used for initial network acquisition and synchronization, such as PSS, SSS, PBCH, and PBCH DMRS. The SSB is sometimes referred to as a synchronization signal / PBCH (SS / PBCH) block. The network entity 402 may send multiple SSBs on multiple corresponding beams, and the SSB may be used for beam selection.
[0083] The CSI-RS may carry information for downlink channel estimation (e.g., downlink CSI acquisition), which may be used for scheduling, link adaptation, or beam management, etc. The network entity 402 may configure a CSI-RS set for the UE 120, and the UE 120 may measure the configured CSI-RS set. Based at least in part on the measurements, the UE 120 may perform channel estimation and may report channel estimation parameters (e.g., in a CSI report) such as CQI, a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a layer indicator (LI), a rank indicator (RI), or RSRP, etc., to the network entity 402. The network entity 402 may use the CSI report to select transmission parameters for downlink communication to the UE 120, such as the number of transmission layers (e.g., rank), a precoding matrix (e.g., a precoder), an MCS, or a refined downlink beam (e.g., using a beam refinement process or a beam management process), etc.
[0084] DMRS can carry information used to estimate the radio channel to demodulate the associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of DMRS can be specific to the physical channel that the DMRS is used to estimate. DMRS is UE-specific, can be beamformed, can be restricted to scheduled resources (e.g., instead of being sent over a wideband), and can be sent only when necessary. As shown, DMRS is used for both downlink and uplink communications.
[0085] PTRS can carry information for compensating for oscillator phase noise. Typically, phase noise increases with the increase of the oscillator carrier frequency. Therefore, PTRS can be used at high carrier frequencies (such as millimeter wave frequencies) to mitigate phase noise. PTRS can be used to track the phase of the local oscillator and to achieve suppression of phase noise and common phase error (CPE). As shown, PTRS is used for both downlink communications (e.g., on PDSCH) and uplink communications (e.g., on PUSCH).
[0086] The PRS may carry information for implementing timing or ranging measurements of the UE 120 based on signals sent by the network entity 402 to improve observed time difference of arrival (OTDOA) positioning performance. For example, the PRS may be a pseudo-random quadrature phase shift keying (QPSK) sequence mapped in a diagonal pattern with a frequency offset and a time offset to avoid conflicts with cell-specific reference signals and control channels (e.g., PDCCH). In general, the PRS may be designed to improve the detectability of the UE 120, which may require detecting downlink signals from multiple neighboring base stations in order to perform OTDOA-based positioning. Thus, the UE 120 may receive PRS from multiple cells (e.g., a reference cell and one or more neighboring cells), and may report a reference signal time difference (RSTD) based on OTDOA measurements associated with the PRS received from the multiple cells. The network entity 402 may then calculate the position of the UE 120 based on the RSTD measurements reported by the UE 120.
[0087] The SRS may carry information for uplink channel estimation, which may be used for scheduling, link adaptation, pre-decoder selection, or beam management, etc. The network entity 402 may configure one or more SRS resource sets for the UE 120, and the UE 120 may send the SRS on the configured SRS resource sets. The SRS resource sets may have configured usages, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, etc. The network entity 402 may measure the SRS, may perform channel estimation based at least in part on these measurements, and may use the SRS measurements to configure communications with the UE 120.
[0088] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 Different than described.
[0089] Figure 5 is a diagram illustrating an example 500 of a discontinuous reception (DRX) configuration according to the present disclosure.
[0090] like Figure 5As shown, the network entity 502 may send a DRX configuration to the UE 120 to configure a DRX cycle 505 for the UE 120. The DRX cycle 505 may include a DRX on duration 510 (e.g., during which the UE 120 is awake or active) and an opportunity to enter a DRX sleep state 515. As used herein, the time during which the UE 120 is configured to be active during the DRX on duration 510 may be referred to as an active time, and the time during which the UE 120 is configured to be in the DRX sleep state 515 may be referred to as an inactive time. As described below, the UE 120 may monitor the PDCCH during the active time and may avoid monitoring the PDCCH during the inactive time.
[0091] During the DRX on duration 510 (e.g., active time), the UE 120 may monitor a downlink control channel (e.g., PDCCH), as indicated by reference numeral 520. For example, the UE 120 may monitor the PDCCH for DCI related to the UE 120. If the UE 120 does not detect and / or successfully decode any PDCCH communication intended for the UE 120 during the DRX on duration 510, the UE 120 may enter a sleep state 515 (e.g., during the inactive time) at the end of the DRX on duration 510, as indicated by reference numeral 525. In this way, the UE 120 may save battery power and reduce power consumption. As shown, the DRX cycle 505 may be repeated at a configured periodicity according to the DRX configuration.
[0092] If the UE 120 detects and / or successfully decodes a PDCCH communication intended for the UE 120, the UE 120 may remain in an active state (e.g., awake) for the duration of the DRX inactivity timer 530 (e.g., which may extend the active time). The UE 120 may start the DRX inactivity timer 530 at the time the PDCCH communication is received (e.g., per a transmit time interval (TTI), such as a timeslot or subframe, in which the PDCCH communication is received). The UE 120 may remain in an active state until the DRX inactivity timer 530 expires, at which time the UE 120 may enter a sleep state 515 (e.g., within the inactivity time), as indicated by reference numeral 535. During the duration of the DRX inactivity timer 530, the UE 120 may continue to monitor PDCCH communications, may obtain downlink data communications scheduled by the PDCCH communications (e.g., on a downlink data channel such as PDSCH), and / or may prepare and / or transmit uplink communications scheduled by the PDCCH communications (e.g., on PUSCH). The UE 120 may restart the DRX inactivity timer 530 each time a PDCCH communication for an initial transmission (e.g., not for a retransmission) is detected for the UE 120. By operating in this manner, the UE 120 may conserve battery power and reduce power consumption by entering the sleep state 515.
[0093] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 Different than described.
[0094] Figure 6 6 is a diagram illustrating an example 600 of a protocol stack for a network entity 602 / 604 / 606 / 608 and a UE 120 according to the present disclosure. The network entity 602 may correspond to Figure 3 DU 330, the network entity 604 may correspond to Figure 3 CU 310, and network entities 606 and 608 may be associated with Figure 3 The core network 320 is associated with the core network device.
[0095] UE 120 and network entity 602 may include corresponding PHY layer, MAC layer and RLC layer. In addition, UE 120 may have PDCP layer, SDAP layer and application layer. Network entity 602 may have General Packet Radio Service (GPRS) Tunneling Protocol (GTP) User Plane (U) (GTP-U) layer, which is the endpoint of GTP-U packet. Network entity 602 and UE 120 may communicate via Uu interface. Network entity 602 and network entity 604 may communicate via F1 interface. Network entity 604 may have Internet Protocol (IP) layer, User Datagram Protocol (UDP) layer, GTP-U layer, PDCP layer and SDAP layer. User plane function (e.g., network entity 606) may handle the transmission of user data between UE 120 and network entity 602.
[0096] Generally, if the first layer is farther from the PHY layer than the second layer, the first layer is referred to as being above the second layer. For example, the PHY layer may be referred to as the lowest layer, and the SDAP / PDCP / RLC / MAC layer may be referred to as being above the PHY layer. The application layer may be above the SDAP / PDCP / RLC / MAC layer. In some cases, an entity may handle services and functions of a given layer (e.g., a PDCP entity may handle services and functions of a PDCP layer), although the description herein refers to the layers themselves handling these services and functions.
[0097] The SDAP layer, the PDCP layer, the RLC layer, and the MAC layer may be collectively referred to as Layer 2 (L2). Therefore, in some cases, the SDAP, PDCP, RLC, and MAC layers are referred to as sublayers of Layer 2. On the transmitting side (e.g., if the UE 120 is sending uplink communications or the network entity 602 / 604 is sending downlink communications), the SDAP layer may receive data streams in the form of quality of service (QoS) flows. A QoS flow is associated with a QoS identifier and a QoS flow identifier (QFI), which identifies QoS parameters associated with the QoS flow, and the QoS flow identifier (QFI) identifies the QoS flow. Policy and charging parameters are implemented based on the QoS flow granularity. A QoS flow may include one or more service data flows (SDFs), as long as each SDF of the QoS flow is associated with the same policy and charging parameters.
[0098] The SDAP layer may map QoS flows or control information to radio bearers. Therefore, it can be said that the SDAP layer handles QoS flows on the sending side. The SDAP layer may provide QoS flows to the PDCP layer via corresponding radio bearers. The PDCP layer may map radio bearers to RLC channels. The PDCP layer may handle various services and functions on the user plane, including sequence numbering, header compression and decompression (if robust header compression is enabled), delivery, reordering and duplication detection of user data (if in-order delivery to layers above the PDCP layer is required), PDCP protocol data unit (PDU) routing (in the case of split bearers), retransmission, encryption and decryption of PDCP service data units (SDUs), PDCP SDU discard (e.g., based on a timer, as described elsewhere herein), PDCP reestablishment and data recovery for RLC acknowledgement mode (AM), and duplication of PDCP PDUs. The PDCP layer may handle similar services and functions on the control plane, including sequence numbering, encryption, decryption, integrity protection, delivery of control plane data, duplication detection, and duplication of PDCP PDUs.
[0099] The PDCP layer may provide data in the form of PDCP PDUs to the RLC layer via an RLC channel. The RLC layer may handle delivery of upper layer PDUs to the MAC and / or PHY layers, sequence numbering independent of the PDCP sequence numbering, error correction via automatic repeat request (ARQ), segmentation and re-segmentation, reassembly of SDUs, RLC SDU discard, and RLC reestablishment.
[0100] The RLC layer can provide the MAC layer with data mapped to logical channels. The services and functions of the MAC layer include mapping between logical channels and transport channels (used by the PHY layer as described below), multiplexing MAC SDUs belonging to one or different logical channels into a transport block (TB) delivered to / from the physical layer on the transport channel, scheduling information reporting, error correction by hybrid ARQ (HARQ), priority handling between UEs with dynamic scheduling, priority handling between logical channels of a UE with logical channel prioritization, and padding.
[0101] The MAC layer can encapsulate data from logical channels into TBs and provide the TBs to the PHY layer on one or more transport channels. The PHY layer can handle various operations related to the transmission of data signals, such as combining Figure 2 The PHY layer is often referred to as Layer 1 (L1).
[0102] On the receiving side (e.g., if the UE 120 is receiving downlink communications or the network entity 602 is receiving uplink communications), operations may be similar to those described for the transmitting side, but in the opposite direction. For example, the PHY layer may receive TBs and may provide TBs to the MAC layer on one or more transport channels. The MAC layer may map transport channels to logical channels and may provide data to the RLC layer via the logical channels. The RLC layer may map logical channels to RLC channels and may provide data to the PDCP layer via the RLC channels. The PDCP layer may map RLC channels to radio bearers and may provide data to the SDAP layer via the radio bearers.
[0103] Data may be passed between layers in the form of PDUs and SDUs. An SDU is a unit of data that has been passed from a layer or sublayer to a lower layer. For example, a PDCP layer may receive a PDCP SDU. A given layer may then encapsulate the data unit into a PDU and may pass the PDU to a lower layer. For example, a PDCP layer may encapsulate a PDCP SDU into a PDCP PDU and may pass the PDCP PDU to an RLC layer. An RLC layer may receive a PDCP PDU as an RLC SDU, may encapsulate the RLC SDU into an RLC PDU, and so on. In effect, a PDU carries an SDU as a payload.
[0104] The network entity 606 (e.g., a user plane function (UPF)) may have an IP layer, a UDP layer, a GTP-U layer, and a service layer. The network entity 606 may communicate burst metadata to the network entity 604 and / or the network entity 602 via the N3 interface. The GTP-U layer of the network entity 606 may form the other end point of a GTP-U flow with the GTP-U layer of the network entity 602. The UE 120 may have an application layer that receives IP packets from the network entity 608. The network entity 608 may send IP packets to the network entity 606 using burst signaling for routing to the UE 120.
[0105] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 Different than described.
[0106] In burst communications, such as for extended reality (XR) services or augmented reality (AR) services, application data units (ADUs) may be grouped into burst transmissions. For example, a single burst transmission may correspond to a video frame, and the ADU may correspond to a slice of the video frame. Similarly, PDUs may be grouped into sets of PDUs that are sent in burst transmissions. "Burst transmission" may refer to data transmissions in which, for example, a group of packets are grouped together within a first threshold time period, but are separated from other burst transmissions, for example, by a second threshold time period. In addition, burst transmissions may have some commonalities, such as shared header information, but may have differences, such as including different numbers of ADUs in different burst transmissions or including different numbers of packets in different ADUs.
[0107] As described above, the UE may transition from a first communication state to a second communication state having a power different from that of the first communication state to reduce the utilization of power resources. For example, the UE may transition from a DRX on duration or an active mode to a DRX off duration or a sleep / inactive mode. In order to switch between communication states, the network entity and / or the UE may use a timer to determine whether to remain in a particular state or transition to a different state. For example, in DRX communication, the UE may transition from a DRX on duration to a DRX off duration after the inactivity timer expires.
[0108] As an example, when the UE is in the DRX off duration, the UE cannot receive a scheduling grant or assignment, which may prevent the UE from receiving data communications, for example, on the PDSCH. Therefore, the UE may use a timer to determine whether to remain in the DRX on duration (and continue to monitor the PDCCH) or to transition to the DRX off duration; each time the UE receives a PDCCH indicating a new uplink or downlink transmission, the timer is restarted. However, in some cases, the UE may waste power resources while waiting for a timer such as an inactivity timer to expire. For example, when the UE receives a PDCCH, the UE may reset the inactivity timer, but may not receive further communications within the duration of the inactivity timer. In this case, the period when the UE is waiting for the inactivity timer but has not received further communications (or sent any communications) may be a period when the UE may have been in a lower power state. For example, in burst communications, the burst transmission may be shorter than the inactivity timer duration, which may cause the UE to stay in the DRX on duration for a period of time after the burst transmission has ended. The length of the inactivity timer may be reduced to save power (e.g., by allowing the UE to enter a lower power state more quickly), but this may cause the UE to enter a lower power state prematurely (e.g., when a network entity has additional control information or data to send to the UE).
[0109] Some aspects described herein use burst metadata to provide burst awareness. For example, a first network entity (e.g., a base station) may receive a burst end indication associated with burst metadata accompanying a burst transmission of one or more packets from a second network entity (e.g., a core network entity, such as an application server (AS) or a UPF, etc.). In this case, the first network entity may determine when the burst transmission will end, and may send a power control indication to trigger a transition from a first communication state (e.g., a DRX on duration) to a second communication state (e.g., a DRX off duration). Based at least in part on receiving the power control indication, the UE may transition from the first communication state to the second communication state. In this way, the UE avoids remaining in the first communication state for an excessively long period of time, thereby saving power resources. In addition, by transitioning based at least in part on receiving the power control indication, the UE avoids transitioning to a power saving state too early, thereby avoiding interrupting communication during the DRX off duration or excessive delays associated with communication being delayed until the next DRX on duration.
[0110] Figure 7 is a diagram illustrating an example 700 associated with power control for burst communications according to the present disclosure. Figure 7 As shown, example 700 includes communications between a first network entity 702 (e.g., network node 110, CU 310, DU 330, RU 340, network entity 602, or network entity 604), a second network entity 704 (e.g., AS, UPF, network entity 606, or network entity 608), and UE 120.
[0111] like Figure 7 1 and further shown by reference numeral 710, a first network entity 702 may receive a burst transmission and provide the burst transmission to a UE 120. For example, the first network entity 702 may receive and transmit a service flow having a burst packet structure (e.g., a set of packets of a set of ADUs forming a burst). In some aspects, one or more second network entities 704 communicate burst signaling related to the burst transmission to enable the burst transmission and the associated burst end indication. For example, an edge server (e.g., an AS) may communicate burst signaling to a UPF, which may be accompanied by burst metadata in an IP packet of the burst transmission.
[0112] like Figure 7 7 and further illustrated by reference numerals 720 and 730, the first network entity 702 may receive a burst end indication in conjunction with the burst transmission and may send a power control indication, such as a power save indication.
[0113] In some aspects, the first network entity 702 may receive ADU information from the second network entity 704, which may implement the transmission of the power control indication. For example, the second network entity 704 may generate a GTP-U header, which includes one or more ADU-aware fields, which may include ADU metadata (e.g., the ADU metadata may include burst metadata or be included in the burst metadata). In this case, the first network entity 702 may receive the GTP-U header and identify a field, which includes an ADU-based service flow flag, an ADU sequence number in a burst, a burst sequence number, a size of the ADU, an ADU content policy, an ADU discard time, or an IP sequence number in the ADU.
[0114] In some aspects, the first network entity 702 may receive burst metadata having a field indicating the last PDU in a burst transmission. For example, the first network entity 702 may identify a burst service flow flag and / or a last PDU of a burst flag. In this case, when the last PDU of the burst flag is set to, for example, "0" for an IP packet, the IP packet is not the last packet of the burst transmission. Conversely, when the last PDU of the burst flag is set to, for example, "1" for the IP packet, the IP packet is the last packet of the burst transmission. In this case, the first network entity 702 may send a power control indication after or in conjunction with sending the last packet of the burst transmission. In this way, the first network entity 702 achieves power savings in the following scenarios: packets arrive at the first network entity 702 in order, the number of IP packets in the burst transmission is not available at the output of the encoder (e.g., when the packets are transmitted before being fully encoded, such as for low-latency applications), and / or when the first network entity 702 only needs burst awareness information for power savings (e.g., and not for FEC or other functionality).
[0115] In some aspects, the first network entity 702 may detect or predict packet loss associated with burst transmission and may fall back to an inactivity timer. For example, the first network entity 702 may detect that a packet has been lost based on a set of packet sequence numbers (e.g., the first network entity 702 may detect a missing sequence number in a set of sequence numbers). Similarly, the first network entity 702 may predict that packet loss may occur based on detected conditions, such as the amount of traffic occurring in the network or the quality of the connection between the first network entity 702 and the second network entity 704, etc. In these cases, the packet loss or predicted packet loss may cause the first network entity 702 to miss burst metadata, such as an end-of-burst indication. Therefore, the first network entity 702 may fall back to using, for example, an inactivity timer to determine when to send a power control indication. In this way, the first network entity 702 avoids the UE 120 remaining in the first communication state for an excessive period of time due to missed end-of-burst indications and failure to send power control indications.
[0116] In some aspects, the first network entity 702 may receive burst metadata in, for example, a GTP-U header, the burst metadata having a set of fields to enable the first network entity 702 to send a power control indication in an out-of-order packet scenario. For example, the first network entity 702 may receive burst metadata, the burst metadata including a burst service flow flag, a burst sequence number, an indicator of the number of IP packets in a burst or the last PDU of the burst flag, and / or an IP sequence number in a burst indicator. The burst service flow flag may indicate whether the IP packet belongs to an ADU-based service flow, in which case the first network entity 702 may interpret other elements of the burst metadata as providing information related to the burst transmission (e.g., when the IP packet does not belong to an ADU-based service flow, the first network entity 702 may ignore other elements of the burst metadata, or may interpret other elements of the burst metadata for another purpose). Other elements of the burst metadata may include information identifying a header packet, a set of intermediate packets, and a last packet of the ADU. The burst sequence number may indicate a burst transmission including an IP packet. The indicator of the number of IP packets in a burst may enable the first network entity 702 to count the number of IP packets received in a burst transmission to identify the last packet of the burst transmission. The IP sequence number in the burst indicator may identify an IP packet within the burst transmission.
[0117] The first network entity 702 may use burst metadata to identify the end of a burst transmission even when packets are received out of order (e.g., using an indication of the number of IP packets in a burst to count packets, and using an indication of the burst sequence number and the IP sequence number to determine which packets are associated with which burst or other transmission). Additionally or alternatively, when packet loss occurs, the first network entity 702 may use the burst sequence number and the number of IP packets in the burst indicator (or the last PDU of the burst flag) to detect packet loss. In this case, when the first network entity 702 detects packet loss, the first network entity 702 may fall back to using an inactivity timer to trigger the transmission of a power control indication, as described above.
[0118] In some aspects, the first network entity 702 may receive burst metadata and ADU metadata. For example, the first network entity 702 may receive a set of information elements for burst metadata and a set of information elements for ADU metadata. In this case, the first network entity 702 may interpret information elements that identify a burst service flow flag, a last ADU of a burst flag (e.g., the ADU is set in all PDUs of the last ADU), an ADU sequence number indicator, an ADU content policy indicator (e.g., the minimum percentage of burst bits to be delivered when the ADU is FEC protected), an ADU discard time indicator, or a size of an ADU indicator, etc. In some aspects, the first network entity 702 may receive burst metadata and ADU metadata that convey all of the aforementioned information elements. By receiving the aforementioned information elements, the first network entity 702 may provide a power saving indication to the UE 120 in a scenario where packets are received in sequence and the number of ADUs in a burst is not available at the output of the encoder, as described above. In addition, when first network entity 702 receives the burst metadata and the ADU metadata, the ADU may be FEC protected, which may enable first network entity 702 to send a power saving indication to cause UE 120 to transition to a lower power state before the last IP packet of the burst transmission is received. In this case, first network entity 702 may send the power saving indication when a threshold percentage of IP packets have been received (e.g., the threshold is based at least in part on the ADU content policy indicator), and FEC protection of the ADU may take into account any IP packets after UE 120 enters the lower power state.
[0119] Additionally or alternatively, the first network entity 702 may receive a set of information elements of burst metadata and ADU metadata, including information elements conveying a burst service flow flag, a burst sequence number, a number of ADUs in a burst, or an indicator of the last ADU of a burst flag, an ADU sequence number, an ADU content policy, an ADU discard time, or a size of an ADU, etc. In some aspects, the first network entity 702 may receive burst metadata and ADU metadata conveying all of the aforementioned information elements. In this way, the first network entity 702 may send a power saving indication when the number of ADUs in a burst is available at the output of the encoder and when FEC is enabled for the ADU.
[0120] like Figure 7 1 and further indicated by reference numeral 740, UE 120 may transition from the first communication state to the second communication state based at least in part on receiving a power control indication. For example, when UE 120 receives a power control indication (e.g., triggered by an end-of-burst indication explicitly conveyed or derived based on burst metadata and / or ADU metadata, or triggered at least in part based on a timer as a backoff), UE 120 may transition to a different (e.g., lower) power state (e.g., to reduce consumption of power resources).
[0121] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 Different than described.
[0122] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a UE in accordance with the present disclosure. Example process 800 is an example of a UE (eg, UE 120) performing operations associated with power control for bursty communications.
[0123] like Figure 8 As shown, in some aspects, process 800 may include receiving a burst transmission of one or more packets (block 810). For example, a UE (e.g., using Fig.11 The communications manager 140 and / or receiving component 1102 depicted in FIG. 10A may receive a burst transmission comprising one or more packets, as described above.
[0124] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include transitioning from a first communication state to a second communication state based at least in part on receiving a power control indication triggered by a burst end indication associated with burst metadata transmitted with the burst, wherein a power of the second communication state is different from a power of the first communication state (block 820). For example, a UE (e.g., using Fig.11The communication manager 140 and / or communication state change component 1108 depicted in the figure may transition from a first communication state to a second communication state based at least in part on receiving a power control indication triggered by a burst end indication associated with burst metadata transmitted along with the burst, wherein the power of the second communication state is different from the power of the first communication state, as described above.
[0125] Process 800 may include additional aspects, such as any single aspect and / or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.
[0126] In a first aspect, the burst end indication comprises an indicator in the packet indicating that the packet is the last packet transmitted in the burst.
[0127] In a second aspect, either alone or in combination with the first aspect, the burst end indication is based at least in part on at least one of: a burst service flow parameter, a burst sequence number parameter, a burst end flag, a parameter identifying the number of packets in a burst transmission, or a parameter identifying the sequence number of one or more packets in a burst transmission.
[0128] In a third aspect, alone or in combination with one or more of the first and second aspects, the burst end indication is based at least in part on burst metadata included in a general packet radio service tunneling protocol user plane header of at least one packet.
[0129] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the burst metadata comprises a burst service flow parameter, a burst sequence number parameter, a parameter indicating one or more last ADUs of the burst, or an ADU sequence number parameter.
[0130] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the burst metadata includes an ADU content policy parameter, an ADU discard time parameter, or an ADU size parameter.
[0131] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, transitioning from the first communication state to the second communication state includes transitioning from the first communication state to the second communication state based at least in part on detection of packet loss and expiration of a timer.
[0132] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.
[0133] Fig. 9 900 is a diagram illustrating an example process 900 performed, for example, by a network entity according to the present disclosure. Example process 900 is an example in which a network entity (e.g., network node 110, CU 310, DU 330, RU 340, or network entity 402 / 502 / 602 / 604 / 606 / 702 / 704, etc.) performs operations associated with power control for bursty communications.
[0134] like Fig. 9 As shown, in some aspects, process 900 may include receiving a burst end indication associated with burst metadata accompanying a burst transmission of one or more packets, identifying an end of the burst transmission of the one or more packets (block 910). For example, a network entity (e.g., using Fig.12 The communication manager 150 and / or receiving component 1202 depicted in FIG. 1 may receive a burst end indication associated with burst metadata accompanying a burst transmission of one or more packets, identifying the end of the burst transmission of one or more packets, as described above.
[0135] like Fig. 9 As further shown in FIG. 9 , in some aspects, process 900 may include transmitting a power control indication in conjunction with the burst transmission of the one or more packets to indicate a transition from a first communication state to a second communication state, wherein a power of the second communication state is different from a power of the first communication state (block 920). For example, a network entity (e.g., using Fig.12 The communication manager 150 and / or sending component 1204 depicted in the figure may send a power control indication in conjunction with the burst transmission of the one or more packets to indicate a transition from a first communication state to a second communication state, wherein the power of the second communication state is different from the power of the first communication state, as described above.
[0136] Process 900 may include additional aspects, such as any single aspect and / or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.
[0137] In a first aspect, a burst end indication is included in the burst metadata.
[0138] In a second aspect, alone or in combination with the first aspect, the burst end indication comprises an indicator in a packet associated with a burst transmission, the indicator indicating that the packet is the last packet of the burst transmission.
[0139] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 900 includes detecting packet loss associated with burst transmission, and sending a power control indication includes sending a power control indication based at least in part on detecting the packet loss and expiration of a timer.
[0140] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the burst metadata associated with the burst end indication includes at least one of the following: a burst service flow parameter, a burst sequence number parameter, a burst end flag, a parameter identifying the number of packets in a burst transmission, or a parameter identifying the sequence number of one or more packets in a burst transmission.
[0141] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, burst metadata associated with the burst end indication is included in a general packet radio service tunneling protocol user plane header of the one or more packets.
[0142] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the burst metadata associated with the burst end indication comprises at least one of: a burst service flow parameter, a burst sequence number parameter, a parameter indicating the last one or more ADUs sent in the burst, or an ADU sequence number parameter.
[0143] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the burst metadata associated with the burst end indication comprises at least one of: an ADU content policy parameter, an ADU discard time parameter, or an ADU size parameter.
[0144] although Fig. 9 Example blocks of process 900 are shown, but in some aspects, process 900 may include Fig. 9 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.
[0145] Fig.10 1 is a diagram illustrating an example process 1000 performed, for example, by a network entity according to the present disclosure. Example process 1000 is an example in which a network entity (e.g., network node 110, CU 310, DU 330, RU 340, or network entity 402 / 502 / 602 / 604 / 606 / 702 / 704, etc.) performs operations associated with power control for bursty communications.
[0146] like Fig.10As shown, in some aspects, process 1000 may include receiving application data for transmission to a UE via another network entity (block 1010). For example, a network entity (e.g., using Fig.12 The communications manager 150 and / or receiving component 1202 depicted in FIG. 1 may receive application data for transmission to a UE via another network entity, as described above.
[0147] like Fig.10 As further shown in FIG. 1 , in some aspects, process 1000 may include transmitting application data with a burst end indication associated with burst metadata accompanying a burst transmission of one or more packets of the application data, identifying an end of the burst transmission of the one or more packets (block 1020). For example, a network entity (e.g., using Fig.12 The communication manager 150 and / or sending component 1204 depicted in the figure may send application data with a burst end indication, which is associated with burst metadata accompanying a burst transmission of one or more packets of the application data, identifying the end of the burst transmission of the one or more packets, as described above.
[0148] Process 1000 may include additional aspects, such as any single aspect and / or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.
[0149] In a first aspect, a burst end indication is included in the burst metadata.
[0150] In a second aspect, alone or in combination with the first aspect, the burst end indication comprises an indicator in a packet associated with a burst transmission, the indicator indicating that the packet is the last packet of the burst transmission.
[0151] In a third aspect, either alone or in combination with one or more of the first and second aspects, the burst metadata associated with the burst end indication includes at least one of the following: a burst service flow parameter, a burst sequence number parameter, a burst end flag, a parameter identifying the number of packets in a burst transmission, or a parameter identifying the sequence number of one or more packets in a burst transmission.
[0152] In a fourth aspect, alone or in combination with one or more of the first to third aspects, burst metadata associated with the burst end indication is included in a general packet radio service tunneling protocol user plane header of the one or more packets.
[0153] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the burst metadata associated with the burst end indication comprises at least one of: a burst service flow parameter, a burst sequence number parameter, a parameter indicating the last one or more ADUs sent in the burst, or an ADU sequence number parameter.
[0154] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the burst metadata associated with the burst end indication comprises at least one of: an ADU content policy parameter, an ADU discard time parameter, or an ADU size parameter.
[0155] although Fig.10 Example blocks of process 1000 are shown, but in some aspects, process 1000 may include Fig.10 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.
[0156] Fig.11 1 is a diagram of an example apparatus 1100 for wireless communication. Apparatus 1100 may be a UE, or a UE may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a transmitting component 1104 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and transmitting component 1104. As further shown, apparatus 1100 may include a communication manager 140. Communication manager 140 may include one or more of a communication state change component 1108, etc.
[0157] In some aspects, the apparatus 1100 may be configured to perform Figure 7 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Figure 8 The process 800. In some aspects, Fig.11 The device 1100 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.11 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the component set may be implemented at least in part 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 can be executed by a controller or processor to perform the function or operation of the component.
[0158] The receiving component 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.
[0159] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.
[0160] Receiving component 1102 can receive a burst transmission including one or more packets. Communication state changing component 1108 can transition from a first communication state to a second communication state based at least in part on receiving a power control indication triggered by an end-of-burst indication associated with burst metadata accompanying the burst transmission, wherein a power of the second communication state is different from a power of the first communication state.
[0161] Fig.11 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.11Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The illustrated set (one or more) of components may be described as being executable by Fig.11 Another group of components shown performs one or more functions.
[0162] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication. Apparatus 1200 may be a network entity, or a network entity may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a transmitting component 1204 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and transmitting component 1204. As further shown, apparatus 1200 may include a communication manager 150. Communication manager 150 may include a detection component 1208, etc.
[0163] In some aspects, the apparatus 1200 may be configured to perform Figure 7 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Fig. 9 Process 900 or Fig.10 The process 1000 etc. In some aspects, Fig.12 The device 1200 and / or one or more components shown may include a combination of Figure 2 One or more components of the network entity. Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part 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 can be executed by a controller or processor to perform the function or operation of the component.
[0164] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the network entity.
[0165] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the network entity. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.
[0166] The receiving component 1202 can receive a burst end indication associated with burst metadata accompanying a burst transmission of one or more packets, identifying an end of the burst transmission of one or more packets. The transmitting component 1204 can transmit a power control indication in conjunction with the burst transmission of the one or more packets to indicate a transition from a first communication state to a second communication state, wherein the power of the second communication state is different from the power of the first communication state. The detecting component 1208 can detect packet loss associated with the burst transmission.
[0167] Fig.12 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.12 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The illustrated set (one or more) of components may be described as being executable by Fig.12 Another group of components shown performs one or more functions.
[0168] The following provides an overview of some aspects of the disclosure:
[0169] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a burst transmission including one or more packets; and transitioning from a first communication state to a second communication state based at least in part on receiving a power control indication triggered by a burst end indication associated with burst metadata accompanying the burst transmission, wherein the power of the second communication state is different from the power of the first communication state.
[0170] Aspect 2: The method according to aspect 1, wherein the burst end indication comprises an indicator in a packet indicating that the packet is the last packet sent in the burst.
[0171] Aspect 3: A method according to any one of aspects 1 to 2, wherein transitioning from the first communication state to the second communication state comprises: transitioning from the first communication state to the second communication state based at least in part on detection of packet loss and expiration of a timer.
[0172] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the burst end indication is based at least in part on at least one of the following: a burst service flow parameter, a burst sequence number parameter, a burst end flag, a parameter identifying the number of packets in the burst transmission, or a parameter identifying the sequence number of the one or more packets in the burst transmission.
[0173] Aspect 5: The method according to any one of aspects 1 to 4, wherein the burst end indication is based at least in part on burst metadata included in a General Packet Radio Service Tunneling Protocol user plane header of at least one packet.
[0174] Aspect 6: The method according to Aspect 5, wherein the burst metadata includes a burst service flow parameter, a burst sequence number parameter, a parameter indicating one or more last application data units (ADUs) of a burst, or an ADU sequence number parameter.
[0175] Aspect 7: The method according to aspect 5, wherein the burst metadata includes an application data unit (ADU) content policy parameter, an ADU discard time parameter, or an ADU size parameter.
[0176] Aspect 8: A method of wireless communication performed by a network entity, the method comprising: receiving a burst end indication, the burst end indication being associated with burst metadata accompanying a burst transmission of one or more packets, identifying the end of the burst transmission of the one or more packets; and sending a power control indication in conjunction with the burst transmission of the one or more packets to indicate a transition from a first communication state to a second communication state, wherein the power of the second communication state is different from the power of the first communication state.
[0177] Aspect 9: The method according to aspect 8, wherein the burst end indication is included in the burst metadata.
[0178] Aspect 10: The method according to any one of aspects 8 to 9, wherein the burst end indication comprises an indicator in a packet associated with the burst transmission, the indicator indicating that the packet is the last packet of the burst transmission.
[0179] Aspect 11: According to any one of Aspects 8 to 10, the method also includes: detecting packet loss associated with the burst transmission; and wherein sending the power control indication includes: sending the power control indication based at least in part on detecting the packet loss and the expiration of a timer.
[0180] Aspect 12: A method according to any one of Aspects 8 to 11, wherein the burst metadata associated with the burst end indication includes at least one of the following: a burst service flow parameter, a burst sequence number parameter, a burst end flag, a parameter identifying the number of packets in the burst transmission, or a parameter identifying the sequence number of the one or more packets in the burst transmission.
[0181] Aspect 13: The method according to any one of aspects 8 to 12, wherein the burst metadata associated with the burst end indication is included in a General Packet Radio Service Tunneling Protocol user plane header of the one or more packets.
[0182] Aspect 14: A method according to any one of Aspects 8 to 13, wherein the burst metadata associated with the burst end indication includes at least one of the following: a burst service flow parameter, a burst sequence number parameter, a parameter indicating the last one or more application data units (ADUs) sent by the burst, or an ADU sequence number parameter.
[0183] Aspect 15: A method according to any one of Aspects 8 to 14, wherein the burst metadata associated with the burst end indication includes at least one of the following: an application data unit (ADU) content policy parameter, an ADU discard time parameter, or an ADU size parameter.
[0184] Aspect 16: A method of wireless communication performed by a network entity, the method comprising: receiving application data for transmission to a user equipment (UE) via another network entity; and sending the application data with a burst end indication, the burst end indication being associated with burst metadata of a burst transmission of one or more packets accompanying the application data, identifying the end of the burst transmission of the one or more packets.
[0185] Aspect 17: The method according to aspect 16, wherein the burst end indication is included in the burst metadata.
[0186] Aspect 18: The method according to any one of aspects 16 to 17, wherein the burst end indication comprises an indicator in a packet associated with the burst transmission, the indicator indicating that the packet is the last packet of the burst transmission.
[0187] Aspect 19: A method according to any one of Aspects 16 to 18, wherein the burst metadata associated with the burst end indication includes at least one of the following: a burst service flow parameter, a burst sequence number parameter, a burst end flag, a parameter identifying the number of packets in the burst transmission, or a parameter identifying the sequence number of the one or more packets in the burst transmission.
[0188] Aspect 20: The method according to any one of aspects 16 to 19, wherein the burst metadata associated with the burst end indication is included in a General Packet Radio Service Tunneling Protocol user plane header of the one or more packets.
[0189] Aspect 21: A method according to any one of Aspects 16 to 20, wherein the burst metadata associated with the burst end indication includes at least one of the following: a burst service flow parameter, a burst sequence number parameter, a parameter indicating the last one or more application data units (ADUs) sent by the burst, or an ADU sequence number parameter.
[0190] Aspect 22: A method according to any one of Aspects 16 to 21, wherein the burst metadata associated with the burst end indication includes at least one of the following: an application data unit (ADU) content policy parameter, an ADU discard time parameter, or an ADU size parameter.
[0191] Aspect 23: An apparatus for performing wireless communications 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 one or more of the methods described in Aspects 1 to 7.
[0192] Aspect 24: 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 7.
[0193] Aspect 25: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 7.
[0194] Aspect 26: 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 7.
[0195] Aspect 27: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform one or more of the methods described in aspects 1 to 7.
[0196] Aspect 28: An apparatus for performing wireless communications 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 one or more of the methods described in Aspects 8 to 15.
[0197] Aspect 29: 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 8 to 15.
[0198] Aspect 30: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 8 to 15.
[0199] Aspect 31: 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 8 to 15.
[0200] Aspect 32: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform one or more of the methods described in aspects 8 to 15.
[0201] Aspect 33: An apparatus for performing wireless communications 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 one or more of the methods described in Aspects 16 to 22.
[0202] Aspect 34: An apparatus for wireless communication, the apparatus 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 16 to 22.
[0203] Aspect 35: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 16 to 22.
[0204] Aspect 36: 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 16 to 22.
[0205] Aspect 37: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform one or more of the methods described in aspects 16 to 22.
[0206] 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 acquired from practice of these aspects.
[0207] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.
[0208] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.
[0209] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an 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, and 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).
[0210] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If you only want to refer to an entry, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "at least partially based on", unless explicitly stated otherwise. In addition, as used herein, the term "or" is intended to be open when used in a series, and can be used interchangeably with "and / or", unless otherwise explicitly stated (for example, if used in combination with "any" or "only one").
Claims
1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a burst transmission comprising one or more packets; and Transitioning from a first communication state to a second communication state at a power different from a power of the first communication state based at least in part on receiving a power control indication triggered by an end-of-burst indication associated with burst metadata accompanying the burst transmission.
2. The UE of claim 1, wherein the power control indication is a power saving indication. The UE according to claim 1 , wherein the power of the second communication state is smaller than the power of the first communication state. 4 . The UE of claim 1 , wherein the burst end indication comprises an indicator in a packet indicating that the packet is a last packet of the burst transmission.
5. The UE of claim 1 , wherein in order to transition from the first communication state to the second communication state, the one or more processors are configured to: Transitioning from the first communication state to the second communication state is based at least in part on detection of packet loss and expiration of a timer.
6. The UE of claim 1 , wherein the burst end indication is based at least in part on at least one of: Burst service flow parameters, Burst sequence number parameters, Burst end flag, a parameter identifying the number of packets in the burst transmission, or A parameter identifying a sequence number of the one or more packets in the burst transmission.
7. The UE of claim 1, wherein the burst end indication is based at least in part on burst metadata included in a General Packet Radio Service Tunneling Protocol user plane header of at least one packet.
8. The UE according to claim 7, wherein the burst metadata comprises: Burst service flow parameters, Burst sequence number parameters, Parameters indicating the last application data unit (ADU) of the burst, or ADU serial number parameter.
9. The UE according to claim 7, wherein the burst metadata comprises: Application Data Unit (ADU) content policy parameters, ADU discard time parameter, or ADU size parameters.
10. A network entity for wireless communication, the network entity comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a burst end indication associated with burst metadata accompanying a burst transmission of one or more packets, identifying an end of the burst transmission of one or more packets; as well as A power control indication is transmitted in conjunction with the burst transmission of the one or more packets to indicate a transition from a first communication state to a second communication state, wherein the power of the second communication state is different from the power of the first communication state. The network entity of claim 10 , wherein the power control indication is a power saving indication.
12. The network entity of claim 10, wherein the power of the second communication state is less than the power of the first communication state.
13. The network entity of claim 10, wherein the burst end indication is included in the burst metadata.
14. The network entity of claim 10, wherein the burst end indication comprises an indicator in a packet associated with the burst transmission, the indicator indicating that the packet is a last packet of the burst transmission.
15. The network entity of claim 10, wherein the one or more processors are further configured to: detecting packet loss associated with the burst transmission; and Wherein, in order to send the power control indication, the one or more processors are configured to: The power control indication is sent based at least in part on detecting the packet loss and expiration of a timer.
16. The network entity of claim 10, wherein the burst metadata associated with the burst end indication comprises at least one of: Burst service flow parameters, Burst sequence number parameters, Burst end flag, a parameter identifying the number of packets in the burst transmission, or A parameter identifying a sequence number of the one or more packets in the burst transmission.
17. The network entity of claim 10, wherein the burst metadata associated with the burst end indication is included in a General Packet Radio Service Tunneling Protocol user plane header of the one or more packets.
18. The network entity of claim 10, wherein the burst metadata associated with the burst end indication comprises at least one of: Burst service flow parameters, Burst sequence number parameters, a parameter indicating the last one or more application data units (ADUs) transmitted in the burst, or ADU serial number parameter.
19. The network entity of claim 10, wherein the burst metadata associated with the burst end indication comprises at least one of: Application Data Unit (ADU) content policy parameters, ADU discard time parameter, or ADU size parameters.
20. A network entity for wireless communication, the network entity comprising: Memory; and one or more processors coupled to the memory and configured to: receiving application data for transmission to a user equipment (UE) via another network entity; as well as The application data is transmitted with a burst end indication associated with burst metadata accompanying a burst transmission of one or more packets of the application data, identifying an end of the burst transmission of one or more packets.
21. The network entity of claim 20, wherein the burst end indication is included in the burst metadata.
22. The network entity of claim 20, wherein the burst end indication comprises an indicator in a packet associated with the burst transmission, the indicator indicating that the packet is a last packet of the burst transmission.
23. The network entity of claim 20, wherein the burst metadata associated with the burst end indication comprises at least one of: Burst service flow parameters, Burst sequence number parameters, Burst end flag, a parameter identifying the number of packets in the burst transmission, or A parameter identifying a sequence number of the one or more packets in the burst transmission.
24. The network entity of claim 20, wherein the burst metadata associated with the burst end indication is included in a General Packet Radio Service Tunneling Protocol user plane header of the one or more packets.
25. The network entity of claim 20, wherein the burst metadata associated with the burst end indication comprises at least one of: Burst service flow parameters, Burst sequence number parameters, a parameter indicating the last one or more application data units (ADUs) transmitted in the burst, or ADU serial number parameter.
26. The network entity of claim 20, wherein the burst metadata associated with the burst end indication comprises at least one of: Application Data Unit (ADU) content policy parameters, ADU discard time parameter, or ADU size parameters.
27. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a burst transmission including one or more packets; as well as Transitioning from a first communication state to a second communication state at a power different from a power of the first communication state based at least in part on receiving a power control indication triggered by an end-of-burst indication associated with burst metadata accompanying the burst transmission.
28. The method of claim 27, wherein the burst end indication comprises an indicator in a packet indicating that the packet is the last packet transmitted in the burst.
29. The method of claim 27, wherein transitioning from the first communication state to the second communication state comprises: Transitioning from the first communication state to the second communication state is based at least in part on detection of packet loss and expiration of a timer.
30. The method of claim 27, wherein the burst end indication is based at least in part on at least one of: Burst service flow parameters, Burst sequence number parameters, Burst end flag, a parameter identifying the number of packets in the burst transmission, or A parameter identifying a sequence number of the one or more packets in the burst transmission.
