Network management system and method therefor

Abstract

According to the present invention, a network management system is proposed. The network management system may comprise: a memory configured to store a database in which device or service-related information is recorded; a processor configured to provide a graphical user interface indicating a state of a service and / or a device configuring a network on the basis of the information recorded in the database; and a display configured to output the graphical user interface.

Description

Network management system and method for the same

[0001] The present invention relates to a network management system and a method for the same, and more specifically, to a network management system and a method for the same capable of integrally managing or controlling not only network devices but also services or devices.

[0002] Recently, with the proliferation of various applications requiring high-speed, low-latency, and high-reliability communication within limited areas such as industrial sites or campuses, the construction of Private 5G (hereinafter P5G) networks, which are closed mobile communication networks for specific users, is actively underway. P5G networks are separated from public mobile communication networks and utilize independent frequency resources; by being built and operated independently by companies or institutions, they offer the advantage of maximizing security and service quality.

[0003] A P5G network includes a 5G core and a radio access network (RAN), and various network devices constituting it (e.g., base stations, routers, gateways, MEC servers, etc.) are operated, monitored, and controlled through a centralized or distributed network management system (NMS).

[0004] However, conventional NMSs have primarily focused on providing functions centered on configuration, status, and fault management at the network device level, and currently lack integrated visibility and management capabilities for vertical services or terminal devices actually provided on P5G networks. For example, even when various industry-specific customized services based on P5G are provided, such as smart factories, smart hospitals, and autonomous logistics systems, conventional NMSs cannot provide functions to access or control information at the level of the operational status of such services or various terminals and applications connected to them.

[0005] Accordingly, in order to enhance the practical operational efficiency and problem-solving capabilities of P5G networks, an integrated management system is required that includes not only network devices but also various services and devices connected to them.

[0006] The present invention proposes a network management system.

[0007] The present invention proposes a network management system capable of managing or controlling services on a per-service basis.

[0008] The problems to be solved by the present invention are not limited to the problems to be solved above, and other problems not mentioned will be clearly understood by those skilled in the art to which the present invention belongs from the description below.

[0009] According to one embodiment of the present invention, a network management system is proposed, wherein the system comprises: a memory configured to store a database containing information related to a device or service; a processor configured to provide a graphical user interface that indicates the status of a service and / or device constituting a network based on information recorded in the database; and a display configured to output the graphical user interface, wherein the graphical user interface may include a user interface component for registering, deleting, or modifying at least one service with respect to the network and / or a first graphical user interface component for registering, deleting, or modifying the device with respect to the service.

[0010] Additionally or alternatively, the graphical user interface includes a second graphical user interface component for displaying the status of network devices constituting the network, and the second graphical user interface component may include a graphical user interface component for displaying the location of the network devices on a map corresponding to the network.

[0011] Additionally or alternatively, the first graphical user interface component may include a graphical user interface component for indicating the status of the service and / or device for each of the plurality of services.

[0012] Additionally or alternatively, at least one device may be registered for each of the plurality of services, and configured to set an individual Quality of Service (QoS) profile for each of the plurality of services.

[0013] Additionally or alternatively, the processor may be configured to set a first QoS profile to ensure throughput of a preset standard for a first service and to set a second QoS profile to ensure latency of a preset standard for a second service.

[0014] Additionally or alternatively, each of the above multiple services may be configured to operate on a network slice different from other services on an end-to-end network slice.

[0015] Additionally or alternatively, the processor may be configured to allocate a first network slice to a first service and a second network slice to a second service.

[0016] Additionally or alternatively, the first graphical user interface component includes a graphical user interface component for outputting detailed information of a device registered with the service, and the detailed information of the device may include at least one of the device's online / offline status information, name, subscriber identification information (IMSI; International Mobile Subscriber Identity), device unique information (IMEI; International Mobile Equipment Identity), or network address information.

[0017] Additionally or alternatively, the processor pairs the device information of the device with the service information of the service to which the device is to be registered, records the paired information in the database, and the device information may include the International Mobile Subscriber Identity (IMSI) of the device and information in which the device's unique information (IMEI) or serial number is matched.

[0018] Additionally or alternatively, the processor may be configured to acquire subscriber identification information of the first device and device unique information or device serial number of the first device as the first device is connected to the network, and to check whether the acquired information matches the matched information recorded in the database.

[0019] Additionally or alternatively, the processor may be configured to perform resource allocation for the first device as the acquired information matches the matched information.

[0020] Additionally or alternatively, the processor may be configured to output an unauthenticated notification to the graphical user interface as the acquired information does not match the matched information.

[0021] Additionally or alternatively, the processor may be configured to form a blacklist by combining the IMSI of the device and the IMEI of the device, and to block the device's connection to the network based on the blacklist.

[0022] Additionally or alternatively, the processor may be configured to collect traffic usage by service or by QoS profile and output a graphical user interface containing the collected traffic usage by service or usage by QoS profile.

[0023] Additionally or alternatively, the processor may be configured to collect traffic usage per network slice and output a graphical user interface containing the collected traffic usage per network slice.

[0024] According to another embodiment of the present invention, a method for network management is proposed, the method comprising the steps of: creating or storing a database that records information related to a device or service; and

[0025] The method includes the step of outputting a graphical user interface to a display that indicates the status of a service and / or device constituting a network based on information recorded in the database, wherein the graphical user interface may include a user interface component for registering, deleting, or modifying at least one service with respect to the network and / or a first graphical user interface component for registering, deleting, or modifying the device with respect to the service.

[0026] Additionally or alternatively, the method may include the step of obtaining subscriber identification information of the first device and device unique information or device serial number of the first device as the first device is connected to the network; and the step of checking whether the obtained information matches information in which the device unique information or serial number is matched with the subscriber identification information, the information recorded in the database.

[0027] Additionally or alternatively, the method may include the step of performing resource allocation for the first device as the acquired information matches the matched information.

[0028] Additionally or alternatively, the method may include the step of outputting an unauthenticated notification to the graphical user interface as the acquired information does not match the matched information.

[0029] In addition, a computer-readable medium is proposed that stores a computer program executed by a computer or processor for performing the method described above.

[0030] The above-mentioned problem-solving methods are merely some of the embodiments of the present invention, and various embodiments reflecting the technical features of the present invention can be derived and understood by those skilled in the art based on the detailed description of the present invention to be described below.

[0031] The present invention has the following technical effects.

[0032] The present invention has the advantage of being able to display not only network devices but also devices connected thereto as a single user interface (UI) in a network such as P5G, and to provide management or control for this purpose.

[0033] In addition, the present invention performs authentication for a device to be connected to a network, and accordingly, can block service access or use by an unauthenticated device.

[0034] The effects according to the present invention are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art from the following detailed description of the invention.

[0035] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present invention, provide embodiments of the present invention and explain the technical concept of the present invention together with the detailed description.

[0036] FIGS. 1 to 9 illustrate a user interface for a network management system according to the present invention.

[0037] FIG. 10 illustrates a structural diagram of a network management system according to the present invention.

[0038] FIG. 11 illustrates the concept of the registration process for subscriber identification (SIM) information, devices, and services according to the present invention.

[0039] FIG. 12 illustrates the concept of service matching for a device according to the present invention, and the allocation of QoS parameters or network slices of the service.

[0040] FIG. 13 illustrates the relationship between each piece of information or database according to the present invention.

[0041] FIG. 14 shows a flowchart of a device authentication procedure according to the present invention.

[0042] FIG. 15 shows a block diagram of a network management system according to the present invention.

[0043] Hereinafter, embodiments disclosed in this specification will be described in detail with reference to the attached drawings. Identical or similar components regardless of drawing symbols will be assigned the same reference number, and redundant descriptions thereof will be omitted. The suffixes "module" and "part" used for components in the following description are assigned or used interchangeably solely for the ease of drafting the specification and do not inherently possess distinct meanings or roles. Furthermore, in describing embodiments disclosed in this specification, if it is determined that a detailed description of related prior art could obscure the essence of the embodiments disclosed in this specification, such detailed description will be omitted. Additionally, the attached drawings are intended only to facilitate understanding of the embodiments disclosed in this specification; the technical concept disclosed in this specification is not limited by the attached drawings, and it should be understood that they include all modifications, equivalents, and substitutions that fall within the spirit and technical scope of the present invention.

[0044] Terms including ordinal numbers, such as first, second, etc., may be used to describe various components, but said components are not limited by said terms. These terms are used solely for the purpose of distinguishing one component from another.

[0045] When it is stated that one component is "connected" or "connected" to another component, it should be understood that while it may be directly connected or connected to that other component, there may also be other components in between. On the other hand, when it is stated that one component is "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between.

[0046] A singular expression includes a plural expression unless the context clearly indicates otherwise.

[0047] In this application, terms such as “comprising” or “having” are intended to specify the existence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0048]

[0049] The term "Vertical Service" is a shortened form of "Vertical Service." "Vertical Service" refers to a communication service or application designed specifically for a particular industry group, such as manufacturing, healthcare, logistics, energy, or education. Unlike general-purpose communication services, such services are customized to possess characteristics such as high reliability, low latency, and security according to the requirements of each industry domain. To achieve this, technologies such as dedicated network slices, edge computing (MEC), dedicated terminals, or gateways may be applied.

[0050] Vertical services are configured to connect to specific industrial systems (e.g., automation equipment, medical equipment, autonomous transport systems, etc.) in a 5G or private 5G (P5G) network environment to support the smooth and real-time operation of said systems. For example, vertical services can be provided for AGV (Automated Guided Vehicle) control in smart factories, and vertical services can be operated for real-time patient monitoring or remote surgery services in smart hospitals.

[0051] Furthermore, a "Network Slice" refers to a virtualized network structure in which independent logical network instances are created within a single physical network infrastructure, and each instance is configured to satisfy specific service requirements.

[0052] Network slices enable the simultaneous operation of different service types—e.g., Ultra Low Latency Communication (URLLC), Massive Machinery Communication (mMTC), and Extra Large Mobile Broadband (eMBB)—by separating their characteristics in 5G or Private 5G (P5G) environments. In particular, to provide vertical services specialized for specific industrial sectors, dedicated network slices optimized for the communication requirements (latency, reliability, bandwidth, security, etc.) of the service can be configured.

[0053] Each slice enables independent end-to-end network operation, and resource allocation and control for the slice are performed across layers such as the core network, transport network, and Radio Access Network (RAN). This structure provides the technical foundation that allows multiple users, industries, or applications to secure their own unique communication environments without mutual interference within a single network infrastructure.

[0054]

[0055] FIG. 1 illustrates a user interface for a network management system according to the present invention.

[0056] FIG. 1 shows a graphical user interface displayed on a display. The illustrated user interface (101) is for a network management system.

[0057] The user interface (101) may include network management and control (10), network device management (20), vertical service management (30), service management (40), device management (50), and event management (60). Each of these may be referred to as a user interface component.

[0058] Although a structure in which device control (40) is partially included in vertical service control (30) has been proposed, the present invention is not limited thereto.

[0059] A user interface component (10) for network control is intended to display the status of a P5G network and may include network traffic (11), information on the amount of traffic over a certain period of time, registered subscriber identification (SIM) card information, or connected subscriber identification card information (hereinafter, “SIM information”) (12). An administrator or user can grasp the status of the P5G network at a glance through the user interface component (10) for network control.

[0060] A user interface component (20) for controlling network devices is intended to display the status of network devices constituting a P5G network and may include a user interface component (21) for displaying each device connected to the network, an input user interface component (22) for checking the connection structure (topology) of the network devices, or an input user interface component (23) for checking detailed information of the network devices. The user interface component (22) may display the topology of the network devices based on a two-dimensional (2D) or three-dimensional (3D) map.

[0061] An administrator or user can see the status of network devices configuring the P5G network at a glance through a user interface component (20) for network device control. When each user interface component (i.e., an icon) is selected, a user interface component that outputs summary information of each device may be displayed (not shown).

[0062] The user interface component (30) for vertical service control is intended to display the status of services provided in the P5G network. Multiple services may be provided in the P5G network.

[0063] The user interface component (30) may include an input user interface component (31) for registering, deleting, or modifying services to be provided in the P5G network. Through this, services to be provided in the P5G network can be defined. At this time, a QoS (quality of service) profile can be assigned to each service. In addition, a separate application can be configured for each service (e.g., CCTV control).

[0064] The user interface component (30) may include a user interface component (40) for service control for each service. The user interface component (40) for service control may include a user interface component for displaying the status (Healthy) of the service and a user interface component (50) for controlling devices registered with the service.

[0065] Additionally, the user interface component (40) for service control for each service may include an input user interface component (32) for registering, deleting, or modifying devices for services to be provided in the P5G network. Through this, devices necessary to provide the corresponding service can be registered for each service.

[0066]

[0067] A user interface component (40) for service control for each service includes an input user interface component (33) for executing or displaying an application for each service, and when an input to the input user interface component (33) is detected, an application for each service can be executed or displayed.

[0068] A user interface component (40) for service control for each service includes an input user interface component (34) for checking detailed information for each service, and when input for the input user interface component (34) is detected, a user interface component that outputs detailed information for each service may be displayed.

[0069] A user interface component (40) for service control for each service may include a user interface component (50) for device control.

[0070] The user interface component (50) for device control is intended to control devices registered and operating in the P5G network. The user interface component (50) for device control is included within the user interface component (40) for service control for each service, and the registration, deletion, or modification of devices is possible through the aforementioned user interface component (32). The user interface component (50) for device control can display the connection status of each device.

[0071] The user interface component (60) for event control is for managing alarms of each component of the P5G network. More specifically, the user interface component (60) for event control can be configured to output the status of alarms generated from a network, system, service, or device.

[0072]

[0073] FIG. 2 shows a graphical user interface that is output to a display. The illustrated user interface (102) is intended to display details of network traffic (11) of a user interface component (10) for network control. The user interface (102) is displayed when the network traffic (11) illustrated in FIG. 1 is selected, and may include information, typically, regarding received signal strength (strength), delay (latency), uplink throughput, and downlink throughput.

[0074]

[0075] FIG. 3 illustrates a graphical user interface that is output to a display. The illustrated user interface (103) is intended to display details of registered subscriber identification (SIM) card information or connected subscriber identification card information (12) of a user interface component (10) for network control. The user interface (103) is displayed when the SIM information illustrated in FIG. 1 is selected, and may include, for example, information regarding IMSI (International Mobile Subscriber Identity), DNN (data network name), IP address, Cell-ID, network connection status, activation / deactivation selection information, and editing (modification or deletion) operations.

[0076]

[0077] FIG. 4 shows a graphical user interface displayed on a display. The illustrated user interface (104) is intended to display the connection structure of network devices that is displayed when an input user interface component (22) for checking the connection structure (topology) of network devices of a user interface component (20) for network device control is selected.

[0078] Figure 4 shows the interconnection relationships of each network device. At this time, the connection structure of the network devices can be displayed at the location of each network device on an actual map of the area where the P5G network is implemented, using icons, user interface components, etc., representing each network device.

[0079]

[0080] FIG. 5 illustrates a graphical user interface that is output to a display. The illustrated user interface (105) is intended to display detailed information of a network device that is output when an input user interface component (23) for checking detailed information of network devices of a user interface component (20) for network device control is selected. The user interface (150) may include information regarding the name of each network device, CPU usage, system load rate, RAM usage rate, storage capacity usage rate, start date, and uptime (time of continuous normal operation).

[0081]

[0082] FIG. 6 illustrates a graphical user interface displayed on a display. The illustrated user interface (106) includes a user interface component for registering, deleting, or modifying a service that is displayed when an input user interface component (31) for registering, deleting, or modifying a service to be provided in a P5G network of a user interface component (30) is selected. In detail, a user interface component for inputting a service name, DNN, server port, client port, or service portal URL may be displayed.

[0083]

[0084] FIG. 7 illustrates a graphical user interface that is displayed on a display. The illustrated user interface (107) includes a user interface component for registering, deleting, or modifying a device that is displayed when an input user interface component (32) for registering, deleting, or modifying a device to be provided in a P5G network of the user interface component (40) is selected.

[0085] The user interface (107) may include device name, type, registration service, service profile, IP address, status, IMEI (International Mobile Equipment Identity) / IMSI matching status, and IMEI blacklisting enable / disable selection information.

[0086]

[0087] FIG. 8 illustrates a graphical user interface that is output to a display. The illustrated user interface (108) includes a user interface of a service application that is output when an input user interface component (33) for executing or displaying an application of a service of a user interface component (40) is selected. As illustrated, information for controlling or managing the service is displayed as a user interface of a CCTV service application.

[0088]

[0089] FIG. 9 illustrates a graphical user interface that is displayed on a display. The illustrated user interface (109) may include a user interface component that outputs details of a service when an input user interface component (34) for checking details of a service of a user interface component (40) is selected.

[0090] The details of the service may include a list of registered devices and details of each device.

[0091] By enabling detailed information to be displayed on the user interface for each service in this way, the following operations are possible.

[0092] - You can output the status of devices by service or manage the status of devices.

[0093] - Devices can be controlled on a per-service basis. In other words, all devices belonging to a service can be controlled to be disconnected or excluded from the connected network at once.

[0094] QoS profiles can be applied to devices on a service-by-service basis. For example, a QoS profile can be set to guarantee high throughput for CCTV services, and a QoS profile can be set to guarantee low latency for smart factory services.

[0095] - Network slices can be allocated per service. For example, devices in the CCTV service can be assigned to use a network slice independent of the devices in the Smart Factory service.

[0096] In addition, traffic usage can be monitored by service, and the following actions are also possible.

[0097] - You can monitor traffic usage by QoS profile.

[0098] - You can monitor traffic usage by network slice.

[0099] - You can monitor traffic usage by device.

[0100] - Traffic usage can be monitored by DNN.

[0101]

[0102] FIG. 10 illustrates a structural diagram of a network management system according to the present invention. The network management system may include a P5G integrated control system (10) and a service control system (20).

[0103] The P5G integrated control system (10) may include a PTMS (Private 5G Total Management System) front end (1), a system manager (2), a PTMS back end (3), a subscriber identification manager (4), a device manager (5), a service manager (6), and a database (7).

[0104] The PTMS front end (1) is configured to perform functions such as outputting the previously described user interface (101, 102, 103, 104, 105, 106, 107, 108, 109), outputting user interface components included therein, or detecting input from a user (or administrator) therein.

[0105] The system manager (2) is configured to perform the function of managing the P5G integrated control (PTMS) system.

[0106] The PTMS backend (3) can be configured to provide functions such as collecting and processing data, generating and managing alarms and events, and managing a database, in order to provide functions such as outputting the previously described user interface (101, 102, 103, 104, 105, 106, 107, 108, 109), and to provide data to the PTMS frontend in real time.

[0107] The subscriber identification manager (4) is configured to register SIM cards that are registered or used in the P5G network and to manage SIM information.

[0108] The device manager (5) may be configured to register information about a device registered or used in a P5G network, or to manage information about the device. The device manager (5) may manage the SIM information of the device and the service to which the device is registered or used in conjunction. This will be explained in more detail in FIG. 11, which will be described later.

[0109] The service manager (6) can be configured to register or manage vertical services provided by the P5G network. As previously described, a service-specific QoS profile may be set for each service, and devices required to provide the service may be registered. The service manager (6) can be configured to communicate with the service frontend (8) to complete the device registration process.

[0110] The service manager (6) can be configured to manage links for connection with the service's own application.

[0111] The database (7) is an integrated database of PTMS, and SIM information, device information, and service information can be stored in a connected manner. As will be described later, one SIM information (IMSI) is matched to one device information (IMEI), and one device information can be matched to multiple device QoS profiles.

[0112] A QoS profile for a single service can be matched to one service information, and multiple device information (IMEI) can also be matched to one service information.

[0113] The service control system (20) may include a service front end (8) and a service back end (9).

[0114] A service front end (8) may exist for each service. The service front end (8) is configured to perform functions such as outputting the user interface of the service application described above or detecting input from a user (or administrator) therefrom.

[0115] The service front end (8) can be configured to communicate with the service manager (6) through link information (A) and SSO (Single Sign-On) authentication information during the service registration process to connect the service application to the PTMS system.

[0116] A service backend (9) may exist for each service. The service backend (9) may be configured to collect and process data, generate or manage alarms, events, etc., and provide data to the service frontend in real time, in order to provide functions such as outputting a user interface related to the service.

[0117] The service backend (9) can be configured to communicate with the device manager (5) via a link (B) during the device registration process to transmit information. Through this, device information between the P5G integrated control system (10) and the service control system (20) can be matched or synchronized with each other.

[0118]

[0119] FIG. 11 illustrates the concept of the registration process for subscriber identification (SIM) information, devices, and services according to the present invention.

[0120] First, a SIM card (SIM information) can be registered to the P5G network. Then, when registering a device to the P5G network, the registered SIM card and device information can be paired for registration. Accordingly, the combination of the registered SIM card and device information can be configured to be registered to a single service.

[0121]

[0122] FIG. 12 illustrates information generated or required during the registration process of subscriber identification (SIM) information, devices, and services according to the present invention.

[0123] SIM information corresponds to IMSI, and device information corresponds to the device's IMEI, device serial number, etc. As previously mentioned, the registered SIM card and device information are paired, and accordingly, an IMSI / IMEI matching value can be generated. Alternatively, an IMSI / serial number matching value can be generated. In this way, by preparing matching values, or combinations, of SIM (IMSI) and IMEI in advance, combinations of SIM (IMSI) and IMEI to be prohibited from connecting to the network can be placed in a blacklist, and upon a device attempting to connect, the connection can be blocked by checking whether it possesses information corresponding to the blacklist.

[0124] After that, QoS profiles, network slices, and DNN information can be assigned per service.

[0125] For example, devices 1, 2, and 3 are registered to Service 1, and Service 1 may be assigned QoS profile A and network slice 1. Device 4 is registered to Service 2, and Service 2 may be assigned QoS profile B and network slice 2.

[0126]

[0127] FIG. 13 illustrates the relationship between each piece of information or database according to the present invention.

[0128] Service information and device information are shown in Fig. 13.

[0129] Service information may include information about the service name, network slice, allowed QoS profiles, allowed DNN list, and service application links. Service information can be configured by an administrator or a user.

[0130] Service information can be stored or recorded in a service information database (71).

[0131] The SIM information database (72) stores a list of SIM information to be allowed in the P5G network. Additionally, the IMEI database (73) stores a list of IMEI information to be allowed in the P5G network.

[0132] Device information may include information about the device name and device type. This can be configured by an administrator or a user. Additionally, device information may include device-specific information such as a serial number and IMEI information.

[0133] The device information may additionally be configured to include service information and SIM information obtained from the service information database (71) and the SIM information database (72), respectively. This information is determined by the service to which the device is registered and the SIM card inserted into the device.

[0134] Accordingly, to configure device information, the IMEI of the device may be selected from the IMEI database (73), and SIM information corresponding to the SIM card inserted into the device may be selected from the SIM information database (72). Additionally, a service to which the device is to be registered may be selected from the service information database (71). Furthermore, information such as the device name and device type of the device may be selected.

[0135] Accordingly, device information includes configurable information, unique information, service information, and SIM information of the device, and can be stored in the device information database (74).

[0136]

[0137] FIG. 14 shows a flowchart of a device authentication procedure according to the present invention. The device authentication procedure illustrated in FIG. 14 may be performed by a network management system or device such as a PTMS, or by the PTMS backend (3) or device manager (5) illustrated in FIG. 10. Hereinafter, the operation of FIG. 14 will be described as being performed by a network management system.

[0138] The network management system (1000) can be configured to detect devices connected to the network (S1401).

[0139] The network management system (1000) may be configured to obtain device information of the detected device (S1402). And / or, the network management system (1000) may be configured to obtain subscriber identification information of the detected device (S1402).

[0140] The network management system (1000) may be configured to check whether the device information of the detected device, or the device information and subscriber identification information, matches any of the device information stored in the device information database (S1403). At this time, the device information stored in the device information database may include information in which the device's subscriber identification information (IMSI) and device unique information (IMEI) or serial number are matched.

[0141] As the device information or subscriber identification information of the detected device matches any of the device information stored in the device information database, the network management system (1000) may be configured to perform network resource allocation or device control for the detected device (S1404).

[0142] As the device information of the detected device does not match any of the device information stored in the device information database, the network management system (1000) may be configured to disable the detected device or output a notification to indicate that an unauthenticated device is connected to the network (S1405).

[0143]

[0144] FIG. 15 shows a block diagram of a network management system according to the present invention.

[0145] The network management system (1000) may be configured to output a user interface or user interface component for controlling a network, device, or service, as described above, to a display, etc., or to detect input from an administrator or user through the user interface or user interface component and to perform control over the network, device, or service according to the detected input.

[0146] The network management system (1000) may be configured to include memory (1001), a processor (1002), a display (1003), and a transceiver (1004).

[0147] The memory (1001) may be configured to store a database that records information related to a network, device, or service.

[0148] The processor (1002) may be configured to provide a graphical user interface that indicates the status of services and / or devices constituting a network based on information recorded in the database.

[0149] The display (1003) may be configured to output the graphic user interface.

[0150] The graphical user interface may be configured to include a user interface component for registering, deleting, or modifying at least one service with respect to the network and / or a first graphical user interface component for registering, deleting, or modifying the device with respect to the service.

[0151] The above graphical user interface may be configured to include a second graphical user interface component for displaying the status of network devices constituting the network. Additionally, the second graphical user interface component may be configured to include a graphical user interface component for displaying the locations of the network devices on a map corresponding to the network.

[0152] The first graphical user interface component may be configured to include a graphical user interface component for indicating the status of a service and / or device for each of a plurality of services. At least one device may be registered for each of the plurality of services, and an individual Quality of Service (QoS) profile may be configured to be set for each of the plurality of services.

[0153] The processor (1002) may be configured to collect traffic usage by service or by QoS profile and to output a graphical user interface containing the collected traffic usage by service or usage by QoS profile.

[0154] The processor (1002) may be configured to set a first QoS profile to ensure throughput of a preset standard for a first service and to set a second QoS profile to ensure latency of a preset standard for a second service. Accordingly, QoS profiles suitable for the characteristics of each service can be set for each service.

[0155] In addition, each of the above multiple services may be configured to operate on a network slice different from other services on an end-to-end network slice.

[0156] The processor (1002) may be configured to collect traffic usage for each network slice and output a graphical user interface containing the collected traffic usage for each network slice.

[0157] The processor (1002) may be configured to allocate a first network slice to a first service and a second network slice to a second service. Accordingly, traffic can be used from different resources for each service.

[0158] The first graphical user interface component may be configured to include a graphical user interface component for outputting detailed information of a device registered with the service. The detailed information of the device may include at least one of the device's online / offline status information, name, subscriber identification information (IMSI; International Mobile Subscriber Identity), device unique information (IMEI; International Mobile Equipment Identity), or network address information.

[0159] The processor (1002) may be configured to pair the device information of the device with the service information of the service to which the device is to be registered, and to record the paired information in the database. The device information may be configured to include information in which the subscriber identification information (IMSI; International Mobile Subscriber Identity) of the device and the device unique information (IMEI; International Mobile Equipment Identity) or serial number of the device are matched.

[0160] The processor (1002) may be configured to form a blacklist by combining the IMSI of the device and the IMEI of the device, and to block the device's connection to the network based on the blacklist.

[0161] The processor (1002) may be configured to obtain subscriber identification information of the first device and device unique information or device serial number of the first device as the first device is connected to the network. The processor (1002) may be configured to check whether the obtained information matches the matched information recorded in the database.

[0162] The processor (1002) may be configured to perform resource allocation for the first device as the acquired information matches the matched information.

[0163] The processor (1002) may be configured to output an unauthenticated notification to the graphical user interface as the acquired information does not match the matched information.

[0164] The processor (1002) may be configured to collect traffic usage by service or by QoS profile and to output a graphical user interface containing the collected traffic usage by service or usage by QoS profile.

[0165] The transceiver (1004) may be configured to receive information related to the status of the device or the status of the network device.

[0166] For descriptions of network management systems or devices not described with reference to FIG. 15, refer to the descriptions given with reference to FIG. 1 to FIG. 14.

[0167]

[0168] In addition, as another aspect of the present invention, the operation of the above-described proposal or invention may be provided as code that can be implemented, practiced, or executed by a "computer" (a comprehensive concept including a system on chip (SoC) or (micro)processor, etc.), or as a computer-readable storage medium or computer program product that stores or contains said code, and the scope of the present invention may be extended to said code or as a computer-readable storage medium or computer program product that stores or contains said code.

[0169]

[0170] The detailed description of the preferred embodiments of the present invention disclosed above is provided to enable those skilled in the art to implement and practice the present invention. Although the present invention has been described with reference to preferred embodiments, those skilled in the art will understand that various modifications and changes can be made to the present invention as described in the following claims. Accordingly, the present invention is not intended to be limited to the embodiments shown herein, but to be given the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. As a network management system, Memory configured to store a database containing information related to a device or service; A processor configured to provide a graphical user interface indicating the status of services and / or devices constituting a network based on information recorded in the above database; and It includes a display configured to output the above graphical user interface, and A system comprising a graphical user interface for registering, deleting, or modifying at least one service with respect to the network and / or a first graphical user interface component for registering, deleting, or modifying the device with respect to the service.

2. In paragraph 1, the graphic user interface is, It includes a second graphical user interface component for displaying the status of network devices constituting the above network, and A system comprising a second graphical user interface component for displaying the locations of the network devices on a map corresponding to the network.

3. In paragraph 1, the first graphic user interface component A system comprising a graphical user interface component for indicating the status of a service and / or device for each of a plurality of services.

4. In paragraph 3, at least one device is registered for each of the plurality of services, and A system configured such that an individual QoS (Quality of Service) profile is set for each of the above plurality of services.

5. In paragraph 4, the processor A system configured to set a first QoS profile to guarantee throughput of a preset standard for a first service, and to set a second QoS profile to guarantee latency of a preset standard for a second service.

6. A system according to paragraph 3, wherein each of the plurality of services is configured to operate on a network slice different from other services on an end-to-end network slice.

7. In paragraph 6, the above processor A system configured to allocate a first network slice to a first service and a second network slice to a second service 8. In paragraph 1, the first graphic user interface component It includes a graphical user interface component for outputting detailed information of a device registered with the above service, and A system in which detailed information of the above device includes at least one of the online / offline status information, name, subscriber identification information (IMSI; International Mobile Subscriber Identity), device unique information (IMEI; International Mobile Equipment Identity), or network address information of the above device.

9. In paragraph 1, the processor Pairing the device information of the above device with the service information of the service to which the device is to be registered, and recording the paired information in the database, A system in which the above device information includes subscriber identification information (IMSI; International Mobile Subscriber Identity) of the device and information matched with the device unique information (IMEI; International Mobile Equipment Identity) or serial number of the device.

10. In paragraph 9, the processor As a first device is connected to the above network, the subscriber identification information of the first device and the device unique information or device serial number of the first device are obtained, and A system configured to check whether the above-mentioned acquired information matches the above-mentioned matched information recorded in the above-mentioned database.

11. In Clause 10, the above processor A system configured to perform resource allocation for the first device as the above-mentioned acquired information matches the above-mentioned matched information.

12. In Clause 10, the above processor A system configured to output an unauthenticated notification to the graphical user interface as the above-mentioned acquired information does not match the above-mentioned matched information.

13. In paragraph 8, the processor A blacklist is constructed by combining the IMSI of the above device and the IMEI of the above device, and A system configured to block the device's access to the network based on the above blacklist.

14. In paragraph 4, the processor A system configured to collect traffic usage by the above-mentioned service or by the above-mentioned QoS profile, and to output a graphical user interface including the collected traffic usage by service or usage by QoS profile.

15. In paragraph 6, the processor A system configured to collect traffic usage for each of the above network slices and to output a graphical user interface containing the collected traffic usage for each network slice.

16. As a method for network management, A step of creating or storing a database that records information related to a device or service; and The method includes the step of outputting a graphical user interface to a display indicating the status of a service and / or device constituting a network based on information recorded in the above database. A method comprising: a graphical user interface for registering, deleting, or modifying at least one service with respect to the network and / or a first graphical user interface component for registering, deleting, or modifying the device with respect to the service.

17. In Paragraph 16, As a first device is connected to the network, a step of obtaining subscriber identification information of the first device and device unique information or device serial number of the first device; and A method comprising the step of verifying whether the device unique information or serial number recorded in a database, which is the information obtained above, matches the information matched with the subscriber identification information.

18. In Paragraph 17, A method comprising the step of performing resource allocation for the first device as the above-mentioned acquired information matches the above-mentioned matched information.

19. In Paragraph 17, A method comprising the step of outputting an unauthenticated notification to the graphical user interface as the above-mentioned acquired information does not match the above-mentioned matched information.

20. A computer-readable medium storing a computer program executed by a computer or processor for performing a method according to any one of paragraphs 16 through 19.

Images