Deterministically analyzable reporting of radio unit performance information in a radio access network

Abstract

The system includes a cellular communication antenna and a radio unit (RU) connected to the cellular communication antenna. The RU is configured to obtain status data of the RU and write a plurality of values ​​of the status data to a file for each of a plurality of lines of the file storing measurement groups and object unit identifiers corresponding to the measurement groups, with measurement group and object unit identifiers assigned to values ​​from the status data stored in each of the plurality of lines of the file. The RU may then store and / or transmit the file.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority from Indian Patent Application No. 202341027682 filed on April 14, 2023, the entire contents of which are incorporated herein by reference.

[0002] The present invention relates to deterministically analyzable reporting of wireless unit performance information in a wireless access network. [Background technology]

[0003] An open radio access network (O-RAN) includes radio units (RUs) connected to one or more antennas for transmitting and receiving radio signals to and from user equipment (UE), such as mobile phones. Each RU is connected to a distributed unit (DU), which may itself be connected to an aggregation unit with multiple other DUs. An orchestrator, such as in the service management and orchestration (SMO) standard in the O-RAN, may receive status information from the RUs to monitor their operation. Summary of the Invention [Means for solving the problem]

[0004] In one aspect of the present invention, a system includes a cellular communication antenna and a radio unit (RU) connected to the cellular communication antenna. The RU is configured to obtain status data of the RU and write multiple values ​​of the status data to a file for each of multiple lines of the file that store measurement groups and object unit identifiers corresponding to the measurement groups, with measurement group and object unit identifiers assigned to values ​​from the status data stored in each of the multiple lines of the file. The RU may then store and / or transmit the file.

[0005] In order that the advantages of the present invention may be readily understood, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments which are illustrated in the accompanying drawings, the invention being described and explained with additional specificity and detail through the use of the accompanying drawings, with the understanding that these drawings depict only typical embodiments of the invention and therefore should not be considered as limiting its scope. [Brief explanation of the drawings]

[0006] [Figure 1] 1 is a schematic block diagram illustrating a cellular communication network. [Figure 2] FIG. 2 is a schematic block diagram of a wireless unit. [Figure 3] FIG. 2 is a process flow diagram of a method for generating a file reporting wireless unit status information according to one embodiment of the present invention. [Figure 4] 4 is a table illustrating the arrangement of data within a file reporting wireless unit status information, according to one embodiment of the present invention. [Figure 5] FIG. 1 is a process flow diagram of a method for writing values ​​to a file having a fixed number of columns. [Figure 6] FIG. 1 is a process flow diagram of a method for reading values ​​in a file having a fixed number of columns. [Figure 7]FIG. 1 is a schematic block diagram of an exemplary computing device suitable for implementing methods according to embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0007] 1 illustrates an exemplary cellular communication network 100. The cellular communication network 100 includes multiple antennas 102 capable of transmitting and receiving cellular radio signals. The antennas 102 may be beamforming antennas, directional antennas, or any type of antenna known in the art of cellular radio communication. The antennas 102 may include power amplifiers or other signal processing electronics.

[0008] The one or more antennas 102 are connected to a radio unit (RU) 104. The radio unit may include electronic components configured to convert binary data to be transmitted into signals transmitted by the one or more antennas 102. Similarly, the RU 104 converts signals received from the one or more antennas 102 into binary data.

[0009] One or more radio units 104 are connected to distributed units (DUs) 106. Each DU 106 may be implemented as a computing device configured to receive binary data from the RUs 104 and forward the binary data over a network connection to a centralized unit (CU) 108 or another DU 106. Similarly, each DU may receive data over the network from a CU 108 or another DU 106 and send the data to one or more RUs 104 for transmission.

[0010] An orchestrator, such as a Service Management and Orchestration Orchestrator (SMO) 110, responsible for service management and orchestration according to the O-RAN standard, monitors the status of the network 100. For example, the SMO 110 may communicate with the RUs 104 to monitor the status of the RUs 104. The SMO 110 may be connected to the RUs 104 by a direct network connection or by communication with the RUs 104 via a DU 106 connected to the RUs 104 and possibly a CU connected to the DUs 106.

[0011] Each RU 104, DU 106, CU 108, and SMO 110 may be implemented in accordance with O-RAN standards, which may be found published by the O-RAN Alliance in the following documents, all of which are incorporated herein by reference in their entirety: O-RAN Architecture Description 9.0,O-RAN.WG1.OAD-R003-v09.00(June 2023) O-RAN Slicing Architecture 10.0,O-RAN.WG1.Slicing-Architecture-R003-v10.00(June 2023) O-RAN Use Cases Analysis Report 11.0,O-RAN.WG1.Use-Cases-Analysis-Report-R003-v11.00(June 2023) O-RAN Use Cases Detailed Specification 11.0,O-RAN.WG1.Use-Cases-Detailed-Specification-R003-v11.00 (June 2023) O-RAN R1 interface:Use Cases and Requirements 4.0,O-RAN.WG2.R1UCR.v04.00(June 2023) O-RAN Massive MIMO Use Cases Technical Report 1.0,O-RAN.WG1.mMIMO-Use-Cases-TR-v01.00(June 2022)

[0012] 2, each RU 104 may include various electronics. For example, the RU 104 may include an RF transceiver 202 configured to transmit and receive radio frequency (RF) signals to one or more antennas 102 connected to the RU 104. The antennas 102 and associated electronics may amplify and transmit the RF signals received from the RU 104.

[0013] The RU 104 may further include an optical transceiver 204. The optical transceiver 204 may be connected to an optical fiber connecting the RU 104 to the DU 106 or other computing device. The optical transceiver 204 converts binary data into optical signals transmitted over the optical fiber and converts optical signals received over the optical fiber into binary data. The optical transceiver 204 may be implemented as a small form-factor pluggable (SFP) transceiver, an SFP28 transceiver, a quad small form-factor transceiver (QSFP), a QSFP+, a QSFP28, a QSFP56, or an XFP transceiver. The optical transceiver 204 may include one or more sensors and may report or facilitate measurement of various items of status data. The output of the one or more sensors and various items of status data may be transmitted by the RU 104 to the SMO 110 to enable the SMO 110 to assess the status of the network 100.

[0014] 3 shows a method 300 for generating a file containing status data for an RU 104. Method 300, and other methods disclosed herein, contemplate data reported by an RU 104 regarding an optical transceiver 204, with the understanding that any other type of data describing the operational state of the RU 104 may be processed in a similar manner. Method 300 may be performed for a time interval (the “current time interval”) having a start time (e.g., the end time of a previous time interval) and an end time.

[0015] The method 300 includes obtaining 302 a status of the optical transceiver 204. Obtaining the status may include obtaining data from registers of the RU 104, such as performance management (PM) counters of the RU 104. Obtaining 302 may include obtaining measurements of physical characteristics, such as some or all of the following: The temperature of the time interval, for example, the maximum, minimum, average, or other statistical value of the temperature readings of the temperature sensor of the optical transceiver 204 during the time interval. The received power for the time interval, e.g., the maximum, minimum, average, or other statistical value of the optical signal received by the optical transceiver 204 during that time period. The received power may be for a particular lane. The transmit power for the time interval, e.g., the maximum, minimum, average, peak, final, or other statistical value of the optical signal transmitted by the optical transceiver 204 during the time interval. The transmit power may be for a particular lane. Frequency data for that time interval, e.g., center frequency, bandwidth (e.g., -3 dB bandwidth), or other information describing the frequency of the transmitted optical signal, and possibly statistical characteristics (e.g., maximum, minimum, average, leading value, trailing value, standard deviation) of the center frequency and / or bandwidth for that time interval. The frequency bin count for that time interval, e.g., the number of occurrences during the time interval of frequencies within the range corresponding to each of a number of frequency bins. Aggregation of any of the above reference values ​​for multiple ports or multiple transceivers.

[0016] The status may include other values ​​describing the volume of data transmitted by the transceiver during the time interval, such as data transmitted per unit time, data received per unit time, or any other statistical characteristic (e.g., maximum, minimum, average, standard deviation) of the data transmitted or received during the time interval.

[0017] The above examples of the status of the optical transceiver 204 are merely illustrative, and any other data describing the operation of the optical transceiver 204 or the RU 104 itself, including with respect to the transmission and reception of radio frequency signals, may be obtained in step 302. For example, other values ​​that may be obtained and processed according to method 300 may include some or all of the following: Received signal strength indicator (RSSI) measurements for each frequency band of a plurality of frequency bands, and / or statistical characteristics of the RSSI for each frequency band during a time interval (e.g., maximum, minimum, average, leading, trailing, standard deviation). Upper frequency limit for the time interval. The lower frequency limit for the time interval. · Functions of time intervals. The voltage for that time interval, e.g., supply voltage and / or statistical characteristics (e.g., maximum, minimum, average, standard deviation). Energy, Power and Environment (EPE) measurements and statistics. · Transmit and receive window measurements. Energy measurements. · Aggregates or statistics about any of the above reference values.

[0018] The method may include obtaining 304 a measurement group of the RUs 104. A measurement group may be an identifier that associates multiple optical transceivers 204 with each other or multiple RUs 104 with each other. The entities (optical transceivers 204 and / or RUs 104) that belong to a measurement group may be associated with each other by geographic proximity, hardware similarity (e.g., same model, same manufacturer, etc.), usage similarity (e.g., similar data transfer volume), or any other logical association deemed relevant by an administrator of the network 100.

[0019] The method 300 may include obtaining 306 one or more measurement objects for the measurement group. The measurement objects may include identifiers of physical characteristics or other parameters measured, recorded, or transmitted by the wireless unit as part of the method 300. The measurement objects may include identifiers of any of the items of data included in the transceiver status of step 302.

[0020] The method 300 may include, for each measurement object obtained in step 306, obtaining 308 an object unit type and obtaining 310 an object unit identifier. The object unit type may identify the type of source of the data represented by the measurement object, and the object unit identifier identifies the source of the data. The object unit type and object unit identifier may be defined in accordance with the O-RAN WG4 M Plane specification, the entire contents of which are incorporated herein by reference. For example, the object unit type may specify the level of granularity of the value recorded in the row (RU level, transport level, port level). For example, a port-level object type may include a port number, where the object unit identifier is the port number itself. In another example, the object unit type may be at the RU level and describe the type of radio hardware, and the object unit identifier is an identifier of a particular RU 104.

[0021] The method 300 may include writing 312 column labels to a file, such as an otherwise unwritten file. The column labels may correspond to a measurement group (e.g., a measurement group identifier), a measurement object (e.g., a measurement object identifier), a time window start time (which may indicate a date), a time window end time (which may also indicate a date), an object unit type, and an object unit identifier as defined above. Other column labels, such as a report information type label, a report information identifier label, and a value label, may also be written. A column labeled with a report information type label may store a value that describes the type of data contained in a value stored in a column labeled with a value label. For example, a value stored in a report information type column may indicate a numeric format (e.g., decimal64 with four decimal places). The report information identifier label includes an identifier for the particular information stored in the column labeled with the value label. For example, example values ​​that may be stored in a column labeled with a report information type label may include a maximum value, a minimum value, a most recent value, a frequency bin, or other values ​​that describe the information stored in a column labeled with a value label.

[0022] Method 300 may include writing 314 the information from steps 302-310 to corresponding columns in a file labeled in step 312. There may be multiple rows in the file. FIG. 4 illustrates a table that may be generated according to method 300. The values ​​shown are merely exemplary, and each row may have a unique value relative to other rows. However, in many cases, values ​​for a particular column may be repeated across multiple rows. For example, multiple rows may represent data for the same time window and therefore have the same start and end times. Multiple rows may list the same values ​​for measurement group, measurement object, object unit type, and object unit identifier. The report information type and report information identifier may be used to identify the specific information stored in the report information value column.

[0023] There may be multiple report information value columns. For example, for a physical parameter (received power, transmitted power, temperature, voltage, frequency bin, or any other value referenced herein), the report information values ​​stored in the report information value column may include some or all of a maximum value, minimum value, average value, leading value, final value, standard deviation, or other statistical value. For a frequency bin, the report information column value may include a frequency bin identifier, a frequency bin count for the frequency bin time interval. The report information column value may include multiple combinations of frequency bin identifier and corresponding frequency bin count for that time interval.

[0024] While the format of Figure 4 results in some duplication of information, parsing of the file is deterministic and conforms to encoding best practices, such as Internet Engineering Task Force (IETF) Request for Comment (RFC) 4180, published October 2005, which is incorporated herein by reference. Note that the format of Figure 4 may be stored as comma separated values ​​(CSV), with commas between adjacent values ​​on each line. The order of columns in the file may follow the order defined in NETCONF notifications, as defined in the O-RAN Performance Management Module standard, or some other order. However, note that the approach described herein uses fewer octets compared to NETZCONF notifications.

[0025] FIG. 4 is an example of a file generated according to method 300. FIG. 5 illustrates an alternative approach for writing to a file in steps 312 and 314 of method 300. In the approach of FIG. 5, rows contain more columns than those shown in FIG. 4. Each row may contain multiple values, and each report value may not have an adjacent value indicating the type or identifier of the report value. Instead, each column represents a specific report value. In the approach of FIG. 5, when writing to a row, if a column is found to have no corresponding value (502), a null value is written (504). If a column is found to have a corresponding value, that value is written to that column (506). Writing to the row ends when it is determined that the last column has been processed (508). FIG. 5 may be used to write comma-separated values ​​(CSV), where commas are placed between adjacent values ​​within each row. While FIG. 5 has the disadvantage of potentially writing many null values, it has the advantage of being more deterministic and easier to parse.

[0026] 4 or generated according to method 500 may be transmitted to a remote computer, such as DU 106, CU 108, and / or SMO 110. The file may be transmitted using the optical transceiver 204 or using different devices and physical network connections other than optical fibers coupled to the optical transceiver 204. The file may be compressed and / or encrypted before transmission. Note that null values ​​and repeated values ​​created to maintain a fixed number of columns are both easily compressible, thus significantly reducing their impact on the size of the file.

[0027] In yet another approach, the number of columns is not fixed. Instead, each row contains one or more, and possibly multiple, attribute-value pairs, each pair containing a value label and a value corresponding to the value label, e.g., "Temperature, 30." Thus, the parser reads each value label to determine the meaning of the adjacent value, and then reads the adjacent values ​​of each attribute-value pair, until it reaches the end of the line.

[0028] 6 illustrates a method 600 for parsing a file generated according to method 300. Method 600 may be performed by SMO 110 upon receiving the file from RU 104.

[0029] The method 600 includes reading a first line of the file 602 and parsing column labels from the first line, which further indicate the number of columns 604. Reading the first line and each other line of the file may include reading up to a symbol indicating the end of line (EOL).

[0030] The method 600 includes reading 606 the next line of the file, which is then parsed to obtain measurement groups (608), parsed to obtain measurement objects (610), parsed to obtain start and end times (612), parsed to obtain object unit types (614), and parsed to obtain object unit identifiers (616).

[0031] The remaining values ​​in the next line may be processed by parsing the next value in the line (618), evaluating whether the value is null (620), and if not, storing the value according to the column label associated with the next value's column (622). If the value parsed in step 618 is found to be the last value in the line (624) and the end of file (EOF) has not been reached (626), processing continues at step 606 to read the next line of the file. If the value parsed in step 618 is not the last value in the line, processing continues at step 618 to parse the next value in the line.

[0032] The values ​​read according to method 600 may be stored in a file or object. For example, the values ​​may be stored in an extensible markup language (XML) file according to a schema, or in a JavaScript object notation (JSON) object or other type of object. In particular, the column label may be used to determine the data represented by the value and store the value in a file or object. In particular, values ​​such as the measurement group, measurement object, object unit type, and object unit identifier facilitate the generation of an object containing the data stored in the file for storage and processing by SMO 110.

[0033] 7 is a block diagram illustrating an example computing device 700. The computing device 700 may be used to perform various procedures as described herein. The nodes 102a-102d and the user equipment 116 may have some or all of the attributes of the computing device 700.

[0034] Computing device 700 includes one or more processors 702, one or more memory devices 704, one or more interfaces 706, one or more mass storage devices 708, one or more input / output (I / O) devices 710, and a display device 730, all connected to a bus 712. Processor 702 includes one or more processors or controllers that execute instructions stored in memory device 704 and / or mass storage device 708. Processor 702 may also include various types of computer-readable media, such as cache memory.

[0035] The memory device 704 includes a variety of computer-readable media, such as volatile memory (e.g., random access memory (RAM) 714) and / or non-volatile memory (e.g., read-only memory (ROM) 716). The memory device 704 may also include re-writable ROM, such as flash memory.

[0036] The mass storage device 708 includes various computer-readable media such as magnetic tape, magnetic disks, optical disks, solid-state memory (e.g., flash memory), etc. As shown in Figure 7, a particular mass storage device is a hard disk drive 724. Various drives may be included in the mass storage device 708 and enable reading from and / or writing to various computer-readable media. The mass storage device 708 includes removable media 726 and / or non-removable media.

[0037] I / O devices 710 include various devices that allow data and / or other information to be input to or obtained from computing device 700. Exemplary I / O devices 710 include cursor control devices, keyboards, keypads, microphones, monitors or other display devices, speakers, printers, network interface cards, modems, lenses, CCDs or other image capture devices, etc.

[0038] Display device 730 includes any type of device capable of displaying information to one or more users of computing device 700. Display device 730 includes, for example, a monitor, a display terminal, a video projection device, etc.

[0039] The interface 706 includes various interfaces that allow the computing device 700 to interact with other systems, devices, or computing environments. An exemplary interface 706 includes any number of different network interfaces 720, such as interfaces to a local area network (LAN), a wide area network (WAN), a wireless network, and the Internet. Other interfaces include a user interface 718 and a peripheral device interface 722. The interface 706 may also include one or more peripheral interfaces, such as interfaces for a printer, a pointing device (mouse, trackpad, etc.), a keyboard, etc.

[0040] The bus 712 allows the processor 702, memory device 704, interface 706, mass storage device 708, I / O device 710, and display device 730, as well as other devices or components connected to the bus 712, to communicate with each other. The bus 712 represents one or more of several types of bus structures, such as a system bus, a PCI bus, an IEEE 1394 bus, a USB bus, etc.

[0041] For purposes of illustration, programs and other executable program components are illustrated herein as separate blocks, with the understanding that such programs and components may reside at various times in different storage components of computing device 700 and are executed by processor 702. Alternatively, the systems and procedures described herein may be implemented in hardware or a combination of hardware, software, and / or firmware. For example, one or more application-specific integrated circuits (ASICs) can be programmed to execute one or more of the systems and procedures described herein.

[0042] In the foregoing disclosure, reference has been made to the accompanying drawings, which form a part hereof, and which show, by way of illustration, specific implementations in which the present disclosure may be practiced. It is understood that other implementations may be utilized and structural changes may be made without departing from the scope of the present disclosure. References herein to "one embodiment," "embodiment," "exemplary embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not all embodiments necessarily include the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed to be within the knowledge of one of ordinary skill in the art to affect such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly stated.

[0043] Implementations of the systems, devices, and methods disclosed herein may include or utilize special-purpose or general-purpose computers, including computer hardware such as one or more processors and system memory, as described herein. Implementations within the scope of the present disclosure may also include physical and other computer-readable media for carrying or storing computer-executable instructions and / or data structures. Such computer-readable media may be any available media accessible by a general-purpose or special-purpose computer system. Computer-readable media that store computer-executable instructions are computer storage media (devices). Computer-readable media that carry computer-executable instructions are transmission media. Thus, by way of example and not limitation, implementations of the present disclosure may include at least two distinctly different types of computer-readable media: computer storage media (devices) and transmission media.

[0044] Computer storage media (devices) include RAM, ROM, EEPROM, CD-ROM, solid-state drives (SSDs) (e.g., RAM-based), flash memory, phase-change memory (PCM), other types of memory, other optical disk storage, magnetic disk storage, or other magnetic storage devices, or any other medium that can be used to store desired program code means in the form of computer-executable instructions or data structures and that can be accessed by a general-purpose or special-purpose computer.

[0045] Implementations of the apparatus, systems, and methods disclosed herein can communicate over a computer network. A "network" is defined as one or more data links that enable the transfer of electronic data between computer systems and / or modules and / or other electronic devices. When information is transferred or provided to a computer over a network or another communications connection (either wired, wireless, or a combination of wired or wireless), the computer properly views the connection as a transmission medium. Transmission media can be used to carry desired program code means in the form of computer-executable instructions or data structures and can include networks and / or data links that can be accessed by a general-purpose or special-purpose computer. Combinations of the above should also be included within the scope of computer-readable media.

[0046] Computer-executable instructions include, for example, instructions and data that, when executed by a processor, cause a general-purpose computer, special-purpose computer, or special-purpose processing device to perform a certain function or group of functions. Computer-executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or source code. While the present subject matter has been described in language specific to structural features and / or methodological acts, it should be understood that the present subject matter defined in the appended claims is not necessarily limited to the described features or acts. Rather, the described features and acts are disclosed as example forms of implementing the claims.

[0047] Those skilled in the art will appreciate that the present disclosure may be implemented in networked computing environments having many types of computer system configurations, including vehicle-mounted computers, personal computers, desktop computers, laptop computers, message processors, handheld devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, cell phones, PDAs, tablets, pagers, routers, switches, various storage devices, etc. The present disclosure may also be implemented in distributed system environments where tasks are performed by both local and remote computer systems that are linked through a network (either by wired data links, wireless data links, or a combination of wired and wireless data links). In a distributed system environment, program modules may be located in both local and remote memory storage devices.

[0048] Additionally, where appropriate, the functions described herein may be performed by one or more of hardware, software, firmware, digital components, or analog components. For example, one or more application-specific integrated circuits (ASICs) may be programmed to execute one or more of the systems and procedures described herein. Certain terms are used throughout this specification and claims to refer to particular system components. As will be understood by those skilled in the art, components may be referred to by different names. This specification does not intend to distinguish between components that differ in name but not function.

[0049] It should be noted that the sensor embodiments described above may include computer hardware, software, firmware, or any combination thereof to perform at least a portion of their functionality. For example, the sensor may include computer code configured to run on one or more processors, or may include hardware logic / electrical circuitry controlled by the computer code. These exemplary devices are provided herein for illustrative purposes and are not intended to be limiting. Embodiments of the present disclosure may be implemented in additional types of devices, as known to those skilled in the art.

[0050] At least some embodiments of the present disclosure are directed to computer program products including such logic (e.g., in the form of software) stored on any computer-usable medium that, when executed on one or more data processing devices, causes the devices to operate as described herein.

[0051] While various embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not limitation. It will be apparent to those skilled in the art that various changes in form and detail can be made without departing from the spirit and scope of the present disclosure. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents. The foregoing description has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure to the precise form disclosed. Many modifications and variations are possible in light of the above teachings. Furthermore, it should be noted that any or all of the foregoing alternative implementations may be used in any combination desired to form additional hybrid implementations of the present disclosure.

Claims

1. a cellular communication antenna; a radio unit (RU) connected to the cellular communication antenna; The wireless unit Obtaining status data of the wireless unit; writing a plurality of values ​​of the status data to the file for each of the plurality of lines of the file storing the measurement group and the object unit identifier corresponding to the measurement group, with the measurement group and object unit identifier being assigned to a value from the status data stored in each of the plurality of lines of the file; configured to store at least the file on the wireless unit or transmit the file; A system characterized by:

2. The system of claim 1 , wherein the status data describes one or more components of the wireless unit.

3. 3. The system of claim 2, wherein the one or more components of the wireless unit include at least one of an optical transceiver measurement, a transmit window measurement, a receive window measurement, an energy measurement, a power measurement, an environmental measurement, or a received signal strength indicator (RSSI) measurement.

4. 2. The system of claim 1, wherein the status data includes at least one of a measurement object, an object unit type, and a report information type, and the report information type can be any one of a minimum value, a maximum value, a top value, a last value, or a frequency bin.

5. The system of claim 1 , wherein the wireless unit is configured to write, for each row of the plurality of rows, an object unit type corresponding to the object unit identifier in each row of the plurality of rows.

6. The system of claim 1 , wherein the wireless unit is configured to write, for each row of the plurality of rows, a start time and an end time corresponding to the status data stored in each row of the plurality of rows.

7. The system of claim 1 , wherein the wireless unit is configured to write a report information type label and a report information value for each row of the plurality of rows.

8. The system of claim 1 , wherein the wireless unit is configured to transmit the file to a remote orchestrator over a network connection.

9. The system of claim 1 , wherein the file stores the status data in a comma-separated format.

10. The system of claim 1 , wherein the file has a row and column format.

11. The system of claim 10 , wherein the row and column format has a fixed number of columns, and the wireless unit is configured to write column labels to the file that label the columns of the row and column format.

12. 11. The system of claim 10, wherein the row and column format has a fixed number of columns, and the wireless unit is configured to write null values ​​to locations in the row and column format for which the status data does not contain corresponding information.

13. The system of claim 1 , wherein the plurality of rows of the file have a plurality of different numbers of columns, and each row of the plurality of rows stores one or more attribute-value pairs.

14. obtaining, by a radio unit (RU) connected to a cellular communication antenna, status data of one or more components of said radio unit; writing, by the wireless unit, a plurality of values ​​of the status data to the file for each of a plurality of rows of the file by writing a measurement group and object unit identifier assigned to a value from the status data stored in each of the plurality of rows of the file; and (b) transmitting, by said wireless unit, at least (a) said file on said wireless unit or (b) said file to a remote computer device over a network connection. A method comprising:

15. The method of claim 14 , wherein the plurality of rows has a plurality of different numbers of columns.

16. The method of claim 15 , wherein each row of the plurality of rows stores one or more attribute-value pairs.

17. The method of claim 14 , further comprising writing, by the wireless unit, for each row of the plurality of rows, a measurement object corresponding to the measurement group.

18. 18. The method of claim 17, further comprising, for each line of the plurality of lines, an object unit type corresponding to the object unit identifier stored in each line of the file.

19. When executed by one or more processing devices, the one or more processing devices: obtaining status data for one or more components of a radio unit (RU) connected to a cellular communication antenna; writing a plurality of values ​​of the status data to the file for each of a plurality of lines of the file by writing a measurement group and object unit identifier assigned to a value from the status data stored in each line of the plurality of lines of the file; A non-transitory computer-readable medium storing executable code that causes at least (a) the file to be stored on the wireless unit or (b) the file to be transmitted over a network connection to a remote computing device.

20. When executed by the one or more processing devices, the one or more processing devices further (c) causing the file to be written with a row and column format having a fixed number of columns, and causing column labels to be written to the file that label the columns of the row and column format; or 20. The non-transitory computer-readable medium of claim 19, storing executable code that (d) causes a plurality of rows to be written to a file having a plurality of different numbers of columns, each row storing one or more attribute-value pairs.

Images