WO2024038609A1 - Passerelle, procédé de commande et programme de commande - Google Patents

Passerelle, procédé de commande et programme de commande Download PDF

Info

Publication number
WO2024038609A1
WO2024038609A1 PCT/JP2022/031453 JP2022031453W WO2024038609A1 WO 2024038609 A1 WO2024038609 A1 WO 2024038609A1 JP 2022031453 W JP2022031453 W JP 2022031453W WO 2024038609 A1 WO2024038609 A1 WO 2024038609A1
Authority
WO
WIPO (PCT)
Prior art keywords
function unit
network function
unit
traffic flow
resources
Prior art date
Application number
PCT/JP2022/031453
Other languages
English (en)
Japanese (ja)
Inventor
孝幸 中村
貴允 鳴海
Original Assignee
日本電信電話株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電信電話株式会社 filed Critical 日本電信電話株式会社
Priority to PCT/JP2022/031453 priority Critical patent/WO2024038609A1/fr
Publication of WO2024038609A1 publication Critical patent/WO2024038609A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS

Definitions

  • the present invention relates to a gateway, a control method, and a control program.
  • FIGS. 8 and 9 are diagrams explaining the existing technology.
  • RSS Receiveive Side Scaling
  • RPS Receiveive Packet Steering
  • Linux registered trademark
  • This function enables resource sharing settings (FIG. 8) that allows sharing of resources for packet processing in each container, and resource exclusive settings (FIG. 9) that allocates dedicated resources to each container based on quality requirements.
  • FIG. 10 is a diagram explaining the existing technology.
  • an existing technology in a system with multiple web applications on containers, when the load on some containers increases, the impact of response delays on other containers' web applications can be minimized, while at the same time it is There are techniques to improve processing delays.
  • this method in the default state, specific resources are allocated to each container (left diagram in Figure 10), the load status of each container is monitored, and if a container becomes overloaded, the resource allocation is canceled, Make all resources available (right diagram in Figure 10).
  • the present invention has been made in view of the above, and when communications with different quality requirements coexist within a VPN GW, the present invention eliminates the influence of communications with low quality requirements on communications with high quality requirements, and reduces resource usage.
  • the purpose is to provide a gateway, control method, and control program that can be used effectively.
  • a control device is a gateway for a virtual private network service, and has a first network function that functions for communication between networks with predetermined quality requirements. a second network function unit that functions to communicate between networks with higher quality requirements than the first network function unit, a monitoring unit that monitors resources within the gateway, and the first network function unit. a measurement unit that measures the traffic flow rate of the first network function unit; a setting unit that sets a limit on the traffic flow rate of the first network function unit; and an instruction to the first network function unit and/or the second network function unit.
  • the first network function unit and the second network function unit can Control is performed between a default state in which resources are shared and a high load state in which resources are separated between the first network function unit and the second network function unit, and the high load state is shifted to the default state.
  • the traffic flow rate of the first network function unit is limited according to the traffic flow rate of the first network function unit, and the traffic flow rate of the first network function unit and the second network function unit are controlled within the gateway.
  • a control unit that gradually eases the restriction on the traffic flow rate of the first network function unit according to the resource usage rate of the second network function unit after sharing all the resources of the first network function unit. shall be.
  • FIG. 1 is a diagram showing an example of the configuration of a VPN GW.
  • FIG. 2 is a diagram illustrating the flow of control processing according to the embodiment.
  • FIG. 3 is a diagram illustrating the flow of control processing according to the embodiment.
  • FIG. 4 is a block diagram showing an example of the configuration of the VPN GW according to the embodiment.
  • FIG. 5 is a flowchart showing the processing procedure of the control processing according to the embodiment.
  • FIG. 6 is a flowchart showing a processing procedure of control processing according to the embodiment.
  • FIG. 7 is a diagram showing an example of a computer that implements a VPN GW by executing a program.
  • FIG. 8 is a diagram explaining the existing technology.
  • FIG. 9 is a diagram explaining the existing technology.
  • FIG. 10 is a diagram illustrating the existing technology.
  • FIG. 1 is a diagram showing an example of the configuration of a VPN GW.
  • the embodiment assumes a VPN GW 10 for a VPN service realized by combining functional containers.
  • the VPN GW 10 according to the embodiment is allocated with compute resources such as a predetermined CPU (Central Processing Unit) based on requests from each VPN user (corporate, etc.), and internally stores requests from the VPN users, etc.
  • Functional containers are arranged based on
  • Container 11C is equipped with NAT (Network Address Translator) / FW (Fire Wall) functions that are applied only to communication with the Internet, and terminates the VPN (tunnel) that connects to the user base.
  • NAT Network Address Translator
  • FW Fire Wall
  • VPN GW communications with different quality requirements, such as high-priority communication and low-priority communication, coexist.
  • the first quality control is to eliminate the influence of communication with high quality requirements (high priority communication) by communication with low quality requirements (low priority communication such as best effort communication).
  • the second quality control is to transfer low-priority communication as much as possible in order to effectively utilize the transfer processing capacity of the VPN GW 10, if there is margin in the processing capacity of the VPN GW 10.
  • the transfer system controls the allocation of resources such as CPUs that can be used, thereby eliminating the influence of communication with low quality requirements on communication with high quality requirements. However, it enables effective use of resources.
  • FIGS. 2 and 3 are diagrams explaining the flow of control processing according to the embodiment.
  • the default state will be explained.
  • the VPN GW 10 normally shares all resources with each container ((1) of Figure 2), and uses the maximum resources for each communication. processing.
  • the VPN GW 10 transitions from the default state to the high load state when some resources become highly loaded ((2) in FIG. 2). Specifically, when the resource usage rate is high, the resources used for high-priority communication and low-priority communication are separated ((3) in Figure 2), and the minimum resources are allocated to the container through which low-priority communication passes. The remaining amount is allocated to the container through which high-priority communication passes. This allows the VPN GW 10 to reliably process high priority communication.
  • the VPN GW 10 confirms that the resource usage rate of high-priority communication is low, and shifts the high-load state to the default state ((4) in FIG. 3).
  • the VPN GW 10 measures the amount of traffic of low-priority communication transferred to the resource allocation state during high load. Then, the VPN GW 10 returns resource allocation to a state in which each container shares all resources as in the default state, while limiting the inflow of low-priority communication according to the measured amount ((5 in Figure 3) ).
  • the VPN GW 10 will perform NAT/FW when canceling ((C) in Figure 3).
  • resource allocation is returned.
  • the amount of traffic that can be transferred relative to the amount of resources allocated to a container varies depending on the packet size of the flowing traffic, so if you apply a limit based on the assumption of short packets that use a lot of resources, it may be an excessive limit. Therefore, we have adopted a method of setting limits according to the amount of traffic actually measured.
  • the VPN GW 10 gradually eases the restriction on the inflow of low-priority communication while monitoring the resource usage status ((6) in Figure 3), thereby avoiding excessively restricting low-priority communication. , to return to the default state without affecting transfer processing of high-priority communication.
  • VPN GW10 gradually eases the 10Mbps limit to 20Mbps, then 30Mbps while confirming that there is no spike in CPU usage, and finally increases the limit value until it becomes the same as the interface speed. It will be eased.
  • FIG. 4 is a block diagram showing an example of the configuration of the VPN GW 10 according to the embodiment.
  • the VPN GW 10 includes a low-priority communication NW function unit 11 (first network function unit), a high-priority communication NW function unit 12 (second network function unit), which is a container. section), high-priority/low-priority communication use NW function section 13 (second network function section), resource monitoring section 14 (monitoring section), flow rate measuring section 15 (measuring section), and flow rate limit setting section 16 ( a setting section), a resource allocation section 17 (allocation section), and a control determination section 18 (control section).
  • NW function unit 11 first network function unit
  • NW function unit 12 second network function unit
  • second network function unit which is a container. section
  • high-priority/low-priority communication use NW function section 13 second network function section
  • resource monitoring section 14 monitoring section
  • flow rate measuring section 15 measuring section
  • flow rate limit setting section 16 a setting section
  • resource allocation section 17 allocation section
  • control determination section 18 control section
  • the VPN GW 10 is realized by loading a predetermined program into a computer, etc., including ROM (Read Only Memory), RAM (Random Access Memory), CPU, etc., and having the CPU execute the predetermined program.
  • the VPN GW 10 has a communication interface that transmits and receives various information to and from other devices connected via a network or the like.
  • the low-priority communication use NW function unit 11 is a container equipped with functions applied to communications with low quality requirements, for example, a container equipped with a NAT/FW function applied only to communication with the Internet to ensure security. It is.
  • the high-priority communication usage NW functional unit 12 is a container equipped with functions applicable to communication with high quality requirements.
  • the high-priority/low-priority communication usage NW functional unit 13 is a container that has functions applied to communication with low quality requirements and communication with high quality requirements, such as a function to terminate a VPN (tunnel) connecting to a user base. It is a container loaded with.
  • the resource monitoring unit 14 monitors the usage rate of resources such as the CPU within the VPN GW 10.
  • the resource monitoring unit 14 notifies the control determining unit 18 (described later) of an overload alert when the resource usage rate of some CPUs or the like exceeds a predetermined threshold.
  • the resource monitoring unit 14 also processes the low-priority communication NW function unit 11, the high-priority communication NW function unit 12, and/or the high-priority/low-priority communication NW function unit 13 that has received an inquiry from the control determination unit 18. (hereinafter collectively referred to as the NW functional unit) returns the resource usage rate.
  • the flow rate measuring unit 15 measures the flow rate of traffic passing through each NW functional unit.
  • the flow rate measurement unit 15 returns the traffic flow rate of the NW function unit that was queried by the control determination unit 18.
  • the flow rate limit setting unit 16 limits the traffic flow rate to the instructed limit value for the instructed NW function unit based on the NW function unit and the limit value included in the instruction, in accordance with the instruction from the control determination unit 18. Input the settings.
  • the resource allocation unit 17 inputs settings to allocate the instructed amount of resources to the instructed NW functional unit based on the NW functional unit and resource amount included in the instruction, in accordance with the instruction from the control determination unit 18. .
  • the control determination unit 18 controls the resource monitoring unit 14, the flow rate measurement unit 15, the flow rate limit setting unit 16, and the resource allocation unit 17, thereby controlling the VPN GW 10 such as resource allocation, traffic flow measurement, and traffic flow rate restriction. conduct.
  • the control determination unit 18 performs control to either a default state or a high load state in which the resource usage rate is high. In the default state, the control determination unit 18 causes all the resources to be shared by each container (low-priority communication NW function unit 11, high-priority communication NW function unit 12, high-priority/low-priority communication NW function unit 13). .
  • control determination unit 18 determines the resources used by the high-priority communication NW function unit 12 and the high-priority/low-priority communication NW function unit 13 and the resources used by the low-priority communication NW function unit 11.
  • the minimum resources are allocated to the container through which the low-priority communication NW functional unit 11 passes.
  • control determination unit 18 limits the inflow of low-priority communication according to the traffic flow rate of low-priority communication, and causes each container to share resources as in the default state. , gradually ease the inflow restrictions for low-priority communications while monitoring resource usage.
  • the control determination unit 18 limits the traffic flow rate of the low priority communication NW function unit 11 according to the traffic flow rate of the low priority communication NW function unit 11.
  • the control determination unit 18 causes the low-priority communication NW function unit 11, the high-priority communication NW function unit 12, and the high-priority/low-priority communication NW function unit 13 to share all resources within the VPN GW 10. .
  • the control determination unit 18 limits the traffic flow rate of the low-priority communication NW function unit 11 in stages according to the resource usage rates of the high-priority communication NW function unit 12 and the high-priority/low-priority communication NW function unit 13. to alleviate it.
  • FIGS. 5 and 6 are flowcharts illustrating the procedure of control processing according to the embodiment.
  • the initial state is the default state.
  • the control determination unit 18 receives an overload alert from the resource monitoring unit 14 (step S1), it determines that a high load state exists (step S2), and determines resource allocation in the high load state. implement.
  • control determination unit 18 instructs the resource allocation unit 17 to minimize the allocated resources in the low-priority communication usage NW function unit 11 (step S3).
  • the control determination unit 18 instructs the resource allocation unit 17 to allocate low priority communication to NW function units other than the low priority communication use NW function unit (high priority communication use NW function unit 12 and high priority/low priority communication use NW function unit 13).
  • An instruction to allocate all resources other than the allocated resources of the priority communication use NW functional unit 11 is executed (step S4).
  • the control determination unit 18 inquires of the resource monitoring unit 14 about the resource usage rate of the high-priority communication usage NW function unit 12 and the high-priority/low-priority communication usage NW function unit 13, and obtains it (step S5).
  • the control determination unit 18 determines whether the resource usage rate obtained in step S5 is less than or equal to a predetermined threshold (step S6). If the resource usage rate acquired in step S5 is not below the predetermined threshold (step S6: No), the control determination unit 18 waits for a certain period of time (step S7), and returns to step S5.
  • step S6 determines whether to transition from the high load state to the default state. Then, the control determination unit 18 acquires the measured value of the traffic flow rate flowing through the low-priority communication NW function unit 11 from the flow rate measurement unit 15 (step S8).
  • the control determination unit 18 instructs the flow rate limit setting unit 16 to limit the traffic flow rate in the low priority communication NW function unit 11 to the measured value obtained in step S7 (step S9).
  • control determination unit 18 instructs the resource allocation unit 17 to allocate all the NW functional units (low-priority communication NW functional unit 11, high-priority communication NW functional unit 12, and high-priority/low-priority communication NW functional unit).
  • the instruction to share the allocated resource in step 13) among all resources is executed (step S10).
  • control determination unit 18 acquires the resource usage rates of the high-priority communication usage NW function unit 12 and the high-priority/low-priority communication usage NW function unit 13 from the resource monitoring unit 14 (step S11 ).
  • the control determination unit 18 determines whether the resource usage rate obtained in step S11 is less than or equal to a predetermined threshold (step S12). If the resource usage rate acquired in step S11 is not below the predetermined threshold (step S12: No), the control determination unit 18 waits for a certain period of time (step S13), and returns to step S11.
  • step S12 If the resource usage rate acquired in step S11 is less than or equal to the predetermined threshold (step S12: Yes), the control determination unit 18 instructs the flow rate restriction setting unit 16 to control the traffic that has already been set in the low-priority communication NW function unit 11. An instruction is issued to limit the flow rate to a new limit value that is increased by a certain amount from the limit value (step S14).
  • the control determination unit 18 causes the resource monitoring unit 14 to acquire the resource usage rates of the high-priority communication usage NW function unit 12 and the high-priority/low-priority communication usage NW function unit 13 (step S15).
  • the control determination unit 18 determines whether the resource usage rate obtained in step S14 is less than or equal to a predetermined threshold (step S16).
  • step S16 A case in which the resource usage rate obtained in step S15 is not below a predetermined threshold (step S16: No), that is, a case in which the resource usage rate obtained in step S14 is greater than the predetermined threshold will be described.
  • the control determination unit 18 instructs the flow rate limit setting unit 16 to limit the traffic flow rate to a new limit value that is reduced by a certain amount from the traffic flow limit value that has already been set in the low priority communication NW function unit 11. Execute (step S17).
  • the control determination unit 18 further limits the set traffic flow rate in the low-priority communication NW function unit 11 to free up the resources of the high-priority communication NW function unit 12 and the high-priority/low-priority communication NW function unit 13.
  • the control determination unit 18 waits for a certain period of time to ensure sufficient control (step S18), and returns to step S15.
  • step S16 If the resource usage rate acquired in step S15 is less than or equal to the predetermined threshold (step S16: Yes), the control determination unit 18 receives the measured value of the traffic flow rate flowing through the low-priority communication NW function unit 11 from the flow rate measurement unit 15. (Step S19).
  • the control determination unit 18 determines whether the measured value acquired in step S19 is smaller than the limit value (step S20).
  • step S19 If the measured value acquired in step S19 is not smaller than the limit value (step S20: No), the control determination unit 18 returns to step S14.
  • step S19 If the measured value acquired in step S19 is smaller than the limit value (step S20: Yes), the control determination unit 18 instructs the flow rate limit setting unit 16 to cancel the restriction on the traffic flow rate in the low priority communication NW function unit 11.
  • the instruction is executed (step S21) and the default state is restored.
  • the control determination unit 18 gradually eases the flow rate restriction of the low-priority communication usage NW function unit 11 while monitoring the resource usage status, thereby avoiding excessively restricting low-priority communication and , to return to the default state without affecting transfer processing of high-priority communication.
  • the VPN GW 10 provided to any VPN user is targeted.
  • the VPN GW 10 is equipped with a container having a VPN termination function and a NAT/FW function.
  • connection destination of the VPN GW 10 there is a connection from the container of the VPN termination function to the cloud service used by the VPN user. Furthermore, the GPN GW 10 is connected to the Internet via the NAT/FW function of the container, which is a VPN termination function.
  • Communication between the cloud and the user's base and communication between the Internet and the user's base have different transfer priorities. For example, communications between the cloud and user locations must be transferred with as little packet loss as possible, and communications between the Internet and user locations require no quality assurance.
  • communication between the cloud and the user base will be referred to as high-quality communication
  • communication between the Internet and the user base will be referred to as low-quality communication.
  • the VPN GW 10 is set in a default state so that each container can share and use the compute resources such as the CPU that the VPN GW 10 has.
  • the resource monitoring unit 14 detects that it has exceeded a threshold (for example, 90% or more) and issues an overload alert to the control determination unit 18. issue.
  • a threshold for example, 90% or more
  • the control determination unit 18 determines that a high load condition exists and executes the following instructions.
  • the control determination unit 18 instructs the resource allocation unit 17 to minimize the allocated resources in the container of the NAT/FW function used by low priority communication (such as allocating only one CPU). Then, the control determination unit 18 instructs the resource allocation unit 17 to allocate all resources other than the above-mentioned allocated resources in the container of the VPN termination function other than the NAT/FW function ((B) in FIG. 2).
  • the control determination unit 18 obtains the resource usage rate of the container of the VPN termination function used by the high priority communication from the resource monitoring unit 14. Here, it is assumed that this resource usage rate is below a certain threshold, for example, below 20%.
  • the control determination unit 18 acquires the measured value of the traffic flow rate flowing through the container of the NAT/FW function from the flow rate measurement unit 15. Here, it is assumed that the measured value is 10 Mbps. The control determination unit 18 instructs the flow rate limit setting unit 16 to limit the traffic flow rate in the container of the NAT/FW function to this measured value of 10 Mbps.
  • control determination unit 18 requests the resource allocation unit 17 to allocate resources in all VPN termination function containers and NAT/FW function containers. Implement instructions for sharing.
  • the control determination unit 18 acquires the resource usage rate of the container of the VPN termination function from the resource monitoring unit 14. Here, it is assumed that this resource usage rate is below a certain threshold, for example, below 20%.
  • the control determination unit 18 instructs the flow rate limit setting unit 16 to set a new limit value that is increased by a certain amount from the traffic flow rate limit value 10 Mbps that has already been set in the container of the NAT/FW function, in this case, 20 Mbps that is increased by 10 Mbps. Implement restrictive instructions.
  • the control determination unit 18 obtains the resource usage rate of the container of the VPN termination function from the resource monitoring unit 14. Here, it is assumed that this resource usage rate is below a certain threshold, for example, below 20%.
  • the control determination unit 18 acquires the measured value of the traffic flow rate flowing through the low-priority communication NW function unit 11 from the flow rate measurement unit 15. Assume that this measured value is approximately the same as the limit value of 20 Mbps. At this time, the control determination unit 18 again asks the flow rate limit setting unit 16 to set a new limit value, which is increased by a certain amount from the traffic flow rate limit value 20 Mbps that has already been set in the container of the NAT/FW function, in this case 10 Mbps. Implement the instruction to limit the speed to an increased 30Mbps.
  • control determination unit 18 controls the traffic by a certain amount at a time, while confirming that the resource usage rate is below a threshold value (for example, 20%), until the traffic flow rate of low-priority communication becomes a value sufficiently smaller than the limit value. Increase the flow limit value.
  • a threshold value for example, 20%
  • the control determination unit 18 instructs the flow rate limit setting unit 16 to cancel the restriction on the traffic flow rate in the low-priority communication usage NW function unit. Implement. With the above operations, the VPN GW 10 returns to the default state.
  • the VPN GW10 separates the resources used by high-priority communication and low-priority communication, and allocates minimal resources to the container through which low-priority communication passes. By allocating the rest to the container through which the high-priority communication passes, the influence of the low-priority communication on the transfer process of the high-priority communication is eliminated.
  • the VPN GW 10 uses the following means to transfer low-priority communication as much as possible in order to effectively utilize the transfer processing capacity when the VPN GW 10 has sufficient resources.
  • the VPN GW 10 allows each container to use the maximum amount of resources to process each communication by sharing all resources with each container.
  • the VPN GW 10 measures the amount of transferred low-priority communication traffic in the resource allocation state during high load, and limits the inflow of low-priority communication according to the measured amount while allocating resources in the same manner as the default. Have them shared.
  • the VPN GW 10 gradually releases the restriction on the inflow of low-priority communications while monitoring the resource usage, thereby forwarding high-priority communications. To transfer without affecting processing and without excessively restricting low priority communication.
  • the VPN GW 10 when communications with different quality requirements coexist within the VPN GW, resources can be used while eliminating the influence of communications with low quality requirements on communications with high quality requirements. Enables effective utilization. In other words, according to the VPN GW 10 according to the embodiment, it is possible to effectively utilize resources while reducing the situation where the quality of high-priority communication cannot be ensured due to resources being consumed by low-priority communication.
  • Each component of the VPN GW 10 shown in FIG. 4 is functionally conceptual, and does not necessarily need to be physically configured as shown.
  • the specific form of distributing and integrating the functions of the VPN GW10 is not limited to what is shown in the diagram, but all or part of it can be functionally or physically distributed in arbitrary units depending on various loads and usage conditions. Can be configured in a distributed or integrated manner.
  • each process performed in the VPN GW 10 may be implemented in whole or in part by a CPU and a program that is analyzed and executed by the CPU. Furthermore, each process performed in the VPN GW 10 may be implemented as hardware using wired logic.
  • FIG. 7 is a diagram showing an example of a computer that implements the VPN GW 10 by executing a program.
  • Computer 1000 includes, for example, a memory 1010 and a CPU 1020.
  • the computer 1000 also includes 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 parts are connected by a bus 1080.
  • the memory 1010 includes a ROM 1011 and a RAM 1012.
  • the ROM 1011 stores, for example, a boot program such as BIOS (Basic Input Output System).
  • Hard disk drive interface 1030 is connected to hard disk drive 1090.
  • Disk drive interface 1040 is connected to disk drive 1100.
  • Serial port interface 1050 is connected to, for example, mouse 1110 and keyboard 1120.
  • Video adapter 1060 is connected to display 1130, for example.
  • the hard disk drive 1090 stores, for example, an OS (Operating System) 1091, an application program 1092, a program module 1093, and program data 1094. That is, a program that defines each process of the VPN GW 10 is implemented as a program module 1093 in which code executable by the computer 1000 is written.
  • Program module 1093 is stored in hard disk drive 1090, for example.
  • a program module 1093 for executing processing similar to the functional configuration in the VPN GW 10 is stored in the hard disk drive 1090.
  • the hard disk drive 1090 may be replaced by an SSD (Solid State Drive).
  • the setting data used in the processing of the embodiment described above is stored as program data 1094 in, for example, the memory 1010 or the hard disk drive 1090. Then, the CPU 1020 reads out the program module 1093 and program data 1094 stored in the memory 1010 and the hard disk drive 1090 to the RAM 1012 as necessary and executes them.
  • program module 1093 and the program data 1094 are not limited to being stored in the hard disk drive 1090, but may be stored in a removable storage medium, for example, and read by the CPU 1020 via the disk drive 1100 or the like.
  • the program module 1093 and the program data 1094 may be stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.).
  • Program module 1093 and program data 1094 may then be read by CPU 1020 from another computer via network interface 1070.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Une GW VPN (10), lorsqu'elle passe d'un état de charge élevée, dans lequel des ressources sont séparées entre des ressources pour une unité de fonction NW ayant recours à une communication à faible priorité (11) et des ressources pour une unité de fonction NW ayant recours à une communication à haute priorité (12) et une unité de fonction NW ayant recours à une communication à haute priorité/faible priorité (13), à un état par défaut dans lequel toutes les ressources sont partagées par toutes les unités de fonction NW, limite le flux de trafic de l'unité de fonction NW ayant recours à une communication à faible priorité (11) selon le flux de trafic de l'unité de fonction NW ayant recours à une communication à faible priorité (11) et partage toutes les ressources entre l'unité de fonction NW ayant recours à une communication à faible priorité (11) et l'unité de fonction NW ayant recours à une communication à haute priorité (12) et l'unité de fonction NW ayant recours à une communication à haute priorité/faible priorité (13), puis assouplit progressivement la limite sur le flux de trafic de l'unité de fonction NW ayant recours à une communication à faible priorité (11) selon le taux d'utilisation de ressources de l'unité de fonction NW ayant recours à une communication à haute priorité (12) et de l'unité de fonction NW ayant recours à une communication à haute priorité/faible priorité (13).
PCT/JP2022/031453 2022-08-19 2022-08-19 Passerelle, procédé de commande et programme de commande WO2024038609A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/031453 WO2024038609A1 (fr) 2022-08-19 2022-08-19 Passerelle, procédé de commande et programme de commande

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/031453 WO2024038609A1 (fr) 2022-08-19 2022-08-19 Passerelle, procédé de commande et programme de commande

Publications (1)

Publication Number Publication Date
WO2024038609A1 true WO2024038609A1 (fr) 2024-02-22

Family

ID=89941759

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/031453 WO2024038609A1 (fr) 2022-08-19 2022-08-19 Passerelle, procédé de commande et programme de commande

Country Status (1)

Country Link
WO (1) WO2024038609A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016509412A (ja) * 2013-01-11 2016-03-24 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． ネットワークデバイスのためのネットワーク機能仮想化

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016509412A (ja) * 2013-01-11 2016-03-24 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． ネットワークデバイスのためのネットワーク機能仮想化

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"Internet Data Center Complete Guide, 2007 Autumn Edition", 29 October 2007, IMPRESS R&D, JP, ISBN: 978-4-8443-2472-0, article YAMAGOE, EIJI: "Balancing Quality Enhancement and Cost Reduction: Virtualizing Servers and Automating Operations", pages: 72 - 85, XP009553988 *
KATSUMA MIYAMOTO, HIROKI KANO, KOJI SUGISONO, SHINYA KAWANO: "Implementation and evaluation of virtual gateway function with XDP/eBPF", IEICE TECHNICAL REPORT, NS, IEICE, JP, vol. 120, no. 413 (NS2020-164), 25 February 2021 (2021-02-25), JP, pages 244 - 249, XP009552968 *
MIKI ENOKI, HIROSHI HORII, TAMIYA ONODERA: "Performance Evaluation of various Workloads’ Web Application on Docker Container Environment", DEIM FORUM 2017 H1-1, 27 February 2017 (2017-02-27), XP093140207 *

Similar Documents

Publication Publication Date Title
JP7509876B2 (ja) 高性能コンピューティング環境においてプライベートファブリックにおける輻輳制御のためのターゲットグループをサポートするためのシステムおよび方法
US9459904B2 (en) NUMA I/O aware network queue assignments
EP3025240B1 (fr) Gestion de ressource pour des domaines d'interconnexion de composants périphériques express
US20190140984A1 (en) Traffic and load aware dynamic queue management
US7079546B2 (en) Adaptive bandwidth throttling for network services
JP4214682B2 (ja) 計算機およびその入出力手段
US20080022016A1 (en) Network memory pools for packet destinations and virtual machines
US8989037B2 (en) System for performing data cut-through
KR102053596B1 (ko) Sdn 기반의 동적 네트워크 트래픽 분석을 통한 네트워크 슬라이싱 방법 및 장치
EP2843891B1 (fr) Gestion de file d'attente dynamique sensible à la charge et au trafic
AU2015361607A1 (en) Resource management method, host, and endpoint
WO2016049322A1 (fr) Classification de réseaux pour applications
Chaturvedi et al. An adaptive and efficient packet scheduler for multipath TCP
WO2024038609A1 (fr) Passerelle, procédé de commande et programme de commande
US11477122B2 (en) Technologies for selecting non-minimal paths and throttling port speeds to increase throughput in a network
US20180165114A1 (en) Control device and control method
US20210014165A1 (en) Load Distribution System and Load Distribution Method
Bresnahan et al. Managed gridftp
Lakshmi et al. I/O Device Virtualization in the multi-core era, a QoS perspective
JP7120059B2 (ja) 負荷分散システム及び負荷分散方法
US20240231940A9 (en) A non-intrusive method for resource and energy efficient user plane implementations
US20240134706A1 (en) A non-intrusive method for resource and energy efficient user plane implementations
WO2024041572A1 (fr) Procédé et appareil de traitement de service, dispositif, support et produit-programme
JP5796693B2 (ja) 安定化システム、安定化方法、コンピュータ装置及びプログラム
JP3708394B2 (ja) マルチプロセッサシステム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22955781

Country of ref document: EP

Kind code of ref document: A1