CN102271079B - Message forwarding method, node and system - Google Patents
Message forwarding method, node and system Download PDFInfo
- Publication number
- CN102271079B CN102271079B CN201010193414.2A CN201010193414A CN102271079B CN 102271079 B CN102271079 B CN 102271079B CN 201010193414 A CN201010193414 A CN 201010193414A CN 102271079 B CN102271079 B CN 102271079B
- Authority
- CN
- China
- Prior art keywords
- message
- traffic identifier
- node
- mpls label
- ingress node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
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, particularly a kind of method of message repeating, node and system.
Background technology
The communications field has proposed a kind of stream switching technology at present, stream switching technology is not processed all messages at the 3rd layer, and first message in analysis stream only, after setting up stream table, forward based on layer 3 address, also be this message of routing forwarding, subsequent packet in stream uses one or more shortcuts to carry out flow forwarding, can solve the network bottleneck problem such as low forwarding rate, high time delay that stream cross-network segment causes.
Existing one is based on hash(Hash) the stream switching technology of look up table technique, in this stream switching technology, each node in a network segment all needs to carry out following operation:
According to the five-tuple information of message, also be source address, destination address, source port number, destination slogan, protocol type, hash obtains a shorter keyword, and utilize this keyword as the address of tabling look-up, table look-up and obtain the relevant retransmitting paramater of stream, and according to retransmitting paramater, this message is carried out to flow forwarding.
Realizing in process of the present invention, inventor finds that prior art at least exists following problem:
Each node in the network segment all needs Hash to generate keyword, and hash algorithm needs hardware to realize conventionally, and need to introduce CAM(Content Addressable Memory, Content Addressable Memory), therefore prior art need to be carried out hardware modification to the node of the whole network.
Summary of the invention
For in the time realizing stream switching technology based on Hash look up table technique, to avoid the node of the whole network to carry out hardware modification, the embodiment of the present invention provides a kind of method, node and system of message repeating.Described technical scheme is as follows:
A method for message repeating, 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 traffic identifier is converted to corresponding multiprotocol label switching MPLS label by described Ingress node;
A described IP message that adds described MPLS label is sent to intermediate node by described Ingress node;
Described intermediate node by a described IP message repeating of described described interpolation MPLS label to Egress node;
Described MPLS label is converted to corresponding traffic identifier by described Egress node, and according to described traffic identifier, forward a described IP message;
Wherein, 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 at least comprises: described traffic identifier and outbound port No. the first;
Described Ingress node is arranged on described traffic identifier in the stream extension header of described the 2nd IP message, described Ingress node forwards described the 2nd IP message, make the Egress node that receives described the 2nd IP message set up second table according to described traffic identifier, described second table at least comprises: described traffic identifier and outbound port No. the second.
A kind of Ingress node, described Ingress node comprises:
The first receiver module, for receiving the first Internet protocol IP message;
Generation module, generates traffic identifier for the IP message receiving according to described the first receiver module;
Modular converter, is converted to corresponding multiprotocol label switching MPLS label for the traffic identifier that described generation module is generated;
The first sending module, for a described IP message that adds the MPLS label that obtains of described modular converter is sent to intermediate node, make described intermediate node by a described IP message repeating of described described interpolation MPLS label to Egress node;
Wherein, described the first receiver module, also for receiving the 2nd IP message;
Described generation module, also generates described traffic identifier for the 2nd IP message receiving according to described the first receiver module, and sets up first-class table according to described traffic identifier, and described first-class table at least comprises: described traffic identifier and outbound port No. the first;
Described the first sending module, also for described traffic identifier being arranged on to the stream extension header of described the 2nd IP message, and forward described the 2nd IP message, make the Egress node that receives described the 2nd IP message set up second table according to described traffic identifier, described second table at least comprises: described traffic identifier and outbound port No. the second;
Described the first sending module, also, for according to described first-class table, sends to intermediate node by a described IP message that adds described MPLS label.
A kind of Egress node, described Egress node comprises:
The second receiver module, be used for the first Internet protocol IP message of the interpolation multiprotocol label switching MPLS label that receives intermediate node forwarding, described MPLS label is that Ingress node generates traffic identifier according to a described IP message, and described traffic identifier is converted to;
The second forwarding module, for described MPLS label is converted to corresponding traffic identifier, and according to described traffic identifier, forwards a described IP message;
Wherein, described the second receiver module, also, for receiving the 2nd IP message from described Ingress node, carries described traffic identifier in the stream extension header of described the 2nd IP message;
Described node also comprises sets up module, and for setting up second table according to described traffic identifier, described second table at least comprises: described traffic identifier and outbound port No. the second;
Described the second forwarding module, also, for according to described traffic identifier and described second table, forwards a described IP message.
A system for message repeating, described system comprises: Ingress node, intermediate node and Egress node;
Described Ingress node, be used for receiving 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, for giving described Egress node by a described IP message repeating of described described interpolation MPLS label;
Described Egress node, for described MPLS label is converted to corresponding traffic identifier, and according to described traffic identifier, forwards a described IP message;
Wherein, described Ingress node, also for before generating traffic identifier according to a described IP message, receive the 2nd IP message, generate described traffic identifier according to described the 2nd IP message, and set up first-class table according to described traffic identifier, described first-class table at least comprises: described traffic identifier and outbound port No. the first, described traffic identifier is arranged in the stream extension header of described the 2nd IP message, and forwards described the 2nd IP message; According to described first-class table, give described intermediate node by a described IP message repeating of the described MPLS label of interpolation;
Described Egress node, also, for receiving described the 2nd IP message, sets up second table according to the traffic identifier in the stream extension header of described the 2nd IP message, and described second table at least comprises: described traffic identifier and outbound port No. the second; According to described traffic identifier and described second table, forward a described IP message.
The beneficial effect that the technical scheme that the embodiment of the present 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 MPLS label, an IP message that adds MPLS label is sent to intermediate node, intermediate node by an IP message repeating that adds MPLS label to Egress node, MPLS label is converted to corresponding traffic identifier by Egress node, and according to traffic identifier, forward an IP message, realize a kind of Ingress node that only needs and supported the stream switching technology that traffic identifier generates, the stream switching technology that for example Hash is tabled look-up, avoid subsequent node to carry out hardware modification, thereby complexity and the lower deployment cost of subsequent node are reduced, the promotion and application of the stream switching technology that is conducive to table look-up based on Hash.
Brief description of the drawings
Fig. 1 is the method flow diagram of the message repeating that provides of the embodiment of the present invention;
Fig. 2 is the network architecture schematic diagram of the message repeating that provides of the embodiment of the present invention;
Fig. 3 is the information interaction figure that the stream table that provides of the embodiment of the present invention is set up;
Fig. 4 is that the band that the embodiment of the present 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 present invention;
Fig. 6 is the information interaction figure of the message repeating that provides of the embodiment of the present invention;
Fig. 7 is that the IP OAM message that the embodiment of the present invention provides creates flow forwarding path, consults the also interaction figure of statistical quality of service;
Fig. 8 a is the structural representation of the Ingress node that provides of the embodiment of the present invention;
Fig. 8 b is another structural representation of the Ingress node that provides of the embodiment of the present invention;
Fig. 9 a is the structural representation of the Egress node that provides of the embodiment of the present invention;
Fig. 9 b is another structural representation of the Egress node that provides of the embodiment of the present invention;
Figure 10 is the system schematic of the message repeating that provides of the embodiment of the present invention.
Embodiment
For making the object, technical solutions and advantages of the present invention clearer, below in conjunction with accompanying drawing, embodiment of the present invention is described further in detail.
Referring to Fig. 1, the present embodiment provides a kind of method of message repeating, comprising:
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 at least comprises: traffic identifier and outbound port No. the first, traffic identifier is arranged in the stream extension header of the 2nd IP message, and forward the 2nd IP message, and make the Egress node that receives the 2nd IP message set up second table according to traffic identifier, second table at least comprises: traffic identifier and outbound port No. the second.
103: traffic identifier is converted to corresponding MPLS(Multiprotocol Label Switching, multiprotocol label switching by Ingress node) label;
104: an IP message that adds MPLS label is sent to intermediate node by Ingress node;
105: intermediate node by an IP message repeating that adds MPLS label to Egress node;
106: MPLS label is converted to corresponding traffic identifier by Egress node, and according to traffic identifier, forward an IP message.
The present embodiment receives an IP message by Ingress node, generate traffic identifier according to an IP message, traffic identifier is converted to corresponding MPLS label, an IP message that adds MPLS label is sent to intermediate node, intermediate node by an IP message repeating that adds MPLS label to Egress node, MPLS label is converted to corresponding traffic identifier by Egress node, and according to traffic identifier, forward an IP message, realize a kind of Ingress node that only needs and supported the stream switching technology that traffic identifier generates, the stream switching technology that for example Hash is tabled look-up, avoid subsequent node to carry out hardware modification, thereby complexity and the lower deployment cost of subsequent node are reduced, the promotion and application of the stream switching technology that is conducive to table look-up based on Hash.
The present embodiment provides a kind of method of message repeating, introduces in detail below in conjunction with the network architecture shown in Fig. 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, the fringe node that Ingress node PE1 and Egress node PE2 are this network.
Before turning transmitting IP packet, Ingress node, Egress node need to be set up respectively first-class table and second table according to IP message, and intermediate node need not be set up stream table.Introduce in detail the process of setting up stream table before transmitting IP packet that turns below.Referring to Fig. 3, detailed process is as follows:
301: sending direction Ingress node sends IP message;
Wherein, this IP message is the 2nd IP message, and conventionally Ingress node first receives the 2nd IP message, then receives an IP message, between step 301-307 by the 2nd IP message referred to as IP message.
Further, transmit leg judges whether this IP message needs to carry out flow forwarding, if needed, for example, this IP message is the Audio/Video Streaming that occupied bandwidth is large, the duration is long (or title " elephant stream "), in this IP message, carries stream extension header, now, flow prolate-headed Flow ID(traffic identifier) can be sky, transmit leg is without being hash.
Wherein, IP message can be specifically IPv4(Internet Protocol Version4, Internet protocol the 4th version) or IPv6(Internet Protocol Version6, Internet protocol the 6th version).
Fig. 4 is that a band flows prolate-headed IPv6 message schematic diagram, and the Next Header territory follow-up IPv6 extension header carrying of statement is for carrying stream relevant information.Stream extension header can adopt new extension header, or utilizes existing " Hop-by-Hop Options Header " to carry stream relevant information, and message can check and process the information of its carrying through the each node on path.Fig. 5 is the stream extension header schematic diagram of IPv6.Wherein,
Next head of Next Header() for showing that IPv6 extension header protocol type is Flow(stream);
Hdr Ext Len(extension header length) for showing the prolate-headed length of IPv6;
Flow ID(traffic identifier) for carrying Ingress node according to the keyword of IP message information Hash generation, can exceed 20, Fig. 4 is only schematic diagram;
M(forwards mark) adopt MPLS(Multiprotocol Label Switching, multiprotocol label switching for being shown to be) label forwards, and still adopts Flow ID to forward;
RSV(reserved place) be used to expanded function in the future reserved;
Flow QoS parameter(streaming quality parameter) optional, for carrying the stream qos parameter relevant to flow ID, as loss ratio (packet loss), BW(Bandwidth, bandwidth);
Sequence Number(sequence number) optional, for coordinating the loss ratio that statistic fluid is relevant;
Hash parameter(Hash parameter) optional, generate flow ID corresponding Source IP(source address for carrying), Flow label(stream label) etc. IP message information.
In addition, for IPv4, can in IPv4 heading, expand a Flow Option(stream option), except there is no Next Header, outside Hdr Ext Len parameter, other parameters, with the stream extension header of IPv6, repeat no more here.
302: Ingress node receives this IP message, if this IP message need to carry out flow forwarding, create the stream table that this IP message of this node is corresponding (first-class table);
Wherein, Ingress node judges whether to carry out flow forwarding and specifically comprises: whether carry stream extension header according to this IP message, judge that this IP message need to carry out flow forwarding.If carry stream extension header, need to carry out flow forwarding, if do not carry stream extension header, do not need to carry out flow forwarding.
Wherein, stream table constructive process is specially: Ingress node generates corresponding keyword according to IP message information hash, it is this keyword that Flow ID is set, then look into outbound port No. the first that this node route list can obtain this IP message, a record using Flow ID and corresponding the first outbound port thereof number as this node-flow table.
Wherein, Ingress node generates the Flow ID of this IP message according to IP message information hash, at least can realize by following three kinds of methods, comprising:
According to the Source IP(source address of IP message), Flow label is hash and obtains keyword, sets it as Flow ID, establishes source address=a, Flow label(stream label in the present embodiment)=b, and establish Flow ID=12345.Accordingly, algorithm can be expressed as Flow ID=hash algorithm { Source IP, Flow label}.
Or, according to the source address of IP message, Destination IP(destination address) and Flow label be hash and obtain keyword, set it as Flow ID.Accordingly, algorithm can be expressed as Flow ID=hash algorithm { Source IP, Destination IP, Flow label}.
Or, according to the source address of this IP message, destination address, Source port(source port number), Destination port(destination slogan) and Protocol type(protocol type) obtain keyword as hash, set 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, establishing the first outbound port number that Ingress node Flow ID=12345 is corresponding is 1, and Ingress node is set up first-class table referring to table 1.
Table 1
| Flow?ID | Outbound port No. the first |
| 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, also can first carry out 303 and carry out 302 again.
304: Ingress node, by prolate-headed the stream that carries Flow ID=12345 IP message, sends to subsequent node by the outbound port route finding;
Wherein, subsequent node can be intermediate node, also can be Egress node, also be that Ingress node can directly send to Egress node by IP message, also can be transmitted to Egress node by intermediate node, in two kinds of modes, Ingress node and Egress node are to the processing of IP message without essential difference, and therefore follow-up the present embodiment describes taking subsequent node as intermediate 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 the present embodiment illustrates as an example of an intermediate node example, and the process that each intermediate node is built stream table to this IP message is identical, and difference is only the object difference that IP message routing forwards.
306: Egress node creates the stream table that this IP message of this node is corresponding (second table);
Concrete, outbound port No. the second of this IP message that Egress node obtains the prolate-headed FlowID of IP message flow receiving and Cha Ben node route list, as a record of this node-flow table.
In the present embodiment, establishing the second outbound port that Egress node Flow ID=12345 is corresponding is 3, and Egress node is set up second table, referring to table 2.
Table 2
| Flow?ID | Outbound port No. the second |
| 12345 | 3 |
307: Egress node is deleted after stream extension header, and this IP message of routing forwarding is to recipient.
So far, Ingress node, Egress node have been set up respectively first-class table and the second table of this node.It should be noted that, in this stream table of above-mentioned first-class table and second table, at least need to comprise: 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, avoid subsequent node to carry out hardware modification, thereby reduced complexity and the lower deployment cost of subsequent node, the promotion and application of the stream switching technology that is conducive to table look-up based on Hash, even if traffic identifier is longer on the other hand, for example exceed 20, also can realize with extension header, and can realize QoS(Quality of Service, service quality) negotiation and statistics etc.
Further, Ingress node and Egress node can also adopt additive method to set up stream table, and the 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 generating.
After the process of the stream table based on above-mentioned foundation, according to the stream table of setting up, the process of carrying out message repeating refers to Fig. 6, and its handling process is as follows:
401: sending direction Ingress node sends IP message;
Wherein, this IP message is an IP message, is generally and sets up the IP message receiving after stream table, is called for short IP message between step 401-407.
402: Ingress node receives this IP message, if need flow forwarding, generate the Flow ID of this IP message according to IP message information;
403: Flow ID is converted to MPLS label by Ingress node;
Ingress node specifically has two kinds of conversion methods:
One is, directly using Flow ID as MPLS label.In the method stream table, can there is no MPLS tag entry, saved memory.
Another kind is, according to the mapping relations of default Flow ID and MPLS label, Flow ID to be converted to corresponding MPLS label.
Wherein, MPLS label can be LSP(Label Switched Path, label switched path) label, PW(Pseudo Wires, pseudo-line) label or Flow label(stream label), corresponding, MPLS passage is lsp tunnel, PW passage or circulation road.If Flow ID exceedes 20, can adopt the form of MPLS label stack to support by multistage label.
404: Ingress node sends the IP message that adds MPLS label;
Concrete, Ingress node is looked into the first-class table of this node according to Flow ID and is obtained its outbound port No. the first, and flow forwarding adds the IP message of MPLS label=12345.
405: intermediate node carries out MPLS exchange according to MPLS label, by IP message repeating to Egress node;
Also, intermediate node is given other intermediate nodes and Egress node by MPLS passage corresponding to MPLS label by this IP message repeating.Wherein, each intermediate node, in the time carrying out MPLS exchange, does not need perception stream.
406: MPLS label is converted to Flow ID by Egress node;
Egress node specifically have two kinds with the corresponding conversion method of Ingress node, one is directly using MPLS label as Flow ID, another kind is according to the mapping relations of default Flow ID and MPLS label, and MPLS label is converted to corresponding Flow ID.
407: Egress node is looked into this node-flow table (second table) according to Flow ID and obtained its second outbound port, by the second outbound port number finding, the IP message flow of Flow ID=12345 is transmitted to recipient.
In the present embodiment, establishing the second outbound port number that Egress node Flow ID=12345 is corresponding is 3.
The method of above-mentioned message repeating, only need Ingress node to support the stream switching technology that traffic identifier generates, the stream switching technology that for example Hash is tabled look-up, avoid subsequent node to carry out hardware modification, thereby complexity and the lower deployment cost of subsequent node are reduced, the promotion and application of the stream switching technology that is conducive to table look-up based on Hash.And, intermediate node does not participate in flow forwarding, only do MPLS exchange, the subsequent packet flowing so just can be from Ingress node by offload(bypass) to the MPLS network of new suitable efficient this stream of forwarding, alleviate the burden of the Traditional IP route network that flow forwarding efficiency is extremely low.In addition, stream table can be transmitted software upgrading by original MPLS and realize, and the MPLS network that can utilize operator to dispose is realized the MPLS knowing based on influenza and forwarded, and has effectively protected the investment of operator to existing network.
Further, in step 301-307 stream table process of establishing, before step 305, intermediate node also can be set up stream table according to the traffic identifier in IP message flow extension header.Accordingly, the present embodiment also provides a kind of method of message repeating, 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 stream extension header, and according to the stream table of this traffic identifier and above-mentioned foundation, forward this IP message.This retransmission method only needs Ingress node to support the stream switching technology that traffic identifier generates, the stream switching technology that for example Hash is tabled look-up, avoid subsequent node to carry out hardware modification, thereby complexity and the lower deployment cost of subsequent node are reduced, the promotion and application of the stream switching technology that is conducive to table look-up based on Hash.
Further, in stream table process of establishing, the 2nd IP message can be specifically IP OAM(Operation Administration and Maintenance, operational administrative and maintenance) message, this IP OAM message except can for create flow forwarding path, can also be used for consulting QoS(Quality of Service, service quality) parameter is so that resource reservation, and the qos statistic flowing etc., below taking agreed bandwidth, statistics loss ratio(packet loss) describe as example, 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, or LDP(Label Distribution Protocol, tag distribution protocol)/RSVP(Resource Reservation Protocol, RSVP) message, or IP OAM message can also be the IP OAM message that IP datagram Wen Suilu carries.Because the agreements such as LDP/RSVP are based on Session(session), flow thinner than the granularity of Session, set up flow forwarding path if still adopt LDP/RSVP agreement, the extensibility of network will be a serious challenge, the foundation that utilizes IP OAM message to carry out 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(streaming quality parameter), Sequence Number(sequence number), Hash parameter(Hash parameter) etc.; These parameters can be carried in IP OAM message flow extension header.
Wherein, the present embodiment does not limit the particular content of stream qos parameter, and the present embodiment describes as an example of bandwidth example, establishes the desired BW(Band Width of stream herein, bandwidth)=2Mbps.
In addition, now flow prolate-headed Flow ID and can be sky, transmit leg is without being hash.
502: Ingress node PE1 generates the Flow ID of IP OAM message, and create the respective record of stream table;
Concrete, according to IP OAM message information, hash generates corresponding keyword, it is this keyword that Flow ID is set, and then looks into this node route list and can obtain the outbound port number of this IP OAM message, a record using Flow ID and corresponding outbound port thereof number as this node-flow table.
, establish according to source address=a herein, Flow label=b, hash obtains Flow ID=12345, and establishing its outbound port number is 1.
503: Ingress node carries out CAC(Call Admission Control according to stream qos parameter, session is received and is controlled), the result of establishing CAC is herein the bandwidth that Ingress node can only provide stream BW=1Mbps;
Wherein, stream qos parameter can flow extension header by transmit leg and obtain, or pre-configured in Ingress node, or obtains by inquiry associated server.
But the stream qos parameter item that now Flow ID is corresponding is empty, needs waiting step 511 resource reservation results.
504: Ingress node forwards IP OAM message, carries parameter F low ID=12345 and self CAC result BW=1Mbps, and destination is Egress node (or recipient);
505a: intermediate node P receives IP OAM message, carries out CAC according to stream qos parameter, and establishing CAC result is herein the bandwidth that intermediate node can only provide stream BW=500Kbps;
505b: intermediate node, according to the prolate-headed Flow ID of IP OAM message flow, creates the respective record of stream table;
Concrete, intermediate node obtains the prolate-headed Flow ID of IP OAM message flow receiving and Cha Ben node route list the outbound port number of this IP message, and establishing its outbound port number is 2, as a record of this node-flow table.
But the QoS item that now Flow ID is corresponding is empty, needs waiting step 514 resource reservation results;
506: intermediate node forwards IP OAM message, carries parameter F low ID=12345 and self CAC result BW=500Kbps;
507a: Egress node PE2 receives IP OAM message, carries out CAC according to stream qos parameter, and establishing CAC result is herein the bandwidth that Egress node can only provide stream BW=250Kbps;
507b: Egress node, according to the prolate-headed Flow ID of IP OAM message flow, creates the respective record of stream table;
Concrete, Egress node obtains prolate-headed the IP message flow receiving Flow ID and Cha Ben node route list the outbound port number of this IP message, and establishing its outbound port number is 3, as a record of this node-flow table.
But the QoS item that now Flow ID is corresponding is empty, needs waiting step 517 resource reservation results;
508: Egress node forwards IP OAM message to recipient, carries parameter F low ID=12345 and self CRC result BW=250Kbps;
509: recipient receives IP OAM message, know that self can only receive the stream of BW=200Kbps, and count the loss ratio(packet loss of a period of time);
Concrete, loss ratio statistical method comprises: to the sequence number(sequence number of the stream packet receiving) detect, sequence number difference by the message amount receiving in a period of time divided by first stream packet and an end stream packet, the business who obtains is the loss ratio in this time period.The present embodiment is established loss ratio(recipient)=99%.
510: recipient replys IP OAM message, carry 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, the stream qos parameter that Flow ID=12345 is corresponding refreshes as 200Kps;
512: Egress node counts the loss ratio of a period of time, and refreshes stream table, fills in the packet loss that Flow ID=12345 is corresponding, and the present embodiment is made as 99%;
Wherein, loss ratio statistical method is identical with step 509, repeats no more here.
Now, 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 forwards 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, the qos parameter that Flow ID=12345 is corresponding refreshes as 200Kps;
515: intermediate node counts the loss ratio of a period of time, and refreshes stream table, fills in the packet loss that Flow ID=12345 is corresponding, and the present embodiment is made as 99%;
Wherein, loss ratio statistical method is identical with step 509, repeats no more here.
Now, 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 forwards 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, the qos parameter that Flow ID=12345 is corresponding refreshes as 200Kps;
518: Ingress node counts the loss ratio of a period of time, and refreshes stream table, fills in the packet loss that Flow ID=12345 is corresponding, and the present embodiment is made as loss ratio(PE1)=100%;
Now, 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 forwards IP OAM message to transmit leg, carries parameter: source address=a, Flow label=b, BW=200Kbps, loss ratio(PE1)=100%, loss ratio(P)=99%, loss ratio(PE2)=99%loss ratio(recipient)=99%;
Wherein, Ingress node need be converted to Flow ID source address and Flow label, because conventionally only have the just corresponding hash algorithm of unified configuration of carrier network devices, 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: transmit leg receives after IP OAM message, determine adjust the speed of stream transmission or no longer support this stream according to BW=200Kbps;
Meanwhile, transmit leg can be according to loss ratio(PE1)=100%, loss ratio(P)=99%, loss ratio(PE2)=99%, loss ratio(recipient)=99%, judge network P node and occur that packet loss appears in packet loss instead of 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 network failure point, and this routine network failure point appears between PE1 to P node and (comprises P node).
The method that the present embodiment provides, subsequent node does not need to carry out Hash calculation on the one hand, avoid subsequent node to carry out hardware modification, thereby reduced complexity and the lower deployment cost of subsequent node, the promotion and application of the stream switching technology that is conducive to table look-up based on Hash; The stream relevant parameter of simultaneously can also holding consultation, so that resource reservation, flows the statistics of relevant parameter, ensures the service quality of stream, has made up existing IP network and do not possess QoS and ensure the shortcoming of ability; In addition, corresponding common OAM message, the OAM message that the present embodiment provides, can carry out based on IP layer negotiation and the statistics of QoS.
Referring to Fig. 8 a, the present embodiment provides a kind of Ingress node, comprising:
The first receiver module 601, for receiving an IP message;
Generation module 602, generates traffic identifier for the IP message receiving according to the first receiver module 601;
Modular converter 603, is converted to corresponding MPLS label for the traffic identifier that generation module 602 is generated;
The first sending module 604, for an IP message that adds the MPLS label that obtains of modular converter 603 is sent to intermediate node, make intermediate node by an IP message repeating that adds MPLS label 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, for using traffic identifier as MPLS label;
The second converting unit 603b, for according to the mapping relations of traffic identifier and MPLS label, is converted to corresponding MPLS label by traffic identifier.
Wherein, the first receiver module 601, also for receiving the 2nd IP message;
Generation module 602, also generates traffic identifier for the 2nd IP message receiving according to the first receiver module 601, and sets up first-class table according to traffic identifier, and first-class table at least comprises: traffic identifier and outbound port No. the first;
The first sending module 604, also for traffic identifier being arranged on to the stream extension header of the 2nd IP message, and forward the 2nd IP message, and make the Egress node that receives the 2nd IP message set up second table according to traffic identifier, second table at least comprises: traffic identifier and outbound port No. the second.
Wherein, the first sending module 604, also, for according to first-class table, sends to intermediate node by an IP message that adds MPLS label.
Wherein, the 2nd IP message is IP operation management maintain OAM message, in the stream extension header of IP OAM message, also carries service quality QoS parameter, for consulting qos parameter or carrying out qos statistic.
The Ingress node that the present embodiment provides, by receiving an IP message, generate traffic identifier according to an IP message, traffic identifier is converted to corresponding MPLS label, an IP message that adds MPLS label is sent to intermediate node, make intermediate node by an IP message repeating that adds MPLS label to Egress node, realize a kind of Ingress node that only needs and supported the stream switching technology that traffic identifier generates, the stream switching technology that for example Hash is tabled look-up, avoid subsequent node to carry out hardware modification, thereby complexity and the lower deployment cost of subsequent node are reduced, the promotion and application of the stream switching technology that is conducive to table look-up based on Hash.
Referring to Fig. 9 a, the present embodiment provides a kind of Egress node, comprising:
The second receiver module 701, the first Internet protocol IP message of interpolation multiprotocol label switching MPLS label forwarding for receiving intermediate node, MPLS label is that Ingress node generates traffic identifier according to an IP message, and traffic identifier is converted to;
The second forwarding module 702, for MPLS label is converted to corresponding traffic identifier, and according to traffic identifier, forwards an IP message.
Referring to Fig. 9 b, the second forwarding module 702 comprises: the 3rd converting unit 702a or the 4th converting unit 702b;
The 3rd converting unit 702a, for using MPLS label as traffic identifier;
The 4th converting unit 702b, for according to the mapping relations of traffic identifier and MPLS label, is converted to corresponding traffic identifier by MPLS.
Wherein, the second receiver module 701.Also, for receiving the 2nd IP message from Ingress node, in the stream extension header of the 2nd IP message, carry traffic identifier;
Egress node also comprises sets up module, and for set up second table according to traffic identifier, second table at least comprises: traffic identifier and outbound port No. the second.
Wherein, the second forwarding module 702, also, for according to traffic identifier and second table, forwards an IP message.
Wherein, the 2nd IP message is IP operation management maintain OAM message, in the stream extension header of IP OAM message, also carries service quality QoS parameter, for consulting qos parameter or carrying out qos statistic.
The Egress node that the present embodiment provides, the one IP message of the interpolation MPLS label forwarding by reception intermediate node, MPLS label is that Ingress node generates traffic identifier according to an IP message, and traffic identifier is converted to, MPLS label is converted to corresponding traffic identifier by Egress node, and according to traffic identifier, forward an IP message, realize a kind of Ingress node that only needs and supported the stream switching technology that traffic identifier generates, the stream switching technology that for example Hash is tabled look-up, avoid subsequent node to carry out hardware modification, thereby complexity and the lower deployment cost of subsequent node are reduced, the promotion and application of the stream switching technology that is conducive to table look-up based on Hash.
Referring to Figure 10, the present embodiment provides a kind of system of message repeating, comprising: Ingress node 801, intermediate node 802 and Egress node 803;
Ingress node 801, for receiving 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 MPLS label is sent to intermediate node 802;
Intermediate node 802, for by an IP message repeating that adds MPLS label to Egress node 803;
Egress node 803, for MPLS label is converted to corresponding traffic identifier, and according to traffic identifier, forwards an IP message.
Wherein, Ingress node 801 comprises: the first converting unit or the second converting unit;
The first converting unit, for using traffic identifier as MPLS label;
The second converting unit, for according to the mapping relations of traffic identifier and MPLS label, is converted to corresponding MPLS label by traffic identifier.
Wherein, Egress node 803 comprises: the 3rd converting unit or the 4th converting unit;
The 3rd converting unit, for using MPLS label as traffic identifier;
The 4th converting unit, for according to the mapping relations of traffic identifier and MPLS label, is converted to corresponding traffic identifier by MPLS.
Wherein, Ingress node 801, also for before generating traffic identifier according to an IP message, 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 at least comprises: traffic identifier and outbound port No. the first, traffic identifier is arranged in the stream extension header of the 2nd IP message, and forwards the 2nd IP message; According to first-class table, by an IP message repeating that adds MPLS label to intermediate node 802;
Egress node 803, also, for receiving the 2nd IP message, sets up second table according to the traffic identifier in the stream extension header of the 2nd IP message, and second table at least comprises: traffic identifier and outbound port No. the second; According to traffic identifier and second table, forward an IP message.
Wherein, the 2nd IP message is IP operation management maintain OAM message, in the stream extension header of IP OAM message, also carries service quality QoS parameter, for consulting qos parameter or carrying out qos statistic.
The present embodiment receives an IP message by Ingress node, generate traffic identifier according to an IP message, traffic identifier is converted to corresponding MPLS label, by an IP message repeating that adds MPLS label to intermediate node, intermediate node by an IP message repeating that adds MPLS label to Egress node, MPLS label is converted to corresponding traffic identifier by Egress node, and according to traffic identifier, forward an IP message, realize a kind of Ingress node that only needs and supported the stream switching technology that traffic identifier generates, the stream switching technology that for example Hash is tabled look-up, avoid subsequent node to carry out hardware modification, thereby complexity and the lower deployment cost of subsequent node are reduced, the promotion and application of the stream switching technology that is conducive to table look-up based on Hash.
All or part of content in the technical scheme that above embodiment provides can realize by software programming, and its software program is stored in the storage medium can read, storage medium for example: hard disk, CD or floppy disk in computer.
The foregoing is only preferred embodiment of the present invention, in order to limit the present invention, within the spirit and principles in the present invention not all, any amendment of doing, be equal to replacement, improvement etc., within all should being included in protection scope of the present invention.
Claims (11)
1. a method for message repeating, 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 traffic identifier is converted to corresponding multiprotocol label switching MPLS label by described Ingress node;
A described IP message that adds described MPLS label is sent to intermediate node by described Ingress node;
Described intermediate node by a described IP message repeating of described described interpolation MPLS label to Egress node;
Described MPLS label is converted to corresponding traffic identifier by described Egress node, and according to described traffic identifier, forward a described IP message;
Wherein, 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 at least comprises: described traffic identifier and outbound port No. the first;
Described Ingress node is arranged on described traffic identifier in the stream extension header of described the 2nd IP message, described Ingress node forwards described the 2nd IP message, make the Egress node that receives described the 2nd IP message set up second table according to described traffic identifier, described second table at least comprises: described traffic identifier and outbound port No. the second.
2. the method for claim 1, is characterized in that, described Ingress node is converted to corresponding multiprotocol label switching MPLS label by described traffic identifier and comprises:
Described Ingress node is using described traffic identifier as described MPLS label;
Or described Ingress node, according to the mapping relations of traffic identifier and MPLS label, is converted to corresponding described MPLS label by described traffic identifier;
Described Egress node is converted to corresponding traffic identifier by described MPLS label and comprises:
Described Egress node is using described MPLS label as described traffic identifier;
Or described Egress node, according to the mapping relations of traffic identifier and MPLS label, is converted to corresponding described traffic identifier by described MPLS.
3. the method for claim 1, is characterized in that, described Ingress node comprises a described IP message repeating that adds described MPLS label to intermediate node:
Described Ingress node, according to described first-class table, sends to intermediate node by a described IP message that adds described MPLS label;
Described MPLS label is converted to corresponding traffic identifier by described Egress node, and according to described traffic identifier, forward a described IP message and comprise:
Described MPLS label is converted to corresponding traffic identifier by described Egress node, and according to described traffic identifier and described second table, forward a described IP message.
4. the method for claim 1, is characterized in that, described the 2nd IP message is IP operation management maintain OAM message, in the stream extension header of described IP OAM message, also carries service quality QoS parameter, for consulting qos parameter or carrying out qos statistic.
5. an Ingress node, is characterized in that, described Ingress node comprises:
The first receiver module, for receiving the first Internet protocol IP message;
Generation module, generates traffic identifier for the IP message receiving according to described the first receiver module;
Modular converter, is converted to corresponding multiprotocol label switching MPLS label for the traffic identifier that described generation module is generated;
The first sending module, for a described IP message that adds the MPLS label that obtains of described modular converter is sent to intermediate node, make described intermediate node by a described IP message repeating of described described interpolation MPLS label to Egress node;
Wherein, described the first receiver module, also for receiving the 2nd IP message;
Described generation module, also generates described traffic identifier for the 2nd IP message receiving according to described the first receiver module, and sets up first-class table according to described traffic identifier, and described first-class table at least comprises: described traffic identifier and outbound port No. the first;
Described the first sending module, also for described traffic identifier being arranged on to the stream extension header of described the 2nd IP message, and forward described the 2nd IP message, make the Egress node that receives described the 2nd IP message set up second table according to described traffic identifier, described second table at least comprises: described traffic identifier and outbound port No. the second;
Described the first sending module, also, for according to described first-class table, sends to intermediate node by a described IP message that adds described MPLS label.
6. Ingress node as claimed in claim 5, is characterized in that, described modular converter comprises: the first converting unit or the second converting unit;
Described the first converting unit, for using described traffic identifier as described MPLS label;
Described the second converting unit, for according to the mapping relations of traffic identifier and MPLS label, is converted to corresponding described MPLS label by described traffic identifier.
7. Ingress node as claimed in claim 5, is characterized in that, described the 2nd IP message is IP operation management maintain OAM message, in the stream extension header of described IP OAM message, also carries service quality QoS parameter, for consulting qos parameter or carrying out qos statistic.
8. an Egress node, is characterized in that, described Egress node comprises:
The second receiver module, be used for the first Internet protocol IP message of the interpolation multiprotocol label switching MPLS label that receives intermediate node forwarding, described MPLS label is that Ingress node generates traffic identifier according to a described IP message, and described traffic identifier is converted to;
The second forwarding module, for described MPLS label is converted to corresponding traffic identifier, and according to described traffic identifier, forwards a described IP message;
Wherein, described the second receiver module, also, for receiving the 2nd IP message from described Ingress node, carries described traffic identifier in the stream extension header of described the 2nd IP message;
Described node also comprises sets up module, and for setting up second table according to described traffic identifier, described second table at least comprises: described traffic identifier and outbound port No. the second;
Described the second forwarding module, also, for according to described traffic identifier and described second table, forwards a described IP message.
9. Egress node as claimed in claim 8, is characterized in that, described the second forwarding module comprises: the 3rd converting unit or the 4th converting unit;
Described the 3rd converting unit, for using described MPLS label as described traffic identifier;
Described the 4th converting unit, for according to the mapping relations of traffic identifier and MPLS label, is converted to corresponding described traffic identifier by described MPLS.
10. Egress node as claimed in claim 8, is characterized in that, described the 2nd IP message is IP operation management maintain OAM message, in the stream extension header of described IP OAM message, also carries service quality QoS parameter, for consulting qos parameter or carrying out qos statistic.
The system of 11. 1 kinds of message repeatings, is characterized in that, described system comprises: Ingress node, intermediate node and Egress node;
Described Ingress node, be used for receiving 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, for giving described Egress node by a described IP message repeating of described described interpolation MPLS label;
Described Egress node, for described MPLS label is converted to corresponding traffic identifier, and according to described traffic identifier, forwards a described IP message;
Wherein, described Ingress node, also for before generating traffic identifier according to a described IP message, receive the 2nd IP message, generate described traffic identifier according to described the 2nd IP message, and set up first-class table according to described traffic identifier, described first-class table at least comprises: described traffic identifier and outbound port No. the first, described traffic identifier is arranged in the stream extension header of described the 2nd IP message, and forwards described the 2nd IP message; According to described first-class table, give described intermediate node by a described IP message repeating of the described MPLS label of interpolation;
Described Egress node, also, for receiving described the 2nd IP message, sets up second table according to the traffic identifier in the stream extension header of described the 2nd IP message, and described second table at least comprises: described traffic identifier and outbound port No. the second; According to described traffic identifier and described second table, forward 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 CN102271079A (en) | 2011-12-07 |
| CN102271079B true 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) |
Families Citing this family (21)
| 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 |
| WO2014166073A1 (en) * | 2013-04-09 | 2014-10-16 | 华为技术有限公司 | Packet forwarding method and network device |
| WO2015078008A1 (en) * | 2013-11-29 | 2015-06-04 | 华为技术有限公司 | Link discovery method, system and device |
| CN104158755B (en) | 2014-07-30 | 2017-12-05 | 华为技术有限公司 | The methods, devices and systems of transmitting message |
| CN104486218B (en) * | 2014-12-16 | 2017-12-22 | 上海斐讯数据通信技术有限公司 | A kind of MPLS network control system and method based on SDN |
| CN106034089A (en) * | 2015-03-20 | 2016-10-19 | 中兴通讯股份有限公司 | Message scheduling method and device based on scheduling flow identification |
| CN106330704B (en) * | 2015-06-26 | 2019-12-06 | 新华三技术有限公司 | Message forwarding method and device |
| EP3306871B1 (en) * | 2015-11-27 | 2021-08-11 | Huawei Technologies Co., Ltd. | Method and apparatus for acquiring path information |
| CN106817299B (en) * | 2015-11-27 | 2019-11-29 | 新华三技术有限公司 | The list item generation method and device and message forwarding method of software defined network |
| 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 |
| CN108206746B (en) * | 2016-12-16 | 2020-07-21 | 华为技术有限公司 | Network transmission control method and related equipment |
| 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 |
| CN112368980B (en) * | 2018-07-13 | 2022-03-01 | 华为技术有限公司 | Method for adding one or more network services to an MPLS network |
| CN111385212B (en) * | 2018-12-29 | 2021-08-31 | 华为技术有限公司 | 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 |
| CN109743340B (en) * | 2019-04-04 | 2019-07-30 | 华为技术有限公司 | The method and network equipment of Message processing |
| CN113904950B (en) * | 2021-12-06 | 2022-02-22 | 广东睿江云计算股份有限公司 | Stream-based network monitoring method and device, computer equipment and storage medium |
Citations (3)
| 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 |
| CN1949779A (en) * | 2005-10-12 | 2007-04-18 | 丛林网络公司 | Checking for spoofed labels within a label switching computer network |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100765320B1 (en) * | 2005-09-14 | 2007-10-09 | 삼성전자주식회사 | MPLS Network and Method for Applying Mobile IP to MPLS Network |
-
2010
- 2010-06-04 CN CN201010193414.2A patent/CN102271079B/en active Active
Patent Citations (3)
| 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 |
| CN1949779A (en) * | 2005-10-12 | 2007-04-18 | 丛林网络公司 | Checking for spoofed labels within a label switching computer network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102271079A (en) | 2011-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102271079B (en) | Message forwarding method, node and system | |
| US6408001B1 (en) | Method for determining label assignments for a router | |
| US6735190B1 (en) | Packet transport method device utilizing header removal fields | |
| US8213311B2 (en) | Control plane to data plane binding | |
| US8427953B2 (en) | Tunnel provisioning with link aggregation and hashing | |
| US20080159150A1 (en) | Method and Apparatus for Preventing IP Datagram Fragmentation and Reassembly | |
| JP2003078556A (en) | Network system, network repeater system, network relay monitoring device and network operating method | |
| CN106454414B (en) | A kind of multipath network method for real-time video transmission | |
| WO2021185043A1 (en) | Forwarding path establishment method and apparatus, and computer-readable storage medium | |
| EP3547690B1 (en) | Real-time video transmission method of multipath network | |
| CN109818960B (en) | Data processing method and device | |
| Rahman et al. | Performance analysis and the study of the behavior of MPLS protocols | |
| JP3688525B2 (en) | Packet flow control method and router apparatus | |
| Matrawy et al. | A survey of congestion control schemes for multicast video applications | |
| CN111131911A (en) | Multicast method and device | |
| CN111565323B (en) | Flow control method and device, electronic equipment and storage medium | |
| CN114710975A (en) | Multi-domain transport multi-transport network context identification | |
| US20180167257A1 (en) | Methods and systems for forming network connections | |
| Volkert et al. | Multipath video streaming based on hierarchical routing management | |
| CN110740087B (en) | Message transmission method, terminal, gateway device, electronic device and storage medium | |
| Aijaz et al. | Performance Evaluation of Multi-protocol Label Switching-Traffic Engineering Schemes | |
| Jurca et al. | Distributed media rate allocation in multipath networks | |
| CN104994331A (en) | Method and system for transmitting flows between networks in low-speed link | |
| Jabbar et al. | An Оverview of the Мultipath Тechnologies, their Importance and Types | |
| Rong et al. | LSMR: A label switching multipath routing protocol for ad hoc 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 |
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. |
|
| TR01 | Transfer of patent right | ||
| 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. |
|
| CP02 | Change in the address of a patent holder |