CN107294746B - Method and equipment for deploying service - Google Patents

Method and equipment for deploying service Download PDF

Info

Publication number
CN107294746B
CN107294746B CN201610195390.1A CN201610195390A CN107294746B CN 107294746 B CN107294746 B CN 107294746B CN 201610195390 A CN201610195390 A CN 201610195390A CN 107294746 B CN107294746 B CN 107294746B
Authority
CN
China
Prior art keywords
service
information
deployment
affinity
logical
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201610195390.1A
Other languages
Chinese (zh)
Other versions
CN107294746A (en
Inventor
李凤凯
夏寅贲
冀智刚
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201610195390.1A priority Critical patent/CN107294746B/en
Publication of CN107294746A publication Critical patent/CN107294746A/en
Application granted granted Critical
Publication of CN107294746B publication Critical patent/CN107294746B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/22Arrangements for maintenance or administration or management of packet switching networks using GUI [Graphical User Interface]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/12Arrangements for maintenance or administration or management of packet switching networks network topology discovery or management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/50Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer
    • H04L41/5041Service implementation

Abstract

The application discloses a method and equipment for deploying services, which relate to the field of communication and can realize final service deployment according to requirement description of an application plane. The method comprises the following steps: acquiring service view information generated by an application plane, wherein the service view information comprises first description information used for describing the communication requirements among service nodes and second description information used for describing the service attributes of the service nodes, and the service nodes are entities for providing services; determining deployment view information for deploying forwarding equipment for the service node according to the service view information; and determining physical forwarding equipment deployed for the service node on a forwarding plane according to the deployment view information, and performing function configuration on the physical forwarding equipment. The embodiment of the invention is used for service deployment.

Description

Method and equipment for deploying service
Technical Field
The present invention relates to the field of communications, and in particular, to a method and an apparatus for deploying a service.
Background
With the continuous development of network device technology, Software Defined Networking (SDN) has become a hotspot, and SDN is characterized in that a control plane and a forwarding plane are decoupled, so as to support centralized network state control, and realize transparency of underlying network infrastructure to upper-layer applications, the top layer of a typical three-layer architecture of SDN is an application plane including various network services and applications, the middle control plane is mainly responsible for processing data resource arrangement, maintaining network topology, forwarding information, and the lowest forwarding plane is responsible for data processing, forwarding, and state collection. The interface between the control plane and the application plane is a northbound interface (abbreviated as NBI).
In an SDN network, a forwarding plane and a control plane of a network device are separated from each other and developed independently, so that the network is open and programmable, and further, network users, network applications or network services can flexibly control network resources and network behaviors through a northbound interface of the control plane according to service requirements. Specifically, through NBI of the control plane, a user only needs to describe abstract requirements for the network, such as connectivity, bandwidth, service deployment lifecycle, etc., and does not need to describe how the network is implemented, and the control plane can convert the user requirements described by specific syntax and semantics used by the user into control requirements for network resources.
However, in the prior art, a technical scheme for realizing final service deployment according to the requirements of an application plane has not been described yet.
Disclosure of Invention
The invention aims to provide a method and equipment for deploying services, which can realize final service deployment according to the requirement description of an application plane.
In order to achieve the purpose, the invention adopts the following technical scheme:
in a first aspect, a method for deploying a service is provided, where the method is applied to a software defined network SDN, where the SDN network includes an application plane, a control plane, and a forwarding plane, and the method includes: acquiring service view information generated by the application plane, wherein the service view information comprises first description information used for describing the communication requirements among service nodes and second description information used for describing the service attributes of the service nodes, and the service nodes are entities for providing services; determining deployment view information for deploying forwarding equipment for the service node according to the service view information; and determining physical forwarding equipment deployed for the service node on the forwarding plane according to the deployment view information, and performing function configuration on the physical forwarding equipment.
With reference to the first aspect, in a first possible implementation manner of the first aspect, the determining, according to the service view information, deployment view information for deploying a forwarding device for the service node includes: determining the service node to be a two-layer network comprising a plurality of hosts according to the second description information; determining a host set with affinity in the two-layer network according to the second description information; deploying one-to-one corresponding logic routers for each host set; and each logical router and the corresponding host set thereof are used as a connection unit.
With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the method further includes: deploying logic switches corresponding to one another for all hosts in each two-layer network, and connecting each logic switch in each two-layer network in pairs; and respectively connecting each logic switch corresponding to the host set with a logic router deployed for the host set.
With reference to the first aspect, in a third possible implementation manner of the first aspect, the determining, according to the service view information, deployment view information for deploying forwarding equipment for the service node includes: determining the service node as a single host according to the second description information; deploying a corresponding logic switch and a logic router for the single host; wherein each of the logical routers serves as a connection unit with the corresponding single host.
With reference to any one of the foregoing possible implementation manners of the first aspect, in a fourth possible implementation manner of the first aspect, the method further includes: determining a connection unit set consisting of connection units with affinity according to the second description information; for any linker in the set of linkers, there is an affinity for another linker in the set of linkers; and connecting the logical routers of the connection units with the affinity in the connection unit set.
With reference to the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the method further includes: connecting the connection unit sets, the independent connection units and the connection unit sets and the independent connection units in series through a logic router; wherein the independent linker is a linker that has no affinity for any other linker.
With reference to the first possible implementation manner of the first aspect, in a sixth possible implementation manner of the first aspect, the determining, according to the service view information, deployment view information for deploying forwarding equipment for the service node includes: determining that the service node is a three-layer network according to the second description information; and deploying corresponding logic routers for the three-layer network.
Wherein the three-tier network may include an outer three-tier network.
With reference to the first possible implementation manner of the first aspect, in a seventh possible implementation manner of the first aspect, the determining, according to the service view information, deployment view information for deploying forwarding equipment for the service node includes: determining that the service node is an external two-layer network according to the second description information; and deploying a corresponding logic switch for the external two-layer network.
With reference to the sixth or seventh possible implementation manner of the first aspect, in an eighth possible implementation manner of the first aspect, the method further includes: and determining whether connection is needed between the logical router of the connection unit and the logical router of the three-layer network or between the logical router of the external two-layer network according to the first description information.
With reference to the first aspect or any one of the foregoing possible implementations of the first aspect, in a ninth possible implementation of the first aspect, the deployment view information includes third description information used to describe a logical forwarding device deployed for each service node, and fourth description information used to describe a logical link between the logical forwarding devices; the determining, at the forwarding plane according to the deployment view information, physical forwarding devices that communicate with each of the service nodes includes: selecting physical forwarding equipment corresponding to the logic forwarding equipment on the forwarding plane according to the third description information; and selecting a physical link corresponding to the logical link between the physical forwarding devices according to the fourth description information.
With reference to the ninth possible implementation manner of the first aspect, in a tenth possible implementation manner of the first aspect, the service view information further includes service data flow information; the deployment view information further includes link attribute information; the performing function configuration on the physical forwarding device includes: and generating configuration management information according to the service data stream information and the link attribute information, and sending the configuration management information to the physical forwarding equipment, wherein the configuration management information is used for configuring the physical forwarding equipment and the physical link.
In a second aspect, a service deployment device is provided, where the service deployment device is applied to a software defined network SDN, and the service deployment device includes: an obtaining unit, configured to obtain service view information generated by an application plane of the SDN network, where the service view information includes first description information used to describe a connection requirement between service nodes and second description information used to describe service attributes of the service nodes, and the service nodes are entities providing services; a first mapping unit, configured to determine, according to the service view information, deployment view information for deploying forwarding equipment for the service node; a second mapping unit, configured to determine, according to the deployment view information, a physical forwarding device deployed for the service node on a forwarding plane of the SDN network; and the configuration unit is used for carrying out function configuration on the physical forwarding equipment.
In a first possible implementation manner combined with the second aspect, the first mapping unit is configured to: determining the service node to be a two-layer network comprising a plurality of hosts according to the second description information; determining a host set with affinity in the two-layer network according to the second description information; deploying one-to-one corresponding logic routers for each host set; and each logical router and the corresponding host set thereof are used as a connection unit.
With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the first mapping unit is configured to: deploying logic switches corresponding to one another for all hosts in each two-layer network, and connecting each logic switch in each two-layer network in pairs; and respectively connecting each logic switch corresponding to the host set with a logic router deployed for the host set.
With reference to the second aspect, in a third possible implementation manner of the second aspect, the first mapping unit is configured to: determining the service node as a single host according to the second description information; deploying a corresponding logic switch and a logic router for the single host; wherein each of the logical routers serves as a connection unit with the corresponding single host.
With reference to any one of the foregoing possible implementation manners of the second aspect, in a fourth possible implementation manner of the second aspect, the first mapping unit is configured to: determining a connection unit set consisting of connection units with affinity according to the second description information; for any linker in the set of linkers, there is an affinity for another linker in the set of linkers; and connecting the logical routers of the connection units with the affinity in the connection unit set.
With reference to the fourth possible implementation manner of the second aspect, in a fifth possible implementation manner of the second aspect, the first mapping unit is configured to: connecting the connection unit sets, the independent connection units and the connection unit sets and the independent connection units in series through a logic router; wherein the independent linker is a linker that has no affinity for any other linker.
With reference to the second possible implementation manner of the second aspect, in a sixth possible implementation manner of the second aspect, the first mapping unit is configured to: determining that the service node is a three-layer network according to the second description information; and deploying corresponding logic routers for the three-layer network.
Wherein the three-tier network comprises an outer three-tier network.
With reference to the second possible implementation manner of the second aspect, in a seventh possible implementation manner of the second aspect, the first mapping unit is configured to: determining that the service node is an external two-layer network according to the second description information; and deploying a corresponding logic switch for the external two-layer network.
With reference to the sixth or seventh possible implementation manner of the second aspect, in an eighth possible implementation manner of the second aspect, the first mapping unit is configured to: and determining whether connection is needed between the logical router of the connection unit and the logical router of the three-layer network or between the logical router of the external two-layer network according to the first description information.
With reference to the second aspect or any one of the foregoing possible implementations of the second aspect, in a ninth possible implementation of the second aspect, the deployment view information includes third description information used to describe a logical forwarding device deployed for each service node, and fourth description information used to describe a logical link between the logical forwarding devices; the second mapping unit is configured to: selecting physical forwarding equipment corresponding to the logic forwarding equipment on the forwarding plane according to the third description information; and selecting a physical link corresponding to the logical link between the physical forwarding devices according to the fourth description information.
With reference to the ninth possible implementation manner of the second aspect, in a tenth possible implementation manner of the second aspect, the service view information further includes service data flow information; the deployment view information further includes link attribute information; the configuration unit is configured to: and generating configuration management information according to the service data stream information and the link attribute information, and sending the configuration management information to the physical forwarding equipment, wherein the configuration management information is used for configuring the physical forwarding equipment and the physical link.
In a third aspect, another service deployment device is provided, including: a processor, a communication interface, a memory, and a communication bus; the processor, the communication interface and the memory complete mutual communication through the communication bus; the memory is used for storing program codes; the processor calls the program code stored by the memory for performing the first aspect, or the method of any of the possible implementations of the first aspect above.
In a fourth aspect, an SDN network is provided, which includes an application plane, a control plane, and a forwarding plane, where the application plane includes the second aspect, or any possible implementation manner of the second aspect, or the service deployment device of the third aspect; or, the control plane includes the second aspect, or any possible implementation manner of the second aspect, or the service deployment device of the third aspect.
By adopting the scheme, the service deployment equipment determines the deployment view information of the forwarding equipment deployed for the service node according to the service view information describing the user and service requirements, maps the logically deployed forwarding equipment to the physical forwarding equipment of the forwarding plane according to the deployment view information, maps the logically deployed link to the link between the physical forwarding equipment of the forwarding plane, and can generate configuration information according to the service data stream information and the link attribute information which are used for describing in the service view, so as to configure the physical forwarding equipment and the physical link, thereby realizing the final service deployment from the user and the service requirements.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic diagram of an SDN network according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of a method for deploying a service according to an embodiment of the present invention;
fig. 3 is a schematic diagram of service view information according to an embodiment of the present invention;
FIG. 4 is a schematic illustration of a deployment view information generated based on the business view information shown in FIG. 3;
fig. 5 is an example of another deployment view information generation provided by the embodiment of the present invention;
fig. 6 is a schematic diagram illustrating mapping from service view information to deployment view information according to an embodiment of the present invention.
Fig. 7 is a schematic diagram illustrating another mapping from service view information to deployment view information according to an embodiment of the present invention;
fig. 8 is a schematic diagram of another deployment view information provided by an embodiment of the present invention;
fig. 9 is a schematic diagram of a physical network resource topology of a forwarding plane according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a service deployment device according to an embodiment of the present invention;
fig. 11 is a schematic structural diagram of another service deployment device according to an embodiment of the present invention;
fig. 12a is a schematic structural diagram of an SDN network according to an embodiment of the present invention;
fig. 12b is a schematic structural diagram of another SDN network according to an embodiment of the present invention.
Detailed Description
In order to facilitate those skilled in the art to more easily understand the technical solutions provided by the embodiments of the present invention, first, terms related to the related art related to the embodiments of the present invention are briefly described below.
Referring to fig. 1, fig. 1 is an architecture diagram of an SDN network, including: an application plane 11, a control plane 12 connected to said application plane 11, and a forwarding plane 13 connected to said control plane 12.
The application plane 11 runs applications, which may be a series of application programs, which may be implemented by any number of software components residing on any number of physical or virtual platforms. The physical platform may be a physical device such as a physical server, the virtual platform may be a virtual device such as a virtual machine (VM for short), and the software component may be an application process, a thread, and the like. The application may be a network application, for example, a Bandwidth on Demand (hereinafter referred to as Bandwidth on Demand) application, an SFC application (Service Function Chaining) and the like.
The control plane 12 includes a controller, which is a software entity that can control a set of network resources. The controller may be implemented by any number of software components residing on any number of physical platforms. The controller may be a network controller, and may be OpenDaylight (a distributed network controller), ONOS (an open network operating system), Floodlight (an OpenFlow controller), or the like.
The application included in the application plane 11 may send the network requirement and the expected given network behavior to the network controller through an abstract interface provided by the network controller in a direct or programmed manner, so as to complete the description of the service requirement required by the service. The controller included in the control plane 12 can control, manage and configure network resources according to the service requirements described by the application, so as to meet the network service customization requirements.
The forwarding plane 13 is a topology network formed by a series of forwarding devices, and the forwarding devices include routers and switches, and are used for processing, forwarding and state collection of data according to control of the control plane.
The Service Node is a logical entity, which may be of different types, specifically, a user host, a two-layer network, a three-layer network, an external network, a firewall, a load balancer, a Service chain group, and the like.
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The embodiment of the invention provides a method for deploying a service, which is applied to an SDN network, wherein the SDN network comprises an application plane, a control plane and a forwarding plane, and an execution subject of the method is a service deployment device, wherein the service deployment device can be in the application plane of the SDN network or in the control plane of the SDN network.
As shown in fig. 2, the method includes:
s201, service deployment equipment acquires service view information generated by an application plane.
The service view information includes first description information for describing a requirement for connectivity between service nodes, which are entities providing a service, and second description information for describing service attributes of the service nodes.
It should be noted that the service view information may be view information generated by a network application or a network user in an application plane through programming, and used for describing user requirements, where the user requirements include connectivity requirements between service nodes, bandwidth requirements between service nodes, service data stream information of controllable service nodes, and the like. When the network application or the network user describes the requirement information, the service node that can be configured and controlled is a controllable service node, the service node that does not belong to the jurisdiction range of the network application or the network user is an uncontrollable service node, and an external three-layer network and an external two-layer network described below are uncontrollable service nodes.
And S202, the service deployment equipment determines deployment view information of the forwarding equipment deployed for the service node according to the service view information.
The deployment view information includes forwarding devices logically deployed in the service nodes, forwarding devices deployed between the service nodes, and a communication relationship between the forwarding devices. The forwarding device includes a switch and a router.
And S203, the service deployment device determines the physical forwarding device deployed for the service node on the forwarding plane according to the deployment view information, and performs function configuration on the physical forwarding device.
That is, step S203 is to map the logically deployed forwarding devices determined in step S202 onto the physical forwarding devices of the forwarding plane, and map logically connected links onto physical links between the physical forwarding devices. And further, the physical forwarding devices and physical links are configured.
By adopting the method, the service deployment equipment divides the user requirements into two stages for processing, firstly, the deployment view information is determined according to the service view information describing the user and the service requirements, and secondly, the deployment and the configuration of the actual physical forwarding equipment are determined according to the deployment view information. The two stages realize the final service deployment from the user and the service requirement, and the network application and the network user can see the composition of the network through the deployment view information.
In order to make those skilled in the art understand the technical solutions provided by the embodiments of the present invention, the following describes the steps S201 to S203 in detail.
The service view information is the intention-based Intent-based network BI mode description of the network service requirements of the network application and the network user, and the network service requirements described by using the Intent-based NBI mode are described from the mode of the network application and the network user, and only the network service requirement is described without specific network technical background and network technical details.
Specifically, the user may use the Intent-based NBI and the network service information model to describe the service view information, which may include: [ node, connection ], that is, service view information is composed of nodes and connections between the nodes. The Connection describes a Connection requirement between service nodes, that is, the first description information in step S201, where the Connection requirement includes a network application, a network resource description required by a network user, a network service process required to be performed, and the like. The node is a service node in the service view, and includes an attribute and related parameters of the node, that is, the second description information in step S201, where the second description information may include a network layer identifier of the service node, and is used to distinguish whether the service node belongs to a two-layer network or a three-layer network, and may also include an affinity identifier of the service node, and the affinity between the service nodes refers to that there is a large demand for information interaction between the service nodes, and physical proximity is required when deploying, and overhead is reduced.
Optionally, the service view information may further include service data flow information, which is used to describe forwarding and processing requirements of service flows between service nodes. The service deployment device may generate configuration information for configuring a flow table entry of the forwarding device between the service nodes according to the service data flow information.
Illustratively, referring to fig. 3, fig. 3 is a schematic diagram of traffic view information, as shown, a region a includes a service node N1 of a type of a two-layer network composed of a host h1 and a host h2, and a service node N2 of a single host type, where the host h1 and the host h2 have affinity (there is affinity between hosts within a dashed box in the figure), a region B includes a service node N3 of a type of a two-layer network composed of a host h4 and a host h5, and a region C includes a service node C of a single host type. Also, the connection relationships between hosts shown in FIG. 3 indicate connectivity requirements between the service nodes.
Further, in a possible implementation manner of the embodiment of the present invention, step S202 includes: the service deployment device determines the service node to be a two-layer network comprising a plurality of hosts according to the second description information; determining a host set with affinity in the two-layer network according to the second description information; deploying one-to-one corresponding logic router for each host set; wherein, each logic router and the corresponding host set are used as a connection unit.
Aiming at the service nodes of the two-layer network type, the service deployment equipment also deploys logic switches corresponding to one for all hosts in each two-layer network, and connects each logic switch in the two-layer network in pairs; and respectively connecting each logic switch corresponding to the host set with a logic router deployed for the host set.
Still referring to fig. 3, the service deployment device may determine, according to the second description information, that the service nodes N1 and N3 are two-layer networks including multiple hosts, where the second description information may include a network layer identifier, and the service deployment device determines, by determining the network layer identifier, which service nodes are two-layer networks, and in addition, the service deployment device may also determine, by other manners, that it is related to a manner in which the user describes attribute information of the service nodes, which is not limited in the present invention.
As shown in fig. 4, since both N1 and N3 include only two hosts with affinity, the service deployment apparatus deploys corresponding logical routers vr1 and vr3 for N1 and N3, respectively. The service deployment equipment further deploys logical switches vs1 and vs2 connected with the hosts h1 and h2 respectively, deploys logical switches vs4 and vs5 connected with the hosts h4 and h5 respectively, connects the logical switches vs1 and vs2 with the logical router vr1, and connects the logical switches vs4 and vs5 with the logical router vr 3. In addition, the logical switches vs1 and vs2 in the same two-layer network are connected, and vs4 and vs5 are connected, in this case, the service node N1, the logical switches vs1 and vs2, and the logical router vr1 are a connection unit, and the service node N3, the logical switches vs4 and vs5, and the logical router vr3 are a connection unit.
It is to be noted that, the foregoing is only an example, and there may not be affinity between hosts in the same two-layer network, as shown in fig. 5, the same two-layer network includes three hosts, i.e., h1, h2, and h3, where h1 and h2 have affinity, and h1 and h2 do not have affinity with h3, in this case, the service deployment apparatus deploys one-to-one corresponding logical switches, i.e., vs1, vs2, and vs3 shown in fig. 5, for each host in the two-layer network, deploys a corresponding logical router vr1 for a set of hosts h1 and h2, and deploys a corresponding logical router vr2 for a host h 3. And the logical switches vs1, vs2 and vs3 in the same two-layer network are connected two by two, and at this time, the hosts h1 and h2, the logical switches vs1 and vs2, and the logical router vr1 are a connection unit.
In another possible implementation manner of the embodiment of the present invention, step S202 further includes: the service deployment device determines the service node as a single host according to the second description information; deploying a corresponding logic switch and a logic router for the single host; wherein each of the logical routers and the corresponding single host serve as a connection unit.
Still by way of example in fig. 3, the service deployment apparatus may determine that the service node N4 is a single host according to the second description information, so as to, as shown in fig. 4, deploy, for the service node N4, a corresponding logical switch vs6 and logical router vr4, and connect the service node N4 with the logical switch vs6 and connect the service node N6 with the logical router vr4, in which case, the service node N4, the logical switch vs6, and the logical router vr4 are a connection unit.
Further, step S202 further includes: the service deployment equipment determines a connection unit set consisting of connection units with affinity according to the second description information; for any linker in the set of linkers, there is another linker in the set of linkers that has an affinity for it; and connecting the logical routers of the connection units with the affinity in the connection unit set.
It should be noted that, in the foregoing method steps, the connection units are divided according to the deployed logical routers, that is, one logical router corresponds to one connection unit, as can be seen from fig. 4, as described above, each logical router in fig. 4 corresponds to one connection unit, where, since N1 and N2 have affinity, the connection unit corresponding to the logical router vr1 and the logical router vr2 is a connection unit set, that is, the connection unit corresponding to the logical router vr1 and the connection unit corresponding to the logical router vr2 have affinity, and therefore, the service deployment apparatus connects the logical router vr1 and the logical router vr 2.
For another example, the connection unit set includes a first connection unit corresponding to the logical router vr1, a second connection unit corresponding to the logical router vr2, and a third connection unit corresponding to the logical router vr 3. In this case, if the first connection unit has affinity with the second connection unit, the second connection unit has affinity with the third connection unit, and the first connection unit does not have affinity with the third connection unit, the service deployment apparatus connects the logical router vr1 with the logical router vr2, and connects the logical router vr2 with the logical router vr 3; if the first connection unit has affinity with the second connection unit, the second connection unit has affinity with the third connection unit, and the first connection unit also has affinity with the third connection unit, the service deployment apparatus connects the logical router vr1 with the logical router vr2, connects the logical router vr2 with the logical router vr3, and connects the logical router vr1 with the logical router vr 3.
Further, step 202 further comprises: connecting the connection unit sets, the independent connection units and the connection unit sets and the independent connection units in series through a logic router; wherein the independent linker means a linker having no affinity to any other linker.
By way of example in fig. 4, fig. 4 includes a connection unit set, which includes two connection units corresponding to logical routers vr1 and vr2, and two independent connection units, that is, a connection unit corresponding to logical router vr3 and a connection unit corresponding to logical router vr4, as shown in fig. 4, the two independent connection units are connected in series through logical routers vr3 and vr4, and one logical router selected from the connection unit set is connected to a logical router of an independent connection unit, where fig. 4 shows that logical routers vr1 and vr3 are connected, and in a specific implementation, logical router vr1 may be connected to logical router vr4, and logical router vr2 may be connected to logical router vr3 or vr 4.
The above-described deployment manner is a deployment manner in the case that the service node is a two-layer network and a single host, and optionally, when the service view information includes a three-layer network or an external network, the step 202 further includes: and when the service node is determined to be a three-layer network according to the second description information, the service deployment equipment deploys a corresponding logic router for the three-layer network.
It is worth mentioning that the three-layer network may be an external three-layer network.
And when the service node is determined to be an external two-layer network according to the second description information, the service deployment equipment deploys a corresponding logic switch for the external two-layer network.
For a three-layer network and an external two-layer network, the service deployment device may determine, according to the first description information, whether connection is required between the logical router of the connection unit and the logical router of the three-layer network or between the logical router of the external two-layer network.
Illustratively, fig. 6 shows a service view information, including service nodes N1, N2, and N3, where the service node N1 includes hosts h1, h2, and h3, the service node N2 includes hosts h4, h5, and h6, and the service node N3 is a three-layer network or an external three-layer network, where all hosts have the same affinity. Fig. 6 also shows deployment view information obtained by the service deployment device according to the service view information, where the logical router vr1, the logical switch vs1, vs2 and vs3, and the host h1, h2 and h3 are a connection unit; the logical router vr2, the logical switches vs4, vs5 and vs6, and the hosts h4, h5 and h6 are another connection unit, and since both the two connection units have affinity, the logical router vr1 and the logical router vr2 are connected, and according to the connection requirement information included in the first description information, when it is determined that the service nodes N1 and N2 both have service interaction with N3, the service deployment information may connect the logical routers vr1 and vr2 with the logical router vr3, respectively.
As another example, fig. 7 shows another service view information, which includes service nodes N1, N2, and N3, where service node N1 includes hosts h1, h2, h3, and h4, service node N2 includes hosts h5, h6, and h7, service node N3 is an external two-layer network, hosts h1 and h2 have affinity with each other, and hosts h3, h4, h5, h6, and h7 have affinity with each other. Fig. 7 also shows deployment view information obtained by the service deployment device according to the service view information, where the logical router vr1, the logical switches vs1 and vs2, and the hosts h1 and h2 are an independent connection unit; the connection unit composed of the logical router vr2, the logical switches vs3 and vs4, and the hosts h3 and h4, the connection unit composed of the logical router vr3, the logical switch vs3, vs4 and vs5, and the hosts h5, h6, and h7 is a connection unit set, the independent connection unit is connected in series with the connection unit set through the logical router, and according to the communication demand information, when it is determined that the service node N2 and N3 have service interaction, the logical router vr3 and vs7 can be connected according to the service deployment information.
As can be seen from the above description, the deployment view information determined by the service deployment device according to the service view information includes third description information for describing the logical forwarding devices deployed for each service node, and fourth description information for describing the logical links between the logical forwarding devices. Thus, step S203 includes: and the service deployment equipment selects physical forwarding equipment corresponding to the logical forwarding equipment in the forwarding plane according to the third description information, and selects a physical link corresponding to the logical link between the physical forwarding equipment according to the fourth description information.
Illustratively, fig. 8 shows deployment view information whose connection structure is as shown, and fig. 9 shows a topological network of physical forwarding devices of the forwarding plane. When the service deployment device maps the logical forwarding device, including the logical router and the logical switch, to the physical forwarding device, the logical switch directly connected to the service node in the deployment view information may be mapped to the physical switch directly connected to the service node in the physical topology network, and the logical router directly connected to the service node in the deployment view information may be mapped to the physical router directly connected to the service node in the physical topology network. For a logical router not directly connected to a service node in the deployment view information, the service deployment device may map it to a gateway router or a core router of the forwarding plane. Referring to table1, the logical forwarding devices and the physical forwarding devices in the same row in table1 represent physical forwarding devices that map the logical forwarding devices in fig. 8 to the forwarding plane.
TABLE1
Logical forwarding device Physical forwarding device
vs1 s1
vs2 s3
vs3 s6
vs4 s10
vs5 s2
vs6 s7
vs7 s9
vr1 s5
vr2 s16
Further, referring to fig. 9, for logical links in the deployment view information, the forwarding plane has multiple physical links available for mapping, for example, for a logical link between vs1 and vs2, since vs1 maps to s1 of the forwarding plane and vs2 maps to s3 of the forwarding plane, a logical link between vs1 and vs2 may map to any physical link between s1 and s 3.
Preferably, the service deployment device may also select an optimal physical link for mapping according to related parameters such as bandwidth, delay, jitter, and the like. The mapping relationship between some logical links and the physical links of the forwarding plane in fig. 8 is shown in table 2.
TABLE2
Logical link Physical link
vs1-vs2 s1-s11-s3
vs3-vs4 s6-s15-s10
vs1-vr1 s1-s12-s5
vr1-vr2 s5-s-13-s16
Further, the service view information also includes service data flow information; if the deployment view information further includes link attribute information, step S203 further includes: and generating configuration management information according to the service data stream information and the link attribute information, and sending the configuration management information to the physical forwarding device, wherein the configuration management information is used for configuring the physical forwarding device and the physical link.
For example, still taking the deployment view information shown in fig. 8 and the forwarding plane shown in fig. 9 as an example for description, after determining the physical forwarding devices that need to be actually deployed, the service deployment device may further configure the functions of the physical forwarding devices and the related parameters of the links between the physical forwarding devices. The configuration of the switch s1 by the service deployment device is specifically described below.
For example, if network user a needs to communicate with hosts H1 and H2 in a two-tier network local to region a, hosts H1 and H2 in region a can access the host located in region B, C, and the network of network user a is isolated and exclusive, other network users cannot access the host of network user a and cannot share the network of network user a.
Based on the description information of the above requirement in the service view, the service deployment device may be configured to implement the following functions for the physical forwarding device s1 deployed in the two-layer network of the region a:
table:0, match [ [ in _ port ═ 1], instructions [ [ goto ═ 1 ]; the% Inport Table enters the message from the WAN port, and is transferred to Table1 for tunnel decapsulation processing, so as to meet the requirement of intercommunication between local regions and remote regions.
table:0, match [ [ in _ port ═ 6], instructions [ [ meta:0x1, goto ═ 2 ]; the% # InportTable enters a message from the CE port, writes a tenant identifier (metadata), and then transfers the message to table2 for routing processing, so as to implement tenant isolation.
table:1,match:[eth_type=0x8847,mpls_label=0],
instructions: [ apply: [ mpls _ pop ═ 0x0800], meta ═ 0x1, goto ═ 2 ]; % MPLSLAbel Table, tunnel decapsulation processing is carried out on the message, tenant identification (metadata) is written, and then Table2 is transferred for routing processing, so that the requirement for tunnel communication is met.
table:2,match:[meta=0x1,eth_dst=00:00:00:00:00:01],
instructions: [ apply: [ out ═ 6] ]; % MAC Table, in tenant space (metadata is consistent), carries out routing processing on the message, the destination host is local, and the message is forwarded from the CE port, so as to meet the communication requirements of the hosts H1 and H2.
table:2,match:[meta=0x1,eth_dst=00:00:00:00:00:02],
instructions: [ apply: [ mpls _ push ═ 0x8847, set _ field ═ 1, and out ═ 1 ]. % MAC Table, in the tenant space (consistent with metadata), carries out routing processing on the message, and the destination host is at the far end, carries out tunnel encapsulation on the message and forwards the message from a WAN port, so as to meet the communication requirement of other regions.
Optionally, in a case that the service view information includes service data flow information, the service forwarding device may further generate configuration information for configuring a flow entry of the forwarding device according to the service data flow information, so as to control a service packet forwarding path of the forwarding device.
By adopting the method, the service deployment equipment determines the deployment view information of the forwarding equipment deployed for the service node according to the service view information describing the user and the service requirements, the service deployment equipment maps the logically deployed forwarding equipment to the physical forwarding equipment of the forwarding plane according to the deployment view information, maps the logically deployed link to the link between the physical forwarding equipment of the forwarding plane, and can generate configuration information according to the service data stream information and the link attribute information which are used for describing in the service view, so as to configure the physical forwarding equipment and the physical link, thereby realizing the final service deployment from the user and the service requirements.
An embodiment of the present invention further provides a service deployment device 10, configured to implement the method for deploying a service provided in the foregoing method embodiment, as shown in fig. 10, where the service deployment device includes:
an obtaining unit 101, configured to obtain service view information generated by an application plane of the SDN network, where the service view information includes first description information used for describing a connection requirement between service nodes and second description information used for describing service attributes of the service nodes, and the service nodes are entities providing services;
a first mapping unit 102, configured to determine, according to the service view information, deployment view information for deploying forwarding equipment for the service node;
a second mapping unit 103, configured to determine, according to the deployment view information, a physical forwarding device deployed for the service node in a forwarding plane of the SDN network;
a configuration unit 104, configured to perform function configuration on the physical forwarding device.
Optionally, the first mapping unit 102 is configured to: determining the service node to be a two-layer network comprising a plurality of hosts according to the second description information; determining a host set with affinity in the two-layer network according to the second description information; deploying one-to-one corresponding logic routers for each host set; and each logical router and the corresponding host set thereof are used as a connection unit.
Optionally, the first mapping unit 102 is further configured to: deploying logic switches corresponding to one another for all hosts in each two-layer network, and connecting each logic switch in each two-layer network in pairs; and respectively connecting each logic switch corresponding to the host set with a logic router deployed for the host set.
Optionally, the first mapping unit 102 is further configured to: determining the service node as a single host according to the second description information; deploying a corresponding logic switch and a logic router for the single host;
wherein each of the logical routers serves as a connection unit with the corresponding single host.
Optionally, the first mapping unit 102 is further configured to: determining a connection unit set consisting of connection units with affinity according to the second description information; for any linker in the set of linkers, there is an affinity for another linker in the set of linkers; and connecting the logical routers of the connection units with the affinity in the connection unit set.
Optionally, the first mapping unit 102 is further configured to: connecting the connection unit sets, the independent connection units and the connection unit sets and the independent connection units in series through a logic router; wherein the independent linker is a linker that has no affinity for any other linker. Specifically, reference may be made to the description of fig. 3, fig. 4, and fig. 5 in the foregoing method embodiments, and details are not repeated here.
Optionally, the first mapping unit 102 is further configured to: determining that the service node is a three-layer network according to the second description information; and deploying corresponding logic routers for the three-layer network.
Wherein the three-tier network comprises an outer three-tier network.
Optionally, the first mapping unit 102 is further configured to: determining that the service node is an external two-layer network according to the second description information; and deploying a corresponding logic switch for the external two-layer network.
Optionally, the first mapping unit 102 is further configured to: and determining whether connection is needed between the logical router of the connection unit and the logical router of the three-layer network or between the logical router of the external two-layer network according to the first description information. Specifically, reference may be made to the description of fig. 3, fig. 4, and fig. 5 in the foregoing method embodiments, and details are not repeated here.
Optionally, the deployment view information includes third description information for describing a logical forwarding device deployed for each service node, and fourth description information for describing a logical link between the logical forwarding devices; the second mapping unit 103 is configured to: selecting physical forwarding equipment corresponding to the logic forwarding equipment on the forwarding plane according to the third description information; and selecting a physical link corresponding to the logical link between the physical forwarding devices according to the fourth description information.
Optionally, the service view information further includes service data flow information; the deployment view information further includes link attribute information; the configuration unit 104 is configured to: and generating configuration management information according to the service data stream information and the link attribute information, and sending the configuration management information to the physical forwarding equipment, wherein the configuration management information is used for configuring the physical forwarding equipment and the physical link. Specifically, reference is made to the description of fig. 8 and fig. 9 in the above method embodiment, and details are not repeated here.
The above division of the units performed on the service deployment apparatus 10 is only one logical function division, and there may be another division manner in actual implementation, for example, the first mapping unit 102 and the second mapping unit 103 may be divided into one processing unit, and there may be multiple implementation manners for physical implementation of each functional unit, which is not limited in this invention.
In addition, it may be clearly understood by those skilled in the art that, for convenience and simplicity of description, the specific working process of the service deployment device described above may refer to the corresponding process of the foregoing method embodiment, and details are not described herein again.
By adopting the service deployment equipment, the service deployment equipment determines deployment view information for deploying forwarding equipment for the service node according to the service view information describing user and service requirements, maps the logically deployed forwarding equipment to the physical forwarding equipment of the forwarding plane according to the deployment view information, maps the logically deployed link to the link between the physical forwarding equipment of the forwarding plane, and can generate configuration information according to the service data stream information and the link attribute information for description in the service view to configure the physical forwarding equipment and the physical link, thereby realizing final service deployment from the user and the service requirements.
An embodiment of the present invention further provides another service deployment device 11, configured to implement the method for deploying a service provided in the foregoing method embodiment, as shown in fig. 11, where the service deployment device 11 includes: a processor 111, a communication interface 112, a memory 113, and a communication bus 114; wherein, the processor 111, the communication interface 112 and the memory 113 complete mutual communication through the communication bus 114.
The processor 111 may be a multi-core central processing unit CPU or an application Specific Integrated circuit asic or one or more Integrated circuits configured to implement embodiments of the present invention.
The memory 113 is used to store program code, including computer operating instructions and network flow diagrams. The memory 113 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 113 may also be a memory array.
The communication interface 112 is used for realizing connection communication between the devices.
The service deployment device 11 is applied to an SDN network comprising an application plane, a control plane and a forwarding plane, and the processor 111 is configured to execute the program codes in the memory 113 to implement the following operations:
acquiring service view information generated by an application plane, wherein the service view information comprises first description information used for describing the communication requirements among service nodes and second description information used for describing the service attributes of the service nodes, and the service nodes are entities for providing services;
determining deployment view information for deploying forwarding equipment for the service node according to the service view information;
and determining physical forwarding equipment deployed for the service node on the forwarding plane according to the deployment view information, and performing function configuration on the physical forwarding equipment.
Optionally, the determining, according to the service view information, deployment view information for deploying forwarding equipment for the service node includes:
determining the service node to be a two-layer network comprising a plurality of hosts according to the second description information;
determining a host set with affinity in the two-layer network according to the second description information;
deploying one-to-one corresponding logic routers for each host set; and each logical router and the corresponding host set thereof are used as a connection unit.
Optionally, the operations further comprise:
deploying logic switches corresponding to one another for all hosts in each two-layer network, and connecting each logic switch in each two-layer network in pairs;
and respectively connecting each logic switch corresponding to the host set with a logic router deployed for the host set.
Optionally, the determining, according to the service view information, deployment view information for deploying forwarding equipment for the service node includes:
determining the service node as a single host according to the second description information;
deploying a corresponding logic switch and a logic router for the single host;
wherein each of the logical routers serves as a connection unit with the corresponding single host.
Optionally, the operations further comprise:
determining a connection unit set consisting of connection units with affinity according to the second description information; for any linker in the set of linkers, there is an affinity for another linker in the set of linkers;
and connecting the logical routers of the connection units with the affinity in the connection unit set.
Optionally, the operations further comprise:
connecting the connection unit sets, the independent connection units and the connection unit sets and the independent connection units in series through a logic router; wherein the independent linker is a linker that has no affinity for any other linker.
Optionally, the determining, according to the service view information, deployment view information for deploying forwarding equipment for the service node includes:
determining that the service node is a three-layer network according to the second description information;
and deploying corresponding logic routers for the three-layer network.
Optionally, the three-layer network comprises an outer three-layer network.
Optionally, the determining, according to the service view information, deployment view information for deploying forwarding equipment for the service node includes:
determining that the service node is an external two-layer network according to the second description information;
and deploying a corresponding logic switch for the external two-layer network.
Optionally, the operations further comprise:
and determining whether connection is needed between the logical router of the connection unit and the logical router of the three-layer network or between the logical router of the external two-layer network according to the first description information.
Optionally, the deployment view information includes third description information for describing a logical forwarding device deployed for each service node, and fourth description information for describing a logical link between the logical forwarding devices; the determining, at the forwarding plane according to the deployment view information, physical forwarding devices that communicate with each of the service nodes includes:
selecting physical forwarding equipment corresponding to the logic forwarding equipment on the forwarding plane according to the third description information;
and selecting a physical link corresponding to the logical link between the physical forwarding devices according to the fourth description information.
Optionally, the service view information further includes service data flow information; the deployment view information further includes link attribute information; the performing function configuration on the physical forwarding device includes:
and generating configuration management information according to the service data stream information and the link attribute information, and sending the configuration management information to the physical forwarding equipment, wherein the configuration management information is used for configuring the physical forwarding equipment and the physical link.
The processor 111 in the embodiment of the present invention may be a Central Processing Unit (CPU). In addition, in order to save the computing resource of the CPU, the processor 111 may also be a Field Programmable Gate Array (Field Programmable Gate Array, abbreviated as FPGA) or other hardware to implement all operations of the service deployment device to deploy the service in the embodiment of the present invention, or the processor 111 may also be the CPU and the FPGA or other hardware, and the FPGA or other hardware and the CPU respectively execute part of the operations of the service deployment device to deploy the service in the embodiment of the present invention. For convenience of description, the processor 111 uniformly described in the embodiment of the present invention implements the operation of deploying the service by the service deployment device in the embodiment of the present invention, which may specifically refer to the description corresponding to the foregoing method embodiment, and details are not described here again.
An embodiment of the present invention further provides an SDN network, as shown in fig. 12a and 12b, where the SDN network includes: an application plane 121, a control plane 122 and a forwarding plane 123.
In a possible implementation manner of the embodiment of the present invention, as shown in fig. 12a, the application plane 121 includes the service deployment device shown in fig. 10 or fig. 11, and specifically, the description corresponding to fig. 10 or fig. 11 may be referred to, and is not described again here.
In another possible implementation manner of the embodiment of the present invention, as shown in fig. 12b, the control plane includes the service deployment device shown in fig. 10 or fig. 11, and specifically, the description corresponding to fig. 10 or fig. 11 may be referred to, and details are not repeated here.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other media capable of storing program codes.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims (24)

1. A method for deploying a service, the method being applied to a software defined network, SDN, comprising an application plane, a control plane and a forwarding plane, the method comprising:
acquiring service view information generated by the application plane, wherein the service view information comprises first description information used for describing the communication requirements among service nodes and second description information used for describing the service attributes of the service nodes, and the service nodes are entities for providing services;
determining deployment view information for deploying forwarding equipment for the service node according to the service view information;
and determining physical forwarding equipment deployed for the service node on the forwarding plane according to the deployment view information, and performing function configuration on the physical forwarding equipment.
2. The method of claim 1, wherein the determining deployment view information for deploying forwarding devices for the service nodes according to the service view information comprises:
determining the service node to be a two-layer network comprising a plurality of hosts according to the second description information;
determining a host set with affinity in the two-layer network according to the second description information, wherein the host set with affinity comprises a plurality of hosts with affinity, and the interaction information requirement between the hosts with affinity is greater than that between the hosts without affinity;
deploying one-to-one corresponding logic routers for each host set; and each logical router and the corresponding host set thereof are used as a connection unit.
3. The method of claim 2, further comprising:
deploying logic switches corresponding to one another for all hosts in each two-layer network, and connecting each logic switch in each two-layer network in pairs;
and respectively connecting each logic switch corresponding to the host set with a logic router deployed for the host set.
4. The method of claim 1, wherein the determining deployment view information for deploying forwarding devices for the service nodes according to the service view information comprises:
determining the service node as a single host according to the second description information;
deploying a corresponding logic switch and a logic router for the single host;
wherein each of the logical routers serves as a connection unit with the corresponding single host.
5. The method according to any one of claims 2 to 4, further comprising:
determining a connection unit set consisting of connection units with affinity according to the second description information, wherein the connection unit set with affinity comprises a plurality of connections with affinity, the interaction information requirement between the connections with affinity is greater than that between the connection units without affinity, and for any connection unit in the connection unit set, another connection unit in the connection unit set has affinity with the connection unit;
and connecting the logical routers of the connection units with the affinity in the connection unit set.
6. The method of claim 5, further comprising:
connecting the connection unit sets, the independent connection units and the connection unit sets and the independent connection units in series through a logic router; wherein the independent linker is a linker that has no affinity for any other linker.
7. The method of claim 2, wherein the determining deployment view information for deploying forwarding devices for the service nodes according to the service view information comprises:
determining that the service node is a three-layer network according to the second description information, and deploying a corresponding logic router for the three-layer network; alternatively, the first and second electrodes may be,
and determining that the service node is an external two-layer network according to the second description information, and deploying a corresponding logic switch for the external two-layer network.
8. The method of claim 7, wherein the three-tier network comprises an outer three-tier network.
9. The method according to any one of claims 7 to 8, further comprising:
determining whether connection between the logical router of the connection unit and the logical router of the three-layer network is needed according to the first description information; alternatively, the first and second electrodes may be,
and determining whether the connection between the logical router of the connection unit and the logical switch of the external two-layer network is needed according to the first description information.
10. The method according to claim 1, wherein the deployment view information includes third description information for describing logical forwarding devices deployed for each of the service nodes, and fourth description information for describing logical links between the logical forwarding devices; the determining, at the forwarding plane according to the deployment view information, physical forwarding devices that communicate with each of the service nodes includes:
selecting physical forwarding equipment corresponding to the logic forwarding equipment on the forwarding plane according to the third description information;
and selecting a physical link corresponding to the logical link between the physical forwarding devices according to the fourth description information.
11. The method of claim 10, wherein the traffic view information further comprises traffic data flow information; the deployment view information further includes link attribute information; the performing function configuration on the physical forwarding device includes:
and generating configuration management information according to the service data stream information and the link attribute information, and sending the configuration management information to the physical forwarding equipment, wherein the configuration management information is used for configuring the physical forwarding equipment and the physical link.
12. A service deployment device, wherein the service deployment device is applied to a Software Defined Network (SDN), and the service deployment device comprises:
an obtaining unit, configured to obtain service view information generated by an application plane of the SDN network, where the service view information includes first description information used to describe a connection requirement between service nodes and second description information used to describe service attributes of the service nodes, and the service nodes are entities providing services;
a first mapping unit, configured to determine, according to the service view information, deployment view information for deploying forwarding equipment for the service node;
a second mapping unit, configured to determine, according to the deployment view information, a physical forwarding device deployed for the service node on a forwarding plane of the SDN network;
and the configuration unit is used for carrying out function configuration on the physical forwarding equipment.
13. The service deployment device of claim 12, wherein the first mapping unit is configured to:
determining the service node to be a two-layer network comprising a plurality of hosts according to the second description information;
determining a host set with affinity in the two-layer network according to the second description information, wherein the host set with affinity comprises a plurality of hosts with affinity, and the interaction information requirement between the hosts with affinity is greater than that between the hosts without affinity;
deploying one-to-one corresponding logic routers for each host set; and each logical router and the corresponding host set thereof are used as a connection unit.
14. The service deployment device of claim 13, wherein the first mapping unit is configured to:
deploying logic switches corresponding to one another for all hosts in each two-layer network, and connecting each logic switch in each two-layer network in pairs;
and respectively connecting each logic switch corresponding to the host set with a logic router deployed for the host set.
15. The service deployment device of claim 12, wherein the first mapping unit is configured to:
determining the service node as a single host according to the second description information;
deploying a corresponding logic switch and a logic router for the single host;
wherein each of the logical routers serves as a connection unit with the corresponding single host.
16. The service deployment device according to any one of claims 13 to 15, wherein the first mapping unit is configured to:
determining a connection unit set consisting of connection units with affinity according to the second description information, wherein the connection unit set with affinity comprises a plurality of connections with affinity, the interaction information requirement between the connections with affinity is greater than that between the connection units without affinity, and for any connection unit in the connection unit set, another connection unit in the connection unit set has affinity with the connection unit;
and connecting the logical routers of the connection units with the affinity in the connection unit set.
17. The service deployment device of claim 16, wherein the first mapping unit is configured to:
connecting the connection unit sets, the independent connection units and the connection unit sets and the independent connection units in series through a logic router; wherein the independent linker is a linker that has no affinity for any other linker.
18. The service deployment device of claim 13, wherein the first mapping unit is configured to:
determining that the service node is a three-layer network according to the second description information, and deploying a corresponding logic router for the three-layer network; alternatively, the first and second electrodes may be,
and determining that the service node is an external two-layer network according to the second description information, and deploying a corresponding logic switch for the external two-layer network.
19. The service deployment device of claim 18 wherein the three-layer network comprises an outer three-layer network.
20. The service deployment device of any one of claims 18 to 19, wherein the first mapping unit is configured to:
determining whether connection between the logical router of the connection unit and the logical router of the three-layer network is needed according to the first description information; alternatively, the first and second electrodes may be,
and determining whether the connection between the logical router of the connection unit and the logical switch of the external two-layer network is needed according to the first description information.
21. The service deployment device according to claim 12, wherein the deployment view information includes third description information for describing a logical forwarding device deployed for each of the service nodes, and fourth description information for describing a logical link between the logical forwarding devices; the second mapping unit is configured to:
selecting physical forwarding equipment corresponding to the logic forwarding equipment on the forwarding plane according to the third description information;
and selecting a physical link corresponding to the logical link between the physical forwarding devices according to the fourth description information.
22. The service deployment device of claim 21, wherein the service view information further comprises service data flow information; the deployment view information further includes link attribute information; the configuration unit is configured to:
and generating configuration management information according to the service data stream information and the link attribute information, and sending the configuration management information to the physical forwarding equipment, wherein the configuration management information is used for configuring the physical forwarding equipment and the physical link.
23. A service deployment device, comprising: a processor, a communication interface, a memory, and a communication bus; the processor, the communication interface and the memory complete mutual communication through the communication bus;
the memory is used for storing program codes;
the processor calls the program code stored in the memory for executing the method of any one of claims 1 to 11.
24. An SDN network comprising an application plane, a control plane and a forwarding plane, wherein the application plane comprises the service deployment device of any one of claims 12 to 23; alternatively, the first and second electrodes may be,
the control plane comprises the service deployment device of any of claims 12 to 23.
CN201610195390.1A 2016-03-30 2016-03-30 Method and equipment for deploying service Active CN107294746B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610195390.1A CN107294746B (en) 2016-03-30 2016-03-30 Method and equipment for deploying service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610195390.1A CN107294746B (en) 2016-03-30 2016-03-30 Method and equipment for deploying service

Publications (2)

Publication Number Publication Date
CN107294746A CN107294746A (en) 2017-10-24
CN107294746B true CN107294746B (en) 2020-09-11

Family

ID=60086697

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610195390.1A Active CN107294746B (en) 2016-03-30 2016-03-30 Method and equipment for deploying service

Country Status (1)

Country Link
CN (1) CN107294746B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109361605B (en) * 2018-11-26 2021-05-04 武汉烽火技术服务有限公司 Dual-IP deployment service protection method and system for transmission network system
CN111600754B (en) * 2020-05-11 2022-02-25 重庆邮电大学 Industrial heterogeneous network scheduling method for interconnection of TSN (transmission time network) and non-TSN (non-Transmission time network)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101621401A (en) * 2008-06-30 2010-01-06 华为技术有限公司 Network management configuration method based on northbound interface and device
CN102439904A (en) * 2011-07-27 2012-05-02 华为技术有限公司 Service realizing method and device based on north interface
CN104753713A (en) * 2013-12-31 2015-07-01 华为技术有限公司 SDN (Self-Defending Network) service deployment method and SDN controller
CN105357112A (en) * 2014-08-19 2016-02-24 华为技术有限公司 Communication method and device in software defined network

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9491264B2 (en) * 2014-02-20 2016-11-08 Futurewei Technologies, Inc. Extensible messaging and presence protocol (XMPP) based software-service-defined-network (SSDN)

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101621401A (en) * 2008-06-30 2010-01-06 华为技术有限公司 Network management configuration method based on northbound interface and device
CN102439904A (en) * 2011-07-27 2012-05-02 华为技术有限公司 Service realizing method and device based on north interface
CN104753713A (en) * 2013-12-31 2015-07-01 华为技术有限公司 SDN (Self-Defending Network) service deployment method and SDN controller
CN105357112A (en) * 2014-08-19 2016-02-24 华为技术有限公司 Communication method and device in software defined network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
基于Intent的SDN北向接口研究综述;张岩等;《信息通信技术》;20160229(第1期);第52-56页 *

Also Published As

Publication number Publication date
CN107294746A (en) 2017-10-24

Similar Documents

Publication Publication Date Title
CN103997414B (en) Generate method and the network control unit of configuration information
US10320664B2 (en) Cloud overlay for operations administration and management
US10812374B2 (en) Segment routing with fast reroute for container networking
CN105706043B (en) The list handling capacity of push type link
CN105791463B (en) A kind of method and apparatus for realizing virtual machine communication
CN109716717A (en) From software-defined network controller management virtual port channel switching equipment peer-to-peer
CN103346900B (en) Method for configuring route after live migration of virtual machine and gateway in big double layer network
CN107211036B (en) Networking method for data center network and data center network
CN104717081B (en) The implementation method and device of a kind of gateway function
CN107733795B (en) Ethernet virtual private network EVPN and public network intercommunication method and device
CN107113241B (en) Route determining method, network configuration method and related device
CN107404436A (en) Communication means and device for virtual expansible LAN
CN109218053A (en) Implementation method, system and the storage medium of virtual data center
CN106878136A (en) A kind of message forwarding method and device
CN109547349A (en) Flow managing method, device, terminal and storage medium based on virtual flow-line
CN108123819B (en) Virtual-real network seamless fusion simulation method
CN111147372A (en) Downlink message sending and forwarding method and device
CN107294746B (en) Method and equipment for deploying service
CN110311860A (en) Multi-link load balance method and device under VXLAN
CN108494607A (en) The design method and system of big double layer network framework based on container
KR20210093312A (en) Logic routers with segmented network elements
CN106936731A (en) The method and apparatus of the message forwarding in software defined network SDN
CN109412922B (en) Method, forwarding device, controller and system for transmitting message
CN106209554A (en) Message forwarding method and equipment across virtual expansible LAN
KR101800320B1 (en) Network on chip system based on bus protocol, design method for the same and computer readable recording medium in which program of the design method is recorded

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant