CN102271079A - Message forwarding method, node and system - Google Patents
Message forwarding method, node and system Download PDFInfo
- Publication number
- CN102271079A CN102271079A CN2010101934142A CN201010193414A CN102271079A CN 102271079 A CN102271079 A CN 102271079A CN 2010101934142 A CN2010101934142 A CN 2010101934142A CN 201010193414 A CN201010193414 A CN 201010193414A CN 102271079 A CN102271079 A CN 102271079A
- Authority
- CN
- China
- Prior art keywords
- message
- traffic identifier
- node
- mpls label
- stream
- 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.)
- Granted
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a message forwarding method, nodes and a system belonging to the field of communication. The method comprises the following steps: an inlet node receives a first IP (Internet Protocol) message, generates a flow identification according to the first IP message, converts the flow identification into a corresponding MPLS (Multiple Protocol Label Switching) label and transmits the first IP message added with the MPLS label to a middle node; the middle node forwards the first IP message added with the MPLS label to an outlet node; and the outlet node converts the MPLS label into the corresponding flow identification and forwards the first IP message according to the flow identification. The invention also comprises nodes for realizing the method and a system consisting of all the nodes. The invention just needs the condition that the inlet node supports a flow identification generation technology, thereby preventing hardware reformation on a following node and reducing the complexity and distributing cost.
Description
Technical field
The present invention relates to the communications field, method, node and system that particularly a kind of message is transmitted.
Background technology
The communications field has proposed a kind of stream switching technology at present, the stream switching technology is not handled all messages at the 3rd layer, and first message in the analysis stream only, setting up stream table back transmits based on layer 3 address, it also is this message of routing forwarding, subsequent packet in the stream uses one or more shortcuts to circulate and sends out, and can solve network bottleneck problems such as the low forwarding rate that flows the inter-network section and cause, high time-delay.
Existing a kind of stream switching technology based on hash (Hash) look up table technique, in this stream switching technology, each interior node of the network segment all needs to carry out following operation:
Five-tuple information according to message, also be source address, destination address, source port number, destination slogan, protocol type, hash obtains short keyword, and utilize this keyword as the address of tabling look-up, the relevant retransmitting paramater of tabling look-up and obtaining flowing, and according to retransmitting paramater this message is circulated and to send out.
In realizing process of the present invention, the inventor finds that there is following problem at least in prior art:
Each node in the network segment all needs Hash to generate keyword, and hash algorithm needs hardware to realize usually, and need to introduce CAM (Content Addressable Memory, Content Addressable Memory), so prior art need be carried out hardware modification to the node of the whole network.
Summary of the invention
For when the stream switching technology that realizes based on the Hash look up table technique, avoid the node of the whole network is carried out hardware modification method, node and system that the embodiment of the invention provides a kind of message to transmit.Described technical scheme is as follows:
The method that a kind of message is transmitted, described method comprises:
Ingress node receives the first Internet protocol IP message;
Described Ingress node generates traffic identifier according to a described IP message;
Described Ingress node is converted to corresponding multiprotocol label switching MPLS label with described traffic identifier;
Described Ingress node sends to intermediate node with a described IP message that adds described MPLS label;
Described intermediate node is transmitted to Egress node with a described IP message of the described MPLS label of described interpolation;
Described Egress node is converted to corresponding traffic identifier with described MPLS label, and according to described traffic identifier, transmits a described IP message.
A kind of Ingress node, described Ingress node comprises:
First receiver module is used to receive the first Internet protocol IP message;
Generation module, an IP message that is used for receiving according to described first receiver module generates traffic identifier;
Modular converter is used for the traffic identifier that described generation module generates is converted to corresponding multiprotocol label switching MPLS label;
First sending module, a described IP message that is used for adding the MPLS label that described modular converter obtains sends to intermediate node, makes described intermediate node that a described IP message of the described MPLS label of described interpolation is transmitted to Egress node.
A kind of Egress node, described Egress node comprises:
Second receiver module, be used to receive the first Internet protocol IP message of the interpolation multiprotocol label switching MPLS label that intermediate node transmits, described MPLS label is that Ingress node generates traffic identifier according to a described IP message, and described traffic identifier is converted to;
Second forwarding module is used for described MPLS label is converted to corresponding traffic identifier, and according to described traffic identifier, transmits a described IP message.
The system that a kind of message is transmitted, described system comprises: Ingress node, intermediate node and Egress node;
Described Ingress node, be used to receive the first Internet protocol IP message, generate traffic identifier according to a described IP message, described traffic identifier is converted to corresponding multiprotocol label switching MPLS label, a described IP message that adds described MPLS label is sent to described intermediate node;
Described intermediate node is used for a described IP message of the described MPLS label of described interpolation is transmitted to described Egress node;
Described Egress node is used for described MPLS label is converted to corresponding traffic identifier, and according to described traffic identifier, transmits a described IP message.
The beneficial effect that the technical scheme that the embodiment of the invention provides is brought is:
Receive an IP message by Ingress node, generate traffic identifier according to an IP message, traffic identifier is converted to corresponding M PLS label, an IP message that adds the MPLS label is sent to intermediate node, intermediate node is transmitted to Egress node with an IP message that adds the MPLS label, Egress node is converted to corresponding traffic identifier with the MPLS label, and according to traffic identifier, transmit an IP message, realized a kind of stream switching technology that only needs Ingress node to support the traffic identifier generation, the Hash stream switching technology of tabling look-up for example, avoided subsequent node is carried out hardware modification, thereby reduced the complexity and the lower deployment cost of subsequent node, helped the promotion and application of the stream switching technology of tabling look-up based on Hash.
Description of drawings
Fig. 1 is the method flow diagram that the message that provides of the embodiment of the invention is transmitted;
Fig. 2 is the network architecture schematic diagram that the message that provides of the embodiment of the invention is transmitted;
Fig. 3 is the information interaction figure that the stream table that provides of the embodiment of the invention is set up;
Fig. 4 is that the band that the embodiment of the invention provides flows prolate-headed IPv6 message schematic diagram;
Fig. 5 is the stream extension header schematic diagram of the IPv6 that provides of the embodiment of the invention;
Fig. 6 is the information interaction figure that the message that provides of the embodiment of the invention is transmitted;
Fig. 7 is that the IP OAM message that the embodiment of the invention provides is created the interaction figure that path, negotiation and statistical quality of service are sent out in circulation;
Fig. 8 a is the structural representation of the Ingress node that provides of the embodiment of the invention;
Fig. 8 b is another structural representation of the Ingress node that provides of the embodiment of the invention;
Fig. 9 a is the structural representation of the Egress node that provides of the embodiment of the invention;
Fig. 9 b is another structural representation of the Egress node that provides of the embodiment of the invention;
Figure 10 is the system schematic that the message that provides of the embodiment of the invention is transmitted.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, embodiment of the present invention is described further in detail below in conjunction with accompanying drawing.
Referring to Fig. 1, the method that present embodiment provides a kind of message to transmit comprises:
101: Ingress node receives an IP (Internet Protocol, Internet protocol) message;
102: Ingress node generates traffic identifier according to an IP message;
Optionally, before this step, Ingress node receives the 2nd IP message, generate traffic identifier according to the 2nd IP message, and set up first-class table according to traffic identifier, first-class table comprises at least: the traffic identifier and first outbound port number, traffic identifier is arranged in the stream extension header of the 2nd IP message, and transmit the 2nd IP message, and make the Egress node that receives the 2nd IP message set up the second stream table according to traffic identifier, the second stream table comprises at least: the traffic identifier and second outbound port number.
103: Ingress node is converted to corresponding M PLS (Multiprotocol Label Switching, multiprotocol label switching) label with traffic identifier;
104: Ingress node sends to intermediate node with an IP message that adds the MPLS label;
105: intermediate node is transmitted to Egress node with an IP message that adds the MPLS label;
106: Egress node is converted to corresponding traffic identifier with the MPLS label, and according to traffic identifier, transmits an IP message.
Present embodiment receives an IP message by Ingress node, generate traffic identifier according to an IP message, traffic identifier is converted to corresponding M PLS label, an IP message that adds the MPLS label is sent to intermediate node, intermediate node is transmitted to Egress node with an IP message that adds the MPLS label, Egress node is converted to corresponding traffic identifier with the MPLS label, and according to traffic identifier, transmit an IP message, realized a kind of stream switching technology that only needs Ingress node to support the traffic identifier generation, the Hash stream switching technology of tabling look-up for example, avoided subsequent node is carried out hardware modification, thereby reduced the complexity and the lower deployment cost of subsequent node, helped the promotion and application of the stream switching technology of tabling look-up based on Hash.
The method that present embodiment provides a kind of message to transmit is introduced in detail below in conjunction with the network architecture shown in Figure 2.This network architecture comprises: comprise transmit leg S, Ingress node PE1, intermediate node P, Egress node PE2, recipient R.Wherein, Ingress node PE1, intermediate node P, Egress node PE2 belong to same carrier network, and Ingress node PE1 and Egress node PE2 are the fringe node of this network.
Before transmitting the IP message, Ingress node, Egress node need be set up the first-class table and the second stream table respectively according to the IP message, and intermediate node need not be set up the stream table.Below introduce in detail the process of setting up the stream table before the IP message of transmitting.Referring to Fig. 3, detailed process is as follows:
301: the sending direction Ingress node sends the IP message;
Wherein, this IP message is the 2nd IP message, and Ingress node receives the 2nd IP message earlier usually, receives an IP message again, abbreviates the 2nd IP message as the IP message between step 301-307.
Further, transmit leg is judged whether this IP message needs to circulate and is sent out, if desired, for example, this IP message is that occupied bandwidth is big, the audio/video of longer duration stream (or title " elephant stream "), then carries the stream extension header in this IP message, at this moment, flow prolate-headed Flow ID (traffic identifier) and can be sky, promptly transmit leg need not to be hash.
Wherein, the IP message specifically can be IPv4 (Internet Protocol Version 4, Internet protocol the 4th version) or IPv6 (Internet Protocol Version 6, Internet protocol the 6th version).
Fig. 4 is the prolate-headed IPv6 message schematic diagram of a band stream, and the Next Header territory follow-up IPv6 extension header that carries of statement is used for carrying stream relevant information.The stream extension header can adopt new extension header, or utilizes existing " Hop-by-Hop Options Header " to carry the stream relevant information, and message all can be checked and handles through each node on the path its loaded information.Fig. 5 is the stream extension header schematic diagram of IPv6.Wherein,
Next Header (next head) is used to show that IPv6 extension header protocol type is Flow (stream);
Hdr Ext Len (extension header length) is used to show the prolate-headed length of IPv6;
Flow ID (traffic identifier) is used to carry the keyword that Ingress node generates according to IP message information Hash, can surpass 20, and Fig. 4 only is a schematic diagram;
M (transmitting sign) is used to show to be to adopt MPLS (Multiprotocol Label Switching, multiprotocol label switching) label to transmit, and still adopts Flow ID to transmit;
RSV (reserved place) is used to expanded function in the future to reserve;
Flow QoS parameter (stream QoS parameter) is optional, is used to carry the stream qos parameter relevant with flow ID, as loss ratio (packet loss), BW (Bandwidth, bandwidth);
Sequence Number (sequence number) is optional, is used to cooperate the relevant loss ratio of statistics stream;
Hash parameter (Hash parameter) is optional, is used to carry the generation flow pairing Source IP of ID (source address), Flow label IP message informations such as (stream labels).
In addition, for IPv4, can expand a Flow Option (stream option) in the IPv4 heading, removing does not have Next Header, and outside the Hdr Ext Len parameter, other parameters repeat no more here with the stream extension header of IPv6.
302: Ingress node receives this IP message, sends out if this IP message need circulate, and creates the stream table (first-class table) of this IP message correspondence of this node;
Wherein, Ingress node judges whether to circulate to send out and specifically comprises: whether carry the stream extension header according to this IP message, judge that this IP message need circulate to send out.If carry the stream extension header, then need to circulate and send out, if do not carry the stream extension header, then do not need to circulate and send out.
Wherein, stream table constructive process is specially: Ingress node generates correspondent keyword according to IP message information hash, it is this keyword that Flow ID is set, look into first outbound port number that this node routing table can obtain this IP message then, with Flow ID and corresponding first outbound port thereof number a record as this node stream table.
Wherein, Ingress node can comprise by following three kinds of methods realization at least according to the Flow ID that IP message information hash generates this IP message:
Be hash according to Source IP (source address), the Flow label of IP message and obtain keyword, it as Flow ID, is established source address=a in the present embodiment, Flow label (stream label)=b, and establish Flow ID=12345.Accordingly, algorithm can be expressed as Flow ID=hash algorithm { Source IP, Flow label}.
Perhaps, be hash according to source address, Destination IP (destination address) and the Flow label of IP message and obtain keyword, with it as Flow ID.Accordingly, algorithm can be expressed as Flow ID=hash algorithm { Source IP, Destination IP, Flow label}.
Perhaps, obtain keyword as hash according to source address, destination address, Source port (source port number), Destinationport (destination slogan) and the Protocol type (protocol type) of this IP message, with it as Flow ID.Accordingly, algorithm can be expressed as Flow ID=hash algorithm { Source IP, Destination IP, Source port, Destination port, Protocol type}.
In the present embodiment, first outbound port of establishing Ingress node Flow ID=12345 correspondence number is 1, and then Ingress node is set up first-class table referring to table 1.
Table 1
| Flow?ID | First outbound port number |
| 12345 | 1 |
303: the Flow ID=12345 that Ingress node obtains hash adds the stream extension header of this IP message to;
Step 302 and 303 there is no sequential relationship, promptly also can carry out 303 earlier and carry out 302 again.
304: Ingress node will carry the prolate-headed IP message of stream of Flow ID=12345, send to subsequent node by the outbound port route that finds;
Wherein, subsequent node can be an intermediate node, it also can be Egress node, also be that Ingress node can directly send to Egress node with the IP message, also can be transmitted to Egress node by intermediate node, Ingress node and Egress node do not have essential difference to the processing of IP message in the dual mode, and therefore follow-up present embodiment is that intermediate node describes with the subsequent node.
305: intermediate node will carry the prolate-headed IP message routing of stream and be transmitted to Egress node;
Wherein, intermediate node can have one or more, and present embodiment is the example explanation with an intermediate node, and the process that each intermediate node is built the stream table to this IP message is identical, and difference only is the object difference that the IP message routing is transmitted.
306: Egress node is created the stream table (the second stream table) of this IP message correspondence of this node;
Concrete, second outbound port of this IP message that Egress node obtains the prolate-headed FlowID of IP message flow that receives and Cha Ben node routing table number is as a record of this node stream table.
In the present embodiment, setting out mouthful second outbound port of node Flow ID=12345 correspondence is 3, and then Egress node is set up the second stream table, referring to table 2.
Table 2
| Flow?ID | Second outbound port number |
| 12345 | 3 |
307: behind the Egress node deletion stream extension header, this IP message of routing forwarding is given the recipient.
So far, Ingress node, Egress node have been set up the first-class table and the second stream table of this node respectively.Need to prove that the above-mentioned first-class table and second stream are shown to need at least to comprise in this stream table: Flow ID and outbound port number, but be not limited only to this, can also content as required comprise other option.
The method that above-mentioned stream table is set up, subsequent node does not need to carry out Hash calculation, avoided subsequent node is carried out hardware modification, thereby reduced the complexity and the lower deployment cost of subsequent node, helped the promotion and application of the stream switching technology of tabling look-up, even traffic identifier is longer on the other hand based on Hash, for example above 20, also can realize, and can realize the negotiation of QoS (Quality of Service, service quality) and statistics etc. with extension header.
Further, Ingress node and Egress node can also adopt additive method to set up the stream table, and present embodiment does not limit.For example, Ingress node and Egress node generate traffic identifier according to IP message Hash respectively, set up the stream table of this node according to the traffic identifier that generates.
After the process based on the stream table of above-mentioned foundation, according to the stream table of setting up, carry out the process that message transmits and see also Fig. 6, its handling process is as follows:
401: the sending direction Ingress node sends the IP message;
Wherein, this IP message is an IP message, is generally and sets up the IP message that receives behind the stream table, is called for short the IP message between step 401-407.
402: Ingress node receives this IP message, and circulation is sent out if desired, then generates the Flow ID of this IP message according to the IP message information;
403: Ingress node is converted to the MPLS label with Flow ID;
Ingress node specifically has two kinds of conversion methods:
A kind ofly be, directly with Flow ID as the MPLS label.Can not have the MPLS tag entry in the method stream table, saved memory.
Another kind is according to the default Flow ID and the mapping relations of MPLS label, Flow ID to be converted to corresponding M PLS label.
Wherein, the MPLS label can be LSP (Label Switched Path, label switched path) label, PW (Pseudo Wires, pseudo-line) label or Flow label (stream label), and corresponding, the MPLS passage is lsp tunnel, PW passage or circulation road.If Flow ID surpasses 20, can adopt the form of MPLS label stack to support by multistage label.
404: Ingress node sends the IP message that adds the MPLS label;
Concrete, Ingress node is looked into the first-class table of this node according to Flow ID and is obtained its first outbound port number, and an IP message that adds MPLS label=12345 is sent out in circulation.
405: intermediate node carries out the MPLS exchange according to the MPLS label, and the IP message is transmitted to Egress node;
Also promptly, intermediate node is transmitted to other intermediate nodes and Egress node by the MPLS passage of MPLS label correspondence with this IP message.Wherein, each intermediate node does not need perception stream when carrying out the MPLS exchange.
406: Egress node is converted to Flow ID with the MPLS label;
Egress node specifically have two kinds with the corresponding conversion method of Ingress node, a kind of be directly with the MPLS label as Flow ID, another kind is according to the default Flow ID and the mapping relations of MPLS label, and the MPLS label is converted to corresponding Flow ID.
407: Egress node is looked into this node stream table (second stream table) according to Flow ID and is obtained its second outbound port, by second outbound port that finds number the IP message flow of Flow ID=12345 is transmitted to the recipient.
In the present embodiment, setting out mouthful second outbound port of node Flow ID=12345 correspondence number is 3.
The method that above-mentioned message is transmitted, only need Ingress node to support the stream switching technology that traffic identifier generates, the Hash stream switching technology of tabling look-up for example, avoided subsequent node is carried out hardware modification, thereby reduced the complexity and the lower deployment cost of subsequent node, helped the promotion and application of the stream switching technology of tabling look-up based on Hash.And, intermediate node does not participate in circulation and sends out, only do the MPLS exchange, Liu subsequent packet just can alleviate the burden that the extremely low Traditional IP route network of efficient is sent out in circulation from Ingress node by the MPLS network of offload (bypass) to new suitable efficient this stream of forwarding like this.In addition, the stream table can be transmitted software upgrading by original MPLS and realize, the MPLS network that can utilize operator to dispose is realized transmitting based on the MPLS of flow awareness, has effectively protected the investment of operator to existing network.
Further, set up in the process at step 301-307 stream table, before step 305, intermediate node also can be set up the stream table according to the traffic identifier in the IP message flow extension header.Accordingly, the method that present embodiment also provides a kind of message to transmit, be that Ingress node is arranged on traffic identifier in the stream extension header of IP message and sends to subsequent node (comprising intermediate node and Egress node), subsequent node is obtained this traffic identifier from the stream extension header, and, transmit this IP message according to the stream table of this traffic identifier and above-mentioned foundation.This retransmission method only needs Ingress node to support the stream switching technology that traffic identifier generates, the Hash stream switching technology of tabling look-up for example, avoided subsequent node is carried out hardware modification, thereby reduced the complexity and the lower deployment cost of subsequent node, helped the promotion and application of the stream switching technology of tabling look-up based on Hash.
Further, set up in the process at the stream table, the 2nd IP message specifically can be IP OAM (OperationAdministration and Maintenance, operational administrative and maintenance) message, this IP OAM message is sent out the path except being used for creating circulation, can also be used to consult QoS (Quality of Service, service quality) parameter is so that resource reservation, and the qos statistic that flows etc., be that example describes with agreed bandwidth, statistics loss ratio (packet loss) below, referring to Fig. 7, specifically comprise:
501: transmit leg sends IP OAM message (establishing its source address=a, Flow label=b);
Wherein, IP OAM message can be defined as ICMP (Internet Control Message Protocol, the Internet Internet Control Message Protocol) message, perhaps LDP (Label Distribution Protocol, tag distribution protocol)/RSVP (Resource Reservation Protocol, RSVP) message, perhaps IP OAM message can also be the IP OAM message that IP datagram Wen Suilu carries.Because agreements such as LDP/RSVP are based on Session's (session), stream is thinner than the granularity of Session, send out the path if still adopt the LDP/RSVP agreement to set up circulation, network extensibility will be a serious challenge, the foundation that utilizes IP OAM message to carry out the IP forward-path distributes, the Session of Maintenance free LDP/RSVP, thus the risk that scalability problem appears in network reduced.
The parameter that IP OAM message carries comprises: Flow ID (traffic identifier), Flow QoS parameter (stream QoS parameter), Sequence Number (sequence number), Hash parameter (Hash parameter) etc.; These parameters can be carried in the IP OAM message flow extension header.
Wherein, present embodiment does not limit the particular content of stream qos parameter, and present embodiment is that example describes with the bandwidth, establishes stream desired BW (Band Width, bandwidth)=2Mbps herein.
In addition, flow prolate-headed Flow ID and can be sky this moment, and promptly transmit leg need not to be hash.
502: Ingress node PE1 generates the Flow ID of IP OAM message, and creates the respective record of stream table;
Concrete, generate correspondent keyword according to IP OAM message information hash, it is this keyword that Flow ID is set, and looks into the outbound port number that this node routing table can obtain this IP OAM message then, with Flow ID and corresponding output port thereof a number record as this node stream table.
, establish according to source address=a, Flow label=b, hash obtain Flow ID=12345 herein, and establishing its outbound port number is 1.
503: Ingress node carries out CAC (Call Admission Control, control is admitted in session) according to the stream qos parameter, and the result who establishes CAC herein is the bandwidth that Ingress node can only provide stream BW=1Mbps;
Wherein, the stream qos parameter can flow extension header by transmit leg and obtain, or pre-configured in Ingress node, or obtains by the inquiry associated server.
But this moment, the stream qos parameter item of Flow ID correspondence was empty, needed waiting step 511 resource reservation results.
504: Ingress node is transmitted IP OAM message, carries parameter F low ID=12345 and self CAC BW=1Mbps as a result, and the destination is Egress node (or recipient);
505a: intermediate node P receives IP OAM message, carries out CAC according to the stream qos parameter, and establishing CAC result herein is the bandwidth that intermediate node can only provide stream BW=500Kbps;
505b: intermediate node is created the respective record of stream table according to the prolate-headed Flow ID of IP OAM message flow;
Concrete, the outbound port that intermediate node obtains this IP message with the prolate-headed Flow ID of IP OAM message flow that receives and Cha Ben node routing table number, establishing its outbound port number is 2, as a record of this node stream table.
But this moment, the QoS item of Flow ID correspondence was empty, needed waiting step 514 resource reservation results;
506: intermediate node is transmitted IP OAM message, carries parameter F low ID=12345 and self CAC BW=500Kbps as a result;
507a: Egress node PE2 receives IP OAM message, carries out CAC according to the stream qos parameter, and establishing CAC result herein is the bandwidth that Egress node can only provide stream BW=250Kbps;
507b: Egress node is created the respective record of stream table according to the prolate-headed Flow ID of IP OAM message flow;
Concrete, Egress node obtains the outbound port number of this IP message with the prolate-headed Flow ID of the IP message flow that receives and Cha Ben node routing table, and establishing its outbound port number is 3, as a record of this node stream table.
But this moment, the QoS item of Flow ID correspondence was empty, needed waiting step 517 resource reservation results;
508: Egress node is transmitted IP OAM message and is given the recipient, carries parameter F low ID=12345 and self CRC BW=250Kbps as a result;
509: the recipient receives IP OAM message, knows that self can only receive the stream of BW=200Kbps, and counts the loss ratio (packet loss) of a period of time;
Concrete, loss ratio statistical method comprises: the sequence number (sequence number) to the stream packet that receives detects, divided by the sequence number difference of first stream packet with an end stream packet, the merchant who obtains is the loss ratio in this time period with the message amount that receives in a period of time.Present embodiment is established loss ratio (recipient)=99%.
510: the recipient replys IP OAM message, carries parameter F low ID=12345, BW=200Kbps, loss ratio (recipient)=99%;
511: Egress node carries out resource reservation according to the result of CAC, and according to the prolate-headed Flow ID of IP OAM message flow and the resource reservation result (BW=200Kbps) that receive, refresh the respective item of stream table, promptly the stream qos parameter of Flow ID=12345 correspondence refreshes and is 200Kps;
512: Egress node counts the loss ratio of a period of time, and refreshes the stream table, fills in the packet loss of Flow ID=12345 correspondence, and present embodiment is made as 99%;
Wherein, loss ratio statistical method is identical with step 509, repeats no more here.
At this moment, the stream table of Egress node PE2 is referring to table 3.
Table 3
| Flow?ID | Outbound port | Packet loss | QoS(BW) |
| 12345 | 3 | 99％ | 200Kbps |
513: Egress node is transmitted IP OAM message, carries parameter F low ID=12345, BW=200Kbps, loss ratio (PE2)=99%, loss ratio (recipient)=99%;
514:IP OAM message is through intermediate node, intermediate node carries out resource reservation according to the result of CAC, and according to the prolate-headed Flow ID of IP OAM message flow and the resource reservation result (BW=200Kbps) that receive, refresh the respective item of stream table, promptly the qos parameter of Flow ID=12345 correspondence refreshes and is 200Kps;
515: intermediate node counts the loss ratio of a period of time, and refreshes the stream table, fills in the packet loss of Flow ID=12345 correspondence, and present embodiment is made as 99%;
Wherein, loss ratio statistical method is identical with step 509, repeats no more here.
At this moment, the stream table of intermediate node P is referring to table 4.
Table 4
| Flow?ID | Outbound port | Packet loss | QoS(BW) |
| 12345 | 2 | 99％ | 200Kbps |
516: intermediate node is transmitted IP OAM message, carries parameter F low ID=12345, BW=200Kbps, loss ratio (P)=99%, loss ratio (PE2)=99%, loss ratio (recipient)=99%;
517:IP OAM message arrives Ingress node, Ingress node carries out resource reservation according to the result of CAC, and according to the prolate-headed Flow ID of IP OAM message flow and the resource reservation result (BW=200Kbps) that receive, refresh the respective item of stream table, promptly the qos parameter of Flow ID=12345 correspondence refreshes and is 200Kps;
518: Ingress node counts the loss ratio of a period of time, and refreshes the stream table, fills in the packet loss of Flow ID=12345 correspondence, and present embodiment is made as loss ratio (PE1)=100%;
At this moment, the stream table of Ingress node PE1 is referring to table 5.
Table 5
| Flow?ID | Outbound port | Packet loss | QoS(BW) |
| 12345 | 1 | 100％ | 200Kbps |
519: Ingress node is transmitted IP OAM message and is given transmit leg, carries parameter: source address=a, Flowlabel=b, BW=200Kbps, loss ratio (PE1)=100%, loss ratio (P)=99%, loss ratio (PE2)=99% loss ratio (recipient)=99%;
Wherein, Ingress node needs Flow ID is converted to source address and Flow label, because have only the corresponding hash algorithm of the just unified configuration of carrier network devices usually, subscriber equipment is not known corresponding hash algorithm, also for the cause of falling cost, subscriber equipment need not be supported hash in addition.
520: after transmit leg received IP OAM message, decision was adjusted the speed of stream transmission or is no longer supported this stream according to BW=200Kbps;
Simultaneously, transmit leg can be according to loss ratio (PE1)=100%, loss ratio (P)=99%, and lossratio (PE2)=99%, loss ratio (recipient)=99% judges that packet loss appears in network P node rather than packet loss appears in the recipient.
Alternatively, network management system can be inquired about the stream table of each node, obtains the lossratio of the respective streams of each node, thereby orients the network failure point, and this routine network failure point appears between PE1 to the P node and (comprises the P node).
The method that present embodiment provides, subsequent node does not need to carry out Hash calculation on the one hand, avoided subsequent node is carried out hardware modification, thereby reduced the complexity and the lower deployment cost of subsequent node, helped the promotion and application of the stream switching technology of tabling look-up based on Hash; The stream relevant parameter of can also holding consultation simultaneously so that resource reservation, flows the statistics of relevant parameter, guarantees the service quality of stream, has remedied existing IP network and has not possessed the shortcoming that QoS guarantees ability; In addition, corresponding common OAM message, the OAM message that present embodiment provides can carry out negotiation and the statistics of QoS based on the IP layer.
Referring to Fig. 8 a, present embodiment provides a kind of Ingress node, comprising:
First receiver module 601 is used to receive an IP message;
Generation module 602 is used for generating traffic identifier according to the IP message that first receiver module 601 receives;
Modular converter 603 is used for the traffic identifier that generation module 602 generates is converted to corresponding M PLS label;
First sending module 604, an IP message that is used for adding the MPLS label that modular converter 603 obtains sends to intermediate node, makes intermediate node that an IP message that adds the MPLS label is transmitted to Egress node.
Wherein, referring to Fig. 8 b, modular converter 603 comprises: the first converting unit 603a or the second converting unit 603b;
The first converting unit 603a is used for traffic identifier as the MPLS label;
The second converting unit 603b is used for the mapping relations according to traffic identifier and MPLS label, and traffic identifier is converted to corresponding M PLS label.
Wherein, first receiver module 601 also is used to receive the 2nd IP message;
Generation module 602, the 2nd IP message that also is used for receiving according to first receiver module 601 generates traffic identifier, and sets up first-class table according to traffic identifier, and first-class table comprises at least: the traffic identifier and first outbound port number;
First sending module 604, also be used for traffic identifier is arranged on the stream extension header of the 2nd IP message, and transmit the 2nd IP message, and make the Egress node that receives the 2nd IP message set up the second stream table according to traffic identifier, the second stream table comprises at least: the traffic identifier and second outbound port number.
Wherein, first sending module 604 also is used for according to first-class table, and an IP message that adds the MPLS label is sent to intermediate node.
Wherein, the 2nd IP message is an IP operation management maintain OAM message, also carries service quality QoS parameter in the stream extension header of IP OAM message, is used to consult qos parameter or carries out qos statistic.
The Ingress node that present embodiment provides, by receiving an IP message, generate traffic identifier according to an IP message, traffic identifier is converted to corresponding M PLS label, an IP message that adds the MPLS label is sent to intermediate node, make intermediate node that an IP message that adds the MPLS label is transmitted to Egress node, realized a kind of stream switching technology that only needs Ingress node to support the traffic identifier generation, the Hash stream switching technology of tabling look-up for example, avoided subsequent node is carried out hardware modification, thereby reduced the complexity and the lower deployment cost of subsequent node, helped the promotion and application of the stream switching technology of tabling look-up based on Hash.
Referring to Fig. 9 a, present embodiment provides a kind of Egress node, comprising:
Second receiver module 701 is used to receive the first Internet protocol IP message of the interpolation multiprotocol label switching MPLS label that intermediate node transmits, and the MPLS label is that Ingress node generates traffic identifier according to an IP message, and traffic identifier is converted to;
Second forwarding module 702 is used for the MPLS label is converted to corresponding traffic identifier, and according to traffic identifier, transmits an IP message.
Referring to Fig. 9 b, second forwarding module 702 comprises: the 3rd converting unit 702a or the 4th converting unit 702b;
The 3rd converting unit 702a is used for the MPLS label as traffic identifier;
The 4th converting unit 702b is used for the mapping relations according to traffic identifier and MPLS label, and MPLS is converted to corresponding traffic identifier.
Wherein, second receiver module 701.Also be used to receive the 2nd IP message, carry traffic identifier in the stream extension header of the 2nd IP message from Ingress node;
Egress node also comprises sets up module, is used for setting up the second stream table according to traffic identifier, and the second stream table comprises at least: the traffic identifier and second outbound port number.
Wherein, second forwarding module 702 also is used for transmitting an IP message according to the traffic identifier and the second stream table.
Wherein, the 2nd IP message is an IP operation management maintain OAM message, also carries service quality QoS parameter in the stream extension header of IP OAM message, is used to consult qos parameter or carries out qos statistic.
The Egress node that present embodiment provides, by receiving an IP message of the interpolation MPLS label that intermediate node transmits, the MPLS label is that Ingress node generates traffic identifier according to an IP message, and traffic identifier is converted to, Egress node is converted to corresponding traffic identifier with the MPLS label, and according to traffic identifier, transmit an IP message, realized a kind of stream switching technology that only needs Ingress node to support the traffic identifier generation, the Hash stream switching technology of tabling look-up for example, avoided subsequent node is carried out hardware modification, thereby reduced the complexity and the lower deployment cost of subsequent node, helped the promotion and application of the stream switching technology of tabling look-up based on Hash.
Referring to Figure 10, the system that present embodiment provides a kind of message to transmit comprises: Ingress node 801, intermediate node 802 and Egress node 803;
Ingress node 801 is used to receive the first Internet protocol IP message, generates traffic identifier according to an IP message, and traffic identifier is converted to corresponding multiprotocol label switching MPLS label, and an IP message that adds the MPLS label is sent to intermediate node 802;
Intermediate node 802, an IP message that is used for adding the MPLS label is transmitted to Egress node 803;
Egress node 803 is used for the MPLS label is converted to corresponding traffic identifier, and according to traffic identifier, transmits an IP message.
Wherein, Ingress node 801 comprises: first converting unit or second converting unit;
First converting unit is used for traffic identifier as the MPLS label;
Second converting unit is used for the mapping relations according to traffic identifier and MPLS label, and traffic identifier is converted to corresponding M PLS label.
Wherein, Egress node 803 comprises: the 3rd converting unit or the 4th converting unit;
The 3rd converting unit is used for the MPLS label as traffic identifier;
The 4th converting unit is used for the mapping relations according to traffic identifier and MPLS label, and MPLS is converted to corresponding traffic identifier.
Wherein, Ingress node 801, also be used for according to before the IP message generation traffic identifier, receive the 2nd IP message, generate traffic identifier according to the 2nd IP message, and set up first-class table according to traffic identifier, first-class table comprises at least: the traffic identifier and first outbound port number, traffic identifier is arranged in the stream extension header of the 2nd IP message, and transmits the 2nd IP message; According to first-class table, an IP message that adds the MPLS label is transmitted to intermediate node 802;
Egress node 803 also is used to receive the 2nd IP message, sets up the second stream table according to the traffic identifier in the stream extension header of the 2nd IP message, and the second stream table comprises at least: the traffic identifier and second outbound port number; According to the traffic identifier and the second stream table, transmit an IP message.
Wherein, the 2nd IP message is an IP operation management maintain OAM message, also carries service quality QoS parameter in the stream extension header of IP OAM message, is used to consult qos parameter or carries out qos statistic.
Present embodiment receives an IP message by Ingress node, generate traffic identifier according to an IP message, traffic identifier is converted to corresponding M PLS label, an IP message that adds the MPLS label is transmitted to intermediate node, intermediate node is transmitted to Egress node with an IP message that adds the MPLS label, Egress node is converted to corresponding traffic identifier with the MPLS label, and according to traffic identifier, transmit an IP message, realized a kind of stream switching technology that only needs Ingress node to support the traffic identifier generation, the Hash stream switching technology of tabling look-up for example, avoided subsequent node is carried out hardware modification, thereby reduced the complexity and the lower deployment cost of subsequent node, helped the promotion and application of the stream switching technology of tabling look-up based on Hash.
All or part of content in the technical scheme that above embodiment provides can realize that its software program is stored in the storage medium that can read by software programming, storage medium for example: the hard disk in the computer, CD or floppy disk.
The above only is preferred embodiment of the present invention, and is in order to restriction the present invention, within the spirit and principles in the present invention not all, any modification of being done, is equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (15)
1. the method transmitted of a message is characterized in that described method comprises:
Ingress node receives the first Internet protocol IP message;
Described Ingress node generates traffic identifier according to a described IP message;
Described Ingress node is converted to corresponding multiprotocol label switching MPLS label with described traffic identifier;
Described Ingress node sends to intermediate node with a described IP message that adds described MPLS label;
Described intermediate node is transmitted to Egress node with a described IP message of the described MPLS label of described interpolation;
Described Egress node is converted to corresponding traffic identifier with described MPLS label, and according to described traffic identifier, transmits a described IP message.
2. the method for claim 1 is characterized in that, described Ingress node is converted to corresponding multiprotocol label switching MPLS label with described traffic identifier and comprises:
Described Ingress node with described traffic identifier as described MPLS label;
Perhaps, described Ingress node is converted to corresponding described MPLS label according to the mapping relations of traffic identifier and MPLS label with described traffic identifier;
Described Egress node is converted to corresponding traffic identifier with described MPLS label and comprises:
Described Egress node with described MPLS label as described traffic identifier;
Perhaps, described Egress node is converted to corresponding described traffic identifier according to the mapping relations of traffic identifier and MPLS label with described MPLS.
3. the method for claim 1 is characterized in that, described Ingress node comprises before generating traffic identifier according to a described IP message:
Described Ingress node receives the 2nd IP message;
Described Ingress node generates described traffic identifier according to described the 2nd IP message, and sets up first-class table according to described traffic identifier, and described first-class table comprises at least: the described traffic identifier and first outbound port number;
Described Ingress node is arranged on described traffic identifier in the stream extension header of described the 2nd IP message, described Ingress node is transmitted described the 2nd IP message, make the Egress node that receives described the 2nd IP message set up the second stream table according to described traffic identifier, the described second stream table comprises at least: the described traffic identifier and second outbound port number.
4. method as claimed in claim 3 is characterized in that, described Ingress node is transmitted to intermediate node with a described IP message that adds described MPLS label and comprises:
Described Ingress node sends to intermediate node according to described first-class table with a described IP message that adds described MPLS label;
Described Egress node is converted to corresponding traffic identifier with described MPLS label, and according to described traffic identifier, transmits a described IP message and comprise:
Described Egress node is converted to corresponding traffic identifier with described MPLS label, and according to described traffic identifier and the described second stream table, transmits a described IP message.
5. method as claimed in claim 3 is characterized in that, described the 2nd IP message is an IP operation management maintain OAM message, also carries service quality QoS parameter in the stream extension header of described IP OAM message, is used to consult qos parameter or carries out qos statistic.
6. an Ingress node is characterized in that, described Ingress node comprises:
First receiver module is used to receive the first Internet protocol IP message;
Generation module, an IP message that is used for receiving according to described first receiver module generates traffic identifier;
Modular converter is used for the traffic identifier that described generation module generates is converted to corresponding multiprotocol label switching MPLS label;
First sending module, a described IP message that is used for adding the MPLS label that described modular converter obtains sends to intermediate node, makes described intermediate node that a described IP message of the described MPLS label of described interpolation is transmitted to Egress node.
7. Ingress node as claimed in claim 6 is characterized in that, described modular converter comprises: first converting unit or second converting unit;
Described first converting unit is used for described traffic identifier as described MPLS label;
Described second converting unit is used for the mapping relations according to traffic identifier and MPLS label, and described traffic identifier is converted to corresponding described MPLS label.
8. Ingress node as claimed in claim 6 is characterized in that, described first receiver module also is used to receive the 2nd IP message;
Described generation module also is used for generating described traffic identifier according to the 2nd IP message that described first receiver module receives, and sets up first-class table according to described traffic identifier, and described first-class table comprises at least: the described traffic identifier and first outbound port number;
Described first sending module, also be used for described traffic identifier is arranged on the stream extension header of described the 2nd IP message, and transmit described the 2nd IP message, make the Egress node that receives described the 2nd IP message set up the second stream table according to described traffic identifier, the described second stream table comprises at least: the described traffic identifier and second outbound port number;
Described first sending module also is used for according to described first-class table, and a described IP message that adds described MPLS label is sent to intermediate node.
9. Ingress node as claimed in claim 8 is characterized in that, described the 2nd IP message is an IP operation management maintain OAM message, also carries service quality QoS parameter in the stream extension header of described IP OAM message, is used to consult qos parameter or carries out qos statistic.
10. an Egress node is characterized in that, described Egress node comprises:
Second receiver module, be used to receive the first Internet protocol IP message of the interpolation multiprotocol label switching MPLS label that intermediate node transmits, described MPLS label is that Ingress node generates traffic identifier according to a described IP message, and described traffic identifier is converted to;
Second forwarding module is used for described MPLS label is converted to corresponding traffic identifier, and according to described traffic identifier, transmits a described IP message.
11. Egress node as claimed in claim 10 is characterized in that, described second forwarding module comprises: the 3rd converting unit or the 4th converting unit;
Described the 3rd converting unit is used for described MPLS label as described traffic identifier;
Described the 4th converting unit is used for the mapping relations according to traffic identifier and MPLS label, and described MPLS is converted to corresponding described traffic identifier.
12. Egress node as claimed in claim 10 is characterized in that, described second receiver module.Also be used to receive the 2nd IP message, carry described traffic identifier in the stream extension header of described the 2nd IP message from described Ingress node;
Described node also comprises sets up module, is used for setting up the second stream table according to described traffic identifier, and the described second stream table comprises at least: the described traffic identifier and second outbound port number;
Described second forwarding module also is used for transmitting a described IP message according to described traffic identifier and the described second stream table.
13. Egress node as claimed in claim 12 is characterized in that, described the 2nd IP message is an IP operation management maintain OAM message, also carries service quality QoS parameter in the stream extension header of described IP OAM message, is used to consult qos parameter or carries out qos statistic.
14. the system that message is transmitted is characterized in that described system comprises: Ingress node, intermediate node and Egress node;
Described Ingress node, be used to receive the first Internet protocol IP message, generate traffic identifier according to a described IP message, described traffic identifier is converted to corresponding multiprotocol label switching MPLS label, a described IP message that adds described MPLS label is sent to described intermediate node;
Described intermediate node is used for a described IP message of the described MPLS label of described interpolation is transmitted to described Egress node;
Described Egress node is used for described MPLS label is converted to corresponding traffic identifier, and according to described traffic identifier, transmits a described IP message.
15. system as claimed in claim 14, it is characterized in that, described Ingress node, also be used for receiving the 2nd IP message, generate described traffic identifier according to described the 2nd IP message according to before the described IP message generation traffic identifier, and set up first-class table according to described traffic identifier, described first-class table comprises at least: the described traffic identifier and first outbound port number are arranged on described traffic identifier in the stream extension header of described the 2nd IP message, and transmit described the 2nd IP message; According to described first-class table, a described IP message that adds described MPLS label is transmitted to described intermediate node;
Described Egress node also is used to receive described the 2nd IP message, sets up the second stream table according to the traffic identifier in the stream extension header of described the 2nd IP message, and the described second stream table comprises at least: the described traffic identifier and second outbound port number; According to described traffic identifier and the described second stream table, transmit a described IP message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010193414.2A CN102271079B (en) | 2010-06-04 | 2010-06-04 | Message forwarding method, node and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010193414.2A CN102271079B (en) | 2010-06-04 | 2010-06-04 | Message forwarding method, node and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102271079A true CN102271079A (en) | 2011-12-07 |
| CN102271079B CN102271079B (en) | 2014-11-05 |
Family
ID=45053247
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010193414.2A Active CN102271079B (en) | 2010-06-04 | 2010-06-04 | Message forwarding method, node and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102271079B (en) |
Cited By (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102882790A (en) * | 2012-10-12 | 2013-01-16 | 北京锐安科技有限公司 | IPv6 (Internet Protocol version 6) real-time dataflow processing method |
| CN102984064A (en) * | 2012-12-28 | 2013-03-20 | 盛科网络（苏州）有限公司 | Method and system for distinguishing and transmitting elephant flow |
| CN103828310A (en) * | 2013-11-29 | 2014-05-28 | 华为技术有限公司 | Method, system and equipment for finding link |
| CN104486218A (en) * | 2014-12-16 | 2015-04-01 | 上海斐讯数据通信技术有限公司 | MPLS network control system and method based on SDN |
| CN104488235A (en) * | 2013-04-09 | 2015-04-01 | 华为技术有限公司 | Packet forwarding method and network device |
| WO2016015582A1 (en) * | 2014-07-30 | 2016-02-04 | 华为技术有限公司 | Packet transmission method, apparatus and system |
| CN105847042A (en) * | 2016-03-18 | 2016-08-10 | 广州市苏瑞计算机科技有限公司 | Communication system configuration method and device |
| WO2016150020A1 (en) * | 2015-03-20 | 2016-09-29 | 中兴通讯股份有限公司 | Scheduling flow identifier-based packet scheduling method and device |
| CN106330704A (en) * | 2015-06-26 | 2017-01-11 | 杭州华三通信技术有限公司 | Message forwarding method and apparatus |
| WO2017088190A1 (en) * | 2015-11-27 | 2017-06-01 | 华为技术有限公司 | Method and apparatus for acquiring path information |
| WO2017088780A1 (en) * | 2015-11-27 | 2017-06-01 | 新华三技术有限公司 | Software-defined-networking table-entry generation and packet forwarding |
| CN107423154A (en) * | 2017-07-26 | 2017-12-01 | 郑州云海信息技术有限公司 | A kind of flow table processing method and processing device |
| CN107682384A (en) * | 2016-08-01 | 2018-02-09 | 中兴通讯股份有限公司 | Virtual desktop multicast control method, terminal, proxy terminal and cloud desktop server |
| WO2018107757A1 (en) * | 2016-12-16 | 2018-06-21 | 华为技术有限公司 | Method for controlling network transmission and related apparatus |
| CN110392395A (en) * | 2018-04-23 | 2019-10-29 | 华为技术有限公司 | It sends the method for message and sends the device of message |
| CN111385212A (en) * | 2018-12-29 | 2020-07-07 | 华为技术有限公司 | Data transmission technology and neural network system |
| CN111614564A (en) * | 2019-02-22 | 2020-09-01 | 瞻博网络公司 | Internet protocol operation and management options |
| WO2020199863A1 (en) * | 2019-04-04 | 2020-10-08 | 华为技术有限公司 | Message processing method and network device |
| CN112368980A (en) * | 2018-07-13 | 2021-02-12 | 华为技术有限公司 | MPLS extension header for on-network traffic |
| CN113904950A (en) * | 2021-12-06 | 2022-01-07 | 广东睿江云计算股份有限公司 | Stream-based network monitoring method and device, computer equipment and storage medium |
| US11909650B2 (en) | 2019-02-22 | 2024-02-20 | Juniper Networks, Inc. | Internet protocol operations and management option |
| US12034636B2 (en) | 2019-04-04 | 2024-07-09 | Huawei Technologies Co., Ltd. | Packet processing method and network apparatus |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1412985A (en) * | 2001-06-21 | 2003-04-23 | Sk电信股份有限公司 | Route determining method for multi-agreement label conversion network |
| WO2005122493A1 (en) * | 2004-06-07 | 2005-12-22 | Huawei Technologies Co., Ltd. | A method for realizing route transmitting in the network |
| US20070076732A1 (en) * | 2005-09-14 | 2007-04-05 | Jin-Hyoung Kim | Multi-protocol label switching (MPLS) network and method of applying a mobile Internet protocol (IP) to MPLS network |
| CN1949779A (en) * | 2005-10-12 | 2007-04-18 | 丛林网络公司 | Checking for spoofed labels within a label switching computer network |
-
2010
- 2010-06-04 CN CN201010193414.2A patent/CN102271079B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1412985A (en) * | 2001-06-21 | 2003-04-23 | Sk电信股份有限公司 | Route determining method for multi-agreement label conversion network |
| WO2005122493A1 (en) * | 2004-06-07 | 2005-12-22 | Huawei Technologies Co., Ltd. | A method for realizing route transmitting in the network |
| US20070076732A1 (en) * | 2005-09-14 | 2007-04-05 | Jin-Hyoung Kim | Multi-protocol label switching (MPLS) network and method of applying a mobile Internet protocol (IP) to MPLS network |
| CN1949779A (en) * | 2005-10-12 | 2007-04-18 | 丛林网络公司 | Checking for spoofed labels within a label switching computer network |
Cited By (35)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102882790A (en) * | 2012-10-12 | 2013-01-16 | 北京锐安科技有限公司 | IPv6 (Internet Protocol version 6) real-time dataflow processing method |
| CN102984064A (en) * | 2012-12-28 | 2013-03-20 | 盛科网络（苏州）有限公司 | Method and system for distinguishing and transmitting elephant flow |
| CN104488235A (en) * | 2013-04-09 | 2015-04-01 | 华为技术有限公司 | Packet forwarding method and network device |
| CN104488235B (en) * | 2013-04-09 | 2017-08-04 | 华为技术有限公司 | Message forwarding method and the network equipment |
| CN103828310A (en) * | 2013-11-29 | 2014-05-28 | 华为技术有限公司 | Method, system and equipment for finding link |
| WO2015078008A1 (en) * | 2013-11-29 | 2015-06-04 | 华为技术有限公司 | Link discovery method, system and device |
| US10374935B2 (en) | 2013-11-29 | 2019-08-06 | Huawei Technologies Co., Ltd. | Link discovery method, system, and device |
| CN103828310B (en) * | 2013-11-29 | 2017-06-06 | 华为技术有限公司 | A kind of method of link discovery, system and equipment |
| US10333835B2 (en) | 2014-07-30 | 2019-06-25 | Huawei Technologies Co., Ltd. | Packet transmission method, apparatus, and system |
| WO2016015582A1 (en) * | 2014-07-30 | 2016-02-04 | 华为技术有限公司 | Packet transmission method, apparatus and system |
| CN104486218A (en) * | 2014-12-16 | 2015-04-01 | 上海斐讯数据通信技术有限公司 | MPLS network control system and method based on SDN |
| WO2016150020A1 (en) * | 2015-03-20 | 2016-09-29 | 中兴通讯股份有限公司 | Scheduling flow identifier-based packet scheduling method and device |
| CN106330704B (en) * | 2015-06-26 | 2019-12-06 | 新华三技术有限公司 | Message forwarding method and device |
| CN106330704A (en) * | 2015-06-26 | 2017-01-11 | 杭州华三通信技术有限公司 | Message forwarding method and apparatus |
| WO2017088190A1 (en) * | 2015-11-27 | 2017-06-01 | 华为技术有限公司 | Method and apparatus for acquiring path information |
| US10833988B2 (en) | 2015-11-27 | 2020-11-10 | New H3C Technologies Co., Ltd. | Generating table entry and forwarding packet in software defined network |
| WO2017088780A1 (en) * | 2015-11-27 | 2017-06-01 | 新华三技术有限公司 | Software-defined-networking table-entry generation and packet forwarding |
| US10554536B2 (en) | 2015-11-27 | 2020-02-04 | Huawei Technologies Co., Ltd. | Method for obtaining path information and apparatus |
| CN105847042A (en) * | 2016-03-18 | 2016-08-10 | 广州市苏瑞计算机科技有限公司 | Communication system configuration method and device |
| CN107682384A (en) * | 2016-08-01 | 2018-02-09 | 中兴通讯股份有限公司 | Virtual desktop multicast control method, terminal, proxy terminal and cloud desktop server |
| WO2018107757A1 (en) * | 2016-12-16 | 2018-06-21 | 华为技术有限公司 | Method for controlling network transmission and related apparatus |
| CN107423154A (en) * | 2017-07-26 | 2017-12-01 | 郑州云海信息技术有限公司 | A kind of flow table processing method and processing device |
| CN110392395B (en) * | 2018-04-23 | 2022-03-29 | 华为技术有限公司 | Method and device for sending message |
| CN110392395A (en) * | 2018-04-23 | 2019-10-29 | 华为技术有限公司 | It sends the method for message and sends the device of message |
| US11190979B2 (en) | 2018-04-23 | 2021-11-30 | Huawei Technologies Co., Ltd. | Methods and apparatus for forwarding packets between child nodes and parent nodes |
| CN112368980B (en) * | 2018-07-13 | 2022-03-01 | 华为技术有限公司 | Method for adding one or more network services to an MPLS network |
| CN112368980A (en) * | 2018-07-13 | 2021-02-12 | 华为技术有限公司 | MPLS extension header for on-network traffic |
| US11582148B2 (en) | 2018-07-13 | 2023-02-14 | Huawei Technologies Co., Ltd. | MPLS extension headers for in-network services |
| CN111385212A (en) * | 2018-12-29 | 2020-07-07 | 华为技术有限公司 | Data transmission technology and neural network system |
| CN111614564A (en) * | 2019-02-22 | 2020-09-01 | 瞻博网络公司 | Internet protocol operation and management options |
| US11909650B2 (en) | 2019-02-22 | 2024-02-20 | Juniper Networks, Inc. | Internet protocol operations and management option |
| WO2020199863A1 (en) * | 2019-04-04 | 2020-10-08 | 华为技术有限公司 | Message processing method and network device |
| US12034636B2 (en) | 2019-04-04 | 2024-07-09 | Huawei Technologies Co., Ltd. | Packet processing method and network apparatus |
| CN113904950A (en) * | 2021-12-06 | 2022-01-07 | 广东睿江云计算股份有限公司 | Stream-based network monitoring method and device, computer equipment and storage medium |
| CN113904950B (en) * | 2021-12-06 | 2022-02-22 | 广东睿江云计算股份有限公司 | Stream-based network monitoring method and device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102271079B (en) | 2014-11-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102271079B (en) | Message forwarding method, node and system | |
| US6408001B1 (en) | Method for determining label assignments for a router | |
| US7903553B2 (en) | Method, apparatus, edge router and system for providing QoS guarantee | |
| EP1401161B1 (en) | Method and network node for having Quality of service (QOS) mechanism in an internet protocol (IP) network | |
| US6735190B1 (en) | Packet transport method device utilizing header removal fields | |
| US8555352B2 (en) | Controlling access nodes with network transport devices within wireless mobile networks | |
| RU2350028C2 (en) | Double-linked reservation of service quality (sq) in mechanism of intrastrip signaling | |
| US20080037425A1 (en) | Control Plane to data plane binding | |
| CN101447919A (en) | Systems and methods for carrier Ethernet using referential tables for forwarding decisions | |
| CN106454414B (en) | A kind of multipath network method for real-time video transmission | |
| US9578281B2 (en) | Managing traffic flow on a network path | |
| US7649896B2 (en) | System using label switching techniques to support QoS for mobile ad-hoc networks and its label distributing and switching method | |
| EP3547690B1 (en) | Real-time video transmission method of multipath network | |
| Rahman et al. | Performance analysis and the study of the behavior of MPLS protocols | |
| US9172638B2 (en) | Global IP-based service-oriented network architecture | |
| JP3688525B2 (en) | Packet flow control method and router apparatus | |
| CN114710975A (en) | Multi-domain transport multi-transport network context identification | |
| Shawl et al. | A Review: Multi Protocol Label Switching (Mpls) | |
| US20180167257A1 (en) | Methods and systems for forming network connections | |
| Volkert et al. | Multipath video streaming based on hierarchical routing management | |
| CN104994331A (en) | Method and system for transmitting flows between networks in low-speed link | |
| Jurca et al. | Distributed media rate allocation in multipath networks | |
| Karsten et al. | On the feasibility of RSVP as general signalling interface | |
| Cabrera-Medina et al. | Video transmission in multicast networks using network coding | |
| M Al-Quzwini et al. | Performance Evaluation of Traffic Engineering Signal Protocols in IPV6 MPLS Networks |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20201110 Address after: 215500 No.13, Caotang Road, Changshu, Suzhou, Jiangsu Province Patentee after: Changshu intellectual property operation center Co.,Ltd. Address before: Unit 2414-2416, main building, no.371, Wushan Road, Tianhe District, Guangzhou City, Guangdong Province Patentee before: GUANGDONG GAOHANG INTELLECTUAL PROPERTY OPERATION Co.,Ltd. Effective date of registration: 20201110 Address after: Unit 2414-2416, main building, no.371, Wushan Road, Tianhe District, Guangzhou City, Guangdong Province Patentee after: GUANGDONG GAOHANG INTELLECTUAL PROPERTY OPERATION Co.,Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd. |
|
| CP02 | Change in the address of a patent holder | ||
| CP02 | Change in the address of a patent holder |
Address after: 215500 5th floor, building 4, 68 Lianfeng Road, Changfu street, Changshu City, Suzhou City, Jiangsu Province Patentee after: Changshu intellectual property operation center Co.,Ltd. Address before: No.13 caodang Road, Changshu City, Suzhou City, Jiangsu Province Patentee before: Changshu intellectual property operation center Co.,Ltd. |