CN110063050B - Service scheduling method and system - Google Patents
Service scheduling method and system Download PDFInfo
- Publication number
- CN110063050B CN110063050B CN201680091545.5A CN201680091545A CN110063050B CN 110063050 B CN110063050 B CN 110063050B CN 201680091545 A CN201680091545 A CN 201680091545A CN 110063050 B CN110063050 B CN 110063050B
- Authority
- CN
- China
- Prior art keywords
- connection
- request information
- client device
- network
- existing
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
Abstract
The application discloses a service scheduling method, which comprises the following steps: receiving request information, and obtaining a source client device identifier, a destination client device identifier and a content tag from the request information; obtaining a network topology meeting the request information according to the source client device identification and the destination client device identification; judging whether a first connection exists in the network topology according to the network topology and the content label, wherein the first connection and the existing connection in the network have a superposition part, and the service requested by the request information has the same content as the service transmitted by the existing connection; if the first connection exists, establishing a second connection according to the part of the first connection which is not overlapped with the existing connection, and taking the overlapped part of the existing connection and the second connection together as the connection meeting the request information; a message is sent that the connection satisfying the request information was successfully established. The scheduling method disclosed by the application can utilize the existing connection in the network, and plays a role in improving the utilization efficiency of network resources.
Description
Technical Field
The application relates to the technical field of communication, in particular to a service scheduling method and system based on a Software Defined Network (SDN).
Background
At present, the application of Software Defined Network (SDN) technology makes Network control go from distributed to centralized, the control plane of Network devices is simplified, and the control function is raised to a centralized controller, which can be used for issuing Network services and configuring Network devices. In such a Network deployment, there is one controller and a plurality of Network devices, i.e., a plurality of Network Elements (NEs). The NE and the controller are connected through a standard interface (generally called SDN southbound interface) to realize the control of the controller on the NE; and the other end of the controller is typically connected to the network user, i.e., the client device. A typical SDN architecture is shown in fig. 1, which is composed of 3 parts, from top to bottom, an application layer controller (client controller), an SDN controller and a Network Equipment (NE).
An existing service scheduling method based on the SDN architecture adopts an unaware mode, that is, if an application layer controller receives a request 1 and needs to establish a connection between a NE1 and a NE2, the application layer controller requests the SDN controller to establish a Label Switched Path (LSP) between the corresponding NEs. If the application layer controller receives request 2 and needs to establish a connection between NE1 and NE3, it requests the SDN controller to establish another LSP between the corresponding NEs. The LSP may be established by some mature southbound technologies, such as Path Computing Element Protocol (PCEP), for data transfer between corresponding NEs.
However, with the existing service scheduling method, the SDN controller cannot sense the content that needs to be transferred between the client devices, and when a large amount of repeated content exists in the network, the use efficiency of network resources is greatly reduced.
Disclosure of Invention
The embodiment of the application provides a service scheduling method, which solves the problem that the use efficiency of network resources is reduced when a large amount of repeated contents exist in a network by sensing the contents needing to be transmitted among client devices.
In a first aspect, a method for scheduling a service is provided, including: receiving request information, and obtaining a source client device identification, a sink client device identification and a content tag from the request information, wherein the request information is used for requesting to transfer service between a source client device and a sink client device, and the content tag is used for identifying the content of the service requested by the request information; obtaining a network topology meeting the request information according to the source client equipment identification and the destination client equipment identification; judging whether a first connection exists in the network topology or not according to the network topology and the content label, wherein the first connection and an existing connection in the network have a superposition part, and the service requested by the request information is the same as the service content transmitted by the existing connection; if the first connection exists, establishing a second connection according to the part which is not overlapped with the existing connection in the first connection, and taking the overlapped part of the existing connection and the second connection together as the connection meeting the request information; and sending a message that the connection meeting the request information is successfully established.
According to the scheduling method provided by the embodiment of the application, the network connection can be efficiently and reasonably established by sensing the service content needing to be transmitted between the client devices, so that the utilization efficiency of network resources is improved.
With reference to the first aspect, in a first possible implementation manner of the first aspect, the first connection completely coincides with an existing connection in the network; establishing a second connection according to a part of the first connection which is not overlapped with the existing connection, and taking the overlapped part of the existing connection and the second connection together as a connection meeting the request information, which specifically comprises the following steps: and the existing connection is used as the connection meeting the request information.
With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, after determining whether the first connection exists in the network topology, the method further includes: and if the first connection does not exist, establishing the second connection, and using the second connection as the connection meeting the request information.
With reference to the first aspect, in a third possible implementation manner of the first aspect, if the first connection exists, establishing a second connection according to a portion of the first connection that is not overlapped with the existing connection includes: if a plurality of first connections exist, comparing the number of links included in the parts of the plurality of first connections which are not overlapped with the existing connections, selecting one connection with the least number of links in the non-overlapped parts, and establishing a second connection according to the selected non-overlapped parts of the connections, wherein the links are information transmission paths between different network elements or between the network elements and client equipment.
With reference to the first aspect or any one possible implementation manner of the first to third possible implementation manners of the first aspect, in a fourth possible implementation manner of the first aspect, the receiving request information, and obtaining a source client device identifier, a sink client device identifier, and a content tag from the request information specifically include: simultaneously receiving N pieces of request information, and obtaining a source client device identifier, a destination client device identifier and a content tag from each piece of request information, wherein N is a positive integer greater than 1; before obtaining a network topology that satisfies the requested information based on the source client device identification and the sink client device identification, the method further comprises: and merging the request information with the same source client device identification, sink client device identification and content label. The embodiment of the application combines the same request information in advance, and each request information does not need to be compared with the existing connection, so that the operation flow is simplified.
In a second aspect, a software defined network, SDN, controller is provided, comprising: the system comprises a receiving module, a processing module and a sending module, wherein the receiving module is used for receiving request information, obtaining a source client device identifier, a destination client device identifier and a content tag from the request information, obtaining a network topology meeting the request information according to the source client device identifier and the destination client device identifier, and sending the content tag and the network topology to the processing module, wherein the request information is used for requesting to transfer service between the source client device and the destination client device, and the content tag is used for identifying the content of the service requested by the request information; the processing module is configured to determine whether a first connection exists in the network topology according to the network topology and the content tag, where the first connection and an existing connection in the network have a superposition portion, and the service requested by the request information is the same as the service content transmitted by the existing connection; if the first connection exists, establishing a second connection according to the part which is not overlapped with the existing connection in the first connection, and taking the overlapped part of the existing connection and the second connection together as the connection meeting the request information; and the sending module is used for sending out a message that the connection meeting the request information is successfully established.
The SDN controller provided by the embodiment of the application efficiently and reasonably establishes network connection by sensing the content needing to be transmitted among the client devices, so that the utilization efficiency of network resources is improved.
With reference to the second aspect, in a first possible implementation manner of the second aspect, the first connection is completely overlapped with an existing connection in a network; the processing module is further configured to use the existing connection as a connection that satisfies the request information.
With reference to the second aspect or the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the processing module is further configured to establish the second connection if the first connection does not exist, and use the second connection as a connection that satisfies the request information.
With reference to the second aspect, in a third possible implementation manner of the second aspect, the processing module is further configured to, if there are multiple first connections, compare the number of links included in a part of the multiple first connections that is not overlapped with the existing connections, select one connection with the smallest number of links in the non-overlapped part, and establish a second connection according to the selected non-overlapped part of the selected connection, where the links are information transmission paths between different network elements or between the network elements and a client device.
With reference to the second aspect or any one possible implementation manner of the first to third possible implementation manners of the second aspect, in a fourth possible implementation manner of the second aspect, the receiving module is further configured to receive N pieces of request information simultaneously, and obtain, from each piece of request information, a source client device identifier, a sink client device identifier, and a content tag, where N is a positive integer greater than 1; the processing module is further configured to merge the request information with the same source client device identifier, sink client device identifier, and content tag before obtaining a network topology that satisfies the request information according to the source client device identifier and the sink client device identifier. The embodiment of the application combines the same request information in advance, and each request information does not need to be compared with the existing connection, so that the operation flow is simplified.
In a third aspect, a service scheduling system is provided, including: a plurality of client devices, a client controller, an SDN controller and a plurality of network elements NEs, wherein the client devices are configured to generate request information, add a content tag to the request information, and send the request information to the client controller, wherein the request information is used to request a service to be transferred between a source client device and a sink client device, and the content tag is used to identify the content of the service requested by the request information; the client controller is used for sending the request information to the SDN controller; the SDN controller is configured to obtain the source client device identifier, the destination client device identifier, and the content tag from the request information, and obtain a network topology that satisfies the request information according to the source client device identifier and the destination client device identifier; judging whether a first connection exists in the network topology or not according to the network topology and the content label, wherein the first connection and an existing connection in the network have a superposition part, and the service requested by the request information is the same as the service content transmitted by the existing connection; if the first connection exists, establishing a second connection according to a part which is not overlapped with the existing connection in the first connection, taking the overlapped part of the existing connection and the second connection together as the connection meeting the request information, and sending a control instruction to an NE (NE) through which the second connection passes, wherein the control instruction is used for indicating to modify the connection relation of the NE; sending a message to the client controller that the connection satisfying the request information is successfully established; and the NE through which the second connection passes is used for establishing the second connection according to the control instruction.
In a fourth aspect, a service scheduling system is provided, which includes a plurality of client devices for transceiving services, and further includes: the SDN gateway comprises a client controller, an SDN controller and a plurality of Network Elements (NE), wherein the client controller is used for generating request information, adding a content label to the request information, and sending the request information to the SDN client controller, wherein the request information is used for requesting to transfer service between a source client device and a sink client device, and the content label is used for identifying the content of the service requested by the request information; the SDN controller is configured to obtain the source client device identifier, the destination client device identifier, and the content tag from the request information, and obtain a network topology that satisfies the request information according to the source client device identifier and the destination client device identifier; judging whether a first connection exists in the network topology or not according to the network topology and the content label, wherein the first connection and an existing connection in the network have a superposition part, and the service requested by the request information is the same as the service content transmitted by the existing connection; if the first connection exists, establishing a second connection according to a part which is not overlapped with the existing connection in the first connection, taking the overlapped part of the existing connection and the second connection together as a connection meeting the request information, and sending a control instruction to an NE (NE) through which the first connection passes, wherein the control instruction is used for indicating to modify the connection relation of the NE; sending a message to the client controller that the connection satisfying the request information is successfully established; and the NE through which the second connection passes is used for establishing the second connection according to the control instruction.
With reference to the third aspect or the fourth aspect, in a first possible implementation manner of the third aspect or the fourth aspect, the first connection coincides with an existing connection in a network; the SDN controller is further configured to use the existing connection as a connection that satisfies the request information.
With reference to the third aspect or the first possible implementation manner of the fourth aspect, in a second possible implementation manner of the third aspect or the fourth aspect, the SDN controller is further configured to establish the second connection if the first connection does not exist, and use the second connection as a connection that satisfies the request information.
With reference to the third aspect or the fourth aspect, in a third possible implementation manner of the third aspect or the fourth aspect, the SDN controller is further configured to, if there are multiple first connections, compare a number of links included in a portion, which is not overlapped with the existing connection, of the multiple first connections, select one connection, which has the smallest number of links, of the non-overlapped portion, and establish a second connection according to the selected non-overlapped portion of the connection, where the links are information transmission paths between different network elements or between the network elements and a client device.
With reference to any one possible implementation manner of the third aspect or the first to third possible implementation manners of the third aspect or any one possible implementation manner of the fourth aspect or the first to third possible implementation manners of the fourth aspect, in a fourth possible implementation manner of the third aspect or the fourth aspect, the SDN controller is further configured to receive N pieces of request information at the same time, obtain a source client device identifier, a sink client device identifier, and a content tag from each piece of request information, and merge the pieces of request information with the same source client device identifier, the same sink client device identifier, and the same content tag, where N is a positive integer greater than 1. The embodiment of the application combines the same request information in advance, and each request information does not need to be compared with the existing connection, so that the operation flow is simplified.
In a fifth aspect, a computer-readable storage medium is provided, where computer-executable instructions are stored in the computer-readable storage medium, and when at least one processor of a device executes the computer-executable instructions, the device executes the service scheduling method provided in the first aspect or any possible implementation manner of the first aspect.
In a sixth aspect, a computer program product is provided, the computer program product comprising computer executable instructions, the computer executable instructions being stored in a computer readable storage medium; the at least one processor of the device may read the computer executable instructions from the computer readable storage medium, and the execution of the computer executable instructions by the at least one processor causes the device to implement the traffic scheduling method provided by the first aspect or any one of the possible implementations of the first aspect.
According to the scheduling method provided by the embodiment of the application, the network connection can be efficiently and reasonably established by sensing the service content needing to be transmitted between the client devices, so that the utilization efficiency of network resources is improved.
Drawings
Figure 1 is a diagram of a typical existing SDN architecture;
FIG. 2 is a basic architecture diagram of a DCI network;
fig. 3 is a flowchart of a service scheduling method according to an embodiment of the present application;
FIG. 4 is a DCI network architecture diagram employed in another embodiment of the present application;
FIG. 5 is a DCI network architecture diagram employed in another embodiment of the present application;
FIG. 6 is a DCI network architecture diagram employed in another embodiment of the present application;
fig. 7 is an SDN controller according to another embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
As is well known, a typical application scenario of SDN is Data Center Interconnection (DCI), and a large number of enterprise or carrier-level applications need to implement Data transmission between Data Centers (DCs) through a network, in this scenario, each DC is accessed into the DCI network through a NE connected to the DC, the basic architecture of the DCI network is shown in fig. 2, a DC controller is used to collect demands of different DCs, send the demands to an SDN controller, and the SDN controller establishes connections between NEs according to the demands.
An embodiment of the present application provides a service scheduling method, as shown in fig. 3, including:
301. receiving the request information, and obtaining the source client device identification, the sink client device identification and the content tag from the request information.
Wherein the request information is for requesting that traffic be communicated between the source client device and the sink client device; optionally, the service is a real-time service; the content label is used for identifying the content of the service requested by the request information; when the method is applied to the DCI network, the client controller is the DC controller, and the client device refers to the DC.
302. And obtaining the network topology meeting the request information according to the source client device identification and the destination client device identification.
It should be noted that, the SDN controller stores the network topology between any source client device and any sink client device in the network, so that the network topology between the two client devices can be known as long as it is determined between which two client devices the requested information request is to transfer the service, where the source client device identifier and the sink client device identifier indicate between which two client devices the requested information request is to transfer the service. The network topology comprises nodes and links, the nodes refer to NEs and the links refer to all connections connected to the NEs, including connections with client devices on one side and NEs on the other side, in other words, all possible connection relationships between the two client devices are known as long as the network topology is known.
303. And judging whether the first connection exists in the network topology or not according to the network topology and the content label.
The first connection has a part overlapping with an existing connection in the network, that is, the first connection is a connection partially or completely overlapping with any existing connection in the network, and the service requested by the request information is the same as the service content transferred by the existing connection in the network.
304. If the first connection exists, establishing a second connection according to the part of the first connection which is not overlapped with the existing connection, and taking the overlapped part of the existing connection and the second connection together as the connection meeting the request information.
Specifically, taking the first connection and a part of an existing connection in the network as an example, the following description is made: as shown in fig. 2, assume that there exists a connection DC1-NE1-NE2-NE3-DC2 in the network for transferring the first service, which is denoted as existing connection 1; the request for information requests that the first service be communicated between DC1 and DC3, then the network has a first connection; the connection DC1-NE1-NE2-NE3-NE5-DC3 in the network topology is overlapped with a part of the existing connection 1, and the transmitted traffic is also the same, so that DC1-NE1-NE2-NE3-NE5-DC3 is the first connection. Sharing the overlapping part of the existing connection 1 and the first connection (DC1-NE1-NE2-NE3), establishing a second connection based on the non-overlapping part of the first connection and the existing connection 1 (NE3-NE5-DC3), the combination of which can be used to transfer the first traffic between DC1 and DC 3. The method utilizes the existing connection in the network, does not need to newly establish the complete connection between the DC1 and the DC3, and saves network resources.
305. A message is sent that the connection satisfying the request message was successfully established.
Alternatively, if the first connection completely coincides with an existing connection in the network, step 302 may be simplified as: and judging whether a first connection exists in the network topology or not according to the network topology and the content label, and if so, taking the existing connection superposed with the first connection as the connection meeting the request information.
Further, if the first connection does not exist, a second connection is established as a connection satisfying the request information. Specifically, the second connection may be established according to a structure of a connection with the least links in the network topology, where the links are information transmission paths between different network elements or between the network elements and the client device.
Optionally, if there are multiple first connections, one of the first connections needs to be selected according to a principle that a network resource utilization rate is highest, and the specific manner is as follows: and comparing the number of links included in the part of the plurality of first connections which is not overlapped with the existing connection, selecting one connection with the least number of links in the non-overlapped part, and establishing a second connection according to the non-overlapped part of the selected connection. The newly-built connection required by the scheme has the minimum number of links and the minimum burden on the network.
Specifically, as shown in fig. 4, it is assumed that two connections for transferring the second service exist in the network, and DC1-NE1-NE2-NE3-DC4 and DC1-NE1-NE6-NE5-NE4-DC3 are respectively marked as existing connection 2 and existing connection 3; the request information requests that the second service is transferred between DC1 and DC2, and there are two connections in the network topology that satisfy the request information, where connection 1 is DC1-NE1-NE2-NE3-NE4-NE5-DC2, and connection 2 is DC1-NE1-NE6-NE5-DC 2. Since the existing connection 2 is the same as part of connection 1, the existing connection 3 is the same as part of connection 2, and the traffic being transferred is the second traffic, both connections in the network topology are the first connections. The two first connections which are not overlapped with the existing connection respectively comprise three links (NE3-NE4, NE4-NE5 and NE5-DC2) and one link (NE5-DC2), that is, the connection 2 is selected as the selected first connection, the existing connection 3 is shared, only one link needs to be newly established to meet the request information, therefore, the second connection is established according to the connection 2 in the network topology, the load on the network is small, and the utilization rate of network resources is higher.
It should be understood that, for different performance requirements and algorithm complexity requirements, there are many ways of selecting which existing connection to share, and the method provided by the present application may be adopted, or other ways such as random selection may also be adopted, which is not limited in the embodiment of the present application.
The service scheduling method provided by the application can efficiently and reasonably establish network connection by sensing the content needing to be transmitted between the client devices, thereby improving the utilization efficiency of network resources.
Optionally, as another embodiment, N pieces of request information are received simultaneously, and a source client device identifier, a sink client device identifier, and a content tag are obtained from each piece of request information, where N is a positive integer greater than 1; since more than one request message is received at the same time, before obtaining the network topology satisfying the request message according to the source client device identifier and the sink client device identifier, the scheduling method further includes: and merging the request information with the same source client device identification, sink client device identification and content label. The scheme provided by the application combines the same request information in advance, and does not need to execute the step 302 and the step 305 on each request information, thereby simplifying the operation.
The present solution is described below in several specific examples.
The first embodiment is as follows:
taking a simplified DCI network as an example, a network structure of the network is shown in fig. 5, where the network structure includes 3 DCs and a network topology, where a DC is maintained by a DC controller in the diagram, and the network topology is controlled and managed by an SDN controller in the diagram, and DC1, DC2, and DC3 access the network shown in fig. 5 through NE1, NE3, and NE4, respectively.
Assuming that the network has a connection DC1-NE1-NE2-NE3-DC2, the content delivered is a real-time signal X. At this time, when the SDN controller receives a request message again, since the prior art cannot support the content expression, the SDN controller still needs to establish a new connection for the request regardless of whether there is duplicate content in the network. Since the content tag is introduced, the DC is allowed to add the requested content into the request information, so that the SDN controller can extract the content tag of the request information, and can know the requested content in addition to knowing the network topology meeting the request information, so as to judge whether the existing connection in the network can be utilized or not according to the content tag, thereby improving the utilization rate of network resources.
In this embodiment, assuming that the SDN controller receives a request message again, that is, DC2 requests to obtain a service from DC1, the service can be known as a real-time signal X by identifying a content tag in the request message; an existing connection DC1-NE1-NE2-NE3-DC2 already exists in the network, and it is the real-time signal X that is transmitted, and the network topology that satisfies the request information also includes the existing connection, that is, the existing connection in the network can be used for the transmission of the real-time signal X in response to the request of DC2, so that the existing connection can be directly used for responding to the request from DC2, and network resources are saved. Finally, after the connection is successfully established, the SDN controller feeds back to the DC controller that the service has been successfully established.
Similarly, when there are multiple connections to the network, the SDN controller needs to look for the possibility to share existing connections against new service requests and each existing service connection.
It should be noted that the common Content tag identification technology includes a Content Centric Networking (CCN) technology, an Information Networking (Networking of Information, NetInf) technology, a Data Organized Network Architecture (DONA) technology, and the like, and the application is not limited to the specifically adopted Content tag identification technology and the naming method of the Content tag.
In addition, the request content is specifically indicated as the real-time signal X in this embodiment because the real-time signal conforms to two characteristics: (1) although content tags specify the uniqueness of the content, there is still a requirement for a synchronization mechanism. Real-time signals do not need to be synchronized, and the signals are broadcast at any time, so that the signals are convenient to share; for example, when a first is watching a football game, a second can join in content sharing at any time, which is irrelevant to whether the football game is just started or is half played, and the second needs the latest game situation rather than starting from the beginning. In a similar scenario, it is not appropriate to change to a non-real-time signal, e.g. watch a movie, a first has half watched, and a second requests content sharing, which needs to be watched from the beginning, rather than from the middle following the first. (2) The real-time signal is usually one of network hotspots, the demand is large, the request dynamics is strong, the trend of outbreak is often seen, and the high-efficiency network resource utilization rate is urgently needed. Besides the real-time signal, functions of data backup, migration and the like can also be realized through the technical scheme of the embodiment, for contents (similar to movies and the like) which cannot be synchronized, some synchronization mechanisms need to be introduced to ensure the completeness of the contents, and the embodiment of the application does not limit the synchronization mechanisms.
Example two:
in the embodiment of the present application, the network structure shown in fig. 5 is taken as an example, and it is assumed that a connection DC1-NE1-NE2-NE3-DC2 exists in the network, and the real-time signal Y is transmitted. At this time, the SDN controller receives a request message from DC3, that is, DC3 requests to transmit a certain service from DC1, and by using a content tag identification technology, the SDN controller knows that the content of the service requested by the request message is a real-time signal Y, and can attempt to share an existing connection, which is the same as the service delivered by the existing connection; however, the existing connection only partially overlaps with one connection in the network topology which meets the requirement of the request information, so that DC1-NE1-NE2-NE4-DC3 in the network topology is the first connection, obviously, the overlapping part of the existing connection and the first connection is DC1-NE1-NE2, and the part of the first connection which does not overlap with the existing connection is NE2-NE4-DC 3. Thus, the connection sharing DC1-NE1-NE2 of the existing connection is chosen to branch off at NE2, and a new connection of NE2-NE4-DC3 is created to provide the requested service. Finally, after the connection is successfully established, the SDN controller feeds back to the DC controller that the service has been successfully established. Compared with the prior art, the embodiment does not need to newly establish the connection of the DC1-NE1-NE2, thereby saving network resources.
Example three:
assuming still a simplified DCI network as an example, the network structure is still as shown in fig. 5, the SDN controller receives two request messages at the same time, and there are already connections for delivering some services in the existing network structure. At this time, comparing the content tags of the two request messages may cause two situations:
in the first case, if the source client device identifier, the destination client device identifier, and the content tag of the two pieces of request information are all matched, the SDN controller merges the two pieces of request information to obtain a network topology satisfying the two pieces of request information, and further compares a connection in the network topology with an existing connection in the network, and if a connection exists in the network topology that has the same transfer service and is overlapped with the existing connection in the network, the working flow is as shown in embodiment one; if there is a connection in the network topology that has the same delivery traffic and is overlapped with a part of the existing connections in the network, the workflow is as shown in the second embodiment.
In the second case, one or more inconsistent items exist in the source client device identifier, the destination client device identifier, and the content tag of the two request information, at this time, the SDN controller needs to process the two request information respectively, a processing procedure of each request information is as shown in the first embodiment or the second embodiment, which is not described herein again.
Example four:
the embodiment of the present application takes a network structure as shown in fig. 6 as an example, where the diagram includes 5 DCs and one network topology, where a DC is maintained by a DC controller in the diagram, and the network topology is controlled and managed by an SDN controller in the diagram, DC1 and DC2 access the DCI network through NE1 and NE2, respectively, and DC3, DC4, and DC5 access the DCI network through NE4, NE6, and NE7, respectively.
Suppose that there are two connections DC1-NE1-NE3-NE7-DC5 and DC2-NE2-NE3-NE4-DC3, which are respectively marked as existing connection 1 and existing connection 2, and the transmitted signals are real-time signals Z. At this time, the SDN controller receives a request message from DC4, that is, DC4 requests to transmit a certain service from DC2, and by using a content tag identification technology, the SDN controller knows that the content of the service requested by the request message is also a real-time signal Y, and the service is the same as the service delivered by two existing connections, and can attempt to share the existing connections; the network topology that meets this requirement has two types of connection structures, both of which have a portion that overlaps with the existing connection, and therefore both of which can be considered as the first connection.
At this time, if only the overlapped part in the existing connection 1 is shared, four links of DC2-NE2, NE2-NE3, NE7-NE6 and NE6-DC4 need to be newly established; if only the overlapped part in the existing connection 2 is shared, three links of NE4-NE5, NE5-NE6 and NE6-DC4 are required to be newly established; because both the existing connections transmit the real-time service Z, the utilization rate of network resources can be improved by sharing a part of each of the two existing connections, in this embodiment, DC2-NE2-NE3 in the existing connection 2 and NE3-NE7 in the existing connection 1 can be shared, so that only two links of NE7-NE6 and NE6-DC4 need to be newly established, and compared with the case of sharing one existing connection alone, the load on network resources is smaller.
It should be noted that, the above embodiments can be used for transmitting real-time signals, but for signals that cannot be synchronized, such as movie signals, the technical solutions provided by the above embodiments can be applied only when the signals are simultaneously requested and do not share the existing network connection.
Another embodiment of the present application provides an SDN controller, as shown in fig. 7, including: a receiving module 701, a processing module 702 and a sending module 703,
a receiving module 701, configured to receive request information, obtain a source client device identifier, a sink client device identifier, and a content tag from the request information, obtain a network topology that satisfies the request information according to the source client device identifier and the sink client device identifier, and send the content tag and the network topology to a processing module 702, where the request information is used to request that a service be transferred between a source client device and a sink client device, and the content tag is used to identify content of the service requested by the request information.
A processing module 702, configured to determine, according to the network topology and the content tag, whether a first connection exists in the network topology, where the first connection and an existing connection in the network have a superposition portion, and a service requested by the request information is the same as a service content transmitted by the connection in the network; if the first connection exists, establishing a second connection according to the part of the first connection which is not overlapped with the existing connection, and taking the overlapped part of the existing connection and the second connection together as the connection meeting the request information. Optionally, the service is a real-time service.
A sending module 703, configured to send a message that the connection that satisfies the request information is successfully established.
Alternatively, if the first connection completely coincides with an existing connection in the network, the processing module 702 is further configured to treat the existing connection coinciding with the first connection as the connection satisfying the requested information.
Optionally, the processing module 702 is further configured to, if the first connection does not exist, establish a second connection as the connection satisfying the request information. Specifically, the second connection may be established according to a structure of a connection with the least links in the network topology, where the links are information transmission paths between different network elements or between the network elements and the client device.
The SDN controller provided by the application can sense the content needing to be transmitted among the client devices by identifying the content tags in the request information, so that the purposes of avoiding network resource waste and improving the network resource utilization rate are achieved.
Further, if there are a plurality of first connections, the processing module 702 is further configured to compare the number of links included in the portion of the plurality of first connections that does not coincide with the existing connection, select one connection with the least number of links in the non-coinciding portion, establish a second connection according to the selected non-coinciding portion of the connection, and use the coinciding portion of the existing connection in the network with the first connection and the second connection together as a connection that satisfies the requested information, where the links refer to information transmission paths between different network elements or between a network element and a client device. The newly-built connection required by the scheme has the minimum number of links and the minimum burden on the network.
Optionally, as another embodiment, the receiving module 701 is further configured to receive N pieces of request information simultaneously, and obtain, from each piece of request information, a source client device identifier, a sink client device identifier, and a content tag, where N is a positive integer greater than 1; the processing module 702 is further configured to merge the request information with the same source client device identifier, sink client device identifier, and content tag before obtaining a network topology that satisfies the request information according to the source client device identifier and the sink client device identifier. The SDN controller provided in this embodiment merges the same request information in advance, and does not need to compare each request information with an existing connection in the network, thereby simplifying an operation flow.
Another embodiment of the present application provides a service scheduling system, including: a plurality of client devices, a client controller, an SDN controller and a plurality of NEs,
a client device for generating request information for requesting a service to be transferred between a source client device and a sink client device, adding a content tag for identifying the content of the service requested by the request information to the request information, and transmitting the request information to a client controller;
the client controller is used for sending the request information to the SDN controller;
the SDN controller is used for obtaining a source client device identifier, a destination client device identifier and a content label from the request information, and obtaining a network topology meeting the request information according to the source client device identifier and the destination client device identifier; judging whether a first connection exists in the network topology according to the network topology and the content label, wherein the first connection and the existing connection in the network have a superposition part, and the service requested by the request information has the same service content as the service transmitted by the existing connection; if the first connection exists, establishing a second connection according to the part which is not overlapped with the existing connection in the first connection, taking the overlapped part of the existing connection and the second connection together as the connection meeting the request information, and sending a control instruction to the NE passed by the second connection, wherein the control instruction is used for indicating to modify the connection relation of the NE; transmitting a message that the connection satisfying the request information is successfully established to the client controller;
and the NE through which the second connection passes is used for establishing the second connection according to the control instruction.
It should be noted that the request may be initiated by the client controller in addition to the client device. At some point, the client controller will decide whether to perform a part of data migration according to the content and state of each client device currently under jurisdiction, in this scenario, the request information is generated by the client controller, and the original/destination client device and the content tag of the migration are also specified by the client controller.
Therefore, another embodiment of the present application provides a service scheduling system, which includes a plurality of client devices for transceiving services; the service scheduling system further comprises: a client controller, an SDN controller and a plurality of NEs,
the SDN client controller is used for generating request information, adding a content label to the request information and sending the request information to the SDN client controller, wherein the request information is used for requesting the service to be transferred between the source client device and the sink client device, and the content label is used for identifying the content of the service requested by the request information;
the SDN controller is used for obtaining a source client device identifier, a destination client device identifier and a content label from the request information, and obtaining a network topology meeting the request information according to the source client device identifier and the destination client device identifier; judging whether a first connection exists in the network topology according to the network topology and the content label, wherein the first connection and the existing connection in the network have a superposition part, and the service requested by the request information has the same service content as the service transmitted by the existing connection; if the first connection exists, establishing a second connection according to the part which is not overlapped with the existing connection in the first connection, taking the overlapped part of the existing connection and the second connection together as the connection meeting the request information, and sending a control instruction to the NE passed by the second connection, wherein the control instruction is used for indicating to modify the connection relation of the NE; sending a message that the connection satisfying the request information is successfully established to the client controller;
and the NE through which the second connection passes is used for establishing the second connection according to the control instruction.
It should be understood that several embodiments of the SDN controller have been described in detail above, and the description of the embodiments is omitted here.
The service scheduling system provided by this embodiment achieves the purpose of sensing the content to be transmitted between the client devices by adding the content tag to the request information, and reasonably utilizes the existing connection by identifying the content to be transmitted, thereby improving the utilization efficiency of network resources.
An embodiment of the present application further provides a computer-readable storage medium, where a computer-executable instruction is stored in the computer-readable storage medium, and when at least one processor of a device executes the computer-executable instruction, the device executes the service scheduling method provided in the embodiment shown in fig. 3.
Embodiments of the present application also provide a computer program product, which includes computer executable instructions stored in a computer readable storage medium; the computer executable instructions may be read by at least one processor of the device from a computer readable storage medium, and the execution of the computer executable instructions by the at least one processor causes the device to perform the service scheduling method provided by the embodiment shown in fig. 3 described above.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (11)
1. A method for scheduling traffic, comprising:
receiving request information, and obtaining a source client device identification, a sink client device identification and a content tag from the request information, wherein the request information is used for requesting to transfer service between a source client device and a sink client device, and the content tag is used for identifying the content of the service requested by the request information;
obtaining a network topology meeting the request information according to the source client equipment identification and the destination client equipment identification;
judging whether a first connection exists in the network topology or not according to the network topology and the content label, wherein the first connection and an existing connection in the network have a superposition part, and the service requested by the request information has the same service content as the service transmitted by the existing connection;
if the first connection exists, establishing a second connection according to the part, which is not overlapped with the existing connection, in the first connection, and taking the overlapped part of the existing connection and the first connection and the second connection together as the connection meeting the request information;
and sending a message that the connection meeting the request information is successfully established.
2. The method of claim 1, wherein the first connection is completely coincident with an existing connection in the network;
establishing a second connection according to a part of the first connection which is not overlapped with the existing connection, and using the overlapped part of the existing connection and the second connection together as a connection meeting the request information, which specifically comprises: and the existing connection is used as the connection meeting the request information.
3. The method of claim 1 or 2, wherein after determining whether the first connection exists in the network topology, the method further comprises:
and if the first connection does not exist, establishing the second connection, and using the second connection as the connection meeting the request information.
4. The method according to claim 1, wherein if the first connection exists, establishing a second connection according to a portion of the first connection that does not coincide with the existing connection, specifically comprising:
if a plurality of first connections exist, comparing the number of links included in the non-overlapped part of the plurality of first connections with the existing connections, selecting one connection with the least number of links in the non-overlapped part, and establishing a second connection according to the selected non-overlapped part of the connection, wherein the links are information transmission paths between different network elements or between the network elements and client equipment.
5. The method according to claim 1 or 2,
the receiving request information, and obtaining the source client device identifier, the destination client device identifier, and the content tag from the request information specifically include: simultaneously receiving N pieces of request information, and obtaining a source client device identifier, a destination client device identifier and a content tag from each piece of request information, wherein N is a positive integer greater than 1;
before obtaining a network topology that satisfies the requested information based on the source client device and the sink client device, the method further comprises: and merging the request information with the same source client device identification, sink client device identification and content label.
6. A software defined network, SDN, controller, comprising: a receiving module, a processing module and a sending module,
the receiving module is configured to receive request information, obtain a source client device identifier, a sink client device identifier, and a content tag from the request information, obtain a network topology that satisfies the request information according to the source client device identifier and the sink client device identifier, and send the content tag and the network topology to the processing module, where the request information is used to request a service to be transferred between a source client device and a sink client device, and the content tag is used to identify content of the service requested by the request information;
the processing module is configured to determine whether a first connection exists in the network topology according to the network topology and the content tag, where the first connection and an existing connection in the network have a superposition portion, and the service requested by the request information is the same as the service content transmitted by the existing connection; if the first connection exists, establishing a second connection according to the part, which is not overlapped with the existing connection, in the first connection, and taking the overlapped part of the existing connection and the first connection and the second connection together as the connection meeting the request information;
and the sending module is used for sending out a message that the connection meeting the request information is successfully established.
7. The SDN controller of claim 6, wherein the first connection is fully coincident with an existing connection in a network;
the processing module is further configured to use the existing connection as a connection that satisfies the request information.
8. The SDN controller of claim 6 or 7, wherein the processing module is further configured to establish the second connection as the connection satisfying the request information if the first connection does not exist.
9. The SDN controller of claim 6, wherein the processing module is further configured to, if there are multiple first connections, compare the number of links included in a non-overlapping portion of the multiple first connections with the existing connections, select one of the connections with the smallest number of links in the non-overlapping portion, and establish a second connection according to the selected non-overlapping portion of the connections, where the links are information transmission paths between different network elements or between the network elements and a client device.
10. SDN controller according to claim 6 or 7,
the receiving module is further configured to receive N pieces of the request information simultaneously, and obtain a source client device identifier, a sink client device identifier, and a content tag from each piece of the request information, where N is a positive integer greater than 1;
the processing module is further configured to merge the request information with the same source client device identifier, sink client device identifier, and content tag before obtaining a network topology that satisfies the request information according to the source client device identifier and the sink client device identifier.
11. A traffic scheduling system, comprising: a plurality of client devices, a client controller, an SDN controller and a plurality of network elements NE,
the client device is used for generating request information, adding a content tag in the request information and sending the request information to the client controller, wherein the request information is used for requesting to transfer service between a source client device and a sink client device, and the content tag is used for identifying the content of the service requested by the request information;
the client controller is used for sending the request information to the SDN controller;
the SDN controller is configured to obtain a source client device identifier, a sink client device identifier, and the content tag from the request information, and obtain a network topology that satisfies the request information according to the source client device identifier and the sink client device identifier; judging whether a first connection exists in the network topology or not according to the network topology and the content label, wherein the first connection and an existing connection in the network have a superposition part, and the service requested by the request information is the same as the service content transmitted by the existing connection; if the first connection exists, establishing a second connection according to a part which is not overlapped with the existing connection in the first connection, taking the overlapped part of the existing connection and the second connection together as the connection meeting the request information, and sending a control instruction to an NE (NE) through which the second connection passes, wherein the control instruction is used for indicating to modify the connection relation of the NE; sending a message to the client controller that the connection satisfying the request information is successfully established;
and the NE through which the second connection passes is used for establishing the second connection according to the control instruction.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011160726.3A CN112398913B (en) | 2016-12-16 | 2016-12-16 | Service scheduling method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2016/110443 WO2018107480A1 (en) | 2016-12-16 | 2016-12-16 | Service scheduling method and system |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011160726.3A Division CN112398913B (en) | 2016-12-16 | 2016-12-16 | Service scheduling method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110063050A CN110063050A (en) | 2019-07-26 |
| CN110063050B true CN110063050B (en) | 2020-11-10 |
Family
ID=62557654
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201680091545.5A Active CN110063050B (en) | 2016-12-16 | 2016-12-16 | Service scheduling method and system |
| CN202011160726.3A Active CN112398913B (en) | 2016-12-16 | 2016-12-16 | Service scheduling method and system |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011160726.3A Active CN112398913B (en) | 2016-12-16 | 2016-12-16 | Service scheduling method and system |
Country Status (2)
| Country | Link |
|---|---|
| CN (2) | CN110063050B (en) |
| WO (1) | WO2018107480A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112398913A (en) * | 2016-12-16 | 2021-02-23 | 华为技术有限公司 | Service scheduling method and system |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114257504B (en) * | 2021-12-15 | 2023-05-23 | 烽火通信科技股份有限公司 | Service scene switching method and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101459656A (en) * | 2007-12-13 | 2009-06-17 | 华为技术有限公司 | Passive optical network aggregation node device and system |
| CN101808128A (en) * | 2010-03-18 | 2010-08-18 | 卢伟 | Virtual system of open wireless architecture of wireless mobile terminal equipment |
| CN106027641A (en) * | 2016-05-19 | 2016-10-12 | 上海斐讯数据通信技术有限公司 | TCP (Transmission Control Protocol) connection multiplexing method based on SDN (Software Defined Network) |
Family Cites Families (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030093799A1 (en) * | 2001-11-14 | 2003-05-15 | Kauffman Marc W. | Streamed content Delivery |
| CN100433748C (en) * | 2003-12-24 | 2008-11-12 | 华为技术有限公司 | Packet service scheduling unit and packet service scheduling method |
| WO2007071114A1 (en) * | 2005-12-23 | 2007-06-28 | Zte Corporation | A method for soft rerouting in optical network |
| CN100396016C (en) * | 2006-03-01 | 2008-06-18 | 华为技术有限公司 | System and method for securing service lelel in content distribution network |
| CN101072321A (en) * | 2006-06-22 | 2007-11-14 | 腾讯科技（深圳）有限公司 | P2P flow media releasing device |
| CN101145930B (en) * | 2007-09-19 | 2010-04-21 | 华为技术有限公司 | Method, system and device for guaranteeing reliable transmission of multicast service |
| CN101610198B (en) * | 2008-06-17 | 2012-03-28 | 大唐移动通信设备有限公司 | Method and device for scheduling packet services |
| CN101753597B (en) * | 2008-12-09 | 2013-04-17 | 华为技术有限公司 | Keeping alive method between peer node and client under peer node-client architecture |
| WO2010140935A1 (en) * | 2009-06-03 | 2010-12-09 | Telefonaktiebolaget L M Ericsson (Publ) | Method and node for finding content in a content distribution network, and method for creating a virtual representation of a content distribution network |
| CN102438002B (en) * | 2011-08-10 | 2016-08-03 | 中山大学深圳研究院 | A kind of based on the video file data transmission under Ad hoc network |
| CN104348728B (en) * | 2013-08-08 | 2018-03-09 | 华为技术有限公司 | Generate the method and apparatus of forwarding information |
| CN105610594B (en) * | 2014-11-19 | 2019-12-17 | 华为技术有限公司 | Service chain fault diagnosis method and device |
| CN110063050B (en) * | 2016-12-16 | 2020-11-10 | 华为技术有限公司 | Service scheduling method and system |
-
2016
- 2016-12-16 CN CN201680091545.5A patent/CN110063050B/en active Active
- 2016-12-16 WO PCT/CN2016/110443 patent/WO2018107480A1/en active Application Filing
- 2016-12-16 CN CN202011160726.3A patent/CN112398913B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101459656A (en) * | 2007-12-13 | 2009-06-17 | 华为技术有限公司 | Passive optical network aggregation node device and system |
| CN101808128A (en) * | 2010-03-18 | 2010-08-18 | 卢伟 | Virtual system of open wireless architecture of wireless mobile terminal equipment |
| CN106027641A (en) * | 2016-05-19 | 2016-10-12 | 上海斐讯数据通信技术有限公司 | TCP (Transmission Control Protocol) connection multiplexing method based on SDN (Software Defined Network) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112398913A (en) * | 2016-12-16 | 2021-02-23 | 华为技术有限公司 | Service scheduling method and system |
| CN112398913B (en) * | 2016-12-16 | 2022-05-13 | 华为技术有限公司 | Service scheduling method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112398913B (en) | 2022-05-13 |
| CN112398913A (en) | 2021-02-23 |
| CN110063050A (en) | 2019-07-26 |
| WO2018107480A1 (en) | 2018-06-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11265210B2 (en) | Network slice configuration method, apparatus, and system | |
| US9461877B1 (en) | Aggregating network resource allocation information and network resource configuration information | |
| US10637794B2 (en) | Resource subscription method, resource subscription apparatus, and resource subscription system | |
| CN109981468B (en) | Link state maintenance method and device | |
| US20140185429A1 (en) | Communication system, path switching method and communication device | |
| CN103117876A (en) | User state information synchronizing method and device | |
| CN112055078B (en) | Data transmission method, device, computer equipment and storage medium | |
| US11909840B2 (en) | Resource subscription method, device, and storage medium | |
| WO2022116920A1 (en) | Topology management method and device thereof, network element management node and storage medium | |
| CN114301828A (en) | Cross-subnet interaction method and device, electronic equipment and storage medium | |
| CN110063050B (en) | Service scheduling method and system | |
| EP3099010B1 (en) | Network path computation method, apparatus and system | |
| CN107302849B (en) | Light path distribution method and device | |
| CN106970843B (en) | Remote calling method and device | |
| CN110417876A (en) | Node server and main control device in session method, distributed system | |
| WO2018036521A1 (en) | Resource adjustment method, apparatus, and system | |
| US11916738B2 (en) | Service processing method and network device | |
| US20190387054A1 (en) | Method, electronic device and computer program product for searching for node | |
| CN114422520B (en) | Cross-chain interaction method and device | |
| CN114363335B (en) | Cross-chain interaction method and device | |
| CN113992740B (en) | Middleware based on autonomous control and data transmission method | |
| CN107872479B (en) | Cloud management platform and controller integration method and system and related modules | |
| WO2021254466A1 (en) | Method, apparatus and system for configuring edge side device | |
| CN115514651A (en) | Cloud-edge data transmission path planning method and system based on software-defined stacked network | |
| CN111064618B (en) | Method, device, equipment and storage medium for realizing high availability of server |
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 |