WO2016107418A1 - 云化网络通信路径的分配方法、装置及系统 - Google Patents

云化网络通信路径的分配方法、装置及系统 Download PDF

Info

Publication number
WO2016107418A1
WO2016107418A1 PCT/CN2015/097605 CN2015097605W WO2016107418A1 WO 2016107418 A1 WO2016107418 A1 WO 2016107418A1 CN 2015097605 W CN2015097605 W CN 2015097605W WO 2016107418 A1 WO2016107418 A1 WO 2016107418A1
Authority
WO
WIPO (PCT)
Prior art keywords
communication path
communication
sdn controller
information
network
Prior art date
Application number
PCT/CN2015/097605
Other languages
English (en)
French (fr)
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 EP15875096.8A priority Critical patent/EP3226495A4/en
Publication of WO2016107418A1 publication Critical patent/WO2016107418A1/zh
Priority to US15/637,814 priority patent/US20170300353A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/38—Flow based routing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/508—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement
    • H04L41/5096—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement wherein the managed service relates to distributed or central networked applications

Definitions

  • the embodiments of the present invention relate to the field of communications, and in particular, to a method, an apparatus, and a system for allocating communication paths in a cloud network.
  • Telecommunication node cloudization refers to deploying traditional physical chassis and board-based telecommunication nodes and applications to a general-purpose data center server in the form of software virtual machines (VMs) to provide various telecommunication services. In the industry, it is called Network Functions Virtualization (NFV).
  • a cloud network may include multiple data centers.
  • the telecommunication nodes and applications exist in the form of virtual machines (VMs) rather than in the form of a single board on traditional telecommunication hardware. Communication between nodes and nodes, and between different business processes within the same node, is represented as communication between VMs.
  • the prior art cannot correctly solve the problem of communication QoS between data centers deployed by the service virtual machine under the cloud network condition by the manual configuration method, in order to ensure that the VM is deployed after the cloud network is deployed.
  • QoS between communications must seek new communication QoS solution architectures and technologies.
  • the communication path allocation method, device and system in the cloud network provided by the embodiments of the present invention can ensure the QoS requirements of communication between different communication nodes in the cloud network, and Improve the utilization efficiency of bearer resources.
  • the method for allocating a communication path in a cloud network includes: a software-defined network SDN controller receives a communication path request message sent by a policy management device, where the communication path requests message carrying and policy management Address information of different communication nodes of the device communication connection, bandwidth requirement information of the communication path, and service quality QoS requirement information;
  • the SDN controller allocates, according to the address information of the different communication node, the bandwidth requirement information of the communication path, and the QoS requirement information, the communication node from the network resource managed by the SDN controller to meet the bandwidth requirement and Communication path for QoS requirements;
  • the SDN controller sends a message carrying the communication path to the bearer network forwarding device to establish a communication path between the different communication nodes by using the forwarding device.
  • a receiving unit configured to receive a communication path request message sent by the policy management apparatus, where the communication path request message carries address information of different communication nodes that are communicably connected with the policy management apparatus, bandwidth requirement information of the communication path, and quality of service QoS requirements information;
  • a path allocation unit configured to allocate, according to the address information of the different communication node, the bandwidth requirement information of the communication path, and the QoS requirement information, the bandwidth requirements and the QoS for the two communication nodes from the network resources managed by the SDN controller Communication path of demand;
  • a sending unit configured to send, to the forwarding device of the data center network, a forwarding flow table of the communication path, to establish a communication path between the different communication nodes by using the forwarding device.
  • a cloud network system includes a plurality of different communication nodes, a policy management device, an SDN controller, and a bearer network forwarding device, where
  • the policy management device is configured to acquire location information of different communication nodes and a communication path between them Wide requirements and QoS requirements, and send a communication path request message to the SDN controller;
  • the SDN controller is configured to receive a communication path request message sent by the policy management apparatus, determine a communication path according to the bandwidth requirement and the QoS requirement carried in the communication path request message, and send a message to the forwarding network forwarding device, and carry the determined Communication path information;
  • the bearer network forwarding device is configured to receive the message carrying the communication path information, and establish a bearer network communication path between the different communication nodes.
  • the communication path request message further carries migration event indication information of the migrated communication node and the migrated Address information before the communication node is migrated
  • the SDN controller deletes the migrated communication node according to the migration event indication information of the migrated communication node and the address information before the migration of the migrated communication node Communication path before migration of other communication nodes.
  • the SDN controller when the bandwidth requirement of the communication path between the different communication nodes and the QoS update are updated, the SDN controller receives an update communication path request message sent by the policy management apparatus;
  • the SDN controller re-allocates the different communication nodes from the network resources managed by the SDN controller according to the updated communication path request message and the updated bandwidth requirement and QoS Communication path.
  • the different communication nodes are respectively located in different data center networks.
  • the policy management device transmits the location information, the bandwidth requirement information, and the QoS requirement information of the different communication nodes to the SDN Controller, and the SDN Controller uniformly plans the forwarding path of the communication node, thereby ensuring the QoS requirements of the communication and avoiding the bearer network.
  • the waste of physical link resources improves network operation efficiency and resource utilization.
  • communication QoS can be ensured after the communication nodes of different data centers are deployed to the clouded data center.
  • FIG. 1 is a schematic structural diagram of a cloud network system according to an embodiment of the present invention.
  • FIG. 2 is a schematic diagram of an SDN network architecture according to an embodiment of the present invention.
  • FIG. 3 is a flow chart of a communication path allocation method of a cloud network.
  • FIG. 4 is an interaction diagram of a cloud network communication path allocation method.
  • FIG. 5 is an interaction flowchart of a cloud network communication path allocation method.
  • FIG. 6 is another interaction flow diagram of a clouded network communication path allocation method.
  • FIG. 7 is a schematic structural diagram of an SDN controller according to an embodiment of the present invention.
  • FIG. 8 is another schematic structural diagram of an SDN controller according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a cloud network system according to an embodiment of the present invention.
  • SDN Software Defined Network
  • the SDN controller stores the network topology information of the SDN.
  • the SDN controller can discover the network topology consisting of network switches, including software switches on the hypervisor and hardware switches in the data center cabinet.
  • SDN controller puts network programming mode from distributed mode (mutual The network device of the communication determines the communication path) and changes to the centralized mode.
  • the SDN controller can use OpenFlow to program the data forwarding of the network switch.
  • FIG. 1 is a schematic diagram of a cloud network architecture according to an embodiment of the present invention.
  • the telecommunications nodes and applications are in the form of virtual machines (VMs) rather than boards in traditional telecommunications hardware.
  • Communication between nodes and nodes, and between different business processes within the same node, is represented as communication between VMs.
  • VM1, VM2, VM3, and VM4 are all deployed on different servers in the data center.
  • Data center services are interconnected by different levels of switches such as Top Of Rack (TOR), Data Center Associative Switch (EOR), and core switches to provide communication channels.
  • Service gateways including firewalls, load balancers, etc., are generally attached to the core switch when networking.
  • the solid line with double arrows in the figure indicates the communication between VMs between nodes.
  • VMs can be deployed and migrated arbitrarily, which means that the traffic between VMs depends on the location of VM deployment. Traffic may pass through TOR, EOR and core switches, or may only pass TOR+EOR. , or only through the TOR, or traffic only inside the server. In order to meet the telecom service SLA standard, IP communication between these VMs must meet certain QoS requirements.
  • FIG. 1 is only an application scenario of the embodiment of the present invention.
  • FIG. 1 only illustrates a data center.
  • the cloud network may include multiple similar data centers, each of which includes different data centers.
  • VM Virtualized Network Function
  • VNF Virtualized Network Function
  • the network application layer includes network applications such as FW (firewall), LB (Load Balance), and NAT (Network Address Translation).
  • the network control plane is centralized in the SDN controller (SDN Controller), and the network forwarding plane is in the infrastructure.
  • the layer carries the network forwarding device.
  • the forwarding device is only responsible for packet forwarding and is not responsible for the calculation and maintenance of the communication path.
  • the specific communication path of each IP flow on the bearer network is controlled by the SDN Controller, and is sent to the forwarding layer device by controlling the data plane interface protocol (for example, Openflow protocol, etc.), and the communication path of each IP flow can be SDN. Controller control system.
  • FIG. 3 is a flow chart of a communication path allocation method of a cloud center network. The method of Figure 3 is performed by an SDN controller.
  • the SDN controller receives a communication path request message sent by the policy management apparatus.
  • the communication path request message carries address information of different communication nodes, bandwidth requirement information of the communication path, and QoS requirement information, and the communication node is a virtual machine (VM) or a virtualized network function (VNF).
  • VM virtual machine
  • VNF virtualized network function
  • the different communication nodes include two or more different communication nodes, wherein the different communication nodes, policy management devices, and SDN controllers may be in the same data center network. They can also be located in different data center networks. For example: the different communication nodes are located in different data center networks. In a cloud network, multiple data centers may be included, and different data centers and the same data center may be routed or communicated through the bearer network.
  • the policy management device may be a Policy and Charging Rules Function (PCRF), a policy management device, a virtualized network function manager (VNFM) device, and a system. Unified coordination device or Management and Orchestration (MANO) device.
  • PCRF Policy and Charging Rules Function
  • VNFM virtualized network function manager
  • MANO Unified coordination device or Management and Orchestration
  • the policy management device manages the plurality of different communication nodes and knows how much bandwidth is required for communication between each communication node, and what kind of QoS is required. This data can be automatically calculated according to the service type of the communication node and the traffic volume model, or can be manually pre-configured according to the network planning network design scheme.
  • the address information may include not only direct address information, such as a Media Access Control (MAC) address, an Internet Protocol (IP) address, but also indirect address information, such as Identification information, etc.
  • the address information of the communication node includes at least one of the following: an identity of the communication node (Identity, ID), a MAC address of the communication node, an IP address of the communication node, an ID of a server where the communication node is located, and the communication The ID of the LAN switch (LSW) where the node is located, the MAC address of the LSW where the communication node is located, and the IP address of the LSW where the communication node is located.
  • LSW LAN switch
  • the bandwidth requirement information of the communication path between the different communication nodes includes at least one of the following: minimum guaranteed bandwidth and maximum available bandwidth between different communication nodes.
  • the QoS requirement information between the different communication nodes includes at least one of the following: maximum allowable delay between different communication nodes, maximum allowable jitter, and maximum allowable packet loss rate.
  • the communication path request message may carry the following contents: Node 1 MAC address + Node 2 MAC address + Minimum guaranteed bandwidth + Maximum available bandwidth + Maximum allowed delay + Maximum allowed jitter + Maximum allowed packet loss rate.
  • Node 1 MAC address Node 2 MAC address + Minimum guaranteed bandwidth + Maximum available bandwidth + Maximum allowed delay + Maximum allowed jitter + Maximum allowed packet loss rate.
  • the SDN controller allocates, according to the address information of the different communication node, the bandwidth requirement information of the communication path, and the QoS requirement information, the bandwidth requirement and the QoS requirement between the different communication nodes from the network resources managed by the SDN controller. Communication path.
  • the SDN controller stores network topology information, available bandwidth resource information, and QoS information of each communication path of the data center network.
  • the SDN controller may combine the network topology information, the available bandwidth resource information, and the QoS information of each communication path according to the address information of the different communication node, the bandwidth requirement information of the communication path, and the QoS requirement information, from the SDN controller.
  • a communication path that meets bandwidth requirements and QoS requirements is allocated to the different communication nodes in the managed network resources.
  • the SDN controller sends a message carrying the communication path to the forwarding device to establish a communication path between the different communication nodes by using the forwarding device.
  • the communication path between the different communication nodes is allocated according to the address information of different communication nodes, the bandwidth requirement information of the communication path, and the QoS requirement information sent by the policy management device, so that different communication in the data center network can be ensured.
  • the service demand of the node communication and to some extent, improve the utilization efficiency of the bearer resources.
  • the forwarding device is located in the bearer network and is capable of performing data resource forwarding between different VMs within the data center and between different data centers.
  • the communication path request message may be used to request the SDN controller to establish a new communication path for different communication nodes.
  • one of the different communication nodes may be a newly deployed VM, and is ready to establish communication with the peer node VM.
  • the communication node and the opposite node have established a communication path, and a new communication path is needed because the bandwidth requirement or the OoS requirement changes or is updated.
  • the communication path request message further carries a migration event indication information. And the address information before the migration of the migrated node.
  • the step 302 is specifically implemented as follows: the SDN controller receives the communication path request message sent by the policy management apparatus, and the SDN controller according to the migration event indication information, the address information of the different communication node, the bandwidth requirement information of the communication path, and The QoS requirement information, the post-migration communication path that meets the bandwidth requirement and the QoS requirement is allocated to the different communication node from the network resource managed by the SDN controller, and the communication node and the other are deleted according to the address information before the migration of the communication node The communication path before the communication node is migrated.
  • the communication path is redistributed for the migrated communication node by the SDN controller, so that the service carried by the communication node can be migrated without interrupting the service communication, thereby ensuring the uninterrupted operation of the service and improving to a certain extent.
  • the communication path request message further carries bandwidth or QoS change indication information.
  • step 302 is specifically implemented as follows: the SDN controller receives the communication path request message sent by the policy management apparatus, and the SDN controller according to the bandwidth or QoS change indication information, the address information of different nodes, the bandwidth requirement information of the communication path, and the QoS requirement information. And re-assigning the communication path that meets the bandwidth requirement and the QoS requirement for the different communication node from the network resources managed by the SDN controller.
  • the communication path is redistributed by the SDN controller for the communication node whose bandwidth changes, and the communication path of the forwarding plane of the bearer network can be dynamically adjusted when the bandwidth or QoS requirement of the communication node service changes, thereby ensuring communication.
  • the bandwidth and QoS of the node so that the services carried by the communication node can be guaranteed, and the performance of the cloud data center system is improved to some extent.
  • FIG. 4 is a schematic diagram of a communication path allocation method when a VM is added to a data center in a cloud network
  • FIG. 5 is a corresponding flowchart.
  • the policy management device may be a PCRF, a VM Manager, which has a communication interface and a communication connection with three data centers (DC1, DC2, DC3), and the policy management device also has an SDN controller corresponding to the IP bearer network. Communication interface and communication connection.
  • the policy management device acquires location information of different VMs and bandwidth requirements and QoS requirements of communication paths between them.
  • the added VM1 sends a request message to the policy management device, which carries the location information of VM1 and VM2, VM3, and the bandwidth requirements and QoS requirements of the communication path between them.
  • the policy management device actively acquires the location information of VM1 and VM2, VM3, and the bandwidth requirements and QoS requirements of the communication path between them according to its own policy.
  • the policy management device sends a communication path request message to the SDN controller.
  • the policy management device sends a communication path request message to the SDN controller, where the communication path request message carries the location information of VM1 and VM2, VM3, and the bandwidth requirements and QoS requirements of the communication path between them.
  • the SDN controller determines a communication path.
  • the SDN controller stores network topology information, available bandwidth resource information, and QoS information of each communication path. After receiving the communication path request message, the SDN controller may determine the communication path between the different nodes according to its own communication path algorithm.
  • a possible communication path calculation algorithm is as follows:
  • the SDN controller maintains the topology and available bandwidth resource data of the entire cloud network, and collects the QoS data of each communication path according to historical traffic statistics. After the SDN controller receives the MAC address, bandwidth requirement, and QoS requirement of the newly added node and the peer node that need to be newly established by the policy management device, a communication path that satisfies the condition may be selected from the maintained bandwidth resource and the QoS database. And modify the original available bandwidth resource data.
  • the SDN controller sends a message to the bearer network forwarding device, and carries the communication path information.
  • the SDN controller can control the data plane interface (for example, Openflow protocol). Sending a message carrying the communication path to the bearer forwarding device.
  • the data plane interface for example, Openflow protocol
  • the bearer network forwarding device establishes a communication path.
  • the bearer network forwarding device After receiving the message carrying the communication path, the bearer network forwarding device establishes a bearer network communication path between the VM1 and VM2 and VM3.
  • the forwarding device sends a path establishment success indication information to the SDN controller.
  • the path establishment success indication information may be sent to the SDN controller.
  • the SDN controller sends feedback information of the communication path request message to the policy management apparatus.
  • the SDN controller may send feedback information of the communication path request message to the policy management device, indicating that the communication path is successfully established.
  • the policy management device completes the deployment.
  • the policy management apparatus After receiving the feedback information of the successful establishment of the communication path fed back by the SDN controller, the policy management apparatus confirms that the communication path of the new VM1 is established.
  • the SDN controller is newly deployed by using the address information of the newly added VM1, the address information of the opposite ends VM2 and VM3, the bandwidth requirement information of the communication path between the VMs, and the QoS requirement information according to the policy management apparatus.
  • the VM1 and the peer VM2 and VM3 allocate communication paths, which can ensure the communication requirements of the VMs in the data center network, and improve the utilization efficiency of the bearer resources.
  • the policy management apparatus further includes a VNFM, a MANO, or a system unified coordination device and the like which are well known in the art.
  • the policy management device is a VNFM
  • the communication node VM can be replaced with a VNF.
  • the communication path request message is also sent to the policy management device; the policy management device carries the change according to the changed service demand. Transmitting the communication path request message to the SDN controller, such as the address information of the changed VM, the address information of the peer VM, the bandwidth requirement information of the communication path communicated between the VMs, and the QoS requirement information; accordingly, the SDN controller Determining a communication path and sending a message to the bearer network forwarding device, where the message carries the communication path information; the bearer network forwarding device receives the carried communication path After the path message, establish a bearer network communication path
  • FIG. 6 is another interaction flowchart of a method for allocating a communication path of a cloud network, specifically including:
  • the policy management device monitors that the VM migrates.
  • the VM migration process is controlled by the policy management device.
  • the policy management device manages the bandwidth and QoS requirements for VM deployment while also managing the bandwidth and QoS requirements required for VM migration.
  • the policy management device sends a communication path request message to the SDN controller.
  • the policy management device sends a communication path request message to the SDN controller requesting that the communication path between the local node (post-migration VM1) and the correspondent node is updated.
  • the communication path request message may carry the VM1 migration event identifier, the address information before the local node migration (the address information before the VM1 migration), the address information of the local node (the address information after the VM1 migration), and the peer node. Address information, bandwidth requirement information of communication paths, and QoS requirement information.
  • the communication path request message may carry the following content: VM1 migration event identifier + local node pre-migration MAC address (VM1 pre-migration MAC address) + local node MAC address (VM1 post-migration MAC address) + peer node MAC address + minimum guaranteed bandwidth + maximum available bandwidth + maximum allowed delay + maximum allowed jitter + maximum allowed packet loss rate.
  • VM1 migration event identifier + local node pre-migration MAC address (VM1 pre-migration MAC address) + local node MAC address (VM1 post-migration MAC address) + peer node MAC address + minimum guaranteed bandwidth + maximum available bandwidth + maximum allowed delay + maximum allowed jitter + maximum allowed packet loss rate.
  • the SDN controller determines a communication path.
  • the SDN controller After receiving the communication path request message, the SDN controller can determine the communication path between the local node (the migrated VM1) and the opposite node according to its own communication path algorithm.
  • a possible communication path calculation algorithm is as follows:
  • the SDN controller maintains the topology of the entire data center IP network and the available bandwidth resource data, and collects the QoS data of each communication path according to the historical traffic statistics. After receiving the communication path request message sent by the policy management apparatus, the SDN controller may confirm that the VM1 has a migration event, and select a communication path that satisfies the condition from the maintained bandwidth resource and the QoS database, and delete the release of the VM1 before the migration. Communication path and modify the original available bandwidth resource data.
  • the communication path request message may carry a VM1 migration event notification, a local node pre-migration MAC address (a VM1 pre-migration MAC address), a local node MAC address (a VM1 post-migration MAC address), a peer node MAC address, and Bandwidth requirements and QoS requirements for communication
  • the SDN controller sends a message to the forwarding device, and carries the communication path information.
  • the forwarding device establishes a communication path.
  • the forwarding device establishes a communication path for the local node (the migrated VM1) and its opposite node, and releases the communication path allocated before the local node (VM1) migrates.
  • the forwarding device sends a path establishment success indication information to the SDN controller.
  • the SDN controller sends feedback information of the communication path request message to the policy management apparatus.
  • step 506 and the step 507 is similar to the steps 406 and 407 of FIG. 4, and details are not described herein again.
  • the policy management device completes the migration operation of VM1.
  • the communication path can be terminated without being terminated.
  • service services the service requirements of the communication between the VM1 and the peer VM in the data center network are ensured, and the utilization efficiency of the bearer resources is improved to some extent.
  • the policy management device may also be other devices, such as a VNFM, a MANO, or a system unified coordination device.
  • the communication node may be different when the policy management device changes.
  • the policy management device is a VNFM
  • the VM can be replaced with a VNF.
  • the embodiments of the present invention are not described herein again.
  • FIG. 7 is a schematic structural diagram of an SDN controller 700 according to an embodiment of the present invention.
  • the SDN controller 700 may include: a receiving unit 701, configured to receive a communication path request message sent by the policy management apparatus.
  • the communication path request message carries address information of different communication nodes, bandwidth requirement information of the communication path, and service quality QoS requirement information, and the communication node is a VM or a VNF.
  • the path allocation unit 702 is configured to allocate bandwidth requirements and QoS for different communication nodes from the network resources managed by the SDN controller according to the address information of the different communication nodes, the bandwidth requirement information of the communication path, and the service quality QoS requirement information.
  • the communication path of the demand is configured to allocate bandwidth requirements and QoS for different communication nodes from the network resources managed by the SDN controller according to the address information of the different communication nodes, the bandwidth requirement information of the communication path, and the service quality QoS requirement information.
  • the sending unit 703 is configured to send a message carrying the communication path to the bearer network forwarding device, to establish a communication path between the different communication nodes by using the forwarding device.
  • the SDN controller may further include a storage unit that stores network topology information, available bandwidth resource information, and QoS information of each communication path of different data center networks.
  • the path allocation unit 702 can combine the network topology information, the available bandwidth resource information, and the QoS information of each communication path according to the address information of different communication nodes, the bandwidth requirement information of the communication path, and the QoS requirement information, from the SDN control.
  • a communication path that meets bandwidth requirements and QoS requirements is allocated to the different communication nodes in the network resources managed by the device.
  • the SDN controller 600 can also perform the method of FIG. 3 and implement the specific functions of the SDN controller in the embodiments shown in FIG. 3, FIG. 5 and FIG. 6, which are not described herein again.
  • FIG. 8 is a schematic structural diagram of an SDN controller 800 according to an embodiment of the present invention.
  • the SDN controller 800 can include a processor 802, a memory 803, and an IO channel 801.
  • the IO channel 801, the processor 802, and the memory 803 are connected to each other through a bus 804 system.
  • the bus 804 can be an ISA bus, a PCI bus, or an EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one double-headed arrow is shown in Figure 8, but it does not mean that there is only one bus or one type of bus.
  • the memory 803 is configured to store a program.
  • the program can include program code, the program code including computer operating instructions.
  • the memory 803 stores the above-mentioned FIG. 3, FIG. 5 and FIG. Related procedures for method embodiments.
  • the processor 802 executes the program stored in the memory 803, and is specifically configured to perform the following operations:
  • FIG. 9 is a schematic structural diagram of a cloud network system 900 according to an embodiment of the present invention.
  • the cloud network system 900 includes a communication node 901, a policy management device 902, an SDN controller 903, and a bearer network forwarding device 904, where
  • the policy management device 902 is configured to acquire location information of different communication nodes 901 and bandwidth requirements and QoS requirements of communication paths between them, and send a communication path request message to the SDN controller;
  • the SDN controller 903 is configured to receive the communication path request message sent by the policy management device 902, determine the communication path, and send a message to the bearer network forwarding device 904, carrying the communication path information;
  • the bearer network forwarding device 904 is configured to establish a bearer network communication path between the different communication nodes 901 after receiving the message carrying the communication path.
  • the SDN controller 903 maintains the topology of the entire cloud network and the available bandwidth resource data, and collects the QoS data of each communication path according to the historical traffic statistics. After the SDN controller 903 receives the MAC address, bandwidth requirement, and QoS requirement of the newly added node and the peer node that need to be newly created by the policy management device 902, a condition that satisfies the condition may be selected from the maintained bandwidth resource and the QoS database. Communication path. Additionally, the different communication nodes can be located in different data center networks, respectively.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明提供了一种云化网络的通信方法、装置及系统，包括：软件定义网络SDN控制器接收策略管理装置发送的通信路径请求消息，其中，所述通信路径请求消息携带和策略管理装置通信连接的不同通信节点的地址信息、通信路径的带宽需求信息以及业务质量QoS需求信息；所述SDN控制器根据所述不同通信节点的地址信息、通信路径的带宽需求信息以及QoS需求信息，从所述SDN控制器管理的网络资源中为所述通信双方节点分配符合所述带宽需求及QoS需求的通信路径；所述SDN控制器向承载网转发设备发送携带所述通信路径的消息，以通过转发设备建立所述不同通信节点之间的通信路径。以上技术方案可以保证通讯的QoS要求也避免了承载网上物理链路资源的浪费，提高了网络运行效率和资源利用率。

Description

云化网络通信路径的分配方法、装置及系统
本申请要求于2014年12月29日提交中国专利局、申请号为201410848105.2，发明名称为“云化网络通信路径的分配方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明实施例涉及通信领域，具体地，涉及一种云化网络中的通信路径分配方法、装置及系统。
背景技术
电信节点云化是指把传统的基于物理机框和单板的电信节点及应用以软件虚拟机(VM)的方式部署到通用的数据中心服务器上面，对外提供各种电信业务，这种部署方式在业界称为网络功能虚拟化(Network Functions Virtualization，NFV)。一个云化网络可以包括多个数据中心，在云化网络的数据中心里，电信节点及应用是以虚拟机(VM)的形态存在，而不是以传统电信硬件上的单板形态存在。节点与节点之间，以及同一个节点内部不同业务进程之间的通信都表现为VM之间的通信。
按照云化虚拟化的固有特性，虚拟机可以灵活部署，根据业务负荷自动扩容和缩容，或者迁移到其他数据中心，在这些情况下，伴随虚拟机位置和容量的变化，必然也会带来数据中心之间通讯流量的变化，如何保证通讯的业务质量(Quality of Service,QoS)就是一个亟待解决的问题。
现有技术中，新部署VM到一个数据中心以前，必须先计算这个VM与其他数据中心VM的通讯带宽需求及QoS需求，然后手工在两个数据中心的接入路由器之间配置虚拟专用网络(Virtual Private Network，VPN)隧道，并设置隧道的QoS标签和VPN的带宽需求。
现有技术通过手工配置的方法无法完美地解决业务虚拟机部署在云化网络条件下的数据中心之间通讯QoS的问题，为了保证电信网元云化部署以后VM 之间通讯的QoS，必须寻求新的通讯QoS解决方案架构和技术。
发明内容
为了解决现有技术中存在的技术问题,本发明实施例提供的一种云化网络中的通信路径分配方法、装置及系统，能够保证云化网络中不同通信节点之间通信的QoS需求，并提高承载资源的利用效率。
具体地，本发明实施例一种云化网络中的通信路径分配方法，包括：软件定义网络SDN控制器接收策略管理装置发送的通信路径请求消息，其中，所述通信路径请求消息携带和策略管理装置通信连接的不同通信节点的地址信息、通信路径的带宽需求信息以及业务质量QoS需求信息；
所述SDN控制器根据所述不同通信节点的地址信息、通信路径的带宽需求信息以及QoS需求信息，从所述SDN控制器管理的网络资源中为所述通信双方节点分配符合所述带宽需求及QoS需求的通信路径；
所述SDN控制器向承载网转发设备发送携带所述通信路径的消息，以通过转发设备建立所述不同通信节点之间的通信路径。
本发明实施例一种软件定义网络SDN控制器，包括：
接收单元，用于接收策略管理装置发送的通信路径请求消息，其中，所述通信路径请求消息携带和策略管理装置通信连接的不同通信节点的地址信息、通信路径的带宽需求信息以及业务质量QoS需求信息；
路径分配单元，用于根据所述不同通信节点的地址信息、通信路径的带宽需求信息以及QoS需求信息，从所述SDN控制器管理的网络资源中为所述通信双方节点分配符合带宽需求及QoS需求的通信路径；
发送单元，用于向所述数据中心网络的转发设备发送所述通信路径的转发流表，以通过转发设备建立所述不同通信节点之间的通信路径。
本发明实施例一种云化网络系统，包括多个不同的通信节点、策略管理装置、SDN控制器和承载网转发设备，其中，
所述策略管理装置用于获取不同通信节点的位置信息及他们之间通讯路径的带 宽要求及QoS要求，并向SDN控制器发送通信路径请求消息；
所述SDN控制器用于接收策略管理装置发送的通信路径请求消息，根据所述通信路径请求消息中携带的带宽要求及QoS要求确定通信路径，并向承载网转发设备发送消息，携带所述确定的通信路径信息；
所述承载网转发设备用于接收所述携带通信路径信息的消息，建立所述不同通信节点之间的承载网通信路径。
在上述方法、装置和系统中，如果所述不同通信节点中的一个通信节点发生迁移，则所述通信路径请求消息还携带所述迁移后的通信节点的迁移事件指示信息以及所述迁移后的通信节点迁移前的地址信息，所述SDN控制器根据所述迁移后的通信节点的迁移事件指示信息、以及所述迁移后的通信节点迁移前的地址信息，删除所述迁移后的通信节点与其他通信节点迁移前的通信路径。
在上述方法、装置和系统中，所述不同通信节点之间的通信路径的带宽需求以及QoS发生更新时，所述SDN控制器收到策略管理装置发送的更新通信路径请求消息；
在上述方法、装置和系统中，所述SDN控制器根据所述更新通信路径请求消息和更新后的带宽需求以及QoS，重新从所述SDN控制器管理的网络资源中为所述不同通信节点分配通信路径。
在上述方法、装置和系统中，所述不同的通信节点分别位于不同的数据中心网络。
基于以上技术方案，策略管理装置把不同通信节点的位置信息、带宽需求信息和QoS需求信息传递给SDN Controller，由SDN Controller统一规划通信节点的转发路径，既保证通讯的QoS要求也避免了承载网上物理链路资源的浪费，提高了网络运行效率和资源利用率。进一步地，可以保证跨不同数据中心的通信节点部署到云化的数据中心以后的通信QoS。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对实施例或现有技术 描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明实施例云化网络系统架构示意图。
图2是本发明实施例SDN网络架构示意图。
图3是云化网络的通信路径分配方法流程图。
图4是云化网络通信路径分配方法的交互示意图。
图5是云化网络通信路径分配方法的交互流程图。
图6是云化网络通信路径分配方法的另一交互流程图。
图7是本发明实施例SDN控制器的结构示意图。
图8是本发明实施例SDN控制器的另一结构示意图。
图9是本发明实施例云化网络系统的结构示意图
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
为了方便理解本发明实施例，首先在此介绍本发明实施例描述中会引入的几个要素。
软件定义网络(Software Defined Network，SDN)：是一种新型网络创新架构，通过将网络设备控制面与数据面分离开来，从而实现网络流量的灵活控制。
SDN控制器，SDN的控制器设备，存储着SDN的网络拓扑信息。SDN控制器能够发现网络交换机组成的网络拓扑结构，包括在hypervisor上的软件交换机，和数据中心机柜里的硬件交换机。SDN控制器把网络编程模式从分布模式(相互 通信的网络设备决定通信路径)转变成了集中模式。SDN控制器可利用OpenFlow对网络交换机的数据转发进行编程。
图1是本发明实施例一种云化网络架构示意图。在图1所示的场景中，电信节点及应用是以虚拟机(VM)而不是以传统电信硬件上的单板形态存在。节点与节点之间，以及同一个节点内部不同业务进程之间的通信都表现为VM之间的通信。如图1所示，VM1，VM2，VM3和VM4都部署在数据中心的不同服务器上。数据中心的服务之间通过数据中心架顶交换机(Top Of Rack，TOR)、数据中心汇集交换机(End Of Row，EOR)、核心交换机等不同层次的交换机互联起来提供通信通道。业务网关，包括防火墙，负载均衡器等，组网时一般旁挂在核心交换机上。图中双箭头实线表示节点间VM的通信。
按照数据中心云计算的特点，VM可以任意部署和迁移，也就意味着VM之间的通信流量依据VM部署位置的不同，流量有可能经过TOR，EOR和核心交换机，也可能只经过TOR+EOR，或者只经过TOR，或者流量只在服务器内部。为满足电信业务SLA标准，这些VM之间的IP通信必须满足一定的QoS要求。
应理解，图1仅仅是本发明实施例的一种应用场景，图1仅示意出了一个数据中心，应理解，云化网路可以包括多个类似的数据中心，每个数据中心均包括不同的VM。另外，在实际的应用中，可能存在多种变形，例如，VM用VNF(Virtualized Network Function，虚拟网络功能)代替等，也可能在图1所示的网络架构中增加或删除若干网络节点，本发明实施例在此不作限制。
图2是本发明实施例SDN网络架构示意图。网络应用层包括FW(firewall)，LB(Load Balance)，NAT(Network Address Translation)等网络应用，在SDN架构下，网络控制面集中在SDN控制器(SDN Controller)实现，网络转发面在基础设施层的承载网络转发设备实现，转发设备只负责报文的转发，不负责通信路径的计算和维护。每一条IP流在承载网络网络上的具体通信路径由SDN Controller控制，并通过控制数据面接口协议(例如，Openflow协议等)发送到转发层设备执行，每一条IP流的通信路径都可以由SDN Controller灵活控 制。
图3是云化中心网络的通信路径分配方法流程图。图3的方法由SDN控制器执行。
301，SDN控制器接收策略管理装置发送的通信路径请求消息。
该通信路径请求消息携带不同通信节点的地址信息、通信路径的带宽需求信息及QoS需求信息，所述通信节点为虚拟机(Virtual Machine，VM)或虚拟网络功能实体(Virtualized Network Function，VNF)。
应理解，本发明实施例中，所述不同通信节点包括两个或多个不同的通信节点、其中，所述不同的通信节点、策略管理装置、SDN控制器可以在同一个数据中心网络中，也可以分别位于不同的数据中心网络中。例如：所述不同通信节点位于不同的数据中心网络中。在一个云化网络中，可以包括多个数据中心，不同的数据中心之间以及同一个数据中心内部可以通过承载网进行路由或通信。应理解，本发明实施例中，策略管理装置可以是策略与计费规则功能单元(Policy and Charging Rules Function,PCRF),策略管理装置、虚拟网络功能管理(Virtualized Network Function Manager，VNFM)装置、系统统一协调装置或管理协调(Management and Orchestration，MANO)装置。策略管理装置管理所述多个不同的通信节点，并知道每一个通信节点之间的通讯需要多少带宽，需要什么样的QoS。这个数据可以根据通信节点的业务类型、话务量话务模型自动计算出来，也可以根据网规网设方案手工预先配置下去。
应理解，本发明实施例中，地址信息不仅可包括直接地址信息，如媒体访问控制(Media Access Control，MAC)地址、互联网协议(Internet Protocol，IP)地址等，还可包括间接地址信息，如标识信息等。具体地，通信节点的地址信息至少包括以下之一：该通信节点的身份标识(Identity，ID)、该通信节点的MAC地址、该通信节点的IP地址、该通信节点所在服务器的ID、该通信节点所在局域网交换机(Lan Switch，LSW)的ID、该通信节点所在LSW的MAC地址、该通信节点所在LSW的IP地址。
应理解，该不同通信节点之间的通信路径的带宽需求信息至少包括以下之一：不同通信节点之间的最小保证带宽和最大可用带宽。
应理解，该不同通信节点之间的QoS需求信息至少包括以下之一：不同通信节点之间的最大允许时延、最大允许抖动和最大允许丢包率。
一个具体的例子，通信路径请求消息可携带以下内容：节点1MAC地址+节点2MAC地址+最小保证带宽+最大可用带宽+最大允许时延+最大允许抖动+最大允许丢包率。例如，“28-6e-d4-88-c4-f8”+“28-6e-d4-88-c5-03”+10Mbps+100Mbps+50ms+5ms+0.01。应理解，本发明实施例通信路径请求消息的例子仅仅是一个示例，本发明实施例并不局限于此。
302，SDN控制器根据所述不同通信节点的地址信息、通信路径的带宽需求信息以及QoS需求信息，从SDN控制器管理的网络资源中为该不同通信节点之间分配符合带宽需求及QoS需求的通信路径。
具体地，SDN控制器存储着该数据中心网络的网络拓扑信息、可用带宽资源信息以及各通信路径的QoS信息。SDN控制器可根据该不同通信节点的地址信息、通信路径的带宽需求信息以及QoS需求信息，结合该数据中心网络的网络拓扑信息、可用带宽资源信息以及各通信路径的QoS信息，从SDN控制器管理的网络资源中为该不同通信节点分配符合带宽需求及QoS需求的通信路径。
303，该SDN控制器向转发设备发送携带该通信路径的消息，以通过转发设备建立该不同通信节点之间的通信路径。
本发明实施例中，通过根据策略管理装置发送的不同通信节点的地址信息、通信路径的带宽需求信息及QoS需求信息，分配该不同通信节点之间的通信路径，能够保证数据中心网络中不同通信节点通信的业务需求，并在一定程度上提高承载资源的利用效率。
所述转发设备位于承载网络中，能够执行数据中心内部以及不同数据中心之间的不同VM之间的数据资源转发。
应理解，本发明实施例的方法，可适用于多种应用场景。
可选地，作为一个实施例，该通信路径请求消息可用于请求SDN控制器为不同通信节点建立新的通信路径。本发明实施例的一种应用场景，该不同通信节点之一可以是新部署的VM，准备与对端节点VM建立通信。本发明实施例的另一种应用场景，该通信节点与对端节点已建立通信路径，因带宽需求或OoS需求变化或更新，需要一条新的通信路径。
可选地，作为另一个实施例，如果所述不同通信节点之一发生迁移，例如，一个通信节点从一个数据中心迁移到另一个不同的数据中心，该通信路径请求消息还携带迁移事件指示信息以及该迁移后的节点迁移前的地址信息。此时，步骤302具体实现为：SDN控制器接收策略管理装置发送的通信路径请求消息，该SDN控制器根据该迁移事件指示信息、该不同通信节点的地址信息、该通信路径的带宽需求信息以及该QoS需求信息，从该SDN控制器管理的网络资源中为该不同通信节点分配符合带宽需求及QoS需求的迁移后通信路径，并根据该通信节点迁移前的地址信息，删除该通信节点与其他通信节点迁移前的通信路径。本发明实施例中，通过SDN控制器为迁移的通信节点重新分配通信路径，使得通信节点承载的业务能够在不中断业务通信的情况实现迁移，保证了业务的不间断运行，在一定程度上提高云化数据中心系统的性能。
可选地，作为再一个实施例，该通信路径请求消息还携带带宽或QoS变化指示信息。此时，步骤302具体实现为：SDN控制器接收策略管理装置发送的通信路径请求消息，SDN控制器根据带宽或QoS变化指示信息、不同节点的地址信息、通信路径的带宽需求信息以及QoS需求信息，重新从SDN控制器管理的网络资源中为该不同通信节点分配符合带宽需求及QoS需求的通信路径。本发明实施例中，通过SDN控制器为带宽发生变化的通信节点重新分配通信路径，能够在通信节点业务的带宽或QoS需求发生变化时，动态调整承载网转发面的通信路径，从而能够保证通信节点的带宽以及QoS，进而使得通信节点承载的业务能够得到保障，在一定程度上提高云化数据中心系统的性能。
下面，将结合具体的实施例，对本发明实施例的方法做进一步的描述。
图4是云化网络中一个数据中心新增VM时的通信路径分配方法示意图，图5是相应的流程图。本发明实施例中，策略管理装置可以为PCRF,VM Manager，其分别跟3个数据中心(DC1，DC2，DC3)有通信接口并通信连接，策略管理装置跟IP承载网的SDN控制器也有相应的通信接口并通信连接。
当数据中心DC1中新增一个VM1，且所述VM1需要跟数据中心DC2中的VM2和数据中心DC3的VM3进行通信，则本发明实施例的方法步骤如下：
501，策略管理装置获取不同VM的位置信息及他们之间通讯路径的带宽要求及QoS要求。
新增的VM1会向策略管理装置发送请求消息，所述请求消息携带VM1与VM2、VM3的位置信息及他们之间通讯路径的带宽要求及QoS要求。或者，策略管理装置根据自身策略，主动获取VM1与VM2、VM3的位置信息及他们之间通讯路径的带宽要求及QoS要求。
502，策略管理装置向SDN控制器发送通信路径请求消息。
策略管理装置向SDN控制器发送通信路径请求消息，所述通信路径请求消息中携带VM1与VM2、VM3的位置信息及他们之间通讯路径的带宽要求及QoS要求。
503，SDN控制器确定通信路径。
SDN控制器存储网络拓扑信息、可用带宽资源信息及各通信路径的QoS信息。SDN控制器接收到通信路径请求消息后，可根据其自身的通信路径算法，确定所述不同节点之间的通信路径。一种可能的通信路径计算算法如下：
SDN控制器维护整个云化网络的拓扑及可用带宽资源数据，并根据历史流量统计收集了各通信路径的QoS数据。当SDN控制器接收策略管理装置发送的需要新建通信路径的新增节点及对端节点MAC地址、带宽需求及QoS需求后，可从维护的带宽资源及QoS数据库中，选择一条满足条件的通信路径，并修改原来的可用带宽资源数据。
504，SDN控制器向承载网转发设备发送消息，携带通信路径信息。
SDN控制器在确定通信路径后，可通过控制数据面接口(例如，Openflow协议) 发送携带通信路径的消息给承载网转发设备。
505，承载网转发设备建立通信路径。
承载网转发设备接收到携带通信路径的消息后，建立所述VM1与VM2、VM3之间的承载网通信路径。
506，转发设备向SDN控制器发送路径建立成功指示信息。
转发设备建立通信路径后，可向SDN控制器发送路径建立成功指示信息。
507，SDN控制器向策略管理装置发送通信路径请求消息的反馈信息。
SDN控制器可向策略管理装置发送通信路径请求消息的反馈信息，指示通信路径建立成功。
508，策略管理装置完成部署。
策略管理装置接收到SDN控制器反馈的通信路径建立成功的反馈信息以后，确认新的VM1的通信路径建立完毕。
本发明实施例中，通过根据策略管理装置发送的新增VM1的地址信息、对端VM2和VM3的地址信息，VM之间的通信路径的带宽需求信息及QoS需求信息，SDN控制器为新部署的VM1与对端VM2和VM3分配通信路径，能够保证数据中心网络中VM之间通信的业务需求，并提高承载资源的利用效率。
应理解，本发明实施例中，策略管理装置还包括本领域公知的VNFM、MANO或系统统一协调装置等。例如，当策略管理装置为VNFM时，所述通信节点VM可以用VNF代替。当然，还可能存在其它类似的实施例，本发明实施例在此不再赘述。
进一步地，当新增VM部署完成，新增的VM或其他VM的带宽或QoS需求发生变化时，同样会向策略管理装置发送通信路径请求消息；策略管理装置会根据变化后的业务需求，携带变化后的VM的地址信息、对端VM的地址信息、所述VM之间通信的通信路径的带宽需求信息，以及QoS需求信息等向SDN控制器发送通信路径请求消息；相应地，SDN控制器确定通信路径并向承载网转发设备发送消息，所述消息携带所述通信路径信息；承载网转发设备接收到携带通信路 径的消息后，建立承载网通信路径
图6是云化网络的通信路径分配方法的另一交互流程图，具体包括：
601，策略管理装置监控到VM发生迁移操作。
在数据中心云环境中，VM的迁移过程受策略管理装置控制。策略管理装置管理着VM部署时的带宽和QoS需求，同时也管理着VM迁移以后所需的带宽和QoS需求。
602，策略管理装置向SDN控制器发送通信路径请求消息。
参考图4，如果VM1从数据中心DC1迁移到数据中心DC4,策略管理装置会向SDN控制器发送通信路径请求消息，请求为本端节点(迁移后VM1)与对端节点的通信更新通信路径。其中，该通信路径请求消息中可携带VM1迁移事件标识、本端节点迁移前的地址信息(VM1迁移前的地址信息)、本端节点的地址信息(VM1迁移后的地址信息)、对端节点的地址信息、通信路径的带宽需求信息以及QoS需求信息等。
一个具体的例子，通信路径请求消息可携带以下内容：VM1迁移事件标识+本端节点迁移前MAC地址(VM1迁移前MAC地址)+本端节点MAC地址(VM1迁移后MAC地址)+对端节点MAC地址+最小保证带宽+最大可用带宽+最大允许时延+最大允许抖动+最大允许丢包率。例如，“01”+“28-6e-d4-88-c4-22”+“28-6e-d4-88-c4-f8”+“28-6e-d4-88-c5-03”+10Mbps+100Mbps+50ms+5ms+0.01，其中“01”为VM迁移事件标识。当然，在实际的应用中，可能采用其它信息作为VM1迁移事件标识，本发明实施例在此不作限制。
应理解，本发明实施例通信路径请求消息的例子仅仅是一个示例，本发明实施例并不局限于此。
603，SDN控制器确定通信路径。
SDN控制器接收到通信路径请求消息后，可根据其自身的通信路径算法，确定本端节点(迁移后VM1)与对端节点之间的通信路径。一种可能的通信路径计算算法如下：
SDN控制器维护整个数据中心IP网络的拓扑及可用带宽资源数据，并根据历史流量统计收集了各通信路径的QoS数据。当SDN控制器接收策略管理装置发送的通信路径请求消息后，可确认VM1发生迁移事件，并从维护的带宽资源及QoS数据库中，选择一条满足条件的通信路径，并删除释放VM1迁移前分配的通信路径，并修改原来的可用带宽资源数据。其中，该通信路径请求消息中可携带VM1迁移事件通知、本端节点迁移前MAC地址(VM1迁移前MAC地址)、本端节点MAC地址(VM1迁移后MAC地址)、对端节点MAC地址，以及通信所需的带宽要求和QoS要求的
604，SDN控制器向转发设备发送消息，携带通信路径信息。
605，转发设备建立通信路径。
转发设备为本端节点(迁移后的VM1)及其对端节点建立通信路径，并释放本端节点(VM1)迁移前分配的通信路径。
606，转发设备向SDN控制器发送路径建立成功指示信息。
607，SDN控制器向策略管理装置发送通信路径请求消息的反馈信息。
步骤506及步骤507的方法与图4的步骤406、407类似，本发明实施例在此不再赘述。
608，策略管理装置完成VM1的迁移操作。
本端节点VM1与对端节点之间的通信路径重新建立成功后，VM1的迁移操作完成。
本发明实施例中，通过根据策略管理装置发送的不同通信节点的地址信息、通信路径的带宽需求信息及QoS需求信息，为迁移后的VM1与对端VM之间分配通信路径，能够在不终止业务服务的情况下，保证数据中心网络中VM1与对端VM通信的业务需求，并在一定程度上提高承载资源的利用效率。
应理解，本发明实施例中，策略管理装置还可以是其它装置，例如，VNFM、MANO或系统统一协调装置等。当策略管理装置发生变化时，通信节点可能有所不同。例如，当策略管理装置为VNFM时，VM可以用VNF代替。当然，还可能存在其 它类似的实施例，本发明实施例在此不再赘述。
图7是本发明实施例SDN控制器700的结构示意图。SDN控制器700可包括：接收单元701，用于接收策略管理装置发送的通信路径请求消息。
其中，该通信路径请求消息携带不同通信节点的地址信息、通信路径的带宽需求信息及业务质量QoS需求信息，所述通信节点为VM或VNF。
路径分配单元702，用于根据所述不同通信节点的地址信息、通信路径的带宽需求信息及业务质量QoS需求信息，从该SDN控制器管理的网络资源中为不同通信节点分配符合带宽需求及QoS需求的通信路径。
发送单元703，用于向承载网转发设备发送携带该通信路径的消息，以通过转发设备建立该不同通信节点之间的通信路径。
具体地，该SDN控制器还可包存储单元，存储着不同数据中心网络的网络拓扑信息、可用带宽资源信息以及各通信路径的QoS信息。路径分配单元702可根据不同通信节点的地址信息、通信路径的带宽需求信息以及QoS需求信息，结合不同数据中心网络的网络拓扑信息、可用带宽资源信息以及各通信路径的QoS信息，从该SDN控制器管理的网络资源中为所述不同通信节点分配符合带宽需求及QoS需求的通信路径。
SDN控制器600还可执行图3的方法，并实现SDN控制器在图3，图5和图6所示实施例的具体功能，本发明实施例在此不再赘述。
图8是本发明实施例SDN控制器800的结构示意图。SDN控制器800可包括处理器802、存储器803和IO通道801。
IO通道801、处理器802和存储器803通过总线804系统相互连接。总线804可以是ISA总线、PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图8中仅用一个双向箭头表示，但并不表示仅有一根总线或一种类型的总线。
存储器803，用于存放程序。具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。本实施例中，存储器803存储上述图3，图5和图6中 方法实施例的相关程序。
处理器802，执行存储器803所存放的程序，并具体用于执行以下操作：
获取不同通信节点的地址信息、通信路径的带宽需求信息及业务质量QoS需求信息，其中，所述不同通信节点可以为VM或VNF；
根据所述不同通信节点的地址信息、通信路径的带宽需求信息以及QoS需求信息，从所述网络资源中为所述通信双方节点分配符合带宽需求及QoS需求的通信路径；
向承载网转发设备发送携带所述通信路径的消息，以通过转发设备建立所述不同通信节点之间的通信路径。
图9是本发明实施例一种云化网络系统900的结构示意图。云化网络系统900包括通信节点901、策略管理装置902、SDN控制器903和承载网转发设备904，其中，
所述策略管理装置902用于获取不同通信节点901的位置信息及他们之间通讯路径的带宽要求及QoS要求，并向SDN控制器发送通信路径请求消息；
所述SDN控制器903用于接收策略管理装置902发送的通信路径请求消息，确定通信路径后向承载网转发设备904发送消息，携带通信路径信息；
所述承载网转发设备904用于接收到携带通信路径的消息后，建立所述不同通信节点901之间的承载网通信路径。
其中，SDN控制器903维护整个云化网络的拓扑及可用带宽资源数据，并根据历史流量统计收集了各通信路径的QoS数据。当SDN控制器903接收策略管理装置902发送的需要新建通信路径的新增节点及对端节点MAC地址、带宽需求及QoS需求后，可从维护的带宽资源及QoS数据库中，选择一条满足条件的通信路径。另外，所述不同的通信节点可以分别位于不同的数据中心网络。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计 约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应所述以权利要求的保护范围为准。

Claims (16)

  1. 一种云化网络中的通信路径分配方法，其特征在于，包括：
    软件定义网络SDN控制器接收策略管理装置发送的通信路径请求消息，其中，所述通信路径请求消息携带和策略管理装置通信连接的不同通信节点的地址信息、通信路径的带宽需求信息以及业务质量QoS需求信息；
    所述SDN控制器根据所述不同通信节点的地址信息、通信路径的带宽需求信息以及QoS需求信息，从所述SDN控制器管理的网络资源中为所述通信双方节点分配符合所述带宽需求及QoS需求的通信路径；
    所述SDN控制器向承载网转发设备发送携带所述通信路径的消息，以通过转发设备建立所述不同通信节点之间的通信路径。
  2. 如权利要求1所述的方法，其特征在于，如果所述不同通信节点中的一个通信节点发生迁移，则所述通信路径请求消息还携带所述迁移后的通信节点的迁移事件指示信息以及所述迁移后的通信节点迁移前的地址信息，
    所述SDN控制器根据所述迁移后的通信节点的迁移事件指示信息、以及所述迁移后的通信节点迁移前的地址信息，删除所述迁移后的通信节点与其他通信节点迁移前的通信路径。
  3. 如权利要求1所述的方法，其特征在于，所述方法进一步包括：
    所述不同通信节点之间的通信路径的带宽需求以及QoS发生更新时，所述SDN控制器收到策略管理装置发送的更新通信路径请求消息；
    所述SDN控制器根据所述更新通信路径请求消息和更新后的带宽需求以及QoS，重新从所述SDN控制器管理的网络资源中为所述不同通信节点分配通信路径。
  4. 如权利要求1所述的方法，其特征在于，所述不同通信节点之间的通信路径的带宽需求信息至少包括以下之一：最小保证带宽和最大可用带宽。
  5. 如权利要求1所述的方法，其特征在于，所述不同通信节点之间的QoS需求信息至少包括以下之一：所述不同通信节点之间的最大允许时延、最大允许抖 动以及最大允许丢包率。
  6. 如权利要求1所述的方法，其特征在于，通信节点的地址信息至少包括以下之一：所述通信节点的身份标识ID、所述通信节点的媒体访问控制MAC地址、所述通信节点的互联网协议IP地址、所述通信节点所在服务器的ID、所述通信节点所在局域网交换机LSW的ID、所述通信节点所在LSW的MAC地址、所述通信节点所在LSW的IP地址。
  7. 如权利要求1到6所述的任一方法，其特征在于，所述通信节点是虚拟机VM。
  8. 如权利要求1到6所述的任一方法，其特征在于，所述不同的通信节点分别位于不同的数据中心网络。
  9. 一种软件定义网络SDN控制器，其特征在于，包括：
    接收单元，用于接收策略管理装置发送的通信路径请求消息，其中，所述通信路径请求消息携带和策略管理装置通信连接的不同通信节点的地址信息、通信路径的带宽需求信息以及业务质量QoS需求信息；
    路径分配单元，用于根据所述不同通信节点的地址信息、通信路径的带宽需求信息以及QoS需求信息，从所述SDN控制器管理的网络资源中为所述通信双方节点分配符合带宽需求及QoS需求的通信路径；
    发送单元，用于向所述数据中心网络的转发设备发送所述通信路径的转发流表，以通过转发设备建立所述不同通信节点之间的通信路径。
  10. 如权利要求9所述的SDN控制器，其特征在于，所述不同通信节点之间的通信路径的带宽需求信息至少包括以下之一：最小保证带宽和最大可用带宽。
  11. 如权利要求9所述的SDN控制器，其特征在于，所述不同通信节点之间的QoS需求信息至少包括以下之一：所述不同通信节点之间的最大允许时延、最大允许抖动以及最大允许丢包率。
  12. 如权利要求9到11任一项所述的SDN控制器，其特征在于，所述不同的通信节点分别位于不同的数据中心网络。
  13. 一种云化网络系统，其特征在于，包括多个不同的通信节点、策略管理装置、SDN控制器和承载网转发设备，其中，
    所述策略管理装置用于获取不同通信节点的位置信息及他们之间通讯路径的带宽要求及QoS要求，并向SDN控制器发送通信路径请求消息；
    所述SDN控制器用于接收策略管理装置发送的通信路径请求消息，根据所述通信路径请求消息中携带的带宽要求及QoS要求确定通信路径，并向承载网转发设备发送消息，携带所述确定的通信路径信息；
    所述承载网转发设备用于接收所述携带通信路径信息的消息，建立所述不同通信节点之间的承载网通信路径。
  14. 如权利要求13所述的系统，其特征在于，所述不同通信节点之间的通信路径的带宽需求信息至少包括以下之一：最小保证带宽和最大可用带宽。
  15. 如权利要求13所述的系统，其特征在于，所述不同通信节点之间的QoS需求信息至少包括以下之一：所述不同通信节点之间的最大允许时延、最大允许抖动以及最大允许丢包率。
  16. 如权利要求13到15所述的任一系统，其特征在于，所述不同的通信节点分别位于不同的数据中心网络。
PCT/CN2015/097605 2014-12-29 2015-12-16 云化网络通信路径的分配方法、装置及系统 WO2016107418A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP15875096.8A EP3226495A4 (en) 2014-12-29 2015-12-16 Allocation method, apparatus and system for cloud network communication path
US15/637,814 US20170300353A1 (en) 2014-12-29 2017-06-29 Method for Allocating Communication Path in Cloudified Network, Apparatus, and System

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410848105.2 2014-12-29
CN201410848105.2A CN104518993A (zh) 2014-12-29 2014-12-29 云化网络通信路径的分配方法、装置及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/637,814 Continuation US20170300353A1 (en) 2014-12-29 2017-06-29 Method for Allocating Communication Path in Cloudified Network, Apparatus, and System

Publications (1)

Publication Number Publication Date
WO2016107418A1 true WO2016107418A1 (zh) 2016-07-07

Family

ID=52793736

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/097605 WO2016107418A1 (zh) 2014-12-29 2015-12-16 云化网络通信路径的分配方法、装置及系统

Country Status (4)

Country Link
US (1) US20170300353A1 (zh)
EP (1) EP3226495A4 (zh)
CN (1) CN104518993A (zh)
WO (1) WO2016107418A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107396335A (zh) * 2017-05-18 2017-11-24 中国科学技术大学 异构网络下的移动切换管理方法

Families Citing this family (46)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8125907B2 (en) * 2008-06-12 2012-02-28 Talari Networks Incorporated Flow-based adaptive private network with multiple WAN-paths
CN104202264B (zh) * 2014-07-31 2019-05-10 华为技术有限公司 云化数据中心网络的承载资源分配方法、装置及系统
CN104518993A (zh) * 2014-12-29 2015-04-15 华为技术有限公司 云化网络通信路径的分配方法、装置及系统
CN106209409B (zh) * 2015-05-07 2019-04-12 中国移动通信集团公司 一种基于虚拟网络功能vnf的调度消息处理方法及装置
CN106302074B (zh) * 2015-06-26 2020-07-31 南京中兴软件有限责任公司 一种虚拟化网络功能vnf的迁移方法及装置
CN112073215B (zh) * 2015-06-29 2022-05-13 华为技术有限公司 一种实现应用的方法及业务控制器
CN105024853A (zh) * 2015-07-01 2015-11-04 中国科学院信息工程研究所 基于谣言传播机制的sdn资源匹配和服务路径发现方法
CN106385365B (zh) 2015-08-07 2019-09-06 新华三技术有限公司 基于开放流Openflow表实现云平台安全的方法和装置
CN105227460B (zh) * 2015-10-13 2018-06-29 电子科技大学 一种基于sdn的地震解释系统
CN106888152B (zh) 2015-12-16 2019-11-12 华为技术有限公司 一种消息处理方法、装置和系统
CN105429806B (zh) * 2015-12-24 2019-06-11 武汉邮电科学研究院 一种基于数据驱动的网络功能虚拟化的装置及方法
CN106921977B (zh) * 2015-12-26 2020-11-06 华为技术有限公司 一种基于业务流的服务质量规划方法、装置及系统
CN106936857B (zh) * 2015-12-29 2020-05-19 中国电信股份有限公司 一种混合云的连接管理方法、sdn控制器及混合云系统
CN105450521B (zh) * 2015-12-31 2019-10-25 中国电子科技集团公司电子科学研究院 一种软件定义的多路径网络流实时动态优化方法
US9967136B2 (en) * 2016-03-28 2018-05-08 Dell Products L.P. System and method for policy-based smart placement for network function virtualization
WO2017166136A1 (zh) * 2016-03-30 2017-10-05 华为技术有限公司 一种vnf的资源分配方法及装置
SG11201809348VA (en) * 2016-06-06 2018-11-29 Hitachi Systems Ltd Data migration system and data migration method
CN107483335B (zh) * 2016-06-07 2021-01-15 中国移动通信有限公司研究院 一种sdn业务实现方法及应用实体、管理实体、控制器
WO2018000240A1 (en) * 2016-06-29 2018-01-04 Orange Method and system for the optimisation of deployment of virtual network functions in a communications network that uses software defined networking
CN107645400B (zh) * 2016-07-22 2019-09-03 中兴通讯股份有限公司 策略发送、接收方法、装置及控制器
US10277528B2 (en) * 2016-08-11 2019-04-30 Fujitsu Limited Resource management for distributed software defined network controller
CN107786995A (zh) * 2016-08-26 2018-03-09 北京三星通信技术研究有限公司 用户平面建立的方法及相应设备
CN108377525B (zh) * 2016-11-16 2020-09-04 中国移动通信有限公司研究院 一种数据传输系统、方法及装置
CN108092909A (zh) * 2016-11-21 2018-05-29 中国移动通信有限公司研究院 数据流量控制方法、装置及系统
CN106789179B (zh) * 2016-11-30 2019-07-09 中国人民解放军国防科学技术大学 一种基于sdn架构的资源分配方法
CN108234313B (zh) * 2016-12-15 2021-03-19 南宁富桂精密工业有限公司 控制器及网络服务动态部署系统及方法
CN108240815B (zh) * 2016-12-26 2022-07-01 大众汽车（中国）投资有限公司 导航路线生成方法和装置
CN108471629B (zh) * 2017-02-23 2021-04-20 华为技术有限公司 传输网络中业务服务质量的控制方法、设备及系统
CN107426109B (zh) * 2017-06-27 2020-10-09 上海华为技术有限公司 一种流量调度方法、vnf模块及流量调度服务器
US10491542B2 (en) * 2017-11-07 2019-11-26 Infinera Corporation Dynamic allocation of network bandwidth
US10616106B2 (en) * 2017-12-06 2020-04-07 Futurewei Technologies, Inc. Establishing virtual network routes in a computer network
US10193761B1 (en) * 2018-03-09 2019-01-29 Loon Llc Hybrid LEO/HAPs constellation for fixed broadband
CN110535672A (zh) * 2018-05-23 2019-12-03 华为技术有限公司 一种网络功能部署方法和网络功能部署装置
EP3804241B1 (en) 2018-06-07 2022-03-09 Telefonaktiebolaget LM Ericsson (publ) Configuring a network path in an sdn
CN108881479B (zh) * 2018-07-19 2021-02-09 河北中科恒运软件科技股份有限公司 一种集成消息队列及消息管理方法
CN109743259B (zh) * 2018-12-24 2022-08-02 中国联合网络通信集团有限公司 一种网络的流量调度方法及装置
EP3715983B1 (de) * 2019-03-28 2022-06-29 Siemens Aktiengesellschaft Verfahren zur bereitstellung von steuerungsanwendungen über ein kommunikationsnetz zur übermittlung zeitkritischer daten und koordinierungseinrichtung
CN111800348A (zh) * 2019-04-09 2020-10-20 中兴通讯股份有限公司 一种负载均衡方法和装置
CN110177031B (zh) * 2019-06-18 2021-01-01 深圳职业技术学院 一种基于sdn网络的数据监控控制系统及其监控控制方法
CN110430236B (zh) * 2019-06-29 2020-11-03 华为技术有限公司 一种部署业务的方法以及调度装置
CN110474842A (zh) * 2019-07-22 2019-11-19 中国联合网络通信集团有限公司 一种通信方法、客户终端设备及传输网络
CN112636991B (zh) * 2021-03-05 2021-06-25 北京航空航天大学 一种基于中介中心度的多类vnf部署方法
US11888752B2 (en) * 2021-09-02 2024-01-30 Cisco Technology, Inc. Combining networking technologies to optimize wide area network traffic
CN114157718B (zh) * 2021-11-12 2023-07-25 国网冀北电力有限公司信息通信分公司 一种sdn网络系统及sdn网络系统的控制方法
CN114268613B (zh) * 2022-03-02 2022-06-03 阿里巴巴（中国）有限公司 数据传输系统、方法、设备及存储介质
CN115150305B (zh) * 2022-06-28 2023-04-25 中国联合网络通信集团有限公司 承载网时延链路确定系统、方法、电子设备及存储介质

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102857416A (zh) * 2012-09-18 2013-01-02 中兴通讯股份有限公司 一种实现虚拟网络的方法和虚拟网络
CN102884763A (zh) * 2012-06-30 2013-01-16 华为技术有限公司 跨数据中心的虚拟机迁移方法、服务控制网关及系统
CN103346922A (zh) * 2013-07-26 2013-10-09 电子科技大学 基于sdn的确定网络状态的控制器及其确定方法
CN103812930A (zh) * 2014-01-16 2014-05-21 华为技术有限公司 一种资源调度的方法及装置
CN104104718A (zh) * 2014-07-02 2014-10-15 北京邮电大学 一种基于软件定义网络的用户自主路由定制系统和方法
US20140307556A1 (en) * 2013-04-10 2014-10-16 Futurewei Technologies, Inc. System and Method for a Control Plane Reference Model Framework
CN104202264A (zh) * 2014-07-31 2014-12-10 华为技术有限公司 云化数据中心网络的承载资源分配方法、装置及系统
CN104518993A (zh) * 2014-12-29 2015-04-15 华为技术有限公司 云化网络通信路径的分配方法、装置及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9350671B2 (en) * 2012-03-22 2016-05-24 Futurewei Technologies, Inc. Supporting software defined networking with application layer traffic optimization
KR102065075B1 (ko) * 2013-06-24 2020-01-10 한국전자통신연구원 소프트웨어 정의 네트워킹 기반 네트워크 제어 방법 및 이를 수행하는 장치
CN103746911B (zh) * 2014-01-20 2017-06-09 中国联合网络通信集团有限公司 一种sdn网络结构及其通信方法

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102884763A (zh) * 2012-06-30 2013-01-16 华为技术有限公司 跨数据中心的虚拟机迁移方法、服务控制网关及系统
CN102857416A (zh) * 2012-09-18 2013-01-02 中兴通讯股份有限公司 一种实现虚拟网络的方法和虚拟网络
US20140307556A1 (en) * 2013-04-10 2014-10-16 Futurewei Technologies, Inc. System and Method for a Control Plane Reference Model Framework
CN103346922A (zh) * 2013-07-26 2013-10-09 电子科技大学 基于sdn的确定网络状态的控制器及其确定方法
CN103812930A (zh) * 2014-01-16 2014-05-21 华为技术有限公司 一种资源调度的方法及装置
CN104104718A (zh) * 2014-07-02 2014-10-15 北京邮电大学 一种基于软件定义网络的用户自主路由定制系统和方法
CN104202264A (zh) * 2014-07-31 2014-12-10 华为技术有限公司 云化数据中心网络的承载资源分配方法、装置及系统
CN104518993A (zh) * 2014-12-29 2015-04-15 华为技术有限公司 云化网络通信路径的分配方法、装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3226495A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107396335A (zh) * 2017-05-18 2017-11-24 中国科学技术大学 异构网络下的移动切换管理方法
CN107396335B (zh) * 2017-05-18 2020-08-25 中国科学技术大学 异构网络下的移动切换管理方法

Also Published As

Publication number Publication date
EP3226495A4 (en) 2017-12-20
US20170300353A1 (en) 2017-10-19
CN104518993A (zh) 2015-04-15
EP3226495A1 (en) 2017-10-04

Similar Documents

Publication Publication Date Title
WO2016107418A1 (zh) 云化网络通信路径的分配方法、装置及系统
WO2016015559A1 (zh) 云化数据中心网络的承载资源分配方法、装置及系统
US11625154B2 (en) Stage upgrade of image versions on devices in a cluster
US11563669B2 (en) Method for implementing network virtualization and related apparatus and communications system
EP3314816B1 (en) Network function virtualization (nfv) hardware trust in data communication systems
US9999030B2 (en) Resource provisioning method
US9692696B2 (en) Managing data flows in overlay networks
JP6538986B2 (ja) 仮想マシンパケット制御
JP6096325B2 (ja) シンキングＤｉａｍｅｔｅｒネットワークアーキテクチャを提供するための方法、システム、およびコンピュータ読取可能媒体
US9584369B2 (en) Methods of representing software defined networking-based multiple layer network topology views
EP3509253A1 (en) Inter-cloud communication method and related device, inter-cloud communication configuration method and related device
JP7109148B2 (ja) スケーラブルな進化したパケットコア
WO2017036288A1 (zh) 一种网元升级方法及设备
US20100287262A1 (en) Method and system for guaranteed end-to-end data flows in a local networking domain
WO2015149604A1 (zh) 一种负载均衡方法、装置及系统
WO2014000292A1 (zh) 跨数据中心的虚拟机迁移方法、服务控制网关及系统
WO2016169218A1 (zh) 一种网关虚拟化方法、系统及计算机存储介质
EP2681878B1 (en) Technique for managing an allocation of a vlan
US20200412612A1 (en) Analyzing and configuring workload distribution in slice-based networks to optimize network performance
US20170238171A1 (en) Method, Apparatus, and System for Migrating Virtual Network Function Instance
EP3621243A1 (en) Virtual network creation method and device, apparatus, transport network system, and storage medium
US20190132152A1 (en) Dynamic customer vlan identifiers in a telecommunications network
CN108345490B (zh) 一种nfv中部署虚拟机的方法和系统
WO2018210075A1 (zh) 网络控制方法、装置及网络设备
CN107769973B (zh) 一种报文转发方法及装置

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: 15875096

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015875096

Country of ref document: EP