Batch numbering of one or more configuration commands for radio unit (RU)

Abstract

An apparatus for wireless communication by a network entity includes a memory and one or more processors coupled to the memory. The one or more processors are configured to receive one or more configuration commands associated with a carrier having a first configuration. The one or more configuration commands each indicate a batch number. The one or more processors are further configured to store the one or more configuration commands, and based on detection of a trigger event, perform a reconfiguration of the carrier from the first configuration to a second configuration, the reconfiguration based on the one or more configuration commands.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application Ser. No. 18 / 356,130, filed on July 20, 2023, entitled “BATCH NUMBERING OF ONE OR MORE CONFIGURATION COMMANDS FOR A RADIO UNIT (RU)” and U.S. Provisional Patent Application Ser. No. 63 / 373,544, filed on August 25, 2022, entitled “BATCH NUMBERING OF ONE OR MORE CONFIGURATION COMMANDS FOR A RADIO UNIT (RU)”, both of which are expressly incorporated herein by reference in their entirety. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly to configuration commands of a Radio Unit (RU) of a wireless communication system. Background Art

[0004] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, etc. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources. Such networks may be multiple-access networks capable of supporting communication for multiple users by sharing the available network resources.

[0005] A wireless communication network may include several components. These components may include wireless communication devices, such as a base station (or Node B) that may support communication of several user equipments (UEs). A UE may communicate with a base station via a downlink and an uplink. A downlink (or forward link) refers to a communication link from a base station to a UE, and an uplink (or reverse link) refers to a communication link from a UE to a base station.

[0006] The base station may send data and control information to the UE on the downlink, or receive data and control information from the UE on the uplink. On the downlink, the transmission from the base station may encounter interference caused by transmissions from neighboring base stations or other wireless radio frequency (RF) transmitters. On the uplink, the transmission from the UE may encounter interference from other UEs communicating with neighboring base stations or from uplink transmissions of other wireless RF transmitters. This interference may degrade performance on both the downlink and uplink.

[0007] As the demand for mobile broadband access continues to grow, the potential for interference and congested networks grows with more UEs accessing long-range wireless communication networks and more short-range wireless systems deployed in communities. Research and development continues to advance wireless technologies to not only meet the growing demand for mobile broadband access, but also to improve and enhance the user experience with mobile communications.

[0008] To enhance the user experience and address the growing demand for mobile broadband access, some wireless communication systems may dynamically change configurations associated with wireless communications. For example, a base station may change the configuration of a carrier used to communicate with a UE, such as by increasing or decreasing the transmit power associated with the carrier to compensate for interference or reduce power consumption. In some cases, changing the configuration of a carrier may be associated with unpredictable or undesirable operation, such as if multiple different changes to the carrier are performed (which may result in unpredictable or unknown "intermediate" states for the carrier, and which may result in poor performance).

[0009] To reduce or prevent such unpredictable conditions, some wireless communication systems may deactivate the carrier before performing a change to the carrier, and may reactivate the carrier after completing the change to the carrier. Such techniques may reduce the availability of wireless communication resources, thereby increasing latency or otherwise degrading performance. Some other wireless communication systems may temporarily reassign the carrier to another base station. Such techniques may use resources (such as processing resources and radio resources) to schedule and implement the reassignment, and may also increase the load associated with the other base station. Summary of the invention

[0010] In some aspects of the present disclosure, an apparatus for wireless communication by a network entity includes a memory and one or more processors coupled to the memory. The one or more processors are configured to receive one or more configuration commands associated with a carrier having a first configuration. The one or more configuration commands each indicate a batch number. The one or more processors are further configured to store the one or more configuration commands and, based on detection of a triggering event, perform a reconfiguration of the carrier from the first configuration to a second configuration, the reconfiguration being based on the one or more configuration commands.

[0011] In some other aspects of the present disclosure, a method of wireless communication performed by a network entity includes: receiving one or more configuration commands associated with a carrier having a first configuration. The one or more configuration commands each indicate a batch number. The method also includes storing the one or more configuration commands, and the method also includes: based on detecting a triggering event, performing a reconfiguration of the carrier from the first configuration to a second configuration, the reconfiguration being based on the one or more configuration commands.

[0012] In some other aspects, an apparatus for wireless communication by a network entity includes a memory and one or more processors coupled to the memory. The one or more processors are configured to send one or more configuration commands associated with a carrier. The one or more configuration commands each indicate a batch number. The one or more processors are further configured to receive a report message based on the one or more configuration commands, the report message indicating a status associated with reconfiguration of the carrier from a first configuration to a second configuration.

[0013] In some other aspects of the present disclosure, a method for wireless communication by a network entity includes: sending one or more configuration commands associated with a carrier. The one or more configuration commands each indicate a batch number. The method also includes: receiving a report message based on the one or more configuration commands, the report message indicating a status associated with reconfiguration of the carrier from a first configuration to a second configuration.

[0014] Although various aspects and specific implementations are described in this application by the illustration of some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects and / or uses can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of a wide range of described innovations may occur. The scope of specific implementations can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the scope of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more aspects of the described innovations. In some practical environments, the equipment in conjunction with the various aspects and features described may also necessarily include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., having different sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a block diagram illustrating details of an example wireless communication system that supports batch numbering of one or more configuration commands for a radio unit (RU) in accordance with one or more aspects.

[0016] Figure 2 is a block diagram illustrating an example of a base station and a user equipment (UE) supporting batch numbering of one or more configuration commands for RUs according to one or more aspects.

[0017] Figure 3 is a block diagram illustrating an example disaggregated base station architecture supporting batch numbering of one or more configuration commands for RUs according to one or more aspects.

[0018] Figure 4 is a block diagram of an example wireless communication system illustrating batch numbering of one or more configuration commands for supporting RUs according to one or more aspects.

[0019] Figure 5 is a flow chart illustrating an example method for supporting batch numbering of one or more configuration commands of a RU according to one or more aspects.

[0020] Figure 6 is a flow chart illustrating another example method for supporting batch numbering of one or more configuration commands of RUs according to one or more aspects.

[0021] Like reference numbers and designations in the various drawings indicate like elements. DETAILED DESCRIPTION

[0022] In some aspects of the present disclosure, batch numbers may be assigned to configuration commands for carriers to enable batch reconfiguration operations. For example, a distributed unit (DU) of an open radio access network (O-RAN) may provide a configuration command to a radio unit (RU) of the O-RAN, and the configuration command may indicate a batch number. The RU may store (e.g., cache or buffer) one or more such configuration commands associated with the batch number until an instruction indicating a triggering event is received from the DU. For example, the instruction may indicate a specific frame or subframe at which the RU will perform an update of the carrier based on each configuration command associated with the batch number. Upon detecting a triggering event, the RU may perform reconfiguration of the carrier based on one or more stored configuration commands associated with the batch number.

[0023] By using batch numbers, the RU can implement multiple configuration commands at a common time or within a common time interval. Therefore, the RU can avoid or reduce instances of unknown or intermediate configuration of carriers (which may occur if multiple configuration commands arrive at the RU or are executed by the RU out of order). Further, in some examples, the RU can perform reconfiguration of carriers on-the-fly without temporarily disabling the carrier during the reconfiguration. The RU can also perform reconfiguration of carriers without reassigning the carrier to another RU during the reconfiguration. Therefore, the availability of wireless resources is increased, while also reducing or avoiding the overhead associated with scheduling the reassignment of carriers, thereby enhancing the performance of the wireless communication system.

[0024] In some aspects, the reconfiguration may be coordinated between multiple RUs to improve performance or avoid conflicts between multiple RUs. To illustrate, in one example, a first RU may be deactivated (e.g., based on the time of day, based on the number of UEs connected to the first RU failing to exceed a threshold, or based on one or more other criteria), and a transmit power associated with a second RU may be increased via reconfiguration when the first RU is in a deactivated state. In such examples, the transmit power may be increased when the second RU is less susceptible to interference (e.g., when in a deactivated state). Other examples are further described with reference to the accompanying drawings.

[0025] In various specific implementations, one or more aspects described herein may be used in wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, fifth generation (5G) or new radio (NR) networks (sometimes referred to as "5G NR" networks, systems or devices), and other communication networks. As described herein, the terms "network" and "system" can be used interchangeably.

[0026] A CDMA network may implement, for example, a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband-CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers IS-2000, IS-95, and IS-856 standards.

[0027] For example, a TDMA network can implement radio technologies such as the Global System for Mobile Communications (GSM). The Third Generation Partnership Project (3GPP) defines the standards for the GSM EDGE (Enhanced Data Rate for GSM Evolution) Radio Access Network (RAN) (also known as GERAN). GERAN is the radio component of the network of GSM / EDGE together with connecting base stations (e.g., Ater and Abis interfaces) and base station controllers (A interfaces, etc.). The radio access network represents the component of the GSM network, through which telephone calls and packet data are routed from the public switched telephone network (PSTN) and the Internet to subscriber phones (also known as user terminals or user equipment (UE)) and from subscriber phones to the PSTN and the Internet. The network of a mobile phone operator may include one or more GERANs, which may be coupled with UTRAN in the case of a UMTS / GSM network. Additionally, the operator network may also include one or more LTE networks, or one or more other networks. Various network types may use different radio access technologies (RATs) and RANs.

[0028] OFDMA network can realize radio technology such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA and GSM are part of Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a UMTS version using E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or under development. For example, 3GPP is a collaboration between telecommunication association groups with the goal of defining a globally applicable third generation (3G) mobile phone specification. 3GPP LTE is a 3GPP plan with the goal of improving the UMTS mobile phone standard. 3GPP can define the specifications of next generation mobile networks, mobile systems and mobile devices. The present disclosure may describe certain aspects with reference to LTE, 4G or 5G NR technology; however, the description is not intended to be limited to a particular technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. Additionally, one or more aspects of the present disclosure may relate to shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces.

[0029] 5G networks are expected to have diverse deployments, diverse spectrum, and diverse services and devices that can be implemented using a unified air interface based on OFDM. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also being considered. 5G NR will be able to scale to provide coverage (1) to massive Internet of Things (IoT), with ultra-high density (e.g., about 1M nodes / km 2 ), ultra-low complexity (e.g., about 10s of bits / second), ultra-low power consumption (e.g., about 10+ years battery life), and deep coverage with the ability to reach challenging locations; (2) including mission-critical control with strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., about 99.9999% reliability), ultra-low latency (e.g., about 1 millisecond (ms)), and users with a wide range of mobility or lack of mobility; and (3) providing services with enhanced mobile broadband (including extremely high capacity (e.g., about 10Tbps / km 2 ), coverage of extremely high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep awareness with advanced discovery and optimization).

[0030] Devices, networks, and systems may be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, 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). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is typically (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. Similar naming issues sometimes arise with respect to FR2, which is typically (interchangeably) referred to as the "millimeter wave" (mmWave) band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "mmWave" band by the International Telecommunication Union (ITU).

[0031] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used in this document, it can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if used in this document, the term "mmWave" or the like can broadly represent frequencies that can include mid-band frequencies, can be within FR2, or can be within the EHF band.

[0032] 5G NR devices, networks, and systems can be implemented to use optimized OFDM-based waveform features. These features may include scalable parameter sets and transmission time intervals (TTIs); a common flexible framework that effectively multiplexes services and features using dynamic, low-latency time division duplex (TDD) designs or frequency division duplex (FDD) designs; and advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust mmWave transmission, advanced channel decoding, and device-centric mobility. The scalability of parameter sets in 5G NR and the scaling of subcarrier spacing can effectively address the operation of various services across different spectrums and different deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD or TDD implementations, the subcarrier spacing may appear at 15kHz, such as over bandwidths of 1MHz, 5MHz, 10MHz, 20MHz, etc. For various other outdoor and small cell coverage deployments with TDD greater than 3GHz, the subcarrier spacing may appear at 30kHz over 80MHz / 100MHz bandwidth. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5GHz band, the subcarrier spacing may occur at 60kHz over a 160MHz bandwidth. Finally, for various deployments transmitting over mmWave components at 28GHz TDD, the subcarrier spacing may occur at 120kHz over a 500MHz bandwidth.

[0033] 5G NR's scalable parameter sets facilitate scalable TTIs for diverse latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmission to start on symbol boundaries. 5G NR also anticipates a self-contained integrated subframe design where uplink or downlink scheduling information, data, and acknowledgments are in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, and adaptive uplink or downlink can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current business needs.

[0034] For clarity, certain aspects of the devices and techniques may be described below with reference to example 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used as illustrative examples in portions of the description below; however, the description is not intended to be limited to 5G applications.

[0035] Furthermore, it should be understood that in operation, a wireless communication network adapted according to the concepts herein can operate using any combination of licensed spectrum or unlicensed spectrum depending on load and availability. Therefore, it will be apparent to one of ordinary skill in the art that the systems, devices, and methods described herein can be applied to other communication systems and applications beyond the specific examples provided.

[0036] Although various aspects and specific implementations are described in this application by the illustration of some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, specific implementation or use can be implemented via integrated chip specific implementation or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail equipment or purchasing equipment, medical equipment, AI-enabled devices, etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of a wide range of described innovations may occur. The scope of specific implementation can range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems containing one or more described aspects. In some practical environments, the equipment in combination with the various aspects and features described may also necessarily include additional components and features for implementing and practicing the various aspects claimed and described. It is intended that the innovations described herein may be implemented in a wide variety of embodiments of different sizes, shapes, and configurations, including both large and small devices, chip-level components, multi-component systems (e.g., radio frequency (RF) chains, communication interfaces, processors), distributed arrangements, end-user devices, and the like.

[0037] Figure 1 1 is a block diagram illustrating details of an example wireless communication system according to one or more aspects. The wireless communication system may include a wireless network 100. The wireless network 100 may, for example, include a 5G wireless network. As will be appreciated by those skilled in the art, Figure 1 Components appearing in are likely to have related corresponding components in other network arrangements (including, for example, cellular-style network arrangements and non-cellular-style network arrangements (e.g., device-to-device or peer-to-peer or ad hoc network arrangements, etc.)).

[0038] Figure 1The illustrated wireless network 100 includes many base stations 105 and other network entities. A base station may be a station that communicates with a UE, and may also be referred to as an evolved Node B (eNB), a next generation eNB (gNB), an access point, etc. Each base station 105 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a specific geographic coverage area of ​​a base station or a base station subsystem serving the coverage area, depending on the context in which the term is used. In the specific implementation of the wireless network 100 herein, the base station 105 may be associated with the same operator or different operators (e.g., the wireless network 100 may include multiple operator wireless networks). Additionally, in the specific implementation of the wireless network 100 herein, the base station 105 may provide wireless communication using one or more frequencies (e.g., one or more frequency bands in a licensed spectrum, an unlicensed spectrum, or a combination thereof) in the same frequency as an adjacent cell. In some examples, a separate base station 105 or UE 115 may be operated by more than one network operating entity. In other examples, each base station 105 and UE 115 may be operated by a single network operating entity.

[0039] A base station may provide communication coverage for a macro cell or a small cell (e.g., a pico cell or a femto cell) or other type of cell. A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with a service subscription with a network provider. Small cells (such as pico cells) will generally cover a relatively small geographic area and may allow unrestricted access by UEs with a service subscription with a network provider. Small cells (such as femto cells) will generally also cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station, or a home base station. In Figure 1 In the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations implemented using one of 3-dimensional (3D), full-dimensional (FD) or massive MIMO. Base stations 105a-105c use their higher-dimensional MIMO capabilities to employ 3D beamforming in elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station, which can be a home node or a portable access point. The base station can support one or more (e.g., two, three, four, etc.) cells.

[0040] The wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, the base stations may have similar frame timings, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, the base stations may have different frame timings, and transmissions from different base stations may not be aligned in time. In some scenarios, the network may be enabled or configured to handle dynamic switching between synchronous or asynchronous operation.

[0041] UE 115 is dispersed throughout the wireless network 100, and each UE may be stationary or mobile. It should be understood that, although in the standards and specifications promulgated by 3GPP, mobile devices are generally referred to as UEs, such devices may be additionally or otherwise referred to as mobile stations (MS), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (AT), mobile terminals, wireless terminals, remote terminals, mobile phones, terminals, user agents, mobile clients, clients, gaming devices, augmented reality devices, vehicle components, vehicle devices or vehicle modules or some other suitable terminology by those skilled in the art. In this document, a "mobile" device or UE does not necessarily have the ability to move and may be stationary. Some non-limiting examples of mobile devices (for example) may include one or more specific implementations of UE 115, including mobile phones, cellular phones, smart phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, laptops, personal computers (PCs), notebooks, netbooks, smart books, tablet computers, and personal digital assistants (PDAs). The mobile device may additionally be an IoT or "Internet of Everything" (IoE) device, such as a car or other transportation vehicle, a satellite radio, a global positioning system (GPS) device, a global navigation satellite system (GNSS) device, a logistics controller, a drone, a multi-rotor helicopter, a quad-rotor helicopter, a smart energy or security device, a solar panel or solar array, city lighting, tap water or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smart watches, health or fitness trackers, mammal implantable devices, gesture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, game consoles, etc.; and digital home or smart home devices, such as home audio, video and multimedia devices, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, a UE may be a device including a universal integrated circuit card (UICC). In another aspect, a UE may be a device that does not include a UICC. In some aspects, a UE that does not include a UICC may also be referred to as an IoE device. Figure 1The UE 115a-115d of the specific implementation illustrated in the figure are examples of mobile smart phone type devices accessing the wireless network 100. The UE may also be a machine specially configured for connected communications (including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc.). Figure 1 The illustrated UEs 115e - 115k are examples of various machines that access the wireless network 100 and are configured for communication.

[0042] A mobile device, such as UE 115, may be able to communicate with any type of base station, whether macro, pico, femto, relay, etc. Figure 1 In the figure, the communication link (represented as a lightning ball) indicates the wireless transmission between the UE and the serving base station (which is a base station designated to serve the UE on the downlink or uplink) or the expected transmission between the base stations and the backhaul transmission between the base stations. The UE can operate as a base station or other network node in some scenarios. The backhaul communication between the base stations of the wireless network 100 can be carried out using wired or wireless communication links.

[0043] In operation, at the wireless network 100, base stations 105a-105c use 3D beamforming and collaborative spatial techniques (e.g., coordinated multipoint (CoMP) or multi-connectivity) to serve UEs 115a and 115b. Macro base station 105d performs backhaul communications with base stations 105a-105c and small cells (base station 105f). Macro base station 105d also transmits multicast services that are subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts.

[0044] The wireless network 100 of the specific implementation supports mission-critical communications with ultra-reliable and redundant links for mission-critical devices such as UE 115e as a drone. The redundant communication links with UE 115e include links from macro base stations 105d and 105e and small cell base station 105f. Other machine-type devices such as UE 115f (thermometer), UE 115g (smart meter) and UE 115h (wearable device) can communicate directly with base stations such as small cell base station 105f and macro base station 105e through the wireless network 100, or in a multi-hop configuration by communicating with another user device that relays its information to the network, such as UE 115f communicating temperature measurement information to smart meter UE 115g, which then reports it to the network through small cell base station 105f. The wireless network 100 may also provide additional network efficiency through dynamic, low-latency TDD communications or low-latency FDD communications (eg, in a vehicle-to-vehicle (V2V) mesh network between UEs 115i-115k communicating with a macro base station 105e).

[0045] Figure 2 1 is a block diagram illustrating an example of a base station 105 and a UE 115 according to one or more aspects. The base station 105 and the UE 115 may be Figure 1 For a restricted association scenario (as described above), base station 105 may be any one of the base stations in the UE and one of the UEs. Figure 1 The small cell base station 105f in the example of FIG. 105 and the UE 115 may be a UE 115c or 115d operating in the service area of ​​the base station 105f, which will be included in the list of accessible UEs of the small cell base station 105f in order to access the small cell base station 105f. The base station 105 may also be some other type of base station. Figure 2 As shown in FIG. 1 , the base station 105 may be equipped with antennas 234a through 234t and the UE 115 may be equipped with antennas 252a through 252r for facilitating wireless communication.

[0046] At the base station 105, the transmit processor 220 may receive data from the data source 212 and control information from the processor 240. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), a physical downlink control channel (PDCCH), an enhanced physical downlink control channel (EPDCCH), an MTC physical downlink control channel (MPDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. Additionally, the transmit processor 220 may process (e.g., encode and symbol map) the data and the control information, respectively, to obtain data symbols and control symbols. The transmit processor 220 may also generate reference symbols, such as for a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), and a cell-specific reference signal. The transmit (TX) MIMO processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, or reference symbols (if applicable), and may provide an output symbol stream to modulators (MODs) 232a to 232t. For example, the spatial processing performed on the data symbols, control symbols, or reference symbols may include pre-decoding. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Additionally or alternatively, each modulator 232 may process the output sample stream (e.g., analog-convert, amplify, filter, and up-convert) to obtain a downlink signal. The downlink signals from modulators 232a to 232t may be transmitted via antennas 234a to 234t, respectively.

[0047] At the UE 115, antennas 252a to 252r may receive downlink signals from the base station 105 and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may adjust (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 256 may obtain received symbols from the demodulators 254a to 254r, perform MIMO detection on the received symbols when necessary, and provide detected symbols. The receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 115 to the data sink 260, and provide decoded control information to the controller 280.

[0048] On the uplink, at the UE 115, a transmit processor 264 may receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a processor 280 (e.g., for a physical uplink control channel (PUCCH)). Additionally, the transmit processor 264 may also generate reference symbols for reference signals. The symbols from the transmit processor 264 may be pre-decoded by a TX MIMO processor 266, if necessary, further processed by modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, the uplink signal from the UE 115 may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236, if necessary, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 115. The receive processor 238 may provide decoded data to a data sink 239 and decoded control information to the processor 240.

[0049] The processors 240 and 280 may direct the operations at the base station 105 and the UE 115, respectively. The controller 240 or other processors and modules at the base station 105 or the controller 280 or other processors and modules at the UE 115 may perform or direct the execution of various processes for the techniques described herein, such as executing or directing Figure 5 and Figure 6 The illustrated execution or other processes for the techniques described herein. Memories 242 and 282 may store data and program codes for base station 105 and UE 115, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink or uplink.

[0050] In some cases, the UE 115 and the base station 105 may operate in a shared radio spectrum band, which may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio spectrum band, the UE 115 or the base station 105 may traditionally perform a medium sensing process to compete for access to the spectrum. For example, the UE 115 or the base station 105 may perform a listen-before-talk or listen-before-send (LBT) process (such as a clear channel assessment (CCA)) before communicating to determine whether the shared channel is available. In some specific implementations, CCA may include an energy detection process to determine whether there are any other active transmissions. For example, a device may infer that a change in a received signal strength indicator (RSSI) of a power meter indicates that the channel is occupied. Specifically, a signal power concentrated in a certain bandwidth and exceeding a predetermined noise floor may indicate another wireless transmitter. CCA may also include detection of a specific sequence indicating the use of a channel. For example, another device may send a specific preamble before sending a data sequence. In some cases, the LBT process may include the wireless node adjusting its own backoff window based on the amount of energy detected on the channel or acknowledgement / negative acknowledgement (ACK / NACK) feedback for its own transmitted packets (as a manifestation of a collision).

[0051] The deployment of a communication system such as a 5G New Radio (NR) system may be arranged with various components or constituent parts 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 radio access network (RAN) node, a core network node, a network element or network equipment such as a base station (BS), or one or more units (or one or more components) performing base station functionality may be implemented in an aggregated or decomposed architecture. For example, a BS such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP), or a cell, etc. may be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0052] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN 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, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0053] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0054] Figure 3 A diagram illustrating an example decomposed base station 300 architecture is shown. In some examples, the decomposed base station 300 architecture may be used to implement the base station 105. The decomposed base station 300 architecture may include one or more central units (CUs) 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (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 distributed units (DUs) 330 via respective midhaul links, such as an F1 interface. The DU 330 may communicate with one or more radio units (RUs) 340 via respective fronthaul links. The RU 340 may communicate with respective UEs 115 via one or more radio frequency (RF) access links. In some implementations, a UE 115 can be served by multiple RUs 340 simultaneously.

[0055] Each of the units (i.e., CU 310, DU 330, RU 340, and 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, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, the unit may include a wired interface configured to receive or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0056] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (which may be referred to as central unit-user plane (CU-UP) functionality), control plane functionality (which may be referred to as central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0057] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, 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 (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 330 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0058] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (IFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 115. In some 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 the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0059] The SMO framework 305 may be configured to support RAN deployment and provisioning 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) 390) to perform network element lifecycle management (such as to instantiate 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, 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 specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0060] 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 communicate 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.

[0061] 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 O1) or via creation of RAN management policies (such as A1 policies).

[0062] Figure 4 is a block diagram illustrating an example of a wireless communication system 400 that supports batch numbering of one or more configuration commands of RUs according to some aspects of the present disclosure. The wireless communication system 400 may include a DU 330 and a RU 340, which may implement at least a portion of a base station 105. The wireless communication system 400 may include one or more UEs, such as UE 115.

[0063] RU 340 may include one or more processors (such as processor 240), one or more memories (such as memory 242), a fronthaul communication interface 414, a transmitter 416, and a receiver 418. Processor 240 may be coupled to memory 242, to fronthaul communication interface 414, to transmitter 416, and to receiver 418. In some examples, any of fronthaul communication interface 414, transmitter 416, and receiver 418 may include a reference Figure 2 One or more components described, such as one or more of the modulator / demodulators 232a-232t, the MIMO detector 236, the receive processor 238, the transmit processor 220, or the TX MIMO processor 230. In some implementations, the transmitter 416 and the receiver 418 can be integrated into one or more transceivers of the RU 340.

[0064] The fronthaul communication interface 414 may be configured to communicate with the DU 330 via the fronthaul link 480. For example, the RU 340 may send and receive control information and other data used by the RU 340 to communicate with the UE 115.

[0065] The transmitter 416 may be configured to transmit reference signals, synchronization signals, control information, and data to one or more other devices, and the receiver 418 may be configured to receive reference signals, control information, and data from one or more other devices. For example, the transmitter 416 may be configured to transmit signaling, control information, and data to the UE 115, and the receiver 418 may be configured to receive signaling, control information, and data from the UE 115. In some examples, one or both of the transmitter 416 or the receiver 418 may communicate with the UE 115 via the carrier 490. The carrier 490 may be included in the reference signal. Figure 3 The access link described may be in or associated with the access link.

[0066] UE 115 may include one or more processors (such as processor 280), memory (such as memory 282), transmitter 456, and receiver 458. Processor 280 may be coupled to memory 282, to transmitter 456, and to receiver 458. In some examples, transmitter 456 and receiver 458 may include reference Figure 2 One or more components described, such as one or more of the modulator / demodulators 254a-r, the MIMO detector 256, the receive processor 258, the transmit processor 264, or the TX MIMO processor 266. In some implementations, the transmitter 456 and the receiver 458 can be integrated into one or more transceivers of the UE 115.

[0067] The transmitter 456 may be configured to transmit reference signals, synchronization signals, control information, and data to one or more other devices, and the receiver 458 may receive reference signals, control information, and data from one or more other devices. For example, in some implementations, the transmitter 456 may transmit signaling, control information, and data to the RU 340, and the receiver 458 may receive signaling, control information, and data from the RU 340. In some examples, one or both of the transmitter 456 or the receiver 458 may communicate with the RU 340 via the carrier 490.

[0068] DU 330 may include one or more processors, such as processor 482, one or more memories, such as memory 484, and a fronthaul communications interface 486. Processor 240 may be coupled to memory 242 and to fronthaul communications interface 486. Fronthaul communications interface 486 may be configured to communicate with RU 340 via fronthaul link 480. For example, DU 330 may send and receive control information and other data used by RU 340 to communicate with UE 115.

[0069] The wireless communication system 400 may use wireless communication channels, which may be specified by one or more wireless communication protocols (such as 5G NR wireless communication protocols). For illustration, the RU 340 may use one or more downlink wireless communication channels (e.g., using one or more of the PDSCH or PDCCH) to communicate with the UE 115. The UE 115 may use one or more uplink wireless communication channels (e.g., using one or more of the PUSCH or PUCCH) to communicate with the RU 340. According to this example, the carrier 490 may be included in the PDSCH, PDCCH, PUSCH, PUCCH, one or more other channels, or a combination thereof, or may be associated with the PDSCH, PDCCH, PUSCH, PUCCH, one or more other channels, or a combination thereof.

[0070] During operation, RU 340 may communicate with UE 115 using one or more carriers, such as carrier 490. For example, RU 340 may transmit signals (such as data, control information, or other signals) via carrier 490. Alternatively or in addition, RU 340 may receive signals (such as data, control information, or other signals) from UE 115 via carrier 490.

[0071] The carrier 490 may be associated with the first configuration 404. For example, the first configuration 404 may specify parameters associated with the carrier 490, such as one or more of the following: a gain associated with the carrier 490, a transmit power associated with the carrier 490 (such as a transmit power of the RU 340 or a transmit power of the UE 115), a subcarrier spacing (SCS) associated with the carrier 490, a static physical random access channel (PRACH) configuration associated with the carrier 490, a static time division duplex (TDD) mode associated with the carrier 490, a static sounding reference signal (SRS) configuration associated with the carrier 490, an endpoint configuration associated with the carrier 490 (such as a specific array carrier or a specific number of antenna elements), one or more other parameters associated with the carrier 490, or a combination thereof.

[0072] In some cases, RU 340 may reconfigure carrier 490 by changing one or more parameters associated with carrier 490. For example, DU 330 may provide RU 340 with a configuration command 422 associated with carrier 490. Configuration command 422 may indicate a change to one or more parameters associated with carrier 490. In some examples, RU 340 may receive configuration command 422 from DU 330 via fronthaul link 480 and using fronthaul communication interface 414.

[0073] In some aspects of the disclosure, configuration command 422 may indicate batch number 426. Batch number 426 may be associated with a group of one or more configuration commands (including configuration command 422) to be implemented together (e.g., as a single group) by RU 340 (even if the one or more configuration commands are received separately by RU 340 over time).

[0074] To illustrate, upon receiving configuration command 422, RU 340 may store (e.g., cache or buffer) configuration command 422 (e.g., rather than implementing configuration command 422 upon receiving configuration command 422). In some examples, RU 340 may store configuration command 422 to memory 242. In some other examples, RU 340 may store configuration command 422 to another location, such as to a cache or buffer (e.g., a physical cache or buffer or a logical cache or buffer) that may be included in or accessible to processor 240.

[0075] To further illustrate, in some examples, after receiving the configuration command 424, the RU 340 may receive the configuration command 424 associated with the carrier 490. The configuration command 424 may indicate a batch number 426. Upon receiving the configuration command 424, the RU 340 may store (e.g., cache) the configuration command 424 (e.g., rather than implementing the configuration command 424 upon receiving the configuration command 424). In some examples, the RU 340 may store the configuration command 424 to the memory 242. In some other examples, the RU 340 may store the configuration command 424 to another location, such as to a cache or buffer (e.g., a physical cache or buffer or a logical cache or buffer), which may be included in the processor 240 or may be coupled to the processor.

[0076] In some aspects, RU 340 may store one or more configuration commands associated with lot number 426, such as configuration commands 422 and 424, until a triggering event 402 is detected. By storing one or more configuration commands associated with lot number 426, RU 340 may defer reconfiguring carrier 490 until a triggering event 402 is detected. Based on detecting triggering event 402, RU 340 may implement one or more stored configuration commands associated with lot number 426, such as configuration commands 422 and 424.

[0077] The one or more configuration commands may be associated with the second configuration 408 of the carrier 490. For example, the one or more configuration commands may indicate one or more of: a gain change associated with the carrier 490, a transmit power change associated with the carrier 490 (such as a change in the transmit power of the RU 340 or a change in the transmit power of the UE 115), an SCS change associated with the carrier 490, a static PRACH configuration change associated with the carrier 490, a static TDD mode change associated with the carrier 490, a static SRS configuration change associated with the carrier 490, or an endpoint configuration change associated with the carrier 490 (such as a change from one array carrier to another array carrier or a change in the number of antenna elements).

[0078] As an illustrative example, the configuration command 422 may indicate one of the gain change, the transmit power change, the SCS change, the static PRACH configuration change, the static TDD mode change, the static SRS configuration change, or the endpoint configuration change, and the configuration command 424 may indicate another one of the gain change, the transmit power change, the SCS change, the static PRACH configuration change, the static TDD mode change, the static SRS configuration change, or the endpoint configuration change. In such examples, the first configuration 404 may indicate one or more of a first gain associated with the carrier 490, a first transmit power associated with the carrier 490, a first SCS associated with the carrier 490, a first static PRACH configuration associated with the carrier 490, a first static TDD mode associated with the carrier 490, a first static SRS configuration associated with the carrier 490, or a first endpoint configuration associated with the carrier 490, and the second configuration 408 may indicate one or more of a second gain associated with the carrier 490 different from the first gain, a second transmit power associated with the carrier 490 different from the first transmit power, a second SCS associated with the carrier 490 different from the first SCS, a second static PRACH configuration associated with the carrier 490 different from the first PRACH configuration, a second static TDD mode associated with the carrier 490 different from the first static TDD mode, a second static SRS configuration associated with the carrier 490 different from the first static SRS configuration, or a second endpoint configuration associated with the carrier 490 different from the first endpoint configuration. Other examples, such as different examples of parameters of the carrier 490, are also within the scope of the present disclosure.

[0079] In some implementations, the DU 330 may indicate the triggering event 402 to the RU 340. Upon detecting the triggering event 402, the RU 340 may implement one or more stored configuration commands associated with the batch number 426. For example, the DU 330 may provide the RU 340 with instructions 430 indicating the triggering event 402 and further indicating the batch number 426. In some examples, the instructions 430 indicate a specific point in time associated with the triggering event 402.

[0080] For illustration, in some examples, a specific frame number 432 associated with the specific time point may be used to indicate (or represent) the specific time point. The trigger event 402 may correspond to a frame boundary between a first frame and a second frame, the first frame being associated with the specific frame number 432, the second frame being before the first frame. These frames may be included in the data sent by the RU 340 (e.g., via the carrier 490) to the UE 115. For illustration, the specific frame number 432 may be referred to as x (wherein x indicates a positive integer). In such examples, the transition from frame x-1 to frame x may correspond to the trigger event 402, and the RU 340 may detect the trigger event 402 based on the identification of the transition from frame x-1 to frame x. Therefore, the batch number 426 enables the RU 340 to "postpone" the implementation of the configuration commands (such as configuration commands 422 and 424) stored and associated with the batch number 426 until the trigger event 402 is detected, which may be associated with the specific time point indicated by the instruction 430.

[0081] Alternatively or in addition, one or more other parameters may be used to indicate (or represent) the specific time point. For example, in another specific implementation, the specific time point indicated by instruction 430 may be associated with one or more of the following: global navigation satellite system (GNSS) time, subframe number, time slot number, symbol number, or another parameter. In the above example, batch number 426 enables RU 340 to "postpone" the implementation of the stored configuration commands associated with batch number 426 (such as configuration commands 422 and 424) until a trigger event 402 is detected, which may be associated with the specific time point indicated by instruction 430.

[0082] Based on detecting the triggering event 402, the RU 340 may access one or more stored configuration commands associated with the batch number 426, such as by performing a search of the memory 242 (or another storage location) for one or more configuration commands having the batch number 426. For example, the RU 340 may access the configuration commands 422, 424 from the memory 242 based on determining that the configuration commands 422, 424 are associated with the batch number 426. Based on detecting the triggering event 402, the RU 340 may perform a reconfiguration 406 of the carrier 490 from the first configuration 404 to the second configuration 408, such as by adjusting one or more of the following: a gain associated with the carrier 490, a power associated with the carrier 490, an SCS associated with the carrier 490, or one or more other parameters associated with the carrier 490.

[0083] In some examples, RU 340 may perform reconfiguration 406 based on a specific order. The specific order may correspond to the order in which the plurality of configuration commands associated with lot number 426 are received by RU 340. To illustrate, in one example, RU 340 may receive configuration command 422 before receiving configuration command 424. In this example, performing reconfiguration 406 based on the specific order may include implementing (e.g., executing) configuration command 422 before implementing (e.g., executing) configuration command 424.

[0084] In some examples, RU 340 may send (e.g., via fronthaul link 480) a report message 440 to DU 330 indicating a state 442 associated with reconfiguration 406 of carrier 490. To illustrate, after performing reconfiguration 406, RU 340 may set state 442 to indicate success of reconfiguration 406.

[0085] In some examples, report message 440 may also indicate one or more batch numbers. For example, the one or more batch numbers may include batch number 426. Alternatively or in addition, report message 440 may indicate a plurality of batch numbers. For illustration, report message 440 may indicate a plurality of states associated with the plurality of batch numbers (the plurality of states may include state 442 associated with batch number 426).

[0086] In some cases, reconfiguration 406 may fail. In such examples, RU 340 may avoid changing carrier 490 from first configuration 404 to second configuration 408, and state 442 may indicate failure of reconfiguration 406. For illustration, in some implementations, reconfiguration 406 is associated with a threshold time interval, and if reconfiguration 406 is not initiated or completed within the threshold time interval, reconfiguration 406 may fail (e.g., by "timeout"). For illustration, instruction 430 may specify the beginning of the threshold time interval or may be associated with the beginning of the threshold time interval. If RU 340 does not detect triggering event 402 within the threshold time interval (e.g., by detecting a transition to a particular frame number 432), RU 340 may determine failure of reconfiguration 406. In such examples, RU 340 may set state 442 to indicate failure of reconfiguration 406. In some implementations, a timeout of reconfiguration 406 based on expiration of a threshold time interval can prevent late execution of reconfiguration 406 that might otherwise occur in some circumstances (such as if frame numbers "wrap around" and are subsequently reused).

[0087] In some implementations, the state 442 includes a flag. The flag may have one of a first value (such as zero or one) to indicate success of the reconfiguration 406 or a second value (such as one or zero) to indicate failure of the reconfiguration 406. The RU 340 may select between the first value and the second value to indicate success of the reconfiguration 406 or failure of the reconfiguration 406 to the DU 330, respectively.

[0088] In some examples, if status 442 indicates a failure of reconfiguration 406, DU 330 may re-initiate reconfiguration 406. For example, DU 330 may provide a command to RU 340 indicating that RU 340 is to retry reconfiguration 406 (or another reconfiguration).

[0089] In some implementations, the reconfiguration 406 may be associated with a guard time 412. For example, the guard time 412 may be associated with a specific mode of the RU 340, such as a reference state or a predetermined state. In some examples, the specific mode corresponds to a mode in which the RU 340 temporarily terminates signal transmission, temporarily terminates signal reception, or both. In such examples, the guard time 412 may be associated with a specific mode in which one or more of signal transmission or signal reception is temporarily terminated. For illustration, before initiating the reconfiguration 406, the RU 340 may initiate the specific mode. After initiating the specific mode, the RU 340 may initiate the reconfiguration 406. After completing the reconfiguration 406, the RU 340 interrupts the specific mode, for example, by resuming the transmission of signals, resuming the reception of signals, or both. By performing the reconfiguration 406 while in the specific mode, the RU 340 may reduce or avoid instances of spurious signal transmission or reception, which may be caused by the RU 340 operating according to an unknown or "intermediate" configuration before the reconfiguration 406 is completed.

[0090] In some examples, the guard time 412 may be based on the capabilities of the RU 340. For illustration, the capabilities may include one or more of the following: the number of processors of the RU 340, the processing speed of the RU 340, the load associated with the RU 340, one or more other parameters, or a combination thereof. Further, the RU 340 may send a capability message 410 indicating the guard time 412 to the DU 330. In such examples, the DU 330 may determine that the second configuration 408 will take effect after the guard time 412.

[0091] In some examples, the guard time may be based on the particular one or more stored reconfiguration commands to be activated based on the triggering event 402. To illustrate, some reconfiguration commands may take little or no time to reconfigure, such as a change to a static time division duplex (TDD) mode, while other reconfiguration commands may take more time to reconfigure, such as a transmit power change. In such cases, the RU 340 may send a report message 440 to the DU 330 that indicates the accumulated guard time for a set of stored commands as a status 442. In such examples, the DU 330 may determine that the second configuration 408 will take effect after the guard time as communicated in the report message 440.

[0092] In some examples, the guard time 412 may occur before the triggering event 402. In such examples, the RU 340 may initiate the particular mode and may perform the reconfiguration 406 before the triggering event 402, such as before a frame boundary associated with a particular frame number 432 (e.g., a frame boundary separating the xth frame from the (x-1)th frame). In some other examples, the guard time 412 may occur after the triggering event 402. In such examples, the RU 340 may initiate the particular mode and may perform the reconfiguration 406 after the triggering event 402, such as after a frame boundary associated with a particular frame number 432 (e.g., a frame boundary separating the xth frame from the (x-1)th frame).

[0093] In some examples, RU 340 may send an acknowledgement (ACK) associated with each configuration command received from DU 330 to DU 330. For example, RU 340 may send a first ACK based on receiving configuration command 422 and a second ACK based on receiving configuration command 424 to DU 330. In some examples, each such ACK may indicate a batch number 426. In some examples, DU 330 may send instructions 430 based on the number of ACKs received from RU 340 associated with batch number 426. For example, if reconfiguration 406 is to include implementing two configuration commands (such as configuration commands 422, 424), DU 330 may transmit instructions 430 to RU 340 based on receiving two ACKs (which may indicate batch number 426).

[0094] After performing the reconfiguration 406, the RU 340 may communicate with one or more UEs based on the second configuration 408 of the carrier 490. For example, the RU 340 may transmit data to or receive data from the UE 115 based on the second configuration 408 of the carrier 490.

[0095] In some examples, RU 340 and DU 330 may be referred to as network entities associated with an open radio access network (O-RAN), such as where RU 340 corresponds to a first network entity of the O-RAN and where DU 330 corresponds to a second network entity of the O-RAN. Configuration commands 422 and 424 may be associated with a management plane (M-plane) associated with the O-RAN. In some examples, configuration commands 422 and 424 may correspond to remote procedure call (RPC) commands received from DU 330. In some aspects of the present disclosure, the M-plane may be referred to as a semi-static M-plane (e.g., where batching of commands using a batch number such as batch number 426 enables a semi-static state of the M-plane).

[0096] In some implementations, a network entity (such as Figure 3DU 330, CU 310, Figure 3 424 to initiate reconfiguration 406 based on one or more criteria. For example, the one or more criteria may include one or more of the following as illustrative examples: time of day, day of week, operating state of the wireless communication system 400, or load associated with the RU 340. To illustrate, in some implementations, the transmit power of the RU 340 or UE 115 may be temporarily reduced via reconfiguration 406 based on the time of day (e.g., at night) when fewer UEs may communicate with the RU 340 and less interference may exist within the wireless communication system 400.

[0097] Alternatively or in addition, reconfiguration 406 may be coordinated between multiple RUs, such as RUs of cells adjacent to the cell of RU 340. In such examples, trigger event 402 may be used across multiple RUs to improve performance or to reduce or avoid conflicts between the multiple RUs. To illustrate, in one example, a RU of a neighboring cell may be deactivated (e.g., based on the time of day, based on the number of UEs connected to the RU failing to exceed a threshold, or based on one or more other criteria), and the transmit power of RU 340 or UE 115 may be increased via reconfiguration 406 when the RU of the neighboring cell is in a deactivated state. In such examples, the transmit power may be increased when the RU of the neighboring cell is less susceptible to interference from UE 115 (e.g., when in a deactivated state). In another example, RU 340 may be deactivated and the transmit power associated with the neighboring cell may be increased.

[0098] Although a single lot number 426 has been described for illustration, in some examples, multiple lot numbers may be used by the wireless communication system 400. For example, the RU 340 may receive multiple configuration commands associated with multiple different lot numbers. Each lot number may be associated with a different corresponding trigger event. Each lot number may be associated with a different corresponding carrier, or may be associated with a different corresponding configuration of the carrier 490.

[0099] One or more aspects described herein can improve the performance of a wireless communication system. For example, by using batch number 426, RU 340 can implement configuration commands 422 and 424 at a common time or within a common time interval. Therefore, RU 340 can avoid or reduce instances of unknown or intermediate configurations of carrier 490 (which may occur if configuration commands 422 and 424 arrive at RU 340 or are executed out of order by the RU). Further, in some examples, RU 340 can perform reconfiguration 406 of carrier 490 on the fly, without temporarily disabling carrier 490 during reconfiguration 406. RU 340 can also perform reconfiguration 406 of carrier 490 without reassigning carrier 490 to another RU during reconfiguration 406. Therefore, the availability of wireless resources is increased, while also reducing or avoiding the overhead associated with scheduling the reassignment of carrier 490, thereby enhancing the performance of wireless communication system 400.

[0100] Figure 5 is a flow chart illustrating an example method 500 for supporting batch numbering of one or more configuration commands of a RU according to one or more aspects. In some examples, the method 500 is performed by a network entity, such as RU 340.

[0101] The method 500 includes receiving one or more configuration commands associated with a carrier having a first configuration, at 504. The one or more configuration commands each indicate a batch number. For example, the RU 340 may receive one or more of the configuration commands 422 and 424 from the DU 330 via the fronthaul link 480. The one or more configuration commands may indicate the batch number 426.

[0102] Method 500 also includes storing the one or more configuration commands, at 506. For example, RU 340 may store (eg, cache or buffer) one or more of configuration commands 422 and 424 at memory 242 or at another location, such as at a cache or buffer.

[0103] The method 500 also includes, at 508, based on detecting the triggering event, performing a reconfiguration of the carrier from the first configuration to the second configuration, the reconfiguration being based on the one or more configuration commands. For example, based on detecting the triggering event 402, the RU 340 may perform a reconfiguration 406 of the carrier 490 from the first configuration 404 to the second configuration 408.

[0104] Figure 6 is a flow chart illustrating an example method 600 for supporting batch numbering of one or more configuration commands for RUs according to one or more aspects. In some examples, the method 600 is performed by a network entity, such as the DU 330.

[0105] The method 600 includes, at 602, sending one or more configuration commands associated with a carrier. The one or more configuration commands each indicate a batch number. For example, the DU 330 may send one or more of the configuration commands 422 and 424 to the RU 340 via the fronthaul link 480. The one or more configuration commands may indicate the batch number 426.

[0106] The method 600 also includes receiving, based on the one or more configuration commands, a report message indicating a status associated with reconfiguration of the carrier from the first configuration to the second configuration, at 604. For example, the DU 330 may receive a report message 440 from the RU 340 (e.g., via the fronthaul link 480) indicating a status 442 associated with reconfiguration 406 of the carrier 490 from the first configuration 404 to the second configuration 408.

[0107] In a first aspect, an apparatus for wireless communication by a network entity includes a memory and one or more processors coupled to the memory. The one or more processors are configured to receive one or more configuration commands associated with a carrier having a first configuration. The one or more configuration commands each indicate a batch number. The one or more processors are further configured to store the one or more configuration commands and, based on detection of a triggering event, perform a reconfiguration of the carrier from the first configuration to a second configuration, the reconfiguration being based on the one or more configuration commands.

[0108] In a second aspect, in combination with the first aspect, the one or more processors are further configured to: receive an instruction before detecting the triggering event, the instruction indicating the triggering event and further indicating the batch number.

[0109] In a third aspect, in combination with one or more of the first aspect or the second aspect, the instruction indicates a specific time point associated with the trigger event, and the specific time point is associated with one or more of the following: global navigation satellite system (GNSS) time, frame number, subframe number, time slot number, symbol number or another parameter.

[0110] In a fourth aspect, in combination with one or more of the first to third aspects, the one or more configuration commands include multiple configuration commands associated with the batch number, the one or more processors are further configured to receive the multiple configuration commands in a specific order, and the one or more processors are further configured to perform the reconfiguration based on the specific order.

[0111] In a fifth aspect, in combination with one or more of the first to fourth aspects, the one or more processors are further configured to: send a capability message indicating a protection time associated with the reconfiguration of the carrier from the first configuration to the second configuration.

[0112] In the sixth aspect, in combination with one or more of the first to fifth aspects, the protection time occurs before the trigger event or after the trigger event, and the protection time is associated with a specific mode in which one or more of signal sending or signal receiving is temporarily terminated.

[0113] In a seventh aspect, in combination with one or more of the first to sixth aspects, the one or more processors are further configured to: send a report message based on all configuration messages associated with the batch number to date, the report message indicating a protection time associated with the reconfiguration of the carrier from the first configuration to the second configuration.

[0114] In an eighth aspect, in combination with one or more of the first to seventh aspects, the one or more processors are further configured to: send a report message indicating a status associated with the reconfiguration of the carrier.

[0115] In a ninth aspect, in combination with one or more of the first to eighth aspects, the report message further indicates that one or more batch numbers include the batch number.

[0116] In a tenth aspect, in combination with one or more of the first to ninth aspects, the network entity corresponds to a radio unit (RU) associated with an open radio access network (O-RAN), the one or more configuration commands are associated with a management plane (M plane), the management plane (M plane) is associated with the O-RAN, and the one or more configuration commands correspond to a remote procedure call (RPC) command received from a distributed unit (DU) associated with the O-RAN.

[0117] In the eleventh aspect, in combination with one or more aspects of the first to tenth aspects, the one or more configuration commands indicate one or more of the following: a gain change associated with the carrier, a transmit power change associated with the carrier, a subcarrier spacing (SCS) change associated with the carrier, a static physical random access channel (PRACH) configuration change associated with the carrier, a static time division duplex (TDD) mode change associated with the carrier, a static sounding reference signal (SRS) configuration change associated with the carrier, an endpoint configuration change associated with the carrier, or another configuration change associated with the carrier.

[0118] In a twelfth aspect, a method of wireless communication performed by a network entity includes: receiving one or more configuration commands associated with a carrier having a first configuration. The one or more configuration commands each indicate a batch number. The method also includes storing the one or more configuration commands, and the method also includes: based on detecting a triggering event, performing a reconfiguration of the carrier from the first configuration to a second configuration, the reconfiguration being based on the one or more configuration commands.

[0119] In a thirteenth aspect, in combination with the twelfth aspect, the method further comprises: before detecting the trigger event, receiving an instruction, the instruction indicating the trigger event and further indicating the batch number.

[0120] In the fourteenth aspect, in combination with one or more aspects of the twelfth to the thirteenth aspects, the instruction indicates a specific time point associated with the trigger event, and the specific time point is associated with one or more of the following: global navigation satellite system (GNSS) time, frame number, subframe number, time slot number, symbol number or another parameter.

[0121] In a fifteenth aspect, in combination with one or more of aspects 12 to 14, the one or more configuration commands include a plurality of configuration commands associated with the batch number received in a specific order, and the reconfiguration is performed based on the specific order.

[0122] In the sixteenth aspect, in combination with one or more aspects from the twelfth to the fifteenth aspect, the method further includes: sending a capability message indicating a protection time associated with the reconfiguration of the carrier from the first configuration to the second configuration.

[0123] In the seventeenth aspect, in combination with one or more aspects from the twelfth to the sixteenth aspect, the protection time occurs before the trigger event or after the trigger event, and the protection time is associated with a specific mode in which one or more of signal sending or signal receiving is temporarily terminated.

[0124] In the eighteenth aspect, in combination with one or more aspects from the twelfth to the seventeenth aspect, the method further includes: sending a report message based on all configuration messages associated with the batch number to date, the report message indicating a protection time associated with the reconfiguration of the carrier from the first configuration to the second configuration.

[0125] In the nineteenth aspect, in combination with one or more aspects from the twelfth to the eighteenth aspects, the method further includes: sending a report message indicating a status associated with the reconfiguration of the carrier.

[0126] In a twentieth aspect, in combination with one or more of the twelfth to nineteenth aspects, the report message further indicates that one or more batch numbers include the batch number.

[0127] In aspect 21, in combination with one or more aspects from aspect 12 to aspect 20, the network entity corresponds to a radio unit (RU) associated with an open radio access network (O-RAN), the one or more configuration commands are associated with a management plane (M plane), the management plane (M plane) is associated with the O-RAN, and the one or more configuration commands correspond to a remote procedure call (RPC) command received from a distributed unit (DU) associated with the O-RAN.

[0128] In the twenty-second aspect, in combination with one or more aspects from the twelfth to the twenty-first aspects, the one or more configuration commands indicate one or more of the following: a gain change associated with the carrier, a transmit power change associated with the carrier, a subcarrier spacing (SCS) change associated with the carrier, a static physical random access channel (PRACH) configuration change associated with the carrier, a static time division duplex (TDD) mode change associated with the carrier, a static sounding reference signal (SRS) configuration change associated with the carrier, an endpoint configuration change associated with the carrier, or another configuration change associated with the carrier.

[0129] In a twenty-third aspect, an apparatus for wireless communication by a network entity includes a memory and one or more processors coupled to the memory. The one or more processors are configured to send one or more configuration commands associated with a carrier. The one or more configuration commands each indicate a batch number. The one or more processors are further configured to receive a report message based on the one or more configuration commands, the report message indicating a status associated with reconfiguration of the carrier from a first configuration to a second configuration.

[0130] In a twenty-fourth aspect, in combination with the twenty-third aspect, the one or more processors are further configured to: send an instruction before receiving the report message, the instruction indicating a triggering event associated with the reconfiguration of the carrier and further indicating the batch number.

[0131] In aspect twenty-fifth, in combination with one or more of aspects twenty-third to twenty-fourth, the instruction indicates a specific point in time associated with the triggering event, and the specific point in time is associated with one or more of the following: global navigation satellite system (GNSS) time, frame number, subframe number, time slot number, symbol number or another parameter.

[0132] In a twenty-sixth aspect, in combination with one or more of the twenty-third to twenty-fifth aspects, the one or more configuration commands include a plurality of configuration commands associated with the batch number sent in a specific order, and the reconfiguration is performed based on the specific order.

[0133] In aspect twenty-seven, in combination with one or more aspects of aspects twenty-third to twenty-six, the one or more processors are further configured to: receive a capability message indicating a protection time associated with the reconfiguration of the carrier from the first configuration to the second configuration.

[0134] In aspect 28, in combination with one or more of aspects 23 to 27, the protection time occurs before a trigger event associated with the reconfiguration or after the trigger event associated with the reconfiguration, and the protection time is associated with a specific mode in which one or more of signal sending or signal reception is temporarily terminated.

[0135] In aspect 29, in combination with one or more aspects from aspect 23 to aspect 28, the report message indicates a protection time associated with the reconfiguration of the carrier from the first configuration to the second configuration based on all configuration messages associated with the batch number to date.

[0136] In a thirtieth aspect, in combination with one or more of the twenty-third to twenty-ninth aspects, the report message further indicates that one or more batch numbers include the batch number.

[0137] In the thirty-first aspect, in combination with one or more aspects of the twenty-third to the thirtieth aspects, the network entity corresponds to a distributed unit (DU) associated with an open radio access network (O-RAN), the one or more configuration commands are associated with a management plane (M plane), the management plane (M plane) is associated with the O-RAN, and the one or more configuration commands correspond to a remote procedure call (RPC) command sent to a radio unit (RU) associated with the O-RAN.

[0138] In aspect 32, in combination with one or more aspects from aspect 23 to aspect 31, the one or more configuration commands indicate one or more of the following: a gain change associated with the carrier, a transmit power change associated with the carrier, a subcarrier spacing (SCS) change associated with the carrier, a static physical random access channel (PRACH) configuration change associated with the carrier, a static time division duplex (TDD) mode change associated with the carrier, a static sounding reference signal (SRS) configuration change associated with the carrier, an endpoint configuration change associated with the carrier, or another configuration change associated with the carrier.

[0139] In a thirty-third aspect, a method of wireless communication by a network entity includes: sending one or more configuration commands associated with a carrier. The one or more configuration commands each indicate a batch number. The method also includes: receiving a report message based on the one or more configuration commands, the report message indicating a status associated with reconfiguration of the carrier from a first configuration to a second configuration.

[0140] In a thirty-fourth aspect, in combination with the thirty-fourth aspect, the method further includes: sending an instruction before receiving the report message, the instruction indicating a triggering event associated with the reconfiguration of the carrier and further indicating the batch number.

[0141] In aspect thirty-fifth, in combination with one or more aspects from aspect thirty-third to aspect thirty-third, the instruction indicates a specific time point associated with the trigger event, and the specific time point is associated with one or more of the following: global navigation satellite system (GNSS) time, frame number, subframe number, time slot number, symbol number or another parameter.

[0142] In aspect thirty-six, in combination with one or more aspects from aspect thirty-three to aspect thirty-five, the one or more configuration commands include a plurality of configuration commands associated with the batch number sent in a specific order, and the reconfiguration is performed based on the specific order.

[0143] In aspect thirty-seven, in combination with one or more aspects from aspect thirty-three to aspect thirty-six, the method further includes: receiving a capability message indicating a protection time associated with the reconfiguration of the carrier from the first configuration to the second configuration.

[0144] In aspect thirty-eight, in combination with one or more aspects from aspect thirty-three to aspect thirty-seven, the protection time occurs before a triggering event associated with the reconfiguration or after the triggering event associated with the reconfiguration, and the protection time is associated with a specific mode in which one or more of signal sending or signal reception is temporarily terminated.

[0145] In aspect thirty-ninth, in combination with one or more aspects from aspects thirty-third to thirty-eight, the report message indicates a protection time associated with the reconfiguration of the carrier from the first configuration to the second configuration based on all configuration messages associated with the batch number to date.

[0146] In a 40th aspect, in combination with one or more of aspects 33 to 39, the report message further indicates one or more batch numbers including the batch number.

[0147] In the forty-first aspect, in combination with one or more aspects from the thirty-third to the fortieth aspects, the network entity corresponds to a distributed unit (DU) associated with an open radio access network (O-RAN), the one or more configuration commands are associated with a management plane (M plane), the management plane (M plane) is associated with the O-RAN, and the one or more configuration commands correspond to a remote procedure call (RPC) command sent to a radio unit (RU) associated with the O-RAN.

[0148] In aspect 42, in combination with one or more aspects from aspect 33 to aspect 41, the one or more configuration commands indicate one or more of the following: a gain change associated with the carrier, a transmit power change associated with the carrier, a subcarrier spacing (SCS) change associated with the carrier, a static physical random access channel (PRACH) configuration change associated with the carrier, a static time division duplex (TDD) mode change associated with the carrier, a static sounding reference signal (SRS) configuration change associated with the carrier, an endpoint configuration change associated with the carrier, or another configuration change associated with the carrier.

[0149] It should be understood by those skilled in the art that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0150] One or more components, functional blocks and modules described herein may include a processor, an electronic device, a hardware device, an electronic component, a logic circuit, a memory, a software code, a firmware code, etc., or any combination thereof. 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, executables, threads of execution, processes, and / or functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms. In addition, the features discussed herein may be implemented via dedicated processor circuits, via executable instructions, or a combination thereof.

[0151] One or more of the illustrative logics, logical blocks, modules, circuits, and processes described herein may be implemented as electronic hardware, computer software, or a combination of both. Whether such functionality can be implemented in hardware or software may depend on the specific application and design of the overall system.

[0152] The hardware and data processing apparatus for implementing the various illustrative logics, logic blocks, modules and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using a general purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller or state machine. In some specific implementations, a processor may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration. In some specific implementations, specific processes and methods may be performed by circuits specific to a given function.

[0153] One or more functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents, or any combination thereof. Specific implementations of the subject matter described in this specification may also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on computer storage media for execution by data processing apparatus or for controlling the operation of data processing apparatus.

[0154] If implemented in software, one or more such functions may be stored as one or more instructions or codes on a computer-readable medium or sent via a computer-readable medium. One or more operations of the method or process disclosed herein may be implemented in a processor executable software module that may reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, and the communication media include any media that may be implemented to transfer a computer program from one place to another. Storage media may be any available medium accessible to a computer. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of an instruction or data structure and can be accessed by a computer. Disks and optical disks as used herein include compact discs (CDs), laser discs, optical disks, digital versatile discs (DVDs), floppy disks and blue discs, wherein disks generally reproduce data magnetically, and optical disks reproduce data optically with lasers. The above combination should also be included in the scope of computer-readable media. Additionally, the operations of a method or process may reside as one or any combination or set of codes and instructions on a machine-readable medium and a computer-readable medium, which may be incorporated into a computer program product.

[0155] Various modifications to the specific implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to some other specific implementations without departing from the spirit or scope of the disclosure. Therefore, the claims are not intended to be limited to the specific implementations shown herein, but are to be consistent with the broadest scope consistent with the disclosure, the principles and novel features disclosed herein.

[0156] Additionally, one of ordinary skill in the art will readily recognize that the terms "upper" and "lower" are sometimes used for ease of describing the drawings and indicate relative positions corresponding to the orientation of the drawings on a correctly oriented page, and may not reflect the correct orientation of any device as implemented.

[0157] Certain features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations, either individually or in any suitable subcombination. Furthermore, while features may be described above as functioning in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be removed from the combination, and a claimed combination may be directed to subcombinations or variations of subcombinations.

[0158] Similarly, although the operations are depicted in a specific order in the figure, this should not be understood as requiring such operations to be performed in the specific order shown or in a sequential order, or to perform all the illustrated operations to achieve the desired result. Further, the accompanying drawings can schematically depict one or more example processes in the form of a flow chart. However, other operations that are not depicted can be combined in the schematically illustrated example process. For example, one or more additional operations can be performed before, after, at the same time, or between any illustrated operations. In some environments, multitasking and parallel processing are advantageous. In addition, the separation of various system components in the specific implementation described above should not be understood as requiring such separation in all specific implementations, and it should be understood that the program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, some other specific implementations also fall within the scope of the appended claims. In some cases, the actions described in the claims can be performed in different orders and still achieve the desired result.

[0159] As used herein, including in the claims, the term "or" used in a list of two or more items means that any of the listed items may be employed alone, or any combination of two or more of the listed items may be employed. For example, if a composition is described as containing components A, B, or C, the composition may contain A alone; B alone; C alone; A and B combined; A and C combined; B and C combined; or A, B, and C combined. In addition, as used herein, including in the claims, "or" as used in a list of items beginning with "at least one" indicates a separate list, so that, for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any combination of any of these. The term "substantially" is defined as to a large extent, but not necessarily entirely, what is specified (and includes what is specified; for example, substantially 90 degrees includes 90 degrees, and substantially parallel includes parallel), as understood by one of ordinary skill in the art. In any disclosed implementation, the term "substantially" may be replaced with "within (percent) of" the specified content, where the percentage includes 0.1%, 1%, 5%, or 10%.

[0160] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Therefore, the disclosure is not intended to be limited to the examples and designs described herein, but to be consistent with the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication by a network entity, the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: receiving one or more configuration commands associated with a carrier having a first configuration, the one or more configuration commands each indicating a batch number; storing the one or more configuration commands; as well as Based on the detection of a triggering event, reconfiguration of the carrier from the first configuration to a second configuration is performed, the reconfiguration being based on the one or more configuration commands. 2 . The apparatus of claim 1 , wherein the one or more processors are further configured to: receive an instruction prior to detecting the triggering event, the instruction indicating the triggering event and further indicating the batch number.

3. An apparatus according to claim 2, wherein the instruction indicates a specific time point associated with the triggering event, and wherein the specific time point is associated with one or more of the following: global navigation satellite system (GNSS) time, a frame number, a subframe number, a time slot number, a symbol number, or another parameter.

4. The apparatus of claim 1 , wherein the one or more configuration commands include a plurality of configuration commands associated with the batch number, wherein the one or more processors are further configured to receive the plurality of configuration commands in a specific order, and wherein the one or more processors are further configured to perform the reconfiguration based on the specific order.

5. The apparatus of claim 1, wherein the one or more processors are further configured to send a capability message indicating a guard time associated with the reconfiguration of the carrier from the first configuration to the second configuration.

6. The apparatus of claim 5, wherein the guard time occurs before the trigger event or after the trigger event, and wherein the guard time is associated with a specific mode in which one or more of signal transmission or signal reception is temporarily terminated.

7. The apparatus of claim 1, wherein the one or more processors are further configured to: send a report message based on all configuration messages associated with the batch number to date, the report message indicating a guard time associated with the reconfiguration of the carrier from the first configuration to the second configuration.

8. The apparatus of claim 1, wherein the one or more processors are further configured to send a report message indicating a status associated with the reconfiguration of the carrier.

9. A method of wireless communication performed by a network entity, the method comprising: receiving one or more configuration commands associated with a carrier having a first configuration, the one or more configuration commands each indicating a batch number; storing the one or more configuration commands; as well as Based on detecting a triggering event, reconfiguration of the carrier from the first configuration to a second configuration is performed, the reconfiguration being based on the one or more configuration commands.

10. The method according to claim 9, further comprising: Prior to detecting the triggering event, an instruction is received, the instruction indicating the triggering event and further indicating the batch number.

11. A method according to claim 10, wherein the instruction indicates a specific time point associated with the triggering event, and wherein the specific time point is associated with one or more of the following: global navigation satellite system (GNSS) time, frame number, subframe number, time slot number, symbol number, or another parameter.

12. The method of claim 9, wherein the one or more configuration commands include a plurality of configuration commands associated with the lot number received in a specific order, and wherein the reconfiguring includes being performed based on the specific order.

13. The method according to claim 9, further comprising: A capability message is sent, the capability message indicating a guard time associated with the reconfiguration of the carrier from the first configuration to the second configuration. The method of claim 13 , wherein the guard time occurs before the trigger event or after the trigger event.

15. The method according to claim 9, further comprising: A report message is sent based on all configuration messages associated to date with the batch number, the report message indicating a guard time associated with the reconfiguration of the carrier from the first configuration to the second configuration.

16. The method according to claim 9, further comprising: A report message is sent, the report message indicating a status associated with the reconfiguration of the carrier.

17. An apparatus for wireless communication by a network entity, the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: sending one or more configuration commands associated with the carrier, the one or more configuration commands each indicating a batch number; as well as A report message is received based on the one or more configuration commands, the report message indicating a status associated with reconfiguration of the carrier from a first configuration to a second configuration.

18. The apparatus of claim 17, wherein the one or more processors are further configured to send an instruction prior to receiving the report message, the instruction indicating a triggering event associated with the reconfiguration of the carrier and further indicating the batch number.

19. An apparatus according to claim 18, wherein the instruction indicates a specific time point associated with the triggering event, and wherein the specific time point is associated with one or more of the following: global navigation satellite system (GNSS) time, a frame number, a subframe number, a time slot number, a symbol number, or another parameter.

20. The apparatus of claim 17, wherein the one or more configuration commands include a plurality of configuration commands associated with the lot number sent in a specific order, and wherein the reconfiguration is performed based on the specific order.

21. The apparatus of claim 17, wherein the one or more processors are further configured to receive a capability message indicating a guard time associated with the reconfiguration of the carrier from the first configuration to the second configuration.

22. The apparatus of claim 21, wherein the guard time occurs before a triggering event associated with the reconfiguration or after the triggering event associated with the reconfiguration.

23. The apparatus of claim 17, wherein the report message indicates a guard time associated with the reconfiguration of the carrier from the first configuration to the second configuration based on all configuration messages associated with the batch number to date.

24. A method for wireless communication by a network entity, the method comprising: sending one or more configuration commands associated with the carrier, the one or more configuration commands each indicating a batch number; as well as A report message is received based on the one or more configuration commands, the report message indicating a status associated with reconfiguration of the carrier from a first configuration to a second configuration.

25. The method according to claim 24, further comprising: An instruction is sent prior to receiving the report message, the instruction indicating a triggering event associated with the reconfiguration of the carrier and further indicating the batch number.

26. A method according to claim 25, wherein the instruction indicates a specific time point associated with the triggering event, and wherein the specific time point is associated with one or more of the following: global navigation satellite system (GNSS) time, frame number, subframe number, time slot number, symbol number, or another parameter.

27. The method of claim 24, wherein the one or more configuration commands include a plurality of configuration commands associated with the lot number sent in a specific order, and wherein the reconfiguration is performed based on the specific order.

28. The method according to claim 24, further comprising: A capability message is received, the capability message indicating a guard time associated with the reconfiguration of the carrier from the first configuration to the second configuration.

29. The method of claim 28, wherein the guard time occurs before a triggering event associated with the reconfiguration or after the triggering event associated with the reconfiguration.

30. The method of claim 24, wherein the report message indicates a guard time associated with the reconfiguration of the carrier from the first configuration to the second configuration based on all configuration messages associated with the batch number to date.

Images