Electronic device and method for managing network nodes

Abstract

According to an embodiment, a method performed by an electronic device may comprise an operation of executing a software application for a first service management entity for managing a plurality of first network nodes and a second service management entity for managing a plurality of second network nodes. The method may comprise an operation of performing, using the software application, a registration procedure for the first service management entity and a registration procedure for the second service management entity. The method may comprise an operation of establishing a connection with the second service management entity on the basis of second account information, during a period in which a connection with the first service management entity is established on the basis of first account information. The method may comprise an operation of providing a user interface including a first visual object for controlling the first service management entity and a second visual object for controlling the second service management entity.

Description

Electronic device and method for managing network nodes

[0001] The present disclosure relates to a wireless communication system. More specifically, the present disclosure relates to an electronic device and method for managing network nodes in a wireless communication system.

[0002] To meet the growing demand for wireless data traffic following the commercialization of 4G (4th generation) communication systems, improved 5G (5th generation) communication systems, or pre-5G communication systems, are being developed and expanded. For this reason, 5G communication systems, or pre-5G communication systems, are also referred to as "Beyond 4G Network" communication systems or "Post-LTE" systems.

[0003] To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., the 60 GHz band). To mitigate radio path loss and increase the transmission range of radio waves in ultra-high frequency bands, advanced technologies such as beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antenna technologies are being discussed and developed for 5G communication systems.

[0004] Additionally, for network improvement, 5G communication systems are developing technologies such as advanced small cells, ultra-dense networks, device-to-device communication (D2D), wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation.

[0005] Additionally, advanced coding modulation (ACM) techniques such as Hybrid Frequency Shift Keying and Quadrature Amplitude Modulation (FQAM) and Sliding Window Superposition Coding (SWSC) are under development for 5G communication systems. Furthermore, advanced access technologies such as Filter Bank Multi-Carrier (FBMC), Non-Orthogonal Multiple Access (NOMA), and Sparse Code Multiple Access (SCMA) are also being developed.

[0006] To meet the growing demand for wireless data traffic, 5G communication systems, also known as new radio (NR), are being commercialized. 5G communication systems, like 4G communication systems, provide users with high data rates. Furthermore, 5G communication systems offer wireless communication services for a variety of purposes, including the Internet of Things and services requiring high reliability for specific purposes. In a system that combines 4G and 5G systems, the Open Radio Access Network (O-RAN), established by operators and equipment providers, defines new network elements (NEs) and interface specifications based on the 3rd Generation Partnership Project (3GPP) standards and presents the O-RAN architecture. O-RAN is established by operators and equipment providers.

[0007] The above information may be provided as background art to aid in understanding the present disclosure. No claim or determination is made as to whether any of the above is applicable as prior art related to the present disclosure.

[0008] According to one embodiment, an electronic device may include a display, at least one processor including a processing circuit, and a memory including one or more storage media storing instructions. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to execute a software application for a first service management entity for managing a plurality of first network nodes and a second service management entity for managing a plurality of second network nodes. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to perform a registration procedure for the first service management entity and a registration procedure for the second service management entity using the software application. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to establish a connection with the first service management entity based on first account information, while the connection is established using the software application, with the second service management entity based on second account information distinct from the first account information. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to provide a user interface for the software application, the user interface including a first visual object for controlling the first service management entity and a second visual object for controlling the second service management entity.

[0009] According to one embodiment, a method performed on an electronic device may include executing a software application for a first service management entity for managing a plurality of first network nodes and a second service management entity for managing a plurality of second network nodes. The method may include performing, using the software application, a registration procedure for the first service management entity and a registration procedure for the second service management entity. The method may include establishing, using the software application, a connection with the second service management entity based on second account information, while a connection is established with the first service management entity based on first account information, the connection being distinct from the first account information. The method may include providing a user interface for the software application, the software application including a first visual object for controlling the first service management entity and a second visual object for controlling the second service management entity.

[0010] According to one embodiment, a non-transitory computer-readable storage medium may store one or more programs. The one or more programs may include instructions that, when executed by a processor of an electronic device including a display, cause the electronic device to execute a software application for a first service management entity for managing a plurality of first network nodes and a second service management entity for managing a plurality of second network nodes. The one or more programs may include instructions that, when executed by the processor of the electronic device, cause the electronic device to perform a registration procedure for the first service management entity and a registration procedure for the second service management entity using the software application. The one or more programs may include instructions that, when executed by the processor of the electronic device, cause the electronic device to establish a connection with the first service management entity based on first account information, while the connection is established with the first service management entity, based on second account information distinct from the first account information. The one or more programs may include instructions that, when executed by the processor of the electronic device, cause the electronic device to provide a user interface for the software application, the user interface including a first visual object for controlling the first service management entity and a second visual object for controlling the second service management entity.

[0011] Figure 1 illustrates a wireless communication system.

[0012] Figure 2 illustrates an example of a management service entity for managing multiple network nodes.

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

[0014] Figure 4 shows an example of an architecture for SMO.

[0015] FIG. 5 illustrates an example of an electronic device and one or more management service entities.

[0016] Figure 6 illustrates an example of the operation of an electronic device for registering a management service entity.

[0017] FIGS. 7a, 7b, and 7c illustrate examples of user interfaces provided on an electronic device for registering a management service entity.

[0018] Figure 8 illustrates an example of the operation of an electronic device for monitoring information about a management service entity via NBI.

[0019] FIGS. 9A, 9B, and 9C illustrate examples of user interfaces provided on an electronic device for managing a management service entity.

[0020] Figure 10 illustrates an example of the operation of an electronic device for controlling a management service entity.

[0021] Figures 11a, 11b, and 11c illustrate examples of user interfaces provided in an electronic device to control a management service entity.

[0022] Figure 12 is a flowchart illustrating the operation of an electronic device for managing multiple management service entities.

[0023] Figure 13 shows the configuration of an electronic device.

[0024] The terms used in this disclosure are used only to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by those of ordinary skill in the art described in this disclosure. Terms defined in general dictionaries among the terms used in this disclosure may be interpreted as having the same or similar meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure.

[0025] The various embodiments of the present disclosure described below illustrate a hardware-based approach as an example. However, since the various embodiments of the present disclosure include techniques utilizing both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.

[0026] In the following description, terms referring to signals (e.g., signal, information, message, signaling), terms referring to data types (e.g., list, set, subset), terms for operational states (e.g., step, operation, procedure), terms referring to data (e.g., packet, user stream, information, bit, symbol, codeword), terms referring to resources (e.g., symbol, slot, subframe, radio frame, subcarrier, resource element (RE), resource block (RB), bandwidth part (BWP), occasion), terms referring to channels, terms referring to network entities, terms referring to components of devices, etc. are examples for convenience of description. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used.

[0027] In the following description, terms referring to configuration (e.g., setup, setting, arrangement, control), terms referring to signals (e.g., packet, message, signal, information, signaling), terms referring to resources (e.g., section, symbol, slot, subframe, radio frame, subcarrier, RE (resource element), RB (resource block), BWP (bandwidth part), occasion), terms for operational states (e.g., step, operation, procedure), terms referring to data (e.g., packet, message, user stream, information, bit, symbol, codeword), terms referring to channels, terms referring to network entities (DU (distributed unit), RU (radio unit), CU (central unit), CU-CP (control plane), CU-UP (user Terms such as O-DU (O-RAN (open radio access network) DU), O-RU (O-RAN RU), O-CU (O-RAN CU), O-CU-UP (O-RAN CU-CP), O-CU-CP (O-RAN CU-CP)), which refer to components of the device, are examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used. In addition, terms such as '... part', '... device', '... object', '... body', etc. used below may mean at least one shape structure or may mean a unit that processes a function.

[0028] In addition, in the present disclosure, expressions such as "more than" or "less than" may be used to determine whether a specific condition is satisfied or fulfilled, but this is merely a description for expressing an example and does not exclude descriptions such as "more than" or "less than." A condition described as "more than" may be replaced with "more than," a condition described as "less than" may be replaced with "less than," and a condition described as "more than and less than" may be replaced with "more than and less than." In addition, hereinafter, "A" to "B" mean at least one of elements from A (including A) to B (including B). hereinafter, "C" and / or "D" mean at least one of "C" or "D," that is, including {"C", "D", "C" and "D"}.

[0029] Although the present disclosure describes various embodiments using terms used in some communication standards (e.g., 3rd Generation Partnership Project (3GPP), European Telecommunications Standards Institute (ETSI), extensible radio access network (xRAN), open-radio access network (O-RAN), etc.), these are merely examples for explanation. The various embodiments of the present disclosure can be easily modified and applied to other communication systems.

[0030] Figure 1 illustrates a wireless communication system.

[0031] Referring to FIG. 1, FIG. 1 illustrates a base station (110) and a terminal (120) as some of the nodes utilizing a wireless channel in a wireless communication system. Although FIG. 1 illustrates only one base station, the wireless communication system may further include other base stations identical or similar to the base station (110).

[0032] The base station (110) is a network infrastructure that provides wireless access to the terminal (120). The base station (110) has coverage defined based on the distance at which a signal can be transmitted. In addition to the base station, the base station (110) may be referred to as an 'access point (AP)', 'eNodeB (eNB)', '5th generation node', 'next generation nodeB (gNB)', 'wireless point', 'transmission / reception point (TRP)', or other terms having equivalent technical meanings.

[0033] The terminal (120) is a device used by a user and communicates with the base station (110) via a wireless channel. The link from the base station (110) to the terminal (120) is referred to as a downlink (DL), and the link from the terminal (120) to the base station (110) is referred to as an uplink (UL). In addition, although not shown in FIG. 1, the terminal (120) and another terminal may communicate with each other via a wireless channel. In this case, the link between the terminal (120) and another terminal (device-to-device link, D2D) is referred to as a sidelink, and the sidelink may be used interchangeably with the PC5 interface. In some other embodiments, the terminal (120) may be operated without the involvement of a user. According to one embodiment, the terminal (120) is a device that performs machine type communication (MTC) and may not be carried by the user. Additionally, according to one embodiment, the terminal (120) may be an NB (narrowband)-IoT (internet of things) device.

[0034] The terminal (120) may be referred to as a terminal, or other terms such as 'user equipment (UE),' 'customer premises equipment (CPE),' 'mobile station,' 'subscriber station,' 'remote terminal,' 'wireless terminal,' 'electronic device,' or 'user device,' or other terms having equivalent technical meanings.

[0035] As web-based services proliferate, networks grow in scale and the complexity of their configurations can increase. This increased complexity can lead to various problems, including failures, outages, packet loss, and / or increased latency. Therefore, a management service entity may be established to manage the network nodes (or network elements (NEs)) that comprise the network. For example, the management service entity may include at least one of an entity related to software defined networks (SDN) or a service management orchestration (SMO).

[0036] In one embodiment, a management service entity may be configured to manage a plurality of network nodes. For example, the management service entity may be controlled based on account information registered with the management service entity.

[0037] A network service manager can manage multiple managed service entities. Each managed service entity can be managed through a different account (or software application). Consequently, managing a large number of managed service entities can be challenging for the network service manager. The following specification describes technical features for integrating and managing multiple managed service entities.

[0038] Figure 2 illustrates an example of a management service entity for managing multiple network nodes.

[0039] Referring to FIG. 2, a management service entity (210) may be used to obtain log data regarding the operation of a plurality of network nodes (230). For example, the plurality of network nodes (230) may include NE (230-1) and NE (230-2). For example, the plurality of network nodes (230) may include a virtual machine, a virtual switch, a physical switch, a router, a central unit (CU), a distributed unit (DU), and / or a radio unit (RU). For example, a network node may be referred to as a network element (NE) or a network device.

[0040] Each of the plurality of network nodes (230) can generate log data regarding operations. Each of the plurality of network nodes (230) can transmit the log data regarding operations to the management service entity (210). For example, the management service entity (210) can receive the log data generated based on various formats. The management service entity (210) can monitor the log data. Based on monitoring the log data, the management service entity (210) can identify (or determine) an anomaly regarding the plurality of network nodes (230).

[0041] According to one embodiment, the management service entity (210) may acquire data collected from network nodes (e.g., network node (230-1), network node (230-2)). The acquired data may be configured in a specific value format. Information regarding normal and abnormal ranges of the acquired data may be stored in the memory of the management service entity (210). The management service entity (210) may provide an alarm based on the acquired data.

[0042] For example, the management service entity (210) can obtain log data regarding a network node (e.g., network node (230-1), network node (230-2)). The management service entity (210) can receive the log data from the network node. The management service entity (210) can provide an alarm based on whether the log data satisfies a specified condition. For example, the management service entity (210) can generate an alarm based on obtaining specific log data.

[0043] According to one embodiment, the management service entity may include at least one of an entity related to a software defined network (SDN) or an entity related to a service management orchestration (SMO). First, the SDN architecture will be described in FIG. 3 . The SMO architecture will be described in FIG. 4 .

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

[0045] Referring to FIG. 3, SDN (300) may include an application layer (310), a control plane layer (320), and / or a data plane layer (330).

[0046] The application layer (310) may include one or more applications used for control operations, including routing and / or load balancing. The applications may have exclusive control over a set of resources exposed by the SDN controller. The applications may invoke or collaborate with other applications.

[0047] The control plane layer (320) may include an SDN controller (321). The SDN controller (321) may be used to control overall network resources. The SDN controller (321) may obtain network information and provide the obtained information to applications.

[0048] The data play layer (330) may include at least one NE (331). At least one NE (331) may include at least one physical switch and / or at least one virtual switch.

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

[0050] While existing network nodes (or NEs, network equipment) operate independently based on a data plane and a control plane, in SDN (300), the data plane and the control plane of the network node can be separated. The SDN controller (321) can perform the operation of the control plane of the network node. The SDN (300) can operate based on an algorithm for network control. Therefore, in SDN (300), the network can be managed and controlled based on a specified algorithm without the intervention of an administrator. In addition, at least one NE (331) constituting the network can be managed through the SDN controller (321). At least one NE (331) can support at least one of REST (representational state transfer protocol), NETCONF (network configuration protocol), or RESTCONF (representational state transfer configuration protocol) in order to operate in conjunction with the SDN controller (321). The SDN controller (321) can control at least one NE (331) using at least one of REST, NETCONF, or RESTCONF.

[0051] Figure 4 shows an example of an architecture for SMO.

[0052] Referring to FIG. 4, the logical architecture of O-RAN may include a service management orchestration (SMO) (400), an O-eNB (405), an O-RU (410), an O-DU (420), an O-CU-CP (431), an O-CU-UP (432), a Near-RT RIC (440), and a Non-RT RIC (450).

[0053] The SMO (400) may be responsible for RAN management among various management domains (e.g., RAN management, core management, transport management, E2E (end-to-end) slice management) in a service provider's network. For RAN management, the SMO (400) may provide RAN optimization using the FCAPS (fault, configuration, accounting, performance, security) interface and the Non-RT RIC (450).

[0054] The O-eNB (405) may be a node providing an access network in an LTE communication system. For the O-eNB (405), reference may be made to the descriptions of the base station (110) of FIG. 1. The O-RU (410), O-DU (420), O-CU-CP (431), and O-CU-UP (432) may be network entities (or nodes) for providing an access network in an NR communication system.

[0055] The Near-RT RIC (440) is a logical node for customizing RAN functionality for new services or regional resource optimization. The Near-RT RIC (440) may provide functions such as network intelligence (e.g., policy enforcement, handover optimization), resource assurance (e.g., radio-link management, advanced self-organized network (SON)), and resource control (e.g., load balancing, slicing policy). The Near-RT RIC (440) may be connected to an O-eNB (405), an O-CU-CP (431), an O-CU-UP (432), and / or an O-DU (420). Near-RT RIC (440) can communicate with O-eNB (405), O-CU-CP (431), O-CU-UP (432), and / or O-DU (420). RIC (440) can be connected to each node through E2 interface. In addition, the interface between O-CU-CP (431) and O-DU (420) can be referred to as F1-c interface. The interface between O-CU-UP (432) and O-DU (420) can be referred to as F1-u interface. In the following description, DU and O-DU, CU-CP and O-CU-CP, CU-UP and O-CU-UP can be used interchangeably.

[0056] The Non-RT RIC (450) is implemented within the SMO (400) and can communicate with the Near-RT RIC (440) via the A1 interface. Policy management services, enrichment information services, and ML (machine learning) model management services can be provided via the A1 interface. The Non-RT RIC (450) can drive content delivered via the A1 interface.

[0057] O-Cloud (460) is a cloud computing platform consisting of a set of physical infrastructure nodes that meet O-RAN requirements to host relevant O-RAN functions (e.g., Near-RT RIC (440), O-CU-CP (431), O-CU-UP (432), and O-DU (420)), supporting software components (e.g., operating system, virtual machine monitor, container runtime, etc.), and / or appropriate management and orchestration functions.

[0058] Although the O-CU-CP (431) and the O-CU-UP (432) are illustrated in FIG. 4 according to the separation of the control plane and the user plane, the embodiments of the present disclosure are not limited thereto. As a non-limiting example, the O-CU-CP (431) and the O-CU-UP (432) may be understood as one O-CU (430). In addition, although FIG. 4 exemplifies one Near-RT RIC (440), according to various embodiments, multiple Near-RT RICs may exist for the O-RAN architecture. The multiple Near-RT RICs may be implemented with multiple hardware located at the same physical location or may be implemented through virtualization using one hardware.

[0059] According to one embodiment, a multi-layer orchestrator may include an orchestrator in an upper layer and an orchestrator in a lower layer. The upper layer may be referred to as a global orchestrator. The lower layer may be referred to as a domain orchestrator. The global orchestrator may concentrate one or more domain orchestrators. The global orchestrator may register one or more domain orchestrators and provide information about the status of one or more domain orchestrators. For example, the global orchestrator may provide FCAPS (fault, configuration, alarm, performance, statistics) information about one or more domain orchestrators. In the following description, examples of the operations of the global orchestrator and one or more domain orchestrators to provide the above-described functions will be described. Hereinafter, the global orchestrator will be described as an electronic device. The domain orchestrator will be described as a management service entity.

[0060] FIG. 5 illustrates an example of an electronic device and one or more management service entities.

[0061] Referring to FIG. 5, the electronic device (510) may be configured to manage a plurality of management service entities (520) (e.g., the management service entity (210) of FIG. 2). The electronic device (510) may provide a service for integrating a plurality of management service entities (520) that operate as individual systems to operate as a single system. For example, the electronic device (510) may provide a service for integrating a plurality of management service entities (520) to operate as a single system using a software application. For example, the electronic device (510) may provide a service for managing a plurality of management service entities (520) based on registration of the plurality of management service entities (520).

[0062] According to one embodiment, the electronic device (510) may include a front end (511) and a back end (512). For example, the front end (511) may be configured to provide a user interface. The front end (511) may configure at least one of a layout, a menu, an object (or a visual object), an element, and / or a button of the user interface. The front end (511) may provide information obtained from the back end (512) through the user interface. For example, the front end (511) may obtain information from the back end (512) using an application programming interface (API) and provide (e.g., display) the obtained information through the user interface.

[0063] For example, the backend (512) may include a gateway service management unit (513), an external service management unit (514), and / or an integrated service management unit (515).

[0064] The gateway service management unit (513) may be configured to perform API calls, management, and / or monitoring. The gateway service management unit (513) may perform the function of an API portal.

[0065] The external service management unit (514) may be configured to manage information regarding a plurality of management service entities (520). The external service management unit (514) may be configured to store information regarding a plurality of management service entities (520) and identify whether each of the plurality of management service entities (520) is connected and / or identify authentication information regarding each of the plurality of management service entities (520) via a northbound interface (NBI).

[0066] The integrated service management unit (515) may be configured to manage a plurality of management service entities (520). For example, the integrated service management unit (515) may be configured to transmit and receive data from the plurality of management service entities (520). The integrated service management unit (515) may request data from the plurality of management service entities (520) and, based on the request, obtain data from each of the plurality of management service entities (520). The integrated service management unit (515) may provide data to each of the plurality of management service entities (520).

[0067] According to one embodiment, a management service entity (e.g., management service entity (520-1)) may include an NBI service management unit (521) and / or a security service management unit (522).

[0068] The NBI service management unit (521) may be configured to perform operations related to NBI, which is an interface between the control plane layer and the application layer. The NBI service management unit (521) may provide NBI services so that the electronic device (510) can access the functions of the management service entity (520-1).

[0069] The security service management unit (522) may be configured to authenticate an account of the management service entity (520-1). The security service management unit (522) may perform a function for generating a token and providing the generated token to the electronic device (510). The security service management unit (522) may perform a function for verifying the validity of a token and / or session.

[0070] Referring to FIG. 5, an electronic device (510), which is an upper system, can access the functions of each of a plurality of management service entities (520), which are lower systems, through the NBI provided by the plurality of management service entities (520). For example, the electronic device (510) can control the functions of each of the plurality of management service entities (520). The electronic device (510) can register the plurality of management service entities (520) through a registration procedure.

[0071] For example, the electronic device (510) may provide a user interface for monitoring each of the plurality of management service entities (520) after registration procedures for the plurality of management service entities (520) are completed. For example, the electronic device (510) may provide a user interface including a visual object corresponding to each of the plurality of management service entities (520). The visual object corresponding to the management service entity (520-1) may include at least one of the number of alarms generated by the management service entity (520-1) (e.g., alarms related to FCAPS), the severity of the alarms, and / or information about the management service entity (520-1).

[0072] For example, the electronic device (510) may provide a user interface for controlling the functions of each of the plurality of management service entities (520) without additional authentication procedures (e.g., login) after registration procedures for the plurality of management service entities (520) are completed.

[0073] For example, the electronic device (510) can extend a subsystem by performing a registration procedure for a new management service entity.

[0074] According to one embodiment, the electronic device (510) may provide a service for centrally managing a network. For example, the electronic device (510) may provide a service for integrating subsystems including an SDN controller and / or an orchestrator (e.g., SMO) using an open API. For example, the electronic device (510) may be configured for at least one of a large-scale enterprise (e.g., campus network automation (CAN)), private 5G, macro cell 5G, and / or a data center.

[0075] According to an embodiment, multiple registrations can be performed for the same domain orchestration portals. By performing multiple registrations for the same domain orchestration portals, massive-scale services can be provided through the electronic device (510).

[0076] In one embodiment, the electronic device (510) may be configured for an enterprise (e.g., a campus network automation (CNA)). For example, the electronic device (510) may support user-specific network authentication (e.g., wired and / or wireless authentication) via an authentication server. When configured for an enterprise, the electronic device (510) may provide large-scale integrated portal functionality and services for managing various management service entities (e.g., orchestrators) through a single system.

[0077] According to one embodiment, the electronic device (510) may be configured for a data center (e.g., a software defined data center (SDDC)). For example, the electronic device (510) may act as a controller and / or orchestrator of network elements including virtual machines (VMs), virtual switches, physical switches, and / or routers. When the electronic device (510) is configured for a data center, it may provide services for managing a large number of network elements.

[0078] According to one embodiment, the electronic device (510) may be configured for a private network management system (PNMS) of a private 5G network. The PNMS may perform user-based universal subscriber identity module (USIM) management functions. The electronic device (510) may be configured to manage USIM numbers along with a MAC address-based policy.

[0079] In one embodiment, the electronic device (510) may be configured for SMO. The electronic device (510) may provide a single portal service for infrastructure management and / or a RAN intelligent controller (RIC).

[0080] Figure 6 illustrates an example of the operation of an electronic device for registering a management service entity.

[0081] Referring to FIG. 6, in operation 601, the electronic device (510) may obtain registration information regarding a management service entity to be registered through a user interface provided by the front end (511). For example, the obtained registration information may include at least one of a name, type, protocol, IP address, port, and / or account information regarding the management service entity. The front end (511) may transmit (or provide) the obtained information to the back end (512).

[0082] According to one embodiment, the electronic device (510) may display a window (or pop-up window) for performing a registration procedure for a management service entity (520-1) through a user interface. The displayed object may include an input area (e.g., a text field) for entering at least one of a name, a type, a protocol, an IP address, a port, and / or account information regarding the management service entity (520-1). The electronic device (510) may perform a registration procedure for the management service entity (520-1) based on the information obtained through the input area.

[0083] In operation 602, the gateway service management unit (513) can obtain at least one of a name, a type, a protocol, an IP address, a port, and / or account information regarding the management service entity (520-1) from the front end (511). The gateway service management unit (513) can transmit (or provide) at least one of the name, the type, the protocol, the IP address, the port, and / or account information regarding the management service entity (520-1) to an external service management unit (514) for managing registration information of a plurality of management service entities (520).

[0084] In operation 603, the external service management unit (514) may store at least one of the name, type, protocol, IP address, port, and / or account information regarding the management service entity (520-1) in the memory of the electronic device (510). The external service management unit (514) may identify whether the management service entity (520-1) is connected and / or the authentication information of the management service entity (520-1) through the NBI of the management service entity (520-1).

[0085] Referring to operations 601 to 603, the electronic device (510) may perform a registration procedure for the management service entity (520-1) based on information about the management service entity (520-1), which is a subsystem to be managed. Based on the registration procedure, the management service entity (520-1) may be set as one of a plurality of management service entities (520) managed by the electronic device (510).

[0086] According to one embodiment, a user of an electronic device (510) may perform a registration procedure for a management service entity using a user interface provided by the electronic device (510). Examples of user interfaces provided for the registration procedure for a management service entity will be described below in FIGS. 7A, 7B, and 7C.

[0087] FIGS. 7A, 7B, and 7C illustrate examples of user interfaces provided on an electronic device for registering a management service entity.

[0088] Referring to FIG. 7A, the electronic device (510) may provide a user interface (700) using a front end (511). The user interface (700) may be used to manage a plurality of management service entities (520). For example, the user interface (700) may be provided by a software application stored in the electronic device (510).

[0089] According to one embodiment, the user interface (700) may include a menu (710) for displaying statistical information of a plurality of management service entities (520), a menu (720) for displaying abnormal alarms of a plurality of management service entities (520), a menu (730) for managing accounts of a plurality of management service entities (520), and / or a menu (740) for managing registration of a plurality of management service entities (520).

[0090] The user interface (700) illustrated in FIG. 7A may be provided in a state where no management service entity is registered with the electronic device (510). For example, the user interface (700) may include an area (711) for displaying information about all management service entities registered with the electronic device (510). The user interface (700) may include an area (712) for displaying information about management service entities according to tenants set as favorites. The user interface (700) may include an area (713) for displaying information about management service entities according to regions set as favorites.

[0091] For example, if no management service entity is registered to the electronic device (510), an object (716) indicating that no management service entity is registered may be displayed in each of the areas (711) to (713).

[0092] According to one embodiment, the user interface (700) may include an object (715) for managing a registered management service entity. The electronic device (510) may display a menu (716) based on an input to the object (715). The menu (716) may be displayed adjacent to the object (715). The menu (716) may include an element (717) for registering a management service entity. The electronic device (510) may display the user interface (700) illustrated in FIG. 7B based on an input to the element (717). However, the present invention is not limited thereto. The element for registering a management service entity may be displayed in various ways within the user interface (700).

[0093] Referring to FIG. 7b, the electronic device (510) may display a window (750) through the user interface (700) based on an input for registering a management service entity (e.g., an input for an element (717)).

[0094] For example, a window (750) may be displayed to obtain information for registering a service management entity. The window (750) may be displayed to obtain at least one of a name, type, protocol, IP address, port, and account information regarding the service management entity.

[0095] The window (750) may include an input area (751) (or text field) for entering a name for the service management entity. The window (750) may include an input area (752) (or text field) for entering a type for the service management entity. The window (750) may include an input area (753) (or text field) for entering a protocol for the service management entity. The window (750) may include an input area (754) (or text field) for entering an IP address for the service management entity. The window (750) may include an input area (755) (or text field) for entering a port for the service management entity. The window (750) may include an input area (756) (or text field) for entering an account name among account information for the service management entity. The window (750) may include an input area (757) (or text field) for entering a password among account information regarding the service management entity.

[0096] The window (750) may include an element (758) for canceling the registration procedure of the service management entity and an element (759) for completing the registration procedure of the service management entity. For example, the electronic device (510) may perform the registration procedure for the service management entity based on identifying the input for the element (759) after information about the service management entity is input in the input area (751) to the input area (757). Operations according to FIG. 6 may be performed for the registration procedure for the service management entity. After the registration procedure for the service management entity is completed, the electronic device (510) may display the user interface (700) illustrated in FIG. 7c.

[0097] Referring to FIG. 7c, the electronic device (510) can display a visual object (760) regarding a registered service management entity within an area (711) of the user interface (700). The visual object (760) can be used to display information (e.g., alarm information) regarding the registered service management entity.

[0098] For example, the visual object (760) may display text (761) indicating the total number of alarms generated from the registered service management entity. The visual object (760) may include an object (762) indicating the number of alarms having a first severity among the total alarms, an object (763) indicating the number of alarms having a second severity among the total alarms, and / or an object (764) indicating the number of alarms having a third severity among the total alarms. For example, the first to third severities may be distinguished according to the importance of the alarms. For example, if the total number of alarms generated from the registered service management entity is 127, the user of the electronic device (510) may confirm that the number of alarms having the first severity is 2, the number of alarms having the second severity is 125, and the number of alarms having the third severity is 0.

[0099] For example, a visual object (760) may include text (765) indicating the number of tenants for the registered service management entity and text (766) indicating the number of regions for the registered service management entity.

[0100] According to one embodiment, the visual object (760) may be displayed based on account information when the service management entity and the electronic device (510) are not connected. For example, the visual object (760) may be displayed based on a registration procedure for the service management entity. The visual object (760) may be displayed when an account authentication procedure for the service management entity has not been performed. For example, based on the registration procedure, the electronic device (510) may obtain alarm information for the service management entity through an API. The electronic device (510) may display the visual object (760) based on the obtained alarm information.

[0101] In some embodiments, an account authentication procedure (e.g., a login procedure) for a service management entity may be performed together with a registration procedure. If the account authentication procedure is performed together with the registration procedure, the visual object (760) may be used to control the registered service management entity. In some embodiments, if the account authentication procedure is not performed together with the registration procedure, the electronic device (510) may perform an account authentication procedure for the service management entity based on an input to the visual object (760). Specific operations of the electronic device (510) for performing the account authentication procedure via the visual object (760) will be described below with reference to FIGS. 10, 11A, 11B, and / or 11C.

[0102] Figure 8 illustrates an example of the operation of an electronic device for monitoring information about a management service entity via NBI.

[0103] Referring to FIG. 8, a plurality of management service entities (520) may be registered in an electronic device (510). In operation 801, the electronic device (510) may provide information about the plurality of management service entities (520) through a user interface. The front end (511) may periodically request information about the plurality of management service entities (520) from the back end (512). The front end (511) may request information about registered service management entities from the back end (512) at a specified time interval.

[0104] In operation 802, the gateway service management unit (513) of the electronic device (510) may forward a request received from the front end (511) to the integrated service management unit (515). The gateway service management unit (513) may request the integrated service management unit (515) for managing a plurality of management service entities (520), which are subsystems, to obtain information about the plurality of management service entities (520).

[0105] In operation 803, the integrated service management unit (515) may obtain registration information for a plurality of management service entities (520), which are subsystems, from the external service management unit (514). The registration information for the plurality of management service entities (520) may include information obtained according to a registration procedure of each of the plurality of management service entities (520). For example, the registration information for the management service entity (520-1) may include at least one of a name, a type, a protocol, an IP address, a port, and / or account information regarding the management service entity (520-1).

[0106] In operation 804, the integrated service management unit (515) may request information about the plurality of management service entities (520) from the NBI service management unit of each of the plurality of management service entities (520) (e.g., the NBI service management unit (521) of the management service entity (520-1)) based on the registration information about the plurality of management service entities (520). The integrated service management unit (515) may receive (or obtain) information about the plurality of management service entities (520) from each of the plurality of management service entities (520). The operations of requesting information about the plurality of management service entities (520) from the plurality of management service entities (520) and receiving information about the plurality of management service entities (520) may be performed sequentially or in parallel.

[0107] According to one embodiment, a user of an electronic device (510) may perform a monitoring operation on a management service entity using a user interface provided by the electronic device (510). In the following FIGS. 9A, 9B, and 9C, examples of a user interface for providing information on a management service entity obtained according to a monitoring operation will be described.

[0108] FIGS. 9A, 9B, and 9C illustrate examples of user interfaces provided on an electronic device for managing a management service entity.

[0109] Referring to FIG. 9A, the user interface (700) may include an area (711) for displaying information about all management service entities registered in the electronic device (510). The user interface (700) may include an area (712) for displaying information about management service entities according to tenants set as favorites. The user interface (700) may include an area (713) for displaying information about management service entities according to regions set as favorites.

[0110] For example, five management service entities may be registered in an electronic device (510). The electronic device (510) may display a visual object for each of the five management service entities on a user interface (700). The electronic device (510) may include a visual object (901) corresponding to a first management service entity, a visual object (902) corresponding to a second management service entity, a visual object (903) corresponding to a third management service entity, a visual object (904) corresponding to a fourth management service entity, and a visual object (905) corresponding to a fifth management service entity. The visual objects (901) to (905) may be displayed in an area (711) for displaying information about all management service entities registered in the electronic device (510).

[0111] For example, within an area (712) for displaying information about a management service entity according to a tenant set as a favorite, a visual object (906) corresponding to a management service entity according to a first tenant and a visual object (907) corresponding to a management service entity according to a second tenant may be displayed.

[0112] For example, within an area (712) for displaying information about a management service entity according to a region set as a favorite, a visual object (908) corresponding to a management service entity according to a first region may be displayed.

[0113] According to one embodiment, the electronic device (510) can identify an input to a menu (730) for account management of multiple management service entities (520). Based on the input to the menu (730), the electronic device (510) can display a user interface (700) as illustrated in FIG. 9B.

[0114] Referring to FIG. 9B, the electronic device (510) may display a screen for managing accounts (or users) of a plurality of management service entities (520) through the user interface (700). For example, the user interface (700) may include an area (911) for displaying a list of the plurality of management service entities (520) and an area (912) for displaying accounts (or users) for the plurality of management service entities (520). The electronic device (510) may display accounts (or users) for each of the plurality of management service entities (520) within the area (912). The electronic device (510) may display, within the area (912), a role, a number of sessions, a status, an account creation time, a last login IP, and / or a last login time according to the accounts for each of the plurality of management service entities (520).

[0115] For example, the electronic device (510) may identify accounts for the plurality of management service entities (520) through the NBI of each of the plurality of management service entities (520) and obtain information about the accounts (e.g., roles, number of sessions, status, account creation time, last login IP, and / or last login time) according to the accounts. The electronic device (510) may display a user interface (700) based on the information about the accounts.

[0116] According to one embodiment, the electronic device (510) may provide a service for managing accounts for a plurality of management service entities (520).

[0117] For example, the electronic device (510) may display an object (913) on the user interface (700) for performing a search for a specific account among the accounts displayed in the area (912).

[0118] For example, the electronic device (510) may provide services for adding, deleting, and / or modifying accounts. As an example, the electronic device (510) may display an object (914) for adding an account on the user interface (700). Based on an input to the object (914), the electronic device (510) may display the user interface (700) illustrated in FIG. 9C.

[0119] Referring to FIG. 9c, the electronic device (510) may display a window (920) for adding an account through the user interface (700) based on an input for adding an account (e.g., an input for an object (914)). The window (920) may be displayed as an overlay on the screen illustrated in FIG. 9b.

[0120] For example, a window (920) may be displayed to obtain information for adding an account. The window (920) may be displayed to obtain at least one of a name for the service management entity, an account (or user) name, a password, a role, and a password for re-authentication.

[0121] The window (920) may include an input area (921) (or text field) for entering a name for the service management entity. The window (920) may include an input area (922) (or text field) for entering an account (or user) name. The window (920) may include an input area (923) (or text field) for entering a password. The window (920) may include an input area (924) (or text field) for confirming the password. The window (920) may include an input area (925) (or text field) for entering a role for the service management entity. The window (920) may include an input area (926) (or text field) for entering a password for re-authentication.

[0122] The window (920) may include an element (927) for canceling the process for adding an account and an element (928) for completing the process for adding an account. For example, the electronic device (510) may complete the process for adding an account based on identifying an input for the element (928) after information about an account to be added is entered in the input area (921) to the input area (926). When the process for adding an account is completed, information about the added account may be displayed in the area (912) of the user interface (700) of FIG. 9B.

[0123] Figure 10 illustrates an example of the operation of an electronic device for controlling a management service entity.

[0124] Referring to FIG. 10, a plurality of management service entities (520) may be registered in an electronic device (510). In operation 1001, the electronic device (510) may provide information about the plurality of management service entities (520) through a user interface. The electronic device (510) may display a visual object corresponding to each of the plurality of management service entities (520) through the user interface. The electronic device (510) may identify an input for one of the visual objects corresponding to the plurality of management service entities (520). For example, the front-end (511) of the electronic device (510) may request account authentication for the management service entity (520-1) to the back-end (512) based on identifying an input for the management service entity (520-1) among the visual objects corresponding to the plurality of management service entities (520).

[0125] In operation 1002, the gateway service management unit (513) of the electronic device (510) may forward a request received from the front end (511) to the integrated service management unit (515). The gateway service management unit (513) may request the integrated service management unit (515) for managing a plurality of management service entities (520), which are subsystems, to obtain information for account authentication for the management service entity (520-1).

[0126] In operation 1003, the integrated service management unit (515) may obtain registration information (e.g., account information) for the management service entity (520-1) from the external service management unit (514). The registration information for the management service entity (520-1) may include information obtained according to the registration procedure of the management service entity (520-1). For example, the registration information for the management service entity (520-1) may include at least one of a name, a type, a protocol, an IP address, a port, and / or account information regarding the management service entity (520-1). However, the present disclosure is not limited thereto.

[0127] In operation 1004, the integrated service management unit (515) may perform an account authentication procedure through the authentication URL of the management service entity (520-1) using the registration information (e.g., account information) for the management service entity (520-1). For example, the security service management unit (522) of the management service entity (520-1) may generate a token for redirection based on identifying that the registration information (e.g., account information) for the management service entity (520-1) is valid. The security service management unit (522) of the management service entity (520-1) may transmit (or provide) the generated token to the electronic device (510). For example, the security service management unit (522) of the management service entity (520-1) may transmit the generated token to the electronic device (510) by adding the generated token to a header. The electronic device (510) can receive a token from the management service entity (520-1) and store the received token in memory.

[0128] In operation 1005, the front-end (511) of the electronic device (510) may transmit a redirect token and URL information regarding the functions of the management service entity (520-1) to the management service entity (520-1). The management service entity (520-1) may verify the validity of the redirect token and set the functions of the management service entity (520-1) to be controlled from the electronic device (510).

[0129] For example, the management service entity (520-1) may establish a session between the front end (511) of the electronic device (510) and the management service entity (520-1) based on verifying the validity of the token. The front end (511) of the electronic device (510) may store information about the session as a cookie based on the session establishment. Thereafter, the electronic device (510) may control the management service entity (520-1) without additional account authentication procedures.

[0130] According to one embodiment, a user of an electronic device (510) can control a management service entity using a user interface provided by the electronic device (510). Examples of user interfaces for controlling a management service entity will be described in the following FIGS. 11A, 11B, and 11C.

[0131] FIGS. 11a, 11b, and 11c illustrate examples of user interfaces provided in an electronic device to control a management service entity.

[0132] Referring to FIG. 11A, the user interface (700) may include an area (711) for displaying information about all management service entities registered in the electronic device (510). The user interface (700) may include an area (712) for displaying information about management service entities according to tenants set as favorites. The user interface (700) may include an area (713) for displaying information about management service entities according to regions set as favorites.

[0133] For example, five management service entities may be registered in an electronic device (510). The electronic device (510) may display a visual object for each of the five management service entities on a user interface (700). The electronic device (510) may include a visual object (901) corresponding to a first management service entity, a visual object (902) corresponding to a second management service entity, a visual object (903) corresponding to a third management service entity, a visual object (904) corresponding to a fourth management service entity, and a visual object (905) corresponding to a fifth management service entity. The visual objects (901) to (905) may be displayed in an area (711) for displaying information about all management service entities registered in the electronic device (510).

[0134] For example, within an area (712) for displaying information about a management service entity according to a tenant set as a favorite, a visual object (906) corresponding to a management service entity according to a first tenant and a visual object (907) corresponding to a management service entity according to a second tenant may be displayed.

[0135] For example, within an area (712) for displaying information about a management service entity according to a region set as a favorite, a visual object (908) corresponding to a management service entity according to a first region may be displayed.

[0136] According to one embodiment, the electronic device (510) can identify an input to a visual object (901). For example, the electronic device (510) can identify an input to the visual object (901) as an input for controlling a first management service entity. The electronic device (510) can connect to the first management service entity based on the input to the visual object (901). For example, the electronic device (510) can establish a connection with the first management service entity based on the input to the visual object (901). Establishing a connection with the first management service entity can mean that the first management service entity can be controlled via the electronic device (510). For example, the electronic device (510) may establish a connection with a first management service entity based on an input to a visual object (901) and display a user interface (700) as illustrated in FIG. 11b for control over the first management service entity.

[0137] Referring to FIG. 11b, within an area (1110) of the user interface (700), status and / or alarm occurrence history regarding the first management service entity may be displayed. Within an area (1120) of the user interface (700), elements for controlling the first management service entity may be displayed. For example, elements for controlling each of a plurality of network elements connected to the first management service entity may be displayed within the area (1120).

[0138] Referring back to FIG. 11A, the electronic device (510) may identify an input for a visual object (903). For example, the electronic device (510) may identify an input for a visual object (904) as an input for controlling a fourth management service entity. Based on the input for the visual object (904), the electronic device (510) may connect to the fourth management service entity. For example, based on the input for the visual object (904), the electronic device (510) may establish a connection with the fourth management service entity. Establishing a connection with the fourth management service entity may mean that the fourth management service entity can be controlled via the electronic device (510). For example, the electronic device (510) may establish a connection with a fourth management service entity based on an input to a visual object (904) and display a user interface (700) as illustrated in FIG. 11c for control over the fourth management service entity.

[0139] Referring to FIG. 11c, within an area (1130) of the user interface (700), status and / or alarm occurrence history regarding the fourth management service entity may be displayed. Within an area (1140) of the user interface (700), elements for controlling the fourth management service entity may be displayed. For example, elements for controlling each of a plurality of network elements connected to the fourth management service entity may be displayed within the area (1140).

[0140] Referring to FIGS. 11A to 11C , the electronic device (510) can establish a connection with a plurality of management service entities (520) based on account information entered according to a registration procedure. The electronic device (510) can connect to each of the plurality of management service entities (520) to control each of the plurality of management service entities (520). The electronic device (510) can establish a connection with each of the plurality of management service entities (520) to control each of the plurality of management service entities (520). The electronic device (510) can provide a service for controlling each of the plurality of management service entities (520) using a user interface (700). Accordingly, a user of the electronic device (510) can control each of the plurality of management service entities (520) using a software application provided by the electronic device (510).

[0141] Figure 12 is a flowchart illustrating the operation of an electronic device for managing multiple management service entities.

[0142] Referring to FIG. 12, in operation 1210, the electronic device (510) may execute a software application for a first service management entity and a second service management entity. For example, the electronic device (510) may execute the software application based on an input for executing the software application. For example, the software application may provide a service for controlling a plurality of service management entities, including the first service management entity and the second service management entity.

[0143] For example, a first service management entity may be configured to manage a plurality of first network nodes. A second service management entity may be configured to manage a plurality of second network nodes. For example, the plurality of service management entities including the first service management entity and the second service management entity may include at least one of an entity related to a software defined network (SDN) and an entity related to a service management orchestration (SMO). For example, the plurality of network nodes including the plurality of first network nodes and the plurality of second network nodes may include at least one of a central unit (CU), a distributed unit (DU), and a radio unit (RU).

[0144] In operation 1220, the electronic device (510) may perform a registration procedure for a first service management entity and a registration procedure for a second service management entity. For example, the electronic device (510) may perform a registration procedure for the first service entity using a software application. The electronic device (510) may perform a registration procedure for the second service entity using a software application. For example, the electronic device (510) may perform a registration procedure for the first service entity and a registration procedure for the second service entity according to FIGS. 6, 7A, 7B, and / or 7C.

[0145] For example, the electronic device (510) may identify an input for registration of a first service management entity. As an example, the electronic device (510) may identify an input for an element for registration of the first service management entity within a user interface. Based on the input for registration of the first service management entity, the electronic device (510) may display a window for input of at least one of a name, a type, a protocol, an IP address, a port, and first account information regarding the first service management entity. The registration procedure for the first service management entity may be performed based on the input of at least one of a name, a type, a protocol, an IP address, a port, and first account information regarding the first service management entity.

[0146] For example, the electronic device (510) may identify an input for registration of a second service management entity. As an example, the electronic device (510) may identify an input for an element for registration of a second service management entity within a user interface. Based on the input for registration of the second service management entity, the electronic device (510) may display a window for input of at least one of a name, a type, a protocol, an IP address, a port, and second account information regarding the second service management entity. The registration procedure for the second service management entity may be performed based on the input of at least one of a name, a type, a protocol, an IP address, a port, and second account information regarding the second service management entity.

[0147] In operation 1230, the electronic device (510) may establish a connection with a second service management entity while a connection with a first service management entity is established. For example, the electronic device (510) may use a software application to establish a connection with a second service management entity based on second account information that is distinct from the first account information while a connection with the first service management entity is established based on first account information.

[0148] For example, the electronic device (510) may establish a connection with a first service management entity based on first account information using a software application. While the connection with the first service management entity is maintained, the electronic device (510) may establish a connection with a second service management entity based on second account information using the software application.

[0149] In operation 1240, the electronic device (510) may provide (or display) a user interface including a first visual object for controlling a first service management entity and a second visual object for controlling a second service management entity. The electronic device (510) may provide a user interface for a software application. The provided user interface may include a first visual object and a second visual object.

[0150] The first visual object may be displayed for controlling the first service management entity. For example, the first visual object may provide alarm information for the first service management entity. The second visual object may be displayed for controlling the second service management entity. For example, the second visual object may provide alarm information for the second service management entity.

[0151] According to one embodiment, the electronic device (510) may provide configuration information regarding a plurality of first network nodes managed by a first service management entity through a user interface based on an input for a first visual object. The electronic device (510) may provide configuration information regarding a plurality of second network nodes managed by a second service management entity through a user interface based on an input for a second visual object.

[0152] According to one embodiment, the electronic device (510) may receive a token (or redirect token) from the first service management entity based on first account information and establishing a connection with the first service management entity. The first service management entity may generate a token based on the first account information and transmit (or provide) the generated token to the electronic device (510). The electronic device (510) may store the received token in memory. The electronic device (510) may transmit the received token and URL information regarding the function of the first service management entity to the first service management entity. The electronic device (510) may provide a service for controlling the function of the first service management entity through a user interface based on the token and URL information. For example, the electronic device (510) may establish a session with the first service management entity based on the token and URL information. The electronic device (510) may store information regarding the session in memory. For example, information about a session may be stored in a cookie.

[0153] Unlike as described in FIG. 12, according to one embodiment, the electronic device (510) may display the first visual object based on a registration procedure for the first service management entity. The electronic device (510) may display the first visual object even if a connection with the first service management entity is not established based on the first account information. For example, the electronic device (510) may establish a connection with the first service management entity based on the first account information in response to an input for the first visual object. Based on establishing a connection with the first service management entity, the electronic device (510) may control the first service management entity through a user interface.

[0154] Figure 13 illustrates the configuration of an electronic device. Terms such as "...part" and "...device" used hereinafter refer to a unit that processes at least one function or operation, which may be implemented by hardware, software, or a combination of hardware and software.

[0155] Referring to FIG. 13, the electronic device (510) may include a transceiver (1310), a memory (1320), a processor (1330), and a display (1340).

[0156] The transceiver (1310) provides an interface for communicating with other electronic devices within a network. That is, the transceiver (1310) converts a bit string transmitted from the electronic device (510) to another electronic device into a physical signal, and converts a physical signal received from another electronic device into a bit string. That is, the transceiver (1310) can transmit or receive a signal. Accordingly, the transceiver (1310) may be referred to as a modem, a communication unit, a transmit unit, a receive unit, or a transmit / receive unit. In this case, the transceiver (1310) enables the electronic device (510) to communicate with other electronic devices or systems via a backhaul connection (e.g., a wired backhaul or a wireless backhaul) or via a network. The transceiver (1310) may include one or more transceivers.

[0157] The memory (1320) stores data such as basic programs, application programs, and setting information for the operation of the electronic device (510). The memory (1320) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. In addition, the memory (1320) provides stored data upon request from the processor (1330). The memory (1320) may be referred to as a storage unit. For example, the memory (1320) may store data for the operation of components (e.g., front-end (511) or back-end (512)) of the electronic device (510) illustrated in FIG. 5.

[0158] The processor (1330) controls the overall operations of the electronic device (510). For example, the processor (1330) transmits and receives signals via the transceiver (1310). Additionally, the processor (1330) writes and reads data to and from the memory (1320). The processor (1330) may be referred to as a control unit. To this end, the processor (1330) may be configured with multiple processors or include at least one sub-processor. According to various embodiments, the processor (1330) may control the electronic device (510) to perform operations according to various embodiments described in the present disclosure.

[0159] The display (1340) can output visualized information to the user. The display (1340) can include a liquid crystal display (LCD), a plasma display panel (PDP), one or more light emitting diodes (LEDs), and / or one or more organic light emitting diodes (OLEDs).

[0160] According to one embodiment, an electronic device may include a display, at least one processor including a processing circuit, and a memory including one or more storage media storing instructions. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to execute a software application for a first service management entity for managing a plurality of first network nodes and a second service management entity for managing a plurality of second network nodes. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to perform a registration procedure for the first service management entity and a registration procedure for the second service management entity using the software application. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to establish a connection with the first service management entity based on first account information while the connection is established using the software application, with the second service management entity based on second account information distinct from the first account information. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to provide a user interface for the software application, the user interface including a first visual object for controlling the first service management entity and a second visual object for controlling the second service management entity.

[0161] According to one embodiment, the software application may provide a service for controlling a plurality of service management entities, including the first service management entity and the second service management entity.

[0162] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to provide, through the user interface, configuration information about the plurality of first network nodes based on an input to the first visual object.

[0163] According to one embodiment, the registration procedure for the first service management entity may be performed based on input of at least one of a name, a type, a protocol, an IP address, a port, and the first account information regarding the first service management entity. The registration procedure for the second service management entity may be performed based on input of at least one of a name, a type, a protocol, an IP address, a port, and the second account information regarding the second service management entity.

[0164] In one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to identify an input for registration of the first service management entity. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to display a window for input of at least one of a name, a type, a protocol, an IP address, a port, and the first account information relating to the first service management entity, based on the input for registration of the first service management entity.

[0165] In one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to display the first visual object within the user interface based on the input of at least one of a name, a type, a protocol, an IP address, a port, and the first account information relating to the first service management entity.

[0166] In one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to receive a token from the first service management entity based on establishing a connection with the first service management entity based on the first account information. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to store the token in the memory.

[0167] In one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to transmit the token and uniform resource locator (URL) information regarding a function of the first service management entity to the first service management entity. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to provide, through the user interface, a service for controlling the function of the first service management entity based on the token and the URL information.

[0168] In one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to establish a session with the first service management entity based on the token and the URL information. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to store information regarding the session in the memory.

[0169] According to one embodiment, the plurality of service management entities including the first service management entity and the second service management entity may include at least one of an entity related to a software defined network (SDN) and an entity related to a service management orchestration (SMO). The plurality of network nodes including the plurality of first network nodes and the plurality of second network nodes may include at least one of a central unit (CU), a distributed unit (DU), and a radio unit (RU).

[0170] According to one embodiment, a method performed on an electronic device may include executing a software application for a first service management entity for managing a plurality of first network nodes and a second service management entity for managing a plurality of second network nodes. The method may include performing, using the software application, a registration procedure for the first service management entity and a registration procedure for the second service management entity. The method may include establishing, using the software application, a connection with the second service management entity based on second account information, while a connection is established with the first service management entity based on first account information, the connection being distinct from the first account information. The method may include providing a user interface for the software application, the software application including a first visual object for controlling the first service management entity and a second visual object for controlling the second service management entity.

[0171] According to one embodiment, the software application may provide a service for controlling a plurality of service management entities, including the first service management entity and the second service management entity.

[0172] In one embodiment, the method may include providing, through the user interface, configuration information about the plurality of first network nodes based on an input for the first visual object.

[0173] According to one embodiment, the registration procedure for the first service management entity may be performed based on input of at least one of a name, a type, a protocol, an IP address, a port, and the first account information regarding the first service management entity. The registration procedure for the second service management entity may be performed based on input of at least one of a name, a type, a protocol, an IP address, a port, and the second account information regarding the second service management entity.

[0174] According to one embodiment, the method may include an action of identifying an input for registration of the first service management entity. The method may include an action of displaying a window for input of at least one of a name, a type, a protocol, an IP address, a port, and the first account information regarding the first service management entity, based on the input for registration of the first service management entity.

[0175] In one embodiment, the method may include displaying the first visual object within the user interface based on the input of at least one of a name, a type, a protocol, an IP address, a port, and the first account information regarding the first service management entity.

[0176] According to one embodiment, the method may include receiving a token from the first service management entity based on establishing a connection with the first service management entity based on the first account information. The method may include storing the token in the memory.

[0177] According to one embodiment, the method may include an operation of transmitting, to the first service management entity, uniform resource locator (URL) information regarding the token and the function of the first service management entity. The method may include an operation of providing, through the user interface, a service for controlling the function of the first service management entity based on the token and the URL information.

[0178] According to one embodiment, the method may include establishing a session with the first service management entity based on the token and the URL information. The method may include storing information regarding the session in the memory.

[0179] According to one embodiment, a non-transitory computer-readable storage medium may store one or more programs. The one or more programs may include instructions that, when executed by a processor of an electronic device including a display, cause the electronic device to execute a software application for a first service management entity for managing a plurality of first network nodes and a second service management entity for managing a plurality of second network nodes. The one or more programs may include instructions that, when executed by the processor of the electronic device, cause the electronic device to perform a registration procedure for the first service management entity and a registration procedure for the second service management entity using the software application. The one or more programs may include instructions that, when executed by the processor of the electronic device, cause the electronic device to establish a connection with the first service management entity based on first account information, while the connection is established with the first service management entity, based on second account information distinct from the first account information. The one or more programs may include instructions that, when executed by the processor of the electronic device, cause the electronic device to provide a user interface for the software application, the user interface including a first visual object for controlling the first service management entity and a second visual object for controlling the second service management entity.

[0180] According to the above-described embodiment, an integrated service can be provided through a higher-level system (e.g., an electronic device (510)) with independent subsystems (e.g., multiple service management entities (5210)). Users can access the subsystems through a single higher-level system without having to input system information (e.g., account information) each time they access the independent subsystems.

[0181] According to the above-described embodiment, an administrator managing all subsystems can access only the parent system and control the subsystems. Furthermore, the subsystems connected to the parent system can be expanded simply by registering the subsystems.

[0182] According to the above-described embodiment, resources can be reduced because the upper system obtains FCAPS information of the lower systems and provides it through a user interface.

[0183] According to the above-described embodiment, cards for one or more subsystems (e.g., multiple management service entities (520) or domain orchestrators) registered with a higher-level system (e.g., an electronic device (510) or a global orchestrator) may be displayed through a user interface. The displayed cards may display summarized thresholds of FACAPS. In addition, in the higher-level system, single sign-on (SSO)-based authentication may be performed in response to input of the cards. Accordingly, the subsystems may be controlled within the same user interface (or screen) without generating a separate browser pop-up. Based on closing the page for the subsystem, a logout for the subsystem may be performed, and a user interface may be provided to allow entry into another subsystem.

[0184] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0185] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

[0186] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

[0187] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.

[0188] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0189] Meanwhile, although the detailed description of the present disclosure has described specific embodiments, it is obvious that various modifications are possible within the scope of the present disclosure.

Claims

1. In electronic devices, display; At least one processor comprising a processing circuit; and A memory comprising one or more storage media for storing instructions, The above instructions, when individually or collectively executed by the at least one processor, Running a software application for a first service management entity for managing a plurality of first network nodes and a second service management entity for managing a plurality of second network nodes; Using the above software application, a registration procedure for the first service management entity and a registration procedure for the second service management entity are performed, Using the software application, while a connection is established with the first service management entity based on first account information, a connection is established with the second service management entity based on second account information that is distinct from the first account information, Causing the electronic device to provide a user interface for the software application, comprising a first visual object for controlling the first service management entity and a second visual object for controlling the second service management entity; Electronic devices.

2. In the first paragraph, the software application, Providing a service for controlling a plurality of service management entities including the first service management entity and the second service management entity, Electronic devices.

3. In the second paragraph, when the instructions are individually or collectively executed by the at least one processor, Causing the electronic device to provide configuration information about the plurality of first network nodes through the user interface based on an input to the first visual object; Electronic devices.

4. In the first paragraph, the registration procedure for the first service management entity is as follows: is performed based on input of at least one of the name, type, protocol, IP address, port, and the first account information regarding the first service management entity; The above registration procedure for the above second service management entity is as follows: is performed based on input of at least one of the name, type, protocol, IP address, port, and second account information regarding the second service management entity; Electronic devices.

5. In the fourth paragraph, when the instructions are individually or collectively executed by the at least one processor, Identify the input for registration of the above first service management entity, Causing the electronic device to display a window for inputting at least one of a name, a type, a protocol, an IP address, a port, and the first account information regarding the first service management entity based on the input for registration of the first service management entity. Electronic devices.

6. In the fifth paragraph, when the instructions are individually or collectively executed by the at least one processor, Causing the electronic device to display the first visual object within the user interface based on at least one of the inputs of the name, type, protocol, IP address, port, and the first account information regarding the first service management entity; Electronic devices.

7. In the first paragraph, when the instructions are individually or collectively executed by the at least one processor, Based on the first account information, based on establishing a connection with the first service management entity, receiving a token from the first service management entity, causing said electronic device to store said token in said memory; Electronic devices.

8. In the 7th paragraph, when the instructions are individually or collectively executed by the at least one processor, Transmitting URL (uniform resource locator) information about the token and the function of the first service management entity to the first service management entity, Causing the electronic device to provide a service for controlling the function of the first service management entity through the user interface based on the token and the URL information. Electronic devices.

9. In the 8th paragraph, when the instructions are individually or collectively executed by the at least one processor, Based on the above token and the above URL information, establish a session with the first service management entity, causing said electronic device to store information about said session in said memory; Electronic devices.

10. In the first paragraph, a plurality of service management entities including the first service management entity and the second service management entity, Contains at least one entity related to SDN (software defined network) and one entity related to SMO (service management orchestration), A plurality of network nodes including the plurality of first network nodes and the plurality of second network nodes, Containing at least one of a CU (central unit), a DU (distributed unit), and a RU (radio unit), Electronic devices.

11. In a method performed in an electronic device, An operation of executing a software application for a first service management entity for managing a plurality of first network nodes and a second service management entity for managing a plurality of second network nodes; An operation of performing a registration procedure for the first service management entity and a registration procedure for the second service management entity using the software application; An operation of establishing a connection with the second service management entity based on second account information that is distinct from the first account information, while a connection is established with the first service management entity using the software application; and A system comprising a first visual object for controlling the first service management entity and a second visual object for controlling the second service management entity, and comprising an operation for providing a user interface for the software application. method.

12. In the 11th paragraph, the software application, Providing a service for controlling a plurality of service management entities including the first service management entity and the second service management entity, method.

13. In the 12th paragraph, the method, An operation comprising providing configuration information about the plurality of first network nodes through the user interface based on an input for the first visual object. method.

14. In the 11th paragraph, the registration procedure for the first service management entity is as follows: is performed based on input of at least one of the name, type, protocol, IP address, port, and the first account information regarding the first service management entity; The above registration procedure for the above second service management entity is as follows: is performed based on input of at least one of the name, type, protocol, IP address, port, and second account information regarding the second service management entity; method.

15. In a non-transitory computer-readable storage medium storing one or more programs, the one or more programs, when executed by a processor of an electronic device including a display, Running a software application for a first service management entity for managing a plurality of first network nodes and a second service management entity for managing a plurality of second network nodes; Using the above software application, a registration procedure for the first service management entity and a registration procedure for the second service management entity are performed, Using the software application, while a connection is established with the first service management entity based on first account information, a connection is established with the second service management entity based on second account information that is distinct from the first account information, A first visual object for controlling the first service management entity and a second visual object for controlling the second service management entity, and instructions for causing the electronic device to provide a user interface for the software application. Non-transitory computer-readable storage medium.

Images