Computer system, network analysis method, and program

The network management server identifies unregistered terminals by analyzing connection history, reducing unnecessary authentication and facilitating user estimation, thus managing unauthorized network connections effectively.

JP7578579B2Active Publication Date: 2024-11-06FORTINET INC
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2021205973
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-12-20
Publication Date
2024-11-06
Estimated Expiration
2041-12-20

AI Technical Summary

Technical Problem

Existing network systems face challenges in identifying and managing unregistered terminals connected to company networks, leading to unnecessary authentication processing and increased load on authentication servers.

Method used

A network management server that monitors network connections, generates connection history information, and identifies unregistered terminals by analyzing connection history with registered terminals, presenting analysis information to estimate the user of unregistered devices.

Benefits of technology

Enables quick and efficient identification of unregistered terminal users, reducing unnecessary authentication processing and allowing administrators to take corrective actions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007578579000001
    Figure 0007578579000001
  • Figure 0007578579000002
    Figure 0007578579000002
  • Figure 0007578579000003
    Figure 0007578579000003
Patent Text Reader

Abstract

To present information useful for identifying a user of a terminal whose use is not permitted.SOLUTION: A computer system is connected to a network that includes multiple network devices that accommodate terminals, acquires information about the connected terminals from the multiple network devices, generates connection history information for grasping a connection status of the terminals in the network, identifies, on the basis of the connection history information, a connection history of a target terminal whose identification information for management of the network is unknown, identifies a connection history of a reference terminal to which the identification information for management is assigned and which performs connection and disconnection at the same time as the target terminal with reference to the connection history information, and presents analysis information including the connection history of the target terminal and the reference terminal.SELECTED DRAWING: Figure 2
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a technology for monitoring a network system. [Background technology]

[0002] In many companies, from the viewpoint of security, the company operates in such a way that only terminals with pre-registered MAC (Media Access Control) addresses can use the company's network. An example of a network system that realizes the above-mentioned network operation is disclosed in, for example, Patent Document 1.

[0003] In the network system disclosed in Patent Document 1, the MAC address of a user terminal that is permitted to connect to and be used by the authentication switch is registered in the authentication DB of the authentication server. When a user terminal is connected to the authentication switch, the authentication switch requests authentication processing from the authentication server along with the MAC address of the user terminal. Based on the authentication result from the authentication server, the authentication switch decides whether or not to allow the user terminal to communicate. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2016-143396 A Summary of the Invention [Problem to be solved by the invention]

[0005] Companies need to operate their networks while considering the possibility that users' privately used terminals, such as personal computers and smartphones, may connect to the company's intranet's Layer 2 switches (hereinafter referred to as L2 switches) and network devices, such as wireless LAN access points, without authorization. By using publicly known authentication technology such as that described in Patent Document 1, it is possible to prevent communication even if an unregistered terminal connects to a network device.

[0006] However, if an unregistered terminal continues to be connected to a network device, authentication processing for connection requests from the unregistered terminal will also continue to occur, placing an unnecessary burden on the authentication server and network devices, etc. Therefore, when there is a terminal that continues to fail authentication, there is a need to quickly identify the user of that terminal and take corrective measures such as disconnecting the terminal from the L2 switch or deleting the connection settings to a wireless LAN access point.

[0007] An object of the present invention is to provide a technique for presenting information useful for identifying a user of an unregistered terminal. [Means for solving the problem]

[0008] A representative example of the invention disclosed in the present application is as follows: That is, a computer system connected to a network including a plurality of network devices accommodating terminals includes at least one computer having a CPU, a storage device connected to the CPU, and a network interface connected to the CPU, the at least one computer acquires information about the connected terminals from the plurality of network devices, generates connection history information for grasping the connection state of the terminals in the network, identifies the connection history of a target terminal whose management identification information of the network is unknown based on the connection history information, refers to the connection history information to identify the connection history of a reference terminal that is assigned the management identification information and that connects and disconnects at the same time as the target terminal, and presents analysis information including the connection histories of the target terminal and the reference terminal. Effect of the Invention

[0009] According to the present invention, it is possible to present information that is useful for identifying the user of a terminal (unregistered terminal) whose management identification information is unknown. Based on the information, the administrator of the network system can quickly and easily guess the user of the unregistered terminal. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 illustrates an example of a configuration of a network system according to a first embodiment. [Diagram 2] FIG. 2 illustrates an example of the configuration of a network management server according to the first embodiment. [Diagram 3] FIG. 2 illustrates an example of the configuration of an L2 switch according to a first embodiment. [Figure 4] FIG. 2 illustrates an example of the configuration of a wireless LAN access point according to the first embodiment. [Diagram 5] 11 is a diagram illustrating an example of a data structure of connection monitoring information according to the first embodiment; [Figure 6] 11 is a diagram illustrating an example of a data structure of wireless connection monitoring information according to the first embodiment. [Figure 7] FIG. 13 is a diagram illustrating an example of a data structure of registered terminal information according to the first embodiment. [Figure 8A] FIG. 11 is a diagram illustrating an example of a data structure of connection history information according to the first embodiment. [Figure 8B] FIG. 13 is a diagram illustrating an example of a data structure of connection history information according to the first embodiment. [Figure 9] FIG. 4 is a diagram illustrating an example of a data structure of mobile terminal analysis information according to the first embodiment. [Figure 10] FIG. 11 is a diagram illustrating an example of a data structure of FDB information according to the first embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of a data structure of FDB information according to the first embodiment. [Figure 12] 11 is a diagram illustrating an example of a data structure of wireless connection terminal information according to the first embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of a data structure of authentication information according to the first embodiment. [Figure 14] 11 is a flowchart illustrating an example of a monitoring information generation process executed by the network management server according to the first embodiment. [Figure 15] 11 is a flowchart illustrating an example of a history information generating process executed by the network management server according to the first embodiment. [Figure 16]11 is a flowchart illustrating an example of an information generating process executed by the network management server according to the first embodiment. [Figure 17] 11 is a flowchart illustrating an example of an information update process executed by the network management server according to the first embodiment. [Figure 18] FIG. 11 is a diagram illustrating an example of a search screen presented by the network management server according to the first embodiment. [Figure 19] 11 is a flowchart illustrating an example of a mobile terminal analysis information generating process executed by the network management server according to the first embodiment. [Figure 20] FIG. 11 is a diagram illustrating an example of a processing result screen presented by the network management server according to the first embodiment. [Figure 21] FIG. 11 is a diagram illustrating an example of a network configuration according to an example of a network system according to a second embodiment. [Figure 22] FIG. 11 illustrates an example of the configuration of a wireless LAN controller according to a second embodiment. [Diagram 23] FIG. 11 is a diagram illustrating an example of a data structure of FDB information according to the second embodiment. [Figure 24] FIG. 11 is a diagram illustrating an example of a data structure of wireless connection terminal information according to the second embodiment. [Diagram 25] FIG. 11 is a diagram illustrating an example of a data structure of wireless LAN access point information according to the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. However, it should be noted that this embodiment is merely an example for realizing the present invention and does not limit the technical scope of the present invention. In the configuration of the invention described below, the same or similar configurations or functions are given the same reference numerals, and duplicated explanations are omitted. The position, size, shape, range, etc. of each configuration shown in the drawings, etc. may not represent the actual position, size, shape, range, etc., in order to facilitate understanding of the invention. Therefore, the present invention is not limited to the position, size, shape, range, etc. disclosed in the drawings, etc.

[0012] In this specification, the switches and access points that configure the network are referred to as “network devices.” Furthermore, when there is no need to distinguish between the network devices and the terminals that communicate within the network, they are referred to as “devices.” EXAMPLES

[0013] Conventional technology has the problem that it is difficult to identify the user of an unregistered terminal connected to a wireless LAN access point. This is because there is no physical connection cable like in a wired connection, and the terminal can be easily moved. Also, while there is a method to register information about the user of an unregistered terminal in advance, this is not realistic.

[0014] In the network system of the first embodiment, a network management server that monitors an intra-company network presents information that is useful for identifying a user of an unregistered terminal, based on the connection history of registered terminals.

[0015] FIG. 1 is a diagram illustrating an example of a configuration of a network system according to a first embodiment.

[0016] The network system is composed of a network management server 100 and an in-house network 101. The network management server 100 and the in-house network 101 are connected via a network 102 such as a LAN or a WAN. The in-house network 101 is composed of one L2 switch 110 and two wireless LAN access points 120-1 and 120-2. The in-house network 101 includes four terminals 130-1, 130-2, 130-3, and 130-4.

[0017] In the following description, the identification information such as the MAC address of L2 switch 110 is designated as S10, the identification information of wireless LAN access point 120-1 as S20, and the identification information of wireless LAN access point 120-2 as S21. Also, the identification information of terminal 130-1 is designated as U10, the identification information of terminal 130-2 as U20, the identification information of terminal 130-3 as U30, and the identification information of terminal 130-4 as U40.

[0018] In the following description, when there is no need to distinguish between the wireless LAN access points 120-1 and 120-2, they will be referred to as wireless LAN access point 120. When there is no need to distinguish between the terminals 130-1, 130-2, 130-3, and 130-4, they will be referred to as terminal 130.

[0019] The configuration of the network devices constituting the intranet 101 is merely an example and is not limited to this. The number of L2 switches 110, wireless LAN access points 120, and terminals 130 may be arbitrary. The network management server 100 may be included in the intranet 101.

[0020] The L2 switch 110 has four ports 111-1, 111-2, 111-3, and 111-4. In the following description, when there is no need to distinguish between the ports 111-1, 111-2, 111-3, and 111-4, they will be referred to as ports 111. The ports 111 are connected to devices via cables such as copper wires and optical fibers. Specifically, the port 111-1 is connected to the wireless LAN access point 120-1, the port 111-2 is connected to the wireless LAN access point 120-2, and the port 111-3 is connected to the terminal 130-4. No device is connected to the port 111-4.

[0021] The wireless LAN access point 120 has a port 121 for connecting to a device by wire and a port 121 for connecting to a device wirelessly. Port 121-1 of the wireless LAN access point 120-1 is connected to the L2 switch 110, and port 121 (not shown) of the wireless LAN access point 120-1 is connected to terminals 130-1, 130-2, and 130-3. Port 121-2 of the wireless LAN access point 120-2 is connected to the L2 switch 110. No terminal 130 is connected to the wireless LAN access point 120-2.

[0022] Next, the configuration of devices included in the network system will be described with reference to FIGS.

[0023] FIG. 2 is a diagram illustrating an example of the configuration of the network management server 100 according to the first embodiment.

[0024] The network management server 100 includes a CPU 201 , a network I / F 202 , and a memory 203 .

[0025] The CPU 201 is a computing device that executes programs stored in the memory 203. The CPU 201 executes processes according to the programs, thereby operating as a functional unit (module) that realizes a specific function. In the following explanation, when a process is explained with the functional unit as the subject, it indicates that the CPU 201 is executing a program that realizes the functional unit. The network I / F 202 is an interface for connecting to an external device via a network. The memory 203 is a storage device that stores the programs executed by the CPU 201 and information used by the programs. The memory 203 is also used as a work area.

[0026] The memory 203 stores programs that realize the history verification unit 210 and the user I / F unit 211. The memory 203 also stores connection monitoring information 220, wireless connection monitoring information 221, registered terminal information 222, connection history information 223, and mobile terminal analysis information 224.

[0027] The connection monitoring information 220 is information for managing the connection state of the device in the current intranet 101. The details of the data structure of the connection monitoring information 220 will be described with reference to FIG. 5. The wireless connection monitoring information 221 is information for managing the connection state of the wireless LAN access point 120. The details of the data structure of the wireless connection monitoring information 221 will be described with reference to FIG. 6. The registered terminal information 222 is information for managing the terminal 130 registered in the intranet 101. The details of the data structure of the registered terminal information 222 will be described with reference to FIG. 7. The connection history information 223 is information for managing the history of the connection state of the device in the intranet 101. The details of the data structure of the connection history information 223 will be described with reference to FIG. 8A and FIG. 8B. The mobile terminal analysis information 224 is information for managing the analysis result of the connection state of the mobile terminal (terminal 130) in the intranet 101. The details of the data structure of the mobile terminal analysis information 224 will be described with reference to FIG. 9.

[0028] The history verification unit 210 monitors the connection status of devices in the company network 101, and also presents information useful for identifying the user of the unregistered terminal 130 in the company network 101. The history verification unit 210 includes a collection unit 230, a history generation unit 231, and an analysis unit 232. The user I / F unit 211 provides an interface for performing various settings and operations.

[0029] FIG. 3 is a diagram illustrating an example of the configuration of the L2 switch 110 according to the first embodiment.

[0030] The L2 switch 110 includes a CPU 301, a network I / F 302, a memory 303, and a packet relay device 304. The CPU 301 and the memory 303 are similar hardware to the CPU 201 and the memory 203.

[0031] The network I / F 302 has a plurality of ports 111. The packet relay 304 assigns the port 111 to which the packet is to be forwarded. Specifically, when a packet is received via one of the ports 111 of the network I / F 302, the packet relay 304 determines the port 111 to which the packet is to be forwarded based on FDB (Forwarding Data Base) information 320 and the destination MAC address included in the packet, and forwards the packet to the port 111. When the destination MAC address is the MAC address of the L2 switch 110, the packet relay 304 interprets the packet as being addressed to the L2 switch 110, and forwards the packet to the CPU 301. The packet relay 304 performs MAC address learning as necessary. That is, the packet relay 304 registers an entry in the FDB information 320, which includes the source MAC address included in the packet and the identification information of the port 111 that received the packet.

[0032] The memory 303 stores a program that realizes the control unit 310 and the user I / F unit 311. The memory 303 also stores FDB information 320.

[0033] The FDB information 320 is information for controlling packet transfer. The details of the data structure of the FDB information 320 will be described with reference to FIG.

[0034] The control unit 310 controls the entire L2 switch 110. The user I / F unit 311 provides an interface for performing various settings and operations.

[0035] FIG. 4 is a diagram illustrating an example of the configuration of the wireless LAN access point 120 according to the first embodiment.

[0036] The wireless LAN access point 120 includes a CPU 401, a network I / F 402, a memory 403, and a packet relay unit 404. The CPU 401 and the memory 403 are similar hardware to the CPU 201 and the memory 203. The packet relay unit 404 is similar hardware to the packet relay unit 304.

[0037] The network I / F 402 has a port 121 for wired connection and a port 121 (antenna) for wireless connection.

[0038] The memory 403 stores a program that realizes a control unit 410 and a user I / F unit 411. The memory 403 also stores FDB information 420, wireless connection terminal information 421, and authentication information 422.

[0039] The FDB information 420 is information for controlling packet forwarding. The details of the data structure of the FDB information 420 will be described with reference to FIG. 11. The wireless connection terminal information 421 is information for managing the terminal 130 performing wireless communication. The details of the data structure of the wireless connection terminal information 421 will be described with reference to FIG. 12. The authentication information 422 is information for performing authentication, and is sometimes called a MAC ACL (Access Control List). The details of the data structure of the authentication information 422 will be described with reference to FIG. 13.

[0040] A control unit 410 controls the entire wireless LAN access point 120. A user I / F unit 411 provides an interface for performing various settings and operations.

[0041] When the control unit 410 receives a packet via the port 121 for wireless communication, it executes authentication processing based on the authentication information 422 and the source MAC address included in the packet. If the source MAC address is included in the authentication information 422, the control unit 410 instructs the packet relay device 404 to transfer the packet. The packet relay device 404 determines the destination port 121 based on the FDB information 420 and the destination MAC address included in the packet, and transfers the packet to the port 121. If the source MAC address is not included in the authentication information 422, the control unit 410 discards the packet.

[0042] It is common for the wireless LAN access point 120 to use an authentication protocol specific to the wireless LAN using a user ID and a password, etc., in addition to the authentication using the authentication information 422. The authentication protocol described above is executed after the authentication using the authentication information 422 has been successful. The authentication protocol specific to the wireless LAN is a well-known technique, and the description of the process related to the authentication protocol is omitted in this embodiment.

[0043] When the control unit 410 receives a packet via the port 121 for wired communication, it instructs the packet relay 404 to transfer the packet. The packet relay 404 determines the destination port 121 based on the FDB information 420 and the destination MAC address included in the packet, and transfers the packet to the determined port 121. When the destination MAC address is the wireless LAN access point 120, the packet relay 404 interprets the packet as being addressed to the wireless LAN access point 120, and transfers the packet to the CPU 401.

[0044] In addition, the packet relay device 404 performs MAC address learning as necessary. That is, the packet relay device 404 registers an entry in the FDB information 420 that combines the source MAC address included in the packet with the identification information of the port 121 that received the packet.

[0045] Next, the data structure of the information held by the network management server 100 will be described with reference to FIGS.

[0046] FIG. 5 is a diagram illustrating an example of the data structure of the connection monitoring information 220 according to the first embodiment.

[0047] The connection monitoring information 220 stores entries including a network device C501, a port C502, and a connection device C503.

[0048] Network device C501 is a column that stores identification information (MAC address) of a network device that connects to a device such as the terminal 130. In the network device C501 of this embodiment, identification information of either the L2 switch 110 or the wireless LAN access point 120 is stored. Port C502 is a column that stores identification information of a port that connects to a device. Connecting device C503 is a column that stores identification information (MAC address) of a connecting device.

[0049] FIG. 6 is a diagram illustrating an example of a data structure of the wireless connection monitoring information 221 according to the first embodiment.

[0050] The wireless connection monitoring information 221 stores entries including a wireless LAN access point C601 and a connected terminal C602.

[0051] The wireless LAN access point C601 is a column that stores the identification information (MAC address) of the wireless LAN access point 120. The connected terminal C602 is a column that stores the identification information (MAC address) of the terminal 130 that connects to the wireless LAN access point 120.

[0052] FIG. 7 is a diagram illustrating an example of a data structure of the registered terminal information 222 according to the first embodiment.

[0053] The registered terminal information 222 stores an entry including a terminal C701 and a user C702.

[0054] Terminal C701 is a column that stores identification information (MAC address) of the terminal 130. User C702 is a column that stores identification information of the user who uses the terminal 130.

[0055] An administrator may set the registered terminal information 222 using an interface provided by the user I / F unit 211, or the network management server 100 may obtain information from a management server or the like (not shown) and set the registered terminal information 222.

[0056] 8A and 8B are diagrams illustrating an example of a data structure of the connection history information 223 according to the first embodiment.

[0057] The connection history information 223 stores entries including a start date and time C801, an end date and time C802, a network device C803, a port C804, a wireless LAN access point C805, a connected terminal C806, and a user C807.

[0058] The start date and time C801 is a column for storing the time when the terminal 130 started the connection. The end date and time C802 is a column for storing the time when the terminal 130 ended the connection. The network device C803 is a column for storing the identification information (MAC address) of the L2 switch 110 that is directly or indirectly connected to the terminal 130. The port C804 is a column for storing the identification information of the port 111 of the L2 switch 110 that is directly or indirectly connected to the terminal 130. The wireless LAN access point C805 is a column for storing the identification information (MAC address) of the wireless LAN access point 120 that is connected to the terminal 130. The connected terminal C806 is a column for storing the identification information (MAC address) of the terminal 130. The user C807 is a column for storing the identification information of the user who uses the terminal 130 corresponding to the connected terminal C806. When the user who uses the terminal 130 is unknown, that is, when the terminal 130 is an unregistered terminal, the user C807 is left blank.

[0059] FIG. 9 is a diagram illustrating an example of a data structure of the mobile terminal analysis information 224 according to the first embodiment.

[0060] The mobile terminal analysis information 224 stores entries including a start date and time C901, an end date and time C902, a network device C903, a port C904, a wireless LAN access point C905, a connected terminal C906, and a user C907. Each column of the mobile terminal analysis information 224 is the same as each column of the connection history information 223.

[0061] As will be described later, the mobile terminal analysis information 224 is generated from the connection history information 223. The mobile terminal analysis information 224 is used as information that is useful for identifying the user of the unregistered terminal .

[0062] Next, the data structure of the FDB information 320 held by the L2 switch 110 will be described with reference to FIG.

[0063] FIG. 10 is a diagram illustrating an example of the data structure of the FDB information 320 according to the first embodiment.

[0064] The FDB information 320 stores an entry including a port C1001 and a connected device C1002.

[0065] Port C 1001 is a column that stores identification information of the port 111 that connects to a device. Connected Device C 1002 is a column that stores identification information (MAC address) of the connected device.

[0066] Next, the data structure of the information held by the wireless LAN access point 120 will be described with reference to FIGS.

[0067] FIG. 11 is a diagram illustrating an example of the data structure of the FDB information 420 according to the first embodiment.

[0068] The FDB information 420 stores an entry including a port C1101 and a connected device C1102.

[0069] Port C 1101 is a column that stores identification information of the port 121 that connects to a device. Connected Device C 1102 is a column that stores identification information (MAC address) of a connected device.

[0070] FIG. 12 is a diagram illustrating an example of a data structure of the wireless connection terminal information 421 according to the first embodiment.

[0071] The wireless connection terminal information 421 stores an entry including the connection terminal C 1201. The connection terminal C 1201 is a column for storing identification information (MAC address) of the terminal 130 connected to the wireless LAN access point 120.

[0072] In this embodiment, even if the authentication of the terminal 130 has failed, an entry of the terminal 130 is registered in the wireless connection terminal information 421. If the control unit 410 has not received a packet from the terminal 130 for a certain period of time, the control unit 410 deletes the entry corresponding to the terminal 130 from the wireless connection terminal information 421. The period of time is set in advance.

[0073] FIG. 13 is a diagram illustrating an example of the data structure of the authentication information 422 according to the first embodiment.

[0074] The authentication information 422 stores an entry including the terminal C 1301. The terminal C 1301 is a column that stores the identification information of the terminal 130 that is permitted to use the in-house network 101. The identification information is, for example, a MAC address.

[0075] An administrator may set the authentication information 422 using an interface provided by the user I / F unit 411, or the wireless LAN access point 120 may obtain information from an administrative server (not shown) and set the authentication information 422.

[0076] Next, the processing executed by the network management server 100 will be described with reference to FIGS.

[0077] FIG. 14 is a flowchart illustrating an example of a monitoring information generation process executed by the network management server 100 according to the first embodiment.

[0078] The history verification unit 210 determines whether or not a start event is detected (step F101). For example, the history verification unit 210 detects the passage of an execution period or the receipt of a start command via the user I / F unit 211 as a start event.

[0079] If the start event has not been detected, the history verification unit 210 ends the monitoring information generation process.

[0080] When a start event is detected, the collection unit 230 of the history verification unit 210 acquires FDB information from the network device using a protocol such as SNMP, and generates the connection monitoring information 220 (step F102).

[0081] Specifically, the collection unit 230 acquires FDB information 320 from the L2 switch 110, and acquires FDB information 420 from the wireless LAN access point 120. The collection unit 230 generates connection monitoring information 220 based on the acquired FDB information 320 and FDB information 420. Identification information of the network device from which the FDB information was acquired is set in network device C501, the value of port C1001 or port C1101 is set in port C502, and the value of connected device C1002 or connected device C1102 is set in connected device C503. In the case of the network connection as shown in Fig. 1, connection monitoring information 220 as shown in Fig. 5 is generated.

[0082] The network device from which the FDB information is to be obtained may be specified in advance using a table (not shown).

[0083] Next, the collection unit 230 of the history verification unit 210 acquires the wireless connection terminal information 421 from the wireless LAN access point 120 using a protocol such as SNMP, and generates the wireless connection monitoring information 221 (step F103). After that, the history verification unit 210 ends the monitoring information generation process.

[0084] The identification information of the wireless LAN access point 120 that acquired the wireless connection terminal information 421 is set in the wireless LAN access point C601, and the value of the connection terminal C1201 is set in the connection terminal C602. In the case of the network connection as shown in Fig. 1, the wireless connection monitoring information 221 as shown in Fig. 6 is generated.

[0085] The wireless LAN access point 120 from which the wireless connection terminal information 421 is obtained may be specified in advance using a table (not shown).

[0086] FIG. 15 is a flowchart illustrating an example of a history information generating process executed by the network management server 100 according to the first embodiment.

[0087] The history verification unit 210 determines whether or not a start event is detected (step F201). For example, the history verification unit 210 detects the passage of an execution period or the reception of a start command via the user I / F unit 211 as a start event.

[0088] If the start event is not detected, the history verification unit 210 ends the history information generation process.

[0089] When a start event is detected, the history generation unit 231 of the history verification unit 210 executes information generation processing (step F202) and also executes information update processing (step F203). After that, the history verification unit 210 ends the history information generation processing.

[0090] In the information generation process, information on the terminal 130 connected to the L2 switch 110 and the wireless LAN access point 120 is extracted based on the connection monitoring information 220, and the information is added to the connection history information 223. In the information update process, the connection state of the terminal whose connection has been detected is confirmed, and the connection history information 223 is updated according to the connection state.

[0091] FIG. 16 is a flowchart illustrating an example of the information generation process executed by the network management server 100 according to the first embodiment.

[0092] The history generating unit 231 starts loop processing of the connection monitoring information 220 (step F301).

[0093] Specifically, the history generating unit 231 selects one entry from the connection monitoring information 220. In the following description, the selected entry is referred to as a "processing target entry," and the terminal 130 corresponding to the processing target entry is referred to as a "processing target terminal 130."

[0094] The history generating unit 231 determines whether or not an entry corresponding to the target terminal 130 has already been registered in the connection history information 223 (step F302).

[0095] Specifically, the history generating unit 231 searches for an entry in which the identification information of the processing target terminal 130 is stored in the connection terminal C 806 and the end date and time C 802 is blank. If the terminal exists, it is determined that the entry has been registered in the connection history information 223.

[0096] If an entry corresponding to the processing target terminal 130 has already been registered in the connection history information 223, the history generation unit 231 proceeds to step F308.

[0097] If an entry corresponding to the processing target terminal 130 is not registered in the connection history information 223, the history generating unit 231 registers an entry for the processing target terminal 130 in the connection history information 223 (step F303). This means that the terminal in question is a terminal whose connection has been newly confirmed.

[0098] Specifically, the history generation unit 231 adds an entry to the connection history information 223, and sets the current date and time to the start date and time C801 of the added entry. The history generation unit 231 sets the values ​​of the network device C501, port C502, and connected device C503 of the processing target entry to the network device C803, port C804, and connected terminal C806 of the added entry. At this point, the end date and time C802, wireless LAN access point C805, and user C807 of the added entry are blank.

[0099] Next, the history generating unit 231 determines whether the processing target terminal 130 is performing wireless communication (step F304).

[0100] Specifically, the history generating unit 231 refers to the wireless connection monitoring information 221 and searches for an entry in which the identification information of the processing target terminal 130 is set to the connecting terminal C 602. If the entry exists, it is determined that the processing target terminal 130 is performing wireless communication.

[0101] If the target terminal 130 is not performing wireless communication, the history generating unit 231 proceeds to step F306.

[0102] If the processing target terminal 130 is performing wireless communication, the history generating unit 231 sets information about the wireless LAN access point 120 in the added entry (step F305).

[0103] Specifically, the history generating unit 231 sets the value of the wireless LAN access point C601 of the entry found in step F304 to the wireless LAN access point C805 of the added entry.

[0104] In step F306, the history generating section 231 determines whether the target terminal 130 is a registered terminal (step F306).

[0105] Specifically, the history generation unit 231 refers to the registered terminal information 222 and searches for an entry in which the identification information of the processing target terminal 130 is set in the terminal C 701. If the entry exists, it is determined that the processing target terminal 130 is a registered terminal.

[0106] If the processing target terminal 130 is not a registered terminal, the history generating section 231 proceeds to step F308.

[0107] If the processing target terminal 130 is a registering terminal, the history generation unit 231 sets the identification information of the registering terminal in the added entry (step F307).Then, the history generation unit 231 proceeds to step F308.

[0108] Specifically, the history generating unit 231 sets the value of the user C 702 of the entry found in step F306 to the user C 807 of the added entry.

[0109] In step F308, the history generation section 231 determines whether or not the processing has been completed for all the entries in the connection monitoring information 220 (step F308).

[0110] If the processing has not been completed for all the entries in the connection monitoring information 220, the history generating unit 231 returns to step F301 and executes the same processing.

[0111] When the processing has been completed for all entries in the connection monitoring information 220, the history generating unit 231 ends the information generating processing.

[0112] FIG. 17 is a flowchart illustrating an example of the information update process executed by the network management server 100 according to the first embodiment.

[0113] The history generating unit 231 references the connection history information 223 and generates a list of entries to be updated (step F401).

[0114] Specifically, the history generation unit 231 searches for entries in which the end date and time C802 is blank, and generates a list of those entries.

[0115] The history generating unit 231 starts loop processing of the list (step F402).

[0116] Specifically, the history generating unit 231 selects one entry from the list. In the following description, the selected entry is referred to as a processing target entry.

[0117] The history generating unit 231 determines, based on the connection monitoring information 220, whether or not the connection of the terminal 130 corresponding to the processing target entry has been terminated (step F403).

[0118] Specifically, the history generation unit 231 refers to the connection monitoring information 220 and searches for an entry in which the combination of values ​​of network device C501, port C502, and connected device C503 matches the combination of values ​​of network device C803, port C804, and connected terminal C806 of the processing target entry. If the above-mentioned entry does not exist, the history generation unit 231 determines that the connection of the terminal 130 corresponding to the processing target entry has ended. A terminal 130 for which no entry exists in the connection monitoring information 220 means that it has been disconnected from the intranet 101.

[0119] If the connection of the terminal 130 corresponding to the entry to be processed has not been terminated, the history generation section 231 proceeds to step F405.

[0120] If the connection of the terminal 130 corresponding to the target entry has ended, the history generation unit 231 sets the current date and time to the end date and time C902 of the entry corresponding to the target entry in the connection history information 223 (step F404). After that, the history generation unit 231 proceeds to step F405.

[0121] In step F405, the history generation unit 231 determines whether or not the processing has been completed for all entries registered in the list (step F405).

[0122] If the processing has not been completed for all entries registered in the list, the history generation unit 231 returns to step F402 and executes the same processing.

[0123] When the processing has been completed for all entries registered in the list, the history generating unit 231 ends the information update processing.

[0124] The connection history information 223 shown in Figure 8A indicates that terminal 130-1 (U10) and terminal 130-2 (U20) connected to wireless LAN access point 120-1 (S20) at time 1, terminal 130-3 (U30) connected to wireless LAN access point 120-1 (S20) at time 3, and terminal 130-4 (U40) connected to L2 switch 110 (S10) at time 5.

[0125] The connection history information 223 shown in Fig. 8B is information generated after the connection history information 223 shown in Fig. 8A is generated. Terminal 130-1 (U10) and terminal 130-2 (U20) disconnected from wireless LAN access point 120-1 (S20) at time 2, and terminal 130-3 (U30) disconnected from wireless LAN access point 120-1 (S20) at time 4. It is also shown that terminal 130-1 (U10) and terminal 130-2 (U20) are connected to wireless LAN access point 120-2 (U21) at time 6.

[0126] In this manner, the history generating unit 231 accumulates information about the connection state of the terminal 130 in the intranet 101 in the connection history information 223 .

[0127] Next, a process for presenting mobile terminal analysis information 224 using connection history information 223 will be described.

[0128] Fig. 18 is a diagram showing an example of a search screen presented by the network management server 100 of the embodiment 1. Fig. 19 is a flowchart explaining an example of a mobile terminal analysis information generation process executed by the network management server 100 of the embodiment 1. Fig. 20 is a diagram showing an example of a processing result screen presented by the network management server 100 of the embodiment 1.

[0129] In response to a user request, the network management server 100 displays an input screen 1800 as shown in Fig. 18. For example, the user I / F unit 211 displays the input screen 1800 on an output device such as a display of the network management server 100 or a terminal operated by the user.

[0130] The input screen 1800 includes a terminal information input field 1801, a search period input field 1802, and an execute button 1803. The terminal information input field 1801 is a field for inputting identification information (MAC address) of the unregistered terminal 130. The search period input field 1802 is a field for inputting a search period. A search start date and time and a search end date and time are input into the search period input field 1802. The search period input field 1802 may be left blank. The execute button 1803 is an operation button for instructing the execution of a mobile terminal analysis information generation process.

[0131] Note that the input screen 1800 is merely an example and is not limited to the one shown in Fig. 18. For example, a field for designating a network device, a port, etc. may be provided.

[0132] When the execute button 1803 is operated, the mobile terminal analysis information generation process described below is executed.

[0133] The analysis unit 232 initializes (step F501) the mobile terminal analysis information 224. Here, initialization means that the mobile terminal analysis information 224 is put into a state in which no entries exist.

[0134] The analysis unit 232 starts a loop process of the connection history information 223 (step F502).

[0135] Specifically, the analysis unit 232 selects one entry from the connection history information 223. In the following description, the selected entry is referred to as a processing target entry. Note that the analysis unit 232 may extract only entries whose start date and time C801 is within the search period from the connection history information 223, and execute the loop process.

[0136] The analysis unit 232 determines whether or not the terminal 130 corresponding to the processing target entry is a search target terminal (step F503).

[0137] Specifically, the analysis unit 232 determines whether the value of the connected terminal C806 of the entry to be processed matches the value of the terminal information input field 1801, and whether the value of the start date and time C801 of the entry to be processed is included in the search range specified in the search period input field 1802. If the above-mentioned conditions are met, it is determined that the terminal 130 corresponding to the entry to be processed is the terminal to be searched.

[0138] If the terminal 130 corresponding to the processing target entry is not the terminal to be searched for, the analysis section 232 proceeds to step F506.

[0139] If the terminal 130 corresponding to the processing target entry is the search target terminal, the analysis unit 232 refers to the connection history information 223 and searches for a terminal 130 having the same connection state as that of the relevant terminal 130 (step F504).

[0140] Specifically, the analysis unit 232 searches for an entry whose combination of start date and time C801 and end date and time C802 values ​​matches the combination of start date and time C801 and end date and time C802 values ​​of the target entry. The dates and times do not have to match completely. For example, if the error is within a certain time (for example, within 3 minutes), they may be treated as the same date and time.

[0141] The analysis unit 232 updates the mobile terminal analysis information 224 based on the processing target entry and the searched entry (step F505). After that, the analysis unit 232 proceeds to step F506.

[0142] Specifically, the analysis unit 232 adds an entry corresponding to the processing target entry and also adds an entry corresponding to the searched entry to the mobile terminal analysis information 224. In step F504, if multiple entries are searched for, multiple entries are added to the mobile terminal analysis information 224.

[0143] In step F506, the analysis unit 232 determines whether or not the processing has been completed for all entries in the connection history information 223 (step F506).

[0144] If the processing has not been completed for all the entries in the connection history information 223, the analysis unit 232 returns to step F502 and executes the same processing.

[0145] When the processing has been completed for all entries of the connection history information 223, the analysis unit 232 presents the mobile terminal analysis information 224 (step F507), and then ends the mobile terminal analysis information generation processing.

[0146] The analysis unit 232 presents, for example, a processing result screen 2000 as shown in Fig. 20. The processing result screen 2000 displays mobile terminal analysis information 224 having the same content as that of Fig. 9. When the terminal 130-2 (U20) is an unregistered terminal and the connection history information 223 is as shown in Fig. 8B, the mobile terminal analysis information 224 shown in Fig. 9 is generated.

[0147] By referring to the processing result screen 2000, the administrator can understand that the unregistered terminal 130-2 (U20) is moving together with the registered terminal 130-1 (U10). Therefore, the administrator can infer that the user using the registered terminal 130-1 (U10) or another user acting together with the user is using the unregistered terminal 130-2 (U20). This enables the administrator to take the necessary measures.

[0148] If the network management server 100 holds location information for managing the physical locations of network devices such as the L2 switch 110 and the wireless LAN access point 120, the information can be used to narrow down the search in more detail. For example, after the process of step F504, the analysis unit 232 refers to the location information based on the values ​​of network device C803 of the target entry and the searched entry, and determines whether the physical locations are the same or close to each other. The analysis unit 232 registers in the mobile terminal analysis information 224 only those entries whose physical locations are the same or close to each other.

[0149] It should be noted that similar information can be generated not only for terminal 130 that performs wireless communication, but also for terminals such as portable notebook computers that perform wired communication.

[0150] As described above, according to the first embodiment, when an unregistered terminal that is not permitted to use the in-house network is connected, the network management server 100 can present information on a registered terminal that is in the same connection state as the unregistered terminal. This allows the administrator to estimate the user of the unregistered terminal. EXAMPLES

[0151] In the second embodiment, the communication protocol of the wireless LAN is different from that in the first embodiment. The following describes the second embodiment, focusing on the differences from the first embodiment.

[0152] FIG. 21 is a diagram illustrating an example of a network configuration according to the example of the network system of the second embodiment.

[0153] The network system of the second embodiment differs from the network system of the first embodiment in that a wireless LAN controller 140 is connected to a port 111-4 of an L2 switch 110. Other configurations are the same as those of the first embodiment. In the following description, identification information such as a MAC address of the wireless LAN controller 140 is designated as S50.

[0154] The wireless LAN controller 140 is a network device designed to centrally manage the settings of wireless LAN access points 120 present in the in-house network 101 and the traffic of terminals 130 that perform wireless communication, and is used in large-scale networks having a large number of wireless LAN access points 120.

[0155] The wireless LAN controller 140 performs necessary settings on the wireless LAN access points 120 present in the internal network 101 so that the wireless LAN access points 120 operate under the management of the wireless LAN controller 140. Packets of the terminals 130 connected to the wireless LAN access points 120 are transmitted and received via the wireless LAN controller 140. This is to enable the wireless LAN controller 140 to centrally monitor the amount of communication data of each terminal 130 and manage traffic control and the like.

[0156] When the wireless LAN access point 120 receives a packet from the terminal 130, it performs encapsulation to store the packet of the terminal 130 in the payload portion of a UDP (User Datagram Protocol) packet, for example, and transmits the encapsulated packet to the wireless LAN controller 140. When the wireless LAN controller 140 receives the encapsulated packet, it extracts (decapsulates) the packet of the terminal 130 from the encapsulated packet and transfers the packet of the terminal 130 to its final destination. From the perspective of the L2 switch 110, all packets of the terminal 130 performing wireless communication are recognized as being transmitted to the wireless LAN controller 140.

[0157] The communication protocol between the wireless LAN controller 140 and the wireless LAN access point 120 described above is, for example, a known technology called CAPWAP (Control And Provisioning of Wireless Access Points).

[0158] The configurations of the network management server 100, the L2 switch 110, and the wireless LAN access point 120 in the second embodiment are the same as those in the first embodiment, and therefore a description thereof will be omitted.

[0159] FIG. 22 is a diagram illustrating an example of the configuration of a wireless LAN controller 140 according to the second embodiment.

[0160] The wireless LAN controller 140 includes a CPU 2201, a network I / F 2202, and a memory 2203. The CPU 2201, the network I / F 2202, and the memory 2203 are similar hardware to the CPU 201, the network I / F 202, and the memory 203.

[0161] The memory 2203 stores programs that realize the control unit 2210 and the user I / F unit 2211. The memory 2203 also stores FDB information 2220, wireless connection terminal information 2221, wireless LAN access point information 2222, and authentication information 2223.

[0162] The wireless LAN controller 140 aggregates and transmits / receives packets of the terminals 130 connected to the wireless LAN access points 120, and therefore operates like the L2 switch 110 with respect to packets of each terminal 130. Therefore, the wireless LAN controller 140 holds FDB information 2220 for managing the connection destinations of the terminals 130. Details of the data structure of the FDB information 2220 will be described with reference to FIG. 23. The wireless connection terminal information 2221 is the same information as the wireless connection terminal information 421, but the data structure is partially different. Details of the data structure of the wireless connection terminal information 2221 will be described with reference to FIG. 24. The wireless LAN access point information 2222 is information for managing the wireless LAN access points 120 to be monitored. Details of the data structure of the wireless LAN access point information 2222 will be described with reference to FIG. 25. The authentication information 2223 is the same information as the authentication information 422.

[0163] The control unit 2210 performs various settings for the wireless LAN access point 120 to be managed, encapsulation and decapsulation of packets of the terminal 130, and overall control of the wireless LAN controller 140. Furthermore, the control unit 2210 executes authentication processing on behalf of the wireless LAN access point 120 using authentication information 2223.

[0164] The user I / F unit 2211 provides a user interface for configuring the operation of the wireless LAN controller 140 and checking the operation status.

[0165] FIG. 23 is a diagram showing an example of the data structure of the FDB information 2220 according to the second embodiment.

[0166] The FDB information 2220 stores an entry including a port C2301 and a connected device C2302. The port C2301 and the connected device C2302 are in the same column as the port C1101 and the connected device C1102. However, the port C2301 stores information about a tunnel addressed to the wireless LAN access point 120-1 (S20). This means that the terminal 130-1 (U10), the terminal 130-2 (U20), and the terminal 130-3 (U30) are connected to the other end of the tunnel. The terminals 130-1, 130-2, and 130-3 are not directly connected to the physical port of the wireless LAN controller 140, but are connected via a logical network interface called a tunnel.

[0167] FIG. 24 is a diagram illustrating an example of a data structure of the wireless connection terminal information 2221 according to the second embodiment.

[0168] The wireless connection terminal information 2221 stores entries including a wireless LAN access point C2401 and a connected terminal C2402. The connected terminal C2402 is in the same column as the connected terminal C1201. The wireless LAN access point C2401 is a column that stores identification information of the wireless LAN access point 120 to which the terminal 130 is connected.

[0169] The wireless LAN controller 140 centrally manages the terminals 130 that perform wireless communication, and therefore manages the wireless LAN access point 120 and the terminals 130 in association with each other. Wireless connection terminal information 2221 shown in Fig. 24 indicates that a terminal 130-1 (U10), a terminal 130-2 (U20), and a terminal 130-3 (U30) are connected to the wireless LAN access point 120-1 (S20).

[0170] FIG. 25 is a diagram illustrating an example of a data structure of the wireless LAN access point information 2222 according to the second embodiment.

[0171] The wireless LAN access point information 2222 stores entries including the wireless LAN access point C 2501. The wireless LAN access point C 2501 is a column for storing the identification information (MAC address) of the wireless LAN access point 120 to be managed.

[0172] An administrator may manually set the wireless LAN access point information 2222. Alternatively, the wireless LAN controller 140 may search for the wireless LAN access point 120 using a method defined in a publicly known technology such as CAPWAP, and generate the wireless LAN access point information 2222 based on the search result.

[0173] Next, the process of the second embodiment will be described.

[0174] In the second embodiment, the wireless LAN controller 140 executes the authentication process. Therefore, in the monitoring information generation process, the information acquisition source differs from that in the first embodiment.

[0175] In step F102, the collection unit 230 acquires the FDB information 320 from the L2 switch 110, and acquires the FDB information 2220 from the wireless LAN controller 140. The data structure of the FDB information 2220 is the same as that of the FDB information 420, and the acquisition method is also the same.

[0176] It should be noted that, like the wireless LAN access point 120, the wireless LAN controller 140 is also capable of reading out internal information from an external device using a protocol such as SNMP. It should be noted that the wireless LAN controller 140 from which information is to be collected is set in advance in the network management server 100.

[0177] In step F103, the collection unit 230 acquires wireless connection terminal information 2221 from the wireless LAN controller 140. Since the wireless connection terminal information 2221 manages the terminal 130 and the wireless LAN access point 120 as a pair, the collection unit 230 reads out the contents of the wireless connection terminal information 2221 using a protocol such as SNMP, and stores the contents in the wireless connection monitoring information 221.

[0178] By the above-mentioned processing, various information required for generating analysis information on the unregistered terminal 130 in the intranet 101 including the wireless LAN controller 140 can be acquired.

[0179] The processes other than the monitoring information generation process are the same as those in the first embodiment.

[0180] According to the second embodiment, when an unregistered terminal that is not permitted to use the in-house network is connected, the network management server 100 can present information on a registered terminal that is in the same connection state as the unregistered terminal. This allows the administrator to estimate the user of the unregistered terminal.

[0181] Representative aspects of the invention other than those described in the claims are as follows: (1) A computer connected to a network including a plurality of network devices accommodating terminals, A computer-readable storage device (CSP) connected to the computer and a network interface (NIC) connected to the computer, acquiring information about the terminals connected to the network from the plurality of network devices, and generating connection history information for grasping a connection state of the terminals in the network; Identifying a connection history of a target terminal whose management identification information of the network is unknown based on the connection history information; referring to the connection history information, identifying a connection history of a reference terminal to which the management identification information is assigned and which has connected and disconnected at the same time as the target terminal; A computer that presents analysis information including connection histories of the target terminal and the reference terminal. (2) The computer according to (1), storing location information for managing locations of the plurality of network devices; The connection history includes identification information of the network device to be connected, The computer includes: Identifying the reference terminal that is connected to the network device that is located at the same location as or near the location of the network to which the target terminal is connected, based on the connection history of the target terminal, the connection history of the reference terminal, and the location information; A computer that presents the analysis information including a connection history of the identified reference terminal. (3) The computer according to (1), the plurality of network devices includes at least one network device that functions as an access point for wireless communication; The computer includes: acquiring a forwarding database for controlling packet forwarding from the plurality of network devices; A computer that acquires wireless communication terminal information regarding the terminal connected to the network device that functions as an access point for the wireless communication.

[0182] Although the present invention has been described in detail above with reference to the accompanying drawings, the present invention is not limited to such specific configurations, and includes various modifications and equivalent configurations within the spirit of the appended claims.

[0183] For example, a non-transient storage medium on which a software program for implementing the functions of the embodiment is recorded may be provided to a computer. A CPU included in the computer reads and executes the program stored in the non-transient storage medium. In this case, the program itself and the non-transient storage medium on which it is stored constitute the present invention. Examples of storage media on which the program is recorded include hard disks, SSDs (Solid State Drives), optical disks, magnetic tapes, non-volatile memory cards, and the like. [Explanation of symbols]

[0184] 100 Network Management Server 101 Internal Network 102 Network 110 L2 Switch 111 Port 120 Wireless LAN Access Point Port 121 130 terminals 140 Wireless LAN Controller 201, 301, 401, 2201 CPUs 202, 302, 402, 2202 Network I / F 203, 303, 403, 2203 Memory 210 History Verification Department 211, 311, 411, 2211 User I / F section 220 Connection monitoring information 221 Wireless connection monitoring information 222 Registered terminal information 223 Connection history information 224 Mobile terminal analysis information 230 Collection Department 231 History Generation Unit 232 Analysis Department 304, 404 packet repeater 310, 410, 2210 Control unit 320, 420, 2220 FDB information 421, 2221 Wireless connection terminal information 422, 2223 Credentials 1800 Input screen 1801 Terminal information input field 1802 Search period input field 1803 Run button 2000 Processing result screen 2222 Wireless LAN access point information

Claims

1. A computer system connected to a network including a plurality of network devices accommodating terminals, comprising: At least one computer having a CPU, a storage device connected to the CPU, and a network interface connected to the CPU; The at least one computer acquiring information about the terminals connected to the network from the plurality of network devices, and generating connection history information for grasping a connection state of the terminals in the network; Identifying a connection history of a target terminal whose management identification information of the network is unknown based on the connection history information; referring to the connection history information, identifying a connection history of a reference terminal to which the management identification information is assigned and which has connected and disconnected at the same time as the target terminal; A computer system that presents analysis information including connection histories of the target terminal and the reference terminal.

2. 2. The computer system of claim 1, storing location information for managing locations of the plurality of network devices; The connection history includes identification information of the network device to be connected, The at least one computer Identifying the reference terminal that is connected to the network device that is located at the same location as or near the location of the network to which the target terminal is connected, based on the connection history of the target terminal, the connection history of the reference terminal, and the location information; A computer system that presents the analysis information, including a connection history of the identified reference terminal.

3. 2. The computer system of claim 1, the plurality of network devices includes at least one network device that functions as an access point for wireless communication; The at least one computer acquiring a forwarding database for controlling packet forwarding from the plurality of network devices; A computer system comprising: a network device that functions as an access point for wireless communication; and a wireless communication terminal information device that acquires wireless communication terminal information relating to the terminal connected thereto.

4. A network analysis method executed by a computer system connected to a network including a plurality of network devices accommodating terminals, comprising: the computer system includes at least one computer having a CPU, a storage device connected to the CPU, and a network interface connected to the CPU; The network analysis method includes: a first step in which the at least one computer acquires information on the terminal connected from the plurality of network devices and generates connection history information for grasping a connection state of the terminal in the network; a second step of identifying a connection history of a target terminal whose management identification information of the network is unknown based on the connection history information by the at least one computer; a third step in which the at least one computer refers to the connection history information to identify a connection history of a reference terminal to which the management identification information is assigned and which connects and disconnects at the same time as the target terminal; a fourth step in which the at least one computer presents analysis information including connection histories of the target terminal and the reference terminal; A network analysis method comprising:

5. 5. A network analysis method according to claim 4, comprising: the computer system holds location information for managing locations of the plurality of network devices; The connection history includes identification information of the network device to be connected, the third step includes a step of identifying the reference terminal connected to the network device located at a position equal to or adjacent to a position where the network to which the target terminal is connected is located, based on the connection history of the target terminal, the connection history of the reference terminal, and the location information, by the at least one computer; The network analysis method, wherein the fourth step includes a step in which the at least one computer presents the analysis information including a connection history of the identified reference terminal.

6. 5. A network analysis method according to claim 4, comprising: the plurality of network devices includes at least one network device that functions as an access point for wireless communication; The first step includes: acquiring, by the at least one computer, a forwarding database for controlling packet forwarding from the plurality of network devices; and a step in which the at least one computer acquires wireless communication terminal information regarding the connected terminal from the network device that functions as an access point for the wireless communication.

7. A program executed by a computer connected to a network including a plurality of network devices accommodating terminals, the computer includes a CPU, a storage device connected to the CPU, and a network interface connected to the CPU; The program is a first step of acquiring information about the terminals connected to the network from the plurality of network devices and generating connection history information for grasping a connection state of the terminals in the network; A second step of identifying a connection history of a target terminal whose management identification information of the network is unknown based on the connection history information; a third step of referring to the connection history information to identify a connection history of a reference terminal to which the management identification information is assigned and which has connected and disconnected at the same time as the target terminal; A fourth step of presenting analysis information including connection histories of the target terminal and the reference terminal; A program for causing the computer to execute the above.

8. The program according to claim 7, the computer holds location information for managing locations of the plurality of network devices; The connection history includes identification information of the network device to be connected, the third step includes a step of identifying the reference terminal connected to the network device located at the same location as or near the location of the network to which the target terminal is connected, based on the connection history of the target terminal, the connection history of the reference terminal, and the location information; The program, wherein the fourth step includes a step of presenting the analysis information, the analysis information including a connection history of the identified reference terminal.

9. The program according to claim 7, the plurality of network devices includes at least one network device that functions as an access point for wireless communication; The first step includes: A step of acquiring a forwarding database for controlling packet forwarding from the plurality of network devices; and a procedure for acquiring wireless communication terminal information regarding the terminal connected to the network device that functions as an access point for the wireless communication.

Citation Information

Patent Citations

  • Terminal for monitoring and network monitor system

    JP2005142800A

  • Equipment data management system

    JP2009048251A

  • Authentication system

    JP2016143396A

  • Determination device, determination method, and determination program

    JP2021149451A