WO2018107480A1 - Procédé et système de planification de service - Google Patents

Procédé et système de planification de service Download PDF

Info

Publication number
WO2018107480A1
WO2018107480A1 PCT/CN2016/110443 CN2016110443W WO2018107480A1 WO 2018107480 A1 WO2018107480 A1 WO 2018107480A1 CN 2016110443 W CN2016110443 W CN 2016110443W WO 2018107480 A1 WO2018107480 A1 WO 2018107480A1
Authority
WO
WIPO (PCT)
Prior art keywords
connection
request information
client device
network
device identifier
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.)
Ceased
Application number
PCT/CN2016/110443
Other languages
English (en)
Chinese (zh)
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 PCT/CN2016/110443 priority Critical patent/WO2018107480A1/fr
Priority to CN202011160726.3A priority patent/CN112398913B/zh
Priority to CN201680091545.5A priority patent/CN110063050B/zh
Publication of WO2018107480A1 publication Critical patent/WO2018107480A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a service scheduling method and system based on a software-defined network SDN.
  • SDN Software Defined Network
  • the application of Software Defined Network (SDN) technology makes network control from distributed to centralized, the control plane of network equipment is simplified, and the control function rises to a centralized controller, which can be used for network services.
  • the delivery and configuration of the network device In this network deployment, there is one controller and multiple network devices, that is, multiple network elements (NEs).
  • the NE and the controller are connected through a standard interface (commonly referred to as an SDN southbound interface) to implement control of the NE by the controller; and the other end of the controller is usually connected to the network user, that is, the client device.
  • a typical SDN architecture is shown in Figure 1.
  • the architecture consists of three parts, from top to bottom, the application layer controller (customer controller), the SDN controller, and the network equipment (NE).
  • the existing service scheduling method based on the SDN architecture adopts a non-aware mode, that is, if the application layer controller receives the request 1 and needs to establish a connection between NE1 and NE2, it requests to establish an SDN controller. Corresponding to the Label Switched Path (LSP) between the NEs. If the application layer controller receives the request 2 and needs to establish a connection between NE1 and NE3, it will request the SDN controller to establish another LSP between the corresponding NEs.
  • LSP can be established by some mature southbound technologies, such as the Path Computation Element Protocol (PCEP), for data transmission between NEs.
  • PCEP Path Computation Element Protocol
  • the SDN controller cannot perceive the content that needs to be transmitted between the client devices.
  • the use efficiency of the network resources is greatly reduced.
  • the embodiment of the present invention provides a service scheduling method, which solves the problem that the use efficiency of network resources will be reduced when there is a large amount of duplicate content in the network by sensing the content that needs to be transmitted between the client devices.
  • the first aspect provides a service scheduling method, including: receiving request information, obtaining source client device identifier, sink client device identifier, and content label from the request information, wherein the request information is used to request the source client device Transmitting a service between the client device and the sink client device, the content tag is used to identify the content of the service requested by the request information; and obtaining, according to the source client device identifier and the sink client device identifier, the request information is satisfied.
  • a network topology determining, according to the network topology and the content label, whether there is a first connection in the network topology, where the first connection has an overlap with an existing connection in the network, and the request information is The requested service is the same as the service content delivered by the existing connection; if the first connection exists, establishing a second connection according to a part of the first connection that does not coincide with the existing connection, Cooperating the overlapped portion of the existing connection with the second connection as a connection satisfying the request information; the request information will be satisfied Connection is established successfully the message sent.
  • the scheduling method provided by the embodiment of the present invention can efficiently and reasonably establish a network connection by sensing the service content that needs to be transmitted between the client devices, thereby improving the utilization efficiency of the network resources.
  • the first connection is completely coincident with an existing connection in the network, and the existing connection is not connected according to the first connection. And a part of the overlap, the second connection is established, and the coincident part of the existing connection and the second connection are used as a connection that satisfies the request information, and the method includes: using the existing connection as the request information connection.
  • the method further includes And if the first connection does not exist, establishing the second connection, and using the second connection as a connection that satisfies the request information.
  • a third possible implementation manner of the first aspect if the first connection exists, establishing a second connection according to a part of the first connection that does not coincide with the existing connection, Specifically, if there are a plurality of the first connections, comparing the number of links included in a portion of the plurality of the first connections that does not coincide with the existing connection, selecting the non-coincident portion Establishing a second connection according to the non-coincident part of the selected connection, where the link is between different network elements or between the network element and the client device. Information transmission path.
  • the receiving request information Obtaining the source client device identifier, the sink client device identifier, and the content label from the request information, specifically: receiving N request information at the same time, obtaining the source client device identifier, the sink client device identifier, and the content from each of the request information a label, N is a positive integer greater than 1; before the network topology that satisfies the request information is obtained according to the source client device identifier and the sink client device identifier, the method further includes: identifying the source client device And the request information that the sink client device identifier and the content label are the same are merged.
  • the embodiment of the present application combines the same request information in advance, and does not need to compare each request information with an existing connection, which simplifies the operation flow.
  • the second aspect provides a software-defined network SDN controller, including: a receiving module, a processing module, and a sending module, where the receiving module is configured to receive request information, obtain a source client device identifier from the request information, and store the client And the device identifier and the content label, the network topology that satisfies the request information is obtained according to the source client device identifier and the sink client device identifier, and the content label and the network topology are sent to the processing module, where The request information is used to request delivery of a service between the source client device and the sink client device, the content tag is used to identify content of the service requested by the request information; and the processing module is configured to: Determining, according to the network topology and the content label, whether there is a first connection in the network topology, where the first connection has an overlap with an existing connection in the network, and the service requested by the request information The same as the service content delivered by the existing connection; if the first connection exists, according to the first connection Having a portion of the connection coincidence
  • the SDN controller provided by the embodiment of the present application improves the utilization efficiency of network resources by sensing the content that needs to be transmitted between the client devices, and establishing the network connection efficiently and reasonably.
  • the first connection is completely coincident with an existing connection in the network, and the processing module is further configured to satisfy the existing connection The connection of the request information.
  • the processing module is further configured to: if the first connection does not exist, establish a location Said second connection, said second connection being a connection that satisfies said request information.
  • the processing module is further configured to: if there are multiple the first connections, compare the plurality of the first connections with the The number of links included in the portion where the connection overlaps is selected, and the connection having the least number of links in the non-coincident portion is selected, and the second connection is established according to the non-coincident portion of the selected connection, where The link is an information transmission path between different network elements or between the network element and the client device.
  • the receiving module is further And receiving, by each of the request information, a source client device identifier, a sink client device identifier, and a content label, where N is a positive integer greater than 1.
  • the processing module is further configured to Determining, according to the source client device identifier and the sink client device identifier, the source client device identifier, the sink client device identifier, and the content label are the same before obtaining a network topology that satisfies the request information Request information to merge.
  • the embodiment of the present application combines the same request information in advance, and does not need to compare each request information with an existing connection, which simplifies the operation flow.
  • a third aspect provides a service scheduling system, including: a plurality of client devices, a client controller, an SDN controller, and a plurality of network elements NE, wherein the client device is configured to generate request information, and add the request information.
  • a content tag the request information is sent to the client controller, wherein the request information is used to request delivery of a service between a source client device and a sink client device, and the content tag is used to identify the request information request
  • the content of the service is configured to send the request information to the SDN controller;
  • the SDN controller is configured to obtain the source client device identifier from the request information,
  • the sink client device identifier and the content tag are obtained according to the source client device identifier and the sink client device identifier.
  • the requested service is the same as the service content delivered by the existing connection; if the first connection exists, establishing a second connection according to a part of the first connection that does not coincide with the existing connection And connecting the coincident portion of the existing connection and the second connection together as a connection satisfying the request information, and sending a control instruction to the NE through which the second connection passes, wherein the control instruction is used to indicate modification a connection relationship of the NE; a message that the connection that satisfies the request information is successfully sent to the client controller; and the NE that the second connection passes is used to establish the second according to the control instruction connection.
  • a fourth aspect provides a service scheduling system, including a plurality of client devices, configured to send and receive services, where the service scheduling system further includes: a client controller, an SDN controller, and a plurality of network elements NE, the client controller, And generating request information, adding a content tag to the request information, and sending the request information to the SDN subscriber controller, wherein the request information is used to request to be transmitted between the source client device and the sink client device
  • the content label is used to identify the content of the service requested by the request information
  • the SDN controller is configured to obtain the source client device identifier from the request information, the sink client device identifier and And determining, by the content label, the network topology that satisfies the request information according to the source client device identifier and the sink client device identifier; determining, according to the network topology and the content label, whether the network topology exists a connection, the first connection has an overlap with an existing connection in the network, and the service requested by the request information and the existing connection
  • the service content
  • the first connection is coincident with an existing connection in the network; the SDN controller is further used to The existing connection is used as a connection that satisfies the request information.
  • the SDN controller is further configured to: if the first connection does not exist, establish the second connection, and use the second connection as a connection that satisfies the request information.
  • the SDN controller is further configured to compare multiple locations if there are multiple the first connections a number of links included in a portion of the first connection that does not coincide with the existing connection, and selecting one of the non-coincident portions with the least number of links, according to the non-coincident portion of the selected connection Establishing a second connection, where the link is an information transmission path between different network elements or between the network element and a client device.
  • the SDN controller is further configured to receive N pieces of the request information at the same time, from each Obtaining a source client device identifier, a sink client device identifier, and a content label in the request information, and combining the source client device identifier, the sink client device identifier, and the request information that are the same as the content label, where N is A positive integer greater than one.
  • N is A positive integer greater than one.
  • a computer readable storage medium where computer executed instructions are stored, and when the at least one processor of the device executes the computer to execute an instruction, the device performs the first aspect or the first aspect A service scheduling method provided by any of the possible implementations.
  • a computer program product comprising computer executable instructions stored in a computer readable storage medium; at least one processor of the device can read the computer from a computer readable storage medium Executing the instructions, the at least one processor executing the computer execution instructions causes the device to implement the service scheduling method provided by the first aspect or any of the possible implementations of the first aspect.
  • the scheduling method provided by the embodiment of the present application is to perceive the service that needs to be transmitted between the client devices. Content can establish network connections efficiently and reasonably, thereby improving the utilization efficiency of network resources.
  • Figure 1 is a diagram of a typical exemplary 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 schematic diagram of a DCI network architecture adopted by another embodiment of the present application.
  • FIG. 5 is a schematic diagram of a DCI network architecture adopted by another embodiment of the present application.
  • FIG. 6 is a schematic diagram of a DCI network architecture adopted by another embodiment of the present application.
  • FIG. 7 is an SDN controller according to another embodiment of the present application.
  • DCI Data Center Interconnection
  • DCs data centers
  • SDN Data Center Interconnection
  • the DC controller is used to collect the requirements of different DCs and send these requirements to the SDN controller.
  • SDN controller establishes a connection between the NEs according to these requirements.
  • the embodiment of the present application provides a service scheduling method, as shown in FIG. 3, including:
  • Receive request information obtain a source client device identifier, a sink client device identifier, and a content label from the request information.
  • the request information is used to request to transfer a service between the source client device and the sink client device; optionally, the service is a real-time service; the content tag is used to identify the content of the service requested by the request information; the method is applied to the DCI
  • the client controller is the DC controller and the client device is the DC.
  • the SDN controller stores the network topology between any source client device and any sink client device in the network. Therefore, as long as it is determined which request information is requested to transfer services between two client devices, it can be known.
  • a network topology between the two client devices wherein the source client device identity and the sink client device identity indicate which two client devices are required to pass the service request information.
  • the network topology includes nodes and links, the nodes refer to NEs, and the links refer to all connections connected to the NE, including one end where the client device is a NE at one end. In other words, as long as the network topology is known, the two are known. All possible connection relationships between client devices.
  • the first connection is overlapped with the existing connection in the network, that is, the first connection is a connection that partially overlaps or completely coincides with any existing connection in the network, and the service requested by the request information is in the network.
  • the business content delivered by the existing connection is the same.
  • the first connection is overlapped with a part of an existing connection in the network, and the following description is performed.
  • FIG. 2 it is assumed that there is a connection DC1-NE1-NE2-NE3-DC2 in the network that transmits the first service.
  • existing connection 1 request information is required to transfer the first service between DC1 and DC3, then the network has a first connection; due to the connection in the network topology DC1-NE1-NE2-NE3-NE5-DC3 It overlaps with a part of the existing connection 1, and the transmitted service is also the same, so DC1-NE1-NE2-NE3-NE5-DC3 is the first connection.
  • the combination of the two can be used to transfer the first service between DC1 and DC3.
  • the method utilizes existing connections in the network, eliminating the need to create a complete connection between DC1 and DC3, saving network resources.
  • step 302 may be simplified as: determining whether the network topology exists in the network topology according to the network topology and the content label.
  • a connection if there is a first connection, an existing connection that coincides with the first connection is used as a connection that satisfies the request information.
  • a second connection is established, and the second connection is used as a connection that satisfies the request information.
  • the second connection may be established according to the structure of the link with the least link in the network topology, where the link is an information transmission path between different network elements or between the network element and the client device.
  • one of the first connections is selected according to the principle of highest network resource utilization, as follows: comparing the parts of the multiple first connections that do not coincide with the existing connection The number of links included, the one with the least number of links in the non-coincident part is selected, and the second connection is established according to the non-coincident part of the selected connection.
  • the newly created connection required by this solution contains the fewest links and the least burden on the network.
  • connection 1 is DC1-NE1-NE2- NE3-NE4-NE5-DC2
  • connection 2 is DC1-NE1-NE6-NE5-DC2.
  • the existing connection 2 is the same as the part of the connection 1
  • the existing connection 3 is the same as the part of the connection 2
  • the delivered service is the second service
  • the two connections in the network topology are the first connection.
  • the portions of the two first connections that do not coincide with the existing connection include three links (NE3-NE4, NE4-NE5, and NE5-DC2) and one link (NE5-DC2), that is, select connections.
  • the selected first connection the existing connection 3 is shared, and only one link is needed to satisfy the request information. Therefore, the embodiment of the present application establishes a second connection according to the connection 2 in the network topology, and the burden on the network is Smaller, the utilization of network resources is higher.
  • the service scheduling method provided by the present application can efficiently and reasonably establish a network connection by sensing content that needs to be transmitted between client devices, thereby improving the utilization efficiency of network resources.
  • N request information is received at the same time, from each request letter.
  • the source client device identifier, the sink client device identifier, and the content label are obtained, and N is a positive integer greater than one; since more than one request information is received at the same time, the request information is satisfied according to the source client device identifier and the sink client device identifier.
  • the scheduling method further includes: combining the source client device identifier, the sink client device identifier, and the request information with the same content label.
  • the solution provided by the present application merges the same request information in advance, and it is not necessary to have each request information perform steps 302-305, which simplifies the operation.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • FIG. 5 Taking a simplified DCI network as an example, its network structure is shown in Figure 5.
  • the diagram contains three DCs and one network topology.
  • the DC is maintained by the DC controller in the figure, and the network topology is represented by the SDN in the figure.
  • the controller performs control and management, and DC1, DC2, and DC3 are connected to the network shown in FIG. 5 through NE1, NE3, and NE4, respectively.
  • the network has a connection DC1-NE1-NE2-NE3-DC2, and the content delivered is the real-time signal X.
  • the SDN controller needs to establish a new connection for the request regardless of whether there is duplicate content in the network.
  • the DC is allowed to add the requested content to the request information, so the SDN controller can extract the content tag of the request information, and can know the request in addition to the network topology that satisfies the request information. Based on this content, it is judged whether it is possible to utilize existing connections in the network to improve the utilization of network resources.
  • the SDN controller receives another request information, and the DC2 requests to obtain a certain service from the DC1.
  • the service can be known as the real-time signal X; the network already exists.
  • An existing connection DC1-NE1-NE2-NE3-DC2 transmits the real-time signal X, and the network topology that satisfies the request information also includes the existing connection, that is, the existing network has The connection can be used for the transmission of the real-time signal X in response to the DC2 request, so this connection can be used directly in response to requests from DC2, saving network resources.
  • the SDN controller feeds back to the DC controller that the service has been established successfully.
  • the SDN controller needs to compare the new service request with each existing service connection to find the possibility of sharing the existing connection.
  • CCN Content Centric Networking
  • NetInf Network of Information
  • DONA Data Oriented Network Architecture
  • the present embodiment specifically indicates that the requested content is the real-time signal X because the real-time signal conforms to two characteristics: (1) Although the content tag specifies the uniqueness of the content, there is still a requirement for the synchronization mechanism.
  • the real-time signal does not need to be synchronized, and it can be shared at any time. It is easy to share at any time. For example, when a certain A is watching a football match, a certain B can join for content sharing at any time. This is not related to whether the football match has just started or halfway. What a B needs is the latest game situation, not from the beginning. In a similar scenario, it is not appropriate to switch to a non-real-time signal. For example, watching a movie, a certain one has already seen half of it.
  • the real-time signal is usually a kind of network hotspot, the demand is large, the dynamic of the request is very strong, and the trend is often erupted, which has an urgent need for efficient utilization of network resources.
  • functions such as data backup and migration can also be implemented by the technical solution of the embodiment. For content that cannot be synchronized (like a movie, etc.), some synchronization mechanism needs to be introduced to ensure the integrity of the content. Not limited.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the embodiment of the present application still takes the network structure shown in FIG. 5 as an example, and assumes that there is a connection DC1-NE1-NE2-NE3-DC2 in the network, and the real-time signal Y is transmitted.
  • the SDN controller receives a request message from the DC3, and the DC3 requests to transmit a certain service from the DC1.
  • the SDN controller knows that the content of the service requested by the request information is the real-time signal Y, and
  • the existing connections deliver the same services and can try to share the existing connections.
  • the existing connections only partially overlap with one of the network topologies that meet the requirements of the request information. Therefore, DC1-NE1-NE2-NE4-DC3 in the network topology.
  • the first connection it is obvious that the overlapping portion of the existing connection with the first connection is DC1-NE1-NE2, and the portion of the first connection that does not coincide with the existing connection is NE2-NE4-DC3. Therefore, the connection of the DC1-NE1-NE2 part of the existing connection is selected, and the connection is established at the NE2, and the connection of the NE2-NE4-DC3 is newly established 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 established successfully. Compared with the prior art, this embodiment does not need to newly establish a part of the connection of DC1-NE1-NE2, which saves network resources.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • the SDN controller receives two request information at the same time, and the existing network structure already has a connection for transmitting certain services. At this point, there are two cases where the content tags of the two request messages are compared:
  • the source client device identifier, the sink client device identifier, and the content label of the two request information are all consistent, and the SDN controller combines the two request information to obtain a network topology that satisfies the two request information, and further If the connection in the network topology is compared with the existing connection in the network, if there is a connection in the network topology that is the same as the connection in the network, and the connection is overlapped with the existing connection in the network, the workflow is as shown in the first embodiment; In the network topology, the connection is the same, and the connection is overlapped with a part of the existing connection in the network, and the workflow is as shown in the second embodiment.
  • the SDN controller needs to separately process the two request information, each request.
  • the processing of the information is as shown in the first embodiment or the second embodiment, and details are not described herein again.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • the embodiment of the present application takes the network structure shown in FIG. 6 as an example, and the figure includes five DCs and one network topology, wherein the DC is maintained by the DC controller in the figure, and the network topology is determined by the SDN controller in the figure.
  • DC1 and DC2 access the DCI network through NE1 and NE2, respectively
  • DC3, DC4, and DC5 access the DCI network through NE4, NE6, and NE7, respectively.
  • FIG. 7 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.
  • the receiving module 701 is configured to receive the request information, obtain the source client device identifier, the sink client device identifier, and the content label 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, and The content tag and the network topology are sent to the processing module 702, wherein the request information is used to request delivery of a service between the source client device and the sink client device, the content tag being used to identify the content of the service requested by the request information.
  • the processing module 702 is configured to determine, according to the network topology and the content label, whether there is a first connection in the network topology, where the first connection has an overlap with an existing connection in the network, and the service and network requested by the request information
  • the service content delivered by the connection is the same; if there is a first connection, the second connection is established according to the part of the first connection that does not coincide with the existing connection, and the overlapping part of the existing connection is used together with the second connection A connection that satisfies the request information.
  • the service is a real-time service.
  • the sending module 703 is configured to send a message that the connection that satisfies the request information is successfully established.
  • the processing module 702 is further configured to use the existing connection that coincides with the first connection as the connection that satisfies the request information.
  • the processing module 702 is further configured to: if the first connection does not exist, establish a second connection Next, the second connection is used as a connection that satisfies the request information.
  • the second connection may be established according to the structure of the link with the least link in the network topology, where the link is an information transmission path between different network elements or between the network element and the client device.
  • the SDN controller provided by the present application senses the content that needs to be transmitted between the client devices by identifying the content tags in the request information, thereby avoiding waste of network resources and improving utilization of network resources.
  • the processing module 702 is further configured to compare the number of links included in the part of the plurality of first connections that does not coincide with the existing connection, and select the number of links in the non-coincident part. a minimum of one connection, establishing a second connection according to the non-coincident part of the selected connection, and connecting the existing connection in the network with the coincident part of the first connection and the second connection as a connection satisfying the request information, wherein the link Refers to the information transmission path between different network elements or between network elements and client devices.
  • the newly created connection required by this solution contains the fewest links and the least burden on the network.
  • the receiving module 701 is further configured to receive N request information at the same time, and obtain a source client device identifier, a sink client device identifier, and a content label from each request information, where N is greater than 1.
  • the processing module 702 is further configured to merge the request information of the source client device identifier, the sink client device identifier, and the content label, before obtaining the 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 combines the same request information in advance, and does not need to compare each request information with an existing connection in the network, which simplifies the operation flow.
  • Another embodiment of the present application provides a service scheduling system, including: multiple client devices, a client controller, an SDN controller, and multiple NEs.
  • a client device configured to generate request information, add a content tag to the request information, and send the request information to the client controller, where the request information is used to request to transfer the service between the source client device and the sink client device, the content
  • the tag is used to identify the content of the service requesting the information request;
  • a client controller configured to send the request information to the SDN controller
  • the SDN controller is configured to obtain the source client device identifier, the sink client device identifier, and the content label from the request information, and obtain the content according to the source client device identifier and the sink client device identifier.
  • Obtaining a network topology of the information determining, according to the network topology and the content label, whether the first connection exists in the network topology, the first connection has an overlap with the existing connection in the network, and the service requested by the request information is The service content of the existing connection is the same; if there is a first connection, the second connection is established according to the part of the first connection that does not coincide with the existing connection, and the overlapping part of the existing connection and the second connection are satisfied together.
  • the connection of the request information is sent to the NE through which the second connection passes, wherein the control instruction is used to indicate that the connection relationship of the NE is modified; and the message that the connection that satisfies the request information is successfully sent to the client controller;
  • the NE through which the second connection passes is used to establish a second connection according to the control instruction.
  • the request may be initiated by the client controller.
  • the client controller decides whether to perform part of the data migration according to the content and status of each client device under the current jurisdiction.
  • the request information is generated by the client controller, and the migrated original/sink client device and Content tags are also specified by the client controller.
  • another embodiment of the present application provides a service scheduling system, including multiple client devices, for transmitting and receiving services; the service scheduling system further includes: a client controller, an SDN controller, and multiple NEs,
  • a client controller configured to generate request information, add a content label to the request information, and send the request information to a SDN account controller, where the request information is used to request to transfer the service between the source client device and the sink client device
  • the content tag is used to identify the content of the service requested by the request information
  • An SDN controller configured to obtain a source client device identifier, a sink client device identifier, and a content label 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; according to the network topology and a content label, determining whether there is a first connection in the network topology, where the first connection has an overlap with an existing connection in the network, and the service requested by the request information is the same as the service content delivered by the existing connection; a connection, according to a portion of the first connection that does not coincide with the existing connection, establishing a second connection, and the overlapping portion of the existing connection and the second connection together as a connection satisfying the request information, sending a control command to the first a second connected NE, wherein the control instruction is used to indicate that the connection relationship of the NE is modified; and the message that the connection that satisfies the request information is successfully established is sent to the client controller;
  • the NE through which the second connection passes is used to establish a second connection according to the control instruction.
  • the service scheduling system provided in this embodiment achieves the purpose of perceiving the content that needs to be delivered between the client devices by adding the content tag in the request information, and improves the network by identifying the content to be delivered and making rational use of the existing connection. Resource utilization efficiency.
  • the embodiment of the present application further provides a computer readable storage medium.
  • the computer readable storage medium stores computer execution instructions.
  • the device executes the embodiment shown in FIG. 3 .
  • the service scheduling method provided.
  • the embodiment of the present application further provides a computer program product, the computer program product comprising computer execution instructions stored in a computer readable storage medium; at least one processor of the device can read the computer readable storage medium The computer executes the instructions, and the at least one processor executes the computer to execute the instructions such that the device performs the service scheduling method provided by the embodiment shown in FIG. 3 above.

Landscapes

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

Abstract

La présente invention concerne un procédé de planification de service comprenant les étapes consistant à : recevoir des informations de requête et obtenir un identifiant de dispositif client source, un identifiant de dispositif client destinataire, et une étiquette de contenu à partir des informations de requête ; obtenir, en fonction de l'identifiant de dispositif client source et de l'identifiant de dispositif client destinataire, une topologie de réseau satisfaisant aux informations de requête ; déterminer, en fonction de la topologie de réseau et de l'étiquette de contenu, s'il existe une première connexion dans la topologie de réseau, un chevauchement étant présent entre la première connexion et une connexion existante dans le réseau, et un service demandé par les informations de requête ayant le même contenu que celui d'un service transféré par la connexion existante ; si la première connexion existe, établir une seconde connexion en fonction d'un segment dans lequel la première connexion ne chevauche pas la connexion existante, et utiliser le segment chevauché de la connexion existante et la seconde connexion en tant que connexion satisfaisant aux informations de requête ; et envoyer un message indiquant qu'une connexion satisfaisant aux informations de requête a été établie avec succès. Le procédé de planification décrit dans la présente invention permet d'utiliser une connexion existante dans le réseau, ce qui permet d'améliorer l'efficacité d'utilisation de ressources de réseau.
PCT/CN2016/110443 2016-12-16 2016-12-16 Procédé et système de planification de service Ceased WO2018107480A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/CN2016/110443 WO2018107480A1 (fr) 2016-12-16 2016-12-16 Procédé et système de planification de service
CN202011160726.3A CN112398913B (zh) 2016-12-16 2016-12-16 一种业务调度方法及系统
CN201680091545.5A CN110063050B (zh) 2016-12-16 2016-12-16 一种业务调度方法及系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/110443 WO2018107480A1 (fr) 2016-12-16 2016-12-16 Procédé et système de planification de service

Publications (1)

Publication Number Publication Date
WO2018107480A1 true WO2018107480A1 (fr) 2018-06-21

Family

ID=62557654

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/110443 Ceased WO2018107480A1 (fr) 2016-12-16 2016-12-16 Procédé et système de planification de service

Country Status (2)

Country Link
CN (2) CN110063050B (fr)
WO (1) WO2018107480A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114257504A (zh) * 2021-12-15 2022-03-29 烽火通信科技股份有限公司 业务场景切换方法及系统

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018107480A1 (fr) * 2016-12-16 2018-06-21 华为技术有限公司 Procédé et système de planification de service

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101753597A (zh) * 2008-12-09 2010-06-23 华为技术有限公司 对等节点-客户端架构下对等节点与客户端间保活方法
CN104348728A (zh) * 2013-08-08 2015-02-11 华为技术有限公司 生成转发信息的方法及设备
CN105610594A (zh) * 2014-11-19 2016-05-25 华为技术有限公司 业务链的故障诊断方法及装置

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030093799A1 (en) * 2001-11-14 2003-05-15 Kauffman Marc W. Streamed content Delivery
CN100433748C (zh) * 2003-12-24 2008-11-12 华为技术有限公司 包业务调度单元及包业务调度方法
CN101223722B (zh) * 2005-12-23 2011-11-16 中兴通讯股份有限公司 光网络中软重路由的方法
CN100396016C (zh) * 2006-03-01 2008-06-18 华为技术有限公司 在内容分发网络中保障服务水平的系统和方法
CN101072321A (zh) * 2006-06-22 2007-11-14 腾讯科技（深圳）有限公司 一种p2p流媒体发布装置
CN101145930B (zh) * 2007-09-19 2010-04-21 华为技术有限公司 保证组播业务可靠传输的方法、系统和设备
CN101459656B (zh) * 2007-12-13 2012-05-23 华为技术有限公司 一种无源光网络汇聚节点设备、系统及数据传输方法
CN101610198B (zh) * 2008-06-17 2012-03-28 大唐移动通信设备有限公司 一种分组业务的调度方法及调度装置
EP2438741A4 (fr) * 2009-06-03 2014-06-04 Ericsson Telefon Ab L M Procédé et n ud permettant de trouver un contenu dans un réseau de distribution de contenu, et procédé permettant de créer une représentation virtuelle d'un réseau de distribution de contenu
CN101808128B (zh) * 2010-03-18 2012-12-26 卢伟 无线移动终端设备的开放无线结构虚拟系统
CN102438002B (zh) * 2011-08-10 2016-08-03 中山大学深圳研究院 一种基于Ad hoc网络下的视频文件数据传输方法
CN106027641A (zh) * 2016-05-19 2016-10-12 上海斐讯数据通信技术有限公司 一种基于sdn网络的tcp连接复用方法
WO2018107480A1 (fr) * 2016-12-16 2018-06-21 华为技术有限公司 Procédé et système de planification de service

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101753597A (zh) * 2008-12-09 2010-06-23 华为技术有限公司 对等节点-客户端架构下对等节点与客户端间保活方法
CN104348728A (zh) * 2013-08-08 2015-02-11 华为技术有限公司 生成转发信息的方法及设备
CN105610594A (zh) * 2014-11-19 2016-05-25 华为技术有限公司 业务链的故障诊断方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114257504A (zh) * 2021-12-15 2022-03-29 烽火通信科技股份有限公司 业务场景切换方法及系统
CN114257504B (zh) * 2021-12-15 2023-05-23 烽火通信科技股份有限公司 业务场景切换方法及系统

Also Published As

Publication number Publication date
CN112398913A (zh) 2021-02-23
CN110063050A (zh) 2019-07-26
CN110063050B (zh) 2020-11-10
CN112398913B (zh) 2022-05-13

Similar Documents

Publication Publication Date Title
US12113667B2 (en) Network slice configuration method, apparatus, and system
CN103051565B (zh) 一种等级软件定义网络控制器的架构系统及实现方法
CN104243496B (zh) 一种软件定义网跨域安全代理方法和系统
CN109391490B (zh) 网络切片的管理方法和装置
CN106664216B (zh) 一种切换vnf的方法和装置
CN115277578B (zh) 一种业务编排方法、装置及存储介质
CN108632067A (zh) 容灾部署方法、装置及系统
CN102387042B (zh) 自动配置的方法和系统以及网络节点
WO2018082491A1 (fr) Procédé d'extension d'instance de tranche de réseau, dispositifs de réseau, et architecture de réseau
CN114301828A (zh) 一种跨子网交互方法、装置、电子设备和存储介质
WO2018036521A1 (fr) Procédé, appareil et système d'ajustement de ressource
CN116260590A (zh) 一种跨链场景下的高并发中继事务协调方法及系统
CN108471373A (zh) 一种资源申请、vnf实例创建方法及装置
EP3016328B1 (fr) Procédé d'acquisition de chemin, élément de calcul de chemin, client de calcul de chemin et système
US20160352636A1 (en) Network path computation method, apparatus, and system
CN110063050B (zh) 一种业务调度方法及系统
CN114531393B (zh) 分段路由策略下发方法、装置、设备及介质
CN103636168B (zh) 一种故障恢复的方法、节点和路径计算单元
WO2017133020A1 (fr) Procédé et dispositif de transmission de principes dans un système nfv
US20240235937A1 (en) Service processing method and network device
CN119135636A (zh) 一种流量调度方法、系统、电子设备及存储介质
CN113852479B (zh) 一种安全网络构建方法、装置、设备和计算机存储介质
CN109962937A (zh) 一种多域多层连接业务建立方法和装置
CN111131350B (zh) 一种端到端的连接建立方法及控制器
CN105704169A (zh) 一种保持数据一致性的方法、装置及ptn传输设备

Legal Events

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

Ref document number: 16923705

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16923705

Country of ref document: EP

Kind code of ref document: A1