Method, device and computer program

By receiving and analyzing alarm-related information in the communication system, identifying and solving alarm failure problems, providing fault reports and recovery suggestions, network security and operational problems caused by alarm failure and malicious activities are solved, and the trust of the system is improved. Level of automation.

CN116458118BActive Publication Date: 2024-11-15ALCATEL LUCENT SHANGHAI BELL CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080106983.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-10-01
Publication Date
2024-11-15
Estimated Expiration
2040-10-01

AI Technical Summary

Technical Problem

In existing communication systems, alarm agents or management service producers may fail when generating alarms, resulting in false positive or false negative alarms, affecting the operation and security of network automation, and existing solutions fail to effectively detect and Resolve alarm failure issues, especially malicious activities related to alarm generation.

Method used

Receive information from adjacent entities of network objects or management objects at the service provider, determine fault information related to generating alarms, and provide service consumers with reports based on fault information, including fault type, location, severity level and resolution, to the service provider The solution is to assess the risk of alarm failure through MDAS analysis services, identify the failure problems of agent or management service producers, and identify the source of failure through multi-level data tracking and metadata, providing recovery advice.

Benefits of technology

Effectively detect and resolve alarm failure problems, improve alarm trust and network security, avoid false positive and false negative alarms, ensure the autonomous operation and security of the network, and be able to independently resolve faults and malicious activities within different automation levels. The alarm fails.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116458118B_ABST
    Figure CN116458118B_ABST
Patent Text Reader

Abstract

A device is provided, comprising components for performing the following at a service provider: receiving information from at least one neighboring entity of a network object or a management object, wherein the network object or the management object has generated an alarm; determining, based on the information, fault information associated with the network object or the management object that generated the alarm; and providing a report based on the fault information to a service consumer.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to a method, apparatus, system, and computer program, and particularly, but not exclusively, to alarm failure detection and resolution. Background Art

[0002] A communication system can be viewed as a facility that enables communication sessions between two or more entities such as user terminals, base stations, and / or other nodes by providing carriers between various entities involved in a communication path. For example, a communication system can be provided by means of a communication network and one or more compatible communication devices (also referred to as stations or user equipment) and / or application servers. A communication session may include, for example, communications for carrying data for communication, such as voice, video, electronic mail (email), text messages, multimedia, content data, time-sensitive network (TSN) streams, and / or data in industrial applications, such as key system messages between actuators and controllers, key sensor data (such as measurements, video feeds, etc.) toward a control system, etc. Non-limiting examples of the services provided include two-way or multi-way calls, data communications or multimedia services, and access to data network systems (such as the Internet).

[0003] In a wireless communication system, at least a portion of a communication session, e.g. between at least two stations or between at least one station and at least one application server (e.g. for video), occurs over a wireless link. Examples of wireless systems include public land mobile networks (PLMNs) operating based on 3GPP radio standards, such as E-UTRA, New Radio, satellite-based communication systems, and different wireless local area networks, such as wireless local area networks (WLANs). Wireless systems can typically be divided into cells and are therefore often referred to as cellular systems.

[0004] A user can access the communication system with the aid of an appropriate communication device or terminal. The user's communication device may be referred to as a user equipment (UE) or user equipment. The communication device is provided with appropriate signal receiving and transmission means to enable communication, for example, to enable access to a communication network or to communicate directly with other users. The communication device may access one or more carriers provided by the network, such as a base station of a cell, and transmit and / or receive communications on one or more carriers. In carrier aggregation (CA), two or more carriers are combined into one channel. In dual connectivity (DC), two carriers from different sites are combined, that is, the user equipment may be dual (or multi) connected to two (or more) sites.

[0005] A communication system and associated equipment typically operate according to a given standard or specification that specifies what the various entities associated with the system are allowed to do and how it should be implemented. Communication protocols and / or parameters that should be used for the connection are also typically defined. An example of a communication system is UTRAN (3G radio). Other examples of communication systems are the Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) based on E-UTRAN radio access technology, and the so-called 5G System (5GS) including 5G or Next Generation Core (NGC) and 5G Access Network based on New Radio (NR) radio access technology. 5GS, including NR, is being standardized by the Third Generation Partnership Project (3GPP). Summary of the invention

[0006] In a first aspect, a device is provided, comprising components for performing the following at a service provider: receiving information from at least one neighboring entity of a network object or a management object, wherein the network object or the management object has generated an alarm; determining, based on the information, fault information associated with the network object or the management object that generated the alarm; and providing a report based on the fault information to a service consumer.

[0007] The report may include an indication of at least one of: a fault type, a fault location, a network object or management object identity, a fault severity level, and a proposed action to resolve the fault.

[0008] The information from the at least one neighboring entity may include metadata identifying a source of the information.

[0009] The means for determining may include means for determining missing or erroneous data based on at least one of historical data and information from at least one neighboring entity.

[0010] A network object or management object may include an alarm agent or a management service producer.

[0011] Management service producers may include fault monitoring functions, fault management functions, or performance management functions.

[0012] The at least one neighboring entity may be at the same or a different automation level as the network object or the management object.

[0013] The information from at least one neighboring entity may relate to another alarm, one of an alarm, an event, and a heartbeat for a given resource or link, or one of an alarm and an event from a neighboring entity.

[0014] The at least one neighboring entity may include a network element, a management function, or a management service producer.

[0015] In a second aspect, a method is provided, comprising: at a service provider: receiving information from at least one neighboring entity of a network object or a management object, wherein the network object or the management object has generated an alarm; based on the information, determining fault information associated with the network object or the management object that generated the alarm; and providing a report based on the fault information to a service consumer.

[0016] The report may include an indication of at least one of: a fault type, a fault location, a network object or management object identity, a fault severity level, and a proposed action to resolve the fault.

[0017] The information from the at least one neighboring entity may include metadata identifying a source of the information.

[0018] Determining may include determining missing or erroneous data based on at least one of historical data and information from at least one neighboring entity.

[0019] A network object or management object may include an alarm agent or a management service producer.

[0020] Management service producers may include fault monitoring functions, fault management functions, or performance management functions.

[0021] The at least one neighboring entity may be at the same or a different automation level as the network object or the management object.

[0022] The information from at least one neighboring entity may relate to another alarm, one of an alarm, an event, and a heartbeat for a given resource or link, or one of an alarm and an event from a neighboring entity.

[0023] The at least one neighboring entity may include a network element, a management function, or a management service producer.

[0024] In a third aspect, a device is provided, comprising: at least one processor and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, enable the device, at least at a service provider, to: receive information from at least one neighboring entity of a network object or a management object, wherein the network object or the management object has generated an alarm; based on the information, determine fault information associated with the network object or the management object that generated the alarm; and provide a report based on the fault information to a service consumer.

[0025] The report may include an indication of at least one of: a fault type, a fault location, a network object or management object identity, a fault severity level, and a proposed action to resolve the fault.

[0026] The information from the at least one neighboring entity may include metadata identifying a source of the information.

[0027] The apparatus may be configured to determine missing or erroneous data based on at least one of historical data and information from at least one neighboring entity.

[0028] A network object or management object may include an alarm agent or a management service producer.

[0029] Management service producers may include fault monitoring functions, fault management functions, or performance management functions.

[0030] The at least one neighboring entity may be at the same or a different automation level as the network object or the management object.

[0031] The information from at least one neighboring entity may relate to another alarm, one of an alarm, an event, and a heartbeat for a given resource or link, or one of an alarm and an event from a neighboring entity.

[0032] The at least one neighboring entity may include a network element, a management function, or a management service producer.

[0033] A computer-readable medium includes program instructions for causing a device to perform at least the following items at a service provider: receiving information from at least one neighboring entity of a network object or a management object, wherein the network object or the management object has generated an alarm; based on the information, determining fault information associated with the network object or the management object that generated the alarm; and providing a report based on the fault information to a service consumer.

[0034] The report may include an indication of at least one of: a fault type, a fault location, a network object or management object identity, a fault severity level, and a proposed action to resolve the fault.

[0035] The information from the at least one neighboring entity may include metadata identifying a source of the information.

[0036] The apparatus may be caused to determine missing or erroneous data based on at least one of historical data and information from at least one neighboring entity.

[0037] A network object or management object may include an alarm agent or a management service producer.

[0038] Management service producers may include fault monitoring functions, fault management functions, or performance management functions.

[0039] The at least one neighboring entity may be at the same or a different automation level as the network object or the management object.

[0040] The information from at least one neighboring entity may relate to another alarm, one of an alarm, an event, and a heartbeat for a given resource or link, or one of an alarm and an event from a neighboring entity.

[0041] The at least one neighboring entity may include a network element, a management function, or a management service producer.

[0042] In a fourth aspect, a non-transitory computer-readable medium is provided, the non-transitory computer-readable medium comprising program instructions for causing an apparatus to at least perform the method according to the second aspect.

[0043] In the above, many different embodiments have been described. It should be understood that further embodiments can be provided by combining any two or more of the above embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0045] Figure 1 A schematic diagram of an example 5GS communication system is shown;

[0046] Figure 2 A schematic diagram of an example mobile communication device is shown;

[0047] Figure 3 A schematic diagram of an example control device is shown;

[0048] Figure 4 A schematic diagram showing an example MDA functional overview and architecture;

[0049] Figure 5 shows example levels of automation in network management;

[0050] Figure 6 A flow chart showing a method according to an example embodiment is shown;

[0051] Figure 7 shows the signaling flow of an example alarm malfunction risk assessment process;

[0052] Figure 8 A schematic diagram showing multi-level data tracking for backtracking alarms of MnS producer mismatches. DETAILED DESCRIPTION

[0053] Before explaining the examples in detail, we will refer to Figures 1 to 3 Certain general principles of wireless communication systems and mobile communication devices are briefly explained to aid understanding of the technology underlying the described examples.

[0054] An example of a suitable communication system is a 5G system (5GS). The network architecture in 5GS may be similar to that of advanced LTE. The base station of the NR system may be referred to as a next generation Node B (gNB). Changes to the network architecture may depend on the need to support various radio technologies and more sophisticated QoS support, as well as some on-demand requirements for QoS levels such as supporting QoE from a user perspective. In addition, network-aware services and applications, as well as service- and application-aware networks may bring changes to the architecture. These are all related to the user-centric content delivery network (UC-CDN) approach. NR may use multiple-input multiple-output (MIMO) antennas, many more base stations or nodes than LTE (the so-called small cell concept), including macro sites that operate in cooperation with smaller stations, and may also employ various radio technologies to achieve better coverage and enhanced data rates.

[0055] 5G networks can utilize network function virtualization (NFV), which is a network architecture concept that proposes virtualizing network functions that can be operably connected or linked together to provide services. A virtualized network function (VNF) may include one or more virtual network function components that run computer program code in a virtual machine or container using a standard or general-purpose type of server rather than customized hardware. Cloud computing or data storage may also be utilized. In radio communications, this may mean that the network function operations are at least partially performed in a server, host, or node that is operably coupled to a remote radio head. The network function operations may also be distributed among multiple servers, nodes, or hosts. It should also be understood that the distribution of labor between core network operations and base station operations may be different from LTE, or even non-existent.

[0056] Figure 1 A schematic representation of a 5G system (5GS) 100 is shown. The 5GS may include a user equipment (UE) 102 (which may also be referred to as a communication device or terminal), a 5G radio access network (5GRAN) 104, a 5G core network (5GCN) 106, one or more application functions (AFs) 108, and one or more data networks (DNs) 110.

[0057] An example 5G core network (CN) includes functional entities. The 5GCN 106 may include one or more access and mobility management functions (AMFs) 112, one or more session management functions (SMFs) 114, an authentication server function (AUSF) 116, a unified data management (UDM) 118, one or more user plane functions (UPFs) 120, a unified data repository (UDR) 122, and / or a network exposure function (NEF) 124. The UPF is controlled by the SMF (session management function), which receives policies from the PCF (policy control function).

[0058] The CN is connected to a terminal, such as a UE, via a radio access network (RAN). A 5G RAN may include one or more gNodeB (GNB) distributed unit functions connected to one or more gNodeB (GNB) centralized unit functions. A RAN may include one or more access nodes.

[0059] The UPF (User Plane Function) whose role is called PSA (PDU Session Anchor) can be responsible for forwarding frames back and forth between the DN (Data Network) and the tunnel established by 5G towards (multiple) UEs that exchange services with the DN.

[0060] Now refer to Figure 2 Describing in more detail a possible mobile communication device, Figure 2 A schematic partial cross-sectional view of a communication device 200 is shown. Such a communication device is generally referred to as a user equipment (UE) or terminal. Suitable mobile communication devices can be provided by any device capable of sending and receiving radio signals. Non-limiting examples include a mobile station (MS) or mobile device, such as a mobile phone or a so-called "smart phone", a computer equipped with a wireless interface card or other wireless interface facilities (e.g., a USB dongle), a personal data assistant (PDA) or a tablet computer equipped with wireless communication capabilities, or any combination of these, etc. For example, a mobile communication device can provide communications for carrying data such as voice, e-mail (email), text messages, multimedia, etc. Therefore, users can be provided with many services via their communication devices. Non-limiting examples of these services include two-way or multi-way calls, data communications or multimedia services, or simply access to a data communication network system (such as the Internet). Users can also be provided with broadcast or multicast data. Non-limiting examples of content include downloads, television and radio programs, videos, advertisements, various alarms, and other information.

[0061] The mobile device is typically provided with at least one data processing entity 201, at least one memory 202, and other possible components 203 for software and hardware-assisted execution of the tasks it is designed to perform, including controlling access to and communication with access systems and other communication devices. Data processing, storage, and other related control devices can be provided on appropriate circuit boards and / or in chipsets. This feature is represented by reference numeral 204. The user can control the operation of the mobile device with the aid of a suitable user interface such as a keypad 205, voice commands, a touch-sensitive screen or keyboard, or a combination thereof. A display 208, a speaker, and a microphone may also be provided. In addition, the mobile communication device may include appropriate connectors (wired or wireless) to other devices and / or for connecting external accessories (e.g., a hands-free device) to it.

[0062] The mobile device 200 may receive signals over the air or radio interface 207 via appropriate means for receiving, and may transmit signals via appropriate means for transmitting radio signals. Figure 2 In the mobile device, the transceiver arrangement is schematically represented by block 206. The transceiver arrangement 206 may be provided, for example, by means of a radio component and an associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

[0063] Figure 3 An example embodiment of a control device for a communication system is shown, for example, the control device is to be coupled to and / or used to control a station (such as a RAN node, such as a base station, eNB or gNB), a relay node or a core network node (such as an MME or S-GW or P-GW), or a core network function (such as an AMF / SMF), or a server or host of an access system. The method can be implemented in a single control device or across more than one control device. The control device can be integrated with a node or module of the core network or RAN, or external to it. In some embodiments, the base station includes a separate control device unit or module. In other embodiments, the control device can be another network element, such as a radio network controller or a spectrum controller. In some embodiments, each base station can have such a control device, and a control device arranged in a radio network controller. The control device 300 can be arranged to provide control of communications in a service area of ​​the system. The control device 300 includes at least one memory 301, at least one data processing unit 302, 303, and an input / output interface 304. Via the interface, the control device can be coupled to a receiver and a transmitter of the base station. The receiver and / or the transmitter may be implemented as a radio front end or a remote radio head.

[0064] The following relates to network fault and security management, where a set of alarms at different levels (e.g., automation levels) are deployed to ensure normal network operation. It particularly relates to the following scenario: in the context of a service-based management architecture (SBMA) that collects security and alarm data, network elements may host alarm and other monitoring agents or management service (MnS) producers, such as performance measurement (PM) and fault supervision / fault management (FS / FM). Such data from various sources may achieve different degrees of data correlation, such as correlation from one source to another, and / or correlation with other data knowledge, such as expected values ​​for a given date and time instance. If the results of such correlation process exceed the expected level, an alarm regarding the corresponding fault or security incident may be triggered.

[0065] In 3GPP SA5 data analytics, i.e., Managed Data Analytics Service (MDAS), TR 28.809 introduces use cases for alarm incident analytics as part of network fault management, as well as use cases for security analytics.

[0066] An overview of the example Management Data Analysis (MDA) functionality and architecture is shown in Figure 4 As shown, Figure 4 Shown are analytics (ie, analytic models that may be proprietary), various types of input sources (eg, MnS Producers, MDAS Producers, and Network Data Analysis Functions (NWDAFs)), and MDAS Producer outputs toward MDAS Consumers.

[0067] MDAS can be applied to different management architecture levels, such as Figure 5 As shown, Figure 5 A network element (NE) level, a domain level, an inter-domain level, and a service level are shown. Each level operates independently in parallel while interacting by exchanging analysis data between directly adjacent automation levels.

[0068] However, the corresponding alarm agents or producers of PM and FS / FM management services (ie, FS / FMMnS producers) may not always be trusted when an alarm is triggered.

[0069] There are cases where the alert agent triggers an alert when it is not needed (i.e., a false positive alert), and there are cases where the alert does not trigger even though it should have, i.e., a false negative alert.

[0070] Alarm failures can be related to:

[0071] a) A security breach where the alarm agent is hacked. As a result, the output of the correlator is maliciously tampered with, resulting in untrustworthy data.

[0072] b) Improper behavior of the alarm agent due to non-human faults, i.e., failure of the alarm agent’s software / hardware and / or failure of the corresponding MnS of the NE or MnF.

[0073] For the reasons stated above, failure and trust in the data collected by the alarm agent may affect the operation, security, and correctness of network automation. Therefore, there is a need to increase the level of trust in the alarm agent (or, in general, the correlator in the event) and the corresponding data collected. Such an increased level of trust should be assured to the network in an autonomous manner at different operational levels, i.e., without the need for human intervention.

[0074] The following relates to alarm failure issues, namely FMIRPAgent according to TS 28.545, TS 28.517, TS 32.111, alarm failure associated with MnS producers in SBMA, and alarm failure associated with MDAS (e.g. according to TS 28.809), all considered in the context of autonomous networks.

[0075] Fault management is a fundamental issue in mobile network management and has been addressed since the early stages of Self-Organizing Networks (SON) TS 28.628, TS 32.522, TS 28.313, and especially with regard to Self-Healing TS 32.541, where monitoring from various network elements enables SON functions to autonomously detect and repair / optimize the network configuration.

[0076] A further step towards more complex systems is contemplated via the alarm correlation concept in TR 32.832, where certain alarms are grouped together to achieve an understanding of the network failure being faced and root cause analysis can point to the source of the problem.

[0077] Fault management and alarm correlation are also considered in US7525422B2, focusing on the combination of alarms with certain alarms to trigger other alarms to create a comprehensive diagnosis. A topology-based reasoning device for root cause analysis of network failures is proposed in EP1279211B1, in which the system determines the root cause failure indicated by at least one alarm. Alarm correlation in a network function virtualization environment is discussed in US20170346676A1, by forwarding at least one of the related alarms to an upper-layer entity that manages the network function virtual environment for further correlation with the upper-layer alarm. Event correlation across heterogeneous operations with security considerations is introduced in US20160301709A1.

[0078] All of these works consider correlating and / or combining alerts to create a comprehensive view of the problem and investigate root cause analysis to identify the source of the problem across different technologies taking into account both fault management and security. However, none of these solutions consider the case where the agent providing the alert fails or there is malicious activity associated with the generation of the alert and how to detect and resolve the problem.

[0079] Figure 6 A flow chart of a method according to an example embodiment is shown.

[0080] In a first step S1 , the method comprises receiving, at a service provider, information from at least one neighboring entity of a network object or a management object, wherein the network object or the management object has generated an alarm.

[0081] In a second step S2, the method comprises determining, based on the information, fault information associated with the network object or management object generating the alarm.

[0082] In a third step S3, the method comprises providing a report based on the fault information to a service consumer.

[0083] The method provides an MDAS-based analysis service for evaluating the failure of an agent or MnS producer providing an alarm or PM, FS / FM due to faults or malicious activities. Such an analysis service can identify agent or MnS producer failure issues associated with reporting fault alarms, such as fault alarms associated with inconsistent performance and fault information between neighboring network elements (NEs) (e.g., cells) or MnS / MnFs.

[0084] A network object or management object may include, but is not limited to, an alarm agent or MnS producer, such as a fault supervision function, a fault management function, or a performance management function.

[0085] The service provider may be an MDAS provider, and the service consumer may be an MDAS consumer.

[0086] The at least one neighboring entity may include a network element, a MnF or a MnS producer.

[0087] The at least one neighboring entity may be at the same or a different automation level as the network object or the management object.

[0088] Alarm Failure Risk Assessment MDAS can select and correlate PM / FS data and / or Key Performance Indicators (KPIs) (based on TS 28.552 and TS 28.554) from a specific NE or Management Function (MnF) and across different automation levels in order to check consistency between neighboring Agents or MnSs. For example, if an Agent or MnS reports high mobility towards a specific neighboring cell, and that specific cell reports low user density, this may be an indication of a failure risk to be investigated. Local analysis can be combined with broader regional analysis to facilitate root cause analysis.

[0089] Information from at least one neighboring entity may relate to another alarm, one of an alarm, event, and heartbeat for a given resource or link, or one of an alarm and event from a neighboring entity. The Alarm Failure Risk Assessment MDAS may correlate alarms or performance information from other alarms, alarms / events / heartbeats related to a specific resource or link, alarms / events from neighboring NE / NF and / or MnS / MnF.

[0090] Table 1 shows an example of data that the information from at least one neighboring entity may include.

[0091]

[0092]

[0093] Table 1

[0094] Information from at least one adjacent entity may include: metadata identifying the source of the information. Multi-level metadata may be used to identify the source of an alarm agent or the source of an MnS producer, which is used to trace back (multiple) failed alarm agents or MnS producers. Multiple levels of metadata in PM, FS / FM, and performance KPI reports may be introduced to enable tracking (i.e., tracing back) the source of failed agents or MnS producers across various MDAS levels (including domain level, cross-domain level, or even service level), although data processing is performed through analysis at each individual MDAS level. The alarm agent or MnS producer is associated with the data source so that the failure point or security incident is tracked.

[0095] The means for determining fault information may include means for determining missing or erroneous data based on at least one of historical data and information from at least one neighboring entity. That is, the missing or erroneous data (e.g., data value) may be recovered using a value estimation mechanism based on the use of historical data, optionally in combination with neighboring data.

[0096] The Alarm Failure Risk Assessment MDAS can be associated with FS / FM control / reporting related configurations, such as filters, subscribers, notifications, clear alarms, acknowledge alarms, etc.

[0097] The report may include an indication of at least one of the following: the type of fault, the location of the fault, the network object or management object identity, the fault severity level, and a proposed action to resolve the fault. For example, an analysis report may be generated toward an MDAS consumer, i.e., an application programming interface (API), the analysis report identifying the type of failure, the location, the network object or management object involved, the severity level, and a recommended action, such as isolating the fault agent, MnS producer, and / or NE.

[0098] Table 2 provides further details of the type of information that may be included in the report. The fault type may be a security incident identifier. The network object or management object identity may be an identifier of the affected object, such as NF, MnS, MnF, protocol data unit (PDU) session, quality of service (QoS) flow, slice identifier. The severity level may be an incremental indicator, such as critical, medium, unimportant. The information may include an indication of the start / stop time of the fault. The information may include an indication of the failed source agent or MnS producer to isolate and recover the failed agent or MnS producer. The proposed actions may be, but are not limited to: isolating / terminating the failed agent or MnS producer and recovering data based on neighbor data.

[0099] In an example embodiment, the MDAS for evaluating the failure of a proxy or MnS may perform the corresponding data association between the failure, virtualization, and NF context, and provide the following recommendation to introduce a new interface containing the attributes shown in Table 2 to the service consumer.

[0100]

[0101] Table 2

[0102] Figure 7 A flow chart of an example alarm failure risk assessment process is shown. The MDAS consumer requests analysis from the MDAS producer, which requests and collects performance measurements in the corresponding MnS and / or MDAS producer in steps 2 and 3, respectively. In steps 4 and 5, the MDAS performs the analysis and provides recommendations based on the analysis. Then in step 6, a report is provided to the MDAS consumer using an interface with properties as described in reference table 2.

[0103] Figure 8 A schematic representation of multi-level data tracking for backtracking alarms or MnS producer mismatches according to an example embodiment is shown. In this example, multi-level metadata for backtracking is deployed in different spatial regions or domains. The process of backtracking is part of the MDAS in the corresponding automation level.

[0104] Management agents (e.g., Integration Reference Point (IRP) agents) or MnS producers or MDAS may be deployed on NEs and / or at relatively large scales (i.e., domains), even across domains. The MDAS cross-domain or scope area 801 traceback process portion may identify data mismatches from data inputs from data traceback processes of different domains 802 (e.g., different cities). Within each domain, multiple local data agents or MnS producers deployed at the NE level 803 introduce metadata for traceback of various measurements, such as PM and FS / FM, performance key performance indicators (KPIs), or local data analytics.

[0105] The use cases and solutions related to fault management issues documented in TR 28.809 can be enhanced by leveraging the benefits of analytics, and new solutions related to alarm broker and / or MnS producer security can also be introduced. Such solutions can not only identify and avoid false positives and false negatives, but also track and resolve the “root cause and object” that caused it.

[0106] refer to Figures 6 to 8 The described method provides an alarm failure risk assessment MDAS that can address the problem of faulty alarms due to agent or MnS producer failure or malicious activity of the agent or MnS producer associated with the alarm generation.

[0107] The method can be applied to various alarm failures, such as false / missed alarms / events, which may be caused by different factors, such as misoperation, ineffectiveness, human factors, etc., and can also be applied to different stages, such as making an alarm subscription, generating an alarm, generating an alarm notification, reporting an alarm, making an alarm confirmation or clearing, etc. Therefore, data input and root cause analysis are considered at each stage.

[0108] This method can be found in the reference Figure 3 The control device described is implemented in the embodiment of the present invention.

[0109] An apparatus may include components for performing the following at a service provider: receiving information from at least one neighboring entity of a network object or a management object, wherein the network object or the management object has generated an alarm; determining, based on the information, fault information associated with the network object or the management object that generated the alarm; and providing a report based on the fault information to a service consumer.

[0110] It should be understood that the apparatus may include or be coupled to other units or modules, such as a radio component or radio head for transmission and / or reception. Although the apparatus have been described as one entity, the different modules and memories may be implemented in one or more physical or logical entities.

[0111] Note that although embodiments have been described with respect to LTE and 5G NR, similar principles may be applied to other networks and communication systems. Thus, although certain embodiments are described above by way of example with reference to certain example architectures for wireless networks, technologies, and standards, the embodiments may also be applied to any other suitable form of communication system other than those illustrated and described herein.

[0112] It is also noted herein that while exemplary embodiments are described above, there are several variations and modifications which may be applied to the disclosed solution without departing from the scope of the present invention.

[0113] In general, the various example embodiments may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects of the invention may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, but the invention is not limited thereto. Although various aspects of the invention may be illustrated and described as block diagrams, flow charts, or using some other graphical representation, it is well understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general purpose hardware or controllers or other computing devices, or some combination thereof.

[0114] Embodiments of the present invention may be implemented by computer software that can be executed by a data processor of a mobile device, such as in a processor entity, or by hardware, or by a combination of software and hardware. Computer software or programs (also referred to as program products, including software routines, applets and / or macros) may be stored in any device-readable data storage medium, and they include program instructions for performing specific tasks. A computer program product may include one or more computer executable components that are configured to perform an embodiment when the program is run. One or more computer executable components may be at least one software code or a portion thereof.

[0115] Furthermore, it should be noted at this point that any block of the logic flow in the figure may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on physical media such as memory chips or memory blocks implemented within a processor, magnetic media such as hard disks or floppy disks, and optical media such as DVDs and their data variants CDs. Physical media is a non-transitory medium.

[0116] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and may include, as non-limiting examples, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, a gate-level circuit, and a processor based on a multi-core processor architecture.

[0117] Example embodiments of the present invention may be practiced in various components such as integrated circuit modules. The design of integrated circuits is generally a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

[0118] The foregoing description provides a complete and informative description of exemplary embodiments of the present invention by way of non-limiting examples. However, various modifications and adaptations may become apparent to those skilled in the relevant art in view of the foregoing description when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of the present invention will still fall within the scope of the present invention as defined in the appended claims. Indeed, there are other embodiments that may include a combination of one or more embodiments with any other embodiment discussed above.

Claims

1. An apparatus comprising means for performing, at a service provider: receiving information from at least one neighboring entity of a network object or a management object, wherein the network object or the management object has generated an alarm; determining, based on the information, fault information associated with the network object or the management object that generated the alarm; as well as providing a report based on the fault information to a service consumer; wherein the information from at least one neighboring entity includes metadata identifying a source of the information; The means for determining includes means for determining missing or erroneous data using a value estimation mechanism based on at least one of historical data and the information from the at least one neighboring entity.

2. The apparatus of claim 1, wherein the report includes an indication of at least one of: a fault type, a fault location, a network object or management object identity, a fault severity level, and a proposed action to resolve the fault.

3. The apparatus according to claim 1 or 2, wherein the network object or the management object comprises an alarm agent or a management service producer.

4. The apparatus of claim 3, wherein the management service producer comprises a fault monitoring function, a fault management function, or a performance management function. 5 . The apparatus according to claim 1 , wherein the at least one neighboring entity is at the same or different automation level as the network object or the management object.

6. An apparatus according to any one of claims 1 to 5, wherein the information from the at least one neighboring entity relates to another alarm, one of an alarm, an event, and a heartbeat for a given resource or link, or one of an alarm and an event from the neighboring entity.

7. The apparatus according to any one of claims 1 to 6, wherein the at least one neighboring entity comprises a network element, a management function, or a management service producer.

8. A method comprising, at a service provider: receiving information from at least one neighboring entity of a network object or a management object, wherein the network object or the management object has generated an alarm; determining, based on the information, fault information associated with the network object or the management object that generated the alarm; as well as providing a report based on the fault information to a service consumer; wherein the information from at least one neighboring entity includes metadata identifying a source of the information; Determining the fault information includes: determining missing or erroneous data using a value estimation mechanism based on at least one of historical data and the information from the at least one neighboring entity.

9. An apparatus comprising: at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the apparatus, at a service provider, to at least: receiving information from at least one neighboring entity of a network object or a management object, wherein the network object or the management object has generated an alarm; determining, based on the information, fault information associated with the network object or the management object that generated the alarm; as well as providing a report based on the fault information to a service consumer; wherein the information from at least one neighboring entity includes metadata identifying a source of the information; Determining the fault information includes: determining missing or erroneous data using a value estimation mechanism based on at least one of historical data and the information from the at least one neighboring entity.

10. A computer-readable medium comprising program instructions for causing an apparatus to perform at least the following at a service provider: receiving information from at least one neighboring entity of a network object or a management object, wherein the network object or the management object has generated an alarm; determining, based on the information, fault information associated with the network object or the management object that generated the alarm; as well as providing a report based on the fault information to a service consumer; wherein the information from at least one neighboring entity includes metadata identifying a source of the information; Determining the fault information includes: determining missing or erroneous data using a value estimation mechanism based on at least one of historical data and the information from the at least one neighboring entity.