Antenna panel split

Abstract

An O-RAN Radio Unit (O-RU) declares to an O-RAN Distributed Unit (O-DU) a set of supported split modes, where each split mode defines how a physical array antenna panel can be divided into individual segments. The O-DU can select a split mode and configure carriers to use specific segments within that mode. When reconfiguring a carrier from a first segment to a second segment, the same set of static-low-level transmission / reception endpoints and the same transmission / reception array can be reused, enabling efficient segment switching without carrier deactivation. The system supports both O-DU controlled and O-RU controlled split mode selection. In O-RU controlled operation, the O-RU autonomously selects segments for carriers and reports the selections to the O-DU. Multiple O-DUs can be connected to a single O-RU, with carriers from different O-DUs configured to use different segments. This approach reduces memory requirements, minimizes traffic interruption during reconfiguration, and enables flexible antenna resource management in O-RAN deployments.

Description

[0001] 23-02-2026

[0002] ANTENNA PANEL SPLIT

[0003] TECHNICAL FIELD

[0004] The present disclosure relates to the field of array antenna management.

[0005] BACKGROUND

[0006] In the current 0-RAN standard specification a physical array antenna panel is represented by [tr]x-array(s) that cover all array elements of the physical antenna panel. [tr]x-array is a generic O-RAN term that covers either a receive array or a transmit array. A [tr]x-array may correspond to all or a part of a physical array antenna panel.

[0007] A [tr]x-array is addressed by static-low-level-[tr]x-endpoints associated with a [tr]x-array-carrier configured to the [tr]x-array. Each [tr]x-array-carrier has its own associated set of static-low-level-[tr]x-endpoints. A static-low-level-[tr]x-endpoint is a managed entity representing a physical radio transmitter / receiver chain. A [tr]x-array-carrier in O-RAN is a logical carrierlevel entity that ties a radio carrier to the static-low-level- [tr]x-endpoints and thus to the physical transmitter / receiver chains. The meaning and use of O-RAN terms are defined in the O-RAN specifications.

[0008] A carrier to be transmitted / received is configured as an O-RAN [tr]x-array-carrier in the O- RU, thus being connected to the part of the physical array antenna that the [tr]x-array corresponds to.

[0009] There currently exist certain challenge(s).

[0010] There may be a desire to configure several different carriers to different parts of a physical array antenna panel. There may also be a desire to be able to change this configuration quickly. There is further a desire to do all of this efficiently.

[0011] iCertain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.

[0012] SUMMARY

[0013] The present disclosure relates to antenna panel split functionality in O-RAN (Open Radio Access Network) systems, enabling efficient management and configuration of physical array antenna panels divided into multiple segments.

[0014] In conventional O-RAN implementations, each possible segment of an antenna panel must be declared as a separate antenna array with its own set of static endpoints, consuming significant memory resources and requiring complex reconfiguration procedures when carriers need to switch between segments. This approach creates operational inefficiencies and can cause unacceptable traffic interruptions during reconfiguration.

[0015] The disclosed approach addresses these limitations by implementing a split mode framework where an O-RAN Radio Unit (O-RU) can declare supported split modes to an O-RAN Distributed Unit (O-DU). Each split mode may define how a physical array antenna panel may be divided into non-overlapping segments that can be individually utilized. Rather than declaring multiple separate arrays for each possible segment, the system can declare arrays corresponding to the entire physical antenna panel and use split mode configurations to control which segments are active for specific earners.

[0016] The system provides flexibility in control mechanisms, supporting both O-DU controlled and O-RU controlled split mode selection. In O-DU controlled operation, the O-DU can select the split mode and specify which segment each carrier should use. In O-RU controlled operation, the O-RU can determine the optimal split mode and segment allocation based on carrier configurations and traffic conditions, then report this information back to the O-DU.

[0017] A key advantage of this approach is that carriers can be reconfigured to use different segments without deactivation or extensive reconfiguration procedures. The same set of static endpoints and transmission / reception arrays can be reused across different segments, significantly reducing memory requirements and enabling faster, more dynamic segment switching with minimal traffic disruption.The split mode functionality enables multiple beneficial use cases, including support for different radio access technologies on the same antenna panel, accommodation of carriers with frequency gaps, increased analog beamforming capacity through spatial separation, and independent operation of multiple O-DUs sharing the same O-RU infrastructure. The system also supports energy-saving features through segment-specific TRX control, allowing independent power management of different antenna segments.

[0018] This approach provides a more efficient and flexible method for managing antenna resources in O-RAN deployments and enables enhanced operational capabilities.

[0019] In a first aspect, then, there is provided a method performed by an O-RAN Radio Unit (O-RU). The method involves declaring to an O-RAN Distributed Unit (O-DU) a set of split modes that the O-RU supports. Each split mode defines how a physical array antenna panel can be divided into individual parts or segments.

[0020] The O-RU may receive from the O-DU a selected split mode. The O-RU can receive information from the O-DU for configuring a carrier, where this information includes an indication of a first segment of the split mode that should be used for the carrier. The O-RU then configures the carrier to use that first segment.

[0021] The O-RU may later receive information from the O-DU for configuring the carrier to use a second segment of the split mode that is different from the first segment. In this case, the O-RU configures the carrier to use the second segment instead of the first. When switching between segments, the same set of static-low-level transmission / reception endpoints that were used for the carrier and the first segment can also be used for the carrier and the second segment. Similarly, the same transmission / reception array used for the carrier and the first segment can also be used for the earner and the second segment.

[0022] The O-RU may declare to the O-DU whether it supports one or both of two control approaches: O-RU controlling the selection of split mode, or O-DU controlling the selection of split mode. An O-RU controller, which may be the O-DU itself, can select whether split mode selection should be controlled by the O-RU or the O-DU.The O-RU may control split mode selection. The O-RU can receive information from an O-DU for configuring a carrier, then select segment to be used for that carrier. The O-RU sends information to the O-DU indicating which segment was selected. This information indicating the selected segment may also indicate one or more properties of that segment.

[0023] The O-RU may be connected to two or more O-DUs, and carriers from different O-DUs can be configured to use different segments.

[0024] In a second aspect, there is provided an O-RU that is adapted to perform the method described in the first aspect.

[0025] In a third aspect, there is provided a computer program comprising instructions which cause an O-RU to perform the method of the first aspect when the program runs on one or more processors of the O-RU.

[0026] In a fourth aspect, there is provided a method performed by an O-DU. The method involves receiving from an O-RU a set of split modes that the O-RU supports, where each split mode defines how a physical array antenna panel can be divided into individual parts or segments. The O-DU may send to the O-RU a selected split mode. The O-DU may also send information to the O-RU for configuring a carrier, where this information includes an indication of a first segment of the split mode that should be used for the carrier, and the carrier is configured to use the first segment.

[0027] The O-DU may later send information to the O-RU for configuring the carrier to use a second segment of the split mode that is different from the first segment, and the carrier is configured to use the second segment instead of the first. The same transmission / rcception array used for the carrier and the first segment can also be used for the carrier and the second segment. In a fifth aspect, there is provided an O-DU that is adapted to perform the method described in the fourth aspect.

[0028] In a sixth aspect, there is provided a computer program comprising instructions which cause an O-DU to perform the method of the fourth aspect when the program runs on one or more processors of the O-DU.In a seventh aspect, there is provided an O-RAN Radio Unit (O-RU) comprising processing circuitry and a memory. The processing circuitry and memory are configured to declare to an O-RAN Distributed Unit (O-DU) a set of split modes that the O-RU supports, where each split mode defines how a physical array antenna panel can be divided into individual parts or segments.

[0029] In an eighth aspect, there is provided a tangible, non-transient computer-readable medium comprising instructions. When these instructions are executed by processing circuitry of an O-RAN Radio Unit (O-RU) connected to an O-RAN Distributed Unit (O-DU) over fronthaul, they cause the processing circuitry to perform operations. These operations include declaring to the O-DU a set of split modes that the O-RU supports, where each split mode defines how a physical array antenna panel can be divided into individual parts or segments.

[0030] In a ninth aspect, there is provided an O-RAN Distributed Unit (O-DU) comprising processing circuitry and a memory. The processing circuitry and memory are configured to receive from an O-RU a set of split modes that the O-RU supports, where each split mode defines how a physical array antenna panel can be divided into individual parts or segments.

[0031] In a tenth aspect, there is provided a tangible, non-transient computer-readable medium comprising instructions. When these instructions are executed by processing circuitry of an O-RAN Distributed Unit (O-DU) connected to an O-RAN Radio Unit (O-RU) over fronthaul, they cause the processing circuitry to perform operations. These operations include receiving from the O-RU a set of split modes that the O-RU supports, where each split mode defines how a physical array antenna panel can be divided into individual parts or segments.

[0032] In an eleventh aspect, there is provided a system comprising an O-RU according to the second aspect connected over fronthaul to an O-DU according to the fifth aspect.

[0033] BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 shows a hierarchy of Radiation Structure according to figure 12.2 1 of ref. [1], Figure 2 shows an example of how O-RU could report possible array panel segments assupported [tr]x-arrays.

[0035] Figure 3 shows an example of possible antenna split mode(s).

[0036] Figure 4 shows an example of O-RU reporting a splitable antenna panel as one supported tx-array.

[0037] Figure 5 shows an example of how O-RU can report supported split-modes and split-mode details.

[0038] Figure 6 shows an example where O-RU does not report supported split-modes or segmentation details.

[0039] Figure 7 shows an example of O-DU controlled array earner configuration

[0040] Figure 8 shows an example of O-RU controlled array carrier configuration.

[0041] Figure 9 shows an example of a shared O-RU using split mode and TRX-control.

[0042] Figure 10 shows an example of a communications system.

[0043] Figure 11 shows another example of a communications system.

[0044] Figure 12 shows a block diagram of a wireless device.

[0045] Figure 13 shows a block diagram of a network node.

[0046] Figure 14 shows a block diagram illustrating a virtualization environment.

[0047] DETAILED DESCRIPTION

[0048] According to the current state of the standard, a set of static-low-level-[tr]x-endpoints must be declared for each declared [tr]x-array, which requires a lot of memory when it is desired to be able to access many different parts of the physical array antenna panel. Changing the configuration of a carrier from one [tr]x-array to another involves deactivating the carrier which may cause an unacceptably long traffic interruption.

[0049] Instead of declaring multiple [tr]x-arrays referring to parts of the same physical array antenna panel, it is proposed to declare [tr]x-array(s) which corresponds to the whole physical array antenna panel and define or declare split modes that define how the physical array antenna panel may be divided into individually usable parts called segments. For a same split mode the segments are non-overlapping. A [tr]x-array-carrier configured to be associated to such [tr]x-array may be configured to use a particular segment. Software associated with the static- low-level-[tr]x-endpoints for the [tr]x-array-carrier controls that signal is transmitted / receivedonly on the array elements of the particular segment of the physical array antenna panel. In this way, less memory is needed for static-low-levcl-[tr]x-endpoints and a change of segment is much quicker than deactivating a carrier and activating it on another [tr]x-array.

[0050] To enable open fronthaul interface to support antenna split, the following can be considered as possible solutions.

[0051] Declare supported [trlx-arrays

[0052] When pardoning a panel array by declaring multiple [tr]x-arrays, the way of partitioning may also be referred to as a split mode and the parts as segments, even though the way of implementing the partitioning may require a lot of memory and can make reconfiguration of carriers slow.

[0053] To enable antenna split using OPEN FH, one alternative is to report each possible segment of any possible split mode as an O-RU antenna array [tr]x-array. New attributes or data structure need to be introduced to indicate which of those reported antenna arrays can be used together.

[0054] Split models)

[0055] Another alternative is to report arrays for full panels (supporting split mode) without reporting arrays for segments, refer to follow chapter about how split mode and possible segment information can be reported.

[0056] Declare supported split mode

[0057] 2.5.2.1 By standardized pre-defined split modes

[0058] Commonly used split modes can be defined in O-RAN M-Plane spec. Those pre-defined split modes can be explained using diagrams. Split mode identifier can be specified using predefined, name, id. O-RU can use those pre-defined split mode names or identifiers to report which split mode an O-RU, or array panel, supports and later to configure or indicate which split mode to be used, or is used.

[0059] By descriptive data structure

[0060] When using separate [tr]x-arrays for segments, supported split modes can be reported by O- RU with split mode name and [tr]x-array names that are part of each split mode; or segmentnames or segment area information of each split mode.

[0061] A [tr]x-array has embedded information about relative position in an array panel, so when a segment is represented by reported [tr]x-array, position information is not needed.

[0062] When segments are not reported as [tr]x-array(s), position information for each segment area needs to be reported. In addition, potential overlaying sub-arrays of each segment also need to be declared. For some implementation, O-RU may report many sub-arrays. Such [taxarrays, each consisting of only one or a limited number of array element(s), are intended to be used for signaling channels requiring special antenna assignments such as SRS or CSI-RS. Those sub-arrays (part of ‘panel’ array or ‘segment’ array) can only belong to some specific segment depending on its location in the array panel.

[0063] If multiple full panel arrays are reported for an antenna panel, for those panel array(s) having relation ‘shared’, they can only be configured using same split mode. For those fullpanel arrays having relation ‘co-located’ and are in same direction (e.g., tx), they may be allowed to be configured to use different split modes. Some additional O-RU capabilities may be needed to indicate how split mode can be configured for ‘co-located’ panel arrays for a specific O-RU implementation.

[0064] Split mode further capacity information

[0065] For each split mode reported using methods defined in 2.5.2.1 and 2.5.2.2, other capabilities, capacities or limitations can be reported related to a specific split mode. Such information can be used by O-DU to consider which split mode to use when O-DU controls the usage of split mode.

[0066] Split mode control methods

[0067] An O-RU can declare its supported split mode control methods. The O-RU can support either O-DU controlled, O-RU controlled, or both.

[0068] Parameters to enable split mode control method can be used by O-RU controller (e.g., O-DU or SMO, Service Management and Orchestration Framework) to determine which split mode control method to be used.

[0069] When O-RU controlled split mode control method is used, O-RU based on carrier configurations decides which split mode an O-RU array panel will use and which segment(antenna array or segment area) an array carrier is allocated by the O-RU.

[0070] Declaring full panel arrays without reporting arrays for segments, and using O-RU controlled split mode control method, array carrier reconfiguration can be avoided when array carrier needs to change segment to be used, traffic disturbance can be minimized.

[0071] Certain embodiments may provide one or more of the following technical advantage(s).

[0072] Support for split mode will enable some vendor products to support multiple technologies using same O-RU array panel, for example both LTE and NR on the same O-RU panel.

[0073] Some of the vendor products, by supporting split mode, can increase the number of supported analog beams and in turn can serve more user layers or more users in different spatial directions.

[0074] Supporting split mode can also enable some carrier configuration with frequency gaps which otherwise cannot be supported by the vendor product.

[0075] Using split mode, the shared O-RU can be possible to use TRX control to save energy when each O-DU can control its own part.

[0076] Adding indication of antenna arrays that can be used as the same time in an antenna panel, will give O-DU insight how they can use the antenna arrays to acheive the configuration goal. O-RU can report supported split modes. For the O-RUs support O-DU controlled split mode control method, operators have the possibility to configure which split mode operators intend to use for an antenna panel. In addition to which antenna array an array carrier is associated with (via static endpoint), operators can also configure which segment the array carrier to be assigned to in case segment is reported only as segment area of a ‘panel’ array and not reported as separate antenna arrays.

[0077] A more O-RU autonomous way of split will enable most efficient way of use of resources.

[0078] Multiple array carriers can be configured associated with the same antenna array, the ‘panel’ array. Static endpoints associated with the ‘panel’ array can be seem as from a resource pool. O-RU based on carrier configurations and traffic situations, will return which split mode the antenna panel uses and also which segment each array carrier is using.Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0079] O-RAN WG4 specifies an Open Fronthaul Interface, including Management-Plane (M-Plane) [1] and Control-, User- and Sync-Plane (CUS-Plane) [2] specifications. In the CUS-Plane specification, the diagram of figure 1 can be found in clause 12.2.

[0080] In O-RAN, relation between antenna arrays (tx-array and / or rx-array) is expressed using expression ‘SHARED’ and ‘COALOCATED’ (misspelled in the model).

[0081] • ‘shared’ means sharing Power Amplifier (PA) and co-locatcd antenna element • ‘co-located’ means co-located antenna element but not shared PA.

[0082] A group of antenna arrays that have relations to each other belong to a same antenna panel. There are no explicit parameters to indicate an antenna panel in the O-RAN Open Fronthaul Interface.

[0083] For each such antenna array relation groups, the tx-array and rx-array which covers all array element in the panel area can be assumed to represent the antenna panel and its capability. Here in this document can be referred as ‘panel’ array.

[0084] In the same group of arrays that are related to each other, there can be multiple ‘panel’ arrays in the same direction (e.g., tx or rx), for example, two tx-arrays can be declared as ‘panel’ arrays, one for each frequency band.

[0085] In this document, an ‘antenna panel’ or an ‘array panel’ refers to a physical antenna panel. A physical antenna panel may in some implementations be composed by several sub-panels.

[0086] When an antenna panel is split, each segment can be either represented as a reported antenna array, or just a segment info. If a reported antenna array covers the same area of a segment, that antenna array can be called ‘segment’ array.

[0087] There are also arrays that are part of bigger array and those are usually called sub-array in O-RAN WG4 specifications.

[0088] In M-Plane clause 20.3.2.3 TRX control configuration, the following is specified:” These two parameters per tx-array and rx-array list entry may be used by the O-RU controller to perform TRX Control. It is problematic if TRX Control commands are issued for sub-arraysof a larger array due to the potential interaction of multiple TRX Control commands affecting the same array elements which are part of multiple [tr]x-arrays. Therefore, the antenna mask configuration shall be done for the largest tx or rx array that is advertised by the O-RU, not for the tx-array or rx-array which is a subset of the largest array (multiple non-overlapping largest arrays are possible)”.

[0089] Due to hardware limitation, sometimes the O-RU integrated antenna panel needs be divided into multiple segments to enable some specific carrier configuration and / or specific traffic model need. When the antenna panel is split, each antenna segment can be used for different purposes.

[0090] For example, when carriers of two different technologies need to be realized using one antenna panel, some vendor may need to split the antenna panel, and each carrier may get its own part of the panel.

[0091] The method can also be used when the carriers configured to use an antenna panel may have frequency gaps, to set up the carrier, the antenna panel needs to be split to accommodate several groups of carriers where each group of carriers utilizes a contiguous frequency range. When an array panel is divided into multiple segments, the number of supported time-domain (e.g. analog) beamforming beams can be increased since each antenna segment can beamform in a different direction. In that way the O-RU can provide service to more UEs that are positioned in different spatial directions simultaneously

[0092] When an O-RU is shared by two O-DUs from different vendors, an antenna panel in the O-RU can be split into two segments, so each O-DU can use its own segment. Antenna split function makes it possible for each O-DU / operator to perform energy saving feature independently. This gives more flexibility and the coordination between O-DUs can be reduced.

[0093] Antenna split functionality is more often used in Massive M1M0 radio which has integrated antenna. The assumption is that a radio can have one or multiple antenna panels.

[0094] Using the current O-RAN open fronthaul interface to support antenna split, one method is to report each possible segments of an array panel for all possible split as a separate antenna array [tr]x-array as defined in O-RAN CUS-plane spec clause 12.2 and respective yang model. But currently there is no way to express which of those reported antenna arrays can be used simultaneously. O-DU needs to have this information since some vendor products may

[0095] llnot support to use the ‘panel’ arrays at the same time as the ‘segment’ arrays, thus interoperability between products from different vendors is hard to achieve.

[0096] Each static endpoint in an O-RU statically refers to a reported antenna array [tr]x-array. Multiple times of static endpoints need to be reported by the O-RU when multiple [tr]x-arrays are used to enable antenna split functionality, consequently more memory is consumed in O-RU and O-DU to store endpoints information.

[0097] As part of carrier configuration, low level endpoints are associated to a [tr]x-array-carrier via low-level-[tr]x-links. A low-level-[tr]x-endpoint refers to a static-low-level-[tr]x-cndpoint which in turn refers to a [tr]x-array. Reconfiguring an O-RU that uses antenna split functionality might require many configuration steps. For example, when a new array earner ‘array-carrier2’ needs to be added or configured to an antenna array in an antenna panel and as a consequence, an existing ‘ array-carrier 1 ’ using the same antenna panel may need to be re-located to use another part / segmentation of antenna panel, ‘array earner 1 ’ needs to be deactivated (set active to INACTIVE) and maybe deleted before it can be created / reconfigured and activated again. Since each segment is reported as an antenna array [tr]x-array with its own set of static-low-lcvcl-[tr]x-cndpoints, a different set of low-level endpoints need to be created and associated to the array carrier. This reconfiguration is not trivial, and the array carrier cannot continue to provide traffic during this reconfiguration This will limit more dynamic change of segment used by a earner when the earner is activated and carrying traffic.

[0098] Energy saving feature “TRX control” is specified in O-RAN M-Plane clause 12.3. The related clauses in CUS-spec are 7.5.2.17, 16.6.1,7.2.9.2.1, 7.92.9.2.2,7.2.9.2.3,7.2.9.2.4 where sub-array and the bigger overlapping array’s relation is mentioned.

[0099] How the “TRX control” can be used when the antenna panel is in split mode is currently not specified. Without antenna split, in case two O-DUs connected to a shared O-RU uses the unsplit ‘panel’ array, the host O-DU needs to coordinate the usage of the antenna array before it can perform TRX-control. Coordination between the two O-DUs is necessary for TRX- control otherwise the host O-DU will not have enough information about how the other O- DU, for example, Shared Resource Operator SRO O-DU, uses the ‘panel’ array. For a shared O-RU, TRX control feature is nearly unfeasible without antenna split function.To enable split mode funetionality, one way is that the O-RU reports each possible segment of antenna as an antenna array [tr]x-array. To make different vendors’ products interoperable, O-RU declares the information about which of those antenna arrays can be used together for an antenna panel.

[0100] O-RU can also report what possible split modes an antenna panel supports. Either possible split mode can be defined in the spec, using predefined split mode names or ids, or more detailed split mode information can be declare using descriptive data structure in YANG model to declare which reported antenna array are part of which split mode.

[0101] There arc drawbacks to report each possible segment of all possible split modes for an antenna panel as antenna array [tr]x-array. When array carrier needs to be located to another array segment, the array carrier needs be totally reconfigured.

[0102] To avoid massive reconfiguration of an array carrier when the array carrier need to be relocated to another antenna segment, the O-RU can report ‘panel’ arrays that covers the antenna panel area and ‘segment’ arrays do not need to be reported. When configuring an array carrier, the ‘panel’ array and its static endpoints can be associated to the array carrier. Antenna panel’s split mode change and carrier’s segment change does not require carrier deactivation and reconfiguration. When antenna panel is used in split mode, only part of the ’panel’ array is used by an array carrier.

[0103] Even if only ‘panel’ arrays are declared and no ‘segment’ arrays are declared, the O-RU still can report which split mode(s) each array panel supports via ‘panel’ array or probably together with segment information for each split mode. To decide which split mode the O-RU is going to use for one array panel can either be O-DU controlled, or O-RU controlled. When O-DU controlled, the O-DU configures which split mode to use for an array panel and which segment to use for an array carrier. When O-RU controlled, the O-RU decides which split mode to be used for an array panel and which segment each array carrier is allocated to. The information of which segment the earner using can be retrieved by the O-DU using read-only parameter or by notification sent from O-RU to O-DU.

[0104] It is also possible that an O-RU does not report any split mode support details and just reports its support of split mode functionality. Then based on array earner configuration, O-RU decides how to split the antenna panel and only information needed by the O-DU will be e.g. retrievable and visualized using read-only parameters, for example information about which segment or segment-id is used by a given array carrier. Notification can be used to inform O-DU if split mode of a panel, or segment used by an array carrier is changed. M-Planc is more suitable for scenario when this change does not happen so frequent. For more dynamic change use case, new C-Plane message can be introduccd / uscd to inform O-DU about the split mode and segment usage change.

[0105] For some scenario, the O-RU may just report a segment-id without position information of array segment. In such case, it is important for the O-DU to understand which array carriers that are allocated using the same antenna segment (having same segment id). Those array carriers may share some predefined characteristic and resource limitations, for example, beamforming gain and analog beamforming capacity. O-DU can consider which array earners are using the same segment when scheduling the traffic or making configurations. For an antenna panel that is used in split, TRX control can be performed on segments of a specific split mode in use. Split-mode in use is either configured by O-DU or decided by O-RU. Antenna mask that can be applied on a segment only need to cover antenna elements that belongs to the segment. If there is ‘segment’ array, antenna mask can be applied on ‘segment’ array. If there is no reported ‘segment’ array, antenna mask can be applied to the array elements in the segment area.

[0106] As explained, one way to split an antenna panel is that an O-RU reports each possible segment of a split antenna panel as an antenna array. Further, the O-RU declares the information about which of those antenna arrays can be used together.

[0107] Figure 2 shows an example of how O-RU could report possible array panel segments as supported [tr]x-arrays.

[0108] The simplest way is that the O-RU reports possible allowed combinations of reported antenna arrays for each antenna panel.

[0109] O-RU reports possible allowed combination of reported tx-arrays

[0110] Example of O-RU declared arrays that can be used simultaneously for an antenna panel.

[0111] • antenna panel 1. [tx-al], [tx-a2, tx-a3], [tx a4, tx-a5], [tx-a6, tx-a7, tx-a8, tx-a9]

[0112] • antenna panel 1 : [rx-al], [rx-a2, rx-a3], [rx a4, rx-a5], [rx-a6, rx-a7, rx-a8, rx-a9]

[0113] • antenna panel 2 : [tx-bl], [tx-b2, tx-b3], [tx b4, tx-b5], [tx-b6, tx-b7, tx-b8, tx-b9]

[0114] • antenna panel 2 : [rx-bl], [rx-b2, rx-b3], [rx b4, rx-b5], [rx-b6, rx-b7, rx-b8, rx-b9] For each antenna panel, simultanous allowed tx-arrays and simultnaous allowed rx-arrays arc reported seperately.

[0115] For the same antenna panel, one combination of tx-arrays can be used together with one combination of rx-arrays.

[0116] When O-DU configures array carriers using static endpoints referring to tx-arrays, associated tx-arrays or rx-arrays should be one of the are allowed combination.

[0117] O-RU will reject the configuration that does not follow declared array combination limitations.

[0118] The O-RU can also declare split modes it supports. The reporting of supported split modes can use simple data structure, such as enumeration, list of integers or list of defined strings. In case identifier of those split modes, either names and / or ids, are defined in the O-RAN specification or other documentation, it can be understood by both O-RU and O-DU.

[0119] Figure 3 shows an example of possible antenna split mode(s).

[0120] Beside which split mode can be supported, the position of reported array in each split mode can also be reported, data structure as follows is one example.

[0121] O-RU reports supported split-modes and split-mode details

[0122] O-RU reports supported split-modes and split mode details, for example, antenna array used in each segment in a split-mode and other information related to split-mode or segment in the split-mode.

[0123] Each reported supported antenna array has information about number of columns, rowsand left bottom array element position.

[0124] Example of supported split-modes for a panel:

[0125] sp-mO

[0126] • antenna arrays: tx-al

[0127] sp-ml

[0128] • antenna arrays: tx-a2, tx-a3

[0129] sp-m3

[0130] antenna arrays: tx-a4, tx-a5

[0131] sp-m4

[0132] antenna arrays: tx-a6, tx-a7, tx-a8, tx-a9

[0133] If O-RU reports supported splits modes and tx-arrays related to each split mode:

[0134] • O-DU can configure which split mode an antenna panel can use.

[0135] • O-DU can configure an array carrier using static endpoints referring to tx-arrays that are allowed for that split mode.

[0136] To avoid reconfiguration of array carrier, O-RU can report ‘panel’ arrays without ‘segment’ arrays. When configuring array carrier, the ‘panel’ array and its static endpoints can be used. Split mode and segment usage change does not require carrier deactivation and extensive reconfiguration. When operating in split mode, only part of ‘panel’ array is used by an array earner.

[0137] Figure 4 shows an example of O-RU reporting a splitable antenna panel as one supported tx- array.

[0138] Even if only ‘panel’ arrays are declared and no ‘segment’ arrays are declared, the O-RU still can report which split mode(s) each array panel supports via ‘panel’ array or probably together with segment information for each split mode. To decide which split mode the O-RU is going to use for one array panel can either be O-DU controlled, or O-RU controlled. When O-DU controlled, the O-DU configures which split mode to use for an array panel and which segment to use for an array carrier. When O-RU controlled, the O-RU decides which split mode to be used for an array panel and which segment each array carrier is allocated to. The information of which segment the carrier using can be retrieved by the O-DU using read-only parameter or by notification sent from O-RU to O-DU.Split-mode control summarized:

[0139] • O-DU-controlled

[0140] • O-DU configures which split-mode to be used on an antenna panel

[0141] • O-DU configures which segment in a split-mode to be used by an array carrier. • O-RU-controlled

[0142] • O-RU based on carrier configuration returns which split-mode the O-RIU uses and / or which segment area or segmentation id is used for each array carrier.

[0143] Figure 5 shows an example of how O-RU can report supported split-modes and split-mode details.

[0144] It is also possible that an O-RU does not report any split mode support details and just reports its support of split mode functionality. Then based on array carrier configuration, O-RU decides how to split the antenna panel and only information needed by the O-DU will be retrievable and visualized using read-only parameters, for example information about which segment or segment-id is used by a given array carrier. Notification can be used to inform O-DU if split mode of a panel, or segment used by an array carrier is changed. M-Plane is more suitable for scenario when this change docs not happen so frequent, e.g., on a timescale of minutes or hours. For more dynamic change use case, new C-Plane message can be introduced / used to inform O-DU about the split mode and segment usage change.

[0145] Figure 6 shows an example where O-RU does not report supported split-modes or segmentation details.

[0146] For some scenario, the O-RU may just report a segment-id without position information of array segment. In such case, it is important for the O-DU to understand which array carriers that are allocated using the same antenna segment (having same segment id). Those array carriers may share some predefined characteristic and resource limitations, for example, beamforming gain and analog beamforming capacity. O-DU can consider which array carriers are using the same segment when scheduling the traffic or making configurations.

[0147] Figure 7 shows an example of O-DU controlled array carrier configurationFigure 8 shows an example of O-RU controlled array carrier configuration.

[0148] When O-RU controlled split is enabled and an array carrier is re-located to a new segment, some of the sub-arrays that are associated to the array carrier may become outside the area of the new segment and become irrelevant. If those sub-arrays are RX arrays, the O-RU may stop using those sub-arrays to receive signal for this re-located array carrier. Endpoints referring to those sub-arrays that are not part of the new segment will not send traffic to the re-located array carrier. New parameters for example, admin-state and opcr-state can be added to low-level endpoint to visualize the state of the low-level endpoint. When carrier is re-located, those endpoints referring to sub-arrays that become outside the new segment area of the carrier will have disabled as oper-state value.

[0149] For an antenna panel that is used in split, TRX control feature can be performed on segments of a specific split mode in use. Especially when two O-DUs share an O-RU, and each uses half of the panel. Antenna mask that can be applied on a segment only need to cover antenna elements that belongs to the segment. If there is ‘segment’ array, antenna mask can be applied on ‘segment’ array. If there is no reported ‘segment’ array, antenna mask can be applied to the array elements in the segment area.

[0150] Figure 9 shows an example of a shared O-RU using split mode and TRX-control.

[0151] Possible impacts to technical specifications

[0152] Parameter to indicate array panel maybe is needed and can be specified in O-RAN M-Plane spec.

[0153] M-Plane specification needs to add possible allowed array combinations when using antenna split mode for each antenna panel. M-Plane also needs to add supported and enabled split mode control methods, O-DU controlled and / or O-RU controlled, or both.

[0154] To enable O-DU controlled split mode, O-RU needs to report either split-modes O-RU supports with antenna arrays used in each split mode or antenna segments and segment information of each split mode. Split-mode identifier can be specified in M-Plane spec with pre-defined name and id, so those split-mode identifier can be used by all vendors. Another approach is to declare supported split-modes using more descriptive data structure wheresplit-mode name can be given by vendor freely. O-DU can understand how the antenna panel is split by O-RU reported information. For example, how many segments are used in a splitmode for an antenna panel, where a segment start and how many columns and rows a segment covers. Data structure need to be defined in M-Plane Yang model.

[0155] By reporting antenna aiTays covering the antenna panel(s), also called ‘panel’ array without reporting possible ‘segment’ as antenna array, using O-RU controlled split mode control method, the reconfiguration of array carrier is avoided when an array carrier needs to use a new segment. In this way more dynamic antenna split feature can be supported.

[0156] Optional YANG feature for split mode also needs to be specified.

[0157] For O-RU controlled split mode control method, notification(s) for split mode change for an array panel and segment change for an array carrier need to be specified.

[0158] The shared O-RU chapter needs to be modified with TRX control should be performed on segment used by array earner. Either on ‘segment’ array or segment area of a split mode How to configure the mask for TRX control maybe need to be further clarified.

[0159] When O-RU only report segment id an array carrier using, for O-RUs that all array carriers using the same segment need to coordinate for analog beamforming, further clarification is needed in M-Plane or CUS-Plane specification.

[0160] Endpoint may need to add new parameter admin-state and oper-state to cover the case when some of sub-arrays used by an array carrier can become outside the new segmentation due to array carrier segment change.

[0161] Figure 10 shows an example of a communication system 1000 in accordance with some embodiments.

[0162] In the example, the communication system 1000 includes a telecommunications network 1002 that includes an access network 1004, such as a radio access network (RAN), and a core network 1006, which includes one or more core network nodes 1008. The access network 1004 includes one or more access network nodes or base stations of various types, access network nodes 1010A and 1010B are depicted (which may be collectively referred to as network nodes 1010), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non- 3GPP access points (APs). Some embodiments of the access network 1004 may include more than one access network technology. The network nodes 1010 of access network 1004 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs),such as by connecting UEs 1012A, 1012B, 1012C, and 1012D (one or more of which may be generally referred to as UEs 1012) to the core network 1006 over one or more wireless connections.

[0163] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 1002 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 1002 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 1002, including one or more access network nodes 1010 and / or core network nodes 1008.

[0164] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-rcal time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A 1 , F 1 , W 1 , E 1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.

[0165] The network nodes 1010 facilitate direct or indirect connection of one or more UEs 1012 to the core network 1006 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1000 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systemsthat may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1000 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0166] The UEs 1012 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 1010 and other communication devices. Similarly, the network nodes 1008, 1010 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 1002) with the UEs 1012 and / or with other network nodes or equipment in the telecommunications network 1002 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 1002. More specifically, UEs 1012 may send messages, data, and / or other signals to network nodes 1008, 1010 or other elements of the telecommunications network 1002 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 1008, 1010 may send messages, data, and other signals to UEs 10122, other network nodes 1008, 1010, and other devices in telecommunications network 1002 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 1012 by transmitting the message to an access network node 1010 that will then transmit the message to the intended UE 1012. Similarly, a core network node 108 may receive a particular message from a UE 1012 by receiving the message from an access network node 1010 that itself received the message from the UE 1012.

[0167] In the depicted example, the core network 1006 connects elements of the access network 1004 (e.g., one or more of the network nodes 1010) to one or more host computing systems, such as host 1016. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1006 includes one or more core network nodes (e.g., core network node 1008) of various types, one or more of which may be generally referred to as network nodes 1008. Network nodes 1008 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1008. Example core network nodesprovide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (S1DF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0168] The host 1016 may be under the ownership or control of a service provider other than an operator or provider of the access network 1004 and / or the telecommunications network 1002. The host 1016 may be operated by the service provider or on behalf of the service provider. The host 1016 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0169] As a whole, the communication system 1000 of Figure 10 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 1000 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 1000 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 1000 supporting different standards, protocols, or rule sets.

[0170] As one example, in certain embodiments, access network 1004 may contain some access network nodes 1010 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 1010 support (or the same access network nodes 1010 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As anotherexample, telecommunications network 1002 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations. Telecommunications network 1002 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 1002. For example, the telecommunications network 1002 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0171] In some examples, one or more of the UEs 1012 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1004 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1004. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.c. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0172] In the example, the hub 1014 communicates with the access network 1004 to facilitate indirect communication between one or more UEs (e.g., UE 1012C and / or 1012D) and network nodes (e.g., network node 1010B). In some examples, the hub 1014 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1014 may be a broadband router enabling access to the core network 1006 for the UEs. As another example, the hub 1014 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1010, or by executable code, script, process, or other instructions in the hub 1014.

[0173] As another example, the hub 1014 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1014 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1014 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node,which the hub 1014 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 1014 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs arc low energy loT devices.

[0174] The hub 1014 may have a constant / persistent or intermittent connection to the network node 101 OB. The hub 1014 may also allow for a different communication scheme and / or schedule between the hub 1014 and UEs (e.g., UE 1012C and / or 1012D), and between the hub 1014 and the core network 1006. In other examples, the hub 1014 is connected to the core network 1006 and / or one or more UEs via a wired connection. Moreover, the hub 1014 may be configured to connect to an M2M service provider over the access network 1004 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1010 while still connected via the hub 1014 via a wired or wireless connection. In some embodiments, the hub 1014 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1010B. In other embodiments, the hub 1014 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1010B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0175] Figure 11 is another example of a communication system 1100 according to some embodiments. As used herein, the communication system 1100 includes multiple access points (APs) 1110 (with four exemplary APs 1110A, 1110B, 1110C, and 1110D being depicted) and multiple wireless devices, referred to in the context of communication system 1100 as stations (ST As) 1112 (referred to individually as STA 1112A, STA 1112B, STA 1112C, STA 1112D, and STA 1112E). STA 1112A is served by AP 1110A in a first basic service set (BSS) 1120A. STA 1110B and STA 1110C are served by AP 1110B in a second BSS, BSS 1120B. STA 1112D is served by AP 1110C in a third BSS, BSS 1120C. STA 1112E is served by AP 1110D in a fourth BSS, BSS 1120D. Stations 1112 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 1112 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like. Each of STAs 1112 may connect through a radio link to one of APs 1110. For example, depending on location or channel conditions experienced by a given STA 1112, the STA mayselect an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) earners from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0176] Each AP 1110 may provide data connectivity to STAs 1112 connected to a particular AP 1110. As illustrated, APs 1110 may be connected to a data network 1130. In this way, APs 1110 may also provide data connectivity between STAs 1112 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 1112 and its serving AP 1110 may be used for providing various kinds of services to STA 1112, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 1112 and / or on a device linked to STA 1112. By way of example, Figure 11 illustrates an application service platform 1132 provided in data network 1130. The application(s) executed on STA 1112 and / or on one or more other devices linked to STA 1112 may use the radio link for data communication with one or more other STA 1112 and / or the application service platform 1132, thereby enabling utilization of the corresponding service(s) at STA 1112. Figure 12 shows a wireless device 1200, which may be configured to operate in communication system 1000 of Figure 10 or in communication system 1100 of Figure 110. The wireless device 1200 may be alternatively referred to as a UE 1200, like a UE 1012 within the context of communication system 1000, or as a station (STA) 1200 or as a non-access-point station (non-AP STA) 1200, like a STA 1112 within the context of the communication system 1100, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptopmounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.A wireless device 1200 may support dcvicc-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructurc (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 1200 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 1200 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 1200 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0177] In particular embodiments, wireless device 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input / output interface 1206, a power source 1208, a memory 1210, a communication interface 1212, and / or any other component, or any combination thereof. Certain embodiments of wireless device 1200 may include all or a subset of the components shown in Figure 12. The level of integration between the components may vary from one embodiment of wireless device 1200 to another. In general, in a particular embodiment of wireless device 1200, processing circuitry 1202, input / output interface 1206, power source 1208, memory 1210, and communication interface 1212 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 1200. Further, certain embodiments of wireless devices 1200 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0178] The processing circuitry 1202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1210. The processing circuitry 1202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1202 may include multiple central processing units (CPUs). In the example, the input / output interface 1206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, amonitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 1200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0179] In some embodiments, the power source 1208 is structured as a battery or battery pack. Other- types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 1 08 may further include power circuitry for delivering power from the power source 1208 itself, and / or an external power source, to the various parts of wireless device 1200 via input circuitry or an interface such as an electrical power cable. Power source 1208 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 1200 to which power is supplied.

[0180] The memory 1210 may be or be configured to include memory such as random access memoiy (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1210 includes one or more programs 1214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1216. The memory 1210 may store, for use by wireless device 1200, any of a variety of various operating systems or combinations of operating systems.

[0181] The memory 1210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM),synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1210 may allow wireless device 1200 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1210, which may be or comprise a device-readable storage medium.

[0182] The processing circuitry 1202 may be configured to communicate with an access network or other network via or using the communication interface 1212. The communication interface 1212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1222. The communication interface 1212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 1218 and / or a receiver 1220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1218 and receiver 1220 may be coupled to one or more antennas (e.g., antenna 1222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0183] In the illustrated embodiment, communication functions of the communication interface 1212 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.Ln particular embodiments, wireless device 1200 may provide an output of data captured via a sensor, through its communication interface 1212, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 1200 can be communicated through a wireless connection to a network node via another wireless device 1200. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0184] As another example, wireless device 1200 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 1200 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0185] Wireless device 1 00, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 1200 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 1200 shown in Figure 12.

[0186] As yet another specific example, in an loT scenario, wireless device 1200 may represent a machine or other device that performs monitoring and / or measurements, and transmits theresults of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 1200 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 1200 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 1200 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0187] In practice, any number of wireless devices 1200 may be used together with respect to a single use case. For example, a first wireless device 1200 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 1200 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 1200 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 1200 can also include more than one of the functionalities described above. For example, wireless device 1200 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0188] Figure 13 shows a network node 1300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 1300 may be configured to operate in communication system 1000 of Figure 10, like network nodes 1008 or 1010, or in communication system 1100 of Figure 11, like an AP 1110 or a station 1112. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0189] Network nodes 1300 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 1300 may be a relay node or a relay donor node controlling a relay. Network nodes 1300 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0190] Other examples of network nodes 1300 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0191] In particular embodiments, network node 1 00 includes a processing circuitry 1302, a memory 1304, a communication interface 1306, and a power source 1308. In general, in a particular embodiment of network node 1300, processing circuitry 1302, memory 1304, communication interface 1306, and power source 1308 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 1300. The network node 1300 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 1300 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 1304 or portions of memoiy 1304 for different RATs) and some components may be reused (e.g., a same antenna 1310 may be shared by different RATs). The network node 1300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1300, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1300.

[0192] The processing circuitry 1302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, applicationspecific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable toprovide, either alone or in conjunction with other components, such as the memory 1304, to provide network node 1300 functionality.

[0193] In some embodiments, the processing circuitry 1302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1302 includes one or more of radio frequency (RF) transceiver circuitry 1312 and baseband processing circuitry 1314. In some embodiments, the RF transceiver circuitry 1312 and the baseband processing circuitry 1314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1312 and baseband processing circuitry 1314 may be on the same chip or set of chips, boards, or units.

[0194] The memory 1304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1302. The memory 1304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1302 and utilized by the network node 1300. The memory 1304 may be used to store any calculations made by the processing circuitry 1302 and / or any data received via the communication interface 1306. In some embodiments, the processing circuitry 1302 and memory 1304 is integrated.

[0195] The communication interface 1306 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 1306 comprises port(s) / tcrminal(s) 1316 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 1200 may be capable of wireless communication and communication interface 1306 may also include radio front-end circuitry 1318 that may be coupled to, or in certain embodiments a part of, an antenna 1310. Particular embodiments of radio front-end circuitry 1318 include filter(s) 1320 and amplifier(s) 1322. The radio front-end circuitry 1318 may be connected to an antenna 1310 and processing circuitry 1302. The radio front-end circuitry may be configured to condition signals communicated between antenna 1310 and processing circuitry 1302. The radio front-end circuitry 1318 may receive digital datathat is to be sent out to other network nodes or UEs via a wireless connection. The radio frontend circuitry 1318 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 1320 and / or amplifiers 1322. The radio signal(s) may then be transmitted via the antenna 1310. Similarly, when receiving data, the antenna 1310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1318. The digital data may be passed to the processing circuitry 1 02. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0196] In certain alternative embodiments, network node 1300 may be capable of wireless communication but does not include separate radio front-end circuitry 1318, instead, the processing circuitry 1302 includes radio fi'ont-end circuitry and is connected to the antenna 1310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1312 is part of the communication interface 1306. In still other embodiments, the communication interface 1306 includes one or more ports or terminals 1316, the radio front-end circuitry 1318, and the RF transceiver circuitry 1312, as part of a radio unit (not shown), and the communication interface 1306 communicates with the baseband processing circuitry 1314, which is part of a digital unit (not shown).

[0197] The antenna 1310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1310 may be coupled to the radio front-end circuitry 1318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1310 is separate from the network node 1300 and connectable to the network node 1300 through one or more interfaces or ports. The antenna 1310, communication interface 1306, and / or the processing circuitry 1302 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 1300. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1310, the communication interface 1306, and / or the processing circuitry 1302 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 1300. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment. The power source 1308 provides power to the various components of network node 1300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1300 with power forperforming the functionality described herein. For example, the network node 1300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1308. As a further example, the power source 1308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0198] Embodiments of the network node 1300 may include additional components beyond those shown in Figure 13 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1300 may include user interface equipment to allow input of information into the network node 1300 and to allow output of information from the network node 1300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1300.

[0199] Figure 14 is a block diagram illustrating a virtualization environment 1400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1400 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0200] Applications 1402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.Hardware 1404 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 1408A and VM 1408B (which may be collectively referred to as VMs 1408), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1406 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 1408.

[0201] The VMs 1408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 1406. Different embodiments of the instance of a virtual appliance 1402 may be implemented on one or more of VMs 1408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0202] In the context of NFV, each of the VMs 1408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1408, and that part of hardware 1404 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 1408 on top of the hardware 1404 and corresponds to an application 1402.

[0203] Hardware 1404 may be implemented in a standalone network node with generic or specific components. Hardware 1404 may implement some functions via virtualization. Alternatively, hardware 1404 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1410, which, among others, oversees lifecycle management of applications 1402. In some embodiments, hardware 1404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In someembodiments, some signaling can be provided with the use of a control system 1412 which may alternatively be used for communication between hardware nodes and radio units.

[0204] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0205] Tn certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.NUMBERED EMBODIMENTS

[0206] la. A method performed by an O-RAN O-DU eomprising the step of associating a carrier with a segment of a panel array.

[0207] lb. A method performed by an O-RAN O-RU comprising the step of

[0208] declaring, to an O-RAN O-DU, a set of split modes that the O-RU supports, a split mode defining a division of a physical array antenna panel into individual parts, segments.

[0209] 2. A method according to numbered embodiment lb, the method comprising the step of receiving from the O-DU a selected split mode.

[0210] 3. A method according to numbered embodiment 2, comprising the steps of receiving from the O-DU information for configuring a carrier, wherein the information comprises an indication of a first segment of the split mode that is to be used for the carrier and configuring the carrier to use the first segment.

[0211] 4. A method according to numbered embodiment 3, comprising the steps of receiving from the O-DU information for configuring the carrier to use a second segment of the split mode, different from the first, and configuring the carrier to use the second segment instead of the first.

[0212] 4a. A method according to numbered embodiment 4 wherein a set of static-low-level-[tr]x- endpoints used for the carrier and the first segment are used also for the carrier and the second segment.

[0213] 4b. A method according to any of numbered embodiments 3 or 4a wherein a [tr]x-array used for the carrier and the first segment is also used for the earner and the second segment.

[0214] 4c. A method according to any preceding numbered embodiment or not according to any other embodiment wherein an O-RAN [tr]x-array is associated with a panel array, and by way of configuration the [tr]x-array can use a selected segment out of a plurality of selectable segments of the panel array for a carrier associated with the [tr]x-array.5. A method performed by an O-RAN O-RU comprising the step of declaring to an O-RAN O-DU of the O-RU supports one or both of O-RU controlling the selection of split mode or O-DU controlling the selection of split mode.

[0215] 6. A method according to numbered embodiment 5 wherein an O-RAN O-RU controller, which may be the O-DU, selects whether split mode selection should be controlled by the O-RU or the O-DU.

[0216] 7. A method performed by an O-RAN O-RU comprising the steps of

[0217] receiving from an O-RAN O-DU information for configuring a earner,

[0218] selecting, by the O-RU, a segment to be used for the carrier and

[0219] sending to the O-DU information indicating the selected segment.

[0220] 8. A method according to numbered embodiment 7 wherein the information indicating the selected segment also indicates one or more properties of the segment.

[0221] 9. A method according to numbered embodiment 8 wherein the indicated properties are one or more of bcamforming gain and analogue beamforming properties.

[0222] 10. A method according to any preceding numbered embodiment wherein the O-RU is connected to two or more O-DUs and carriers from different O-DUs are configured to different segments.

[0223] 11. A method according to any preceding numbered embodiment comprising the steps of receiving from the O-DU an O-RAN TRX control command for a [tr]x-array-carrier and applying the command to a segment that the [tr]x-array-carrier is configured for.

[0224] 12. A method according to a combination of any of the preceding numbered embodiments.

[0225] 13. An O-RAN O-RU adapted to perform the method of any of the preceding numbered embodiments.

[0226] 14. A computer program comprising instructions which cause an O-RAN O-RU to perform the method of any of the numbered embodiments la- 12 when it is run on one or moreprocessors of the O-RU.

[0227] 15. An O-RAN O-DU adapted to send the information received by an O-RU from an O-DU and / or adapted to receive the information that is sent from an O-RU to an O-DU in any of the numbered embodiments la- 12.

[0228] 16. A method comprising the step of declaring, by an O-RAN O-DU a plurality of [tr]x-arrays, each representing a subset of the array elements of a same panel antenna.

[0229] 17. A method according to claim 17 wherein at least some of the [tr]x-arrays represent a strict subset of the array elements of the panel antenna

[0230] 17. A method according to numbered embodiment 16 further comprising the step of declaring which [tr]x-arrays that can be used simultaneously by different carriers.

[0231] 18. A method performed in an O-RAN O-RU wherein a same set of O-RAN static-low-level-[tr]x-endpoints associated with an O-RAN [tr]x-array-carrier is used to access different parts of a physical array antenna panel.

[0232] REFERENCES

[0233] 1. 0-RAN.WG4.TS.MP.0-R004-vl7.00

[0234] 2. O-RAN.WG4.TS.CUS.0-R004-vl 7.00

Claims

23-02-2026CLAIMS1. A method performed by an O-RAN Radio Unit, O-RU, comprising the step of declaring, to an O-RAN Distributed Unit, O-DU, a set of split modes that the O-RU supports, a split mode defining a division of a physical array antenna panel into individual parts, segments.

2. A method according to claim 1, the method comprising the step of receiving from the O-DU a selected split mode.

3. A method according to claim 2, comprising the steps of receiving from the O-DU information for configuring a carrier, wherein the information comprises an indication of a first segment of the split mode that is to be used for the carrier and configuring the carrier to use the first segment.

4. A method according to claim 3, comprising the steps of receiving from the O-DU information for configuring the carrier to use a second segment of the split mode, different from the first, and configuring the carrier to use the second segment instead of the first.

5. A method according to claim 4 wherein a set of static-low-level-[tr]x-endpoints used for the carrier and the first segment are used also for the carrier and the second segment.

6. A method according to claim 5 wherein a [tr]x-array used for the carrier and the first segment is also used for the carrier and the second segment.

7. A method according to any preceding claim, further comprising the step of declaring to an O-DU if the O-RU supports one or both of O-RU controlling the selection of split mode or O-DU controlling the selection of split mode.

8. A method according to claim 7 wherein an O-RU controller, which may be the O-DU, selects whether split mode selection should be controlled by the O-RU or the O-DU.

9. A method according to claim 1, 7 or 8, further comprising the steps ofreceiving from an O-DU information for configuring a carrier,23-02-2026selecting, by the O-RU, a segment to be used for the earner andsending to the 0-DU information indicating the selected segment.

10. A method according to claim 9 wherein the information indicating the selected segment also indicates one or more properties of the segment.

11. A method according to any preceding claim wherein the O-RU is connected to two or more O-DUs and carriers from different O-DUs are configured to different segments.

12. An O-RU adapted to perform the method of any of the preceding claims.

13. A computer program comprising instructions which cause an O-RU to perform the method of any preceding claim when it is run on one or more processors of the O-RU.

14. A method performed by an O-DU the method comprising:receiving from an O-RU a set of split modes that the O-RU supports, a split mode defining a division of a physical array antenna panel into individual parts, segments.

15. A method according to claim 14, the method further comprising sending to the O-RU a selected split mode.

16. A method according to claim 15, the method further comprising sending to the O-RU information for configuring a carrier, wherein the information comprises an indication of a first segment of the split mode that is to be used for the carrier and configuring the carrier to use the first segment.

17. A method according to claim 16, the method further comprising sending to the O-RU information for configuring the earner to use a second segment of the split mode, different from the first, and configuring the carrier to use the second segment instead of the first.

18. A method according to claim 17 wherein a [tr]x-array used for the carrier and the first segment is also used for the carrier and the second segment.

19. An O-DU adapted to perform the method of any of the claims 14-18.23-02-202620. A computer program comprising instructions which cause an O-DU to perform the method of any of the claims 14-18 when it is run on one or more processors of the O-DU.

1. An O-RAN Radio Unit, O-RU comprising processing circuitry and a memory configured to declare, to an O-RAN Distributed Unit, O-DU, a set of split modes that the O-RU supports, a split mode defining a division of a physical array antenna panel into individual parts, segments.

22. A tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry of an O-RAN Radio Unit, O-RU connected to an O-RAN Distributed Unit, O-DU over fronthaul, cause the processing circuitry to perform operations comprising declaring, to an O-RAN Distributed Unit, O-DU, a set of split modes that the 0-RU supports, a split mode defining a division of a physical array antenna panel into individual parts, segments.

23. An O-RAN Distributed Unit, O-DU comprising processing circuitry and a memory configured to receive from an O-RU a set of split modes that the O-RU supports, a split mode defining a division of a physical array antenna panel into individual parts, segments.

24. A tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry of an O-RAN Radio Unit, O-RU connected to an O-RAN Distributed Unit, O-DU over fronthaul, cause the processing circuitry to perform operations comprising receiving from an O-RU a set of split modes that the O-RU supports, a split mode defining a division of a physical array antenna panel into individual parts, segments.

25. A system comprising an O-RU according to claim 12 connected over fronthaul to an O- DU according to claim 19.

Images