Monitoring control device, monitoring control method, and program
The monitoring control device optimizes alive monitoring by calculating IP address allocation rates and adjusting monitoring request amounts to manage processing loads, addressing limitations in conventional systems and ensuring effective monitoring despite varying user device states.
Patent Information
- Application Number
- PCT/JP2024/030158
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-08-26
- Publication Date
- 2026-03-05
AI Technical Summary
Conventional alive-or-dead monitoring systems face challenges due to limited processing capabilities of monitoring devices, leading to difficulties in sending measurement packets at predetermined intervals when user equipment is in a stopped state, which affects the effectiveness of monitoring.
A monitoring control device that calculates an allocation rate of IP addresses and determines a monitoring request amount based on the number of user devices and a predetermined monitoring interval, adjusting the number of measurement packets sent to each user equipment to optimize processing load and capacity.
The solution enables appropriate alive monitoring by reducing processing load on the monitoring device and ensuring it can handle changes in user device attachment rates, effectively managing monitoring demands within the device's processing capabilities.
Smart Images

Figure JP2024030158_05032026_PF_FP_ABST
Abstract
Description
Monitoring control device, monitoring control method, and program
[0001] The present disclosure relates to control of alive monitoring for checking the operating status of user equipment.
[0002] In computer networks, health monitoring is performed at various layers to check whether the target device is operating or not in order to confirm communication continuity or the operating status of user devices (Non-Patent Document 1).
[0003] Here, conventional alive-or-dead monitoring will be explained with reference to Fig. 12. Fig. 12 shows a conventional system for performing alive-or-dead monitoring, with Fig. 12(a) showing an active system and Fig. 12(b) showing a passive system.
[0004] As shown in Figure 12(a), the active method will be described in a situation where a closed network 1100 includes user equipment (UE) 1111 and 1112 such as smartphones, a network device 1120 with gateway functionality, and a server 1140. For example, the user equipment 1112 is performing data communication with the server 1140 via the network device 1120. Under such circumstances, the monitoring device 160 periodically transmits measurement packets (ping, etc.) for monitoring to the user equipment 1112 via the network device 1120, and receives responses (ack, etc.) to the packets, thereby determining that the user equipment 1112 is in operation.
[0005] 12(b), the passive method will be described in a situation where a closed network 1200 includes user equipment (UE) 1211 and 1212 such as smartphones, a network device 1220, and a server 1240. For example, the network device 1220 relays data communication between the user equipment 1212 and the server 1240, and always confirms that the user equipment 1212 is operating during relaying.
[0006] "Forest of Knowledge" by the Institute of Electronics, Information and Communication Engineers, Vol. 5, No. 9, Chapter 3, "Common Functions of Network Management" (Access, Nov. 2023.)<https: / / www.ieice-hbkb.org / files / ad_base / view_pdf.html?p= / files / 05 / 05gun_09hen_03.pdf>
[0007] However, since the processing capabilities of the monitoring device (CPU performance, memory capacity, etc.) are limited, if the monitoring device uses its processing capabilities to send measurement packets to user equipment that is in a stopped state and does not receive a response, it may become difficult to send measurement packets at the predetermined monitoring interval.
[0008] The present disclosure has been made in consideration of the above circumstances, and aims to provide control so that a monitoring device performs appropriate alive monitoring.
[0009] In order to achieve the above-mentioned object, the present disclosure provides a monitoring control device that controls alive monitoring to check the operating status of user equipment, and that has: a communication unit that receives the IP address of an authenticated user equipment from an authentication device that assigns an IP address to each user equipment by authenticating each user equipment within a specified closed network; and a calculation unit that calculates an allocation rate of the IP address of the user equipment based on the IP address of the authenticated user equipment and the number of user equipment within the specified closed network, and calculates a monitoring request amount that indicates the number of times per unit time that measurement packets for alive monitoring should be sent to a specified user equipment among the user equipment based on the allocation rate, the number, and a predetermined monitoring interval.
[0010] As described above, the present disclosure provides the effect of enabling control so that a monitoring device performs appropriate alive monitoring.
[0011] FIG. 1 is an overall configuration diagram of a communication system according to a first embodiment. FIG. 2 is an electrical hardware configuration diagram of each device in the communication system. FIG. 3 is a functional configuration diagram of a monitoring control device. FIG. 4 is a sequence diagram showing the processing of the communication system according to the first embodiment. FIG. 5 is a flowchart showing the calculation processing of the monitoring request amount according to the first embodiment. FIG. 6 is a conceptual diagram showing specific processing of alive-or-dead monitoring by a monitoring device. FIG. 7 is an overall configuration diagram of a communication system according to a second embodiment. FIG. 8 is a sequence diagram showing the processing of the communication system according to the second embodiment. FIG. 9 is an overall configuration diagram of a communication system according to a third embodiment. FIG. 10 is a sequence diagram showing the processing of the communication system according to the third embodiment. FIG. 11 is a flowchart showing the calculation processing of the monitoring request amount according to the third embodiment. FIG. 12 is a diagram showing a conventional system that performs alive-or-dead monitoring, where (a) is an active system and (b) is a passive system.
[0012] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the present invention is not limited to the embodiments shown below, and various modifications are possible within the scope of the technical concept of the present invention. Since the drawings are intended to conceptually explain the present invention, dimensions, ratios, or numbers may be exaggerated or simplified as necessary to facilitate understanding.
[0013] First Embodiment [System Configuration of the Embodiment] First, the overall configuration of a communication system 10a according to the first embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing the overall configuration of the communication system according to the first embodiment.
[0014] As shown in Fig. 1, a communication system 10a of this embodiment is constructed by a monitoring control device 50a, a monitoring device 60, each device (equipment) in a closed network (closed network) 100, each device (equipment) in a closed network 200, an authentication device 140, and an authentication device 240. Note that, due to limitations of the drawing, two closed networks 100 and 200 are shown as multiple closed networks in Fig. 1, but three or more closed networks may be constructed.
[0015] The closed network 100 is, for example, a closed mobile network, and includes multiple user equipment (UE) 111, 112, a network device 120a, and a server 130. Note that, in Fig. 1, due to limitations of the drawing, two user equipment 111, 112 are shown as the multiple user equipment, but three or more user equipment may be included. Note that the closed network 100 may be a network other than a mobile network.
[0016] The user devices 111 and 112 in the closed network 100 are smartphones, mobile phones, tablet terminals, node PCs (Personal Computers), desktop PCs, car navigation devices, network home appliances, and the like.
[0017] The network device 120a is a communication device with a gateway function. The network device 120a relays data communication between the user devices 111 and 112 and the server 130 or the authentication device 140, and in some cases relays data communication between the user devices 111 and 112 and the wide area network 99.
[0018] The server 130 is a computer that provides services to the user devices 111 and 112 .
[0019] The authentication device 140 authenticates each of the user devices 111, 112 and assigns an IP address to each of the user devices 111, 112, thereby attaching each of the user devices 111, 112 within the closed network 100. The authentication device 140 also transmits a list of IP addresses of authenticated user devices within the closed network 100 to the monitoring control device 50a. Note that the list does not have to be in list format as long as the IP addresses of authenticated user devices are indicated.
[0020] Similarly to the closed network 100, the closed network 200 is, for example, a closed mobile network, and includes a plurality of user equipment (UE) 211, 212, a network device 220a, and a server 230. Note that, due to limitations of the drawing, two user equipment 211, 212 are shown as the plurality of user equipment in Fig. 1, but three or more user equipment may be included.
[0021] The user devices 211 and 212 in the closed network 200 are smartphones, mobile phones, tablet terminals, node PCs, car navigation devices, network home appliances, and the like.
[0022] The network device 220a is a communication device with a gateway function. The network device 220a relays data communication between the user devices 211 and 212 and the server 230 or the authentication device 240, and in some cases relays data communication between the user devices 211 and 212 and the wide area network 99.
[0023] The server 230 is a computer that provides services to the user devices 211 and 212 .
[0024] The authentication device 240 authenticates each of the user devices 211, 212 and assigns an IP address to each of the user devices 211, 212, thereby attaching each of the user devices 211, 212 within the closed network 200. The authentication device 240 also transmits a list of IP addresses of authenticated user devices within the closed network 200 to the monitoring and control device 50a.
[0025] The monitoring control device 50a generates control information (amount of monitoring required for each closed network, IP addresses of user equipment to be measured (monitored)) based on the list of IP addresses of authenticated user equipment (UE) received from the authentication devices 140 and 240 for each closed network, and transmits this control information to the monitoring device 60. The monitoring control device 50a will be described in detail later.
[0026] Based on the control information received from the monitoring control device 50a, the monitoring device 60 transmits a measurement packet (ping, etc.) at a predetermined timing to a predetermined user device among the user devices 111 and 112 in the closed network 100 and the user devices 211 and 212 in the closed network 200. The monitoring device 60 then receives responses to the measurement packet from the user devices that are in operation. This allows the monitoring device 60 to monitor the alive status of each user device.
[0027] [Hardware Configuration] Next, the electrical hardware configuration of the monitoring and control device 50a will be described with reference to Fig. 2. Fig. 2 is an electrical hardware configuration diagram of each device in the communication system.
[0028] As shown in Figure 2, the monitoring control device 50a has a drive device 1000, an auxiliary storage device 1002, a memory device 1003, a processor 1004, an interface device 1005, a display device 1006, an input device 1007, an output device 1008, etc., which are all connected to each other by a bus 1010.
[0029] The program that realizes the processing on the computer is provided by a recording medium 1001, such as a CD-ROM or a memory card. When the recording medium 1001 storing the program is set in the drive device 1000, the program is installed from the recording medium 1001 to the auxiliary storage device 1002 via the drive device 1000. However, the program does not necessarily have to be installed from the recording medium 1001, but may be downloaded from another computer via the wide area network 99. The auxiliary storage device 1002 stores the installed program as well as necessary files, data, etc.
[0030] When an instruction to start a program is received, the memory device 1003 reads the program from the auxiliary storage device 1002 and stores it. The processor 1004 realizes functions related to the device in accordance with the program stored in the memory device 1003. The processor 1004 may include not only a CPU (Central Processing Unit) but also a GPU (Graphics Processing Unit).
[0031] The interface device 1005 is used as an interface for connecting to a communication network, etc. The display device 1006 displays a GUI (Graphical User Interface) etc. according to a program. The input device 1007 is composed of a keyboard, mouse, buttons, a touch panel, etc., and is used to input various operation instructions. The output device 1008 outputs the calculation results to the outside.
[0032] The monitoring device 60, each user device 111, each network device 120a, each server 130, and each authentication device 140 have the same hardware configuration as the monitoring control device 50a, so their explanation will be omitted.
[0033] [Functional Configuration of First Embodiment] Next, the functional configuration of the monitoring control device 50a will be described with reference to Fig. 3. Fig. 3 is a functional configuration diagram of the monitoring control device according to the embodiment.
[0034] 3, the monitoring and control device 50a has a communication unit 51, a calculation unit 52, and a determination unit 53. Each of these units has a function realized by an instruction from the processor 1004 in FIG. 2 based on a program. The monitoring and control device 50a also has a storage unit 59 constructed by an auxiliary storage device 1002 or a memory device 1003.
[0035] <Storage Unit> The storage unit 59 stores in advance the number N of user devices in each closed network. X , the monitoring interval (time interval) of each closed network is P X , and the upper limit M of the processing capacity (monitoring capacity) of the monitoring device 60 are stored.
[0036] <Communication Unit> The communication unit 51 performs data communication with each of the authentication devices 140 and 240 and the monitoring device 60 .
[0037] <Calculation Unit> The calculation unit 52 acquires from the communication unit 51 a list of IP addresses of authenticated user devices that the communication unit 51 has received from each authentication device 140, 240, and also reads out the number of user devices in a predetermined closed network (each closed network 100, 200) stored in the memory unit 59, and calculates an allocation rate of IP addresses for user devices based on this list and the number of user devices in the predetermined closed network (all closed networks 100, 200). Furthermore, the calculation unit 52 calculates a monitoring request amount indicating the number of times per unit time that measurement packets for alive monitoring should be transmitted to a predetermined user device among the user devices, based on the allocation rate, the number of devices, and a predetermined monitoring interval.
[0038] Furthermore, the calculation unit 52 calculates the (corrected) monitoring demand amount based on the determination result acquired from the determination unit 53. For example, when the predetermined closed network is a plurality of closed networks, the calculation unit 52 calculates the total value of the monitoring demand amounts calculated for each of the plurality of closed networks, and when the total value exceeds the upper limit value of the processing capacity for alive monitoring of user devices in the plurality of closed networks, calculates the corrected monitoring demand amount by subtracting each of the monitoring demand amounts in accordance with the proportion of each monitoring demand amount so that the total value becomes the upper limit value.
[0039] The determination unit 53 acquires the total value S of the monitoring request amounts from the calculation unit 52, and reads out the upper limit value M of the processing capacity (CPU performance, memory capacity, etc.) of the monitoring device 60 from the storage unit 59. The determination unit 53 also determines whether the total value S of the monitoring request amounts exceeds the upper limit value M of the processing capacity (monitoring capacity) of the monitoring device 60, and outputs the determination result to the calculation unit 52.
[0040] [Processing of the First Embodiment] Next, processing of the first embodiment will be described with reference to Fig. 4 and Fig. 5. Fig. 4 is a sequence diagram showing processing of the communication system according to the first embodiment.
[0041] S11: The authentication device 140 authenticates each of the user devices 111 and 112 in the closed network 100. Similarly, the authentication device 240 authenticates each of the user devices 211 and 212 in the closed network 200.
[0042] S12: If the authentication device 140 determines in process S11 that each of the user devices 111, 112 is a legitimate device to be used within the closed network 100, it transmits a list of IP addresses of the authenticated user devices to the monitoring control device 50a. As a result, the communication unit 51 of the monitoring control device 50a receives the list of IP addresses of the authenticated user devices from the authentication device 140. Similarly, if the authentication device 240 determines in process S11 that each of the user devices 211, 212 is a legitimate device to be used within the closed network 200, it transmits a list of IP addresses of the authenticated user devices to the monitoring control device 50a. As a result, the communication unit 51 of the monitoring control device 50a receives the list of IP addresses of the authenticated user devices from the authentication device 240.
[0043] S13a: The monitoring control device 50a performs a process of calculating the monitoring request amount based on the lists received in step S12. Here, the calculation process of the monitoring request amount will be explained using Fig. 5. Fig. 5 is a flowchart showing the calculation process of the monitoring request amount according to the first embodiment.
[0044] S101: The calculation unit 52 calculates the IP address of the authenticated user device in the private network 100 obtained from the communication unit 51 and the number N of the user devices in the private network 100 read from the storage unit 59. 100 Based on this, the IP address allocation rate (attachment rate) α of the user equipment is calculated using the following (Equation 1). 100 Similarly, the calculation unit 52 calculates the number N of authenticated user devices in the private network 200 obtained from the communication unit 51 and the number N of authenticated user devices in the private network 100 read from the storage unit 59. 200 Based on this, the IP address allocation rate α of the user equipment is calculated using the following (Equation 1). 200 Calculate.
[0045] α X = A X / N X ...(Formula 1) α X : IP address allocation rate A X : Number of user devices to which IP addresses are assigned N X The number of user devices in the closed network X. The calculation unit 52 can recognize the number of user devices to which IP addresses have been assigned in the closed networks 100 and 200 by the IP addresses of authenticated user devices.
[0046] S102: The calculation unit 52 calculates the allocation rate α calculated in step S101. 100 , and the number N of user devices in the private network 100 read from the storage unit 59 100 and the monitoring interval P of the private network 100 100 Based on this, the monitoring demand amount D of the closed network 100 is calculated using the following (Equation 2). 100 Similarly, the calculation unit 52 calculates the allocation rate α 200 , and the number N of user devices in the private network 200 read from the storage unit 59 200 and the monitoring interval P of the closed network 200200 Based on this, the monitoring demand amount D of the closed network 200 is calculated using the following (Equation 2). 200 Calculate.
[0047] D X = α X * N X * P X ...(Formula 2) D X : Monitoring demand amount P of closed network X X : monitoring interval S103: The calculation unit 52 calculates each monitoring request amount D X The total value S is calculated by adding up the above.
[0048] S = Σ D X ... (Equation 3) S: total value of monitoring request amounts S104: The determination unit 53 determines whether or not the total value S exceeds the upper limit value M of the processing capacity of the monitoring device 60, based on the total value S acquired from the calculation unit 52 and the upper limit value M of the processing capacity (monitoring capacity) of the monitoring device 60 read from the storage unit 59. If the total value S does not exceed the upper limit value M (NO), the determination unit 53 outputs a determination result indicating that the total value S does not exceed the upper limit value M to the calculation unit 52, and the calculation process shown in FIG. 5 ends.
[0049] S105: In the process S104, if the total value S exceeds the upper limit value M (YES), the determination unit 53 outputs a determination result indicating that the total value S exceeds the upper limit value M to the calculation unit 52. As a result, the calculation unit 52 calculates each monitoring demand amount D by using the following (Equation 4) so that the total value S becomes the upper limit value M. X Each monitored demand quantity D' after correction reduced according to the ratio of X Calculate.
[0050] D' X = D X * M / S (Equation 4) This completes the calculation process shown in FIG.
[0051] S14a: Returning to FIG. 4, the communication unit 51 of the monitoring control device 50a transmits to the monitoring device 60 the monitoring demand amount D 100,200 (or D' 100,200), and the IP address of each user device that is the measurement target in the list received in step S12.
[0052] S15: The monitoring device 60 performs alive monitoring for each user device 111, etc. In this case, the monitoring device 60 monitors the IP addresses of the user devices received in step S14a based on the monitoring request amount D 100,200 (or D' 100,200 ) and transmits a measurement packet to the user device 111, etc. at a timing based on the received signal (S15a). Then, if the user device 111, etc. is in operation, the monitoring device 60 receives a response from the user device 111, etc., and if the user device 111, etc. is stopped (not in operation), the monitoring device 60 does not receive a response from the user device 111, etc. Here, a specific example of process S15 will be described with reference to Fig. 6. Fig. 6 is a conceptual diagram showing a specific process of alive monitoring by the monitoring device.
[0053] 6 shows a state in which user devices 111 to 114 are included in the private network 100, with only the user device 113 having been assigned an IP list (attached), and user devices 211 to 215 are included in the private network 200, with only the user device 215 having not been assigned an IP list (not attached). In this case, the monitoring control device 50a calculates the monitoring demand amount D1 of the private network 100 as 1.0 and the monitoring demand amount D2 of the private network 200 as 0.5. If the total communication volume is 3 times / s, the monitoring device 60 transmits a measurement packet to the user device 113 in the private network 100 at a timing of 1 time / s of communication volume, and transmits a measurement packet to the user devices 212 and 213 in the private network 200 at a timing of 2 times / s of communication volume. Then, one second later, the monitoring device 60 transmits a measurement packet to the user device 113 in the closed network 100 at a communication rate of 1 packet per second, and transmits a measurement packet to the user devices 211 and 214 in the closed network 200 at a communication rate of 2 packets per second.
[0054] [Major Effects of the First Embodiment] As described above, according to this embodiment, the monitoring control device 50 obtains the IP addresses of user devices that have been authenticated in advance, and excludes stopped user devices from the targets of monitoring (measurement), thereby reducing the processing load on the monitoring device and enabling control to perform appropriate alive monitoring.
[0055] Furthermore, the monitoring control device 50 can allocate the monitoring demand volume to each private network in consideration of the attachment rate within the private network. Also, the monitoring demand volume for each private network can be changed in accordance with changes in the attachment rate of user devices. This provides the advantage that the monitoring control device 50a can control the monitoring device 60 to perform appropriate alive monitoring in consideration of the processing capabilities of the monitoring device 60 (CPU performance, memory capacity, etc.).
[0056] Second Embodiment Next, a second embodiment will be described with reference to FIGS.
[0057] [Functional Configuration of Second Embodiment] Figure 7 is a diagram showing the overall configuration of a communication system according to a second embodiment. The overall configuration of the second embodiment is basically the same as that of the first embodiment, and the same devices and the like are designated by reference numerals and their description will be omitted. Furthermore, since the second embodiment is similar to the first embodiment in terms of the system configuration (Figure 1), hardware configuration (Figure 2), functional configuration (Figure 3), and general processing (Figures 4 and 5), only the differences will be described below.
[0058] The second embodiment differs from the first embodiment in that a communication system 10b is shown in place of the communication system 10a of the first embodiment, and the functional configuration of the monitoring control device 50b is basically the same as the functional configuration of the monitoring control device 50a. Differences from the processing contents of each functional configuration in the first embodiment will be explained later. A monitoring control device 50b is shown in place of the monitoring control device 50a of the first embodiment. Also, a network device 120b is shown in place of the network device 120a of the first embodiment, and a network device 220b is shown in place of the network device 220a of the first embodiment.
[0059] Furthermore, compared to the network device 120a, the network device 120b has a new communication status monitoring unit 121b. Similarly, compared to the network device 220a, the network device 220b has a new communication status monitoring unit 221b. Note that the electrical hardware configurations of the monitoring and control device 50b and the network devices 120b and 220b are similar to those of the monitoring and control device 50a shown in FIG. 2, and therefore description thereof will be omitted.
[0060] The communication status monitoring units 121b and 221b are functions that are realized by instructions from the processor 1004 in FIG. 2 based on a program.
[0061] The monitoring control device 50b of the second embodiment has the functional configuration shown in FIG. 3, similar to the monitoring control device 50a of the first embodiment, but the processing is slightly different.
[0062] As a process specific to the second embodiment, for example, the communication unit 51 receives information indicating the communication status of each user device from the network devices 120b and 220b that relay data communication between the user device and other devices (e.g., the servers 130 and 230). Then, the calculation unit 52 performs a process of excluding a specific user device that is currently communicating data from the calculation of the allocation rate based on the communication status. This will be described in detail later.
[0063] <Communication Status Monitoring Unit> When relaying data communication between each of the user devices 111, 112 in the closed network 100 and the server 130, the communication status monitoring unit 121b collects the number of packets of this data communication to monitor the communication status of each of the user devices 111, 112. Similarly, when relaying data communication between each of the user devices 211, 212 in the closed network 200 and the server 230, the communication status monitoring unit 221b collects the number of packets of this data communication to monitor the communication status of each of the user devices 211, 212.
[0064] 7 shows a situation in which the user device 112 has been assigned an IP address (attached) through authentication and is in communication with the server 130. Also, FIG. 7 shows a situation in which the user device 212 is stopped (not in operation).
[0065] [Processing of Second Embodiment] Next, processing of the second embodiment will be described with reference to Fig. 8. Fig. 8 is a sequence diagram showing processing of the communication system according to the second embodiment.
[0066] S10: When relaying data communication between each of the user devices 111, 112 in the closed network 100 and the server 130, the communication status monitoring unit 121b of the network device 120b monitors the communication status of each of the user devices 111, 112, and the network device 120b transmits information indicating the communication status of each of the user devices 111, 112 in the closed network 100 to the monitoring control device 50b. In this case, the communication status information includes information indicating that the user device 111 is not communicating with the server 130, but that the user device 112 is communicating with the server 130. As a result, the communication unit 51 receives information indicating the communication status of each of the user devices 111, 112.
[0067] Similarly, when the communication status monitoring unit 221b of the network device 220b relays data communication between each of the user devices 211, 212 in the closed network 200 and the server 230, it monitors the communication status of each of the user devices 211, 212, and the network device 220b transmits information indicating the communication status of each of the user devices 211, 212 in the closed network 200 to the monitoring control device 50b. In this case, the communication status information includes information indicating that the user devices 211, 212 are not communicating with the server 230. Note that the user device 212 is in a stopped state to begin with, and is not even operating. As a result, the communication unit 51 receives information indicating the communication status of each of the user devices 211, 212.
[0068] The process from S11 onwards is basically the same as that of the first embodiment. Note that the process S13b is basically the same as the process S13a (see FIG. 5) according to the first embodiment, but in the second embodiment, in process S101, the calculation unit 52 does not use the entire list of IP addresses of authenticated user devices in the closed network 100 received in process S12, but instead uses information indicating the communication status received in process S10 from this list (the IP address of the user device 111 not communicating with the server 130) to calculate the allocation rate (attach rate) β of the IP addresses of the user devices. 100 Calculate.
[0069] Similarly, in the second embodiment, in processing S101, the calculation unit 52 does not use the entire list of IP addresses of authenticated user devices in the closed network 200 received in processing S12, but instead uses information indicating the communication status received in processing S10 from this list (the IP address of the user device 211 that is not stopped like the user device 212 but is not communicating with the server 130) to calculate the allocation rate (attachment rate) β of the IP addresses of the user devices. 200 Calculate.
[0070] That is, in step S101, the calculation unit 52 calculates the IP address allocation rate (attachment rate) β of the user devices in the closed network 100 using the following (Equation 5): 100 and the IP address allocation rate (attachment rate) β of user devices in the closed network 200 200 Calculate.
[0071] β X =B X / n X ...(Formula 5) β X : IP address allocation rate B X : Number of user devices that are not currently communicating with a server, etc., among the user devices that have been assigned IP addresses n X : The number of user devices that are not in data communication with the server, etc., among all user devices in the closed network X. Accordingly, in process S102, the calculation unit 52 calculates the allocation rate α calculated in process S101 using the following (Equation 6): 100 , and the number n of predetermined user devices in the private network 100 read from the storage unit 59 100 and the monitoring interval P of the private network 100 100 Based on this, the monitoring demand amount D of the closed network 100 is calculated using the following (Equation 6). 100 and the monitoring demand amount D of the closed network 200 200 Calculate.
[0072] D X = β X * n X * P X ...(Formula 6) D X : Monitoring demand amount P of closed network X X: Monitoring interval [Major effects of the second embodiment] As described above, according to the present embodiment, in addition to the effects of the first embodiment, by excluding the user devices 112 that are already in data communication with the server 130, etc. from the targets to be monitored (measured), the processing capacity (resources) of the monitoring device 60 can be effectively utilized.
[0073] Third Embodiment Next, a third embodiment will be described with reference to FIGS.
[0074] [Functional Configuration of Third Embodiment] Figure 9 is a diagram showing the overall configuration of a communication system according to a third embodiment. The overall configuration of the third embodiment is basically the same as that of the second embodiment, and the same devices and the like are designated by reference numerals and their description will be omitted. Furthermore, since the third embodiment is similar to the second embodiment in terms of the system configuration (Figure 1), hardware configuration (Figure 2), functional configuration (Figure 3), and general processing (Figure 8), only the differences will be described below.
[0075] The third embodiment differs from the second embodiment in that a communication system 10c is shown instead of the communication system 10b of the second embodiment, and a monitoring control device 50c is shown instead of the monitoring control device 50b of the second embodiment. The functional configuration of the monitoring control device 50c is basically the same as the functional configuration of the monitoring control device 50b. Differences from the processing content of each functional configuration of the second embodiment will be explained later. Also, the monitoring device 60 of the second embodiment is omitted, and each network device 120c, 220c performs processing in place of the monitoring device 60.
[0076] In FIG. 9, the communication status of each of the user devices 111, 112, 211, and 212 is the same as that shown in FIG.
[0077] As a process specific to the third embodiment, for example, when the monitoring request amount exceeds the upper limit of the processing capacity for alive monitoring of the user equipment, the calculation unit 52 performs a process of reducing the monitoring request amount to the upper limit, which will be described in detail later.
[0078] [Processing of the Third Embodiment] Next, the processing of the third embodiment will be described with reference to FIG. 10. FIG. 10 is a sequence diagram showing the processing of the communication system according to the third embodiment. Note that since processes S10 to S12 are the same as those of the second embodiment shown in FIG. 8, the description will begin with process S13c. Process S13c is executed instead of process S13b. Here, process S13c will be described in detail with reference to FIG. 11. FIG. 11 is a flowchart showing the calculation processing of the monitoring request amount according to the third embodiment. In the first and second embodiments, the monitoring device 60 distributes the processing capacity of the monitoring device 60 to each of the closed networks 100, 200, so that the processing capacity of the monitoring device 60 does not exceed the processing load on each of the closed networks 100, 200 (processes S103 to S105). However, in the third embodiment, each network device 120c, 220c performs alive monitoring, and therefore, as shown below, each network device 120c, 220c performs processing within each closed network 100, 200 within a range that does not exceed the processing capacity for alive monitoring (processing S303, S304).
[0079] 11, since the processes S301 and S302 are the same as the processes S101 and S102 in the second embodiment, the process S303 will be described first. Note that the storage unit 59 stores the upper limit M X is stored.
[0080] S303: The determination unit 53 determines each monitoring request amount D X is the upper limit M of the processing capacity (monitoring capacity) of the network device (monitoring device) in each of the closed networks 100 and 200. X Specifically, the determination unit 53 determines whether the monitoring request amount D 100 is the upper limit M of the processing capacity of the network device (monitoring device) in the closed network 100. 100 Similarly, the determination unit 53 determines whether the monitoring demand amount D 200 is the upper limit M of the processing capacity of the network device (monitoring device) in the closed network 200. 200 Then, it is judged whether the monitoring demand amount D X is the upper limit M XIf it does not exceed (NO), the determination unit 53 notifies the calculation unit 52 of the monitoring request amount D X is the upper limit M X 11 is completed by outputting a determination result indicating that the calculated value does not exceed the predetermined value.
[0081] S304: In the process S303, the monitoring demand amount D X is the upper limit M X If it exceeds (YES), the determination unit 53 notifies the calculation unit 52 of the monitoring request amount D X is the upper limit M X As a result, the calculation unit 52 outputs a determination result indicating that the monitoring demand amount D X is the upper limit M X Each monitored demand quantity D' after reduction to be equal to X Calculate.
[0082] D' X = M X (Equation 7) This completes the calculation process shown in FIG.
[0083] 4, the communication unit 51 transmits to the monitoring device 60 the monitoring demand quantity D 100,200 (or D' 100,200 ) and the IP addresses of the user devices to be measured in the list received in step S12. However, in step S14c of FIG. 11, the communication unit 51 transmits to each of the network devices 120c and 220c the monitoring demand quantity D 100,200 (or D' 100,200 ), and the IP address of each user device that is a measurement target in the list received in step S12. Specifically, the communication unit 51 transmits to the network device 120c the monitoring request amount D 100 (or D' 100 ), and the IP address of each user device that is a measurement target in the list received in process S12. Similarly, the communication unit 51 transmits to the network device 220c the monitoring request amount D 200 (or D' 200), and the IP address of each user device that is the measurement target in the list received in step S12.
[0084] Accordingly, in the third embodiment, in process S16, each network device 120a, 220c performs alive monitoring of the user devices in each private network 100, 200 (S16a, S16b), similar to process S15 (S15a, S15b).
[0085] [Major Effects of the Third Embodiment] As described above, according to this embodiment, the same effects as those of the first and second embodiments can be achieved without using the monitoring device 60.
[0086] Supplementary Note: The present invention is not limited to the above-described embodiment, and may have the following configurations or processes (operations), for example.
[0087] (1) The monitoring and control devices 50a, b, and c can be realized using a computer and a program, but this program can also be recorded on a (non-temporary) recording medium or provided via a communication network (such as a wide area network 99).
[0088] (2) The processor 1004, which is hardware, may be a single processor or multiple processors.
[0089] 10a, 10b, 10c Communication system 50a, 50b, 50c Monitoring control device 51 Communication unit 52 Calculation unit 53 Determination unit 59 Storage unit 60 Monitoring device
Claims
1. A monitoring control device that controls alive monitoring to check the operating status of user equipment, comprising: a communication unit that receives the IP addresses of authenticated user equipment from an authentication device that assigns IP addresses to each user equipment by authenticating each user equipment within a specified closed network; and a calculation unit that calculates an allocation rate of IP addresses for user equipment based on the IP addresses of the authenticated user equipment and the number of user equipment within the specified closed network, and calculates a monitoring request amount that indicates the number of times per unit time that measurement packets for alive monitoring should be sent to a specified user equipment among the user equipment based on the allocation rate, the number, and a predetermined monitoring interval.
2. A monitoring and control device as described in claim 1, wherein, when the specified closed network is a plurality of closed networks, the calculation unit calculates the total value of the monitoring demand quantities calculated for each of the plurality of closed networks, and, if the total value exceeds an upper limit of the processing capacity for alive monitoring of user equipment within the plurality of closed networks, calculates each modified monitoring demand quantity by reducing it in accordance with the proportion of each monitoring demand quantity so that the total value becomes the upper limit.
3. The monitoring and control device described in claim 1, wherein the communication unit receives information indicating the communication status of each user device from a network device that relays data communication between the user device and other devices, and the calculation unit excludes a specified user device that is currently communicating data from the calculation of the allocation rate based on the communication status.
4. The monitoring control device according to claim 1, wherein when the monitoring request amount exceeds an upper limit of processing capacity for alive monitoring of the user equipment, the calculation unit performs processing to reduce the monitoring request amount to the upper limit.
Citation Information
Patent Citations
Communication system
JP2003141083A
Server device, information processor, program, and recording medium
JP2008276686A
IP telephone exchange and IP telephone system
JP2011003981A
Communication system
JP2016178609A