CN106453138B - Message processing method and device - Google Patents
Message processing method and device Download PDFInfo
- Publication number
- CN106453138B CN106453138B CN201611058038.XA CN201611058038A CN106453138B CN 106453138 B CN106453138 B CN 106453138B CN 201611058038 A CN201611058038 A CN 201611058038A CN 106453138 B CN106453138 B CN 106453138B
- Authority
- CN
- China
- Prior art keywords
- message
- local
- qos
- packet
- flow table
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/50—Queue scheduling
- H04L47/62—Queue scheduling characterised by scheduling criteria
- H04L47/6215—Individual queue per QOS, rate or priority
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application provides a message processing method and a device, the method is applied to forwarding equipment, and the method comprises the following steps: receiving a first message through a first port; finding a first flow table item matched with the first message in local existing flow table items; determining that the output port indicated by the first flow table item is a second port, setting the value of QoS-local-ID of the first message as the value of queue ID indicated by the first flow table item according to the QoS strategy enabled by the second port, and adding the first message into the output port queue matched with the Qos-local-ID of the first message. According to the method, the queue ID of the OpenFlow queue is transmitted through the internal attribute QoS-local-ID of the message, so that the OpenFlow queue function and the priority mapping function can be used simultaneously.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for processing a packet.
Background
After the packet enters the forwarding device, the forwarding device may perform priority mapping, OpenFlow forwarding processing, and the like on the packet.
The so-called priority mapping is to implement the conversion between the Quality of Service (QoS) priority carried by a packet and the Local Priority (LP) inside the device. The priority mapping may include a priority mapping in an ingress direction and a priority mapping in an egress direction. In the incoming direction, when a message enters the equipment, the QoS priority carried by the message is mapped into a local priority; in the outgoing direction, when a device sends a message, the local priority of the message is remapped to the QoS priority.
The OpenFlow forwarding process is to match the packet with an OpenFlow flow entry on the device, and if the matching is successful, perform a Set-Queue setting (Set-Queue) on the packet according to the matched flow entry, and send the packet to a corresponding port for forwarding.
Action queue setting is to set a dequeue Identifier (ID) of a packet, and when forwarding the packet to a port, the queue ID indicates which queue is used among the queues associated with the port to forward the packet.
At present, forwarding devices transmit a queue Identifier (ID) mainly through a local priority of a packet, that is, before the packet enters a queue, a value of the local priority of the packet is modified into the queue ID. And then, the forwarding equipment sends the message to a corresponding queue for processing according to the queue ID carried by the local priority of the message.
However, since the priority mapping in the ingress direction occurs before the OpenFlow forwarding process, the priority mapping in the egress direction occurs after the OpenFlow forwarding process. If the value of the local priority of the packet is modified again for transmitting the queue ID after the priority mapping in the ingress direction, then the local priority of the packet cannot be used to implement the priority mapping in the egress direction. This results in the OpenFlow forwarding processing function and the priority mapping function of the forwarding device not being used simultaneously.
Disclosure of Invention
In view of this, the present application provides a message processing method and apparatus, so as to solve the problem that the OpenFlow forwarding processing function and the function using the local priority (such as the priority mapping function) cannot be used simultaneously.
Specifically, the method is realized through the following technical scheme:
in a first aspect of the present application, a method for processing a packet is provided, where the method is applied to a forwarding device, and includes:
receiving a first message through a first port;
finding a first flow table item matched with the first message in local existing flow table items;
determining that the output port indicated by the first flow table item is a second port, setting the value of QoS-local-ID of the first message as the value of a queue identifier ID indicated by the first flow table item according to a QoS strategy enabled by the second port, and adding the first message into an output port queue matched with the Qos-local-ID of the first message.
In a second aspect of the present application, a packet processing apparatus is provided, where the apparatus may be applied to a forwarding device and has a function of implementing the foregoing method. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules or units corresponding to the above functions.
In one possible implementation, the apparatus includes:
a receiving unit, configured to receive a first packet through a first port;
a matching unit, configured to find a first flow table entry matching the first packet in a local existing flow table entry;
and the processing unit is used for determining that the output port indicated by the first flow table item is a second port, setting the value of the QoS-local-ID of the first message as the value of the queue identifier ID indicated by the first flow table item according to the QoS strategy enabled by the second port, and adding the first message into the output port queue matched with the QoS-local-ID of the first message.
In another possible implementation manner, the apparatus includes a communication interface, a processor, a memory, and a bus, where the communication interface, the processor, and the memory are connected to each other through the bus; the processor executes the message processing method according to the first aspect of the present application by reading the logic instruction stored in the memory.
By using the scheme provided by the application, the queue ID of the OpenFlow queue is transmitted through the internal attribute QoS-local-ID (quality of service local identifier) of the message, so that the OpenFlow queue function and the priority mapping function can be used simultaneously.
Drawings
Fig. 1 is a schematic diagram of an OpenFlow virtual network to which a message processing method according to an embodiment of the present invention is applied;
fig. 2 is a flowchart of a message processing method according to an embodiment of the present application;
FIG. 3 is a schematic diagram of the networking of an embodiment of the present application;
FIG. 4 is a QoS policy diagram according to an embodiment of the present application;
FIG. 5 is a diagram illustrating an association between a flow entry, QoS-local-id and a queue in a forwarding device according to an embodiment of the present application;
fig. 6 is a functional block diagram of a message processing apparatus according to an embodiment of the present application;
fig. 7 is a hardware architecture diagram of a message processing apparatus according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
Hereinafter, some terms in the present application will be explained first.
QoS priority: carried in the header of the message. Commonly used QoS priority fields include 802.1p, Differentiated Services Code Point (DSCP), exp (experimental), and the like. Users may use different QoS priority fields in different networks according to Network planning, such as 802.1p in a Virtual Local Area Network (VLAN) Network, DSCP in an Internet Protocol (IP) Network, and EXP in a Multi-Protocol Label Switching (MPLS) Network.
Local priority: the message is a priority with local significance, and after the message reaches the forwarding device, a local data field is allocated, and the local data field can be used for storing the local priority. The local priority is only 0-7 eight values and corresponds to eight output port queues of queue 0-queue 7.
The technical scheme of the application is described in the following with the accompanying drawings and various embodiments of the specification.
The processing flow of the forwarding device to the packet can be briefly described as follows:
firstly, performing priority mapping and other service processing on a message in an incoming direction; secondly, searching a routing table; thirdly, carrying out OpenFlow forwarding processing on the message; then, mapping the priority of the message in the outgoing direction; and finally, performing message queuing processing.
Since the implementation order of the OpenFlow forwarding processing is after the priority mapping in the ingress direction and before the priority mapping in the egress direction, both the OpenFlow forwarding processing and the priority mapping need to use the local priority, it is currently impossible for a device to use both the priority mapping function and the OpenFlow forwarding processing function.
Therefore, the application provides a message processing method and device, which are used for transmitting the queue ID of the OpenFlow queue through the internal attribute QoS-local-ID (quality of service local identifier) of the message, so that the OpenFlow queue function and the priority mapping function can be used simultaneously.
The message processing method provided by the present application may be applied to an OpenFlow virtual network shown in fig. 1, where the OpenFlow virtual network includes an OpenFlow controller (hereinafter referred to as a controller) 100, a forwarding device 110, and a secure channel (secure channel)120, where the controller 100 and the forwarding device 110 communicate with each other through the pre-configured secure channel 120.
The controller 100 is a control center of the OpenFlow virtual network, and is configured to generate a flow table according to a configuration of a user or a dynamically operating protocol, and send the flow table to the forwarding device 110. The flow table is a core data structure for the forwarding device 110 to perform forwarding policy control, and includes a matching field (Match), a Counter (Counter), and an Action field (Action).
The forwarding device 110 is configured to receive the flow table issued by the controller 100, and process the packet according to the flow table, such as OpenFlow forwarding processing, priority mapping, and the like.
The following describes a message processing method provided in the present application with reference to fig. 2.
Referring to fig. 2, fig. 2 is a flow chart of a method provided by the present application. As shown in fig. 2, the process may include the following steps:
step 201: the forwarding device receives the message through the first port.
Step 202: and the forwarding equipment finds a first flow table item matched with the first message in the local existing flow table items.
Step 203: and the forwarding equipment determines that the output port indicated by the first flow table item is a second port, sets the value of QoS-local-ID of the first message as the value of the queue ID indicated by the first flow table item according to the QoS strategy enabled by the second port, and adds the first message into the output port queue matched with the Qos-local-ID of the first message.
The controller issues a local flow entry of the forwarding device to the forwarding device in advance, where the flow entry generally includes a matching field and an action field.
The matching field is used for matching the message, and may be a five-tuple of the message, a type of the message (e.g., a video service message, a voice service message), and the like.
In this application, the action field of the flow entry is used to instruct that when a packet matches with the matching field, the value of QoS-local-ID of the matching packet is set to the value of the specified queue ID, and the matching packet is forwarded to the specified egress port, for example, the action field may instruct that the matching packet is forwarded to a specific egress port R2, and QoS-local-ID of the matching packet is assigned to 1. The message will eventually be sent from the queue with queue ID 1 of egress port R2.
In the present application, different messages sent by the same device and addressed to the same destination device may be sent from different queues at the same port of the forwarding device when passing through the forwarding device. The specific implementation mode is as follows:
the forwarding device receives a second packet through the first port, where the second packet is different from the first packet in step 201.
For example, if the five-tuple of the first packet is different from the second packet, e.g., the source port of the first packet is different from the source port of the second packet, the second packet may be considered different from the first packet. For another example, if the type of the first packet is different from that of the second packet, such as the first packet is a video service packet and the second packet is a voice service packet, the second packet may also be considered to be different from the first packet.
After receiving the second message, the forwarding device finds a second flow table entry matched with the second message in the local existing flow table entries.
Then, the forwarding device determines that the output port indicated by the second flow table entry is the second port, sets the value of the QoS-local-ID of the second packet as the value of the queue ID indicated by the second flow table entry according to the QoS policy enabled by the second port, and adds the second packet to the output port queue matched with the QoS-local-ID of the second packet.
Wherein if the value set for the QoS-local-id of the first packet is different from the value set for the QoS-local-id of the second packet, the first packet and the second packet enter different egress port queues and are forwarded from different egress port queues, although both the first packet and the second packet are forwarded to the second port.
Different queues may correspond to different flow behaviors, where the flow behaviors are QoS actions performed on packets, and include Assured Forwarding (AF), Expedited Forwarding (EF), Weighted Fair Queuing (WFQ), and the like.
According to the method and the device, the queue ID of the OpenFlow queue is transmitted through the internal attribute QoS-local-ID of the message, and the queue ID is not carried by using the local priority of the message, so that a priority mapping function or other functions using the local priority can be used simultaneously with an OpenFlow forwarding processing function.
Taking the priority mapping function as an example, before finding the flow entry matched with the packet, the forwarding device may map the initial QoS priority carried by the packet to a local priority according to a preset priority mapping relationship in the ingress direction; and after a flow table item matched with the message is found, mapping the local priority of the message into a new QoS priority according to a preset priority mapping relation in the outgoing direction, and replacing the initial QoS priority carried by the message with the new QoS priority.
The value or type of QoS priority may vary before and after mapping.
For example, when the priority values of some packets need to be raised according to the actual networking requirements to achieve the purpose of processing the packets preferentially, the mapping relationship of different priority values of the same priority field may be configured on the forwarding device.
For example, priority mapping is configured to DSCP-LP (60-6) in the ingress direction, and priority mapping is configured to LP-DSCP (6-63) in the egress direction, then after a certain message with initial DSCP of 60 enters the forwarding device, LP of the message may be set to 6 by priority mapping in the ingress direction, and the value of DSCP carried by the message may be set to 63 by priority mapping in the egress direction.
For another example, when a packet passes through different networks, in order to maintain the priority of the packet, the mapping relationship of different priority fields may be configured on the forwarding devices connected to the different networks.
For example, when a packet with an initial DSCP of 60 enters a forwarding device, LP of the packet may be set to 6 in the ingress direction through priority mapping, and the priority field of the packet may be modified to EXP in the egress direction through priority mapping, if the packet with the initial DSCP of 60 is configured with DSCP-LP (60-6) and the packet with the priority mapping to LP-EXP (6-50) in the egress direction.
In addition, because the value range of the internal attribute QoS-local-id of the message is 1 to 4095, if the message is sent into different queues by matching the QoS-local-id, the range of the number of queues which can be set by each port of the forwarding equipment is 1 to 4095, that is, maximum 4095 queues can be set at each output port, obviously, the available range of the queues is improved, and the application scene of a large number of queues can be met.
In order to more clearly describe the technical solution of the present application, the above technical solution is further described below by using an embodiment, and it should be noted that this embodiment is only one implementation manner of the present application, and does not limit the present application.
Referring to fig. 3, it is assumed that 4 different message flows sent from device a to device B enter from port R1 of the forwarding device and exit from port R2 when passing through the forwarding device. In order to make these 4 message flows be able to be forwarded through different queues at port R2 of the forwarding device, the following procedures are implemented:
1. the controller issues 4 flow table entries to the forwarding device, the matching fields of the 4 flow table entries are respectively matched with the 4 message flows, and the action field of the flow table entry designates an egress interface (port R2) and a queue ID (such as 1, 2, 3, 4, etc.) set in the message.
2. The forwarding device configures a QoS policy on the R2 interface, that is, sets a classification rule of a flow and a flow behavior corresponding to a queue, and binds the classification rule and the flow behavior of the flow. In the present application, the flow classification rule may be based on the QoS-local-id value of the packet, and the flow behavior of the queue may select AF, EF, WFQ, and the like. An example of QoS policy configuration is shown in fig. 4, where a packet is sent to queue 1 when the QoS-local-id of the packet is 1; when the QoS-local-id of the message is 2, sending the message into a queue 2; when the QoS-local-id of the message is 3, sending the message into a queue 3; when the QoS-local-id of the message is 4, the message is sent into a queue 4.
3. The 4 message flows from device a to device B enter from port R1 of the forwarding device. The forwarding device matches the message flow with the flow table items preset in the local by the controller one by one, and sets the action Queue (Set-Queue) for the message according to the matched flow table items. For example, the QoS-local-id of message flow 1 is assigned to 1, the QoS-local-id of message flow 2 is assigned to 2, the QoS-local-id of message flow 3 is assigned to 3, the QoS-local-id field of message flow 4 is assigned to 4, and then the 4 message flows are sent to port R2.
4. These 4 flows match their own QoS-local-id values into different queues at port R2. As shown in FIG. 5, QoS-local-id (1) corresponds to queue 1, QoS-local-id (2) corresponds to queue 2, QoS-local-id (3) corresponds to queue 3, and QoS-local-id (4) corresponds to queue 4. Finally, message flow 1 is sent from queue 1 at port R2, message flow 2 is sent from queue 2 at port R2, message flow 3 is sent from queue 3 at port R2, and message flow 4 is sent from queue 4 at port R2.
The methods provided herein are described above. The apparatus provided in the present application is described below.
Referring to fig. 6, this figure is a functional block diagram of a message processing apparatus according to an embodiment of the present application, where the apparatus may be applied to a forwarding device. The apparatus comprises a receiving unit 601, a matching unit 602 and a processing unit 603.
The receiving unit 601 is configured to receive a first packet through a first port.
The matching unit 602 is configured to find a first flow entry matching the first packet in a local existing flow entry.
The processing unit 603 is configured to determine that the egress port indicated by the first flow entry is a second port, set the value of QoS-local-ID of the first packet to the value of the queue identifier ID indicated by the first flow entry according to the QoS policy enabled by the second port, and add the first packet to the egress port queue matched with the QoS-local-ID of the first packet.
Optionally, the receiving unit 601 may further be configured to: and receiving a second message through the first port, wherein the second message is different from the first message.
The matching unit 602 may further be configured to: and finding a second flow table item matched with the second message in the local existing flow table items.
The processing unit 603 may be further configured to: and determining that the output port indicated by the second flow table item is the second port, setting the value of QoS-local-ID of the second message as the value of the queue ID indicated by the second flow table item according to the QoS strategy enabled by the second port, and adding the second message into the output port queue matched with the QoS-local-ID of the second message.
Wherein the value of QoS-local-id of the first packet is different from the value of QoS-local-id of the second packet, so that the first packet and the second packet will enter different egress port queues and be sent out from different queues of the same port.
Optionally, the apparatus may further include:
a mapping unit, configured to map, before the matching unit 602 finds, in an existing local flow entry, a first flow entry matched with the first packet, an initial QoS priority carried by the first packet to a local priority according to a preset priority mapping relationship in an incoming direction. And after the matching unit 602 finds a first flow table entry matched with the first packet in the local existing flow table entries, according to a preset priority mapping relationship in the outgoing direction, mapping the local priority of the first packet to a new QoS priority, and replacing the initial QoS priority carried by the packet with the new QoS priority.
Optionally, the number of queues settable by the second port ranges from 1 to 4095.
Optionally, the flow table entry is issued to the forwarding device by a controller; the flow entry includes a matching field for matching the packet, and an action field for instructing to set a value of QoS-local-ID of the matching packet to a value of a specified queue ID when the packet matches the matching field, and to forward the matching packet to a specified egress port.
It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation. The functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
As shown in fig. 7, an embodiment of the present application further provides a message processing apparatus, where the apparatus includes a communication interface 701, a processor 702, a memory 703, and a bus 704; the communication interface 701, the processor 702, and the memory 703 complete communication with each other through the bus 704.
Therein, the communication interface 701 is used for communicating with a network element. The processor 702 may be a Central Processing Unit (CPU), the memory 703 may be a non-volatile memory (non-volatile memory), and the memory 703 stores a message processing logic instruction, and the processor 702 may execute the message processing logic instruction stored in the memory 703 to implement the function of the forwarding device in the message processing method, which is described above with reference to the flow shown in fig. 2.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (10)
1. A message processing method is applied to forwarding equipment and comprises the following steps:
receiving a first message through a first port;
finding a first flow table item matched with the first message in local existing flow table items;
and determining that the output port indicated by the first flow table item is a second port, setting the value of a quality of service local identifier QoS-local-ID of the first message as the value of a queue identifier ID indicated by the first flow table item according to a quality of service QoS strategy enabled by the second port, and adding the first message into an output port queue matched with the QoS-local-ID of the first message.
2. The method of claim 1, wherein the method further comprises:
receiving a second message through the first port, wherein the second message is different from the first message;
finding a second flow table item matched with the second message in the local existing flow table items;
determining that the output port indicated by the second flow table item is the second port, setting the value of QoS-local-ID of the second message as the value of queue ID indicated by the second flow table item according to the QoS strategy enabled by the second port, and adding the second message into the output port queue matched with the QoS-local-ID of the second message;
wherein the value of QoS-local-id of the first packet is different from the value of QoS-local-id of the second packet, and the first packet and the second packet enter different egress port queues.
3. The method of claim 1, wherein before finding a first flow entry matching the first packet in locally existing flow entries, the method further comprises:
mapping the initial QoS priority carried by the first message into a local priority according to a preset priority mapping relation in the incoming direction;
after finding the first flow table entry matching the first packet in the local existing flow table entries, the method further includes:
and mapping the local priority of the first message into a new QoS priority according to a preset priority mapping relation in the outgoing direction, and replacing the initial QoS priority carried by the message with the new QoS priority.
4. The method of claim 1, wherein the second port has a settable number of queues in the range of 1 to 4095.
5. The method of claim 1, wherein the flow table entry is issued by a controller to the forwarding device;
the flow entry includes a matching field for matching the packet, and an action field for instructing to set a value of QoS-local-ID of the matching packet to a value of a specified queue ID when the packet matches the matching field, and to forward the matching packet to a specified egress port.
6. A message processing apparatus, wherein the apparatus is applied to a forwarding device, and comprises:
a receiving unit, configured to receive a first packet through a first port;
a matching unit, configured to find a first flow table entry matching the first packet in a local existing flow table entry;
and the processing unit is used for determining that the output port indicated by the first flow table item is a second port, setting the value of a quality of service local identifier QoS-local-ID of the first message as the value of a queue identifier ID indicated by the first flow table item according to a quality of service QoS strategy enabled by the second port, and adding the first message into an output port queue matched with the QoS-local-ID of the first message.
7. The apparatus of claim 6,
the receiving unit is further configured to:
receiving a second message through the first port, wherein the second message is different from the first message;
the matching unit is further configured to:
finding a second flow table item matched with the second message in the local existing flow table items;
the processing unit is further to:
determining that the output port indicated by the second flow table item is the second port, setting the value of QoS-local-ID of the second message as the value of queue ID indicated by the second flow table item according to the QoS strategy enabled by the second port, and adding the second message into the output port queue matched with the QoS-local-ID of the second message;
wherein the value of QoS-local-id of the first packet is different from the value of QoS-local-id of the second packet, and the first packet and the second packet enter different egress port queues.
8. The apparatus of claim 6, wherein the apparatus further comprises:
a mapping unit, configured to map, before the matching unit finds, in an existing local flow table entry, a first flow table entry matching the first packet, an initial QoS priority carried by the first packet to a local priority according to a preset priority mapping relationship in an incoming direction;
and after the matching unit finds a first flow table item matched with the first message in the existing local flow table items, mapping the local priority of the first message into a new QoS priority according to a preset priority mapping relation in the outgoing direction, and replacing the initial QoS priority carried by the message with the new QoS priority.
9. The apparatus of claim 6, wherein the second port is configurable for a number of queues ranging from 1 to 4095.
10. The apparatus of claim 6, wherein the flow table entry is issued by a controller to the forwarding device;
the flow entry includes a matching field for matching the packet, and an action field for instructing to set a value of QoS-local-ID of the matching packet to a value of a specified queue ID when the packet matches the matching field, and to forward the matching packet to a specified egress port.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611058038.XA CN106453138B (en) | 2016-11-25 | 2016-11-25 | Message processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611058038.XA CN106453138B (en) | 2016-11-25 | 2016-11-25 | Message processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106453138A CN106453138A (en) | 2017-02-22 |
| CN106453138B true CN106453138B (en) | 2020-03-06 |
Family
ID=58219613
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611058038.XA Active CN106453138B (en) | 2016-11-25 | 2016-11-25 | Message processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106453138B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018170833A1 (en) | 2017-03-23 | 2018-09-27 | Oppo广东移动通信有限公司 | Uplink data transmission method, terminal, network side device and system |
| CN109729022B (en) * | 2017-10-30 | 2020-07-28 | 华为技术有限公司 | Data sending method, device and system based on software defined network |
| CN109194581B (en) * | 2018-08-24 | 2020-12-25 | 新华三技术有限公司 | Message processing method and device |
| CN111385212B (en) * | 2018-12-29 | 2021-08-31 | 华为技术有限公司 | Data transmission technology and neural network system |
| CN109889453B (en) * | 2019-01-31 | 2022-07-01 | 新华三技术有限公司 | HQoS (quality of service) implementation method and device |
| CN112242966B (en) * | 2019-07-19 | 2023-11-28 | 华为技术有限公司 | Data forwarding method and device |
| CN112787827A (en) * | 2019-11-08 | 2021-05-11 | 华为技术有限公司 | Communication method, device and system |
| CN111865838B (en) * | 2020-07-21 | 2022-03-08 | 深圳市风云实业有限公司 | Multichannel data transmission system of signal |
| CN116112452A (en) * | 2021-11-11 | 2023-05-12 | 华为技术有限公司 | Message transmission method and communication device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104243362A (en) * | 2013-06-24 | 2014-12-24 | 杭州华三通信技术有限公司 | Message forwarding method and device |
| CN104823416A (en) * | 2012-11-29 | 2015-08-05 | 华为技术有限公司 | Packet prioritization in a software-defined network implementing OpenFlow |
| CN105376158A (en) * | 2015-10-12 | 2016-03-02 | 上海斐讯数据通信技术有限公司 | SDN circulation method and device based on EXP value in MPLS message |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104378309B (en) * | 2013-08-16 | 2019-05-21 | 中兴通讯股份有限公司 | Method, system and the relevant device of QoS are realized in OpenFlow network |
-
2016
- 2016-11-25 CN CN201611058038.XA patent/CN106453138B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104823416A (en) * | 2012-11-29 | 2015-08-05 | 华为技术有限公司 | Packet prioritization in a software-defined network implementing OpenFlow |
| CN104243362A (en) * | 2013-06-24 | 2014-12-24 | 杭州华三通信技术有限公司 | Message forwarding method and device |
| CN105376158A (en) * | 2015-10-12 | 2016-03-02 | 上海斐讯数据通信技术有限公司 | SDN circulation method and device based on EXP value in MPLS message |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106453138A (en) | 2017-02-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106453138B (en) | Message processing method and device | |
| EP3624408B1 (en) | Method for generating forwarding table entry, controller, and network device | |
| US20220103477A1 (en) | Packet processing method for implementing qos guarantee, device, and system | |
| EP3866414A1 (en) | Message processing method, apparatus, device and system | |
| US11394646B2 (en) | Packet sending method, network node, and system | |
| EP1401161A2 (en) | Quality of service (QOS) mechanism in an internet protocol (IP) network | |
| US20070206602A1 (en) | Methods, systems and apparatus for managing differentiated service classes | |
| US8284789B2 (en) | Methods and apparatus for providing dynamic data flow queues | |
| US20160323189A1 (en) | Method for controlling qos by handling traffic depending on service | |
| US6473434B1 (en) | Scaleable and robust solution for reducing complexity of resource identifier distribution in a large network processor-based system | |
| EP3094053A1 (en) | Predictive egress packet classification for quality of service | |
| WO2018149338A1 (en) | Sdn-based remote stream mirroring control method, implementation method, and related device | |
| US20160205041A1 (en) | Bandwidth providing method based on multi-flow grouping | |
| WO2015066878A1 (en) | Control device and control method in software defined network (sdn) | |
| KR20140052847A (en) | Method and apparatus for providing quality of service in software defiend neworking network | |
| EP3718269B1 (en) | Packet value based packet processing | |
| KR100891208B1 (en) | A method of processing a packet data flow in a packet data network, an apparatus thereof, a system thereof and a computer readable recording medium having a computer program for performing the method | |
| CN109039791B (en) | Bandwidth management method and device and computer equipment | |
| US7061919B1 (en) | System and method for providing multiple classes of service in a packet switched network | |
| Cisco | MPLS QoS Multi-VC Mode for PA-A3 | |
| KR101587379B1 (en) | Method of dynamic control for queue size and apparatus thereof | |
| Cisco | Commands: ip rsvp reservation-host -- match ip dscp | |
| Cisco | MPLS QoS Multi-VC Mode for PA-A3 | |
| Demir et al. | A priority-based queuing model approach using destination parameters forreal-time applications on IPv6 networks | |
| KR101445466B1 (en) | Source based queue selection mechanism in the routing environment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant before: Huasan Communication Technology Co., Ltd. |
|
| CB02 | Change of applicant information | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |