WO2015024411A1 - Procédé d'obtention d'informations de capacité de nœud de desserte, et plate-forme de contrôle - Google Patents

Procédé d'obtention d'informations de capacité de nœud de desserte, et plate-forme de contrôle Download PDF

Info

Publication number
WO2015024411A1
WO2015024411A1 PCT/CN2014/080437 CN2014080437W WO2015024411A1 WO 2015024411 A1 WO2015024411 A1 WO 2015024411A1 CN 2014080437 W CN2014080437 W CN 2014080437W WO 2015024411 A1 WO2015024411 A1 WO 2015024411A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
service node
openflow
control platform
information
Prior art date
Application number
PCT/CN2014/080437
Other languages
English (en)
Chinese (zh)
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 中兴通讯股份有限公司
Publication of WO2015024411A1 publication Critical patent/WO2015024411A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present invention relates to the field of SDN architecture network communication, and in particular, to a method and a control platform for acquiring service node capability information.
  • BACKGROUND Currently, many complex functions, such as OSPF (Open Shortest Path First), BGP (border gateway protocol), multicast, differentiated services, and traffic engineering, are required in the architecture of a router. , NAT (Network Address Translation), firewall, and MPLS (Multi-Protocol Label Switching). As a result, switching devices such as routers are becoming more and more bloated and the space for performance improvement is getting smaller and smaller.
  • the computer field uses a simple, low-level hardware (x86 instruction set) that makes the computer world a fast-moving one.
  • OpenFlow Protocol OpenFlow Protocol
  • Figure 1 realizes flexible network traffic by separating the network device control plane (including OpenFlow Controller) from the data plane (including OpenFlow Capable Switch). Control provides a good platform for innovation in core networks and applications.
  • the OpenFlow protocol is used to describe the standards used for the interaction between controllers and switches, as well as the interface standards for controllers and switches.
  • the core part of the protocol is a collection of information structures for the OpenFlow protocol.
  • An OpenFlow flow table or a plurality of flow tables are cascaded into a pipeline to configure a switch forwarding path (as shown in FIG. 2).
  • the entry definition of the flow table is composed of the following fields: a matching field, a counter, and an instruction set. , As shown in Table 1.
  • the Match Fields are the input keywords of the message matching, which are used to match a flow table entry; the counter is used for various statistical information for management; the instruction set (Instructions) refers to the operation instructions of the message, including: Forward packets to the specified port, set the value of the packet header field, and add encapsulation labels.
  • the Action Set is associated with each message. It is passed between multiple flow tables in the pipeline and modified by the instructions of each flow table until the end of the pipeline or the instruction of the flow table entry that is matched to be executed. In the action set, all actions in the action set are executed centrally.
  • the existing network the control face SDN APP an application function provides network services, when open interfaces, a logical network topology APP just contracted to provide further comprising adhering properties thereof subscription network service unit (Service Nodes) 0
  • subscription network service unit Service Nodes
  • the forwarding network and the service node are usually deployed in a static configuration manner to form a certain service orchestration. This approach is limited by the topology of the network and cannot accommodate virtualized network functions.
  • a service node is added or deleted, it needs to be reconfigured and affects the underlying network topology.
  • the existing OpenFlow capability negotiation function cannot support the information awareness of the OpenFlow controller to non-OpenFlow switches (such as service nodes).
  • the present invention provides a method and a control platform for acquiring service node capability information, so as to solve the defect that the existing OpenFlow capability negotiation function cannot support the information perception capability of the OpenFlow controller to a non-OpenFlow switch (such as a service node).
  • a method for acquiring service node capability information including: controlling a platform to obtain information of the service node by using an interface with a service node; or The information of the service node sent by the control platform or the device having the network management function through the northbound interface; wherein the information of the service node includes: an identity identifier and a capability attribute of the service node; and the control platform includes an open flow (OpenFlow) ) Controller or OpenFlow configuration point.
  • OpenFlow open flow
  • the acquiring, by the control platform, the information of the service node by using an interface with the service node specifically: when the interface exists between the OpenFlow configuration point and the service node, expanding the The OpenFlow configuration protocol
  • the OpenFlow configuration point acquires information of the service node from the service node by using a Get-Config message.
  • the acquiring, by the control platform, the information of the service node by using an interface with the service node specifically: when the interface exists between the OpenFlow controller and the service node, extending the OpenFlow protocol Obtaining information about the service node by enhancing an OpenFlow feature (OF-Feature) or adding a sub-message of a multipart message.
  • OF-Feature OpenFlow feature
  • the capability attribute includes: a service type, a topology connection, and/or a performance indicator of the service node.
  • the information of the service node further includes a local policy of the service node, where the local policy includes a static policy configured by an operator.
  • the method further includes: the control platform is configured to form a network service view by using the information of the obtained service node, where the network service view includes a network topology connection and each service of the service node and the OpenFlow switch. The capability attribute of the node.
  • the method further includes: forming, by the control platform, a service chain according to a service application and/or a service requirement managed by the service, and combining the network service view, and generating corresponding to each service node involved in the service chain.
  • the forwarding policy generates a corresponding flow table entry for each OpenFlow switch involved in the service chain, and sends the flow table entry to the corresponding OpenFlow switch through the OpenFlow protocol, and sends the forwarding policy to the corresponding one through the control protocol.
  • Service node is forming, by the control platform, a service chain according to a service application and/or a service requirement managed by the service, and combining the network service view, and generating corresponding to each service node involved in the service chain.
  • the forwarding policy generates a corresponding flow table entry for each OpenFlow switch involved in the service chain, and sends the flow table entry to the corresponding OpenFlow switch through the OpenFlow protocol, and sends the forwarding policy to the corresponding one through the control protocol.
  • Service node is
  • a control platform including: an obtaining module, configured to acquire information of the service node by using an interface with a service node; or, a receiving module, configured to receive a service control platform Or the information of the service node that is sent by the device with the network management function through the northbound interface; the information of the service node includes: the identity identifier and the capability attribute of the service node; and the control platform includes OpenFlow control Or OpenFlow configuration point.
  • the acquiring module is configured to acquire the information of the service node by using an interface with the service node, where the method includes: When the interface exists between the OpenFlow configuration point and the service node, the OpenFlow configuration protocol is extended, and the information of the service node is obtained from the service node by using a Get-Config message.
  • the control platform is the OpenFlow controller
  • the acquiring module acquires the information of the service node by using an interface between the service node, and the acquiring module includes: The information of the service node is obtained by enhancing the OpenFlow feature (OF-Feature) or adding a sub-message of a multi-part message.
  • OF-Feature OpenFlow feature
  • the capability attribute includes: a service type, a topology connection, and/or a performance indicator of the service node.
  • the information of the service node further includes a local policy of the service node, where the local policy includes a static policy configured by an operator.
  • the control platform further includes: a service view forming module, configured to form a network service view by using the information of the obtained service node; wherein the network service view includes a network topology of the service node and the OpenFlow switch Connections and capability attributes of individual service nodes.
  • control platform further includes: a service chain forming module, configured to form a service chain according to a service application and/or a service requirement managed by the service, and a network service view generated by the service view forming module, for the service
  • a service chain forming module configured to form a service chain according to a service application and/or a service requirement managed by the service
  • a network service view generated by the service view forming module for the service
  • Each service node involved in the chain generates a corresponding forwarding policy, and generates a corresponding flow table entry for each OpenFlow switch involved in the service chain, and sends the flow table entry to the corresponding OpenFlow switch through the OpenFlow protocol, and passes the control protocol.
  • the forwarding policy is delivered to the corresponding service node.
  • the OpenFlow control plane can not only grasp the network topology of the SDN network, but also the service nodes and their capability information attached to the network, thereby dynamically orchestrating the service service chain as needed, and providing the network more flexibly and efficiently.
  • service. 1 is a schematic diagram of an OpenFlow configuration (OF-Config) protocol and an OpenFlow protocol application in the prior art
  • FIG. 2 is a schematic diagram of a packet flow passing through an OpenFlow processing pipeline in the prior art
  • FIG. 3 is a schematic diagram of a packet flow through an OpenFlow processing pipeline according to an embodiment of the present invention
  • FIG. 4 is a structural diagram of a service node reporting capability attributes to a control platform according to an embodiment of the present invention
  • FIG. 5 is a diagram of a control platform acquiring a service node capability through a network management system according to an embodiment of the present invention
  • FIG. 6 is a flowchart of an OpenFlow configuration point acquiring a service node capability attribute according to an embodiment of the present invention
  • 7 is a flow chart of an OpenFlow controller acquiring a service node capability attribute according to an embodiment of the present invention
  • FIG. 8 is a flowchart 1 for forwarding a data message according to a service chain arranged by a control platform according to an embodiment of the present invention
  • FIG. The data packet of the embodiment is forwarded according to the service chain of the control platform.
  • FIG. 10 is an embodiment of the service control platform passing the service node information to the control platform according to an embodiment of the present invention.
  • the method mainly includes: the control platform acquires information of the service node by using an interface with a service node (ie, method 1) Or the control platform receives the information of the service node that is sent by the service control platform or the device having the network management function through the northbound interface (ie, method 2); wherein the information of the service node includes: the identity of the service node And capability attributes, the control platform includes an OpenFlow controller or an OpenFlow configuration point.
  • Method 1 First, the control platform obtains information of the service node through an interface with the service node, and the service node sets its own information (including: identity and capability attributes, and may also include local policies, etc.) through the interface. Reported to the control platform.
  • the control platform includes an OpenFlow controller or an OpenFlow configuration point.
  • the interface between the control platform and the service node communicates by using a control protocol (such as the OF-Config (OpenFlow Configuration) protocol or the OpenFlow protocol), such as capability negotiation, status notification, and the like.
  • a control protocol such as the OF-Config (OpenFlow Configuration) protocol or the OpenFlow protocol
  • the OF-Config protocol is extended, and the OpenFlow configuration point acquires information of the service node from the service node by using a Get-Config message.
  • the extended OF-Config protocol is: Define a data model describing the capability attributes under its framework.
  • the capability description file is pre-configured on the service node, such as a file based on XML Schema.
  • the OpenFlow protocol When the interface exists between the OpenFlow controller and the service node, the OpenFlow protocol is extended, and the information of the service node is obtained by enhancing the OFPT-Feature (OpenFlow feature) message.
  • the capability attribute includes: a service type of the service node (such as video, voice, etc.), a topology connection, and/or a performance indicator (such as a rate, a delay, and the like).
  • the local policy includes a static policy configured by an operator.
  • the control platform uses the acquired information of the service node to form a network service view.
  • the network service view includes a network topology connection between the service node and the OpenFlow switch and capability attributes of each service node.
  • the control platform forms a service chain composed of a plurality of service nodes according to service applications and/or service requirements of the self-management and the network service view, and generates corresponding flow table entries for the OpenFlow switches involved in the service chain, which are related to the service chain.
  • Each service node generates a corresponding forwarding policy, and the flow table entry is sent to the corresponding OpenFlow switch through the OpenFlow protocol, and/or the forwarding policy is sent to the corresponding service node by using the control protocol; or the control platform is sent to the corresponding service node.
  • the element (such as the network management system) sends the forwarding policy to the corresponding service node.
  • the OpenFlow switch forwards the data packet according to the received flow table entry; the service node forwards the data packet according to the received forwarding policy. Specifically, if the OpenFlow switch forwards the data packet to the serving node according to the received flow table entry, after the service node processes the data packet, the data packet is forwarded according to the local default policy (for example, the processed data is processed). The packet is sent back to the OpenFlow switch, or sent to the next OpenFlow switch according to the received forwarding policy.
  • Method 2 First, the service control platform or the device with the network management function sends the information of the service node through the northbound interface (including: identity and capability attributes (service type, topology connection, and/or performance indicators (such as rate, delay, etc.) ), can also include local policies) to notify the control platform. Then, the control platform can orchestrate the service chain according to the service application and/or the service requirements managed by itself, and the information of the service node from the service control platform, and generate corresponding flow table entries and/or corresponding service node entries for the service chain. Forwarding strategy. Optionally, the control platform may send the flow table entry to the corresponding OpenFlow switch by using the OpenFlow protocol.
  • identity and capability attributes service type, topology connection, and/or performance indicators (such as rate, delay, etc.)
  • performance indicators such as rate, delay, etc.
  • the control platform can orchestrate the service chain according to the service application and/or the service requirements managed by itself, and the information of the service node from the service control platform, and generate corresponding flow table
  • the control platform sends the forwarding policy to the corresponding service node by using a control protocol.
  • the interface between the control platform and the service node is controlled by a control protocol (such as the OF-Config protocol or the OpenFlow protocol), such as policy delivery, status notification, and the like.
  • a control protocol such as the OF-Config protocol or the OpenFlow protocol
  • the forwarding policy is delivered by extending the OF-Config protocol.
  • the forwarding policy is delivered by extending the OpenFlow protocol.
  • the control platform includes an OpenFlow controller and an OpenFlow configuration point; the control platform acquires a service application requirement from an Application (application server); and the OpenFlow protocol is used to communicate between the control platform and the OpenFlow switch; A new interface is defined between the platform and the service node for capability negotiation, status notification, etc.; the service node pre-configures the capability description file, such as a file based on the XML Schema form; the XML instance of the service node pre-configured capability description file is as follows:
  • ypyOteNG ATAL/te ⁇ v ⁇ v- sevceri ⁇ >
  • control platform communicates with the service node through a control protocol (such as OF-Config protocol, OpenFlow protocol), and the control platform obtains the identity and capability attributes of the service node, and may also obtain the local policy of the service node.
  • a control protocol such as OF-Config protocol, OpenFlow protocol
  • the control platform forms a network service view according to the information reported by the service node, where the network topology connection between the service node and the OpenFlow switch and the capability attribute of each service node are included;
  • the control platform forms a service chain according to the service application requirements and/or the service requirements of the self-management service, and combines the foregoing network service views to generate a corresponding forwarding policy for each service node involved in the service chain, and generates corresponding corresponding services for each service OpenFlow switch involved in the service chain.
  • Flow table entry The control platform delivers the flow table entry to the corresponding OpenFlow switch through the OpenFlow protocol, and sends the forwarding policy to the corresponding service node through the control protocol.
  • the control platform includes an OpenFlow controller and an OpenFlow configuration point; the control platform obtains a service application requirement from the Application; and the OpenFlow protocol is used for communication between the control platform and the OpenFlow switch;
  • the network topology connection and capability attributes of the service node are advertised to the control platform;
  • the control platform forms a network service view according to the network topology connection and the capability attribute of the service node (including the network topology connection of the service node and the OpenFlow switch and the service attributes of each node)
  • the control platform forms a service chain according to the service application requirements and/or the service requirements of the self-management, and the network service view, generates a corresponding forwarding policy for each service node involved in the service chain, and generates a flow table for each OpenFlow switch involved in the service chain.
  • FIG. 6 is a flowchart of an OpenFlow configuration point acquiring service node capability attribute according to an embodiment of the present invention. . Before starting this process, three conditions need to be met. First, there is an interface between the OpenFlow configuration point and the service node, and communication is performed through the OF-Config protocol (the OF-Config protocol uses the ETCONF XML data format to define the language), such as the capability. Negotiation, status announcements, etc.
  • the service node needs to be pre-configured with a capability description.
  • a file based on the XML Schema form For example, a file based on the XML Schema form; third, the extended OF-Config protocol, in which a data model describing the capability attributes of the service node is defined.
  • the method mainly includes the following steps (1) - (5).
  • the OpenFlow configuration point sends an ETCO F_Hello message to the serving node.
  • the service node sends an ETCO F_Hello message to the OpenFlow configuration point.
  • the OpenFlow configuration point and the service node complete the negotiation of the basic capability, version number, and the like. If the negotiation is successful, the OpenFlow configuration point establishes a session with the service node.
  • the OpenFlow configuration point sends a Get Configuration Request (Get-Config_REQUEST) to the service node to obtain capability information of the service node.
  • Get-Config_REQUEST a Get Configuration Request
  • the service node replies to the OpenFlow configuration point to obtain a configuration response (Get-Config_RESPONSE), which carries the identity identifier and the capability attribute, and can also carry the local policy.
  • Get-Config_RESPONSE a configuration response
  • FIG. 7 is a flowchart of an OpenFlow controller acquiring a service node capability attribute according to an embodiment of the present invention.
  • the conditions for performing this process are as follows:
  • the OpenFlow controller has an interface with the service node and communicates through the OpenFlow protocol, such as capability negotiation, status notification, and so on.
  • the OpenFlow controller acquires the service node capability attribute mainly includes the following steps (1) - step (4).
  • the OpenFlow controller sends an OFPT_HELLO message to the service node; (2) the service node replies to the OFPT_HELLO message to the OpenFlow controller; through steps (1) and (2), the basic capability and version number are completed between the OpenFlow controller and the service node.
  • Negotiation If the negotiation is successful, a session is established between the OpenFlow controller and the service node;
  • FIG. 8 is an example 1 in which data packets are forwarded according to a service chain orchestrated by a control platform. As shown in FIG. 8, specifically, the following (1) - (5) are included.
  • the interface between the OpenFlow configuration point and the service node in the control platform communicates using the OF-Config protocol (OF-Config uses the ETCO F XML data format to define the language).
  • OF-Config uses the ETCO F XML data format to define the language.
  • the OpenFlow configuration point obtains the identity and capability attributes of the service node from the service node through the Get-Config message, and may also obtain information such as the local policy. After the OpenFlow configuration point obtains the information of the service node, it sends it to the OpenFlow controller.
  • the OpenFlow controller forms a network service view according to the information reported by the service node (including the network topology connection between the service node and the OpenFlow switch and the capability information of each service node).
  • the OpenFlow controller forms a service chain according to the service application requirements and/or the service requirements of the self-management service, and combines the network service views to generate a corresponding forwarding policy for each service node involved in the service chain, and generates for each OpenFlow switch involved in the service chain.
  • the corresponding flow table entry The OpenFlow controller forms a service chain according to the service application requirements and/or the service requirements of the self-management service, and combines the network service views to generate a corresponding forwarding policy for each service node involved in the service chain, and generates for each OpenFlow switch involved in the service chain.
  • the OpenFlow controller sends the flow table entry to the corresponding OpenFlow switch through the OpenFlow protocol, and the forwarding policy is sent to the corresponding service node by using the control protocol.
  • the OpenFlow switch After receiving the data packet, the OpenFlow switch forwards the data packet according to the flow table entry. In the example of FIG. 8, after the packet enters a certain network from the OpenFlow switch 1, the packet is forwarded to the serving node 1 according to the flow table entry. If the serving node 1 does not have the local forwarding policy, the packet is sent back to the packet after the processing is completed.
  • FIG. 9 is an example 2 of forwarding a data message according to a service chain arranged by a control platform. As shown in FIG. 9, specifically, the following (1) - (5) are included. (1) The interface between the OpenFlow controller and the service node in the control platform communicates using the OpenFlow protocol.
  • the OpenFlow controller obtains the identity and capability attributes of the service node from the service node through the OFPT_FEATURES message or the OFPMP SERVICE FEATURE multipart message, and also obtains information such as the local policy of the service node.
  • the OpenFlow controller forms a network service view according to the information reported by the service node (including the network topology connection between the service node and the OpenFlow switch and the service attributes of each node).
  • the OpenFlow controller forms a service chain according to the service application requirements and/or the service requirements of the service and the network service view, and generates corresponding forwarding policies for each service node involved in the service chain, and generates for each OpenFlow switch involved in the service chain.
  • Flow table entry (4)
  • the OpenFlow controller sends the flow table entry to the corresponding OpenFlow switch through the OpenFlow protocol, and sends the generated forwarding policy to the corresponding service node.
  • the OpenFlow switch After receiving the data packet, the OpenFlow switch forwards the data packet according to the flow table entry.
  • the packet After the packet enters a certain network from the OpenFlow switch 1, the packet is forwarded to the service node 1 according to the flow table entry. If the service node 1 does not have a local forwarding policy, after the processing is completed, the packet is sent back to the OpenFlow switch 1; the OpenFlow switch 1 further forwards the packet to the OpenFlow switch 2 according to the flow table entry; the OpenFlow switch 2 reports according to the flow table entry.
  • the message is forwarded to the service node 2; the service node 2 forwards the message to the OpenFlow switch 3 according to the local forwarding policy, and finally the packet flows out from the OpenFlow switch 3.
  • Figure 10 is an embodiment of a service control platform for transmitting service node information to a control platform according to the present invention, specifically including the following (1) - (4).
  • the service node control module in the service control platform (perceives the service node information through static configuration or other conventional means) to information of the service node, such as identity and capability attributes (service type, and/or topology connection, and/or Performance indicators (such as rate, latency, etc.) are advertised to the control platform. Of course, local policies can also be advertised to the control platform.
  • the OpenFlow controller in the control platform orchestrate the service chain according to the service application and/or the service requirements managed by the service, and the information of the service node from the service control platform, and generate corresponding forwarding for each service node involved in the service chain.
  • the policy generates a flow table entry for each OpenFlow switch involved in the service chain.
  • the service chain orchestrated service chain is based on the port information provided by the service control platform, and the control platform may not sense the specific capability attribute of the service node.
  • the OpenFlow controller sends the flow table entry to the corresponding OpenFlow switch through the OpenFlow protocol.
  • the control platform sends the forwarding policy to the corresponding service node through the control protocol.
  • the interface between the control platform and the service node is controlled by a control protocol (such as the OF-Config protocol or the OpenFlow protocol), such as policy delivery, status notification, and the like.
  • a control protocol such as the OF-Config protocol or the OpenFlow protocol
  • the forwarding policy is delivered by extending the OF-Config protocol.
  • the forwarding policy is delivered by extending the OpenFlow protocol.
  • a control platform including: an acquiring module, configured to acquire information of the service node by using an interface with a service node; or, a receiving module, configured to receive a service control platform or have a network management function
  • the information of the service node sent by the device through the northbound interface wherein the information of the service node includes: an identity identifier and a capability attribute of the service node; the control platform includes an OpenFlow controller or an OpenFlow configuration point.
  • the acquiring module is configured to acquire the information of the service node by using an interface with the service node, where the method includes: When the interface exists between the OpenFlow configuration point and the service node, the OpenFlow configuration protocol is extended, and the information of the service node is obtained from the service node by using a Get-Config message.
  • the acquiring module acquires the information of the service node by using an interface with the service node, specifically: the acquiring module extends the OpenFlow protocol, and enhances OpenFlow feature (OF-Feature) or a sub-message of a multi-part (Multipart) message to obtain information about the service node.
  • OF-Feature OpenFlow feature
  • Multipart multi-part
  • the capability attribute comprises: a service type, a topology connection, and/or a performance indicator of the service node.
  • the information of the service node further includes a local policy of the service node, where the local policy includes a static policy configured by an operator.
  • the control platform further includes: a service view forming module, configured to form a network service view by using the information of the obtained service node; wherein the network service view includes a network topology of the service node and the OpenFlow switch Connections and capability attributes of individual service nodes.
  • control platform further includes: a service chain forming module, configured to form a service chain according to a service application and/or a service requirement managed by the service, and a network service view generated by the service view forming module,
  • a service chain forming module configured to form a service chain according to a service application and/or a service requirement managed by the service
  • a network service view generated by the service view forming module
  • the OpenFlow switch generates a corresponding flow table entry, and sends the flow table entry to the corresponding OpenFlow switch through the OpenFlow protocol, and sends the forwarding policy to the corresponding service node by using a control protocol.
  • a program instructing the associated hardware such as a read-only memory, a magnetic disk, or an optical disk.
  • all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits.
  • each module/unit in the above embodiment may be implemented in the form of hardware or in the form of a software function module. The invention is not limited to any specific form of combination of hardware and software.
  • the OpenFlow control plane not only can grasp the network topology of the SDN network, but also the service nodes and their capability information attached to the network, and can dynamically arrange the service service chain as needed. Provide network services flexibly and efficiently. Therefore, it has industrial applicability.

Landscapes

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

Abstract

L'invention concerne un procédé d'obtention d'informations de capacité de nœud de desserte, et une plate-forme de contrôle. Le procédé d'obtention comprend les étapes suivantes : une plate-forme de contrôle obtient des informations relatives à un nœud de desserte via une interface entre la plate-forme de contrôle et le nœud de desserte, ou bien la plate-forme de contrôle obtient les informations relatives au nœud de desserte qui sont envoyées via une interface sud-nord par une plate-forme de contrôle de service ou un dispositif doté d'une fonction de gestion de réseau. Les informations relatives au nœud de desserte comprennent une identité et un attribut de capacité du nœud de desserte, et la plate-forme de contrôle comprend un contrôleur OpenFlow ou un point de configuration OpenFlow. Grâce à la présente invention, un plan de contrôle OpenFlow peut maîtriser une topologie de réseau, qui gère et contrôle un réseau SDN, du plan de contrôle OpenFlow. Il peut également reconnaître un nœud de desserte rattaché au réseau et des informations de capacité du nœud de desserte, et exécuter une orchestration de chaîne de service dynamique afin de fournir un service de réseau avec une flexibilité et une efficacité accrues.
PCT/CN2014/080437 2013-08-19 2014-06-20 Procédé d'obtention d'informations de capacité de nœud de desserte, et plate-forme de contrôle WO2015024411A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310362490.5 2013-08-19
CN201310362490.5A CN104426756B (zh) 2013-08-19 2013-08-19 一种服务节点能力信息的获取方法及控制平台

Publications (1)

Publication Number Publication Date
WO2015024411A1 true WO2015024411A1 (fr) 2015-02-26

Family

ID=52483037

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/080437 WO2015024411A1 (fr) 2013-08-19 2014-06-20 Procédé d'obtention d'informations de capacité de nœud de desserte, et plate-forme de contrôle

Country Status (2)

Country Link
CN (1) CN104426756B (fr)
WO (1) WO2015024411A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108600028A (zh) * 2018-05-08 2018-09-28 重庆邮电大学 适用于异构工业网络的功能型sdn北向接口系统及实现方法
US10812376B2 (en) 2016-01-22 2020-10-20 Red Hat, Inc. Chaining network functions to build complex datapaths
CN114172937A (zh) * 2022-01-19 2022-03-11 重庆邮电大学 基于深度强化学习的动态服务功能链编排方法及系统
CN114785548A (zh) * 2022-03-23 2022-07-22 中国人民解放军战略支援部队信息工程大学 基于加权自适应集成学习的虚拟流量异常检测方法、系统及流量智能监测平台

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9929945B2 (en) * 2015-07-14 2018-03-27 Microsoft Technology Licensing, Llc Highly available service chains for network services
CN107294752A (zh) * 2016-04-01 2017-10-24 中兴通讯股份有限公司 实现网络功能通信的架构、方法及装置
CN107360011A (zh) * 2016-05-10 2017-11-17 中兴通讯股份有限公司 一种业务链生成方法及系统
WO2017201722A1 (fr) * 2016-05-26 2017-11-30 华为技术有限公司 Procédé de contrôle de communication et élément de réseau associé
JP6850865B2 (ja) 2016-07-27 2021-03-31 新華三技術有限公司Ｎｅｗ Ｈ３Ｃ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．， Ｌｔｄ． データストリームの処理方法および第１ゲートウェイ設備
CN107666447B (zh) * 2016-07-27 2020-09-08 新华三技术有限公司 数据流的处理方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110211583A1 (en) * 2010-03-01 2011-09-01 Deutsche Telekom Ag Apparatus, method, manufacture, and system for providing network services from building blocks
CN103051629A (zh) * 2012-12-24 2013-04-17 华为技术有限公司 一种基于软件定义网络中数据处理的系统、方法和节点
CN103119897A (zh) * 2010-09-22 2013-05-22 日本电气株式会社 控制装置、通信系统、通信方法和其上记录有通信程序的记录介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004100010A1 (fr) * 2003-04-30 2004-11-18 Iptv Systems, Llc Systeme securise de reception en continu de donnes de telechargement dispositif a dispositif optimise au niveau du mandataire et son procede d'utilisation
CN101137191B (zh) * 2006-08-28 2012-07-18 北京三星通信技术研究有限公司 管理手机在无线通信系统间移动时的安全信息的方法
CN101296152B (zh) * 2008-06-26 2012-08-29 腾讯科技（深圳）有限公司 对等连接网络的数据调度方法和系统
US20120250496A1 (en) * 2009-11-26 2012-10-04 Takeshi Kato Load distribution system, load distribution method, and program
US8688775B2 (en) * 2010-05-28 2014-04-01 Juniper Network, Inc. Application-layer traffic optimization service spanning multiple networks

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110211583A1 (en) * 2010-03-01 2011-09-01 Deutsche Telekom Ag Apparatus, method, manufacture, and system for providing network services from building blocks
CN103119897A (zh) * 2010-09-22 2013-05-22 日本电气株式会社 控制装置、通信系统、通信方法和其上记录有通信程序的记录介质
CN103051629A (zh) * 2012-12-24 2013-04-17 华为技术有限公司 一种基于软件定义网络中数据处理的系统、方法和节点

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SONKOLY, B. ET AL.: "OpenFlow Virtualization Framework with Advanced Capabilities", 2012 EUROPEAN WORKSHOP ON SOFTWARE DEFINED NETWORKING, 26 October 2012 (2012-10-26), pages 18 - 23, Retrieved from the Internet <URL:http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6385042> *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10812376B2 (en) 2016-01-22 2020-10-20 Red Hat, Inc. Chaining network functions to build complex datapaths
CN108600028A (zh) * 2018-05-08 2018-09-28 重庆邮电大学 适用于异构工业网络的功能型sdn北向接口系统及实现方法
CN108600028B (zh) * 2018-05-08 2021-02-09 重庆邮电大学 适用于异构工业网络的功能型sdn北向接口系统及实现方法
CN114172937A (zh) * 2022-01-19 2022-03-11 重庆邮电大学 基于深度强化学习的动态服务功能链编排方法及系统
CN114172937B (zh) * 2022-01-19 2023-12-29 广州市宝思信息科技有限公司 基于深度强化学习的动态服务功能链编排方法及系统
CN114785548A (zh) * 2022-03-23 2022-07-22 中国人民解放军战略支援部队信息工程大学 基于加权自适应集成学习的虚拟流量异常检测方法、系统及流量智能监测平台
CN114785548B (zh) * 2022-03-23 2024-04-30 中国人民解放军战略支援部队信息工程大学 流量智能监测平台

Also Published As

Publication number Publication date
CN104426756B (zh) 2019-03-15
CN104426756A (zh) 2015-03-18

Similar Documents

Publication Publication Date Title
WO2015024411A1 (fr) Procédé d&#39;obtention d&#39;informations de capacité de nœud de desserte, et plate-forme de contrôle
CN107204867B (zh) 一种信息传输方法、装置和系统
Sharafat et al. Mpls-te and mpls vpns with openflow
EP2843906B1 (fr) Procédé, appareil et système de transmission de données
EP3148113B1 (fr) Procédé, appareil et système de multidiffusion pour un réseau défini par logiciel
EP2985960A1 (fr) Procédé et système de découverte de topologie réseau
JP6544401B2 (ja) パケット転送装置、制御装置、通信システム、通信方法及びプログラム
JP6648893B2 (ja) ローカルライブラリからのネットワーク接続用の機能要件の提供
JP2019500822A (ja) 仮想マシンパケット制御
TWI663854B (zh) 控制裝置、控制方法及程式
WO2021000848A1 (fr) Procédé de transfert de paquet et procédé et appareil de traitement de paquet
WO2018149338A1 (fr) Procédé de commande de duplication de flux à distance basé sdn, procédé de mise en œuvre, et dispositif associé
WO2014047784A1 (fr) Procédé pour déterminer un trajet d&#39;envoi de paquets, dispositif de réseau et dispositif de commande
WO2018068588A1 (fr) Procédé et contrôleur de réseautage défini par logiciel (sdn) destinés à fournir un service de multidiffusion
US10389618B2 (en) Distributing network path information in a network environment
WO2015035616A1 (fr) Procédé et dispositif permettant des communications multiréseaux
WO2015157979A1 (fr) Procédé et appareil pour un établissement de chemin
EP3176987A1 (fr) Dispositif de commande de communication, procédé de commande de communication, et système de communication
US9491264B2 (en) Extensible messaging and presence protocol (XMPP) based software-service-defined-network (SSDN)
WO2014187429A1 (fr) Méthode et dispositif de réalisation d&#39;une configuration de tableau des flux
JP6206493B2 (ja) 制御装置、通信システム、中継装置の制御方法及びプログラム
JP5063726B2 (ja) 仮想ノード装置のコンフィグ制御方法
JP2007243481A (ja) マルチキャストｍｐｌｓネットワーク構築方法及びマルチキャストｍｐｌｓネットワークシステム及びルータ及びプログラム
Nguyen et al. S-manage protocol for provisioning IoT applications on demand
WO2015035813A1 (fr) Procédé et appareil pour rapporter un type de commutateur

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14838645

Country of ref document: EP

Kind code of ref document: A1