| (11) | EP 3 361 684 B1 |
(12) | EUROPEAN PATENT SPECIFICATION |
|
|
(54) | ROUTE DETERMINING METHOD AND CORRESPONDING APPARATUS AND SYSTEM ROUTENBESTIMMUNGSVERFAHREN UND ZUGEHÖRIGE VORRICHTUNG UND SYSTEM PROCÉDÉ DE DÉTERMINATION DE ROUTE ET APPAREIL ET SYSTÈME CORRESPONDANTS |
|
| ||||||||||||||||||||||||||||
Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention). |
TECHNICAL FIELD
BACKGROUND
SUMMARY
receiving a first flow entry, where the first flow entry includes a first route mapping relationship of a service flow of a first service chain, a first load proportion of each service node, and a first effective time period of the first flow entry;
receiving a second flow entry, where the second flow entry includes a second route mapping relationship of the service flow of the first service chain, a second load proportion of each service node, and a second effective time period of the second flow entry, and the second effective time period is different from the first effective time period;
receiving a first packet of a first service flow, where the first packet includes a first timestamp of the first service flow and a first service chain identifier, the first service chain identifier indicates that the first service flow is a service flow of the first service chain, and the first timestamp indicates a creation time of the first service flow;
determining a time period that includes the first timestamp from the first effective time period and the second effective time period;
determining, according to a flow entry corresponding to the determined time period, a service node for receiving the first packet; and
sending the first packet to the determined service node.
determining whether a start time of the second effective time period precedes an end time of the first effective time period; and
if the start time of the second effective time period precedes the end time of the first effective time period, changing the end time of the first effective time period to the start time of the second effective time period.
determining at least two service nodes according to an input node of the first packet and the first route mapping relationship;
generating a load balancing factor according to the first timestamp; and
determining, from the at least two service nodes according to the respective first load proportions of the at least two service nodes and the load balancing factor, a first service node for receiving the first packet.
determining at least two service nodes according to an input node of the first packet and the first route mapping relationship; and
determining, from the at least two service nodes according to the respective first load proportions of the at least two service nodes and the load balancing factor, a first service node for receiving the first packet.
receiving a second packet of the first service flow; and
sending the second packet to the first service node.
starting a timeout timer; and
before the sending the second packet to the first service node, the method further includes:
determining that the timeout timer does not expire.
receiving a first packet of a first service flow;
determining, according to a feature field included in the first packet, that the first service flow is a service flow of a first service chain;
adding a first timestamp of the first packet and a first service chain identifier to the first packet, where the first service chain identifier indicates that the first service flow is a service flow of the first service chain, and the first timestamp indicates a creation time of the first service flow; and
sending the first packet to a switch.
obtaining first current load of each service node existing at a first moment;
generating a first flow entry, where the first flow entry includes a first route mapping relationship of a service flow of a first service chain, a first load proportion of each service node, and a first effective time period of the first flow entry, and the first load proportion is generated according to the first current load of each service node;
sending the first flow entry to a switch;
obtaining second current load of each service node existing at a second moment;
generating a second flow entry, where the second flow entry includes a second route mapping relationship of a packet of the first type of service flow, a second load proportion of each service node, and a second effective time period of the second flow entry, the second load proportion is generated according to the second current load of each service node, and the second effective time period is different from the first effective time period; and
sending the second flow entry to the switch.
a first receiving module, configured to: receive a first flow entry, where the first flow entry includes a first route mapping relationship of a service flow of a first service chain, a first load proportion of each service node, and a first effective time period of the first flow entry; and receive a second flow entry, where the second flow entry includes a second route mapping relationship of the service flow of the first service chain, a second load proportion of each service node, and a second effective time period of the second flow entry, and the second effective time period is different from the first effective time period;
a second receiving module, configured to receive a first packet of a first service flow, where the first packet includes a first timestamp of the first service flow and a first service chain identifier, the first service chain identifier indicates that the first service flow is a service flow of the first service chain, and the first timestamp indicates a creation time of the first service flow;
a first determining module, configured to determine a time period that includes the first timestamp from the first effective time period and the second effective time period;
a second determining module, configured to determine, according to a flow entry corresponding to the determined time period, a service node for receiving the first packet; and
a sending module, configured to send the first packet to the determined service node.
determine at least two service nodes according to an input node of the first packet and the first route mapping relationship;
generate a load balancing factor according to the first timestamp; and
determine, from the at least two service nodes according to the respective first load proportions of the at least two service nodes and the load balancing factor, a first service node for receiving the first packet.
determine at least two service nodes according to an input node of the first packet and the first route mapping relationship; and
determine, from the at least two service nodes according to the respective first load proportions of the at least two service nodes and the load balancing factor, a first service node for receiving the first packet.
a receiving module, configured to receive a first packet of a first service flow;
a determining module, configured to determine, according to a feature field included in the packet, that the first service flow is a service flow of a first service chain;
an identification module, configured to add a first timestamp of the first packet and a first service chain identifier to the first packet, where the first service chain identifier indicates that the first service flow is a service flow of the first service chain, and the first timestamp indicates a creation time of the first service flow; and
a sending module, configured to send the first packet to a switch.
a first obtaining module, configured to obtain first current load of each service node existing at a first moment;
a first generation module, configured to generate a first flow entry, where the first flow entry includes a first route mapping relationship of a service flow of a first service chain, a first load proportion of each service node, and a first effective time period of the first flow entry, and the first load proportion is generated according to the first current load of each service node;
a sending module, configured to send the first flow entry to a switch;
a second obtaining module, configured to obtain second current load of each service node existing at a second moment; and
a second generation module, configured to generate a second flow entry, where the second flow entry includes a second route mapping relationship of a packet of the first type of service flow, a second load proportion of each service node, and a second effective time period of the second flow entry, the second load proportion is generated according to the second current load of each service node, and the second effective time period is different from the first effective time period, where
the sending module is further configured to send the second flow entry to the switch.
a receiver, configured to: receive a first flow entry, where the first flow entry includes a first route mapping relationship of a service flow of a first service chain, a first load proportion of each service node, and a first effective time period of the first flow entry; receive a second flow entry, where the second flow entry includes a second route mapping relationship of the service flow of the first service chain, a second load proportion of each service node, and a second effective time period of the second flow entry, and the second effective time period is different from the first effective time period; and receive a first packet of a first service flow, where the first packet includes a first timestamp of the first service flow and a first service chain identifier, the first service chain identifier indicates that the first service flow is a service flow of the first service chain, and the first timestamp indicates a creation time of the first service flow;
a processor, configured to: determine a time period that includes the first timestamp from the first effective time period and the second effective time period; and determine, according to a flow entry corresponding to the determined time period, a service node for receiving the first packet; and
a transmitter, configured to send the first packet to the determined service node.
determining at least two service nodes according to an input node of the first packet and the first route mapping relationship;
generating a load balancing factor according to the first timestamp; and
determining, from the at least two service nodes according to the respective first load proportions of the at least two service nodes and the load balancing factor, a first service node for receiving the first packet.
determining at least two service nodes according to an input node of the first packet and the first route mapping relationship; and
determining, from the at least two service nodes according to the respective first load proportions of the at least two service nodes and the load balancing factor, a first service node for receiving the first packet.
a receiver, configured to receive a first packet of a first service flow;
a processor, configured to: determine, according to a feature field included in the first packet, that the first service flow is a service flow of a first service chain; and add a first timestamp of the first packet and a first service chain identifier to the first packet, where the first service chain identifier indicates that the first service flow is a service flow of the first service chain, and the first timestamp indicates a creation time of the first service flow; and
a transmitter, configured to send the first packet to a switch.
a receiver, configured to obtain first current load of each service node existing at a first moment;
a processor, configured to generate a first flow entry, where the first flow entry includes a first route mapping relationship of a service flow of a first service chain, a first load proportion of each service node, and a first effective time period of the first flow entry, and the first load proportion is generated according to the first current load of each service node; and
a transmitter, configured to send the first flow entry to a switch, where
the receiver is further configured to obtain second current load of each service node existing at a second moment;
the processor is further configured to generate a second flow entry, where the second flow entry includes a second route mapping relationship of a packet of the first type of service flow, a second load proportion of each service node, and a second effective time period of the second flow entry, the second load proportion is generated according to the second current load of each service node, and the second effective time period is different from the first effective time period; and
the transmitter is further configured to send the second flow entry to the switch.
a controller, configured to: obtain first current load of each service node existing at a first moment; generate a first flow entry, where the first flow entry includes a first route mapping relationship of a service flow of a first service chain, a first load proportion of each service node, and a first effective time period of the first flow entry, and the first load proportion is generated according to the first current load of each service node; send the first flow entry to a switch; obtain second current load of each service node existing at a second moment; generate a second flow entry, where the second flow entry includes a second route mapping relationship of a packet of the first type of service flow, a second load proportion of each service node, and a second effective time period of the second flow entry, and the second load proportion is generated according to the second current load of each service node; and send the second flow entry to the switch, where the second effective time period is different from the first effective time period;
a classifier, configured to: receive a first packet of a first service flow; determine, according to a feature field included in the first packet, that the first service flow is a service flow of the first service chain; add a first timestamp of the first packet and a first service chain identifier to the first packet, where the first service chain identifier indicates that the first service flow is a service flow of the first service chain, and the first timestamp indicates a creation time of the first service flow; and send the first packet to the switch; and
the switch, configured to: receive the first flow entry; receive the second flow entry; receive the first packet of the first service flow; determine a time period that includes the first timestamp from the first effective time period and the second effective time period; determine, according to a flow entry corresponding to the determined time period, a service node for receiving the first packet; and send the first packet to the determined service node.
determining at least two service nodes according to an input node of the first packet and the first route mapping relationship;
generating a load balancing factor according to the first timestamp; and
determining, from the at least two service nodes according to the respective first load proportions of the at least two service nodes and the load balancing factor, the first service node for receiving the first packet.
determining at least two service nodes according to an input node of the first packet and the first route mapping relationship; and
determining, from the at least two service nodes according to the respective first load proportions of the at least two service nodes and the load balancing factor, the first service node for receiving the first packet.
BRIEF DESCRIPTION OF DRAWINGS
FIG. 1 is a schematic diagram of a packet routing system;
FIG. 2A and FIG. 2B are a schematic flowchart of a route determining method according to an embodiment of this application;
FIG. 3 is a schematic flowchart of a further detailed route determining method according to an embodiment of this application;
FIG. 4 is another schematic flowchart of a route determining method according to an embodiment of this application;
FIG. 5 is a schematic structural block diagram of a route determining apparatus 300 according to an embodiment of this application;
FIG. 6 is a schematic structural block diagram of a route determining apparatus 400 according to an embodiment of this application;
FIG. 7 is a schematic structural block diagram of a route determining apparatus 500 according to an embodiment of this application;
FIG. 8 is a schematic structural block diagram of a route determining device 600 according to an embodiment of this application; and
FIG. 9 is a schematic diagram of a route determining system according to an embodiment of this application.
DESCRIPTION OF EMBODIMENTS
determining whether a start time of the second effective time period precedes an end time of the first effective time period; and
if the start time of the second effective time period precedes the end time of the first effective time period, changing the end time of the first effective time period to the start time of the second effective time period. Specifically, a flow entry delivered by the controller to the switch may further include an effective time period field used to indicate an effective time of the flow entry. If an effective time period of a subsequently received (generated) flow entry overlaps an effective time period of a previously received (generated) flow entry, a route for a packet including a timestamp that falls within an overlapping time period is determined by using a policy defined in the subsequent flow entry, to respond to a latest routing policy and quickly implement load balancing.
"Match: InPort=0, SC-ID=1, T1≤TimeStamp<T2.
Output: OutPort=1, Ratio=50%; OutPort=2, Ratio=50%."
a first receiving module 301, configured to: receive a first flow entry, where the first flow entry includes a first route mapping relationship of a service flow of a first service chain, a first load proportion of each service node, and a first effective time period of the first flow entry; and receive a second flow entry, where the second flow entry includes a second route mapping relationship of the service flow of the first service chain, a second load proportion of each service node, and a second effective time period of the second flow entry, and the second effective time period is different from the first effective time period;
a second receiving module 302, configured to receive a first packet of a first service flow, where the first packet includes a first timestamp of the first service flow and a first service chain identifier, the first service chain identifier indicates that the first service flow is a service flow of the first service chain, and the first timestamp indicates a creation time of the first service flow;
a first determining module 303, configured to determine a time period that includes the first timestamp from the first effective time period and the second effective time period;
a second determining module 304, configured to determine, according to a flow entry corresponding to the determined time period, a service node for receiving the first packet; and
a sending module 305, configured to send the first packet to the determined service node.
determine at least two service nodes according to an input node of the first packet and the first route mapping relationship;
generate a load balancing factor according to the first timestamp; and
determine, from the at least two service nodes according to the respective first load proportions of the at least two service nodes and the load balancing factor, a first service node for receiving the first packet.
determine at least two service nodes according to an input node of the first packet and the first route mapping relationship; and
determine, from the at least two service nodes according to the respective first load proportions of the at least two service nodes and the load balancing factor, a first service node for receiving the first packet.
a receiving module 401, configured to receive a first packet of a first service flow;
a determining module 402, configured to determine, according to a feature field included in the packet, that the first service flow is a service flow of a first service chain;
an identification module 403, configured to add a first timestamp of the first packet and a first service chain identifier to the first packet, where the first service chain identifier indicates that the first service flow is a service flow of the first service chain, and the first timestamp indicates a creation time of the first service flow; and
a sending module 404, configured to send the first packet to a switch.
a first obtaining module 501, configured to obtain first current load of each service node existing at a first moment;
a first generation module 502, configured to generate a first flow entry, where the first flow entry includes a first route mapping relationship of a service flow of a first service chain, a first load proportion of each service node, and a first effective time period of the first flow entry, and the first load proportion is generated according to the first current load of each service node;
a sending module 503, configured to send the first flow entry to a switch;
a second obtaining module 504, configured to obtain second current load of each service node existing at a second moment; and
a second generation module 505, configured to generate a second flow entry, where the second flow entry includes a second route mapping relationship of a packet of the first type of service flow, a second load proportion of each service node, and a second effective time period of the second flow entry, the second load proportion is generated according to the second current load of each service node, and the second effective time period is different from the first effective time period.
a receiver 601, configured to: receive a first flow entry, where the first flow entry includes a first route mapping relationship of a service flow of a first service chain, a first load proportion of each service node, and a first effective time period of the first flow entry; receive a second flow entry, where the second flow entry includes a second route mapping relationship of the service flow of the first service chain, a second load proportion of each service node, and a second effective time period of the second flow entry, and the second effective time period is different from the first effective time period; and receive a first packet of a first service flow, where the first packet includes a first timestamp of the first service flow and a first service chain identifier, the first service chain identifier indicates that the first service flow is a service flow of the first service chain, and the first timestamp indicates a creation time of the first service flow;
a processor 602, configured to: determine a time period that includes the first timestamp from the first effective time period and the second effective time period; and determine, according to a flow entry corresponding to the determined time period, a service node for receiving the first packet; and
a transmitter 603, configured to send the first packet to the determined service node.
determining at least two service nodes according to an input node of the first packet and the first route mapping relationship;
generating a load balancing factor according to the first timestamp; and
determining, from the at least two service nodes according to respective first load proportions of the at least two service nodes and the load balancing factor, a first service node for receiving the first packet.
determining at least two service nodes according to an input node of the first packet and the first route mapping relationship; and
determining, from the at least two service nodes according to respective first load proportions of the at least two service nodes and the load balancing factor, a first service node for receiving the first packet.
a receiver, configured to receive a first packet of a first service flow;
a processor, configured to: determine, according to a feature field included in the first packet, that the first service flow is a service flow of a first service chain; and add a first timestamp of the first packet and a first service chain identifier to the first packet, where the first service chain identifier indicates that the first service flow is a service flow of the first service chain, and the first timestamp indicates a creation time of the first service flow; and
a transmitter, configured to send the first packet to a switch.
a receiver, configured to obtain first current load of each service node existing at a first moment;
a processor, configured to generate a first flow entry, where the first flow entry includes a first route mapping relationship of a service flow of a first service chain, a first load proportion of each service node, and a first effective time period of the first flow entry, and the first load proportion is generated according to the first current load of each service node; and
a transmitter, configured to send the first flow entry to a switch.
a controller 701, configured to: obtain first current load of each service node existing at a first moment; generate a first flow entry, where the first flow entry includes a first route mapping relationship of a service flow of a first service chain, a first load proportion of each service node, and a first effective time period of the first flow entry, and the first load proportion is generated according to the first current load of each service node; send the first flow entry to a switch; obtain second current load of each service node existing at a second moment; generate a second flow entry, where the second flow entry includes a second route mapping relationship of a packet of the first type of service flow, a second load proportion of each service node, and a second effective time period of the second flow entry, and the second load proportion is generated according to the second current load of each service node; and send the second flow entry to the switch, where the second effective time period is different from the first effective time period;
a classifier 702, configured to: receive a first packet of a first service flow; determine, according to a feature field included in the first packet, that the first service flow is a service flow of the first service chain; add a first timestamp of the first packet and a first service chain identifier to the first packet, where the first service chain identifier indicates that the first service flow is a service flow of the first service chain, and the first timestamp indicates a creation time of the first service flow; and send the first packet to the switch; and
the switch 703, configured to: receive the first flow entry; receive the second flow entry; receive the first packet of the first service flow; determine a time period that includes the first timestamp from the first effective time period and the second effective time period; determine, according to a flow entry corresponding to the determined time period, a service node for receiving the first packet; and send the first packet to the determined service node.
receiving a first flow entry (103), wherein the first flow entry comprises a first route mapping relationship of a service flow of a first service chain, a first load proportion of each service node, and a first effective time period of the first flow entry;
receiving a second flow entry (106), wherein the second flow entry comprises a second route mapping relationship of the service flow of the first service chain, a second load proportion of each service node, and a second effective time period of the second flow entry, and the second effective time period is different from the first effective time period;
receiving a first packet of a first service flow (107), wherein the first packet comprises a first timestamp of the first service flow and a first service chain identifier, the first service chain identifier indicates that the first service flow is a service flow of the first service chain, and the first timestamp indicates a creation time of the first service flow;
determining, from the first effective time period and the second effective time period, a time period that includes the first timestamp (108);
determining, according to a flow entry corresponding to the determined time period, a service node for receiving the first packet (109); and
sending the first packet to the determined service node (110).
determining whether a start time of the second effective time period precedes an end time of the first effective time period; and
if the start time of the second effective time period precedes the end time of the first effective time period, changing the end time of the first effective time period to the start time of the second effective time period.
determining at least two service nodes according to an input node of the first packet and the first route mapping relationship (1091);
generating a load balancing factor according to the first timestamp (1092); and
determining, from the at least two service nodes according to respective first load proportions of the at least two service nodes and the load balancing factor, a first service node for receiving the first packet (1093).
determining at least two service nodes according to an input node of the first packet and the first route mapping relationship (1091); and
determining, from the at least two service nodes according to respective first load proportions of the at least two service nodes and the load balancing factor, a first service node for receiving the first packet (1093).
receiving a second packet of the first service flow (111); and
sending the second packet to the first service node (112).
starting a timeout timer (113); and
before the sending the second packet to the first service node (112), further comprising:
determining that the timeout timer does not expire (114).
receiving a first packet of a first service flow (201);
determining, according to a feature field comprised in the first packet, that the first service flow is a service flow of a first service chain (202);
adding a first timestamp of the first packet and a first service chain identifier to the first packet, wherein the first service chain identifier indicates that the first service flow is a service flow of the first service chain, and the first timestamp indicates a creation time of the first service flow (203); and
sending the first packet to a switch (204) adapted to perform the method steps of claim 1.
obtaining first current load of each service node existing at a first moment (101);
generating a first flow entry, wherein the first flow entry comprises a first route mapping relationship of a service flow of a first service chain, a first load proportion of each service node, and a first effective time period of the first flow entry, and the first load proportion is generated according to the first current load of each service node (101);
sending the first flow entry to a switch (102);
obtaining second current load of each service node existing at a second moment (104);
generating a second flow entry, wherein the second flow entry comprises a second route mapping relationship of the service flow of the first service chain, a second load proportion of each service node, and a second effective time period of the second flow entry, the second load proportion is generated according to the second current load of each service node, and the second effective time period is different from the first effective time period (104); and
sending the second flow entry to the switch adapted to perform the method step of claim 1.
a first obtaining module (501), configured to obtain first current load of each service node existing at a first moment;
a first generation module (502), configured to generate a first flow entry, wherein the first flow entry comprises a first route mapping relationship of a service flow of a first service chain, a first load proportion of each service node, and a first effective time period of the first flow entry, and the first load proportion is generated according to the first current load of each service node;
a sending module (503), configured to send the first flow entry to a switch;
a second obtaining module (504), configured to obtain second current load of each service node existing at a second moment; and
a second generation module (505), configured to generate a second flow entry, wherein the second flow entry comprises a second route mapping relationship of the service flow of the first service chain, a second load proportion of each service node, and a second effective time period of the second flow entry, the second load proportion is generated according to the second current load of each service node, and the second effective time period is different from the first effective time period, wherein
the sending module is further configured to send the second flow entry to the switch adapted to perform the method according to claim 1.
a controller (701), configured to: obtain first current load of each service node existing at a first moment; generate a first flow entry, wherein the first flow entry comprises a first route mapping relationship of a service flow of a first service chain, a first load proportion of each service node, and a first effective time period of the first flow entry, and the first load proportion is generated according to the first current load of each service node; send the first flow entry to a switch; obtain second current load of each service node existing at a second moment; generate a second flow entry, wherein the second flow entry comprises a second route mapping relationship of a packet of the first type of service flow, a second load proportion of each service node, and a second effective time period of the second flow entry, and the second load proportion is generated according to the second current load of each service node; and send the second flow entry to the switch, wherein the second effective time period is different from the first effective time period;
a classifier (702), configured to: receive a first packet of a first service flow; determine, according to a feature field comprised in the first packet, that the first service flow is a service flow of the first service chain; add a first timestamp of the first packet and a first service chain identifier to the first packet, wherein the first service chain identifier indicates that the first service flow is a service flow of the first service chain, and the first timestamp indicates a creation time of the first service flow; and send the first packet to the switch; and
the switch (703), configured to: receive the first flow entry; receive the second flow entry; receive the first packet of the first service flow; determine, from the first effective time period and the second effective time period, a time period that includes the first timestamp; determine, according to a flow entry corresponding to the determined time period, a service node for receiving the first packet; and send the first packet to the determined service node.
Empfangen eines ersten Datenstromeintritts (103), wobei der erste Datenstromeintritt umfasst: eine erste Routenzuordnungsbeziehung eines Dienstdatenstroms einer ersten Dienstkette, einen ersten Lastanteil von jedem Dienstknoten und eine erste effektive Zeitdauer des ersten Datenstromeintritts;
Empfangen eines zweiten Datenstromeintritts (106), wobei der zweite Datenstromeintritt umfasst: eine zweite Routenzuordnungsbeziehung des Dienstdatenstroms der ersten Dienstkette, einen zweiten Lastanteil von jedem Dienstknoten und eine zweite effektive Zeitdauer des zweiten Datenstromeintritts; und
wobei die zweite effektive Zeitdauer verschieden von der ersten effektiven Zeitdauer ist;
Empfangen eines ersten Datenpakets eines ersten Dienstdatenstroms (107), wobei das erste Datenpaket eine erste Zeitmarke des ersten Dienstdatenstroms und eine erste Dienstkettenkennung umfasst, wobei die erste Dienstkettenkennung anzeigt, dass der erste Dienstdatenstrom ein Dienstdatenstrom der ersten Dienstkette ist, und wobei die erste Zeitmarke einen Erstellungszeitpunkt des ersten Dienstdatenstroms anzeigt;
Ermitteln aus der ersten effektiven Zeitdauer und der zweiten effektiven Zeitdauer einer Zeitdauer, welche die erste Zeitmarke enthält (108);
Ermitteln gemäß einem Datenstromeintritt, welcher der ermittelten Zeitdauer entspricht, eines Dienstknotens zum Empfangen des ersten Datenpakets (109); und
Senden des ersten Datenpakets an den ermittelten Dienstknoten (110).
Ermitteln, ob ein Startzeitpunkt der zweiten effektiven Zeitdauer vor einem Endzeitpunkt der ersten effektiven Zeitdauer liegt; und
wenn der Startzeitpunkt der zweiten effektiven Zeitdauer vor dem Endzeitpunkt der ersten effektiven Zeitdauer liegt, Ändern des Endzeitpunkts der ersten effektiven Zeitdauer auf den Startzeitpunkt der zweiten effektiven Zeitdauer.
Ermitteln von mindestens zwei Dienstknoten gemäß einem Eingangsknoten des ersten Datenpakets und der ersten Routenzuordnungsbeziehung (1091);
Erzeugen eines Lastausgleichfaktors gemäß der ersten Zeitmarke (1092); und
Ermitteln aus den mindestens zwei Dienstknoten gemäß den jeweiligen Lastanteilen der mindestens zwei Dienstknoten und dem Lastausgleichfaktor eines ersten Dienstknotens zum Empfangen des ersten Datenpakets (1093).
Ermitteln von mindestens zwei Dienstknoten gemäß einem Eingangsknoten des ersten Datenpakets und der ersten Routenzuordnungsbeziehung (1091); und
Ermitteln gemäß den jeweiligen Lastanteilen der mindestens zwei Dienstknoten und dem Lastausgleichfaktor, eines ersten Dienstknotens zum Empfangen des ersten Datenpakets aus den mindestens zwei Dienstknoten (1093).
Empfangen eines zweiten Datenpakets des ersten Dienstdatenstroms (111), und
Senden des zweiten Datenpakets an den ersten Dienstknoten (112).
Starten einer Zeitüberschreitungsmesseinheit (113); und
wobei das Verfahren vor dem Senden des zweiten Datenpakets an den ersten Dienstknoten (112) außerdem umfasst:
Ermitteln, dass die Zeitüberschreitungsmesseinheit nicht abgelaufen ist (114).
Empfangen eines ersten Datenpakets eines ersten Dienstdatenstroms (201);
Ermitteln gemäß einem Merkmalsfeld, das in dem ersten Datenpaket enthalten ist, dass der erste Dienstdatenstrom ein Dienstdatenstrom einer ersten Dienstkette ist (202);
Hinzufügen einer ersten Zeitmarke des ersten Datenpakets und einer ersten Dienstkettenkennung zu dem ersten Datenpaket, wobei die erste Dienstkettenkennung anzeigt, dass der erste Dienstdatenstrom ein Dienstdatenstrom der ersten Dienstkette ist, und wobei die erste Zeitmarke einen Erstellungszeitpunkt des ersten Dienstdatenstroms anzeigt (203); und
Senden des ersten Datenpakets an einen Verteiler (204), der geeignet ist zum Ausführen der Verfahrensschritte nach Anspruch 1.
Erhalten einer an einem ersten Zeitpunkt (101) vorhandenen ersten aktuellen Last von jedem Dienstknoten;
Erzeugen eines ersten Datenstromeintritts, wobei der erste Datenstromeintritt umfasst:
eine erste Routenzuordnungsbeziehung eines Dienstdatenstroms einer ersten Dienstkette, einen ersten Lastanteil von jedem Dienstknoten und eine erste effektive Zeitdauer des ersten Datenstromeintritts, und wobei der erste Lastanteil gemäß der ersten aktuellen Last von jedem Dienstknoten erzeugt wird (101);
Senden des ersten Datenstromeintritts an einen Verteiler (102);
Erhalten einer an einem zweiten Zeitpunkt (104) vorhandenen zweiten aktuellen Last von jedem Dienstknoten;
Erzeugen eines zweiten Datenstromeintritts, wobei der zweite Datenstromeintritt umfasst: eine zweite Routenzuordnungsbeziehung des Dienstdatenstroms der ersten Dienstkette, einen zweiten Lastanteil von jedem Dienstknoten und eine zweite effektive Zeitdauer des zweiten Datenstromeintritts, wobei der zweite Lastanteil gemäß der zweiten aktuellen Last von jedem Dienstknoten erzeugt wird, und wobei die zweite effektive Zeitdauer verschieden von der ersten effektiven Zeitdauer ist (104); und
Senden des zweiten Datenstromeintritts an den Verteiler, der geeignet ist zum Ausführen der Verfahrensschritte nach Anspruch 1.
ein erstes Erhaltemodul (501), das konfiguriert ist zum Erhalten einer ersten an einem ersten Zeitpunkt vorhandenen aktuellen Last von jedem Dienstknoten;
ein erstes Erzeugungsmodul (502), das konfiguriert ist zum Erzeugen eines ersten Datenstromeintritts, wobei der erste Datenstromeintritt umfasst: eine erste Routenzuordnungsbeziehung eines Dienstdatenstroms einer ersten Dienstkette, einen ersten Lastanteil von jedem Dienstknoten und eine erste effektive Zeitdauer des ersten Datenstromeintritts, und wobei der erste Lastanteil gemäß der ersten aktuellen Last von jedem Dienstknoten erzeugt wird;
ein Sendemodul (503), das konfiguriert ist zum Senden des ersten Datenstromeintritts an einen Verteiler;
ein zweites Erhaltemodul (504), das konfiguriert ist zum Erhalten einer an einem zweiten Zeitpunkt vorhandenen zweiten aktuellen Last von jedem Dienstknoten; und
ein zweites Erzeugungsmodul (505), das konfiguriert ist zum Erzeugen eines zweiten Datenstromeintritts, wobei der zweite Datenstromeintritt umfasst: eine zweite Routenzuordnungsbeziehung des Dienstdatenstroms der ersten Dienstkette, einen zweiten Lastanteil von jedem Dienstknoten und eine zweite effektive Zeitdauer des zweiten Datenstromeintritts, wobei der zweite Lastanteil gemäß der zweiten aktuellen Last von jedem Dienstknoten erzeugt wird, und wobei die zweite effektive Zeitdauer verschieden von der ersten effektiven Zeitdauer ist, wobei das Sendemodul außerdem konfiguriert ist zum Senden des zweiten Datenstromeintritts an den Verteiler, der geeignet ist zum Ausführen des Verfahrens nach Anspruch 1.
eine Steuereinheit (701), die konfiguriert ist zum: Erhalten einer an einem ersten Zeitpunkt vorhandenen ersten aktuellen Last von jedem Dienstknoten; Erzeugen eines ersten Datenstromeintritts, wobei der erste Datenstromeintritt umfasst: eine erste Routenzuordnungsbeziehung eines Dienstdatenstroms einer ersten Dienstkette, einen ersten Lastanteil von jedem Dienstknoten und eine erste effektive Zeitdauer des ersten Datenstromeintritts, und wobei der erste Lastanteil gemäß der ersten aktuellen Last von jedem Dienstknoten erzeugt wird; Senden des ersten Datenstromeintritts an einen Verteiler; Erhalten einer an einem zweiten Zeitpunkt vorhandenen zweiten aktuellen Last von jedem Dienstknoten, die an einem zweiten Zeitpunkt vorhanden ist; Erzeugen eines zweiten Datenstromeintritts, wobei der zweite Datenstromeintritt umfasst: eine zweite Routenzuordnungsbeziehung eines Datenpakets des ersten Typs des Dienstdatenstroms, einen zweiten Lastanteil von jedem Dienstknoten und eine zweite effektive Zeitdauer des zweiten Datenstromeintritts, und wobei der zweite Lastanteil gemäß der zweiten aktuellen Last von jedem Dienstknoten erzeugt wird; und Senden des zweiten Datenstromeintritts an den Verteiler; wobei die zweite effektive Zeitdauer verschieden von der ersten effektiven Zeitdauer ist,
eine Klassifizierungseinheit (702), die konfiguriert ist zum: Empfangen eines ersten Datenpakets eines ersten Dienstdatenstroms; Ermitteln gemäß einem Merkmalsfeld, das in dem ersten Datenpaket enthalten ist, dass der erste Dienstdatenstrom ein Dienstdatenstrom der ersten Dienstkette ist; Hinzufügen einer ersten Zeitmarke des ersten Datenpakets und einer ersten Dienstkettenkennung zu dem ersten Datenpaket, wobei die erste Dienstkettenkennung anzeigt, dass der erste Dienstdatenstrom ein Dienstdatenstrom der ersten Dienstkette ist, und wobei die erste Zeitmarke einen Erstellungszeitpunkt des ersten Dienstdatenstroms anzeigt; und Senden des ersten Datenpakets an den Verteiler; und
wobei der Verteiler (703) konfiguriert ist zum: Empfangen des ersten Datenstromeintritts; Empfangen des zweiten Datenstromeintritts; Empfangen des ersten Datenpakets des ersten Dienstdatenstroms; Ermitteln aus der ersten effektiven Zeitdauer und der zweiten effektiven Zeitdauer einer Zeitdauer, welche die erste Zeitmarke enthält; Ermitteln gemäß einem Datenstromeintritt, welcher der ermittelten Zeitdauer entspricht, eines Dienstknotens zum Empfangen des ersten Datenpakets; und
Senden des ersten Datenpakets an den ermittelten Dienstknoten.
la réception d'une première entrée de flux (103), la première entrée de flux comprenant une première relation de mappage de voie d'acheminement d'un flux de services d'une première chaîne de service, une première proportion de charge de chaque nœud de service et une première période de temps effective de la première entrée de flux ;
la réception d'une deuxième entrée de flux (106), la deuxième entrée de flux comprenant une deuxième relation de mappage de voie d'acheminement du flux de services de la première chaîne de services, une deuxième proportion de charge de chaque nœud de service et une deuxième période de temps effective de la deuxième entrée de flux, et la deuxième période de temps effective étant différente de la première période de temps effective ;
la réception d'un premier paquet d'un premier flux de services (107), le premier paquet comprenant un premier horodatage du premier flux de services et un premier identifiant de chaîne de services, le premier identifiant de chaîne de services indiquant que le premier flux de services est un flux de services de la première chaîne de services, et le premier horodatage indiquant une heure de création du premier flux de services ; la détermination, à partir de la première période de temps effective et de la deuxième période de temps effective, d'une période de temps qui comprend le premier horodatage (108) ;
la détermination, selon une entrée de flux correspondant à la période de temps déterminée, d'un nœud de service pour recevoir le premier paquet (109) ; et
l'envoi du premier paquet au nœud de service déterminé (110).
la détermination si une heure de début de la deuxième période de temps effective précède une heure de fin de la première période de temps effective ; et
si l'heure de début de la deuxième période de temps effective précède l'heure de fin de la première période de temps effective, le changement de l'heure de fin de la première période de temps effective en heure de début de la deuxième période de temps effective.
la détermination d'au moins deux nœuds de service selon un nœud d'entrée du premier paquet et la première relation de mappage de voie d'acheminement (1091) ;
la génération d'un facteur d'équilibrage de charge selon le premier horodatage (1092) ; et
la détermination, à partir des au moins deux nœuds de service selon les premières proportions de charge respectives des au moins deux nœuds de service et le facteur d'équilibrage de charge, d'un premier nœud de service pour recevoir le premier paquet (1093).
la détermination d'au moins deux nœuds de service selon un nœud d'entrée du premier paquet et la première relation de mappage de voie d'acheminement (1091) ; et
la détermination, à partir des au moins deux nœuds de service selon les premières proportions de charge respectives des au moins deux nœuds de service et le facteur d'équilibrage de charge, d'un premier nœud de service pour recevoir le premier paquet (1093).
la réception d'un deuxième paquet du premier flux de services (111) ; et
l'envoi du deuxième paquet au premier nœud de service (112).
le démarrage d'un temporisateur d'expiration (113) ; et
comprenant en outre, avant l'envoi du deuxième paquet au premier nœud de service (112) :
la détermination que le temporisateur d'expiration n'expire pas (114).
la réception d'un premier paquet d'un premier flux de services (201) ;
la détermination, selon un champ de caractéristiques compris dans le premier paquet, que le premier flux de services est un flux de services d'une première chaîne de services (202) ;
l'ajout d'un premier horodatage du premier paquet et d'un premier identifiant de chaîne de services au premier paquet, le premier identifiant de chaîne de services indiquant que le premier flux de services est un flux de services de la première chaîne de services,
et le premier horodatage indiquant une heure de création du premier flux de services (203) ; et
l'envoi du premier paquet à un commutateur (204) adapté pour effectuer les étapes de procédé selon la revendication 1.
l'obtention d'une première charge actuelle de chaque nœud de service existant à un premier instant (101) ;
la génération d'une première entrée de flux, la première entrée de flux comprenant une première relation de mappage de voie d'acheminement d'un flux de services d'une première chaîne de services, une première proportion de charge de chaque nœud de service et une première période de temps effective de la première entrée de flux, et la première proportion de charge étant générée selon la première charge actuelle de chaque nœud de service (101) ;
l'envoi de la première entrée de flux à un commutateur (102) ;
l'obtention d'une deuxième charge actuelle de chaque nœud de service existant à un deuxième instant (104) ;
la génération d'une deuxième entrée de flux, la deuxième entrée de flux comprenant une deuxième relation de mappage de voie d'acheminement du flux de services de la première chaîne de services, une deuxième proportion de charge de chaque nœud de service, et une deuxième période de temps effective de la deuxième entrée de flux, la deuxième proportion de charge étant générée selon la deuxième charge actuelle de chaque nœud de service, et la deuxième période de temps effective étant différente de la première période de temps effective (104) ; et
l'envoi de la deuxième entrée de flux au commutateur adapté pour effectuer l'étape de procédé selon la revendication 1.
un premier module d'obtention (501), configuré pour obtenir une première charge actuelle de chaque nœud de service existant à un premier instant ;
un premier module de génération (502), configuré pour générer une première entrée de flux, la première entrée de flux comprenant une première relation de mappage de voie d'acheminement d'un flux de services d'une première chaîne de services, une première proportion de charge de chaque nœud de service et une première période de temps effective de la première entrée de flux, et la première proportion de charge étant générée selon la première charge actuelle de chaque nœud de service ;
un module d'envoi (503), configuré pour envoyer la première entrée de flux à un commutateur ;
un deuxième module d'obtention (504), configuré pour obtenir une deuxième charge actuelle de chaque nœud de service existant à un deuxième instant ; et
un deuxième module de génération (505), configuré pour générer une deuxième entrée de flux, la deuxième entrée de flux comprenant une deuxième relation de mappage de voie d'acheminement du flux de services de la première chaîne de services, une deuxième proportion de charge de chaque nœud de service et une deuxième période de temps effective de la deuxième entrée de flux, la deuxième proportion de charge étant générée selon la deuxième charge actuelle de chaque nœud de service, et la deuxième période de temps effective étant différente de la première période de temps effective, dans lequel
le module d'envoi est en outre configuré pour envoyer la deuxième entrée de flux au commutateur adapté pour effectuer le procédé selon la revendication 1.
un contrôleur (701), configuré pour : obtenir une première charge actuelle de chaque nœud de service existant à un premier instant ; générer une première entrée de flux, la première entrée de flux comprenant une première relation de mappage de voie d'acheminement d'un flux de services d'une première chaîne de services, une première proportion de charge de chaque nœud de service et une première période de temps effective de la première entrée de flux, et la première proportion de charge étant générée selon la première charge actuelle de chaque nœud de service ; envoyer la première entrée de flux à un commutateur ; obtenir la deuxième charge actuelle de chaque nœud de service existant à un deuxième instant ; générer une deuxième entrée de flux, la deuxième entrée de flux comprenant une deuxième relation de mappage de voie d'acheminement d'un paquet du premier type de flux de services, une deuxième proportion de charge de chaque nœud de service et une deuxième période de temps effective de la deuxième entrée de flux, et la deuxième proportion de charge étant générée selon la deuxième charge actuelle de chaque nœud de service ; et envoyer la deuxième entrée de flux au commutateur, la deuxième période de temps effective étant différente de la première période de temps effective ;
un classificateur (702), configuré pour : recevoir un premier paquet d'un premier flux de services ; déterminer, selon un champ de caractéristiques compris dans le premier paquet, que le premier flux de services est un flux de services de la première chaîne de services ; ajouter un premier horodatage du premier paquet et un premier identifiant de chaîne de services au premier paquet, le premier identifiant de chaîne de services indiquant que le premier flux de services est un flux de services de la première chaîne de services, et le premier horodatage indiquant une heure de création du premier flux de services ; et envoyer le premier paquet au commutateur ; et
le commutateur (703), configuré pour : recevoir la première entrée de flux ; recevoir la deuxième entrée de flux ; recevoir le premier paquet du premier flux de services ; déterminer, à partir de la première période de temps effective et de la deuxième période de temps effective, une période de temps qui comprend le premier horodatage ;
déterminer, selon une entrée de flux correspondant à la période de temps déterminée, un nœud de service pour recevoir le premier paquet ; et envoyer le premier paquet au nœud de service déterminé.
REFERENCES CITED IN THE DESCRIPTION
Patent documents cited in the description