Management device, management method, and management program

Abstract

A management device (10) includes: a cloud server delay time measurement unit (16) that, by probing toward a server, acquires in advance, for each area, a first transfer delay time which is the transfer delay time from a NW edge node to a representative cloud server; a NW measurement unit (17) that probes within the NW and acquires, for each slice, a second transfer delay time which is the transfer delay time within the NW; and an end-to-end delay calculation unit (18) that totals a value based on the first transfer delay time of an area corresponding to an end-to-end to be calculated, from among the first transfer delay times acquired by the cloud server delay time measurement unit (16), and the second transfer delay time of a slice corresponding to the end-to-end to be calculated, from among the second transfer delay times acquired by the NW measurement unit (17), and uses the totaled time as an end-to-end transfer delay time.

Description

Technical Field

[0001] The present invention relates to a management device, a management method, and a management program.

Background Art

[0002] As methods for measuring network (NW) information, for example, there are xflow that performs port monitoring and probe packet monitoring defined in RFC5357.

[0003] In xflow, information is collected based on 5-tuples in packet units, but there is no identifier for identifying the logical plane, and NW information in slice units cannot be collected.

[0004] On the other hand, in probe packet monitoring, it is possible to measure the transfer delay of the logical plane using probe packets of Segment Routing (SR). In this method, the quality of the network in the SR network is measured by measuring the delay time in the SR network.

[0005] Also, as a method for measuring the network quality from a network element (NE) to a server, a method for measuring the quality using probe packets such as HTTP has been proposed.

Prior Art Documents

Patent Documents

[0006]

Patent Document 1

Non-Patent Documents

[0007]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Non-Patent Document 4

Summary of the Invention

Problems to be Solved by the Invention

[0008] Conventional methods cannot measure the end-to-end network quality for each slice, and since there are a large number of servers on the network, measuring the quality of the network to all servers consumes a large amount of resources.

[0009] The present invention has been made in view of the above, and an object thereof is to provide a management device, a management method, and a management program capable of measuring the end-to-end network quality for each slice while reducing network resource consumption due to quality measurement.

Means for Solving the Problem

[0010] In order to solve the above-described problems and achieve the object, a management device according to the present invention is a management device that calculates an end-to-end transfer delay time, which is a transfer delay time in a network from a node at a network edge to which a UE (User Equipment) is connected and a transfer delay time from the node at the network edge to a cloud server, and based on communication information of probe packets transmitted from a node at a network edge to a representative cloud server of each area, a first acquisition unit that acquires in advance, for each area, a first transfer delay time that is a transfer delay time from the node at the network edge to the representative cloud server, a second acquisition unit that performs a network probe and acquires, for each slice, a second transfer delay time that is a transfer delay time in the network, and a calculation unit that adds together a value based on the first transfer delay time of the area corresponding to the end-to-end to be calculated among the first transfer delay times acquired by the first acquisition unit and the second transfer delay time of the slice corresponding to the end-to-end to be calculated among the second transfer delay times acquired by the second acquisition unit, and sets the added time as the end-to-end transfer delay time.

Advantages of the Invention

[0011] According to the present invention, it is possible to measure the end-to-end network quality for each slice while reducing network resource consumption due to quality measurement.

Brief Description of the Drawings

[0012]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited by this embodiment. In the description of the drawings, the same parts are denoted by the same reference numerals.

[0014] [Embodiment] First, the communication system in the embodiment will be described. FIG. 1 is a diagram for explaining the outline of the measurement process of network quality in the embodiment.

[0015] In the embodiment, as the network (NW) quality, the transfer delay time (end-to-end transfer delay time) from the node at the NW edge to which the UE (User Equipment) is connected to the cloud server is measured for each slice. Note that the SID described in FIG. 1 is a Segment Identifier. The node has a logical path monitoring function and a physical path monitoring function for each slice.

[0016] In the communication system according to the embodiment, by transmitting a probe packet from a node at the NW edge (for example, node N15) to the representative cloud server (router·SW·server) of each area, the transfer delay time (first transfer delay time) from the node at the NW edge to the representative cloud server for each area is measured in advance. In the communication system, the first transfer delay time from the node at the NW edge to the representative cloud server is acquired in advance for each area by the probe for the cloud server (step (1) in FIG. 1).

[0017] In the communication system, by measuring the inside of the NW (for example, inside the SR network) with a probe packet, the transfer delay time (second transfer delay time) inside the NW is acquired for each slice in advance (step (2) in FIG. 1). For example, in the communication system, the second transfer delay time is acquired for each slice by transmitting a probe packet from a node at the NW edge (for example, node N15) to another node at the NW edge (for example, node N1) (step (2) in FIG. 1).

[0018] Then, the communication system adds the first transfer delay time acquired by the NW internal probe and the second transfer delay time acquired by the server-oriented probe in correspondence with the slice and area for which the quality is to be measured. Thereby, the communication system acquires the end-to-end transfer delay time corresponding to the slice and area for which the quality measurement is to be performed (step (3) in FIG. 1).

[0019] In this way, in the embodiment, measurement of the end-to-end network quality through the slice to be measured in the NW and the NW edge and the server is realized. Further, in the communication system, since it is only necessary to measure the transfer delay time to the representative cloud server for each area, compared with the method of measuring the NW quality to all servers, it is possible to reduce the network resource consumption by quality measurement.

[0020] [Communication system] Next, the configuration of the communication system according to the embodiment will be described. FIG. 2 is a diagram schematically showing an example of the configuration of the communication system in the embodiment.

[0021] As shown in FIG. 2, the communication system 100 has a configuration in which the UE 20 and the cloud server 40 (router / SW / server) are connected via the NW 30. There are a plurality of UEs 20 and cloud servers 40. The communication system 100 has a management device 10 that measures the end-to-end transfer delay time for each slice.

[0022] [Management device] The management device 10 will be described. The management device 10 is realized, for example, by a computer including a ROM (Read Only Memory), a RAM (Random Access Memory), a CPU (Central Processing Unit), etc., in which a predetermined program is loaded and the CPU executes the predetermined program. Further, the management device 10 has a communication interface for transmitting and receiving various information to and from other devices connected via a network or the like.

[0023] As shown in FIG. 1, the management device 10 includes a network topology management unit 11, an area unit cloud server management unit 12, a Flow information acquisition unit 13, a Flow information management unit 14, a server measurement unit 15, a cloud server delay time measurement unit 16, an NW measurement unit 17, and an end-to-end delay calculation unit 18.

[0024] The network topology management unit 11 acquires topology information, which is the configuration information of the network, and manages the configuration of the NW30 based on the topology information. The network topology management unit 11 performs slice route management from topology management.

[0025] The area unit cloud server management unit 12 has management information of the cloud servers installed in each area, and manages various information of the cloud servers in area units.

[0026] The Flow information acquisition unit 13 acquires the Flow information of the NW30.

[0027] The Flow information management unit 14 manages the Flow information acquired by the Flow information acquisition unit 13. For example, the Flow information management unit 14 acquires the dst information on the Flow based on the Flow information acquired by the Flow information acquisition unit 13. Then, the Flow information management unit 14 derives the area corresponding to the destination from the dst information.

[0028] The server measurement unit 15 causes a probe packet to be transmitted from a node at the NW30 edge to the representative cloud server 40 of each area for the server-oriented probe.

[0029] The cloud server delay time measurement unit 16 measures in advance, for each area, a first delay time, which is the transfer delay time from the node at the NW30 edge to the representative cloud server, based on the communication information of the probe packet transmitted from the node at the NW30 edge to the representative cloud server 40 of each area. The cloud server delay time measurement unit 16 registers or updates the first transfer delay time obtained by measuring for each area.

[0030] FIG. 3 is a diagram for explaining the measurement of the first transfer delay time. The management device 10 searches for the area corresponding to the packet destination from the dst information of the packet for the cloud server 40 in the server-oriented probe. Then, the cloud server delay time measurement unit 16 measures the transfer delay time to the cloud server 40 for each area (FIG. 3(1)).

[0031] The cloud server delay time measurement unit 16 causes the server measurement unit 15 to send probe packets from the nodes at the edge of the NW 30 to the representative cloud servers 40 in each area, and measures the first transfer delay time for each area. The cloud server delay time measurement unit 16 measures, as the first transfer delay time, the transfer delay time between the NW edge and any one of the router, SW, and server of the cloud servers established for each area.

[0032] Here, from the concept of distance, it can be said that within the same area, the difference in transfer delay time between cloud servers is within the error range. Based on this, in the embodiment, the transfer delay time from the node at the edge of the NW 30 to the representative cloud server 40 is set to the transfer delay time from the node at the edge of the NW 30 to each router, SW, and server within the same area as the representative cloud server 40.

[0033] Therefore, in the embodiment, since it is not necessary to measure the transfer delay time for all the router, SW, and servers in the area, it is possible to reduce the network resource consumption due to quality measurement as compared with the case where the transfer delay time is measured for all the router, SW, and servers in the area.

[0034] FIG. 4 is a diagram showing an example of the first transfer delay measurement result. FIG. 4 is the result of measuring the transfer delay time between the NW and the cloud servers of each server at the node of the NW edge for each slice. In FIG. 4, for example, the result of measuring the transfer delay time between the NW edge and the cloud servers of servers 1 and 2 in the American area at node N15 for each of slices 1 and 2 is shown.

[0035] The cloud server delay time measurement unit 16 measures the transfer delay time between the node N15 and the servers 1 and 2 a plurality of times for each of the slices 1 and 2. Based on these measurement results, the cloud server delay time measurement unit 16 calculates the average and deviation of the transfer delay time between the node N15 and the servers 1 and 2, and registers the calculated average and deviation as information regarding the transfer delay time between the node N15 and the servers 1 and 2 (for example, frame W41).

[0036] At this time, the cloud server delay time measurement unit 16 may calculate the average and deviation of the transfer delay time by dividing them according to a predetermined time zone (daytime or nighttime) or a predetermined period (weekday, end of month, etc.) according to the usage status of the service to be measured.

[0037] The NW measurement unit 17 measures the second transfer delay time in advance for each slice by performing in-NW probing. The NW measurement unit 17 determines the slice through which this probe packet passes based on the tunnel ID etc. of the probe packet.

[0038] FIG. 5 is a diagram showing an example of the measurement result of the second transfer delay time. The NW measurement unit 17 measures in advance the transfer delay time of each slice at each node in the NW30. The NW measurement unit 17 registers or updates the measured transfer delay time for each slice. The measurement result of the transfer delay time of slice 1 at the node N15 is shown in frame W51 of FIG. 5.

[0039] The end-to-end delay calculation unit 18 calculates the transfer delay time of the end-to-end to be calculated by adding together a value based on the first transfer delay time of the area corresponding to the end-to-end for which the transfer delay time is to be calculated and the second transfer delay time corresponding to the slice corresponding to the end-to-end for which the transfer delay time is to be calculated.

[0040] FIG. 6 is a diagram for explaining the calculation of the end-to-end transfer delay time. The end-to-end delay calculation unit 18 refers to the dst address of the destination from the Flow information of the packet communication obtained by the Flow information management unit 14, and searches for which area the packet is destined for ((1) in FIG. 6). The end-to-end delay calculation unit 18 refers to the first transfer delay time measurement result of each area (for example, the measurement result in FIG. 4), and acquires the first transfer delay time of the corresponding area ((2) in FIG. 6).

[0041] The end-to-end delay calculation unit 18 determines a slice for which the transfer delay time is to be calculated based on segment routing or a tunnel protocol. The end-to-end delay calculation unit 18 refers to the second delay time measurement result of each slice (for example, the measurement result in FIG. 5), and acquires the transfer delay time of the slice for which the calculation is to be performed. At this time, the end-to-end delay calculation unit 18 acquires and sums up the transfer delay times of all the nodes through which the slice for which the calculation is to be performed passes.

[0042] The end-to-end delay calculation unit 18 calculates the end-to-end transfer delay time of the calculation target using Equation (1).

[0043]

Equation

[0044] The network-server delay measurement in Equation (1) is a value based on the first transfer delay time of the area corresponding to the end-to-end for which the transfer delay time is to be calculated. The NW delay measurement is the second transfer delay time corresponding to the slice corresponding to the end-to-end for which the transfer delay time is to be calculated.

[0045] At this time, the end-to-end delay calculation unit 18 applies either the average value of the first transfer delay time or the maximum value of the first transfer delay time obtained based on the average value and deviation of the first transfer delay time, according to the quality requirement of the slice corresponding to the end-to-end for which the transfer delay time is to be calculated, as the value based on the first transfer delay time in Equation (1).

[0046] For example, for services that are not strict about transfer delay, the end-to-end delay calculation unit 18 adopts the average value of the first transfer delay time. Also, for services that are strict about transfer delay, the end-to-end delay calculation unit 18 adopts the maximum value of the first transfer delay time. For example, the strictness of transfer delay for each service is set in five levels. Level 5 is strict about transfer delay, levels 3 - 4 have a standard strictness for transfer delay, and levels 1 - 2 are set to not be strict about transfer delay.

[0047] In this way, by using the transfer delay time to the cloud server in units of areas, the management device 10 calculates the end-to-end transfer delay time for all of the hundreds to thousands of servers without measuring the transfer delay time for each one.

[0048] [Flow Information Management Process] Next, the Flow information management process performed by the management device 10 will be described. FIG. 7 is a flowchart showing the processing procedure of the Flow information management process.

[0049] The Flow information acquisition unit 13 acquires the Flow information of the NW 30 (step S1). The Flow information management unit 1414 acquires the dst information on the Flow based on the Flow information acquired by the Flow information acquisition unit 13 (step S2). Then, the Flow information management unit 1414 derives the corresponding area of the destination from the dst information (step S3).

[0050] [First Transfer Delay Time Measurement Process] Next, the second transfer delay time measurement process performed by the management device 10 will be described. FIG. 8 is a flowchart showing the processing procedure of the second transfer delay time measurement process.

[0051] The server measurement unit 15 causes a probe packet to be transmitted from a node at the edge of the NW 30 to a representative cloud server 40 (router / SW / server) for each area. The cloud server delay time measurement unit 16 measures the first transfer delay time between the node at the edge of the NW 30 and the cloud server 40 for each area based on this probe packet for the server (step S11).

[0052] Based on the measured first transfer delay time, the cloud server delay time measurement unit 16 updates the transfer delay information of the cloud server for each area (for example, the measurement result in FIG. 4) (step S12).

[0053] The cloud server transfer delay measurement process is executed periodically or according to a predetermined schedule.

[0054] [Second transfer delay time measurement process] Next, the second transfer delay time measurement process performed by the management device 10 will be described. FIG. 9 is a flowchart showing the processing procedure of the second transfer delay time measurement process.

[0055] The NW measurement unit 17 performs probing within the NW 30 (step S21) and measures the second transfer delay time in advance for each slice (step S22). Based on the measured second transfer delay time, the NW measurement unit 17 updates the NW delay information (for example, FIG. 5) (step S23).

[0056] [End-to-end delay measurement process] Next, the end-to-end delay calculation process performed by the management device 10 will be described. FIG. 10 is a flowchart showing the processing procedure of the end-to-end delay calculation process.

[0057] The management device 10 has the end-to-end delay calculation unit 18 select a logical path (step S31). For the Flow information of the selected logical path, the Flow information management unit 14 extracts the dst address of the acquired data (step S32) and detects the area of the cloud server for which the end-to-end transfer delay time is to be calculated (step S33).

[0058] The end-to-end delay calculation unit 18 refers to the delay time measurement result between the cloud server and the node of the NW edge (for example, the measurement result in FIG. 4) (step S34), and acquires the first transfer delay time of the area detected in step S33.

[0059] The end-to-end delay calculation unit 18 refers to the NW delay time measurement result (for example, the measurement result in FIG. 5) (step S35), and acquires the second transfer delay time corresponding to the slice for which the end-to-end transfer delay time is to be calculated.

[0060] Then, the end-to-end delay calculation unit 18 calculates the end-to-end delay time by adding the value based on the first transfer delay time acquired in step S34 and the second transfer delay time acquired in step S35 (step S36).

[0061] [Effects of the Embodiment] FIGS. 11 and 12 are diagrams for explaining an existing NW monitoring method in the prior art.

[0062] In the monitoring method of the NW slice composed of SR, in the monitoring using the SR probe packet, the SR router section is monitored ((1) in FIG. 11). Therefore, in this method, in the section from the node of the NW edge other than the SR router section to the server, monitoring by a probe packet (HTTP, etc.) could not be performed ((2) in FIG. 11). Further, in this method, in the end-to-end network slice between the UE and the server, the end-to-end network quality could not be monitored ((3) in FIG. 11).

[0063] Also, it is possible to measure the delay time from the UE to the server using probe packets such as HTTP. However, when there are a large number of destination servers, the number of measurement targets becomes extremely large ((1) in FIG. 12), and there is a problem that measuring the quality of the network to all servers consumes a large amount of resources. In addition, due to the large number of UEs, there is a problem that the inside of the NW becomes congested due to probe packets from the UEs ((2) in FIG. 12).

[0064] In contrast, the management device 10 according to the embodiment preliminarily acquires the first transfer delay time for each area based on the communication information of the probe packets transmitted from the nodes at the NW30 edge to the representative cloud servers in each area. The management device 10 performs in-NW30 probing and acquires the second transfer delay time for each slice.

[0065] Then, the management device 10 adds together the value based on the first transfer delay time of the area corresponding to the end-to-end to be calculated among the acquired first transfer delay times and the second transfer delay time of the slice corresponding to the end-to-end to be calculated among the acquired second transfer delay times, and sets the added time as the end-to-end transfer delay time.

[0066] In this way, the management device 10 only needs to preliminarily acquire the first transfer delay time and the second transfer delay time, and by adding the first transfer delay time and the second transfer delay time corresponding to the slice and area of the end-to-end to be measured, it realizes the measurement of the network quality passing through the slice of the NW30, the nodes at the NW30 edge, and the cloud server 40 corresponding to the end-to-end to be calculated.

[0067] In addition, since the management device 10 only needs to measure the transfer delay time to the representative cloud server for each area, it is possible to reduce the consumption of network resources due to quality measurement as compared with the method of measuring the transfer delay time for all servers.

[0068] In addition, the management device 10 applies, as the time based on the first transfer delay time, either the average value of the first transfer delay time or the maximum value of the first transfer delay time according to the quality requirements of the slice corresponding to the end-to-end to be calculated. By calculating the end-to-end transfer delay time according to the severity of the transfer delay of the service corresponding to the slice to be calculated, the management device 10 can appropriately manage the operation status of the service.

[0069] [System Configuration of the Embodiment] Each component of the management device 10 is functionally conceptual and does not necessarily have to be physically configured as shown in the figure. That is, the specific form of the distribution and integration of the functions of the management device 10 is not limited to that shown in the figure, and all or part of it can be functionally or physically distributed or integrated in any unit according to various loads, usage situations, etc.

[0070] In addition, all or any part of each process performed in the management device 10 may be realized by a program analyzed and executed by a CPU, a GPU (Graphics Processing Unit), and the CPU and GPU. Also, each process performed in the management device 10 may be realized as hardware by wired logic.

[0071] In addition, among the processes described in the embodiment, all or part of the processes described as being automatically performed can also be manually performed. Or, all or part of the processes described as being manually performed can also be automatically performed by a known method. In addition, the processing procedures, control procedures, specific names, and information including various data and parameters described above and shown in the figure can be appropriately changed unless otherwise specified.

[0072] [Program] FIG. 13 is a diagram showing an example of a computer by which the management device 10 is realized when a program is executed. The computer 1000 has, for example, a memory 1010 and a CPU 1020. The computer 1000 also has a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These components are connected by a bus 1080.

[0073] The memory 1010 includes a ROM 1011 and a RAM 1012. The ROM 1011 stores a boot program such as a BIOS (Basic Input Output System), for example. The hard disk drive interface 1030 is connected to a hard disk drive 1031. The disk drive interface 1040 is connected to a disk drive 1041. A removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive 1041, for example. The serial port interface 1050 is connected to, for example, a mouse 1110 and a keyboard 1120. The video adapter 1060 is connected to, for example, a display 1130.

[0074] The hard disk drive 1031 stores, for example, an OS (Operating System) 1091, an application program 1092, a program module 1093, and program data 1094. That is, the program that defines each process of the management device 10 is implemented as a program module 1093 in which executable code by the computer 1000 is described. The program module 1093 is stored in the hard disk drive 1031, for example. For example, a program module 1093 for executing the same process as the functional configuration in the management device 10 is stored in the hard disk drive 1031. Note that the hard disk drive 1031 may be replaced by an SSD (Solid State Drive).

[0075] Also, the setting data used in the processing of the above-described embodiment is stored as program data 1094 in, for example, the memory 1010 or the hard disk drive 1031. Then, the CPU 1020 reads out and executes the program modules 1093 and the program data 1094 stored in the memory 1010 or the hard disk drive 1031 into the RAM 1012 as needed.

[0076] Note that the program modules 1093 and the program data 1094 are not limited to being stored in the hard disk drive 1031, and may be stored in, for example, a removable storage medium and read out by the CPU 1020 via the disk drive 1041 or the like. Alternatively, the program modules 1093 and the program data 1094 may be stored in another computer connected via a network (such as a LAN (Local Area Network) or a WAN (Wide Area Network)). Then, the program modules 1093 and the program data 1094 may be read out by the CPU 1020 from the other computer via the network interface 1070.

[0077] As described above, the embodiments to which the invention made by the present inventor is applied have been described. However, the present invention is not limited by the description and the drawings that form a part of the disclosure of the present invention according to the present embodiment. That is, all other embodiments, examples, operation techniques, etc. made by those skilled in the art based on the present embodiment are included in the scope of the present invention.

Description of Reference Numerals

[0078] 10 Management Device 20 UE (User Equipment) 30 NW (Network) 40 Cloud Server 11 Network Topology Management Unit 12 Area Unit Cloud Server Management Unit 13 Flow Information Acquisition Unit 14 Flow Information Management Unit 15 Measurement Unit for Server 16 Cloud Server Delay Time Measurement Unit 17 Measurement Unit for NW 18 End-to-End Delay Calculation Unit

Claims

1. A management device that calculates an end - to - end transfer delay time, which is the transfer delay time within the network from a node at the network edge to which a UE (User Equipment) is connected and the transfer delay time from the node at the network edge to a cloud server, comprising: A first acquisition unit that acquires, in advance for each area, a first transfer delay time, which is the transfer delay time from the node at the network edge to the representative cloud server of each area, based on the communication information of probe packets transmitted from the node at the network edge to the representative cloud servers of each area; A second acquisition unit that performs network probing and acquires, for each slice, a second transfer delay time, which is the transfer delay time within the network; A calculation unit that adds together a value based on the first transfer delay time of the area corresponding to the end - to - end to be calculated among the first transfer delay times acquired by the first acquisition unit and the second transfer delay time of the slice corresponding to the end - to - end to be calculated among the second transfer delay times acquired by the second acquisition unit, and sets the added - up time as the end - to - end transfer delay time; A management device, characterized by comprising the above.

2. The management device according to claim 1, wherein the calculation unit applies, as the value based on the first transfer delay time, either the average value of the first transfer delay time or the maximum value of the first transfer delay time obtained based on the deviation and the average value of the first transfer delay time.

3. The management device according to claim 2, wherein the calculation unit applies, as the time based on the first transfer delay time according to the quality requirement of the slice corresponding to the end - to - end to be calculated, either the average value of the first transfer delay time or the maximum value of the first transfer delay time obtained based on the deviation and the average value of the first transfer delay time.

4. A management method executed by a management device that calculates an end - to - end transfer delay time, which is the transfer delay time within the network from a node at the network edge to which a UE (User Equipment) is connected and the transfer delay time from the node at the network edge to a cloud server, comprising: A first acquisition step of acquiring in advance, for each area, a first transfer delay time, which is the transfer delay time from the node at the network edge to the representative cloud server of the area, based on communication information of probe packets transmitted from the node at the network edge to the representative cloud servers of each area; A second acquisition step of performing a network - wide probe and acquiring, for each slice, a second transfer delay time, which is the transfer delay time within the network; A calculation step of adding together a value based on the first transfer delay time of the area corresponding to the end - to - end to be calculated among the first transfer delay times acquired in the first acquisition step and the second transfer delay time of the slice corresponding to the end - to - end to be calculated among the second transfer delay times acquired in the second acquisition step, and setting the added time as the end - to - end transfer delay time; The management method is characterized by including the above steps.

5. A first acquisition step of acquiring in advance, for each area, a first transfer delay time, which is the transfer delay time from the node at the network edge to the representative cloud server of the area, based on communication information of probe packets transmitted from the node at the network edge to the representative cloud servers of each area; A second acquisition step of performing a network - wide probe and acquiring, for each slice, a second transfer delay time, which is the transfer delay time within the network from the node at the network edge; Based on the first transfer delay time corresponding to the end-to-end area from the node at the network edge to which the UE (User Equipment) to be calculated for the transfer delay time among the first transfer delay times obtained in the first acquisition step is connected to the cloud server, and the second transfer delay time of the slice corresponding to the end-to-end to be calculated among the second transfer delay times obtained in the second acquisition step, a calculation step of adding them together and setting the added time as the transfer delay time of the end-to-end, A management program for causing a computer to execute.

Images