Method and device for operating and managing one or more sites on basis of digital twin

Abstract

Disclosed are a method and device for operating and managing one or more sites on the basis of a digital twin. According to one aspect of the present disclosure, provided is a method implemented by a computing system including one or more computing devices in order to operate and manage one or more sites, the method comprising the steps of: collecting operation indices of one or more network nodes disposed in each of the one or more sites; visualizing, in a first virtual space, operation indices for one or more candidate sites among the one or more sites; and visualizing, on the basis of user interaction with the first virtual space, an operation index for a target site, which is determined among the one or more candidate sites, in a second virtual space simulating the target site.

Description

Method and device for operating and managing one or more sites based on digital twins

[0001] The present disclosure relates to a method and device for operating and managing one or more sites based on a digital twin.

[0002] The content described below merely provides background information related to the present embodiment and does not constitute prior art.

[0003] In network-based systems, it's crucial to intuitively understand and manage network status through real-time data collection and visualization across various network nodes (e.g., radio units, access points, terminal devices, etc.). Existing network monitoring systems have been limited to providing simple text-based data, failing to reflect the physical location of network nodes.

[0004] These limitations are even more pronounced in environments where network nodes are distributed. In particular, in complex operating environments involving multiple sites, the lack of integrated management of individual site status reduces operational efficiency, making it difficult to quickly detect and respond to network failures or inefficiencies.

[0005] Furthermore, when individual sites have complex structures, such as multi-story buildings, existing systems struggle to effectively visualize the physical locations and status of network nodes. These visual limitations hinder the intuitive understanding of problems occurring on specific floors or network status changes resulting from inter-floor interactions, hindering managers' ability to quickly diagnose and respond to issues.

[0006] The present disclosure aims to provide a method and device capable of comprehensively managing the operational status of a network including one or more sites.

[0007] The present disclosure aims to provide a method and device capable of effectively visualizing the operational status of a network by taking into account the structural characteristics of individual sites (e.g., multi-story buildings).

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

[0009] According to one aspect of the present disclosure, a method is provided for operational management of one or more sites, implemented by a computing system including one or more computing devices, comprising: collecting operational metrics of one or more network nodes deployed in each of the one or more sites, wherein the operational metrics include at least one of resource performance of a corresponding network node, a network connection status, a connected network service quality, alarm data according to a failure occurrence, and event data according to a status change; visualizing operational metrics for one or more candidate sites among the one or more sites on a first virtual space; and visualizing operational metrics for a target site determined among the one or more candidate sites based on a user's interaction with the first virtual space on a second virtual space that simulates the target site.

[0010] According to another aspect of the present disclosure, there is provided a computing system comprising: a memory for storing commands; and at least one processor, wherein the at least one processor executes the commands to collect operational metrics of one or more network nodes deployed in each of one or more sites, wherein the operational metrics include at least one of resource performance of a corresponding network node, a network connection status, a connected network service quality, alarm data according to a failure occurrence, and event data according to a status change; and visualizing operational metrics for one or more candidate sites among the one or more sites on a first virtual space, and visualizing operational metrics for a target site determined among the one or more candidate sites based on a user's interaction with the first virtual space on a second virtual space that simulates the target site.

[0011] According to another aspect of the present disclosure, a computer program stored on a computer-readable recording medium is provided to execute the processes included in the above-described method.

[0012] According to an embodiment of the present disclosure, the efficiency and reliability of network management can be improved by comprehensively managing the operational status of a network provided to one or more sites.

[0013] According to an embodiment of the present disclosure, by providing a 3D visualization of the network operation status by considering the structural characteristics of each site (e.g., a multi-story building), the manager can intuitively understand the status of the network.

[0014] According to an embodiment of the present disclosure, by implementing devices supporting various network technologies as digital twins, the status and performance indicators of each device can be effectively visualized and monitored.

[0015] According to embodiments of the present disclosure, digital twins of each network device can be placed in 3D space based on their location information, and the status and performance of the devices can be managed in real time and / or on a periodic basis. This allows for the display of status changes and performance trends over time for network devices on a single screen, enabling administrators to analyze network service operational efficiency and effectively monitor devices.

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

[0017] FIG. 1 is a block diagram schematically illustrating an exemplary digital twin system to which the present disclosure can be applied.

[0018] FIGS. 2A to 2C are exemplary diagrams showing various examples of the layout of a user interface according to one embodiment of the present disclosure.

[0019] FIGS. 3A and 3B are exemplary diagrams referenced to explain the location and status visualization function of one or more sites according to one embodiment of the present disclosure.

[0020] FIGS. 4A to 4C are exemplary diagrams referenced to explain building-level visualization capabilities for a single site according to one embodiment of the present disclosure.

[0021] FIG. 5A and FIG. 5B are exemplary diagrams referenced to explain a layer-level visualization function for a single site according to one embodiment of the present disclosure.

[0022] FIGS. 6A and 6B are exemplary diagrams referenced to explain a past operating indicator visualization function for one or more sites according to one embodiment of the present disclosure.

[0023] FIG. 7 is an exemplary diagram referenced to explain the location visualization and work instruction assignment functions of field workers according to one embodiment of the present disclosure.

[0024] FIG. 8 is a flowchart illustrating a network operation management method according to one embodiment of the present disclosure.

[0025] FIG. 9 is a block diagram schematically illustrating an exemplary computing device that can be used to implement the devices and methods described in the present disclosure.

[0026] Hereinafter, some embodiments of the present disclosure will be described in detail using exemplary drawings. When designating components in each drawing, it should be noted that, where possible, identical components are given the same reference numerals, even if they appear in different drawings. Furthermore, when describing the present disclosure, detailed descriptions of related known structures or functions will be omitted if they are deemed to obscure the gist of the present disclosure.

[0027] In describing components of embodiments according to the present disclosure, symbols such as first, second, i), ii), a), b) may be used. These symbols are only for distinguishing the components from other components, and the nature, order, or sequence of the components are not limited by the symbols. When a part in the specification is said to "include" or "have" a component, this does not mean that other components are excluded, but rather that other components may be included, unless explicitly stated otherwise.

[0028] The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced.

[0029] FIG. 1 is a block diagram schematically illustrating an exemplary digital twin system to which the present disclosure can be applied.

[0030] A digital twin system (10) may include all or part of a digital twin engine (100), one or more network nodes (120), one or more EMS (Element Management System, 130), a network operation management system (140), a GIS server (160), and a user terminal (180). Not all blocks illustrated in FIG. 1 are essential components, and some blocks included in other embodiments may be added, changed, or deleted. Meanwhile, the components illustrated in FIG. 1 represent functionally distinct elements, and at least one of the components may be implemented in a form that is integrated with each other in an actual physical environment.

[0031] The digital twin engine (100) provides monitoring and control functions for one or more network nodes (120). Here, the network nodes (120) may be distributed and deployed at one or more sites providing network services. The network nodes (120) may include all devices that provide or use a network and employ various network technologies (e.g., Private 5G, Wi-Fi, DAS). For example, the network nodes (120) may include a radio unit (RU), a switch, a router, or an access point (AP).

[0032] The digital twin engine (100) can collect data on one or more sites through interaction with a network operation management system (140), and the network operation management system (140) can interact with an EMS (130) that performs network management of individual sites. For example, the EMS (130) can be responsible for fault management, configuration management, security management, performance management, and network domain management for individual sites, and the network operation management system (140) can be responsible for fault management, configuration management, security management, performance management, and network domain management for one or more sites based on interaction with one or more EMSs (130).

[0033] The digital twin engine (100) may include a collection module (102), a 3D space map (104), and a visualization module (106).

[0034] The collection module (102) can collect data on individual network nodes or individual sites from the network operation management system (140). The collection module (102) can collect data periodically according to a predetermined cycle, or can request data from the network operation management system (140) in real time and collect and store the data. To this end, the EMS (130) can collect information such as the connection status, received signal status, and traffic usage of the network nodes (120) it manages and transmit the information to the network operation management system (140).

[0035] The data collected by the collection module (102) may include, for example, one or more of the status of the network node (e.g., normal or abnormal), the resource performance of the network node (e.g., CPU, memory, or traffic usage), the network connection status, the quality of the connected network service, alarm data due to the occurrence of a failure, and event data due to a change in status. The collection module (102) may also collect key performance indicators (KPIs) indicating the quality and performance of each network node. In addition, the collection module (102) may collect various data related to each network node. In the present disclosure, the data collected by the collection module (102) may be referred to as operational metrics of the network node. For example, the operational metrics may include the version of the operating system (OS) installed in the network node, connection port information, the history of work performed (or allocated) for maintenance, and / or the currently scheduled maintenance schedule. Additionally or alternatively, the operational indicators may further include one or more of the following: attribute information of the network node (e.g., manufacturer, name of support service representative, contact information of the representative), installation information of the network node (e.g., installation location and date within the field), wiring information for communication connection or power supply to the network node (e.g., type of wiring, wiring route, etc.), and / or satellite information for the operation of the network node (e.g., configuration information, remote operation representative information, etc.).

[0036] The collection module (102) may provide a manual synchronization function that can immediately check the status of a network node. The manual synchronization function may support the immediate collection and updating of current status data of a specific network node or all network nodes at the request of a user (e.g., a network service operator, field manager, or field worker).

[0037] The visualization module (106) can visualize the locations of network nodes (120) or sites and their corresponding operational indicators on a 3D spatial map (104) or a GIS map received from a GIS server (160). The 3D spatial map (104) may be 3D data representing a specific site or a virtual space replicating a detailed space of the site.

[0038] To visualize the location of a network node or site, the site's geographic location information and the relative location information of network nodes deployed within the site can be utilized. This location information may be, for example, information previously entered by a network service operator, but is not limited thereto. For example, the location of each network node (120) can be identified using tags attached to individual network nodes (e.g., Bluetooth Low Energy (BLE) tags or Ultra-Wideband (UWB) tags).

[0039] The visualization module (106) can visualize not only the current status of network nodes (120) or site(s), but also the past status history. For example, the visualization module (106) can compare and analyze current and past operating indicators to display change history or change trends. As another example, the visualization module (106) can display the results of a comparative analysis with the operating indicators of other devices within the same or similar site.

[0040] The visualization results can be displayed through a user terminal (180). The user terminal (180) may be, for example, a personal computer (PC), but is not limited thereto. As another example, the user terminal (180) may be another type of electronic device, such as a smartphone or tablet PC. That is, the visualization results may be provided through various platforms, such as the web as well as mobile applications. The user can access the platform through the user terminal (180) to check the network connection status and KPI of individual network nodes, and perform bandwidth monitoring to evaluate the quality of service (QoS) of individual network nodes.

[0041] FIGS. 2A to 2C are exemplary diagrams showing various examples of the layout of a user interface according to one embodiment of the present disclosure.

[0042] FIG. 2a shows an example of the layout of a user interface (UI) 20 for network operation management. The UI (20) may include all or part of a virtual space viewer (200) and one or more menu panels (menu panels, 220 and 240).

[0043] The virtual space viewer (200) can visually represent one or more sites where network services are provided and a digital twin of the network nodes deployed at each site. Through the virtual space viewer (200), users can confirm the locations of sites or network nodes and monitor the status (or quality) of the network.

[0044] The virtual space viewer (200) can provide a camera viewpoint control function to enable users to efficiently monitor various locations within the virtual space or network nodes. The camera viewpoint within the virtual space can be manipulated through rotation, zooming in / out, and panning, depending on the user's needs.

[0045] In some examples, the virtual space may be recreated based on Geographic Information System (GIS) data. For example, the virtual space may include a 2D map with the locations of one or more sites represented in the form of pins. Additionally or alternatively, the virtual space may be visualized in a 3D coordinate system and include 3D models replicating individual sites. For example, if the site where the network service is provided is a multi-story building with multiple floors, the virtual space may include a 3D model replicating the structure of the building. Additionally, the virtual space may further include 3D models of not only the overall structure of the building, but also individual floors within the building or one or more physical elements (e.g., furniture, etc.) actually placed within each floor. In some examples, if the connection between the digital twin engine (100) and the GIS server (160) is not supported, the virtual space may provide the locations of one or more sites as a text list and / or an image list.

[0046] In some examples, various UI elements may be integrated into the virtual space to support operational and management functions for network services. These UI elements can display real-time information within the virtual space, such as the status of sites, the status of network nodes, and the connection relationships between network nodes. Users can interact with these UI elements to control and monitor network nodes. Examples of UI elements integrated into the virtual space are described below with reference to FIGS. 3A through 7.

[0047] The menu panels (220 and 240) provide platform users with an interface for controlling various functions and settings. These menu panels (220 and 240) may be implemented, for example, in the form of a header (220) and a sidebar (240). The menu panels (220 and 240) may include buttons for user account management and basic setting functions, such as logging in / logging out, changing personal information, and setting language. This allows users to easily set up personalized environments or perform account-related tasks within the platform. Additionally or alternatively, the menu panels (220 and 240) may provide interactive functions for controlling UI elements integrated within the virtual space or displayed outside the virtual space. For example, the menu panels (220 and 240) may provide buttons for activating or deactivating a function that indicates the locations of field workers within the virtual space, and buttons for performing additional tasks, such as generating reports and exporting data. In some examples, at least one button may be selectively activated or visible depending on the content currently displayed in the virtual space viewer (200). Thus, the menu panels (220 and 240) include various interactive features to enhance the user experience within the platform, and can help users efficiently navigate and control the virtual space and the entire platform.

[0048] Meanwhile, in the UIs described below, menu panels (220 and 240) may be omitted, but this is for ease of identification, and the present disclosure is not limited thereto. That is, it will be clearly understood by those skilled in the art that all or part of the menu panels (220 and 240) illustrated in FIG. 2A or the UI elements included therein may be combined in the UIs described below.

[0049] Figure 2b shows the layout of a UI (22) that supports operational management for one or more sites.

[0050] Referring to FIG. 2b, the UI (22) may include all or part of a field summary container (260), a period summary container (262), and one or more UI controls (264 to 268).

[0051] The site summary container (260) can provide statistical information on the status of one or more sites providing network services at a specific point in time. For example, the site summary container (260) can display real-time aggregated results of the number of sites in normal condition and / or sites in abnormal condition among all sites providing network services. This allows users to determine at a glance the number of sites requiring action.

[0052] The period summary container (262) can provide statistical information on the past status of one or more sites. For example, the period summary container (262) can visualize the trend of changes in the number of sites experiencing failures by unit period (e.g., daily) over a certain past period (e.g., the past week). This allows users to analyze failure occurrence patterns or identify trends in past data.

[0053] One or more UI controls (264-268) may provide various interactive functions for controlling the virtual space, UI elements integrated within the virtual space, or UI elements displayed outside the virtual space. As illustrated in FIG. 2B, the UI controls (264-268) may include, but are not limited to, buttons and / or text fields. In other examples, the UI controls (264-268) may include toggle switches, sliders, dropdown menus, checkboxes, radio buttons, tabs, and the like.

[0054] A user can dynamically control UI elements within the virtual space and / or outside the virtual space through interaction with UI controls (264-268). For example, a first UI control (264) may include a button for registering a new UI element corresponding to a specific scene in the virtual space, or for modifying the location or metadata of an already registered UI element. This allows a user to add a new scene to the virtual space, or update the location and related information of existing data. As another example, a second UI control (266) may include a search tool for searching for UI elements to be displayed in the virtual space viewer (200) among the registered UI elements. For example, the second UI control (266) may include an input field, such as a text field, and a user can input a search query in the field to control the UI element corresponding to a scene satisfying the query to be focused. As another example, a third UI control (268) may include a button for zooming in or out of the virtual space. This allows users to explore the virtual space in more detail or view the entire space, and efficiently review information within the virtual space.

[0055] Examples of information elements provided by the field summary container (260) and the period summary container (262), and UI elements and / or functions that can be controlled by the UI controls (264 to 268), are described below with reference to FIGS. 3a, 3b, and 6a.

[0056] Figure 2c shows the layout of the UI (24) that supports operation management for a single site.

[0057] Referring to FIG. 2c, the virtual space viewer (200) may include all or part of a field profile container (280), an equipment summary container (282), and one or more UI controls (284 to 288).

[0058] The site profile container (280) is an element that displays metadata about a physical space (i.e., a site) corresponding to a virtual space, and may provide identification information such as the name, address, and floor of the site. The site profile container (280) may include UI elements (e.g., text or labels) for displaying each information element.

[0059] The equipment summary container (282) can provide statistical information about network nodes displayed in the virtual space. For example, the equipment summary container (282) can display the real-time aggregated results of the number of normal and / or abnormal network nodes deployed within the site (or a specific floor of the site) currently displayed in the virtual space. This allows the user to determine at a glance the number of network nodes requiring action.

[0060] One or more UI controls (284-288) may provide various interactive functions for controlling the virtual space, UI elements integrated within the virtual space, or UI elements displayed outside the virtual space. As illustrated in FIG. 2C, the UI controls (284-288) may include, but are not limited to, buttons and / or text fields. In other examples, the UI controls (284-288) may include toggle switches, sliders, drop-down menus, checkboxes, radio buttons, tabs, and the like.

[0061] The user can dynamically control UI elements within the virtual space and / or UI elements outside the virtual space through interaction with the UI controls (284 to 288). For example, the fourth UI control (284) may include a button for registering a new UI element corresponding to a specific network node in the virtual space, or for deleting or modifying an already registered UI element. This allows the user to add a new network node to the virtual space, or update information about the location or connection relationship of an existing network node. As another example, the fifth UI control (286) may include a search tool for searching for UI elements to be displayed in the virtual space viewer (200) among the registered UI elements. For example, the fifth UI control (286) may include an input field, such as a text field, and the user can input a search query in the field to control the UI element corresponding to a network node that satisfies the query to be focused. As another example, the sixth UI control (288) may include buttons that can change the virtual space displayed on the virtual space viewer (200) or activate specific monitoring functions. For example, a button included in the sixth UI control (288) may provide a filtering function that selectively visualizes UI elements corresponding to a network node based on whether the network node satisfies a specific condition.

[0062] Examples of information elements provided by the field profile container (280) and the equipment summary container (282), and UI elements and / or functions that can be controlled by the UI controls (284 to 288), are described below with reference to FIGS. 4a to 5b.

[0063] In some examples, the virtual space viewer (200) may further include a minimap container (289). A minimap showing the overall view of the site (or a specific floor of the site) currently displayed in the virtual space viewer (200) may be visualized within the minimap container (289). For example, the minimap may be provided in the form of a two-dimensional flat map of the site or a top-view of a three-dimensional model replicating the site, but is not limited thereto. The user may move the camera viewpoint by clicking or dragging a specific location on the minimap. For example, when the user clicks on the location of a specific network node on the minimap, the camera viewpoint of the virtual space viewer (200) may be adjusted so that a UI element corresponding to the network node is displayed. Through this, even if the currently displayed site is wide, the user can easily move to a specific location.

[0064] Meanwhile, the UI elements (260 to 289) described in FIGS. 2B and 2C can be independently expressed with respect to the camera viewpoint viewing the virtual space. From this perspective, the UI elements (260 to 289) can be referred to as external UI elements or independent UI elements. Meanwhile, in the above, it is assumed that the external UI elements (260 to 289) are expressed together with the virtual space viewer (200) within the content area (e.g., floating or overlaying on the virtual space viewer (200), but the present disclosure is not limited thereto. That is, in another embodiment, at least one external UI element may be placed in a separate location (e.g., the header (220) or the sidebar (240) of FIG. 2A) that is distinct from the area where the virtual space viewer (200) is placed.

[0065] FIG. 3A and FIG. 3B are exemplary diagrams referenced to explain the location and status visualization function of one or more sites according to one embodiment of the present disclosure.

[0066] FIGS. 3A and 3B illustrate various examples of a UI (30) for visualizing the location and status of one or more sites where network services are provided. FIGS. 3A and 3B illustrate virtual spaces (300a and 300b) having different scales. For example, the virtual space (300a) illustrated in FIG. 3A can express the approximate geographical locations of sites where network services are provided with precision at the level of a country or continent, thereby enabling global visualization of one or more sites. The virtual space (300b) illustrated in FIG. 3B expresses the location and status of sites within a specific region in detail, thereby enabling local visualization in which a user can check the exact geographical location of an individual site and its surrounding environment (e.g., roads, buildings, etc.). Switching between scales can be accomplished through a wheel scroll, a pinch gesture, or a click (or touch) of a specific UI element (e.g., a third UI control (268)).

[0067] The virtual space (300a and 300b) may include a map recreated based on GIS data and one or more field markers (310 to 322) corresponding to one or more fields. The locations where the field markers (310 to 322) are placed within the virtual space (300a and 300b) may be determined based on the geographic locations of the corresponding fields. To this end, the user may activate an edit mode via the first UI control (264) to create a new field marker and register corresponding field information (e.g., name, geographic location [latitude / longitude]) or modify information on previously created field markers, but is not limited thereto.

[0068] The site markers (310-322) may include single markers (310-318) corresponding to a single site, and group markers (320-322) corresponding to a site group comprising two or more sites. A site group may be a grouping of sites belonging to the same customer or a grouping of sites managed by the same site manager. This can improve site management efficiency. In other examples, candidate sites within a certain radius may be grouped, taking into account the scale of the virtual space.

[0069] The single markers (310-318) and the group markers (320-322) may have different shapes. For example, as illustrated in FIG. 3A, the single markers (310-318) may have a pin shape, and the group markers (320-322) may have a multiple circle shape, but are not limited thereto. The color of each field marker (310-322) may be dynamically adjusted according to the status of the corresponding field (or field group). Fields may be classified into normal and abnormal states depending on whether they contain a network node that has experienced a failure. For example, field markers (314 and 320) corresponding to a field and field group in an abnormal state may be displayed in red, and the remaining field markers (310, 312, 316, 318, and 322) may be displayed in green or blue, but are not limited thereto.

[0070] In some examples, a user can search for a desired site or site group using the second UI control (266). The user can use search criteria not only for the site or site group itself (e.g., the site's location, name, customer, or site manager), but also for the network nodes deployed at each site.

[0071] In some examples, when a user interacts (e.g., clicks or touches) with a specific site marker (310-322), detailed information about the corresponding target site or group of target sites may be displayed. For example, UI elements containing target site metadata and operational indicators collected for the target site may be selectively visualized.

[0072] Additionally or alternatively, when a user interacts (e.g., clicks or touches) with a specific field marker (310-322), the scale of the virtual space may be automatically adjusted to allow the user to determine the precise geographic location and surrounding environment (e.g., roads, buildings, etc.) of the corresponding target field or group of target fields. For example, if the user interacts with a group marker (320) corresponding to the first field group in the virtual space (300a) illustrated in FIG. 3a, the scale may be converted to a building-level precision, as in the virtual space (300b) illustrated in FIG. 3b. This allows the user to determine the geographic locations of individual fields included in the first field group.

[0073] Additionally or alternatively, when a user interacts (e.g., clicks or touches) with a specific single marker (310-318), a visualization function for the corresponding single scene may be selectively activated. The visualization function for the single scene is described below with reference to FIGS. 4A to 5B.

[0074] The virtual spaces (300a and 300b) may further include group summary containers (330 and 332) that visually provide statistics on the status of sites within individual site groups. These group summary containers (330 and 332) may be positioned around, but are not limited to, corresponding group markers (320 and 322). The group summary containers (330 and 332) may also be selectively visualized based on user interaction with specific group markers (320 and 322).

[0075] The site summary container (260) can visually provide statistics on the current status of one or more sites. For example, the number of sites corresponding to normal and abnormal states can be aggregated and displayed in the site summary container (260). If a user interaction (e.g., a click or touch) is detected on the text (or corresponding text area) indicating the number of sites in an abnormal state, the camera viewpoint of the virtual space viewer (200) can be adjusted so that all sites in an abnormal state are displayed.

[0076] The period summary container (262) may include a graph showing a change trend in the number of sites where failures occurred by unit period (e.g., daily). For example, statistical information on sites where failures occurred over the past week from the current time point may be displayed in the period summary container (262). When a user interaction (e.g., a click or touch) is detected in a portion (e.g., a specific coordinate of the graph) corresponding to the number of sites in an abnormal state at a specific time point in the period summary container (262), a list of sites analyzed as being in an abnormal state at that time may be displayed. When the user selects a specific site from this list, the camera viewpoint of the virtual space viewer (200) may be adjusted so that the site is displayed.

[0077] To provide such visualization capabilities, the digital twin engine (100) can periodically collect information on the connection status and occurrence of faults of network nodes. The digital twin engine (100) can group the collected data by individual site units where network nodes are deployed, and generate status information for the respective sites. Furthermore, status information for a site group can be generated by integrating status information from sites that satisfy specific conditions (e.g., belonging to the same customer or the same site manager). Furthermore, status information from one or more sites can be grouped by specific period (e.g., a week based on the current date) to generate statistical information. This allows users to intuitively check the current status of a specific site or site group, as well as status change trends over a recent period.

[0078] Through the UI (30) described above, users can easily check the actual geographical locations and status of individual sites, enabling them to establish operational strategies and make quick and accurate decisions regarding maintenance. Furthermore, information on sites that experienced failures over a certain period of time can be easily accessed, thereby improving operational efficiency.

[0079] FIGS. 4A to 4C are exemplary diagrams referenced to explain building-level visualization capabilities for a single site according to one embodiment of the present disclosure.

[0080] Figures 4a to 4c illustrate various examples of a UI (40) for providing building-level visualization of a single target site. In building-level visualization, the locations and statuses of all network nodes deployed within the target site can be visually represented. Here, the target site to be visualized can be determined based on, for example, user interaction with single markers (310 to 318) illustrated in Figures 3a or 3b, but is not limited thereto.

[0081] The virtual space (400) may include a building-level 3D model (410) simulating the target site and one or more node markers (420-428) corresponding to network nodes within the target site. The virtual space (400) may visually provide the current location, device type, and / or status of individual network nodes through the node markers (420-428).

[0082] In some examples, the target site may be a building comprising one or more floors. The building-level 3D model (410) may be a 3D model that replicates the overall structure of the target site, as may the virtual space (400). For example, referring to FIG. 4A , the virtual space (400) may include a 3D model (410) that replicates the overall structure of a multi-story building. In the 3D model (410), the floor, ceiling, and intra-story space between the floor and ceiling of the building may be distinguished from each other using the concept of layers. For example, the 3D model (410) may include sub-models (4100, 4200, and 4300) for each of one or more layers, and each sub-model (4100, 4200, or 4300) may include a floor layer (4120, 4220, or 4320) representing the floor of the corresponding layer, a layer layer (4140, 4240, or 4340) representing the space within the layer, and a ceiling layer (4160, 4260, or 4360) representing the ceiling. At least some of the layers (4100-4360) may be selectively made invisible. For example, a user may make one or more of the floor, the ceiling, and the space within the layer invisible through a layer visibility property setting panel.

[0083] The positions where node markers (420 to 428) are placed within the virtual space (400) can be determined based on the relative positions of the corresponding network nodes with respect to the target site. The relative positions with respect to the target site can be defined as specific coordinates on a three-dimensional virtual coordinate system in which the virtual space (400) is expressed. To this end, the user can activate the edit mode through the fourth UI control (284) to create a new node marker and register information (e.g., name, device type, network connection relationship, relative position) of the corresponding network node, or modify (or delete) information on previously created node markers, but is not limited thereto. In some examples, the coordinates of the node markers (420 to 428) can be dynamically determined based on physical location data collected in real time for the network node. To this end, a mapping relationship between the real-world coordinate system and the virtual coordinate system can be determined in advance.

[0084] At least some areas of the node markers (420-428) may have a color that is dynamically determined according to the status of the network node. For example, node markers (420-423, 425-428) corresponding to a normal network node may be expressed in green, and node marker (424) corresponding to an abnormal network node may be expressed in red, but the present invention is not limited thereto. In some examples, the node markers (420-428) may include an icon (not shown) indicating the device type of the network node. As another example, the node markers (420-428) may include a 3D model that simulates the actual shape of the corresponding network node. The representation using a 3D model allows the user to more clearly identify the device type and layout of the network node. The user can effectively review the spatial layout and usage status in advance before expanding the network.

[0085] In some examples, when a user interacts with specific node markers (e.g., clicking, hovering, or touching) (e.g., by clicking, hovering, or touching) on ​​the markers, detailed information about the corresponding network node may be displayed. For example, UI elements including the network node's name, device type, and real-time collected operational indicators may be selectively displayed. To this end, the digital twin engine (100) may periodically collect information about the connection status and occurrence of faults of the network nodes.

[0086] In some examples, the virtual space (400) may further include one or more sensor markers (430-431), each corresponding to one or more sensor nodes. The sensor nodes may include, for example, one or more of a mobility (e.g., a robot, a drone, etc.) moving within the target site, an IoT (Internet of Things) device carried by a visitor to the target site, and an IoT device attached within the target site.

[0087] The locations where the sensor markers (430-431) are placed within the virtual space (400) may be fixed to coordinates registered in advance by the user, or may be dynamically adjusted based on physical locations collected in real time from sensor nodes. For example, if an IoT device (e.g., a visitor bracelet) with a real-time location recognition function is distributed to a visitor at a target site, the movement of the visitor can be expressed in real time in the virtual space (400) through the sensor markers (430-431). Similarly, the mobility may include a sensor and / or a communication module to support real-time location recognition, and the movement of such mobility can be visualized within the virtual space (400) through the sensor markers (430-431). Even when a visitor or mobility moves between floors via an elevator or stairs, the movement status can be dynamically displayed through the sensor markers (430-431).

[0088] In some examples, when a user interacts with specific sensor markers (430-431) (e.g., by clicking, hovering, or touching), detailed information about the corresponding sensor node may be displayed. For example, UI elements including identification information of the sensor node and sensing values ​​measured by the sensor node (e.g., temperature, humidity, energy usage, etc.) may be selectively visualized. This information may be used for environmental monitoring and security management of the site. The shape or color of the sensor markers (430-431) may also be dynamically adjusted depending on the sensing values ​​measured by the sensor node.

[0089] In some examples, the virtual space (400) may selectively visualize only node markers (420-428) and / or sensor markers (430-431) that satisfy certain conditions. For example, the user may search for network nodes of a desired device type (e.g., CCTV, wireless AP, radio unit, etc.) using the fifth UI control (286). As another example, the virtual space (400) may provide a UI element (e.g., an object type selection option panel) that displays a list of device types deployed on site, thereby enabling the user to select a desired device type. Such UI elements may be selectively visualized based on user interaction with a button included in the sixth UI control (288), but are not limited to such examples.

[0090] The site profile container (280) can provide identification information such as the name and address of the target site. The site profile container (280) can additionally provide data collection times for various nodes. This allows the user to clearly recognize when the information displayed on the UI (40) has been updated. The site profile container (280) may further include UI elements that provide a switching function for the target site. For example, when the user clicks the back button included in the site profile container (280), the user can return to the GIS-based virtual space (300a and 300b) described in FIG. 3a or FIG. 3b to visualize one or more sites in their entirety.

[0091] The equipment summary container (282) can visually provide statistics on the current status of one or more network nodes within a target site. For example, the number of network nodes corresponding to normal and abnormal states can be aggregated and displayed in the equipment summary container (282).

[0092] Referring to FIG. 4b, the virtual space (400) may further include one or more linear objects (440 to 447) representing connection relationships between network nodes. For example, the linear objects (440 to 447) may connect a node marker corresponding to a node (e.g., a radio unit) that provides a network to at least one other node and a node marker corresponding to a node that receives a network from the node. Here, the node that receives a network may include not only an end-user node (e.g., a CCTV) but also a relay node (e.g., an AP) that provides a network to other nodes. Through this, the virtual space (400) can intuitively visualize the interconnectivity of the network configuration.

[0093] For network nodes connected via wired cables, linear objects (440-447) can visualize the path along walls, ceilings, or floors, reflecting the actual cable layout. This allows operators to intuitively understand the entire network cable routing path and review the complexity of physical installation in advance.

[0094] In addition to network connection cables, the virtual space (400) may additionally include linear objects (448) corresponding to power cables. To visualize the power cables, markers (450) corresponding to distribution panels within the target site may be additionally displayed in the virtual space (400). These markers (450) indicate the starting point of a power supply path and can visually provide a connection relationship with at least one network node through the linear objects (448). This allows users to intuitively check the status of the power supply network as well as the network connection. In an environment where the Power over Ethernet (PoE) function is applied, network connections and power supply may be achieved through the same linear objects (440-448).

[0095] Linear objects (440-448) may vary in thickness and color depending on the cable type. For example, since optical cables use very thin cables, linear objects may be expressed as thin. Conversely, UTP cables used for wired Internet LAN connections may be expressed as relatively thick cables. Power cables may be expressed as cables thicker than UTP cables, and the antenna connection cables of radio units may be expressed as thick cables of a different texture. This visual differentiation allows users to clearly distinguish between cable types in the virtual space (400).

[0096] The creation and editing of linear objects (440-448) can be performed using an edit mode that the user can activate via the fourth UI control (284). The edit mode provides various tools that allow the user to directly add or modify cable layout paths within the virtual space (400). For example, the user can define a cable route using drag-and-drop, or automatically generate an optimal route by selecting connection points between specific nodes. The user can also click on a specific cable route to modify or delete the properties of that section (e.g., cable type, bandwidth, length, etc.).

[0097] The UI (40) visually displays the types of network and power cables, enabling more effective inventory management and fault response. This allows users to systematically manage on-site connectivity and power supply networks, reducing maintenance time and costs and maximizing operational efficiency.

[0098] The connection visualization feature may be selectively activated based on user interaction with a button included in the sixth UI control (288), but is not limited to this example. In other examples, the connection visualization feature may be always activated.

[0099] Meanwhile, FIG. 4b illustrates an example in which all linear objects (440 to 448) are visually expressed regardless of the camera viewpoint of the virtual space viewer (200), but the present disclosure is not limited thereto. In another example, some of the linear objects (440 to 448) may be occluded or excluded from the viewpoint depending on the camera viewpoint. The visibility of the linear objects (440 to 448) may be adjusted according to user settings. For example, the user may activate an anti-occlusion option to prevent a specific linear object from being occluded by other objects (e.g., floor, ceiling, wall), or may set the corresponding section to be displayed as a dotted line or transparent color to allow recognition of the entire path. As another example, the user may effectively manage the cable wiring status inside the floor or the equipment and connection lines inside the ceiling, which are generally invisible, by making a specific layer (e.g., ceiling or floor) invisible or adjusting the transparency.

[0100] In some examples, the 3D model (410) may be intentionally distorted to avoid visual confusion depending on the camera viewpoint. For example, a linear object (443) may represent a cable arranged along the ceiling of the second floor, but from a certain camera viewpoint, a user may mistake it for a cable arranged along the floor of the third floor. To reduce this confusion, layers of adjacent floors may be expressed with a certain distance between them so that the ceiling and floor of the 3D model (410) are visually clearly distinguishable.

[0101] Fig. 4c exemplarily shows a portion of an intentionally distorted 3D model (410). As illustrated in Fig. 4c, the positions of at least one layer (4260 and / or 4320) may be adjusted such that the ceiling layer (4260) of the lower layer and the floor layer (4320) of the upper layer have a predetermined spacing along a direction perpendicular to the ceiling and floor (e.g., the z-axis direction). Additionally or alternatively, the positions of the floor layer (4240) and the ceiling layer (4260) belonging to the same sub-model may be adjusted such that the spacing between the layers is predetermined. To accommodate the spacing between the layers, portions of linear objects (443 and 447) passing through the multiple layers may be extended. In this process, distorted parts that do not exist in the real world (e.g., vertical extension part (4430) of linear object (443) and vertical extension part (4470) of linear object (447)) can be expressed as dotted lines so that the user can intuitively identify the distorted path.

[0102] The UI (40) described above can intuitively visualize the building structure and network node layout, providing users with efficient network and power supply management tools. This allows users to perform on-site maintenance more efficiently and proactively identify potential problems or areas requiring improvement during network construction or equipment expansion, thereby reducing operating costs and time. Furthermore, operational efficiency can be maximized by quickly identifying the cause and resolving issues when a failure occurs.

[0103] In some examples, the building-level visualization feature may include a viewpoint switching function between a third-person view and a first-person view. For example, when a user interacts with a specific point within a building-level 3D model (410) expressed in a third-person view, the camera viewpoint may switch to a first-person view. This provides the user with an immersive experience, as if they were directly positioned at that point and viewing the interior of the building.

[0104] In some examples, the building-level visualization feature may include a route guidance feature that guides a user through a path between specific points within the building. To this end, the UI (40) may provide an interface that allows the user to select a starting point and / or an ending point. For example, the user may activate the route guidance feature via a specific button included in the sixth UI control (288) and select a starting point and / or an ending point from a building-level 3D model (410) displayed in the virtual space viewer (200). In another example, the user may click on a specific node marker (420-428) or sensor marker (430-431) to request a path that ends at the point corresponding to the corresponding marker. This can reduce on-site travel time during on-site maintenance visits, thereby improving the productivity of field workers.

[0105] FIG. 5A and FIG. 5B are exemplary diagrams referenced to explain a layer-level visualization function for a single site according to one embodiment of the present disclosure.

[0106] FIGS. 5A to 5B illustrate various examples of a UI (50) for providing floor-level visualization for a single site. In floor-level visualization, the location and status of network nodes deployed on a specific floor of a target site can be visually represented. Here, the target floor to be visualized can be determined based on user interaction with, for example, a building-level 3D model (410) illustrated in FIGS. 4A to 4C . For example, when a user clicks on a sub-model (4100, 4200, or 4300) corresponding to a specific floor within the 3D model (410), floor-level visualization for the corresponding floor can be activated. Additionally or alternatively, the UI (50) may provide a button for activating a floor selection or inter-floor movement function via the sixth UI control (288).

[0107] Referring to FIG. 5A, the virtual space (500) may include a floor-level 3D model (5200) that mimics a target floor and one or more node markers (523 to 525) corresponding to network nodes within the target floor. Here, the 3D model (5200) may be any one of the sub-models (4100, 4200, or 4300). As another example, a separate 3D model (5200) may be provided for floor-level visualization. For example, in building-level visualization, sub-models (4100, 4200, or 4300) that express only the rough structure of an individual floor may be used, while in floor-level visualization, a precise 3D model (5200) that includes detailed spatial layout and objects within the floor may be utilized. Through this, the user can check the structure and layout of the floor in detail as well as the network nodes within the floor, and perform operation and maintenance more efficiently.

[0108] In some examples, the virtual space (500) may further include one or more sensor markers (531) corresponding to one or more sensor nodes within the target layer. Additionally or alternatively, the virtual space (500) may further include one or more linear objects (542 to 546) representing connection relationships between network nodes. The node markers (523 to 525), the sensor marker (531), and the linear objects (542 to 546) visualized by the virtual space (500) are identical to or correspond to at least one of the node markers (420 to 428), the sensor markers (430 to 431), and the linear objects (440 to 447) described above in FIGS. 4A and 4B , and therefore, a redundant description thereof will be omitted.

[0109] The site profile container (280) can provide identification information for the target floor along with identification information such as the name and address of the target site. The site profile container (280) can additionally provide data collection time points for various nodes. This allows the user to clearly recognize when the information displayed on the UI (50) was updated. The site profile container (280) may further include a UI element that provides a switching function for the target site or target floor. For example, when the user clicks the back button included in the site profile container (280), the user can return to the GIS-based virtual space (300a and 300b) described in FIG. 3a or 3b to visualize one or more entire sites, or return to the building-level virtual space (400) described in FIGS. 4a and 4b to visualize the entire building.

[0110] The equipment summary container (282) can visually provide statistics on the current status of network nodes within the target layer. For example, the number of network nodes corresponding to normal and abnormal states can be aggregated and displayed in the equipment summary container (282).

[0111] Referring to FIG. 5B, a 3D model (5200) may be intentionally distorted to prevent visual confusion regarding the arrangement or connection relationship of network nodes. The 3D model (5200) may include a floor layer (5240) representing the floor and / or intra-floor space of the target floor, and a ceiling layer (5260) representing the ceiling. The position and / or angle of the ceiling layer (5260) may be adjusted so that at least a portion of the ceiling of the target floor can always be visible, regardless of the camera viewpoint of the virtual space viewer (200). For example, the ceiling layer (5260) may be rotated around a specific axis (e.g., the x-axis or the y-axis) of the virtual coordinate system and / or moved to have a certain distance from the floor layer (5240). Through such adjustments, the intra-floor space and the ceiling can be visualized simultaneously, regardless of the camera viewpoint. In particular, by clearly representing elements such as network nodes and connection lines placed on the ceiling, users can easily grasp the network configuration even in locations that are normally difficult to identify.

[0112] In some examples, the floor layer (5240) and the ceiling layer (5260) may be optionally made invisible or have their transparency adjusted. For example, a user may individually make the floor layer (5240) and the ceiling layer (5260) invisible or adjust their transparency to a desired level through the Layer Visibility Properties Settings panel.

[0113] In some examples, the floor-level visualization feature may include a viewpoint switching function between a third-person view and a first-person view. For example, when a user interacts with a specific point within a floor-level 3D model (5200) expressed in a third-person view, the camera viewpoint may switch to a first-person view. This may provide the user with an immersive experience, as if they were directly positioned at that point and looking inside the target floor. In some examples, the third-person view for the target floor may be referred to as a floor view, and the first-person view for the target floor may be referred to as an indoor view.

[0114] The UI (50) described above can reduce visual clutter by allowing users to focus only on the information necessary for a specific floor. Furthermore, users can utilize the Whole View, Zoom In / Out, and Position Navigation functions to examine network nodes deployed in specific spaces within a floor in detail. These functions are particularly useful for detailed analysis of network node deployment or for intensive inspection of specific areas. Furthermore, the UI (50) loads only a 3D model (5200) for a single floor, thereby eliminating the need to load unnecessary detailed data for the entire building interior, thereby providing fast loading speeds. This effect can be particularly noticeable in large-scale buildings. Furthermore, if building management elements are expanded in the future, data such as space utilization and energy consumption for a specific floor can be analyzed and provided to users through the UI (50), thereby providing practical assistance in establishing building management plans. This allows users to maximize operational efficiency and effectively achieve long-term management goals such as energy savings and space optimization.

[0115] FIGS. 6A and 6B are exemplary diagrams referenced to explain a past operating indicator visualization function for one or more sites according to one embodiment of the present disclosure.

[0116] Figure 6a shows a UI (60) for visualizing operating indicators of a past point in time.

[0117] The UI (60) for the past operating indicator visualization function may include a timeline summary panel (610) that supports selecting a specific past point in time to be reproduced in the virtual space (600). For example, the timeline summary panel (610) may include a UI element (611) for selecting a past date and / or a UI element (612) for selecting a specific time on the date. The UI element (611) may support a user to select a date through a calendar or a drop-down menu. The UI element (612) may support specifying a specific time in hours or minutes through a slider.

[0118] According to the date and time selected by the user (hereinafter, “target time”), the UI (60) can reproduce the operating indicators of the target time in the virtual space (600). For example, the site summary container (260) may display the aggregated results of the number of sites recorded as being in a normal state and / or the number of sites recorded as being in an abnormal state at the target time. Additionally or alternatively, the period summary container (262) may visualize the occurrence trend of failures by unit period for a certain past period (e.g., the past week from the target time) based on the target time. Additionally or alternatively, the shape and / or color of the site markers (314 and 320) may be adjusted depending on the status of each site recorded at the target time.

[0119] Figure 6b illustrates an expanded form of the timeline summary panel (610). The timeline summary panel (610) can be selectively expanded or collapsed based on user interaction. The expanded timeline summary panel (610) can assist the user in selecting a target time point by visualizing the history of detailed items of the operating indicator. The detailed items may include, for example, all or part of alarm occurrence history, event occurrence history, critical performance alarm occurrence history, configuration change history, and / or performance change history.

[0120] For example, the timeline summary panel (610) may include a UI element (613) for visualizing the alarm occurrence history for a day selected by the user (hereinafter, “target date”). The alarm may represent data transmitted to the EMS (130) and / or the network operation management system (140) in charge of the site when a failure occurs in a network node deployed in the site. For example, when a failure occurs such as when the transmission / reception signal strength exceeds a threshold, when the temperature value exceeds a threshold, or when other failures are detected in the flow of transmission / reception packets, an alarm may be generated and transmitted to the EMS (130), and the EMS (130) may transmit the alarm to the network operation management system (140). The UI element (613) may include a heatmap that expresses the number of alarm occurrences by time zone in colors. Here, the number of alarms may be aggregated on a site or network node basis.

[0121] Additionally or alternatively, the timeline summary panel (610) may include a UI element (614) for visualizing the history of event occurrences during a target date. An event may represent data transmitted to the EMS (130) and / or the network operations management system (140) when the status of a network node changes. For example, an event may be generated and transmitted to the EMS (130) when the software of a specific network node is upgraded or the network node is rebooted, and the EMS (130) may transmit the event to the network operations management system (140). The UI element (614) may include a heat map that color-codes the number of event occurrences by time zone. Here, the number of event occurrences may be aggregated on a site or network node basis.

[0122] Additionally or alternatively, the timeline summary panel (610) may include a UI element (615) for visualizing the history of occurrence of critical performance alarms for a target date. Here, the performance represents various performances related to the network node, such as various input / output-related signal status information, and a critical performance alarm may be generated when the performance of the network node falls outside a predetermined critical range. For example, a critical performance alarm may be generated when the session time, packet loss rate, CPU usage, memory usage, and / or traffic of a specific network node falls outside a predetermined critical range. The UI element (615) may include a heat map that color-codes the number of occurrences of critical performance alarms by time zone. Here, the number of occurrences of critical performance alarms may be aggregated on a site or network node basis.

[0123] Additionally or alternatively, the timeline summary panel (610) may include a UI element (616) for visualizing the history of setting changes for a single day on a target date. The UI element (616) may include a heat map that color-codes the number of setting changes by time zone. Here, the setting changes may indicate changes to various setting values ​​for the operation of a field or network node. For example, if a threshold (or threshold range) applied to the aforementioned alarm or critical performance alarm is changed, it may be counted as a setting change. Here, the number of setting changes may be counted on a field or network node basis.

[0124] Additionally or alternatively, the timeline summary panel (610) may include a UI element (617) for visualizing performance change trends over the course of a target date. The UI element (617) may include a graph representing performance over time. The performance over time may, for example, represent an average, maximum, or minimum value at the site or network node level, but is not limited thereto. The UI element (617) may provide a user-selected performance indicator among various performance indicators. For example, the user may select a performance indicator to be added to the UI element (617) via a button (618) displayed on the timeline summary panel (610).

[0125] Through this timeline summary panel (610), the user can check the history of various detailed operating indicators for one day of the target date and, based on this, select a specific time to be reproduced in the virtual space (600).

[0126] Referring back to FIG. 6A, the past operating indicator visualization function can be selectively activated based on user interaction with a timeline button (620) formed in at least one area of ​​the UI (60). For example, when a predetermined interaction (e.g., click or touch) is detected on the timeline button (620), the digital twin engine (100) can retrieve the operating indicator history for a specified period from a database within the network operation management system (140) or a separately provided database. The digital twin engine (100) or the user terminal (180) can dynamically generate the UI (60) based on the retrieved data. To this end, operating indicators such as registered network nodes, connection status, occurrence failure information, and device setting changes can be configured in vector format in adjustable time units through UI elements (611 and 612) and stored in the database. For example, the vector format may be configured as multidimensional data to represent the status of operational indicators in specific time units (e.g., seconds, minutes, hours), and may include, for each time unit, a unique identifier of the network node, a connection status (e.g., normal, disconnected), occurrence of a fault (e.g., fault type and duration), and a history of device setting changes (e.g., changed parameters and change times). Such data may be selectively retrieved according to a time range adjusted by the user through UI elements (611 and 612), and based on the retrieved data, the UI (60) may visually reproduce the network status of a selected past point in time in the virtual space (600). Meanwhile, although FIG. 6A illustrates that the timeline button (620) is displayed on the header (220), the present disclosure is not limited thereto. In another example, the timeline button (620) may be displayed on the sidebar (240), or may be displayed in a floating or overlay manner on the virtual space (700).

[0127] Through the UI (60) described above, users can intuitively analyze past data. Specifically, by digitally twinning the virtual space (600) to a specific point in time when a past failure occurred, users can visually review operational history. This allows users to clearly identify the cause of the failure and quickly analyze and devise countermeasures.

[0128] Meanwhile, in FIG. 6a, an example in which the past operating indicator visualization function is applied to a virtual space (600) for regional visualization of one or more sites is illustrated, but the present disclosure is not limited thereto. Additionally or alternatively, the past operating indicator visualization function may be applied to a virtual space (e.g., virtual space (300a, 400, or 500)) for global visualization of one or more sites, building-level visualization of a single site, or floor-level visualization of a single site. Additionally or alternatively, within the virtual space (600) for regional visualization, the regional scope analyzed by the timeline summary panel (610) may be adjusted for the entire site, a site group, a site, or a network node unit. For example, when a user selects site nodes (314 to 318) corresponding to one or more sites or inputs a search condition into the second UI control (266) to select specific sites, the timeline summary panel (610) may display the past operating indicator history of the corresponding sites. As another example, if a user selects one field node (314-318), the past operational indicator history for the network node unit for that field may be displayed in the timeline summary panel (610).

[0129] FIG. 7 is an exemplary diagram referenced to explain the location visualization and work instruction assignment functions of field workers according to one embodiment of the present disclosure.

[0130] Fig. 7 illustrates a UI (70) for visualizing the locations of field workers. The virtual space (700) may include one or more worker markers (710 and 711), each indicating the location of one or more field workers. The locations where the worker markers (710 and 711) are placed within the virtual space (700) may be dynamically adjusted based on the physical locations collected in real time by terminals (e.g., smartphones or wearable devices) carried by the field workers.

[0131] When a user interacts (e.g., clicks, mouses over, or taps) with a particular worker marker (710 or 711), a profile card (713) of the corresponding field worker may be displayed. The profile card (713) may include, for example, the field worker's name, office address, title, phone number, and / or headshot. Additionally or alternatively, the profile card (713) may include a UI button (e.g., a chat button) for activating a chatting function with the field worker. Additionally or alternatively, the profile card (713) may further include a UI button (e.g., a work order button) for instructing the field worker to visit a particular site and perform maintenance work.

[0132] The location visualization function of field workers can be selectively activated based on user interaction with the worker button (720) formed in at least one area of ​​the UI (70). For example, when a predetermined interaction is detected with the worker button (720), the digital twin engine (100) can collect the locations of field workers from the network operation management system (140) or the terminals of individual field workers. For this purpose, the network operation management system (140) can periodically collect the locations of field workers, but is not limited thereto. In another example, new locations can be collected only when there is a request from the digital twin engine (100), or only when the field worker allows location sharing. Meanwhile, although FIG. 7 illustrates the worker button (720) as being displayed on the header (220), the present disclosure is not limited thereto. In another example, the worker button (720) may be displayed in a sidebar (240) or may be displayed floating or overlaid on the virtual space (700).

[0133] Through the UI (70) described above, users can intuitively identify the field worker closest to the site where the failure occurred and assign a work order to that worker, requiring them to visit the site and take action. This minimizes the time required for troubleshooting. Furthermore, a chat function allows for prior consultation with field workers regarding assignments, enabling efficient management of field worker workflows.

[0134] In some examples, the work order assignment function may include various support functions to facilitate on-site entry by field workers. For example, the digital twin engine (100) may automatically perform pre-security registration for on-site workers to enter the site through linkage with the on-site (e.g., building) security management system. Additionally or alternatively, if on-site access is restricted, the digital twin engine (100) may provide the on-site worker's terminal with the contact information of the on-site security manager and / or the contact information for exiting the site. Additionally or alternatively, the digital twin engine (100) may receive real-time reports related to work progress (e.g., work start, work progress, or work completion) from the on-site worker and share these reports with the customer or on-site manager.

[0135] Through these support functions, the digital twin engine (100) can support the most rapid and accurate maintenance of network nodes installed within a private building.

[0136] In the various examples described in FIGS. 3a to 7, the visualization function may be proactively processed by the digital twin engine (100). That is, the main operations for configuring the UI (30, 40, 50, 60, or 70) may be processed by the digital twin engine (100), and the user terminal (180) may simply perform the role of visually displaying the operation results. For example, the digital twin engine (100) may periodically collect the connection status of network nodes, event data, and / or alarm data, and based on this, dynamically adjust the parameters of UI elements displayed inside or outside the virtual space (300a, 300b, 400, 500, 600, or 700). In this way, the parameters determined by the digital twin engine (100) may be transmitted to the user terminal (180) and reflected in the UI. Alternatively, the digital twin engine (100) may directly render visual elements of the UI (30, 40, 50, 60, or 70) and provide them to the user terminal (180) in a streaming manner. When a user interaction occurs, the digital twin engine (100) may receive interaction detection data from the user terminal (180) and update the rendering result.

[0137] In other examples, the visualization function may be proactively processed by the user terminal (180). That is, the main operations for configuring the UI (30, 40, 50, 60, or 70) may be processed by the user terminal (180), and the digital twin engine (100) may play a role in providing data required for the operations. For example, the user terminal (180) may receive raw data such as the location of the field, the location of the network node, and the operating indicators from the digital twin engine (100), and based on this, may dynamically adjust the parameters of the UI elements displayed inside or outside the virtual space (300a, 300b, 400, 500, 600, or 700). The parameters adjusted by the user terminal (180) may be immediately reflected in the UI (30, 40, 50, 60, or 70).

[0138] In other examples, the visualization function may be processed through collaboration between the digital twin engine (100) and the user terminal (180). For example, the digital twin engine (100) may be responsible for complex operations such as coordinate calculations or statistical analysis, while the user terminal (180) may be responsible for simple conditional processing such as color determination based on status, but the present invention is not limited to these examples.

[0139] FIG. 8 is a flowchart illustrating a network operation management method according to one embodiment of the present disclosure.

[0140] The method illustrated in FIG. 8 can be implemented by executing the functions of the aforementioned digital twin system (10) by a computing system including one or more computing devices. The following description is given from the perspective of the computing system's operation.

[0141] A computing system can collect operational metrics of one or more network nodes deployed in each of one or more sites (S800). The operational metrics may include one or more of the following: resource performance of the corresponding network node, network connection status, connected network service quality, alarm data due to failure occurrence, and event data due to status changes. In some examples, the operational metrics may further include one or more of the following: attribute information of the corresponding network node, the deployment location of the corresponding network node, the type of wiring for communication connection or power supply to the corresponding network node, the wiring path, the work history for maintenance of the corresponding network node, and the currently scheduled maintenance schedule for the corresponding network node.

[0142] The computing system can visualize operational indicators for one or more candidate sites among one or more sites in a first virtual space (S810). The first virtual space may be a virtual space recreated based on Geographic Information System (GIS) data. For example, the first virtual space may be a virtual space (300a) to which global visualization for one or more sites is applied, or a virtual space (300b, 600, or 700) to which local visualization for one or more sites is applied. Here, the candidate sites may be sites included within the geographic range displayed by the virtual space viewer (or within a certain additional radius therefrom). As another example, the first virtual space may express the geographic location of each candidate site in text or image format.

[0143] In step S810, the computing system may generate one or more first UI elements (e.g., site markers (310-322)) representing the geographic location and operational indicators of each candidate site group including a single candidate site or two or more candidate sites. The one or more first UI elements may have different colors depending on whether a failure has occurred at the corresponding single candidate site or group of candidate sites. The one or more first UI elements may include a site-specific UI element (e.g., single markers (310-318)) corresponding to the single candidate site. The one or more first UI elements may also include a group-specific UI element (e.g., group markers (320-320)) corresponding to the candidate site group. The site-specific UI elements and the group-specific UI elements may have different shapes. Optionally, the user interface on which the first virtual space is displayed may include a third UI element (e.g., site summary container (260)) representing statistical information about the current status of each of the one or more sites. The computing system can determine the status of each site as either a normal status or an abnormal status based on whether or not there is a network node currently experiencing a failure at each site. The computing system can generate statistical information by counting the number of sites in a normal status and the number of sites in an abnormal status. Additionally or alternatively, the user interface (e.g., UI (22 or 30)) on which the first virtual space is displayed can include a fourth UI element (e.g., period summary container (262)) that represents a status history for one or more sites over a predetermined past period. The computing system can generate a status history by dividing the past period into predetermined unit periods and counting the number of sites where a network node experiencing a failure exists for each unit period.

[0144] If a user interaction is detected in the first virtual space (S820, "Yes"), the computing system can determine whether the user interaction is for target site determination (S830). For example, if an event (e.g., a touch or click) is detected that selects a first UI element displayed in the first virtual space, it can be recognized that a user interaction for target site determination has occurred.

[0145] If a user interaction for determining a target site is detected (S830, Yes), the computing system can visualize the operational indicators for the target site determined from among one or more sites on a second virtual space that simulates the target site (S840). The second virtual space may be a virtual space (400) to which building-level visualization for a single site is applied, or a virtual space (500) to which floor-level visualization for a single site is applied. For example, the target site may be a building having one or more floors, and the second virtual space may include a building-level 3D model (e.g., 3D model (410)) that simulates the building. The building-level 3D model may include a first layer representing a floor of each floor of the building (e.g., floor layer (4120, 4220, and / or 4320)), a second layer representing a ceiling (e.g., ceiling layer (4160, 4260, and / or 4360)), and a third layer representing an intra-story space between the floor and the ceiling (e.g., story layer (4140, 4240, and / or 4340)). Additionally or alternatively, the second virtual space may include one or more floor-level 3D models (e.g., sub-models (4100, 4200, and / or 4300), or 3D model (5200)) replicating each floor of the building.

[0146] In process S840, the computing system may generate one or more fifth UI elements (e.g., node markers (420 to 428)) corresponding to each of one or more target network nodes arranged in the target site for visualization of the second virtual space. The one or more fifth UI elements may indicate the relative position and operating index of each target network node with respect to the target site. The computing system may adjust each fifth UI element to have a different shape and color depending on the device type and whether a failure occurs of the target network node corresponding to each of the one or more fifth UI elements. The one or more target network nodes may include a first target network node that provides a connection to a network to at least one other node, and a second target network node connected to the network by the first target network node. The computing system may generate a graphic object (e.g., linear object (440 to 447)) connecting the fifth UI element corresponding to the first target network node and the fifth UI element corresponding to the second target network node. The computing system may determine a visual representation (e.g., color, thickness, and / or texture) of a graphical object based on the type of connecting cable physically connecting the first target network node and the second target network node. Optionally, the computing system may generate one or more sixth UI elements (e.g., sensor markers (430-431)) corresponding to one or more sensor nodes within the target scene, respectively, in the visualization of the second virtual space. The sixth UI elements may indicate a relative position of each sensor node with respect to the target scene. The one or more sensor nodes may include, for example, one or more of mobility moving within the target scene, an Internet of Things (IoT) device carried by a visitor to the target scene, and an IoT device attached within the target scene.Optionally, if the site includes a multi-story building, the computing system may intentionally distort the building-level 3D model so that the visual representation of the multi-story building and the building-level 3D model differ in the visualization of the second virtual space. For example, the computing system may space a second layer representing the ceiling of any floor within the multi-story building and a first layer representing the floor of the floor above that floor in a direction perpendicular to the ceiling and the floor. Additionally or alternatively, the second layer representing the ceiling of the floor may space the third layer representing the space within the floor of the floor.

[0147] If it is determined that the user interaction for the first virtual space is not an interaction for target site determination (S830, No), the computing system can execute a function corresponding to the user interaction (S860).

[0148] For example, the computing system may activate a search function for the first UI element based on a user interaction with a second UI element (e.g., a second UI control (266)) arranged in at least one area of ​​a user interface where the first virtual space is displayed. The computing system may receive a search condition for one or more candidate sites through the second UI element. The computing system may search for a single candidate site and a group of candidate sites that satisfy the search condition based on metadata of each candidate site, each group of candidate sites, or network nodes included in each candidate site. Here, the metadata may include, for example, identification information (e.g., name, location, device type, etc.), identification information of a customer company having rights to the site, and / or identification information of a site manager managing the site. The computing system may selectively visualize a site-specific UI element corresponding to a single candidate site searched in the first virtual space and a group-specific UI element corresponding to a group of candidate sites searched. That is, site-specific UI elements and group-specific UI elements that do not satisfy the search condition may be made invisible.

[0149] Additionally or alternatively, the computing system can trigger an operational indicator visualization function for a specific target time point based on a user interaction with an eighth UI element (e.g., UI elements 611 and / or 612) disposed in at least one area of ​​the user interface where the first virtual space is displayed. The computing system can receive, via the eighth UI element, a selection of any target time point during a predetermined past period. The computing system can dynamically adjust the first virtual space so that one or more of the first UI elements represent measured operational indicators at the target time point based on the user interaction with the eighth UI element. The computing system can generate one or more ninth UI elements (e.g., UI elements 613, 614, 615, 616 and / or 617)) in at least one area of ​​the user interface that represent a history of operational indicators for one or more sites during the past period.

[0150] Additionally or alternatively, the computing system may activate a location visualization function of field workers based on a user interaction with an eleventh UI element (e.g., worker button (720)) disposed in at least one area of ​​a user interface on which the first virtual space is displayed. For example, based on the user interaction with the eleventh UI element, one or more tenth UI elements (e.g., worker markers (710-711)) representing real-time geographic locations of each of one or more field workers may be selectively visualized. The computing system may selectively visualize, on the first virtual space, a profile card (e.g., profile card (713)) of a field worker corresponding to the tenth UI element on which the user interaction was detected, based on the user interaction with any one of the tenth UI elements.

[0151] If a user interaction with respect to the second virtual space is detected (S850, Yes), the computing system can execute a function corresponding to the user interaction (S860).

[0152] For example, the computing system may selectively make at least a portion of the three-dimensional model invisible based on a user interaction with a seventh UI element (e.g., a layer visibility property setting panel) positioned in at least one area of ​​the user interface where the second virtual space is displayed. For example, the computing system may selectively make at least one of the first layer, the second layer, and the third layer invisible based on the user interaction with the seventh element.

[0153] Additionally or alternatively, the computing system may activate a floor-level visualization function based on a user interaction with at least one area of ​​the user interface in which the building-level 3D model or the second virtual space is displayed. For example, the computing system may selectively visualize a floor-level target 3D model corresponding to a target floor selected from one or more floors of the building. Here, the floor-level target 3D model may include a fourth layer (e.g., ceiling layer (5260)) representing the ceiling of the target floor, and a fifth layer (e.g., floor layer (5240)) representing the space within the floor of the target floor. The computing system may rotate the fourth layer around one axis of the 3D coordinate system in which the second virtual space is displayed. The rotation axis, which is the reference for the rotation, may be adaptively adjusted depending on a camera viewpoint in which the floor-level target 3D model is displayed in the second virtual space. The computing system can adaptively adjust the rotation axis and rotation angle of the fourth layer so that at least a portion of the ceiling of the target layer is visible to the user's view, regardless of the camera viewpoint. In other words, the visual representation of the target layer in the real world corresponding to the camera viewpoint and the visual representation of the target 3D model at the floor level displayed within the virtual space viewer can be intentionally different.

[0154] FIG. 9 is a block diagram schematically illustrating an exemplary computing device that can be used to implement the devices and methods described in the present disclosure.

[0155] The computing device (90) may include some or all of a memory (900), a processor (920), storage (940), an input / output interface (960), and a communication interface (980). The computing device (90) may structurally and / or functionally include at least a portion of the digital twin system (10). The computing device (90) may be a stationary computing device, such as a desktop computer or a server, as well as a mobile computing device, such as a laptop computer or a smart phone. The computing device (90) may also be implemented with any specialized hardware accelerator capable of processing specific operations in an efficient manner. For example, the computing device (90) may include a graphic processing unit (GPU), a Tensor Processing Unit (TPU), or a neural processing unit (NPU).

[0156] The memory (900) may store a program that causes the processor (920) to perform a method or operation according to various embodiments of the present disclosure. For example, the program may include a plurality of instructions executable by the processor (920), and the above-described method or operation may be performed by executing the plurality of instructions by the processor (920). The memory (900) may be a single memory or a plurality of memories. In this case, information required to perform the method or operation according to various embodiments of the present disclosure may be stored in a single memory or may be divided and stored in a plurality of memories. When the memory (900) is composed of a plurality of memories, the plurality of memories may be physically separated. The memory (900) may include at least one of a volatile memory and a nonvolatile memory. The volatile memory includes a static random access memory (SRAM) or a dynamic random access memory (DRAM), and the nonvolatile memory includes a flash memory.

[0157] The processor (920) may include at least one core capable of executing at least one instruction. The processor (920) may execute instructions stored in the memory (900). The processor (920) may be a single processor or multiple processors.

[0158] Storage (940) maintains stored data even when power supplied to the computing device (90) is cut off. For example, storage (940) may include non-volatile memory, or may include storage media such as magnetic tape, optical disk, or magnetic disk. A program stored in storage (940) may be loaded into memory (900) before being executed by processor (920). Storage (940) may store a file written in a programming language, and a program generated from the file by a compiler or the like may be loaded into memory (900). Storage (940) may store data to be processed by processor (920) and / or data processed by processor (920).

[0159] The input / output interface (960) may provide an interface with an input device such as a keyboard, mouse, etc. and / or an output device such as a display device, printer, etc. A user may trigger the execution of a program by the processor (920) through an input device and / or check the processing result of the processor (920) through an output device.

[0160] The communication interface (980) may provide access to an external network. The computing device (90) may communicate with other devices via the communication interface (980).

[0161] As used herein, the term "engine" is broadly used to refer to a software-based system, subsystem, or process programmed to perform one or more specific functions. An engine may be implemented as one or more software modules or components installed on one or more computing devices at one or more locations. In some instances, one or more computing devices may be dedicated to a particular engine, or in other instances, multiple engines may run on the same computing device (or devices).

[0162] Each component of the device or method according to the present invention may be implemented in hardware, software, or a combination of hardware and software. Furthermore, the functions of each component may be implemented in software, with a microprocessor executing the software functions corresponding to each component.

[0163] Various implementations of the systems and techniques described herein may be implemented as digital electronic circuits, integrated circuits, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include implementations of one or more computer programs executable on a programmable system. The programmable system includes at least one programmable processor (which may be a special purpose processor or a general purpose processor) coupled to receive data and instructions from and transmit data and instructions to a storage system, at least one input device, and at least one output device. Computer programs (also known as programs, software, software applications, or code) include instructions for the programmable processor and are stored on a "computer-readable recording medium."

[0164] A computer-readable recording medium includes any type of recording device that stores data that can be read by a computer system. Such a computer-readable recording medium may be a non-volatile or non-transitory medium such as a ROM, CD-ROM, magnetic tape, floppy disk, memory card, hard disk, magneto-optical disk, storage device, and may further include a transitory medium such as a data transmission medium. Furthermore, the computer-readable recording medium may be distributed across network-connected computer systems, so that computer-readable code can be stored and executed in a distributed manner.

[0165] Although the flowchart / timing diagram of this specification describes each process as being executed sequentially, this is merely an illustrative description of the technical idea of ​​one embodiment of the present disclosure. In other words, a person of ordinary skill in the art to which one embodiment of the present disclosure belongs may modify and apply various modifications and variations by changing the order described in the flowchart / timing diagram without departing from the essential characteristics of one embodiment of the present disclosure, or by executing one or more of the processes in parallel. Therefore, the flowchart / timing diagram is not limited to a chronological order.

[0166] The above description is merely an example of the technical idea of ​​the present embodiment, and those skilled in the art will appreciate that various modifications and variations can be made without departing from the essential characteristics of the present embodiment. Therefore, the present embodiments are not intended to limit the technical idea of ​​the present embodiment, but rather to explain it, and the scope of the technical idea of ​​the present embodiment is not limited by these embodiments. The scope of protection of the present embodiment should be interpreted by the claims below, and all technical ideas within a scope equivalent thereto should be interpreted as being included in the scope of rights of the present embodiment.

[0167]

[0168] CROSS-REFERENCE TO RELATED APPLICATION

[0169] This patent application claims priority to Korean Patent Application No. 10-2024-0025492, filed in Korea on February 22, 2024, and Korean Patent Application No. 10-2025-0020656, filed in Korea on February 18, 2025, the entire contents of which are incorporated herein by reference.

Claims

1. A method implemented by a computing system including one or more computing devices for operational management of one or more sites, A process of collecting operational metrics of one or more network nodes deployed in each of one or more sites, wherein the operational metrics include one or more of resource performance of the corresponding network node, network connection status, connected network service quality, alarm data according to occurrence of a failure, and event data according to change of status; A process of visualizing operational indicators for one or more candidate sites among the one or more sites on a first virtual space; and A process of visualizing an operational indicator for a target site determined from among one or more candidate sites based on a user's interaction with the first virtual space on a second virtual space that simulates the target site. A method comprising:

2. In paragraph 1, A method wherein the above first virtual space is reproduced based on GIS (Geographic Information System) data.

3. In paragraph 1, The process of visualizing on the above first virtual space is: A process for generating one or more first UI elements representing the geographic location and operational indicators of each candidate site group including a single candidate site or two or more candidate sites, A method wherein said one or more first UI elements have different colors depending on whether a failure has occurred in a corresponding single candidate site or group of candidate sites.

4. In paragraph 3, One or more of the first UI elements, Includes a site-specific UI element corresponding to the single candidate site and a group-specific UI element corresponding to the candidate site group, A method wherein the above-mentioned UI elements for each site and the above-mentioned UI elements for each group have different shapes.

5. In paragraph 4, The user interface in which the first virtual space is displayed further includes a second UI element for receiving search conditions for one or more candidate sites, The process of visualizing on the above first virtual space is: A method comprising the process of searching for a single candidate site and a group of candidate sites that satisfy the search conditions based on metadata of each candidate site, each group of candidate sites, or the network nodes included in each candidate site.

6. In paragraph 3, The user interface in which the first virtual space is displayed includes a third UI element that displays statistical information about the current status of each of the one or more sites, The above current status is determined as either a normal status or an abnormal status based on whether there is a network node currently experiencing a failure at each site, The above statistical information is a method including information that aggregates the number of sites in a normal state and the number of sites in an abnormal state.

7. In paragraph 3, The user interface in which the first virtual space is displayed includes a fourth UI element that represents a status history for one or more of the sites for a predetermined past period, The above status history is a method in which the past period is divided into predetermined unit periods and information is included that aggregates the number of sites where a network node in which a failure occurred exists for each unit period.

8. In paragraph 1, The process of visualizing on the above second virtual space is: A method comprising the step of generating one or more fifth UI elements corresponding to each of one or more target network nodes deployed at the target site, and indicating the relative position and operating indicator of each target network node with respect to the target site.

9. In paragraph 8, A method wherein the one or more fifth UI elements have different shapes and colors depending on the device type and whether a failure has occurred of the corresponding target network node.

10. In paragraph 8, The one or more target network nodes include a first target network node providing a connection to a network to at least one other node and a second target network node connected to the network by the first target network node, The process of visualizing on the above second virtual space is: A method further comprising a process of creating a graphic object connecting a fifth UI element corresponding to the first target network node and a fifth UI element corresponding to the second target network node.

11. In paragraph 10, A method for generating the graphic object, wherein the color or thickness of the graphic object is determined based on the type of connecting cable that physically connects the first target network node and the second target network node.

12. In paragraph 1, The process of visualizing on the above second virtual space is: A process for generating one or more sixth UI elements, each corresponding to one or more sensor nodes within the target site and indicating a relative position of each sensor node with respect to the target site, A method wherein the one or more sensor nodes include one or more of a mobility moving within the target site, an IoT (Internet of Things) device carried by a visitor to the target site, and an IoT device attached within the target site.

13. In paragraph 1, The second virtual space includes a building-level 3D model that simulates the target site, which is a building having one or more floors. The three-dimensional model of the building level includes a first layer representing the floor of each floor of the building, a second layer representing the ceiling, and a third layer representing the intra-story space between the floor and the ceiling. The above first layer, second layer, and third layer, A method in which a seventh UI element is selectively made invisible based on a user interaction with at least one area of ​​a user interface in which the second virtual space is displayed.

14. In paragraph 13, The second virtual space further includes one or more floor-level 3D models replicating each floor of the building, The process of visualizing on the above second virtual space is: A method comprising a process of selectively visualizing a floor-level target 3D model corresponding to a target floor selected from among the one or more floors, based on a user interaction with at least one area of ​​a user interface in which the building-level 3D model or the second virtual space is displayed.

15. In paragraph 14, The target 3D model at the above floor level includes a fourth layer representing the ceiling of the target floor, and a fifth layer representing the intra-floor space of the target floor. The process of selectively visualizing the target 3D model at the above layer level is as follows: A process of rotating the fourth layer based on one axis of the three-dimensional coordinate system in which the second virtual space is expressed so that at least a portion of the ceiling of the target floor is visible to the user's field of view regardless of the camera view point in which the target three-dimensional model at the floor level is displayed in the second virtual space. A method comprising:

16. In paragraph 1, The second virtual space includes a building-level 3D model that simulates the target site, which is a multi-story building having two or more floors. The three-dimensional model of the building level includes a first layer representing the floor of each floor of the building, a second layer representing the ceiling, and a third layer representing the intra-floor space between the floor and the ceiling. The process of visualizing on the second virtual space includes a process of intentionally distorting the three-dimensional model at the building level so that the visual representation of the multi-story building and the three-dimensional model at the building level are different. A method wherein the above-described intentionally distorting process comprises a process of separating a second layer representing a ceiling of an arbitrary floor within the multi-story building and a first layer representing a floor of an upper floor of the arbitrary floor in a direction perpendicular to the ceiling and the floor.

17. In paragraph 3, The user interface in which the first virtual space is displayed includes an eighth UI element for receiving a selection for an arbitrary target point in time during a predetermined past period, and one or more ninth UI elements representing the history of the operating indicators for the one or more sites during the past period. The process of visualizing on the above first virtual space is: A method comprising a process of dynamically adjusting the first virtual space so that the one or more first UI elements represent the measured operating indicator at the target time based on a user interaction with the eighth UI element.

18. In paragraph 1, The first virtual space includes one or more tenth UI elements representing the real-time geographic location of each of one or more field workers, The one or more 10th UI elements are selectively visualized based on a user interaction with an 11th UI element positioned in at least one area of ​​the user interface where the first virtual space is displayed, The process of visualizing on the above first virtual space is: A method comprising: selectively visualizing, on the first virtual space, a profile card of a field worker corresponding to the 10th UI element in which the user interaction is detected, based on a user interaction with any one of the 10 UI elements.

19. In paragraph 1, The above operating indicators are: A method further comprising at least one of attribute information of the corresponding network node, a location of the corresponding network node, a type of wiring for communication connection or power supply to the corresponding network node, a path of the wiring, a work history for maintenance of the corresponding network node, and a maintenance schedule currently reserved for the corresponding network node.

20. A memory for storing instructions; and at least one processor, At least one processor executes the instructions, Collecting operational metrics of one or more network nodes deployed in each of one or more sites, wherein the operational metrics include one or more of resource performance of the corresponding network node, network connection status, connected network service quality, alarm data according to occurrence of a failure, and event data according to status change; Visualizing the operational indicators for one or more candidate sites among the one or more sites in a first virtual space, A computing system that visualizes an operational indicator for a target site determined from among one or more candidate sites based on a user's interaction with the first virtual space on a second virtual space that simulates the target site.

Images