Method and apparatus for identifying information of network device

Abstract

According to an embodiment, a method performed by a server supporting an SDN system may comprise: an operation of identifying network devices to be managed through the SDN system; an operation of obtaining, at designated intervals, address information for network addresses of the network devices and port information for ports of the network devices; an operation of determining, when inputted is a request for a first user equipment (UE) associated with at least one network device among the network devices, first address information for a network address of the at least one network device and first port information for a port of the at least one network device, on the basis of the address information and the port information; and providing at least one of the first address information and the first port information to an external device.

Description

Method and device for identifying information of a network device

[0001] The present disclosure relates to a software defined networking (SDN) system. Specifically, the present disclosure relates to a method and apparatus for a server supporting an SDN system to identify information about a network device.

[0002] SDN systems can be described as a technology that enables efficient centralized network management by separating the network control plane from the data plane. Through centralized control and programmability, SDN systems rapidly adapt to changing network requirements and can decouple network infrastructure from applications through virtualization. In particular, in 5G (fifth generation) networks, SDN systems can provide network slicing, dynamic resource allocation, support for edge computing, and / or automated network management, thereby delivering the flexibility and scalability of 5G. As another example, in enterprise networks, SDN systems can support technologies such as cloud computing and the Internet of Things (IoT) by enabling agility, cost reduction, enhanced security, cloud integration, and / or application-aware networking.

[0003] According to one embodiment, a method performed by a server supporting a software defined networking (SDN) system may include: identifying network devices to be managed through the SDN system; obtaining address information for network addresses of the network devices and port information for ports of the network devices at specified intervals; determining first address information for a network address of the at least one network device and first port information for a port of the at least one network device based on the address information and port information when a request for a first UE (user equipment) associated with at least one network device is input; and providing at least one of the first address information and the first port information to an external device.

[0004] According to one embodiment, a server supporting a software defined networking (SDN) system includes at least one processor and a memory for storing instructions. When the instructions are executed individually or collectively by the at least one processor, the server identifies network devices to be managed through the SDN system, obtains address information for network addresses of the network devices and port information for ports of the network devices at specified intervals, and when a request for a first user equipment (UE) associated with at least one network device is input, determines first address information for the network address of the at least one network device and first port information for the port of the at least one network device based on the address information and the port information, and transmits at least one of the first address information and the first port information to an external device.

[0005] FIG. 1a illustrates a method for a server supporting an SDN system according to one embodiment to manage network devices.

[0006] FIG. 1b illustrates a method in which a server supporting an SDN system according to one embodiment collects address information and / or port information of network devices and provides it to a management device.

[0007] FIG. 2 describes a method for identifying first address information and first port information of at least one network device associated with a first UE.

[0008] FIG. 3 is a diagram illustrating a method for registering network devices in a device inventory of a server according to one embodiment.

[0009] FIG. 4 illustrates a method for adding network devices to a device inventory according to one embodiment.

[0010] FIG. 5 is a diagram illustrating a management screen displaying registered network devices according to one embodiment.

[0011] FIG. 6 illustrates a method for identifying the provisioning status of network devices according to one embodiment.

[0012] FIG. 7 is a diagram illustrating the form in which address information of collected network devices is stored according to one embodiment.

[0013] FIG. 8 illustrates a method for inputting address information of a first UE according to one embodiment.

[0014] FIG. 9 illustrates a method for inputting address information of a plurality of UEs according to one embodiment.

[0015] FIG. 10 illustrates UIs displayed on a display when a plurality of UEs are entered into input fields according to one embodiment.

[0016] FIG. 11 illustrates UIs displayed on a display when a plurality of UEs are entered into input fields according to one embodiment.

[0017] FIG. 12 is a block diagram of a server according to one embodiment of the present disclosure.

[0018] In relation to the description of the drawings, the same or similar reference numerals may be used for identical or similar components.

[0019] Hereinafter, various embodiments of the present disclosure are described with reference to the accompanying drawings. However, this is not intended to limit the present disclosure to specific embodiments and should be understood to include various modifications, equivalents, and / or alternatives of embodiments of the present invention.

[0020] According to one embodiment, an SDN system may be referred to as a network management approach that enables efficient network configuration in a dynamic and programmatic manner to improve network performance and monitoring. An SDN system can separate the network control plane (e.g., the part that determines how traffic is processed) from the data plane (e.g., the underlying system that delivers traffic (or data)). Key features of an SDN system may be as follows: 1) Centralized control: An SDN system can provide a holistic view of the network by centralizing network intelligence in a software-based controller. 2) Programmability: An SDN system can programmatically configure the network, allowing for rapid adaptation to changing requirements. 3) Virtualization: An SDN system can virtualize the underlying infrastructure for applications and network services. The importance of SDN systems may be further highlighted by the emergence of 5G technology. 5G networks may require unprecedented levels of flexibility, scalability, and efficiency to support a wide range of use cases, from enhanced mobile broadband to large-scale IoT deployments and ultra-reliable, low-latency communication. In 5G, SDN systems play the following important roles. 1) Network Slicing: SDN systems can enable the creation of multiple virtual networks optimized for specific services or clients within a shared physical infrastructure. 2) Dynamic Resource Allocation: SDN systems can adjust network resources in real-time based on demand and service requirements. 3) Edge Computing Support: SDN systems can facilitate the deployment and management of edge computing resources to reduce latency and improve service quality. 4) Automated Network Management: SDN systems can enable self-organizing networks (SON) that can automatically optimize configuration and performance.

[0021] SDN systems can provide several benefits, including the following: Agility: SDN systems can rapidly provision and modify network services to meet changing business needs. 1) Cost Reduction: SDN systems can reduce operational costs by simplifying network hardware and through automation. 2) Enhanced Security: SDN systems can apply more granular and dynamic security policies across the network. 3) Cloud Integration: SDN systems facilitate seamless integration between on-premises infrastructure and cloud services. 4) Application-Aware Networking: SDN systems enable the network to dynamically adapt to application requirements.

[0022] However, despite the benefits provided by SDN systems, the increasing complexity of the environment can become a problem for both 5G and enterprise networks. For example: 1) Device proliferation: The explosive growth of connected devices, particularly driven by IoT and mobile devices, can make it difficult to maintain accurate and up-to-date information regarding network endpoints. 2) Dynamic IP address allocation: The use of dynamic IP allocation, especially in large-scale networks, can complicate the task of tracking and managing device identifiers and locations. 3) Security concerns: As networks become more complex and dynamic, maintaining security and compliance can become increasingly difficult, particularly in identifying and managing authorized devices. 4) Rapid network changes: The agility provided by SDN implies that network configurations can change rapidly, which can make it difficult to maintain an accurate, real-time view of the network state. 5) Heterogeneous environments: As many organizations operate in hybrid environments combining traditional networking with SDN, cloud services, and edge computing, network management can become even more complex. 6) Performance Optimization: Due to the high performance requirements of 5G and modern enterprise applications, there is an increasing need for real-time network optimization based on current conditions and demand. Consequently, there is a growing need for advanced solutions capable of providing real-time visibility into network devices, network device identifiers (MAC addresses), and / or logical locations (IP addresses).

[0023] The present disclosure can solve the aforementioned problems by providing a dynamic MAC and IP address collection and on-demand query system specifically designed to operate in an SDN-enabled environment. The present disclosure can provide a powerful tool for managing the complexity of modern 5G and enterprise networks by combining the centralized control and programmability of SDN with advanced data collection and analysis technologies.

[0024] According to one embodiment, the integration of a digital twin and SDN can provide the following benefits: 1) Network simulation: By combining the programmability of SDN with the simulation capabilities of a digital twin, network changes can be tested and optimized before actual implementation. 2) Predictive maintenance: By creating digital twins of network equipment and infrastructure to monitor performance and predict potential problems, preemptive maintenance can be enabled. 3) Resource optimization: Using a digital twin model, the present disclosure can analyze network traffic patterns and resource usage, and implement optimal resource allocation in real time through SDN. 4) Enhanced security: By utilizing a digital twin of a network, the present disclosure can simulate security threats and implement immediate response strategies through SDN. 5) Improved quality of service: The present disclosure can create a digital twin of an end-to-end service path to monitor performance and optimize it in real time through SDN.

[0025] According to one embodiment, the requirements for a network management solution for a digital twin may be as follows: 1) Real-time data collection: Real-time, high-precision data collection on network devices and traffic may be required for the accuracy of the digital twin model. 2) Large-scale data processing: Since digital twins in complex network environments must process vast amounts of data, efficient data management and analysis functions may be required. 3) API integration: Robust API support may be required for seamless integration between the digital twin platform, the SDN controller, and the network management system. 4) Dynamic model updates: A function to continuously update the digital twin model by reflecting network configuration changes in real time may be required. 5) Visualization and analysis tools: Advanced tools capable of effectively visualizing and analyzing complex network topologies and states may be required. In conclusion, the convergence of SDN, 5G, enterprise networks, and digital twin technologies is opening up new dimensions in network management and optimization. In this environment, the importance of solutions that provide dynamic MAC and IP address collection, real-time network status monitoring, and advanced analysis capabilities is growing. The present disclosure satisfies these complex requirements and constitutes a core technology for next-generation network management and digital twin implementation.

[0026] When at least one server (e.g., a management server) manages network devices (e.g., switches, routers) through an SDN system, network failures may occur in user equipment (UEs) (e.g., terminals, laptops, computers) connected to the network devices. In this case, to identify the source of the network failure, the user may need to use at least one server to individually check the network devices and identify the port of the network device to which the UE is connected.

[0027] If all network devices are checked individually to identify the source of a network failure, a large workforce may be required, and there may be a problem with the time required for failure identification and resolution becoming prolonged.

[0028] FIG. 1a illustrates a method for a server supporting an SDN system according to one embodiment to manage network devices.

[0029] Referring to FIG. 1a, a network system according to one embodiment may include a management device (or, external device) (100), a server (101), network devices (130), and / or user equipment (UEs) (150) connected to the network devices (130). For example, the management device (or, external device) (100) may be a device for managing network devices (130) connected to a server (101) that supports an SDN system (110). For example, the server (101) may be a server that supports an SDN system (110). For example, the server (101) may be a server equipped with an SDN system (110). For example, network devices (130) may be devices used to transmit, process, or manage data in a network. For example, network devices (130) may include a network switch (or, switch) and / or a router.

[0030] For example, network devices (130) may include a first network device (131), a second network device (132), a third network device (133), a fourth network device (134), a fifth network device (135) and / or a sixth network device (136).

[0031] According to one embodiment, a management device (100) (e.g., terminal, laptop, computer) may be connected to or connected to a server (101) that supports an SDN system (110). For example, a user's management device (100) (e.g., terminal, laptop, computer) may be connected to a server (101) that supports an SDN system (110) via a wired or wireless connection. For example, the user may identify information (e.g., network address) of the server (101) through the management device (100). In another example, the management device (100) may be formed integrally with the server (101). For example, the management device (100) may be a display device mounted on the server (101).

[0032] According to one embodiment, network devices (130) may include devices for transmitting signals within a wired communication network and / or a wireless communication network (e.g., router, switch, server). For example, network devices (130) may include a third network device (133) (e.g., network switch), and the third network device (133) may be connected to UEs (150). For example, a first port of the third network device (133) may be connected to a first UE (151), and a fourth port of the third network device (133) may be connected to a second UE (152). For example, the third network device (133) may transmit data to the first UE (151) through the first port and to the second UE (152) through the fourth port.

[0033] According to one embodiment, a server (101) supporting an SDN system (110) may include a device inventory (111), a network address storage (121), a network address collection module (122), and a graphical user interface (GUI) module (123). For example, the SDN system (110) may be referred to as a system supporting a digital twin. For example, a digital twin may be referred to as a technology that virtualizes a physical object (e.g., a network device) in a digital environment to convert it into a virtualized instance, and checks the state of the physical object (e.g., a network device) in real time using the virtualized instance or controls the physical object using the virtualized instance.

[0034] According to one embodiment, a tracer module (120) (e.g., MAC / Tracer) of an SDN system (110) may include a network address storage (121), a network address collection module (122), and a GUI module (123). For example, the functions of an SDN system supported by a server (101) may be divided into a device inventory (111) and a tracer module (120). For example, the device inventory (111) may be a component (or module) for setting up a management target before collecting address information of network devices (130). The tracer module (120) may be a component (or module) for storing address information and / or port information obtained from network devices (130) when the management target has already been determined, and for displaying address information and / or port information associated with a UE based on a request from a management device (100).

[0035] For example, the device inventory (111) may be a configuration module for configuring network devices to be managed by the SDN system (110) (or server (101)). For example, the tracer module (120) may be a module for identifying the status of network devices (130) configured as management targets or for identifying the source of a failure that occurred to the UE.

[0036] However, the functions of the SDN system (110) supported by the server (101) of the present disclosure are not limited to the examples described above, and the SDN system (110) may perform various functions. For example, the SDN system (110) may not include at least some of the functions described above (e.g., device inventory (111) and tracer module (120)). For example, the SDN system (110) may further include configurations (or functions) other than those described above.

[0037] According to one embodiment, the device inventory (111) may store information regarding the network addresses of network devices to be managed by the server (101) supporting the SDN system (110). For example, the device inventory (111) may store address information of network devices (130) (e.g., switches, routers, servers) to be managed by the server (101) to provide the SDN system (110). For example, the device inventory (111) may be the memory and / or storage of the server (101). For example, the device inventory (111) may be a module that stores information about network devices (130) that are subject to management by the server (101), and may differ from a module that stores address information and / or port information of network devices (130) that are subject to collection of network addresses (e.g., network address storage (121)).

[0038] According to one embodiment, a network address storage (121) (e.g., MAC (medium access control) and IP (internet protocol) storage) may obtain address information regarding the addresses of network devices (130) and / or port information associated with network devices (130) from a network address collection module (122). The network address storage (121) may store the obtained address information and / or port information. For example, the network address collection module (122) may periodically collect address information regarding network addresses (e.g., MAC addresses, and / or IP addresses) and / or port information from network devices (130). The network address collection module (122) may transmit the collected address information and / or port information to the network address storage (121), and the network address storage (121) may store the address information and / or port information.

[0039] For example, the port information may be port information of network devices (130) that are subject to management. For example, the third network device (133) may include multiple ports and may identify information regarding whether the multiple ports are connected to UEs (150) and / or information regarding UEs (150) connected to the multiple ports. In this case, the third network device (133) may transmit port information (e.g., information regarding whether the multiple ports are connected to UEs (150) and information regarding UEs (150) connected to the multiple ports) to the server (101).

[0040] In FIG. 1a of the present disclosure, the information obtained (or collected) by the network address collection module (122) is divided into address information and port information of network devices (130), but this is merely an example. For example, the address information obtained by the network address collection module (122) may be a concept that includes information about the addresses of network devices (130) (e.g., MAC address, IP address) and port information. That is, address information may be a concept that includes MAC address, IP address and / or port information. However, this is merely an example and the present disclosure is not limited thereto.

[0041] According to one embodiment, the network address storage (121) may store address information and / or port information of network devices (130) for a specified period of time. For example, the server (101) may identify address information and / or port information of network devices (130) registered in the device inventory (111) using the network address collection module (122) at a first time point (e.g., T1). The server (101) may identify address information and / or port information of network devices (130) at a second time point (e.g., T2) after a period (e.g., about 15 minutes) has elapsed from the first time point (e.g., T1). The server (101) may identify address information and / or port information of network devices (130) at a third time point (e.g., T3) after a period (e.g., about 15 minutes) has elapsed from the second time point (e.g., T2). In this case, the network address storage (121) of the server (101) may store address information and port information corresponding to a first time point (T1), address information and port information corresponding to a second time point (T2), and / or address information and port information corresponding to a third time point (T3).

[0042] Consequently, the network address storage (121) can store address information and / or port information of network devices (130) at past times as well as at present times, based on the time when the user identifies address information and / or port information of network devices (130) through the management device (100) (e.g., present time).

[0043] According to one embodiment, the conditions that trigger the network address storage (121) to perform information collection for at least some of the registered network devices (130) may include 1) a condition in which user input to the server (101) (e.g., user input using the server's display or interface) is identified, and / or 2) a condition in which a control signal transmitted from the management device (100) is received.

[0044] For example, the network address storage (121) may collect address information and / or port information of network devices (130) based on an input that enables information collection. For example, the server (101) may identify user input to the server (101) to enable information collection of network devices (130). In this case, the server (101) may perform identification of address information and / or port information for at least some of the network devices (130) based on the user input. The user input to enable information collection may direct information collection for at least some of the network devices (130). For example, the network devices (130) registered in the device inventory (111) may include a first network device (131), a second network device (132), a third network device (133), a fourth network device (134), a fifth network device (135), and / or a sixth network device (136). The network address collection module (122) may not collect address information and / or port information for all registered network devices (130), and the network address collection module (122) may collect address information and / or port information only for network devices specified by user input among the network devices (130) (e.g., first network device (131), third network device (133)). This may reduce the possibility of a load occurring due to excessive information collection.

[0045] For example, the server (101) may receive a control signal from the management device (100) to enable information collection. In this case, the server (101) may perform identification of address information and / or port information for at least some of the network devices based on user input. The control signal to enable information collection may instruct the collection of information for at least some of the network devices (130). For example, address information and / or port information may not be collected for all network devices (130) registered in the device inventory (111). The network address collection module (122) may collect address information and / or port information only for the network devices (130) that are instructed by the control signal (e.g., the first network (131), the third network device (133)). This may reduce the likelihood of a load occurring due to excessive information collection.

[0046] In FIG. 1a of the present disclosure, for the sake of explanation, user input to the server (101) and control signals received from the management device (100) are described separately, but this is merely an example, and inputs that trigger information collection may be referred to by various terms. For example, the terms user input and control signal may be replaced with signals that trigger information collection, initiation signals, triggering inputs, or operating signals.

[0047] According to one embodiment, a network address collection module (122) (e.g., MAC / IP collection module) can collect (or acquire) address information regarding the network addresses of network devices (130) registered as management targets on the server (101). For example, the network address collection module (122) can identify address information of network devices (130) stored in the device inventory (111). Based on the identified address information, the network address collection module (122) can identify network devices (130) stored in the device inventory (111) as targets for periodic information collection. The network address collection module (122) can acquire the network addresses of network devices (130) at specified intervals (e.g., about 15 minutes).

[0048] According to one embodiment, the period (or interval, collection period) for the network address collection module (122) to collect address information of network devices (130) can be set in various ways.

[0049] For example, the period may be determined by the management device (100) and / or server (101). In this case, the user may use the management device (100) and / or server (101) to set the period for information collection to a specified value (e.g., about 15 minutes, about 30 minutes).

[0050] For example, the period may be determined based on whether there is a change in the network devices (130) that are subject to management by the server (101). For example, the server (101) may reduce the period for information collection when network devices (130) that are subject to management are added or when some of the network devices (130) are excluded. That is, the server (101) may reduce the period for information collection from a first period (e.g., about 15 minutes) to a second period (e.g., 5 minutes) when network devices (130) are reduced or added. The server (101) may change the period for information collection from the second period (e.g., 5 minutes) to a first period (e.g., about 15 minutes) if there is no change in the network devices (130) for a specified period after the period for information collection has been changed to the second period (e.g., 5 minutes).

[0051] For example, the period may be determined based on the congestion or traffic volume of network devices (130) managed by the server (101). For example, if the congestion (or traffic volume) of the network devices (130) managed by the server (101) exceeds a threshold value, the server (101) may reduce the period for information collection to quickly identify the source of the failure, as network failures may occur due to congestion. For example, if the congestion (or traffic volume) exceeds a threshold value, the server (101) may reduce the period for information collection from a first period (e.g., about 15 minutes) to a second period (e.g., 5 minutes). Additionally, the server (101) may increase the period for information collection if the congestion (or traffic volume) is below a threshold value. For example, the server (101) may increase the period for information collection from a first period (e.g., about 15 minutes) to a third period (e.g., 20 minutes).

[0052] According to one embodiment, a GUI module (123) (e.g., MAC / IP Query GUI) may provide a UI to a user that directs the user to address information of network devices (130) and / or port information of network devices (130). For example, a server (101) may display address information of network devices (130) (e.g., the first address information of FIG. 2) and / or port information of network devices (130) (e.g., the first address information of FIG. 2) on a management site for an SDN system through the GUI module (123). Hereinafter, address information and port information displayed on a management site for an SDN system are described in FIG. 10 and FIG. 11.

[0053] For example, the server (101) can display address information of network devices (130) and / or port information of network devices (130) on the display of the server (101) through the GUI module (123). For example, the server (101) can generate a GUI (or UI) that indicates address information of network devices (130) and / or port information of network devices (130) through the GUI module (123), and the server (101) can transmit information about the GUI (or UI) to the management device (100) so that the GUI (or UI) is displayed on the display of the management device (100).

[0054] According to one embodiment, a server (101) may receive a request for a first UE (151) of a management device (100). Based on the request for the first UE (151), the server (101) may obtain address information of a network device (e.g., a third network device (133)) associated with the first UE (151) and / or port information of a network device associated with the first UE (151) from a network address storage (121). For example, a network device associated with the first UE (151) may include a network device (e.g., a third network device) to which the first UE (151) is connected at a current time (e.g., the time when the request for the first UE (151) is received) and / or a network device to which the first UE (151) was connected at a past time prior to the current time. That is, the first UE (151) may be connected to the first network device (131), then disconnected, and connected to the network through the first port of the third network device (133). In this case, the network device associated with the first UE (151) may include the first network device (131) and the third network device (133).

[0055] The server (101) can use the GUI module (123) to display address information of a network device associated with the first UE (151) and / or port information of a network device associated with the first UE (151) on the display of the server (101). As another example, the server (101) can use the GUI module (123) to display address information of a network device associated with the first UE (151) and / or port information of a network device associated with the first UE (151) on the display of the management device (100).

[0056] According to one embodiment, a request to the first UE (151) input to the server (101) may include address information (e.g., MAC address, IP address) of the first UE (151). For example, the management device (100) and / or the server (101) may identify that a communication failure has occurred in the first UE (151) among the UEs (150).

[0057] For example, if the management device (100) identifies that a communication failure has occurred in the first UE (151), the management device (100) may send a request for the first UE (151) containing address information of the first UE (151) to the server (101). In this case, the server (101) may identify the address information and / or port information of the network device associated with the first UE (151) stored in the network address storage (121). The server (101) may display the address information and / or port information associated with the first UE (151) on a management site, transmit it to the management device (100), or transmit information about a UI that directs the address information and / or port information to the management device (100). For example, the server (101) may upload the address information and / or port information to a management site (or management system) of the network. The management device (100) may access the management site (or management system) to identify the address information and / or port information.

[0058] For example, if the server (101) identifies that a communication failure has occurred in the first UE (151), the server (101) may notify the user that a communication failure has occurred in the first UE (151). The server (101) may receive a request for the first UE (151) from the user through the interface of the server (101) or receive a request for the first UE (151) from the management device (100). In this case, the server (101) may identify the address information and / or port information of the network device associated with the first UE (151) stored in the network address storage (121). The server (101) may transmit the address information and / or port information associated with the first UE (151) to the management device (100) or transmit information about the UI that directs the address information and / or port information to the management device (100).

[0059] In FIG. 1a of the present disclosure, the acquisition of address information and / or port information by the network address collection module (122) is described as being triggered based on a single user input or control signal, but this is merely an example. For example, the triggering for the acquisition of address information and / or port information may be performed over multiple steps. For example, network devices (130) may be registered in the device inventory (111), and the server (101) may turn the provision state of the network devices (130) on / off based on a first user input (or a first control signal). For example, when the provision state of the first network device (131) is turned on, the first network device (131) may be identified as a device capable of acquiring address information and / or port information. When the provisioning status of the first network device (131) is off, the first network device (131) may be identified as a device for which the acquisition of address information and / or port information is disabled (Step 1 - On / Off). The server (101) may identify a second user input (or a second control signal) for network devices (130) for which the provisioning status is on (e.g., the first network device (131)). The second user input may indicate a network device for which the collection of information is to be enabled among the network devices for which the provisioning status is on. Accordingly, the server (101) may initiate the collection of information for the network devices indicated by the second user input among the network devices for which the provisioning status is on, based on the second user input.

[0060] For example, the provisioning state of network devices (130) may be referred to as a state indicating whether the network devices (130) are enabled to provide address information and / or port information.

[0061] In FIG. 1a of the present disclosure, the operations performed by the device inventory (111), network address storage (121), network address collection module (122) and / or GUI module (123) within the server (101) can substantially be referred to as the operations of the server (101) or at least one server. Accordingly, the subject of the operations described in FIG. 1a may be the server (101) or at least one server.

[0062] In the drawing of FIG. 1a of the present disclosure, the network device (e.g., third network device (133)) and the port of the network device are depicted as being physically separated, but this is merely an example and the network devices (130) and the ports may be virtualized instances.

[0063] The device inventory (111), network address storage (121), network address collection module (122), and / or GUI module (123) included in the SDN system (110) of the present disclosure may be virtualized software modules. However, the present disclosure is not limited thereto, and the device inventory (111), network address storage (121), network address collection module (122), and / or GUI module (123) included in the SDN system (110) may be physically separated configurations.

[0064] In FIG. 1a of the present disclosure, it is described that a user accesses a server (101) through a management device (100) (e.g., terminal, laptop, computer), but this is merely an example. For example, a user may directly access a server (101) that supports an SDN system (110) without a separate management device (100). For example, a user may identify information (e.g., network address) of the server (101) through a display and interface device (e.g., keyboard, mouse) of the server (101).

[0065] In FIG. 1a of the present disclosure, network devices (130) are described as including network switches and / or routers, but this is merely an example. For example, network devices (130) may include a router that connects different networks and transmits data, a switch that transmits data within one network, a gateway that connects different networks and processes data conversion, and / or a firewall to protect the network.

[0066] In FIG. 1a of the present disclosure, the SDN system (110) is described as being supported by a server (101), but this is merely an example. For example, the SDN system (110) may be supported by one server (e.g., server (101)) or may be supported by multiple servers.

[0067] FIG. 1b illustrates a method in which a server supporting an SDN system according to one embodiment collects address information and / or port information of network devices and provides it to a management device.

[0068] Referring to FIG. 1b, a user management device (100) according to one embodiment may input (or transmit) information regarding network devices (130) to be managed through the SDN system (110) to the server (101) in operation 171. For example, the management device (100) may input address information (e.g., IP address, MAC address) regarding the network address of the network devices (130) to be managed through the SDN system (110) to the server (101) based on user input. For example, the user may register a network device to be managed (e.g., a switch) through a UI supported by the server (101). For example, FIGS. 3 and 4 describe a method in which the user inputs information regarding network devices (130) to the server (101) through the display of the management device (100) (e.g., the display (300) of FIG. 3). In another example, the server (101) can receive input from the user for network devices (130) directly without a management device (100). For example, the server (101) can identify input for network devices (130) through the server (101)'s interface (e.g., keyboard, mouse) and / or display.

[0069] In FIG. 1b of the present disclosure, it is described that a server (101) receives address information for network devices (130) through a management device (100), but this is merely an example. For example, the server (101) may include a display and an interface (e.g., keyboard, mouse), and a user may directly input address information for network devices (130) into the server (101). As another example, the user's management device (100) may be implemented as an integral part of the server (101) or mounted on the server (101). In this case, the server (101) including the management device (100) can identify user input (e.g., input of address information) to the management device (100).

[0070] According to one embodiment, the server (101) may identify and store network devices (130) as network devices to be managed through the server (101) or the SDN system (110) based on the input of address information for network devices (130). For example, the server (101) may identify input for address information (e.g., MAC address, and / or IP address) of a third network device (133) through a user or management device (100). The server (101) may store the address information of the third network device (133) in the device inventory (111). For example, FIG. 5, described below, describes how the address information of network devices (130) is stored in the memory (or device inventory (111)) of the server (101) based on the input of network devices (130) to the server (101).

[0071] In FIG. 1b of the present disclosure, network devices (130) registered in the device inventory (111) are described as being subject to management (e.g., subject to information collection), but this is merely an example. For example, the collection of address information and / or port information may not be performed for all network devices (130) registered in the device inventory (111). That is, among all network devices (130) registered in the device inventory (111), information collection may be performed only for the network device (e.g., third network device (133)) indicated by the input (or control signal) that enables collection and has the provisioning status ON.

[0072] As another example, when network devices (130) are registered in the device inventory (111), it can be assumed that the registered network devices (130) have a provisioning status ON and are activated. In this case, address information and / or port information collection (or acquisition) for the registered network devices (130) can be performed based on the network devices (130) being registered in the device inventory (111).

[0073] In FIGS. 1a and 1b of the present disclosure, the provisioning state may be referenced as information indicating whether information collection for a network device is enabled. For example, when the provisioning state is on, information collection for a network device may be enabled, and when the provisioning state is off, information collection for a network device may be disabled. In FIGS. 1a and 1b of the present disclosure, the input that enables collection (or, the second user input, the second control signal in FIG. 1a) may be referenced as information indicating the network device for which information collection is initiated. For example, the first network device (131) and the second network device (132) may have the provisioning state on, and the third network device (133) may have the provisioning state off. In this case, the server (101) cannot perform information collection regardless of the input that enables the third network device (133) (or, the second user input, the second control signal in FIG. 1a). On the other hand, if an activation input (or, second user input, second control signal of FIG. 1a) for a first network device (131) with a provisioning state on indicates a first value (e.g., activation), the server (101) may perform information collection for the first network device (131). If an activation input (or, control signal) for a first network device (131) with a provisioning state on indicates a second value (e.g., deactivation), the server (101) may not perform information collection for the first network device (131).

[0074] According to one embodiment, the server (101) can transmit address information (e.g., MAC address and / or IP address) of network devices (130) registered in the device inventory (111) to the network address collection module (122) in operation 172. For example, the device inventory (111) of the server (101) can identify the input of address information of network devices (130) and transmit the input address information to the network address collection module (122).

[0075] For example, the device inventory (111) of the server (101) can transmit address information of all registered network devices (130) to the network address collection module (122). In this case, being registered in the device inventory (111) may substantially signify the initiation of information collection for the registered network devices (130). Consequently, they may become targets for information collection when registered in the device inventory (111), regardless of the first user input for provisioning status and the second user input for activation.

[0076] For example, the device inventory (111) of the server (101) may transmit only the address information of network devices that are activated and have a provisioning status of 'on' among the registered network devices (130) to the network address collection module (122). That is, even if a network device (e.g., first network device (131)) is registered in the device inventory (111) but has a provisioning status of 'off' or a second user input for activation has a second value (e.g., 'off'), the address information for that network device may not be transmitted to the network address collection module (122). On the other hand, the address information for a network device (e.g., second network device (133)) that is registered in the device inventory (111), has a provisioning status of 'on', and has a second user input for activation has a first value (e.g., 'on') may be transmitted to the network address collection module (122).

[0077] According to one embodiment, the server (101) may obtain address information and / or port information from network devices (130) (e.g., switches, routers, servers) in operation 173. For example, the network address collection module (122) of the server (101) may receive address information for registered network devices (130) from the device inventory (111). In this case, the network address collection module (122) may obtain address information (e.g., MAC address, IP address) for the network address of the network devices (130) and / or port information of the network devices (130) at a specified period (or interval).

[0078] For example, a network address collection module (122) of a server (101) may receive address information for active network devices (e.g., a third network device (133)) among the registered network devices (130) from a device inventory (111). In this case, the network address collection module (122) may obtain address information and / or port information of the active devices (e.g., a third network device (133)) at specified intervals (or intervals).

[0079] According to one embodiment, address information received from network devices (130) may include various types of information. For example, the address information may include MAC addresses and / or IP addresses of network devices (130). For example, the address information may include MAC addresses, IP addresses, and / or an Address Resolution Protocol (ARP) table of network devices (130). For example, the ARP table may be information indicating the correspondence between the MAC address and IP address of each network device (130). For example, a server (101) may request address information from a third network device (133), and the third network device (133) (e.g., a switch) may transmit a MAC address, IP address, and / or ARP table to the server (101) in response to the request.

[0080] According to one embodiment, the operation of the server (101) collecting address information and / or port information of network devices (130) can be performed in parallel. For example, the server (101) can collect address information and / or port information independently for each of the network devices (130). For example, the server (101) can perform the operation of receiving address information and / or port information of a first network device (131) and the operation of receiving address information and / or port information of a second network device (132) in parallel.

[0081] According to one embodiment, the server (101) can store information collected in operation 174. For example, the server (101) can acquire address information and / or port information from network devices (130) at designated intervals and can store the acquired address information and / or port information in the memory of the server (101). For example, the server (101) can acquire address information and / or port information from network devices (130) at designated intervals using a network address collection module (122). The server (101) can store the collected information using a network address storage (121).

[0082] According to one embodiment, the management device (100) can input address information (e.g., IP address, MAC address) of the first UE (151) to the server (101) in operation 175. For example, the management device (100) can identify that a communication failure has occurred in the first UE (151). The management device (100) can input address information (e.g., IP address, MAC address) of the first UE (151) to the server (101) through the GUI module (123) of the server (101). That is, by inputting the address information of the first UE (151) to the server (101), the management device (100) can request the server (101) to provide address information and port information of the network device associated with the first UE (151) that has experienced a communication failure.

[0083] The address information and port information of the network device described in FIGS. 1a and 1b of the present disclosure may substantially be referenced as location information of the UE. For example, when the first UE (151) is connected to the first port of the third network device (133), the address information of the third network device (133) associated with the first UE (151) may be the MAC address or IP address of the third network device (133), and the port information may be information indicating port 1. Accordingly, when the management device (100) inputs the address information of the first UE (151) to the server (101), it may receive the MAC address or IP address of the third network device (133) and information indicating port 1 as a response. In this case, since the management device (100) can identify that the first UE (151) that has failed is connected to port 1 of the third network device (133), the address information and port information may substantially be referenced as location information of the UE (on the network).

[0084] According to one embodiment, the server (101) can identify the address information of a network device (e.g., a third network device (133)) associated with the first UE (151) and the port information (e.g., a first port) associated with the first UE (151) based on the address information and port information stored in memory in operation 176. For example, the server (101) can identify a request (e.g., address information) for the first UE (151) through the GUI module (123) and can identify the network device (e.g., a third network device (133)) and port information (e.g., port 1) corresponding to the first UE (151) (or, the address information of the first UE (151)) based on the address information and port information stored in the network address storage (121).

[0085] According to one embodiment, the server (101) may transmit address information and port information (e.g., port 1) of a third network device (133) associated with the first UE (151) identified in operation 177 to the management device (100). For example, the GUI module (123) of the server (101) may inform the management device (100) of the address information and port information of the third network device (133). For example, the GUI module (123) of the server (101) may display the address information and port information of the third network device (133) to a management site (or management system) in response to a request for the first UE (151).

[0086] According to one embodiment, the management device (100) may receive information regarding address information and port information (e.g., port 1) of the third network device (133) in response to a request from the first UE (151), and may display the address information and port information on the display of the management device (100). As a result, the user can easily identify the source of the communication failure (e.g., port 1 of the third network device (133)) to resolve the communication failure of the first UE (151).

[0087] In FIG. 1b of the present disclosure, it is described that in operation 171, the server (101) receives information about network devices (130) from the management device (100), but this is merely an example. For example, the server (101) can automatically identify network devices (130) without inputting separate information about network devices (130). For example, when network devices (130) enter or are included within a network supported by the server (101), the server (101) can automatically store network devices (130) in the device inventory (111) without inputting separate information about network devices (130). That is, network devices (130) can automatically register network devices (130) that have entered the network.

[0088] FIG. 2 describes a method for identifying first address information and first port information of at least one network device associated with a first UE.

[0089] Referring to FIG. 2, a server (101) according to one embodiment can identify network devices to be managed through the SDN system (110) in operation 201. For example, a management device (100) can input address information of network devices (130) (e.g., switch, router, server) into a server (101) that supports the SDN system (110). For example, a user can input address information (e.g., IP address, MAC address) of network devices (130) into a server (101) that supports the SDN system (110) through the management device (100). For example, the management device (100) can input address information of a first network device (131), address information of a second network device (132), address information of a third network device (133), address information of a fourth network device (134), and / or address information of a fifth network device (135) into the server (101).

[0090] According to one embodiment, the server (101) can obtain address information for network addresses of network devices (130) and port information for ports of network devices (130) at specified intervals in operation 203. For example, the server (101) can identify address information and port information of network devices (130) registered in the device inventory (111).

[0091] For example, address information of network devices (130) can be referenced to the IP address, MAC address, and / or ARP table of each network device (130). For example, a server (101) can obtain information about the IP address, MAC address, and / or ARP table of the first network device (131).

[0092] For example, port information of network devices (130) may include identification information of ports included in each of the network devices (130), whether the ports are connected to a UE, and / or address information of the UE connected to the ports (e.g., IP address, MAC address). For example, port information of a third network device (133) may include information about a first port, information about a second port, information about a third port, and information about a fourth port.

[0093] Information regarding the first port may include identification information of the first port (e.g., interface name), information indicating that the first port is connected to the first UE (151), and / or address information of the first UE (151) connected to the first port. Information regarding the second port may include identification information of the second port (e.g., interface name) and information indicating that the second port is not connected to the UE. Information regarding the third port may include identification information of the third port (e.g., interface name) and information indicating that the third port is not connected to the UE. Information regarding the fourth port may include identification information of the fourth port (e.g., interface name), information indicating that the fourth port is connected to the second UE (152), and / or address information of the second UE (152) connected to the fourth port.

[0094] According to one embodiment, when a request for a first UE (151) associated with at least one network device among network devices is input in operation 205, the server (101) may determine first address information for the network address of at least one network device and first port information for the port of at least one network device based on address information and port information. For example, the server (101) may receive user input (or, request) associated with the first UE (151). The user input (or, request) associated with the first UE (151) may include address information of the first UE (151) that has failed. As another example, the server (101) may receive a request for the first UE (151) that has failed through a management device (100). The request for the first UE (151) may include address information of the first UE (151).

[0095] When a request for the first UE (151) is input, the server (101) may determine the first address information and first port information of at least one network device associated with the first UE (151) based on the acquired address information and port information. For example, the server (101) may identify and / or store the address information and port information of the network devices (130) collected in operation 203. The identified address information and port information may include the address information of the third network device (133) and port information for the first port of the third network device (133).

[0096] In this case, since the port information for the first port indicates that the first port is connected to the first UE (151), the server (101) can identify that the third network device (133) is included in at least one network device associated with the first UE (151), and that the first port of the third network device (133) is included in the port associated with the first UE (151).

[0097] Meanwhile, the server (101) may include not only the third network device (133) to which the first UE (151) is currently connected, but also a network device (e.g., the first network device (131)) to which the first UE (151) was previously connected and then disconnected, in at least one network device associated with the first UE (151). Additionally, the server (101) may include the second port of the first network device (131) to which the first UE (151) is disconnected in the ports associated with the first UE (151).

[0098] Consequently, the server (101) can identify a first network device (131) (e.g., previously connected) and a third network device (133) (e.g., currently connected) as at least one network device associated with the first UE (151). The server (101) can determine the address information of the first network device (131) and the address information of the third network device (133) as the first address information.

[0099] The server (101) can identify the second port of the first network device (131) and the first port of the third network device (133) as ports associated with the first UE (151). The server (101) can determine the information regarding the second port and the information regarding the third port as the first port information.

[0100] According to one embodiment, the determined first address information and second port information may be referenced as location information of the first UE (151). For example, through the first address information and first port information, a user (or a management device (100)) can identify the current location information of the first UE (151) (e.g., at the time when a request for the first UE (151) is entered) and the past location information of the first UE (151).

[0101] For example, by combining the first address information and the first port information, the address information of the network device (e.g., the third network device (133)) to which the first UE (151) is connected at the current time and the port information (e.g., port 1) to which the first UE (151) is connected can be derived. Thus, the user (or the management device (100)) can identify the current location information of the first UE (151) within the network.

[0102] Likewise, by combining the first address information and the first port information, the address information of a network device (e.g., the first network device (131)) to which the first UE (151) was connected and then disconnected in the past prior to the current time, and the port information to which the first UE (151) was disconnected (e.g., port 2 of the first network device (131)) can be derived. Thus, the user (or the management device (100)) can identify the location information of the first UE (151) in the past within the network. That is, the server (101) can provide the user not only with the network device and port to which the first UE (151) is currently connected, but also with the change history of the network device and port associated with the first UE (151).

[0103] According to one embodiment, the server (101) may display at least one of the first address information and the first port information determined in operation 207 on the display of the server (101) or provide it to an external device (e.g., an external server, a management device (100)).

[0104] For example, the server (101) may display at least one of the determined first address information and first port information on the display of the server (101). In this case, the user can identify the first address information and first port information displayed on the display of at least one server (101).

[0105] For example, the server (101) may upload at least one of the determined first address information and first port information onto a management site (e.g., an SDN management site) supported by the server (101). In this case, the user can identify the first address information and first port information uploaded onto the management site.

[0106] For example, the server (101) may provide (or transmit) at least one of the first address information and the first port information to an external server. For example, the external server may upload the first address information and the first port information to a management site (e.g., an SDN management site (or management system)). In this case, the user may identify the first address information and the first port information uploaded to the management site (or management system).

[0107] For example, the server (101) may transmit at least one of the first address information and the first port information to the management device (100). In this case, the user may identify the first address information and the first port information through the display of the management device (100).

[0108] Operation 201 of FIG. 2 of the present disclosure may correspond to operation 171 of FIG. 1b. Operation 203 of FIG. 2 of the present disclosure may correspond to operation 173 of FIG. 1b. Operation 205 of FIG. 2 of the present disclosure may correspond to operations 175 to 176 of FIG. 1b. Operation 207 of FIG. 2 of the present disclosure may correspond to operation 177 of FIG. 1b.

[0109] FIG. 3 is a diagram illustrating a method for registering network devices in a device inventory of a server according to one embodiment.

[0110] Referring to FIG. 3, a management screen (311) for network devices (130) may be displayed on the display (300) of a management device (100) according to one embodiment. For example, the screen (311) may include a first tab (301) for a device inventory (111).

[0111] When the first tab (301) for the device inventory (111) is selected, network devices (130) registered in the device inventory (111) may be displayed in one area of ​​the screen (311).

[0112] In one area of ​​Fig. 3, network devices (130) are not displayed and "no data to display" is displayed, so there may not be any network devices (130) registered in the device inventory (111) of the current server (101).

[0113] Hereinafter, FIGS. 4 and 5 describe a method for registering network devices (130) in a device inventory (111).

[0114] FIG. 4 illustrates a method for adding network devices to a device inventory according to one embodiment.

[0115] Referring to FIG. 4, a display (300) of a management device (100) according to one embodiment may display a screen (311) for network devices (130). When a first tab (301) within the screen (311) is selected, a first UI (401) for adding (or registering) network devices (130) may be displayed on the screen (311).

[0116] According to one embodiment, a user may select a first UI (401) through an interface (e.g., touch screen, keyboard) of a management device (100). In this case, a second UI (410) for adding (or registering) network devices (130) may be displayed in an area of ​​the screen (311).

[0117] According to one embodiment, the second UI (410) may include a first input field (411) for the name of a network device (e.g., the first network device (131)), a second input field (412) for a group to which the network device is included, a third input field (413) for address information of the network device to be managed, a fourth input field (414) for the type of the network device, a fifth input field (415) for the model of the network device, a sixth input field (416) for the profile of the network device, a seventh input field (417) for the physical location of the network device (e.g., rack number 3, shelf number 4), and / or an eighth input field (418) for matters associated with the network device.

[0118] According to one embodiment, the user can input information into each of the input fields of the second UI (410) (e.g., first input field (411) to eighth input field (418)) through the management device (100).

[0119] According to one embodiment, when information is entered into each of the input fields, the entered information can be stored in the device inventory (111) of the server (101).

[0120] The input of information into each of the input fields described in FIG. 4 of the present disclosure can be substantially understood as inputting address information of network devices (130) to the server (101). For example, inputting address information of a network device (e.g., MAC address) into the third input field (413) of FIG. 4 may correspond to operation 171 of FIG. 1b.

[0121] FIG. 5 is a diagram illustrating a management screen displaying registered network devices according to one embodiment.

[0122] Referring to FIG. 5, when a first tab corresponding to a device inventory (111) according to one embodiment is selected, UIs (510) containing information associated with network devices (130) may be displayed in a part of the screen (311).

[0123] For example, the screen (311) may include a first UI (511) containing information associated with a first network device (131), a second UI (512) containing information associated with a second network device (132), a third UI (513) containing information associated with a third network device (133), a fourth UI (514) containing information associated with a fourth network device (134), a fifth UI (515) containing information associated with a fifth network device (135), and / or a sixth UI (516) containing information associated with a sixth network device (136).

[0124] According to one embodiment, each of the UIs (510) may include information (521) indicating the provisioning status of the network devices (130) (e.g., Status), information (522) indicating the name of the network devices (130) (e.g., Name), information (523) indicating the group to which the network devices (130) are included (e.g., Group), address information (524) for each network device (130) (e.g., Management IP), model information (525) for each network device (130) (e.g., Model), information (526) for each type of the network devices (130) (e.g., Type), information for specific details of the network devices (130) (e.g., Note), and / or toggle buttons (527) for changing the provisioning status.

[0125] For example, the first UI (511) may correspond to the first network device (131). The first UI (511) may include the provisioning status of the first network device (131) (e.g., Unprovisioned), the name of the first network device (131) (e.g., A), the group to which the first network device (131) belongs (e.g., ALL), address information of the first network device (131) (e.g., 172.20.10.33), information about the model of the first network device (131), and / or information about the type of the first network device (131) (e.g., ACCESS). For example, the second UI (512) may correspond to the second network device (132). The second UI (512) may include the provisioning status of the second network device (132) (e.g., Unprovisioned), the name of the second network device (132) (e.g., B), the group to which the second network device (132) belongs (e.g., ALL), address information of the second network device (132) (e.g., 172.20.10.34), information about the model of the second network device (132), and / or information about the type of the second network device (132) (e.g., ACCESS).

[0126] For example, the sixth UI (516) may correspond to the sixth network device (136). The sixth UI (516) may include the provisioning status of the sixth network device (136) (e.g., provisioned), the name of the sixth network device (136) (e.g., F), the group to which the sixth network device (136) belongs (e.g., ALL), the address information of the sixth network device (136) (e.g., 172.20.10.24), information about the model of the sixth network device (136), and / or information about the type of the sixth network device (136) (e.g., ACCESS).

[0127] According to one embodiment, the screen (311) may display a first state UI (531) indicating the number of network devices with the provisioning status set to ON, a second state UI (532) indicating the number of network devices with the provisioning status set to OFF, and a third state UI (533) indicating whether data processing has failed.

[0128] According to one embodiment, a user can change the provisioning status of network devices (130) (e.g., a state indicating whether information collection is enabled) by selecting toggle buttons (527) displayed on the display (300) of the management device (100). For example, if the first toggle button (561) corresponding to the first network device (131) among the toggle buttons (527) indicates an off state, the provisioning status of the first network device (131) can be changed to on when the user selects the first toggle button (561) displayed on the screen (311). In another example, if the first toggle button (561) indicates an on state, the provisioning status of the first network device (131) can be changed to off when the user selects the first toggle button (561) displayed on the screen (311).

[0129] FIG. 6 illustrates a method for identifying the provisioning status of network devices according to one embodiment.

[0130] Referring to FIG. 6, when a second tab (302) corresponding to a tracer module (120) according to one embodiment is selected, a first UI (610) for managing network devices may be displayed in a part of the screen (311).

[0131] According to one embodiment, network devices (130) registered in the device inventory (111) may be displayed in the first UI (610), and the provisioning status of the network devices (130) may be displayed.

[0132] For example, when the provisioning status of the first network device (131) is OFF, the box for the name of the first network device (131) (e.g., A) may not be checked. For example, when the provisioning status of the sixth network device (136) is ON, the box for the name of the sixth network device (136) (e.g., F) may be checked.

[0133] According to one embodiment, the user can check whether the provisioning status of the sixth network device (136) is ON through the first UI (610) displayed on the display (300) of the management device (100).

[0134] FIG. 7 is a diagram illustrating the form in which address information of collected network devices is stored according to one embodiment.

[0135] Referring to FIG. 7, a server (101) according to one embodiment can obtain address information and / or port information from network devices (130) at specified intervals.

[0136] According to one embodiment, the acquired address information and / or port information may be stored in the memory of the server (101) or network address storage (121), such as in the first table (700). For example, the first table (700) may include IP address information (711) (e.g., 10.50.10.5), MAC address information (712) (e.g., A8:2B:B5:47:1C:A3), and / or VLAN (Virtual Local Area Network) related information (713) (e.g., 11) of a network device (e.g., the first network device (131)).

[0137] For example, a VLAN can be referred to as a method of dividing a single physical network into multiple logical networks. In other words, a VLAN can logically separate a network, and if network devices on the same physical network are configured to belong to different VLANs, communication between network devices belonging to different VLANs can be blocked.

[0138] FIG. 8 illustrates a method for inputting address information of a first UE according to one embodiment.

[0139] Referring to FIG. 8, a screen corresponding to a second tab (302) (e.g., MAC and IP Tracer) may be displayed on the display (300) of a management device (100) according to one embodiment. For example, a first UI (810) for searching for a UE may be displayed on one area of ​​the display (300). For example, the first UI (810) may include a first input field (811) for searching for a UE. For example, an input field addition button (820) for increasing the number of UEs being searched may be displayed on one area of ​​the display (300). For example, if there is user input for the input field addition button (820), additional input fields may be created in addition to the first input field (811).

[0140] According to one embodiment, a user can input address information (e.g., IP information, MAC information) of a first UE (151) that has failed in the first UI (810) into a first input field (811) of the first UI (810) through a management device (100). In this case, the address information of the first UE (151) can be input into a server (101).

[0141] For example, a user entering address information into the first input field (811) of the first UI (810) through the management device (100) can be substantially referred to as entering a request for the first UE (151) to the server (101). For example, a user entering address information into the first input field (811) of the first UI (810) through the management device (100) can substantially correspond to operation 171 of FIG. 1B.

[0142] FIG. 9 illustrates a method for inputting address information of a plurality of UEs according to one embodiment.

[0143] Referring to FIG. 9, a screen corresponding to a second tab (302) (e.g., MAC and IP Tracer) may be displayed on the display (300) of a management device (100) according to one embodiment. For example, a first UI (910) for searching for multiple UEs may be displayed on one area of ​​the display (300). For example, the first UI (910) may include a first input field (811), a second input field (812), and / or a third input field (813) for searching for multiple UEs.

[0144] According to one embodiment, address information of a UE (e.g., MAC address or IP address) can be entered into each of the first input field (811), second input field (812), and third input field (813) of the first UI (910).

[0145] FIG. 10 illustrates UIs displayed on a display when a plurality of UEs are entered into input fields according to one embodiment.

[0146] Referring to FIG. 10, according to one embodiment, a user can input address information of a plurality of UEs into each of the first input field (811), the second input field (812), and the third input field (813) using a management device (100). For example, the MAC address of the first UE (151) can be input into the first input field (811), the MAC address of the second UE (152) can be input into the second input field (812), and the MAC address of the third UE can be input into the third input field (813).

[0147] According to one embodiment, based on the input fields where address information of a plurality of UEs that have failed is entered, the server (101) can identify the address information of a plurality of UEs. For example, the server (101) can identify the address information of a first UE (151) (e.g., 57:04:80:67:60:12), and the server (101) can identify the address information of a second UE (152) (e.g., 65:56:38:50:43:58). The server (101) can identify the address information of a third UE (e.g., 22:27:73:02:30:80).

[0148] According to one embodiment, a screen corresponding to a second tab may be displayed on the display (300), and a first UE tab (1011) associated with a first UE (151), a second UE tab (1012) associated with a second UE (152), and a third UE tab (1013) associated with a third UE may be displayed on the display (300).

[0149] According to one embodiment, a user can identify location information of a UE (e.g., address information and / or port information) by selecting one of a plurality of UE tabs through a management device (100). For example, if the user selects a second tab (1012) through the management device (100), a UI (1021) associated with the second UE (152) may be displayed on the display (300).

[0150] The UI (1021) associated with the second UE (152) may display the name of the third network device (133) to which the second UE (152) is connected (e.g., device_10104146), the IP address of the third network device (133) to which the second UE (152) is connected (e.g., 10.10.4.146), the port information of the third network device (133) to which the second UE (152) is connected (e.g., TenGi670), the model name of the third network device (133) (e.g., E7124), and / or the time of information collection (e.g., 2024-10-20:53:40 PM).

[0151] As a result, the user can identify the address information and / or port information of a network device (e.g., a third network device (133)) associated with multiple UEs by entering the address information (e.g., MAC address, IP address) of multiple UEs that have failed into the input fields. Through this, the server (101) and / or management device (100) can quickly and easily identify the source of the failure when a failure occurs.

[0152] According to one embodiment, the location of a network device connected to a UE in a complex network environment can be quickly identified in the present disclosure.

[0153] According to one embodiment, the collection of network addresses (e.g., MAC addresses, IP addresses) in the present disclosure is automated, so that the accuracy and consistency of the collected data can be improved.

[0154] In addition, various effects identified directly or indirectly through the present disclosure may be provided.

[0155] FIG. 11 illustrates UIs displayed on a display when a plurality of UEs are entered into input fields according to one embodiment.

[0156] Referring to FIG. 11, location information of the second UE (152) (e.g., address information (1141) and / or port information (1142)) may be displayed on the display (300) according to one embodiment.

[0157] According to one embodiment, the location information of the second UE (152) displayed on the display (300) (e.g., address information (1141) and / or port information (1142)) may include location information of past times as well as the current time (e.g., the time when a request for the second UE (152) is received).

[0158] For example, the first UI (1131) may include information about a network device associated with the second UE (152) at the current time (or, recent time). For example, the first UI (1131) may include address information (e.g., 10.10.5.145) and port information (e.g., TenGi983) of a third network device (133) that is a network device associated with the second UE (152) at the current time. For example, the second UI (1132) may include address information (e.g., 10.10.5.145) and port information (e.g., TenGi236) of a third network device (133) that is a network device associated with the second UE (152) at a first time that is a specified period prior to the current time. For example, the third UI (1133) may include address information (e.g., 10.10.5.145) and port information (e.g., TenGi114) of the third network device (133), which is the network device associated with the second UE (152) at a second time point that is a specified period prior to the first time point. For example, the fourth UI (1134) may include address information (e.g., 10.10.5.145) and port information (e.g., TenGi538) of the third network device (133), which is the network device associated with the second UE (152) at a third time point that is a specified period prior to the second time point. For example, the 5th UI (1135) may include address information (e.g., 10.10.5.145) and port information (e.g., TenGi469) of the 3rd network device (133), which is the network device associated with the 2nd UE (152) at a 4th time point that is a specified period prior to the 3rd time point. For example, the 6th UI (1136) may include address information (e.g., 10.10.5.145) and port information (e.g., TenGi26) of the 3rd network device (133), which is the network device associated with the 2nd UE (152) at a 5th time point that is a specified period prior to the 4th time point.

[0159] When comparing the first UI (1131) and the second UI (1132), the network device to which the second UE (152) was connected at the current time and the first time, respectively, may be the same as the third network device (133). On the other hand, the port to which the second UE (152) was connected at the current time and the first time, respectively, was changed from the current port (e.g., TenGi983) to the first port (e.g., TenGi236).

[0160] Although not illustrated in FIG. 11 of the present disclosure, the network devices to which the second UE (152) was connected may differ depending on the time. For example, at a first future time, which is a specified period after the current time, the second UE (152) may be connected to the first network device (131). In this case, the address information (1141) corresponding to the first future time may indicate the address information of the first network device (131) rather than the address information of the third network device (133) (e.g., 10.10.5.145).

[0161] Consequently, the user can identify the address information and / or port information of the network device associated with the second UE (152) that changes over time based on the location information of the second UE (152) (e.g., address information (1141) and / or port information (1142)) displayed on the display (300) of the management device (100).

[0162] The present disclosure can enhance the efficiency of network management through the automation of network management (e.g., automation of the process of collecting, storing, and managing MAC / IP addresses). For example, the present disclosure can provide real-time network visibility. The present disclosure can enable rapid troubleshooting by establishing a system capable of identifying the location and connection status of network equipment in real time. As another example, the present disclosure can implement a scalable network management system. As yet another example, the present disclosure can enhance the accuracy and consistency of network information through an automated data collection and storage system. As yet another example, the present disclosure can implement a function capable of effectively tracking and recording changes in equipment location and network topology. As yet another example, the present disclosure can provide an intuitive user interface that allows for easy querying and management of complex network information.

[0163] As another example, the present disclosure enables IT personnel and resources to be focused on more critical tasks by streamlining network management processes. As another example, the present disclosure can reduce long-term network management costs through an automated management system. As another example, the present disclosure can reduce the time and effort required for network expansion and modification by automating the registration and configuration process of new equipment. As another example, the present disclosure can enhance the accuracy and reliability of the digital twin by enabling real-time synchronization between the physical network and the digital twin model through the periodic collection and storage of MAC and IP addresses. As another example, the present disclosure can establish a foundation for performing network performance prediction, identification of potential problems, and simulation of optimization scenarios by utilizing the digital twin model. As another example, the present disclosure dynamically visualizes network topology based on collected data, allowing administrators to intuitively understand network structure and changes.

[0164] As another example, the present disclosure may provide simulation and analysis functions utilizing a digital twin model to support decision-making regarding network expansion, upgrades, troubleshooting, etc. As yet another example, the present disclosure may provide a function capable of analyzing network usage patterns and change trends over time by reflecting the change history of MAC and IP addresses in the digital twin model.

[0165] FIG. 12 is a block diagram of a server according to one embodiment of the present disclosure.

[0166] Referring to FIG. 12, the server (101) of the present disclosure may include a control unit (controller) (1230), a transmission / reception unit (1210), and a storage unit (memory) (1220). However, the components of the server (101) are not limited to the examples described above. For example, the server (101) may include more components or fewer components than the components described above. Furthermore, the control unit (1230), the transmission / reception unit (1210), and the storage unit (1220) may be implemented in the form of a single chip. The control unit (1230) of FIG. 12 may include at least one processor or controller.

[0167] According to one embodiment, the control unit (1230) can control a series of processes so that the server can operate according to the embodiment of the present disclosure described above.

[0168] According to one embodiment, the transceiver (1210) can transmit and receive signals with a server. The signals transmitted and received with the server may include control information and data. The transceiver (1210) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver (1210), and the components of the transceiver (1210) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1210) can receive a signal through a wireless channel and output it to a control unit (1230), and transmit the signal output from the control unit (1230) through a wireless channel.

[0169] According to one embodiment, the storage unit (1220) may store programs and data necessary for the operation of the server (101). Additionally, the storage unit (1220) may store control information or data included in signals transmitted and / or received by the server (101). The storage unit (1220) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple storage units (1220).

[0170] According to one embodiment, a method performed by a server supporting a software defined networking (SDN) system may include: identifying network devices to be managed through the SDN system; obtaining address information for network addresses of the network devices and port information for ports of the network devices at specified intervals; determining first address information for the network address of the at least one network device and first port information for the port of the at least one network device based on the address information and port information when a request for a first UE (user equipment) associated with at least one network device is input; and displaying at least one of the first address information and the first port information on a display of the server or providing it to an external device.

[0171] According to one embodiment, the method further includes the operation of receiving the request for the first UE based on the occurrence of a communication failure of the first UE, and at least one of the first address information and the first port information may be used for managing the communication failure.

[0172] According to one embodiment, the at least one network device associated with the first UE may include at least one of a first network device to which the first UE is connected, or network devices disconnected from the first UE.

[0173] According to one embodiment, the first address information includes at least one of the address information of the first network device or the address information of the disconnected network devices, and the first port information may include at least one of the information about the port to which the first UE is connected among the ports of the first network device, or the information about the port to which the first UE was connected among the ports of the disconnected network devices.

[0174] According to one embodiment, the request for the first UE includes information regarding the network address of the first UE, and the request for the first UE can be input to the server through user input.

[0175] According to one embodiment, the method includes an operation of identifying an input that enables the collection of the address information and the port information, and based on the input that enables the collection, the address information and the port information may be obtained at the specified interval.

[0176] According to one embodiment, the input that enables the collection may correspond to user input for the user interfaces (UIs) of the network devices displayed on the display of the server.

[0177] According to one embodiment, the method may further include the operation of storing the acquired address information and the acquired port information in the memory of the server.

[0178] According to one embodiment, the address information may include at least one of an IP (internet protocol) address or a MAC (medium access control) address.

[0179] According to one embodiment, the network devices may include a switch for controlling data transmission within a network managed through the SDN system or a router for controlling data transmission between networks managed through the SDN system.

[0180] According to one embodiment, a server supporting a software defined networking (SDN) system includes at least one processor and a memory for storing instructions. When the instructions are executed individually or collectively by the at least one processor, the server identifies network devices to be managed through the SDN system, obtains address information for network addresses of the network devices and port information for ports of the network devices at designated intervals, and when a request for a first UE (user equipment) associated with at least one network device is input, determines first address information for the network address of the at least one network device and first port information for the port of the at least one network device based on the address information and the port information, and can display at least one of the first address information and the first port information on the server's display or transmit it to an external device.

[0181] According to one embodiment, when the instructions are executed individually or collectively by the at least one processor, the server receives the request for the first UE based on the occurrence of a communication failure of the first UE, and at least one of the first address information and the first port information may be used for managing the communication failure.

[0182] According to one embodiment, the at least one network device associated with the first UE may include at least one of a first network device to which the first UE is connected, or network devices disconnected from the first UE.

[0183] According to one embodiment, the first address information includes at least one of the address information of the first network device or the address information of the disconnected network devices, and the first port information may include at least one of the information about the port to which the first UE is connected among the ports of the first network device, or the information about the port to which the first UE was connected among the ports of the disconnected network devices.

[0184] According to one embodiment, the request for the first UE includes information regarding the network address of the first UE, and the request for the first UE can be input to the server through user input.

[0185] According to one embodiment, when the instructions are executed individually or collectively by the at least one processor, the server identifies an input that enables the collection of the address information and the port information, and based on the input that enables the collection, the address information and the port information may be obtained at the specified interval.

[0186] According to one embodiment, the input that enables the collection may correspond to user input for the user interfaces (UIs) of the network devices displayed on the display of the server.

[0187] According to one embodiment, when the instructions are executed individually or collectively by the at least one processor, the server may store the acquired address information and the acquired port information in the memory of the server.

[0188] According to one embodiment, the address information may include at least one of an IP (internet protocol) address or a MAC (medium access control) address.

[0189] According to one embodiment, the network devices may include a switch for controlling data transmission within a network managed through the SDN system or a router for controlling data transmission between networks managed through the SDN system.

[0190] Meanwhile, the present specification and drawings disclose preferred embodiments of the present invention. Although specific terms have been used, they are used merely in a general sense to facilitate the explanation of the technical content of the present invention and to aid in understanding the invention, and are not intended to limit the scope of the present invention. It is obvious to those skilled in the art that, in addition to the embodiments disclosed herein, other variations based on the technical concept of the present invention are possible.

Claims

1. A method performed by a server supporting an SDN (software defined networking) system, An operation to identify network devices to be managed through the above SDN system; An operation of acquiring address information for the network addresses of the network devices and port information for the ports of the network devices at designated intervals; When a request for a first UE (user equipment) associated with at least one of the above network devices is input, an operation to determine first address information for the network address of the at least one network device and first port information for the port of the at least one network device based on the address information and the port information; and A method comprising the operation of providing at least one of the first address information and the first port information to an external device.

2. In Claim 1, The operation of receiving the request for the first UE based on the occurrence of a communication failure of the first UE is further included. A method in which at least one of the first address information and the first port information is used for managing the communication failure.

3. In Claim 1, A method comprising at least one network device associated with the first UE, the first network device to which the first UE is connected, or at least one of network devices disconnected from the first UE.

4. In Claim 3, The first address information includes at least one of the address information of the first network device or the address information of the disconnected network devices, and A method comprising at least one of the following: the first port information is information about a port to which the first UE is connected among the ports of the first network device, or information about a port to which the first UE was connected among the ports of the disconnected network devices.

5. In Claim 1, The request for the first UE includes information about the network address of the first UE, and A method in which the request for the first UE is input to the server through user input.

6. In Claim 1, It includes an operation to identify an input that enables the collection of the above address information and the above port information, and A method in which the address information and the port information are obtained at the specified intervals based on the input that enables the collection.

7. In Claim 6, A method in which the input enabling the above collection corresponds to user input for the UI (user interface) of the network devices displayed on the display of the server or the external device.

8. In Claim 6, A method further comprising the operation of storing the acquired address information and the acquired port information in the memory of the server.

9. In Claim 1, A method in which the above address information includes at least one of an IP (internet protocol) address or a MAC (medium access control) address.

10. In Claim 1, A method comprising the above network devices including a switch for controlling data transmission within a network managed through the SDN system or a router for controlling data transmission between networks managed through the SDN system.

11. In a server supporting an SDN (software defined networking) system, At least one processor; and It includes memory for storing instructions, When the above instructions are executed individually or collectively by the at least one processor, the server: Identify network devices to be managed through the above SDN system, and At designated intervals, obtain address information for the network addresses of the above network devices and port information for the ports of the above network devices, and When a request for a first UE (user equipment) associated with at least one of the above network devices is input, first address information for the network address of the at least one network device and first port information for the port of the at least one network device are determined based on the address information and the port information, and A server that provides at least one of the first address information and the first port information to an external device.

12. In Claim 11, When the above instructions are executed individually or collectively by the at least one processor, the server: Based on the occurrence of a communication failure of the first UE, the request for the first UE is received, and A server, wherein at least one of the first address information and the first port information is used for managing the communication failure.

13. In Claim 11, The at least one network device associated with the first UE comprises a server including at least one of a first network device to which the first UE is connected, or network devices disconnected from the first UE.

14. In Claim 13, The first address information includes at least one of the address information of the first network device or the address information of the disconnected network devices, and A server comprising at least one of the following: information regarding a port to which the first UE is connected among the ports of the first network device, or information regarding a port to which the first UE was connected among the ports of the disconnected network devices.

15. In Claim 11, The request for the first UE includes information about the network address of the first UE, and The request for the first UE is input to the server through user input.

Images