JP2016116184A - Network monitoring device and virtual network management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system capable of flexibly utilizing a network resource.SOLUTION: In a virtual network construction, a model in which physical or virtual network resource information is pooled once is established. A virtual network 1305 can be constructed using pooled resource information 1304, and the resource information 1304 that is not used for the virtual network construction and left in a pool prepares another resource pool 1306 so that the resource information can be distributed. A resource pool 1306 at a distribution destination can be managed by a different user. The user constructs freely a virtual network 1307 and can further distribute the resource to different users.SELECTED DRAWING: Figure 13

Description

  The present invention relates to a network monitoring apparatus and a virtual network management method, and more particularly to a network monitoring apparatus and a virtual network management method for allocating network resources in network virtualization technology.

With the recent expansion of the use of cloud services, the diversification of information communication services in terminals and data centers has progressed, and the characteristics of traffic via public networks have also diversified. On the other hand, looking at the entire network that constitutes a service, the complexity is increasing in which a large number of communication devices such as packets and light are arranged hierarchically. In such an environment, it is necessary for the entire network to respond flexibly and quickly to changes in service specifications and significant traffic fluctuations.
Further, in today's communication networks, the traffic volume in the Internet is expected to increase rapidly in the future due to the increase in network population and the spread of various communication services. As the amount of traffic increases, the number of IT devices such as servers and routers that process the traffic tends to increase. From the viewpoint of cost reduction, the operation efficiency of network devices such as servers and routers is maximized and limited resources are maximized. There is a need for operational technology that draws out limited performance.

In general, there is a virtualization technology as a technology for efficiently using limited network resources. Even in a virtualized network, it is necessary to adapt the network configuration flexibly and quickly to service specification changes and large traffic fluctuations.
In general, various virtualization technologies that efficiently and efficiently use limited resources are known.
Patent Document 1 proposes a network resource management method that detects a change in a traffic pattern and dynamically allocates physical resources to prevent deterioration in network quality.

JP 2014-090501 A

  In Patent Document 1, for example, when there is a virtual network with low usage frequency, the allocated physical resource may be small, but the virtual resource allocated to the virtual network remains used in the virtual network, Depending on the case, it may be a floating resource that is not used, and it is assumed that limited network resources cannot be used efficiently.

  An object of this invention is to provide the structure which can utilize a network resource flexibly in view of the above point.

According to the first solution of the present invention,
A network monitoring device,
A control unit;
A resource object management table in which resource pool ID, resource NEID, resource port ID, resource port maximum bandwidth, resource port use bandwidth are stored correspondingly;
A resource link management table in which resource link IDs, resource pool IDs, and resource port IDs of ports at both ends of the resource link are stored correspondingly;
A virtual object management table in which slice IDs, virtual NEIDs, virtual port IDs, and virtual port maximum bandwidths of slices, which are virtual networks logically constructed using all or part of resources, are stored correspondingly ,
A virtual link management table in which slice IDs, virtual link IDs, and virtual port IDs of ports at both ends of the virtual link are stored correspondingly;
With
The controller is
When there is a slice allocation request, the resource object management table is searched, a list of registered resource pools is sent to the management terminal,
The selected resource pool ID is received from the management terminal, the resource object management table is searched, and the resource NEID and resource port ID are all or a plurality of predetermined numbers from the records that match the selected resource pool ID. Obtain and send to the management terminal as a resource NEID / resource port ID list,
The resource link receives one or more resource NEIDs selected from the resource NEID / resource port ID list, one or more resource port IDs, and an allocated bandwidth for each selected resource port ID by the management terminal, and the resource link Search the management table, and acquire all or a plurality of predetermined resource link IDs from the record that matches the combination of the selected one or more resource NEIDs and one or more resource port IDs, as a resource link ID list , Send to the management terminal,
The management terminal receives one or more resource link IDs selected from the resource link ID list,
Register and select the selected resource pool ID, resource NEID, resource port ID, and allocated bandwidth in the slice ID, virtual NEID, virtual port ID, and virtual port maximum bandwidth of the virtual object management table, respectively. The resource pool ID, the resource link ID, and the resource port ID of the port at both ends of the resource link are respectively registered in the slice ID, the virtual link ID, and the port at both ends of the virtual link in the virtual link management table, A virtual object management table and a network monitoring apparatus for allocating slices according to the virtual object management table are provided.

According to the second solution of the present invention,
A virtual network management method in a network monitoring device, comprising:
The network monitoring device
A control unit;
A resource object management table in which resource pool ID, resource NEID, resource port ID, resource port maximum bandwidth, resource port use bandwidth are stored correspondingly;
A resource link management table in which resource link IDs, resource pool IDs, and resource port IDs of ports at both ends of the resource link are stored correspondingly;
A virtual object management table in which slice IDs, virtual NEIDs, virtual port IDs, and virtual port maximum bandwidths of slices, which are virtual networks logically constructed using all or part of resources, are stored correspondingly ,
A virtual link management table in which slice IDs, virtual link IDs, and virtual port IDs of ports at both ends of the virtual link are stored correspondingly;
With
The controller is
When there is a slice allocation request, the resource object management table is searched, a list of registered resource pools is sent to the management terminal,
The selected resource pool ID is received from the management terminal, the resource object management table is searched, and the resource NEID and resource port ID are all or a plurality of predetermined numbers from the records that match the selected resource pool ID. Obtain and send to the management terminal as a resource NEID / resource port ID list,
The resource link receives one or more resource NEIDs selected from the resource NEID / resource port ID list, one or more resource port IDs, and an allocated bandwidth for each selected resource port ID by the management terminal, and the resource link Search the management table, and acquire all or a plurality of predetermined resource link IDs from the record that matches the combination of the selected one or more resource NEIDs and one or more resource port IDs, as a resource link ID list , Send to the management terminal,
The management terminal receives one or more resource link IDs selected from the resource link ID list,
Register and select the selected resource pool ID, resource NEID, resource port ID, and allocated bandwidth in the slice ID, virtual NEID, virtual port ID, and virtual port maximum bandwidth of the virtual object management table, respectively. The resource pool ID, the resource link ID, and the resource port ID of the port at both ends of the resource link are respectively registered in the slice ID, the virtual link ID, and the port at both ends of the virtual link in the virtual link management table, A virtual object management table and a virtual network management method for allocating slices according to the virtual object management table are provided.

  ADVANTAGE OF THE INVENTION According to this invention, the mechanism which can utilize a network resource flexibly can be provided.

System Configuration. Functional block diagram. Explanatory drawing of a physical network object management table. Explanatory drawing of a link management table. The flowchart at the time of registering a resource pool from a physical resource. Explanatory drawing of a resource object management table. Explanatory drawing of a resource link management table. Explanatory drawing of what showed the change of the band at the time of resource pool registration to the table. The flowchart of slice allocation. Explanatory drawing of a virtual object management table and a virtual link management table. Explanatory drawing of what showed the change of the band at the time of slice allocation to the table. Explanatory drawing of the resource management system table at the time of resource pool registration. The figure which shows the example of a management structure. The sequence diagram at the time of lending a virtual resource. The flowchart of the virtual resource management of the communication carrier A. The flowchart of the virtual resource management of the communication carrier B.

Hereinafter, examples will be described with reference to the drawings.
FIG. 1 is a system configuration diagram of this embodiment. The network monitoring device (101) is a device that monitors a physical network (102) configured by an NE (Node Element) (103) that is a device constituting a communication network. The network monitoring device (101) is connected to the NE (103) via a wired or wireless connection line (106) and controls the NE (103).
The network monitoring device (101) is operated by the communication carrier A and the communication carrier B, and is operated from the communication carrier A management terminal (104) and the communication carrier B management terminal (105). In FIG. 1, communication carrier A and communication carrier B are illustrated, but there may be a plurality of other communication carriers.

  FIG. 2 shows a functional block diagram of the network monitoring apparatus (101). The network monitoring device (101) includes a transmission / reception unit (201), a control unit (202), a physical network management unit (203), and a virtual network management unit (204). The transmission / reception unit (201) is an interface between the network monitoring device (101) and the NE (103), the communication carrier A terminal (104), and the communication carrier B terminal (105), and exchanges information between the network monitoring device and the external device. I do. The control unit (202) controls the information received from the transmission / reception unit (201), and outputs the processed information to the outside.

  The physical network management unit (203) includes a physical network object management table (205) and a link management table (206). A physical network object management table (205) and a link management table (206) manage configuration information of the physical network (102). Particularly in this embodiment, the physical network object management table (205) is a table for managing physical networks, NEs, and ports (details of ports will be described later). Here, for example, the physical network constructed in Tokyo and the physical network constructed in Osaka are distinguished by naming them “Tokyo network” and “Osaka network” respectively. An identifier is also assigned to the physical network (102) itself to make it one of the management targets in the physical network object management table (205). The NE (103) includes an external connection point, and the external connection point is referred to as a “port”. Further, a state in which each port of two different NEs is connected by a cable is called a “link”. The link management table (206) is a table for managing links.

  The virtual network management unit (204) includes a resource object management table (207), a resource link management table (208), a virtual object management table (209), and a virtual link management table (210). A “resource pool” is defined as a concept for uniformly managing physical network resources and virtual network resources. That is, a part of the physical network (102) cut out in whole or in part is called a “resource”, and the resource is managed as table information in the virtual network management unit (204) of the network monitoring device, that is, the resource information is pooled. (Resource pool). A virtual network that is logically constructed using all or part of the resource is called a “slice”.

FIG. 3 and FIG. 4 are explanatory diagrams of tables storing physical network configuration information.
The physical network object management table (205) shown in FIG. 3 (A) stores network, NE and port identification information. In this embodiment, the table for managing the network, NE, and port identification information is described as one physical network object management table (205). However, the physical network, NE, and port identification information are stored in different tables. You may manage with.
The physical network object management table (205) includes a network ID (301) for storing physical network identification information, a NEID (302) for storing NE identification information, and a port ID (303) for storing port identification information. ), A maximum bandwidth (304) in which the maximum bandwidth of the port is stored, and a used bandwidth (305) in which a value used in the port bandwidth is stored.

As an example, a table configuration will be described using a physical network having the configuration described in FIG. NE (306) including port (307) and port (308), NE (309) including port (310) and port (311), NE (312) including port (313) and port (314), port ( 316) and NE (315) having a port (317), the port (307) and the port (317), the port (308) and the port (310), the port (311), the port (313), and the port (311). And a port (313), a port (314), and a port (316) are physically connected by a cable, and there is a network having a link (326), a link (327), a link (328), and a link (329), respectively.
Network ID = 1 is assigned to the network to identify the network, NEID = 1 is assigned to identify NE (306), NEID = 2 is assigned to identify NE (309), and NE (312) is assigned. ) Is assigned NEID = 3, NE (315) is assigned NEID = 4, port (307) is assigned port ID = 1.1, and port (308) is assigned. A port ID = 1.2 is assigned to identify, a port ID = 2.1 is assigned to identify the port (310), a port ID = 2.2 is assigned to identify the port (311), and the port Port ID = 3.1 is assigned to identify (313), Port ID = 3.2 is assigned to identify port (314), and Port ID is used to identify port (316). 4.1 was applied, and the port ID = 4.2 was applied to identify the port (317). Also assume that the maximum bandwidth of each port is 200 MB.
At this time, the network ID (301) in the first row (318) of the physical network object management table (205) is 1, the NEID (302) is 1, the port ID (303) is 1.1, and the maximum bandwidth (304) is set. A value such as 200M and 0M is stored in the used bandwidth (305). Stored in the same manner from row (319) to row (325).

  Also, the link management table (206) shown in FIG. 4 is given a link ID = 1 to identify the link (326), a link ID = 2 to identify the link (327), and the link (328). When link ID = 3 is assigned to identify the link and link ID = 4 is assigned to identify the link (329), the link ID is assigned to the link ID (401) column and the link is assigned to the network ID (402) column. The corresponding network ID value is one port ID of the port connected to the link in the A point port ID (403) column, and the other port of the port connected to the link in the Z point port ID (404) column. ID is stored.

FIG. 5 is a flowchart for creating a resource pool from physical network configuration information stored in the physical network object management table (205) and the link management table (206), and FIGS. FIG. 6 is an explanatory diagram of a resource object management table (207) created according to the flowchart of FIG. 8 and an explanatory diagram of a resource link management table (208).
When the physical network configuration information is registered by the physical network management table (205) and the link management table (206), a resource pool registration request (501) is automatically made, and the control unit (202) It shall be received. The control unit (202) confirms the record registered in the physical network object management table (205) from the record registered in the top row (502), and performs the processing after the flow (502). It is confirmed whether there is no record (unconfirmed record). If there is an unconfirmed record, the control unit (202) copies the top one row of the physical network object management table in which the record is registered (503). The resource object management table (207) is copied (504).
That is, the control unit (202) uses the value registered in the network ID (301) of the physical network object management table (205) copied in the flow (503) as the resource pool ID ( 601), the value registered in NEID (302) is registered in resource NEID (602), the value registered in port ID (303) is registered in resource port ID (603), and the maximum bandwidth (304). The registered value is registered (pasted) in the maximum bandwidth (604) and the value registered in the usage bandwidth (305) is registered (504) in the usage bandwidth (605). After pasting, the control unit (202) registers the same value as the value registered in the maximum bandwidth (304) in the use bandwidth (305) of the copy source record in the physical network object management table (205) (505). .

  Here, when the resource pool is registered as shown in the above flows (503) to (505) from the information of the physical network object management table (205) of FIG. 3A, the resource information shown in FIG. It is registered in the object management table (207). FIG. 6B shows a conceptual diagram of registered resources.

When there is no unconfirmed record in the flow (502), the control unit (202) confirms the record registered in the link management table (206) from the record registered in the top line (506), It is confirmed whether there is a record (unconfirmed record) that has not been processed after the flow (506). If there is an unconfirmed record, the control unit (202) displays the link management table (206) in which the record is registered. ) Is copied (507) and copied to the resource link management table (208) (508).
That is, the control unit (202) uses the value registered in the link ID (401) of the link management table (206) copied in the flow (507) as the resource link ID (701) of the resource link management table. The value registered in the ID (402) is the resource pool ID (702), the value registered in the A point port ID (403) is the A point resource port ID (703), and the Z point port ID (404). Is registered (pasted) in the Z point resource port ID (704) (508).

Here, when the resource pool is registered as shown in the flow (507) to (508) from the information of the link management table (206) of FIG. 4, the resource information shown in FIG. ). FIG. 7B is a conceptual diagram showing resources registered in the resource object management table (207) of FIG. 6A and the resource link management table 208 of FIG. 7A.
When there is no unconfirmed record in the flow (506), the control unit (202) ends the process.

  FIG. 8 shows the physical network object management table (205) and the resource object management table (207) after the flow processing of FIG. Since the control unit (202) updates the use band value of the physical network management table (205) in the flow (505), the use band (305) of the physical network object management table (205) changes to 200M. doing.

  FIG. 9 shows a flowchart for allocating slices from the resource pool. Logical resources such as resources NE and resource ports registered in the resource object management table (207) and the resource link management table (208) are allocated to slices associated with the resource pool on a one-to-one basis, and a virtual network, that is, a slice Create

  When there is a slice allocation request (902) from the operator of the network monitoring apparatus (101), the control unit (202) searches the resource object management table (207) and displays a list of registered resource pools as an operator. Return to (management terminal (104 or 105)) (903). This list is displayed on the management terminal (104 or 105). The operator selects one resource pool to which a slice is to be assigned from the list of resource pools (904). When the resource pool is selected, the control unit (202) receives it, searches the resource object management table (207), and acquires all the resource NEIDs from the record that matches the resource pool ID of the selected resource pool. And a list of resource NEs are returned (905). The operator selects all the resource NEs to be assigned to the slice from the list of resource NEs using the management terminal (104 or 105) (906). When the resource NE is selected, the control unit (202) receives it, searches the resource object management table (207), and selects all the resource ports from the record that matches one of the resource NEIDs of the selected resource NE. It is acquired and returned to the management terminal (104 or 105) as a list of resource ports (907). The operator uses the management terminal (104 or 105) to select all resource ports to be assigned to the slice from the resource port list (908). Further, the operator decides a bandwidth to be allocated for each resource port selected by the management terminal (104 or 105) (909). When a resource port is selected by the management terminal (104 or 105), the control unit (202) receives it, searches the resource link management table (208), and selects one of the resource port IDs of the selected resource port. However, all resource link IDs are acquired from records that match both the point A resource port ID and the point Z resource port ID, all resource link IDs are acquired, and a list of resource links is sent to the management terminal (104 or 105). Return (910). The operator uses the management terminal (104 or 105) to select all resource links to be assigned to the slice from the list of resource links (911). Next, the control unit (202) receives the information selected by the operator from the management terminal (104 or 105), displays the resource pool, resource NE, resource port information, and bandwidth selected by the operator in the virtual object management table (209). The resource link information selected by the operator is registered in the virtual link management table (210) and managed as a slice (912).

  Here, FIG. 10A and FIG. 10B show, for example, the resource object management table (207) shown in FIG. 6A and the resource link management table (208) shown in FIG. 7A. 9 shows a virtual object management table (209) and a virtual link management table (210) when slices are allocated according to the flow of FIG.

Hereinafter, an example of forming FIGS. 10A to 10C in accordance with the flow of FIG. 9 will be described.
In the flow (903), the control unit (202) searches the resource object management table (207), acquires the resource pool with the resource pool ID1, and displays the list. In flow (904), the operator selects a resource pool with resource pool ID1. The control unit (202) acquires the resource NEs of the resource NEIDs 1, 2, 3, and 4 from the record of the resource pool ID1, and displays the list as a list. The operator selects resource NEID1 and resource NE2. The control unit (202) acquires resource ports with resource port IDs 1.1, 1.2, 2.1, and 2.2 from the record with resource NEID1 or 2, and displays the list. The operator selects resource ports with resource port IDs 1.2 and 2.1. Also, 100M is allocated as the bandwidth of the resource port with resource port IDs 1.2 and 2.1. The control unit (202) searches the resource link management table (208), and from the record in which either of the resource port ID 1.2 or 2.1 is registered in the point A resource port ID and the point Z resource port ID, Resource links with resource link ID1 are acquired and displayed in a list. The operator selects a resource link with resource link ID1.

  In the virtual object management table (209), the control unit (202) selects the same value as the selected resource pool ID for the slice ID (1001) and the same value as the selected resource NEID for the virtual NEID (1002). The same value as the resource port ID is registered in the virtual port ID (1003), and the allocated bandwidth is registered in the maximum bandwidth (1004). In the virtual link management table (210), the same value as the selected resource pool ID is set as the slice ID (1005), the same value as the selected resource link ID is set as the virtual link ID, and the point A of the selected resource link ID The same values as the resource port and the Z point resource port are registered in the A point virtual port ID and the Z point virtual port ID.

  FIG. 10C shows slices registered in the above example. FIG. 11 shows the resource object management table (207) after the slice assignment in FIG. 10 (C). The used bandwidth of the resource port IDs 1.2 and 2.1 assigned to the slice with the bandwidth of 100M is 100M.

  Each ID information of the virtual object management table (209) and virtual link management table (210) registers the same value as the ID value of the corresponding resource object management table (207) and resource link management table (208). However, the ID provision rule may be determined separately and registered, and the values need not necessarily be the same.

  Here, a new resource pool can be registered from the resources registered in the resource pool. Select a resource pool as a registration source, select a resource to be registered (for example, resource NE) from the resource pool of the registration source, and add a new record to the resource object management table (207) or the resource link management table (208) . At this time, a new resource pool may be created, a new resource pool ID may be assigned and a record may be registered, or an addition may be made to an already registered resource pool (ID assigned).

  Note that the processing of returning each list of the flow (905) and the flow (907) may be collectively returned. For example, in this case, the control unit (202) receives the selected resource pool ID from the management terminal, searches the resource object management table, and selects the resource NEID and resource port ID from the record that matches the selected resource pool ID. Or a plurality of predetermined numbers may be acquired and sent to the management terminal as a resource NEID / resource port ID list. Then, the control unit (202) uses the management terminal to select one or more resource NEIDs selected from the resource NEID / resource port ID list, one or more resource port IDs, and an allocated bandwidth for each selected resource port ID. The resource link management table is searched, and all or a plurality of predetermined resource link IDs are acquired from the record that matches the combination of the selected one or more resource NEIDs and one or more resource port IDs. The resource link ID list may be sent to the management terminal.

FIG. 12 shows an example of the resource object management table (207) and the resource link management table (208) when a new resource pool is registered from the resources of the existing resource pool.
Register the resource pool with ID = 2 from the registration source resource pool (ID = 1) as the new resource pool, register the resource NE with ID = 5 and ID = 6 as the resource NE, and each as the resource port belonging to the NE Registered resource ports with ID = 5.1, 5.2, ID = 6.1, 6.2, and registered resource link ID = 5 between resource port ID = 5.2 and ID = 6.1 This indicates that a new resource pool ID = 2 has been registered.

FIG. 13 shows an example of virtual network management using the network monitoring apparatus of this embodiment.
It is assumed that the communication carrier A is a management user of a network composed of physical devices (1302) and a network monitoring device (1301). The physical resource is managed in the configuration information by each table of the physical network management unit (1303). The resource pool A (1304), which manages the physical network resources as logical resources, includes all resources corresponding to the physical network resources. The communication carrier A allocates network resources to be managed by itself from the resource pool A to the slice A (1305).
Here, the resources of the resource pool A remaining without being assigned to the slice A (1305) can be newly registered and assigned. The communication carrier B does not have a physical device or network, but is an operator that manages a virtual network and provides a service. Communication carrier A registers a new resource pool B (1306) from resource pool A (1304) for communication carrier B, and causes communication carrier B to manage this, thereby remaining resources as communication carrier A The communication carrier B can freely create and operate a virtual network, that is, a slice B (1307) using the borrowed resources.

  FIG. 14 shows an example of a sequence when communication carrier A lends resources to communication carrier B. There is a request from the communication carrier B (1401) to lend a virtual resource to the communication carrier A (1402) (1405). The communication carrier A requests the network monitoring device (1403) to register the resource pool for the communication carrier B, and the network monitoring device (1403) registers it (1406). The communication carrier A requests the network monitoring device (1403) to grant the management authority of the resource pool to the communication carrier B, and the network monitoring device (1403) lends the resource pool to the communication carrier B (1407).

  FIG. 15 shows an example of a flowchart of the virtual resource management of the communication carrier A. Here, the resource pool (for example, resource pool A (1304) in FIG. 13) corresponding to the resource of the physical network may be referred to as a base resource pool. The communication carrier A uses the management terminal 1 to select, from the base resource pool, a virtual network to be managed by the communication carrier A, that is, a resource to be allocated to a slice, from the base resource pool when the network monitoring apparatus of this embodiment is operated (1502). . Communication carrier A confirms the remaining resources of the base resource pool by the management terminal (1503), and if there is no remaining resources (1503 remaining), slice allocation fails (1504), and if there are remaining resources (1504 remaining). Yes) Slice assignment succeeds.

  FIG. 16 shows an example of a flowchart of the virtual resource management of the communication carrier B. The communication carrier B confirms whether there is a resource pool that can be managed by the management terminal (1602). If there is no resource pool (no 1602), the communication carrier B issues a resource pool lending request to the communication carrier A (1603). Communication carrier A newly registers a resource pool for communication carrier B by the management terminal. In a case where the remaining amount of resources in the resource pool managed by the communication carrier A is insufficient for the resource requested by the communication carrier B, the resource pool registration for the communication carrier B fails (registration failure at 1604, 1606), Otherwise, the resource pool for the communication carrier B is registered (registration succeeded in 1604), and the communication carrier B is managed by the management terminal from the resource pool lent to itself to the virtual network managed by itself, that is, the slice. In order to allocate a resource, a resource is selected from the lent resource pool (1605). The communication carrier B checks whether the resource to be allocated to the slice exists in the resource pool lent to the slice by the management terminal (1607), and if there is no remaining resource (no remaining 1607), the slice allocation fails. If there is a remaining resource (1608), slice allocation is executed (1609).

  In the first embodiment, the flowchart of slice allocation is shown in FIG. 9, but the already allocated slice information may be updated, that is, the registered virtual resource may be deleted and returned to the resource pool associated with the slice. Further, a virtual resource may be allocated from the corresponding resource pool additionally to the allocated slice.

  Similarly, the information of the registered resource pool may be updated, that is, the resource information of the registered resource pool may be deleted and the resource information may be returned to the registration source resource pool. Further, the resource information of the registration source resource pool may be further added to the registered resource pool.

  In the first and second embodiments, only the configuration management information as shown in FIG. 2, that is, the NE, the port, and the link is mentioned, but other information constituting the network may be handled. For example, when two different NEs can be traced by a link, it may be defined as management information called a path connecting the NEs, and the path information may be applied to this embodiment.

[Effect of Example]
According to this embodiment, as a network resource abstraction management technology, a “resource” that abstracts virtual and physical models is established as a “pooled” management model, and is managed centrally using a unified model. Can be possible.
In addition, according to the present embodiment, as a network resource abstraction management technology, “resources” obtained by abstracting virtual and physical models can be “pooled” to be managed in a unified model, Establishing a method for allocating resources for the entire network, and renting in the form of a resource pool rather than allocating the network resources themselves, so that the work of the lending source can be reduced and the resources received by the recipient user can be freely customized Therefore, it became possible to respond flexibly and promptly to various requests.

[Appendix]
In addition, this invention is not limited to an above-described Example, Various modifications are included. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. Further, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. Further, it is possible to add, delete, and replace other configurations for a part of the configuration of each embodiment.
Each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit. Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor. Information such as programs, tables, and files for realizing each function can be stored in a memory, a hard disk, a recording device such as an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.
Further, the control lines and information lines indicate what is considered necessary for the explanation, and not all the control lines and information lines on the product are necessarily shown. Actually, it may be considered that almost all the components are connected to each other.

101 Network Monitoring Device 102 Physical Network 103 NE (Node Element)
104 communication carrier A management terminal 105 communication carrier B management terminal 106 wired or wireless connection line

Claims (10)

A network monitoring device,
A control unit;
A resource object management table in which resource pool ID, resource NEID, resource port ID, resource port maximum bandwidth, resource port use bandwidth are stored correspondingly;
A resource link management table in which resource link IDs, resource pool IDs, and resource port IDs of ports at both ends of the resource link are stored correspondingly;
A virtual object management table in which slice IDs, virtual NEIDs, virtual port IDs, and virtual port maximum bandwidths of slices, which are virtual networks logically constructed using all or part of resources, are stored correspondingly ,
A virtual link management table in which slice IDs, virtual link IDs, and virtual port IDs of ports at both ends of the virtual link are stored correspondingly;
With
The controller is
When there is a slice allocation request, the resource object management table is searched, a list of registered resource pools is sent to the management terminal,
The selected resource pool ID is received from the management terminal, the resource object management table is searched, and the resource NEID and resource port ID are all or a plurality of predetermined numbers from the records that match the selected resource pool ID. Obtain and send to the management terminal as a resource NEID / resource port ID list,
The resource link receives one or more resource NEIDs selected from the resource NEID / resource port ID list, one or more resource port IDs, and an allocated bandwidth for each selected resource port ID by the management terminal, and the resource link Search the management table, and acquire all or a plurality of predetermined resource link IDs from the record that matches the combination of the selected one or more resource NEIDs and one or more resource port IDs, as a resource link ID list , Send to the management terminal,
The management terminal receives one or more resource link IDs selected from the resource link ID list,
Register and select the selected resource pool ID, resource NEID, resource port ID, and allocated bandwidth in the slice ID, virtual NEID, virtual port ID, and virtual port maximum bandwidth of the virtual object management table, respectively. The resource pool ID, the resource link ID, and the resource port ID of the port at both ends of the resource link are respectively registered in the slice ID, the virtual link ID, and the port at both ends of the virtual link in the virtual link management table, A virtual object management table and a network monitoring apparatus that allocates slices according to the virtual object management table.
The network monitoring device according to claim 1,
The controller is
The management terminal receives one or more resource NEIDs selected from the resource NEID list, searches the resource object management table, and selects all resource port IDs from records that match the selected one or more resource NEIDs. Or, obtain a plurality of predetermined, send as a resource port ID list to the management terminal,
The management terminal receives one or a plurality of resource port IDs selected from the resource port ID list and the allocated bandwidth for each selected resource port ID, searches the resource link management table, and selects the selected resource A network monitoring apparatus, wherein all or a plurality of predetermined resource link IDs are acquired from a record whose port ID matches a resource port ID, and sent to the management terminal as the resource link ID list.
The network monitoring device according to claim 1,
A physical network object management table in which network ID, NEID, port ID, port maximum bandwidth, and port usage bandwidth, which are identification information of the physical network, are stored correspondingly
A link management table in which link IDs, network IDs, and port IDs of ports at both ends of the link are stored correspondingly;
With
The controller is
The values registered in the network ID, NEID, port ID, maximum bandwidth, and used bandwidth of the physical network object management table are used as the resource pool ID, resource NEID, resource port ID, maximum bandwidth, and used bandwidth of the resource object management table. And register each
Register the maximum bandwidth in the bandwidth used for the copy source record in the physical network object management table,
The values registered in the link ID of the link management table, the network ID, and the port IDs of the ports at both ends of the link are used as the resource link ID, the resource pool ID, and the resource ports of the ports at both ends of the resource link. A network monitoring apparatus that registers each ID.
The network monitoring device according to claim 1,
The controller is
The network monitoring apparatus, wherein the allocated bandwidth is stored in a data use bandwidth for the corresponding resource pool ID, resource NEID, resource port ID, and maximum bandwidth of the resource object management table after the slice is allocated. .
The network monitoring device according to claim 1,
The controller is
From the resources registered in the resource object management table and the resource link management table, a resource pool ID to be registered, a resource NEID and a resource port ID to be registered are selected, and the resource object management table or the resource link management table A network monitoring device characterized in that a new resource pool is created, a new resource pool ID is assigned and a record is registered, or an additional registration is made with an already registered resource pool ID.
A virtual network management method in a network monitoring device, comprising:
The network monitoring device
A control unit;
A resource object management table in which resource pool ID, resource NEID, resource port ID, resource port maximum bandwidth, resource port use bandwidth are stored correspondingly;
A resource link management table in which resource link IDs, resource pool IDs, and resource port IDs of ports at both ends of the resource link are stored correspondingly;
A virtual object management table in which slice IDs, virtual NEIDs, virtual port IDs, and virtual port maximum bandwidths of slices, which are virtual networks logically constructed using all or part of resources, are stored correspondingly ,
A virtual link management table in which slice IDs, virtual link IDs, and virtual port IDs of ports at both ends of the virtual link are stored correspondingly;
With
The controller is
When there is a slice allocation request, the resource object management table is searched, a list of registered resource pools is sent to the management terminal,
The selected resource pool ID is received from the management terminal, the resource object management table is searched, and the resource NEID and resource port ID are all or a plurality of predetermined numbers from the records that match the selected resource pool ID. Obtain and send to the management terminal as a resource NEID / resource port ID list,
The resource link receives one or more resource NEIDs selected from the resource NEID / resource port ID list, one or more resource port IDs, and an allocated bandwidth for each selected resource port ID by the management terminal, and the resource link Search the management table, and acquire all or a plurality of predetermined resource link IDs from the record that matches the combination of the selected one or more resource NEIDs and one or more resource port IDs, as a resource link ID list , Send to the management terminal,
The management terminal receives one or more resource link IDs selected from the resource link ID list,
Register and select the selected resource pool ID, resource NEID, resource port ID, and allocated bandwidth in the slice ID, virtual NEID, virtual port ID, and virtual port maximum bandwidth of the virtual object management table, respectively. The resource pool ID, the resource link ID, and the resource port ID of the port at both ends of the resource link are respectively registered in the slice ID, the virtual link ID, and the port at both ends of the virtual link in the virtual link management table, A virtual object management table and a virtual network management method for allocating slices according to the virtual object management table.
The virtual network management method according to claim 6,
The controller is
The first resource pool includes all resources corresponding to physical network resources, and the management terminal of the first communication carrier allocates network resources to be managed by itself from the first resource pool to the first slice. ,
With respect to the remaining resources of the first resource pool that remain without being assigned to the first slice, the management terminal of the first communication carrier makes a new one from the first resource pool to the second communication carrier. Register two resource pools, lend them to the second communication carrier,
The management terminal of the second communication carrier allocates a second slice using the second resource pool borrowed from the first communication carrier.
The virtual network management method according to claim 7,
When a resource pool lending request is made from the management terminal of the second communication carrier to the management terminal of the first communication carrier,
The management terminal of the first communication carrier requests the network monitoring device to register the resource pool for the second communication carrier, and the network monitoring device sets the resource pool for the second communication carrier. Register,
The management terminal of the first communication carrier requests the network monitoring device to give the second communication carrier management authority of the resource pool for the second communication carrier, and the network monitoring device A virtual network management method, wherein a resource pool for the second communication carrier is lent out to a management terminal of a second communication carrier.
The virtual network management method according to claim 8, wherein
The management terminal of the first communication carrier selects from the first resource pool a resource to be allocated to a slice for management by the first communication carrier from the first resource pool,
The management terminal of the first communication carrier confirms the remaining resource of the first resource pool, and if there is no remaining resource, slice allocation fails, and if there is remaining resource, slice allocation is executed. Virtual network management method.
The virtual network management method according to claim 8, wherein
The management terminal of the second communication carrier confirms whether or not there is a resource pool that can be managed by itself, and if there is no resource pool, performs a resource pool lending request to the management terminal of the first communication carrier,
The resource pool for the second communication carrier newly registered by the management terminal of the first communication carrier and managed by the first communication carrier for the resource requested by the second communication carrier If the remaining resource amount is insufficient, the resource pool registration for the second communication carrier is failed, and if the remaining amount is insufficient, the resource pool for the second communication carrier is registered,
The management terminal of the second communication carrier checks whether or not the resource to be allocated to the slice exists in the resource pool lent to itself, and if there is no remaining resource, the slice allocation fails, and if there is a remaining resource, the slice A virtual network management method characterized by executing allocation.

Images