System and methods relating to topology from heterogeneous sources

Abstract

Methods, and apparatus are disclosed. According to some embodiments, a Topology Exposure & Inventory (TE&IV) node (4) is provided. The TE&IV node (4) is configured to consolidate (S100) capabilities of each of a plurality of adaptors (6). Each adaptor (6) is for mediating network information comprising representations for one or network entities in the communication network, and / or representations of relationships between network entities in the communication network. The method further comprises receiving (S102) network information from the plurality of adaptors; and performing (S104) at least one action based on the consolidated capabilities and the received network information.

Description

[0001] SYSTEM AND METHODS RELATING TO TOPOLOGY FROM HETEROGENEOUS SOURCES

[0002] FIELD

[0003] The present disclosure relates to management of wireless communication systems, and in particular, to topology information from heterogeneous sources.

[0004] BACKGROUND

[0005] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes and between UEs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0006] Service Management and Orchestration (SMO) is the function responsible for the management and orchestration of the managed elements under its control. Within the Open-Radio Access Network (O-RAN or ORAN) Alliance architectural framework, the SMO terminates the 01, 02 and Al interfaces (in the non-Real-time Radio Access Network (RAN) Intelligent Controller (RIC)). It also encapsulates the R1 interface between the non-Real-Time RIC and the rApps.

[0007] The R1 interface operates towards multi-vendor rApps. R1 interfaces are designed to support portability of multi-vendor rApps and provide value-added services to rApp developers and solution providers. The R1 interface enables Open Application Programming Interfaces (APIs) to be integrated in the SMO framework.

[0008] Topology Exposure & Inventory (TE&IV) is a software realization of an R1 interface. It persists certain things and the relationships between them, exposing a single network level model that enables rApps to traverse domains across different vendors. TE&IV Documentation and Confluence / Wiki have been discussed in the O-RAN community.

[0009] The following is found in the O-RAN “Topology Exposure & Inventory Overview” (https: / / docs.o-ran-sc.org / projects / o-ran-sc-smo-teiv / en / latest / index.html):Introducing topology and inventory data

[0010] Topology and inventory data is the information that represents the entities in a telecommunications network and the relationships between them. Topology and inventory data can be derived from inventory and configuration. Topology & Inventory is being updated autonomously based on changes in the network.

[0011] Topology & Inventory supports several topology and inventory domains, ... . The understanding of the model is important to enable a user making queries on topology and inventory data. The entities are modelled as managed objects (under the schema in a data dictionary) and are grouped together in modules based on functionality. ...

[0012] Concepts

[0013] The building blocks of the Topology & Inventory are domains, entities, and the relationships between each other. From a graph perspective, entities are the vertices and relationships are the edges. These two components are part of a subgraph, or the so-called domain. A relationship can be a cross-domain relationship when its entities belong to different domains.

[0014] Domain

[0015] A domain is a grouping of topology and inventory entities that handles topology and inventory data. The topology and inventory model defines what the telecoms network entities and relationships are. ... The Topology Exposure and Inventory Management (TEIV) domain is the parent domain used for entities and relationships. This domain can be used in reading and querying topology and inventory data when the domain name of an entity or relationship is not known.

[0016] Entity

[0017] Entities are enabling the modelling and storage of complex network infrastructure and relationships. ...

[0018] RelationshipIt is a bi-directional connection between two entities, one of which is the originating side (A-side) and the other is the terminating side (B-side). The order of the sides matters since it defines the relationship itself which must be unique. A relationship between two entities is based on the effect that one has on the other. An entity can have one or multiple relationships which can be defined by the user. A possible relationship between ManagedElement and ODUFunction can be MANAGEDELEMENT MANAGES ODUFUNCTION.

[0019] SUMMARY

[0020] Topology information is built from consuming data from heterogeneous sources with heterogeneous behavior. These competing data sources are associated with different time frames, formats, and order of discovery from the discovery adaptors. In wireless communication systems, a discovery adapter (or just ‘adaptor’ herein) is provided to mediate two (or more) representations of the same or equivalent concepts in the system, potentially exposed by different protocols, transports and languages. Adaptors can also be referred to as ‘mediation’, ‘plug-ins’ and / or ‘Extract, Transform, Load’ (‘ETL’).

[0021] In 0-RAN, SMO adaptors form part of TE&IV, as TE&IV has an autonomous responsibility to discover topology from multiple sources, some of which are defined by SMO: e.g. Radio Access Network (RAN) Network Function (NF) Operations, Administration and Maintenance (0AM), Federated O-Cloud Management and Orchestration (FOCOM), Network Function Orchestrator (NFO), and others which are not, e.g. external inventory systems.

[0022] As the sources are defined separately, they have the potential (and in general are) heterogeneous in terms of transport, model language and protocol. The adaptors provide a homogeneous interface to the heterogeneous sources. In addition, the 0-RAN standards specifications for the sources are incomplete without vendor extensions. The vendor extensions often include raw ‘topology data’ required to construct the standard-defined ‘topology’.

[0023] Information from the data sources may be overlapping and competing, where competing data sources can provide information for the same entity. For example, geographical information is typically not stored in the network for security and / or other reasons. Most customers have an inventory system which tracks assets, including theirlocation, and the inventory system tends to be the trusted source of geographical data. The configuration of the asset in a location is considered trusted in the device itself. Thus, a topology entity encapsulating both configuration and location can be constructed from ‘topology data’ from two different sources, with physical information (such as geographical location of an antenna) being provided by an inventory and planning system, and logical information (such as antenna configuration) being provided by the RAN via Element Management System (EMS). In another example, a Communication Service Provider (CSP) may have decided to store geographical information in the network (or EMS). In this case the trusted source will be the same as configuration, however somebody must inform the system which source is trusted.

[0024] The topology and inventory model describes constraints (e.g. cardinality). When multiple sources are combined without coordination, ordering or transactions, the topology may be inconsistent with the topology and inventory model and also with the reality in the trusted sources. Thus, the variation of data sources and / or overlapping / competing of data sources may disadvantageously result in an inconsistent network view, in terms of relationships to other entities. For example, a model may only allow for three relationships of a type, but collecting the data out of order could temporarily result in there being four relationships. In another example, a data update from a less-trusted source may result in a change after the adaptor of the trusted source has been notified / finished / synchronised with the correct value. In another example, a topology instance may have five attributes, where one adaptor sets three of them, while another adaptor sets the remaining two. If one adaptor has finished its task, the instance will be partially consistent, and the instance remains inconsistent until both adapters have set all five attributes.

[0025] Some embodiments advantageously provide methods, systems, and apparatuses related to consolidating topology information from heterogeneous sources and achieve a consistent network view.

[0026] One or more embodiments described herein can relate to one or more of:

[0027] applying an ‘eventual consistency’ approach to the problem space and adding meta-data to inform users of the status of the data on which they depend; rule checking and validation framework; and

[0028] meta-data based on constraints in schema.‘Eventual consistency’ is a term used in relation to distributed system architectures (storage and software). The distributed system architectures discussed in this disclosure have sources that are both heterogeneous and distributed. A goal is to avoid forcing distributed transactional behaviour on all participants in the ‘system’, and have a ‘goodenough’ representation at any point in time. Thus embodiments of this disclosure relate to the provision and publication of a ‘consistency state’ (which is used interchangeably with “reliability indicator” herein), to enhance the decision making of consumers of the topology and inventory. This can result in less waste, and more reliable outcomes.

[0029] One or more embodiments relate to independent processes for adapting the source of truth to topology & inventory entities and relationships.

[0030] One or more embodiments relate to publication of the capability of the adaptor, where the capability relate to what entities and relationships the adaptor produces, and in what timeframe.

[0031] One or more embodiments relate to a method and system to coordinate and override the capability when adaptors are combined.

[0032] One or more embodiments relate to a method and system to publish (make available) the consolidated capabilities - consumers can determine if they have sufficient information (entities and relationships) updated with a latency suitable to their use cases.

[0033] One or more embodiments relate to a method and system to publish the consistency state (‘reliability indicator”) of modelled entities and relationships, which enables consumers to make an on-the-fly decision on whether to proceed based on the reported consistency.

[0034] According to a first aspect, there is provided a method implemented in a Topology Exposure & Inventory (TE&IV) node for a communication network. The method comprises: consolidating capabilities of each of a plurality of adaptors, wherein each adaptor is for mediating network information comprising representations for one or network entities in the communication network, and / or representations of relationships between network entities in the communication network; receiving network information from the plurality of adaptors; and performing at least one action based on the consolidated capabilities and the received network information.

[0035] According to a second aspect, there is provided a method implemented in an adaptor in a communication network. The adaptor is for mediating network information comprising representations for one or network entities in the communication network, and / or representations of relationships between network entities in the communicationnetwork. The method comprising: communicating capabilities for the adaptor to a Topology Exposure & Inventory (TE&IV) node in the communication network, wherein the TE&IV node consolidates capabilities of a plurality of adaptors; and transmitting network information to the TE&IV node for use by the TE&IV node in determining topology-based information.

[0036] According to a third aspect, there is provided a Topology Exposure & Inventory (TE&IV) node for use in a communication network, wherein the TE&IV node is configured to perform the method according to the first aspect or any embodiment thereof.

[0037] According to a fourth aspect, there is provided an adaptor for use in a communication network. The adaptor is for mediating network information comprising representations for one or network entities in the communication network, and / or representations of relationships between network entities in the communication network. The adaptor is configured to perform the method of according to the second aspect or any embodiment thereof.

[0038] According to a fifth aspect, there is provided a computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method according to the first aspect, the second aspect, or any embodiment thereof.

[0039] BRIEF DESCRIPTION OF THE DRAWINGS

[0040] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0041] FIG. l is a schematic diagram of an example network architecture illustrating a communication system according to principles disclosed herein;

[0042] FIG. 2 is a schematic diagram of another example network architecture illustrating a communication system according to principles disclosed herein;

[0043] FIG. 3 is a block diagram of a node and adaptors according to some embodiments of the present disclosure;

[0044] FIG. 4 is a schematic diagram of another example network architecture illustrating a communication system according to principles disclosed herein;FIG. 5 is a flowchart of an example process in a node according to some embodiments of the present disclosure; and

[0045] FIG. 6 is a flowchart of an example process in an adaptor according to some embodiments of the present disclosure;

[0046] FIG. 7 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized;

[0047] FIG. 8 is a diagram of example context and components according to some embodiments of the present disclosure; and

[0048] FIG. 9 is a diagram of example topology relationships according to some embodiments of the present disclosure.

[0049] DETAILED DESCRIPTION

[0050] As described above, an existing issue is how to consolidate Topology Data in TE&IV to achieve consistency of the network view. The topology data is raw data from heterogeneous data sources relating to entities in a network (e.g. a configuration and inventory of entities), and the relationships between the entities. The topology data is used to construct a topology of the network. One or more embodiments described herein address this issue, at least in part.

[0051] A network entity is a device or a part of a device. Exemplary devices include a Distributed Unit (0-DU, or “ODUFunction”), a Radio Unit (ORU), an antenna, a Centralised Unit-Control Plane function (“CUCPFunction”), and a Centralised Unit-User Plane function (“CUUPFunction”). Devices are represented in topology as entities and relationships. Adaptors are used to mediate the two representations. In the network the representations are, in general, siloed and focused on configuration. In topology, the silos are combined and the focus moves to context and determination of scope.

[0052] Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to topology information from heterogeneous sources. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0053] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity orelement without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0054] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0055] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0056] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0057] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a corenetwork node (e.g. mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g. 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.

[0058] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein can be any type of user equipment capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

[0059] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi -cell / multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0060] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR) and / or 6G, may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. It is contemplated that other 3GPP systems may make use of the concepts and arrangements disclosed herein. For example, a disclosure relating to NR may also be implementable in a 6G system and / or an LTE system, a disclosure relating to 6G may also be implementable in a NR and / or LTE system, and a disclosure relating to LTE may also be implementable in a NR and / or 6G system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and / or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0061] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0062] Some embodiments are directed to obtaining topology information from heterogeneous sources.

[0063] Referring to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 1 a schematic diagram of a communication system 2, according to, for example, 3 GPP -type cellular network that may support standards such as LTE and / or NR (5G) and / or 6G. Communication system 2 includes node 4 that is in communication with one or more adaptors 6a-6n (collectively referred to as adaptors 6). Node 4 may be, for example, a Topology Exposure & Inventory (TE&IV) node or another RAN node or core node that implements or performs TE&IV functions in addition to other RAN or core functions. References herein to “TE&IV node” relate to both a standalone TE&IV node, and a node in the RAN or core that implements or performs TE&IV functions. TE&IV Node 4 includes management unit 7 that is configured to perform one or more node 4 functions as described herein.

[0064] As noted above, an adaptor 6 mediates two (or more) representations of the same or equivalent concepts in the system, potentially exposed by different protocols, transports and languages. In 0-RAN, SMO adaptors form part of TE&IV, as TE&IV has an autonomous responsibility to discover topology from multiple sources, some of which are defined by SMO: e.g. RAN NF 0AM, FOCOM, NFO, and others which are not, e.g. external inventory systems. Thus, an adaptor 6 provides abstraction and multi-vendor integration of data models, which feeds “Topology data” into TE&IV repositories retrieved from heterogeneous sources.

[0065] In some embodiments, adaptors 6 may be stacked. For example, the ultimate source of truth for RAN configuration topology data is the 0AM repository in the device(e.g. an ODUFunction). It can be mediated three times before topology is extracted and persisted in the TE&IV node 4, for example by a network management system, a RAN Intelligent Controller (RIC) (or RAN NF 0AM CM), and a RAN Topology Adaptor (RTA). The network management system mediation is transactional, and its native data language is not suitable for an intelligent controller. The intelligent controller consumes the network management system output, but its mediation is not transactional (for read), and its structure is not suitable for topology. The RTA mediation consumes the mediation output of the intelligent controller, and transforms the ‘topology data’ into ‘topology’.

[0066] The adaptors 6 are typically decoupled and independent from each other, meaning that the adaptors 6 are not aware of each other, and operate in parallel performing mediation according to their configured logic. As described further below, the TE&IV node 4 performs a consolidation process to coordinate the outputs of the adaptors 6.

[0067] As an example, Adaptor(s) 6 may be Service Management and Orchestration (SMO) entities. As shown in Fig. 1, Adaptor(s) 6 may include an information unit 8 that is configured to perform one or more adaptor 6 functions described herein.

[0068] FIG. 2 a schematic diagram of another example communication system 10, according to an embodiment, such as a 3 GPP -type cellular network that may support standards such as LTE and / or NR (5G) and / or 6G, which comprises an access network 12, such as a radio access network, and a core network 14. For example, TE&IV node 4 and / or adaptor 6 may be embedded / deployed / included in communication system 10. The core network 14 includes one or more core nodes 15 (or core network nodes 15). In one or more embodiments, core network 14 is or includes TE&IV node 4 that is in communication with one or more adaptors 6a-6n. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipments 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.

[0069] As one example, in certain embodiments, access network 12 may contain some access network nodes 16 that support 3 GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 16 support (or the same access network nodes 16 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, communication system 10 may support multiple generations of related communication standards (e.g. 4G, 5G and 6G 3GPP communication standards) and, as a result, may include an access network 12 and / or a core network 14 that supports multiple different standard generations or may include multiple access networks 12 and / or multiple core networks 14 with individual networks supporting different standards generations.

[0070] Also, it is contemplated that a UE 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 can be in communication with an eNB for LTE / E-UTRAN, a gNB for NR / NG-RAN (i.e. 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) and / or Wi-Fi.

[0071] Example implementations, in accordance with an embodiment, of the TE&IV node 4 and adaptor(s) 6 discussed in the preceding paragraphs will now be described with reference to FIG. 3.

[0072] The communication system 2 includes a TE&IV node 4 provided in a communication system 2 and including hardware 28 enabling it to communicate with the adaptor 6. The hardware 28 may include a communication interface 29 for enabling communication with adaptor 6. In some embodiments, communication interface 29 is configured for setting up and maintaining a wired connection with adaptor 6.

[0073] In the embodiment shown, the hardware 28 of the TE&IV node 4 further includes processing circuitry 36. The processing circuitry 36 may include a processor 38 and a memory 40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 36 may comprise integrated circuitry for processing and / or control, e.g. one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 38 may be configuredto access (e.g. write to and / or read from) the memory 40, which may comprise any kind of volatile and / or non-volatile memory, e.g. cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0074] Thus, the TE&IV node 4 further has software 42 stored internally in, for example, memory 40, or stored in external memory (e.g. database, storage array, network storage device, etc.) accessible by the TE&IV node 4 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g. by TE&IV node 4. Processor 38 corresponds to one or more processors 38 for performing TE&IV node 4 functions described herein. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or processing circuitry 36, causes the processor 38 and / or processing circuitry 36 to perform the processes described herein with respect to TE&IV node 4. For example, processing circuitry 36 of the TE&IV node 4 may include management unit 7 that is configured to perform one or more TE&IV node 4 functions described herein.

[0075] TE&IV Node 4 can include one or more components described above with respect to TE&IV node 4, e.g. communication interface 29, ports, processing circuitry 36, processor 38, memory 40 and software 42. These elements of TE&IV node 4 can be arranged such that TE&IV node 4 can perform various functions.

[0076] The communication system 10 further includes the adaptor 6 already referred to. The adaptor 6 may have hardware 44 that may include a communication interface 46 configured to communicate with TE&IV node 4 and / or other entities in communication system 2.

[0077] The hardware 44 of the adaptor 6 further includes processing circuitry 50. The processing circuitry 50 may include a processor 52 and memory 54. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 50 may comprise integrated circuitry for processing and / or control, e.g. one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 52 may be configured to access (e.g. write to and / or readfrom) memory 54, which may comprise any kind of volatile and / or non-volatile memory, e.g. cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0078] Thus, the adaptor 6 may further comprise software 56, which is stored in, for example, memory 54 at the adaptor 6, or stored in external memory (e.g. database, storage array, network storage device, etc.) accessible by the adaptor 6. The software 56 may be executable by the processing circuitry 50.

[0079] The processing circuitry 50 may be configured to control any of the methods and / or processes described herein with respect to the adaptor 6, and / or to cause such methods, and / or processes to be performed, e.g. by adaptor 6. The processor 52 corresponds to one or more processors 52 for performing adaptor 6 functions described herein. The adaptor 6 includes memory 54 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 56 may include instructions that, when executed by the processor 52 and / or processing circuitry 50, causes the processor 52 and / or processing circuitry 50 to perform the processes described herein with respect to adaptor 6. For example, the processing circuitry 50 of the adaptor 6 may include information unit 8 that is configured to perform one or more adaptor 6 functions as described herein.

[0080] In some embodiments, the components of the adaptor 6 and / or TE&IV node 4 may be as shown in FIG. 3 and independently, the surrounding network topology may be that of FIG. 2.

[0081] Although FIGS. 1 and 3 show various “units” such as management unit 7 and information unit 8 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0082] FIG. 4 is another example of a communication system 10 according to some embodiments. As used herein, the communication system 10 of FIG. 4 includes multiple access points (APs) 60 (with four example APs 60a, 60b, 60c, and 60d being depicted) and multiple wireless devices, referred to in the context of communication system 10 of FIG. 4 as stations (STAs) 62 (referred to individually as STA 62a, STA 62b, STA 62c, STA 62d, and STA 62e). STA 62a is served by AP 60a in a first basic service set (BSS) 64a. STA 60b and STA 60c are served by AP 60b in a second BSS, BSS 64b. STA 62d is served byAP 60c in a third BSS, BSS 64c. STA 62e is served by AP 60d in a fourth BSS, BSS 64d. Stations 62 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, including UEs 22 that are shown and described with respect to FIG. 2. In other words, in some embodiment, STA 62 is a UE 22. Further, stations 62 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0083] Each of STAs 62 may connect through a radio link to one of APs 60. For example, depending on location or channel conditions experienced by a given STA 62, the STA may select 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) carriers 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.

[0084] Each AP 60 may provide data connectivity to STAs 62 connected to a particular AP 60. As illustrated, APs 60 may be connected to a data network 66. In this way, APs 60 may also provide data connectivity between STAs 62 and other entities, e.g. to one or more servers, service providers, data sources, data sinks, user terminals, or the like.

[0085] Accordingly, the radio link established between a given STA 62 and its serving AP 60 may be used for providing various kinds of services to STA 62, e.g. a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 62 and / or on a device linked to STA 62. By way of example, FIG. 4 illustrates an application service platform 68 provided in data network 66. The application(s) executed on STA 62 and / or on one or more other devices linked to STA 62 may use the radio link for data communication with one or more other STA 62 and / or the application service platform 68, thereby enabling utilization of the corresponding service(s) at STA 62. In one or more embodiments, node 4 may be implemented in, for example, application service platform 68 or in data network 66.

[0086] FIG. 5 is a flowchart of an example process in a TE&IV node 4 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of TE&IV node 4 such as by one or more of processing circuitry 36 (including the management unit 7), processor 38, and / or communicationinterface 29. TE&IV Node 4 is configured to consolidate (Block SI 00) capabilities of each of a plurality of adaptors 6, as described herein.

[0087] TE&IV Node 4 is configured to receive (Block S102) network information (i.e. information about the entities) from the plurality of adaptors 6, as described herein.

[0088] TE&IV Node 4 is configured to perform (Block SI 04) at least one action based on the consolidated capabilities and the received network information, as described herein.

[0089] As described above, each adaptor 6 can mediate one or more data sources for one or more topology entities (or relationships). Each combination of source and entity / relationship is a capability. That is, an adaptor 6 is capable of populating entity X from source Y. Thus, a capability can comprise one or more of: attributes, an indication of network entities, and an indication of relationships among the network entities.

[0090] An “attribute” may refer to capability metadata and / or a topology entity / relationship attribute. For capability metadata, examples can include topology entity / relationship and the attributes of same populated / maintained by that adaptor, the sources for the topology entity / relationship, the normal frequency of updates, and / or the limits of update frequency. For a topology entity / relationship attribute, examples can be geographical data, names, identifiers, and / or key selection criteria (key to consumers setting context, or navigating).

[0091] Consolidation in step SI 00 comprises the TE&IV node 4 collating all adaptor capabilities (from all adaptors 6) and annotating an internal record of the definition of each topology entity / relationship to indicate they may be populated, and from where. This information is then exposed to consumers so they can understand if their requirements (on topology) will be satisfied.

[0092] In order to consolidate the capabilities in step SI 00, the TE&IV node 4 needs to receive capabilities from the adaptors 6. Therefore, according to one or more embodiments, the TE&IV node 4 is further configured to determine capabilities of each of the plurality of adaptors 6. To exchange the capability information, a model that defines a capability can be published and / or agreed between the TE&IV node 4 and the adaptors 6. The model may be intemal / private, external / public, or defined in a specification.

[0093] Options for receiving the capabilities from the adaptors 6 (or ‘capability exchange’ between the adaptors 6 and the TE&IV node 4) can include:

[0094] • On deployment, an adaptor 6 can register a manifest that details the adaptor capabilities in a location (e.g. a repository) known to the TE&IV node 4. The TE&IV node 4 can obtain this manifest during the consolidation process in step SI 00.• On deployment, the adaptor 6 registers directly with the consolidation process performed by the TE&IV node 4 and provides its list of capabilities via an interface.

[0095] • The TE&IV node 4 can interrogate adaptors 6 during the consolidation process in step SI 00 (when the adaptor(s) 6 are first encountered) to establish and record their capabilities.

[0096] According to one or more embodiments, an action that can be performed by the TE&IV node 4 in step 104 is determining a reliability indicator for a plurality of network entities. That is, a reliability indicator can indicate a reliability of a representation of the entity in TE&IV, for example indicating whether and / or what inconsistency exists in a representation for a network entity and / or in a representation of relationships between network entities. The reliability indicator (or “consistency state” herein) can be a state value with one of a predefined set of possible values. Some examples of possible values for a reliability indicator are shown in Table 1 below. In particular, an exemplary set of values for the reliability indicator / consistency state can include any of: ADVISED, DEVIATED, PARTIAL, NOT IN SYNC, RESTORED, OK, and NOT POPULATED.

[0097] Other actions that can be performed by the TE&IV node 4 in step SI 04 can comprise one or more of the following: annotating a model with capability metadata; publishing the annotated model to consumers; and applying priority policy / configuration where capabilities have overlap. Where an adaptor 6 also provides criteria for reliability, the TE&IV node 4 can apply these criteria to entity and relationship instances during the runtime of the TE&IV node 4.

[0098] In particular embodiments, the at least one action may be determining topologybased characteristics among a plurality of network entities. Topology-based characteristics are a type of metadata that indicates, for example, normal operation frequency of updates; limits beyond which the entity may be considered unreliable; update frequency (e.g. near real-time; on demand; scheduled; weekly; ...); etc.

[0099] The at least one action may also or alternatively be reporting topology-based information, where the topology-based information comprises one or more of states of the plurality of network entities and relationships among the plurality of network entities. The metadata included in the adaptor ‘registration’, consolidated by the TE&IV node 4 in step SI 00 (using a priority set by the user, if applicable) is used to annotate instances of topology entities and relationships with a reliability indicator in the runtime of the TE&IV node 4. As the network changes, the adaptor(s) 6 mediate this network information towards the TE&IV node 4, and updates are made by the TE&IV node 4 to configurationand inventory relevant to the topology. The consolidated capabilities from step SI 00 inform the TE&IV node 4 how to calculate the reliability indicator metadata for individual instances of topology entities and relationships.

[0100] According to one or more embodiments, the TE&IV node 4 is further configured to report metadata that indicates a reliability of topology-based information. That is, the TE&IV node 4 can use the registered capabilities together with data that is mediated (by one or more adaptors 6) to determine the consistency state / reliability indicator. The TE&IV node 4 may also use non-adaptor data, e.g. the data has just been restored from backup, and indicate the reliability indicator as RESTORED.

[0101] FIG. 6 is a flowchart of an example process in an adaptor 6 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of adaptor 6 such as by one or more of processing circuitry 50 (including the information unit 8), processor 52, and / or communication interface 46. Adaptor 6 is configured to communicate (Block SI 06) capability information for consolidation of capabilities of a plurality of adaptors by a TE&IV node 4, as described herein. The capability information can be as described above with respect to FIG. 5.

[0102] Also as described above with reference to Fig. 5, to exchange the capability information according to Step SI 06, a model that defines a capability can be published and / or agreed between the TE&IV node 4 and the adaptors 6. The model may be internal / private, external / public, or defined in a specification.

[0103] Options for communicating the capabilities from the adaptors 6 (or ‘capability exchange’ between the adaptors 6 and the TE&IV node 4) in step SI 06 can include:

[0104] • On deployment, an adaptor 6 can register a manifest in a location (e.g. a repository) known to the TE&IV node 4. The TE&IV node 4 can obtain this manifest during the consolidation process in step SI 00.

[0105] • On deployment, the adaptor 6 registers directly with the consolidation process performed by the TE&IV node 4 and provides its list of capabilities via an interface.

[0106] • The TE&IV node 4 can interrogate adaptors 6 during the consolidation process in step SI 00 (when the adaptor(s) 6 are first encountered) to establish and record their capabilities

[0107] Adaptor 6 is configured to transmit (Block SI 08) network information to the TE&IV node 4 for determining topology -based information, as described herein.The TE&IV node 4 described herein is developed in line with SMO architecture. It will comply with the cardinality of SMO Service (SMOS) and SMO Function (SMOF) as and when they are defined as per the Decoupled SMO Architecture work item in O-RAN. One or more embodiments described herein may form part of the TE&IV specification in O-RAN SMO that is being developed by, for example, O-RAN Alliance Working Group 10 (WG10).

[0108] For example, in some embodiments, the telecommunication system 10 includes one or more Open-RAN (ORAN or O-RAN) network nodes 16. An ORAN network node 16 is a node in the telecommunication system 10 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 nodes to implement one or more functionalities of any node in the telecommunication system 10, including one or more network nodes 16 in the access network 12 and / or core nodes (e.g. TE&IV node 4).

[0109] Examples of an ORAN network node 16 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-real time control application (e.g. rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access 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. The network nodes 16 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 22a, 22b, 22c, and 22d (one or more of which may be generally referred to as UEs 22) to the core network 14 over one or more wireless connections.

[0110] FIG. 7 is a block diagram illustrating a virtualization environment 94 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 94 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the 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 94 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0111] Applications 96 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 94 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0112] Hardware 98 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.

[0113] Software may be executed by the processing circuitry to instantiate one or more virtualization layers 100 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 102a and 102b (one or more of which may be generally referred to as VMs 102), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 100 may present a virtual operating platform that appears like networking hardware to the VMs 102.

[0114] The VMs 102 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 100. Different embodiments of the instance of a virtual appliance 96 may be implemented on one or more of VMs 102, and the implementations may be made in different ways.

[0115] Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment typesonto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0116] In the context of NFV, a VM 102 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 102, and that part of hardware 98 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 VMs 102 on top of the hardware 98 and corresponds to the application 96.

[0117] Hardware 98 may be implemented in a standalone network node with generic or specific components. Hardware 98 may implement some functions via virtualization. Alternatively, hardware 98 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 104, which, among others, oversees lifecycle management of applications 96. In some embodiments, hardware 98 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 some embodiments, some signaling can be provided with the use of a control system 106 which may alternatively be used for communication between hardware nodes and radio units.

[0118] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements related to generating topology information from heterogeneous sources.

[0119] One or more TE&IV node 4 functions described below may be performed by one or more of processing circuitry 36, processor 38, management unit 7, communication interface 29, etc. One or more adaptor 6 functions described below may be performed by one or more of processing circuitry 50, information unit 8, processor 52, communication interface 46, etc.

[0120] Table 1 below shows inconsistencies that can arise in an ‘eventually consistent’ system, specifically a topology (or TEIV). The table provides a short description of the inconsistency, a description that explains the rationale for the inconsistency, and the valuethat will be assigned to the reliability indicator when that condition (inconsistency) is met / detected, in (or subsequent to) step SI 04.

[0121] Table 1

[0122] Inconsistency Description Visibility

[0123] Entity exists but is not Entities may be created Reliability indicator: connected to an adaptor implicitly when a ADVISED relationship is created

[0124] before an entity is

[0125] associated

[0126] Entities exist but model An example of this would Reliability indicator: relationship between them be the creation of 2 entities DEVIATED

[0127] is not yet discovered by one or more adapters,

[0128] and the model relationship

[0129] between them is not yet

[0130] created.

[0131] Some of the attributes in An example of this would Reliability indicator: the entity or relationship be the creation of a sixth DEVIATED

[0132] do not comply with the relation where the model

[0133] constraints in the model indicates that a maximum

[0134] of five relations are

[0135] allowed. This is likely to

[0136] be transient and a

[0137] corresponding delete is

[0138] pending.

[0139] The model element An rApp or consumer may The content of the model (attribute, entity or depend on a proprietary is available to query at relationship) is not model but the model runtime

[0140] deployed doesn’t exist. Reliability indicator: — The model element No adaptor is attached that The content of the model (attribute, entity or has the capability to is available to query at relationship) is not populate the needed runtime and includes populated attribute, entity or information about the relationship population of the data.

[0141] Reliability indicator: OK The model element (entity An example of this would Reliability indicator: or relationship) is partially be the creation of an entity PARTIAL populated by an adapter and the

[0142] populating of a subset of

[0143] the attributes by the

[0144] adapter.

[0145] The software on which the Some software or network Reliability indicator: adaptor depends reports a issue has caused a NOT IN SYNC sync issue disconnect with the

[0146] ultimate source of truth

[0147] The connected adaptor has The adaptor has failed, or Reliability indicator: not made any updates in a the underlying software NOT IN SYNC period specified by the stack has failed and not

[0148]

[0149] adaptor as normal reportedInconsistency Description Visibility

[0150] The DB has been restored Connection to the source- Reliability indicator: from a backup of-truth is being RESTORED reestablished, and an audit

[0151] is ongoing

[0152]

[0153] With reference to Table 1, the “Reliability indicator: is “Not applicable” but the ” could remain as such in Table 1, e.g. ” may indicate and / or correspond to “Not applicable.”

[0154] FIG. 8 is a diagram of example context and components according to some embodiments of the present disclosure. Each adaptor 6 publishes its capabilities to populate the type of data (attributes, entities and relationships) in the TE&IV node 4. TE&IV node 4 may consume the capabilities of the adaptor 6 on registration. A second process (“priority and conflict process” in FIG. 8) can be performed that sets relative priorities of adaptors 6 with overlapping capabilities, and that also consumes the adaptor 6 capabilities and produces a policy with optional input from the customer. The input from the customer may be, e.g. ‘GeoData from source X is more trusted than the same data from source Y’. ‘GeoData from source X’ is a capability provided by an adaptor 6, ‘more trusted than’ is an optional input. In the event that GeoData is mediated by both adaptors 6, the data from source X will be used to update the topology entity.

[0155] The policy is consumed by the TE&IV node 4 and is used to realize the customer preferences for eventual consistency. This allows the customer to steer the eventually consistent system to reflect how the customer has organized their information systems (sources). The techniques described herein provide a customer with a means to understand the nature of the inconsistency (in the context of their own information systems) enabling better outcomes for topology consumer algorithms.

[0156] The TE&IV node 4 can provide an API for static information about the models deployed, and the population status. Static information is data that does not change during a deployment of the model. The model is provided to TE&IV node 4, and it generates a semantically equivalent model for the purposes of persisting and reading / querying data. TE&IV node 4 also adds metadata (such as a reliability indicator) to the models, to add value. Once the model is deployed, the operations (e.g. consolidating capabilities, prioritising capabilities, accepting mediated data, setting a reliability indicator of the data) can be performed.A population status can indicate whether certain data will be populated. In particular, as models and capabilities are deployed independently, it is possible that there is no source (adaptor) for a given entity, relationship or attribute. In such cases, TE&IV node 4 can indicate via the static information that such data will not be populated. A consumer that relies on this data will then query and understand that it is not able to provide its value, and may enter an error state (unsatisfied requirements).

[0157] The TE&IV node 4 can provide a runtime API for information about the reliability of individual entities, relationships and attributes. This API forms an implicit part of the read and query APIs.

[0158] The TEIV specifications provide mechanisms to control coupling of model fragments, and to help understand the coupling that consumers have on those fragments. This helps with the following:

[0159] • System administrators can identify which consumers will need to be updated and which will not.

[0160] • Model fragments are allowed to be added later to an existing system without endangering existing consumer compatibility.

[0161] FIG. 9 is an example of Source(s) of Inconsistency, and illustrates the above mechanisms. The start point (or baseline) is the bold-bordered boxes. The addition of the relationship MANAGEDELEMENT MANAGES ENODEBFUNCTION, updates the consolidated model without impacting on the base information model, or existing consumers.

[0162] The inconsistency here is subtle. By adding a mandatory (from a consolidate model perspective) after the system is deployed (e.g. upgrade), instances of ManagedElement and ENodeBFunction can now become inconsistent with Reliability Indicator: PARTIAL (indicating missing data, in this case the reciprocal references).

[0163] Further, in FIG. 9:

[0164] • Topology Entity Classes (TEC) exist already (as indicated in FIG. 9 by italicized text).

[0165] • New Topology Relationship Class (TRC) is added (as indicated in FIG. 9 by bold text) - associations made mandatory on the Topology Entity Classes - Relationship must exist.

[0166] • This impacts the initial Topology Entity Classes.• Adding this relationship class / model (at a later stage in the discovery process) made the Topology Entity Classes inconsistent with the data it supports (attributes, relationships).

[0167] One or more embodiments described herein may be cloud native such that all components may be distributed in a cloud-based network.

[0168] Hence, one or more embodiments described herein provides one or more of the following advantages:

[0169] A low complexity-decoupled implementation of adaptors 6 both in time and organization. To be useful, topology and inventory may have to combine data from multiple sources. Some of these will be supported natively by product, others by necessity will require services to deliver adaptations post product delivery (Time To Customer -TTC). Still others will be customer specific proprietary models that relate existing and new entities in what was not envisaged by the product. Having no coupling between adaptors 6 that interact with (sometimes overlapping) sources of truth (i.e. the system or component that holds raw data that may be mediated and used in the construction of TEC / TRC) allows for this flexibility.

[0170] -A powerful and flexible mechanism to consolidate output of multiple adaptors 6. The challenge of the flexibility enabled by the decoupling and independent adaptors is the high potential for contention and race / compete conditions. That is, two adaptors may have the same capability, and as they operate independently they may (without prioritization) compete (race) to update the same data. If their algorithms (or sources) are different the values they try to set will be different. The actual value in TE&IV node 4 will be non-deterministic. As described herein, one or more embodiments provides at least one solution. The published capabilities of each adaptor 6 are combined, and potential overlaps detected, enabling behavior (such as priority) to be specified for each potential conflict at any level: entity; relationship; attribute.

[0171] Clear publication of data needed to satisfy needs. While declaring dependencies may be known, it is reserved for run-time dependencies, and not on secondary dependencies such as: (1) Does the model need to be deployed; (2) Is the model being populated; (3) Is the data population in line with the characteristics needed for an effective use case execution. One or more embodiments described herein captures the dependencies at this level.

[0172] -Clear publication of the consistency of data at any point in time. In the present case there is an inherent chaos of heterogeneous data sources and adaptor behaviors. Any consumerof such data should be aware of the reliability of that data at any given time, and it is desirable to design the consumer with this awareness. One or more embodiments described herein provide access to reliable meta-data that can be incorporated into the design and used in the runtime seamlessly for those use cases that are sensitive to the quality of the data, e.g. update frequency; last update, etc.

[0173] Rule checking and validation framework. Embodiments provide a logical function to apply pre-defined rules based on schema constraints to discovered data. This can apply relevant “Reliability / Visibility” states to class definitions and / or individual attributes.

[0174] Meta-data based on constraints in schema. Embodiments provide a logical function to expose “Reliability / Visibility” states and Topology specific metadata to TE&IV Service Consumers.

[0175] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module”. Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0176] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means forimplementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0177] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0178] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0179] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0180] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the “C” programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0181] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be undulyrepetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0182] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings.

[0183] The following numbered statements outline various embodiments of the techniques described herein. Embodiment Al . A node configured to, and / or comprising a communication interface and / or processing circuitry configured to:

[0184] consolidate capabilities of each of a plurality of adaptors;

[0185] receive network information from the plurality of adaptors; and

[0186] perform at least one action based on the consolidated capabilities and the received network information.

[0187] Embodiment A2. The node of Embodiment Al, wherein the node is further configured to determine capabilities of each of the plurality of adaptors, the plurality of adaptors being decoupled and independent from each other.

[0188] Embodiment A3. The node of any one of Embodiments A1-A2, wherein the node is further configured to determine a reliability indicator for a plurality of network entities.

[0189] Embodiment A4. The node of any one of Embodiments A1-A3, wherein the at least one action comprises one or more of:

[0190] determining topology-based characteristics among a plurality of network entities; andreporting topology-based information, the topology-based information comprising one or more of states of the plurality of network entities and relationships among the plurality of network entities.

[0191] Embodiment A5. The node of Embodiment A4, wherein the node is further configured to report metadata that indicates a reliability of topology -based information.

[0192] Embodiment A6. The node of any one of Embodiments A1-A5, wherein the capabilities comprises one or more of attributes, indication of network entities and indication of relationships among the network entities.

[0193] Embodiment A7. The node of any one of Embodiments A1-A6, wherein the node is a Topology Exposure & Inventory, TE&IV, node.

[0194] Embodiment Bl. A method implemented in a node, the method comprising: consolidating capabilities of each of a plurality of adaptors;

[0195] receiving network information from the plurality of adaptors; and

[0196] performing at least one action based on the consolidated capabilities and the received network information.

[0197] Embodiment B2. The method of Embodiment Bl, further comprising determining capabilities of each of the plurality of adaptors, the plurality of adaptors being decoupled and independent from each other.

[0198] Embodiment B3. The method of any one of Embodiments B1-B2, further comprising determining a reliability indicator for a plurality of network entities.

[0199] Embodiment B4. The method of any one of Embodiments B1-B3, wherein the at least one action comprises one or more of:

[0200] determining topology-based characteristics among a plurality of network entities; andreporting topology-based information, the topology-based information comprising one or more of states of the plurality of network entities and relationships among the plurality of network entities.

[0201] Embodiment B5. The method of Embodiment B4, further comprising reporting metadata that indicates a reliability of topology -based information.

[0202] Embodiment B6. The method of any one of Embodiments B1-B5, wherein the capabilities comprises one or more of attributes, indication of network entities and indication of relationships among the network entities.

[0203] Embodiment B7. The method of any one of Embodiments B1-B6, wherein the node is a Topology Exposure & Inventory, TE&IV, node.

[0204] Embodiment Cl . An adaptor configured to, and / or comprising a communication interface and / or comprising processing circuitry configured to:

[0205] communicate capability information for consolidation of capabilities of a plurality of adaptors by a node; and

[0206] transmit network information to the node for determining topology -based information.

[0207] Embodiment C2. The adaptor of Embodiment Cl, wherein the adaptor is associated with at least one attribute that is different from at least one attribute of at least one other adaptor of the plurality of adaptors.

[0208] Embodiment C3. The adaptor of any one of Embodiments C1-C2, wherein the node is a Topology Exposure & Inventory, TE&IV, node.

[0209] Embodiment DI . A method implemented in an adaptor, the method comprising:

[0210] communicating capability information for consolidation of capabilities of a plurality of adaptors by a node; and

[0211] transmitting network information to the node for determining topology -based information.Embodiment D2. The method of Embodiment DI, wherein the adaptor is associated with at least one attribute that is different from at least one attribute of at least one other adaptor of the plurality of adaptors.

[0212] Embodiment D3. The method of any one of Embodiments D1-D2, wherein the node is a Topology Exposure & Inventory, TE&IV, node.

Claims

32CLAIMS1. A method implemented in a Topology Exposure & Inventory, TE&IV, node for a communication network, the method comprising:consolidating (SI 00) capabilities of each of a plurality of adaptors, wherein each adaptor is for mediating network information comprising representations for one or network entities in the communication network, and / or representations of relationships between network entities in the communication network;receiving (SI 02) network information from the plurality of adaptors; and performing (SI 04) at least one action based on the consolidated capabilities and the received network information.

2. The method of claim 1, further comprising determining capabilities of each of the plurality of adaptors.

3. The method of claim 2, wherein determining capabilities of an adaptor comprises any of:obtaining a manifest for an adaptor before, or when, consolidating capabilities; obtaining a list of capabilities from an adaptor when the adaptor is deployed in the communication network; andinterrogating an adaptor to determine the capabilities.

4. The method of any of claims 1-3, wherein consolidating (S100) capabilities comprises:collating capabilities of each of the plurality of adaptors into a record defining each network entity and / or relationship between network entities; andannotating the record to indicate whether network information for each network entity and / or relationship may be populated, and / or from which adaptor the network information for each network entity and / or relationship is received.

5. The method of any of claims 1-4, wherein the at least one action comprises one or more of:determining a reliability indicator for a plurality of network entities;33determining topology-based characteristics among a plurality of network entities; reporting topology-based information, the topology-based information comprising one or more of states of the plurality of network entities and relationships among the plurality of network entities; andannotating a model with capability metadata, publishing the annotated model to consumers, and applying priority policy or configuration where capabilities have overlap.

6. The method of claim 5, wherein topology-based characteristics comprise any of: a normal operation frequency of updates; limits beyond which the network entity may be considered unreliable; and update frequency.

7. The method of claim 5 or 6, further comprising reporting metadata that indicates a reliability of topology-based information.

8. The method of any of claims 5-7, wherein the reliability indicator is one of: ADVISED, DEVIATED, PARTIAL, NOT IN SYNC, RESTORED, OK, and NOT POPULATED.

9. The method of any of claims 5-8, wherein the reliability indicator indicates whether and / or what inconsistency exists in a representation for a network entity and / or in a representation of relationships between network entities.

10. The method of any claims 1-9, wherein the capabilities of an adaptor comprises one or more of: attributes, an indication of network entities, and an indication of relationships among the network entities.

11. The method of claim 10, wherein an attribute refers to capability metadata and / or is a topology entity / relationship attribute,wherein the capability metadata is one or more of: topology entity / relationship and the attributes of same populated / maintained by that adaptor, the sources for the topology entity / relationship, the normal frequency of updates, and / or the limits of update frequency; andwherein the topology entity / relationship attribute is one or more of: geographical data, names, identifiers, and / or key selection criteria.

12. The method of any of claims 1-11, wherein the communication network is an Open-Radio Access Network, O-RAN.

13. A method implemented in an adaptor in a communication network, wherein the adaptor is for mediating network information comprising representations for one or network entities in the communication network, and / or representations of relationships between network entities in the communication network, the method comprising:communicating (SI 06) capabilities for the adaptor to a Topology Exposure & Inventory, TE&IV, node in the communication network, wherein the TE&IV node consolidates capabilities of a plurality of adaptors; andtransmitting (SI 08) network information to the TE&IV node for use by the TE&IV node in determining topology -based information.

14. The method of claim 13, wherein the capabilities of an adaptor comprises one or more of: attributes, an indication of network entities, and an indication of relationships among the network entities.

15. The method of claim 14, wherein an attribute refers to capability metadata and / or is a topology entity / relationship attribute,wherein the capability metadata is one or more of: topology entity / relationship and the attributes of same populated / maintained by that adaptor, the sources for the topology entity / relationship, the normal frequency of updates, and / or the limits of update frequency; andwherein the topology entity / relationship attribute is one or more of: geographical data, names, identifiers, and / or key selection criteria.

16. The method of any of claims 13-15, wherein the communication network is an Open-Radio Access Network, O-RAN.

17. A Topology Exposure & Inventory, TE&IV, node (4) for use in a communication network, wherein the TE&IV node (4) is configured to perform the method of any of claims18. An adaptor (6) for use in a communication network, wherein the adaptor (6) is for mediating network information comprising representations for one or network entities in the communication network, and / or representations of relationships between network entities in the communication network, and wherein the adaptor (6) is configured to perform the method of any of claims 13-16.

19. A computer program product comprising a computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform the method of any of claims 1-16.

Images