Communication device, method, and non-transitory computer-readable storage medium for displaying alarm

Abstract

This communication device may comprise: a display; a communication circuit; a memory storing instructions; and at least one processor comprising processing circuitry. The instructions, when individually or collectively executed by the at least one processor, may cause the communication device to: register at least one NE in the communication device; continuously receive, from the at least one NE, system logs of the at least one NE; in response to a user input, generate a condition related to the system logs and an alarm corresponding to the condition; while the system logs of the at least one NE are continuously received, determine whether a target system log satisfying the condition is detected from among the system logs of the at least one NE; and according to a determination that the target system log is detected from among the system logs of the at least one NE, display, through the display, the alarm corresponding to the condition.

Description

Communication device, method, and non-transient computer-readable storage medium for displaying a notification

[0001] The present disclosure relates to a communication device, a method, and a non-transient computer-readable storage medium for displaying a notification.

[0002] To meet the demand for wireless data traffic, 5G (5th generation) communication systems and NR (new radio or next radio) are being commercialized. 5G communication systems provide users with high data transmission rate services, similar to 4G (4th generation) communication systems. With the introduction of 5G communication systems, the number of network equipment has increased exponentially. As the number of network equipment increases, various measures are being proposed to manage abnormal conditions of network equipment.

[0003] The information described above may be provided as related art for the purpose of aiding understanding of the present disclosure. No claim or determination is made as to whether any of the foregoing may be applied as prior art related to the present disclosure.

[0004] A communication device configured to perform the function of a software defined network (SDN) controller is provided. The communication device may include a display. The communication device may include a communication circuit. The communication device may include a memory comprising one or more storage media for storing instructions. The communication device may include at least one processor comprising a processing circuitry. The instructions may cause the communication device to register at least one network element (NE) to the communication device based on identification information transmitted from at least one network element (NE) when executed individually or collectively by the at least one processor. The instructions may cause the communication device to continuously receive system logs of the at least one NE from the at least one NE through the communication circuit after registering the at least one NE when executed individually or collectively by the at least one processor. When the above instructions are executed individually or collectively by the at least one processor, they may cause the communication device to generate a condition related to a system log and a notification corresponding to the condition in response to user input. When the above instructions are executed individually or collectively by the at least one processor, they may cause the communication device to determine whether a target system log satisfying the condition is detected among the system logs of the at least one NE while the system logs of the at least one NE are continuously received.When the above instructions are executed individually or collectively by the at least one processor, the communication device may cause the notification corresponding to the condition to be displayed through the display in accordance with the determination that the target system log is detected among the system logs of the at least one NE. When the above instructions are executed individually or collectively by the at least one processor, the communication device may cause the notification corresponding to the condition to be withheld in accordance with the determination that the target system log is not detected among the system logs of the at least one NE.

[0005] A method is provided. The method may be performed in a communication device having a display and a communication circuit. The communication device may be configured to perform the function of an SDN controller. The method may include an operation of registering the at least one NE to the communication device based on identification information transmitted from at least one NE. After registering the at least one NE, the method may include an operation of continuously receiving the system log of the at least one NE from the at least one NE through the communication circuit. The method may include an operation of generating a condition related to the system log and an alert corresponding to the condition in response to user input. The method may include an operation of determining whether a target system log satisfying the condition is detected among the system logs of the at least one NE while the system log of the at least one NE is continuously received. The method may include an operation of displaying the alert corresponding to the condition through the display based on the determination that the target system log is detected among the system logs of the at least one NE. The above method may include an operation of refraining from displaying the notification corresponding to the condition based on a determination that the target system log is not detected among the system logs of the at least one NE.

[0006] A non-transient computer-readable storage medium is provided. The non-transient computer-readable storage medium may store one or more programs. The one or more programs may include instructions that cause the communication device to register the at least one network element (NE) to the communication device based on identification information transmitted from at least one NE, when executed by the communication device, which has a display and a communication circuit and is configured to perform the function of an SDN controller. The one or more programs may include instructions that cause the communication device to continuously receive the system log of the at least one NE from the at least one NE through the communication circuit after registering the at least one NE when executed by the communication device. The one or more programs may include instructions that cause the communication device to generate a condition related to the system log and a notification corresponding to the condition in response to user input when executed by the communication device. The above one or more programs may include instructions that cause the communication device to determine whether a target system log satisfying the condition is detected among the system logs of the at least one NE while the system logs of the at least one NE are continuously received when executed by the communication device. The above one or more programs may include instructions that cause the communication device to display the notification corresponding to the condition through the display, upon the determination that the target system log is detected among the system logs of the at least one NE when executed by the communication device.The above one or more programs may include instructions that cause the communication device to refrain from displaying the notification corresponding to the condition, based on the determination that the target system log is not detected among the system logs of the at least one NE when executed by the communication device.

[0007] FIG. 1 is a block diagram of an electronic device in a network environment according to one embodiment.

[0008] Figure 2 illustrates an example of a software defined network (SDN) architecture.

[0009] Figure 3 illustrates an example of a simplified block diagram of a communication device.

[0010] FIG. 4 illustrates examples of components of a communication device for providing notifications based on system logs of multiple network elements (NEs).

[0011] Figure 5 illustrates examples of the operations of a communication device.

[0012] Figure 6 illustrates an example of a user interface displayed on a communication device.

[0013] Figure 7 illustrates an example of a user interface for changing system log collection settings.

[0014] FIG. 8 illustrates an example of a user interface for generating a notification corresponding to a condition and condition related to a system log.

[0015] FIG. 9 illustrates an example of a user interface showing a list of conditions generated according to user input and notifications corresponding to the conditions.

[0016] Figure 10 illustrates an example of a user interface displaying a list of notifications.

[0017] Throughout the drawings, the same reference numerals will be understood to refer to the same parts, components, and structures.

[0018] The terms used in this disclosure are used merely to describe specific embodiments and are not intended to limit the scope of other embodiments. A singular expression may include a plural expression unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as generally understood by those skilled in the art described in this disclosure. Terms used in this disclosure that are defined in a general dictionary may be interpreted as having the same or similar meaning as they have in the context of the relevant technology, and are not to be interpreted in an ideal or overly formal sense unless explicitly defined in this disclosure. In some cases, even terms defined in this disclosure are not to be interpreted to exclude the embodiments of this disclosure.

[0019] In the various embodiments of the present disclosure described below, a hardware-based approach is described as an example. However, since the various embodiments of the present disclosure include techniques using both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.

[0020] Terms used in the following description to refer to data (e.g., data, information, system log), terms for operation states (e.g., operation, process), terms to refer to objects (e.g., visual object, list), terms to refer to network entities (e.g., NE (network element), switch, router, RU (radio unit), DU (distributed unit), SDN (software defined network) controller, server, virtual NE), and terms to refer to device components are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used. Additionally, terms such as '...part', '...device', '...object', '...body' used below may refer to at least one structural form or a unit that processes a function.

[0021] Additionally, in this disclosure, expressions of "greater than" or "less than" may be used to determine whether a specific condition is satisfied or fulfilled; however, this is merely for the purpose of expressing an example and does not exclude descriptions of "greater than" or "less than." Conditions described as "greater than" may be replaced with "greater than," conditions described as "less than" may be replaced with "less than," and conditions described as "greater than and less than" may be replaced with "greater than and less than." Furthermore, "A" to "B" below refer to at least one of elements from A (including A) to B (including B). Below, "C" and / or "D" refers to including at least one of "C" or "D," i.e., {"C", "D", "C" and "D"}.

[0022] This disclosure describes various embodiments using terms used in some communication standards (e.g., 3GPP (3rd Generation Partnership Project), ETSI (European Telecommunications Standards Institute), xRAN (extensible radio access network), O-RAN (open-radio access network), but these are merely illustrative examples. Various embodiments of this disclosure can be easily modified and applied to other communication systems.

[0023] In the present disclosure, techniques for network management may be described. According to embodiments of the present disclosure, a communication device for managing (or analyzing) system logs of network elements (NEs) (or network nodes) constituting a network may be proposed. According to one embodiment, the communication device may be used for managing system logs of NEs in a 5G new radio (NR), OpenRAN (open radio access network), and / or cloud-native based network environment. According to one embodiment, the communication device may be used to manage system logs of various formats generated by multiple NEs manufactured by multiple manufacturers (e.g., vendors). According to one embodiment, the communication device may be used for managing system logs of multiple NEs in a distributed network environment for providing microservices. Such a communication device will be described and illustrated with reference to FIGS. 1 through 10.

[0024] FIG. 1 illustrates an example of a system including a communication device that performs the function of a software defined network (SDN) controller.

[0025] Referring to FIG. 1, a communication device (101) can perform the function of an SDN controller. An SDN controller may be referred to as a central control unit of a network. An SDN controller can identify the state of a network by communicating with a plurality of network elements (NEs) (130) within the network. An SDN controller can control the operation of the control planes of the plurality of NEs (130). An SDN controller can provide control commands to the plurality of NEs (130) according to the state of the network. By providing control commands, an SDN controller can dynamically optimize the traffic paths of the plurality of NEs (130). The communication device (101) may be referred to as an SDN controller. An SDN will be described and illustrated in more detail with reference to FIG. 2.

[0026] A communication device (101) may be used to obtain system logs of a plurality of network elements (NEs) (130). For example, the plurality of NEs (130) may include NE (130-1) and NE (130-2). For example, the plurality of NEs (130) may include a switch, a router, a distributed unit (DU), and / or a radio unit (RU). For example, an NE may be referred to as a network device, a network node, and / or an equivalent technical term.

[0027] According to one embodiment, a plurality of NEs (130) may include a virtual NE implemented in software. For example, the virtual NE may be implemented in software and may be referred to as a system that provides the functions of the NE. For example, the virtual NE may be used in a cloud computing environment. For example, the virtual NE may include a virtual router, a virtual switch, a virtual server, a virtual DU (distributed unit), a virtual RU (radio unit), and / or a virtual controller. As an example, not limited to, the virtual NE may include a virtual cell site router (VCSR) in which a virtual router is included in the virtual DU.

[0028] Each of the plurality of NEs (130) can generate a system log. Each of the plurality of NEs (130) can transmit the system log to a communication device (101). The system log may represent various events (or messages) that occurred in each of the plurality of NEs (130). The system log may include identification information (or name information) of the corresponding NE, a timestamp, information on a process (or program) running in the corresponding NE, priority information (e.g., a combination of source information of the system load and risk information of the system log), and / or information on the event that occurred. For example, the system log may include identification information of the NE to which the system log was transmitted (e.g., device name), time information of when the system log was generated at the NE (e.g., collected time), time information of when the system log was received at the communication device (101) (e.g., device time), identification information of the communication device (101) (e.g., host name), source information of the system log (e.g., facility), risk information of the system log (e.g., severity), and / or information of the event that caused the generation of the system log (e.g., message).

[0029] The communication device (101) can receive system logs generated based on various formats. The communication device (101) can monitor or manage the system logs. Based on monitoring the system logs, the communication device (101) can identify the status of multiple NEs (130). Based on monitoring the system logs, the communication device (101) can identify (or determine) an anomaly for multiple NEs (130).

[0030] The communication device (101) can generate or set conditions related to system logs and notifications corresponding to conditions according to user input. While the communication device continuously receives system logs from a plurality of NEs (130), if it detects a target system log that satisfies the conditions, it can display a notification corresponding to the conditions. By displaying the notification, the communication device (101) can inform a user (e.g., a network administrator) of the status of the NE to which the target system log was transmitted.

[0031] According to one embodiment, the system log may be configured in various data formats. The communication device (101) may have text set by user input stored in the memory of the communication device (101). The communication device (101) may identify or determine whether the system log contains text.

[0032] Below, a technique for generating conditions related to system logs in a communication device (101) that performs the function of an SDN controller in a network configured based on a software defined network (SDN) will be described, and for identifying target system logs that satisfy the generated conditions. First, the SDN architecture will be described in FIG. 2.

[0033] Figure 2 illustrates an example of a software defined network (SDN) architecture.

[0034] Referring to FIG. 2, the SDN (200) may include an application layer (210), a control plane layer (220), and / or a data plane layer (230).

[0035] The application layer (210) may include one or more applications used for control operations, including routing and / or load balancing. An application may exclusively control a resource set exposed by the SDN controller (221). An application may invoke other applications or collaborate with other applications.

[0036] The control plane layer (220) may include an SDN controller (221). The SDN controller (221) may be used for controlling all network resources. The SDN controller (221) may acquire network information and provide the acquired information to an application. For example, the SDN controller (221) may be an example of the communication device (101) of FIG. 1.

[0037] The data plane layer (230) may include at least one NE (231). The at least one NE (231) may be an example of a plurality of NEs (130) of FIG. 1. The at least one NE (231) may include at least one physical switch and / or at least one virtual switch.

[0038] The interface between the control plane layer (220) and the application layer (210) may be referred to as a northbound API (application programming interface). The interface between the control plane layer (220) and the data plane layer (230) may be referred to as a southbound API. For example, between the control plane layer (220) and the data plane layer (230), the OpenFlow protocol or the OpFlex protocol may be used.

[0039] Unlike conventional NEs (or network devices) which operate independently based on a data plane and a control plane, in SDN (200), the data plane and control plane of the NE can be separated. An SDN controller (221) can perform the operation of the control plane of the NE. SDN (200) can operate based on an algorithm for network control. Therefore, in SDN (200), the network can be managed and controlled based on a specified algorithm without the intervention of an administrator. Additionally, at least one NE (231) constituting the network can be managed through the SDN controller (221). To operate in conjunction with the SDN controller (221), at least one NE (231) can support at least one of SNMP (Simple Network Management Protocol), REST (representational state transfer protocol), NETCONF (network configuration protocol), or RESTCONF (representational state transfer configuration protocol). The SDN controller (221) can control at least one NE (231) using at least one of SNMP, REST, NETCONF, or RESTCONF.

[0040] Figure 3 illustrates an example of a simplified block diagram of a communication device.

[0041] Referring to FIG. 3, the communication device (101) may include at least one processor (300), memory (310), display (320), and / or communication circuit (330). The communication device (101) may be connected to NEs (e.g., a plurality of NEs (130), at least one NE (231)) based on a wired network and / or a wireless network. For example, the communication device (101) may be connected directly to the NEs or indirectly through one or more routers and / or access points (APs).

[0042] For example, at least one processor (300), memory (310), display (320), and / or communication circuit (330) may be electrically and / or operably coupled with each other by a communication bus. In the following, operably coupled hardware components may mean that a direct connection or indirect connection between hardware components is established by wire or wirelessly so that a second hardware component is controlled by a first hardware component among the hardware components.

[0043] At least one processor (300) may include a hardware component for processing data based on executing instructions. At least one processor (300) may be configured to execute instructions stored in memory (310) individually or collectively. At least one processor (300) may include a processing circuit. For example, the hardware component for processing data may include an arithmetic and logic unit (ALU), a floating point unit (FPU), and a field programmable gate array (FPGA). For example, the hardware component for processing data may include a central processing unit (CPU), a graphic processing unit (GPU), a display processing unit (DPU), a neural processing unit (NPU), a digital signal processor (DSP), an application processor (AP), and / or a microcontroller (MCU). At least one processor (300) may include one or more cores. For example, at least one processor (300) may have the structure of a multi-core processor such as a dual core, quad core, or hexa core.

[0044] The memory (310) may include a hardware component for storing data and / or instructions that are input to and / or output from at least one processor (300). For example, instructions may represent operations and / or actions to be performed on the data by at least one processor (300) of the communication device (101). The memory (310) may include one or more storage media. The memory (310) may include volatile memory, such as random-access memory (RAM), and / or non-volatile memory, such as read-only memory (ROM). Volatile memory may include at least one of dynamic RAM (DRAM), static RAM (SRAM), cache RAM, or pseudo SRAM (PSRAM). Non-volatile memory may include at least one of, for example, PROM (programmable ROM), EPROM (erasable PROM), EEPROM (electrically erasable PROM), flash memory, hard disk, compact disk, or EMMC (embedded multimedia card).

[0045] According to one embodiment, within the memory (310) of the communication device (101), one or more instructions (or commands) representing operations and / or operations to be performed on data by at least one processor (300) of the communication device (101) may be stored. A set of one or more instructions may be referred to as a program, firmware, operating system, process, routine, sub-routine and / or application.

[0046] The display (320) may include hardware components of a communication device (101) used to display a screen (e.g., a user interface). For example, the display (320) may include light-emitting elements and circuits (e.g., transistors) that control the light-emitting elements to emit light. For example, each of the light-emitting elements may include an organic light-emitting diode (OLED) or a micro LED. However, it is not limited thereto. For example, the display (320) may include a liquid crystal display (LCD).

[0047] The communication circuit (330) may be used to communicate with multiple NEs. The communication circuit (330) may be included in a transceiver. The communication circuit (330) may perform functions for transmitting and receiving signals in a wired communication environment. The communication circuit (330) may include a wired interface for controlling a direct connection between devices through a transmission medium (e.g., copper wire, optical fiber). For example, the communication circuit (330) may transmit an electrical signal to another device through a copper wire or perform conversion between an electrical signal and an optical signal.

[0048] The communication circuit (330) may perform functions for transmitting and receiving signals in a wireless communication environment. For example, the communication circuit (330) may perform a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the system. For example, when transmitting data, the communication circuit (330) generates complex-valued symbols by encoding and modulating the transmitted bit sequence. Also, when receiving data, the communication circuit (330) restores the received bit sequence by demodulating and decoding the baseband signal. Additionally, the communication circuit (330) may include a plurality of transmission and reception paths.

[0049] The communication circuit (330) can be used to transmit and receive signals as described above. Accordingly, all or part of the communication circuit (330) may be referred to as a 'communication unit', 'transmitter unit', 'receiver unit', or 'transmitter / receiver unit'.

[0050] FIG. 4 illustrates examples of components of a communication device for providing notifications according to system logs of multiple network elements (NEs). The communication device (101) can communicate with multiple NEs (130).

[0051] Referring to FIG. 4, the communication device (101) may include a system log management module (401), a registration management module (402), and / or a notification display module (403). The system log management module (401) may be used to receive or collect system logs of a plurality of NEs (130) from a plurality of NEs (130) registered with the communication device (101). The system log management module (401) may include a system log processing module (410) and / or a notification trigger module (411). The system log processing module (410) may be used to identify or determine whether the collected system logs satisfy a condition. The communication device (101) may provide a notification using the notification trigger module (411) upon determining that the system logs satisfy a condition. For example, the notification trigger module (411) may provide a signal to the notification display module (403) to provide a notification.

[0052] A registration management module (402) may be used to register a plurality of NEs (130) to a communication device (101). The communication device (101) may receive identification information from each of the plurality of NEs (130) within the network. The communication device (101) may determine whether to register based on the identification information of the plurality of NEs (130). The communication device (101) may support a network management protocol to register the plurality of NEs (130) to the communication device (101). For example, the network management protocol may include at least one of SNMP (Simple Network Management Protocol), REST (representational state transfer protocol), NETCONF (network configuration protocol), or RESTCONF (representational state transfer configuration protocol).

[0053] According to one embodiment, the communication device (101) can register a plurality of NEs (130) using a registration management module (402) and then continuously receive or obtain system logs from the plurality of NEs (130).

[0054] According to one embodiment, the communication device (101) may remove the registration of one of the registered NEs using the registration management module (402) in response to user input. The communication device (101) may stop continuously receiving system logs from the removed NE.

[0055] The notification display module (403) can be used to display a notification generated according to user input. For example, the communication device (101) can use the notification display module (403) to display a notification through a display (e.g., display (320)) based on the determination that the system log satisfies the condition generated according to user input.

[0056] Figure 5 illustrates examples of the operations of a communication device.

[0057] Referring to FIG. 5, in operation 501, a communication device (101) (e.g., at least one processor (300)) can receive identification information of at least one NE (network element) (e.g., a plurality of NEs (130), at least one NE (231)) from at least one NE through a communication circuit (e.g., a communication circuit (330)). The communication device (101) can register at least one NE to the communication device (101) based on the identification information transmitted from at least one NE. For example, the communication device (101) can use the registration management module (402) of FIG. 4 to register at least one NE.

[0058] In operation 503, a communication device (101) (e.g., at least one processor (300)) can continuously receive system logs of at least one NE from at least one NE through a communication circuit (330). For example, the communication device (101) can continuously receive system logs of at least one NE after registering at least one NE to the communication device (101) in operation 501.

[0059] According to one embodiment, the communication device (101) can automatically receive a system log of at least one NE from at least one registered NE. For example, the communication device (101) can receive a system log of at least one NE from at least one registered NE without a request for a system log. For example, since at least one NE has been registered with the communication device (101), it can transmit a system log of at least one NE to the communication device (101) independently of a request from the communication device (101).

[0060] According to one embodiment, a communication device (101) may receive a system log of at least one NE at regular intervals since at least one NE has been registered. For example, at least one NE may periodically transmit a system log of at least one NE to the communication device (101). However, the embodiments are not limited. For example, the communication device (101) may receive a system log of at least one NE based on an event that occurred in at least one NE. For example, at least one NE may transmit a system log of at least one NE to the communication device (101) upon detecting a specified event (e.g., port down, traffic surge).

[0061] In operation 505, a communication device (101) (e.g., at least one processor (300)) may, in response to user input, generate or set a notification corresponding to conditions and conditions related to a system log. The communication device (101) may provide a user interface for monitoring (or managing) the system log. For example, the communication device (101) may display the user interface through a display (e.g., a display (320)).

[0062] According to one embodiment, the communication device (101) may provide a function to generate a notification corresponding to conditions related to a system log through a user interface. For example, while displaying the user interface, the communication device (101) may generate or set a notification corresponding to conditions related to a system log according to user input. The communication device (101) may generate or define a notification independently of the network management protocol. Since the communication device (101) generates the notification through the user interface, it can generate the notification and manage the system log relatively easily.

[0063] According to one embodiment, conditions related to a system log may include conditions indicating text that the system log has set according to user input. For example, a communication device (101) may set text according to user input. For example, the communication device (101) may display a notification when it identifies that the system log contains text that has been set according to user input. For example, the text may be referred to as a keyword. For example, the communication device (101) may generate or set various types of conditions according to user input.

[0064] According to one embodiment, a condition related to a system log may include a condition in which a system log transmitted from one NE represents text set according to user input. For example, one NE may be an NE determined according to user input among at least one registered NE.

[0065] According to one embodiment, a condition related to a system log may include a condition in which a system log received during a specified time interval represents text set according to user input. For example, the specified time interval may be determined according to user input. For example, the specified time interval may be referred to as an expiration period.

[0066] According to one embodiment, conditions related to system logs may include a condition in which the number of detections of system logs representing text is greater than the number set according to user input. The communication device (101) may continuously receive system logs from at least one NE. For example, the communication device (101) may display a notification when it detects system logs representing text a set number of times. For example, a system log representing text corresponding to the set number of times may be an example of a target system log to be described later.

[0067] According to one embodiment, the type of notification corresponding to the condition may be determined by user input from among various types. For example, various types may include critical, warning, major, and / or minor. However, the embodiments are not limited. The communication device (101) may set or determine the type of notification according to user input.

[0068] In operation 507, the communication device (101) (e.g., at least one processor (300)) can determine whether a target system log satisfying a condition is detected among the system logs of at least one NE while the system logs of at least one NE are continuously received. The communication device (101) can execute operation 509 based on the determination that a target system log satisfying a condition is detected among the system logs of at least one NE. The communication device (101) can execute operation 511 based on the determination that a target system log satisfying a condition is not detected among the system logs of at least one NE.

[0069] In operation 509, the communication device (101) (e.g., at least one processor (300)) may display a notification corresponding to the condition through the display (320) upon the determination that a target system log satisfying the condition is detected among the system logs of at least one NE. The communication device (101) may display through the display (320) that a target system log satisfying the condition set according to user input has been detected.

[0070] According to one embodiment, a communication device (101) may receive a system log indicating a port down of the NE. A port down may be referred to as a state in which a physical port and / or a logical port of the NE is down. A port down may correspond to an abnormal state in the state of the physical port and / or the state of the logical port. The causes of a port down may vary. For example, the causes of a port down may include physical damage (e.g., cable breakage, port failure, power supply problem), logical failure (e.g., incorrect configuration, security problem), and / or environmental factors (e.g., change in temperature, change in humidity).

[0071] According to one embodiment, a communication device (101) may generate conditions and notifications to display a notification when a system log containing specified text (e.g., state, down) is detected in response to user input. For example, the communication device (101) may receive a system log containing specified text (e.g., state, down) from an NE that is in a port down state. The communication device (101) may display a notification in response to detecting a system log containing specified text (e.g., state, down). A user of the communication device (101) (e.g., a network administrator) may take relatively quick action regarding the NE that is in a port down state through the notification of the communication device (101).

[0072] According to one embodiment, a communication device (101) may receive a system log indicating an error in a routing protocol (e.g., BGP (border gateway protocol), MPLS (multiprotocol label switching)). An error in route information exchanged through a routing protocol may cause a disconnection of the network and / or interruption of communication services. The communication device (101) may generate conditions and notifications to display a notification when a system log containing specified text (e.g., bgp, mpls, no longer available) is detected in response to user input. For example, the communication device (101) may receive a system log containing specified text (e.g., bgp, mpls, no longer available) from an NE where a routing protocol error occurred. The communication device (101) may display a notification in response to detecting a system log containing specified text (e.g., bgp, mpls, no longer available). A user of the communication device (101) (e.g., a network administrator) can take relatively quick action regarding an NE where a routing protocol error has occurred through a notification from the communication device (101).

[0073] According to one embodiment, a communication device (101) may receive a system log indicating a precision time protocol (PTP) error. PTP may be referred to as a protocol for synchronizing the time of NEs within a network. PTP may be related to a billing system of a network user. The communication device (101) may generate conditions and notifications to display a notification when a system log indicating a specified text (e.g., phase, lock, clock, lost, sync) is detected in response to user input. For example, the communication device (101) may receive a system log containing the specified text (e.g., phase, lock, clock, lost, sync) from an NE where a PTP error occurred. The communication device (101) may display a notification in response to detecting a system log containing the specified text (e.g., phase, lock, clock, lost, sync). A user of the communication device (101) (e.g., a network administrator) may take relatively quick action regarding an NE where a PTP error occurred through the notification of the communication device (101).

[0074] According to one embodiment, the communication device (101) can provide the user (e.g., network administrator) of the communication device (101) with information through a notification regarding whether an event that the user wants to know has occurred. The user of the communication device (101) can relatively quickly identify an abnormal state of the NE within the network through the notification.

[0075] According to one embodiment, the communication device (101) can enhance the visibility of the user's notification by displaying the notification through the display (320). According to embodiments of the present disclosure, since conditions and notifications are generated according to user input, the communication device (101) can provide notifications for various events in addition to notification functions according to conventional network protocols. According to embodiments of the present disclosure, the time spent by a user of the communication device (101) (e.g., a network administrator) responding to various events occurring in at least one NE can be reduced.

[0076] In operation 511, the communication device (101) (e.g., at least one processor (300)) may refrain from displaying a notification corresponding to the condition based on the determination that no target system log satisfying the condition is detected among at least one NE system log.

[0077] By way of example, the embodiments of the present disclosure may also be applied to a virtual NE. A virtual NE may be referred to as a system that is implemented in software and provides the functions of an NE. For example, a virtual NE may include a virtual router, a virtual switch, a virtual server, a virtual distributed unit (DU), a virtual radio unit (RU), and / or a virtual controller. For example, a virtual router may be implemented in software and provide the functions of a physical router. A virtual router (or router) may process data to deliver data from a network to a destination (e.g., a target device). A virtual router (or router) may be used to ensure the quality of service (QOS) of a network. The slower a user (e.g., a network administrator, a carrier) responds to an event (e.g., port down, link down) occurring in a virtual router (or router), the lower the network's quality of service may be.

[0078] According to one embodiment, the high availability of a virtual NE may be higher than the high availability of a physical NE. For example, the time required to replace a virtual NE when an error occurs in the virtual NE may be shorter than the time required to replace a physical NE when an error occurs in the physical NE. In a network, the scalability of a virtual NE may be higher than the scalability of a physical NE. Resources (e.g., cost, time) for maintaining a virtual NE may be less than resources for maintaining a physical NE.

[0079] According to one embodiment, the network management protocol provided to the virtual NE and the network management protocol provided to the physical NE may be different. For example, SNMP may be provided to the physical NE, but SNMP may not be provided to the virtual NE. For example, since SNMP is not provided to the virtual NE, it may not be able to support legacy notification functions based on SNMP. Since the embodiments of the present disclosure may also apply to the virtual NE, a user of the communication device (101) (e.g., a network administrator) can identify an abnormal state of the virtual NE through a notification displayed on the communication device (101).

[0080] Figure 6 illustrates an example of a user interface displayed on a communication device.

[0081] Referring to FIG. 6, a communication device (e.g., communication device (101)) may display a user interface (600) through a display (e.g., display (230)). The user interface (600) may include a visual object (601), a visual object (602), a visual object (603), a visual object (604), a list (605), a list (606), and / or a visual object (607).

[0082] A visual object (601) may be associated with a function representing a list of system logs collected (or received) by the communication device (101) and / or a list of conditions related to system logs generated according to user input. The user interface (600) exemplified in FIG. 6 may represent a list of system logs displayed according to user input to the visual object (601). A visual object (602) may be associated with a function representing a history of notifications corresponding to conditions set according to user input. The communication device (101) may display the history of notifications through the user interface according to user input to the visual object (602). The history of notifications will be described and exemplified with reference to FIG. 10.

[0083] A visual object (603) may be associated with a list of system logs collected (or received) by a communication device (101). For example, the communication device (101) may display a list (606) of system logs collected from at least one NE through a user interface (600) in accordance with user input to the visual object (603). A visual object (604) may be associated with a list of conditions associated with system logs generated in accordance with user input. The list of conditions will be described and illustrated with reference to FIG. 9.

[0084] The list (605) may represent at least one NE (e.g., multiple NEs (130), at least one NE (231)). For example, at least one NE represented by the list (605) may be registered in the communication device (101). For example, the communication device (101) may display a list of system logs collected from the NE corresponding to the text through the user interface (600) in response to user input for text within the list (605) (e.g., SEC_LEAF4_QFX5120-48Y).

[0085] According to one embodiment, the communication device (101) can display a list (605) through a user interface (600) while a system log is continuously received from at least one NE.

[0086] According to one embodiment, the communication device (101) may remove the registration of at least one NE among the registered NEs indicated by the list (605) in response to user input. The communication device (101) may stop continuously receiving system logs from the removed NE.

[0087] The user interface (600) may include a list (606). The list (606) may represent system logs collected from at least one NE. The list (606) may represent identification information of the NE to which the system log was transmitted (e.g., device name), time information when the system log was generated at the NE (e.g., collected time), time information when the system log was received at the communication device (101) (e.g., device time), identification information of the communication device (101) (e.g., host name), source information of the system log (e.g., facility), risk information of the system log (e.g., severity), and / or information of the event that caused the generation of the system log (e.g., message).

[0088] According to one embodiment, the communication device (101) may select an NE corresponding to the text based on user input for the text in the list (605). For example, the list (606) may represent only system logs collected from the selected NE. However, the embodiments are not limited.

[0089] A visual object (607) may be associated with a function for changing the system log collection settings. For example, a communication device (101) may display a user interface (e.g., user interface (700)) for changing the system log collection settings according to user input to the visual object (607). A user interface for changing the system log collection settings will be described and illustrated with reference to FIG. 7.

[0090] Figure 7 illustrates an example of a user interface for changing system log collection settings.

[0091] Referring to FIG. 7, the user interface (700) may include a visual object (701), a visual object (702), a list (703), a visual object (704), and / or a visual object (705). The user interface (700) may be used to change the collection settings of system logs.

[0092] According to one embodiment, a communication device (e.g., communication device (101)) can change the retention policy of a system log received from at least one NE using a user interface (700). The communication device (101) can change or set the period (e.g., 30 days) during which the system log is stored in the memory (e.g., memory (310)) of the communication device (101) according to user input regarding a visual object (701). For example, the communication device (101) can remove the system log as the period according to the visual object (701) has elapsed since the system log was received.

[0093] The communication device (101) can change or set the maximum number of system logs that can be stored in the memory (310) of the communication device (101) according to user input regarding the visual object (702) (e.g., 100000000). For example, the communication device (101) can remove at least some of the stored system logs when the number of system logs stored in the memory (310) reaches the number according to the visual object (702). For example, the communication device (101) can remove the system log that has been stored the longest among the stored system logs.

[0094] According to one embodiment, the list (703) may be related to the filtering of system logs received from at least one NE. The list (703) may be referenced as a filtering condition for system logs that are not displayed through a user interface (e.g., user interface (600)) among the system logs. For example, the filtering condition may include a condition that if the priority of a system log is lower than a reference priority, the corresponding system log is not displayed through a user interface (e.g., user interface (600)). For example, the priority of a system log may be composed of a combination of source information of the system log and risk information of the system log. For example, the source information of the system log may indicate the type of NE from which the system log was generated or the type of service of the NE from which the system log was generated. Values ​​that the source information of the system log may represent will be explained with reference to [Table 1] to be described later. For example, the risk information of the system log may represent the importance or risk level of the system log. Values ​​that the risk information of the system log may represent will be explained with reference to [Table 2] to be described later.

[0095] Value Name Description 0 kernel Occurs in the operating system kernel. 1 user Occurs in applications and / or general programs. 2 mail Related to the mail system. 3 daemon Related to system daemons (e.g., background services). 4 auth Related to authentication. 5 syslog Occurs in the system log itself. 6 lpr Related to the print system. 7 news Related to news servers. 8 ucp Related to UCP (Unix-to-Unix Copy Protocol). 9 cron Related to periodic task schedulers. 10 authpriv Related to sensitive authentication information. 11 ftp Related to FTP (File Transfer Protocol). 12 ntp Related to NTP (Network Time Protocol). 13 security / alert Related to security alerts. 14 clock daemon Related to the system clock daemon. 15 local 0 Defined by the user. 16 local 1 Defined by the user. 17 local 2 Defined by the user. 18 local 3 Defined by the user. 19 local 4 Defined by the user. 20 local 5 By the user Defined.21 Defined by local6 user.22 Defined by local7 user.

[0096] Value Name Description 0 Emergency Indicates that the system is unavailable. 1 Alert Indicates that immediate action is required. 2 Critical Indicates that a critical error has occurred. 3 Error Indicates a general error. 4 Warning Indicates a warning situation. 5 Notice Indicates that this is important information in a normal state. 6 Informational Indicates that information is provided. 7 Debug Indicates information useful for debugging.

[0097] The communication device (101) can change or set filtering conditions according to user input regarding the list (703). For example, the communication device (101) can change or set filtering conditions for each of the values ​​that the source information of the system log can represent. For example, the communication device (101) can change or set the value of the risk information of the system log to be filtered according to user input. For example, the smaller the value of the risk information of the system log in [Table 2], the higher the importance may be. According to one embodiment, when the value of the risk information for 'kernel' in the list (703) is set to 'warning', the communication device (101) may not display system logs having a lower importance than 'warning' among system logs having source information representing 'kernel' through the user interface (e.g., user interface (600)). According to one embodiment, when the value of the risk information for 'ntp' in the list (703) is set to 'alert', the communication device (101) may not display system logs having a lower importance than 'alert' among system logs having source information representing 'ntp' through the user interface (e.g., user interface (600)).

[0098] FIG. 8 illustrates an example of a user interface for generating a notification corresponding to a condition and condition related to a system log.

[0099] Referring to FIG. 8, the user interface (800) may include a visual object (801), a visual object (802), a visual object (803), a visual object (804), a visual object (805), and / or a visual object (806).

[0100] A visual object (801) may be used to select one NE from at least one NE registered in a communication device (e.g., communication device (101)). For example, the communication device (101) may determine or select one NE based on user input to the visual object (801). For example, the communication device (101) may determine whether a system log transmitted from one NE represents text set according to user input. The one NE determined according to user input may be displayed through the visual object (802).

[0101] A visual object (803) can be used to set text according to user input. For example, text according to user input may be referred to as a keyword. For example, a communication device (101) can set text in response to user input regarding the visual object (803). The communication device (101) can determine whether a received system log indicates the set text (e.g., AUTH).

[0102] A visual object (804) can be used to set the validity period of a condition. For example, a communication device (101) can set or change the validity period of the condition according to user input regarding the visual object (804).

[0103] A visual object (805) may be used to set the number of times a system log containing text (e.g., text corresponding to a condition) must be detected to display a notification. For example, if the number of times a system log containing text (e.g., set via the visual object (803)) is detected is greater than the number set via the visual object (805), the communication device (101) may display a notification corresponding to the condition through a display (e.g., display (320)).

[0104] A visual object (806) may be used to generate or set a notification corresponding to a condition. For example, the communication device (101) may determine the type of notification to be displayed in response to detecting a system log (e.g., target system log) that satisfies the condition, based on user input to the visual object (806). For example, the type of notification may be one of specified types (e.g., critical, warning, major, minor). However, the embodiments are not limited.

[0105] FIG. 9 illustrates an example of a user interface showing a list of conditions generated according to user input and notifications corresponding to the conditions.

[0106] Referring to FIG. 9, the user interface (900) may display conditions generated according to user input. The user interface (900) may include a list (901), a list (902), a list (903), a list (904), a list (905), a list (906), and / or a list (907).

[0107] List (901) may represent identification information of NE corresponding to the condition. List (901) may be associated with the visual object (802) of FIG. 8. List (902) may represent text corresponding to the condition. For example, List (902) may represent keywords of the condition. List (902) may be associated with the visual object (803) of FIG. 8. List (903) may represent the validity period of the condition. List (903) may be associated with the visual object (804) of FIG. 8. List (904) may represent the number of times a system log representing text (e.g., text corresponding to the condition) must be detected to display a notification. List (904) may be associated with the visual object (805) of FIG. 8. List (905) may represent the actual number of detections of a system log representing text corresponding to the condition. List (906) may represent the type of notification corresponding to the condition. The list (906) may be associated with the visual object (806) of FIG. 8. The list (907) may indicate the activation or deactivation of a condition. For example, the communication device (101) may change whether a condition within the list (907) is activated based on user input to the list (907).

[0108] According to one embodiment, the communication device (101) may periodically identify or search for a list of conditions generated according to user input. The communication device (101) may detect or identify a target system log satisfying the conditions among system logs received from at least one NE. In response to detecting a target system log, the communication device (101) may display a notification through a display (e.g., display (320)). In an example that is not limited to, the communication device (101) may not display a notification even if it detects another target system log after displaying a notification corresponding to the condition. For example, the communication device (101) may display a notification in response to detecting another target system log after providing feedback on the notification of the condition. For example, displaying a notification will be described with reference to FIG. 10.

[0109] FIG. 10 illustrates an example of a user interface representing a list of notifications. The user interface (1000) of FIG. 10 may be displayed through a display (e.g., display (320)) of a communication device (e.g., communication device (101)) according to user input to a visual object (602) in the user interface (600) of FIG. 6.

[0110] Referring to FIG. 10, the user interface (1000) can display a history of notifications generated according to user input. For example, the communication device (101) can display, through the user interface (1000), a target system log satisfying a condition generated according to user input among the system logs. The user interface (1000) may include a list (1001), a list (1002), a list (1003), a list (1005), a list (1006), and / or a list (1007).

[0111] List (1001) may indicate the risk level of a notification. The risk level of a notification may indicate the importance of the notification. The risk level of a notification may be set according to user input for a visual object (806) in the user interface (800) of FIG. 8. List (1002) may indicate identification information of the NE where the target system log corresponding to the notification was generated. List (1003) may indicate a summary of the notification or the name of the notification. For example, 'switch_keyword_alarm' may indicate that the target system log transmitted from the switch contains text set according to user input.

[0112] List (1005) may indicate identification information of the NE where the target system log corresponding to the notification was generated. List (1006) may indicate a description of the target system log corresponding to the notification. List (1007) may indicate time information where the target system log satisfying the conditions generated according to user input was detected.

[0113] In an embodiment according to the present disclosure, since at least one NE has been registered to a communication device (e.g., communication device (101)), system logs can be continuously received from at least one NE. The communication device (101) can increase the efficiency of collecting system logs from at least one registered NE. The communication device (e.g., communication device (101)) can generate or set conditions related to the system logs and notifications corresponding to those conditions. The communication device (101) can enhance the user's visibility of notifications by displaying the notifications through a display (e.g., display (320)). According to embodiments of the present disclosure, since conditions and notifications are generated based on user input, the communication device (101) can provide notifications for various events in addition to notification functions according to conventional network protocols. According to embodiments of the present disclosure, the time spent by a user of the communication device (101) (e.g., network administrator) responding to various events occurring in at least one NE can be reduced.

[0114] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.

[0115] The technical problems to be solved in this disclosure are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this disclosure belongs.

[0116] A communication device configured to perform the functions of a software defined network (SDN) controller as described above may include a display. The communication device may include a communication circuit. The communication device may include a memory comprising one or more storage media for storing instructions. The communication device may include at least one processor comprising a processing circuitry. When the instructions are executed individually or collectively by the at least one processor, the communication device may cause the communication device to register the at least one network element (NE) based on identification information transmitted from the at least one NE. When the instructions are executed individually or collectively by the at least one processor, after registering the at least one NE, the communication device may cause the communication device to continuously receive system logs of the at least one NE from the at least one NE through the communication circuit. When the above instructions are executed individually or collectively by the at least one processor, they may cause the communication device to generate a condition related to a system log and a notification corresponding to the condition in response to user input. When the above instructions are executed individually or collectively by the at least one processor, they may cause the communication device to determine whether a target system log satisfying the condition is detected among the system logs of the at least one NE while the system logs of the at least one NE are continuously received.When the above instructions are executed individually or collectively by the at least one processor, the communication device may cause the notification corresponding to the condition to be displayed through the display in accordance with the determination that the target system log is detected among the system logs of the at least one NE. When the above instructions are executed individually or collectively by the at least one processor, the communication device may cause the notification corresponding to the condition to be withheld in accordance with the determination that the target system log is not detected among the system logs of the at least one NE.

[0117] According to one embodiment, the condition associated with the system log may include a condition in which the system log represents text set according to the user input.

[0118] According to one embodiment, the condition associated with the system log may include a condition in which the system log received during a time interval set according to the user input represents the text.

[0119] According to one embodiment, the condition related to the system log may include a condition in which the number of detections of the system log representing the text is greater than the number set according to the user input.

[0120] According to one embodiment, the at least one NE may include a virtual NE implemented in software.

[0121] According to one embodiment, when the instructions are executed individually or collectively by the at least one processor, the communication device may cause the system log of the at least one NE to be displayed through the display while the system log of the at least one NE is continuously received.

[0122] According to one embodiment, the instructions, when executed individually or collectively by the at least one processor, may cause the communication device to discard the registration of one of the at least one registered NE in response to other user input. The instructions, when executed individually or collectively by the at least one processor, may cause the communication device to stop continuously receiving the system log of the NE from the NE through the communication circuit.

[0123] A method performed in a communication device configured to perform the functions of an SDN controller, having a display and a communication circuit as described above, may include an operation of registering the at least one NE to the communication device based on identification information transmitted from at least one NE. The method may include an operation of continuously receiving a system log of the at least one NE from the at least one NE through the communication circuit after registering the at least one NE. The method may include an operation of generating a condition related to the system log and a notification corresponding to the condition in response to user input. The method may include an operation of determining whether a target system log satisfying the condition is detected among the system logs of the at least one NE while the system logs of the at least one NE are continuously received. The method may include an operation of displaying the notification corresponding to the condition through the display in accordance with the determination that the target system log is detected among the system logs of the at least one NE. The above method may include an operation of refraining from displaying the notification corresponding to the condition based on a determination that the target system log is not detected among the system logs of the at least one NE.

[0124] According to one embodiment, the condition associated with the system log may include a condition in which the system log represents text set according to the user input.

[0125] According to one embodiment, the condition associated with the system log may include a condition in which the system log received during a time interval set according to the user input represents the text.

[0126] According to one embodiment, the condition related to the system log may include a condition in which the number of detections of the system log representing the text is greater than the number set according to the user input.

[0127] According to one embodiment, the at least one NE may include a virtual NE implemented in software.

[0128] According to one embodiment, the method may include the operation of displaying a list of the system logs of the at least one NE through the display while the system logs of the at least one NE are continuously received.

[0129] According to one embodiment, the method may include an operation of discarding the registration of one of the at least one registered NE in response to another user input. The method may include an operation of stopping the continuous reception of the system log of the NE from the NE through the communication circuit.

[0130] In a computer-readable storage medium in which one or more programs as described above are stored, the one or more programs may include instructions that cause the communication device to register the at least one network element (NE) to the communication device based on identification information transmitted from at least one NE, when executed by the communication device which has a display and a communication circuit and is configured to perform the function of an SDN controller. The one or more programs may include instructions that cause the communication device to continuously receive the system log of the at least one NE from the at least one NE through the communication circuit after registering the at least one NE when executed by the communication device. The one or more programs may include instructions that cause the communication device to generate a condition related to the system log and a notification corresponding to the condition in response to user input when executed by the communication device. The above one or more programs may include instructions that cause the communication device to determine whether a target system log satisfying the condition is detected among the system logs of the at least one NE while the system logs of the at least one NE are continuously received when executed by the communication device. The above one or more programs may include instructions that cause the communication device to display the notification corresponding to the condition through the display, upon the determination that the target system log is detected among the system logs of the at least one NE when executed by the communication device.The above one or more programs may include instructions that cause the communication device to refrain from displaying the notification corresponding to the condition, based on the determination that the target system log is not detected among the system logs of the at least one NE when executed by the communication device.

[0131] According to one embodiment, the condition associated with the system log may include a condition in which the system log represents text set according to the user input.

[0132] According to one embodiment, the condition associated with the system log may include a condition in which the system log received during a time interval set according to the user input represents the text.

[0133] According to one embodiment, the condition related to the system log may include a condition in which the number of detections of the system log representing the text is greater than the number set according to the user input.

[0134] According to one embodiment, the at least one NE may include a virtual NE implemented in software.

[0135] According to one embodiment, the one or more programs may include instructions that cause the communication device to display a list of the system logs of the at least one NE through the display while the system logs of the at least one NE are continuously received when executed by the communication device.

[0136] According to one embodiment, the one or more programs may include instructions that cause the communication device to discard the registration of one of the at least one registered NE in response to other user input when executed by the communication device. The one or more programs may include instructions that cause the communication device to stop continuously receiving the system log of the NE from the NE through the communication circuit when executed by the communication device.

[0137] The electronic device (e.g., communication device (101)) according to the various embodiments disclosed in this document may be of various forms. The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments and should be understood to include various modifications, equivalents, or substitutions of said embodiments. In relation to the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of said items unless the relevant context clearly indicates otherwise. In this document, phrases such as “A or B”, “at least one of A and B”, “at least one of A or B”, “A, B or C”, “at least one of A, B and C”, and “at least one of A, B, or C” may each include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as “first,” “second,” or “first” or “second” may be used simply to distinguish a component from another component and do not limit the components in any other aspect (e.g., importance or order). Where any (e.g., first) component is referred to as “coupled” or “connected” to another (e.g., second) component, with or without the terms “functionally” or “communicationally,” it means that said component may be connected to said other component directly (e.g., wired), wirelessly, or through a third component.

[0138] The term “module” as used in the various embodiments of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be a component formed integrally, or a minimum unit of said component or a part thereof that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0139] Various embodiments of the present document may be implemented as software comprising one or more instructions stored in a storage medium (e.g., memory (310)) readable by a machine (e.g., communication device (101) of FIG. 1). For example, a processor (e.g., at least one processor (300)) of the machine (e.g., communication device (101)) may call at least one of the one or more instructions stored in the storage medium and execute it. This enables the machine to be operated to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. The storage medium readable by the machine may be provided in the form of a non-transitory storage medium. Here, 'non-temporary' simply means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily.

[0140] According to one embodiment, the method according to the various embodiments disclosed herein may be provided by being included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or distributed online (e.g., download or upload) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0141] According to various embodiments, each component (e.g., module or program) of the components described above may include a singular or multiple entities, and some of the multiple entities may be separated and placed in other components. According to various embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as those performed by the corresponding component among the multiple components prior to integration. According to various embodiments, operations performed by the module, program, or other components may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

Claims

1. In a communication device configured to perform the functions of an SDN (software defined network) controller, display; Communication circuit; Memory comprising one or more storage media for storing instructions; and It includes at least one processor comprising a processing circuit, and When the above instructions are executed individually or collectively by the at least one processor, the communication device: Based on identification information transmitted from at least one network element (NE), the at least one NE is registered with the communication device; After registering at least one NE, continuously receive the system log of the at least one NE from the at least one NE through the communication circuit; In response to user input, generate conditions related to system logs and notifications corresponding to said conditions; While the system log of the at least one NE is continuously received, determining whether a target system log satisfying the condition is detected among the system logs of the at least one NE; Based on the determination that the target system log is detected among the system logs of at least one NE, the notification corresponding to the condition is displayed through the display; and Causing to refrain from displaying the notification corresponding to the condition based on a determination that the target system log is not detected among the system logs of at least one NE. Communication device.

2. In Claim 1, The above condition related to the above system log includes a condition in which the system log represents text set according to the user input. Communication device.

3. In Claim 2, The above condition related to the above system log includes a condition in which the system log received during a time interval set according to the user input represents the text. Communication device.

4. In Claim 2, The above condition related to the above system log includes a condition in which the number of detections of the system log representing the text is greater than the number set according to the user input. Communication device.

5. In Claim 1, The above at least one NE includes a virtual NE implemented in software, Communication device.

6. In Claim 1, When the above instructions are executed individually or collectively by the at least one processor, the communication device: Causing to display, through the display, a list of the system logs of the at least one NE while the system logs of the at least one NE are continuously received. Communication device.

7. In Claim 1, When the above instructions are executed individually or collectively by the at least one processor, the communication device: In response to other user input, discard the registration of one of the at least one registered NE; and Causing to stop continuously receiving the system log of the above NE from the above NE through the communication circuit, Communication device.

8. A method performed in a communication device having display and communication circuits and configured to perform the functions of a software defined network (SDN) controller, An operation of registering at least one network element (NE) to the communication device based on identification information transmitted from at least one NE; After registering at least one NE, the operation of continuously receiving the system log of the at least one NE from the at least one NE through the communication circuit; An action of generating conditions related to system logs and notifications corresponding to said conditions in response to user input; An operation to determine whether a target system log satisfying the condition is detected among the system logs of the at least one NE while the system logs of the at least one NE are continuously received; An operation of displaying the notification corresponding to the condition through the display, in accordance with a determination that the target system log is detected among the system logs of at least one NE; and Based on a determination that the target system log is not detected among the system logs of at least one NE, the operation of refraining from displaying the notification corresponding to the condition, method.

9. In Claim 8, The above condition related to the above system log includes a condition in which the system log represents text set according to the user input. method.

10. In Claim 9, The above condition related to the above system log includes a condition in which the system log received during a time interval set according to the user input represents the text. method.

11. In Claim 9, The above condition related to the above system log includes a condition in which the number of detections of the system log representing the text is greater than the number set according to the user input. method.

12. In claim 8, The above at least one NE includes a virtual NE implemented in software, method.

13. In claim 8, The method further includes the operation of displaying a list of the system logs of the at least one NE through the display while the system logs of the at least one NE are continuously received. method.

14. In Claim 8, An operation to discard the registration of one of the at least one registered NE in response to another user input; and Further including the operation of stopping the continuous reception of the system log of the above NE from the above NE through the communication circuit, method.

15. In a non-transient computer-readable storage medium storing one or more programs, When the above one or more programs are executed by a communication device having display and communication circuits and configured to perform the functions of an SDN (software defined network) controller, Based on identification information transmitted from at least one network element (NE), the at least one NE is registered with the communication device; After registering at least one NE, continuously receive the system log of the at least one NE from the at least one NE through the communication circuit; In response to user input, generate conditions related to system logs and notifications corresponding to said conditions; While the system log of the at least one NE is continuously received, determining whether a target system log satisfying the condition is detected among the system logs of the at least one NE; Based on the determination that the target system log is detected among the system logs of at least one NE, the notification corresponding to the condition is displayed through the display; and Instructions that cause the communication device to refrain from displaying the notification corresponding to the condition, based on a determination that the target system log is not detected among the system logs of at least one NE. Non-transient computer-readable storage media.

Images