Managing network elements in radio access network of telecommunication system

By introducing intermediary processor modules between element managers and operation support systems, and using filtering standards to achieve complex isolation and fine management of RAN, the security and privacy issues of RAN management in MORAN and private networks in the prior art are solved, and the security and privacy issues of RAN management in MORAN and private networks are provided. Customized segmentation scheme and efficient network resource management.

CN118975204APending Publication Date: 2024-11-15TELECOM ITALIA SPA
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202380031271.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-01
Filing Date
2023-03-16
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

The prior art has difficulty in effectively managing network elements of radio access networks (RAN) in multi-operator radio access networks (MORAN) and dedicated network scenarios, especially in the need of complex RAN isolation and customized segmentation schemes, with security and privacy issues, and lack of programmable RAN isolation mechanism.

Method used

By introducing intermediary processor modules between the element manager (EM) and its northbound interface and operation support system, filtering communications using predetermined filtering standards allows each operator to independently manage the RAN partitions it controls, realizing the network elements Fine isolation and custom segmentation schemes.

Benefits of technology

The complex isolation and fine management of RAN is realized, ensuring the satisfaction of security and privacy needs, and providing customized segmentation solutions, allowing each network operator to independently manage its network cells, improving the efficiency of network resource allocation and Security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118975204A_ABST
    Figure CN118975204A_ABST
Patent Text Reader

Abstract

A method of managing, by one or more telecommunications operators, a network element (110a, 110b, 115a, 115b) of a system of an access network (105a, 105b) of a telecommunications network through one or more network element management functions (120a, 120b) of an operation support system (130-1, 130-2, 130-N) of the telecommunications operator. The method comprises providing an intermediary processor module (135) configured to intermedially process a communication between an operation support system (130-1, 130-2, 130-N) of a telecommunications operator and a network element management function (120a, 120b) by filtering the communication according to a predetermined filtering criterion (140), the network elements (110a, 110b, 115a, 115b) of the access network (105a, 105b) are connected to the operation support system (130-1, 130-2, 130-N) to allow the operation support system (130-1, 130-2, 130-N) of each of the one or more telecommunications operators to manage only respective portions of the network elements (110a, 110b, 115a, 115b) of the access network (105a, 105b) depending on the filtering criteria.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Background Technical Field

[0001] The solution disclosed herein relates broadly to the field of telecommunications, in particular to wireless (radio) telecommunication systems and networks, such as (cellular) mobile phone networks. In particular, the solution disclosed herein relates to the management of network elements in a radio access network, eg a mobile phone network.

[0002] Overview of related technologies

[0003] In a radio telecommunication system, such as a mobile phone network, a Radio Access Network (RAN) is a part of the telecommunication system which enables radio access of user equipment to the telecommunication system, such as a mobile phone network, by implementing a certain radio access technology. The RAN is located between user equipment (User Equipment - UE, or Terminal Equipment, or Mobile Station - MS, the name depends on the telecommunication standard) such as a mobile phone, and provides a connection to the Core Network (CN) of the telecommunication system.

[0004] The RAN of a radio telecommunication network comprises several Network Elements (NEs), which are elements deployed at the edge of the telecommunication network for managing the radio transmission of the network (e.g., NodeB, eNodeB, gNodeB, depending on the generation of the radio telecommunication network). The NEs need to be managed and monitored by the telecommunication network operator(s) in order to ensure the desired Quality of Service (QoS) level for the users.

[0005] Fault Configuration Accounting Performance and Security (FCAPS) is an ISO telecommunications management network model and framework for the management of telecommunications networks. Fault, configuration, accounting (or sometimes governance), performance and security are the management categories that the ISO model defines network management tasks as.

[0006] The FCAPS management of NEs in the RAN by a telecommunication network operator is usually based on so-called Element Managers (EM).

[0007] An EM is an element of a telecommunications network that is concerned with managing the functions and capabilities of one or usually more NEs with which it is associated and under its responsibility.

[0008] The EM provides (i.e. exposes) two interfaces: a southbound interface (SBI) towards the NEs under its responsibility, and a northbound interface (NBI), i.e. an interface that allows the EM to communicate with higher-level subsystems of the wireless telecommunication system (specifically, the Operation Support System (OSS) including, for example, the telecommunication network operator's systems for configuration management (CM), performance management (PM), trace management (TM), etc. of the NEs). The NBI conceptualizes the low-level details (e.g., data or functions) used by or in the EM, allowing the EM to interface with the OSS.

[0009] There are radio telecommunication systems in which the RAN is fully owned and operated by a single network operator. Other radio telecommunication systems have a RAN infrastructure known as a Multi-Operator Radio Access Network (MORAN) that is shared by two or more network operators: each of the network operators owns some of the NEs of the RAN and shares them with the other network operators for the purpose of providing services to the respective subscribers.

[0010] The network operator that substantially owns a NE (e.g., NodeB, eNodeB, gNodeB) is the "primary" network operator of that NE. The primary network operator may share the owned NEs (i.e., e.g., its NodeBs, its eNodeBs, its gNodeBs) with other network operators that are "guest" network operators with respect to that NE. Sharing may include, for example, hosting a set of cells on the same NE, where some of such cells belong to the "primary" operator and the remaining cells belong to different "guest" operators, respectively.

[0011] Typically, in a MORAN scenario, NEs owned by different operators are deployed in different geographical areas, i.e., one network operator deploys its NEs in one geographical area, another network operator deploys its NEs in another geographical area, and so on.

[0012] EP 2477427 A1 discloses a RAN, in particular, a method and system for enabling multi-operator billing in the RAN. A radio base station in a radio access network is described, wherein the radio base station is adapted to be connected to a plurality of core networks upstream of the radio base station. The radio base station comprises a wireless transmission and / or reception unit adapted to establish communication with a user equipment via a radio interface, and a processing unit adapted to determine a first core network among the plurality of core networks, wherein the first core network processes communication with the user equipment upstream of the radio base station; allocates resources to communication with the user equipment; and tracks indications of allocated resources associated with the first core network.

[0013] CA 2521224 A1 discloses a method for radio communication in a cellular radio network having a radio access network and a core network, the method comprising connecting at least two different core networks to one RAN and sharing at least one network element (RNC, BTS) of the RAN between the at least two different core networks.

[0014] US2014 / 0348068 A1 discloses a device, comprising: a core interface component, adapted to provide an eastbound interface to a first core network element and to a second core network element different from the first core network element; a radio interface component, adapted to provide a westbound interface to a first radio access network element and to a second radio access network element different from the first radio access network element; a multiplexing detection component, adapted to detect whether a first request received at one of the eastbound interface and the westbound interface is directed to the first network element and / or the second network element of the corresponding other interface; an adaptation component, adapted to adapt the first request according to the network element to which the first request is directed; and a multiplexing component, adapted to multiplex the adapted first request to the first network element and / or the second network element of the corresponding other interface according to the detection of the multiplexing detection component.

[0015] WO 2014 / 053597 A1 discloses a method in a network node for configuring a network node for a first PLMN and at least one second PLMN in a telecommunication system. The network node is adapted to serve one or more cells. The network node configures primary PLMN information for the one or more cells to include neither the first PLMN nor the at least one second PLMN. The network node configures further PLMN information for each of the one or more cells in the network node based on information indicating which of the first PLMN or the at least one second PLMN each cell belongs to.

[0016] EP 3059903 A1 discloses that, in order to allow multiple mobile network operators (MNOs) to share at least two of a RAN, a mobile backhaul network (MBH), and a core network (CN), a network control system operates to enforce network resource configuration for each of at least two networks to be shared among the RAN, the MBH, and the CN according to common resource partitioning information indicating slices of network resources between the multiple MNOs. Therefore, it can help to improve the efficiency of performing network resource allocation settings for at least two networks to be shared. Summary of the invention

[0017] The applicant notes that all the prior art documents cited above focus on the radio aspect rather than the management of NEs of the RAN, where "management of NEs of the RAN" here refers to the FCAPS (Fault Configuration Accounting Performance and Security) management of NEs in the RAN by the telecommunication network operator based on the Element Manager (EM) and its functions, as defined in the ISO Telecommunication Management Network Model and Framework for Management of Telecommunication Networks or any equivalent management system for management of NEs having functions equivalent to those of FCAPS.

[0018] In particular, all the prior art documents mentioned above only deal with RAN sharing from the perspective of radio resource allocation and equipment. None of the cited documents focuses on the management of NEs, let alone FCAPS.

[0019] Furthermore, the cited prior art documents do not cover the management of NEs of RAN in scenarios such as MORAN and private networks. As mentioned above, MORAN refers to a scenario in which the RAN infrastructure of a radio telecommunication system is shared by two or more network operators, each of which owns some of the NEs of the RAN (e.g., NodeB, eNodeB, gNodeB) and shares them with (at least one of) the other network operators (which are guest network operators with respect to the NEs owned by the primary network operators). A private network (also referred to as a "non-public network") is a private cellular network that uses cellular mobile phone network technology, in particular licensed, shared or unlicensed wireless spectrum and 4G or 5G cellular networking base stations, small cells and other parts of the 4G or 5G RAN infrastructure to deliver voice and data to edge devices including smartphones, embedded modules, routers and gateways. The difference between public and private networks is who has a license or priority access to the wireless spectrum, and who owns and operates the base stations and infrastructure of the network: with respect to public networks, the telecommunication network operator owns and operates the spectrum and network infrastructure, and generally all subscribers of the telecommunication network operator have the same access rights to the network. In contrast, in a private network, a private organization owns, operates, or has some level of priority access to the network infrastructure or spectrum.

[0020] The solution disclosed in this document relates to the management of Network Elements (NEs) in a Radio Access Network (RAN) of a radio telecommunication network. As mentioned in the above lines, where "management of NEs in the RAN" refers here to the FCAPS (Fault Configuration Accounting Performance and Security) management of the NEs in the RAN by the telecommunication network operator based on the Element Manager (EM) and its functionalities as defined in the ISO Telecom Management Network Model and Framework for Management of Telecommunication Networks or any equivalent management system for management of NEs having functionalities equivalent to those of FCAPS.

[0021] The applicant has realized that an EM that allows OSS access to the NE can be used to implement a RAN "isolation" scheme for creating partitions of the RAN of a radio telecommunications network. However, the applicant has noticed that current implementations of the EM are able to allow only simple "partitioning" of the RAN (e.g., partitioning related only to 5G nodes of a specific manufacturer, as 5G is still a new technology), which makes it impossible to manage complex RAN "isolation" schemes (as will be required in certain use cases (such as MORAN and private networks)), and also leads to security and privacy issues.

[0022] Furthermore, the functionality and capabilities of EMs available in the market depend on their specific manufacturers, and an analysis of the products available in the market revealed a lack of programmable RAN isolation mechanisms. Thus, telecom network operators are not allowed to define customized RAN segmentation schemes using the mechanisms implemented within the EM, but only simple segmentation is possible, such as isolation of clusters consisting of nodes / NEs, rather than isolation on a per-network cell basis.

[0023] The Applicant has solved the problem of offering telecommunication network operators enhanced capabilities for managing their NEs of RAN in particular, but not limited to, MORAN and dedicated network scenarios. In such scenarios, it is desirable to leverage management of NEs separately for each of the different network operators (such as FCAPS management as defined in the ISO Telecom Management Network Model and Framework for the Management of Telecom Networks or any equivalent management system for the management of NEs having functionalities equivalent to those of FCAPS), thus requiring not only NE level but also fine-grained segregation within the same NE, for example on a per-network cell basis (as is known, a NE can manage radio transmissions for more than one (possibly several) network cells; different network cells entering the same NE can belong to different network operators: a primary network operator and one or more guest network operators, which should be enabled to manage the network cells they control). In fact, the Applicant has conceived a solution that offers the ability to define a customized RAN segmentation scheme also within the same NE, for example by defining appropriate filtering criteria, for managing the NE based on an Element Manager (EM) and its functions or based on equivalent functions implemented by elements other than the EM (e.g. by distributed microservices distributed between the NEs and the OSS of the network operator).

[0024] According to one aspect, the solution disclosed herein provides a method for managing network elements of a system of an access network of a telecommunication network by one or more telecommunication operators through one or more network element management functions of an operation support system of the telecommunication operators.

[0025] The common network elements (e.g., NodeB, eNodeB, gNodeB) of the system of the access network are owned by a telecommunication operator (the primary network operator or primary operator of the network element), and the primary operator may share its NE with at least one other telecommunication operator, which is a guest network operator or guest operator with respect to the NE.

[0026] The method includes providing an intermediary processor module configured to intermediary process the communications between the operation support system of the telecommunications operator and the network element management function by filtering the communications according to predetermined filtering criteria to allow the operation support system of each of one or more telecommunications operators to manage only the corresponding part of the network element of the access network depending on the filtering criteria.

[0027] Specifically, the communication between the telecom operator's operations support system and the network element management function can be intended for Fault Configuration Accounting Performance and Security (FCAPS) management operations on the network element, as defined in the ISO Telecom Management Network Model and Framework for management of telecommunications networks or any equivalent management system for management of NEs having functional equivalents to those of FCAPS.

[0028] In an embodiment, the network element management function may be implemented by an element manager.

[0029] In particular, the element manager exposes a northbound interface, and in an embodiment, an intermediate processor module may be located between the northbound interface of the element manager and the operation support system of the telecommunications operator.

[0030] In other embodiments, the network element management function may be implemented by distributed partial services distributed between the network elements and the operation support system of the telecommunications operator, and the distributed partial services jointly implement the network element management function.

[0031] According to another aspect, the solution disclosed herein provides a communication intermediary processor designed to be located between a network element management function responsible for management of corresponding network elements of an access network system of a telecommunication system and at least one operation support system of at least one telecommunication operator of the telecommunication system.

[0032] The communication mediation processor is configured to mediate the communication between the operation support system and the network element management function by filtering the communication according to predetermined filtering criteria to allow the operation support system to manage only the corresponding portion of the network elements of the access network depending on the filtering criteria.

[0033] Communications between the telecommunications operator's operations support system and the network element management function may be intended for Fault Configuration Accounting Performance and Security (FCAPS) management operations on the network element.

[0034] In an embodiment, the network element management function may be implemented by an element manager.

[0035] The element manager exposes a northbound interface, and the intermediate processor module may be located between the northbound interface of the element manager and the operation support system of the telecommunications operator.

[0036] In other embodiments, the network element management function may be implemented by distributed partial services distributed between the network elements and the operation support system of the telecommunications operator, and the distributed partial services jointly implement the network element management function.

[0037] Communication intermediary processors may include:

[0038] - a communication filtering module configured to filter said communication between the operation support system and the network element management function according to said predetermined filtering criteria, and

[0039] - a programming interface configured to receive filtering parameters defining said predetermined filtering criteria for configuring said communication filtering module.

[0040] According to yet another aspect, the solution disclosed herein provides a telecommunication system comprising an access network system including a plurality of network elements.

[0041] One or more network element management functions are each responsible for management of a corresponding group of network elements in the plurality of network elements.

[0042] The telecommunication system includes at least one operation support system of corresponding at least one telecommunication operator.

[0043] A communication intermediary processor is provided. The communication intermediary processor is located between a network element management function and at least one operation support system of at least one telecommunications operator, and is configured to mediate the communication between the operation support system and the network element management function by filtering the communication according to a predetermined filtering criterion, so as to allow the operation support system to manage only a corresponding portion of the network element of the access network depending on the filtering criterion.

[0044] BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The above features and advantages and other features and other advantages will become clear from the following detailed description of the solutions disclosed herein, which are provided by way of non-limiting examples only. For a better understanding, the following description should be read in conjunction with the accompanying drawings, in which:

[0046] Figure 1 schematically depicts a part of a system of a RAN of a wireless mobile telecommunication network with an NBI mediator processor according to an embodiment of the solution disclosed herein, and

[0047] Figure 2 Describes in more detail Figure 1 An NBI mediator processor according to an embodiment of the solution disclosed herein is shown.

[0048] Detailed Description of Exemplary Embodiments

[0049] The solution disclosed here is an advanced intermediate processor module for the North Bound Interface (NBI) of an Element Manager (EM) (hereinafter also referred to as the advanced intermediate processor for NBI, or the advanced intermediate processor, or the NBI intermediate processor or simply, the intermediate processor), which allows to isolate a complex Radio Access Network (RAN) or system of RANs of a radio telecommunication system into different RAN partitions, giving one or more network operators the possibility to manage each RAN partition separately.

[0050] The advanced mediator processor sits between the EM (with which it interacts via its NBI) and one or more Operation Support Systems (OSS), and is configured to expose to the OSS a different "filtered" NBI for each desired RAN partition.

[0051] For example, considering a multi-operator RAN (MORAN) scenario (where, for example, two telecommunication network operators A and B share a RAN or a network element (EM) of a system of RANs for the purpose of providing services to their respective subscribers), a NE shared by operator A and operator B may be connected to the same EM. Through an advanced intermediary processor for NBI, each network operator may have dedicated access to its own NE for the purpose of FCAPS management with the aid of a filtered NBI for a dedicated purpose. The overall NBI exposed by the EM responsible for the shared NE is filtered by the advanced intermediary processor for NBI (in this example, using a single identifier of the Public Land Mobile Networks (PLMNs) of operator A and operator B as a filtering parameter) and exposed to the appropriate network operator that owns the NE and therefore should have dedicated FCAPS management authorization for the NE.

[0052] In another exemplary scenario, the advanced intermediate processor can split the data of the entire NBI among different radio access technologies (RATs), different radio frequencies, etc. to meet any requirements for data isolation. In this way, the OSS of the telecommunications network operator is allowed to manage the NEs of the RAN separately according to their corresponding RATs, radio frequencies, etc. (for FCAPS management purposes).

[0053] See also Figure 1 , schematically depicts a part of a system of a RAN of an exemplary wireless mobile telecommunication network with an NBI mediator processor according to an embodiment of the solution disclosed herein.

[0054] Figure 1 The exemplary RAN system shown in FIG. 1 includes a first RAN 105a and a second RAN 105b (the RAN system may include Figure 1 Other RANs not shown).

[0055] The first RAN 105a includes, for example, radio network nodes (e.g., NodeB, eNodeB, gNodeB, depending on the generation of the wireless communication network), collectively referred to as 110a, which belong to the same RAT (e.g., 3G RAT, 4G RAT, 5G RAT) and / or are owned by the same single network operator (operator-1, or operator-2, ..., or operator-N). The first RAN 105a also includes radio network nodes (e.g., NodeB, eNodeB, gNodeB), collectively referred to as 110b, which belong to different RATs and / or are owned by two or more different network operators (e.g., any combination of two or more of network operators operator-1, or operator-2, ..., or operator-N).

[0056] Similar to the first RAN 105a, the second RAN 105b includes, for example, radio network nodes (e.g., NodeB, eNodeB, gNodeB), collectively referred to as 115a, which belong to the same RAT (e.g., 3G RAT, 4G RAT, 5G RAT) and / or are owned by the same single network operator (operator-1, or operator-2, ..., or operator-N). The second RAN 105b also includes radio network nodes (e.g., NodeB, eNodeB, gNodeB), collectively referred to as 115b, which belong to different RATs and / or are owned by two or more different network operators (e.g., any combination of two or more of network operators operator-1, or operator-2, ..., or operator-N).

[0057] The radio network nodes 110a, 110b, 115a, 115b are network elements (NE) of the wireless mobile telecommunication network.

[0058] For FCAPS purposes, the first RAN 105a (i.e., the radio network nodes or NEs 110a and 110b of the first RAN 105a) is managed by a first element manager (EM) 120a. Similarly, for FCAPS purposes, the second RAN 105b (i.e., the radio network nodes or NEs 115a and 115b of the second RAN 105b) is managed by a second EM 120b. For FCAPS purposes, other RANs (which may be part of a system of RANs not in Figure 1 ) are similarly provided by the corresponding other EMs (not shown in Figure 1 management.

[0059] For FCAPS purposes, EMs 120a and 120b (and other EMs, if present) manage the NEs under their responsibility and need to be managed and monitored by the telecommunications network operator in order to ensure the desired quality of service (QoS) level for network users. To this end, EMs 120a and 120b (and other EMs, if present; hereinafter in this specification, reference will only be made to EMs 120a and 120b, with the intention that if other EMs are present, the same considerations apply to them as well) expose two interfaces: a southbound interface (SBI) towards the corresponding NEs under their responsibility (for EM 120a, the radio network nodes 110a and 110b; for EM 120b, the radio network nodes 115a and 115b), and a northbound interface (NBI) 123 towards higher-level subsystems of the wireless mobile telecommunications network.

[0060] The NBI of an EM typically allows direct communication between the EM and the Operations Support System (OSS) of a telecommunications network operator, for enabling the OSS to perform operations involving the NE under the EM's responsibility, in particular Fault Management Configuration Accounting Performance and Security (FCAPS) operations, such as Configuration Management (CM), Performance Management (PM), Tracking Management (TM) and Fault Management (FM).

[0061] According to the examples described herein, with reference to a multi-operator RAN (MORAN) scenario, the NBIs of the EMs 120a and 120b allow the latter to communicate with different OSSs 130-1, 130-2, 130-N of different network operators Operator-1, or Operator-2, ..., or Operator-N. Each of the OSSs 130-1, 130-2, 130-N includes systems / functionality of the respective network operator for several operations involving the NEs 110a, 110b, 115a, and 115b, in particular FCAPS operations such as configuration management (CM), performance management (PM), trace management (TM), and fault management (FM), as well as other operations, as described in detail later.

[0062] According to the solution disclosed herein, the NBIs 123 of all EMs 120a and 120b are commonly connected to the same bus 125, and the communication with different OSSs 130-1, 130-2, 130-N of different network operators Operator-1, or Operator-2, ..., or Operator-N is mediated by an NBI mediator 135. The NBI mediator 135 (which is attached to the bus 125) is located between the NBIs 123 of the EMs 120a and 120b and the OSSs 130-1, 130-2, 130-N of different network operators.

[0063] As mentioned in the above lines, Figure 1The wireless telecommunication network scenario depicted in and considered here by way of example is a MORAN scenario, in which different network operators Operator-1, Operator-2, ..., Operator-N share the same NEs (at least some of all NEs) for the purpose of providing services to their subscribers, i.e. the same radio network nodes (NodeB, eNodeB, gNodeB) of NEs 110a, 110b, 115a and 115b. As mentioned before, the radio network node 110b of the first RAN 105a and the radio network node 115b of the second RAN 105b may be shared between different network operators for the purpose of providing services to their subscribers.

[0064] In fact, any of the radio network nodes 110a, 110b, 115a and 115b, although possibly shared between different network operators, is actually owned by a specific one of the network operators Operator-1, Operator-2, ..., Operator-N (i.e., belongs to the RAN physically deployed by it). Each network operator, although sharing the use of its own radio network nodes with other network operators for the purpose of providing services to users, needs to have full control over its own radio network nodes for the purpose of managing them. A single OSS for all EMs 120a and 120b that communicate directly with them via their NBI 123 is not suitable to allow this, because from one point of view, the OSS will have arbitrary access to all data made available by the EMs 120a and 120a, while from another point of view, the OSS will be allowed to perform every management operation arbitrarily on the EMs 120b and 120b. If all OSSs 130-1, 130-2, 130-N will communicate directly with the EMs 120a and 120b via their NBIs 123, the same problem arises.

[0065] According to an embodiment of the solution disclosed herein, the NBI mediator 135 is designed and configured to enable partitioning of the system of RAN 105a, 105b, which allows different network operators (operator-1, operator-2, ..., operator-N) of the MORAN to exercise full control over their own RAN (i.e., their own radio network nodes) for management purposes, while allowing RAN sharing between different network operators for the purpose of providing services to users.

[0066] For the purpose of management of the RAN 105a, 105b of the RAN system, the OSS 130-1, 130-2, 130-N of different network operators Operator-1, or Operator-2, ..., or Operator-N interfaces with the NBI mediator processor 135 (in Figure 1, the interaction between the OSSs of different network operators Operator-1, or Operator-2, ..., or Operator-N is represented as 137-1a and 137-1b for the OSS 130-1 of network operator Operator-1; 137-2 for the OSS 130-2 of network operator Operator-2, and 137-N for the OSS 130-N of network operator Operator-N). The OSS 130-1, 130-2, 130-N interfaces with the NBI mediator 135 via an interface 139, which can be viewed as a "filtered" version of the NBI 123 of the EM 120a, 120b, where "filtered" here means that different OSSs 130-1, 130-2, 130-N of different network operators Operator-1, Operator-2, ..., Operator-N can only "see" those data exposed by the NBI 123 of the different EM 120a, 120b that are of interest / relevant to them.

[0067] The NBI mediator processor 135 is preferably programmable and includes programmable logic that allows for management purposes (e.g., based on filtering parameters, Figure 1 The filtering parameters may be used to isolate the intelligence of the systems of the RAN 105a, 105b by using the global representation 140 in FIG. Such filtering parameters may include, for example, but are not limited to: a single identifier for different PLMNs of different network operators, an E-UTRA Absolute Radio Frequency Channel Number (EARFCN, for 4G FDD, a code for a pair of physical radio carriers designated for transmission and reception in a land mobile radio system, one of the pair of physical radio carriers being used for uplink signals and one for downlink signals), an identifier of a RAT available in the system of the RAN, a network cell name, a network cell identifier, etc.

[0068] Figure 1 Also depicted is an overall network controller 145, which communicates directly with the EMs 120a, 120b (via the full NBI 123 exposed by the EMs) without the mediation of the NBI mediator 135 as indicated by reference numeral 147 for the purpose of supervising the management of the EMs. The overall network controller 145 can be one of the different network operators Operator-1, Operator-2, ..., Operator-N, or it can be a third party entity different from the network operator. The overall network controller 145 can, for example, set the filtering parameters 140 for the NBI mediator 135. The overall network controller 145 can also interface with the NBI mediator (e.g., Figure 1 150 in the figure) for application or system management (e.g., maintenance, software / firmware updates).

[0069] Figure 2The internal structure of the NBI mediator processor 135 in an embodiment of the solution disclosed herein is shown in some detail at a functional block / module level.

[0070] The NBI intermediary processor 135 includes: an NBI termination function module 205; an FCAPS intermediary processor module 210; a filtering capability module 215; an encryption and ciphering module 220; a data storage module 225, and a configuration import adaptation module 230.

[0071] The NBI termination functional module 205 is configured to be able to manage NBIs that depend on different manufacturers (in practice, EMs from different manufacturers may implement and expose NBIs 123 that may be more or less slightly different from each other, e.g. in terms of data models: for example, EM 120a and EM 120b deployed in the field may be produced by different manufacturers and their NBIs 123 may not be exactly the same).

[0072] The FCAPS intermediate processor module 210 implements an adaptation layer that is configured to ensure correct conversion from the proprietary NBI data model of the NBI 123 to a standard data model (defined by a standardization entity or by a user, such as defined by Operator-1, Operator-2, ..., Operator-N) so as to ensure that the EM 120a, 120b exposes a common interface to the OSS 130-1, 130-2, 130-N of different network operators Operator-1, Operator-2, ..., Operator-N.

[0073] The NBI termination function module 205 and the FCAPS mediator processor module 210 together enable consistent bidirectional communications between the EMs 120a and 120b and the OSSs 130-1, 130-2, 130-N of different network operators Operator-1, Operator-2, ..., Operator-N.

[0074] The filtering capability module 215 is configured to implement the core functionality of the NBI mediator 135. The filtering capability module 215 is configured to execute (one or more) filtering algorithms for "filtering" the data exposed by the EMs 120a, 120b through their NBIs 123 and made available on the bus 125, so that the OSSs 130-1, 130-2, 130-N of different network operators Operator-1, Operator-2, ..., Operator-N only access those data in the different EMs 120a, 120b that are of interest to them / relevant to them (e.g., filtering for 4G on PLMN). The filtering capability module 215 may expose an interface 235, such as an application programming interface (API), which enables its configuration to be set based on the filtering parameters 140 provided externally (e.g., by the overall network controller 145). The configuration of the filtering capability module 215 may occur in real time and automatically. Through the interface 139 of the NBI mediator 135, the OSSs 130-1, 130-2, 130-N of different network operators Operator-1, Operator-2, ..., Operator-N can request and obtain in real time from the filtering capability module 215 "filtered" data from the EM 120a, 120b, which is derived from the data available on the bus 125 by isolating the portion of the data that is of interest / related to the specific OSS 130-1, 130-2, 130-N for management purposes. The filtering capability module 215 also stores the "filtered" data available on the bus 125 in the data storage module 225, thereby allowing the OSSs 130-1, 130-2, 130-N to access and retrieve the relevant data offline at a later time.

[0075] The encryption and cryptography module 220 is configured to enable activation of a security mechanism for storing and managing data stored in the data storage module 225, which are not in plain text but are protected with a higher security standard.

[0076] The data storage module 225 is configured to enable the OSS 130-1, 130-2, 130-N to access relevant NE management data offline, possibly with predefined data historicization. The data storage module 225 can be configured to store configuration management (CM) data, performance management (PM) data, tracking management (TM) data, fault management (FM) data, etc. in individual repositories.

[0077] The configuration import adaptation module 230 is configured to enable all automation functions of management (e.g., configuration) of NEs (i.e., radio network nodes 110a, 110b, 115a, 115b) by the competent OSS in OSS130-1, 130-2, 130-N of different network operators Operator-1, Operator-2, ..., Operator-N. Specifically, the configuration import adaptation module 230 receives management (e.g., configuration) commands from the OSSs 130-1, 130-2, 130-N of different network operators Operator-1, Operator-2, ..., Operator-N, and identifies which OSS can manage which NEs 110a, 110b, 115a, 115b of the RAN 105a, 105 system by performing checks on the NE parameters that the OSS attempts to configure / modify (e.g., to ensure that a certain OSS has the authority to configure / change the parameters of certain NEs belonging to a certain RAN), and addresses the management commands to the correct (one or more) EMs 120a, 120b (which will then configure the correct NEs). In addition, time scheduling of configuration commands is also possible.

[0078] The NBI mediator 135 may further include a Web graphical user interface (GUI) module 240 for allowing a system administrator (eg, of the overall network controller 140 ) to manage the NBI mediator 135 via the Web.

[0079] Advantageously, all data exchanges between (the functional modules of) the NBI mediator 135 and the OSS are API-based.

[0080] The NBI mediator 135 working on the NBI 123 of the EM 120a, 120b is also useful for meeting the security and automation aspects which are important and critical aspects of the RAN. With programmable cloud-based microservices, enabling the OSS of different network operators to complete the management of their own RAN parts (e.g., FCAPS management or equivalent management functions), the NBI mediator 135 can be used for several functions, such as those that fall under FCAPS management: Configuration Management (CM) of NE, Performance Management (PM) of NE, Tracking Management (TM) of NE, Fault Management (FM) of NE.

[0081] Advantageously, the NBI mediator 135 enables fully automated filtering parameter changes (eg, via the API 235).

[0082] The NBI mediator 135 may also enable fully automatic network parameter changes by means of (the API of) the configuration import adaptation module 230 .

[0083] The NBI broker 135 may also enable regular topology exports and / or on-demand topology exports, thanks to an API 139 that exposes filtered topology. The EMs 120a, 120b make topology data describing the network of NEs under their responsibility available to network operators. The NBI broker 135 allows each network operator to access these topology data filtered for the NEs owned by the network operator.

[0084] The NBI mediator 135 may also selectively enable fully automated configuration of Minimization of Drive Tests (MDT) measurement activities on NEs or even network cells belonging to different network operators.

[0085] As described above, the NBI intermediate processor 135 can advantageously enable encryption of communication channels between the NBI intermediate processor 135 and the OSS130-1, 130-2, 130-N of different network operators Operator-1, Operator-2, ..., Operator-N, as well as encryption of data exchanged with the OSS of different network operators, backup of historical information, encryption and storage of CM / PM / FM / TM data (even for long storage times).

[0086] The NBI mediator 135 allows MOCN (Multiple Operator Core Network, a scenario where a single network operator may have different core networks used, for example, to support dedicated networks) management, including filtering associated with different core networks and / or radio access technologies. For example, the NBI mediator 135 allows the network operator to separately manage different RATs among several possible RATs of the RAN 105a, 105b. This is particularly useful in Figure 1 and Figure 2 1 is schematically depicted by two interactions 137-1a and 137-1b between the OSS 130-1 of the network operator operator-1: for example, 137-1a represents the filtered NBI visible to operator-1 for one of the RATs available in the RAN 120a, 120b system, while 137-1b represents the filtered NBI visible to operator-1 for another RAT of the available RATs.

[0087] The NBI mediator 135 also allows management of a private network while isolating management data.

[0088] The NBI mediator 135 allows overall activity log tracking for security purposes (keeping a log of all activities performed by different OSSs on both the NBI mediator 135 and the NE).

[0089] The network operator has the possibility to obtain near real-time data or offline data as required. All data exchanged with the network operator can also be provided by encryption on an encrypted channel.

[0090] Considering the flow from EM 120a, 120b to OSS 130-1, 130-2, ..., 130-N, a possible example may be daily topology generation: each EM routinely prepares a topology with a description of the entire management network (NE, network cells, adjacency between network cells, etc.), but each operator needs its own network topology to understand the network status. For this reason, the NBI intermediary processor 135 needs to filter the entire topology in order to expose the parts required by the specific operator through the interface 139. This filtering operation is possible thanks to the NBI termination function module 205, the FCAPS intermediary processor module 210 and the filtering capability module 215, which respectively terminate the interface, translate the topology into a standard format and filter based on the defined filtering criteria. Based on the export, the operator can choose to change one or more parameters, such as one or more physical cell IDs (PCI) to avoid PCI conflicts. In this case, through the interface 139, the configuration import adaptation module 230 and the NBI termination function module 205, the operator's request is sent to the EM to change the PCI.

[0091] The configuration import adaptation module 230 can also perform checks on the NE parameters that the OSS attempts to configure / modify in order to prevent the operator from changing parameters that affect other NEs / operators. In addition, requests to update one or more parameters can be scheduled in a timely manner according to the most appropriate time; in the PCI example above, this action should be scheduled at night when network traffic is at its lowest.

[0092] The solution disclosed in this document can be applied in several scenarios with the goal of creating partitions of a wireless telecommunication network that can be managed separately ensuring security and privacy requirements.

[0093] The solution disclosed in this document is also easily applicable to the future evolution of RAN, in which the FCAP management function will be implemented by distributed partial services ("microservices") distributed, for example, between network elements and operation support systems instead of by element managers; the distributed partial services jointly implement the FCAPS management function. Therefore, the FCAPS function ("EM function") implemented by the EM in the current traditional network may be implemented by distributed microservices distributed between the NE and the OSS in future developments. Therefore, for the purpose of the solution disclosed herein, the expression "EM function" or "network element management function" should be interpreted as meaning the function implemented by the EM, or the equivalent function implemented by distributed microservices in the NE or in the OSS.

Claims

1. A method for managing network elements (110a, 110b, 115a, 115b) of a system of an access network (105a, 105b) of a telecommunications network by one or more telecommunications operators through one or more network element management functions (120a, 120b) of an operation support system (130-1, 130-2, 130-N) of the telecommunications operators, the method comprising: An intermediate processor module (135) is provided, which is configured to intermediate the communication between the operation support system (130-1, 130-2, 130-N) of the telecommunications operator and the network element management function (120a, 120b) by filtering the communication according to predetermined filtering criteria (140) to allow the operation support system (130-1, 130-2, 130-N) of each of the one or more telecommunications operators to manage only the corresponding part of the network element (110a, 110b, 115a, 115b) of the access network (105a, 105b) depending on the filtering criteria.

2. The method of claim 1, wherein the communication between the operations support system of the telecommunications operator and the network element management function is intended for fault configuration accounting performance and security FCAPS management operations on the network element.

3. The method according to claim 1 or 2, wherein the network element management function is implemented by an element manager (120a, 120b).

4. The method according to claim 3, wherein the element manager exposes a northbound interface (123), and the intermediate processor module (135) is located between the northbound interface (123) of the element manager and the operation support system of the telecommunications operator.

5. The method according to claim 1 or 2, wherein the network element management function is implemented by distributed partial services distributed between the network element and the operation support system of the telecommunications operator, and the distributed partial services jointly implement the network element management function.

6. A communication intermediate processor (135): - is designed to be located between a network element management function (120a, 120b) and at least one operation support system (130-1, 130-2, 130-N) of at least one telecommunication operator of a telecommunication system, the network element management function being responsible for the management of corresponding network elements (110a, 110b, 115a, 115b) of an access network system (105a, 105b) of the telecommunication system, and - configured to mediate the communication between the operations support system and the network element management function by filtering the communication according to predetermined filtering criteria (140) to allow the operations support system to manage only the corresponding part of the network element of the access network depending on the filtering criteria.

7. The communication intermediate processor according to claim 6, wherein the communication between the operation support system of the telecommunications operator and the network element management function is intended for fault configuration accounting performance and security FCAPS management operations on the network element.

8. The communication intermediary processor according to claim 6 or 7, wherein the network element management function is implemented by an element manager (120a, 120b).

9. The communication intermediary processor according to claim 8, wherein the element manager exposes a northbound interface (123), and the intermediary processor module (135) is located between the northbound interface (123) of the element manager and the operation support system of the telecommunications operator.

10. The communication intermediate processor according to claim 6 or 7, wherein the network element management function is implemented by distributed partial services distributed between the network element and the operation support system of the telecommunications operator, and the distributed partial services jointly implement the network element management function.

11. The communication intermediate processor according to any one of claims 6 to 10, comprising: - a communication filtering module (215) configured to filter the communication between the operation support system and the network element management function according to the predetermined filtering criteria (140), - a programming interface (235) configured to receive filtering parameters defining said predetermined filtering criteria for configuring said communication filtering module.

12. A telecommunication system comprising: - an access network system (105a, 105b), the access network system comprising a plurality of network elements (110a, 110b, 115a, 115b); - one or more network element management functions (120a, 120b), each network element management function being responsible for managing a corresponding group of network elements in the plurality of network elements; - at least one operation support system (130-1, 130-2, 130-N) of at least one corresponding telecommunications operator, The features include: - A communication intermediary processor (135) according to any one of claims 6 to 11, the communication intermediary processor is located between the network element management function and the at least one operation support system of the at least one telecommunications operator, and the communication intermediary processor is configured to intermediary the communication by filtering the communication between the operation support system and the network element management function according to predetermined filtering criteria (140) to allow the operation support system to manage only the corresponding part of the network element of the access network depending on the filtering criteria.

Citation Information

Patent Citations

  • A network and method for sharing radio access nodes between core networks

    CA2521224A1

  • O&M Counters for Ran Sharing and Inter-Operator Billing

    EP2477427A1

  • System and method for controlling network

    EP3059903A1

  • Multiplexing Core Networks in RAN Sharing

    US20140348068A1

  • Multiple operator radio access network (MORAN) in a telecommunications system

    WO2014053597A1