Priority determination device, priority determination method, and program

Abstract

This priority degree determination device includes: a collection unit that is configured to collect usage states of identification information for virtually dividing a network from each of a plurality of forwarding devices that are distributed across a plurality of domains; and a determination unit that is configured to determine, on the basis of the collected usage states, the degree of priority for use in the plurality of domains for each value usable as the identification information. By including these features, the priority degree determination device enables effective use of the identification information of the network that was virtually divided.

Description

[Technical field]

[0001] The present invention relates to a priority determination device, a priority determination method, and a program. [Background technology]

[0002] There are cases where multiple business company domains need to connect networks using limited ID resources for Layer 2 virtual separation protocol IDs such as VLAN IDs. With conventional technology, it is necessary to secure an ID area that can be shared between domains in advance. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2018-085585 A [Non-patent literature]

[0004] [Non-Patent Document 1] YAMAHA, "Setting tagged VLAN", [online], Internet <URL:https: / / network.yamaha.com / setting / switch_swx / simple_smart / switch_swx-command / tag_vlan> Summary of the Invention [Problem to be solved by the invention]

[0005] However, since the IDs of the Layer 2 virtual separation protocol are also used for different services in different domains, the commonly available ID range changes over time.

[0006] If the ID range reserved in advance is too large, the flexibility of the IDs that can be provided by other services will be reduced, and if the ID range is too small, it will be difficult to respond to sudden demand and will require operators to work.

[0007] The present invention has been made in consideration of the above-mentioned points, and has an object to enable effective use of identification information for virtually isolating networks. [Means for solving the problem]

[0008] In order to solve the above problem, the priority determination device has a collection unit configured to collect usage status of identification information for virtually separating a network from each of a plurality of forwarding devices distributed across a plurality of domains, and a determination unit configured to determine the priority of use in each of the plurality of domains for each value that can be used as the identification information based on the collected usage status. Effect of the Invention

[0009] This makes it possible to effectively utilize the identification information of a virtually separated network. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 illustrates an example of a configuration of a network system according to a first embodiment. [Diagram 2] 1 is a diagram illustrating an example of a hardware configuration of an arbitration device 10 according to a first embodiment. [Diagram 3] 4 is a flowchart illustrating an example of a processing procedure executed by the reconciliation device 10 in the first embodiment. [Figure 4] FIG. 11 is a diagram showing an example of information indicating the usage status of an ID. [Diagram 5] FIG. 4 is a diagram showing an example of notification information in the first embodiment. [Figure 6] FIG. 11 illustrates an example of a configuration of a network system according to a second embodiment. [Figure 7] 13 is a flowchart illustrating an example of a process procedure executed by the reconciliation device 10 in the second embodiment. [Figure 8]FIG. 11 is a diagram illustrating an example of notification information according to the second embodiment. [Figure 9] FIG. 13 illustrates an example of a configuration of a network system according to a third embodiment. [Figure 10] 13 is a flowchart illustrating an example of a process procedure executed by the reconciliation device 10 according to the third embodiment. [Figure 11] FIG. 13 is a diagram illustrating an example of notification information according to the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing an example of the configuration of a network system in a first embodiment. In FIG. 1, the network system includes a transfer device 20a, a transfer device 20b, an NEF device 30a, an NEF device 30b, an arbitration device 10, and the like. Hereinafter, when the transfer device 20a and the transfer device 20b are not distinguished from each other, they will be referred to as "transfer device 20". Furthermore, when the NEF device 30a and the NEF device 30b are not distinguished from each other, they will be referred to as "NEF device 30".

[0012] The transfer device 20a is a switch or a router in a business company domain A (hereinafter referred to as "domain A"). The NEF device 30a is a device that functions as a NEF (Network Exposure Function) for domain A. The NEF device 30a is installed at the boundary of domain A and serves as a window for requests from outside domain A.

[0013] The transfer device 20b is a switch or a router in a business company domain B (hereinafter referred to as "domain B") that is separate from the business company domain B. The NEF device 30b is a device that functions as a NEF (Network Exposure Function) for domain B. The NEF device 30b is installed at the boundary of domain B and serves as a window for requests from outside domain B.

[0014] That is, in this embodiment, the transfer device 20a and the transfer device 20b are distributed across a plurality of domains (domains A and B).

[0015] The transfer device 20a and the transfer device 20b are interconnected by a VLAN. As the ID of the VLAN (hereinafter simply referred to as "ID"), a value that is available in common in both domains within the range of IDs that can be used is used. In addition, each transfer device 20 also accommodates VLANs of other services in the domain to which it belongs.

[0016] The arbitration device 10 is one or more computers connected to each transfer device 20 and each NEF device 30 via a network. The arbitration device 10 arbitrates IDs to be used for VLANs. More specifically, the arbitration device 10 collects the usage status (consumption status) of IDs in each domain, and notifies each domain of IDs that should be used preferentially over other services in the domain. This allows the IDs to be used effectively.

[0017] The arbitration device 10 has a usage status collection unit 11, a consumption priority determination unit 12, and a consumption priority notification unit 13. Details of each unit will be made clear in the explanation of the processing procedure.

[0018] Fig. 2 is a diagram illustrating an example of a hardware configuration of the arbitration device 10 in the first embodiment. The arbitration device 10 in Fig. 2 includes a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, and an interface device 105, which are all connected to each other via a bus B.

[0019] A program for implementing the processing in the arbitration device 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 storing the program is set in the drive device 100, the program is installed from the recording medium 101 via the drive device 100 into the auxiliary storage device 102. However, the program does not necessarily have to be installed from the recording medium 101, but may be downloaded from another computer via a network. The auxiliary storage device 102 stores the installed program as well as necessary files, data, and the like.

[0020] When an instruction to start a program is received, the memory device 103 reads out the program from the auxiliary storage device 102 and stores it. The CPU 104 executes functions related to the arbitration device 10 in accordance with the program stored in the memory device 103. The interface device 105 is used as an interface for connecting to a network.

[0021] The usage status collecting unit 11, the consumption priority determining unit 12, and the consumption priority notifying unit 13 in FIG. 1 are realized by processing executed by the CPU 104 of one or more programs installed in the arbitration device 10.

[0022] The following describes the processing procedure executed by the arbitration device 10. Fig. 3 is a flowchart for explaining an example of the processing procedure executed by the arbitration device 10 in the first embodiment. The processing procedure in Fig. 3 is executed at multiple timings, for example, periodically.

[0023] In step S101, the usage status collector 11 collects (acquires) information indicating the usage status of IDs in each domain (information on consumed and released IDs) from each of the transfer device 20a and the transfer device 20b.

[0024] Fig. 4 is a diagram showing an example of information indicating the usage status of the ID. As shown in Fig. 4, in step S101, for each value included in the range that the ID can take, information is collected that indicates whether or not the value is being used as an ID (unused). Note that in this embodiment, an example is shown in which there is one transfer device 20 facing domain A and domain B in each domain. However, in a certain domain, when multiple transfer devices 20 face each other, the usage status collector 11 collects information indicating the usage status of the ID from the multiple transfer devices 20, and derives the usage status in the entire range of values ​​that the ID can take based on the result.

[0025] Next, the consumption priority determination unit 12 determines the consumption priority of the ID being used in both domain A and domain B as “high” (S102). The consumption priority refers to the priority regarding the use (consumption) of the ID in domain A and domain B, and means that the ID with the highest consumption priority value should be used first.

[0026] Next, the consumption priority determination unit 12 determines the consumption priority of an ID that is in use only in either domain A or domain B as "low" (S103). The consumption priority of an ID that is in use only in one is made lower than the consumption priority of an ID that is in use by both (i.e., it is made easier to assign to a VLAN between both) because an ID that is in use only in one can be used by both if that one is released. Therefore, the ID (value) that is in use by a larger number of domains has a higher consumption priority.

[0027] Next, the consumption priority determination unit 12 determines the consumption priority of the unused ID in both domain A and domain B as “unusable” (S104). “Unusable” is an example of the lowest priority and means that it cannot be used (use is prohibited).

[0028] Next, the consumption priority notification unit 13 transmits notification information including the result of the consumption priority determination in steps S102 to S104 to each domain (S105). At this time, the consumption priority notification unit 13 transmits the notification information to the NEF device 30 of each domain, rather than directly to the transfer device 20 of each domain. In other words, the notification information passes through the NEF device 30. Note that an interface for receiving the notification information is implemented in advance in each NEF device 30.

[0029] Fig. 5 is a diagram showing an example of the notification information in the first embodiment. As shown in Fig. 5, the notification information includes, for each value within a range that an ID can take, a consumption priority when the value is used as an ID.

[0030] The NEF device 30 of each domain evaluates the consumption priority of each ID included in the notification information and the priority of other services independently held within the domain with weighting, and judges whether to adopt the consumption priority included in the notification information. In both domains, the ID allocation is determined based on the notification information, so that the possibility that an "unusable" ID is used in each domain can be reduced. Therefore, the ID can be reserved for a layer 2 virtual separation protocol such as VLAN between domains. As a result, the ID can be used without waste, and the limited IDs can be effectively used. In other words, IDs can be managed more efficiently and while adapting to changes compared to the existing method. This can reduce the lead time for service provision and the frequency of equipment expansion, and can also reduce the workload of maintenance personnel.

[0031] Next, a second embodiment will be described. In the second embodiment, differences from the first embodiment will be described. Points not specifically mentioned in the second embodiment may be the same as those in the first embodiment.

[0032] Fig. 6 is a diagram showing an example of the configuration of a network system in the second embodiment. In Fig. 6, the same parts as those in Fig. 1 are given the same reference numerals, and the description thereof will be omitted.

[0033] In the second embodiment, a case where the forwarding device 20 of each domain has a VLAN conversion function will be described. Note that, in FIG. 6, only the forwarding device 20b appears to have the VLAN conversion function, but this shows a state in which the VLAN conversion function is used only in the forwarding device 20b, and the forwarding device 20a may also have the VLAN conversion function. Note that the VLAN conversion function refers to a function of converting an ID in the forwarding device 20. If the VLAN conversion function is used, even an ID used in at least one of the domains can be assigned to a VLAN between the domains. This is because, in the domain using the ID, the ID can be converted to an ID not used in the domain.

[0034] Fig. 7 is a flowchart for explaining an example of a processing procedure executed by the arbitration device 10 in the second embodiment. In Fig. 7, the same steps as those in Fig. 3 are given the same step numbers, and the description thereof will be omitted.

[0035] Following step S104, the consumption priority determination unit 12 determines whether or not there is an ID whose consumption priority is "unusable" in the determination results up to step S104 (S201). If there is a corresponding ID (i.e., if there is an ID that can be assigned between two domains) (Yes in S201), step S105 is executed. In this case, notification information having the configuration shown in FIG. 5 is transmitted.

[0036] If there is no corresponding ID (No in S201), the consumption priority determination unit 12 randomly selects one ID, giving priority to IDs whose consumption priority is "low" in the determination results up to step S104 (S202). That is, if there is one or more IDs whose consumption priority is "low", an ID whose consumption priority is "low" is selected at random. If there is no ID whose consumption priority is "low", an ID whose consumption priority is "high" is selected at random.

[0037] Next, the consumption priority determination unit 12 randomly selects an ID that is not in use by the domain in which the selected ID (hereinafter referred to as the "selected ID") is being used as a conversion destination ID (hereinafter referred to as the "conversion destination ID") in the domain in use (S203). If the consumption priority of the selected ID is "high", the conversion destination ID is selected for both domains. If the consumption priority of the selected ID is "low", the conversion destination ID is selected for one of the domains.

[0038] Next, the consumption priority determination unit 12 changes (rewrites) the consumption priority of the selected ID in the determination result up to step S104 to "unusable" (S204).

[0039] Next, the consumption priority notification unit 13 transmits notification information to which the conversion destination ID selected in step S203 is added for the rewritten determination result to the VNF device of each domain (S105). However, the conversion destination ID is added only to the notification information for the domain using the selected ID. Also, in the notification information for the domain using the selected ID, the consumption priority of the conversion destination ID is set to "unusable".

[0040] Fig. 8 is a diagram showing an example of notification information in the second embodiment. The notification information shown in Fig. 8 further includes a column of "VLAN conversion" in addition to the notification information shown in Fig. 5. The column of "VLAN conversion" is a column showing a conversion destination ID for a selected ID.

[0041] When the transfer device 20 of the domain that received the notification information shown in Figure 8 is assigned "1003" as the ID for the VLAN between the other domain, it converts "1003" to "2003" for communications related to that VLAN within its own domain.

[0042] As described above, according to the second embodiment, even if there is no common ID available between domains, it is possible to connect VLANs between domains by using the VLAN conversion function, making it easier to respond to sudden demand.

[0043] Next, a third embodiment will be described. In the third embodiment, differences from the first embodiment will be described. Points not specifically mentioned in the third embodiment may be the same as those in the first embodiment.

[0044] Fig. 9 is a diagram showing an example of the configuration of a network system in the third embodiment. In Fig. 9, the same parts as those in Fig. 1 are given the same reference numerals, and the description thereof will be omitted.

[0045] As shown in Fig. 9, in the third embodiment, a VLAN spanning three or more domains is considered. That is, in Fig. 9, a business company domain C (hereinafter, referred to as "domain C" 9) is added. Domain C includes a transfer device 20c and a NEF device 30c.

[0046] Fig. 10 is a flowchart for explaining an example of a processing procedure executed by the arbitration device 10 in the third embodiment. In Fig. 10, the same step numbers as in Fig. 3 are given to the same steps, and the explanations thereof are omitted. In step S101, the ID usage status of domain C is also collected.

[0047] Following step S101, the consumption priority determination unit 12 determines the number of domains in use for each ID as the consumption priority of the ID (S301). In this embodiment, the total number of domains is 3. Therefore, the consumption priority of an ID used in all domains is "3", the consumption priority of an ID used in two domains is "2", the consumption priority of an ID used in one domain is "1", and the consumption priority of an ID not used in any domain is "0".

[0048] Next, if there is an ID whose consumption priority is "0", the consumption priority determination unit 12 updates the consumption priority of that ID to "unusable" (S302).

[0049] Next, the consumption priority notification unit 13 transmits notification information including the above-mentioned determination result to each domain (S303). The notification information is transmitted to the NEF device 30 in the same manner as in step S105 of FIG.

[0050] Fig. 11 is a diagram showing an example of notification information in the third embodiment. As shown in Fig. 11, in the third embodiment, the consumption priority of each ID is expressed by an integer. The larger the value, the higher the consumption priority (the higher the priority should be given to allocation to other services).

[0051] The third embodiment may be combined with the second embodiment, in which case steps S201 to S205 in FIG. 7 may be executed following step S302 in FIG.

[0052] As described above, according to the third embodiment, it is possible to obtain the same effects as those of the above embodiments with respect to three or more domains.

[0053] In the first and second embodiments, the consumption priority of each ID may be determined in the same manner as in the third embodiment.

[0054] The above-described embodiments can also be applied to identification information other than a VLAN ID, so long as the identification information is for virtually separating a network.

[0055] In this embodiment, the arbitration device 10 is an example of a priority determination device, the usage status collection unit 11 is an example of a collection unit, and the consumption priority determination unit 12 is an example of a determination unit.

[0056] Although the embodiment of the present invention has been described in detail above, the present invention is not limited to such specific embodiment, and various modifications and variations are possible within the scope of the gist of the present invention described in the claims. [Explanation of symbols]

[0057] 10 Mediation device 11 Usage Collection Unit 12 Consumption priority determination unit 13 Consumption priority notification section 20a, 20b, 20c Transfer device 30a, 30b, 30c NEF equipment 100 Drive device 101 Recording media 102 Auxiliary storage device 103 Memory device 104 CPU 105 Interface device B Bus

Claims

1. A collection unit configured to collect usage status of identification information for virtually isolating a network from each of a plurality of forwarding devices distributed in a plurality of domains; a determination unit configured to determine a priority of use in each of the plurality of domains for each of the values ​​available as the identification information based on the collected usage status; A priority determination device comprising:

2. The determination unit is configured to give a higher priority to a value having a larger number of domains in use.

2. The priority determination device according to claim 1.

3. the determining unit is configured to, when there is no unused value in all the domains, select a value having the lowest priority and a value not used in the domain in which the value is being used as a conversion destination value in the domain; 3. The priority determination device according to claim 1 or 2.

4. A collection step of collecting usage status of identification information for virtually isolating a network from each of a plurality of forwarding devices distributed in a plurality of domains; a determination step of determining a priority of use in each of the plurality of domains for each of the values ​​usable as the identification information based on the collected usage status; A priority determination method characterized by being executed by a computer.

5. The determination step is to give a higher priority to a value having a larger number of domains in use.

5. The method of claim 4, wherein the priority is determined based on the number of priority determinations.

6. The determination step is, if there is no unused value in all domains, to select a value having the lowest priority and a value not used in the domain in which the value is being used as a conversion destination value in the domain; 6. The method of claim 4, wherein the priority is determined based on the priority of the first and second data.

7. 7. A program for causing a computer to execute the priority determination method according to claim 4.

Images